CN114281378A

CN114281378A - Vehicle part list management method and device and related equipment

Info

Publication number: CN114281378A
Application number: CN202111549533.1A
Authority: CN
Inventors: 徐大伟
Original assignee: Shanghai Jidu Automobile Co Ltd
Current assignee: Shanghai Jidu Automobile Co Ltd
Priority date: 2021-12-17
Filing date: 2021-12-17
Publication date: 2022-04-05

Abstract

The disclosure provides a vehicle part list management method, a vehicle part list management device and related equipment, and relates to the technical field of data management. The specific implementation scheme is as follows: the vehicle parts list management method comprises the following steps: determining the part type of the target part under the condition of receiving the updating operation aiming at the target part; under the condition that the part type of the target part is a first type, generating a first updating request, wherein the first updating request carries the configuration information of the target part; updating configuration information of the target part in the target object based on the first update request; the target object comprises a structure BOM and N EBOMs associated with the structure BOM, wherein N is an integer larger than 1, the structure BOM comprises configuration information of parts of a first type, the parts of the first type are N parts shared by vehicles and associated with the N EBOMs one by one, each EBOM comprises the parts of the first type and the parts of a second type, and the parts of the second type are N parts not shared by the vehicles.

Description

Vehicle part list management method and device and related equipment

Technical Field

The present disclosure relates to the field of data management technologies, and in particular, to a vehicle part list management method, apparatus, and related device.

Background

In the field of automobile manufacturing technology, currently, a complete part list (Bill of Material, BOM) of an automobile is generally managed in an Excel form, and as the number of automobile models increases, a plurality of BOMs are generally managed.

There is no way in the prior art to automate the topographic management of BOM for multiple vehicle models.

Disclosure of Invention

The disclosure provides a vehicle part list management method and device and related equipment.

According to a first aspect of the present disclosure, there is provided a vehicle parts list management method including:

determining a part type of a target part in the case of receiving an update operation for the target part;

generating a first updating request under the condition that the part type of the target part is a first type, wherein the first updating request carries the configuration information of the target part;

updating configuration information of the target part in a target object based on the first update request;

the target object comprises a framework part list BOM and N engineering part lists EBOMs associated with the framework BOM, wherein N is an integer greater than 1, the framework BOM comprises configuration information of parts of the first type, the parts of the first type are N parts shared by vehicles associated with the N EBOMs one by one, each EBOM comprises the parts of the first type and parts of a second type, and the parts of the second type are non-shared parts of the N vehicles.

According to a second aspect of the present disclosure, there is provided a vehicle parts list management apparatus including:

the device comprises a receiving module, a judging module and a judging module, wherein the receiving module is used for determining the part type of a target part under the condition of receiving the updating operation aiming at the target part;

a first generation module, configured to generate a first update request when a part type of the target part is a first type, where the first update request carries configuration information of the target part;

an update module to update configuration information of the target part in a target object based on the first update request;

the target object comprises an architecture part list BOM and N engineering part lists EBOMs associated with the architecture BOM, wherein N is an integer greater than 1, the architecture BOM comprises configuration information of parts of the first type, the parts of the first type are used for representing N parts shared by vehicles in one-to-one association with the N EBOMs, each EBOM comprises the parts of the first type and parts of the second type, and the parts of the second type are used for representing the parts which are not shared by the N vehicles.

According to a third aspect of the present disclosure, there is provided an electronic device comprising:

at least one processor; and

a memory communicatively coupled to the at least one processor; wherein the content of the first and second substances,

the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the method of the first aspect.

According to a fourth aspect of the present disclosure, there is provided a non-transitory computer readable storage medium having stored thereon computer instructions for causing a computer to perform the method of the first aspect.

According to a fifth aspect of the present disclosure, there is provided a computer program product comprising a computer program which, when executed by a processor, implements the method of the first aspect.

According to the technology disclosed by the invention, the configuration information of the part of the first type is stored through the framework BOM, the configuration information of the part of the first type and the configuration information of the part of the second type are stored in the EBOM, the part type of the target part is determined when the updating operation aiming at the target part is received, and the configuration information of the target part in the framework BOM and the N EBOMs related to the framework BOM is uniformly updated based on the first updating request when the part type of the target part is of the first type. Therefore, when the configuration information of the first type of parts is updated, the updating management of the plurality of EBOMs is automatically realized, so that each EBOM does not need to be updated repeatedly independently, the working efficiency is improved, and the maintenance and management cost of the vehicle part list is reduced.

It should be understood that the statements in this section do not necessarily identify key or critical features of the embodiments of the present disclosure, nor do they limit the scope of the present disclosure. Other features of the present disclosure will become apparent from the following description.

Drawings

The drawings are included to provide a better understanding of the present solution and are not to be construed as limiting the present disclosure. Wherein:

FIG. 1 is a flow chart of a vehicle parts list management method of the present disclosure;

FIG. 2 is a block diagram of the vehicle parts list management apparatus of the present disclosure;

fig. 3 is a block diagram of an electronic device of the present disclosure.

Detailed Description

Exemplary embodiments of the present disclosure are described below with reference to the accompanying drawings, in which various details of the embodiments of the disclosure are included to assist understanding, and which are to be considered as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the present disclosure. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.

As shown in fig. 1, the present disclosure provides a vehicle parts list management method, including the steps of:

step 101, determining a part type of a target part under the condition of receiving an updating operation aiming at the target part;

102, generating a first updating request under the condition that the part type of the target part is a first type, wherein the first updating request carries configuration information of the target part;

103, updating the configuration information of the target part in the target object based on the first updating request;

the target object comprises a framework part list BOM and N Engineering part lists (EBOMs) associated with the framework BOM, wherein N is an integer greater than 1, the framework BOM comprises configuration information of the parts of the first type, the parts of the first type are parts shared by N vehicles associated with the N EBOMs one by one, each EBOM comprises the parts of the first type and parts of a second type, and the parts of the second type are parts not shared by the N vehicles.

In the embodiment of the present disclosure, the update operation may be used to add a part, delete a part, or modify configuration information of a part. For example, an update interface may be provided based on which a user may query and update a part. The information content specifically included in the configuration information of the part may be set according to actual needs, for example, in some embodiments, the configuration information of the part may include information such as a part number, a part function, an installation position, a part name, a quantity, a vehicle type series configuration, and a purchase level.

Optionally, in some embodiments, the user may query the configuration information of the target part by part name or part number, and after the query, the configuration information of the target part may be displayed on the update interface. At this time, the configuration information of the target part can be deleted or modified through the corresponding operation control, and when the user confirms the deletion or modification, the update operation of the target part is received, so that the part type of the target part can be further determined, and the subsequent deletion or modification operation is executed based on the part type. In addition, the configuration information of the new part can be directly edited on the updating interface, and when the configuration information is edited and the new addition is confirmed through the corresponding operation control, the updating operation of the target part is received, so that the part type of the target part can be further determined, and the subsequent additional operation is executed based on the part type.

It should be understood that in the disclosed embodiments, the part types of the part may include a first type and a second type, where the first type characterizes parts that are common to N vehicles associated with the architecture BOM, and the second type characterizes parts that are not common to N vehicles, i.e., different parts that are used in different vehicles at the same location. The first type of component may also be referred to as a carrier component and the second type of component may also be referred to as a non-carrier component, for example, for a steering wheel, if N measurements all use the steering wheel 1, the steering wheel 1 is a carrier component, and if some of the N vehicles use the steering wheel 1, some use the steering wheel 2, and some use the steering wheel 3, the steering wheel is a non-carrier component. The N vehicles may be understood as vehicles of at least one platform vehicle type under one architecture, each platform vehicle type may comprise vehicles of one or more different vehicle types, such as an architecture derived AA platform, an AB platform and an AC platform, the AA platform comprises three vehicle types of AA1, AA2 and AA3, the AB platform comprises three vehicle types of AB1, AB2 and AB3, and the AC platform comprises three vehicle types of AC1, AC2 and AC 3.

It should be noted that, in the embodiment of the present disclosure, in the process of adding a part, the part type of the target part may be determined based on the part type set on the update interface by the user, for example, an operation option may be provided on the update interface for the user to select the part type. The part type of the newly added target part can also be determined based on different update interfaces, for example, a first update interface is provided for the first type of part, a second update interface is provided for the second type of part, and if the user adds the target part in the first update interface, it indicates that the newly added target part is the first type of part; if the user adds the target part in the second updating interface, the newly added target part is the part of the second type. In this embodiment, different update interfaces may be associated with different update units, and are used to update the configuration information of the part of the corresponding part type. If a first updating unit is set for updating the architecture BOM and a second updating unit is set for each vehicle for updating the corresponding EBOM, the architecture BOM is triggered to be updated when the first updating unit receives an update request, and the configuration information of the update is pushed to each second updating unit based on the update of the architecture BOM, so that each second updating unit is triggered to update the configuration information in the corresponding EBOM.

Optionally, if the target part is a part existing in the architecture BOM or the EBOM, that is, the target operation is used to modify or delete the configuration information of the part in the architecture BOM or the EBOM, the part type of the target part may be determined based on the update interface: for example, the part type of the target part may be determined according to identification information of the part type displayed by the update interface, where the identification information may be determined based on whether the target part is stored in the architecture BOM or based on the type identification of the part in the EBOM, and the identification information of the target interface may be further modified by the user. For another example, the part type of the target part may be determined based on different operation interfaces, for example, a first update interface is provided for the first type of part, a second update interface is provided for the second type of part, and if the user updates the target part in the first update interface, it indicates that the updated target part is the first type of part; if the user updates the target part in the second updating interface, the updated target part is the part of the second type. In some embodiments, the part type of the target part may also be determined directly based on whether the target part is stored in the architecture BOM, or based on the part type identification of the part in the EBOM. It should be understood that, in this embodiment, the configuration information of the part in the EBOM may further include the type of the part, for example, the first type may be represented by a character Y, and the second type may be represented by a character N.

According to the embodiment of the disclosure, configuration information of a first type of part is stored through the framework BOM, configuration information of the first type of part and configuration information of a second type of part are stored in the EBOM, the part type of the target part is determined when an updating operation for the target part is received, and the configuration information of the framework BOM and the configuration information of the target part in the N EBOMs associated with the framework BOM are uniformly updated based on the first updating request when the part type of the target part is the first type. Therefore, when the configuration information of the first type of parts is updated, the updating management of the plurality of EBOMs is automatically realized, so that each EBOM does not need to be updated repeatedly independently, the working efficiency is improved, and the maintenance and management cost of the vehicle part list is reduced.

It should be noted that the above-mentioned architectures BOM and EBOM may be created in advance, or the existing EBOM may be automatically identified to create the EBOM. For example, in some embodiments, the architectures BOM and EBOM may be actively created by a user. Specifically, in the case of receiving an update operation for a target part, before determining a part type of the target part, the method further includes:

acquiring configuration information of at least one first part input by a user, wherein the first part is the part of the first type;

generating the architecture BOM based on configuration information of the first part;

for each of the N vehicles, generating an EBOM for the vehicle based on configuration information for a second part of the vehicle and configuration information for the first part in the architecture BOM, the second part being a second type of part.

In the embodiment of the disclosure, a creation interface may be provided for a user to input configuration information of the first part and configuration information of the second part, for example, a part type identifier may be set on the creation interface, and a part type may be set through the part type identifier. Two different creation interfaces may also be provided for a user to input configuration information for parts of different part types, for example, configuration information for a part input on a first creation interface as a first type of part and configuration information for a part input on a second creation interface as a second type of part. The first generation unit of the architecture BOM and the second generation unit of the EBOM may be the same unit or different units, and if the first generation unit and the second generation unit are different units, after the first generation unit completes creation of the architecture BOM based on the configuration information of the first part input by the user, the data of the architecture BOM may be transmitted to the second generation unit, and then the second generation unit creates the EBOM based on the configuration information of the second part input by the user and the data of the architecture BOM transmitted by the first generation unit. In the embodiment, the EBOM of the corresponding vehicle is generated based on the structure BOM and the configuration information of the second part of each vehicle, so that repeated input of the configuration information of the first type of part can be avoided, and the EBOM creation efficiency is improved.

Optionally, an account may be set for each vehicle for the user to input configuration information of parts of the corresponding vehicle, or an account may be set for the user to input configuration information of parts of all vehicles. An administrator account can be set for inputting the configuration information of the first part, and an account is set for each vehicle for a user to input the configuration information of the second part of the corresponding vehicle. The specific configuration mode may be set according to actual needs and is not further limited herein. Thus, configuration information for a first part may be entered by a user or users, and configuration information for a second part of a different vehicle may be entered by a user or by different users.

Optionally, when the configuration information of the second part of each vehicle is input, the validity of the configuration information of the second part may also be verified. For example, the generating, for each of the N vehicles, the EBOM for the vehicle according to the configuration information for the second part of the vehicle and the configuration information for the first part in the architectural BOM includes:

executing a target operation based on whether a second part of a target vehicle is present in the architectural BOM if a configuration information input for the second part is received;

generating an EBOM of the target vehicle according to the configuration information of the second parts of the target vehicle and the configuration information of the first parts in the architecture BOM under the condition that the input of the configuration information of all the second parts of the target vehicle is completed;

wherein the target operation comprises: when the second part does not exist in the architecture BOM, storing currently input configuration information of the second part of the target vehicle; and when the second part exists in the framework BOM, outputting prompt information, wherein the prompt information is used for prompting that the currently input configuration information of the second part of the target vehicle is the configuration information of the first type of part.

In this embodiment, the EBOM generation unit may determine validity of the configuration information of the currently input second part, determine whether the second part exists in the framework BOM, that is, obtain the configuration information of the second part currently input by the user, determine whether the framework BOM has configuration information that is the same as the configuration information of the second part, if the configuration information that is the same as the configuration information of the second part exists, determine that the second part exists in the framework BOM, output corresponding prompt information, and remind the user that the currently input second part is actually a first type part; and if the same configuration information does not exist, determining that the second part does not exist in the BOM, and storing the currently input configuration information of the second part of the target vehicle. The structural BOM has the configuration information which is the same as the currently input configuration information of the second part, and it can be understood that the configuration information of one part in the structural BOM is at least partially the same as the currently input configuration information of the second part. For example, if the part number and the part name of a certain part in the framework BOM are the same, the configuration information of the part in the framework BOM can be understood to be the same as the currently input configuration information of the second part, regardless of whether the remaining configuration information is the same. Since the validity of the inputted configuration information of the second part is judged, the accuracy of the input can be improved.

Further, in some embodiments, the target operation further comprises: determining a currently input second part of the target vehicle as a second type of part and deleting the currently input configuration information of the second part of the target vehicle from the architecture BOM in case of receiving a target input for the prompt message; wherein the target input is an input to adjust the currently input second part of the target vehicle to the second type of part.

In this embodiment, the prompt message may be displayed through a pop-up window, an operation control is provided on the pop-up window, the operation control includes a first sub-control for canceling input of configuration information of the second part at this time, and a second sub-control for adjusting a part type corresponding to the currently input configuration information of the second part, and a user may implement target input by selecting the second control. At this time, the configuration information of the currently input second part may be deleted from the framework BOM by the first updating unit corresponding to the framework BOM, and further, the first updating unit may trigger the corresponding second updating unit to adjust the configuration information of the second part in the created EBOM, for example, adjust information such as a part number and a part type.

Because the part types of the parts in the BOM can be updated when the EBOM is created, a user does not need to independently modify the configuration information of the parts in the BOM, so that the intelligent degree of part list management is improved, and the management efficiency is effectively improved.

Optionally, in some embodiments, before determining the part type of the target part in a case that the update operation for the target part is received, the method further includes:

acquiring EBOMs corresponding to the N vehicles;

generating the framework BOM according to the configuration information of the parts with the same target configuration information;

wherein the target configuration information is at least part of configuration information in the configuration information of the part.

In this embodiment, obtaining the EBOMs corresponding to the N vehicles may be understood as the initial EBOM that has been created, after the architecture BOM is generated, the EBOMs may not be adjusted, or partial adjustment may be performed on configuration information of the parts in the EBOMs, for example, information such as part numbers and part types may be adjusted, where the part numbers may be replaced by the system that automatically generates corresponding part numbers based on the parts of the first type and the parts of the second type, and the part types may determine that the part in the architecture BOM is of the first type, and determine that the part in the architecture BOM does not exist in the EBOMs and is of the second type. Because the BOM is established based on the existing EBOM, the unified update management of the existing EBOM can be realized, and the application range is improved.

Optionally, the target configuration information may be all configuration information of the part, or may be partial configuration information, for example, in some embodiments, the target configuration information may include a part number and a part name.

Further, in some embodiments, before generating the architecture BOM according to the configuration information of the parts with the same target configuration information, the method further includes:

updating the configuration information of the first object in a target EBOM when the first object meets a preset condition in the EBOMs corresponding to the N vehicles, so that the configuration information of the first object is the same in the EBOMs corresponding to the N vehicles;

the first object is any one part in the EBOM, and the preset condition includes: the preset configuration information of the first object is partially different in the EBOM corresponding to the N vehicles, and the preset configuration information is at least one configuration information in the target configuration information.

In this embodiment, the target configuration information may include information such as part number, part name, installation position, number, vehicle type series configuration, and purchase level. The preset configuration information may be one or more configuration information, for example, the preset configuration information may be information such as quantity, vehicle type series configuration, and purchasing level. Optionally, in some embodiments, when the target configuration information of a certain first object in the N EBOMs is the same except the preset configuration information, it may be understood or considered that the configuration information of the first object is the same in all the EBOMs, and different configuration information may be understood or considered as a user input error, and the reliability of the EBOMs may be ensured by changing the configuration information.

Optionally, in order to further ensure the correctness of the change, the user may further confirm, for example, the configuration information of the first object may be displayed through a real interface for the user to view, a corresponding operation control may be set on the display interface for the user to adjust the configuration information, and the configuration information in the EBOM is updated based on the adjusted configuration information, so that the configuration information of the first object is the same in the EBOMs corresponding to the N vehicles.

Further, when the configuration information of a certain first type of target part is updated, there may be a case where the part type is changed, and thus the architectures BOM and EBOM need to be further adjusted based on the part type change. For example, the first update request further carries an indication of adjusting a type of a part, and the updating, in a target object, the configuration information of the target part based on the first update request includes:

deleting the configuration information of the target part in the framework BOM based on the first updating request, and updating the first configuration information of the target part in the N EBOMs, wherein the first configuration information is determined based on part type change;

and adjusting the configuration information of the target part in the EBOM associated with the updating operation into the configuration information of the target part carried in the first updating request.

In this embodiment, the determining of the part type of the target part may be understood as determining the part type of the target part based on the framework BOM or EBOM, or determining the part type of the target part based on the part type selected by the user on the update interface, where the generated first update request further carries an indication to adjust the part type if the part type associated with the update interface is different from the determined part type. The specific information content of the updated first configuration information may be set according to actual needs, for example, in some embodiments, the first configuration information may include a part type, and further may include a part number.

Optionally, in some embodiments, the user updates the configuration information of the target part through a specific second update interface, when it is determined that the target part is the first type of part, a prompt message may be output to prompt the user that the target part is the first type of part, the update is required through the first update interface, when the user continues to select the update based on the prompt message, an indication for adjusting the type of the part is carried in the first update request, and the first update request is sent to the first update unit. At this time, after the first updating unit receives the first updating request, the configuration information of the target part in the framework BOM may be deleted, and corresponding updating information is sent to each second updating unit, so as to trigger the second updating units to update the first configuration information of the target part in each EBOM. Meanwhile, the configuration information of the target part in the EBOM associated with the updating operation is adjusted to the configuration information of the target part carried in the first updating request. It should be understood that, in the embodiment of the present disclosure, the EBOM associated with the update operation may be understood as at least one EBOM associated with the above specific second update interface, may also be at least one EBOM associated with a logged-in account, and may also be at least one EBOM that needs to be updated by the user setting. Assuming that each EBOM is associated with one second updating unit, the first updating unit may directly send the first updating request as the updating information to each second updating unit, or may send the first updating request as the updating information only to the second updating unit associated with the EBOM associated with the updating operation, and send the type change information of the target part to the second updating units associated with other EBOMs.

It should be understood that, in other embodiments, there may be one second update unit for updating all EBOMs, and the first update unit and the second update unit may also be the same update unit, which is not further limited herein.

According to the embodiment of the disclosure, the indication for adjusting the type of the part is carried in the first update request, so that the configuration information of the target part in the framework BOM and the EBOM can be directly updated, and meanwhile, the configuration information of the target part in the first update request is updated to the EBOM associated with the update operation, so that the framework BOM and the EBOM can be uniformly updated, repeated update operation of a plurality of EBOMs by a user is avoided, the management efficiency is improved, and the labor cost is reduced.

Optionally, in some embodiments, after determining the part type of the target part in a case that the update operation for the target part is received, the method further includes:

generating a second update request under the condition that the part type of the target part is the second type, wherein the second update request carries the configuration information of the target part;

and adjusting the configuration information of the target part in the EBOM associated with the updating operation into the configuration information of the target part carried in the second updating request.

In the embodiment of the present disclosure, a second updating unit may be provided for each EBOM, and each updating unit is associated with a second updating interface, so as to update the configuration information of the second part in the corresponding EBOM. For example, in a case where the system receives an update operation input by the user based on the second update interface, a second update request is generated and sent to the second update unit, and the second update unit updates the configuration information of the target part in the corresponding EBOM. It should be noted that the update to the target part may be addition, modification or deletion.

Further, in some embodiments, if an update to a target part is added or modified, a part type change may occur to the target part, so that it is necessary to further determine whether the part type change occurs, so as to improve the efficiency of subsequent management. For example, after the adjusting the configuration information of the target part in the EBOM associated with the update operation to the configuration information of the target part carried in the second update request, the method further includes:

determining whether the target configuration information of the target part in the N EBOMs is the same;

and under the condition that the target configuration information of the target part in the N EBOMs is the same, adjusting the part type of the target part to be a first type, and updating the target object.

It should be understood that the target configuration information may be set according to actual needs, and for example, in some embodiments, information such as part number, part name, installation location, number, vehicle type series configuration, and purchase level may be included.

Alternatively, the updating of the target object may be understood as adding configuration information of the target part in the BOM, and adjusting the configuration information of the target part in the EBOM based on the part type adjustment of the target part, for example, adjusting information such as the part type and the part number of the target part in the EBOM. In this embodiment, after the configuration information of the second part in the EBOMs is updated, the part type of the target part is adjusted from the second type to the first type under the condition that the target configuration information of the target part in the N EBOMs is the same, and the target object is updated based on the change of the type, so that the user can conveniently perform subsequent unified management on the target part, thereby improving the management efficiency and saving the management cost.

For a better understanding of the present disclosure, the following detailed description is given by way of specific examples.

Assuming an A architecture derived AA platform, an AB platform and an AC platform, the AA platform comprises three vehicle types of AA1, AA2 and AA3, the AB platform comprises three vehicle types of AB1, AB2 and AB3, and the AC platform comprises three vehicle types of AC1, AC2 and AC 3.

First, the BOM administrator may create an "architecture part functions and installation locations" database, associating frame members with "part functions and installation locations". The association relationship is different in different architectures, the part functions and the installation positions of the architecture A and the architecture B are different, and a user can select the part functions and the installation positions in the creation interfaces of BOMs in different architectures.

Then, the BOM administrator creates a framework BOM generation unit (i.e., a first generation unit) of the a framework, and the user can fill configuration information such as part number, part name, number, vehicle model series configuration, and purchase level of the framework BOM by checking the "part function and installation location" information in the "part function and installation location" database when creating the framework BOM. After all users are created, the BOM administrator freezes the framework BOM generation unit of the A framework.

Secondly, the BOM administrator releases the data of the architecture BOM generation unit of the a-architecture to the architecture BOM update unit (i.e., the first update unit), and the data of the architecture BOM generation unit of the a-architecture is invalid. All changes submit engineering change flow updates in the architecture BOM updating unit. And after the modified process passes the examination and approval, the modified data takes effect in the framework BOM updating unit of the A framework.

Next, after the AA, AB, and AC platforms each model starts development, the BOM administrator creates EBOM generation units (i.e., second generation units) of the AA1, AA2, AA3, AB1, AB2, AB3, AC1, AC2, and AC3 models, respectively. The EBOM generation units in the AA1, AA2, AA3, AB1, AB2, AB3, AC1, AC2, and AC3 models call the latest effective information in the architecture BOM update unit of the a architecture by the system, and the shelf member field is shown as Y in the EBOM generation units in the AA1, AA2, AA3, AB1, AB2, AB3, AC1, AC2, and AC3 models.

Next, the user creates information of the non-framework BOM, for example, configuration information such as part number, part function and mounting position, part name, number, vehicle type series configuration, and purchase level of filling out other non-framework BOMs, in the EBOM generation units of the AA1, AA2, AA3, AB1, AB2, AB3, AC1, AC2, and AC3 vehicle models. The data shelf component field created in the EBOM generation cell is shown as N.

Optionally, when the user fills in the non-framework part function and the installation position in the EBOM generation units of the AA1, AA2, AA3, AB1, AB2, AB3, AC1, AC2, and AC3 vehicle models, if the system identifies that the part function and the installation position exist in the framework BOM of the a framework, the user is reminded that the function and the installation position exist in the framework BOM, and if the function and the installation position do need to be added continuously, the function and the installation position need to be modified in the framework BOM update unit of the a framework in advance. If the part is determined to be a non-shelf member based on the "part function and mounting location", the user deletes the part in the A-shelf BOM update unit. If the part is determined to be a carrier member based on the "part function and mounting position", the user selects other part functions and mounting positions in the EBOM generation units of the AA1, AA2, AA3, AB1, AB2, AB3, AC1, AC2, and AC3 models.

Finally, after all user creations are completed, the BOM administrator freezes the EBOM generation units of AA1, AA2, AA3, AB1, AB2, AB3, AC1, AC2, and AC3 models. Then the BOM administrator releases the EBOM generation unit data of the AA1, AA2, AA3, AB1, AB2, AB3, AC1, AC2, and AC3 models to the EBOM update unit (i.e., the second update unit), and the EBOM generation unit data of the AA1, AA2, AA3, AB1, AB2, AB3, AC1, AC2, and AC3 models fails. All changes submit engineering change flow updates in the EBOM update units of AA1, AA2, AA3, AB1, AB2, AB3, AC1, AC2, and AC3 models. After the approval of the modification process, the modified data are validated in the EBOM update units of the AA1, AA2, AA3, AB1, AB2, AB3, AC1, AC2, and AC3 models.

Optionally, the user submits engineering changes in the EBOM update units of AA1, AA2, AA3, AB1, AB2, AB3, AC1, AC2, and AC3 models, and when the system determines that the modified cradle component field is Y, the system alerts the user that the change can only be changed in the architecture BOM update unit. The system does not allow the configuration information in the BOM to be changed in the EBOM updating unit of the whole vehicle. And if the user judges that the architecture BOM needs to be updated, submitting 1 part of engineering change flow update in the architecture BOM updating unit. And after the modified process passes the examination and approval, the modified data takes effect in the framework BOM updating unit. The system sends the change amount of the framework component to the EBOM update units of AA1, AA2, AA3, AB1, AB2, AB3, AC1, AC2 and AC3 models and takes effect.

When the system determines that the changed frame member field is Y, the system reminds the user that the change can only be changed in the structure BOM updating unit. And if the user judges that the part is a non-frame member, the user deletes the part in the BOM updating unit of the A framework, and adds parts required by different platforms and different vehicle types in the EBOM updating units of the AA1, AA2, AA3, AB1, AB2, AB3, AC1, AC2 and AC3 vehicle types respectively.

As shown in fig. 2, the present disclosure provides a vehicle parts list management apparatus 200 including:

the receiving module 201 is configured to determine a part type of a target part in a case of receiving an update operation for the target part;

a first generating module 202, configured to generate a first update request when the part type of the target part is a first type, where the first update request carries configuration information of the target part;

an update module 203 for updating the configuration information of the target part in the target object based on the first update request;

Optionally, the vehicle parts list management apparatus 200 further includes:

the acquisition module is used for acquiring configuration information of at least one first part input by a user, wherein the first part is the first type of part;

a second generation module for generating the architecture BOM based on the configuration information of the first part;

a third generation module that generates, for each of the N vehicles, an EBOM for the vehicle according to configuration information of a second part of the vehicle and configuration information of the first part in the architecture BOM, the second part being a second type of part.

Optionally, the third generating module is specifically configured to:

Optionally, the target operation further comprises: determining a currently input second part of the target vehicle as a second type of part and deleting the currently input configuration information of the second part of the target vehicle from the architecture BOM in case of receiving a target input for the prompt message; wherein the target input is an input to adjust the currently input second part of the target vehicle to the second type of part.

Optionally, the vehicle parts list management apparatus 200 further includes:

the acquisition module is used for acquiring the EBOMs corresponding to the N vehicles;

the second generation module is used for generating the framework BOM according to the configuration information of the parts with the same target configuration information;

Optionally, the updating module 203 is further configured to:

Optionally, the first update request further carries an indication of adjusting a type of the part, and the update module is specifically configured to:

Optionally, the first generating module 202 is further configured to generate a second update request when the part type of the target part is the second type, where the second update request carries configuration information of the target part;

the updating module 203 is further configured to adjust the configuration information of the target part in the EBOM associated with the updating operation to the configuration information of the target part carried in the second updating request.

Optionally, the vehicle parts list management apparatus 200 further includes:

the determining module is used for determining whether the target configuration information of the target part in the N EBOMs is the same;

the updating module 203 is further configured to, when the target configuration information of the target part in the N EBOMs is the same, adjust the part type of the target part to be the first type, and update the target object.

The vehicle part list management device provided by the disclosure can realize each process realized by the vehicle part list management method embodiment, and can achieve the same beneficial effects, and is not repeated here for avoiding repetition.

In the technical scheme of the disclosure, the collection, storage, use, processing, transmission, provision, disclosure and other processing of the personal information of the related user are all in accordance with the regulations of related laws and regulations and do not violate the good customs of the public order.

The present disclosure also provides an electronic device, a readable storage medium, and a computer program product according to embodiments of the present disclosure.

FIG. 3 illustrates a schematic block diagram of an example electronic device that can be used to implement embodiments of the present disclosure. Electronic devices are intended to represent various forms of digital computers, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other appropriate computers. The electronic device may also represent various forms of mobile devices, such as personal digital processing, cellular phones, smart phones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions, are meant to be examples only, and are not meant to limit implementations of the disclosure described and/or claimed herein.

As shown in fig. 3, the apparatus 300 includes a computing unit 301 that can perform various appropriate actions and processes according to a computer program stored in a Read Only Memory (ROM)302 or a computer program loaded from a storage unit 308 into a Random Access Memory (RAM) 303. In the RAM 303, various programs and data required for the operation of the device 300 can also be stored. The calculation unit 301, the ROM 302, and the RAM 303 are connected to each other via a bus 304. An input/output (I/O) interface 305 is also connected to bus 304.

Various components in device 300 are connected to I/O interface 305, including: an input unit 306 such as a keyboard, a mouse, or the like; an output unit 307 such as various types of displays, speakers, and the like; a storage unit 308 such as a magnetic disk, optical disk, or the like; and a communication unit 309 such as a network card, modem, wireless communication transceiver, etc. The communication unit 309 allows the device 300 to exchange information/data with other devices via a computer network such as the internet and/or various telecommunication networks.

The computing unit 301 may be a variety of general and/or special purpose processing components having processing and computing capabilities. Some examples of the computing unit 301 include, but are not limited to, a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), various dedicated Artificial Intelligence (AI) computing chips, various computing units running machine learning model algorithms, a Digital Signal Processor (DSP), and any suitable processor, controller, microcontroller, and so forth. The computing unit 301 performs the various methods and processes described above, such as the vehicle parts list management method. For example, in some embodiments, the vehicle parts inventory management method may be implemented as a computer software program tangibly embodied in a machine-readable medium, such as storage unit 308. In some embodiments, part or all of the computer program may be loaded and/or installed onto device 300 via ROM 302 and/or communication unit 309. When the computer program is loaded into RAM 303 and executed by computing unit 301, one or more steps of the vehicle parts inventory management method described above may be performed. Alternatively, in other embodiments, the computing unit 301 may be configured to perform the vehicle parts list management method in any other suitable manner (e.g., by way of firmware).

Various implementations of the systems and techniques described here above may be implemented in digital electronic circuitry, integrated circuitry, Field Programmable Gate Arrays (FPGAs), Application Specific Integrated Circuits (ASICs), Application Specific Standard Products (ASSPs), system on a chip (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and/or combinations thereof. These various embodiments may include: implemented in one or more computer programs that are executable and/or interpretable on a programmable system including at least one programmable processor, which may be special or general purpose, receiving data and instructions from, and transmitting data and instructions to, a storage system, at least one input device, and at least one output device.

Program code for implementing the methods of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the program codes, when executed by the processor or controller, cause the functions/operations specified in the flowchart and/or block diagram to be performed. The program code may execute entirely on the machine, partly on the machine, as a stand-alone software package partly on the machine and partly on a remote machine or entirely on the remote machine or server.

In the context of this disclosure, a machine-readable medium may be a tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

To provide for interaction with a user, the systems and techniques described here can be implemented on a computer having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to a user; and a keyboard and a pointing device (e.g., a mouse or a trackball) by which a user can provide input to the computer. Other kinds of devices may also be used to provide for interaction with a user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form, including acoustic, speech, or tactile input.

The systems and techniques described here can be implemented in a computing system that includes a back-end component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front-end component (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such back-end, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: local Area Networks (LANs), Wide Area Networks (WANs), and the Internet.

The computer system may include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. The server may be a cloud server, a server of a distributed system, or a server with a combined blockchain.

It should be understood that various forms of the flows shown above may be used, with steps reordered, added, or deleted. For example, the steps described in the present disclosure may be executed in parallel or sequentially or in different orders, and are not limited herein as long as the desired results of the technical solutions disclosed in the present disclosure can be achieved.

The above detailed description should not be construed as limiting the scope of the disclosure. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions may be made in accordance with design requirements and other factors. Any modification, equivalent replacement, and improvement made within the spirit and principle of the present disclosure should be included in the scope of protection of the present disclosure.

Claims

1. A vehicle parts list management method, the method comprising:

2. The method of claim 1, wherein prior to determining the part type of the target part if an update operation is received for the target part, the method further comprises:

3. The method of claim 2, wherein the generating, for each of the N vehicles, an EBOM for the vehicle from configuration information for a second part of the vehicle and configuration information for the first part in the architectural BOM comprises:

4. The method of claim 3, wherein the target operation further comprises: determining a currently input second part of the target vehicle as a second type of part and deleting the currently input configuration information of the second part of the target vehicle from the architecture BOM in case of receiving a target input for the prompt message; wherein the target input is an input to adjust the currently input second part of the target vehicle to the second type of part.

5. The method of claim 1, wherein prior to determining the part type of the target part if an update operation is received for the target part, the method further comprises:

acquiring EBOMs corresponding to the N vehicles;

6. The method of claim 5, wherein before generating the architectural BOM according to the configuration information of the parts with the same target configuration information, the method further comprises:

7. The method of claim 1, wherein the first update request further carries an indication of an adjusted part type, and wherein updating the configuration information of the target part in the target object based on the first update request comprises:

8. The method of any one of claims 1 to 7, wherein upon determining a part type of a target part upon receiving an update operation for the target part, the method further comprises:

9. The method of claim 8, wherein after adjusting the configuration information of the target part in the EBOM associated with the update operation to the configuration information of the target part carried in the second update request, the method further comprises:

10. A vehicle parts list management apparatus, comprising:

11. An electronic device, comprising:

at least one processor; and

the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the method of any one of claims 1-9.

12. A non-transitory computer readable storage medium having stored thereon computer instructions for causing the computer to perform the method of any one of claims 1-9.

13. A computer program product comprising a computer program which, when executed by a processor, implements the method according to any one of claims 1-9.