A quality plan control point forced verification method and system integrated in a work order execution process
By binding quality control points to the work order execution process and implementing process interruptions, the problem of the disconnect between work order execution and quality plan verification in the nuclear power industry has been solved, realizing the mandatory execution and traceability of the quality plan, and improving nuclear safety and management efficiency.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- NAT NUCLEAR INFORMATION TECH CO LTD
- Filing Date
- 2026-04-02
- Publication Date
- 2026-07-24
AI Technical Summary
In the nuclear power industry, the traditional work order execution and quality plan verification processes are disconnected, relying on human factors, which leads to omissions of quality control points and difficulties in traceability, posing significant safety hazards.
By binding quality control points into the work order execution process, process blocking and status verification are achieved. Combined with the work order management module, quality plan management module and data interaction bus, quality plan verification is enforced and recorded.
It completely eliminated omissions in quality planning, improved the level of nuclear safety quality assurance, reduced the risk of human error, achieved digital integration and traceability of quality activities and production activities, and improved management efficiency.
Smart Images
Figure CN122453232A_ABST
Abstract
Description
Technical Field
[0001] This application belongs to the field of nuclear power production management information technology, specifically relating to a method and system for mandatory verification of quality plan control points integrated into the work order execution process. Background Technology
[0002] In the nuclear power industry, quality plans are crucial documents ensuring that maintenance, testing, and modification activities comply with regulations and standards. Quality plans establish important quality control points, primarily including "witness points" and "stop-work inspection points." In traditional workflows, work order execution and quality plan verification are two relatively independent processes, typically relying on staff communication and paper document transfer. This approach has the following significant drawbacks: Risk of process disconnect: Due to negligence or poor communication, the work order executor may fail to notify the quality personnel to be present and witness before the critical process steps, resulting in "skipping points" and rendering the quality plan ineffective, which may lead to significant quality and safety hazards.
[0003] Dependence on human factors: The entire process relies heavily on the sense of responsibility and experience of the personnel, lacks system-level hard constraints, and has poor management controllability.
[0004] Traceability difficulties: Once a quality problem occurs, it is difficult to quickly and accurately trace whether each quality control point was strictly followed during the execution of the work order, resulting in low efficiency in auditing and investigation.
[0005] Therefore, there is an urgent need in this field for a solution that can deeply integrate quality planning control points with work order execution processes and, through technical means, enforce their execution and recording. Summary of the Invention
[0006] The purpose of this application is to overcome the shortcomings of existing technologies, such as the risk of process disconnect, reliance on human factors, and difficulty in traceability.
[0007] To achieve the above objectives, this application proposes a method for mandatory verification of quality planning control points integrated into the work order execution process, including: Step 1: When a work order reaches the process step bound to a quality control point, pause the subsequent operations of that work order at that process step; Step 2: Periodically check the status of the bound quality control points and verify their current status. If the status of the quality control point in the verification result is "signed", then remove the process block and allow the work order to proceed to the next process step. If the status of the quality control point in the verification result is "not signed" or "awaiting witnessing", then maintain the blocked status.
[0008] As an improvement to the above method, it also includes: During the work order creation or planning phase, the work order is associated with the corresponding quality plan, and at least one quality control point in the quality plan is bound to one or more process steps of the work order.
[0009] As an improvement to the above method, it also includes: During the execution of the work order, record the verification time, verification results, and corresponding quality plan number of the quality control points.
[0010] This application also provides a quality plan control point mandatory verification system integrated into the work order execution process, implemented based on the above method, the system comprising: The work order management module is used to create, dispatch, and execute work orders. When creating a work order, quality control points are bound to process steps, and the process execution is determined based on the status of the quality control points during work order execution. The quality plan management module is used to create and manage quality plans, enable electronic signatures for quality control points, and store the real-time status of each quality control point; and A data interaction bus is used to enable data communication between the work order management module and the quality plan management module.
[0011] As an improvement to the above system, the work order management module includes: Binding units are used to establish the association between work order process steps and quality plan control points; The execution control unit controls the work order execution process, detects whether the current process step is bound to a quality control point, and triggers process blocking or continuation of the next process step based on the status of the quality control point; logs are recorded during execution; and... The interface call unit is used to initiate status queries to the quality planning management module.
[0012] As an improvement to the above system, the implementation process of the execution control unit includes: When a work order is executed to a process step, the database table is queried to determine whether the current process step is bound to a quality control point. If a binding exists, the work order status will be set to blocked, and the "Next" or "Submit" buttons will be disabled in the front-end interface, with only the "View Verification Status" or "Refresh" functions enabled. Record the blocking time and blocking point information to the log table.
[0013] Compared with existing technologies, the advantages of this application are: 1. Mandatory Quality Assurance: By using "process interruption" technology, the system mandates the completion of quality plan verification, completely eliminating "skipping points" caused by human negligence and greatly improving the quality assurance level of nuclear safety work.
[0014] 2. Deep integration of processes: The originally independent quality verification process is seamlessly embedded into the main line of work order execution, realizing the deep digital integration of quality activities and production activities and eliminating process silos.
[0015] 3. Reduce human error: It reduces staff's reliance on paper documents and memory, and effectively reduces the risk of human error through system guidance and mandatory constraints.
[0016] 4. Enhanced traceability: All quality control verification processes are automatically and accurately recorded in the work order execution log, forming a complete and tamper-proof electronic record, which greatly facilitates quality auditing and root cause analysis.
[0017] 5. Improve management efficiency: Real-time and transparent monitoring of quality control status is achieved, allowing quality personnel and planners to clearly understand the status of work order execution at quality control points, which facilitates management and decision-making. Attached Figure Description
[0018] Figure 1 The diagram shows the flowchart of the mandatory verification method for quality plan control points integrated into the work order execution process. Figure 2 The diagram shows the structure of the quality plan control point mandatory verification system integrated into the work order execution process. Detailed Implementation
[0019] The technical solution of this application will be described in detail below with reference to the accompanying drawings.
[0020] This application provides a method and system for mandatory verification of quality plan control points integrated into the work order execution process, which can eliminate the risk of missing quality plan control points at the system level.
[0021] Example 1 like Figure 1 As shown, this application provides a method for mandatory verification of quality plan control points integrated into the work order execution process, which includes the following steps: S1: Association and Binding Steps: During the work order creation or planning stage, the work order is electronically associated with the corresponding quality plan, and at least one quality control point in the quality plan is bound to one or more process steps of the work order. S2: Process Interruption Step: When a user executes a process step that has been bound to a quality control point through the work order execution interface, the verification process is triggered, and the subsequent operations of the work order in the process step are forcibly suspended. S3: Status verification steps: Periodically query the status of quality control points and verify the current status of the bound quality control points; S4: Conditional Release Step: If the status of the quality control point in the verification result is "signed", then the process blockade is lifted, and the work order execution process is allowed to proceed to the next process step; If the status of the quality control point in the verification results is "unsigned" or "pending witnessing", the blocking status will remain unchanged, and the user will be prompted to "wait for the quality plan control point to close". S5: Record generation steps: Automatically record the verification time, verification result, and corresponding quality plan number of the quality control point in the work order execution log.
[0022] Example 2 like Figure 2 As shown, this application also provides a quality plan control point mandatory verification system integrated into the work order execution process, implemented based on the above method, which includes: Work Order Management Module: Used for creating, dispatching, and executing work orders. When creating a work order, quality control points are bound to process steps. During work order execution, the process execution is determined based on the status of the quality control points. It includes a binding unit, an execution control unit, and an interface call unit. Specifically: Binding Unit: Used to establish the association between work order processes and quality plan control points.
[0023] Execution control unit: Used to control the execution process of work orders, detect whether the current process step is bound to a quality control point, and trigger the process to block or continue to execute the next process step according to the status of the quality control point; logs are recorded during the execution process.
[0024] Interface call unit: Used to initiate status queries to the quality plan management module during the verification step.
[0025] Quality Plan Management Module: Used to create and manage quality plans, electronically sign quality control points, and store the real-time status of each quality control point.
[0026] Data interaction bus: Used to enable data communication between the work order management module and the quality planning management module.
[0027] 1. The implementation of the work order management module includes: (1) The implementation of the binding unit includes: Data model: Create a related table `work_order_qp_binding` in the database, with the following fields: binding_id: A unique identifier for the binding; work_order_id: Work order ID; work_order_step: Work order process number; qp_id: Quality plan ID; control_point_id: Quality control point ID; binding_time: Binding time; created_by: The person to whom the operation is bound.
[0028] Binding method: During the work order creation or planning stage, the system provides a visual interface that allows users to associate work order processes with quality plan control points by dragging or dropping. The system automatically writes the data into the above-mentioned data table.
[0029] (2) The implementation of the execution control unit includes: State machine mechanism: Each work order maintains a state machine during execution, with states including: not started, in progress, blocked, and completed.
[0030] Blocking trigger logic: When a work order is executed to a certain process step, the system queries the work_order_qp_binding table to determine whether the current process step is bound to a quality control point. If a binding exists, the system will set the work order status to blocked and disable the "Next" or "Submit" buttons on the front-end interface, only enabling the "View Verification Status" or "Refresh" functions; At the same time, the system records the blocking time and blocking point information to the block_log table.
[0031] The implementation of the record generation step in the execution control unit includes: Log recording points: Logs are automatically generated at the following points: When a work order is linked to a quality plan control point; When work order execution triggers blocking; Each time the control point status is queried from the quality planning management module; When the blockade is lifted and the work order continues to be executed.
[0032] Log content includes: operation time, operator, work order number, process number, quality plan number, control point number, verification result, operation type (binding / blocking / querying / releasing), etc.
[0033] Storage method: Write to the execution_log table and simultaneously write to the blockchain or tamper-proof log system (optional) to ensure non-repudiation.
[0034] (3) The implementation of the interface calling unit includes: Interface Definition: The work order management module calls the query interface provided by the quality plan management module through the data interaction bus. API path: / api / qp / control-point / status Request method: GET Request parameters: qp_id, control_point_id The returned result is the `status` field, with values of "SIGNED" (signed), "PENDING" (pending witnessing), or "UNSIGNED" (not signed). Invocation mechanism: A synchronous call method is used to ensure that the work order process will not continue until a clear verification result is obtained; Set up a timeout retry mechanism (e.g., 3 times, 2-second interval) to prevent misjudgment due to network jitter; When the call fails, the system remains blocked and displays the message "Verification service error, please contact the administrator".
[0035] 2. The implementation of the quality planning management module includes: Electronic signature: Quality personnel can electronically sign control points through a dedicated interface or mobile terminal. The signature information includes the signer, signature time, signature certificate fingerprint, etc.
[0036] Status change: After signing is completed, the system updates the status field in the control_point table to "SIGNED" and records the signing log.
[0037] Status synchronization: If a message middleware is used, the quality planning management module sends an event message after the status changes, and the work order management module can subscribe to the message to achieve real-time status updates.
[0038] This application adopts a front-end / back-end separated B / S architecture, deployed within the nuclear power plant's internal LAN or an isolated industrial internet environment. The overall architecture includes: Front-end interface: Work order execution interface and quality plan management interface, implemented using Web technology and supported by mainstream browsers; Backend services: Work order management service and quality plan management service, which are deployed on independent or clustered application servers respectively; Database layer: Relational databases (such as Oracle and MySQL) are used to store work order data, quality plan data, binding relationships, and execution logs; Data interaction bus: Enables asynchronous or synchronous communication between modules based on RESTful APIs or message middleware (such as Kafka, RabbitMQ).
[0039] Example 3: The method described in this application is illustrated using the execution process of a steam turbine maintenance work order at a nuclear power plant as an example: During the work order creation phase, the planner binds the "Steam Turbine Low-Pressure Cylinder Opening Inspection" process to "Witness Point W-01" in the quality plan "QP-2024-001" in the work order management interface.
[0040] On-site personnel log in to the work order execution interface via mobile terminal, complete the preliminary procedures, and then proceed to the "low-pressure cylinder opening inspection of the steam turbine" procedure.
[0041] The system detected that the process was already bound to a quality control point, and automatically set the work order status to "blocked". The interface displayed the message "This process requires the witness of quality personnel. Please wait for the control point to sign."
[0042] If the operator is unable to continue, the system will automatically call the quality planning management module interface every 30 seconds to query the status of the control points.
[0043] After the quality personnel arrive on-site to witness the event, they complete the electronic signature via mobile device, and the system updates the control point status to "signed".
[0044] When the work order management module retrieves the "signed" status on the next query, it automatically removes the block, restores the "Next" button to the interface, and prompts "Control point has been signed, you can continue execution".
[0045] The system records information such as the verification time, verification result, and operator in the log for subsequent auditing.
[0046] This application may also provide a computer device, including: at least one processor, memory, at least one network interface, and a user interface. The various components in this device are coupled together via a bus system. It is understood that the bus system is used to implement communication between these components. In addition to a data bus, the bus system also includes a power bus, a control bus, and a status signal bus.
[0047] The user interface can include a display, keyboard, or clicking device. Examples include a mouse, trackball, touchpad, or touchscreen.
[0048] It is understood that the memory in the embodiments disclosed in this application may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory may be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDRSDRAM), Enhanced Synchronous DRAM (ESDRAM), Synchlink DRAM (SLDRAM), and Direct Rambus RAM (DRRAM). The memories described herein are intended to include, but are not limited to, these and any other suitable types of memory.
[0049] In some implementations, the memory stores elements such as executable modules or data structures, or subsets thereof, or extended sets thereof: operating systems and applications.
[0050] The operating system includes various system programs, such as the framework layer, core library layer, and driver layer, used to implement various basic business functions and handle hardware-based tasks. The application programs include various applications, such as media players and browsers, used to implement various application functions. Programs implementing the methods of the embodiments of this disclosure can be included in the application programs.
[0051] In the above embodiments, the processor can also invoke programs or instructions stored in memory, specifically programs or instructions stored in an application program, for the following purposes: Follow the steps described above.
[0052] The above methods can be applied to or implemented by a processor. The processor may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above methods can be completed by integrated logic circuits in the processor's hardware or by software instructions. The processor can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic diagrams disclosed above. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the disclosed methods can be directly implemented by a hardware decoding processor, or by a combination of hardware and software modules in the decoding processor. The software modules can reside in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. This storage medium is located in memory; the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above methods.
[0053] It is understood that the embodiments described in this application can be implemented using hardware, software, firmware, middleware, microcode, or a combination thereof. For hardware implementation, the processing unit can be implemented in one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), general-purpose processors, controllers, microcontrollers, microprocessors, other electronic units for performing the functions described in this application, or combinations thereof.
[0054] For software implementation, the technology of this application can be implemented by executing the functional modules (e.g., procedures, functions, etc.) of this application. The software code can be stored in memory and executed by a processor. The memory can be implemented in the processor or outside the processor.
[0055] This application may also provide a non-volatile storage medium for storing a computer program. When the computer program is executed by a processor, it can implement the steps in the above method embodiments.
[0056] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of this application and are not intended to limit it. Although this application has been described in detail with reference to the embodiments, those skilled in the art should understand that modifications or equivalent substitutions to the technical solutions of this application do not depart from the spirit and scope of the technical solutions of this application, and should all be covered within the scope of the claims of this application.
Claims
1. A method for mandatory verification of quality planning control points integrated into the work order execution process, comprising: Step 1: When a work order reaches the process step bound to a quality control point, pause the subsequent operations of that work order at that process step; Step 2: Periodically check the status of the bound quality control points and verify their current status; if the status of the quality control point in the verification result is "signed", then remove the process block and allow the work order to proceed to the next process step; if the status of the quality control point in the verification result is "not signed" or "awaiting witnessing", then maintain the blocked status.
2. The method for mandatory verification of quality planning control points integrated into the work order execution process according to claim 1, characterized in that, Also includes: During the work order creation or planning phase, the work order is associated with the corresponding quality plan, and at least one quality control point in the quality plan is bound to one or more process steps of the work order.
3. The method for mandatory verification of quality plan control points integrated into the work order execution process according to claim 1, characterized in that, Also includes: During the execution of the work order, record the verification time, verification results, and corresponding quality plan number of the quality control points.
4. A quality planning control point mandatory verification system integrated into the work order execution process, implemented based on the method described in any one of claims 1-3, characterized in that, The system includes: The work order management module is used to create, dispatch, and execute work orders. When creating a work order, quality control points are bound to process steps, and the process execution is determined based on the status of the quality control points during work order execution. The quality plan management module is used to create and manage quality plans, enable electronic signatures for quality control points, and store the real-time status of each quality control point; and A data interaction bus is used to enable data communication between the work order management module and the quality plan management module.
5. The quality planning control point mandatory verification system integrated into the work order execution process according to claim 4, characterized in that, The work order management module includes: Binding units are used to establish the association between work order process steps and quality plan control points; The execution control unit controls the work order execution process, detects whether the current process step is bound to a quality control point, and triggers process blocking or continuation of the next process step based on the status of the quality control point; logs are recorded during execution; and... The interface call unit is used to initiate status queries to the quality planning management module.
6. The quality planning control point mandatory verification system integrated into the work order execution process according to claim 5, characterized in that, The implementation process of the execution control unit includes: When a work order is executed to a process step, the database table is queried to determine whether the current process step is bound to a quality control point. If a binding exists, the work order status will be set to blocked, and the "Next" or "Submit" buttons will be disabled in the front-end interface, with only the "View Verification Status" or "Refresh" functions enabled. Record the blocking time and blocking point information to the log table.