Cross-system vehicle data verification method, device, equipment and storage medium

Abstract

The present invention discloses a cross-system whole vehicle data verification method, device, equipment and storage medium. The method obtains whole vehicle production detail data and whole vehicle design detail data; performs data cleaning and filtering on the whole vehicle production detail data and the whole vehicle design detail data to obtain the cleaned and filtered production data and design data; compares the production data with the design data according to the data structure to generate difference data, and sends an email reminder based on the difference data. The method can automatically identify the difference data and send an email reminder to the responsible person, effectively avoiding the problems of verification delay, omission and untimely response, ensuring the timeliness of production data verification, and at the same time ensuring the integrity of whole vehicle production verification, improving the accuracy of cross-system whole vehicle data verification, and improving the speed and efficiency of cross-system whole vehicle data verification.

Description

Technical Field

[0001] The present invention relates to the field of vehicle manufacturing technology, and in particular to a cross-system vehicle data verification method, device, equipment and storage medium. Background Art

[0002] According to the actual needs of vehicle manufacturers, data management is composed of different business systems. Design data and production data belong to different data platforms and are stored and managed according to corresponding management logic.

[0003] Manufacturing companies need to ensure that the differences between production details and design details are under control. Therefore, business personnel need to frequently check and manage various data to ensure the validity and accuracy of production data, and invest a lot of manpower and material resources in this area.

[0004] The existing data acquisition method is to obtain system data details based on the business system and the second system data, record the business system data voucher, and associate it with the same type of data in the second system through the key identification code of the voucher; by performing data table calculation on the above original business data and the second system data, it is determined whether there are differences; if there are differences, the differences are located according to the query module, and the reasons for the differences are analyzed; however, this method has the following disadvantages: only a single-layer data direct table is performed, and multi-layer data with complex structures cannot be compared; there is no timeliness management for business scenarios, resulting in weak business timeliness or omissions in business work; there is redundant difference data, which is prone to the risk of analysis errors and omissions, and it relies on manual labor, and the data verification efficiency is low. Summary of the invention

[0005] The main purpose of the present invention is to provide a cross-system vehicle data verification method, device, equipment and storage medium, aiming to solve the technical problems in the prior art of poor data verification timeliness, risk of errors and omissions, and low data verification efficiency.

[0006] In a first aspect, the present invention provides a cross-system vehicle data verification method, the cross-system vehicle data verification method comprising the following steps:

[0007] Obtain vehicle production detailed data and vehicle design detailed data;

[0008] Performing data cleaning and filtering on the vehicle production detail data and the vehicle design detail data to obtain cleaned and filtered production data and design data;

[0009] The production data and the design data are compared according to the data structure to generate difference data, and an email reminder is issued according to the difference data.

[0010] Optionally, the obtaining of vehicle production detailed data and vehicle design detailed data includes:

[0011] In response to the detailed data request sent by the business system, obtain the vehicle code of the vehicle production and the corresponding production effective date;

[0012] Determine the corresponding vehicle production detailed data from the production data center according to the vehicle code and the production effective date;

[0013] The backup production detail data is obtained from the manufacturing data center, and the whole vehicle design detail data is obtained based on the backup production detail data.

[0014] Optionally, before the vehicle code and the corresponding production effective date of the vehicle are obtained in response to the detailed data request sent by the business system, the cross-system vehicle data verification method further includes:

[0015] Split the production requirements initiated by the business system into vehicle production codes and corresponding production times;

[0016] Retrieving the production vehicle code in the vehicle code library, and judging whether the production vehicle code is in a production-ready state according to the retrieval result;

[0017] When the production vehicle code is in the production-ready state, determining whether the production time is within a valid range;

[0018] When the production time is within a valid range, the business system sends a detailed data request to the production data center.

[0019] Optionally, the step of obtaining backup production detail data from the manufacturing data center and obtaining vehicle design detail data according to the backup production detail data includes:

[0020] Obtain backup production detail data from the manufacturing data center, and determine the backup vehicle code and production attribute information based on the backup production detail data;

[0021] Determining whether the backup vehicle code has stopped production;

[0022] When the production of the backup vehicle code has not been stopped, the valid vehicle detail data corresponding to the corresponding time point is obtained through the design center according to the backup vehicle code and the production attribute information, and the valid vehicle detail data is used as the vehicle design detail data.

[0023] Optionally, the performing data cleaning and filtering on the vehicle production detail data and the vehicle design detail data to obtain the cleaned and filtered production data and design data includes:

[0024] According to preset business requirements, redundant data and reasonable difference detail data in the vehicle production detail data and the vehicle design detail data are cleaned and filtered to obtain cleaned and filtered production data and design data.

[0025] Optionally, comparing the production data and the design data according to the data structure to generate difference data, and sending an email reminder according to the difference data, includes:

[0026] Comparing the production data and the design data by different project level codes according to the data structure to obtain data comparison results;

[0027] Differentiate the vehicle models of the data comparison results to obtain a comparison list;

[0028] Mark the difference points and difference fields in the comparison list according to preset business rules to obtain a difference list;

[0029] The difference list is located by the vehicle type field in the vehicle code to obtain a vehicle type classification result, and the difference list and the vehicle type classification result are used as difference data;

[0030] An email reminder is sent based on the difference data.

[0031] Optionally, sending an email reminder based on the difference data includes:

[0032] Differentiate the vehicle series field from the vehicle code, and establish a corresponding relationship between the vehicle series field and the person responsible for the corresponding vehicle series;

[0033] Emails are generated based on the difference data, and are automatically and regularly delivered by vehicle series through the email system.

[0034] In a second aspect, in order to achieve the above-mentioned purpose, the present invention further proposes a cross-system vehicle data verification device, the cross-system vehicle data verification device comprising:

[0035] A data acquisition module is used to acquire detailed vehicle production data and detailed vehicle design data;

[0036] A filtering module, used to clean and filter the vehicle production detail data and the vehicle design detail data to obtain cleaned and filtered production data and design data;

[0037] The checking module is used to compare the production data with the design data according to the data structure, generate difference data, and send an email reminder according to the difference data.

[0038] In the third aspect, in order to achieve the above-mentioned purpose, the present invention also proposes a cross-system whole vehicle data verification device, which includes: a memory, a processor, and a cross-system whole vehicle data verification program stored in the memory and executable on the processor, and the cross-system whole vehicle data verification program is configured to implement the steps of the cross-system whole vehicle data verification method as described above.

[0039] In a fourth aspect, in order to achieve the above-mentioned purpose, the present invention also proposes a storage medium, on which a cross-system whole vehicle data verification program is stored, and when the cross-system whole vehicle data verification program is executed by a processor, the steps of the cross-system whole vehicle data verification method described above are implemented.

[0040] The cross-system whole vehicle data verification method proposed in the present invention obtains whole vehicle production detail data and whole vehicle design detail data; performs data cleaning and filtering on the whole vehicle production detail data and the whole vehicle design detail data to obtain the cleaned and filtered production data and design data; compares the production data with the design data according to the data structure to generate difference data, and sends an email reminder based on the difference data. The method can automatically identify the difference data and send an email reminder to the responsible person, effectively avoiding the problems of delay, omission and untimely response in the verification work, ensuring the timeliness of production data verification, and at the same time ensuring the integrity of whole vehicle production verification, thereby improving the accuracy of cross-system whole vehicle data verification and improving the speed and efficiency of cross-system whole vehicle data verification. BRIEF DESCRIPTION OF THE DRAWINGS

[0041] Figure 1 A schematic diagram of the device structure of the hardware operating environment involved in the embodiment of the present invention;

[0042] Figure 2 This is a flow chart of a first embodiment of a method for checking vehicle data across systems according to the present invention;

[0043] Figure 3 This is a flow chart of a second embodiment of the cross-system vehicle data verification method of the present invention;

[0044] Figure 4 A flowchart for obtaining production details in the cross-system vehicle data verification method of the present invention;

[0045] Figure 5 A schematic diagram of a flow chart of a third embodiment of a cross-system vehicle data verification method of the present invention;

[0046] Figure 6 Design a detailed acquisition flow chart for the cross-system vehicle data verification method of the present invention;

[0047] Figure 7 A schematic diagram of a flow chart of a fourth embodiment of a cross-system vehicle data verification method of the present invention;

[0048] Figure 8 This is a flow chart of a fifth embodiment of the cross-system vehicle data verification method of the present invention;

[0049] Fig. 9 A flowchart of a complex hierarchical structure comparison in a cross-system vehicle data verification method of the present invention;

[0050] Fig.10 It is a flow chart of attribute and structure comparison in the cross-system vehicle data verification method of the present invention;

[0051] Fig.11 It is a composition diagram of the checking device in the cross-system vehicle data checking method of the present invention;

[0052] Fig.12 It is a functional module diagram of the first embodiment of the cross-system vehicle data verification device of the present invention.

[0053] The realization of the purpose, functional features and advantages of the present invention will be further explained in conjunction with embodiments and with reference to the accompanying drawings. DETAILED DESCRIPTION

[0054] It should be understood that the specific embodiments described herein are only used to explain the present invention, and are not used to limit the present invention.

[0055] The solution of the embodiment of the present invention is mainly: by obtaining the detailed production data of the whole vehicle and the detailed design data of the whole vehicle; performing data cleaning and filtering on the detailed production data of the whole vehicle and the detailed design data of the whole vehicle to obtain the production data and design data after cleaning and filtering; comparing the production data and the design data according to the data structure to generate difference data, and sending email reminders according to the difference data, which can automatically identify the difference data and send email reminders to the responsible person, effectively avoiding the problems of delay, omission and untimely response in the verification work, ensuring the timeliness of the production data verification, and at the same time ensuring the integrity of the whole vehicle production verification, improving the accuracy of the cross-system whole vehicle data verification, and improving the speed and efficiency of the cross-system whole vehicle data verification, and solving the technical problems of poor timeliness of data verification, risk of errors and omissions, and low data verification efficiency in the prior art.

[0056] Reference Figure 1 , Figure 1 The figure is a schematic diagram of the device structure of the hardware operating environment involved in the embodiment of the present invention.

[0057] like Figure 1As shown, the device may include: a processor 1001, such as a CPU, a communication bus 1002, a user interface 1003, a network interface 1004, and a memory 1005. Among them, the communication bus 1002 is used to realize the connection and communication between these components. The user interface 1003 may include a display screen (Display), an input unit such as a keyboard (Keyboard), and the optional user interface 1003 may also include a standard wired interface and a wireless interface. The network interface 1004 may optionally include a standard wired interface and a wireless interface (such as a Wi-Fi interface). The memory 1005 may be a high-speed RAM memory, or it may be a stable memory (Non-Volatile Memory), such as a disk memory. The memory 1005 may optionally be a storage device independent of the aforementioned processor 1001.

[0058] Those skilled in the art will understand that Figure 1 The device structure shown in the figure does not constitute a limitation of the device, and may include more or less components than shown in the figure, or combine certain components, or arrange the components differently.

[0059] like Figure 1 As shown, the memory 1005 as a storage medium may include an operating device, a network communication module, a user interface module, and a cross-system vehicle data verification program.

[0060] The device of the present invention calls the cross-system vehicle data verification program stored in the memory 1005 through the processor 1001, and performs the following operations:

[0061] Obtain vehicle production detailed data and vehicle design detailed data;

[0062] Performing data cleaning and filtering on the vehicle production detail data and the vehicle design detail data to obtain cleaned and filtered production data and design data;

[0063] The production data and the design data are compared according to the data structure to generate difference data, and an email reminder is issued according to the difference data.

[0064] The device of the present invention calls the cross-system vehicle data verification program stored in the memory 1005 through the processor 1001, and also performs the following operations:

[0065] In response to the detailed data request sent by the business system, obtain the vehicle code of the vehicle production and the corresponding production effective date;

[0066] Determine the corresponding vehicle production detailed data from the production data center according to the vehicle code and the production effective date;

[0067] The backup production detail data is obtained from the manufacturing data center, and the whole vehicle design detail data is obtained based on the backup production detail data.

[0068] The device of the present invention calls the cross-system vehicle data verification program stored in the memory 1005 through the processor 1001, and also performs the following operations:

[0069] Split the production requirements initiated by the business system into vehicle production codes and corresponding production times;

[0070] Retrieving the production vehicle code in the vehicle code library, and judging whether the production vehicle code is in a production-ready state according to the retrieval result;

[0071] When the production vehicle code is in the production-ready state, determining whether the production time is within a valid range;

[0072] When the production time is within a valid range, the business system sends a detailed data request to the production data center.

[0073] The device of the present invention calls the cross-system vehicle data verification program stored in the memory 1005 through the processor 1001, and also performs the following operations:

[0074] Obtain backup production detail data from the manufacturing data center, and determine the backup vehicle code and production attribute information based on the backup production detail data;

[0075] Determining whether the backup vehicle code has stopped production;

[0076] When the production of the backup vehicle code has not been stopped, the valid vehicle detail data corresponding to the corresponding time point is obtained through the design center according to the backup vehicle code and the production attribute information, and the valid vehicle detail data is used as the vehicle design detail data.

[0077] The device of the present invention calls the cross-system vehicle data verification program stored in the memory 1005 through the processor 1001, and also performs the following operations:

[0078] According to preset business requirements, redundant data and reasonable difference detail data in the vehicle production detail data and the vehicle design detail data are cleaned and filtered to obtain cleaned and filtered production data and design data.

[0079] The device of the present invention calls the cross-system vehicle data verification program stored in the memory 1005 through the processor 1001, and also performs the following operations:

[0080] Comparing the production data and the design data by different project level codes according to the data structure to obtain data comparison results;

[0081] Differentiate the vehicle models of the data comparison results to obtain a comparison list;

[0082] Mark the difference points and difference fields in the comparison list according to preset business rules to obtain a difference list;

[0083] The difference list is located by the vehicle type field in the vehicle code to obtain a vehicle type classification result, and the difference list and the vehicle type classification result are used as difference data;

[0084] An email reminder is sent based on the difference data.

[0085] The device of the present invention calls the cross-system vehicle data verification program stored in the memory 1005 through the processor 1001, and also performs the following operations:

[0086] Differentiate the vehicle series field from the vehicle code, and establish a corresponding relationship between the vehicle series field and the person responsible for the corresponding vehicle series;

[0087] Emails are generated based on the difference data, and are automatically and regularly delivered by vehicle series through the email system.

[0088] Through the above scheme, this embodiment obtains the vehicle production detail data and the vehicle design detail data; performs data cleaning and filtering on the vehicle production detail data and the vehicle design detail data to obtain the cleaned and filtered production data and design data; compares the production data and the design data according to the data structure to generate difference data, and sends email reminders based on the difference data. The method can automatically identify the difference data and send email reminders to the responsible person, effectively avoiding the problems of delayed verification, omissions and untimely response, ensuring the timeliness of production data verification, and at the same time ensuring the integrity of vehicle production verification, improving the accuracy of cross-system vehicle data verification, and improving the speed and efficiency of cross-system vehicle data verification.

[0089] Based on the above hardware structure, an embodiment of the cross-system vehicle data verification method of the present invention is proposed.

[0090] Reference Figure 2 , Figure 2 It is a flowchart diagram of the first embodiment of the cross-system vehicle data verification method of the present invention.

[0091] In a first embodiment, the cross-system vehicle data verification method comprises the following steps:

[0092] Step S10: Obtain vehicle production detailed data and vehicle design detailed data.

[0093] It should be noted that the vehicle production detailed data is the detailed data generated during the vehicle production process, and the vehicle design detailed data is the detailed data during the vehicle design process.

[0094] Step S20: clean and filter the vehicle production detail data and the vehicle design detail data to obtain cleaned and filtered production data and design data.

[0095] It can be understood that data cleaning and filtering of the vehicle production detail data and the vehicle design detail data can ensure the validity of the verification data and avoid the influence of redundant data, thereby obtaining the cleaned and filtered production data and design data.

[0096] Step S30: compare the production data and the design data according to the data structure, generate difference data, and send an email reminder based on the difference data.

[0097] It should be understood that the production data and the design data are compared according to the data structure to generate corresponding difference data after the comparison between the production data and the design data. The difference data can be sent via email to remind relevant personnel.

[0098] Through the above scheme, this embodiment obtains the vehicle production detail data and the vehicle design detail data; performs data cleaning and filtering on the vehicle production detail data and the vehicle design detail data to obtain the cleaned and filtered production data and design data; compares the production data and the design data according to the data structure to generate difference data, and sends email reminders based on the difference data. The method can automatically identify the difference data and send email reminders to the responsible person, effectively avoiding the problems of delayed verification, omissions and untimely response, ensuring the timeliness of production data verification, and at the same time ensuring the integrity of vehicle production verification, improving the accuracy of cross-system vehicle data verification, and improving the speed and efficiency of cross-system vehicle data verification.

[0099] Further, Figure 3 FIG. 1 is a flow chart of a second embodiment of the cross-system vehicle data verification method of the present invention. Figure 3 As shown, a second embodiment of the cross-system vehicle data verification method of the present invention is proposed based on the first embodiment. In this embodiment, the step S10 specifically includes the following steps:

[0100] Step S11, in response to the detailed data request sent by the business system, obtain the vehicle code of the vehicle production and the corresponding production effective date.

[0101] It should be noted that the business can initiate a request for calculation of vehicle production data, i.e., a detailed data request, according to demand, whereby the business system obtains the vehicle code for calculating vehicle production and the corresponding production effective date, and triggers the verification device at the same time.

[0102] Furthermore, before step S11, the following steps are also included:

[0103] Split the production requirements initiated by the business system into vehicle production codes and corresponding production times;

[0104] Retrieving the production vehicle code in the vehicle code library, and judging whether the production vehicle code is in a production-ready state according to the retrieval result;

[0105] When the production vehicle code is in the production-ready state, determining whether the production time is within a valid range;

[0106] When the production time is within a valid range, the business system sends a detailed data request to the production data center.

[0107] It can be understood that the comparison rules can be triggered and the comparison vehicle model can be determined and the production details data can be obtained. The production vehicle code can be retrieved in the vehicle code library, and whether the production vehicle code is in a producible state can be determined based on the retrieval results. It can be determined whether the production time is within the valid range. If it is within the range, a detailed data request can be sent to the production data center.

[0108] In the specific implementation, Figure 4 As shown, Figure 4 This is a flowchart of obtaining production details in the cross-system vehicle data verification method of the present invention, see Figure 4 , it is necessary to obtain the vehicle code and the effective time of the vehicle details through the specific production information imported by the business. First, the business system (PLS) initiates the production demand, which is automatically split into the vehicle code and the corresponding production time. Then, through the vehicle code library search, it is confirmed that the imported vehicle code is in a producible state. Secondly, it is determined that the corresponding production time is within the valid range. After the conditional judgment is passed, the PLS system initiates a detailed data request to the production data middle platform (BA) system. The BA system provides the business system 1 with the vehicle detailed data at the corresponding time point based on the vehicle code and the corresponding production time. The manufacturing middle platform (BA) transmits the vehicle detailed data to the business system 1 (PLS) and simultaneously transmits the same data to the design middle platform (PI).

[0109] Step S12: determining corresponding vehicle production detailed data from the production data according to the vehicle code and the production effective date.

[0110] It is understandable that based on the vehicle code and the effective date of production data, the business system applies for complete vehicle production details through the data middle platform.

[0111] Step S13: Obtain backup production detail data from the manufacturing data center, and obtain vehicle design detail data based on the backup production detail data.

[0112] It should be understood that the data middle platform, based on the rules, while responding to the needs of the business system, will actively back up the vehicle production details data to the data middle platform of the upstream system platform. The backup details data includes a complete vehicle details list, vehicle code and corresponding production effective date. This data is stored in the design middle platform data pool.

[0113] Through the above scheme, this embodiment obtains the vehicle code and the corresponding production effective date of the vehicle production by responding to the detailed data request sent by the business system; determines the corresponding vehicle production detailed data from the production data center according to the vehicle code and the production effective date; obtains the backup production detailed data from the manufacturing data center, and obtains the vehicle design detailed data according to the backup production detailed data, thereby ensuring the integrity of the vehicle detailed data and improving the accuracy and efficiency of cross-system vehicle data verification.

[0114] Further, Figure 5 FIG. 1 is a flow chart of a third embodiment of the cross-system vehicle data verification method of the present invention. Figure 5 As shown, a third embodiment of the cross-system vehicle data verification method of the present invention is proposed based on the second embodiment. In this embodiment, the step S13 specifically includes the following steps:

[0115] Step S131, obtaining backup production detail data from the manufacturing data center, and determining the backup vehicle code and production attribute information based on the backup production detail data.

[0116] It should be noted that the design middle platform determines attribute information such as the vehicle code and effective time information based on the backup production details transmitted by the manufacturing data middle platform.

[0117] Step S132: Determine whether the backup vehicle code has stopped production.

[0118] It is understandable that after obtaining the backup vehicle code and production attribute information, it will be determined whether the backup vehicle code has stopped production. If production has stopped, an abnormal alarm will be issued.

[0119] In the specific implementation, Figure 6 As shown, Figure 6 The detailed acquisition flow chart is designed in the cross-system vehicle data verification method of the present invention, referring to Figure 6 After the business system inputs the vehicle details and the corresponding production time, the vehicle code is split according to the vehicle details, and the vehicle code is retrieved to see whether production has been stopped. If production has been stopped, an abnormal alarm is issued, and the vehicle design details of the day are extracted according to the rules, that is, the design middle-end system data extracts the backup design data; through the vehicle details and the corresponding time input by the manufacturing system, a backup is generated to generate the design details table of the vehicle model on that day.

[0120] Step S133: When the production of the backup vehicle code has not been stopped, the valid vehicle detail data corresponding to the corresponding time point is obtained through the design center according to the backup vehicle code and the production attribute information, and the valid vehicle detail data is used as the vehicle design detail data.

[0121] It should be understood that when the production of the backup vehicle code has not been stopped, the vehicle design details for the day can be extracted according to the rules. The design middle station stores the valid vehicle details table corresponding to the corresponding time point into the data pool based on the above vehicle code and production attribute information, that is, the valid vehicle detail data corresponding to the corresponding time point is obtained through the design middle station according to the backup vehicle code and the production attribute information, and the valid vehicle detail data is used as the vehicle design detail data.

[0122] This embodiment adopts the above scheme, obtains backup production detail data from the manufacturing data middle station, determines the backup vehicle code and production attribute information according to the backup production detail data; judges whether the backup vehicle code has stopped production; when the backup vehicle code has not stopped production, obtains the valid vehicle detail data corresponding to the corresponding time point through the design middle station according to the backup vehicle code and the production attribute information, and uses the valid vehicle detail data as the vehicle design detail data; ensures the integrity of the vehicle detail data, and improves the accuracy and efficiency of cross-system vehicle data verification.

[0123] Further, Figure 7 FIG. 4 is a flow chart of a fourth embodiment of the cross-system vehicle data verification method of the present invention. Figure 7 As shown, a fourth embodiment of the cross-system vehicle data verification method of the present invention is proposed based on the first embodiment. In this embodiment, the step S20 specifically includes the following steps:

[0124] Step S21: Clean and filter the redundant data and the reasonable difference data in the vehicle production detail data and the vehicle design detail data according to preset business requirements to obtain the cleaned and filtered production data and design data.

[0125] It should be noted that the corresponding redundant data in the two data details can be eliminated according to the pre-set business requirements. When the structural data does not meet the business needs, for example, when the structure field "ITEM-PID" is specified as "A610010", or the data attribute field "assembly route" is "CG" or "FZ", the data will not be included in the comparison.

[0126] In the specific implementation, the corresponding detailed data in the data pool is cleaned according to the set business rules to ensure the validity of the data used for verification and avoid the impact of redundant data. Such redundant data mainly includes secondary procurement parts, non-specified production data, drawing standard data and some non-procurement units. At the same time, this step will filter some confirmed reasonable difference detailed data, such as some confirmed background data of system batch changes.

[0127] Through the above scheme, this embodiment cleans and filters the redundant data and reasonable difference detail data in the vehicle production detail data and the vehicle design detail data according to preset business needs, obtains the cleaned and filtered production data and design data, and can remove redundant data, thereby improving the accuracy of cross-system vehicle data verification and improving the speed and efficiency of cross-system vehicle data verification.

[0128] Further, Figure 8 FIG. 5 is a flow chart of a fifth embodiment of the cross-system vehicle data verification method of the present invention. Figure 8 As shown, a fifth embodiment of the cross-system vehicle data verification method of the present invention is proposed based on the first embodiment. In this embodiment, the step S30 specifically includes the following steps:

[0129] Step S31: Compare the production data and the design data at different project levels according to the data structure to obtain data comparison results.

[0130] It should be noted that the production data and the design data are compared at different project level codes, and the comparison rule is to index by functional primary key, and compare the hierarchical structure, coding and key attributes respectively.

[0131] In the specific implementation, Fig. 9 As shown, Fig. 9 This is a flowchart of the complex hierarchical structure comparison in the cross-system vehicle data verification method of the present invention, referring to Fig. 9 , Fig. 9 To judge based on the data structure, compare each level layer by layer, compare the field attributes of the same level data, record the differences, and after expanding according to the project level, assign structure serial numbers according to the parents and levels, combine and generate each project level code to form a complete level code, and use the level code to perform structural differences.

[0132] In the specific implementation, Fig.10 As shown, Fig.10 This is a flow chart of attribute and structure comparison in the cross-system vehicle data verification method of the present invention, see Fig.10 , the process is divided into three steps:

[0133] 1. Computational layer code

[0134] 1. Calculate the path of each project node in the hierarchy. Assign a hierarchical serial number to each level under the same parent item, for example: 0000 / G33XXXXXXXX~0001 / A120BJ-F0300~0001 / A120110J-B0100~0002 / A120117J-X0100.

[0135] 2. Generate project level codes respectively. The combination is: parent number + structure serial number + / + sub-component code. Then, each level code from the top level to the current level is spliced ​​into a complete level code in the order of expansion.

[0136] Second, matching and comparing structural differences,

[0137] ①Based on the layer code, match the lower-level expansion path starting from the first-level node until the parent node of the current project (the parent nodes must be the same to align)

[0138] ② If the child numbers are the same (or the function codes are the same), they will be aligned; if they do not match, a blank line will be used instead.

[0139] 3. Match and compare attribute differences,

[0140] By default, all data attributes are compared in the same layer structure. Any inconsistencies are marked as differences, and "XX attributes are different" is displayed in the difference column.

[0141] Step S32: Differentiate the data comparison results by vehicle type to obtain a comparison list.

[0142] It should be understood that, based on the data comparison results, a comparison list can be formed according to the vehicle model, and the list can be exported in EXCEL format.

[0143] Step S33: Mark the difference points and difference fields in the comparison list according to preset business rules to obtain a difference list.

[0144] It is understandable that the difference points and difference fields in the comparison list can be marked according to preset business rules, so as to obtain a difference list, which can be used for cause location analysis.

[0145] Step S34: locate the difference list through the vehicle type field in the vehicle code, obtain the vehicle type classification result, and use the difference list and the vehicle type classification result as difference data.

[0146] It should be understood that the vehicle model classification is obtained by locating through the vehicle model field in the vehicle code, and the difference list of a single vehicle is merged and summarized according to the vehicle series classification. The difference list and the vehicle model classification result are then used as difference data, which can be organized and exported according to a standard template.

[0147] Step S35: Send an email reminder based on the difference data.

[0148] It is understandable that email reminders can be made based on the difference data.

[0149] Furthermore, the step S35 specifically includes the following steps:

[0150] Differentiate the vehicle series field from the vehicle code, and establish a corresponding relationship between the vehicle series field and the person responsible for the corresponding vehicle series;

[0151] Emails are generated based on the difference data, and are automatically and regularly delivered by vehicle series through the email system.

[0152] It should be understood that according to the rules, the vehicle series field is split from the whole vehicle code, and a corresponding relationship is established between the vehicle series field and the person responsible for the corresponding vehicle series in the system. After the difference list is generated, it is automatically distributed on a regular basis by vehicle series through the email system; in the specific implementation, the difference data can be organized and exported according to the standard EXCEL template, and the exported EXCEL file can be distributed by email according to the list of persons responsible for the vehicle series.

[0153] In the specific implementation, based on the above analysis method and process, Fig.11 As shown, a checking device is also provided. Fig.11 This is a composition diagram of the verification device in the cross-system vehicle data verification method of the present invention, including a business trigger module: triggering the data verification business and submitting the relevant condition information required for the verification; a condition judgment and data extraction and storage module: extracting data and storing detailed data through data conditions; a data cleaning module: cleaning the stored detailed data; a data comparison and sorting module: comparing and sorting the data, locating the causes; a result export and notification module: the comparison results are exported according to the vehicle model classification and sent to the responsible person according to the rules.

[0154] It can be understood that, according to the characteristics of the detailed production data of the whole vehicle, targeted multi-level comparison is carried out by combining and expanding the layer codes, determining the mode of structure code + parent code comparison, and distinguishing according to the display methods of different difference modes; the problem of difference identification during data verification under complex structures is solved, and at the same time, the difference identification of full attribute comparison of data coded at the same level and project is screened and located, thereby improving the accuracy and speed of production data verification; this embodiment determines the working mode of comparison based on the timeliness characteristics of production release, through the system automatically triggering the comparison mode, ensuring the timeliness of production data verification, and at the same time, automatic comparison can ensure the integrity of verification data, solve the problem of delayed business verification, and ensure the integrity of vehicle production verification; this solution effectively avoids the problems of delayed verification, omissions and untimely response through the system automatically identifying the summary difference list of the vehicle series and automatically reminding the responsible person by email.

[0155] Accordingly, the present invention further provides a cross-system vehicle data verification device.

[0156] Reference Fig.12 , Fig.12 It is a functional module diagram of the first embodiment of the cross-system vehicle data verification device of the present invention.

[0157] In the first embodiment of the cross-system vehicle data verification device of the present invention, the cross-system vehicle data verification device comprises:

[0158] The data acquisition module 10 is used to acquire the vehicle production detailed data and the vehicle design detailed data.

[0159] The filtering module 20 is used to clean and filter the vehicle production detail data and the vehicle design detail data to obtain cleaned and filtered production data and design data.

[0160] The checking module 30 is used to compare the production data with the design data according to the data structure, generate difference data, and send an email reminder according to the difference data.

[0161] The data acquisition module 10 is also used to respond to the detailed data request sent by the business system, obtain the vehicle code and the corresponding production effective date of the vehicle production; determine the corresponding vehicle production detailed data from the production data center according to the vehicle code and the production effective date; obtain the backup production detailed data from the manufacturing data center, and obtain the vehicle design detailed data according to the backup production detailed data.

[0162] The data acquisition module 10 is also used to split the production demand initiated by the business system into a production vehicle code and a corresponding production time; retrieve the production vehicle code in the vehicle code library, and determine whether the production vehicle code is in a producible state based on the retrieval result; when the production vehicle code is in the producible state, determine whether the production time is within a valid range; when the production time is within a valid range, the business system sends a detailed data request to the production data center.

[0163] The data acquisition module 10 is also used to obtain backup production detail data from the manufacturing data center, determine the backup vehicle code and production attribute information based on the backup production detail data; determine whether the backup vehicle code has stopped production; when the backup vehicle code has not stopped production, obtain the valid vehicle detail data corresponding to the corresponding time point through the design center based on the backup vehicle code and the production attribute information, and use the valid vehicle detail data as the vehicle design detail data.

[0164] The filtering module 20 is also used to clean and filter the redundant data and reasonable difference detailed data in the vehicle production detailed data and the vehicle design detailed data according to preset business requirements to obtain the cleaned and filtered production data and design data.

[0165] The checking module 30 is further used to compare the production data and the design data at different project levels according to the data structure to obtain data comparison results; to differentiate vehicle models based on the data comparison results to obtain a comparison list; to mark the difference points and difference fields in the comparison list according to preset business rules to obtain a difference list; to locate the difference list through the vehicle model field in the vehicle code to obtain a vehicle model classification result, and to use the difference list and the vehicle model classification result as difference data; and to issue an email reminder based on the difference data.

[0166] The checking module 30 is further used to obtain a vehicle series field from the whole vehicle code by difference, and establish a corresponding relationship between the vehicle series field and the person responsible for the corresponding vehicle series; generate an email based on the difference data, and automatically send the email on a scheduled basis by vehicle series through the email system.

[0167] Among them, the steps implemented by each functional module of the cross-system whole vehicle data verification device can refer to the various embodiments of the cross-system whole vehicle data verification method of the present invention, and will not be repeated here.

[0168] In addition, an embodiment of the present invention further provides a storage medium, on which a cross-system vehicle data verification program is stored. When the cross-system vehicle data verification program is executed by a processor, the following operations are implemented:

[0169] Obtain vehicle production detailed data and vehicle design detailed data;

[0170] Performing data cleaning and filtering on the vehicle production detail data and the vehicle design detail data to obtain cleaned and filtered production data and design data;

[0171] The production data and the design data are compared according to the data structure to generate difference data, and an email reminder is issued according to the difference data.

[0172] Furthermore, when the cross-system vehicle data verification program is executed by the processor, the following operations are also implemented:

[0173] In response to the detailed data request sent by the business system, obtain the vehicle code of the vehicle production and the corresponding production effective date;

[0174] Determine the corresponding vehicle production detailed data from the production data center according to the vehicle code and the production effective date;

[0175] The backup production detail data is obtained from the manufacturing data center, and the whole vehicle design detail data is obtained based on the backup production detail data.

[0176] Furthermore, when the cross-system vehicle data verification program is executed by the processor, the following operations are also implemented:

[0177] Split the production requirements initiated by the business system into vehicle production codes and corresponding production times;

[0178] Retrieving the production vehicle code in the vehicle code library, and judging whether the production vehicle code is in a production-ready state according to the retrieval result;

[0179] When the production vehicle code is in the production-ready state, determining whether the production time is within a valid range;

[0180] When the production time is within a valid range, the business system sends a detailed data request to the production data center.

[0181] Furthermore, when the cross-system vehicle data verification program is executed by the processor, the following operations are also implemented:

[0182] Obtain backup production detail data from the manufacturing data center, and determine the backup vehicle code and production attribute information based on the backup production detail data;

[0183] Determining whether the backup vehicle code has stopped production;

[0184] When the production of the backup vehicle code has not been stopped, the valid vehicle detail data corresponding to the corresponding time point is obtained through the design center according to the backup vehicle code and the production attribute information, and the valid vehicle detail data is used as the vehicle design detail data.

[0185] Furthermore, when the cross-system vehicle data verification program is executed by the processor, the following operations are also implemented:

[0186] According to preset business requirements, redundant data and reasonable difference detail data in the vehicle production detail data and the vehicle design detail data are cleaned and filtered to obtain cleaned and filtered production data and design data.

[0187] Furthermore, when the cross-system vehicle data verification program is executed by the processor, the following operations are also implemented:

[0188] Comparing the production data and the design data by different project level codes according to the data structure to obtain data comparison results;

[0189] Differentiate the vehicle models of the data comparison results to obtain a comparison list;

[0190] Mark the difference points and difference fields in the comparison list according to preset business rules to obtain a difference list;

[0191] The difference list is located by the vehicle type field in the vehicle code to obtain a vehicle type classification result, and the difference list and the vehicle type classification result are used as difference data;

[0192] An email reminder is sent based on the difference data.

[0193] Furthermore, when the cross-system vehicle data verification program is executed by the processor, the following operations are also implemented:

[0194] Differentiate the vehicle series field from the vehicle code, and establish a corresponding relationship between the vehicle series field and the person responsible for the corresponding vehicle series;

[0195] Emails are generated based on the difference data, and are automatically and regularly delivered by vehicle series through the email system.

[0196] Through the above scheme, this embodiment obtains the vehicle production detail data and the vehicle design detail data; performs data cleaning and filtering on the vehicle production detail data and the vehicle design detail data to obtain the cleaned and filtered production data and design data; compares the production data and the design data according to the data structure to generate difference data, and sends email reminders based on the difference data. The method can automatically identify the difference data and send email reminders to the responsible person, effectively avoiding the problems of delayed verification, omissions and untimely response, ensuring the timeliness of production data verification, and at the same time ensuring the integrity of vehicle production verification, improving the accuracy of cross-system vehicle data verification, and improving the speed and efficiency of cross-system vehicle data verification.

[0197] It should be noted that, in this article, the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises a ..." does not exclude the existence of other identical elements in the process, method, article or device including the element.

[0198] The serial numbers of the above embodiments of the present invention are only for description and do not represent the advantages or disadvantages of the embodiments.

[0199] The above are only preferred embodiments of the present invention, and are not intended to limit the patent scope of the present invention. Any equivalent structure or equivalent process transformation made using the contents of the present invention specification and drawings, or directly or indirectly applied in other related technical fields, are also included in the patent protection scope of the present invention.

Claims

1. A cross-system vehicle data verification method, characterized in that: The cross-system vehicle data verification method includes: Obtain vehicle production detailed data and vehicle design detailed data; Performing data cleaning and filtering on the vehicle production detail data and the vehicle design detail data to obtain cleaned and filtered production data and design data; Comparing the production data with the design data according to the data structure, generating difference data, and sending an email reminder according to the difference data; The obtaining of vehicle production detailed data and vehicle design detailed data includes: In response to the detailed data request sent by the business system, obtain the vehicle code of the vehicle production and the corresponding production effective date; Determine the corresponding vehicle production detailed data from the production data center according to the vehicle code and the production effective date; Obtain backup production detail data from the manufacturing data center, and obtain vehicle design detail data based on the backup production detail data; Before the detailed data request sent by the business system is responded to and the vehicle code and the corresponding production effective date of the vehicle production are obtained, the cross-system vehicle data verification method further includes: Split the production requirements initiated by the business system into vehicle production codes and corresponding production times; Retrieving the production vehicle code in the vehicle code library, and judging whether the production vehicle code is in a production-ready state according to the retrieval result; When the production vehicle code is in the production-ready state, determining whether the production time is within a valid range; When the production time is within a valid range, the business system sends a detailed data request to the production data center.

2. The cross-system vehicle data verification method according to claim 1, characterized in that: The step of obtaining backup production detail data from the manufacturing data center and obtaining vehicle design detail data according to the backup production detail data includes: Obtain backup production detail data from the manufacturing data center, and determine the backup vehicle code and production attribute information based on the backup production detail data; Determining whether the backup vehicle code has stopped production; When the production of the backup vehicle code has not been stopped, the valid vehicle detail data corresponding to the corresponding time point is obtained through the design center according to the backup vehicle code and the production attribute information, and the valid vehicle detail data is used as the vehicle design detail data.

3. The cross-system vehicle data verification method according to claim 1, characterized in that: The step of performing data cleaning and filtering on the vehicle production detail data and the vehicle design detail data to obtain the cleaned and filtered production data and design data includes: According to preset business requirements, redundant data and reasonable difference detail data in the vehicle production detail data and the vehicle design detail data are cleaned and filtered to obtain cleaned and filtered production data and design data.

4. The cross-system vehicle data verification method according to claim 1, characterized in that: The step of comparing the production data with the design data according to the data structure to generate difference data, and sending an email reminder according to the difference data includes: Comparing the production data and the design data by different project level codes according to the data structure to obtain data comparison results; Differentiate the vehicle models of the data comparison results to obtain a comparison list; Mark the difference points and difference fields in the comparison list according to preset business rules to obtain a difference list; The difference list is located by the vehicle type field in the vehicle code to obtain a vehicle type classification result, and the difference list and the vehicle type classification result are used as difference data; An email reminder is sent based on the difference data.

5. The cross-system vehicle data verification method according to claim 4, characterized in that: The sending of email reminders according to the difference data includes: Differentiate the vehicle series field from the vehicle code, and establish a corresponding relationship between the vehicle series field and the person responsible for the corresponding vehicle series; Emails are generated based on the difference data, and are automatically and regularly delivered by vehicle series through the email system.

6. A cross-system vehicle data verification device, which verifies data using the cross-system vehicle data verification method according to any one of claims 1 to 5, characterized in that: The cross-system vehicle data verification device comprises: A data acquisition module is used to acquire detailed vehicle production data and detailed vehicle design data; A filtering module, used to clean and filter the vehicle production detail data and the vehicle design detail data to obtain cleaned and filtered production data and design data; The checking module is used to compare the production data with the design data according to the data structure, generate difference data, and send an email reminder according to the difference data.

7. A cross-system vehicle data verification device, characterized in that: The cross-system vehicle data verification device includes: a memory, a processor, and a cross-system vehicle data verification program stored in the memory and executable on the processor, wherein the cross-system vehicle data verification program is configured to implement the steps of the cross-system vehicle data verification method as described in any one of claims 1 to 5.

8. A storage medium, characterized in that: The storage medium stores a cross-system vehicle data verification program, which, when executed by the processor, implements the steps of the cross-system vehicle data verification method as described in any one of claims 1 to 5.

Images