A BOM configuration method, device, system and storage medium

Abstract

This application discloses a BOM configuration method, apparatus, system, and storage medium. The method includes: when a selection operation on a product planning document is received, loading the product planning document; when a selection operation on a specific release module in the product planning document is received, determining the functional feature code corresponding to the release module through the product planning document; determining the assembly combination matching the functional feature code through the product planning document; determining the sub-part information corresponding to the assembly combination through a knowledge base; and outputting a BOM file containing the assembly combination and the corresponding sub-part information. The solution provided in this application can improve the efficiency of building BOM files for automotive assemblies and sub-parts.

Description

Technical Field

[0001] This application relates to the field of automotive R&D product data management technology, and in particular to a BOM configuration method, device, system and storage medium. Background Technology

[0002] A car is composed of tens of thousands of parts, assembled together through a complex hierarchical relationship. The Bill of Materials (BOM) is the core foundational data for automotive R&D. Assembly configuration information describes the relationship between components and the entire vehicle, while sub-part structural information displays the parent-child hierarchical assembly structure. These elements are present throughout the entire product lifecycle, from engineering design and prototyping to mass production and after-sales service. Because a car contains multiple assemblies—for example, the chassis system includes the suspension assembly and drivetrain—and each assembly is composed of numerous sub-parts, accurate assembly configuration and sub-part structural information are arguably the most critical information in the BOM. However, they are also the most complex and error-prone.

[0003] Current technologies can only automatically create vehicle-level assembly BOM configurations based on known product function configurations and module constraints. However, the current automotive product series are highly variable, and project product plans differ significantly and are dynamically changing, making it impractical to pre-define all product series. Therefore, under complex product series, engineers must manually analyze the situation of each module assembly and select functional feature codes to create configuration combinations based on experience. Moreover, during product development, engineers must manually build sub-part BOM structures for specific assemblies to meet after-sales and other business needs. The cycle for completing the BOM configuration and sub-part structure construction of a certain module assembly often takes one month or even longer, which is difficult to meet the urgent need for rapid product data release and changes.

[0004] Therefore, how to provide a BOM configuration method to improve the efficiency of BOM configuration for automotive assemblies and sub-part structure assembly has become an urgent technical problem to be solved. Summary of the Invention

[0005] This application provides a BOM configuration method, apparatus, system, and storage medium to improve the efficiency of building BOM files for automotive assemblies and sub-parts.

[0006] This application provides a BOM configuration method, including: When a selection action for the product planning document is received, the product planning document is loaded. When a selection operation for a specific release module in the product planning document is received, the functional feature code corresponding to the release module is determined through the product planning document. The product planning document determines the assembly combinations that match the aforementioned functional feature codes; The sub-part information corresponding to the assembly is determined using a knowledge base; Output a BOM file containing information on the assembly components and their corresponding sub-parts.

[0007] The beneficial effects of this application are as follows: When receiving a selection operation for a product planning document, this application loads the product planning document; when receiving a selection operation for a specific release module in the product planning document, it determines the functional feature code corresponding to the release module through the product planning document; it determines the assembly combination matching the functional feature code through the product planning document; it determines the sub-part information corresponding to the assembly combination through the knowledge base; and it outputs a BOM file containing the assembly combination and corresponding sub-part information. Since this application can determine the corresponding functional feature code and matching assembly combination based on the selection operation for a specific release module in the product planning document, and determine the BOM structure of the corresponding sub-parts, and then output the final BOM file containing assembly and sub-part information, engineers do not need to manually interpret the configuration options and constraints related to the functional feature codes in the product planning document based on experience, thus improving the efficiency of building automotive assembly and sub-part BOM files.

[0008] In one embodiment, loading the product planning document includes: Automatically extract and parse the functional feature codes, configuration options, and constraints in the product planning document to define the distribution matrix of project product functions, technical parameters, and market requirements across various vehicle models.

[0009] In one embodiment, determining the assembly combination matching the functional feature code through the product planning document includes: Obtain the distribution matrix of configuration options and constraints for each functional feature code in the product planning document; Invalid configuration combinations are parsed and filtered based on the configuration options and constraint distribution matrix. The remaining assemblies after filtering out invalid configuration combinations are determined as valid assembly configuration combinations.

[0010] In one embodiment, the method further includes: Based on the user's selection of the release module and release scheme, the system automatically associates all assembly part types and corresponding functional feature codes within the module, and provides the user with a visual function list in a tree structure.

[0011] In one embodiment, determining the sub-part information corresponding to the assembly using a knowledge base includes: Analyze the assembly BOM file to identify the functional characteristic codes of each assembly; Traverse the knowledge base to identify the sub-part types and function location codes corresponding to the functions of each assembly; Based on the combination of functional feature codes of the assembly, the functional relationship between different sub-parts and the assembly is automatically established, and a sub-part BOM file containing sub-part number, part name, area location code, part quantity and the corresponding assembly part number of the sub-part is generated.

[0012] In one embodiment, the method further includes: Collect historical project data for different vehicle models and release plans within the company; A knowledge base is built based on the historical project data.

[0013] In one embodiment, constructing a knowledge base based on the historical project data includes: The collected data is cleaned and preprocessed to remove duplicate, erroneous, or incomplete information, thereby improving data quality. Based on the functions of components and assembly processes, the vehicle is divided into multiple modules, each module is assigned a unique code, and the relationship between the module code and the design release schemes of the assembly parts and sub-parts within the module is established to form a module-level design release knowledge base with universality and versatility. The design release scheme includes the binding relationship between assembly part types, area location codes, and functional feature codes, as well as the binding relationship between different sub-part types, area location codes, and assembly functional feature codes.

[0014] This application also provides a BOM configuration device, including: A loading unit is used to load the product planning document when a selection operation for the product planning document is received; The first determining unit is used to determine the functional feature code corresponding to the release module through the product planning document when a selection operation for a specific release module in the product planning document is received. The second determining unit is used to determine the assembly combination that matches the functional feature code through the product planning document; The third determining unit is used to determine the sub-part information corresponding to the assembly through a knowledge base; The output unit is used to output a BOM file containing information on the assembly of components and corresponding sub-parts.

[0015] In one embodiment, the loading unit is further configured to: Automatically extract and parse the functional feature codes, configuration options, and constraints in the product planning document to define the distribution matrix of project product functions, technical parameters, and market requirements across various vehicle models.

[0016] In one embodiment, the second determining unit includes: The sub-unit is used to obtain the distribution matrix of configuration options and constraints for each functional feature code in the product planning document. The first parsing subunit is used to parse and filter invalid configuration combinations based on the configuration option and constraint condition distribution matrix; The sub-unit is used to determine the remaining assemblies after filtering out invalid configuration combinations as valid assembly configuration combinations.

[0017] In one embodiment, the apparatus further includes: The association unit is used to automatically associate all assembly part types and corresponding functional feature codes within the module based on the user's selection of the release module and release scheme, and provide the user with a visual function list in a tree structure.

[0018] In one embodiment, the third determining unit includes: The second parsing subunit is used to parse the assembly BOM file to confirm the functional characteristic codes of each assembly. Traverse sub-units to traverse the knowledge base to identify the sub-part types and function location codes corresponding to the functions of each assembly; Sub-units are created to automatically establish the functional relationships between different sub-parts and assemblies based on the combination of functional feature codes of assemblies, and to generate a sub-part BOM file containing sub-part numbers, part names, area location codes, part quantities, and the corresponding assembly part numbers of the sub-parts.

[0019] In one embodiment, the apparatus further includes: The collection unit is used to collect historical project data for different vehicle models and release schemes within the enterprise. A building unit is used to build a knowledge base based on the historical project data.

[0020] In one embodiment, the building unit includes: The preprocessing subunit is used to clean and preprocess the collected data to remove duplicate, erroneous, or incomplete information and improve data quality. Sub-units are used to divide the vehicle into multiple modules based on the functions of the components and the assembly process. Each module is assigned a unique code, and the relationship between the module code and the design release schemes of the assembly parts and sub-parts within the module is established to form a module-level design release knowledge base with universality and versatility. The design release scheme includes the binding relationship between assembly part types, area location codes, and functional feature codes, as well as the binding relationship between different sub-part types, area location codes, and assembly functional feature codes.

[0021] This application also provides a BOM configuration system, including: At least one processor; and, A memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor to implement the BOM configuration method described in any of the above embodiments.

[0022] This application also provides a computer-readable storage medium, which, when the instructions in the storage medium are executed by a processor corresponding to the BOM configuration system, enables the BOM configuration system to implement the BOM configuration method described in any of the above embodiments.

[0023] Other features and advantages of this application will be set forth in the description which follows, and will be apparent in part from the description, or may be learned by practicing the application. The objectives and other advantages of this application may be realized and obtained by means of the structures particularly pointed out in the written description, claims, and drawings.

[0024] The technical solution of this application will be further described in detail below with reference to the accompanying drawings and embodiments. Attached Figure Description

[0025] The accompanying drawings are provided to further illustrate the present application and form part of the specification. They are used together with the embodiments of the present application to explain the application and do not constitute a limitation thereof. In the drawings: Figure 1 This is a flowchart of a BOM configuration method in one embodiment of this application; Figure 2 This is a flowchart illustrating the output of the assembly BOM file in one embodiment of this application; Figure 3 This is a flowchart illustrating the output of a sub-part BOM file in one embodiment of this application; Figure 4 This is a schematic diagram of the structure of a BOM configuration device according to an embodiment of this application; Figure 5 This is a schematic diagram of the hardware structure of a BOM configuration system according to an embodiment of this application. Detailed Implementation

[0026] The preferred embodiments of this application are described below with reference to the accompanying drawings. It should be understood that the preferred embodiments described herein are for illustration and explanation only and are not intended to limit this application.

[0027] As the diversity of vehicle models within the company increases, the product portfolio becomes increasingly complex. The project execution process generates a large amount of process and delivery data, which, when combined with historical project data, forms a robust, multi-structured, and multi-featured product database within the company. To create a universally applicable knowledge base that can be directly accessed by software tools during product development and BOM release processes without requiring manual parsing by individual engineers, this application utilizes big data analysis and expert extraction to pre-collect historical project data for different vehicle models and release schemes within the company. Based on this historical project data, a knowledge base is constructed, which includes a set of design release schemes for all assembly parts and sub-parts of all products within the company. Specifically, the collected data is cleaned and preprocessed to remove duplicate, erroneous, or incomplete information, thereby improving data quality. Then, based on the functions of the components and the assembly process, the vehicle is divided into multiple modules, each assigned a unique code, and a relationship is established between the module code and the design release schemes of the assembly parts and sub-parts within that module, forming a universal and applicable module-level design release knowledge base. The design release schemes include the binding relationships between assembly part types, regional location codes, and functional feature codes, as well as the binding relationships between different sub-part types, regional location codes, and assembly functional feature codes.

[0028] For example, in this knowledge base, the entire vehicle is divided into approximately 260 modules based on component functions and assembly processes, and each module is coded. Selecting a specific module code automatically associates it with all assembly parts and sub-part design release schemes within that module. Specifically: the assembly part design release scheme set describes the binding relationship between different design release schemes and assembly part types, region location codes, and functional feature codes, ensuring that any design release scheme selected by the user can match a specific assembly part type, region location code, and functional feature code; the sub-part design release scheme set reflects the binding relationship between different assembly functional feature codes and corresponding sub-parts, ensuring that any functional feature code involved in the selected design release scheme corresponds to a specific sub-part type and region location code.

[0029] Furthermore, since the knowledge base is greatly influenced by the professional characteristics of different modules and the experience and habits of different engineers, and changes relatively frequently with the integration of new technologies, when creating the knowledge base, it is necessary to fully consider the characteristics of historical data of each project and new release requirements, while integrating expert experience judgment and analysis of historical big data of each project, performing correlation coupling calculations, selecting the recommended solution with the highest correlation value, and enabling dynamic maintenance.

[0030] Based on the creation of a knowledge base, Figure 1 This is a flowchart of a BOM configuration method in one embodiment of this application, as follows: Figure 1 As shown, the method can be implemented as follows: S101-S105: In step S101, when a selection operation for the product planning document is received, the product planning document is loaded. In step S102, when a selection operation for a specific release module in the product planning document is received, the functional feature code corresponding to the release module is determined through the product planning document; In step S103, the assembly combination that matches the functional feature code is determined through the product planning document; In step S104, the sub-part information corresponding to the assembly is determined through a knowledge base; In step S105, a BOM file containing assembly information and corresponding sub-part information is output.

[0031] In this application, when a selection operation for a product planning document is received, the product planning document is loaded. The product planning document defines a distribution matrix of the usage conditions of a project's product functions, technical parameters, and market requirements across various vehicle models, in the form of functional feature codes, configuration options, and constraints. The distribution matrix of project product functions, technical parameters, and market requirements across various vehicle models is defined by automatically extracting and parsing the functional feature codes, configuration options, and constraints in the product planning document. For example, loading a product planning document can automatically extract and parse key information related to the BOM file release, such as automatically identifying basic product information like vehicle year, platform, brand code, vehicle series (different configuration levels such as high, low, and mid-range), and body type (SUV, sedan, MPV, etc.). Different basic product information corresponds to different detailed release schemes for different modules.

[0032] When a selection operation for a specific release module in the product planning document is received, the functional feature code corresponding to the release module is determined through the product planning document. In this application, multiple modules based on "vehicle structure division" define the location of components within the vehicle in the form of structural codes. For example, when an engineer selects the structural code (40.02) for the "seat" module they are responsible for, all part names, area location codes, and functional feature codes within the seat module can be automatically associated. For instance, seats are divided into front seats and rear seats, with the front seats further divided into driver's seat and passenger seat.

[0033] In one embodiment, based on the user's selection of the release module and release scheme, all assembly part types and corresponding functional feature codes within the module are automatically associated, and a visual functional list is provided to the user in a tree structure. By traversing the product planning document, all functional feature codes corresponding to the user-selected module are found, and after detailed parsing of the release scheme, a visual tree structure is automatically presented. This tree structure automatically extracts a list of all functions (in textual description form) and functional feature codes (technical parameters, such as codes representing different functions appearing in the BOM file) associated with the module in the product planning document. The purpose of this list is to facilitate engineers in verifying whether the functions they are interested in are included, and to decide whether to customize additions or deletions based on the actual project situation. On the one hand, functions can be added: new associations do not appear in the previous knowledge base; on the other hand, functions can be deleted: based on expert experience, if a function is not present in this project, or if the function is not different across different vehicle series in this project, it can be directly removed, reducing data redundancy.

[0034] The product planning document is used to determine the assembly combinations that match the functional feature codes. Specifically, the configuration options and constraints distribution matrix of each functional feature code in the product planning document is obtained; invalid configuration combinations are analyzed and filtered based on the configuration options and constraints distribution matrix; the remaining assemblies after filtering invalid configuration combinations are determined as valid assembly configuration combinations.

[0035] Assembly components are typically parts directly assembled on the production line. In the BOM (Bill of Materials) file, the configuration relationship of each assembly component in the vehicle is described using a combination of functional characteristic codes and logical symbols (&, / , -), reflecting the product function and usage definitions for different vehicle models in the product planning document. Taking the front driver's seat as an example, as shown in Table 1, for a certain product planning document definition, if the usage indicator for a certain function in a certain vehicle series is "S", it indicates that the function is 100% fully equipped in that vehicle series. For example, the configuration result of the "massage" function in the "H" vehicle series is "S", represented by "&CCC". If the usage indicator for a certain function in a certain vehicle series is "-", it indicates that the function is not equipped in that vehicle series. For example, the configuration result of the "massage" function in the "L" vehicle series is "-", represented by "-CCC". If the usage indicator for a certain function in a certain vehicle series is "0", it indicates that the function is an optional installation in the vehicle series. For example, the configuration result of the "fabric" function in the "H" vehicle series is "0", represented by "&CCC" and "-CCC".

[0036] Table 1

[0037] Using the same method, the configuration and usage results of each function in the "L" and "H" vehicle series were analyzed and arranged and combined. The resulting configuration and combination arrangements of each function in each vehicle series are shown in Table 2 below: Table 2

[0038] In addition, for ease of calculation, the configuration results in the table above are converted into a distribution matrix composed of "1" and "0". For example, if the configuration condition of a certain function feature code in this series is "&", it is represented by 1; if the configuration condition is "-", it is represented by "0". The configuration combination arrangement of each function in each model series is represented in binary method as shown in Table 3 below.

[0039] Table 3

[0040] Then, the information in the "Restrictions" is read. As shown in Table 1, the restriction for the ventilation function characteristic code BBB is "&AAA-DDD". Therefore, it is determined that: BBB and AAA must appear simultaneously (both can be 1), or neither can appear simultaneously (both can be 0); BBB and DDD cannot appear simultaneously (neither can be 1), nor can they both be absent simultaneously (neither can be 0). Combinations that do not meet the above conditions will be considered invalid combinations. As shown in Table 4, this is the invalid configuration combination identification process, indicated by underlines. For the system, the background will automatically mark these combinations.

[0041] Table 4 Identifying Invalid Configuration Combinations

[0042] Based on the above judgment process, invalid combinations are removed, valid combinations are selected, and finally valid configuration combinations are formed, as shown in Table 5 below.

[0043] Table 5

[0044] Figure 2 This is a flowchart illustrating the output of the assembly BOM file in one embodiment of this application, as follows: Figure 2 As shown, after filtering out invalid configuration combinations to obtain valid assembly configuration combinations, the assembly BOM file can be output. Based on the valid configuration combinations, all functional feature codes are concatenated with &, -, and / to generate functional feature code combinations, and the assembly part number (serial number), part name, area location code, and part quantity are output sequentially in the BOM file. Table 6 shows the core information for generating the assembly BOM file.

[0045] Table 6

[0046] The knowledge base is used to determine the sub-part information corresponding to the assembly. First, the assembly BOM file is parsed to confirm the functional feature codes of each assembly. Table 7 below shows the parsed information of each assembly BOM file: Table 7

[0047] Then, the knowledge base is traversed to identify the sub-part types and function location codes corresponding to the functions of each assembly, as shown in Table 8, to match the sub-part types and function location codes.

[0048] Table 8

[0049] Figure 3 This is a flowchart illustrating the output of a sub-part BOM file in one embodiment of this application, as follows: Figure 3 As shown, based on the combination of functional feature codes of the assembly, the functional relationship between different sub-parts and the assembly is automatically established, and a sub-part BOM file containing the sub-part number, part name, area location code, part quantity, and the corresponding assembly part number of the sub-part is generated. Table 9 below shows the establishment of the functional relationship between sub-parts and the assembly, and Table 10 shows the output sub-part BOM file.

[0050] Table 9

[0051] Table 10

[0052] Finally, output a BOM file containing information on the assembly components and their corresponding sub-parts.

[0053] In this application, the default part number is a serial number. During product development, engineers need to reuse existing part numbers for parts with the same function to reduce the workload of repeated design and release. Therefore, a part reuse function can be added. Based on the knowledge base, it can automatically recommend existing part numbers of other projects under development or in production. For example, it can automatically recommend heating pad backrests of other projects and related BOM information (such as part number, part name, regional location code, and project codes). When an engineer determines that the heating pad backrest of a certain car model is the same as the heating pad backrest of another car model and can share a part number, he can click on the corresponding part to complete the reuse of that part.

[0054] The beneficial effects of this application are as follows: When receiving a selection operation for a product planning document, this application loads the product planning document; when receiving a selection operation for a specific release module in the product planning document, it determines the functional feature code corresponding to the release module through the product planning document; it determines the assembly combination matching the functional feature code through the product planning document; it determines the sub-part information corresponding to the assembly combination through the knowledge base; and it outputs a BOM file containing the assembly combination and corresponding sub-part information. Since this application can determine the corresponding functional feature code and matching assembly combination based on the selection operation for a specific release module in the product planning document, and determine the BOM structure of the corresponding sub-parts, and then output the final BOM file containing assembly and sub-part information, engineers do not need to manually interpret the configuration options and constraints related to the functional feature codes in the product planning document based on experience, thus improving the efficiency of building automotive assembly and sub-part BOM files.

[0055] In one embodiment, step S101 above can be implemented as follows: Automatically extract and parse the functional feature codes, configuration options, and constraints in the product planning document to define the distribution matrix of project product functions, technical parameters, and market requirements across various vehicle models.

[0056] In one embodiment, step S103 above can be implemented as steps A1-A3 as follows: In step A1, obtain the distribution matrix of configuration options and constraints for each functional feature code in the product planning document; In step A2, invalid configuration combinations are parsed and filtered based on the configuration options and constraint distribution matrix; In step A3, the remaining assemblies after filtering out invalid configuration combinations are determined to be valid assembly configuration combinations.

[0057] In one embodiment, the method may also be implemented as follows: Based on the user's selection of the release module and release scheme, the system automatically associates all assembly part types and corresponding functional feature codes within the module, and provides the user with a visual function list in a tree structure.

[0058] In one embodiment, step S104 above can be implemented as steps B1-B3 as follows: In step B1, the assembly BOM file is parsed to confirm the functional characteristic codes of each assembly; In step B2, the knowledge base is traversed to identify the sub-part types and function location codes corresponding to the functions of each assembly; In step B3, based on the combination of functional feature codes of the assembly, the functional relationship between different sub-parts and the assembly is automatically established, and a sub-part BOM file containing sub-part number, part name, area location code, part quantity and the assembly part number corresponding to the sub-part is generated.

[0059] In one embodiment, the method may also be implemented as follows: C1-C2: In step C1, historical project data for different vehicle models and release schemes within the enterprise are collected; In step C2, a knowledge base is constructed based on the historical project data.

[0060] In one embodiment, step C2 above can be implemented as steps C21-C22: In step C21, the collected data is cleaned and preprocessed to remove duplicate, erroneous, or incomplete information and improve data quality. In step C22, the vehicle is divided into multiple modules based on the functions of the components and the assembly process. Each module is assigned a unique code, and the association between the module code and the design release schemes of the assembly parts and sub-parts within that module is established to form a module-level design release knowledge base with universality and versatility. The design release scheme includes the binding relationship between assembly part types, area location codes, and functional feature codes, as well as the binding relationship between different sub-part types, area location codes, and assembly functional feature codes.

[0061] Figure 4 This is a schematic diagram of the structure of a BOM configuration device according to an embodiment of this application, as shown below. Figure 4 As shown, it includes: The loading unit 401 is used to load the product planning document when a selection operation for the product planning document is received; The first determining unit 402 is used to determine the functional feature code corresponding to the release module through the product planning document when a selection operation for a specific release module in the product planning document is received. The second determining unit 403 is used to determine the assembly combination that matches the functional feature code through the product planning document; The third determining unit 404 is used to determine the sub-part information corresponding to the assembly through a knowledge base; Output unit 405 is used to output a BOM file containing information on the assembly of components and corresponding sub-parts.

[0062] In one embodiment, the loading unit is further configured to: Automatically extract and parse the functional feature codes, configuration options, and constraints in the product planning document to define the distribution matrix of project product functions, technical parameters, and market requirements across various vehicle models.

[0063] In one embodiment, the second determining unit includes: The sub-unit is used to obtain the distribution matrix of configuration options and constraints for each functional feature code in the product planning document. The first parsing subunit is used to parse and filter invalid configuration combinations based on the configuration option and constraint condition distribution matrix; The sub-unit is used to determine the remaining assemblies after filtering out invalid configuration combinations as valid assembly configuration combinations.

[0064] In one embodiment, the apparatus further includes: The association unit is used to automatically associate all assembly part types and corresponding functional feature codes within the module based on the user's selection of the release module and release scheme, and provide the user with a visual function list in a tree structure.

[0065] In one embodiment, the third determining unit includes: The second parsing subunit is used to parse the assembly BOM file to confirm the functional characteristic codes of each assembly. Traverse sub-units to traverse the knowledge base to identify the sub-part types and function location codes corresponding to the functions of each assembly; Sub-units are created to automatically establish the functional relationships between different sub-parts and assemblies based on the combination of functional feature codes of assemblies, and to generate a sub-part BOM file containing sub-part numbers, part names, area location codes, part quantities, and the corresponding assembly part numbers of the sub-parts.

[0066] In one embodiment, the apparatus further includes: The collection unit is used to collect historical project data for different vehicle models and release schemes within the enterprise. A building unit is used to build a knowledge base based on the historical project data.

[0067] In one embodiment, the building unit includes: The preprocessing subunit is used to clean and preprocess the collected data to remove duplicate, erroneous, or incomplete information and improve data quality. Sub-units are used to divide the vehicle into multiple modules based on the functions of the components and the assembly process. Each module is assigned a unique code, and the relationship between the module code and the design release schemes of the assembly parts and sub-parts within the module is established to form a module-level design release knowledge base with universality and versatility. The design release scheme includes the binding relationship between assembly part types, area location codes, and functional feature codes, as well as the binding relationship between different sub-part types, area location codes, and assembly functional feature codes.

[0068] Figure 5 This is a schematic diagram of the hardware structure of a BOM configuration system according to an embodiment of this application, as shown below. Figure 5 As shown, this BOM configuration system includes: At least one processor 520; and, Memory 504 communicatively connected to the at least one processor 520; wherein, The memory 504 stores instructions that can be executed by the at least one processor 520 to implement the BOM configuration method described in any of the above embodiments.

[0069] Reference Figure 5 The BOM configuration system 500 may include one or more of the following components: processing component 502, memory 504, power supply component 506, input / output (I / O) interface 508, sensor component 510, and communication component 512.

[0070] Processing component 502 typically controls the overall operation of BOM configuration system 500. Processing component 502 may include one or more processors 520 to execute instructions to complete all or part of the steps of the methods described above. Furthermore, processing component 502 may include one or more components to facilitate interaction between processing component 502 and other components. The processor 520 may be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor.

[0071] Memory 504 is configured to store various types of data to support the operation of BOM configuration system 500. Examples of this data include instructions for any application or method operating on BOM configuration system 500. Memory 504 may be an internal storage unit of the terminal device, such as the terminal device's hard disk or memory. Memory 504 may also be an external storage device of the terminal device, such as a plug-in hard disk equipped on the terminal device. Memory 504 may be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk. Memory 504 is used to store programs and data required by this application. Memory 504 may also be used to temporarily store data that has been output or will be output.

[0072] Power supply component 506 provides power to the various components of BOM configuration system 500. Power supply component 506 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power for BOM configuration system 500.

[0073] I / O interface 508 provides an interface between processing component 502 and peripheral interface modules, such as keyboards, click wheels, buttons, etc.

[0074] Sensor assembly 510 includes one or more sensors for providing status assessments of various aspects of the BOM configuration system 500. Additionally, sensor assembly 510 can detect the on / off state of the BOM configuration system 500, the relative positioning of components, and the operational status of the BOM configuration system 500 or a component of the BOM configuration system 500. In some embodiments, sensor assembly 510 may include an accelerometer, gyroscope, magnetometer, pressure sensor, or temperature sensor, etc.

[0075] Communication component 512 is configured to enable BOM configuration system 500 to provide wired or wireless communication capabilities with other devices and cloud platforms. BOM configuration system 500 can access wireless networks based on communication standards, such as WiFi, 2G, or 3G, or combinations thereof. In one exemplary embodiment, communication component 516 receives broadcast signals or broadcast-related information from an external broadcast management system via a broadcast channel. In one exemplary embodiment, communication component 516 also includes a near-field communication (NFC) module to facilitate short-range communication. For example, the NFC module may be implemented based on radio frequency identification (RFID) technology, Infrared Data Association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.

[0076] In an exemplary embodiment, the BOM configuration system 500 may be implemented by one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic components to perform the BOM configuration method described in any of the above embodiments.

[0077] This application also provides a computer-readable storage medium, which, when the instructions in the storage medium are executed by a processor corresponding to the BOM configuration system, enables the BOM configuration system to implement the BOM configuration method described in any of the above embodiments.

[0078] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product implemented on one or more computer-usable storage media (including, but not limited to, disk storage and optical storage) containing computer-usable program code.

[0079] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart... Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0080] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0081] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0082] Obviously, those skilled in the art can make various modifications and variations to this application without departing from the spirit and scope of this application. Therefore, if such modifications and variations fall within the scope of the claims of this application and their equivalents, this application also intends to include such modifications and variations.

Claims

1. A BOM configuration method, characterized in that, include: When a selection action for the product planning document is received, the product planning document is loaded. When a selection operation for a specific release module in the product planning document is received, the functional feature code corresponding to the release module is determined through the product planning document. The product planning document determines the assembly combinations that match the aforementioned functional feature codes; The sub-part information corresponding to the assembly is determined using a knowledge base; Output a BOM file containing information on the assembly components and their corresponding sub-parts.

2. The method as described in claim 1, characterized in that, The loading of the product planning document includes: Automatically extract and parse the functional feature codes, configuration options, and constraints in the product planning document to define the distribution matrix of project product functions, technical parameters, and market requirements across various vehicle models.

3. The method as described in claim 1, characterized in that, The step of determining the assembly combination that matches the functional feature code through the product planning document includes: Obtain the distribution matrix of configuration options and constraints for each functional feature code in the product planning document; Invalid configuration combinations are parsed and filtered based on the configuration options and constraint distribution matrix. The remaining assemblies after filtering out invalid configuration combinations are determined as valid assembly configuration combinations.

4. The method according to claim 1, further comprising: Based on the user's selection of the release module and release scheme, the system automatically associates all assembly part types and corresponding functional feature codes within the module, and provides the user with a visual function list in a tree structure.

5. The method according to claim 1, wherein determining the sub-part information corresponding to the assembly through a knowledge base includes: Analyze the assembly BOM file to identify the functional characteristic codes of each assembly; Traverse the knowledge base to identify the sub-part types and function location codes corresponding to the functions of each assembly; Based on the combination of functional feature codes of the assembly, the functional relationship between different sub-parts and the assembly is automatically established, and a sub-part BOM file containing sub-part number, part name, area location code, part quantity and the corresponding assembly part number of the sub-part is generated.

6. The method according to claim 1, further comprising: Collect historical project data for different vehicle models and release plans within the company; A knowledge base is built based on the historical project data.

7. The method as described in claim 6, characterized in that, The construction of the knowledge base based on the historical project data includes: The collected data is cleaned and preprocessed to remove duplicate, erroneous, or incomplete information, thereby improving data quality. Based on the functions of components and assembly processes, the vehicle is divided into multiple modules, each module is assigned a unique code, and the relationship between the module code and the design release schemes of the assembly parts and sub-parts within the module is established to form a module-level design release knowledge base with universality and versatility. The design release scheme includes the binding relationship between assembly part types, area location codes, and functional feature codes, as well as the binding relationship between different sub-part types, area location codes, and assembly functional feature codes.

8. A BOM configuration device, characterized in that, include: A loading unit is used to load the product planning document when a selection operation for the product planning document is received; The first determining unit is used to determine the functional feature code corresponding to the release module through the product planning document when a selection operation for a specific release module in the product planning document is received. The second determining unit is used to determine the assembly combination that matches the functional feature code through the product planning document; The third determining unit is used to determine the sub-part information corresponding to the assembly through a knowledge base; The output unit is used to output a BOM file containing information on the assembly of components and corresponding sub-parts.

9. A BOM configuration system, characterized in that, include: At least one processor; as well as, A memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor to implement the BOM configuration method as described in any one of claims 1-7.

10. A computer-readable storage medium, characterized in that, When the instructions in the storage medium are executed by the processor corresponding to the BOM configuration system, the BOM configuration system is able to implement the BOM configuration method as described in any one of claims 1-7.

Images