System, method, and apparatus for auditing a vehicle component assembly list

Abstract

This application discloses a system, method, and apparatus for reviewing a vehicle component list, relating to the automotive field. The system includes a first client, a data server, and a second client. The first client obtains a first component list and a configuration requirement table; determines target configuration information based on feature codes in the configuration requirement table, and obtains a second component list; sends the second component list to the data server; upon receiving a review instruction from the second client, reviews the target configuration information in the second component list and generates a first review result; sends the first review result and the second component list to the second client; the second client determines a target component list based on the first review result and the second component list, and sends the target component list to the data server; the data server receives and stores the target component list. This improves the accuracy of data in the component list and the efficiency of the review process.

Description

Technical Field

[0001] This application relates to the automotive field, and in particular to a system, method, and apparatus for reviewing a vehicle component list. Background Technology

[0002] A Bill of Materials (BOM) is a document that describes the structure of a product in a data format. It is used to assist in a company's production management and requires that the BOM be complete and accurate. The component list of vehicle parts forms the basis of the data in the BOM.

[0003] In related technologies, the component list contains a lot of data. The component list data is collected manually by professionals who collect component list data for different vehicle parts and then summarize the different component list data.

[0004] Manual data collection is prone to errors and omissions, resulting in poor completeness and disorganized information in the vehicle parts and components list, leading to low work efficiency. Furthermore, the lack of standardized review and verification of the component list data results in low accuracy, impacting the completeness and accuracy of the overall vehicle bill of materials. Summary of the Invention

[0005] This application provides a system, method, and apparatus for reviewing a vehicle component list, which can improve the accuracy of data in the component list and the efficiency of the review process. The technical solution is as follows:

[0006] On the one hand, a system for reviewing a vehicle parts and components list is provided, the system including a first client, a data server, and a second client;

[0007] The first client is configured to: obtain a first component list, which includes component configuration information corresponding to the vehicle component; obtain a configuration requirement table, which contains feature codes corresponding to the feature description information of the vehicle component, the feature description information including the material and function of the vehicle component; determine target configuration information based on the feature codes; and obtain a second component list based on the first component list and the target configuration information, the target configuration information representing the type of vehicle corresponding to the vehicle component; and send the second component list to the data server.

[0008] The data server is configured to receive the second component list; upon receiving an audit instruction from the second client, audit the target configuration information in the second component list and generate a first audit result, the first audit result being used to correct the type configuration of the vehicle; and send the first audit result and the second component list to the second client.

[0009] The second client is configured to receive the first review result and the second component list; determine a target component list based on the first review result and the second component list, and send the target component list to the data server, wherein the target component list is used to represent the relevant parameters of the vehicle component;

[0010] The data server is also used to receive and store the list of target components.

[0011] On the other hand, a method for reviewing a vehicle component list is provided, the method comprising:

[0012] The system receives a second component list sent by a first client. The second component list is a component list generated by the first client based on the first component list. The first component list includes component configuration information corresponding to the vehicle components.

[0013] Upon receiving an audit instruction from the second client, the target configuration information in the second component list is audited, and a first audit result is generated. The target configuration information is used to indicate the type of vehicle corresponding to the vehicle component, and the first audit result is used to correct the type configuration of the vehicle.

[0014] Send the first audit result and the second component list to the second client;

[0015] Receive and store the target component list sent by the second client, the target component list being used to represent the relevant parameters of the vehicle components.

[0016] On the other hand, a device for reviewing a vehicle component list is provided, the device comprising:

[0017] The receiving module receives a second component list sent by a first client. The second component list is a component list generated by the first client based on the first component list. The first component list includes component configuration information corresponding to the vehicle components.

[0018] Upon receiving an audit instruction from the second client, the audit module audits the target configuration information in the second component list and generates a first audit result. The target configuration information is used to indicate the type of vehicle corresponding to the vehicle component, and the first audit result is used to correct the type configuration of the vehicle.

[0019] The sending module sends the first review result and the second component list to the second client;

[0020] The receiving module receives and stores a list of target components sent by the second client, the list of target components being used to represent the relevant parameters of the vehicle components.

[0021] On the other hand, a computer device is provided, the computer device including a processor and a memory, the memory storing at least one instruction, at least one program, code set or instruction set, the at least one instruction, the at least one program, the code set or instruction set being loaded and executed by the processor to implement the vehicle component list review method as described in any of the above embodiments of this application.

[0022] On the other hand, a computer-readable storage medium is provided, wherein at least one instruction, at least one program, code set, or instruction set is stored therein, wherein the at least one instruction, the at least one program, the code set, or the instruction set is loaded and executed by a processor to implement the vehicle component list review method as described in any of the embodiments of this application above.

[0023] On the other hand, a computer program product or computer program is provided, which includes computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the vehicle component list review method described in any of the above embodiments.

[0024] The beneficial effects of the technical solutions provided in this application include at least the following:

[0025] The vehicle component list review system provided in this application can transform the creation and review process of the component list from offline to online, ensuring the traceability of the component list generation process. Based on the review results, the system can modify the content of the component list that needs to be corrected, resulting in a more accurate component list and improving the accuracy of the data in the component list and work efficiency. Attached Figure Description

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

[0027] Figure 1 This is a schematic diagram of an implementation environment provided by an exemplary embodiment of this application;

[0028] Figure 2This is a flowchart illustrating a method for managing a vehicle component list using an exemplary embodiment of this application;

[0029] Figure 3 This is a flowchart illustrating a method for reviewing a vehicle component list using a review system provided in an exemplary embodiment of this application.

[0030] Figure 4 This is a flowchart illustrating a method for modifying the contents of a vehicle component list review system provided in an exemplary embodiment of this application.

[0031] Figure 5 This is a flowchart of a method for reviewing a vehicle component list provided in an exemplary embodiment of this application;

[0032] Figure 6 This is a schematic diagram illustrating the process of reviewing a vehicle component list provided in an exemplary embodiment of this application.

[0033] Figure 7 This is a structural block diagram of a vehicle component list review device provided in an exemplary embodiment of this application;

[0034] Figure 8 This is a structural block diagram of a vehicle component list review device provided in another exemplary embodiment of this application;

[0035] Figure 9 This is a structural block diagram of a computer device provided in an exemplary embodiment of this application. Detailed Implementation

[0036] To make the objectives, technical solutions, and advantages of this application clearer, the embodiments of this application will be described in further detail below with reference to the accompanying drawings.

[0037] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0038] The terminology used in this application is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. The singular forms “a,” “the,” and “the” used in this application and the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise. It should also be understood that the term “and / or” as used herein refers to and includes any or all possible combinations of one or more of the associated listed items.

[0039] It should be noted that the information (including but not limited to instruction information sent by the client to the server) and data (including but not limited to data used to generate component lists, such as product model data) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of related data must comply with the relevant laws, regulations and standards of the relevant countries and regions.

[0040] It should be understood that although the terms first, second, etc., may be used in this application to describe various information, this information should not be limited to these terms. These terms are only used to distinguish information of the same type from one another. For example, without departing from the scope of this application, a first parameter may also be referred to as a second parameter, and similarly, a second parameter may also be referred to as a first parameter. Depending on the context, the word "if" as used herein may be interpreted as "when," "when," or "in response to determination."

[0041] First, a brief introduction to the terms used in the embodiments of this application:

[0042] Bill of Material (BOM): A document that describes the structure of a product in a data format. It is a product structure data file that a computer can recognize. The BOM enables the system to identify the product structure and is also a link connecting and communicating various business operations of an enterprise.

[0043] A bill of materials (BOM) is a complete, formally structured list of components that describes how a product is made or assembled. The list includes a description and object number for each component, as well as the quantity and unit of measurement.

[0044] CAD (Computer-Aided Design): Utilizing computers and their graphics devices to assist designers in their work. In the design process, computers typically perform extensive calculations, analyses, and comparisons of different solutions to determine the optimal one. Various design information, whether numerical, textual, or graphical, can be stored in the computer's memory or external storage and retrieved quickly. Designers usually begin with sketches; the arduous task of converting sketches into working drawings can be handled by the computer. Computer-generated design results can be quickly rendered into graphics, allowing designers to make timely judgments and modifications. Computers can also be used for graphic data processing tasks such as editing, enlarging, reducing, translating, and rotating graphics.

[0045] Concurrent Engineering, also known as parallel engineering, is a systematic approach and technology that involves the simultaneous development of various subsystems of a product throughout the entire product development process, the simultaneous development of the product with processes and tooling, and the simultaneous planning of the product with quality objectives. It enables developers to consider the interfaces and requirements of other subsystems from the initial concept stage, the level and capabilities of subsequent processes and tooling, and the requirements for achieving quality objectives. In other words, it is a system approach and technology that takes into account all factors (including quality, cost, schedule, and user requirements) throughout the entire product lifecycle during development.

[0046] In the development and management of the entire vehicle product lifecycle, virtual synchronous engineering verification based on the vehicle product CAD BOM (Carry-on-Material) data plays a crucial role. The completeness, accuracy, and timeliness of the vehicle product CAD BOM data determine whether the synchronous engineering analysis structure is correct and updated in a timely manner. The component list is a vital input for realizing the vehicle CAD BOM data and is the foundation for rapid response to all applications and services based on the vehicle CAD BOM data. The component list is a parts list for the configuration and usage layer.

[0047] In related technologies, the management method for component lists is traditional manual data collection. During the production process of vehicle components, the data in the CAD BOM of the complete vehicle product changes frequently, requiring a high degree of accuracy in the component list information. However, the manual data collection process is prone to inaccurate and incomplete entries, resulting in chaotic data. This causes relevant personnel to spend a lot of time sorting, summarizing, and analyzing the accuracy of the information, and makes it difficult to trace the information later.

[0048] This application provides a vehicle component list review system that enables multiple users to edit the component list online and review it in a timely manner, submitting the review process layer by layer, and finally obtaining a highly accurate and complete component list. This saves the step of summarizing the component list and improves the management efficiency and quality of vehicle component lists.

[0049] Secondly, the implementation environment involved in the embodiments of this application will be described, for illustrative purposes only. Please refer to [the relevant documentation]. Figure 1 It illustrates a schematic diagram of an implementation environment provided by an exemplary embodiment of this application, such as... Figure 1 As shown, the implementation environment includes a first client 100, a data server 110, and a second client 120; wherein, the first client 100 and the data server 110 are connected through a communication network 130, and the second client 120 and the data server 110 are connected through a communication network 130.

[0050] Among them, data server 110 corresponds to the auditing platform for the vehicle parts and components list.

[0051] The first client 100 acquires product digital model data and generates a corresponding first component list based on the product digital model data. The product digital model data is generated by 3D modeling of vehicle components. The first client 100 then acquires a configuration requirement table, which contains feature codes corresponding to the feature description information of the vehicle components. The feature description information includes the material and function of the vehicle components. Based on the feature codes, the first client 100 determines the target configuration information and obtains a second component list based on the first component list and the target configuration information. The target configuration information indicates the type of vehicle corresponding to the vehicle component.

[0052] The first client 100 sends the second component list to the data server 110, and the data server 110 receives and stores the second component list.

[0053] The second client 120 sends an audit instruction to the data server 110, instructing the data server 110 to audit the target configuration information in the second component list and generate a first audit result.

[0054] Data server 110 sends the first audit result and the second component list to the second client 120. Based on the first audit result, the second client 120 corrects the vehicle type configuration in the second component list to obtain the target component list, which is used to represent the relevant parameters of the parts in the vehicle components.

[0055] If the first review result indicates a match, the second client 120 directly determines the second component list as the target component list; if the first review result indicates a mismatch, the second client 120 corrects the mismatches in the second component list based on the information in the first review result, and determines the corrected second component list as the target component list.

[0056] The second client 120 sends the target component list to the data server 110, and the data server 110 receives and stores the target component list.

[0057] Other clients can download the target component list from data server 110 for use in subsequent production processes.

[0058] It is worth noting that the product model data obtained by the first client 100 may be generated by other clients and sent to the first client 100 by other clients, or it may be product model data generated by the first client 100. This embodiment does not limit this.

[0059] The first client 100 and the second client 120 can be implemented as terminals, including but not limited to at least one of the following terminals: smartphones, tablets, portable laptops, desktop computers, smart speakers, smart wearable devices, smart voice interaction devices, and smart home appliances.

[0060] It is worth noting that the aforementioned communication network 130 can be implemented as a wired network or a wireless network, and the communication network 130 can be implemented as any one of a local area network, a metropolitan area network, or a wide area network. This application embodiment does not limit this.

[0061] It is worth noting that the aforementioned data server 110 can be an independent physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud security, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, content delivery networks (CDN), and big data and artificial intelligence platforms.

[0062] Cloud technology refers to a hosting technology that unifies hardware, software, and network resources within a wide area network (WAN) or local area network (LAN) to achieve data computation, storage, processing, and sharing. Based on the cloud computing business model, cloud technology encompasses network technology, information technology, integration technology, management platform technology, and application technology. It can form resource pools, providing flexible and convenient on-demand access. Cloud computing technology will become a crucial support. Backend services of technical network systems require substantial computing and storage resources, such as video websites, image websites, and many portal websites. With the rapid development and application of the internet industry, every item may have its own identification mark in the future, requiring transmission to backend systems for logical processing. Data at different levels will be processed separately, and various industry data will require robust system support, which can only be achieved through cloud computing.

[0063] In some embodiments, the data server 110 described above can also be implemented as a node in a blockchain system. Blockchain is a novel application model of computer technologies such as distributed data storage, peer-to-peer transmission, consensus mechanisms, and cryptographic algorithms. Essentially, a blockchain is a decentralized database, a chain of data blocks linked together using cryptographic methods. Each data block contains information about a batch of network transactions, used to verify the validity of the information (anti-counterfeiting) and generate the next block. A blockchain can include a blockchain underlying platform, a platform product service layer, and an application service layer.

[0064] Based on the above-described terminology and application scenarios, the vehicle component list review system provided in this application embodiment will be described. This system includes a first client 210, a second client 220, and a data server 230, wherein the data server 230 corresponds to the vehicle component list review platform. Please refer to... Figure 2 , Figure 2 This is a flowchart of a method for managing a vehicle component list through an auditing system, which includes the following steps.

[0065] S211, the first client obtains the product model data and generates the corresponding first component list based on the product model data.

[0066] Product model data refers to data generated from 3D modeling of vehicle components. Types of product model data include, but are not limited to:

[0067] (1) Model Name: The name of a single object used to indicate the name of the vehicle component; (2) Model Number: The ID number of a single object used to uniquely identify the number of the vehicle component; (3) Owner: The person who owns the model data of the vehicle component; (4) First Applicable Model: The model of the first vehicle to which the vehicle component is applicable; (5) Product Architecture Group: The group to which the vehicle component belongs in the overall vehicle function group, etc.

[0068] The first component list is a list of components obtained after organizing the product's digital model data. It is used to represent the relevant parameters of the vehicle component and includes the component configuration information corresponding to the vehicle component.

[0069] Optionally, taking a vehicle seat as an example, the first component list of the vehicle seat is presented in tabular form, as shown in Table 1 below. Table 1 is the first component list of the vehicle seat.

[0070] Table 1

[0071]

[0072] Table 1 includes, but is not limited to, the following data: (1) vehicle model, i.e., the vehicle model for which it is first applied; (2) architecture group code, i.e., product architecture group; (3) digital model number; (4) name, i.e., digital model name; (5) feature code: the feature information of vehicle parts expressed in the form of a code, etc.

[0073] The first client obtains product model data in the following ways, including but not limited to: (1) Obtain product model data from other clients: Other clients have applications that support three-dimensional modeling of vehicle parts installed on them. After successful modeling by other clients, product model data is generated and sent to the first client; (2) The first client performs three-dimensional modeling of vehicle parts and generates corresponding product model data.

[0074] In some embodiments, in addition to creating a new table for filling in product model data as shown in the example above, the first client can also generate the first component list by selecting a preset component list as a framework from a pre-prepared list of candidate components, filling in the product model data into the preset component list, and thus obtaining the first component list.

[0075] At this point, some data from the product's numerical model data can be used as matching parameters. For example, matching parameters may include at least one of the following: the applicable vehicle type for the vehicle component, or the product architecture group. These matching parameters are used to select a preset list of components suitable for the vehicle component from the candidate component list. The specific process is as follows.

[0076] The first client obtains a list of candidate components, which includes at least one list of preset components. The list of preset components contains multiple parameter options that have not been populated with data, corresponding to the parameter types contained in the product model data.

[0077] Based on matching parameters, the first client determines a preset list of components that meet the type matching requirements from the candidate component list. The type matching requirements refer to the matching of vehicle type and product architecture groupings in the preset component list with the product model data. The first client then determines the product data within the preset component list that meets the type matching requirements based on the product model data, thus obtaining the first component list.

[0078] Optionally, the candidate component list includes three preset component lists: (1) Component list A, vehicle type X1, product architecture group 40.02.01; (2) Component list B, vehicle type X1, product architecture group 40.02.02; (3) Component list C, vehicle type X2, product architecture group 40.02.01.

[0079] If the vehicle type in the product model data is X1 and the product architecture group is 40.02.01, then component list A meets the type matching requirements. Select component list A, fill in the data for component list A based on the product model data, and obtain the first component list.

[0080] S212, the first client obtains the configuration requirements table.

[0081] The configuration requirements table contains feature codes corresponding to the feature description information of vehicle components, including the material and function of the vehicle components.

[0082] In step S211 above, the obtained first component list also includes other parameters for which no data has been filled in, such as configuration information, which refers to the configuration of the vehicle to which the vehicle component is applicable. The feature codes contained in the configuration requirements table are used to provide a reference for supplementing the data not filled in in the first component list. For illustration, see Table 2 below, which is the configuration requirements table for vehicle seats.

[0083] Table 2

[0084]

[0085] Table 2 includes, but is not limited to, the following data: (1) Professional department: the department to which the technician responsible for designing the vehicle component belongs; (2) Classification: the type of the vehicle component; (3) Feature description: in the early stages of designing the vehicle component, the relevant personnel are not clear about the design details of the product and need to express the features of the vehicle component through descriptive language; (4) Feature code: the feature information of the vehicle component in the form of a code; (5) the configuration information corresponding to the feature code, such as: configuration 1, configuration 2 and configuration 3, the configuration of the vehicle to which the vehicle component is applicable; In Table 2, the column of configuration information corresponding to the specified feature code is marked with black dots. The method of marking with black dots is also called dotting, which is used to indicate the correspondence between the feature code and the configuration information.

[0086] The vehicle configurations mainly include the following:

[0087] 1. Base model: The vehicle lacks leather seats, power windows and doors, and many electronic control functions;

[0088] 2. Standard configuration: It has all the electric controls that a normal vehicle should have, such as power windows, power steering, air conditioning, etc.

[0089] 3. Mid-range vehicle: More advanced than the standard vehicle, it not only has all the functions of the standard vehicle, but in some cases, it adds multiple airbags, sunroof, leather seats, power seats, seat heating and other equipment or functions on the basis of the standard vehicle;

[0090] 4. High-end model: This model is higher than the three configurations mentioned above and can be considered the flagship model of this vehicle. It has a better appearance and functions, such as wheels, tires, and logos.

[0091] It is worth noting that the contents included in the above configuration requirements table, the list of different types of components, and the product model data can be arbitrary, including but not limited to the contents used as examples above, and this embodiment does not limit them.

[0092] S213, the first client determines the target configuration information based on the feature code, and obtains the second component list based on the first component list and the target configuration information.

[0093] The target configuration information indicates the type of vehicle to which the vehicle component corresponds.

[0094] Table 1 also includes a candidate configuration list, which contains at least one type of configuration information, namely, a list of configuration information such as Configuration 1, Configuration 2, and Configuration 3 that are not yet marked with black dots. To distinguish between the feature codes in the first component list and the feature codes in the configuration requirement table, the feature codes in the first component list will be referred to as the first feature code and the feature codes in the configuration requirement table as the second feature code. The first feature code is used to determine the target configuration information from the candidate configuration list.

[0095] The first client determines the second feature code corresponding to the feature description information in the configuration requirement table; based on the matching result of the second feature code and the first feature code, it determines the configuration information that meets the configuration matching requirements from the candidate configuration list as the target configuration information; and obtains the second component list based on the target configuration information.

[0096] The configuration matching requirement means that the first feature code contains the second feature code.

[0097] Optionally, the first feature code is BM00 & DF00, and the second feature code includes the following:

[0098] (1)BM00: The corresponding configuration information is configuration 1 and configuration 2;

[0099] (2)BM01: The corresponding configuration information is configuration 3;

[0100] (3)DF00: The corresponding configuration information is configuration 1;

[0101] (4)DF01: The corresponding configuration information is configuration 2 and configuration 3;

[0102] Therefore, the target configuration information corresponding to BM00&DF00 is the configuration information that BM00 and DF00 possess simultaneously, that is: configuration 1, so the target configuration information is configuration 1.

[0103] Following the steps above, determine the target configuration information corresponding to each first feature code. In the first component list, mark the target configuration information with black dots to obtain the second component list.

[0104] S214, the first client sends the list of the second components to the data server.

[0105] S231, the data server receives the second component list.

[0106] S232, Upon receiving the audit instruction sent by the second client, the data server audits the target configuration information in the second component list and generates the first audit result.

[0107] The first review result is used to correct the vehicle's type and configuration.

[0108] In some embodiments, after receiving the second component list, the data server automatically sends a prompt message to the second client to notify the second client that it has received the second component list and can begin to review it. The second client sends a review instruction to the data server based on the prompt message, and the data server reviews the target configuration information in the second component list based on the review instruction.

[0109] The data server may also automatically review the target configuration information in the second component list after receiving it; or, after receiving the second component list, the data server may store the second component list locally, and the second client may actively retrieve the status of the component list stored in the data server and then send a review instruction to the data server. This embodiment does not limit this.

[0110] S233, the data server sends the first audit result and the second component list to the second client.

[0111] S221, the second client receives the first audit result and the second component list.

[0112] S222, the second client determines the target component list based on the first audit result and the second component list, and sends the target component list to the data server.

[0113] The target component list is used to represent the relevant parameters of vehicle parts.

[0114] The information included in the first audit result is as follows:

[0115] (1) Match / No Match;

[0116] (2) When the first audit result shows a mismatch, it also includes the type of mismatch and the method of correcting the vehicle type configuration in the second component list. If the first audit result is "matched", the second component list is directly determined as the target component list; if the first audit result is "mismatched", the type configuration of the vehicles in the second component list is corrected based on the "type of mismatch and method of correcting the vehicle type configuration in the second component list" in the first audit result, and the corrected second component list is determined as the target component list.

[0117] S234, The data server receives and stores the list of target components.

[0118] Then, other clients can obtain the list of target components from the data server for subsequent processes.

[0119] In summary, the vehicle component list review system provided in this application can shift the creation and review process of the component list from offline to online, ensuring the traceability of the component list generation process. Based on the review results, the system can modify the content of the component list that needs to be corrected, resulting in a more accurate component list and improving the accuracy of the data in the component list and work efficiency.

[0120] The system provided in this embodiment can find a preset list of components that meet the type matching requirements based on the matching parameters in the product digital model data, and use the preset list of components as the basis for generating the first list of components, which can improve the efficiency of generating the first list of components.

[0121] The system provided in this embodiment finds target configuration information that meets the configuration matching requirements by matching the first feature code in the first component list and the second feature code in the configuration requirement table. The target configuration information is then filled into the first component list to obtain the second component list, which improves the accuracy of the target configuration information and the efficiency of the work.

[0122] The process by which the data server reviews the target configuration information in the second component list and generates the first review result primarily relies on binary AND operation logic. To ensure the accuracy of the data in the second component list, in addition to reviewing the target configuration information, other content in the second component list can also be reviewed. For example... Figure 3 As shown, Figure 3 This is a flowchart of a method for a vehicle component list review system to review the component list. This method is jointly executed by the second client 320 and the data server 330, and includes the following steps.

[0123] S331, Upon receiving the audit instruction sent by the second client, the data server converts the first feature code into a first matching number and the second feature code into a second matching number.

[0124] The first matching number is a binary number, and the second matching number is also a binary number.

[0125] Since the first feature code contains at least one second feature code, the first match number corresponds to at least one second match number.

[0126] For illustrative purposes, please refer to Table 3, which is a list of the second components of the vehicle seats.

[0127] Table 3

[0128]

[0129] Optionally, in Table 3, the first feature code includes: BM00&DF00, BM00&DF01, and BM01, with configuration information 1 as an example.

[0130] For illustrative purposes, please refer to Table 4, which is another configuration requirement table for vehicle seats.

[0131] Table 4

[0132]

[0133] Optionally, in Table 4, the second feature code includes: BM00, BM01, DF00, DF01, with configuration information 1 as an example.

[0134] For illustration, please refer to Table 5, which is a table of conversion rules for converting the second feature code into the second match number.

[0135] Table 5

[0136]

[0137] Optionally, in Table 4, configuration information is used as an example for configuration 1.

[0138] In the second feature codes, BM00 and DF00 are marked with black dots to indicate that they are selected. Therefore, the second feature codes BM00 and DF00 are converted to binary numbers 1, and the second feature codes DF01 and BM01 are converted to binary numbers 0. Thus, the second matching numbers corresponding to the second feature codes BM00, BM01, DF00, and DF01 are 1, 0, 1, and 0, respectively.

[0139] Based on the above rules, the first feature code in Table 3 is converted.

[0140] In the second feature code, BM00&DF00 and BM01 are marked with black dots to indicate that they are selected and converted to binary number 1; BM00&DF01 is converted to binary number 0. Therefore, the first matching numbers corresponding to the first feature codes BM00&DF00, BM00&DF01, and BM01 are 1, 0, and 1, respectively.

[0141] S332, the data server performs a binary AND operation between at least one second matching number to obtain the result.

[0142] The result of the operation is a binary number.

[0143] The first feature code BM00&DF00 corresponds to BM00 and DF00 in the second feature code. Perform a binary AND operation, BM00&DF00=1&1=1, the result of which is 1, and should be marked with a black dot.

[0144] The first feature code BM00&DF01 corresponds to BM00 and DF01 in the second feature code. Perform a binary AND operation, BM00&DF01=1&0=0, the result of the operation is 0, and no mark is made.

[0145] The first feature code BM01 corresponds to BM01 in the second feature code. The result of the operation is 0, so it is not marked.

[0146] S333, the data server generates the first review result based on the calculation result and the first matching number.

[0147] When the calculation result is the same as the first matching number, the first review result is considered a match.

[0148] For illustration, please refer to Table 6, which is a comparison table of the calculation results and the first matching number.

[0149] Table 6

[0150]

[0151] The first audit result indicates that the first matching number corresponding to the first feature code BM01 is inconsistent with the calculation result. Therefore, the configuration information in Table 3 corresponding to the first feature code BM01 is incorrect, i.e., it does not match, and should be "Configuration 1 not selected".

[0152] S334, the data server sends the first review result to the second client.

[0153] S321, if the first audit result indicates a mismatch, the second client corrects the second component list based on the first audit result to obtain the third component list.

[0154] When the calculation result is different from the first matching number, the first review result is indicated as a mismatch.

[0155] Optionally, based on the first audit result, the selection status of the configuration information in the second component list is corrected. Then, in the corrected third component list, the configuration information corresponding to the first feature code BM01 is "Unselected Configuration 1".

[0156] S322, the second client uses the third component list as the target component list and sends the target component list to the data server.

[0157] S323, the second client obtains the list of required components.

[0158] The mandatory parts list is a list of parts that must be installed in a vehicle, including at least one mandatory part, which is also a vehicle component. For example, the vehicle's seats and steering wheel are mandatory parts, used to enable the vehicle to move; the vehicle's ambient lighting and navigation system are optional parts, and a vehicle can still move even without these optional parts.

[0159] In some embodiments, the target component list may be a component list of all parts of the vehicle or a component list of at least one vehicle component in the vehicle. When the target component list is a component list of all parts of the vehicle, in order to ensure the completeness and accuracy of the target component list, the mandatory components in the target component list may also be reviewed.

[0160] When obtaining the list of essential parts, you can use the vehicle's powertrain and transmission type as selection criteria to find the essential parts list suitable for the current vehicle from the candidate list.

[0161] Among them, the power form of a vehicle refers to the form of the power source of a car. Vehicles are classified according to their power form, mainly including the following types: gasoline vehicles, hybrid vehicles, and pure electric vehicles.

[0162] A gearbox is a device used to change the speed ratio and direction of movement of a vehicle. Based on the different operating methods, it can be divided into two main categories: manual gearboxes and automatic gearboxes.

[0163] S324, the second client reviews the target component list based on the mandatory component list and generates a second review result.

[0164] The second audit result is used to correct the target component list. The information included in the second audit result is: (1) match / non-match; (2) when the second audit result shows a non-match, it also includes the type of non-match and the method of correcting the target component list.

[0165] Optionally, mismatch types include, but are not limited to, the following: (1) missing required components; (2) duplicate required components.

[0166] When the second audit result shows that a required item is missing, the second audit result also includes the type of the missing required item and the number of missing required items; when the second audit result shows that a required item is duplicated, the second audit result also includes the type of duplicate required item and the number of duplicate required items.

[0167] Alternatively, to improve the efficiency of the review process, the review of the target component list can be divided into two parts.

[0168] 1. Professional review: Review vehicle components belonging to the same profession.

[0169] In some embodiments, the target component list includes vehicle parts belonging to multiple specialties, and the target component list is reviewed in a preset order, with each specialty as a unit.

[0170] The specific implementation process uses the professional name and the digital model name of the vehicle component as matching conditions: the professional name and digital model name of the required component are used as search keywords to search for the required component in the target component list, and data such as whether the required component exists in the target component list and the quantity of the required component are obtained. Based on the data obtained from the above search, it is determined whether there are any missing or duplicate required components.

[0171] It is worth noting that the process of reviewing the target component list by professional unit can be carried out by multiple second clients, that is, by different professionals, in order to improve work efficiency.

[0172] 2. Vehicle-level audit: The list of target components is audited on a vehicle-by-vehicle basis. The steps are the same as the professional audit above.

[0173] S325, if the second client indicates a match in the second audit result, it sends the list of target components to the data server.

[0174] Optionally, if there are no missing mandatory components in the target component list, the second review result is: match (no missing or duplicate mandatory components), and the target component list is sent directly to the data server.

[0175] S326, if the second client indicates a mismatch in the second audit result, it corrects the target component list based on the second audit result to obtain a corrected target component list and sends the corrected target component list to the data server.

[0176] Optionally, if the missing mandatory component in the target component list is a vehicle seat, the second audit result will be: mismatch (mandatory component missing), the missing mandatory component is a vehicle seat, and the quantity is 2.

[0177] Then, add two vehicle seats to the target component list to obtain the corrected target component list, and send the corrected target component list to the data server.

[0178] Once the data server receives the corrected list of target components, other clients can download and use the list of target components from the data server.

[0179] In summary, the system provided in this application can automatically review the component list, submit the review process layer by layer, and finally obtain a highly accurate and complete component list. This saves the step of summarizing the component list and improves the management efficiency and quality of vehicle component applications.

[0180] The method provided in this embodiment uses binary AND operation logic to perform matching operations on the feature codes corresponding to the feature description information, thereby achieving automatic review of the component list and improving work efficiency. It obtains accurate review results, and based on these results, modifies the component list to further improve its accuracy.

[0181] The method provided in this embodiment obtains a list of required components and reviews cases where the component list contains required components, thereby ensuring the completeness of the component list, avoiding missing or duplicate required components, and improving the accuracy of the component list.

[0182] In some embodiments, there is a need to modify the contents of the component list. Changes to the component list can be made through the vehicle component list review system. In this case, the vehicle component list review system includes a third client in addition to the first client, the second client, and the data server, such as... Figure 4 As shown, Figure 4 This is a flowchart of a method for modifying the contents of a vehicle component list based on an audit system. This method is jointly executed by a third client 430 and a data server 400, and includes the following steps.

[0183] S431, the third client obtains the change information.

[0184] The change information includes the content and methods that need to be changed in the target component list.

[0185] Optionally, when the vehicle component is a vehicle seat, the material of the seat in the target component list is: genuine leather seat fabric. The change requirement for the target component list is: change the material of the seat to fabric seat fabric.

[0186] The change information includes the following: the seat material will be changed from genuine leather to fabric.

[0187] Optionally, the third client may obtain change information in the following ways: (1) receiving change information sent by other clients; (2) the professional personnel corresponding to the third client may directly generate change information based on the third client according to the change requirements.

[0188] It is worth noting that the above change information is only for example. The content included in the change information can be arbitrary, including but not limited to changes in the seat material. The client that changes the target component list can be arbitrary, that is, it can be the first client, the second client, or other clients. This embodiment does not limit this.

[0189] S432, the third client modifies the target component list based on the change information to obtain the modified component list.

[0190] Following the same steps as S431 above, the material of the seat in the component list is changed to: fabric seat fabric, and the other contents of the component list are the same as the target component list.

[0191] In some embodiments, the target component list can also be modified by the data server. The data server has an application deployed capable of modifying the contents of the target component list. The third client sends the change information to the data server and simultaneously sends a change instruction. The change instruction prompts the data server to modify the corresponding data content in the target component list according to the change information, resulting in a modified component list. This modified component list is then stored by the data server and can be downloaded and used by different clients at any time.

[0192] S433, the third client sends the list of changed components to the data server.

[0193] S401, the data server receives and stores the list of changed components.

[0194] The data server contains a dedicated database for storing component lists at different stages. This database corresponds to the vehicle component list review system proposed in this application. The database stores all data information involved in the system, such as: product model data of vehicle components, configuration requirement table, component lists at different stages, etc.

[0195] The aforementioned data can be obtained from the database and downloaded to the client for use. The database stores component lists at different stages, including but not limited to the first component list, the second component list, the target component list, and the changed component list, enabling data traceability and allowing access to historical records during the generation of the final target component list. This allows for timely retrieval of component lists from different stages when errors are discovered or adjustments are needed.

[0196] In summary, the vehicle component list review system provided in this application can also modify the already determined target component list to obtain a modified component list that better meets the actual production design requirements, thereby improving the efficiency of the modification and obtaining a component list with higher accuracy and better completeness.

[0197] Figure 5 This is a flowchart of the review method for a vehicle component list in this application, which is executed by the data server and includes the following steps.

[0198] S510 receives the second component list sent by the first client.

[0199] The second component list is a component list generated by the first client based on the product model data and the configuration requirement table. The product model data is data generated by 3D modeling of the vehicle product. The configuration requirement table contains feature codes that indicate the feature description information of the vehicle product. The feature description information includes the material and function of the vehicle product. The first component list includes the component configuration information corresponding to the vehicle parts.

[0200] S520, upon receiving an audit instruction from the second client, audits the target configuration information in the second component list and generates a first audit result.

[0201] The target configuration information is used to indicate the type of vehicle corresponding to the vehicle component, and the first review result is used to correct the vehicle type configuration.

[0202] S530 sends the first audit result and the second component list to the second client.

[0203] After receiving the first audit result and the second component list, the second client determines the target component list based on the information contained in the first audit result and the second component list, and sends the target component list to the data server.

[0204] S540 receives and stores the list of target components sent by the second client.

[0205] The target component list represents the relevant parameters of vehicle parts and can be downloaded and used by other clients.

[0206] In summary, the method provided in this application can shift the creation and review process of the component list from offline to online, ensuring the traceability of the component list generation process. Based on the review results, the content of the component list that needs to be corrected can be modified to obtain a more accurate component list, thereby improving the accuracy of the data in the component list and the efficiency of the work.

[0207] The vehicle component list review system includes a first client, a second client, and a data server. The vehicle component list review system corresponds to the review platform. During the review process, the interface of the review platform is displayed on the screens of the first and second clients, and the component list is reviewed according to the prompts on the interface. Figure 6 This is a schematic diagram illustrating the review process for the vehicle component list proposed in this application, which includes multiple steps, such as... Figure 6 As shown, the information represented by each step is as follows.

[0208] Step (601): The process begins, instructing the vehicle component list review system to execute the generation, review, and release of the component list in sequence;

[0209] Step (602): Based on the configuration requirements of vehicle components and the vehicle model project development plan, initiate the component list collection work;

[0210] Step (603): Obtain the configuration requirements table, select the preset component list from the candidate component list, which corresponds to the vehicle model to which the current vehicle component is first applied;

[0211] Step (604): Obtain product model data, create a model of vehicle parts based on 3D design software, the data corresponding to the model includes: model name, model number, owner, first applicable vehicle model, product architecture group and other attributes, and store the product model data in the database corresponding to the audit system, fill the product model data into the preset component list to obtain the first component list;

[0212] Step (605): Fill in the relevant information in the configuration requirements table into the first component list to obtain the second component list. The relevant data includes: feature description information and target configuration information;

[0213] Step (606): Send the second component list to the data server, that is, publish it on the audit platform corresponding to the audit system;

[0214] Step (607): Review the target configuration information in the second component list and generate a first review result. Determine the target component list based on the first review result and the second component list. Specifically, find matching feature description information from the configuration requirement table according to the feature description information of the digital module number, parse the feature description information and select the target configuration information, and mark it with a black dot. Review the target configuration information based on the review rules. If the first review result indicates a mismatch, correct the second component list according to the prompt information in the first review result and resubmit it for review until the first review result indicates a match. Only then can the review be passed and the target component list be determined.

[0215] Step (608): Review the completeness of the professional data in the target component list. The professional project contact person confirms the target component list within the professional field and submits it for freezing. Freezing means that the target component list cannot be modified temporarily.

[0216] Step (609): Based on the review results of step (608), determine whether to proceed to step (610). If the professional data is complete, proceed to the next step.

[0217] Step (610): Review the completeness of the vehicle data in the target component list;

[0218] Step (611): Based on the review results of step (610), determine whether to proceed to step (612). When the vehicle data is complete, the next step can be initiated.

[0219] Step (612): Confirm the final list of target components and send it to the data server, that is, publish it on the audit platform corresponding to the audit system and submit it for freezing;

[0220] Step (613): In the subsequent application step, the target component list will be sent to the weight report database for subsequent vehicle weight management.

[0221] Step (614): Process ends.

[0222] Figure 7 This is a structural block diagram of a vehicle component list review device provided in one embodiment of this application, as shown below. Figure 7 As shown, the device includes the following parts.

[0223] The receiving module 710 is used to receive a second component list sent by the first client. The second component list is a component list generated by the first client based on the first component list. The first component list includes component configuration information corresponding to the vehicle components.

[0224] The audit module 720 is used to audit the target configuration information in the second component list when it receives an audit instruction sent by the second client, and generate a first audit result. The target configuration information is used to indicate the type of vehicle corresponding to the vehicle component, and the first audit result is used to correct the type configuration of the vehicle.

[0225] The sending module 730 is used to send the first review result and the second component list to the second client;

[0226] The receiving module 710 is further configured to receive and store a list of target components sent by the second client, the list of target components being used to represent relevant parameters of the vehicle components.

[0227] In an optional embodiment, such as Figure 8 As shown, the device further includes:

[0228] The conversion module 740 is used to, upon receiving an audit instruction sent by the second client, convert a first feature code into a first matching number, wherein the first matching number is a binary number; and convert a second feature code into a second matching number, wherein the second matching number is a binary number, and the first matching number corresponds to at least one second matching number, wherein the first feature code is a feature code in the first component list that corresponds to the feature description information, and the second feature code is a feature code in the configuration requirement table that corresponds to the feature description information;

[0229] The arithmetic module 750 is used to perform a binary AND operation on at least one of the second matching numbers to obtain an operation result, wherein the operation result is a binary number.

[0230] The generation module 760 is used to generate the first review result based on the calculation result and the first matching number, wherein when the calculation result and the first matching number are the same, the first review result indicates a correct match;

[0231] The sending module 730 is further configured to send the first review result to the second client.

[0232] In an optional embodiment, the receiving module 710 is further configured to receive and store a list of changed components sent by a third client. The list of changed components is a list of components obtained by the third client by changing the target component list based on change information. The change information includes the content and method that need to be changed in the target component list.

[0233] In summary, the device provided in this application can shift the creation and review process of the component list from offline to online, ensuring the traceability of the component list generation process. Based on the review results, the content of the component list that needs to be corrected is modified to obtain a more accurate component list, thereby improving the accuracy of the data in the component list and the work efficiency.

[0234] It should be noted that the vehicle component list review device provided in the above embodiments is only an example of the division of the above functional modules. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0235] Figure 9 This illustration shows a structural block diagram of a computer device 900 provided in an exemplary embodiment of this application. The computer device 900 may be a smartphone, tablet computer, MP3 player (Moving Picture Experts Group Audio Layer III), MP4 player (Moving Picture Experts Group Audio Layer IV), laptop computer, or desktop computer. The computer device 900 may also be referred to as user equipment, portable terminal, laptop terminal, desktop terminal, or other names.

[0236] Typically, computer device 900 includes a processor 901 and a memory 902.

[0237] Processor 901 may include one or more processing cores, such as a quad-core processor or an octa-core processor. Processor 901 may be implemented using at least one hardware form selected from DSP (Digital Signal Processing), FPGA (Field-Programmable Gate Array), and PLA (Programmable Logic Array). Processor 901 may also include a main processor and a coprocessor. The main processor, also known as a CPU (Central Processing Unit), is used to process data in the wake-up state; the coprocessor is a low-power processor used to process data in the standby state. In some embodiments, processor 901 may integrate a GPU (Graphics Processing Unit), which is responsible for rendering and drawing the content to be displayed on the screen. In some embodiments, processor 901 may also include an AI processor for handling computational operations related to machine learning.

[0238] The memory 902 may include one or more computer-readable storage media, which may be non-transitory. The memory 902 may also include high-speed random access memory and non-volatile memory, such as one or more disk storage devices or flash memory devices. In some embodiments, the non-transitory computer-readable storage media in the memory 902 are used to store at least one instruction, which is executed by the processor 901 to implement the vehicle component list review method provided in the method embodiments of this application.

[0239] In some embodiments, the computer device 900 also includes other components, as those skilled in the art will understand. Figure 9 The structure shown does not constitute a limitation on terminal 900 and may include more or fewer components than shown, or combine certain components, or use different component arrangements.

[0240] Optionally, the computer-readable storage medium may include: read-only memory (ROM), random access memory (RAM), solid-state drives (SSDs), or optical discs, etc. The random access memory may include resistive random access memory (ReRAM) and dynamic random access memory (DRAM). The sequence numbers of the embodiments in this application are merely descriptive and do not represent the superiority or inferiority of the embodiments.

[0241] This application also provides a computer device, which includes a processor and a memory. The memory stores at least one instruction, at least one program, a code set, or an instruction set. The at least one instruction, the at least one program, the code set, or the instruction set is loaded and executed by the processor to implement the vehicle component list review method as described in any of the above embodiments of this application.

[0242] This application also provides a computer-readable storage medium storing at least one instruction, at least one program, code set, or instruction set, wherein the at least one instruction, the at least one program, the code set, or the instruction set is loaded and executed by a processor to implement the vehicle component list review method as described in any of the above embodiments of this application.

[0243] This application also provides a computer program product or computer program that includes computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the vehicle component list review method described in any of the above embodiments.

[0244] Those skilled in the art will understand that all or part of the steps of the above embodiments can be implemented by hardware or by a program instructing related hardware. The program can be stored in a computer-readable storage medium, such as a read-only memory, a disk, or an optical disk.

[0245] The above description is merely an optional embodiment of this application and is not intended to limit this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the protection scope of this application.

Claims

1. A system for reviewing a vehicle component list, characterized in that, The system includes a first client, a data server, and a second client; The first client is used to obtain product digital model data generated by 3D modeling of vehicle parts from other clients, or to perform 3D modeling of vehicle parts to generate corresponding product digital model data. A first component list is generated based on the product digital model data, including the component configuration information corresponding to the vehicle components; a configuration requirement table containing the feature codes corresponding to the feature description information of the vehicle components is obtained, and the feature description information includes the material and function of the vehicle components; The target configuration information is determined based on the feature code, and the second component list is obtained based on the first component list and the target configuration information. The target configuration information is used to indicate the type of vehicle corresponding to the vehicle component. Send the second component list to the data server; A data server is used to receive the list of the second components; Upon receiving an audit instruction from the second client, the target configuration information in the second component list is audited, and a first audit result is generated. The first audit result is used to correct the vehicle type configuration. Send the first audit result and the second component list to the second client; The second client is used to receive the first review result and the second component list; Based on the first audit result and the second component list, a target component list is determined and sent to the data server. The target component list is used to represent the relevant parameters of vehicle parts. The data server is also used to receive and store the list of target components.

2. The system according to claim 1, characterized in that, The product digital model data includes matching parameters, which include at least one of the following: applicable vehicle type for vehicle components and product architecture grouping. The first client is also used to obtain a list of candidate components, which contains at least one preset component list. Based on the matching parameters, a list of preset components that meet the type matching requirements is determined from the list of candidate components. The type matching requirements refer to the matching of the vehicle type and product architecture grouping of the preset component list with the product digital model data. Based on the product model data, the product data in the preset component list that meets the type matching requirements is determined, and the first component list is obtained.

3. The system according to claim 2, characterized in that, The first component list includes a candidate configuration list and a first feature code. The candidate configuration list contains at least one type of configuration information, and the first feature code is used to determine the target configuration information from the candidate configuration list. The first client is also used to determine the second feature code corresponding to the feature description information based on the feature description information in the configuration requirement table; and to determine the configuration information that meets the configuration matching requirements from the candidate configuration list as the target configuration information based on the matching result of the second feature code and the first feature code. Based on the target configuration information, the second component list is obtained.

4. The system according to claim 3, characterized in that, The first feature code contains at least one second feature code; The data server is also used to, upon receiving an audit instruction from the second client, convert the first feature code into a first matching number, which is a binary number; convert the second feature code into a second matching number, which is a binary number, and the first matching number corresponds to at least one second matching number; perform a binary AND operation on the at least one second matching number to obtain a result, which is a binary number; generate a first audit result based on the result and the first matching number, wherein when the result and the first matching number are the same, the first audit result is considered a match; and send the first audit result to the second client.

5. The system according to claim 4, characterized in that, The second client is also used to correct the second component list based on the first audit result when the first audit result indicates a mismatch, and obtain a third component list. When the calculation result is different from the first matching number, the first audit result indicates a mismatch. The third component list is used as the target component list and sent to the data server.

6. The system according to claim 5, characterized in that, The second client is also used to obtain a list of mandatory parts, which contains the parts that the vehicle must be equipped with; based on the list of mandatory parts, the target component list is reviewed and a second review result is generated, which is used to correct the target component list; if the second review result indicates a match, the target component list is sent to the data server.

7. The system according to claim 6, characterized in that, The system also includes: The third client is used to obtain change information, including the content and methods that need to be changed in the target component list; to modify the target component list based on the change information to obtain a changed component list; and to send the changed component list to the data server. The data server is also used to receive and store a list of changed components.

8. A method for reviewing a vehicle component list, characterized in that, Executed by the data server, the methods include: The system receives a second component list sent by the first client. The second component list is a component list generated by the first client based on the first component list. The first component list includes component configuration information corresponding to the vehicle components. The first component list is generated by the first client based on product digital model data. The product digital model data is data generated by the first client from other clients through 3D modeling of vehicle components, or data generated by the first client through 3D modeling of vehicle components. Upon receiving an audit instruction from the second client, the target configuration information in the second component list is audited, and a first audit result is generated. The target configuration information is used to indicate the type of vehicle corresponding to the vehicle component, and the first audit result is used to correct the type configuration of the vehicle. Send the first audit result and the second component list to the second client; Receive and store the target component list sent by the second client, which represents the relevant parameters of the vehicle parts.

9. A device for reviewing a vehicle component list, characterized in that, The device includes: The receiving module receives a second component list sent by the first client. The second component list is a component list generated by the first client based on the first component list. The first component list includes component configuration information corresponding to the vehicle components. The first component list is generated by the first client based on product digital model data. The product digital model data is data generated by the first client from other clients through 3D modeling of vehicle components, or data generated by the first client through 3D modeling of vehicle components. Upon receiving an audit instruction from the second client, the audit module audits the target configuration information in the second component list and generates a first audit result. The target configuration information is used to indicate the type of vehicle corresponding to the vehicle component, and the first audit result is used to correct the vehicle type configuration. The sending module sends the first review result and the second component list to the second client. The receiving module receives and stores the target component list sent by the second client. The target component list is used to represent the relevant parameters of the vehicle parts.

Images