Production line test construction system based on MES system

Abstract

The invention discloses a production line test construction system based on an MES system, and relates to the technical field of intelligent manufacturing and production line testing, and the production line test construction system comprises a test configuration module, a test execution module, a data integration module, a visual interface module and an authority management module. The test configuration module is used for automatically obtaining a test process template from the MES system according to the product model information and completing process customization in a graphical mode; the test execution module identifies a to-be-tested product and calls a process file, and controls the test equipment to execute a test and perform data acquisition and judgment; the data integration module binds the test result with the unique identifier of the product, and uploads the test result to the MES system to realize full-process tracing; the visual interface module is used for displaying a process state and a test result; the authority management module is used for performing hierarchical control and version conflict detection on the operation authority; according to the system, the construction efficiency and execution reliability of the test process are improved, and closed-loop and intelligent management of data in the test process is realized.

Description

Technical Field

[0001] This invention relates to the field of intelligent manufacturing and production line testing technology, specifically to a production line testing construction system based on an MES system. Background Technology

[0002] With the continuous improvement of the level of intelligence in the manufacturing industry, Manufacturing Execution Systems (MES) are playing an increasingly important role in modern production lines. MES systems can realize functions such as comprehensive monitoring of the production process, resource scheduling, production traceability, and quality control, and have become a key support system for realizing intelligent manufacturing.

[0003] Before production line construction and product launch, the design and verification of testing processes are crucial to ensuring production efficiency and product quality. Most existing testing systems are manually configured or based on PLCs (Programmable Logic Controllers), which suffer from long deployment cycles, poor reusability, and high system integration complexity, making it difficult to meet the requirements of rapid test construction and deployment under changing product demands.

[0004] In addition, current testing systems and MES platforms often lack deep integration, resulting in the inability to upload test data in real time and the inability to flexibly adjust test processes, which affects the production line's flexible management and data closed-loop capabilities.

[0005] Therefore, there is an urgent need for a production line test construction system based on MES to enable rapid construction, flexible configuration and efficient integration of test processes, thereby improving production line debugging efficiency and automation level. Summary of the Invention

[0006] The purpose of this invention is to provide a production line test construction system based on MES system to address the shortcomings of the prior art.

[0007] To achieve the above objectives, the present invention provides the following technical solution: a production line test construction system based on an MES system, comprising: The test configuration module is used to automatically retrieve the corresponding test process template from the MES system based on the product model information, and to customize the test process through a graphical editing method. The test execution module is used to automatically identify the product under test during production line operation, call the configured test process, control the test equipment to perform the corresponding test operations, and collect test data in real time and make preliminary judgments. The data integration module is used to bind test results with the product's unique identifier and upload them to the MES system in a structured manner, so as to realize the real-time integration and traceability management of test data and production history. The visualization interface module is used to display the test process status, key test results, equipment operation status and abnormal alarm information to operators in real time, and supports online adjustment of test parameters and dynamic plugging and unplugging of test nodes; The access control module is used to control access to, editing, and deployment of test process templates based on user identity and role, ensuring the security and consistency of test process configuration.

[0008] Preferably, the test configuration module specifically includes: Identify the product model information corresponding to the current production task and send a test process template request instruction to the MES system; Receive the preset test process template returned by the MES system, and parse the test nodes, execution order and parameter configuration items in the template; Through the graphical workflow editing interface, users can call the functional modules in the standard test component library, customize the test workflow and set parameters by dragging and dropping according to logic, and generate a test workflow configuration file for the current product.

[0009] Preferably, the test execution module specifically includes: By reading the unique identification information label or QR code on the product, the model and work order number of the product under test can be automatically identified. Based on the recognition results, the system automatically matches and calls the corresponding test process configuration file, and parses the test instruction sequence and device interface parameters therein. According to the test process control logic, instructions are issued to each test device to perform electrical, functional or communication type test operations, and test data is collected in real time through interface protocols to perform preliminary threshold judgment or logical judgment locally.

[0010] Preferably, the data integration module specifically includes: After the testing process is completed, the collected test results are bound with the unique identifier of the corresponding product to generate a test data entity object; The test data entities are formatted according to a predefined data structure, including test time, test items, result status, judgment criteria, and exception information fields; Structured data is pushed to the corresponding production history database of the MES system through a standardized interface protocol, and a connection is established with the process records to achieve real-time integration of test data and full-process traceability.

[0011] Preferably, the visualization interface module specifically includes: The system can acquire the execution status of the test process, the progress of test nodes, and the equipment operation information in real time, and dynamically display them on the operation interface in the form of flowcharts and data panels. The collected key test results are categorized and displayed, including normal items, boundary items, and abnormal items, while also supporting historical record comparison and result filtering; It provides access to parameter adjustment and process editing, allowing authorized operators to plug, switch, or rearrange test nodes without interrupting the overall process.

[0012] Preferably, the permission management module specifically includes: User identity is identified based on user login information, and their corresponding role information and operation permission level are read from the permission configuration database. Access, editing, and deployment operations of test process templates are subject to permission scope verification, allowing only users who meet the permission policy to perform the corresponding operations, and critical operations are logged. When multiple users operate on the same test process template, a version locking and conflict detection mechanism is implemented to prevent concurrent modifications from causing configuration anomalies.

[0013] The technical effects and advantages provided by the present invention in the above technical solution are as follows: 1. This invention constructs a production line test building system based on an MES system, connecting key aspects of test process configuration, execution, data acquisition, visual monitoring, and access control, achieving a high degree of automation and flexibility in the testing process. The system can automatically match and call test process templates based on product models, supports graphical configuration and standard component calls, significantly improving the efficiency and reusability of test process configuration; during test execution, it automatically identifies product identification information, precisely controls test equipment to complete multiple types of test operations, and performs preliminary data judgment locally, ensuring the accuracy and real-time nature of test execution.

[0014] 2. This invention achieves the binding and structured uploading of test data with unique product identifiers through a data integration module, and integrates it in real time with the production history data of the MES system to build a complete product quality traceability chain. The visualization interface module dynamically displays process status, test results, and equipment information, while supporting online process adjustments based on permissions. The permission management module ensures system security and configuration consistency in a multi-user collaborative environment through user role recognition, hierarchical permission control, and version conflict detection mechanisms. In summary, this invention improves the efficiency of test process construction, operational stability, and management intelligence, and has significant potential for widespread application. Attached Figure Description

[0015] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in this invention. For those skilled in the art, other drawings can be obtained based on these drawings.

[0016] Figure 1 This is a mind map of the system modules of the present invention. Detailed Implementation

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

[0018] For examples, please refer to Figure 1 As shown in this embodiment, a production line test construction system based on an MES system includes: The test configuration module is used to automatically retrieve the corresponding test process template from the MES system based on the product model information, and to customize the test process through a graphical editing method. The test execution module is used to automatically identify the product under test during production line operation, call the configured test process, control the test equipment to perform the corresponding test operations, and collect test data in real time and make preliminary judgments. The data integration module is used to bind test results with the product's unique identifier and upload them to the MES system in a structured manner, so as to realize the real-time integration and traceability management of test data and production history. The visualization interface module is used to display the test process status, key test results, equipment operation status and abnormal alarm information to operators in real time, and supports online adjustment of test parameters and dynamic plugging and unplugging of test nodes; The access control module is used to control access to, editing, and deployment of test process templates based on user identity and role, ensuring the security and consistency of test process configuration.

[0019] This invention provides a production line test construction system based on an MES system. The test configuration module, as a core component of the system, is responsible for enabling rapid acquisition and visual configuration of test processes, as well as integration with standard components, ensuring the flexibility, reusability, and high compatibility of the test processes. The following provides a detailed description of the composition, specific processes, and implementation methods of the test configuration module to enable those skilled in the art to fully implement this technical solution.

[0020] The test configuration module automatically retrieves the corresponding test process template from the MES system based on the product model information involved in the current production task, and customizes the process through a visual graphical editing interface. The configuration process supports calling standard test component libraries, enabling drag-and-drop combination of process nodes and parameter settings, ultimately generating a test process configuration file suitable for the specific product, which can then be called by subsequent execution modules.

[0021] This module aims to improve the configuration efficiency of the testing process, reduce the error rate of manual configuration, enhance the reusability of test templates, and adapt to complex production line environments with multiple products and processes.

[0022] The test configuration module specifically includes the following three core steps: Once a production task is issued in the MES system, the system will trigger the workflow of the test configuration module based on the product model specified in the task order or work order. This module first reads the product model information of the current work order in the MES system through an interface, and then sends a request instruction for the test process template to the MES system based on the model.

[0023] This request instruction is formatted as a standard API call message and includes the following fields: Product Model Code; Task ID; Request type identifier (TemplateRequestType, such as initialization request, version update request, etc.); After receiving the instruction, the MES system retrieves the preset test process template corresponding to the product model from the template library and returns it to the test configuration module in a structured data format (such as XML or JSON).

[0024] After receiving the test process template returned from the MES system, the test configuration module first performs integrity verification on the template file (such as field checking, version number verification, format consistency, etc.) to ensure that no abnormalities occur during data transmission.

[0025] The module then parses the template content and extracts its main structural elements, including: Test node list: Each node represents an independent test task, including test type, device interface called, expected results, etc. Execution order definition: The logical relationship between nodes (serial, parallel, conditional jump, etc.); Parameter configuration items: These are used to control parameters such as limits, waiting time, and voltage range during the testing process.

[0026] After parsing, the template structure is converted into intermediate data of a visual graphical model within the system for use in the next step of the editing process.

[0027] Users can further configure and customize the analyzed test process through the graphical process editing interface provided by the test configuration module. This editing interface is a drag-and-drop visual operating environment that supports the following key functions: Node addition and reorganization: Users can select functional modules (such as electrical testing, functional verification, communication checks, etc.) from the standard test component library and drag and drop them into the process to insert or replace existing nodes as needed; Node parameter settings: After clicking on any test node, a parameter setting window will pop up, allowing users to fine-tune parameters such as the test threshold, time, and judgment conditions for that node; Process logic orchestration: Users can set the execution order between nodes through graphical connections, including sequential execution, conditional judgment (such as "if the test fails, jump to node X") and parallel branch logic; Real-time preview and verification: During the process configuration, the system will generate a preview diagram of the process structure in real time and perform consistency verification on parameter settings and logical paths, and promptly prompt configuration errors or missing items.

[0028] The above editing process does not rely on coding, allowing operators to construct complex workflows without requiring a programming background. Furthermore, the graphical workflow editing interface also supports the following auxiliary functions: Template version control: Automatically generates a new process version number after each edit, supporting version rollback and comparison; Configuration import / export: Supports exporting configured processes as standard configuration file formats for import and use by other production lines or systems; Permission verification interface: Automatically calls the permission management module for modification of key parameters to ensure that operators have the appropriate permissions.

[0029] After editing, the system encapsulates the configuration results into a standard test process configuration file and stores it in the database, establishing a one-to-one correspondence with the product model for subsequent use by the test execution module.

[0030] In the production line testing system based on MES provided by this invention, the test execution module is a key component throughout the testing process of production. It is mainly used to realize functions such as product identification, test process invocation, equipment control, and data acquisition and judgment. Its design goal is to achieve automation, standardization, and real-time response capabilities in the testing process to meet the testing needs of modern production lines with multiple models on mixed lines, complex processes, and multi-process collaboration.

[0031] The following section will provide a systematic explanation of this module in terms of its technical structure, workflow, key functions, and implementation details.

[0032] The test execution module is responsible for automatically identifying the unique identifier of the product under test during actual production line operation. Combined with work order data issued by the MES system, it automatically matches and calls the corresponding test process configuration file. This module relies on test process logic instructions to control various test devices within the production line to execute specified test actions. It also collects test data through standard communication interfaces, performing real-time local preliminary judgments to provide a foundation for subsequent data integration and quality traceability.

[0033] By integrating this module, a fully automated closed loop can be achieved, encompassing "product identification → process scheduling → equipment control → test acquisition → data judgment".

[0034] The test execution module specifically includes the following three key steps: At the production line testing station, after a product arrives at the testing location, the system uses deployed automatic identification equipment (such as QR code scanners, RFID readers, etc.) to read the unique identification information bound to the product itself. This identification typically includes: Product Model Code; Work order number (OrderID); Product serial number (SerialNumber).

[0035] After successful reading, the system compares the above information with the MES system or local cached work order information to verify its validity and confirm the test status.

[0036] This step completes data collection through a standard recognition protocol and includes timeout and misreading handling mechanisms. For example, if recognition fails, the system will automatically pause the current process and issue an error message to ensure accurate correspondence of the test task.

[0037] After product identification is complete, the test execution module automatically calls the test process configuration file corresponding to the product model based on the product model information. This configuration file is generally a structured process definition file generated by the test configuration module and stored in a local database or a remote configuration server.

[0038] This module completes the process loading through the following steps: Search process document: Search for matching process documents based on product model; Verify process version: Confirm whether the currently invoked version is the one issued by MES or the latest configuration version; Parse the test instruction sequence: including parameters such as test item number, test type (electrical, functional, communication, etc.), execution order, device call interface, waiting time, and expected value; Parse device interface parameters: Generate standardized interface call instructions (such as Modbus, RS-485, TCP / IP, etc.) based on the execution device type and control protocol defined for each test node.

[0039] Process parsing enables process-level instruction encapsulation and execution preparation, decoupling test logic from underlying device control and improving system versatility and maintainability.

[0040] After the process parsing is completed, the system begins to execute the instructions of each test node one by one according to the test process control logic, specifically including: Control interface transmission: Send execution commands to the test equipment through middleware or control gateway that interfaces with the device, such as start measurement, set voltage and current output, initiate communication detection, etc. Status feedback monitoring: Listen to device status signals to confirm whether the device response status is normal (such as response time, readiness status, etc.). Real-time data acquisition: The data acquisition module reads the test results returned by the device, including various data types such as voltage, current, waveform, and signal response time; Local preliminary judgment: Based on the threshold range or logical rules set in the configuration process, the collected data is initially judged, such as "whether it is qualified", "whether it exceeds the limit", "whether it times out", etc.

[0041] The judgment result will generate preliminary test conclusions locally and mark the corresponding conclusions in the process execution status diagram. Simultaneously, this module supports marking and caching abnormal test cases for later analysis.

[0042] To ensure the stability of the testing process and the robustness of the system, the test execution module also integrates the following technical measures: Test timeout control: Each test operation is configured with a maximum response time, and will automatically terminate and report if the timeout occurs; Multi-device concurrent management: Supports the control of multiple test devices at the same workstation to collaboratively execute different test tasks, and coordinates the test order through a queue mechanism; Breakpoint recovery mechanism: When the test is interrupted due to equipment failure or network fluctuations, the system automatically records the current test progress and resumes execution from the breakpoint after the problem is resolved; Execution log recording: Detailed execution logs are generated throughout the entire process, recording the time of each instruction issuance, response data, judgment result, and error code, which facilitates tracing and diagnosis.

[0043] In the production line testing construction system based on the MES system provided by this invention, the data integration module is one of the key modules for realizing structured processing, binding traceability, and closed-loop control of test data. Its main task is to establish a binding relationship between the collected test data and the unique identifier of the specific product after the test process is completed, perform formatting processing, upload it to the MES system through a standardized interface protocol, and establish a logical association with the production process history, thereby realizing real-time integration of test information and full-process traceability management.

[0044] The data integration module automatically starts at the end of the testing process. It extracts the data results generated during the test execution and achieves hierarchical data integration with the production process management function of the MES system. This module not only ensures the complete and accurate uploading of test data, but also supports hierarchical management of structured fields and traceability binding, ultimately achieving a product-level quality control closed loop.

[0045] This module mainly includes three core functions: Generate test data entity objects; The test data was structured. Push the data to the MES system and establish a resume association.

[0046] After the test execution module completes all test node operations, it aggregates the test results to form a complete test output dataset. The dataset typically contains the following information: The raw data collected for each test item (such as voltage, current, signal strength, etc.); Judgment result (pass / fail); Test start and end times; Test equipment number and channel information; Abnormal information (such as device error codes, over-limit flags, timeout records, etc.).

[0047] At this point, the data integration module binds the test result to the unique identifier of the current product. This unique identifier is the identification information assigned to the product at the initial stage of production, such as a QR code, serial number (SN) code, or RFID tag, and is used to uniquely identify a specific product unit throughout the entire production cycle.

[0048] This binding process encapsulates the test results into a TestDataObject and records metadata such as object creation time, operator number, and process version. The entity object structure includes: ProductID: A unique identifier; TestItems: Records of multiple test items; TestTime: Test timestamp; ResultSummary: Overall test conclusions; DeviceInfo: Executes device information; ExceptionRecord: A list of exception data.

[0049] This object model ensures that test data is complete and traceable within the system.

[0050] To ensure the parsability of uploaded data and the efficiency of subsequent analysis and processing, the data integration module performs structured transformation on the test data entities. Specifically, this includes: Field standardization: All test items use predefined field naming conventions (such as Voltage_U1, Current_I2, Comm_Check1) to ensure data consistency; Unified data format: JSON or XML structure is used as the transmission format, with a clear nested structure, including subfields such as test items, values, units, and status; Content integrity verification: The system will verify the data fields before uploading to ensure that all test items have corresponding results, units and judgment criteria, to prevent incomplete or missing data from being uploaded. Judgment Basis Record: The system writes information such as the parameter template ID and limit standard number used in this test into the data object, forming a complete quality judgment chain.

[0051] After structuring, the data integration module uploads the encapsulated test data objects to the production history database in the MES system via a standardized interface protocol. The upload interface follows a unified data transmission protocol; common protocols include: HTTP / HTTPS RESTful API; OPC UA / DA; WebSocket or message queue middleware (such as MQTT, Kafka), etc.

[0052] The upload process includes the following steps: Interface verification: The system performs signature verification on upload requests to ensure the legality of the data source; Transaction control: Data uploads use transactional operations to ensure that a confirmation response is returned as soon as the write is successful; Association and binding: The MES system automatically binds the uploaded test data with the process execution history (such as "FCT test station") to form a complete link in the production process.

[0053] Once successfully bound, the test data will become part of the product's quality record and can be used subsequently for: Product-level quality traceability; Batch-level quality analysis; Workstation yield analysis and equipment performance evaluation; Linked analysis with data from other processes (such as assembly, aging, packaging, etc.).

[0054] In addition, the data integration module supports a status feedback mechanism after data upload. If MES returns an abnormal response (such as missing fields or duplicate data), the module will log and initiate a retransmission retry according to the configuration rules.

[0055] In the production line test construction system based on MES provided by this invention, the visualization interface module serves as an important interface component for human-computer interaction. It is mainly used to dynamically present the test process execution status, result feedback, and equipment operation status. At the same time, it provides parameter adjustment and process modification functions, enabling operators to intervene and optimize the test process in real time.

[0056] This module aims to improve the transparency of system operation, the intuitiveness of data presentation, and the flexibility of process debugging. It is particularly suitable for testing environments with multiple test nodes, multi-device collaboration, and dynamic process scenarios.

[0057] The visual interface module is built on a browser / client graphical interface development framework, integrating functions such as process status display, test result feedback, parameter adjustment, and process control. Its main tasks include: Real-time acquisition and graphical presentation of test process execution information; Key test results are categorized and displayed with interactive filtering support; It provides online parameter and process adjustment functions to enhance the flexibility and responsiveness of testing.

[0058] This module is designed with a focus on responsiveness, visual clarity, and interactive controllability. It adopts a modular UI architecture, is compatible with multi-resolution terminals, and meets the multi-role usage needs of production line engineers, equipment maintenance personnel, and quality management personnel.

[0059] The visualization interface module first periodically retrieves or listens for status data pushed by the test execution module via the system message bus or real-time data channel, including: The name and version of the currently executing test process; The execution progress (complete / in progress / waiting) of the test nodes in the process; The operating status of the associated test equipment (ready / running / abnormal / offline); The current product's unique identifier and batch information.

[0060] The above data is presented in parallel on the interface in two formats: Flowchart Mode: The flowchart view displays the logical relationships between test nodes, uses colors to mark node status (e.g., green for completion, yellow for execution, and red for exception), and displays key information such as node execution time and test values ​​through floating boxes; Data panel mode: Displays the overall execution status of the current process, test results of each node, equipment information, and cumulative process time in the form of tables or charts.

[0061] The interface supports customizable data refresh rates (e.g., 1 second / time to 5 seconds / time) to ensure that the interface state remains highly synchronized with the actual process. Furthermore, the module incorporates push mechanisms such as WebSocket to optimize status response latency.

[0062] During the process execution, the various test data collected by the test execution module will be synchronously transmitted to the visualization interface module for display. This module processes and labels the received test data according to preset classification rules, mainly including: Normal items (qualified and stable data); Boundary terms (critical value data close to the decision threshold); Abnormal items (items judged as unqualified or missing data).

[0063] The categorization results are displayed using different color indicators or labels, allowing users to quickly identify items of interest. The interface provides the following interactive functions: Results Filter: Users can filter the displayed items by category, test type, node position, time, and other dimensions; Historical data comparison: The system supports calling historical test data of the same product model and presenting trend comparison charts between the current results and historical values ​​to assist in fault tracing and quality analysis; Results export function: Supports exporting test reports for the current product or batch, with formats including PDF and Excel, to meet the needs of quality inspection archiving or external provision.

[0064] This module also supports manual annotation and screenshot recording of key nodes, providing auxiliary explanations for subsequent analysis or problem reporting.

[0065] To address the needs for real-time debugging, parameter correction, and process optimization during testing, the visual interface module provides access for parameter adjustment and process editing. Authorized operators can perform the following operations without interrupting the overall testing process: Online parameter adjustment: Clicking on any running or pending test node will bring up a parameter setting panel, allowing modification of parameters such as voltage values, timeout periods, and judgment thresholds. The system performs syntax and logic checks on the changed values ​​to ensure the adjustments are effective. Process node insertion and removal: Operators can drag and drop standard test nodes from the component library into the current process, insert them into a specified position or replace abnormal nodes, and support real-time re-arrangement of execution paths; Jump and skip control: In response to test anomalies or temporary strategy changes, the system allows operators to issue commands to skip the current node or jump to a specified node, and the process engine automatically adjusts the execution path; Adjustment records and version control: All online modification operations are recorded in the operation log, and a new configuration version is automatically generated in the process version control module, which facilitates later retrospection and comparison.

[0066] This functional area is strictly integrated with the access control module, allowing only users with specific role permissions (such as process engineers, test supervisors, etc.) to access and operate it. At the same time, the operation interface will highlight the "Temporary Debugging Mode" prompt to prevent accidental operation.

[0067] Through the above design and implementation, the visualization interface module significantly improves the system's interactivity, observability, and on-site responsiveness, and has the following technical advantages: Transparent and visible process status: The flowchart is linked with the equipment status in real time, making it easy to intuitively understand the system's operating status; Precise result classification: Pass, boundary and abnormal test items are clearly visible, making it easy to quickly focus on and trace the problem; Online adjustable and ready to use: Parameters and processes can be adjusted without interrupting testing, shortening the debugging cycle; Access control and logging: Operations are fully controlled and traceable, meeting the auditing and management requirements of industrial applications; Adaptable to multiple terminals and roles: The interface supports touch devices, large screen displays, and simplified operation on mobile devices, making it suitable for use in multiple scenarios.

[0068] In summary, the visualization interface module in this invention, which combines process display, data analysis, and real-time control, provides powerful human-computer interaction support for the testing system, effectively improving the ease of use, debugging flexibility, and anomaly response capabilities of the testing system. It is an important component in realizing the automation and intelligence of production line testing.

[0069] In the production line test construction system based on MES proposed in this invention, the permission management module is an important mechanism to ensure system security and configuration consistency. This module is responsible for implementing hierarchical permission control based on user identity recognition, ensuring that access, editing, and deployment operations of test process templates are subject to authorization restrictions, and managing version conflicts and logging in multi-person collaborative scenarios, effectively preventing problems such as accidental operation, unauthorized operation, and configuration inconsistency.

[0070] The access control module is primarily used to implement functions such as user role identification, operation permission verification, collaborative modification conflict detection, and operation log retention. Its core objective is: To achieve system operation behavior that is identifiable, controllable, traceable, and conflict-preventable; It supports fine-grained permission control based on role / user / functional module / operation type; It maintains compatibility with the MES user system, enabling single sign-on and unified identity authentication across platforms.

[0071] This module is widely used in the permission call interfaces of the test configuration module, test execution module, and visual interface module, and is a fundamental component that supports the safe and orderly operation of the entire system.

[0072] After a user logs into the system, the access control module first verifies the user's identity. The verification process includes: User login information authentication (username / password or MES system SSO interface); Verify the legitimacy of the identity and obtain a unique user identifier (UserID); Query the permission configuration database to retrieve the user's bound role information (such as: test engineer, process supervisor, system administrator, etc.) and corresponding permission level; User roles and permissions are managed in the system using a structured permission table. Each operation and access object has a permission identifier (PermissionCode), and control is achieved through role mapping. For example: User Role Permissions Function Permission Code Process Engineer Edit test process EDIT_FLOW Test Manager Release Process Template PUBLISH_TEMPLATE Operator Browse test data VIEW_DATA When users perform operations within the system, the access management module performs real-time permission checks on access, editing, and deployment operations involving test process templates. The verification process includes: Intercept the target operation request and extract the operation intent and object; Match the current user's permission cache; Check the permission rules table to determine whether you have permission for this operation; If permissions are insufficient, the system will refuse the operation and return a clear permission error message; If the permissions match successfully, execution is allowed to continue, and a critical operation logging mechanism is initiated.

[0073] The critical operation log contains the following information fields: Operate user IDs and roles; Operation object identifier (e.g., template ID); Operation types (Add, Edit, Delete, Deploy); Operation timestamp; Snapshot of differences before and after the operation (for audit trail); Client IP and terminal information (for security protection).

[0074] Log files are stored in a log database and can be queried and exported by user, template, time, and other dimensions, facilitating auditing and backtracking by management departments.

[0075] When multiple users edit the same test process template in parallel, it can easily lead to configuration conflicts or version overwriting issues. To address this, the access control module introduces a version locking and conflict detection mechanism, as follows: When a user opens a workflow template for editing, the system automatically locks the template and records the "editing" status and the current editing user. When the template is locked, other users will receive a message saying "The current template is being edited by user X" and will be prevented from entering the editing mode. If the first user does not operate for a long time, the system will automatically release the lock (there is a timeout mechanism, such as 15 minutes of inactivity). If multiple users obtain historical copies of the same template, edit them offline, and attempt to submit them, the system will use a version number comparison mechanism to detect if there are version differences and prompt users to handle conflicts (such as merging, overwriting, or abandoning). All version conflict operations must be confirmed by a senior user with "process release permissions" to prevent low-privilege users from accidentally damaging the process.

[0076] This mechanism significantly reduces the probability of process configuration errors in multi-person collaborative scenarios, ensuring the consistency and stability of test process logic and data configuration.

[0077] This access control module is designed with loose coupling in mind, allowing for flexible integration with various user authentication systems. Key features include: Supports integration with unified identity authentication systems (such as LDAP, OAuth2.0, SSO). Supports dynamic adjustment of role permissions without requiring a system restart; Provides an access control API interface for other subsystems or third-party platforms to call; Configurable permission-based templates are available to adapt to different enterprise security policies and management architectures.

[0078] In addition, the system also supports a risk level assessment mechanism for operational behaviors. For example, when a user frequently performs highly sensitive operations, the system will trigger behavior audits or administrator reminders, which helps to enhance security.

[0079] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any changes or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application.

Claims

1. A production line test construction system based on an MES system, characterized in that: include: The test configuration module is used to automatically retrieve the corresponding test process template from the MES system based on the product model information, and to customize the test process through a graphical editing method. The test execution module is used to automatically identify the product under test during production line operation, call the configured test process, control the test equipment to perform the corresponding test operations, and collect test data in real time and make preliminary judgments. The data integration module is used to bind test results with the product's unique identifier and upload them to the MES system in a structured manner, so as to realize the real-time integration and traceability management of test data and production history. The visualization interface module is used to display the test process status, key test results, equipment operation status and abnormal alarm information to operators in real time, and supports online adjustment of test parameters and dynamic plugging and unplugging of test nodes; The access control module is used to control access to, editing, and deployment of test process templates based on user identity and role, ensuring the security and consistency of test process configuration.

2. The production line test construction system based on MES system according to claim 1, characterized in that: The test configuration module specifically includes: Identify the product model information corresponding to the current production task and send a test process template request instruction to the MES system; Receive the preset test process template returned by the MES system, and parse the test nodes, execution order and parameter configuration items in the template; Through the graphical workflow editing interface, users can call the functional modules in the standard test component library, customize the test workflow and set parameters by dragging and dropping according to logic, and generate a test workflow configuration file for the current product.

3. The production line test construction system based on MES system according to claim 1, characterized in that: The test execution module specifically includes: By reading the unique identification information label or QR code on the product, the model and work order number of the product under test can be automatically identified. Based on the recognition results, the system automatically matches and calls the corresponding test process configuration file, and parses the test instruction sequence and device interface parameters therein. According to the test process control logic, instructions are issued to each test device to perform electrical, functional or communication type test operations, and test data is collected in real time through interface protocols to perform preliminary threshold judgment or logical judgment locally.

4. The production line test construction system based on MES system according to claim 1, characterized in that: The data integration module specifically includes: After the testing process is completed, the collected test results are bound with the unique identifier of the corresponding product to generate a test data entity object; The test data entities are formatted according to a predefined data structure, including test time, test items, result status, judgment criteria, and exception information fields; Structured data is pushed to the corresponding production history database of the MES system through a standardized interface protocol, and a connection is established with the process records to achieve real-time integration of test data and full-process traceability.

5. A production line test construction system based on an MES system according to claim 1, characterized in that: The visualization interface module specifically includes: The system can acquire the execution status of the test process, the progress of test nodes, and the equipment operation information in real time, and dynamically display them on the operation interface in the form of flowcharts and data panels. The collected key test results are categorized and displayed, including normal items, boundary items, and abnormal items, while also supporting historical record comparison and result filtering; It provides access to parameter adjustment and process editing, allowing authorized operators to plug, switch, or rearrange test nodes without interrupting the overall process.

6. The production line test construction system based on MES system according to claim 1, characterized in that: The permission management module specifically includes: User identity is identified based on user login information, and their corresponding role information and operation permission level are read from the permission configuration database. Access, editing, and deployment operations of test process templates are subject to permission scope verification, allowing only users who meet the permission policy to perform the corresponding operations, and critical operations are logged. When multiple users operate on the same test process template, a version locking and conflict detection mechanism is implemented to prevent concurrent modifications from causing configuration anomalies.

Images