Vehicle data verification method and apparatus, and device, storage medium and product

Abstract

Disclosed in the present application are a vehicle data verification method and apparatus, and a device, a storage medium and a product. The method comprises: acquiring MBOM data from an ERP system, wherein the MBOM data comprises manufacturing material information of a plurality of first vehicle parts; acquiring EBOM data from a BOM system, wherein the EBOM data comprises engineering material information of a plurality of second vehicle parts; on the basis of the manufacturing material information of the plurality of first vehicle parts and the engineering material information of the plurality of second vehicle parts, determining verification identification codes of the plurality of first vehicle parts and verification identification codes of the plurality of second vehicle parts; and on the basis of the verification identification codes of the plurality of first vehicle parts and the verification identification codes of the plurality of second vehicle parts, performing consistency verification on the MBOM data and the EBOM data to obtain a consistency verification result.

Description

Vehicle data verification methods, devices, equipment, storage media and products

[0001] This disclosure is based on and claims priority to Chinese Patent Application No. 202510356518.7, filed on March 25, 2025, entitled “Method, Apparatus, Device, Storage Medium and Product for Verifying Vehicle Data”, the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the fields of automobile manufacturing and computer technology, and in particular to a method, apparatus, equipment, storage medium and product for verifying vehicle data. Background Technology

[0003] Enterprise Resource Planning (ERP) systems manage vehicle manufacturing bill of materials (MBOM) data, while Bill of Materials (BOM) systems manage engineering bill of materials (EBOM) data. Therefore, MBOM and EBOM data are managed by two independent management systems; consequently, ensuring consistency between the two for vehicles with the same configuration becomes increasingly crucial. Summary of the Invention

[0004] This application provides a method, apparatus, device, storage medium, and product for verifying vehicle data. The technical solution is as follows:

[0005] On the one hand, a method for verifying vehicle data is provided, the method comprising:

[0006] The vehicle part number is determined, and the vehicle part number is used to identify the vehicle configuration;

[0007] Based on the vehicle material identifier, the manufacturing bill of materials (MBOM) data is obtained from the enterprise resource planning (ERP) system. The MBOM data includes the first BOM data of multiple first vehicle parts corresponding to the vehicle configuration managed in the ERP system. The first BOM data includes the manufacturing material information of the first vehicle parts.

[0008] Based on the vehicle material identifier, the Engineering Bill of Materials (EBOM) data is obtained from the BOM system. The EBOM data includes the second BOM data of multiple second vehicle parts corresponding to the vehicle configuration managed in the BOM system. The second BOM data includes the engineering material information of the second vehicle parts.

[0009] Based on the manufacturing material information of the plurality of first vehicle parts, the verification identification code of the plurality of first vehicle parts is determined, and based on the engineering material information of the plurality of second vehicle parts, the verification identification code of the plurality of second vehicle parts is determined.

[0010] Based on the verification identifiers of the plurality of first vehicle parts and the verification identifiers of the plurality of second vehicle parts, a consistency check is performed on the MBOM data and the EBOM data to obtain a consistency check result.

[0011] In one possible implementation, the step of performing a consistency check on the MBOM data and the EBOM data based on the verification identifiers of the plurality of first vehicle parts and the verification identifiers of the plurality of second vehicle parts to obtain a consistency check result includes:

[0012] The verification identification codes of the plurality of first vehicle parts and the verification identification codes of the plurality of second vehicle parts are compared.

[0013] If there is no engineering material information for a second vehicle part that is identical to the first vehicle part in the EBOM data, the consistency check result is determined to be a discrepancy, and the discrepancy information is that there are overlapping parts or differences in quantity in the MBOM data. The overlapping parts are vehicle parts that are generated by different design departments and manufacturing departments that generate the MBOM data.

[0014] If the MBOM data does not contain manufacturing material information for a first vehicle part that is identical to the second vehicle part, the consistency check result is determined to be a discrepancy. The discrepancy information is that the EBOM data contains a printed part, which is a vehicle part that is pasted on the vehicle body but is not present in the MBOM data.

[0015] In another possible implementation, the consistency check of the MBOM data and the EBOM data based on the verification identifiers of the plurality of first vehicle parts and the verification identifiers of the plurality of second vehicle parts, to obtain the consistency check result, includes:

[0016] Based on the verification codes of the plurality of first vehicle parts and the verification codes of the plurality of second vehicle parts, a target vehicle part is determined, wherein the target vehicle part is the same vehicle part but has a different verification code.

[0017] The consistency verification result is determined based on the manufacturing material information and engineering material information of the target vehicle parts.

[0018] In another possible implementation, determining the consistency verification result based on the manufacturing material information and engineering material information of the target vehicle part includes:

[0019] Based on the multiple attribute information included in the manufacturing material information of the target vehicle part and the multiple attribute information included in the engineering material information of the target vehicle part, the attribute information that is different is determined.

[0020] If the attribute information of the difference is a part identifier, the consistency verification result is determined to be that a difference exists, and the difference information is a part identifier.

[0021] If the attribute information of the difference is the number of parts, then the consistency verification result is determined to be that there is a difference, and the difference information is the number of parts.

[0022] In another possible implementation, determining the consistency verification result based on the manufacturing material information and engineering material information of the target vehicle part includes:

[0023] Based on the multiple attribute information included in the manufacturing material information of the target vehicle part and the multiple attribute information included in the engineering material information of the target vehicle part, the attribute information that is different is determined.

[0024] The attribute information of the difference is part level information, which determines the first parent part of the target vehicle part in the MBOM data and the second parent part in the EBOM data;

[0025] If the first parent part and the second parent part are the same, then the first child part of the target vehicle part in the MBOM data and the second child part in the EBOM data are determined.

[0026] The consistency verification result is determined based on the attribute information of the first sub-level part and the attribute information of the second sub-level part.

[0027] In another possible implementation, the method further includes:

[0028] Based on the consistency verification results, at least one discrepancy is determined;

[0029] The at least one difference information is summarized to obtain difference summary information;

[0030] Output the summary information of the differences.

[0031] On the other hand, a vehicle data verification device is provided, the device comprising:

[0032] The first determining module is used to determine the vehicle material identifier of the vehicle, wherein the vehicle material identifier is used to identify the vehicle configuration of the vehicle;

[0033] The first acquisition module is used to acquire manufacturing bill of materials (MBOM) data from the enterprise resource planning (ERP) system based on the vehicle material identifier. The MBOM data includes the first BOM data of multiple first vehicle parts corresponding to the vehicle configuration managed in the ERP system. The first BOM data includes the manufacturing material information of the first vehicle parts.

[0034] The second acquisition module is used to acquire Engineering Bill of Materials (EBOM) data from the BOM system based on the vehicle material identifier. The EBOM data includes the second BOM data of multiple second vehicle parts corresponding to the vehicle configuration managed in the BOM system. The second BOM data includes the engineering material information of the second vehicle parts.

[0035] The second determining module is used to determine the verification identification code of the plurality of first vehicle parts based on the manufacturing material information of the plurality of first vehicle parts, and to determine the verification identification code of the plurality of second vehicle parts based on the engineering material information of the plurality of second vehicle parts.

[0036] The verification module is used to perform consistency verification on the MBOM data and the EBOM data based on the verification identification codes of the plurality of first vehicle parts and the verification identification codes of the plurality of second vehicle parts, and obtain a consistency verification result.

[0037] In one possible implementation, the verification module is used to compare the verification identification codes of the plurality of first vehicle parts and the verification identification codes of the plurality of second vehicle parts; if the EBOM data does not contain engineering material information for a second vehicle part that is identical to the first vehicle part, the consistency verification result is determined to be inconsistent, and the inconsistency information is that the MBOM data contains overlapping parts or differences in quantity, wherein the overlapping parts are vehicle parts from different design departments that generate the EBOM data and different manufacturing departments that generate the MBOM data; if the MBOM data does not contain manufacturing material information for a first vehicle part that is identical to the second vehicle part, the consistency verification result is determined to be inconsistent, and the inconsistency information is that the EBOM data contains printed parts, wherein the printed parts are vehicle parts that are pasted on the vehicle body but are not present in the MBOM data.

[0038] In another possible implementation, the verification module is used to determine a target vehicle part based on the verification identification codes of the plurality of first vehicle parts and the verification identification codes of the plurality of second vehicle parts, wherein the target vehicle part is a vehicle part that is the same vehicle part but has a different verification identification code; and to determine the consistency verification result based on the manufacturing material information and engineering material information of the target vehicle part.

[0039] In another possible implementation, the verification module is configured to determine the attribute information of the discrepancy based on multiple attribute information included in the manufacturing material information of the target vehicle part and multiple attribute information included in the engineering material information of the target vehicle part; if the attribute information of the discrepancy is a part identifier, the consistency verification result is determined to be that a discrepancy exists, and the discrepancy information is a part identifier; if the attribute information of the discrepancy is the number of parts, the consistency verification result is determined to be that a discrepancy exists, and the discrepancy information is the number of parts.

[0040] In another possible implementation, the verification module is configured to determine the differing attribute information based on multiple attribute information included in the manufacturing material information and multiple attribute information included in the engineering material information of the target vehicle part; if the differing attribute information is part level information, determine the first parent part of the target vehicle part in the MBOM data and the second parent part in the EBOM data; if the first parent part and the second parent part are the same, then determine the first child part of the target vehicle part in the MBOM data and the second child part in the EBOM data; and determine the consistency verification result based on the attribute information of the first child part and the attribute information of the second child part.

[0041] In another possible implementation, the device further includes:

[0042] The third determining module is used to determine at least one difference based on the consistency verification result;

[0043] The summarization module is used to summarize the at least one difference information to obtain difference summary information;

[0044] The output module is used to output the summary information of the differences.

[0045] On the other hand, a computer device is provided, the computer device including a main control module, the main control module including a processor and a memory, the memory storing at least one piece of program code, the at least one piece of program code being loaded and executed by the processor to implement the above-mentioned vehicle data verification method.

[0046] On the other hand, a computer-readable storage medium is provided, wherein at least one piece of program code is stored in the storage medium, the at least one piece of program code being loaded and executed by a processor to implement the above-described vehicle data verification method.

[0047] On the other hand, a computer program product is provided, the product storing at least one piece of program code, the at least one piece of program code being executed by a processor to implement the above-described vehicle data verification method.

[0048] In this embodiment, the MBOM and EBOM data of the same vehicle configuration can be obtained from the ERP system and BOM system through the vehicle material identification. Then, the consistency verification of the MBOM and EBOM data can be realized based on the verification identification code of the vehicle parts in the MBOM and EBOM data. It can be seen that this embodiment can automatically perform consistency verification of MBOM and EBOM data, which can improve the efficiency of consistency verification compared with manual verification.

[0049] It should be understood that the above general description and the following detailed description are merely exemplary and do not limit this disclosure. Attached Figure Description

[0050] Figure 1 is a schematic diagram illustrating the implementation environment of a vehicle data verification method according to an exemplary embodiment of this application;

[0051] Figure 2 is a flowchart illustrating a vehicle data verification method according to an exemplary embodiment of this application;

[0052] Figure 3 is a flowchart illustrating a vehicle data verification method according to an exemplary embodiment of this application;

[0053] Figure 4 is a schematic diagram illustrating a vehicle data verification method according to an exemplary embodiment of this application;

[0054] Figure 5 is a flowchart illustrating a vehicle data verification method according to an exemplary embodiment of this application;

[0055] Figure 6 is a block diagram illustrating a vehicle data verification device according to an exemplary embodiment of this application;

[0056] Figure 7 is a block diagram of a computer device illustrated in an exemplary embodiment of this application. Detailed Implementation

[0057] To make the technical solution and advantages of this application clearer, the embodiments of this application will be described in further detail below.

[0058] The terms "first," "second," "third," and "fourth," etc., used in the specification, claims, and accompanying drawings of this application are used to distinguish different objects, not to describe a specific order. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or apparatus that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to these processes, methods, products, or apparatuses.

[0059] It should be noted that all information (including but not limited to user device information, user personal information, etc.), data (including but not limited to data used for analysis, stored data, displayed data, etc.), and signals involved in this application have been 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. For example, the manufacturing material information and engineering material information involved in this application were obtained with full authorization.

[0060] Please refer to Figure 1, which shows a schematic diagram of the implementation environment of a vehicle data verification method according to an exemplary embodiment of this application. The implementation environment includes a vehicle 101 and a computer device 102. The computer device 102 is used to verify the vehicle data of the vehicle 101. For example, the computer device 101 is used to perform consistency verification on the MBOM data and EBOM data of the vehicle 101.

[0061] MBOM data includes manufacturing material information for multiple first vehicle parts. This manufacturing material information refers to the material information used during the manufacturing of the first vehicle part. For example, the manufacturing material information for a first vehicle part includes multiple attribute information, such as part hierarchy information, part identifier, part name, part quantity, part usage, Global Professional in Project Controls (GPC) certification, and Factory Neutral Data Transmission (FND) rules. Part hierarchy information describes the parent-child relationship between vehicle parts. The part identifier can be a part number, and different part numbers are generated for different vehicle parts due to different functions or uses. The part name is a Chinese description of the vehicle part. The part quantity describes the number of vehicle parts used per vehicle (the quantity used in one vehicle). The part usage describes the function and usage scenario of the vehicle part. GPC indicates the group to which the vehicle part belongs; FND identifies the assembly location of the vehicle part in the vehicle.

[0062] EBOM data includes engineering material information for multiple second vehicle parts, which is the material information used when designing the first vehicle parts. For example, the engineering material information for second vehicle parts also includes multiple attribute information, such as part level information, part identifier, part name, part quantity, part usage, GPC, and FND.

[0063] Under normal circumstances, the MBOM and EBOM data for the same vehicle configuration should be consistent, meaning the material information during the design phase and the manufacturing phase should be the same. However, there are several reasons that can cause inconsistencies between the MBOM and EBOM data for the same vehicle configuration; therefore, it is necessary to perform a consistency check on the vehicle's MBOM and EBOM data.

[0064] The first reason is the difference in quantity uncertainty; for example, there may be multiple balance blocks in the EBOM data, but the difference between multiple balance blocks is not reflected in the MBOM data; another example is that there may be multiple types of adhesives in the EBOM data, but the difference between multiple types of adhesives is not reflected in the MBOM data.

[0065] The second reason is the discrepancy caused by cross-components. For example, the air conditioning compressor, a cross-component, is designed by the vehicle assembly department but assembled in the engine shop (manufacturing process). Because the design and manufacturing (or assembly) departments are different, the engineering material information and manufacturing material information for the air conditioning compressor may differ. Similarly, the starter motor, another cross-component, is designed by the engine design department but assembled in the final assembly shop. Because the design and manufacturing (or assembly) departments are different, the engineering material information and manufacturing material information for the starter motor may differ.

[0066] The third reason is the difference caused by the different breakpoint effective times; the breakpoint effective times of the vehicle parts on the R&D side (used to generate EBOM data) and the production side (used to generate MBOM data) are different; the EBOM data has been changed to the engineering material information of the modified vehicle parts, but the MBOM is still the manufacturing material information of the vehicle parts before the change.

[0067] The fourth reason: the difference caused by the self-printed parts in the final assembly; the final assembly workshop prints the vehicle parameter label on a roll of paper, cuts it and sticks it on the vehicle body. The vehicle parameter label is used to display the parameters of the whole vehicle. The printed part will be reflected in the EBOM data, but not in the MBOM data.

[0068] The fifth reason is the difference caused by the relative quantity under the BOM structure; for example, if there are 4 wheel assemblies, then the number of tires and rims used is 1, the relative quantity is 1, and the absolute quantity is 4; there is also a way of expressing it as 1 wheel assembly and 4 tires and rims used, which will occur when comparing across models.

[0069] The sixth reason is the difference caused by different vehicle supply status; for example, the left front seat has a seat belt buckle assembly. The EBOM data shows the parent-child BOM structure relationship between the left front seat assembly and the seat belt buckle assembly, but the MBOM data only shows the left front seat has a seat belt buckle assembly, which causes the difference.

[0070] The seventh reason: Differences caused by cross-workshop transfer of welding parts. Vehicle parts of different models may share a tailgate assembly (the tailgate assembly is a key structural system of the vehicle's rear). When this vehicle part is produced in the welding workshop, it needs to be welded into a tailgate assembly in one welding workshop and then transferred to another welding workshop for direct assembly to obtain the vehicle part. For such transferred vehicle parts, the parent-child BOM structure relationship between the tailgate assembly and the vehicle part is not reflected in the EBOM data, but it will be reflected in the MBOM data, thus leading to the difference between the EBOM data and the MBOM data.

[0071] In related technologies, consistency checks on vehicle MBOM and EBOM data are performed manually, resulting in low efficiency. In this embodiment, consistency checks on vehicle MBOM and EBOM data can be performed automatically, thereby improving efficiency.

[0072] Vehicle 101 is a new energy vehicle, such as a pure electric vehicle, a plug-in hybrid electric vehicle, or a fuel cell electric vehicle. Vehicle 101 is equipped with a vehicle controller, an on-board charger, a power battery, and a battery management system for managing the power battery. The vehicle controller can communicate with the on-board terminal, the battery management system, and the on-board charger via a CAN (Controller Area Network) bus.

[0073] Please refer to Figure 2, which shows a flowchart of a vehicle data verification method illustrated in an exemplary embodiment of this application.

[0074] Referring to Figure 2, the method includes:

[0075] Step 201: The computer equipment determines the vehicle's material identification, which is used to identify the vehicle's configuration.

[0076] Step 202: Based on the vehicle material identification, the computer equipment obtains the Manufacturing Bill of Materials (MBOM) data from the Enterprise Resource Planning (ERP) system. The MBOM data includes the first BOM data of multiple first vehicle parts corresponding to the vehicle configuration managed in the ERP system. The first BOM data includes the manufacturing material information of the first vehicle parts.

[0077] Step 203: The computer equipment obtains the Engineering Bill of Materials (EBOM) data from the BOM system based on the vehicle material identifier. The EBOM data includes the second BOM data of multiple second vehicle parts corresponding to the vehicle configuration managed in the BOM system. The second BOM data includes the engineering material information of the second vehicle parts.

[0078] Step 204: The computer equipment determines the verification identification code of the multiple first vehicle parts based on the manufacturing material information of the multiple first vehicle parts, and determines the verification identification code of the multiple second vehicle parts based on the engineering material information of the multiple second vehicle parts.

[0079] Step 205: The computer equipment performs a consistency check on the MBOM data and EBOM data based on the verification identifier codes of multiple first vehicle parts and multiple second vehicle parts, and obtains the consistency check result.

[0080] In this embodiment, the MBOM and EBOM data of the same vehicle configuration can be obtained from the ERP system and BOM system through the vehicle material identification. Then, the consistency verification of the MBOM and EBOM data can be realized based on the verification identification code of the vehicle parts in the MBOM and EBOM data. It can be seen that this embodiment can automatically perform consistency verification of MBOM and EBOM data, which can improve the efficiency of consistency verification compared with manual verification.

[0081] Please refer to Figure 3, which shows a flowchart of a vehicle data verification method illustrated in an exemplary embodiment of this application.

[0082] Referring to Figure 3, the method includes:

[0083] Step 301: The computer equipment determines the vehicle's material identification, which is used to identify the vehicle's configuration.

[0084] The vehicle material identifier can be a vehicle material number; different vehicle material numbers correspond to different vehicle configurations. This application embodiment supports batch consistency verification of MBOM and EBOM data; therefore, in this step, the computer device can determine multiple vehicle material identifiers for a vehicle, and these multiple vehicle material identifiers correspond to multiple vehicle configurations. That is, this application embodiment can achieve parallel consistency verification of MBOM and EBOM data for multiple vehicle configurations, thereby improving the efficiency of consistency verification.

[0085] The computer equipment is equipped with a data comparison device. In this step, the computer equipment activates the comparison device and displays its main interface. The main interface includes an input box for inputting or selecting vehicle material identifiers, and the input box supports inputting or selecting multiple vehicle material identifiers at once. The computer equipment receives the vehicle material identifiers input or selected in the input box. This data comparison device can be data comparison software.

[0086] In this embodiment, the MBOM and EBOM data of the same vehicle configuration can be obtained from the ERP system and BOM system through the vehicle material identification. Then, the consistency verification of the MBOM and EBOM data can be realized based on the verification identification code of the vehicle parts in the MBOM and EBOM data. It can be seen that this embodiment can automatically perform consistency verification of MBOM and EBOM data, which can improve the efficiency of consistency verification compared with manual verification.

[0087] Step 302: The computer equipment obtains the Manufacturing Bill of Materials (MBOM) data from the Enterprise Resource Planning (ERP) system based on the vehicle material identification. The MBOM data includes the first BOM data of multiple first vehicle parts corresponding to the vehicle configuration managed in the ERP system. The first BOM data includes the manufacturing material information of the first vehicle parts.

[0088] Manufacturing material information includes several items such as part level information, part identifier (part number), part name, part quantity, part usage, GPC, and FND. For example, MBOM data is shown in Table 1 below:

[0089] Table 1

[0090] The ERP system manages the MBOM data for vehicles, and the MBOM data in the ERP system is stored using the vehicle material identifier as an index. Therefore, the steps for the computer device to retrieve MBOM data from the ERP system based on the vehicle material identifier can be as follows: the computer device sends a first call request to the ERP system through the ERP system interface, the first call request carrying the vehicle material identifier; the ERP system receives the first call request, retrieves the MBOM data corresponding to the vehicle material identifier based on the vehicle material identifier, and sends the MBOM data corresponding to the vehicle material identifier to the computer device; the computer device receives the MBOM data corresponding to the vehicle material identifier.

[0091] Step 303: The computer equipment obtains the Engineering Bill of Materials (EBOM) data from the BOM system based on the vehicle material identifier. The EBOM data includes the second BOM data of multiple second vehicle parts corresponding to the vehicle configuration managed in the BOM system. The second BOM data includes the engineering material information of the second vehicle parts.

[0092] Manufacturing material information includes several items such as part level information, part identifier (part number), part name, part quantity, part usage, GPC, and FND. For example, EBOM data is shown in Table 2 below:

[0093] Table 2

[0094] The BOM system is used to manage the EBOM data of vehicles, and the EBOM data in the BOM system is stored with engineering material identifiers (such as engineering material numbers) as indexes. Therefore, the steps for computer equipment to obtain the engineering material list EBOM data from the BOM system based on the vehicle material identifier can be as follows: the computer equipment determines the engineering material identifier corresponding to the vehicle material identifier from the correspondence between the vehicle material identifier and the engineering material identifier, and obtains the vehicle's EBOM data from the BOM system based on the engineering material identifier.

[0095] The steps for a computer device to obtain vehicle EBOM data from a BOM system based on an engineering material identifier can be as follows: the computer device sends a second call request to the BOM system through the BOM system's interface. The second call request carries the engineering material identifier. The BOM system receives the second call request, obtains the EBOM data corresponding to the engineering material identifier based on the engineering material identifier, and sends the EBOM data corresponding to the engineering material identifier to the computer device. The computer device receives the EBOM data corresponding to the engineering material identifier.

[0096] Step 304: The computer equipment determines the verification identification code of the multiple first vehicle parts based on the manufacturing material information of the multiple first vehicle parts, and determines the verification identification code of the multiple second vehicle parts based on the engineering material information of the multiple second vehicle parts.

[0097] For any first vehicle part, the computer device determines the verification identifier code of the first vehicle part based on the manufacturing material information of the first vehicle part; for example, the computer device determines the hash value of the manufacturing material information of the first vehicle part to obtain the verification identifier code of the first vehicle part; or, the computer device determines the Message-Digest Algorithm 5 (MD5) value of the manufacturing material information of the first vehicle part to obtain the verification identifier code of the first vehicle part.

[0098] For any second vehicle part, the computer device determines the verification code of the second vehicle part based on the engineering material information of the second vehicle part; for example, the computer device determines the hash value of the engineering material information of the second vehicle part to obtain the verification code of the second vehicle part; or, the computer device determines the MD5 value of the engineering material information of the second vehicle part to obtain the verification code of the second vehicle part.

[0099] Step 305: The computer equipment compares the verification identification codes of multiple first vehicle parts with the verification identification codes of multiple second vehicle parts.

[0100] The computer equipment determines the number of verification codes for multiple first vehicle parts and multiple second vehicle parts. If the number of verification codes for multiple first vehicle parts is greater than the number of verification codes for multiple second vehicle parts, it determines that the EBOM data does not contain engineering material information for a second vehicle part identical to that of a first vehicle part, and proceeds to step 306. If the number of verification codes for multiple first vehicle parts is less than the number of verification codes for multiple second vehicle parts, it determines that the MBOM data does not contain manufacturing material information for a first vehicle part identical to that of a second vehicle part, and proceeds to step 307. If the number of verification codes for multiple first vehicle parts is equal to the number of verification codes for multiple second vehicle parts, the consistency check result of the MBOM data and EBOM data is determined to be consistent; alternatively, if the number of verification codes for multiple first vehicle parts is equal to the number of verification codes for multiple second vehicle parts, the consistency of the MBOM data and EBOM data can be checked through the next embodiment.

[0101] It should be noted that, in step 301, when the computer device determines multiple vehicle material identifiers, in this step, the computer device matches and groups the verification codes of multiple first vehicle parts and multiple second vehicle parts based on the vehicle material identifier. That is, the verification codes of multiple first vehicle parts included in the MBOM data and the verification codes of multiple second vehicle parts included in the EBOM data corresponding to the same vehicle material identifier are grouped into the same group, and then the verification codes of multiple first vehicle parts included in the MBOM data and the verification codes of multiple second vehicle parts included in the EBOM data of the same group are compared.

[0102] For example, referring to Figure 4, the user inputs multiple vehicle material identifiers into the data comparison device. Then, the computer device, based on these identifiers, calls the ERP system to obtain the MBOM data corresponding to each vehicle material identifier, and calls the BOM system to obtain the EBOM data corresponding to each vehicle material identifier, resulting in multiple EBOM data. For any MBOM data, based on the manufacturing material information of multiple first vehicle parts included in the MBOM data, the verification identifier code for each first vehicle part is determined (this process can be called MBOM preprocessing). For any EBOM data, based on the engineering material information of multiple second vehicle parts included in the EBOM data, the verification identifier code for each second vehicle part is determined (this process can be called EBOM preprocessing). Through the data comparison device... Based on the vehicle material identifier, the verification identification codes of multiple first vehicle parts and multiple second vehicle parts are matched and grouped. That is, the verification identification codes of multiple first vehicle parts included in the MBOM data and multiple second vehicle parts included in the EBOM data corresponding to the same vehicle material identifier are divided into the same group (this process can be called device matching grouping). Then, the verification identification codes of multiple first vehicle parts included in the MBOM data and multiple second vehicle parts included in the EBOM data of the same group are compared (this process can be called group batch verification). Then, the consistency verification results are summarized (this process can be called verification result post-processing, and this process will be described in detail in subsequent embodiments). Finally, the consistency verification results are output (this process is called verification result output).

[0103] Step 306: If there is no engineering material information for a second vehicle part that is identical to the first vehicle part in the EBOM data, the computer equipment determines that the consistency check result is that there is a difference, and the difference information is that there are cross parts or differences in quantity in the MBOM data. The cross parts are vehicle parts that are different between the design department that generates the EBOM data and the manufacturing department that generates the MBOM data.

[0104] Quantity-related differences refer to differences in quantities that are uncertain; for example, multiple balance blocks may exist in EBOM data, but the differences between multiple balance blocks may not be reflected in MBOM data; similarly, multiple types of adhesives may exist in EBOM data, but the differences between multiple types of adhesives may not be reflected in MBOM data.

[0105] Step 307: If there is no manufacturing material information for the first vehicle part that is identical to the second vehicle part in the MBOM data, the computer equipment determines that the consistency check result is that there is a difference, and the difference information is that there is a printed part in the EBOM data, which is pasted on the vehicle body but is not a vehicle part in the MBOM data.

[0106] For example, the final assembly workshop prints vehicle parameter labels from a roll of paper, cuts them, and affixes them to the vehicle body. This printed part will appear in the EBOM (Embodied Entity Inventory) data, but not in the MBOM (Material Management Inventory) data. Therefore, the MBOM data will lack the manufacturing material information for a first vehicle part that is identical to a part in the second vehicle.

[0107] Step 308: The computer device outputs the consistency verification results of MBOM data and EBOM data.

[0108] In this embodiment, by using the vehicle material identification, MBOM and EBOM data of the same vehicle configuration can be obtained from the ERP system and BOM system. Then, based on the verification identification codes of vehicle parts in the MBOM and EBOM data, consistency verification of the MBOM and EBOM data can be achieved. Therefore, this embodiment can automatically perform consistency verification of MBOM and EBOM data, which can improve the efficiency of consistency verification compared to manual verification. The fully automated processing of this embodiment can improve work efficiency by more than 80%.

[0109] Furthermore, this application embodiment also supports automatic batch processing, which can obtain the consistency verification results of MBOM data and EBOM data. Moreover, the consistency verification rules for MBOM data and EBOM data integrate various complex scenarios and can be continuously optimized, reducing the requirements for manual skills and making the result display more standardized.

[0110] Please refer to Figure 5, which shows a flowchart of a vehicle data verification method illustrated in an exemplary embodiment of this application. Referring to Figure 5, the method includes:

[0111] Step 501: The computer equipment determines the vehicle's material identification, which is used to identify the vehicle's configuration.

[0112] In some embodiments, this step is the same as step 301, and will not be described again here.

[0113] Step 502: Based on the vehicle material identification, the computer equipment obtains the Manufacturing Bill of Materials (MBOM) data from the Enterprise Resource Planning (ERP) system. The MBOM data includes the first BOM data of multiple first vehicle parts corresponding to the vehicle configuration managed in the ERP system. The first BOM data includes the manufacturing material information of the first vehicle parts.

[0114] In some embodiments, this step is the same as step 302, and will not be described again here.

[0115] Step 503: The computer equipment obtains the Engineering Bill of Materials (EBOM) data from the BOM system based on the vehicle material identifier. The EBOM data includes the second BOM data of multiple second vehicle parts corresponding to the vehicle configuration managed in the BOM system. The second BOM data includes the engineering material information of the second vehicle parts.

[0116] In some embodiments, this step is the same as step 303, and will not be described again here.

[0117] Step 504: The computer equipment determines the verification identification code of the multiple first vehicle parts based on the manufacturing material information of the multiple first vehicle parts, and determines the verification identification code of the multiple second vehicle parts based on the engineering material information of the multiple second vehicle parts.

[0118] In some embodiments, this step is the same as step 304, and will not be described again here.

[0119] The computer device determines whether the number of verification codes for multiple first vehicle parts and the number of verification codes for multiple second vehicle parts are the same; if the number of verification codes for multiple first vehicle parts and the number of verification codes for multiple second vehicle parts are the same, step 505 is executed.

[0120] Step 505: The computer device determines the target vehicle part based on the verification codes of multiple first vehicle parts and multiple second vehicle parts. The target vehicle part is the same vehicle part but with different verification codes.

[0121] The computer equipment determines vehicle parts with the same verification code based on the verification codes of multiple first vehicle parts and multiple second vehicle parts, and identifies vehicle parts among the multiple first vehicle parts that do not have the same verification code as target vehicle parts, or identifies vehicle parts among the multiple second vehicle parts that do not have the same verification code as target vehicle parts.

[0122] Step 506: The computer equipment determines the consistency verification result based on the manufacturing material information and engineering material information of the target vehicle parts.

[0123] This step can be implemented in any of the following ways. The first implementation method: The step of determining the consistency verification result based on the manufacturing material information and engineering material information of the target vehicle parts by the computer equipment can be implemented through the following steps 5061-5063, including:

[0124] Step 5061: The computer equipment determines the differing attribute information based on the multiple attribute information included in the manufacturing material information of the target vehicle part and the multiple attribute information included in the engineering material information of the target vehicle part.

[0125] For example, referring to Tables 1 and 2, since the engineering material information for the engine in Table 1 and the manufacturing material information for the engine in Table 2 are the same, the engine's verification code will be the same. Similarly, since the engineering material information for the motor in Table 1 and the manufacturing material information for the motor in Table 2 are the same, the motor's verification code will also be the same. However, the engineering material information for the seat in Table 1 and the manufacturing material information for the seat in Table 2 are not entirely the same; therefore, the seat is the target vehicle part. Based on the multiple attribute information of the seat in Table 1 and the multiple attribute information of the seat in Table 2, the difference in attribute information is the number of parts.

[0126] The computer device determines the consistency check result of the vehicle's MBOM data and EBOM data based on the attribute information of the discrepancies. For example, if the computer device determines that the consistency check result of the vehicle's MBOM data and EBOM data is that there are discrepancies, and the discrepancy information is the attribute information of the discrepancy, for example, if the attribute information of the discrepancy is a part identifier, then step 5062 is executed; or if the attribute information of the discrepancy is the number of parts, then step 5063 is executed.

[0127] Step 5062: If the attribute information of the difference is a part identifier, the computer device determines that the consistency verification result is that there is a difference, and the difference information is a part identifier.

[0128] The attribute information of the difference is the difference information; for example, if the part name, part quantity, part usage, GPC and FND of the target vehicle part are the same, but the part identifier (part number) is different, then the computer equipment determines that the consistency check result of the vehicle's MBOM data and EBOM data is that there is a difference, and the difference information is the part identifier.

[0129] Step 5063: If the attribute information of the difference is the number of parts, the computer device determines that the consistency check result is that there is a difference, and the difference information is the number of parts.

[0130] For example, if the part identifier, part name, part usage, GPC, and FND of the target vehicle parts are the same, but the number of parts is different, the computer equipment will determine that the consistency check result of the vehicle's MBOM data and EBOM data is that there is a difference, and the difference information is the number of parts.

[0131] The second implementation method: The steps for determining the consistency verification result based on the manufacturing material information and engineering material information of the target vehicle parts by the computer equipment can be implemented through the following steps 5064-5067, including:

[0132] Step 5064: The computer equipment determines the differing attribute information based on the multiple attribute information included in the manufacturing material information of the target vehicle part and the multiple attribute information included in the engineering material information of the target vehicle part.

[0133] In some embodiments, this step is the same as step 5061, and will not be described again here.

[0134] Step 5065: Given the difference in attribute information as part hierarchy information, the computer device determines the first parent part of the target vehicle part in the MBOM data and the second parent part in the EBOM data.

[0135] Step 5066: If the first parent part and the second parent part are the same, the computer device determines the first child part of the target vehicle part in the MBOM data and the second child part in the EBOM data.

[0136] If the part identifiers of the first parent part and the second parent part are different, the computer determines that the first parent part and the second parent part are different. In this case, the consistency check result of the MBOM data and EBOM data can be directly determined to be a difference, and the difference information is a difference in the parent vehicle part. If the part identifiers of the first parent part and the second parent part are the same, the computer continues to compare down to the child parts, finds the differences, and records the differences.

[0137] Step 5067: The computer device determines the consistency verification result based on the attribute information of the first sub-level part and the attribute information of the second sub-level part.

[0138] The attribute information of the first-level sub-part includes part identifier, part name, part quantity, part usage, GPC, and FND; similarly, the attribute information of the second-level sub-part includes part identifier, part name, part quantity, part usage, GPC, and FND.

[0139] In one possible implementation, if the number of parts in the attribute information of the first sub-part and the number of parts in the attribute information of the second sub-part are different, the computer device determines that the consistency check result of the MBOM data and the EBOM data is different, and the difference information is that the number of sub-parts is different.

[0140] Because the methods of recording the number of parts may differ—MBOM data may record the relative number of vehicle parts, while EBOM data may record the absolute number of vehicle parts; or MBOM data may record the absolute number of vehicle parts, while EBOM data may record the relative number of vehicle parts—the computer device determines the absolute number of the first-level part and the absolute number of the second-level part when the number of parts in the attribute information of the first-level part differs from that in the attribute information of the second-level part. If the absolute number of the first-level part and the absolute number of the second-level part differ, the consistency check result of the MBOM data and EBOM data is determined to be a discrepancy, and the discrepancy information indicates a difference in the number of sub-level parts (it can also distinguish between absolute and relative quantity differences).

[0141] For example, when the assembly is 4, the quantity of the first sub-level parts (or the second sub-level parts) will be multiplied by 4 layer by layer to obtain the absolute quantity of the first sub-level parts (or the second sub-level parts); when the assembly is 1, the quantity of the first sub-level parts (or the second sub-level parts) is the absolute quantity.

[0142] In another possible implementation, if the part identifier in the attribute information of the first sub-part is different from the part identifier in the attribute information of the second sub-part, the computer device determines that the consistency check result of the MBOM data and EBOM data is that there is a difference, and the difference information is the difference in the sub-part identifier.

[0143] In another possible implementation, due to different supply statuses, the first-level sub-part may not be present in the MBOM data. However, considering spare parts or knockdown components (KD), the EBOM data will reflect the second-level sub-part, thus causing a difference in sub-parts. Correspondingly, if the second-level sub-part exists in the EBOM data but the first-level sub-part does not exist in the MBOM data, the computer determines that the consistency check result between the MBOM and EBOM data shows a discrepancy, and the discrepancy information is a difference in supply status.

[0144] In another possible implementation, the operation of the workshop results in the presence of a first-level sub-part in the MBOM data, but the second-level sub-part is not reflected in the EBOM data. Accordingly, when the first-level sub-part exists in the MBOM data, but the second-level sub-part does not exist in the EBOM data, the computer equipment determines that the consistency check result of the MBOM data and the EBOM data is that there is a difference, and the difference information is a difference in workshop operation.

[0145] Step 507: The computer device outputs the consistency verification results of MBOM data and EBOM data.

[0146] After the computer equipment outputs the consistency verification results of MBOM and EBOM data, it supports viewing the consistency verification results of MBOM and EBOM data online, and also supports downloading the consistency verification results of MBOM and EBOM data to a spreadsheet (Excel) for viewing.

[0147] Since computer equipment can perform consistency checks on multiple sets of MBOM and EBOM data, it can also summarize and output the consistency check results of MBOM and EBOM data. Accordingly, the steps for computer equipment to output the consistency check results of MBOM and EBOM data can be as follows: based on the consistency check results of MBOM and EBOM data, the computer equipment determines at least one discrepancy; summarizes the at least one discrepancy to obtain a discrepancy summary; and outputs the discrepancy summary.

[0148] The computer equipment summarizes the manufacturing material information and engineering material information of vehicle parts with differences in cross-parts, uncertain quantities, and printed parts into the first category of difference information; summarizes the manufacturing material information and engineering material information of vehicle parts with only differences in part identification (part number) into the second category of difference information; summarizes the manufacturing material information and engineering material information of vehicle parts with differences in relative quantity, absolute quantity, sub-part identification, supply status, and workshop operation into the third category of difference information; and summarizes the manufacturing material information and engineering material information of vehicle parts with only differences in part quantity into the fourth category of difference information.

[0149] In this embodiment, the MBOM and EBOM data of the same vehicle configuration can be obtained from the ERP system and BOM system through the vehicle material identification. Then, the consistency verification of the MBOM and EBOM data can be realized based on the verification identification code of the vehicle parts in the MBOM and EBOM data. It can be seen that this embodiment can automatically perform consistency verification of MBOM and EBOM data, which can improve the efficiency of consistency verification compared with manual verification.

[0150] Please refer to Figure 6, which shows a block diagram of a vehicle data verification device according to an exemplary embodiment of this application. The device includes:

[0151] The first determining module 601 is used to determine the vehicle material identifier of the vehicle, wherein the vehicle material identifier is used to identify the vehicle configuration of the vehicle.

[0152] The first acquisition module 602 is used to acquire manufacturing bill of materials (MBOM) data from the enterprise resource planning (ERP) system based on the vehicle material identifier. The MBOM data includes the first BOM data of multiple first vehicle parts corresponding to the vehicle configuration managed in the ERP system. The first BOM data includes the manufacturing material information of the first vehicle parts.

[0153] The second acquisition module 603 is used to acquire Engineering Bill of Materials (EBOM) data from the BOM system based on the vehicle material identifier. The EBOM data includes the second BOM data of multiple second vehicle parts corresponding to the vehicle configuration managed in the BOM system. The second BOM data includes the engineering material information of the second vehicle parts.

[0154] The second determining module 604 is used to determine the verification identification code of the plurality of first vehicle parts based on the manufacturing material information of the plurality of first vehicle parts, and to determine the verification identification code of the plurality of second vehicle parts based on the engineering material information of the plurality of second vehicle parts.

[0155] The verification module 605 is used to perform consistency verification on the MBOM data and the EBOM data based on the verification identification codes of the plurality of first vehicle parts and the verification identification codes of the plurality of second vehicle parts, and obtain a consistency verification result.

[0156] In one possible implementation, the verification module 605 is used to compare the verification identification codes of the plurality of first vehicle parts and the verification identification codes of the plurality of second vehicle parts; if there is no engineering material information for a second vehicle part that is identical to that of a first vehicle part in the EBOM data, the consistency verification result is determined to be inconsistent, and the inconsistency information is that there are overlapping parts or differences in quantity in the MBOM data, wherein the overlapping parts are vehicle parts from different design departments that generate the EBOM data and different manufacturing departments that generate the MBOM data; if there is no manufacturing material information for a first vehicle part that is identical to that of a second vehicle part in the MBOM data, the consistency verification result is determined to be inconsistent, and the inconsistency information is that there are printed parts in the EBOM data, wherein the printed parts are vehicle parts that are pasted on the vehicle body but are not present in the MBOM data.

[0157] In another possible implementation, the verification module 605 is used to determine a target vehicle part based on the verification identification codes of the plurality of first vehicle parts and the verification identification codes of the plurality of second vehicle parts, wherein the target vehicle part is a vehicle part that is the same vehicle part but has a different verification identification code; and to determine the consistency verification result based on the manufacturing material information and engineering material information of the target vehicle part.

[0158] In another possible implementation, the verification module 605 is used to determine the attribute information of the difference based on multiple attribute information included in the manufacturing material information of the target vehicle part and multiple attribute information included in the engineering material information of the target vehicle part; if the attribute information of the difference is a part identifier, the consistency verification result is determined to be that there is a difference, and the difference information is a part identifier; if the attribute information of the difference is the number of parts, the consistency verification result is determined to be that there is a difference, and the difference information is the number of parts.

[0159] In another possible implementation, the verification module 605 is configured to determine the differing attribute information based on multiple attribute information included in the manufacturing material information and multiple attribute information included in the engineering material information of the target vehicle part; if the differing attribute information is part level information, determine the first parent part of the target vehicle part in the MBOM data and the second parent part in the EBOM data; if the first parent part and the second parent part are the same, then determine the first child part of the target vehicle part in the MBOM data and the second child part in the EBOM data; and determine the consistency verification result based on the attribute information of the first child part and the attribute information of the second child part.

[0160] In another possible implementation, the device further includes:

[0161] The third determining module is used to determine at least one difference based on the consistency verification result;

[0162] The summarization module is used to summarize the at least one difference information to obtain difference summary information;

[0163] The output module is used to output the summary information of the differences.

[0164] In this embodiment, the MBOM and EBOM data of the same vehicle configuration can be obtained from the ERP system and BOM system through the vehicle material identification. Then, the consistency verification of the MBOM and EBOM data can be realized based on the verification identification code of the vehicle parts in the MBOM and EBOM data. It can be seen that this embodiment can automatically perform consistency verification of MBOM and EBOM data, which can improve the efficiency of consistency verification compared with manual verification.

[0165] It should be noted that the vehicle data verification device provided in the above embodiments is only illustrated by the division of the above functional modules when verifying vehicle data. In practical applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the computer device can be divided into different functional modules to complete all or part of the functions described above. In addition, the vehicle data verification device and the vehicle data verification method embodiments provided in the above embodiments belong to the same concept, and their specific implementation process can be found in the method embodiments, which will not be repeated here.

[0166] Figure 7 is a schematic diagram of a computer device according to an embodiment of this application. The computer device 700 can be a portable mobile terminal, such as 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 700 may also be referred to as a user device, portable terminal, laptop terminal, desktop terminal, or other names.

[0167] Typically, computer device 700 includes a processor 701 and a memory 702.

[0168] Processor 701 may include one or more processing cores, such as a quad-core processor, an octa-core processor, etc. Processor 701 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 701 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 701 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 701 may also include an AI (Artificial Intelligence) processor, which is used to handle computational operations related to machine learning.

[0169] The memory 702 may include one or more computer-readable storage media, which may be non-transitory. The memory 702 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 702 are used to store at least one program code, which is executed by the processor 701 to implement the verification of vehicle data provided in the method embodiments of this application.

[0170] In some embodiments, the computer device 700 may also optionally include a peripheral device interface 703 and at least one peripheral device. The processor 701, memory 702, and peripheral device interface 703 can be connected via a bus or signal line. Each peripheral device can be connected to the peripheral device interface 703 via a bus, signal line, or circuit board. Specifically, the peripheral device includes at least one of the following: a radio frequency circuit 704, a display screen 705, a camera assembly 706, an audio circuit 707, and a power supply 708.

[0171] Peripheral device interface 703 can be used to connect at least one I / O (Input / Output) related peripheral device to processor 701 and memory 702. In some embodiments, processor 701, memory 702 and peripheral device interface 703 are integrated on the same chip or circuit board; in some other embodiments, any one or two of processor 701, memory 702 and peripheral device interface 703 can be implemented on separate chips or circuit boards, which is not limited in this embodiment.

[0172] The radio frequency (RF) circuit 704 is used to receive and transmit RF (Radio Frequency) signals, also known as electromagnetic signals. The RF circuit 704 communicates with communication networks and other communication devices via electromagnetic signals. The RF circuit 704 converts electrical signals into electromagnetic signals for transmission, or converts received electromagnetic signals back into electrical signals. Optionally, the RF circuit 704 includes: an antenna system, an RF transceiver, one or more amplifiers, a tuner, an oscillator, a digital signal processor, a codec chipset, a user identity module card, etc. The RF circuit 704 can communicate with other terminals through at least one wireless communication protocol. This wireless communication protocol includes, but is not limited to: the World Wide Web, metropolitan area networks, intranets, various generations of mobile communication networks (2G, 3G, 4G, and 5G), wireless local area networks, and / or WiFi (Wireless Fidelity) networks. In some embodiments, the RF circuit 704 may also include circuitry related to NFC (Near Field Communication), which is not limited in this application.

[0173] Display screen 705 is used to display a UI (User Interface). This UI may include graphics, text, icons, videos, and any combination thereof. When display screen 705 is a touch display screen, it also has the ability to collect touch signals on or above its surface. These touch signals can be input as control signals to processor 701 for processing. In this case, display screen 705 can also be used to provide virtual buttons and / or a virtual keyboard, also known as soft buttons and / or a soft keyboard. In some embodiments, display screen 705 may be a single screen, disposed on the front panel of computer device 700; in other embodiments, display screen 705 may be at least two screens, disposed on different surfaces of computer device 700 or in a folded design; in other embodiments, display screen 705 may be a flexible display screen, disposed on a curved or folded surface of computer device 700. Furthermore, display screen 705 may be configured as a non-rectangular irregular shape, i.e., a non-rectangular screen. Display screen 705 may be made of materials such as LCD (Liquid Crystal Display) or OLED (Organic Light-Emitting Diode).

[0174] The camera assembly 706 is used to acquire images or videos. Optionally, the camera assembly 706 includes a front-facing camera and a rear-facing camera. Typically, the front-facing camera is located on the front panel of the terminal, and the rear-facing camera is located on the back of the terminal. In some embodiments, there are at least two rear-facing cameras, which are any one of a main camera, a depth-sensing camera, a wide-angle camera, and a telephoto camera, to achieve background blurring by fusion of the main camera and the depth-sensing camera, panoramic shooting by fusion of the main camera and the wide-angle camera, VR (Virtual Reality) shooting, or other fusion shooting functions. In some embodiments, the camera assembly 706 may also include a flash. The flash can be a single-color temperature flash or a dual-color temperature flash. A dual-color temperature flash refers to a combination of a warm-light flash and a cool-light flash, which can be used for light compensation at different color temperatures.

[0175] The audio circuit 707 may include a microphone and a speaker. The microphone is used to collect sound waves from the user and the environment, converting the sound waves into electrical signals that are input to the processor 701 for processing, or input to the radio frequency circuit 704 for voice communication. For stereo sound acquisition or noise reduction purposes, multiple microphones may be used, each located in a different part of the computer device 700. The microphone may also be an array microphone or an omnidirectional microphone. The speaker is used to convert electrical signals from the processor 701 or the radio frequency circuit 704 into sound waves. The speaker may be a conventional diaphragm speaker or a piezoelectric ceramic speaker. When the speaker is a piezoelectric ceramic speaker, it can convert electrical signals not only into audible sound waves but also into inaudible sound waves for purposes such as distance measurement. In some embodiments, the audio circuit 707 may also include a headphone jack.

[0176] Power supply 708 is used to supply power to the various components in computer device 700. Power supply 708 can be AC ​​power, DC power, a disposable battery, or a rechargeable battery. When power supply 708 includes a rechargeable battery, the rechargeable battery can be a wired rechargeable battery or a wireless rechargeable battery. A wired rechargeable battery is a battery that is charged via a wired line, while a wireless rechargeable battery is a battery that is charged via a wireless coil. The rechargeable battery can also be used to support fast charging technology.

[0177] In some embodiments, the computer device 700 further includes one or more sensors 709. The one or more sensors 709 include, but are not limited to, an accelerometer 710, a gyroscope 711, a pressure sensor 712, an optical sensor 713, and a proximity sensor 714.

[0178] Accelerometer 710 can detect the magnitude of acceleration along the three coordinate axes of a coordinate system established by computer device 700. For example, accelerometer 710 can be used to detect the components of gravitational acceleration along the three coordinate axes. Processor 701 can control display screen 705 to display the user interface in either a landscape or portrait view based on the gravitational acceleration signal acquired by accelerometer 710. Accelerometer 710 can also be used for games or for acquiring user motion data.

[0179] The gyroscope sensor 711 can detect the orientation and rotation angle of the computer device 700. The gyroscope sensor 711, in conjunction with the accelerometer sensor 710, can collect 3D motion data from the user on the computer device 700. Based on the data collected by the gyroscope sensor 711, the processor 701 can perform the following functions: motion sensing (e.g., changing the UI based on the user's tilt), image stabilization during shooting, game control, and inertial navigation.

[0180] The pressure sensor 712 can be disposed on the side bezel of the computer device 700 and / or on the lower layer of the display screen 705. When the pressure sensor 712 is disposed on the side bezel of the computer device 700, it can detect the user's grip signal on the computer device 700, and the processor 701 can perform left / right hand recognition or quick operation based on the grip signal collected by the pressure sensor 712. When the pressure sensor 712 is disposed on the lower layer of the display screen 705, the processor 701 can control the operable controls on the UI interface based on the user's pressure operation on the display screen 705. The operable controls include at least one of button controls, scroll bar controls, icon controls, and menu controls.

[0181] An optical sensor 713 is used to collect ambient light intensity. In one embodiment, the processor 701 can control the display brightness of the display screen 705 based on the ambient light intensity collected by the optical sensor 713. Specifically, when the ambient light intensity is high, the display brightness of the display screen 705 is increased; when the ambient light intensity is low, the display brightness of the display screen 705 is decreased. In another embodiment, the processor 701 can also dynamically adjust the shooting parameters of the camera assembly 706 based on the ambient light intensity collected by the optical sensor 713.

[0182] A proximity sensor 714, also known as a distance sensor, is typically located on the front panel of a computer device 700. The proximity sensor 714 is used to detect the distance between the user and the front of the computer device 700. In one embodiment, when the proximity sensor 714 detects that the distance between the user and the front of the computer device 700 is gradually decreasing, the processor 701 controls the display screen 705 to switch from a screen-on state to a screen-off state; when the proximity sensor 714 detects that the distance between the user and the front of the computer device 700 is gradually increasing, the processor 701 controls the display screen 705 to switch from a screen-off state to a screen-on state.

[0183] Those skilled in the art will understand that the structure shown in FIG7 does not constitute a limitation on the computer device 700, and may include more or fewer components than shown, or combine certain components, or employ different component arrangements.

[0184] This application also provides a computer-readable storage medium storing at least one piece of program code, which is loaded and executed by a processor to implement the vehicle data verification method described in any of the above implementations. Optionally, the storage medium may be a non-transitory computer-readable storage medium, such as ROM (Read-Only Memory), RAM (Random Access Memory), CD-ROM (Compact Disc Read-Only Memory), magnetic tape, floppy disk, and optical data storage device.

[0185] This application also provides a computer program product that stores at least one piece of program code, which is loaded and executed by a processor to implement the vehicle data verification method shown in the above embodiments.

[0186] In some embodiments, the computer program product involved in the present application can be deployed and executed on a computer device, or on multiple computer devices located in one location, or on multiple computer devices distributed in multiple locations and interconnected through a communication network. Multiple computer devices distributed in multiple locations and interconnected through a communication network can form a blockchain system.

[0187] 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.

[0188] The above description is only for the purpose of enabling those skilled in the art to understand the technical solution 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 method for verifying vehicle data, wherein, The method includes: The vehicle part number is determined, and the vehicle part number is used to identify the vehicle configuration; Based on the vehicle material identifier, the manufacturing bill of materials (MBOM) data is obtained from the enterprise resource planning (ERP) system. The MBOM data includes the first BOM data of multiple first vehicle parts corresponding to the vehicle configuration managed in the ERP system. The first BOM data includes the manufacturing material information of the first vehicle parts. Based on the vehicle material identifier, the Engineering Bill of Materials (EBOM) data is obtained from the BOM system. The EBOM data includes the second BOM data of multiple second vehicle parts corresponding to the vehicle configuration managed in the BOM system. The second BOM data includes the engineering material information of the second vehicle parts. Based on the manufacturing material information of the plurality of first vehicle parts, the verification identification code of the plurality of first vehicle parts is determined, and based on the engineering material information of the plurality of second vehicle parts, the verification identification code of the plurality of second vehicle parts is determined. Based on the verification identifiers of the plurality of first vehicle parts and the verification identifiers of the plurality of second vehicle parts, a consistency check is performed on the MBOM data and the EBOM data to obtain a consistency check result.

2. The method according to claim 1, wherein, The consistency check of the MBOM data and the EBOM data based on the verification identifier codes of the plurality of first vehicle parts and the plurality of second vehicle parts, to obtain the consistency check result, includes: The verification identification codes of the plurality of first vehicle parts and the verification identification codes of the plurality of second vehicle parts are compared. If there is no engineering material information for a second vehicle part that is identical to the first vehicle part in the EBOM data, the consistency check result is determined to be a discrepancy, and the discrepancy information is that there are overlapping parts or differences in quantity in the MBOM data. The overlapping parts are vehicle parts that are generated by different design departments and manufacturing departments that generate the MBOM data. If the MBOM data does not contain manufacturing material information for a first vehicle part that is identical to the second vehicle part, the consistency check result is determined to be a discrepancy. The discrepancy information is that the EBOM data contains a printed part, which is a vehicle part that is pasted on the vehicle body but is not present in the MBOM data.

3. The method according to claim 1, wherein, The consistency check of the MBOM data and the EBOM data based on the verification identifier codes of the plurality of first vehicle parts and the plurality of second vehicle parts, to obtain the consistency check result, includes: Based on the verification codes of the plurality of first vehicle parts and the verification codes of the plurality of second vehicle parts, a target vehicle part is determined, wherein the target vehicle part is the same vehicle part but has a different verification code. The consistency verification result is determined based on the manufacturing material information and engineering material information of the target vehicle parts.

4. The method according to claim 3, wherein, The determination of the consistency verification result based on the manufacturing material information and engineering material information of the target vehicle parts includes: Based on the multiple attribute information included in the manufacturing material information of the target vehicle part and the multiple attribute information included in the engineering material information of the target vehicle part, the attribute information that is different is determined. If the attribute information of the difference is a part identifier, the consistency verification result is determined to be that a difference exists, and the difference information is a part identifier; If the attribute information of the difference is the number of parts, then the consistency verification result is determined to be that there is a difference, and the difference information is the number of parts.

5. The method according to claim 3, wherein, The determination of the consistency verification result based on the manufacturing material information and engineering material information of the target vehicle parts includes: Based on the multiple attribute information included in the manufacturing material information of the target vehicle part and the multiple attribute information included in the engineering material information of the target vehicle part, the attribute information that is different is determined. The attribute information of the difference is part level information, which determines the first parent part of the target vehicle part in the MBOM data and the second parent part in the EBOM data; If the first parent part and the second parent part are the same, then the first child part of the target vehicle part in the MBOM data and the second child part in the EBOM data are determined. The consistency verification result is determined based on the attribute information of the first sub-level part and the attribute information of the second sub-level part.

6. The method according to claim 1, wherein, The method further includes: Based on the consistency verification results, at least one discrepancy is determined; The at least one difference information is summarized to obtain difference summary information; Output the summary information of the differences.

7. A vehicle data verification device, wherein, The device includes: The first determining module is used to determine the vehicle material identifier of the vehicle, wherein the vehicle material identifier is used to identify the vehicle configuration of the vehicle; The first acquisition module is used to acquire manufacturing bill of materials (MBOM) data from the enterprise resource planning (ERP) system based on the vehicle material identifier. The MBOM data includes the first BOM data of multiple first vehicle parts corresponding to the vehicle configuration managed in the ERP system. The first BOM data includes the manufacturing material information of the first vehicle parts. The second acquisition module is used to acquire Engineering Bill of Materials (EBOM) data from the BOM system based on the vehicle material identifier. The EBOM data includes the second BOM data of multiple second vehicle parts corresponding to the vehicle configuration managed in the BOM system. The second BOM data includes the engineering material information of the second vehicle parts. The second determining module is used to determine the verification identification code of the plurality of first vehicle parts based on the manufacturing material information of the plurality of first vehicle parts, and to determine the verification identification code of the plurality of second vehicle parts based on the engineering material information of the plurality of second vehicle parts. The verification module is used to perform consistency verification on the MBOM data and the EBOM data based on the verification identification codes of the plurality of first vehicle parts and the verification identification codes of the plurality of second vehicle parts, and obtain a consistency verification result.

8. The apparatus according to claim 7, wherein, The verification module is used to compare the verification identification codes of the plurality of first vehicle parts and the verification identification codes of the plurality of second vehicle parts; if there is no engineering material information for a second vehicle part that is identical to that of a first vehicle part in the EBOM data, the consistency verification result is determined to be inconsistent, and the inconsistency information is that there are overlapping parts or differences in quantity in the MBOM data. The overlapping parts are vehicle parts from different design departments that generate the EBOM data and different manufacturing departments that generate the MBOM data. If there is no manufacturing material information for a first vehicle part that is identical to that of a second vehicle part in the MBOM data, the consistency verification result is determined to be inconsistent, and the inconsistency information is that there are printed parts in the EBOM data. The printed parts are vehicle parts that are pasted on the vehicle body but are not present in the MBOM data.

9. The apparatus according to claim 7, wherein, The verification module is used to determine a target vehicle part based on the verification identification codes of the plurality of first vehicle parts and the verification identification codes of the plurality of second vehicle parts, wherein the target vehicle part is the same vehicle part but has different verification identification codes. The consistency verification result is determined based on the manufacturing material information and engineering material information of the target vehicle parts.

10. The apparatus according to claim 9, wherein, The verification module is used to determine the attribute information of the difference based on multiple attribute information included in the manufacturing material information of the target vehicle part and multiple attribute information included in the engineering material information of the target vehicle part; when the attribute information of the difference is a part identifier, the consistency verification result is determined to be that there is a difference, and the difference information is a part identifier; when the attribute information of the difference is the number of parts, the consistency verification result is determined to be that there is a difference, and the difference information is the number of parts.

11. The apparatus according to claim 9, wherein, The verification module is used to determine the differing attribute information based on multiple attribute information included in the manufacturing material information and multiple attribute information included in the engineering material information of the target vehicle part; if the differing attribute information is part level information, it determines the first parent part of the target vehicle part in the MBOM data and the second parent part in the EBOM data; if the first parent part and the second parent part are the same, it determines the first child part of the target vehicle part in the MBOM data and the second child part in the EBOM data. The consistency verification result is determined based on the attribute information of the first sub-level part and the attribute information of the second sub-level part.

12. The apparatus according to claim 7, wherein, The device further includes: The third determining module is used to determine at least one difference based on the consistency verification result; The summarization module is used to summarize the at least one difference information to obtain difference summary information; The output module is used to output the summary information of the differences.

13. A computer device, wherein, The computer device includes a main control module, which includes a processor and a memory. The memory stores at least one piece of program code, which is loaded and executed by the processor to implement the vehicle data verification method as described in any one of claims 1 to 6.

14. A computer-readable storage medium, wherein, The storage medium stores at least one piece of program code, which is loaded and executed by a processor to implement the vehicle data verification method as described in any one of claims 1 to 6.

15. A computer program product, wherein, The product stores at least one piece of program code, which is executed by a processor to implement the vehicle data verification method as described in any one of claims 1 to 6.

Images