Tree-based complex electronic equipment BOM comparison method

Abstract

The invention belongs to the field of digital research, development and manufacturing, and particularly relates to a tree-based complex electronic equipment BOM comparison method, which designs tree structure storage and display of a BOM (Bill of Material), monitors and compares the change of the BOM on the basis of a tree path of each material, and monitors design files of different hierarchies in combination with the characteristics of complex electronic equipment, so as to improve the design efficiency of the complex electronic equipment. And finally, reflecting a comparison result on the BOM tree structure layer by layer and object by object, and performing clear and effective display.

Description

Technical Field

[0001] The invention belongs to the field of digital research and development and manufacturing, and in particular relates to a tree-based complex electronic equipment BOM comparison method. Background Art

[0002] In the field of R&D and manufacturing of complex electronic equipment, BOM (Bill of Materials) is a summary of design and R&D results and a basis for guiding subsequent procurement, process, manufacturing, quality, and after-sales. It occupies a key position in the business flow of manufacturing enterprises and runs through the data flow of the enterprise's business.

[0003] During the research and trial production stage, product equipment is often in rapid iteration of design. At the same time, in order to ensure the progress of trial production, some key materials with long procurement cycles are also purchased simultaneously. At this time, the design changes must be able to be intuitively reflected in the BOM, so as to directly discover the wrong change behavior and avoid the situation of over-purchase and missed purchase caused by repeated changes. The impact of BOM changes will also be transmitted to all links of the enterprise. It is particularly important for an enterprise to grasp the changes in BOM at any time and avoid the negative impact of BOM changes. The demand for BOM comparison has been around for a long time. The solution is to realize the difference in the text of two BOM lists through the Excel list comparison and duplication check function. The comparison items are limited by the organization form of the text on the list, and the comparison ability is weak, which cannot accurately reflect the differences; there is also a configuration comparison function provided by Siemens' mature product data management tool Teamcenter - compare the differences in the quantity of materials between two versions of BOM, and give a summary of the difference results, which cannot accurately reflect the comparison of each level. In the scenario of complex electronic equipment, BOM can only reflect the use of materials, but not the changes in design files, and cannot give intuitive feedback to the design end. Summary of the invention

[0004] In view of this, the present invention provides a tree-based BOM comparison method for complex electronic equipment, designs a tree structure storage and display of the BOM (bill of materials), and monitors and compares the changes in the BOM based on the tree path of each material. At the same time, combined with the characteristics of complex electronic equipment, design files at different levels are monitored. Finally, the comparison results are reflected layer by layer and object by object in the BOM tree structure for clear and effective display.

[0005] The technical solution of the present invention is:

[0006] A tree-based BOM comparison method for complex electronic equipment is used to compare BOM item additions, deletions, status changes, version changes, quantity changes, and version changes of design files. The comparison method includes the following steps:

[0007] S101: Process each version of the bill of materials through the parent-child relationship and convert it into a tree list;

[0008] S102: During the processing and conversion process, a structural path is generated for each node in each bill of materials. The structural path is generated by combining all node names of the material from the starting node to the current node and the relative order of the current level;

[0009] S103: Using the structure path of each material as the unique identifier of the material;

[0010] S104: When comparing two versions of bills of materials, determine whether the material exists, whether the material is added, deleted, or the property is modified based on comparing the unique identifier of the same material in the two bills of materials.

[0011] Furthermore, in S104, the method for determining whether attribute modification occurs is: when the unique identifiers of the same material in two versions are consistent, determining whether the quantity, status, version and document attachments of the two materials are consistent.

[0012] Furthermore, in S104, the method based on comparing the unique identifier of the same material in the two bills of materials is:

[0013] First, compare the existence of each node. If it exists, compare the properties of each node. The comparison results are divided into newly added data, deleted data, and modified data.

[0014] When using the first bill of materials to compare with the second bill of materials, if there is a unique identification code in the first bill of materials that does not appear in the second bill of materials, the data is placed in the newly added data class; if there is a unique identification code in the second bill of materials that does not appear in the first bill of materials, the data is placed in the deleted data class; if the unique identification code exists in both the first bill of materials and the second bill of materials, the attribute differences of the two data are compared and recorded one by one, and finally the difference information is placed in the modified data class; after the comparison results are matched and mounted in the tree structure, they are handed over to the application front end for display.

[0015] Furthermore, after S104, S105 is also included:

[0016] After the comparison object and the compared object are compared, the comparison result is mapped to the structural path of the comparison object.

[0017] Furthermore, the comparison method is implemented based on a comparison module;

[0018] In the comparison module, when the user initiates a comparison instruction of two bills of materials to the comparison module;

[0019] The comparison module queries the two bills of materials respectively, reads the components of the two bills of materials from the database, establishes a parent-child relationship between the two bills of materials, and encapsulates the two bills of materials into a tree data structure according to the parent-child relationship;

[0020] The comparison module generates unique identification codes for all materials from top to bottom in a tree data structure;

[0021] The comparison module compares the presence or absence of each node according to the unique identification code, and then compares the attribute differences of the same material. The comparison results are put into the newly added data, deleted data and modified data by category.

[0022] Furthermore, the comparison module maps the comparison structure to a corresponding tree structure;

[0023] The comparison module returns the tree data structure from its own backend to the display interface, and the display interface displays the bill of materials according to the tree structure, and renders the page according to the display effect of the comparison result between the two bills of materials.

[0024] Furthermore, the identification code format of the unique identifier is: #{top-level material}({relative position sequence number of the same material under the same node})#{second-level material}({relative position sequence number of the same material under the same node})#...#{current material}({relative position sequence number of the same material under the same node}).

[0025] Furthermore, the tree data structure has the following properties:

[0026] BOM parent item number: father_part

[0027] Parent state: father_part_state

[0028] BOM parent name: father_name

[0029] Parent version: father_part_version

[0030] Parent edition: father_part_edition

[0031] BOM child item drawing number: child_part

[0032] Child state: child_part_state

[0033] BOM child name: child_name

[0034] Child version: child_part_version

[0035] Child Part Edition: child_part_edition

[0036] Number of structures: amount

[0037] {Extendable fields}: ...

[0038] Attachment name: part_doc

[0039] Attachment version: part_doc_version

[0040] Attachment status: part_doc_state

[0041] {Extendable fields}: ...

[0042] Tree path: part_path

[0043] BOM new list: add_list

[0044] BOM deletion list: del_list

[0045] BOM modification list: change_list

[0046] Among them, father_part and child_part use the material code to build a tree structure; child_part_state is used to identify the status of the current level; child_part_version and edition are used to identify the version and edition of the current level; amount is used to identify the quantity of the material used at the current level; part_doc is used to identify the design file name of the current level; part_doc_version is used to identify the design file version of the current level; part_doc_state is used to identify the design file status of the current level; part_path is used to indicate the unique path of the current material in the BOM.

[0047] Beneficial Effects of the Invention

[0048] The present invention implements a tree-based BOM comparison method by design, and establishes a fine-grained comparison mechanism for complex electronic equipment BOMs. By designing the tree data structure of the BOM, the storage, attribute expansion, unique identification positioning and display support of the BOM are realized; the BOM comparison algorithm is designed, and with the support of unique identification positioning and tree data extensible attributes, it supports the addition and deletion of BOM items, status changes, version changes, quantity changes, and version changes of design files, and can make fine-grained and customizable comparisons of BOM data. The visualization of the tree structure and the comparison structure is realized by the application front end, which improves the overall ease of use. BRIEF DESCRIPTION OF THE DRAWINGS

[0049] In order to more clearly illustrate the technical solutions of the embodiments of the present disclosure, 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 disclosure. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0050] Figure 1 A tree relationship diagram of a specific implementation mode of the present invention;

[0051] Figure 2 The application architecture diagram that carries the BOM comparison method is presented;

[0052] Figure 3 A workflow diagram of the tree-based BOM comparison method for complex electronic equipment is presented. DETAILED DESCRIPTION

[0053] The embodiments of the present disclosure are described in detail below with reference to the accompanying drawings.

[0054] The following describes the embodiments of the present disclosure through specific examples, and those skilled in the art can easily understand other advantages and effects of the present disclosure from the contents disclosed in this specification. Obviously, the described embodiments are only a part of the embodiments of the present disclosure, rather than all of the embodiments. The present disclosure can also be implemented or applied through other different specific embodiments, and the details in this specification can also be modified or changed in various ways based on different viewpoints and applications without departing from the spirit of the present disclosure. It should be noted that the following embodiments and features in the embodiments can be combined with each other without conflict. Based on the embodiments in the present disclosure, all other embodiments obtained by ordinary technicians in the field without making creative work are within the scope of protection of the present disclosure.

[0055] It should be noted that various aspects of the embodiments within the scope of the appended claims are described below. It should be apparent that the aspects described herein can be embodied in a wide variety of forms, and any specific structure and / or function described herein is merely illustrative. Based on the present disclosure, it should be understood by those skilled in the art that an aspect described herein can be implemented independently of any other aspect, and two or more of these aspects can be combined in various ways. For example, any number of aspects described herein can be used to implement the device and / or practice the method. In addition, other structures and / or functionalities other than one or more of the aspects described herein can be used to implement this device and / or practice this method.

[0056] It should also be noted that the illustrations provided in the following embodiments are only schematic illustrations of the basic concept of the present disclosure. The illustrations only show components related to the present disclosure rather than being drawn according to the number, shape and size of components in actual implementation. In actual implementation, the type, quantity and proportion of each component may be changed arbitrarily, and the component layout may also be more complicated.

[0057] Additionally, in the following description, specific details are provided to facilitate a thorough understanding of the examples. However, it will be understood by those skilled in the art that the aspects described may be practiced without these specific details.

[0058] In order to solve the problem of effective monitoring of changes in BOM (Bill of Materials) and design files loaded on BOM during the scientific research and trial production stage of complex electronic equipment, it is possible to reflect the changes in BOM and design files at each level, such as item addition, deletion, status change, version change, quantity change, and version change of design files, and to display them clearly and explicitly in a tree structure, feed back the changes to the design, and provide guidance for subsequent procurement. To this end, this embodiment designs the tree structure storage and display of BOM, based on the tree path of each material, to monitor and compare changes in BOM, and at the same time, combined with the characteristics of complex electronic equipment, monitor design files at different levels, and finally reflect the comparison results layer by layer and object by object on the BOM tree structure for clear and effective display.

[0059] In one embodiment of the present invention, a tree-based BOM comparison method for complex electronic equipment is provided to compare BOM item additions, deletions, status changes, version changes, quantity changes, and version changes of design files. The comparison method comprises the following steps:

[0060] S101: Process each version of the bill of materials through the parent-child relationship and convert it into a tree list;

[0061] S102: During the processing and conversion process, a structural path is generated for each node in each bill of materials. The structural path is generated by combining all node names of the material from the starting node to the current node and the relative order of the current level;

[0062] S103: Using the structure path of each material as the unique identifier of the material;

[0063] S104: When comparing two versions of bills of materials, determine whether the material exists, whether the material is added, deleted, or the property is modified based on comparing the unique identifier of the same material in the two bills of materials.

[0064] In this embodiment, in S104, the method for determining whether attribute modification occurs is: when the unique identifiers of the same material in two versions are consistent, determining whether the quantity, status, version and document attachments of the two materials are consistent.

[0065] In this embodiment, in S104, the method based on comparing the unique identifier of the same material in the two bills of materials is:

[0066] First, compare the existence of each node. If it exists, compare the properties of each node. The comparison results are divided into newly added data, deleted data, and modified data.

[0067] When using the first bill of materials to compare with the second bill of materials, if there is a unique identification code in the first bill of materials that does not appear in the second bill of materials, the data is placed in the newly added data class; if there is a unique identification code in the second bill of materials that does not appear in the first bill of materials, the data is placed in the deleted data class; if the unique identification code exists in both the first bill of materials and the second bill of materials, the attribute differences of the two data are compared and recorded one by one, and finally the difference information is placed in the modified data class; after the comparison results are matched and mounted in the tree structure, they are handed over to the application front end for display.

[0068] In this embodiment, after S104, S105 is also included:

[0069] After the comparison object and the compared object are compared, the comparison result is mapped to the structural path of the comparison object.

[0070] In this embodiment, the comparison method is implemented based on the comparison module;

[0071] In the comparison module, when the user initiates a comparison instruction of two bills of materials to the comparison module;

[0072] The comparison module queries the two bills of materials respectively, reads the components of the two bills of materials from the database, establishes a parent-child relationship between the two bills of materials, and encapsulates the two bills of materials into a tree data structure according to the parent-child relationship;

[0073] The comparison module generates unique identification codes for all materials from top to bottom in a tree data structure;

[0074] The comparison module compares the presence or absence of each node according to the unique identification code, and then compares the attribute differences of the same material. The comparison results are put into the newly added data, deleted data and modified data by category.

[0075] In this embodiment, the comparison module maps the comparison structure to the corresponding tree structure;

[0076] The comparison module returns the tree data structure from its own backend to the display interface, and the display interface displays the bill of materials according to the tree structure, and renders the page according to the display effect of the comparison result between the two bills of materials.

[0077] In this embodiment, the identification code format of the unique identifier is: #{top-level material}({relative position sequence number of the same material under the same node})#{second-level material}({relative position sequence number of the same material under the same node})#...#{current material}({relative position sequence number of the same material under the same node}).

[0078] In this embodiment, the tree data structure has the following attributes: BOM parent item drawing number: father_part

[0079] Parent state: father_part_state

[0080] BOM parent name: father_name

[0081] Parent version: father_part_version

[0082] Parent edition: father_part_edition

[0083] BOM child item drawing number: child_part

[0084] Child state: child_part_state

[0085] BOM child name: child_name

[0086] Child version: child_part_version

[0087] Child Part Edition: child_part_edition

[0088] Number of structures: amount

[0089] {Extendable fields}: ...

[0090] Attachment name: part_doc

[0091] Attachment version: part_doc_version

[0092] Attachment status: part_doc_state

[0093] {Extendable fields}: ...

[0094] Tree path: part_path

[0095] BOM new list: add_list

[0096] BOM deletion list: del_list

[0097] BOM modification list: change_list

[0098] Among them, father_part and child_part use the material code to build a tree structure; child_part_state is used to identify the status of the current level; child_part_version and edition are used to identify the version and edition of the current level; amount is used to identify the quantity of the material used at the current level; part_doc is used to identify the design file name of the current level; part_doc_version is used to identify the design file version of the current level; part_doc_state is used to identify the design file status of the current level; part_path is used to indicate the unique path of the current material in the BOM.

[0099] The present invention designs a tree structure of BOM for storage, comparison and display of BOM, and designs a BOM comparison algorithm for comparing additions and deletions of BOM items, status changes, version changes, quantity changes, and version changes of design files. In terms of technical architecture, the design includes an application front-end and a back-end. The back-end is responsible for the implementation of the above-mentioned tree structure and comparison algorithm, and the front-end is responsible for the display of the tree structure and comparison structure.

[0100] The tree structure designed in this invention is to achieve storage, comparison and display. The tree structure is as follows: BOM parent item drawing number: father_part

[0101] Parent state: father_part_state

[0102] BOM parent name: father_name

[0103] Parent version: father_part_version

[0104] Parent edition: father_part_edition

[0105] BOM child item drawing number: child_part

[0106] Child state: child_part_state

[0107] BOM child name: child_name

[0108] Child version: child_part_version

[0109] Child Part Edition: child_part_edition

[0110] Number of structures: amount

[0111] {Extendable fields}: ...

[0112] Attachment name: part_doc

[0113] Attachment version: part_doc_version

[0114] Attachment status: part_doc_state

[0115] {Extendable fields}: ...

[0116] Tree path: part_path

[0117] BOM new list: add_list

[0118] BOM deletion list: del_list

[0119] BOM modification list: change_list

[0120] Among them, father_part and child_part use the material code to build a tree structure, child_part_state (to identify the state of the current level), child_part_version, edition (to identify the version and edition of the current level), amount (to identify the number of materials used at the current level), part_doc (to identify the design file name of the current level), part_doc_version (to identify the design file version of the current level), part_doc_state (to identify the design file state of the current level), and part_path (to indicate the unique path of the current material in the BOM). The construction method of part_path is as follows:

[0121] If there are materials A, B, and C, where A and B are in a parent-child relationship, B and C are in a parent-child relationship, and material C is built twice under material B, namely C(1) and C(2), then the tree relationship is as follows: Figure 1 shown.

[0122] The part_path of C is #A(1)#B(1)#C(1) and #A(1)#B(1)#C(2), and the part_path of E is #A(1)#B(1)#E(1), where the pound sign plus the letter represents the material drawing number, and the number in brackets represents the relative position of the material under the current parent node and in the same drawing number. Therefore, part_path can uniquely identify the unique position of any material in the BOM, and realize the tracking of each material in the BOM for subsequent comparison.

[0123] The BOM comparison algorithm designed by the present invention is based on the BOM tree structure. First, the existence of each node is compared, and then the attributes of each node (such as status, quantity, version, attachment version, status) are compared. The comparison results are divided into three categories: new data, deleted data, and modified data. When BOM B1 is used to compare BOM B2, if part_path exists in B1 but does not appear in B2, the data is placed in the new data class; if part_path exists in B2 but does not appear in B1, the data is placed in the deleted data class; if part_path exists in both B1 and B2, the attribute differences of the two data are compared and recorded one by one, and finally the difference information is placed in the modified data class. After the comparison result is matched and mounted to the BOM tree structure, it is handed over to the application front end for display, in which the new data is marked in green, the deleted data is marked in line, and the modified data is marked in light red.

[0124] The properties of the tree data structure BOM comparison are shown in Table 1

[0125] Table 1: Properties of tree data structure BOM comparison

[0126]

[0127]

[0128] In order to make the purpose, technical solution and advantages of the embodiments of the present invention clearer, the technical solution in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are 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.

[0129] The system architecture implemented by the present invention is as follows Figure 2As shown, the present invention designs a tree data structure of BOM; the storage and display of BOM basic data and superior-subordinate relationships are realized through basic fields, the customization requirements of complex electronic equipment are met through expandable fields, and each material of BOM is located and marked by designing a unique identification path. On the basis of the tree data structure of BOM, the present invention then designs a BOM comparison algorithm, which, with the support of unique identification positioning and tree data expandable attributes, supports the addition and deletion of BOM items, status changes, version changes, quantity changes, and version changes of design files, and can make fine-grained and customizable comparisons of BOM data. The visualization of the tree structure and the comparison structure is realized through the application front end, which improves the overall ease of use.

[0130] Workflow of tree-based BOM comparison method for complex electronic equipment Figure 3 As shown:

[0131] The first step is for the user to initiate a BOM comparison request, which needs to specify the two BOMs that need to be compared.

[0132] The second step is to query the two specified BOMs respectively, read their BOM components from the database, and encapsulate them into a tree data structure according to the parent-child relationship. ;

[0133] The third step is to generate a unique identification code for the material from top to bottom according to the BOM. The format of the identification code is as follows: #{top material}({relative position sequence number of the same material under the same node})#{second-level material}({relative position sequence number of the same material under the same node})#...#{current material}({relative position sequence number of the same material under the same node});

[0134] The fourth step is to compare the existence of each node based on the unique identification code, and then to compare the properties of each node (such as status, quantity, version, attachment version, status), and put the comparison results into the categories of newly added data, deleted data, and modified data;

[0135] The fifth step is to map the contrast structure to the corresponding tree structure;

[0136] The sixth step is to return the tree data structure from the back end to the front end. The front end displays the BOM according to the tree structure and renders the page according to the BOM difference display effect.

[0137] The above is only a specific implementation of the present disclosure, but the protection scope of the present disclosure is not limited thereto. Any changes or substitutions that can be easily thought of by a person skilled in the art within the technical scope disclosed in the present disclosure should be included in the protection scope of the present disclosure. Therefore, the protection scope of the present disclosure should be based on the protection scope of the claims.

Claims

1. A tree-based BOM comparison method for complex electronic equipment, characterized in that: For comparing BOM item additions and deletions, status changes, version changes, quantity changes, and version changes of design files, the comparison method includes the following steps: S101: Process each version of the bill of materials through the parent-child relationship and convert it into a tree list; S102: During the processing and conversion process, a structural path is generated for each node in each bill of materials. The structural path is generated by combining all node names of the material from the starting node to the current node and the relative order of the current level; S103: Using the structure path of each material as the unique identifier of the material; S104: When comparing two versions of bills of materials, determine whether the material exists, whether the material is added, deleted, or the property is modified based on comparing the unique identifier of the same material in the two bills of materials.

2. The tree-based complex electronic equipment BOM comparison method according to claim 1, characterized in that: In S104, the method for determining whether attribute modification occurs is: when the unique identifiers of the same material in two versions are consistent, determining whether the quantity, status, version and document attachments of the two materials are consistent.

3. The tree-based complex electronic equipment BOM comparison method according to claim 2, characterized in that: In S104, the method based on comparing the unique identifier of the same material in the two bills of materials is: First, compare the existence of each node. If it exists, compare the properties of each node. The comparison results are divided into newly added data, deleted data, and modified data. When comparing the first bill of materials with the second bill of materials, if the first bill of materials has a unique identification code that does not appear in the second bill of materials, the data is placed in the newly added data category; if the second bill of materials has a unique identification code that does not appear in the first bill of materials, the data is placed in the deleted data category; If the unique identification code exists in both the first bill of materials and the second bill of materials, the attribute differences between the two data are compared and recorded one by one, and finally the difference information is put into the modified data class; After the comparison results are matched and mounted into a tree structure, they are handed over to the application front end for display.

4. The tree-based complex electronic equipment BOM comparison method according to claim 3, characterized in that: The S104 further includes S105: After the comparison object and the compared object are compared, the comparison result is mapped to the structural path of the comparison object.

5. The tree-based complex electronic equipment BOM comparison method according to claim 4, characterized in that: The comparison method is implemented based on the comparison module; In the comparison module, when the user initiates a comparison instruction of two bills of materials to the comparison module; The comparison module queries the two bills of materials respectively, reads the components of the two bills of materials from the database, establishes a parent-child relationship between the two bills of materials, and encapsulates the two bills of materials into a tree data structure according to the parent-child relationship; The comparison module generates unique identification codes for all materials from top to bottom in a tree data structure; The comparison module compares the presence or absence of each node according to the unique identification code, and then compares the attribute differences of the same material. The comparison results are put into the newly added data, deleted data and modified data by category.

6. The tree-based complex electronic equipment BOM comparison method according to claim 5, characterized in that: The comparison module maps the comparison structure to the corresponding tree structure; The comparison module returns the tree data structure from its own backend to the display interface, and the display interface displays the bill of materials according to the tree structure, and renders the page according to the display effect of the comparison result between the two bills of materials.

7. The tree-based complex electronic equipment BOM comparison method according to claim 6, characterized in that: The identification code format of the unique identifier is: #{top-level material}({relative position sequence number of the same material under the same node})#{second-level material}({relative position sequence number of the same material under the same node})#...#{current material}({relative position sequence number of the same material under the same node}).

8. The tree-based complex electronic equipment BOM comparison method according to claim 7, characterized in that: The tree data structure has the following properties: BOM parent item number: father_part Parent state: father_part_state BOM parent item name: father_name Parent item version: father_part_version Parent edition: father_part_edition BOM child item drawing number: child_part Child item state: child_part_state BOM child item name: child_name Child item version: child_part_version Child item edition: child_part_edition Structure quantity: amount {Extendable fields}: ... Attachment name: part_doc Attachment version: part_doc_version Attachment status: part_doc_state {Extendable fields}: ... Tree path: part_path BOM new list: add_list BOM deletion list: del_list BOM modification list: change_list Among them, father_part and child_part use the material code to build a tree structure; child_part_state is used to identify the status of the current level; child_part_version and edition are used to identify the version and edition of the current level; amount is used to identify the quantity of the material used at the current level; part_doc is used to identify the design file name of the current level; part_doc_version is used to identify the design file version of the current level; part_doc_state is used to identify the design file status of the current level; part_path is used to indicate the unique path of the current material in the BOM.

Images