Hybrid software BOM management method and system and computer program

Abstract

The invention discloses a hybrid software BOM management method and system and a computer program, and the method comprises the following steps: maintaining an EEA grouping structure corresponding to a BOM room according to an automobile electronic and electrical architecture; selecting a controller node of an EEA grouping structure, and creating a corresponding software product object; configuring an exclusive structure management space for the software product object; defining that the software product object has a corresponding software package, and uploading the software package corresponding to the software product object to a management space of the software product object; and adding a corresponding usage to the software product object in the BOM room. According to the technical scheme provided by the invention, the characteristics of usage and software products are utilized, and the mixed BOM is established for software BOM management, so that the requirement of accurate control of upstream software change is met, and the flexibility of using software combination by a downstream production end is also considered.

Description

Technical Field

[0001] The present invention relates to the field of vehicle technology, and in particular to a hybrid software BOM management method, system and computer program. Background Art

[0002] The combination of vehicle ECU (Electronic Control Unit) software is called a software product. In order to manage software products, car companies generally use the vehicle PLM (Product Lifecycle Management) system to build a software BOM.

[0003] At present, vehicle PLM systems generally adopt a flat BOM management solution that displays a parts list. This BOM structure can obtain a clear bill of materials, but it cannot reflect the product structure hierarchy, nor can it meet a variety of application scenarios and needs. Summary of the invention

[0004] In view of the above-mentioned deficiencies in the current technology, the present invention provides a hybrid software BOM management method, which utilizes the characteristics of usage lines and software products to build a hybrid BOM for software BOM management, which not only meets the needs of precise control of upstream software changes, but also takes into account the flexibility of software combinations used by downstream production ends.

[0005] To achieve the above object, the embodiments of the present invention adopt the following technical solutions:

[0006] A hybrid software BOM management method comprises the following steps:

[0007] Maintain the EEA grouping structure corresponding to the BOM room according to the automotive electrical and electronic architecture;

[0008] Select the controller node of the EEA grouping structure and create the corresponding software product object;

[0009] Configure a dedicated structure management space for software product objects;

[0010] Define that the software product object has a corresponding software package, and upload the software package corresponding to the software product object to its management space;

[0011] Add a corresponding usage line for the software product object in the BOM room.

[0012] According to one aspect of the present invention, the EEA grouping structure includes a control domain layer and a controller layer.

[0013] According to one aspect of the present invention, the software product includes application software, driver software, and calibration software types.

[0014] According to one aspect of the present invention, the usage line includes: a usage address, a unique line number determined by a software product part number, and a usage expression for maintaining the usage line.

[0015] According to one aspect of the present invention, the hybrid software BOM management method further includes:

[0016] Add the corresponding software and hardware version information in the management space of the software product object.

[0017] According to one aspect of the present invention, the hybrid software BOM management method further includes:

[0018] Add usage lines to the work order;

[0019] After the work order is approved, the usage line can be officially used.

[0020] According to one aspect of the present invention, the hybrid software BOM management method further includes:

[0021] Maintain the automotive electrical and electronic architecture.

[0022] According to one aspect of the present invention, the maintenance of the automotive electronic and electrical architecture includes:

[0023] Maintain the structural relationship of software product objects;

[0024] Update the software package corresponding to the software product object according to the R&D progress;

[0025] Change the usage line according to actual situation.

[0026] A hybrid software BOM management system, based on the hybrid software BOM management method as described above, comprises:

[0027] Structure tree building module, used to maintain the EEA grouping structure corresponding to the BOM room according to the automotive electronic and electrical architecture;

[0028] A software object creation module is used to select a controller node of the EEA grouping structure and create a corresponding software product object;

[0029] A management space creation module is used to configure a dedicated structure management space for a software object;

[0030] An upload module, used to define that a software product object has a corresponding software package, and upload the software package corresponding to the software product object to its management space;

[0031] The usage line adding module is used to add corresponding usage lines for software product objects in the BOM room.

[0032] A computer program, which implements the steps of the hybrid software BOM management method as described above when executed.

[0033] Advantages of the present invention:

[0034] The present invention provides a hybrid software BOM management method, which utilizes usage lines and characteristics of software products to build a hybrid BOM for software BOM management, which not only meets the needs of precise control of upstream software changes, but also takes into account the flexibility of software combinations used by downstream production ends. BRIEF DESCRIPTION OF THE DRAWINGS

[0035] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings required for use in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0036] Figure 1 This is a flow chart of a hybrid software BOM management method according to Embodiment 1 of the present invention;

[0037] Figure 2 It is a structural diagram of the hybrid software BOM of the present invention;

[0038] Figure 3 This is a flow chart of a hybrid software BOM management method described in Embodiment 2 or 3 of the present invention. DETAILED DESCRIPTION

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

[0040] Embodiment 1

[0041] like Figure 1 and 2 As shown, a hybrid software BOM management method includes the following steps:

[0042] S1: Maintain the EEA grouping structure corresponding to the BOM room according to the automotive electrical and electronic architecture.

[0043] The EEA grouping structure includes a control domain layer, a controller layer, and the like.

[0044] In practical applications, this EEA grouping structure can clearly display the hierarchical relationship and interconnection between various ECUs in the car, which helps to better manage and maintain software products.

[0045] S2: Select a controller node of the EEA grouping structure and create a corresponding software product object.

[0046] The software products include application software, driver software, calibration software, etc. These different types of products play different roles in the automotive electronic system, and can be effectively classified and managed through this management method.

[0047] The software product objects represent the actual software components of the vehicle controller.

[0048] S3: Configure a dedicated structure management space for software product objects.

[0049] In order to better manage these software product objects, a dedicated management space is configured for each object. In this management space, software packages can be uploaded, and relevant information of software products, including versions, update history, etc., can be recorded and managed in detail.

[0050] S4: Define that the software product object has a corresponding software package, and upload the software package corresponding to the software product object to its management space.

[0051] This ensures that version control and update management of software packages is more orderly and efficient.

[0052] S5: Add corresponding usage lines for the software product object in the BOM room.

[0053] In actual applications, usage lines are also called LOU lines. They are the smallest unit and core model of usage BOM management. By adding LOU lines to the structure tree of a software product, the use and management of structure and usage are realized at the same time. This information helps ensure the correct use and maintenance of software products in actual applications.

[0054] The usage line includes: a usage address, a unique line number determined by a software product part number, a usage expression for maintaining the usage line, and the like.

[0055] LOU line: Usage address + software product part number determines the unique line number. Changes to other line attributes will result in a line upgrade. The LOU line defines the usage changes of the software product that is flashed with the vehicle usage address.

[0056] Preferably, the method further comprises:

[0057] Add the corresponding software and hardware version information in the management space of the software product object.

[0058] In practical applications, during the process of managing software products, not only the version of the software itself needs to be concerned about, but also the version information of the supporting hardware devices. Specifically, it includes key information such as the release version number of the software, the update date, the patch level, as well as the model of the hardware device, the firmware version, the driver version, etc. By comprehensively recording this information, it can be ensured that during the development, testing, deployment, and maintenance processes of software products, the compatibility and performance of each component can be accurately traced and managed. Such an approach helps to improve the stability and reliability of software products, and at the same time facilitates quick positioning and resolution of problems when they occur.

[0059] Preferably, this method further includes:

[0060] Add the BOM line of the software product layer to the TO work order and release it.

[0061] In practical applications, adding the BOM line of the software product layer to the TO work order and releasing it means integrating and publicly disclosing the data and information related to the software product so that all relevant personnel can view and use this information. Through this operation, we ensure the integrity and accuracy of the BOM, and at the same time improve the efficiency and transparency of the entire production process.

[0062] The beneficial effect of this embodiment lies in that this method uses the characteristics of usage lines and software products to build a hybrid BOM for software BOM management, which not only meets the needs of precise control of upstream software changes but also takes into account the flexibility of using software combinations at the downstream production end.

[0063] Embodiment Two

[0064] As Figure 2 and 3 shown, a hybrid software BOM management method includes the following steps:

[0065] S1: According to the automotive electronic and electrical architecture, maintain the EEA grouping structure corresponding to the BOM room.

[0066] The EEA grouping structure includes a control domain layer, a controller layer, etc.

[0067] In practical applications, this EEA grouping structure can clearly show the hierarchical relationship and mutual connection between each ECU in the vehicle, which helps to better manage and maintain software products.

[0068] S2: Select the controller node of the EEA grouping structure and create a corresponding software product object.

[0069] The software products include types such as application software, driver software, calibration software, etc. These different types of products play different roles in the automotive electronic system, and through this management method, they can be effectively classified and managed.

[0070] The software product objects represent the actual software components of the vehicle controller.

[0071] S3: Configure a dedicated structure management space for software product objects.

[0072] In order to better manage these software product objects, a dedicated management space is configured for each object. In this management space, software packages can be uploaded, and relevant information of software products, including versions, update history, etc., can be recorded and managed in detail.

[0073] S4: Define that the software product object has a corresponding software package, and upload the software package corresponding to the software product object to its management space.

[0074] This ensures that version control and update management of software packages is more orderly and efficient.

[0075] S5: Add corresponding usage lines for the software product object in the BOM room.

[0076] In actual applications, usage lines are also called LOU lines. They are the smallest unit and core model of usage BOM management. By adding LOU lines to the structure tree of a software product, the use and management of structure and usage are realized at the same time. This information helps ensure the correct use and maintenance of software products in actual applications.

[0077] The usage line includes: a usage address, a unique line number determined by a software product part number, a usage expression for maintaining the usage line, and the like.

[0078] LOU line: Usage address + software product part number determines the unique line number. Changes to other line attributes will result in line upgrades. LOU line defines the usage changes of the software product that is flashed with the vehicle usage address.

[0079] Preferably, the method further comprises:

[0080] Add the corresponding software and hardware version information in the management space of the software product object.

[0081] In actual applications, when managing software products, we should not only pay attention to the version of the software itself, but also the version information of the hardware devices that match it. Specifically, it includes key information such as the software release version number, update date, patch level, and hardware device model, firmware version, driver version, etc. By fully recording this information, we can ensure that the compatibility and performance of each component can be accurately tracked and managed during the development, testing, deployment, and maintenance of software products. This approach helps to improve the stability and reliability of software products, and also facilitates the rapid location and resolution of problems when they occur.

[0082] Preferably, the method further comprises:

[0083] The software product layer BOM line is added to the TO work order and released.

[0084] In actual application, the software product layer BOM line is added to the TO work order and released, that is, the data and information related to the software product are integrated and published to the public so that all relevant personnel can view and use this information. Through this operation, we ensure the integrity and accuracy of the BOM, and also improve the efficiency and transparency of the entire production process.

[0085] S6: Add the usage line to the work order.

[0086] S7: After the work order is approved, the usage line can be officially used.

[0087] In actual applications, EWO work orders are usually used to automatically release LOU lines. The LOU lines to be released are added to the EWO work order, and then submitted to the relevant reviewers for review. After careful review and confirmation, the reviewers will give a pass on the work order. Once approved, these LOU lines can be officially put into use, thus ensuring the efficiency and smoothness of the entire process. This process ensures that the use process of the software product meets the company's standards and specifications.

[0088] The beneficial effect of this embodiment is that this method provides rigor in software BOM management by adding usage lines to the work order and approving it before formal use.

[0089] Embodiment 3

[0090] like Figure 2 and 3 As shown, a hybrid software BOM management method includes the following steps:

[0091] S1: Maintain the EEA grouping structure corresponding to the BOM room according to the automotive electrical and electronic architecture.

[0092] The EEA grouping structure includes a control domain layer, a controller layer, and the like.

[0093] In practical applications, this EEA grouping structure can clearly display the hierarchical relationship and interconnection between various ECUs in the car, which helps to better manage and maintain software products.

[0094] S2: Select a controller node of the EEA grouping structure and create a corresponding software product object.

[0095] The software products include application software, driver software, calibration software, etc. These different types of products play different roles in the automotive electronic system, and can be effectively classified and managed through this management method.

[0096] The software product objects represent the actual software components of the vehicle controller.

[0097] S3: Configure a dedicated structure management space for software product objects.

[0098] In order to better manage these software product objects, a dedicated management space is configured for each object. In this management space, software packages can be uploaded, and relevant information of software products, including versions, update history, etc., can be recorded and managed in detail.

[0099] S4: Define that the software product object has a corresponding software package, and upload the software package corresponding to the software product object to its management space.

[0100] This ensures that version control and update management of software packages is more orderly and efficient.

[0101] S5: Add corresponding usage lines for the software product object in the BOM room.

[0102] In actual applications, usage lines are also called LOU lines. They are the smallest unit and core model of usage BOM management. By adding LOU lines to the structure tree of a software product, the use and management of structure and usage are realized at the same time. This information helps ensure the correct use and maintenance of software products in actual applications.

[0103] The usage line includes: a usage address, a unique line number determined by a software product part number, a usage expression for maintaining the usage line, and the like.

[0104] LOU line: Usage address + software product part number determines the unique line number. Changes to other line attributes will result in line upgrades. LOU line defines the usage changes of the software product that is flashed with the vehicle usage address.

[0105] Preferably, the method further comprises:

[0106] Add the corresponding software and hardware version information in the management space of the software product object.

[0107] In actual applications, when managing software products, we should not only pay attention to the version of the software itself, but also the version information of the hardware devices that match it. Specifically, it includes key information such as the software release version number, update date, patch level, and hardware device model, firmware version, driver version, etc. By fully recording this information, we can ensure that the compatibility and performance of each component can be accurately tracked and managed during the development, testing, deployment, and maintenance of software products. This approach helps to improve the stability and reliability of software products, and also facilitates the rapid location and resolution of problems when they occur.

[0108] Preferably, the method further comprises:

[0109] The software product layer BOM line is added to the TO work order and released.

[0110] In actual application, the software product layer BOM line is added to the TO work order and released, that is, the data and information related to the software product are integrated and published to the public so that all relevant personnel can view and use this information. Through this operation, we ensure the integrity and accuracy of the BOM, and also improve the efficiency and transparency of the entire production process.

[0111] Preferably, the method further comprises:

[0112] S6: Add the usage line to the work order.

[0113] S7: After the work order is approved, the usage line can be officially used.

[0114] In actual applications, EWO work orders are usually used to automatically release LOU lines. The LOU lines to be released are added to the EWO work order, and then submitted to the relevant reviewers for review. After careful review and confirmation, the reviewers will give a pass on the work order. Once approved, these LOU lines can be officially put into use, thus ensuring the efficiency and smoothness of the entire process. This process ensures that the use process of the software product meets the company's standards and specifications.

[0115] The method further comprises:

[0116] Maintain the automotive electrical and electronic architecture.

[0117] The maintenance of the automotive electronic and electrical architecture includes:

[0118] Maintain the structural relationship of software product objects;

[0119] Update the software package corresponding to the software product object according to the R&D progress;

[0120] Change the usage line according to actual situation.

[0121] In practical applications, it is necessary to maintain the structural relationship of software products, ensure that the relationship between various software components is properly managed and updated, and ensure the stability and consistency of the entire software system.

[0122] According to the progress of R&D, the software packages corresponding to the software products need to be updated in time. In actual applications, as the project progresses, new functional modules will be developed and old modules may be modified or replaced. Therefore, the software packages need to be updated in time to ensure that all modules are up to date and can work together seamlessly. This includes adding new software packages, replacing old software packages, and fixing known bugs and problems.

[0123] When the usage of software products changes, timely changes are also required.

[0124] These maintenance measures help keep the vehicle structure tree accurate and up-to-date, thus ensuring effective management of software products.

[0125] The beneficial effect of this embodiment is that the method also maintains and updates the software BOM according to actual needs, making the software BOM management more complete.

[0126] Embodiment 4

[0127] A hybrid software BOM management system, based on the hybrid software BOM management method as described in Embodiment 1, 2 or 3, comprises:

[0128] Structure tree building module, used to maintain the EEA grouping structure corresponding to the BOM room according to the automotive electronic and electrical architecture;

[0129] A software object creation module is used to select a controller node of the EEA grouping structure and create a corresponding software product object;

[0130] A management space creation module is used to configure a dedicated structure management space for a software object;

[0131] An upload module, used to define that a software product object has a corresponding software package, and upload the software package corresponding to the software product object to its management space;

[0132] The usage line adding module is used to add corresponding usage lines for software product objects in the BOM room.

[0133] Preferably, the system further includes:

[0134] The work order module is used to add usage lines to work orders. After the work order is approved, the usage lines can be officially used.

[0135] Preferably, the system further includes:

[0136] Maintenance module, used to maintain the automotive electrical and electronic architecture.

[0137] Embodiment 5

[0138] A computer program, when executed, implements the steps of the hybrid software BOM management method as described in Embodiment 1, 2 or 3.

[0139] Embodiment 6

[0140] A readable storage medium stores a computer program as described in Example 4, and when the computer program is executed, the steps of the hybrid software BOM management method as described in Example 1, 2 or 3 are implemented.

[0141] The above is only a specific embodiment of the present invention, but the protection scope of the present invention is not limited thereto. Any changes or substitutions that can be easily thought of by any technician familiar with the art within the technical scope disclosed in the present invention should be included in the protection scope of the present invention. Therefore, the protection scope of the present invention shall be based on the protection scope of the claims.

Claims

1. A hybrid software BOM management method, characterized in that: The following steps are involved: Maintain the EEA grouping structure corresponding to the BOM room according to the automotive electrical and electronic architecture; Select the controller node of the EEA grouping structure and create the corresponding software product object; Configure a dedicated structure management space for software product objects; Define that the software product object has a corresponding software package, and upload the software package corresponding to the software product object to its management space; Add a corresponding usage line for the software product object in the BOM room.

2. The hybrid software BOM management method according to claim 1, characterized in that: The EEA grouping structure includes a control domain layer and a controller layer.

3. The hybrid software BOM management method according to claim 1, characterized in that: The software products include application software, driver software, and calibration software types.

4. The hybrid software BOM management method according to claim 1, characterized in that: The usage line includes: a usage address, a unique line number determined by a software product part number, and a usage expression for maintaining the usage line.

5. The hybrid software BOM management method according to claim 1, characterized in that: The hybrid software BOM management method further includes: Add the corresponding software and hardware version information in the management space of the software product object.

6. The hybrid software BOM management method according to claim 1, characterized in that: The hybrid software BOM management method further includes: Add usage lines to the work order; After the work order is approved, the usage line can be officially used.

7. The hybrid software BOM management method according to claim 1, characterized in that: The hybrid software BOM management method further includes: Maintain the automotive electrical and electronic architecture.

8. The hybrid software BOM management method according to claim 1, characterized in that: The maintenance of the automotive electronic and electrical architecture includes: Maintain the structural relationship of software product objects; Update the software package corresponding to the software product object according to the R&D progress; Change the usage line according to actual situation.

9. A hybrid software BOM management system, characterized in that: The hybrid software BOM management method according to any one of claims 1 to 8 comprises: Structure tree building module, used to maintain the EEA grouping structure corresponding to the BOM room according to the automotive electronic and electrical architecture; A software object creation module is used to select a controller node of the EEA grouping structure and create a corresponding software product object; A management space creation module is used to configure a dedicated structure management space for a software object; An upload module, used to define that a software product object has a corresponding software package, and upload the software package corresponding to the software product object to its management space; The usage line adding module is used to add corresponding usage lines for software product objects in the BOM room.

10. A computer program, characterized in that When the computer program is executed, the steps of the hybrid software BOM management method according to any one of claims 1 to 8 are implemented.

Images