Engineering bill of material management method, device, equipment and medium

Abstract

The invention discloses an engineering bill of material management method and device, equipment and a medium. The method comprises the steps of obtaining engineering bill of material EBOM data; the EBOM data comprises system assembly data, the system assembly data comprises data of a plurality of subsystems, and each subsystem comprises a plurality of parts; performing storage primary key and attribute analysis on the EBOM data, and storing the EBOM data into a database; dividing the component data in each subsystem into modules according to a modularization rule; determining non-modular data according to the component data in the module, and performing hierarchical structure optimization on the component data and the non-modular data in the module; performing consistency and rationality verification on the optimized EBOM data to obtain a verification report; the verification report is used for managing the engineering bill of materials. According to the technical scheme, the time consumption for searching and updating the information in the multi-level structure can be reduced, so that the whole EBOM data is easy to manage and maintain, and the management efficiency of the bill of materials is improved.

Description

Technical Field

[0001] The present invention generally relates to the field of data management technology, and in particular to a method, device, equipment and medium for managing an engineering material list. Background Art

[0002] With the continuous development of the automobile manufacturing industry, the bill of material (BOM), as a technical document describing the composition of an enterprise's products, has been used throughout the entire production management process, from project establishment, R&D design, trial production, formal production and manufacturing to sales and after-sales, due to its characteristics of improving production efficiency, optimizing cost control and inventory management. Among them, in the product life cycle, different stages correspond to different BOMs, including design BOM (EBOM), process BOM (PBOM), and manufacturing BOM (MBOM). In the process of continuous updating of the automobile market, universal parts are needed to meet the needs of large-scale production, and customized configurations are needed to meet the personalized needs of consumers. This strategy of coexistence of universalization and customization leads to the complexity of the EBOM structure level. In order to improve production efficiency and optimize the product structure level, it is particularly important to manage the logarithmic product data.

[0003] At present, in the related technology, the engineering material bill is managed by utilizing product data management (PDM) and product lifecycle management (PLM). However, when the number of engineering material bills of a product is large, a lot of time is required for hierarchical structure design and type conversion processing, resulting in low management efficiency of the material bill. Summary of the invention

[0004] In view of the above-mentioned defects or deficiencies in the prior art, it is desirable to provide a method, device, equipment and medium for managing a project bill of materials.

[0005] In a first aspect, an embodiment of the present application provides a method for managing a project bill of materials, the method comprising:

[0006] Acquire engineering bill of materials (EBOM) data; the EBOM data includes system assembly data, the system assembly data includes data of multiple subsystems, and the subsystem includes multiple components;

[0007] Perform storage primary key and attribute analysis on the EBOM data, and store the EBOM data in a database;

[0008] According to modularization rules, the component data in each of the subsystems is divided into modules;

[0009] Determine non-modular data according to the component data in the module, and optimize the hierarchical structure of the component data in the module and the non-modular data;

[0010] The optimized EBOM data is verified for consistency and rationality to obtain a verification report; the verification report is used to manage the engineering material list.

[0011] In one embodiment, performing storage primary key and attribute analysis on the EBOM data and storing the EBOM data in a database includes:

[0012] Analyze the EBOM data to determine the attribute type, attribute information, primary key information and primary key type of the EBOM data;

[0013] The EBOM data is stored in a database based on the attribute type, the attribute information, the primary key information and the primary key type.

[0014] In one embodiment, according to the modularization rule, the component data in each subsystem is divided into modules, including:

[0015] Dividing the component data according to function to determine the functional class to which each component data belongs;

[0016] For each functional class in each subsystem, calculating the correlation between every two functional classes;

[0017] When the correlation is greater than a preset correlation threshold, the component data corresponding to the two functional classes are divided into the same area; the same area includes multiple regional functional classes;

[0018] For the regional function classes within the same area, calculating the design change frequency value between every two regional function classes;

[0019] When the design change frequency value is less than a preset design change frequency threshold, the component data corresponding to the two regional function classes are divided into the same module.

[0020] In one embodiment, for the functional classes in each subsystem, calculating the association degree between every two functional classes includes:

[0021] Obtaining the number of components required to implement each of the two functional classes and the number of common components required to implement the two functional classes;

[0022] The degree of association between the two functional classes is calculated according to the number of components required to implement each of the two functional classes and the number of common components.

[0023] In one embodiment, the module includes multiple levels, and the hierarchical structure optimization of the component data and the non-modular data in the module includes:

[0024] Performing hierarchical analysis on the component data in the module to determine the degree of duplication between hierarchical component data of every two levels;

[0025] When the degree of repetition is greater than a preset repetition threshold, obtaining and deleting the repetitive component data;

[0026] Calculating an index of component data in the non-modular data;

[0027] When the indicator is not greater than a preset indicator threshold, obtaining target component data and deleting it;

[0028] The subordinate component of the target component data is mounted under the parent of the target component data.

[0029] In one embodiment, the optimized EBOM data is verified for consistency and rationality to obtain a verification report, including:

[0030] Comparing the optimized EBOM data with a preset document file to obtain a comparison result;

[0031] Verifying the configuration logic relationship of the optimized EBOM data to obtain a logic verification result;

[0032] Performing dependency verification on each component data in the optimized EBOM data to obtain a dependency verification result;

[0033] A verification report is obtained according to the comparison result, the logic verification result and the dependency verification result.

[0034] In one embodiment, the configuration logic relationship verification is performed on the optimized EBOM data to obtain a logic verification result, including:

[0035] Obtain a configuration table; the configuration table is used to characterize, record and manage product configuration information, and the configuration table includes multiple configuration options;

[0036] Determine a mapping relationship between the optimized EBOM data and the configuration options in the configuration table;

[0037] According to the mapping relationship, the EBOM data and the configuration options in the configuration table are functionally matched and verified to obtain the logic verification result.

[0038] In a second aspect, the present application provides a device for managing a bill of materials for an engineering project, the device comprising:

[0039] An acquisition module is used to acquire engineering bill of materials (EBOM) data; the EBOM data includes system assembly data, the system assembly data includes data of multiple subsystems, and the subsystem includes multiple components;

[0040] A data storage module, used for performing storage primary key and attribute analysis on the EBOM data, and storing the EBOM data in a database;

[0041] A data division module, used for dividing the component data in each of the subsystems into modules according to modular rules;

[0042] A hierarchical optimization module, used for determining non-modular data according to the component data in the module, and performing hierarchical structure optimization on the component data in the module and the non-modular data;

[0043] The data verification module is used to verify the consistency and rationality of the optimized EBOM data to obtain a verification report; the verification report is used to manage the engineering material list.

[0044] In a third aspect, an embodiment of the present application provides a computer device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the program, the engineering material bill management method as described in the first aspect above is implemented.

[0045] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium having a computer program stored thereon, wherein the computer program is used to implement the engineering material bill management method as described in the first aspect above.

[0046] The engineering bill of materials management method, device, equipment and medium provided in the embodiments of the present application include: obtaining engineering bill of materials EBOM data, the EBOM data includes system assembly data, the system assembly data includes data of multiple subsystems, the subsystem includes multiple components, and performing storage primary key and attribute analysis on the EBOM data, storing the EBOM data in a database, and then dividing the component data in each subsystem into modules according to modular rules, and determining non-modular data based on the component data in the module, and optimizing the hierarchical structure of the component data and non-modular data in the module, and finally verifying the consistency and rationality of the optimized EBOM data to obtain a verification report. Compared with the existing technology, this solution can make the storage of EBOM data more regular by storing EBOM data in the database and dividing it into modular data and non-modular data according to modular rules, and optimize the hierarchical structure of modular data and non-modular data, reducing the hierarchical depth and complexity, making the entire EBOM data easy to manage and maintain, reducing the time and energy consumption of searching and updating information in the multi-level structure, and helping to more effectively realize system integration and modular design. It can also verify the consistency and rationality of the optimized EBOM data, improve the management efficiency of the bill of materials, further improve the efficiency of product design and development, and optimize the overall production and operation, improve product quality and enhance product competitiveness. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0048] Figure 1 A system architecture diagram of an application system of the engineering material bill management method provided in an embodiment of the present application;

[0049] Figure 2 A flowchart of a method for managing a bill of materials for an engineering project provided in an embodiment of the present application;

[0050] Figure 3 A flowchart of a method for dividing component data in each subsystem into modules provided in an embodiment of the present application;

[0051] Figure 4 A schematic diagram of the structure of the engineering material bill management method provided in the embodiment of the present application;

[0052] Figure 5A schematic diagram of the structure of the engineering material bill management device provided in an embodiment of the present application;

[0053] Figure 6 A schematic diagram of the structure of a computer device shown in an embodiment of the present application. DETAILED DESCRIPTION

[0054] The present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It is to be understood that the specific embodiments described herein are only used to explain the relevant invention, rather than to limit the invention. It is also necessary to explain that, for ease of description, only the parts related to the invention are shown in the accompanying drawings.

[0055] It should be noted that, in the absence of conflict, the embodiments and features in the embodiments of the present application can be combined with each other. The present application will be described in detail below with reference to the accompanying drawings and in combination with the embodiments.

[0056] As mentioned in the background technology, in the related technology, the engineering material bill is managed by utilizing product data management (PDM) and product lifecycle management (PLM). However, when the number of engineering material bills of a product is large, a lot of time is required for hierarchical structure design and type conversion processing, resulting in low management efficiency of the material bill.

[0057] Based on the above-mentioned defects, the present application provides a method, device, equipment and medium for managing an engineering bill of materials. Compared with the prior art, this solution stores the EBOM data in a database and divides it into modular data and non-modular data according to modular rules, so that the storage of EBOM data can be more regular, and the hierarchical structure of modular data and non-modular data is optimized, reducing the hierarchical depth and complexity, making the entire EBOM data easy to manage and maintain, reducing the time and energy consumption for searching and updating information in a multi-level structure, and helping to more effectively realize system integration and modular design. It can also verify the consistency and rationality of the optimized EBOM data, thereby improving the management efficiency of the bill of materials, further improving the efficiency of product design and development, and optimizing the overall production and operation, improving product quality and enhancing product competitiveness.

[0058] Figure 1 This is an implementation environment architecture diagram of an engineering material bill management method provided in an embodiment of the present application. Figure 1 As shown, the implementation environment architecture includes: a computer device, which may include a terminal 100 and a server 200.

[0059] The terminal 100 may be a terminal device in various AI application scenarios. For example, the terminal 100 may be a smart home device such as a smart TV or a smart TV set-top box, or the terminal 100 may be a mobile portable terminal such as a smart phone, a tablet computer, and an e-book reader, or the terminal 100 may be a smart wearable device such as smart glasses or a smart watch, which is not specifically limited in this embodiment.

[0060] The server 200 may be a single server, or a server cluster consisting of a plurality of servers, or the server 200 may include one or more virtualization platforms, or the server 200 may be a cloud computing service center.

[0061] The server 200 may be a server device that provides background services for the AI ​​application installed in the terminal 100 .

[0062] The terminal 100 and the server 200 establish a communication connection via a wired or wireless network. Optionally, the wireless network or wired network uses standard communication technology and / or protocols. The network is usually the Internet, but can also be any network, including but not limited to a local area network (LAN), a metropolitan area network (MAN), a wide area network (WAN), a mobile, wired or wireless network, a private network or any combination of a virtual private network.

[0063] Optionally, the terminal 100 is used to obtain the engineering bill of materials EBOM data and send the EBOM data to the server 200, so that the server 200 performs storage primary key and attribute analysis on the EBOM data, stores the EBOM data in the database, and divides the component data in each subsystem into modules according to the modularization rule, and then determines the non-module data according to the component data in the module, and optimizes the hierarchical structure of the component data and non-module data in the module, and then verifies the consistency and rationality of the optimized EBOM data to obtain a verification report, and the server can send the verification report to the terminal 100. Alternatively, the terminal 100 can independently implement the management operation of the engineering bill of materials.

[0064] For ease of understanding and explanation, the following Figures 2 to 6 The engineering material bill management method, device, equipment and medium provided in the embodiments of the present application are described in detail.

[0065] Figure 2 The flowchart of the engineering material bill management method of the embodiment of the present application is shown. The method can be executed by a computer device, which can be the above-mentioned Figure 1The server 200 or the terminal 100 in the system shown, or the computer device can also be a combination of the terminal 100 and the server 200. Figure 2 As shown, the method includes:

[0066] S101, obtaining engineering bill of materials (EBOM) data; the EBOM data includes system assembly data, the system assembly data includes data of multiple subsystems, and the subsystem includes multiple components.

[0067] It should be noted that the above EBOM data is the bill of materials generated during the engineering design phase of the product, which reflects the design structure and component composition of the product. EBOM usually consists of the following parts: product structure tree, component information, design document association, etc.; the product structure tree displays the composition relationship of the product in a hierarchical structure, from the top-level product to each sub-component and part. Component information includes: component number, name, specification, material, quantity and other detailed information. Design document association means that it may be associated with documents such as product design drawings and technical specifications to facilitate query and reference design requirements. For example, EBOM data can include but is not limited to: part code, part features, part name, quantity, location, weight, size, etc.

[0068] The EBOM data may include system assembly data, which includes data of multiple subsystems, and the subsystems include multiple components.

[0069] It is understandable that, taking the product as a vehicle, the vehicle includes five major assemblies, namely: engine assembly, transmission assembly, steering wheel assembly, front and rear axle assembly, and frame assembly. The engine assembly is the core of the car, responsible for converting the chemical energy generated by fuel combustion into mechanical energy to drive the car forward. It consists of basic components such as cylinder block, cylinder head, piston, crankshaft, connecting rod, camshaft, fuel system and ignition system. The transmission assembly is responsible for changing the speed and torque of power transmission to adapt to different driving conditions. It achieves gear shifting by changing the gear ratio to ensure that the car can operate effectively at different speeds. The steering wheel assembly, front and rear axle assembly and frame assembly are respectively involved in the control, suspension and structural support of the car. They work closely with the engine and transmission to ensure that the car can drive stably and operate safely. Each assembly can include multiple subsystems, such as power system, chassis system, etc. Each subsystem includes multiple components, which can include accelerator, engine, etc.

[0070] Optionally, in the process of obtaining the engineering bill of materials EBOM data, the user may perform input operations on the terminal to obtain the EBOM data; the EBOM data may be obtained by importing through an external device; or the EBOM data may be obtained from a blockchain or other database. In this embodiment, there is no limitation on the method of obtaining EBOM data.

[0071] S102, performing storage primary key and attribute analysis on the EBOM data, and storing the EBOM data in a database.

[0072] It is understandable that in database design, primary key and attribute are two different concepts. The primary key is a field or a group of fields used to shift-identify each row of records in a table. The value of the primary key must be unique and cannot be empty. The role of the primary key is to ensure the integrity of the data, avoid duplicate data records, provide a way to quickly find specific records, and establish associations between tables. Attributes refer to columns in a table, each column represents a feature or attribute of an entity. For example, in the EBOM table, part code, part name, quantity, etc. are all attributes. Its role is to store specific information about the entity so that the data can be described in more detail and accurately.

[0073] After acquiring the EBOM data, the storage primary key and attribute analysis of the EBOM data can be performed in the operating system of the database, and then the EBOM data can be stored in the database according to the analysis results. As an implementable method, in the process of storing the EBOM data in the database, the attribute type, attribute information, primary key information and primary key type of the EBOM data can be first analyzed according to the EBOM data to determine the attribute type, attribute information, primary key information and primary key type of the EBOM data, and then the EBOM data can be stored in the database based on the attribute type, attribute information, primary key information and primary key type. Among them, the attribute type can include Char or Boolean type, the primary key type can include VarChar type, the primary key information is used to uniquely identify the component, and the attribute information can be the component information in the EBOM data.

[0074] Specifically, the EBOM data is analyzed, and the attribute type is determined to be Char or Boolean type according to the nature of the information represented by each attribute in the EBOM data. The primary key information storing the primary key may include the part code, which can usually be encoded using a serial number, and the first few digits are fixed professional identification codes. For example, 001 represents the chassis system and 002 represents the power system. The primary key type is set to VarChar type, and the primary key content cannot be empty (NOT NULL), and the length is not less than 6 bits and not more than 32 bits. After setting the attributes and primary keys of the EBOM data, the EBOM data is stored in the database.

[0075] Among them, in the process of determining the attribute information of each EBOM data, for example: the part code of the EBOM data is usually a string type (Char), because it is a unique identifier containing letters and numbers. The part characteristics of the EBOM data can be Char or Boolean type, depending on the specific feature description. If the feature is descriptive (such as material type, surface treatment, etc.), then it should be Char type; if the feature can be simply expressed as "yes / no" (such as whether it is recyclable), then Boolean type can be used. The part name of the EBOM data is a string type (Char), which is used to provide an easy-to-understand name. The quantity of EBOM data is usually an integer type (Integer) or a floating point type (Float), indicating how many such parts are required. The position of the EBOM data can be a Char type if it is descriptive information (for example, "left front door"). If it is a specific position in the coordinate system, it may be a numeric type.

[0076] For example, after obtaining the EBOM data, the attribute information of the engine (Part A), transmission (Part B), brake system (Part C) and other components in the EBOM data may include: version number, component name, quantity, weight, size, material, etc. A unique part code is generated for each component, and the part code is used as the primary key information, such as engine code ENG001, transmission code TRN002, and brake system code BRK003. The primary key type can be set to VARCHAR, and the uniqueness is ensured by setting the primary key ID to these codes.

[0077] In this embodiment, by performing storage primary key and attribute analysis on the EBOM data, the EBOM data can be accurately stored in the database so that the EBOM data can be processed in a timely manner, and the storage of the EBOM data is made more regular while ensuring the uniqueness of the storage of the EBOM data.

[0078] S103. Divide the component data in each subsystem into modules according to modularization rules.

[0079] It should be noted that the above modularization rules are customized according to actual needs, and the modularization rules are used to perform modularization processing on the component data in the subsystem. Different component data are determined to be divided into the same module according to the modularization rules.

[0080] In one of the embodiments, the present application also provides a specific implementation method for dividing the component data in each subsystem into modules according to the modularization rule, see Figure 3 As shown, the method includes:

[0081] S201, dividing component data according to functions, and determining the functional class to which each component data belongs.

[0082] S202: For each functional class in each subsystem, calculate the degree of association between every two functional classes.

[0083] S203: When the correlation degree is greater than a preset correlation degree threshold, the component data corresponding to the two functional classes are divided into the same region; the same region includes multiple regional functional classes.

[0084] S204. For the regional function classes in the same area, calculate the design change frequency value between every two regional function classes.

[0085] S205: When the design change frequency value is less than a preset design change frequency threshold, the component data corresponding to the two regional function classes are divided into the same module.

[0086] Specifically, after storing the EBOM data in the database, the component data in the EBOM data can be functionally divided to determine the functional class to which each component data belongs. The functional class to which the component data belongs refers to the functional category to which the component belongs, which may include power system, transmission system, safety system, etc. Each component data may correspond to one functional class or multiple functional classes. For example, the functional class to which the ENG001 engine component in the EBOM data belongs is the power system, the functional class to which the TRN002 transmission component belongs is the transmission system, and the functional class to which the BRK003 brake component belongs is the safety system.

[0087] After determining the functional class, the component data can be analyzed for functions and the correlation between devices to determine the correlation between each functional class. The correlation between the functional classes can be calculated by obtaining the number of components required to realize each of the two functional classes and the number of common components required to realize the two functional classes. For each subsystem functional class i and functional class j, the correlation between functional class i and functional class j is calculated by the following formula:

[0088]

[0089] Among them, N ij It refers to the number of common components required to realize both functional class i and functional class j, N i Refers to the total number of components required to implement functional class i, Nj It refers to the total number of components required to implement functional class j.

[0090] After obtaining the correlation between each two functional classes, the correlation can be compared with the preset correlation threshold R thd For comparison, when the correlation is greater than the preset correlation threshold, it indicates that the correlation between the two functional classes is high, and the component data corresponding to the two functional classes are divided into the same area; the same area includes multiple regional functional classes; when the correlation is not greater than the preset correlation threshold, it indicates that the correlation between the two functional classes is low, and the component data corresponding to the two functional classes cannot be divided into the same area.

[0091] After determining the component data in the same area, the design change frequency value between each two regional function classes can be calculated for the regional function classes in the same area, that is, the design change frequency value is calculated for each component data in the subsystem whose correlation is higher than the preset correlation threshold, and the design change frequency value is obtained. The design change frequency value is compared with the preset design change frequency threshold. When the design change frequency value is greater than or equal to the preset design change frequency threshold V thd When the design change frequency value is less than the preset design change frequency threshold, it indicates that the design change frequency is small, and it is suitable to be packaged in the same module, and the component data is divided into the same module. Among them, the above-mentioned correlation threshold and the preset design change frequency threshold can be customized according to actual needs. For example, the correlation threshold can be set to 0.6, and the design change frequency threshold can be 4.

[0092] For example, for the components, the correlation between the function class corresponding to the engine and the function class corresponding to the transmission is 0.8, the correlation between the function class corresponding to the engine and the function class corresponding to the brake system is 0.3, and the correlation threshold R thd It can be 0.6, then the engine and transmission can be divided into the same area. The number of design changes of the engine is obtained to be 5 times, and the number of design changes of the transmission is 3 times, so it is determined that the number of design changes of the engine and transmission is 5. Since the number of changes 5> the preset design change frequency threshold 4, although the correlation is high, the changes are relatively frequent, so it is not suitable to be divided into the same module. And because the correlation between the engine and the brake system is low, they each maintain independent modules.

[0093] In the embodiment of the present application, by combining the correlation and the number of design changes for analysis, the EBOM data can be modularized more accurately, thereby providing good data guidance information for subsequent hierarchical optimization.

[0094] S104: Determine non-modular data according to the component data in the module, and optimize the hierarchical structure of the component data and non-modular data in the module.

[0095] Specifically, after modularizing the component data into modules, the data of the EBOM data that is not divided into modules is used as non-modularized data, and it is determined whether there is duplicate data in the modularized component data. If there is duplicate data, the duplicate component data is merged and one of the duplicate component data is deleted. The index of the component data in the non-modularized data is determined, and then the virtual assembly component is optimized according to the index.

[0096] As an implementable method, in the process of optimizing the hierarchical structure of component data and non-modular data in a module, a hierarchical analysis can be performed on the component data in the module to determine the degree of repetition between hierarchical component data of every two levels. When the degree of repetition is greater than a preset repetition threshold, the repeated component data is obtained and deleted; the index of the component data in the non-modular data is calculated; when the index is not greater than the preset index threshold, the target component data is obtained and deleted; and the subordinate components of the target component data are mounted under the parent of the target component data. The target component data is the virtual assembly component data to be deleted.

[0097] In this embodiment, the component data in the module includes multiple levels, and the multiple levels may include a parent level, a child level, etc. The component data in the module may be subjected to a hierarchical analysis, and the degree of repetition between the hierarchical component data in every two levels may be calculated, which may be expressed by the following formula:

[0098]

[0099] Among them, D mn N is the duplication degree of component data between level m and level n, mn N is the number of components used by level m and level n. m is the number of components used at level m, N n The number of components used for level n.

[0100] After calculating the degree of repetition, the degree of repetition can be compared with the preset repetition threshold M. thd When the repetition degree is greater than the preset repetition threshold M thd , it means that the component data of the two levels have a high degree of duplication. One of the duplicate component data can be released and the difference content can be mounted under the unique component data.

[0101] After the modular data is merged, the structure that cannot be modularized in the system can be optimized and adjusted, and unnecessary virtual assembly parts can be deleted. An indicator can be used to analyze the necessity of the virtual assembly. Among them, the non-modular data includes multiple virtual assembly parts. This indicator is used to characterize the importance of virtual assembly data in non-modular data, which can be expressed by the following formula:

[0102] V i =α f *F i +β r *R i +γ m *M i ;

[0103] Among them, V i is the indicator, F i is the functional dependency of the virtual assembly components, R i is the component reusability of the virtual assembly parts, M i is the management complexity of virtual assembly parts, α f is the weight of functional dependency, β r is the weight of component reusability, γ m The weight of management complexity.

[0104] After the index is calculated, the index can be compared with the preset index threshold. When the index is greater than the preset index threshold, it indicates that the importance of the virtual assembly component is high and it will not be deleted. When the index is not greater than the preset index threshold, it indicates that the importance of the virtual assembly component is poor and it will be used as the target component data and deleted. Then, the subordinate components of the target component data are mounted under the parent of the target component data.

[0105] For example, for a virtual assembly component "engine assembly" in non-modular data, the virtual assembly component includes: an engine and related components, and its corresponding indexes can be calculated to obtain the functional dependency F of the virtual assembly component. i =7, component reusability of virtual assembly parts R i =5, the management complexity of virtual assembly parts M i =3,α f =0.5,β r =0.3,γ m =0.2, calculate the index V i =5.8. The index is compared with the preset index threshold 6. Since 5.8>5, it indicates that the importance of the virtual assembly component is high, and the virtual assembly component can be retained.

[0106] In this embodiment, by performing hierarchical analysis on the components within the module, duplicate component data is deleted to avoid redundant data, and by calculating the indicators of non-modular data, the target component data can be obtained and deleted, and the subordinate components of the target component data are mounted under the parent level of the target component data, thereby reducing the hierarchical depth and complexity, making the entire EBOM data easy to manage and maintain, reducing the time and energy consumption of searching and updating information in the multi-level structure, and helping to more effectively realize system integration and modular design.

[0107] S105. Verify the consistency and rationality of the optimized EBOM data to obtain a verification report; the verification report is used to manage the engineering material list.

[0108] After the hierarchical optimization process, the optimized EBOM data is verified for consistency and rationality, and the optimized EBOM data is compared with the preset document file to obtain the comparison result, and the configuration logic relationship of the optimized EBOM data is verified to obtain the logic verification result, and the dependency verification of each component data in the optimized EBOM data is performed to obtain the dependency verification result, and the verification report is obtained based on the comparison result, the logic verification result and the dependency verification result. Among them, the preset document file can refer to the CAD drawing, the production order and the supplier list.

[0109] The optimized EBOM data, CAD drawings, production orders and supplier lists are converted into a processable format, which may include: Excel, CSV, XML or Json format. After conversion into a processable format, the optimized EBOM data is then compared with the preset document file, and key fields can be defined and the consistency fields that need to be checked in the optimized EBOM data can be determined, and the consistency fields include: part number, name, quantity, specification, etc. Then a mapping table is created, and the key fields in the CAD drawings, production orders and supplier lists and the consistency fields corresponding to the EBOM data are determined according to the mapping table, and a programming tool or a comparison tool is used to verify whether the consistency fields in the optimized EBOM data are consistent with the key fields in the preset document file, and a comparison result is obtained; when the comparison result indicates that the comparison is consistent, it indicates that the comparison between the optimized EBOM data and the preset document file is successful; when the comparison result indicates that the comparison is inconsistent, it indicates that the comparison between the optimized EBOM data and the preset document file fails, and the information of the inconsistent comparison is determined, and the corresponding component is found according to the information of the inconsistent comparison, and then the component is redesigned and optimized. The programming tools mentioned above may include tools corresponding to Python or other programming languages, and the data comparison tools may include, for example, the corresponding VLOOKUP function in Excel.

[0110] In this embodiment, by converting the optimized EBOM data, CAD drawings, production orders and supplier lists into a processable format, it can be ensured that all files use the same encoding format, which facilitates more accurate subsequent comparison processing and improves the accuracy of the comparison results.

[0111] Furthermore, after the optimized EBOM data is compared for consistency, the configuration logic relationship of the EBOM data can be verified. First, a configuration table is obtained, which is used to characterize, record and manage product configuration information. The configuration table includes multiple configuration options, and a mapping relationship between the optimized EBOM data and the configuration options in the configuration table is determined; based on the mapping relationship, the EBOM data and the configuration options in the configuration table are functionally matched and verified to obtain a logical verification result.

[0112] In this embodiment, the configuration table can be pre-set according to actual needs, which may include: unique identification information that should be included in the structure of component selection, parameter setting, configuration options, etc. The identification information may include configuration ID, component number, option description, parameter range, etc. Each EBOM data corresponds to one or more configuration items in the configuration table, and there is a mapping relationship between each configuration item and the corresponding EBOM data. After obtaining the configuration table, the mapping relationship between the optimized EBOM data and the configuration options in the configuration table is determined, and then the EBOM data and the configuration options in the configuration table are functionally matched and verified according to the mapping relationship to determine whether the component data in the EBOM data correctly matches the configuration options in the configuration table. Specifically, it can be determined whether the parameters in the EBOM are within the definition range of the parameters in the configuration table in the configuration table, and whether the size, capacity, and characteristics of the component are within the parameter range defined in the configuration table to obtain a logical verification result. Finally, the dependency and logic between the data of each component in the optimized EBOM data are verified, and it is determined whether each component meets the design specifications and functional requirements when added to the assembly to obtain a dependency verification result. Then, the comparison results, the logical verification results, and the dependency verification results are integrated and processed to obtain a verification report.

[0113] In the process of judging whether the parameters in the EBOM are within the definition range of the parameters in the configuration table, the parameters may be compared with the definition range of the parameters in the configuration table to check whether the conditions are met. When the conditions are met, the parameters in the EBOM meet the definition range of the parameters in the configuration table; when the conditions are not met, it indicates that the parameters in the EBOM do not meet the definition range of the parameters in the configuration table.

[0114] Optionally, in order to manage the EBOM data in the database in real time, an automatic update mode and a corresponding update cycle can be set, and the update cycle can be 6 months. After each cycle, the input EBOM data is first obtained and stored in the database, and then the component data in each subsystem is divided into modules according to the modular rules, and non-modular data is determined according to the component data in the module, and the hierarchical structure of the component data and non-modular data in the module is optimized, and finally the consistency and rationality of the optimized EBOM data are verified to obtain a verification report.

[0115] For example, see Figure 4 As shown, the engineering bill of materials EBOM data is first collected, and the EBOM data is input according to the rules. The EBOM data is stored in the database through the data storage module, and then the data storage module is entered. The component data in the EBOM data is first functionally divided to determine the functional class to which each component data belongs. For the functional class in each subsystem, the correlation between each two functional classes is analyzed. When the correlation is greater than the preset correlation threshold, the functional class with a correlation greater than the preset correlation threshold is subjected to a change frequency analysis, thereby being divided into various modules. Then the data hierarchy optimization module is entered, and the degree of repetition between the hierarchical component data of each two levels is determined by performing a hierarchical analysis on the component data in the module, and the repeated components are merged according to the degree of repetition, and the component data in the non-modular data is processed to delete useless virtual assembly components. Then the data verification module is entered, and the optimized EBOM data is sequentially checked for data consistency and configuration logic relationship verification to generate a verification report. The automatic update cycle is set, and when the corresponding cycle is reached, the redesign process is performed.

[0116] The engineering bill of materials management method provided in the embodiment of the present application includes: obtaining engineering bill of materials EBOM data, the EBOM data includes system assembly data, the system assembly data includes data of multiple subsystems, the subsystem includes multiple components, and storing primary key and attribute analysis on the EBOM data, storing the EBOM data in a database, and then dividing the component data in each subsystem into modules according to modular rules, and then determining non-modular data based on the component data in the module, and optimizing the hierarchical structure of the component data and non-modular data in the module, and finally verifying the consistency and rationality of the optimized EBOM data to obtain a verification report. Compared with the existing technology, this solution can make the storage of EBOM data more regular by storing EBOM data in the database and dividing it into modular data and non-modular data according to modular rules, and optimize the hierarchical structure of modular data and non-modular data, reducing the hierarchical depth and complexity, making the entire EBOM data easy to manage and maintain, reducing the time and energy consumption of searching and updating information in the multi-level structure, and helping to more effectively realize system integration and modular design. It can also verify the consistency and rationality of the optimized EBOM data, improve the management efficiency of the bill of materials, further improve the efficiency of product design and development, and optimize the overall production and operation, improve product quality and enhance product competitiveness.

[0117] on the other hand, Figure 5 The schematic diagram of the structure of a project material list management device provided in an embodiment of the present application. The device may be a device in a terminal or a server, such as Figure 5 As shown, the device 700 includes:

[0118] The acquisition module 710 is used to acquire the engineering bill of materials EBOM data; the EBOM data includes system assembly data, the system assembly data includes data of multiple subsystems, and the subsystem includes multiple components;

[0119] The data storage module 720 is used to perform storage primary key and attribute analysis on the EBOM data and store the EBOM data in a database;

[0120] The data division module 730 is used to divide the component data in each subsystem into modules according to the modularization rule;

[0121] A hierarchical optimization module 740, for determining non-modular data according to component data in the module, and performing hierarchical structure optimization on the component data and non-modular data in the module;

[0122] The data verification module 750 is used to verify the consistency and rationality of the optimized EBOM data and obtain a verification report; the verification report is used to manage the engineering material list.

[0123] Optionally, the data storage module 720 is specifically used for:

[0124] Analyze the EBOM data to determine the attribute type, attribute information, primary key information and primary key type of the EBOM data;

[0125] Based on the attribute type, attribute information, primary key information and primary key type, the EBOM data is stored in the database.

[0126] Optionally, the data partitioning module 730 is specifically configured to:

[0127] Divide component data according to function and determine the functional category to which each component data belongs;

[0128] For each functional class in each subsystem, calculate the correlation between every two functional classes;

[0129] When the correlation is greater than a preset correlation threshold, the component data corresponding to the two functional classes are divided into the same area; the same area includes multiple regional functional classes;

[0130] For the regional function classes within the same area, the design change frequency value between every two regional function classes is calculated;

[0131] When the design change frequency value is less than a preset design change frequency threshold, the component data corresponding to the two regional function classes are divided into the same module.

[0132] Optionally, the data partitioning module 730 is further configured to:

[0133] Obtain the number of components required to implement each of the two functional classes and the number of common components required to implement the two functional classes;

[0134] The association degree between the two functional classes is calculated based on the number of components required to implement each of the two functional classes and the number of common components.

[0135] Optionally, the hierarchical optimization module 740 is specifically used to:

[0136] Perform hierarchical analysis on the component data in the module to determine the degree of duplication between hierarchical component data of every two levels;

[0137] When the degree of duplication is greater than a preset duplication threshold, the duplicate component data is obtained and deleted;

[0138] Calculate indicators of component data in non-modular data;

[0139] When the indicator is not greater than the preset indicator threshold, the target component data is obtained and deleted;

[0140] Mount the subordinate components of the target component data under the parent of the target component data.

[0141] Optionally, the data verification module 750 is specifically used to:

[0142] Compare the optimized EBOM data with the preset document file to obtain the comparison result;

[0143] Verify the configuration logic relationship of the optimized EBOM data to obtain the logic verification result;

[0144] Perform dependency verification on each component data in the optimized EBOM data to obtain dependency verification results;

[0145] A verification report is obtained based on the comparison results, logic verification results and dependency verification results.

[0146] Optionally, the data verification module 750 is further used to:

[0147] Obtain a configuration table; the configuration table is used to represent, record and manage product configuration information, and the configuration table includes multiple configuration options;

[0148] Determine the mapping relationship between the optimized EBOM data and the configuration options in the configuration table;

[0149] According to the mapping relationship, the EBOM data and the configuration options in the configuration table are functionally matched and verified to obtain a logical verification result.

[0150] It can be understood that the functions of each functional module of the engineering material bill management system of this embodiment can be specifically implemented according to the method in the above method embodiment, and its specific implementation process can refer to the relevant description of the above method embodiment, which will not be repeated here.

[0151] On the other hand, the computer device provided in the embodiment of the present application includes a memory, a processor, and a computer program stored in the memory and executable on the processor, and when the processor executes the program, the engineering material bill management method as described above is implemented.

[0152] Reference below Figure 6 , Figure 6 A schematic diagram of the structure of a computer system of a terminal device according to an embodiment of the present application.

[0153] like Figure 6As shown, the computer system 300 includes a central processing unit (CPU) 301, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 302 or a program loaded from a storage part 303 to a random access memory (RAM) 303. In the RAM 303, various programs and data required for the operation of the system 300 are also stored. The CPU 301, the ROM 302, and the RAM 303 are connected to each other through a bus 304. An input / output (I / O) interface 305 is also connected to the bus 304.

[0154] The following components are connected to the I / O interface 305: an input section 306 including a keyboard, a mouse, etc.; an output section 307 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 308 including a hard disk, etc.; and a communication section 309 including a network interface card such as a LAN card, a modem, etc. The communication section 309 performs communication processing via a network such as the Internet. A drive 310 is also connected to the I / O interface 305 as needed. A removable medium 311, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 310 as needed, so that a computer program read therefrom is installed into the storage section 308 as needed.

[0155] In particular, according to an embodiment of the present application, the process described above with reference to the flowchart can be implemented as a computer software program. For example, an embodiment of the present application includes a computer program product, which includes a computer program carried on a machine-readable medium, and the computer program includes a program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from the network through the communication part 303, and / or installed from the removable medium 311. When the computer program is executed by the central processing unit (CPU) 301, the above-mentioned functions defined in the system of the present application are executed.

[0156] It should be noted that the computer-readable medium shown in the present application may be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. The computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present application, a computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in combination with an instruction execution system, device or device. In the present application, a computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, which carries a computer-readable program code. This propagated data signal may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. Computer-readable signal media may also be any computer-readable medium other than computer-readable storage media, which may send, propagate or transmit a program for use by or in conjunction with an instruction execution system, apparatus or device. The program code contained on the computer-readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, optical cable, RF, etc., or any suitable combination of the above.

[0157] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present application. In this regard, each box in the flow chart or block diagram can represent a module, a program segment or a part of the code, and the aforementioned module, program segment or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram and / or flow chart, and the combination of the boxes in the block diagram and / or flow chart can be implemented with a dedicated hardware-based system that performs the specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0158] The units or modules involved in the embodiments described in the present application may be implemented by software or by hardware. The units or modules described may also be arranged in a processor, for example, may be described as: a processor comprising: an acquisition module, a data storage module, a data partitioning module, a hierarchical optimization module and a data verification module. Among them, the names of these units or modules do not constitute a limitation on the units or modules themselves under certain circumstances. For example, the acquisition module may also be described as "used to obtain engineering bill of materials EBOM data; the EBOM data includes system assembly data, the system assembly data includes data of multiple subsystems, and the subsystem includes multiple components".

[0159] As another aspect, the present application further provides a computer-readable storage medium, which may be included in the electronic device described in the above embodiment; or may exist independently without being assembled into the electronic device. The above computer-readable storage medium stores one or more programs, and when the above programs are used by one or more processors to execute the engineering material bill management method described in the present application:

[0160] Acquire engineering bill of materials (EBOM) data; the EBOM data includes system assembly data, the system assembly data includes data of multiple subsystems, and the subsystem includes multiple components;

[0161] Perform storage primary key and attribute analysis on the EBOM data, and store the EBOM data in a database;

[0162] According to modularization rules, the component data in each of the subsystems is divided into modules;

[0163] Determine non-modular data according to the component data in the module, and optimize the hierarchical structure of the component data in the module and the non-modular data;

[0164] The optimized EBOM data is verified for consistency and rationality to obtain a verification report; the verification report is used to manage the engineering material list.

[0165] In summary, the engineering bill of materials management method, device, equipment and medium provided in the embodiments of the present application include: obtaining engineering bill of materials EBOM data, the EBOM data includes system assembly data, the system assembly data includes data of multiple subsystems, the subsystem includes multiple components, and storing primary key and attribute analysis on the EBOM data, storing the EBOM data in a database, and then dividing the component data in each subsystem into modules according to modular rules, and then determining non-modular data based on the component data in the module, and optimizing the hierarchical structure of the component data and non-modular data in the module, and finally verifying the consistency and rationality of the optimized EBOM data to obtain a verification report. Compared with the existing technology, this solution can make the storage of EBOM data more regular by storing EBOM data in the database and dividing it into modular data and non-modular data according to modular rules, and optimize the hierarchical structure of modular data and non-modular data, reducing the hierarchical depth and complexity, making the entire EBOM data easy to manage and maintain, reducing the time and energy consumption of searching and updating information in the multi-level structure, and helping to more effectively realize system integration and modular design. It can also verify the consistency and rationality of the optimized EBOM data, improve the management efficiency of the bill of materials, further improve the efficiency of product design and development, and optimize the overall production and operation, improve product quality and enhance product competitiveness.

[0166] The above description is only a preferred embodiment of the present application and an explanation of the technical principles used. Those skilled in the art should understand that the scope of the invention involved in the present application is not limited to the technical solution formed by a specific combination of the above technical features, but should also cover other technical solutions formed by any combination of the above technical features or their equivalent features without departing from the inventive concept. For example, the above features are replaced with the technical features with similar functions disclosed in this application (but not limited to) by each other.

Claims

1. A method for managing a project bill of materials, characterized in that: The engineering material bill management method comprises: Acquire engineering bill of materials (EBOM) data; the EBOM data includes system assembly data, the system assembly data includes data of multiple subsystems, and the subsystem includes multiple components; Perform storage primary key and attribute analysis on the EBOM data, and store the EBOM data in a database; According to modularization rules, the component data in each of the subsystems is divided into modules; Determine non-modular data according to the component data in the module, and optimize the hierarchical structure of the component data in the module and the non-modular data; The optimized EBOM data is verified for consistency and rationality to obtain a verification report; the verification report is used to manage the engineering material list.

2. The method for managing a project bill of materials according to claim 1, characterized in that: Performing storage primary key and attribute analysis on the EBOM data and storing the EBOM data in a database includes: Analyze the EBOM data to determine the attribute type, attribute information, primary key information and primary key type of the EBOM data; The EBOM data is stored in a database based on the attribute type, the attribute information, the primary key information and the primary key type.

3. The method for managing a project bill of materials according to claim 1, characterized in that: According to modularization rules, the component data in each subsystem is divided into modules, including: Dividing the component data according to function to determine the functional class to which each component data belongs; For each functional class in each subsystem, calculating the correlation between every two functional classes; When the correlation is greater than a preset correlation threshold, the component data corresponding to the two functional classes are divided into the same area; the same area includes multiple regional functional classes; For the regional function classes within the same area, calculating the design change frequency value between every two regional function classes; When the design change frequency value is less than a preset design change frequency threshold, the component data corresponding to the two regional function classes are divided into the same module.

4. The method for managing a project bill of materials according to claim 3, characterized in that: For each functional class in each subsystem, the correlation between every two functional classes is calculated, including: Obtaining the number of components required to implement each of the two functional classes and the number of common components required to implement the two functional classes; The degree of association between the two functional classes is calculated according to the number of components required to implement each of the two functional classes and the number of common components.

5. The method for managing a project bill of materials according to claim 1, characterized in that: The module includes multiple levels, and the component data in the module and the non-modular data are optimized in a hierarchical structure, including: Performing hierarchical analysis on the component data in the module to determine the degree of duplication between hierarchical component data of every two hierarchical levels; When the degree of repetition is greater than a preset repetition threshold, obtaining and deleting the repetitive component data; Calculating an index of component data in the non-modular data; When the indicator is not greater than a preset indicator threshold, obtaining target component data and deleting it; The subordinate component of the target component data is mounted under the parent of the target component data.

6. The method for managing a project bill of materials according to claim 1, characterized in that: Verify the consistency and rationality of the optimized EBOM data and obtain a verification report, including: Comparing the optimized EBOM data with the preset document file to obtain a comparison result; Verifying the configuration logic relationship of the optimized EBOM data to obtain a logic verification result; Performing dependency verification on each component data in the optimized EBOM data to obtain a dependency verification result; A verification report is obtained according to the comparison result, the logic verification result and the dependency verification result.

7. The method according to claim 6, characterized in that The optimized EBOM data is configured with a logical relationship verification to obtain a logical verification result, including: Obtain a configuration table; the configuration table is used to characterize, record and manage product configuration information, and the configuration table includes multiple configuration options; Determine a mapping relationship between the optimized EBOM data and the configuration options in the configuration table; According to the mapping relationship, the EBOM data and the configuration options in the configuration table are functionally matched and verified to obtain the logic verification result.

8. A project material bill management device, characterized in that: The engineering material bill management device comprises: An acquisition module is used to acquire engineering bill of materials (EBOM) data; the EBOM data includes system assembly data, the system assembly data includes data of multiple subsystems, and the subsystem includes multiple components; A data storage module, used for performing storage primary key and attribute analysis on the EBOM data, and storing the EBOM data in a database; A data division module, used for dividing the component data in each of the subsystems into modules according to modular rules; A hierarchical optimization module, used for determining non-modular data according to the component data in the module, and performing hierarchical structure optimization on the component data in the module and the non-modular data; The data verification module is used to verify the consistency and rationality of the optimized EBOM data to obtain a verification report; the verification report is used to manage the engineering material list.

9. A computer device comprising: A memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the steps of the engineering material bill management method described in any one of claims 1-7.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the engineering material bill management method described in any one of claims 1 to 7 are implemented.

Images