BOM data management method, program product and storage medium

Abstract

The invention discloses a BOM data management method, a program product and a storage medium, and belongs to the technical field of BOM data. The BOM data comprises vehicle type BOM data and platform BOM data, and the platform BOM data comprises a plurality of different vehicle type BOM data. According to the method, vehicle type BOM data and platform BOM data are stored in the form of a structure tree, and the vehicle type BOM data and the platform BOM data are associated through a system plug-in, so that corresponding parts in the platform BOM data can be synchronously changed when the vehicle type BOM data are changed. Therefore, linkage between the vehicle type BOM data and the platform BOM data can be realized, and the consistency of the platform BOM data and the vehicle type BOM data can be ensured.

Description

Technical Field

[0001] The present application belongs to the technical field of BOM data, and in particular, relates to a BOM data management method, program product and storage medium. Background Art

[0002] At present, the platform BOM (Bill of Materials) and model BOM of automobiles are in separate BOM rooms. The data between different BOM rooms are independent of each other, and BOM changes cannot be linked. However, in the actual production process, the platform BOM and model BOM must be consistent, otherwise there will be data differences, affecting work.

[0003] However, many engineers often forget to make synchronous changes to the platform BOM data when making changes to the vehicle model BOM data, resulting in differences between the platform BOM data and the vehicle model BOM data. Summary of the invention

[0004] The embodiments of the present application provide a BOM data management method, program product and storage medium, which aim to associate vehicle model BOM data with platform BOM data through a system plug-in so that when the vehicle model BOM data is changed, the corresponding part in the platform BOM data can be changed synchronously, thereby ensuring the consistency of the platform BOM data with the vehicle model BOM data.

[0005] Other features and advantages of the present application will become apparent from the following detailed description, or may be learned in part by the practice of the present application.

[0006] According to a first aspect of an embodiment of the present application, a method for managing BOM data is provided, wherein the BOM data includes vehicle type BOM data and platform BOM data, and the platform BOM data includes a plurality of different vehicle type BOM data, and the method includes:

[0007] The vehicle model BOM data and the platform BOM data are stored in the form of a structure tree;

[0008] The vehicle type BOM data is associated with the platform BOM data through a system plug-in, so that when the vehicle type BOM data is changed, the corresponding part in the platform BOM data can be changed synchronously.

[0009] In some embodiments of the present application, based on the aforementioned scheme, the structure tree of the platform BOM data and the structure tree of the vehicle model BOM data both contain a physical installation assembly level and a component level with the same naming format, wherein the physical installation assembly level is the parent of the component level.

[0010] In some embodiments of the present application, based on the aforementioned scheme, the naming format of the physical installation assembly level corresponding to the structure tree of the vehicle model BOM data is the vehicle model project code plus multi-digit characters, and the naming format of the physical installation assembly level corresponding to the structure tree of the platform BOM data is the platform project code plus multi-digit characters, wherein, if the multi-digit characters are the same, the physical installation assembly level in the structure tree of the vehicle model BOM data is the same as the physical installation assembly level in the structure tree of the platform BOM data, the component levels under the same physical installation assembly level are the same, and the codes corresponding to the same components are the same.

[0011] In some embodiments of the present application, based on the above solution, when the vehicle model BOM data is changed, the corresponding part of the platform BOM data can be changed synchronously, including:

[0012] When a replacement operation is performed on a component at a target entity installation assembly level in the structure tree of the vehicle model BOM data, the system plug-in is used to detect whether a component having the same code as the replaced component is included at a physical installation assembly level that is the same as the target physical installation assembly level in the structure tree of the platform BOM data;

[0013] If the physical installation assembly level that is the same as the target physical installation assembly level in the structure tree of the platform BOM data does not contain a component with the same code as the replaced component, then replace the component under the target physical installation assembly level in the structure tree of the vehicle model BOM data;

[0014] If a component having the same code as the replaced component is included under the entity installation assembly level that is the same as the target entity installation assembly level in the structure tree of the platform BOM data, the release status of the entity installation assembly level that is the same as the target entity installation assembly level in the structure tree of the platform BOM data is detected by the system plug-in;

[0015] When the publishing status is a frozen status, changing the publishing status to an active status through the system plug-in;

[0016] When the release status is active, the system plug-in automatically replaces the components with the same code as the replaced components in the structure tree of the platform BOM data.

[0017] In some embodiments of the present application, based on the above solution, when the vehicle model BOM data is changed, the corresponding part of the platform BOM data can be changed synchronously, including:

[0018] When a component under a target entity installation assembly level in the structure tree of the vehicle model BOM data is deleted, the system plug-in is used to detect whether a component with the same code as the deleted component is included in the entity installation assembly level that is the same as the target entity installation assembly level in the structure tree of the platform BOM data;

[0019] If the entity installation assembly level that is the same as the target entity installation assembly level in the structure tree of the platform BOM data does not contain a component with the same code as the deleted component, then the component under the target entity installation assembly level in the structure tree of the vehicle model BOM data is deleted;

[0020] If a component having the same code as the deleted component is included under the entity installation assembly level that is the same as the target entity installation assembly level in the structure tree of the platform BOM data, the publishing status of the entity installation assembly level that is the same as the target entity installation assembly level in the structure tree of the platform BOM data is detected by the system plug-in;

[0021] When the publishing status is a frozen status, changing the publishing status to an active status through the system plug-in;

[0022] When the publishing status is active, the system plug-in automatically and synchronously deletes the components with the same code as the deleted components in the structure tree of the platform BOM data.

[0023] In some embodiments of the present application, based on the above solution, when the vehicle model BOM data is changed, the corresponding part of the platform BOM data can be changed synchronously, including:

[0024] When adding a new component to the target entity installation assembly level in the structure tree of the vehicle model BOM data, determining whether the newly added component is a platform component;

[0025] If the newly added component is not a platform component, then the component is added under the target entity installation assembly level in the structure tree of the vehicle model BOM data;

[0026] If the newly added component is a platform component, the system plug-in automatically and synchronously adds the component at the same entity installation assembly level as the target entity installation assembly level in the structure tree of the platform BOM data.

[0027] In some embodiments of the present application, based on the above solution, the method further includes:

[0028] When the name of the physical installation assembly level in the structure tree of the vehicle model BOM data is changed, the name of the physical installation assembly level that is the same as the changed physical installation assembly level in the structure tree of the platform BOM data is synchronously changed by the system plug-in;

[0029] and / or,

[0030] When the code of the component under the physical installation assembly level in the structure tree of the vehicle model BOM data is changed, the code of the component identical to the changed component in the structure tree of the platform BOM data is synchronously changed through the system plug-in.

[0031] In some embodiments of the present application, based on the above solution, the method further includes:

[0032] When deleting a component in the structure tree of the platform BOM data, the system plug-in detects whether the component to be deleted belongs to the data in the selected project;

[0033] In the case that the component to be deleted belongs to the data in the selected project, it is allowed to delete the component in the structure tree of the platform BOM data, and the component is automatically and synchronously deleted in the structure tree of the vehicle model BOM data through the system plug-in.

[0034] According to a second aspect of an embodiment of the present application, a computer program product is provided, which includes computer instructions stored in a computer-readable storage medium and suitable for being read and executed by a processor, so that a computer device having the processor executes the method described in any embodiment of the first aspect above.

[0035] According to a third aspect of an embodiment of the present application, a computer-readable storage medium is provided, in which computer program instructions are stored. The computer program instructions are loaded and executed by a processor to implement the operations performed by the method described in any embodiment of the first aspect above.

[0036] Based on the technical solution proposed in this application, BOM data includes vehicle model BOM data and platform BOM data. The platform BOM data contains multiple different vehicle model BOM data. The vehicle model BOM data and platform BOM data are stored in the form of a structure tree, and the vehicle model BOM data and platform BOM data are associated through a system plug-in, so that when the vehicle model BOM data is changed, the corresponding part of the platform BOM data can be changed synchronously. In this way, the linkage between the vehicle model BOM data and the platform BOM data can be achieved, thereby ensuring the consistency of the platform BOM data and the vehicle model BOM data.

[0037] It should be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0038] The drawings herein are incorporated into the specification and constitute a part of the specification, showing embodiments consistent with the present application, and together with the specification, are used to explain the principles of the present application. Obviously, the drawings described below are only some embodiments of the present application, and for ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work. In the drawings:

[0039] Figure 1 This is a flowchart of the first step of a BOM data management method provided by an embodiment of the present application;

[0040] Figure 2 is a schematic diagram of a structure tree provided by an embodiment of the present application;

[0041] Figure 3 It is a flowchart of the second step of the BOM data management method provided in an embodiment of the present application;

[0042] Figure 4 is a flowchart of the third step of the BOM data management method provided in an embodiment of the present application;

[0043] Figure 5 is a flowchart of the fourth step of the BOM data management method provided in an embodiment of the present application;

[0044] Figure 6 is a flowchart of the fifth step of the BOM data management method provided in an embodiment of the present application;

[0045] Figure 7 A schematic diagram of the structure of a computer program product in an embodiment of the present application is shown. DETAILED DESCRIPTION

[0046] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0047] In addition, described feature, structure or characteristic can be combined in one or more embodiments in any suitable manner. In the following description, many specific details are provided to provide a full understanding of the embodiments of the present application. However, those skilled in the art will appreciate that the technical scheme of the present application can be put into practice without one or more of the specific details, or other methods, components, devices, steps, etc. can be adopted. In other cases, known methods, devices, realizations or operations are not shown or described in detail to avoid blurring the various aspects of the application.

[0048] The block diagrams shown in the accompanying drawings are merely functional entities and do not necessarily correspond to physically independent entities. That is, these functional entities may be implemented in software form, or in one or more hardware modules or integrated circuits, or in different networks and / or processor devices and / or microcontroller devices.

[0049] The flowcharts shown in the accompanying drawings are only exemplary and do not necessarily include all the contents and operations / steps, nor must they be executed in the order described. For example, some operations / steps can be decomposed, and some operations / steps can be combined or partially combined, so the actual execution order may change according to actual conditions.

[0050] In the description of this application, it should be understood that the terms "first" and "second" are used for descriptive purposes only and should not be understood as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of the feature. In the description of this application, unless otherwise specified, "plurality" means two or more.

[0051] In order to enable those skilled in the art to better understand the present application, the application scenarios involved in the present application are first briefly described.

[0052] In the manufacturing industry, especially in the vehicle manufacturing industry, BOM is an important output in the product development process. Usually, product development will form DBOM and EBOM, which will be continuously iterated and updated during the development process. BOM data is referenced by many departments and systems. Therefore, the accuracy of the BOM data itself and the consistency between the platform BOM and the vehicle model BOM are very important.

[0053] However, many engineers often forget to make synchronous changes to the platform BOM data when making changes to the vehicle model BOM data, resulting in differences between the platform BOM data and the vehicle model BOM data.

[0054] Based on this, an embodiment of the present application provides a BOM data management method, which associates vehicle model BOM data with platform BOM data through a system plug-in, so that when the vehicle model BOM data is changed, the corresponding part in the platform BOM data can be changed synchronously, thereby ensuring the consistency of the platform BOM data with the vehicle model BOM data.

[0055] Reference Figure 1 , Figure 1 This is a flowchart of the first step of a BOM data management method provided in an embodiment of the present application, including but not limited to steps S110 to S120.

[0056] Step S110, storing both the vehicle model BOM data and the platform BOM data in the form of a structure tree;

[0057] Step S120, associating the vehicle model BOM data with the platform BOM data through the system plug-in, so that when the vehicle model BOM data is changed, the corresponding part in the platform BOM data can be changed synchronously.

[0058] In the embodiment of the present application, BOM data includes vehicle model BOM data and platform BOM data, and the platform BOM data contains multiple different vehicle model BOM data. By storing both the vehicle model BOM data and the platform BOM data in the form of a structure tree, and associating the vehicle model BOM data with the platform BOM data through a system plug-in, when the vehicle model BOM data is changed, the corresponding part of the platform BOM data can be changed synchronously, thereby ensuring the consistency of the platform BOM data and the vehicle model BOM data.

[0059] Reference Figure 2 , Figure 2 This is a schematic diagram of a structure tree provided in an embodiment of the present application. In the embodiment of the present application, the structure tree may include five layers, among which the topmost layer (zero layer) is the vehicle structure (vehicle platform, which can be divided into products based on appearance and vehicle length). The first layer is the main system, which can be divided into three main systems: body, chassis, and electrical. The second layer is the main subsystem categories, such as the engine system, clutch system, chassis electrical system, battery compartment electrical system, etc. The third layer is the physical installation assembly, such as the battery bracket assembly, battery installation assembly, battery compartment cable assembly, etc. The fourth layer is the parts, which may include various parts, such as Part 1, Part 2, and Part 3. Among them, each layer can be associated with relevant technical documents (such as drawings, technical agreements, etc.). The third layer (i.e., the physical installation assembly) is to centralize the management of many modules with similar functions, and use the functions such as component parameters and constraints provided by the system to achieve optional matching. This helps to decompose the vehicle structure into multiple standard modules, which is conducive to parallel design. Figure 2The first and second layers in the product design are used as templates. The standardized product structure makes data query convenient and fast.

[0060] In some embodiments, the structure tree of the platform BOM data and the structure tree of the vehicle type BOM data both contain a physical installation assembly level and a component level in the same naming format, wherein the physical installation assembly level is the parent of the component level. Specifically, the naming format of the physical installation assembly level corresponding to the structure tree of the vehicle type BOM data is the vehicle type project code plus multi-digit characters, and the naming format of the physical installation assembly level corresponding to the structure tree of the platform BOM data is the platform project code plus multi-digit characters. Wherein, if the multi-digit characters are the same, the physical installation assembly level in the structure tree of the vehicle type BOM data is the same as the physical installation assembly level in the structure tree of the platform BOM data. For example, the naming format of the physical installation assembly level corresponding to the structure tree of the vehicle type BOM data is the vehicle type project code plus 9-digit characters, and the naming format of the physical installation assembly level corresponding to the structure tree of the platform BOM data is the platform project code plus 9-digit characters. As long as these 9-digit characters are the same, the physical installation assemblies corresponding to the structure tree of the vehicle type BOM data and the structure tree of the platform BOM data are the same. The component levels under the same physical installation assembly level are the same, and the codes corresponding to the same components are the same.

[0061] Reference Figure 3 , Figure 3 This is a flowchart of the second step of the BOM data management method provided in an embodiment of the present application, including but not limited to steps S310 to S350.

[0062] Step S310, when a replacement operation is performed on a component under a target entity installation assembly level in the structure tree of the vehicle model BOM data, the system plug-in is used to detect whether a component with the same code as the replaced component is contained in a physical installation assembly level that is the same as the target physical installation assembly level in the structure tree of the platform BOM data;

[0063] Step S320, if the physical installation assembly level that is the same as the target physical installation assembly level in the structure tree of the platform BOM data does not contain a component with the same code as the replaced component, then replace the component under the target physical installation assembly level in the structure tree of the vehicle model BOM data;

[0064] Step S330, if the entity installation assembly level that is the same as the target entity installation assembly level in the structure tree of the platform BOM data contains a component with the same code as the replaced component, then the release status of the entity installation assembly level that is the same as the target entity installation assembly level in the structure tree of the platform BOM data is detected by the system plug-in;

[0065] Step S340, when the publishing status is frozen, the publishing status is changed to active status through the system plug-in;

[0066] Step S350, when the publishing status is active, the system plug-in automatically replaces the components with the same code as the replaced components in the structure tree of the platform BOM data.

[0067] In an embodiment of the present application, when an engineer performs a replacement operation on a component under a target entity installation assembly level in a structure tree of the vehicle model BOM data in a vehicle model room, the system plug-in first detects whether a component with the same code as the replaced component is contained in the structure tree of the platform BOM data at the entity installation assembly level that is the same as the target entity installation assembly level. If the component does not exist, only the component under the target entity installation assembly level in the structure tree of the vehicle model BOM data is replaced. If the component is found to exist, the release status of the entity installation assembly level that is the same as the target entity installation assembly level in the structure tree of the platform BOM data is detected through the system plug-in. If the release status is active, the component with the same code as the replaced component in the structure tree of the platform BOM data is automatically replaced synchronously through the system plug-in. If the release status is frozen, the entity installation assembly level that is the same as the target entity installation assembly level in the structure tree of the platform BOM data is upgraded first, and the release status of the entity installation assembly level that is the same as the target entity installation assembly level in the structure tree of the platform BOM data is changed to active status, and then the parts with the same code as the replaced parts in the structure tree of the platform BOM data are automatically replaced synchronously through the system plug-in.

[0068] In an embodiment of the present application, when a component in the structure tree of the vehicle model BOM data is replaced, the system plug-in can automatically and synchronously replace the component with the same code as the replaced component in the structure tree of the platform BOM data, thereby ensuring the consistency of the platform BOM data and the vehicle model BOM data.

[0069] Reference Figure 4 , Figure 4 This is a flowchart of the third step of the BOM data management method provided in an embodiment of the present application, including but not limited to steps S410 to S450.

[0070] Step S410, when a component under a target entity installation assembly level in the structure tree of the vehicle model BOM data is deleted, the system plug-in is used to detect whether a component with the same code as the deleted component is included in the structure tree of the platform BOM data at the entity installation assembly level that is the same as the target entity installation assembly level;

[0071] Step S420, if the entity installation assembly level that is the same as the target entity installation assembly level in the structure tree of the platform BOM data does not contain a component with the same code as the deleted component, then delete the component under the target entity installation assembly level in the structure tree of the vehicle model BOM data;

[0072] Step S430, if the entity installation assembly level that is the same as the target entity installation assembly level in the structure tree of the platform BOM data contains a component with the same code as the deleted component, then the publishing status of the entity installation assembly level that is the same as the target entity installation assembly level in the structure tree of the platform BOM data is detected by the system plug-in;

[0073] Step S440, when the publishing status is frozen, the publishing status is changed to active status through the system plug-in;

[0074] Step S450, when the publishing status is active, the system plug-in automatically deletes the components with the same code as the deleted components in the structure tree of the platform BOM data.

[0075] In an embodiment of the present application, when an engineer deletes a component under a target entity installation assembly level in a structure tree of the vehicle model BOM data in a vehicle model room, the system plug-in first detects whether a component with the same code as the deleted component is contained in the structure tree of the platform BOM data at the entity installation assembly level that is the same as the target entity installation assembly level. If the component does not exist, only the component under the target entity installation assembly level in the structure tree of the vehicle model BOM data is deleted. If the component is found to exist, the system plug-in is used to detect the publishing status of the entity installation assembly level that is the same as the target entity installation assembly level in the structure tree of the platform BOM data. If the publishing status is active, the system plug-in is used to automatically and synchronously delete the component with the same code as the deleted component in the structure tree of the platform BOM data. If the release status is frozen, the entity installation assembly level that is the same as the target entity installation assembly level in the structure tree of the platform BOM data is upgraded first, and the release status of the entity installation assembly level that is the same as the target entity installation assembly level in the structure tree of the platform BOM data is changed to active status, and then the components with the same code as the deleted components in the structure tree of the platform BOM data are automatically deleted synchronously through the system plug-in.

[0076] In an embodiment of the present application, when a component in the structure tree of the vehicle model BOM data is deleted, the system plug-in can automatically and synchronously delete the components with the same code as the deleted component in the structure tree of the platform BOM data, thereby ensuring the consistency of the platform BOM data and the vehicle model BOM data.

[0077] Reference Figure 5 , Figure 5 This is a flowchart of the fourth step of the BOM data management method provided in an embodiment of the present application, including but not limited to steps S510 to S530.

[0078] Step S510, when adding a new component to the target entity installation assembly level in the structure tree of the vehicle model BOM data, determining whether the newly added component is a platform component;

[0079] Step S520, if the newly added component is not a platform component, then the component is added under the target entity installation assembly level in the structure tree of the vehicle model BOM data;

[0080] Step S530, if the newly added component is a platform component, the system plug-in automatically and synchronously adds the corresponding component at the entity installation assembly level that is the same as the target entity installation assembly level in the structure tree of the platform BOM data.

[0081] In the embodiment of the present application, when an engineer adds a new component to the target entity installation assembly level in the structure tree of the vehicle model BOM data in the vehicle model room, a judgment box will pop up for the newly added component to determine whether the newly added component is a platform component. If the engineer confirms that it is not a platform component, the component is only added to the target entity installation assembly level in the structure tree of the vehicle model BOM data. If the engineer confirms that it is a platform component, the system plug-in will be used to synchronously add a corresponding component to the entity installation assembly level that is the same as the target entity installation assembly level in the structure tree of the platform BOM data.

[0082] In an embodiment of the present application, when new parts are added under the target entity installation assembly level in the structure tree of the vehicle model BOM data, the system plug-in can automatically and synchronously add new parts under the entity installation assembly level that is the same as the target entity installation assembly level in the structure tree of the platform BOM data, thereby ensuring the consistency of the platform BOM data and the vehicle model BOM data.

[0083] In some embodiments, when the name of the physical installation assembly level in the structure tree of the vehicle model BOM data is changed, the name of the physical installation assembly level that is the same as the changed physical installation assembly level in the structure tree of the platform BOM data is changed synchronously through the system plug-in. And / or, when the code of the parts under the physical installation assembly level in the structure tree of the vehicle model BOM data is changed, the code of the parts that are the same as the changed parts in the structure tree of the platform BOM data is changed synchronously through the system plug-in. This is conducive to the synchronous change of parts between the subsequent vehicle model BOM data and the platform BOM data.

[0084] In some embodiments, reference Figure 6 , Figure 6 This is the fifth step flow chart of the BOM data management method provided in the embodiment of the present application, including but not limited to steps S610 to S620.

[0085] Step S610, when deleting the parts in the structure tree of the platform BOM data, the system plug-in is used to detect whether the parts to be deleted belong to the data in the selected project;

[0086] Step S620, when the parts to be deleted belong to the data in the selected project, it is allowed to delete the parts in the structure tree of the platform BOM data, and the parts are automatically deleted synchronously in the structure tree of the vehicle model BOM data through the system plug-in.

[0087] In an embodiment of the present application, when an engineer deletes a component in the structure tree of the platform BOM data in the platform room, the system plug-in will detect whether the component to be deleted belongs to the data in the selected project; only when the component to be deleted belongs to the data in the selected project, the component is allowed to be deleted in the structure tree of the platform BOM data, and at the same time, the component is automatically and synchronously deleted in the structure tree of the vehicle model BOM data through the system plug-in. Specifically, when an engineer deletes a component in the structure tree of the platform BOM data in the platform room, the system plug-in will ask the engineer to select a project first when opening the structure tree of the platform BOM data, and then allow the engineer to operate on the platform BOM data. If the system plug-in detects that the component to be deleted by the engineer does not belong to the data of the selected project, a pop-up box will be displayed to remind the engineer whether to confirm the deletion. If the engineer confirms to delete, the engineer needs to reselect the project corresponding to the component to be deleted before deleting the component.

[0088] In an embodiment of the present application, when deleting components in the structure tree of the platform BOM data in the platform room, deletion of components in the structure tree of the platform BOM data is allowed only if the components to be deleted belong to the data of the selected project. This can avoid the situation where engineers accidentally delete components in the BOM data that other engineers are responsible for when making changes to the platform BOM data.

[0089] Based on the same inventive concept, an embodiment of the present application also provides a computer program product, which includes computer instructions, which are stored in a computer-readable storage medium and are suitable for being read and executed by a processor, so that a computer device with the processor executes a method provided in any of the above embodiments.

[0090] See also Figure 7 , Figure 7 The hardware structure of the computer program product of the embodiment of the present application is illustrated, and the computer program product includes:

[0091] The processor 701 may be implemented by a general-purpose CPU (Central Processing Unit), a microprocessor, an application-specific integrated circuit (Application Specific Integrated Circuit, ASIC), or one or more integrated circuits, and is used to execute relevant programs to implement the technical solutions provided in the embodiments of the present application;

[0092] The memory 702 can be implemented in the form of a read-only memory (ROM), a static storage device, a dynamic storage device, or a random access memory (RAM). The memory 702 can store an operating system and other applications. When the technical solution provided in the embodiments of this specification is implemented by software or firmware, the relevant program code is stored in the memory 702, and the processor 701 calls and executes the automatic charging method for a filling station executed by the control device in the embodiment of the present application, or executes the automatic charging method for a filling station executed by the cloud server in the embodiment of the present application;

[0093] Input / output interface 703, used to implement information input and output;

[0094] Communication interface 704, used to realize communication interaction between the device and other devices, which can be realized by wired mode (such as USB, network cable, etc.) or wireless mode (such as mobile network, WIFI, Bluetooth, etc.);

[0095] A bus 705 that transmits information between the various components of the device (e.g., the processor 701, the memory 702, the input / output interface 703, and the communication interface 704);

[0096] The processor 701 , the memory 702 , the input / output interface 703 and the communication interface 704 are connected to each other in communication within the device via a bus 705 .

[0097] Based on the same inventive concept, an embodiment of the present application provides a computer-readable storage medium, in which at least one computer program instruction is stored, and the at least one computer program instruction is loaded and executed by a processor to implement the operations performed by the method provided in any of the above embodiments.

[0098] The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored as one or more instructions or codes on a computer-readable medium or transmitted via a computer-readable medium. Other examples and implementations are within the scope and spirit of the present application and the appended claims. For example, due to the nature of software, the functions described above may be implemented using software executed by a processor, hardware, firmware, hard wiring, or a combination of any of these. In addition, each functional unit may be integrated into a processing unit, each unit may exist physically separately, or two or more units may be integrated into one unit.

[0099] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. Among them, the device embodiments described above are only schematic. For example, the division of the units can be a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of units or modules, which can be electrical or other forms.

[0100] The units described as separate components may or may not be physically separated, and the components of the control device may or may not be physical units, that is, they may be located in one place or distributed in multiple units. Some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.

[0101] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application can be essentially or partly or all or partly embodied in the form of a software product that contributes to the prior art. The computer software product is stored in a storage medium, including several instructions for a computer device (which can be a personal computer, a server or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), mobile hard disk, disk or optical disk, etc., which can store computer program instructions.

[0102] The above description is only an embodiment of the present application and is not intended to limit the present application. For those skilled in the art, the present application may have various modifications and variations. Any modification, equivalent substitution, improvement, etc. made within the spirit and principle of the present application shall be included in the scope of the claims of the present application.

Claims

1. A method for managing BOM data, characterized in that: The BOM data includes vehicle type BOM data and platform BOM data, the platform BOM data includes a plurality of different vehicle type BOM data, and the method includes: The vehicle model BOM data and the platform BOM data are stored in the form of a structure tree; The vehicle type BOM data is associated with the platform BOM data through a system plug-in, so that when the vehicle type BOM data is changed, the corresponding part in the platform BOM data can be changed synchronously.

2. The method according to claim 1, characterized in that: The structure tree of the platform BOM data and the structure tree of the vehicle type BOM data both contain a physical installation assembly level and a component level in the same naming format, wherein the physical installation assembly level is the parent level of the component level.

3. The method according to claim 2, characterized in that The naming format of the physical installation assembly level corresponding to the structure tree of the vehicle model BOM data is the vehicle model project code plus multi-digit characters, and the naming format of the physical installation assembly level corresponding to the structure tree of the platform BOM data is the platform project code plus multi-digit characters, wherein, if the multi-digit characters are the same, the physical installation assembly level in the structure tree of the vehicle model BOM data is the same as the physical installation assembly level in the structure tree of the platform BOM data, the component levels under the same physical installation assembly level are the same, and the codes corresponding to the same components are the same.

4. The method according to claim 3, characterized in that When the vehicle model BOM data is changed, the corresponding part of the platform BOM data can be changed synchronously, including: When a replacement operation is performed on a component at a target entity installation assembly level in the structure tree of the vehicle model BOM data, the system plug-in is used to detect whether a component having the same code as the replaced component is included at a physical installation assembly level that is the same as the target physical installation assembly level in the structure tree of the platform BOM data; If the physical installation assembly level that is the same as the target physical installation assembly level in the structure tree of the platform BOM data does not contain a component with the same code as the replaced component, then replace the component under the target physical installation assembly level in the structure tree of the vehicle model BOM data; If a component having the same code as the replaced component is included under the entity installation assembly level that is the same as the target entity installation assembly level in the structure tree of the platform BOM data, the release status of the entity installation assembly level that is the same as the target entity installation assembly level in the structure tree of the platform BOM data is detected by the system plug-in; When the publishing status is a frozen status, changing the publishing status to an active status through the system plug-in; When the release status is active, the system plug-in automatically replaces the components with the same code as the replaced components in the structure tree of the platform BOM data.

5. The method according to claim 3, characterized in that: When the vehicle model BOM data is changed, the corresponding part of the platform BOM data can be changed synchronously, including: When a component under a target entity installation assembly level in the structure tree of the vehicle model BOM data is deleted, the system plug-in is used to detect whether a component with the same code as the deleted component is included in the entity installation assembly level that is the same as the target entity installation assembly level in the structure tree of the platform BOM data; If the entity installation assembly level that is the same as the target entity installation assembly level in the structure tree of the platform BOM data does not contain a component with the same code as the deleted component, then the component under the target entity installation assembly level in the structure tree of the vehicle model BOM data is deleted; If a component having the same code as the deleted component is included under the entity installation assembly level that is the same as the target entity installation assembly level in the structure tree of the platform BOM data, the publishing status of the entity installation assembly level that is the same as the target entity installation assembly level in the structure tree of the platform BOM data is detected by the system plug-in; When the publishing status is a frozen status, changing the publishing status to an active status through the system plug-in; When the publishing status is active, the system plug-in automatically and synchronously deletes the components with the same code as the deleted components in the structure tree of the platform BOM data.

6. The method according to claim 3, characterized in that When the vehicle model BOM data is changed, the corresponding part of the platform BOM data can be changed synchronously, including: When adding a new component to the target entity installation assembly level in the structure tree of the vehicle model BOM data, determining whether the newly added component is a platform component; If the newly added component is not a platform component, then the component is added under the target entity installation assembly level in the structure tree of the vehicle model BOM data; If the newly added component is a platform component, the system plug-in automatically and synchronously adds the component at the same entity installation assembly level as the target entity installation assembly level in the structure tree of the platform BOM data.

7. The method according to claim 3, characterized in that The method further comprises: When the name of the physical installation assembly level in the structure tree of the vehicle model BOM data is changed, the name of the physical installation assembly level that is the same as the changed physical installation assembly level in the structure tree of the platform BOM data is synchronously changed through the system plug-in; and / or, When the code of the component under the physical installation assembly level in the structure tree of the vehicle model BOM data is changed, the code of the component identical to the changed component in the structure tree of the platform BOM data is synchronously changed through the system plug-in.

8. The method according to claim 1, characterized in that: The method further comprises: When deleting a component in the structure tree of the platform BOM data, the system plug-in detects whether the component to be deleted belongs to the data in the selected project; In the case where the component to be deleted belongs to the data in the selected project, it is allowed to delete the component in the structure tree of the platform BOM data, and the component is automatically and synchronously deleted in the structure tree of the vehicle model BOM data through the system plug-in.

9. A computer program product, characterized in that The computer program product includes computer instructions, which are stored in a computer-readable storage medium and are suitable for being read and executed by a processor, so that a computer device having the processor executes the method according to any one of claims 1 to 8.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer program instructions, which are loaded and executed by a processor to implement the operations performed by the method according to any one of claims 1 to 8.

Images