Product design change and record parameter change monitoring method, device and equipment

Abstract

The application discloses a product design change and record parameter transaction monitoring method, device and equipment, relates to the vehicle production and manufacturing technical field, and the method comprises the following steps: based on the RPA technology, a standardized report template file is acquired and loaded in a periodic or active mode; all PCR change order lists in a target query time range in a target system are inquired, key monitoring object PCR is determined, and multi-dimensional information of each key monitoring object PCR is extracted; part list data corresponding to the key monitoring object PCR is acquired, and the acquired part list data and the extracted multi-dimensional information are written into the standardized report template file and output. The application can realize automatic, accurate and efficient monitoring of design change information in a PLM system, and automatically generates a standardized checking report.

Description

Technical Field

[0001] This application relates to the field of vehicle manufacturing technology, specifically to a method, device, and equipment for monitoring changes in product design and filing parameters. Background Technology

[0002] In industries like automotive, which involve complex product development, product design changes are frequent and often involve fluctuations in key parameters such as relevant regulations and product announcements. Traditionally, monitoring these design changes relies on manual, periodic logins to the target system (such as a PLM system) to query, filter, record, and organize data across multiple interfaces to generate monitoring reports. However, this approach has the following problems: (1) Inefficient: Manual operation is time-consuming and labor-intensive, especially when the number of change orders is large, it is difficult to guarantee the timeliness of monitoring; (2) Poor accuracy: Manual processing is prone to problems such as omissions, misjudgments, and recording errors, especially when judging whether design changes involve key attributes such as legal or announcement parameters, the accuracy is poor; (3) The process is not traceable: the operation process relies on personal experience and lacks standardized and structured records, making it difficult to audit and trace. (4) Response delay: It is impossible to achieve near real-time monitoring and alarms. When critical changes occur, information transmission is delayed.

[0003] Therefore, given the complexity of monitoring product design changes, how to build an automated solution that integrates intelligent sensing, information structuring, and proactive early warning has become an urgent problem to be solved. Summary of the Invention

[0004] This application provides a method, device, and equipment for monitoring changes in product design and filing parameters, which can realize automatic, accurate, and efficient monitoring of design change information in the PLM system and automatically generate standardized verification reports.

[0005] In a first aspect, embodiments of this application provide a method for monitoring changes in product design and filing parameters, the method comprising: Based on RPA technology, pre-stored standardized report template files are retrieved and loaded periodically or proactively; Query the list of all PCR change orders within the target query time range in the target system, identify the key monitoring PCRs, and extract multi-dimensional information of each key monitoring PCR. Obtain the parts list data corresponding to the key monitoring object PCR, write the obtained parts list data and extracted multi-dimensional information into a standardized report template file and output it.

[0006] In conjunction with the first aspect, in one implementation, the step of periodically or proactively acquiring and loading pre-stored standardized report template files based on RPA technology specifically includes: Based on periodically or actively triggered monitoring commands, the RPA robot accesses predefined shared storage paths; Based on the shared storage path, obtain and load the standardized report template file, which is used to define the structure of the output data.

[0007] In conjunction with the first aspect, in one implementation, before querying the list of all PCR change orders within the target query time range in the target system, the method further includes: The RPA robot automatically launches the browser and enters the PLM system login interface, reads the securely stored login credentials, automatically fills in the username and password, and performs the login operation: If login is successful, the system will query a list of all PCR change orders within the target query time range. If login fails, the login will be retried until successful or the preset number of retries is reached, at which point the login retries will stop.

[0008] In conjunction with the first aspect, in one implementation, the step of querying the list of all PCR change orders within the target query time range in the target system to determine the key monitoring target PCR specifically includes: Enter the product definition approval form query interface, determine the target query time range based on the running time, and execute the query operation; Obtain a list of all PCR change orders within the target query time range, and perform in-depth information extraction on each PCR in the PCR change order list to identify key monitored PCRs.

[0009] In conjunction with the first aspect, in one implementation, the depth information extraction operation specifically includes: The system obtains the identifier fields for whether the PCR involves regulatory or announcement parameters, and whether it involves announcement photos or optional photos. If either identifier field is yes, the current PCR is determined to be a key monitoring target PCR; otherwise, the current PCR is determined not to be a key monitoring target PCR, and the system skips the current PCR and proceeds to determine whether the next PCR is a key monitoring target PCR.

[0010] In conjunction with the first aspect, in one implementation method, For PCRs identified as key monitoring targets, the RPA robot extracts multi-dimensional information corresponding to the key monitoring target PCRs; The multi-dimensional information includes the notification number, vehicle model involved, creator, department, design specialty, current definition status, application definition status, definition difference description, part numbers and names before and after the change, suggested switching method, and planned release time. Among them, the multi-dimensional information of the key monitoring object PCR is stored in a structured manner according to the PCR and part dimensions.

[0011] In conjunction with the first aspect, in one implementation, the step of acquiring the parts list data corresponding to the key monitoring object PCR, writing the acquired parts list data and extracted multi-dimensional information into a standardized report template file, and outputting it specifically includes: Based on the export part PCR design change list query operation, obtain the part list data corresponding to the key monitoring object PCR; The acquired parts list data and extracted multi-dimensional information are correlated and integrated. The integrated data is written into a standardized report template file, and the standardized report template file is saved and output.

[0012] In conjunction with the first aspect, in one implementation method, the product design change and filing parameter anomaly monitoring method further includes: During the execution of the product design change and filing parameter anomaly monitoring method, when a preset anomaly occurs at any stage, the anomaly information is acquired and recorded, and an anomaly alarm is issued simultaneously. The abnormal information includes the cause of the abnormality, the stage in which the abnormality occurred, and suggested operating instructions.

[0013] Secondly, embodiments of this application provide a product design change and filing parameter anomaly monitoring device, the product design change and filing parameter anomaly monitoring device comprising: The loading module is used to retrieve and load pre-stored standardized report template files in a periodic or proactive manner based on RPA technology. The query module is used to query the list of all PCR change orders within the target query time range in the target system, identify key monitoring PCRs, and extract multi-dimensional information of each key monitoring PCR. The acquisition module is used to acquire the parts list data corresponding to the key monitoring object PCR, write the acquired parts list data and extracted multi-dimensional information into a standardized report template file and output it.

[0014] Thirdly, this application provides a product design change and filing parameter anomaly monitoring device. The product design change and filing parameter anomaly monitoring device includes a processor, a memory, and a product design change and filing parameter anomaly monitoring program stored in the memory and executable by the processor. When the product design change and filing parameter anomaly monitoring program is executed by the processor, it implements the steps of the product design change and filing parameter anomaly monitoring method described above.

[0015] The beneficial effects of the technical solutions provided in this application include: (1) Full-process automation: It realizes the unattended automation of the entire process from login, query, judgment, extraction, integration to report generation and notification, completely freeing manpower from repetitive labor and significantly improving efficiency; (2) Intelligent screening and precise monitoring: By introducing a trigger-based extraction mechanism based on key identifier fields, the robot can make judgments like a business expert, only handle the key changes that really need to be monitored, avoid data redundancy, and focus on core risks. (3) Data fusion and highly structured output: The detailed attribute data extracted from the interface and the list data exported from the system are automatically associated and integrated to generate a standardized report that is comprehensive, clearly structured, and can be directly used for subsequent analysis and archiving, with high data value; (4) High robustness and maintainability: A hierarchical exception handling strategy (retry, record, skip, terminate) and a detailed exception notification mechanism are designed to ensure the stable operation of the process in non-ideal environments. All configurations (such as path, account, recipient) can be externalized for easy maintenance and adaptation. (5) Good scalability: This application does not depend on a specific PLM system. By adapting to different UI element positioning methods, it can be quickly ported to other similar product data management or ERP systems for monitoring different types of business change processes. Attached Figure Description

[0016] Figure 1 This is a flowchart illustrating the method for monitoring changes in product design and filing parameters in this application. Figure 2 This is a schematic diagram of the functional modules of the monitoring device for product design changes and filing parameter anomalies in this application. Figure 3 This is a schematic diagram of the hardware structure of the monitoring equipment for changes in product design and filing parameters in this application. Detailed Implementation

[0017] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present application, and not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of the present application.

[0018] First, some of the technical terms used in this application will be explained to help those skilled in the art understand this application.

[0019] RPA (Robotic Process Automation) is a technology that uses software to automate business processes based on specified rules and procedures, thereby assisting or replacing manual tasks, freeing employees from low-value labor, and supporting 24 / 7 online operation. At the same time, RPA has a natural advantage in AI integration, achieving automation of highly complex and challenging processes through the fusion of AI technologies such as OCR and Chatbots.

[0020] Product Definition Approval Form (PCR): A document that proposes design changes to a product definition that is currently valid. It must include at least the corresponding product design change application number, change type, change specialty, associated change, switching method, implementation time after the change, problem description, current customization status, application definition status, and component details.

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

[0022] Firstly, this application provides a method for monitoring changes in product design and filing parameters. Specifically, addressing the problems of low efficiency, inaccurate identification of key changes, difficulty in integrating multi-source data, poor robustness of automated processes, and non-standard output reports caused by long-term reliance on manual operation for monitoring product design changes and parameter changes, this application provides an RPA-based automated monitoring method that can achieve intelligent filtering, automatic integration, stable operation, and standardized report generation. This method can automatically identify key changes involving regulations and announcements, achieve structured extraction and fusion of multi-source data, generate standardized reports, and has the ability to handle anomalies and proactively notify users, thereby improving the accuracy, timeliness, and reliability of monitoring. In other words, it enables automatic, accurate, and efficient monitoring of design change information in the PLM (Product Lifecycle Management) system, automatically generates standardized verification reports, and has a complete anomaly handling and notification mechanism.

[0023] In one embodiment, reference is made to Figure 1 , Figure 1This is a flowchart illustrating the method for monitoring changes in product design and filing parameters in this application. Figure 1 As shown, the methods for monitoring changes in product design and filing parameters include: S1: Based on RPA technology, retrieve and load pre-stored standardized report template files periodically or proactively; S2: Query the list of all PCR change orders within the target query time range in the target system, identify the key monitoring object PCRs, and extract multi-dimensional information of each key monitoring object PCR; S3: Obtain the parts list data corresponding to the key monitoring object PCR, write the obtained parts list data and extracted multi-dimensional information into a standardized report template file and output it.

[0024] Furthermore, in one embodiment, the process of periodically or proactively retrieving and loading pre-stored standardized report template files based on RPA technology specifically includes: S101: Based on periodically triggered or actively triggered monitoring commands, the RPA robot accesses a predefined shared storage path; S102: Obtain and load a standardized report template file according to the shared storage path. The standardized report template file is used to define the structure of the output data.

[0025] Specifically, based on a scheduled trigger (once per week) or a manual trigger command, the RPA robot accesses a predefined shared storage path and loads a standardized report template file.

[0026] Furthermore, in one embodiment, before querying the list of all PCR change orders within the target query time range in the target system, the method further includes: The RPA robot automatically launches the browser and enters the PLM system login interface, reads the securely stored login credentials, automatically fills in the username and password, and performs the login operation: If login is successful, the system will query a list of all PCR change orders within the target query time range. If login fails, the login will be retried until successful or the preset number of retries is reached, at which point the login retries will stop.

[0027] Specifically, the RPA robot automatically launches a browser, navigates to the login page of the target system (PLM system), reads the securely stored login credentials, automatically fills in the username and password, and performs the login operation. If the login fails, it executes the preset retry policy. If the retry fails, the process is terminated and an exception notification process is triggered.

[0028] Furthermore, in one embodiment, querying the list of all PCR change orders within the target query time range in the target system to determine the key monitoring target PCRs specifically includes: S201: Enter the product definition approval form query interface, determine the target query time range based on the running time, and execute the query operation; S202: Obtain a list of all PCR change orders within the target query time range, and perform deep information extraction on each PCR in the PCR change order list to identify key monitored PCRs.

[0029] Specifically, after successful login, the RPA robot automatically navigates to the product definition approval form query interface, automatically calculates and inputs the target query time range (Monday to Sunday) based on the running time, executes the query operation, obtains a list of all PCR change orders within the time range, and performs in-depth information extraction for each PCR in the list (identified by "PCR notification number") to determine the key monitoring target PCR.

[0030] Furthermore, in one embodiment, the deep information extraction operation specifically includes: obtaining the identifier field of whether the PCR involves regulatory or announcement parameters, and the identifier field of whether it involves announcement photos or optional photos. If either identifier field is yes, the current PCR is determined to be a key monitoring target PCR; otherwise, the current PCR is determined not to be a key monitoring target PCR, and the current PCR is skipped to determine whether the next PCR is a key monitoring target PCR.

[0031] Specifically, the process begins with a preliminary screening. Upon entering the PCR details interface, two key identifier fields are read: "Whether it involves legal or announcement parameters" and "Whether it involves announcement photos or optional equipment photos." Then, conditional extraction is performed. If at least one of the above identifier fields is "yes," the PCR is determined to be a key monitoring object, triggering the subsequent detailed information extraction process. If both key identifier fields are "no," the PCR is skipped, and the next PCR is processed.

[0032] Furthermore, in one embodiment, for PCRs identified as critical monitoring objects, the RPA robot extracts multi-dimensional information corresponding to the critical monitoring object PCR. That is, for PCRs identified as critical monitoring objects, the RPA robot accurately locates and extracts predefined multi-dimensional information from the graphical user interface. The multi-dimensional information includes notification number, vehicle model involved, creator, department, design change specialty, current definition status, application definition status, definition difference description, part numbers and names before and after the change, suggested switching method, and planned release time. The multi-dimensional information of the critical monitoring object PCR is structured and stored according to PCR and part dimensions.

[0033] Specifically, for PCRs identified as key monitoring objects, the RPA robot accurately locates and extracts predefined multi-dimensional information from the graphical user interface, and stores each set of extracted information in a structured manner according to the PCR and part dimensions.

[0034] Furthermore, in one embodiment, the parts list data corresponding to the key monitoring object PCR is obtained, and the obtained parts list data and extracted multi-dimensional information are written into a standardized report template file and output, specifically including: S301: Based on the export part PCR design change list query operation, obtain the part list data corresponding to the key monitoring object PCR; S302: Associate and integrate the acquired parts list data and extracted multi-dimensional information, write the integrated data into a standardized report template file, and save and output the standardized report template file.

[0035] Specifically, after completing the query and extraction of all PCRs, the RPA robot returns to the query list interface, executes the export of part PCR design change list operation, obtains supplementary part list data, and then associates and integrates the obtained part list data with the extracted multi-dimensional information. Following this, based on the loaded standardized report template file, it writes the integrated data to the specified location in the standardized report template file. Multiple part information under the same PCR notification number is presented on separate lines, while common information corresponding to that PCR number (such as definition status and difference descriptions) is merged across multiple lines to maintain the report's clarity and readability. The completed standardized report template file is saved to the specified output directory (the filename must include the time for version management). Afterwards, result notifications can be sent automatically. Based on the process execution results, an email notification is automatically triggered, generating a notification email containing a link to the output report and sending it to the designated recipients.

[0036] Furthermore, in one embodiment, the product design change and filing parameter anomaly monitoring method of this application further includes: during the execution of the product design change and filing parameter anomaly monitoring method, when a preset anomaly occurs in any link, acquiring and recording the anomaly information, and issuing an anomaly alarm at the same time; wherein, the anomaly information includes the anomaly cause, the link in which the anomaly occurred, and suggested operating instructions.

[0037] Specifically, anomaly notifications are issued. When a pre-defined anomaly occurs at any stage of the process (such as login failure, missing template, data anomaly, or system element not found), the anomaly information is captured, and an anomaly notification email containing the cause of the anomaly, the stage in which the anomaly occurred, and suggested operating instructions is generated and sent to the operations and maintenance personnel. At the same time, the anomaly information is logged to a log file.

[0038] This application utilizes RPA technology to construct an overall monitoring and verification logic, automating the monitoring process for product design changes and parameter variations. This differs from the traditional manual operation model, effectively improving efficiency and accuracy. By reading two key identifier fields—"whether it involves regulatory or announcement parameters" and "whether it involves announcement photos or optional equipment photos"—it accurately determines whether a change order is a key monitoring object, solving the problem of inaccurate key change identification. It automatically calculates and inputs the target query time range based on the runtime, enabling intelligent querying and ensuring the acquisition of all change order information within a specific time period. It accurately locates and extracts predefined multi-dimensional information from the graphical user interface, covering aspects such as notification number, involved vehicle model, and creator, providing a comprehensive data foundation for subsequent data processing. The extracted information is structured and temporarily stored according to change order and part dimensions. For subsequent data integration and utilization; the structured detailed data is associated and integrated with the exported parts list data to achieve the fusion of multi-source data and solve the problem of difficult multi-source data integration; according to the loaded report template, the integrated data is written to the specified location, and special processing is performed on part information and public information under the same notification number (part information is presented in multiple lines, public information cells are merged, etc.) to generate standardized reports, ensuring that the report format is uniform, clear and readable; when a preset abnormality occurs at any stage of the process, the abnormal information can be captured and corresponding handling measures can be executed, such as terminating the process and logging; according to the process execution result, the notification mechanism is automatically triggered. When successful, a notification email containing a link to the output report is sent. When an abnormality occurs, an abnormal notification email containing the cause of the abnormality, the stage in which it occurred and suggested operation instructions are sent, ensuring that relevant personnel are informed of the process status in a timely manner.

[0039] Secondly, this application also provides a device for monitoring changes in product design and filing parameters.

[0040] In one embodiment, reference is made to Figure 2 , Figure 2 This is a schematic diagram of the functional modules of the monitoring device for changes in product design and filing parameters in this application. Figure 2 As shown, the monitoring device for changes in product design and filing parameters includes: a loading module, a query module, and an acquisition module.

[0041] The loading module is used to periodically or proactively retrieve and load pre-stored standardized report template files based on RPA technology; the query module is used to query all PCR change order lists within the target query time range in the target system, identify key monitoring PCRs, and extract multi-dimensional information for each key monitoring PCR; the acquisition module is used to acquire the parts list data corresponding to the key monitoring PCRs, write the acquired parts list data and extracted multi-dimensional information into the standardized report template file, and output it.

[0042] Thirdly, this application provides a product design change and filing parameter change monitoring device, which can be a personal computer (PC), laptop computer, server or other device with data processing function.

[0043] Reference Figure 3 , Figure 3 This is a schematic diagram of the hardware structure of the product design change and filing parameter anomaly monitoring device involved in the embodiments of this application. In this embodiment, the product design change and filing parameter anomaly monitoring device may include a processor, a memory, a communication interface, and a communication bus.

[0044] The communication bus can be of any type and is used to interconnect the processor, memory, and communication interface.

[0045] Communication interfaces include input / output (I / O) interfaces, physical interfaces, and logical interfaces used for interconnecting internal components of the monitoring equipment for product design changes and changes in filing parameters, as well as interfaces used for interconnecting the monitoring equipment with other devices (such as other computing devices or user equipment). Physical interfaces can be Ethernet interfaces, fiber optic interfaces, ATM interfaces, etc.; user equipment can be displays, keyboards, etc.

[0046] Memory can be various types of storage media, such as random access memory (RAM), read-only memory (ROM), non-volatile RAM (NVRAM), flash memory, optical storage, hard disk, programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), etc.

[0047] The processor can be a general-purpose processor, which can call the product design change and filing parameter change monitoring program stored in the memory and execute the product design change and filing parameter change monitoring method provided in the embodiments of this application. For example, the general-purpose processor can be a central processing unit (CPU). The method executed when the product design change and filing parameter change monitoring program is called can be referred to the various embodiments of the product design change and filing parameter change monitoring method of this application, and will not be repeated here.

[0048] Those skilled in the art will understand that Figure 3 The hardware structure shown does not constitute a limitation of this application and may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0049] The terms "comprising" and "having," and any variations thereof, in the specification, claims, and accompanying drawings of this application are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or apparatus that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to such process, method, product, or apparatus. The terms "first," "second," and "third," etc., are used to distinguish different objects, etc., and do not indicate a sequence, nor do they limit "first," "second," and "third" to different types.

[0050] In the description of the embodiments of this application, terms such as "exemplary," "for example," or "for instance" are used to indicate examples, illustrations, or explanations. Any embodiment or design described as "exemplary," "for example," or "for instance" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or designs. Specifically, the use of terms such as "exemplary," "for example," or "for instance" is intended to present the relevant concepts in a concrete manner.

[0051] In the description of the embodiments of this application, unless otherwise stated, " / " means "or". For example, A / B can mean A or B. The "and / or" in the text is merely a description of the relationship between related objects, indicating that there can be three relationships. For example, A and / or B can mean: A exists alone, A and B exist simultaneously, and B exists alone. In addition, in the description of the embodiments of this application, "multiple" means two or more.

[0052] In some processes described in the embodiments of this application, multiple operations or steps are included in a specific order. However, it should be understood that these operations or steps may not be executed in the order they appear in the embodiments of this application, or they may be executed in parallel. The sequence number of the operation is only used to distinguish different operations, and the sequence number itself does not represent any execution order. In addition, these processes may include more or fewer operations, and these operations or steps may be executed sequentially or in parallel, and these operations or steps may be combined.

[0053] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) as described above, and includes several instructions to cause a terminal device to execute the methods described in the various embodiments of this application.

[0054] The above are merely preferred embodiments of this application and do not limit the patent scope of this application. Any equivalent structural or procedural transformations made using the content of this application's specification and drawings, or direct or indirect applications in other related technical fields, are similarly included within the patent protection scope of this application.

Claims

1. A method for monitoring changes in product design and filing parameters, characterized in that, The method for monitoring changes in product design and filing parameters includes: Based on RPA technology, pre-stored standardized report template files are retrieved and loaded periodically or proactively; Query the list of all PCR change orders within the target query time range in the target system, identify the key monitoring PCRs, and extract multi-dimensional information of each key monitoring PCR. Obtain the parts list data corresponding to the key monitoring object PCR, write the obtained parts list data and extracted multi-dimensional information into a standardized report template file and output it.

2. The method for monitoring changes in product design and filing parameters as described in claim 1, characterized in that, The process of periodically or proactively retrieving and loading pre-stored standardized report template files based on RPA technology specifically includes: Based on periodically or actively triggered monitoring commands, the RPA robot accesses predefined shared storage paths; Based on the shared storage path, obtain and load the standardized report template file, which is used to define the structure of the output data.

3. The method for monitoring changes in product design and filing parameters as described in claim 1, characterized in that, Before querying the list of all PCR change orders within the target query time range in the target system, the following is also included: The RPA robot automatically launches the browser and enters the PLM system login interface, reads the securely stored login credentials, automatically fills in the username and password, and performs the login operation: If login is successful, the system will query a list of all PCR change orders within the target query time range. If login fails, the login will be retried until successful or the preset number of retries is reached, at which point the login retries will stop.

4. The method for monitoring changes in product design and filing parameters as described in claim 1, characterized in that, The query system retrieves a list of all PCR change orders within the target time frame to identify key monitored PCRs, specifically including: Enter the product definition approval form query interface, determine the target query time range based on the running time, and execute the query operation; Obtain a list of all PCR change orders within the target query time range, and perform in-depth information extraction on each PCR in the PCR change order list to identify key monitored PCRs.

5. The method for monitoring changes in product design and filing parameters as described in claim 4, characterized in that, The depth information extraction operation specifically includes: The system obtains the identifier fields for whether the PCR involves regulatory or announcement parameters, and whether it involves announcement photos or optional photos. If either identifier field is yes, the current PCR is determined to be a key monitoring target PCR; otherwise, the current PCR is determined not to be a key monitoring target PCR, and the system skips the current PCR and proceeds to determine whether the next PCR is a key monitoring target PCR.

6. The method for monitoring changes in product design and filing parameters as described in claim 1, characterized in that: For PCRs identified as key monitoring targets, the RPA robot extracts multi-dimensional information corresponding to the key monitoring target PCRs; The multi-dimensional information includes the notification number, vehicle model involved, creator, department, design specialty, current definition status, application definition status, definition difference description, part numbers and names before and after the change, suggested switching method, and planned release time. Among them, the multi-dimensional information of the key monitoring object PCR is stored in a structured manner according to the PCR and part dimensions.

7. The method for monitoring changes in product design and filing parameters as described in claim 1, characterized in that, The process of obtaining the parts list data corresponding to the key monitoring object PCR, writing the obtained parts list data and extracted multi-dimensional information into a standardized report template file, and outputting it specifically includes: Based on the export part PCR design change list query operation, obtain the part list data corresponding to the key monitoring object PCR; The acquired parts list data and extracted multi-dimensional information are correlated and integrated. The integrated data is written into a standardized report template file, and the standardized report template file is saved and output.

8. The method for monitoring changes in product design and filing parameters as described in claim 1, characterized in that, The method for monitoring changes in product design and filing parameters also includes: During the execution of the product design change and filing parameter anomaly monitoring method, when a preset anomaly occurs at any stage, the anomaly information is acquired and recorded, and an anomaly alarm is issued simultaneously. The abnormal information includes the cause of the abnormality, the stage in which the abnormality occurred, and suggested operating instructions.

9. A device for monitoring changes in product design and filing parameters, characterized in that, The product design change and filing parameter anomaly monitoring device includes: The loading module is used to retrieve and load pre-stored standardized report template files in a periodic or proactive manner based on RPA technology. The query module is used to query the list of all PCR change orders within the target query time range in the target system, identify key monitoring PCRs, and extract multi-dimensional information of each key monitoring PCR. The acquisition module is used to acquire the parts list data corresponding to the key monitoring object PCR, write the acquired parts list data and extracted multi-dimensional information into a standardized report template file and output it.

10. A monitoring device for changes in product design and filing parameters, characterized in that, The product design change and filing parameter anomaly monitoring device includes a processor, a memory, and a product design change and filing parameter anomaly monitoring program stored in the memory and executable by the processor. When the product design change and filing parameter anomaly monitoring program is executed by the processor, it implements the steps of the product design change and filing parameter anomaly monitoring method as described in any one of claims 1 to 8.

Images