A structured processing and application system for automobile standards and regulations

Abstract

The present application relates to the field of data processing technology, and more specifically, to a structured processing and application system for automobile standards and regulations. The system includes a product project compliance control unit, which determines a matching first set of standards and regulations based on the attribute information; extracts keywords from the test process of the test report, and determines a second set of standards and regulations in the first set of standards and regulations through a keyword matching algorithm; determines a third set of standards and regulations in the second set of standards and regulations based on the matching of the step sequence and step content of the matching keywords; determines a fourth set of standards and regulations in the third set of standards and regulations by performing a similarity comparison on the test images; and determines whether the target vehicle model meets the standards based on the test requirements of each standard regulation in the fourth set of standards and regulations. This embodiment realizes the automatic processing of standards and regulations and the automatic and accurate comparison with the test report.

Description

Technical Field

[0001] The present application relates to the field of data processing technology, and in particular to a structured processing and application system for automobile standards and regulations. Background Art

[0002] Currently, the automotive industry's management of domestic and international standards and regulations primarily relies on traditional manual processing methods, including the manual retrieval, interpretation, and application of regulatory documents. This leads to the following problems with existing technologies: 1. Inefficiency and the tendency for human error, especially when dealing with large volumes of regulatory documents and frequently updated regulatory requirements; 2. The lack of effective structured processing methods makes it difficult to quickly locate and compare regulatory provisions. The lack of effective comparative analysis methods for differences between different versions of regulations increases the difficulty of understanding and applying them; 3. Information silos: Poor information flow between different departments leads to delays in regulatory updates and application; 4. Compliance risks: The lack of effective tools for regulatory compliance checks increases the likelihood of companies facing legal risks.

[0003] In view of this, this application is filed. Summary of the Invention

[0004] To solve the problems in the background technology, the present application provides a structured processing and application system for automobile standards and regulations, including: a basic data control unit for managing and maintaining standards and regulations in the automobile field;

[0005] A standard structured processing unit, which performs structured processing and storage on the standard regulations;

[0006] Input unit, receiving attribute information and test report of target vehicle model;

[0007] The product project compliance control unit determines a matching first set of standards and regulations based on the attribute information; extracts keywords from the test process of the test report, and determines a second set of standards and regulations in the first set of standards and regulations through a keyword matching algorithm; determines a third set of standards and regulations in the second set of standards and regulations based on the matching of the step sequence and step content of the matching keywords; determines a fourth set of standards and regulations in the third set of standards and regulations by performing a similarity comparison on the test images; and determines whether the target vehicle model complies with the standards based on the test requirements of each standard and regulation in the fourth set of standards and regulations.

[0008] This application addresses the existing challenges of inefficient standard text processing, analysis, and interpretation, information silos, increased compliance risks, and high accountability in enterprise standard management processes. Compared to existing technologies, this application offers the following benefits: 1. Improved regulatory processing efficiency and accuracy: The system enables rapid online compilation and structured processing of automotive standards and regulations, reducing manual operations, avoiding human errors, and significantly improving work efficiency. 2. Enhanced regulatory difference comparison and analysis capabilities: Through standard difference comparison methods, the system can effectively identify and compare differences between different versions of regulations, streamlining the process of understanding and applying regulations. 3. Promoted information sharing and collaboration: Information silos are eliminated, ensuring the synchronization of regulatory updates and application across departments and enhancing cross-departmental communication and collaboration. 4. Reduced compliance risks: The system provides a regulatory compliance check function, helping enterprises promptly identify and address potential legal risks and ensuring product compliance. 5. Optimized full lifecycle management of enterprise standards: The system covers the entire process of enterprise standards, from formulation to revision to abolition, improving the systematicity and efficiency of standards management and ensuring the continuity and consistency of standards. 6. Enhanced compatibility with internal and external standards and regulations: This ensures that corporate standards meet both industry norms and market-specific regulatory requirements, increasing their scope of application and flexibility. 7. Promoted the digital transformation of the automotive industry: Through the application of automated and intelligent processes, automotive companies are able to more efficiently interpret, analyze, and respond to data related to standards and regulations, accelerating their digital transformation and improving overall operational efficiency and market competitiveness. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] In order to more clearly illustrate the specific implementation methods of the present application or the technical solutions in the prior art, the following is a brief introduction to the drawings required for use in the specific implementation methods or the description of the prior art. Obviously, the drawings described below are some implementation methods of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0010] Figure 1 This is a schematic diagram of the structure of a system for structured processing and application of automotive standards and regulations provided in an embodiment of the present application;

[0011] Figure 2 is a schematic structural diagram of a standard structured processing unit provided in an embodiment of the present application;

[0012] Figure 3 This is a schematic diagram of the structure of an OCR text recognition tool based on automotive standards provided in an embodiment of the present application;

[0013] Figure 4 Schematic diagram of the structure of the standard text structured splitting tool provided in the embodiment of the present application;

[0014] Figure 5 This is a schematic diagram of the structure of the product project compliance management unit provided in the embodiment of the present application;

[0015] Figure 6 It is a structural diagram of the standard full life cycle management unit provided in the embodiment of the present application. DETAILED DESCRIPTION

[0016] The following description of exemplary embodiments of the present application is made in conjunction with the accompanying drawings, including various details of the embodiments of the present application to facilitate understanding. These details should be considered as merely exemplary. Therefore, those skilled in the art will recognize that various changes and modifications may be made to the embodiments described herein without departing from the scope and spirit of the present application. Similarly, for the sake of clarity and conciseness, descriptions of well-known functions and structures are omitted in the following description.

[0017] The embodiment of this application provides a structured processing and application system for automobile standards and regulations, which is applicable to the management of standards and regulations in the domestic and foreign automobile industries. Figure 1 The system provided in this embodiment includes: a basic data management unit, a standard structured processing unit, an input unit, and a product project compliance management unit. Each unit is introduced below.

[0018] The basic data management and control unit manages and maintains standards and regulations for the automotive sector. Specifically, the basic data management and control unit is used to store, access, and manage domestic and international standards, regulations, and policy data, as well as enterprise standards data. This includes a domestic standards and regulations library, an overseas standards and regulations library, a domestic and international policy library, an enterprise standards library, and a dynamic information library. For example, the domestic / overseas standards and regulations library primarily manages all domestic and international standards, regulations, and policies collected by an enterprise, including domestic certification standards, domestic mandatory standards, and overseas certification standards. The enterprise standards library primarily manages all internally developed standards resources, including technical foundation standards, product standards, engineering verification technical standards, process technical standards, and quality control technical standards. These databases primarily implement entry-based storage and detailed display capabilities, supporting customizable system catalogs, data management and maintenance, data import and export, online text preview, multilingual text translation, intelligent query, automatic status changes, data distribution and borrowing, provision of value-added information, and permission control. In addition to these functions, enterprises also integrate processes such as enterprise standard planning, formulation, revision, review, and revocation to dynamically update the status of standards. The following details the various functions of these databases.

[0019] 1. Itemized storage and detailed display functions are used to store and display standards, regulations, policies, and corporate standards in an itemized manner, allowing users to view detailed information for each standard. Attribute fields for standards, regulations, and policies include basic standard information (standard number, standard name, implementation date, applicable certifications, energy type, applicable vehicle models, applicable regions, and other information inherent to the standard itself); extended information (internal enterprise information such as responsible department, responsible engineer, associated assemblies and components, associated test items, and interpretation documents related to the standard); text information (release drafts, in-progress drafts, supplements, etc.); and attachment value information (standard interpretation, standard breakdown sheet, comparison results, Q&A records, project conformity assessment results, etc.). The attribute fields of enterprise standards include basic information of the enterprise standard (enterprise standard number, enterprise standard name, confidentiality level, standard status, release date, implementation date and other information inherent in the standard itself), drafting information (drafting person, drafting department, applicable vehicle model, energy type, system category, related assembly and component numbers, etc.), text information (release version, historical version, preparation instructions, amendment sheet, etc.), and related information (replacement enterprise standard number, replaced enterprise standard number, referenced standards, related processes, related files, etc.).

[0020] 2. Customized system classification function is used to customize the standard and regulatory system directory and display the standard, regulatory and policy data under different categories in a tree structure.

[0021] 3. Data management and maintenance functions are used to add, edit, delete, configure, remove, favorite, and share standard and regulatory data (including detailed information and related attachments). The Add operation is used to add a new standard or regulation; the Edit operation is used to modify the detailed information and related attachments of a standard or regulation already in the database; the Delete operation is used to delete standard or regulatory data from the database individually or in batches; the Configure operation is used to add standard or regulatory data in batches to the selected directory; the Remove operation is used to remove standard or regulatory data in batches from the selected directory; the Favorite operation is used to add a standard or regulation to the Personal Center unit - My Favorites; the Share operation is used to share a standard or regulation with other users, who can view it in the Received Shares section of the Personal Center unit.

[0022] 4. Data import and export function is used to provide an EXCEL import template for standard basic data. After entering the detailed information of standards and regulations according to the filling rules, local standards, regulations, policies or enterprise standards data can be imported into the corresponding directory in batches by uploading the template and related attachment texts. At the same time, the data already in the database can be selected and exported in batches, including detailed information and corresponding attachments.

[0023] 5. The online file preview function supports online preview of corresponding attachments (PDF, Docx, Excel formats) in the detailed information of standards and regulations. Personal notes can be added to the preview, and a watermark can be added to the global preview page to increase confidentiality.

[0024] 6. Text multilingual translation function, used to convert foreign standards into Chinese text through big data translation engine and provide preview and download.

[0025] 7. Intelligent query function supports general query by attribute fields such as standard number and standard name, and multi-condition combination query.

[0026] 8. The function of automatic standard status change is used to determine the status of various standards and regulations based on the standard status change rules, the current time and the substitution relationship between standards, including: drafting, soliciting opinions, review, approval, publication, upcoming implementation, current validity and abolition. Specifically, it is automatically updated through fields such as replacement standards, implementation date, and process progress. The specific standard status change rules are: ① When the standard is put into the library, you can manually select the release and its previous status; ② When the standard status is "released", starting from the next day, it will be judged whether the current date has reached the implementation date in the published standards. If it has not reached the implementation date, it will be displayed as "to be implemented", and if it has reached the implementation date, it will be displayed as "currently valid"; ③ For the currently valid standards, they can be replaced by new standards and automatically changed to abolished (when the new standard status is not "currently valid", the old standard status is still "currently valid", and when the new standard status is "currently valid", the replaced standard status will become abolished). ), or it can become abolished after reaching the abolition date. The status of the standard is not allowed to be changed after being abolished; the status of enterprise standards are: planned revision, released, under revision, revised, and abolished. The specific standard status change rules are: enterprise standard A replaces enterprise standard B. When the application process for the formulation and revision of enterprise standard A is approved, enterprise standard B becomes planned revision; enterprise standard A replaces enterprise standard B; when the formulation and revision process of enterprise standard A enters the approval stage, the standard status of enterprise standard B automatically becomes "under revision". When the formulation and revision process of enterprise standard A is completed, enterprise standard A is published and enterprise standard B becomes revised.

[0027] 9. The data issuance and borrowing function is mainly used to grant users who do not have the right to view standard details and preview attachments the right to view detailed information preview and download related attachments. Users can apply for borrowing permissions for multiple standards under a certain category.

[0028] 10. Provides value-added information, supporting the association of modules such as update logs, interpretation reports, split results, comparison results, standard Q&A, and compliance assessment results for the data in the standard and regulation details. With one click, users can jump to the corresponding module to view the application status of the corresponding standard. In particular, for enterprise standards, users can jump to the corresponding enterprise standard formulation and revision process and view the enterprise standard rating.

[0029] 11. The permission control function is used to control the user's data access rights and menu function permissions based on organizational hierarchy, role and other dimensions, which are divided into data permissions and functional permissions. Among them, data permissions include directory-level permissions and single standard permissions, which are used to set a certain type of user to only access a certain directory or data with a certain characteristic attribute. In particular, for the enterprise standard library, different detail viewing permissions can be set according to the enterprise standard confidentiality level: everyone with an enterprise standard confidentiality level of C1 can view the details, only the drafting department and relevant department personnel with C2 can view the details, and only the main drafter, other drafters, enterprise standard engineers, system administrators and those who apply for authorization separately can view C3. Functional permissions include module permissions and button permissions.

[0030] See also Figure 2 , standard structured processing unit, carries out structured processing and storage of standards and regulations. This unit includes: OCR text recognition tools based on automotive standards, standard text structured splitting tools, standard text difference comparison tools and standard online editing tools, forming four aspects of processing and application: external standard data format conversion, external standard item decomposition, interpretation of differences between old and new external standards, and online formulation and revision of enterprise standards. The structured data generated by this unit constitutes a structured database of standards and regulations, which serves as information input for the product project compliance management unit. The standard online editing tool can be applied to the enterprise standard full life cycle management unit to carry out online formulation and revision of enterprise standards. The functions implemented by each tool are introduced below.

[0031] 1. The OCR (Optical Character Recognition) text recognition tool based on automotive standards is mainly used to convert non-editable domestic and international standard and regulatory resources uploaded by users into editable files. After entering the tool, the user clicks Upload to upload the PDF file to the server. The service uploads the user's uploaded file to the OCR recognition cloud service through the webserver. In the cloud service, the system will automatically recognize and convert the PDF file, and finally convert the uploaded PDF file into an editable Docx document. See Figure 3 The tool consists of a central processing module, an image pre-processing module, an OCR recognition module, a file conversion module, a user account management module, and an external interface. The specific working steps include:

[0032] S101. File upload and reception: The user logs in to the Standards and Regulations Structured Application System through the User Account Management Module, enters the tool to upload files, calls the server's external interface to upload PDF files, and the external interface receives the files and saves them to the file directory. The task request is queued for processing, and the user and file information is saved to the database.

[0033] S102, file preprocessing: The central processing module takes out the pending tasks from the task queue and sends the files to the image preprocessing module for processing. The image is extracted from the PDF file and OpenCV is used to adjust the image size, reduce noise, enhance contrast, adjust grayscale, and perform binarization.

[0034] S103, OCR text recognition and format conversion: The pre-processed file is sent by the central processing module to the OCR recognition module. Based on the big data deep learning algorithm based on the Abbyy12 algorithm core library, the OCR SDK is used to perform text image recognition on the file, and then the recognized content is passed through the file conversion module to generate a Docx file.

[0035] S104, post-processing correction: the file conversion module continues to perform intervention correction on some Chinese characters with recognition errors that appear regularly in the converted file.

[0036] S105. File output: The corrected file is stored in the database by the central processing module, and callback is performed to return the final file to the standard and regulation structured application system through the external interface.

[0037] 2. Standard text structured splitting tool, which splits the text, tables, pictures and other information in the editable text content according to the clause structure to form structured data, and reorganizes, arranges and displays the structured data according to the tree structure of the clause, forming editable knowledge entries in terms of clauses, and stores them in the standard and legal structured database. The standard and legal structured database can perform attribute maintenance and shared collection of knowledge entries, and is associated with the intelligent retrieval center. In the process of searching for useful knowledge, it is only necessary to retrieve and analyze the knowledge entries to filter out more fine-grained retrieval results. The tool consists of a data reading module, a data rule analysis module, a structured data generation module, and a data storage and display module. Its structure diagram is shown below. Figure 4 As shown. Combined with actual application scenarios and effects, the specific working steps of the standard text structure splitting tool include:

[0038] S201. File upload and reception: The user logs in to the standard and regulation structured application system, enters the standard text structured splitting tool, uploads the standard and regulation file in doc / docx format stored locally or generated by the OCR text recognition tool, and reads the standard number / policy number, standard name / policy name, and text content in the file through the data reading module.

[0039] S202: For each standard or regulation, determine the splitting range, for example, filtering out all target paragraphs within the range based on the chapter number.

[0040] S203: traverse each paragraph within the split range and mark the paragraphs that meet the clause identification rules with a clause number. The clause identification library is read and each paragraph is traversed simultaneously. The corresponding clause number is marked for each paragraph that meets the clause identification rules. The detailed content is obtained and the process proceeds to step S204. The process then loops through each paragraph within the split range until each paragraph is marked with a clause number.

[0041] Among them, the paragraphs of the symbolic clause identification rules generally contain any one or a combination of two or more of the three elements: multi-level document number, chapter title and chapter content.

[0042] S204, identify paragraphs with the same clause number and merge them, and then sort the merged paragraphs according to the context order and clause level, and extract and split the content in terms of clauses. Specifically, identify paragraphs with the same clause number and merge them, and then sort the merged paragraphs according to the context order and clause level, and extract and split the content in terms of clauses. During the extraction, the data is divided into three types according to the data type definition: text type, table type, and image type, and the data is split and converted according to the different data types. For text type data, paragraph separation storage and key attribute analysis are performed, and attribute words are marked. For table type data, two-dimensional structure storage is performed and the text position is marked. For image type data, it is stored in the form of attachments, and then different types of data are arranged and assembled according to the order in the clauses. Text type, table type and image type data are respectively used as the minimum storage unit for structured storage.

[0043] S205, Data Storage, Synchronization, and Maintenance: The structured text is displayed in a tree-like directory structured by chapter, first-level clause number, second-level clause number, and so on. After the structure is split, it is automatically synchronized to the detailed information of the corresponding standard in the basic data control unit. Clauses can be tagged with attributes to associate vehicle assemblies and parts, responsible departments, and applicable target markets, vehicle types, powertrain types, etc. The text, tables, and images within the clauses can be edited and referenced from other standards.

[0044] 3. The standard text difference comparison tool, based on the structured data generated by the standard text structured splitting tool, performs difference analysis and marking on different standards and regulations, and generates a standard and regulation difference interpretation report, so as to quickly identify the difference information between different versions of standards and regulations. In one application scenario, the difference comparison between two similar or previous versions of standards and regulations is carried out. The specific working steps include:

[0045] S301 : Preprocess the two standard regulations, for example, preprocess the texts, tables, and images of the two input standard regulations.

[0046] Preprocessing of textual data involves word segmentation and standardization, stop word filtering and stemming, and constructing a semantic tree structure for regulatory clauses. Word segmentation and standardization segment the regulatory text and standardize the format of regulatory terminology to ensure consistency in subsequent analysis, particularly for automotive industry terminology (such as "ABS" and "ESP"). Stop word filtering and stemming remove irrelevant terms and extract stems to reduce the impact of synonyms. Semantic tree construction builds a semantic structure for regulatory clauses based on grammatical analysis, enabling deeper semantic understanding.

[0047] Preprocessing of tabular data: Convert the table content into a structured data format, such as XML or JSON format, to facilitate further data processing; standardize the numerical data in the table to ensure a uniform data format, such as standardizing units (such as kilometers per hour, millimeters, etc.); process the text content in the table in the same way as plain text data.

[0048] Preprocessing of image data: For text content in images, use OCR text recognition tools to identify it and convert it into editable text format; for charts or complex symbols in images, including structural diagrams, circuit diagrams, etc., perform ① binarization processing: convert the image to black and white to simplify subsequent processing steps; ② edge detection: use the Canny edge detection algorithm to detect lines and boundaries in the image; ③ shape recognition: identify specific shapes (such as circles, rectangles, polygons, etc.) to determine the position and type of chart elements; ④ pattern recognition: use deep learning technology to identify specific chart types or complex symbols; ④ feature extraction: identify and extract key features such as part numbers and connecting lines in the chart; ⑤ data conversion: convert the extracted information into a graphic model SVG file, maintaining the vector characteristics of the graphic.

[0049] S302. Use a deep learning model to perform semantic analysis on the preprocessed standard regulations to obtain two matching clauses. Specifically, a deep learning model, such as BERT or Transformer, is used to perform semantic analysis on the preprocessed text, converting the text into semantic vectors. By calculating the cosine similarity between these vectors, accurate matching across different clauses in the standard regulations is achieved.

[0050] S303. Use a distance algorithm to perform a preliminary difference analysis on any two clauses. For example, the Levenshtein distance is an indicator that measures the difference between two sequences by calculating the minimum number of single-character editing operations (including insertion, deletion, or replacement) required to change from one sequence to another. For text-based data: Use the Levenshtein distance algorithm to calculate the edit distance between texts to quantify the similarity between the two texts, and record this value as a preliminary quantitative difference indicator; For tabular data: Calculate the Levenshtein distance for each cell, and comprehensively consider the structural differences of the entire table. If the table structure has changed, these differences can be identified by comparing the number and order of rows and columns; For image-based data: Utilize the editable file preprocessed in S301 and also use the Levenshtein distance algorithm to calculate the difference between the converted texts. If there is content that is difficult to convert, the system will store the compared images in a manual verification library for manual difference comparison. After preliminary difference analysis, two relatively similar clauses can be obtained.

[0051] S304, using the Smith-Waterman (SW) algorithm and the diff algorithm, conduct an in-depth difference analysis on the two clauses. Specifically, for the two relatively similar clauses obtained from the preliminary difference analysis, the SW algorithm is first used to perform a local sequence alignment on the two clauses to identify the maximum matching fragment in the text, helping to identify similar but not identical clause paragraphs in the standard regulatory text. This is applicable to clauses that have undergone minor modifications but whose core meanings remain unchanged and for which no differences can be identified in S303. The diff algorithm is then used to mark the text differences, clearly showing which content has been added, deleted or modified, and highlighting the specific changes in the standard regulatory texts. This embodiment combines the SW algorithm with the Levenshtein algorithm to identify local maximum matching areas and calculate the differences between these areas, while the diff algorithm is used to assist in displaying the specific locations and properties of these differences. The three complement each other and jointly complete a detailed difference analysis.

[0052] S305: Quantify and identify the preliminary and in-depth difference analyses, generating a difference report. Specifically, quantitative methods are used to precisely identify the specific location and nature of the changes. Combining the results of the previous steps, a quantitative assessment is performed on each identified difference, such as calculating a similarity percentage. The differences are also annotated in the text with specific markers (e.g., color coding, annotation boxes) to facilitate intuitive understanding by the user.

[0053] 4. The Standards Online Editing Tool allows users to edit standard documents online, pre-set the document format templates required by the enterprise, and produce documents according to a fixed format, quickly generating enterprise standard text that meets the writing specifications. A custom editor allows users to insert tables, images, directories, appendices, and other content during the document compilation process. Standard information can also be retrieved through other module interfaces in the system and directly inserted into the enterprise standard document, ultimately forming an enterprise standard library. The tool's core functions include: 1) Initializing the Enterprise Standard Template: Upon entering the online enterprise standard editing platform, users can select a pre-made template corresponding to the enterprise standard type. After selecting, the document content is initialized, automatically generating information such as the preface and table of contents. Formatting is also preset for certain sections, clauses, and main text based on enterprise requirements. User-entered content defaults to the overall document requirements, but formatting can be modified based on actual business scenarios. 2) Automatic Content Population: During the compilation of enterprise standard content, certain content, such as the standard name, standard number, replacement status, implementation date, and compiling department, can be automatically imported from the development and revision process data and populated where needed. 3) Automatic Section and Clause Numbering: When users add new chapters, sections, or clauses, inserted content is automatically numbered. 4) Local File Export: You can export the same Word version of the content edited online. 5) Format Painter: You can copy text and, by clicking shortcut keys for chapters, sections, notes, and paragraphs, rewrite the copied text to the corresponding text format, facilitating user operations. 6) Structured Splitting: Once the user has finished writing, they can pass it to the standard text structured splitting tool for structural decomposition. After decomposition, it is bound to corporate standards and passed to other business systems.

[0054] The system also includes an input unit that receives attribute information and a test report of a target vehicle model. Attribute information includes vehicle model information, test item information, region information (where the target vehicle model is sold), and time information (when the target vehicle model was released to the market). The test report is generated by testing the target vehicle model and includes the test process, test diagrams, and test report results.

[0055] The product project compliance control unit determines a matching first set of standards and regulations based on the attribute information. Specifically, the first set of standards and regulations that matches the vehicle model information, test item information, and is valid within the region and time information is determined based on the attribute information. The first set of standards and regulations includes multiple standards and regulations. Subsequently, the product project compliance control unit uses a series of algorithms to find the standards and regulations that match the test item in the first set of standards and regulations, specifically including the following steps:

[0056] Step 1: extract keywords from the test process of the test report, and determine the second standard regulation set from the first standard regulation set through a keyword matching algorithm.

[0057] Keywords can be test item names, test equipment names, test parameters and indicators, etc. Keywords are extracted from the first set of standards and regulations and the test process, and matched against each other to obtain a second set of standards and regulations with matching keywords. This second set of standards and regulations is selected from the first set of standards and regulations.

[0058] Step 2: Determine a third set of standard regulations from the second set of standard regulations based on the matching order of the steps and the matching of the step contents.

[0059] The vehicle testing process includes multiple steps. The order of some steps can be swapped. For example, there is no substantial difference between adjusting the temperature of the environmental chamber first and then adjusting the humidity of the environmental chamber and adjusting the pressure of the environmental chamber first. However, whether the step content is high temperature or low temperature makes a big difference. Based on this, this embodiment puts the matching keywords back into the original steps, so that matching steps are obtained. In these matching steps, the influence of the step sequence is weakened and the influence of the step content is strengthened. Then, the following formula is used to calculate the matching M of the step sequence and step content of the matching keywords in the second standard regulation set and the test report; the standard regulations with M greater than the set value are added to the third standard regulation set. The set value can be set by yourself.

[0060] ;

[0061] Where A and B are coefficients, and , i is the serial number of the keyword, N is the number of keywords, It is a key word in the standard regulations The steps, It is a key word in the testing process The steps, and is the matching keyword, express and The difference in the order of steps, for example, It's step 5. It is step 6, then =6-5=1. express and The semantic distance of the step contents is expressed, for example, by semantic similarity.

[0062] The third standard regulation set is selected from the second standard regulation set.

[0063] Step 3: Determine the fourth standard regulation set from the third standard regulation set by performing similarity comparison on the test images.

[0064] Consider that some test details aren't documented in written form in standards and test reports, but rather in test drawings. For example, a chassis dynamometer might be depicted in a test drawing, but since it's a standard piece of equipment, it's not reflected in the test report's steps. Therefore, it's necessary to perform a similarity comparison between the test drawings in the standards and test reports. These drawings can be mechanical drawings or on-site photographs. In this step, if the aforementioned keywords and steps match, the test drawings are further compared for similarity.

[0065] Optionally, a search is performed around the steps containing the matching keywords. An image similarity comparison algorithm and a keyword comparison algorithm for the test image annotation names are used to determine the fourth set of standard regulations within the third set of standard regulations. For example, the test image is converted into a short, fixed-length fingerprint using a hash algorithm, and the test image similarity comparison is achieved through fingerprint comparison. Keyword comparison is performed on the test image annotation names (e.g., the name of each labeled test component). If the test image and annotation name of a standard regulation in the third set of standard regulations match the test image and annotation name in the test report, the standard regulation is added to the fourth set of standard regulations.

[0066] Step 4: Determine whether the target vehicle model complies with the standards based on the test requirements of each standard regulation in the fourth standard regulation set.

[0067] Basically, if the standards and regulations in the fourth standard and regulation set match the test report, the project compliance judgment process will automatically assign responsible persons for each standard and regulation in the fourth standard and regulation set that the target vehicle model needs to meet, create assessment tasks, and execute assessment tasks; and determine whether the test report results meet the qualitative and quantitative requirements of each standard and regulation in the fourth standard and regulation set.

[0068] The following is a more detailed example to illustrate the function of the product project compliance control unit.

[0069] like Figure 5As shown, the product project compliance control unit includes a vehicle project library, a vehicle development compliance checklist, a project compliance assessment process (project / regulatory line), an analysis of standard-related items, a non-conformance tracking library, and a non-conformance rectification process. This unit uses a library of domestic and international standards and regulations, as well as a structured database of standards and regulations, as input. It first intelligently matches regulatory requirements with target vehicle information to create a development compliance checklist for the target vehicle. Then, through the project compliance assessment process, it automatically assigns individuals responsible for verifying each regulatory requirement for the target vehicle. Assessment tasks are created and executed, automatically or manually determining whether automotive product design parameters (such as basic vehicle attributes, performance parameters, and component installation parameters) meet the quantitative and qualitative requirements specified in the regulations. All assessment results (compliant, non-compliant, not involved, pending verification) generated during the assessment process are synchronized to the standard-related item analysis and vehicle development compliance checklist. Non-compliant items (non-compliant, pending verification) identified in the assessment results are synchronized to the non-conformance tracking library for tracking. Finally, the non-conformance rectification process completes the rectification and closure of the issues. The execution of the product project compliance control unit includes the following operations:

[0070] S401. Acquire, create, and edit vehicle model project information. Engineers automatically acquire or upload project documents from the vehicle model project library, automatically parse vehicle model information, quickly create vehicle model projects, generate raw vehicle model data, and customize and edit the raw data based on business needs to input vehicle model attribute information for subsequent compliance assessment processes.

[0071] The vehicle project library synchronizes information on vehicles within the company for the domestic market, overseas exports, under development, and in production, as needed. It includes a homepage, a details page, and a vehicle development compliance checklist. The homepage stores and manages vehicle data in a list format, allowing for automatic creation, editing, retrieval, and export of vehicle project lists. The vehicle project details page displays all basic data and technical parameters for created vehicles. The system allows for setting viewing permissions for different roles, allowing authorized users to view detailed information. The vehicle development compliance checklist generates a list of standards and regulations that a vehicle must meet, displays the results of the project compliance assessment process, and summarizes the number of risk items at different levels (red, yellow, and green).

[0072] To reduce the workload of manually screening and filling in attribute information when engineers create vehicle project, improve data processing efficiency, and reduce the risk of manual errors, the vehicle project library provides automatic vehicle data synchronization and parsing functions, which mainly include synchronization and parsing rule settings and automatic synchronization mechanism settings. Specifically, 1) Synchronization and parsing rule settings: Based on the needs of compliance investigation, synchronization rules (including vehicle requirements and attribute field ranges) are configured. For the full amount of vehicle data in the system and local project archive, only a certain type of vehicle (for example, selectively synchronizing a certain type of vehicle based on dimensions such as vehicle category, power type, and configuration level) and key vehicle attribute information used for compliance judgment (for example, only synchronizing vehicle type, active safety, and passive safety technical parameters for compliance judgment in the safety field) are extracted. 2) Automatic synchronization mechanism settings: The synchronization frequency is set in advance, such as once a day, once a week, or when the project reaches a certain project node. Timed automatic synchronization can be achieved to ensure that the vehicle attributes used in compliance investigation are the latest. The vehicle attribute information created after extraction generally includes basic data (such as the target market (region) of the vehicle model, project code, project name, project members, vehicle model category (M1, M2, M3, N1, N2, etc.), power type (gasoline, diesel, HEV, PHEV, etc.), announced vehicle model, valve time nodes of each project, etc.) and technical parameters (appearance design, structural design, interior design, performance design, testing and verification, etc.).

[0073] S402: Assign project compliance assessment roles. Engineers configure the permissions of various roles involved in the project compliance assessment process within the project. Users with corresponding role permissions will perform different node tasks in the subsequent compliance assessment process.

[0074] The authority configuration of each role can be customized according to the company's own situation; usually, the regulatory engineer or project leader is the initiator of the process and can issue assessment tasks to various professional fields; the interface person or person in charge of each professional field is the distributor of compliance determination tasks, and according to the situation of their own professional field, they distribute the regulations or clauses that need to be evaluated to lower-level design engineers; design engineers receive tasks and fill in the compliance determination results of the corresponding regulations or clauses based on the current project status; experts or managers in each profession are the reviewers of the content of the regulatory compliance determination results.

[0075] S403: Automatically generate an initial vehicle model development compliance checklist. After completing the vehicle model project creation and project role assignment, the system automatically associates and matches external standards and regulations, including their structured clauses, with the vehicle model project based on attributes such as the target market, vehicle type, and powertrain type. Specifically, the fourth standard and regulatory set is combined with the test report to form a preliminary matching table between the vehicle model product and regulatory requirements.

[0076] S404: Execute the vehicle project compliance assessment process (including qualitative and quantitative requirements) based on the preliminary matching table, automatically assign and distribute assessment responsibilities, and complete and review the compliance assessment results. The regulatory engineer selects the compliance assessment process type, further screens the vehicle development compliance checklist to form a compliance assessment task list, and automatically assigns domain interface personnel / system engineers based on the professional areas covered by the regulatory requirements. The domain interface personnel can further distribute tasks, and the design engineer will assess compliance with the received regulatory requirements based on the actual project situation. Quantitative requirements can be automatically assessed. After the assessment results are submitted and reviewed by experts from various departments / professions, the project's compliance assessment is completed.

[0077] In a specific implementation, the regulatory engineer initiates the project compliance determination process in the task processing unit. After the process is initiated, he needs to select any one of the following two lines: one is the project line, which reviews and reviews the regulations in real time at each node from before to after the launch, and makes compliance determinations on all regulatory requirements that need to be met by this vehicle model project; the other line is the regulatory line, which identifies all possible vehicle model projects involved when new regulations are issued or updated, and makes compliance determinations. Regardless of whether it is the project line or the regulatory line, after the compliance determination process, the latest regulatory requirements and corresponding evaluation results will be updated to the vehicle model R&D compliance list to ensure the timeliness and completeness of the list. The vehicle model project compliance determination process includes the following operations:

[0078] S4041. Select a process type to generate different types of compliance assessment task lists, including project-line compliance assessment task lists and regulatory-line compliance assessment task lists. Specifically, if you select the project-line compliance assessment process, select a vehicle model from the vehicle project library and the fourth standard and regulation set to generate a single-vehicle, multi-standard compliance assessment task list. If you select the regulatory-line compliance assessment process, select a newly released or updated regulation from the domestic and international standard and regulation libraries. The system then searches the R&D compliance checklist data for each vehicle model, automatically selecting vehicles that already meet that regulation, and generating a single-standard, multi-vehicle compliance assessment task list.

[0079] S4042. Automatically assign professional contact persons to standards and regulations in the compliance assessment task list and issue assessment tasks. Specifically, after the compliance assessment task list is formed, the system automatically brings up the corresponding professional contact persons based on the associated assemblies, components, and responsible departments maintained in the standards / clauses. For example, if a standard in the list is associated with an engine assembly and cylinder block, and the responsible department is the powertrain R&D department, the system automatically reads the personnel position information from the company's organizational directory, assigns the contact person in the engine structure design field as the responsible person for this standard, and automatically issues the task to them.

[0080] S4043. Conduct compliance assessments on test report results based on standards and regulations, including automatic assessment of quantitative requirements and auxiliary assessment of qualitative requirements. Supporting materials should be uploaded for the assessment results, and the risk level should be marked (red for high risk, yellow for medium risk, and green for low risk).

[0081] Among them, automatic determination of quantitative requirements: For quantitative requirements that limit the performance or characteristics of a certain aspect of a car through specific parameters, the system identifies the parameter type and determination conditions in the standard regulations, reads the actual design parameters and / or test parameters of the corresponding vehicle model, determines whether the determination conditions are met and outputs the determination results.

[0082] For qualitative requirements that define vehicle performance or characteristics using descriptive language, semantic analysis is used to assist in the determination of these requirements. First, a BERT model is used to perform semantic analysis of standards and regulations to extract keywords related to the qualitative requirements. Then, test report results are matched against these keywords to identify test information relevant to the standards and regulations. For example, Pandas is used to integrate test report results and match them against keywords to identify information related to the vehicle model's actual design and test parameters that is relevant to the regulatory requirements. Finally, Scikit-learn is used to analyze the data and calculate the consistency score between the test information and the qualitative requirements. For example, a classification model provided by Scikit-learn is used to determine whether the test information related to the standards and regulations and the qualitative requirements belong to the same category, and the confidence level of the category is used as the consistency score. Next, a web framework is used to generate an analysis report on the consistency between the vehicle model's actual parameters and the qualitative requirements for reference by the responsible person. The responsible person, based on the system's output of the quantitative requirement determination and qualitative requirement analysis report, confirms and submits all the determination results, combined with the vehicle model's actual conditions, for expert review.

[0083] S405. Summary of project compliance determination results: At the end of the project compliance determination process, all determination results (compliant, non-compliant, not involved, pending verification) are synchronized to the standard-related project analysis and vehicle model development compliance checklist. Non-compliant or pending verification items in the determination results will be synchronized to the non-compliant item tracking library.

[0084] The Non-Conformance Tracking Library aggregates and displays non-conformances and pending verification issues identified during project compliance assessments. It also includes follow-up remediation plans, such as the responsible individual, remediation measures, and estimated completion time. Regulatory engineers can also manually add non-conformances and pending verification issues. After the non-conformance tracking process concludes, the remediation status of the issues involved, including completion status, actual completion time, and supporting documentation, is updated to the Non-Conformance Tracking Library. This module allows for role-specific permissions at the module, action button, and data levels. The Standards-Involved Project Analysis module aggregates and displays the compliance status of each standard at each stage of the compliance assessment process across projects, from a standards and regulations perspective. This module allows for role-specific permissions at the module, action button, and data levels, which must be configured through the Role Management module in the System Management Unit. If the standards or clauses involved in the process are included in the R&D compliance checklist for a vehicle project, the judgment results for the corresponding standards or clauses will be updated to the checklist. This means that the R&D compliance checklist aggregates and displays the compliance status of each node in each project, as reported through the compliance assessment process, from a vehicle perspective.

[0085] S406. Correction process for non-conformities: For all problem items that fail the compliance assessment, a correction process for non-conformities is created to track the correction status until all corrective measures are completed for the non-compliant data and the final expert review is passed. The completion status and process data of each correction stage will be updated in real time in the non-conformity tracking module.

[0086] The data source of the non-conformance tracking library is the project line and regulatory line of the non-compliance determination process. It displays the standards / clauses corresponding to each problem item, related projects, problem types, responsible departments, rectification responsible persons, rectification plans for each stage (design rectification, verification rectification, final rectification), current rectification status, actual closure time, closure method, etc. in the form of a list. You can view the specific rectification process materials and the progress of the corresponding non-conformance item rectification process.

[0087] For compliance issues that have not been identified in the project compliance determination process, it is allowed to directly create non-compliance problem items in the non-compliant item tracking module, which needs to be set up through the system management unit-role management module. It is allowed to manually close non-compliant data in non-compliant items, which needs to be set up through the system management unit-role management module. After each stage of rectification is completed, the corresponding rectification status, supporting materials and completion time will be synchronously updated in the non-compliant item tracking module; for the problem items that have completed the final stage of rectification, an email or system reminder will be sent to the initiator of the problem item rectification process. During the entire non-compliant item rectification process, users can log in to the application system to check the process status at any time. After the process is initiated, after each process node is completed, it will automatically flow to the next process node and send real-time emails or system notifications to PCs and mobile phones to remind relevant personnel to ensure that the tasks are processed and submitted in a timely manner.

[0088] Optionally, the system provided in this embodiment also includes a standard life cycle management unit, which is used to manage the planning stage, enterprise standard formulation and revision stage, enterprise standard evaluation and supervision and inspection stage, and enterprise standard review and cancellation stage of the enterprise standard.

[0089] Specifically, the Standards Lifecycle Management Unit implements compliance process control throughout the entire product project lifecycle, automatically mapping domestic and international standards and regulatory requirements to vehicle project models, automatically allocating assessment tasks, and automatically determining quantitative requirements. This ensures the timeliness, accuracy, and completeness of regulatory audits, avoiding delays and omissions during the response process. By visually displaying task allocation and specific audit progress, it helps regulatory engineers, design engineers, professional experts, and administrative and technical personnel gain a clear understanding of the overall product compliance audit progress and results. The system implements hierarchical control of process data based on user roles to ensure data security.

[0090] like Figure 6 As shown, the standard lifecycle management unit includes the following modules: enterprise standard project establishment / development, revision, and evaluation process, enterprise standard plan adjustment process, enterprise standard plan management ledger, enterprise standard development and revision process, enterprise standard supervision and inspection process, enterprise standard evaluation process, enterprise standard review process, and enterprise standard abolition process. The online standard editing tool is also used to quickly generate enterprise standard texts that meet writing specifications during the enterprise standard development and revision process.

[0091] During the enterprise standard planning stage: the enterprise standard plan management ledger automatically aggregates plans from different sources into the plan management ledger according to the standardized enterprise standard plan template, solving the problem of manual judgment, screening and sorting of various plan sources in the traditional enterprise standard management model, avoiding information legacy and verification work time costs caused by inconsistent formats when collecting plans offline, and at the same time establishing a unified portal for publishing formulation and revision tasks, and automatically reminding delayed plans to ensure the timely implementation of enterprise standard formulation and revision tasks.

[0092] During the formulation and revision stage of enterprise standards: the main drafter can initiate the process through simple operations and automatically obtain the enterprise standard plan and number, reducing human errors. Secondly, the system can automatically generate pre-made templates that meet the requirements according to the type of enterprise standard, including detailed settings such as chapter and clause numbers, font size, etc., to ensure the uniformity and professionalism of document format specifications. Then, with the help of standard online editing tools, not only can documents be edited efficiently online, but also rich content such as tables and pictures can be directly inserted, and it supports automatic acquisition of relevant information from other modules of the system, which improves the efficiency of writing enterprise standard texts. Finally, the process also covers links such as soliciting opinions, standardization review, and multi-level approval to ensure the quality and compliance of enterprise standard content, and can automatically archive published enterprise standards to achieve closed-loop management of the entire formulation and revision process. This series of functions significantly improves the efficiency and accuracy of enterprise standard formulation and revision.

[0093] During the enterprise standard evaluation and supervision and inspection stage: in the approval of formulation and revision content, enterprise standard evaluation and supervision and inspection work, the workflow engine is used to assign responsibilities to corresponding persons, thus realizing online process and visual management during the approval of enterprise standard related business. At the same time, the formulation and revision progress, evaluation results, supervision and inspection results and rectification progress are synchronized to the corresponding modules in real time, making it easier to understand the execution of enterprise standard business.

[0094] During the review and cancellation stage of enterprise standards: the system automatically reviews the review date and automatically processes enterprise standards with different review results, improving review efficiency and ensuring the health and applicability of the enterprise standard system.

[0095] The following is a further detailed description of this unit. The specific implementation steps of this unit are as follows:

[0096] S501. Execute the enterprise standard project establishment / formulation and revision assessment process, complete the annual or temporary formulation and revision plan approval and synchronize it to the enterprise standard plan management ledger, which will serve as the main source for subsequent enterprise standard formulation and revision tasks.

[0097] The enterprise standard project establishment / development and revision assessment process collects, approves, and publishes annual and interim standard development and revision plans within each department. This process includes information such as the category, name, number, drafting department, and start and end dates of the proposed enterprise standard. After the process is complete, enterprise standard engineers no longer need to manually screen and organize the list of plans submitted by each department; instead, they can directly aggregate and store them in the enterprise standard ledger.

[0098] S502. The enterprise standard plan management ledger synchronizes enterprise standard formulation and revision plan information from different sources (manual addition, enterprise standard project establishment / formulation and revision process, enterprise standard evaluation process, enterprise standard review process) in real time, and manages and reviews each plan detail. Plans that need to be changed are completed through the enterprise standard plan adjustment process.

[0099] The Enterprise Standard Plan Management Ledger manages enterprise standard formulation and revision plans and is used to publish enterprise standard formulation and revision tasks. It displays the status and related information of each enterprise standard formulation and revision process task in real time. For plans that have been extended beyond their planned completion date, red delay reminders are displayed and pushed to the corresponding responsible persons. Enterprise standard plans can be generated from the following four methods: ① Manual addition, that is, adding a single plan or batch importing enterprise standard formulation and revision plans through the plan preparation template; ② Plans that have passed the enterprise standard project establishment / formulation and revision evaluation process; ③ Enterprise standards that are determined to require revision during the enterprise standard evaluation process; ④ Enterprise standards that are determined to require revision during the enterprise standard review process.

[0100] The Enterprise Standard Plan Management Ledger includes a master list of plans and detailed pages for each plan's development and revision. The master list displays only basic information about the plan, such as the plan type, enterprise standard number, name, replacement number, drafter, drafting department, and completion date. The detailed development and revision pages contain basic, related, and drafting information for each plan, including the plan's source, completion status, other drafting departments, and related process numbers.

[0101] S503. Initiate a drafting and revision task in the enterprise plan management ledger to complete the enterprise standard storage: During the process, the drafter fills in the enterprise standard attribute information, selects the corresponding type of pre-made enterprise standard template, and uses the standard text editing tool to compile the content to generate the enterprise standard draft. After soliciting opinions, submitting for review, and submitting for approval, the enterprise standard text is officially released and automatically archived in the enterprise standard library after final approval.

[0102] The process of formulating and revising enterprise standards is mainly divided into the following steps:

[0103] 1. The main drafter initiates the process, selects the enterprise standard plan to be carried out in the ledger, enters the enterprise standard attribute information, and the enterprise standard number is automatically generated according to the corresponding rules.

[0104] 2. Generate standard prefabricated templates. Provides various enterprise standard templates. Automatically generate text formatting that meets the requirements, including chapter and clause numbering, font size, line spacing, figure numbering, headers and footers, based on the corresponding enterprise standard type. 3. After selecting a template, invoke standard online editing functions, supporting shortcut keys to insert numbers, charts, formulas, references, and set editing areas for online content editing and proofreading.

[0105] 4. Initiate the process of soliciting opinions, standardization review, and approval for the completed draft of the enterprise standard text, and pass the compiled / revised enterprise standard to other drafters or heads of departments to review the content of the enterprise standard and provide feedback on revisions.

[0106] 5. Summarize and analyze the modification opinions, revise and polish the content of the enterprise standard text once or multiple times, and form the final draft for approval.

[0107] 6. After completing multi-level approval and countersignature on the revised enterprise standard text, the enterprise standard will be officially released and automatically archived. After the standard is released, it will be automatically included in the enterprise standard library for storage.

[0108] S504. Execute the enterprise standard evaluation process for newly added enterprise standards: Distribute the enterprise standard evaluation form to relevant standardization experts for scoring the quality of the enterprise standard and completing their review comments for subsequent review. After the process is complete, any new or revised enterprise standards mentioned in the enterprise standard evaluation comments will be included in the enterprise standard plan management ledger for subsequent enterprise standard development and revision work.

[0109] The Enterprise Standard Evaluation Process is used to evaluate and improve newly released enterprise standards. This process manages enterprise standard evaluation forms online and assigns them to relevant standardization experts for completion. These experts then score the quality of the enterprise standard and provide their review opinions for subsequent review. After the process is complete, any new or revised enterprise standards mentioned in the evaluation opinions should be included in the Enterprise Standard Plan Management Ledger for subsequent standard development and revision.

[0110] S505. Execute the supervision and inspection process for newly added enterprise standards: Inspect the use of enterprise standards, compile and publish supervision and inspection plans, distribute and execute supervision and inspection tasks, generate supervision and inspection reports and rectification plans, rectify supervision and inspection issues, and track and close them. The supervision and inspection of enterprise standards is mainly divided into the following steps:

[0111] 1. Initiate the enterprise standard supervision and inspection process, compile and publish the annual or single standard supervision and inspection plan, confirm the supervision and inspection objects, start and end time, inspection person in charge, etc., and notify relevant departments and personnel;

[0112] 2. Allocate supervision and inspection tasks according to the entire enterprise standard or clause. Based on the previous task push, automatically remind relevant professionals and personnel before the corresponding inspection completion time node;

[0113] 3. Fill out and summarize the supervision and inspection report and corresponding rectification plan. The supervision and inspection report should include enterprise standards / clause requirements, inspection time, implementation status, supporting materials, non-conformity description, etc. For issues that do not meet enterprise standards or clause requirements, you need to upload a rectification plan, including rectification measures, responsible persons for rectification, planned rectification completion time, etc. The supervision and inspection report and rectification plan should be published through the system to notify relevant departments and personnel, and the inspection report and corresponding rectification plan should be entered into the supervision and inspection issue dashboard;

[0114] The Supervision and Inspection Issues dashboard provides a unified display and analysis of supervision and inspection issues and rectification plans. It displays enterprise standard supervision and inspection data in a table format. For each issue, users can access the inspection report to understand the details of the supervision and inspection issue and the corresponding rectification plan. The dashboard also displays the rectification progress of each issue in real time, confirming whether the rectification has been completed or exceeded the planned completion time.

[0115] The Supervision and Inspection Problem Rectification Process pushes issues from the Supervision and Inspection Problem Dashboard to the person responsible for rectification. The person responsible receives a task reminder and submits the rectification status and supporting materials. If the rectification is not completed, they can apply for an extension and provide an explanation of the situation. After the Supervision and Inspection Problem Rectification Process is completed, the rectification status of the corresponding issue will be updated synchronously on the dashboard, published, and pushed to relevant personnel to review the rectification results. The person in charge of inspection will view the rectification status reported by the person responsible for rectification on the dashboard. Issues that meet the rectification requirements will be automatically updated to a closed status on the dashboard. For issues that still do not meet the requirements, a rectification process can be initiated until the rectification is in place.

[0116] S506. Every day, the enterprise standards stored in the enterprise standard library are automatically judged to see whether the review date has arrived: for enterprise standards that are about to reach the review date, the enterprise standard review process is automatically initiated; for enterprise standards that are still valid after the review result, the next review time is updated; for enterprise standards that are revised after the review result, they are included in the enterprise standard plan management ledger; for enterprise standards that are invalid after the review result, they are automatically put into the enterprise standard cancellation process.

[0117] The enterprise standard review process, for the enterprise standards that have been stored in the enterprise standard library, the system regularly scans the enterprise standard library every day to see if the review date is about to arrive, triggers the automatic initiation process of the review conditions, and carries out the enterprise standard review task. After the enterprise standard review process is completed, the system issues a notification to handle the standard review results. The review results in the review process include continued validity, revision, and invalidation. If the review result is continued validity, the next review time of the current enterprise standard will be updated; if the review result is revision, it will be automatically included in the enterprise standard plan management ledger for enterprise standard formulation and revision plan work; if the review result is invalidation, the invalidation standard can be automatically initiated as an enterprise standard invalidation process, and the status of the enterprise standard in the enterprise standard library will be converted to invalidation.

[0118] The system also optionally includes a standards early warning module, which provides reminders of upcoming standards in the domestic and international standards and regulations database, as well as the corporate standards database. Each standard or regulation is entered into the database with a corresponding implementation date, including the standard implementation date, the implementation date for new vehicle models, and the implementation date for vehicles currently in production. For each standard, a reminder time is set before the implementation date to periodically scan domestic and international standards and corporate standards to determine if a warning is needed for their respective implementation dates. If the conditions are met, the corresponding standard information will be automatically pushed to the standards early warning module, and a system reminder or warning email will be sent to the relevant responsible person for the corresponding standard.

[0119] Optionally, the system also includes a system integration unit, which is used to achieve data sharing with business systems such as personnel management, project management, parts management, test management, and certification, and to achieve guidance of standards and regulations and their structured data for various business areas through continued data exchange with upstream and downstream systems. Taking the unified certification system, project management, and parts management system as an example, data exchange is carried out through the system integration unit to provide data acquisition, push, query and other operations. By connecting with the project management system, vehicle model project information is obtained for real-time synchronization of vehicle model project library information, and the conformity assessment results of vehicle model projects are fed back to the project management system. By connecting with the parts management system, the parts tree structure and part number related information are obtained as the basis for binding standards and regulations and their clauses to parts. The unit can also integrate corporate emails through SMTP, and standard dynamics and process reminders in the system can remind users through emails.

[0120] It should be understood that the various forms of the processes shown above can be used to reorder, add, or delete steps. For example, the steps described in this application can be performed in parallel, sequentially, or in a different order, as long as the desired results of the technical solutions disclosed in this application can be achieved. This is not a limitation herein.

[0121] The above specific embodiments do not constitute a limitation on the scope of protection of this application. Those skilled in the art will appreciate that various modifications, combinations, sub-combinations, and substitutions may be made based on design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this application shall be included within the scope of protection of this application.

Claims

1. A structured processing and application system for automobile standards and regulations, characterized in that: include: Basic data control unit, which manages and maintains standards and regulations in the automotive field; A standard structured processing unit for structured processing and storage of the standard regulations; An input unit receives attribute information and a test report of a target vehicle model; The product item compliance control unit determines a matching first standard and regulation set according to the attribute information; Keywords are extracted from the first set of standards and regulations and the test flow of the test report, and are matched in pairs. A second set of standards and regulations is determined from the first set of standards and regulations by a keyword matching algorithm; the matching M of the step sequence and step content of the matching keywords in the second set of standards and regulations and the test report is calculated by the following formula; ； Among them, A and B are coefficients, and , i is the index of the keyword, N is the number of keywords, It is a key word in the standard regulations The steps are It is a key word in the testing process The steps are and is the matching keyword, express and The difference in the order of steps is express and The semantic distance of the step contents; Add the standard regulations whose M is greater than the set value to the third standard regulation set; search for test images around the steps where the keywords matching the test report are located in the third standard regulation set; use an image similarity comparison algorithm and a keyword comparison algorithm of the test image annotation name to determine a fourth standard regulation set in the third standard regulation set; determine whether the target vehicle model meets the standards according to the test requirements of each standard regulation in the fourth standard regulation set.

2. The system according to claim 1, characterized in that The attribute information includes vehicle model information, test item information, region information and time information; Determining a first set of matching standard regulations according to the attribute information includes: A first set of standard regulations that conforms to the vehicle model information and the test item information and is valid within the geographical information and the time information is determined according to the attribute information.

3. The system according to claim 1, characterized in that Management and maintenance of standards and regulations in the automotive field, including: According to the standard status change rules, current time and the substitution relationship between standards, the status of each standard and regulation is determined, including: drafting, soliciting opinions, review, approval, publication, upcoming implementation, currently effective and abolished.

4. The system according to claim 1, characterized in that Structuring and storing the standards and regulations, including: For each standard regulation, confirm the scope of the split; Traverse each paragraph in the split range and mark the paragraphs that meet the clause identification rules with clause numbers; Identify paragraphs with the same clause number and merge them, sort the merged paragraphs according to context order and clause level, and extract and split the content in clause units; Text, table and image data are respectively used as the smallest storage unit for structured storage.

5. The system according to claim 1, characterized in that Management and maintenance of standards and regulations in the automotive field, including: Compare the differences between two similar or previous versions of standard regulations; The difference comparison includes: Preprocessing of two standard regulations; A deep learning model is used to perform semantic analysis on the pre-processed standard regulations to obtain two matching clauses; A distance algorithm was used to conduct a preliminary difference analysis between the two clauses; The Smith-Waterman algorithm and the diff algorithm are used to conduct a deep difference analysis of the two clauses; Quantify and identify preliminary difference analysis and in-depth difference analysis, and generate difference reports.

6. The system according to claim 1, characterized in that Determining whether the target vehicle model complies with the standard according to the test requirements of each standard regulation in the fourth standard regulation set includes: Through the project compliance determination process, each standard and regulation in the fourth standard and regulation set that the target vehicle model needs to meet is automatically assigned a responsible person, and an assessment task is created and executed; Determine whether the test report results meet the qualitative and quantitative requirements of each standard and regulation in the fourth standard and regulation set; Among them, the judgment methods for qualitative requirements include: The BERT model is used to perform semantic analysis on standards and regulations, and keywords related to qualitative requirements are extracted; Match test report results with keywords to identify test information related to standards and regulations; Scikit-learn was used to perform data analysis and calculate the consistency score between the test information and the qualitative requirements.

7. The system according to claim 1, characterized in that Also includes: The standard life cycle management unit manages the planning stage, formulation and revision stage, evaluation and supervision and inspection stage, and review and cancellation stage of enterprise standards.

Images