Information-based method for nuclear power plant operator to participate in debugging isolation control

Abstract

The present application belongs to the technical field of nuclear power plant operation management, and particularly relates to an information-based method for a nuclear power plant operator to participate in debugging isolation control under a small business owner mode. The method comprises the following: debugging party and operator scope distribution; interface of the operation system and the debugging system; responsibility division summary of the debugging party and the operator in the work control process; detailed process design description and data through field; processing of ticket refund; information transmission after the implementation of isolation; information transmission after the work order starts; processing of temporary check-out and temporary check-in; work order completion; isolation removal; and completion report. The method has the beneficial effects that the operator can intervene in the debugging isolation control in the TOB stage under the small business mode, the specific information interface and data through of the operator system and the debugging party system can be realized, and through the specific control process and the data interaction field and control logic of the debugging isolation control, the debugging boundary safety control and handover quality can be ensured.

Description

Technical Field

[0001] This invention belongs to the field of nuclear power plant operation and management technology, specifically relating to an information-based method for nuclear power plant operators to participate in commissioning and isolation control under a small-owner model. Background Technology

[0002] Nuclear power plants are time-consuming and massively complex systems engineering projects, generally divided into several important stages such as design, procurement, construction and installation, commissioning, and operation. Different models exist for the procurement, construction and installation, and commissioning stages, including those involving "major owners" and "minor owners."

[0003] The "large owner" model involves the owner company being responsible for project management, equipment procurement, and unit commissioning, while outsourcing only the engineering design and construction. The "small owner" model involves the owner company signing an EPC (Engineering, Procurement, and Construction) contract with a specialized nuclear power engineering company. The engineering company is responsible for the entire project's design, procurement, construction, and commissioning, and the project is then handed over to the owner company for operation after completion. Currently, domestic nuclear power projects primarily use the "small owner" model. Under this model, commissioning is handled by the nuclear power engineering company, and once the subsystems are commissioned, the project can be transferred to the operator for production and operation.

[0004] Generally, the small-owner model involves a process of system and equipment handover from the commissioning party to the operator: Installation Completion Report Handover (EESR), Isolation Handover (TOB), Maintenance Handover (TOM), and Temporary Operation Handover (TOTO), completing the process from installation and commissioning to trial operation. EESR handover is the stage where the installer hands over to the commissioning party, while TOB / TOM / TOTO handover is the stage where the commissioning party hands over to the operator. The equipment boundary between commissioning and operation is called the TOB / TOTO boundary. Generally, the commissioning party is responsible for the work related to the equipment within the boundary, while the operator is responsible for the work related to the equipment above the boundary. In reality, due to the continuous commissioning work, the TOB / TOTO boundary is constantly changing, and the scope of equipment each party is responsible for also changes, thus impacting the commissioning handover process. Moreover, under the current small-owner model, the operator is often not sensitive to changes in the TOB / TOTO boundary. Sometimes, without understanding the situation, a large number of devices are handed over at a single point in time, creating significant receiving pressure for the operator. Moreover, since the commissioning parties are often not from the same company, and similarly, the information management systems they use are often not the same, their data cannot be connected. Therefore, the changes in the TOB / TOTO boundary and the progress of commissioning are hindered by the lack of information exchange and synchronization. Currently, some power plants use paper-based work tickets for communication, which is inefficient and prone to human error.

[0005] Therefore, an information-based method and model are needed to facilitate communication between the commissioning and operation parties through a production information management system, enabling the operation party to easily and readily understand the commissioning progress. Since TOB handover is one of the earlier stages, the owner's involvement in isolation boundary management during the TOB phase allows for earlier involvement in commissioning, understanding of commissioning progress and equipment status. Furthermore, the TOB phase provides the necessary equipment isolation and work permit management capabilities, facilitating information-based management. Summary of the Invention

[0006] The purpose of this invention is to provide an information-based method for nuclear power plant operators to participate in commissioning isolation control, thereby enabling standardized business data flow between the operator's production information system and the commissioning information system, ensuring information exchange and synchronization, improving safety, and reducing the risk of human error.

[0007] The technical solution of this invention is as follows: An information-based method for nuclear power plant operators to participate in commissioning isolation control, comprising the following:

[0008] Step 1: Scope allocation between the debugging and operation teams;

[0009] Step 2: Interface between the operating system and the debugging system;

[0010] Step 3: Overview of the division of responsibilities between the commissioning and operation parties in the work control process;

[0011] Step 4: Detailed process design description and data integration fields;

[0012] Step 5: Handling ticket refunds;

[0013] Step 6: Implement information transmission after isolation;

[0014] Step 7: Information transmission after the work order is started;

[0015] Step 8: Handling temporary check-out and temporary check-in;

[0016] Step 9: Work order completed;

[0017] Step 10: Release from quarantine;

[0018] Step 11: Completion Report.

[0019] Step 1 involves the business party issuing commissioning work tickets for equipment outside the TOB boundary using the operator's production information system, the business party issuing commissioning work tickets for equipment on the TOB boundary using the operator's production information system, and the commissioning party issuing commissioning work tickets for equipment inside the TOB boundary using the commissioning party's production information system.

[0020] The interface mentioned in step 2 includes:

[0021] SSCs data interface: The operator's information system queries the SSCs data that has taken effect in the commissioning party's information system to ensure that the SSCs data of both parties are consistent during the commissioning period;

[0022] Document data interface: The operator's information system can query the debugging files that have taken effect in the debugging system;

[0023] Work order preparation data interface: All debugging work orders are applied for and prepared in the debugging party's information system. Debugging work orders under the operation's jurisdiction are transmitted to the operation party's information system through the interface to automatically generate corresponding work orders.

[0024] Isolation and Permission Data Interface: The commissioning party's information system obtains isolation and start-up / completion permit information from the operator's information system, which is used by the commissioning party to verify isolation boundary conflicts and advance the work order status of the commissioning party's system, etc.

[0025] Start-up and completion business data interface: The commissioning party's information system obtains the start-up and completion permit information of relevant work orders from the operator's information system, and directly advances the status of the commissioning work orders under the operation and management in the commissioning party's information system;

[0026] Completion report data interface: The completion report of the commissioning work order is filled in the commissioning party's information system and synchronized to the operator's information system to close the corresponding work order automatically generated in the operator's system.

[0027] Step 3 involves the division of jurisdiction for debugging work. Debugging work involving the TOB boundary is the responsibility of the operator, while other debugging work is the responsibility of the debugging party. The entire debugging process for the debugging party is completed in the debugging party's information system. If the operator is responsible for debugging work, the division of responsibilities for the debugging work control and management process and the information systems used are as follows:

[0028] Debugging work application: The debugging party fills in the debugging work application in the debugging party information system, including debugging tests, debugging and troubleshooting, etc.

[0029] Work order preparation: The commissioning party completes the work package preparation and approval in the commissioning party's information system;

[0030] Planning and Scheduling: The commissioning party plans and schedules the approved work orders in the commissioning party's information system;

[0031] Work order marking: The debugging party marks the debugging work orders that the debugging plan will confirm and that are the responsibility of the operation party in the debugging party information system. The marked work orders are synchronized to the operation party information system to generate the corresponding work orders.

[0032] Isolation preparation and approval: Isolation measures required for the operator to complete the debugging work in the operator's information system;

[0033] Start and completion permits: The process for controlling work tickets such as start and completion permits for commissioning work completed by the operator in the operator's information system;

[0034] Completion Report: The commissioning party fills out the completion report in the commissioning party information system.

[0035] Step 4 involves the commissioning system preparing and scheduling work orders, marking the operation ticket, and automatically or manually synchronizing the work order to the operations system. When the work order is first pushed from the commissioning system to the operations system, a work order and a 01 work order task are directly generated in the operations system. The work order task status is "prepared" and the plan is "issued". The work order number on the commissioning system side is marked. At the same time, the commissioning system reads the work order number and work order task number generated by the operations system, and the commissioning system locks the modification of the work order.

[0036] Step 5 involves processing ticket refunds in the production system. The relevant refund information is sent back to the debugging system via an interface. If the production system does not process ticket refunds, the rollback function of the synchronized marked work order and the function of modifying the work package content in the debugging system are locked. After the ticket is refunded, the debugging system makes the modifications. After completion, the data can be synchronized back to the production system. At this time, the production system only updates the changed field data.

[0037] Step 6 involves the debugging system reading the isolation information after the operation system implements isolation.

[0038] Step 7 involves the debugging system reading the work permit information after the work order is started; the operation system pushes the work order task status to "working"; the debugging system reads the work order status to "working" and automatically advances the work order status in the debugging system to "pending completion".

[0039] Step 8 involves the temporary check-out and temporary check-in of the work order corresponding to the marked work order. These processes are all performed in the production system, and the temporary check-out / check-in status and the reason for the temporary check-out are promptly transmitted from the production system to the debugging system through the isolation and permission data interface.

[0040] Step 9 involves the debugging system reading the application completion and permission completion information after the work order in the operation system is completed; when the work order task status in the operation system reaches "completed" and the debugging system reads the work order status as "completed", the work order status on the debugging system side is automatically advanced to "completed".

[0041] Step 10 involves the operation system unblocking the isolation, debugging and reading the isolation status, and the corresponding isolation device's tagging status becoming invalid.

[0042] Step 11 involves the system automatically or via a scheduled task pushing the completion report to the production system's completion report module after the debugging system completion report is approved, and the corresponding work order task status in the production system is advanced to "completed".

[0043] The beneficial effects of this invention are as follows: This invention enables operators to intervene in debugging and isolation control during the TOB stage under small business models, and enables specific information interfaces and data connectivity between the operator's system and the debugging system. Moreover, through the specific control process, data interaction fields, and control logic of debugging isolation control in this invention, the security management of debugging boundaries and the quality of handover can be guaranteed. Attached Figure Description

[0044] Figure 1 Diagram illustrating the boundary control division for debugging;

[0045] Figure 2 This is a diagram illustrating the flow of business data.

[0046] Figure 3 Diagram illustrating the division of control areas for operational management and debugging work;

[0047] Figure 4 This is a schematic diagram of the interface between work orders and work tickets. Detailed Implementation

[0048] The present invention will be further described in detail below with reference to the accompanying drawings and specific embodiments.

[0049] This invention analyzes the business needs of nuclear power plant operators to understand commissioning progress, clarify TOB boundaries, and control commissioning quality. It summarizes the business processes of the nuclear power plant's production information system intervening in the commissioning information system, proposes current methods for operators to intervene in TOB boundary management during nuclear power plant commissioning, and also proposes methods that can both meet the normal operation of commissioning operations and enable operators to deeply intervene in TOB boundary management. It achieves standardized business data connectivity between the operator's production information system (hereinafter referred to as the production system) and the commissioning system's commissioning information system (hereinafter referred to as the commissioning system), derives a method for managing isolation boundaries between the production system and the commissioning system during commissioning, and utilizes information technology to ensure information exchange and synchronization, improve safety, and reduce the risk of human error.

[0050] This invention establishes a system that satisfies both the debugging and operation parties' needs for normal debugging and production operations, while also enabling the operation company to deeply intervene in TOB boundary management and achieve seamless integration of business processes and standardized business data between the operation party's production information system and the debugging party's debugging information system. A method for isolating and managing the boundary between the production information system and the debugging information system during the debugging period is derived.

[0051] An information-based method for nuclear power plant operators to participate in commissioning isolation control includes the following:

[0052] Step 1: Scope allocation between the debugging and operation teams

[0053] The commissioning work order for equipment outside the TOB boundary shall be issued by the business party using the operator's production information system (e.g., Figure 1 The rectangular area in the middle), and the equipment commissioning work order at the TOB boundary are also issued by the operator's production information system (such as...). Figure 1 (Different jurisdictional boundaries between regions), and for equipment within the TOB boundary, the commissioning work order shall be issued by the commissioning party using the commissioning party's production information system (e.g., Figure 1 (Middle debugging and control area).

[0054] Step 2: Interface between the operating system and the debugging system

[0055] This invention aims to implement interfaces for the following six types of data, with transmission directions as follows: Figure 2 As shown.

[0056] • SSCs data interface: The operator's information system queries the commissioning party's information system for the effective SSCs (systems, equipment, structures) data to ensure that the SSCs data of both parties are consistent during the commissioning period.

[0057] • Document Data Interface: The operator's information system can query the debugging information system for effective debugging documents, such as debugging test procedures, system flowcharts, electrical diagrams, etc.

[0058] • Work order preparation data interface: All debugging work orders are applied for and prepared in the debugging party's information system. Debugging work orders under the operation department are transmitted to the operation party's information system through the interface to automatically generate corresponding work orders.

[0059] • Isolation and Permission Data Interface: The commissioning party's information system obtains isolation and start-up / completion permit information from the operator's information system, which is used by the commissioning party to verify isolation boundary conflicts and advance the status of work orders in the commissioning party's system.

[0060] • Start-up and completion business data interface: The commissioning party's information system obtains the start-up and completion permit information of relevant work orders from the operator's information system, and directly advances the status of the commissioning work orders under the operation management in the commissioning party's information system.

[0061] • Completion report data interface: The completion report of the commissioning work order is filled in in the commissioning party's information system and synchronized to the operator's information system to close the corresponding work order automatically generated in the operator's system.

[0062] Step 3: Overview of the division of responsibilities between the commissioning and operation parties in the work control process

[0063] Regarding the division of jurisdiction for commissioning work, commissioning work involving the TOB boundary (where the commissioning work object is TOB boundary equipment or requires a change to the TOB boundary) is the responsibility of the operator, while other commissioning work is the responsibility of the commissioning party. The entire process of commissioning work undertaken by the commissioning party is completed in the commissioning party's information system. If the commissioning work is undertaken by the operator, the division of responsibilities for its commissioning work control and management process and the information systems used are as follows:

[0064] Debugging work application: The debugging party fills in the debugging work application in the debugging party information system, including debugging tests, debugging and troubleshooting, etc.

[0065] Work order preparation (work package): The commissioning party completes the preparation and approval of the work package in the commissioning party's information system;

[0066] Planning and Scheduling: The commissioning party plans and schedules the approved work orders in the commissioning party's information system;

[0067] Work order marking: The debugging party marks the debugging work orders that the debugging plan will confirm and that are the responsibility of the operation party in the debugging party information system. The marked work orders are synchronized to the operation party information system to generate the corresponding work orders.

[0068] Isolation preparation and approval: Isolation measures required for the operator to complete the debugging work in the operator's information system;

[0069] Start and completion permits: The process for controlling work tickets such as start and completion permits for commissioning work completed by the operator in the operator's information system;

[0070] Completion Report: The commissioning party fills out the completion report in the commissioning party information system.

[0071] Step 4: Detailed process design description and data integration fields

[0072] The debugging system completes work order preparation and scheduling, marks the operation ticket issuance, and automatically or manually synchronizes it to the operations system. When a work order is first pushed from the debugging system to the operations system, a work order and a work order task (01) are directly generated in the operations system. The work order task status is "Prepared Completed," and the plan issuance is "Issued," marking the work order number on the debugging system side. Simultaneously, the debugging system reads the work order number and work order task number generated by the operations system, and the debugging system locks the modification of this work order. The field table for pushing from the debugging system to the operations system is shown in Table 1, and the detailed process is as follows... Figure 4 .

[0073] Table 1

[0074]

[0075]

[0076]

[0077]

[0078] Step 5: Handling ticket refunds

[0079] Refunds can be processed in the production system, and relevant refund information (including refund reason, refund message, refund recipient, refund time, etc.) is sent back to the debugging system via an interface. To ensure data consistency between the two systems, the refund function and the function to modify work package content of synchronized work orders are locked in the debugging system when a refund has not been processed in the production system. After a refund is processed, modifications are made in the debugging system, and the data can be synchronized back to the production system. At this time, the production system only updates the changed field data. Relevant refund information (including refund reason, refund message, refund recipient, refund time, etc.) is sent back to the debugging system. The fields are shown in Table 2.

[0080] Table 2

[0081] 1 Reason for rollback Reason for ticket refund 2 Back to comment Refund message 3 rollback person Person in charge 4 rollback time Processing time

[0082] Step 6: Implementing Information Transmission After Isolation

[0083] After the operation system implements isolation, the debugging system reads the isolation information (isolation code, isolation name, isolation status, isolation tagging / removal instruction information, isolation approval information, etc.), as shown in Table 3, which includes all currently isolated tagged device information.

[0084] Table 3

[0085]

[0086] Step 7: Information transmission after work order commencement

[0087] After a work order is initiated, the debugging system reads the work order permission information (work order permission status, permitter, permission time, etc.); the operation system pushes the work order task status to "working", the debugging system reads the work order status to "working", and automatically advances the work order status in the debugging system to "pending completion". See Table 4.

[0088] Table 4

[0089] 1. Construction permit status Construction permit status 2. Licensor Licensor 3. License period License period

[0090] Step 8: Processing temporary check-out and temporary check-in

[0091] For temporary checkouts and check-ins of work tickets corresponding to marked work orders, both are performed in the production system. The temporary checkout / check-in status and the reason for the temporary checkout are promptly transmitted from the production system to the debugging system through the isolation and permission data interface, as shown in Table 5.

[0092] Table 5

[0093] 1 Temporary check-out status Temporary check-out status 2 Reason for temporary check-out Reason for temporary check-out

[0094] Step 9: Work order completed

[0095] After a work order is completed in the operations system, the debugging system reads the application completion and permission completion information (worker who applied for completion, worker who was granted completion, completion status, etc.); when the work order task status in the operations system reaches "completed" and the debugging system reads the work order status as "completed", it automatically advances the work order status on the debugging system side to "completed". See Table 6.

[0096] Table 6

[0097] 1 After applying for workers After applying for workers 2 Permitted workers Permitted workers 3 Completed status Completed status

[0098] Step 10: Release from quarantine

[0099] After the operating system is unisolated, the isolation status is read during debugging, and the corresponding isolated device tag status becomes invalid. See Table 3.

[0100] Step 11: Completion Report

[0101] After the commissioning system completion report is approved, the system automatically or by a scheduled task pushes the completion report to the production system completion report module, and the corresponding work order task status in the production system is advanced to "completed".

[0102] Table 7

[0103]

Claims

1. An information-based method for nuclear power plant operators to participate in commissioning isolation control, characterized in that, Including the following: Step 1: Scope allocation between the debugging and operation teams; Step 1 is that the commissioning work order for equipment outside the TOB boundary is issued by the business party using the operator's production information system, the commissioning work order for equipment on the TOB boundary is also issued by the operator's production information system, and the commissioning work order for equipment inside the TOB boundary is issued by the commissioning party using the commissioning party's production information system. Step 2: Interface between the operating system and the debugging system; The interface mentioned in step 2 includes: SSCs data interface: The operator's information system queries the SSCs data that has taken effect in the commissioning party's information system to ensure that the SSCs data of both parties are consistent during the commissioning period; Document data interface: The operator's information system can query the debugging files that have taken effect in the debugging system; Work order preparation data interface: All debugging work orders are applied for and prepared in the debugging party's information system. Debugging work orders under the operation's jurisdiction are transmitted to the operation party's information system through the interface to automatically generate corresponding work orders. Isolation and Permission Data Interface: The commissioning party's information system obtains isolation and start-up / completion permit information from the operator's information system, which is used by the commissioning party to verify isolation boundary conflicts and advance the work order status of the commissioning party's system; Start-up and completion business data interface: The commissioning party's information system obtains the start-up and completion permit information of relevant work orders from the operator's information system, and directly advances the status of the commissioning work orders under the operation and management in the commissioning party's information system; Completion report data interface: The completion report of the commissioning work order is filled in the commissioning party's information system and synchronized to the operator's information system to close the corresponding work order automatically generated in the operator's system; Step 3: Overview of the division of responsibilities between the commissioning and operation parties in the work control process; Step 3 involves the division of jurisdiction for debugging work. Debugging work involving the TOB boundary is the responsibility of the operator, while other debugging work is the responsibility of the debugging party. The entire debugging process for the debugging party is completed in the debugging party's information system. If the operator is responsible for debugging work, the division of responsibilities for the debugging work control and management process and the information systems used are as follows: Debugging work application: The debugging party fills in the debugging work application in the debugging party information system, including debugging tests and debugging troubleshooting; Work order preparation: The commissioning party completes the work package preparation and approval in the commissioning party's information system; Planning and Scheduling: The commissioning party plans and schedules the approved work orders in the commissioning party's information system; Work order marking: The debugging party marks the debugging work orders that the debugging plan will confirm and that are the responsibility of the operation party in the debugging party information system. The marked work orders are synchronized to the operation party information system to generate the corresponding work orders. Isolation preparation and approval: Isolation measures required for the operator to complete the debugging work in the operator's information system; Start and completion permits: The process for controlling work tickets such as start and completion permits for commissioning work completed by the operator in the operator's information system; Completion Report: The commissioning party completes the completion report in the commissioning party's information system; Step 4: Detailed process design description and data integration fields; Step 5: Handling ticket refunds; Step 6: Implement information transmission after isolation; Step 7: Information transmission after the work order is started; Step 8: Handling temporary check-out and temporary check-in; Step 9: Work order completed; Step 10: Release from quarantine; Step 11: Completion Report.

2. The information-based method for nuclear power plant operators to participate in commissioning isolation control as described in claim 1, characterized in that: Step 4 involves the debugging information system completing work order preparation and scheduling, marking the operation ticket, and automatically or manually synchronizing it to the operation system. When the work order is first pushed from the debugging system to the operation system, a work order and a 01 work order task are directly generated in the operation system. The work order task status is "completed preparation" and the plan is "issued". The work order number on the debugging system side is marked. Simultaneously, the debugging system reads the work order number and work order task number generated by the operations system, and the debugging system locks the modification of the work order.

3. The information-based method for nuclear power plant operators to participate in commissioning isolation control as described in claim 1, characterized in that: Step 5 involves processing ticket refunds in the production system. The relevant refund information is sent back to the debugging system via an interface. If the production system does not process ticket refunds, the rollback function of the synchronized marked work order and the function of modifying the work package content in the debugging system are locked. After the ticket is refunded, the debugging system makes the modifications. After completion, the data can be synchronized back to the production system. At this time, the production system only updates the changed field data.

4. The information-based method for nuclear power plant operators to participate in commissioning isolation control as described in claim 1, characterized in that: Step 6 involves the debugging system reading the isolation information after the operation system implements isolation.

5. An information-based method for nuclear power plant operators to participate in commissioning isolation control as described in claim 1, characterized in that: Step 7 is the process where the debugging system reads the work permit information after the work order is started. The operation system pushes the work order task status to "Working", the debugging system reads the work order status and puts it into "Working", and automatically advances the work order status in the debugging system to "Pending Completion".

6. The information-based method for nuclear power plant operators to participate in commissioning isolation control as described in claim 1, characterized in that: Step 8 involves the temporary check-out and temporary check-in of the work order corresponding to the marked work order. These processes are all performed in the production system, and the temporary check-out / check-in status and the reason for the temporary check-out are promptly transmitted from the production system to the debugging system through the isolation and permission data interface.

7. An information-based method for nuclear power plant operators to participate in commissioning isolation control as described in claim 1, characterized in that: Step 9 involves the debugging system reading the application completion and permit completion information after the work order in the operation system is completed. When the work order status in the operation system reaches "completed" and the work order status in the debugging system reaches "completed", the work order status on the debugging system side will automatically be pushed to "completed".

8. An information-based method for nuclear power plant operators to participate in commissioning isolation control as described in claim 1, characterized in that: Step 10 involves the operation system unblocking the isolation, debugging and reading the isolation status, and the corresponding isolation device's tagging status becoming invalid.

9. An information-based method for nuclear power plant operators to participate in commissioning isolation control as described in claim 1, characterized in that: Step 11 involves the system automatically or via a scheduled task pushing the completion report to the production system's completion report module after the debugging system completion report is approved, and the corresponding work order task status in the production system is advanced to "completed".

Images