Method and apparatus for converting EBOM to MBOM based on collaborative projects

Abstract

This application relates to a method and apparatus for converting EBOM to MBOM based on collaborative projects, belonging to the field of automotive design technology. The method includes the following steps: a first working end builds an EBOM based on a corresponding first encoding rule; a second working end performs internal transcoding on the EBOM to generate second-end component coding information; the second working end adds corresponding process route information and effective time information based on the second-end component coding information; and the second working end generates the corresponding MBOM based on the second-end component coding information, process route information, and effective time information. This application achieves automatic conversion of EBOM to MBOM data through internal transcoding, while still preserving the structural hierarchy of the EBOM, thus improving the efficiency and accuracy of automatic data conversion.

Description

Technical Field

[0001] This application relates to the field of automotive design technology, specifically to a method and apparatus for converting EBOM to MBOM based on collaborative projects. Background Technology

[0002] In the automotive industry, it's common practice for OEMs' technology centers to conduct research and development on key automotive products like engine assemblies and new energy powertrain modules, while component suppliers handle procurement, production, and sales. This model involves collaboration between two R&D units: R&D unit X designs the new energy module and manages the EBOM (Electronic Business Model Occupational Data), while R&D unit Y manufactures the new energy module and manages the MBOM (Mean Business Model Occupational Data).

[0003] A single new energy vehicle powertrain module comprises over 200 parts. With increasingly stringent product quality requirements in the automotive market, continuous cost reductions in components, and ever-changing market demands, design changes to these parts are becoming more frequent. These design changes directly lead to real-time updates to the EBOM (Electronic Business Components) data, and accurately and efficiently transmitting this data to collaborating units is a pressing issue.

[0004] Therefore, to meet actual design and production needs, a technology for converting EBOM to MBOM based on collaborative projects is provided. Summary of the Invention

[0005] This application provides a method and apparatus for converting EBOM to MBOM based on collaborative projects. It achieves automatic conversion of EBOM to MBOM data through internal transcoding, while still preserving the structural hierarchy of EBOM, thus improving the efficiency and accuracy of automatic data conversion.

[0006] To achieve the above objectives, this application provides the following solution.

[0007] Firstly, this application provides a method for converting EBOM to MBOM based on collaborative projects, the method comprising the following steps:

[0008] The first working end builds the EBOM based on the corresponding first encoding rule;

[0009] The second working end performs internal transcoding based on the EBOM to generate second-end component coding information;

[0010] The second working end adds corresponding process route information and effective time information based on the component coding information of the second end;

[0011] The second working end generates the corresponding MBOM based on the component coding information of the second end, the process route information, and the effective time information.

[0012] Furthermore, the second working end performs internal transcoding based on the EBOM to generate the second-end component coding information, including the following steps:

[0013] The second working end performs internal transcoding based on the EBOM to generate material component codes, component names, and change tags that conform to the corresponding second encoding rules;

[0014] Based on the corresponding drawing information in the first working terminal, internal conversion is performed to generate the corresponding drawing number and drawing number mark;

[0015] Based on the material component code, the component name, the change mark, the drawing number, and the drawing number mark, the corresponding second-end component code information is generated.

[0016] Furthermore, the method also includes the following steps:

[0017] The second working terminal establishes a correspondence between the component coding information of the second terminal and the component coding information of the first terminal, generates a correspondence table, and feeds it back to the first working terminal; wherein,

[0018] The first end component coding information includes the material component code, component name, change mark, drawing number and drawing number mark corresponding to the first working end.

[0019] Furthermore, the method also includes the following steps:

[0020] When the EBOM undergoes design changes, the corresponding EBOM change information is obtained;

[0021] Based on the EBOM change information and the corresponding relationship table, the MBOM is changed synchronously.

[0022] Furthermore, the first working end constructs the EBOM based on the corresponding first encoding rule, including the following steps:

[0023] The first working end builds the upper-level structure data of the EBOM based on the corresponding first encoding rule, and then generates the EBOM with the drawing information.

[0024] Secondly, this application provides an EBOM to MBOM conversion device based on collaborative projects, the device comprising:

[0025] The EBOM building module is used to control the first working end to build the EBOM based on the corresponding first encoding rule.

[0026] An internal transcoding module is used to control the second working end to perform internal transcoding based on the EBOM to generate component coding information for the second end.

[0027] The information addition module is used to control the second working end to add corresponding process route information and effective time information based on the component coding information of the second end;

[0028] The MBOM generation module controls the second working end to generate the corresponding MBOM based on the component coding information of the second end, the process route information, and the effective time information.

[0029] Furthermore, the device also includes:

[0030] The internal transcoding module is also used to control the second working end to perform internal transcoding based on the EBOM to generate material component codes, component names and change marks that conform to the corresponding second encoding rules;

[0031] The internal transcoding module is also used to perform internal conversion based on the corresponding drawing information in the first working terminal to generate the corresponding drawing number and drawing number mark.

[0032] The internal transcoding module is also used to generate corresponding second-end component code information based on the material component code, the component name, the change mark, the drawing number, and the drawing number mark.

[0033] Furthermore, the device also includes:

[0034] The relationship table establishment module is used to control the second working end to establish a correspondence between the component coding information of the second end and the component coding information of the first end of the first working end, generate a correspondence table, and feed it back to the first working end; wherein,

[0035] The first end component coding information includes the material component code, component name, change mark, drawing number and drawing number mark corresponding to the first working end.

[0036] Furthermore, the device also includes:

[0037] The information synchronization module is used to obtain the corresponding EBOM change information when the EBOM undergoes design changes;

[0038] The information synchronization module is also used to synchronize the changes to the MBOM based on the EBOM change information and the corresponding relationship table.

[0039] Furthermore, the device also includes:

[0040] The EBOM building module is also used by the first working end to build the upper-level structure data of the EBOM based on the corresponding first encoding rule, thereby generating an EBOM with the drawing information.

[0041] The beneficial effects of the technical solution provided in this application include:

[0042] This application achieves automatic conversion of EBOM to MBOM data through internal transcoding, while still preserving the structural hierarchy of EBOM, thus improving the efficiency and accuracy of automatic data conversion. Attached Figure Description

[0043] Terminology Explanation:

[0044] BOM: Bill of Material;

[0045] EBOM: Engineering BOM, Design Bill of Materials;

[0046] MBOM: Manufacturing BOM (Bill of Materials for Manufacturing).

[0047] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0048] Figure 1 This is a flowchart illustrating the steps of the EBOM to MBOM conversion method based on collaborative projects provided in this application embodiment;

[0049] Figure 2 This is a flowchart illustrating the principle of the EBOM to MBOM conversion method based on collaborative projects provided in the embodiments of this application.

[0050] Figure 3 This is a schematic diagram of double-number management in the EBOM to MBOM conversion method based on collaborative projects provided in the embodiments of this application;

[0051] Figure 4 This is a structural block diagram of the EBOM to MBOM conversion device based on collaborative projects provided in the embodiments of this application. Detailed Implementation

[0052] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0053] The embodiments of this application will be further described in detail below with reference to the accompanying drawings.

[0054] This application provides a method and apparatus for converting EBOM to MBOM based on collaborative projects. It achieves automatic conversion of EBOM to MBOM data through internal transcoding, while still preserving the structural hierarchy of EBOM, thus improving the efficiency and accuracy of automatic data conversion.

[0055] To achieve the aforementioned technical effects, the overall concept of this application is as follows:

[0056] A method for converting EBOM to MBOM based on collaborative projects, the method includes the following steps:

[0057] S1. The first working end builds EBOM based on the corresponding first encoding rule;

[0058] S2. The second working end performs internal transcoding based on EBOM to generate the second end component coding information;

[0059] S3. The second working end adds corresponding process route information and effective time information based on the component coding information of the second end;

[0060] S4. The second working end generates the corresponding MBOM based on the component coding information, process route information and effective time information of the second end.

[0061] The embodiments of this application will be further described in detail below with reference to the accompanying drawings.

[0062] Firstly, see [the following] Figures 1-3 As shown in the figure, this application provides a method for converting EBOM to MBOM based on collaborative projects. The method includes the following steps:

[0063] S1. The first working end builds EBOM based on the corresponding first encoding rule;

[0064] S2. The second working end performs internal transcoding based on EBOM to generate the second end component coding information;

[0065] S3. The second working end adds corresponding process route information and effective time information based on the component coding information of the second end;

[0066] S4. The second working end generates the corresponding MBOM based on the component coding information, process route information and effective time information of the second end.

[0067] The technical solution of this application embodiment not only meets the business solution of component design change management in multi-unit collaborative design and development, but also meets the business scenario requirements of frequent design changes where the component change mark status changes but the component code remains unchanged.

[0068] It achieves automatic conversion of EBOM to MBOM data, and the converted MBOM data retains the structural hierarchy of EBOM. By comparing EBOM and MBOM data, abnormal data in the EBOM to MBOM data conversion process caused by system bugs or system instability can be quickly detected, thus improving the efficiency and accuracy of automatic data conversion.

[0069] In this embodiment, the automatic conversion of EBOM to MBOM data is achieved through internal transcoding, while still preserving the structural hierarchy of EBOM, thus improving the efficiency and accuracy of automatic data conversion.

[0070] It should be noted that background explanations are provided for the relevant terms:

[0071] Component code: A code representing a product using a specified number of characters, also known as a material number. It is a unique identification code automatically generated by the system and includes virtual product numbers and management numbers generated for technical, manufacturing, and management needs.

[0072] Change markers, also known as change marker information, refer to the codes indicating that a part has undergone physical changes but that do not affect its interchangeability. They are numbered sequentially, starting with two characters "00" or the Arabic numeral "a". The purpose of change markers is to track the evolution of part definitions.

[0073] EBOM: During the product design phase, designers obtain a list of components and materials needed to organize and manage the product from the design drawings; this is known as the Engineering BOM (EBOM). The EBOM primarily includes the product's design attributes (component codes, part names, part quantities, change markers, materials, technical features, etc.) and assembly hierarchy relationships. The EBOM always reflects the latest state of the product design and forms the basis for compiling the manufacturing BOM data.

[0074] MBOM: After the design BOM is released, the data management engineer adds process routes (including manufacturing routes and assembly routes) and effective dates to the design BOM based on the requirements of manufacturing processes, procurement, logistics, and assembly, thus generating the Manufacturing BOM. The Manufacturing BOM expresses the product evolution status at various points in time (including past definitions, present definitions, and future definitions). The structure of the MBOM and the evolution of parts are derived from the EBOM.

[0075] The above technical solution not only meets the business solution of dual-number management of component design changes in collaborative design and development by multiple units, but also meets the business scenario requirements of frequent design changes where the status of component change markers changes but the component code remains unchanged.

[0076] It achieves automatic conversion of EBOM to MBOM data, and the converted MBOM data retains the structural hierarchy of EBOM. By comparing EBOM and MBOM data, abnormal data in the EBOM to MBOM data conversion process caused by system bugs or system instability can be quickly detected, thus improving the efficiency and accuracy of automatic data conversion.

[0077] Furthermore, the second working end performs internal transcoding based on the EBOM to generate the second-end component coding information, including the following steps:

[0078] The second working end performs internal transcoding based on the EBOM to generate material component codes, component names, and change tags that conform to the corresponding second encoding rules;

[0079] Based on the corresponding drawing information in the first working terminal, internal conversion is performed to generate the corresponding drawing number and drawing number mark;

[0080] Based on the material component code, the component name, the change mark, the drawing number, and the drawing number mark, the corresponding second-end component code information is generated.

[0081] Furthermore, the method also includes the following steps:

[0082] The second working terminal establishes a correspondence between the component coding information of the second terminal and the component coding information of the first terminal, generates a correspondence table, and feeds it back to the first working terminal; wherein,

[0083] The first end component coding information includes the material component code, component name, change mark, drawing number and drawing number mark corresponding to the first working end.

[0084] Furthermore, the method also includes the following steps:

[0085] When the EBOM undergoes design changes, the corresponding EBOM change information is obtained;

[0086] Based on the EBOM change information and the corresponding relationship table, the MBOM is changed synchronously.

[0087] Furthermore, the first working end constructs the EBOM based on the corresponding first encoding rule, including the following steps:

[0088] The first working end builds the upper-level structure data of the EBOM based on the corresponding first encoding rule, and then generates the EBOM with the drawing information.

[0089] Assuming the first working end in this application embodiment is R&D unit X and the second working end is R&D unit Y, based on the technical solution of this application embodiment, in actual implementation, as shown in the accompanying drawings. Figure 2 As shown, the specific situation is as follows:

[0090] Step 1: R&D unit X builds the upper-level structure data of EBOM according to its own coding rules and publishes EBOM with drawing information;

[0091] Step 2: R&D unit Y obtains the EBOM data of R&D unit X through the system interface;

[0092] Step 3: R&D unit Y internally transcodes the EBOM data received from R&D unit X to generate material and component codes, component names, change marks, and other information that are adapted to its own coding rules. It also internally converts the drawings from R&D unit X to generate drawing numbers and drawing number marks for R&D unit Y.

[0093] Step 4: R&D unit Y adds process route and effective time information to the newly generated material and component codes that meet its own coding rules;

[0094] Step 5: The R&D unit Y generates MBOM data and sends it to the production system.

[0095] It should be noted that when information is modified, step three above may include the following operations:

[0096] Step 3.1: R&D unit Y transcodes and generates new component coding information in the system, and establishes a correspondence table between R&D unit X and R&D unit Y for component codes, component names, drawing numbers, and drawing number markers, as shown in the attached diagram of the instruction manual. Figure 3 As shown;

[0097] Step 3.2: R&D unit Y transmits this dual-code correspondence table to R&D unit X through the system;

[0098] Step 3.3: Research and development unit X stores this correspondence table in the corresponding location;

[0099] Step 3.4: When the designer of R&D unit X publishes a part design change, the information in the corresponding relationship table is automatically called. The part code of R&D unit X is automatically used to retrieve the part code of R&D unit Y and other information, so as to realize dual number management.

[0100] The specific implementation process of the dual-number management scheme for component design changes issued by R&D unit X is as follows:

[0101] After the first version of EBOM is built and released, if the design change of the component does not meet the interchangeability requirements and involves the addition of a new component code, then return to step 1. The R&D unit releases the component code, component name, drawing number, drawing number mark and other information of the new component. Following steps 2 to 5, the R&D unit Y triggers the generation of the component code, component name, drawing number, drawing number mark and other information corresponding to the internal coding rules of the R&D unit Y, and defines the process route and effective time to build MBOM.

[0102] If a component design change meets interchangeability requirements and does not involve adding new component codes, but only requires an upgrade of the change markings for already released components, then the following steps should be followed:

[0103] Step 1: R&D unit X releases a design change to the upgraded version of the component change markings;

[0104] Step 2: The system finds the part code, component name, drawing number, drawing number mark, and other information corresponding to the part code of the design change part in R&D unit Y based on the dual-code correspondence table of R&D unit X and R&D unit Y, and automatically retrieves the information of the component in R&D unit Y.

[0105] Step 3: R&D unit Y upgrades the version of the part codes, drawings, drawing number versions, etc., that conform to R&D unit Y's coding rules and coding system;

[0106] Step 4: R&D unit Y adds an effective time to the new mark of its component code and builds MBOM.

[0107] The technical solution of this application embodiment realizes the management of component design changes in multi-unit collaborative design and development, realizes the simultaneous display of dual codes of components, and can automatically retrieve the component code information of another R&D unit when the R&D unit initiates a component design change.

[0108] By using component codes as a conversion bridge, a one-to-one conversion of component codes is achieved, realizing a unique correspondence between the two component codes. This avoids business scenarios where component codes are one-to-many and reduces the amount of manual verification work required for component code correspondence.

[0109] In summary, the technical solutions of this application have the following technical advantages:

[0110] First, this application does not require the two R&D units to introduce new design systems and design environments separately. It only requires adding data transmission interfaces to the existing design systems and performing internal transcoding. The design environment of the R&D designers remains unchanged, thus saving costs.

[0111] Secondly, R&D designers do not need to manage the dual coding correspondence between two R&D units offline. The system automatically converts EBOM to MBOM data with different coding rules and coding systems, which meets the data management needs of collaborative design and development by multiple units.

[0112] Thirdly, this application uses component codes as a bridge to perform one-to-one data conversion of component codes, realizing collaborative design and development among multiple units with different coding rules and coding systems. This reduces the workload of manual verification of the correspondence between component numbers of multiple units. At the same time, the system can be updated in real time, making it convenient for various business areas such as procurement, quality, process, and production management to view the correspondence between dual codes online.

[0113] Fourthly, this application does not change the hierarchical structure of EBOM, but retains the tree structure of EBOM. By comparing EBOM and MBOM data, abnormal data transmission problems caused by system bugs and instability during the EBOM to MBOM conversion process can be quickly identified, ensuring 100% accuracy of data transmission.

[0114] Fifthly, this application can meet the business scenario of the automotive industry with numerous parts and frequent design changes, realize design change management for collaborative design and development by multiple units, and automatically retrieve the part code information of another R&D unit when the R&D unit initiates a part design change, so that downstream production units in the fields of procurement, quality, process, cost, and finance can provide online feedback on the part design change.

[0115] It should be noted that the step numbers in the embodiments of this application do not limit the order of operations in the technical solution of this application.

[0116] Secondly, see Figure 4 As shown, based on the same inventive concept as the method embodiment, this application provides an EBOM to MBOM conversion device based on collaborative projects, the device comprising:

[0117] The EBOM building module is used to control the first working end to build the EBOM based on the corresponding first encoding rule.

[0118] An internal transcoding module is used to control the second working end to perform internal transcoding based on the EBOM to generate component coding information for the second end.

[0119] The information addition module is used to control the second working end to add corresponding process route information and effective time information based on the component coding information of the second end;

[0120] The MBOM generation module controls the second working end to generate the corresponding MBOM based on the component coding information of the second end, the process route information, and the effective time information.

[0121] The technical solution of this application embodiment not only meets the business solution of component design change management in multi-unit collaborative design and development, but also meets the business scenario requirements of frequent design changes where the component change mark status changes but the component code remains unchanged.

[0122] It achieves automatic conversion of EBOM to MBOM data, and the converted MBOM data retains the structural hierarchy of EBOM. By comparing EBOM and MBOM data, abnormal data in the EBOM to MBOM data conversion process caused by system bugs or system instability can be quickly detected, thus improving the efficiency and accuracy of automatic data conversion.

[0123] In this embodiment, the automatic conversion of EBOM to MBOM data is achieved through internal transcoding, while still preserving the structural hierarchy of EBOM, thus improving the efficiency and accuracy of automatic data conversion.

[0124] It should be noted that background explanations are provided for the relevant terms:

[0125] Component code: A code representing a product using a specified number of characters, also known as a material number. It is a unique identification code automatically generated by the system and includes virtual product numbers and management numbers generated for technical, manufacturing, and management needs.

[0126] Change markers, also known as change marker information, refer to the codes indicating that a part has undergone physical changes but that do not affect its interchangeability. They are numbered sequentially, starting with two characters "00" or the Arabic numeral "a". The purpose of change markers is to track the evolution of part definitions.

[0127] EBOM: During the product design phase, designers obtain a list of components and materials needed to organize and manage the product from the design drawings; this is known as the Engineering BOM (EBOM). The EBOM primarily includes the product's design attributes (component codes, part names, part quantities, change markers, materials, technical features, etc.) and assembly hierarchy relationships. The EBOM always reflects the latest state of the product design and forms the basis for compiling the manufacturing BOM data.

[0128] MBOM: After the design BOM is released, the data management engineer adds process routes (including manufacturing routes and assembly routes) and effective dates to the design BOM based on the requirements of manufacturing processes, procurement, logistics, and assembly, thus generating the Manufacturing BOM. The Manufacturing BOM expresses the product evolution status at various points in time (including past definitions, present definitions, and future definitions). The structure of the MBOM and the evolution of parts are derived from the EBOM.

[0129] The above technical solution not only meets the business solution of dual-number management of component design changes in collaborative design and development by multiple units, but also meets the business scenario requirements of frequent design changes where the status of component change markers changes but the component code remains unchanged.

[0130] It achieves automatic conversion of EBOM to MBOM data, and the converted MBOM data retains the structural hierarchy of EBOM. By comparing EBOM and MBOM data, abnormal data in the EBOM to MBOM data conversion process caused by system bugs or system instability can be quickly detected, thus improving the efficiency and accuracy of automatic data conversion.

[0131] Furthermore, the device also includes:

[0132] The internal transcoding module is also used to control the second working end to perform internal transcoding based on the EBOM to generate material component codes, component names and change marks that conform to the corresponding second encoding rules;

[0133] The internal transcoding module is also used to perform internal conversion based on the corresponding drawing information in the first working terminal to generate the corresponding drawing number and drawing number mark.

[0134] The internal transcoding module is also used to generate corresponding second-end component code information based on the material component code, the component name, the change mark, the drawing number, and the drawing number mark.

[0135] Furthermore, the device also includes:

[0136] The relationship table establishment module is used to control the second working end to establish a correspondence between the component coding information of the second end and the component coding information of the first end of the first working end, generate a correspondence table, and feed it back to the first working end; wherein,

[0137] The first end component coding information includes the material component code, component name, change mark, drawing number and drawing number mark corresponding to the first working end.

[0138] Furthermore, the device also includes:

[0139] The information synchronization module is used to obtain the corresponding EBOM change information when the EBOM undergoes design changes;

[0140] The information synchronization module is also used to synchronize the changes to the MBOM based on the EBOM change information and the corresponding relationship table.

[0141] Furthermore, the device also includes:

[0142] The EBOM building module is also used by the first working end to build the upper-level structure data of the EBOM based on the corresponding first encoding rule, thereby generating an EBOM with the drawing information.

[0143] Assuming the first working end in this embodiment is R&D unit X and the second working end is R&D unit Y, the specific implementation of the technical solution based on this embodiment is as follows:

[0144] Step 1: R&D unit X builds the upper-level structure data of EBOM according to its own coding rules and publishes EBOM with drawing information;

[0145] Step 2: R&D unit Y obtains the EBOM data of R&D unit X through the system interface;

[0146] Step 3: R&D unit Y internally transcodes the EBOM data received from R&D unit X to generate material and component codes, component names, change marks, and other information that are adapted to its own coding rules. It also internally converts the drawings from R&D unit X to generate drawing numbers and drawing number marks for R&D unit Y.

[0147] Step 4: R&D unit Y adds process route and effective time information to the newly generated material and component codes that meet its own coding rules;

[0148] Step 5: The R&D unit Y generates MBOM data and sends it to the production system.

[0149] It should be noted that when information is modified, step three above may include the following operations:

[0150] Step 3.1: R&D unit Y transcodes and generates new component coding information in the system, and establishes a correspondence table between R&D unit X and R&D unit Y for component codes, component names, drawing numbers, and drawing number markers, as shown in the attached diagram of the instruction manual. Figure 3 As shown;

[0151] Step 3.2: R&D unit Y transmits this dual-code correspondence table to R&D unit X through the system;

[0152] Step 3.3: Research and development unit X stores this correspondence table in the corresponding location;

[0153] Step 3.4: When the designer of R&D unit X publishes a part design change, the information in the corresponding relationship table is automatically called. The part code of R&D unit X is automatically used to retrieve the part code of R&D unit Y and other information, so as to realize dual number management.

[0154] The specific implementation process of the dual-number management scheme for component design changes issued by R&D unit X is as follows:

[0155] After the first version of EBOM is built and released, if the design change of the component does not meet the interchangeability requirements and involves the addition of a new component code, then return to step 1. The R&D unit releases the component code, component name, drawing number, drawing number mark and other information of the new component. Following steps 2 to 5, the R&D unit Y triggers the generation of the component code, component name, drawing number, drawing number mark and other information corresponding to the internal coding rules of the R&D unit Y, and defines the process route and effective time to build MBOM.

[0156] If a component design change meets interchangeability requirements and does not involve adding new component codes, but only requires an upgrade of the change markings for already released components, then the following steps should be followed:

[0157] Step 1: R&D unit X releases a design change to the upgraded version of the component change markings;

[0158] Step 2: The system finds the part code, component name, drawing number, drawing number mark, and other information corresponding to the part code of the design change part in R&D unit Y based on the dual-code correspondence table of R&D unit X and R&D unit Y, and automatically retrieves the information of the component in R&D unit Y.

[0159] Step 3: R&D unit Y upgrades the version of the part codes, drawings, drawing number versions, etc., that conform to R&D unit Y's coding rules and coding system;

[0160] Step 4: R&D unit Y adds an effective time to the new mark of its component code and builds MBOM.

[0161] The technical solution of this application embodiment realizes the management of component design changes in multi-unit collaborative design and development, realizes the simultaneous display of dual codes of components, and can automatically retrieve the component code information of another R&D unit when the R&D unit initiates a component design change.

[0162] By using component codes as a conversion bridge, a one-to-one conversion of component codes is achieved, realizing a unique correspondence between the two component codes. This avoids business scenarios where component codes are one-to-many and reduces the amount of manual verification work required for component code correspondence.

[0163] In summary, the technical solutions of this application have the following technical advantages:

[0164] First, this application does not require the two R&D units to introduce new design systems and design environments separately. It only requires adding data transmission interfaces to the existing design systems and performing internal transcoding. The design environment of the R&D designers remains unchanged, thus saving costs.

[0165] Secondly, R&D designers do not need to manage the dual coding correspondence between two R&D units offline. The system automatically converts EBOM to MBOM data with different coding rules and coding systems, which meets the data management needs of collaborative design and development by multiple units.

[0166] Thirdly, this application uses component codes as a bridge to perform one-to-one data conversion of component codes, realizing collaborative design and development among multiple units with different coding rules and coding systems. This reduces the workload of manual verification of the correspondence between component numbers of multiple units. At the same time, the system can be updated in real time, making it convenient for various business areas such as procurement, quality, process, and production management to view the correspondence between dual codes online.

[0167] Fourthly, this application does not change the hierarchical structure of EBOM, but retains the tree structure of EBOM. By comparing EBOM and MBOM data, abnormal data transmission problems caused by system bugs and instability during the EBOM to MBOM conversion process can be quickly identified, ensuring 100% accuracy of data transmission.

[0168] Fifthly, this application can meet the business scenario of the automotive industry with numerous parts and frequent design changes, realize design change management for collaborative design and development by multiple units, and automatically retrieve the part code information of another R&D unit when the R&D unit initiates a part design change, so that downstream production units in the fields of procurement, quality, process, cost, and finance can provide online feedback on the part design change.

[0169] It should be noted that the EBOM to MBOM conversion device based on collaborative projects provided in this application has similar technical problems, technical means and technical effects to the EBOM to MBOM conversion method based on collaborative projects in principle.

[0170] It should be noted that in this application, relational terms such as "first" and "second" are used merely to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes the element.

[0171] The above are merely specific embodiments of this application, enabling those skilled in the art to understand or implement this application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of this application. Therefore, this application is not to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features claimed herein.

Claims

1. A method for converting EBOM to MBOM based on collaborative projects, characterized in that, The method includes the following steps: The first working end builds the EBOM based on the corresponding first encoding rule; The second working end performs internal transcoding based on the EBOM to generate second-end component coding information; The second working end adds corresponding process route information and effective time information based on the component coding information of the second end; The second working end generates the corresponding MBOM based on the component coding information of the second end, the process route information, and the effective time information; The second working end performs internal transcoding based on the EBOM to generate the second-end component coding information, including the following steps: The second working end performs internal transcoding based on the EBOM to generate material component codes, component names, and change tags that conform to the corresponding second encoding rules; Based on the corresponding drawing information in the first working terminal, internal conversion is performed to generate the corresponding drawing number and drawing number mark; Based on the material component code, the component name, the change mark, the drawing number, and the drawing number mark, generate the corresponding second-end component code information; The method further includes the following steps: The second working terminal establishes a correspondence between the component coding information of the second terminal and the component coding information of the first terminal, generates a correspondence table, and feeds it back to the first working terminal; wherein, The first end component coding information includes the material component code, component name, change mark, drawing number and drawing number mark corresponding to the first working end.

2. The EBOM to MBOM conversion method based on collaborative projects as described in claim 1, characterized in that, The method further includes the following steps: When the EBOM undergoes design changes, the corresponding EBOM change information is obtained; Based on the EBOM change information and the corresponding relationship table, the MBOM is changed synchronously.

3. The EBOM to MBOM conversion method based on collaborative projects as described in claim 1, characterized in that, The first working end builds the EBOM based on the corresponding first encoding rule, including the following steps: The first working end builds the upper-level structure data of the EBOM based on the corresponding first encoding rule, and then generates the EBOM with the drawing information.

4. A device for converting EBOM to MBOM based on collaborative projects, characterized in that, The device includes: The EBOM building module is used to control the first working end to build the EBOM based on the corresponding first encoding rule. An internal transcoding module is used to control the second working end to perform internal transcoding based on the EBOM to generate component coding information for the second end. The information addition module is used to control the second working end to add corresponding process route information and effective time information based on the component coding information of the second end; The MBOM generation module controls the second working end to generate the corresponding MBOM based on the component coding information of the second end, the process route information, and the effective time information. The device further includes: The internal transcoding module is also used to control the second working end to perform internal transcoding based on the EBOM to generate material component codes, component names and change marks that conform to the corresponding second encoding rules; The internal transcoding module is also used to perform internal conversion based on the corresponding drawing information in the first working terminal to generate the corresponding drawing number and drawing number mark. The internal transcoding module is also used to generate corresponding second-end component code information based on the material component code, the component name, the change mark, the drawing number, and the drawing number mark; The device further includes: The relationship table establishment module is used to control the second working end to establish a correspondence between the component coding information of the second end and the component coding information of the first end of the first working end, generate a correspondence table, and feed it back to the first working end; wherein, The first end component coding information includes the material component code, component name, change mark, drawing number and drawing number mark corresponding to the first working end.

5. The EBOM to MBOM conversion device based on collaborative projects as described in claim 4, characterized in that, The device further includes: The information synchronization module is used to obtain the corresponding EBOM change information when the EBOM undergoes design changes; The information synchronization module is also used to synchronize the changes to the MBOM based on the EBOM change information and the corresponding relationship table.

6. The EBOM to MBOM conversion device based on collaborative projects as described in claim 4, characterized in that, The device further includes: The EBOM building module is also used by the first working end to build the upper-level structure data of the EBOM based on the corresponding first encoding rule, thereby generating an EBOM with the drawing information.

Images