BOM Data Conversion Management Method

Abstract

The invention discloses a BOM data conversion management method, which creates an initial BOM data structure according to BOM data, and the initial BOM data structure includes: node number information of each node, description information of the node number, node group information to which each node belongs, description information of the node group, and parent node number information of each node; the node is a modular component. According to the created initial BOM data structure, multi-layer configurable modular data is released in a multi-layer configurable and multi-flattened manner to convert the initial BOM data structure into a target BOM data structure; the target BOM data structure is a BOM structure tree; the multi-layer configurable modular data is used to describe the multi-layer configurable matrix of the modular group in the initial BOM data. Then, the production data is released in a multi-layer configurable and flattened manner, and when it is converted to the formal BOM, the system automatically converts it into a traditional BOM structure and effectively supports downstream production and manufacturing.

Description

Technical Field

[0001] The present invention relates to the automotive field, and in particular to a BOM data conversion management method. Background Art

[0002] The traditional BOM data structure mainly manages the purchased or self-made parts used in the assembly line in a flat BOM, and the head parts are reflected by the parent-child relationship. This traditional BOM management method has a big disadvantage, that is, when the modular head parts involve more functions, the number of modular head part numbers will increase exponentially, and engineers are prone to errors when publishing data. A large number of part numbers are required when engineering changes occur, and sometimes the intersection of multiple sub-parts will make the system impossible to implement. With the diversification of automobile companies' manufacturing models and the promotion of platform-based vehicle design models, the traditional BOM data structure can no longer efficiently support the release of engineering data and downstream production and manufacturing. In order to better meet the business development needs of enterprises, a new BOM management method is urgently needed to solve the business needs of multi-factory and multi-process flexibility.

[0003] Therefore, the data structure of the BOM in the prior art is inconvenient to use. Summary of the invention

[0004] The purpose of the present invention is to solve the problem that the BOM data structure in the prior art is inconvenient to use. The present invention provides a BOM data conversion management method, which has the advantage of being easy to use.

[0005] To solve the above problems, an embodiment of the present invention provides a BOM data conversion management method, which creates an initial BOM data structure according to BOM data, wherein the initial BOM data structure includes: node number information of each node, description information of the node number, node group information to which each node belongs, description information of the node group, and parent node number information of each node; the node is a modular component;

[0006] According to the created initial BOM data structure, multi-layer configurable modular data is published in a multi-layer configurable and multi-flattened manner to convert the initial BOM data structure into a target BOM data structure; the target BOM data structure is a BOM structure tree; the multi-layer configurable modular data is used to describe a multi-layer configurable matrix of modular groups in the initial BOM data.

[0007] By adopting the above technical solution, the BOM data conversion management method in this embodiment can publish production data in a multi-layer configurable flat manner in the initial BOM. When converted to the formal BOM, the system automatically converts it into the traditional BOM structure and effectively supports downstream production and manufacturing.

[0008] Another embodiment of the present invention provides a BOM data conversion management method, which creates an initial BOM data structure based on BOM data, including creating a node tree structure; and creating the node tree structure includes: creating node layers of the node tree structure and nodes within each node layer based on characteristic information of parts and components, and creating parent-child relationships between each node; the characteristic information includes functional structural relationships and business requirements of different products and version years.

[0009] Another embodiment of the present invention provides a BOM data conversion management method, including:

[0010] According to the functional structure relationship, the whole vehicle is defined as the first-layer node of the node tree; the first three layers of SVPPS are defined as the second-layer node, the third-layer node and the fourth-layer node of the node tree respectively;

[0011] The node structure of the node tree below the fourth level is created according to the business requirements of the different products and version years.

[0012] Another embodiment of the present invention provides a BOM data conversion management method, further comprising creating the node number information for each node in the node tree structure:

[0013] Define the node number of the first layer node as 0;

[0014] The second-layer nodes are defined as node groups, and the node numbers of the second-layer nodes are represented by letters;

[0015] The numbering of nodes below the second-layer node in the node layer is defined by numbers;

[0016] The node numbers of the third-layer node group and the node groups below it are composed of the node number of the node's parent node and the number of the node in the node layer to which it belongs.

[0017] Another embodiment of the present invention provides a BOM data conversion management method, wherein the node number of the node is expressed in a multi-level structure, and a distinguishing symbol for distinguishing the levels is formed between each level; the node number of the node is expressed in that the first character is the node group information.

[0018] Another embodiment of the present invention provides a BOM data conversion management method, which, after publishing all modular data in a multi-layer configurable and multi-flattened manner, also includes: confirming whether all relevant fields of the published data are valid and complete.

[0019] Another embodiment of the present invention provides a BOM data conversion management method, wherein the initial BOM data structure is a multi-layer configurable data structure obtained by performing hierarchical node processing on data in the BOM data.

[0020] Another embodiment of the present invention provides a BOM data conversion management method.

[0021] The multi-layer configurable matrix I is In=(C1, C2, C3, C4), where:

[0022] C1=(P1,P2,…P n );

[0023] C2=(G1,G2,…G n );

[0024] C3=(N1,N2,…N n );

[0025] C4=(U1,U2,…U n );

[0026] C1 represents a set of part numbers in the multi-layer configurable matrix, wherein Px represents any element of C1, and Px is a part number from the enterprise part number base library;

[0027] C2 represents a set of node groups in the multi-layer configurable matrix;

[0028] C3 represents a set of node numbers in the multi-layer configurable matrix;

[0029] C4 represents the set of UCstring in the multi-layer configurable module matrix, where each element Ux is a logical operator of a specific part row function.

[0030] Another embodiment of the present invention provides a BOM data conversion management method, wherein the part number includes the part number of the module assembly and the part number of the module sub-component.

[0031] Another embodiment of the present invention provides a BOM data conversion management method, wherein the same module is the same modular group, and any element Gx in the same modular group is the same code.

[0032] Another embodiment of the present invention provides a BOM data conversion management method, Ux=M&Oc1&Oc2&Oc3&…&Ocn, where M is Model and Oc x is different Feature Codes.

[0033] Another embodiment of the present invention provides a BOM data conversion management method, wherein the UCstrings of a parent and child parts in the same node group are respectively:

[0034] U 父 =M1&C1&C2&C3&……&C n

[0035] U 子1 =M1&C1&C2&C3

[0036] U 子2 =M2&C1&C2&C3

[0037] U 子3 =M1&C1'&C2&C3

[0038] The corresponding part numbers are P 父 , P 子1 , P 子2 , P 子3 .

[0039] Beneficial effects of the present invention:

[0040] The BOM data conversion management method in the present invention is a new multi-layer configurable flat BOM technology and implementation method, which can support complex businesses such as modular development and multi-factory flexible manufacturing, greatly reduce the amount of data released by the project and simplify the difficulty of engineering changes, improve the efficiency and accuracy of BOM data release, shorten the project data release cycle, and reduce human resource investment. BRIEF DESCRIPTION OF THE DRAWINGS

[0041] Figure 1 A flowchart of a BOM data conversion management method provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0042] The following specific embodiments illustrate the implementation of the present invention, and those skilled in the art can easily understand other advantages and effects of the present invention from the contents disclosed in this specification. Although the description of the present invention will be introduced in conjunction with the preferred embodiment, this does not mean that the features of this invention are limited to this implementation. On the contrary, the purpose of introducing the invention in conjunction with the implementation is to cover other options or modifications that may extend based on the claims of the present invention. In order to provide a deep understanding of the present invention, the following description will include many specific details. The present invention can also be implemented without using these details. In addition, in order to avoid confusion or blurring the focus of the present invention, some specific details will be omitted in the description. It should be noted that the embodiments of the present invention and the features in the embodiments can be combined with each other without conflict.

[0043] It should be noted that in this specification, similar reference numerals and letters denote similar items in the following drawings, and therefore, once an item is defined in one drawing, it does not need to be further defined and explained in the subsequent drawings.

[0044] The technical solution of the present invention will be described clearly and completely below in conjunction with the accompanying drawings. 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.

[0045] In the description of the present invention, it should be noted that the terms "center", "upper", "lower", "left", "right", "vertical", "horizontal", "inner", "outer", etc., indicating the orientation or positional relationship, are based on the orientation or positional relationship shown in the drawings, and are only for the convenience of describing the present invention and simplifying the description, rather than indicating or implying that the device or element referred to must have a specific orientation, be constructed and operated in a specific orientation, and therefore cannot be understood as limiting the present invention. In addition, the terms "first", "second", and "third" are used for descriptive purposes only, and cannot be understood as indicating or implying relative importance.

[0046] In the description of the present invention, it should be noted that, unless otherwise clearly specified and limited, the terms "installed", "connected", and "connected" should be understood in a broad sense, for example, it can be a fixed connection, a detachable connection, or an integral connection; it can be a mechanical connection or an electrical connection; it can be a direct connection, or it can be indirectly connected through an intermediate medium, or it can be the internal communication of two components. For ordinary technicians in this field, the specific meanings of the above terms in the present invention can be understood according to specific circumstances.

[0047] In order to make the objectives, technical solutions and advantages of the present invention more clear, the embodiments of the present invention will be further described in detail below with reference to the accompanying drawings.

[0048] An implementation method of this embodiment provides a BOM data conversion management method, such as Figure 1 As shown, it includes the following steps:

[0049] In step S1, an initial BOM data structure is created based on the BOM data. The initial BOM data structure includes: node number information of each node, description information of the node number, node group information to which each node belongs, description information of the node group, and parent node number information of each node; nodes are modular components.

[0050] In step S2, based on the created initial BOM data structure, multi-layer configurable modular data is published in a multi-layer configurable and multi-flattened manner to convert the initial BOM data structure into a target BOM data structure; the target BOM data structure is a BOM structure tree; the multi-layer configurable modular data is used to describe the multi-layer configurable matrix of modular groups in the initial BOM data.

[0051] More specifically, in this embodiment, the BOM data conversion management method in the embodiment can publish production data in a multi-layer configurable flat manner in the initial BOM. When converted to the formal BOM, the system automatically converts it into a traditional BOM structure and effectively supports downstream production and manufacturing.

[0052] More specifically, in this embodiment, the node number information of each node, the description information of the node number, the node group information to which each node belongs, and the description information of the node group are illustrated below.

[0053] Furthermore, another implementation of this embodiment provides a BOM data conversion management method, which creates an initial BOM data structure based on BOM data, including creating a node tree structure; and creating the node tree structure includes: creating node layers of the node tree structure and nodes within each node layer based on feature information of parts, and creating parent-child relationships between each node; the feature information includes functional structural relationships and business requirements of different products and version years.

[0054] Another implementation of this embodiment provides a BOM data conversion management method, including:

[0055] According to the functional structure relationship, the whole vehicle is defined as the first-level node of the node tree; the first three levels of SVPPS are defined as the second-level nodes, the third-level nodes and the fourth-level nodes of the node tree respectively;

[0056] Create node structures below the fourth level of the node tree based on the business requirements of different products and version years.

[0057] Another implementation of this embodiment provides a BOM data conversion management method, which also includes creating node number information for each node in the node tree structure:

[0058] Define the node number of the first layer node as 0;

[0059] The second-layer nodes are defined as node groups, and the node numbers of the second-layer nodes are represented by letters;

[0060] The numbering of nodes below the second-layer nodes in their node layer is defined by numbers;

[0061] The node number of the third-level node group and the node groups below it is composed of the node number of the node's parent node and the number of the node in its node layer.

[0062] For example, BOM data can be configured as follows:

[0063]

[0064] Another implementation of this embodiment provides a BOM data conversion management method, in which the node number of the node is expressed as a multi-level structure, and a distinguishing symbol for distinguishing the levels is formed between each level; the node number of the node is expressed in that the first character is the node group information.

[0065] Specifically, in this embodiment, the distinguishing character may be a letter or a number, which may be specifically determined according to actual design and usage requirements, and this embodiment does not limit this.

[0066] Another implementation of this embodiment provides a BOM data conversion management method, which, after publishing all modular data in a multi-layer configurable and multi-flattened manner, also includes: confirming whether all relevant fields of the published data are valid and complete.

[0067] Another implementation of this embodiment provides a BOM data conversion management method, wherein the initial BOM data structure is a multi-layer configurable data structure obtained by performing hierarchical node processing on the data in the BOM data.

[0068] Another implementation of this embodiment provides a BOM data conversion management method.

[0069] The multi-layer configurable matrix I is In=(C1, C2, C3, C4), where:

[0070] C1=(P1,P2,…P n );

[0071] C2=(G1,G2,…G n );

[0072] C3=(N1,N2,…N n );

[0073] C4=(U1,U2,…U n );

[0074] C1 represents a set of part numbers in a multi-layer configurable matrix, where Px represents any element of C1, and Px is a part number from the enterprise part number base library;

[0075] C2 represents the set of node groups in the multi-layer configurable matrix;

[0076] C3 represents the set of node numbers in the multi-layer configurable matrix;

[0077] C4 represents the set of UCstring in the multi-layer configurable module matrix, where each element Ux is a logical operator of a specific part row function.

[0078] Specifically, in this embodiment,

[0079] C1 represents the set of all part numbers in the multi-layer configurable matrix, that is, there are module assembly part numbers and module sub-component part numbers, where Px represents any element of C1, and Px is a part number from the enterprise part number base library;

[0080] C2 represents the set of node groups in the multi-layer configurable matrix. Generally, the same module is the same modular group, so any element Gx in the same modular group has the same code, for example, Gx = A (dashboard group);

[0081] C3 represents the set of node numbers in the multi-layer configurable matrix. The node number is expressed in the form of a node group number with the first character being the node group number, and each layer is distinguished by a dot. Each level is a 2-digit number, for example: Nx = A.01.01…01, where A is the node group code, A.01 is the next layer of A, and so on;

[0082] C4 represents the set of UCstring (in this article, it refers to a part number composed of automobile model, function and feature as usage conditions) in the multi-layer configurable module matrix, where each element Ux is the logical operator of the specific part row function, specifically expressed as Ux=M&Oc1&Oc2&Oc3&…&Ocn, where M is Model and Ocx is different Feature Code.

[0083] Another implementation of this embodiment provides a BOM data conversion management method, where the part number includes the part number of the module assembly and the part number of the module sub-component.

[0084] Another implementation of this embodiment provides a BOM data conversion management method, where the same module is the same modular group, and any element Gx in the same modular group is the same code.

[0085] Another implementation of this embodiment provides a BOM data conversion management method, Ux = M&Oc1&Oc2&Oc3&…&Ocn, where M is Model (referring to the vehicle model), and Oc x is different Feature Codes (referring to the part function feature code).

[0086] Another implementation of this embodiment provides a BOM data conversion management method, where the UCstrings of a parent and child parts in the same node group are:

[0087] U 父 =M1&C1&C2&C3&……&C n

[0088] U 子1 =M1&C1&C2&C3

[0089] U 子2 =M2&C1&C2&C3

[0090] U 子3 =M1&C1'&C2&C3

[0091] The corresponding part numbers are P 父 , P 子1 , P 子2 , P 子3 .

[0092] Specifically, in this embodiment, due to U 子1 The Model can be used with U 父 Match, and U 父 The Feature Code contains U 子1 All Feature Codes, so U 父 Contains U 子1 , then P 子1 P 父 sub-parts; due to U 子2 Model cannot be used with U 父 So U 父不 Contains U 子2 , then P 子2 Not P 父 Subpart of U 子3 The Model can be used with U 父 However, due to U 父 The Code in cannot contain all U 子3 All Feature Codes, so P 子3 Not P either 父 subparts of.

[0093] More specifically, in this embodiment, the multi-layer configurable data in the initial BOM is converted as follows:

[0094]

[0095] Furthermore, the BOM data conversion management method in this embodiment is a new multi-layer configurable flat BOM technology and implementation method, which can support complex businesses such as modular development and multi-factory flexible manufacturing, greatly reduce the amount of data released by the project and simplify the difficulty of engineering changes, improve the efficiency and accuracy of BOM data release, shorten the project data release cycle, and reduce human resource investment.

[0096] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit it. Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or replace some or all of the technical features therein with equivalents. However, these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present invention.

Claims

1. A BOM data conversion management method, characterized in that: include: An initial BOM data structure is created according to the BOM data, wherein the initial BOM data structure includes: node number information of each node, description information of the node number, node group information to which each node belongs, description information of the node group, and parent node number information of each node; the nodes are modular components; According to the created initial BOM data structure, multi-layer configurable modular data is published in a multi-layer configurable and multi-flattened manner to convert the initial BOM data structure into a target BOM data structure; the target BOM data structure is a BOM structure tree; the multi-layer configurable modular data is used to describe a multi-layer configurable matrix of modular groups in the initial BOM data; Creating an initial BOM data structure according to the BOM data includes creating a node tree structure; and creating the node tree structure includes: creating node layers of the node tree structure and nodes in each node layer according to feature information of parts, and creating a parent-child relationship between each node; the feature information includes a functional structure relationship and business requirements of different products and version years; The multi-layer configurable matrix I is In=(C1, C2, C3, C4), where: C1=(P1,P2,…P n );C2=(G1,G2,…G n );C3=(N1,N2,…N n );C4=(U1,U2,…U n ); C1 represents the set of part numbers in the multi-layer configurable matrix, where Px represents any element of C1, and Px is a part number from the enterprise part number base library; C2 represents the set of node groups in the multi-layer configurable matrix; C3 represents the set of node numbers in the multi-layer configurable matrix; C4 represents the set of UCstring in the multi-layer configurable matrix, where each element Ux is a logical operator of a specific part row function; Ux=M&Oc1&Oc2&Oc3&…&Ocn, where M is Model and Ocx is different Feature Codes; The UCstrings of a parent and child part in the same node group are: U 父 =M1&C1&C2&C3&……&C n ;U 子1 =M1&C1&C2&C3;U 子2 =M2&C1&C2&C3;U 子3 =M1&C1’&C2&C3; The corresponding part numbers are P 父 , P 子1 , P 子2 , P 子3 .

2. The BOM data conversion management method according to claim 1 is characterized in that: include: The entire vehicle is defined as a first-level node of the node tree according to the functional structure relationship; The first three layers of SVPPS are defined as the second layer nodes, the third layer nodes and the fourth layer nodes of the node tree respectively; The node structure of the node tree below the fourth level is created according to the business requirements of the different products and version years.

3. The BOM data conversion management method according to claim 2 is characterized in that: The method also includes creating the node number information for each node in the node tree structure: Define the node number of the first layer node as 0; The second-layer nodes are defined as node groups, and the node numbers of the second-layer nodes are represented by letters; The numbering of nodes below the second-layer node in the node layer is defined by numbers; The node numbers of the third-layer node group and the node groups below it are composed of the node number of the node's parent node and the number of the node in the node layer to which it belongs.

4. The BOM data conversion management method according to claim 3 is characterized in that: The node number of the node is expressed in a multi-level structure, and a distinguisher for distinguishing the levels is formed between the levels; the node number of the node is expressed in a way that the first character is the node group information.

5. The BOM data conversion management method according to claim 1 is characterized in that: After all modular data is published in a multi-layer configurable multi-flattened manner, it also includes: confirming whether all relevant fields of the published data are valid and complete.

6. The BOM data conversion management method according to any one of claims 1 to 4, characterized in that: The initial BOM data structure is a multi-layer configurable data structure obtained by performing hierarchical node processing on the data in the BOM data.

7. The BOM data conversion management method according to claim 1 is characterized in that: The part number includes the part number of the module assembly and the part number of the module sub-component.

8. The BOM data conversion management method according to claim 1 is characterized in that: The same module is the same modular group, and any element Gx in the same modular group is the same code.

Images