A cross-factory nuclear power engineering management method and device

Abstract

The application discloses a kind of nuclear power engineering management methods and devices across factory, wherein, method includes the following steps: step S1, for each nuclear power engineering deployment independent physical environment, the independent physical environment includes independent database, independent service instance and independent file storage;Step S2, deployment unified gateway as the unified access entrance of all nuclear power engineering, each nuclear power engineering is based on the gateway and carries out service request and access;Step S3, based on the gateway deployment unified management console, each nuclear power engineering is centrally managed;Step S4, based on the gateway and the management console, realize the cross factory data sharing and data reference of each nuclear power engineering.The application is under the premise of guaranteeing the independent safety of each nuclear power engineering across factory, and they are uniformly managed.

Description

Technical Field

[0001] This invention relates to the field of nuclear power engineering management technology, and in particular to a method and apparatus for managing nuclear power engineering across multiple plants. Background Technology

[0002] Existing digital management systems for nuclear power projects, when deployed across multiple sites and units, typically employ one of two extreme models: a unified central database or completely independent and decentralized systems for each nuclear power plant. Each model has its drawbacks. The unified central database model presents data security risks; if the central database is compromised, data from all sites will be leaked. It also suffers from performance bottlenecks, as the massive amounts of data in the central database lead to slow query responses. Furthermore, it introduces operational complexity, as version upgrades at one nuclear power plant can affect all sites. Conversely, the completely independent and decentralized model results in fragmented management, inconsistent standards, and difficulties in centralized operation and maintenance. Summary of the Invention

[0003] In view of this, it is necessary to provide a method and apparatus for cross-plant nuclear power engineering management to effectively solve the technical problem of balancing independent safety and unified management in cross-plant nuclear power engineering management.

[0004] This invention provides a method for managing nuclear power plant projects across multiple plants, comprising the following steps: Step S1: Deploy an independent physical environment for each nuclear power project. The independent physical environment includes an independent database, an independent service instance, and independent file storage. Step S2: Deploy a unified gateway as the unified access point for all nuclear power projects, and each nuclear power project makes service requests and accesses based on the gateway; Step S3: Deploy a unified management console based on the gateway to centrally manage each of the nuclear power projects; Step S4: Based on the gateway and the management console, realize cross-plant data sharing and data referencing for each of the nuclear power projects.

[0005] Preferably, step S1 specifically comprises: The independent database is used to store the drawing data, legend library and user permission information of the corresponding nuclear power project. The independent service instance is used to process the business logic of the corresponding nuclear power project. The independent file storage is used to store the static resources of the corresponding nuclear power project.

[0006] Preferably, step S2 specifically comprises: A unified API gateway is deployed as the unified access point for all nuclear power projects. Each nuclear power project sends a request based on the gateway, and the gateway routes the request to the corresponding nuclear power project's independent service instance for processing according to the project identifier in the request.

[0007] Preferably, step S2 further includes: The gateway is used to authenticate user access to each of the nuclear power plants; the gateway is used to collect access traffic statistics for each of the nuclear power plants and set corresponding rate limiting policies; the gateway is used to collect access logs for all nuclear power plants and centrally store and analyze the access logs.

[0008] Preferably, step S3 specifically comprises: Based on the management console, new nuclear power projects are registered and their environments initialized. User permissions for each nuclear power project are managed uniformly. The legend library for each nuclear power project is maintained independently. The operating indicators of each nuclear power project are centrally monitored and alarms are triggered when anomalies occur. The independent service instances of each nuclear power project are upgraded and data is automatically backed up. The logs of each nuclear power project are summarized and analyzed. Disaster recovery backups are performed in the backup systems of each nuclear power project itself and other backup systems. Regular disaster recovery drills are conducted for each nuclear power project.

[0009] Preferably, the cross-plant data sharing of each nuclear power plant in step S4 specifically involves: The central database is set up to publish new versions of data. Each nuclear power project selects the data that needs to be synchronized from the central database, subscribes to it, and synchronizes it automatically.

[0010] Preferably, the cross-plant data sharing of each nuclear power plant in step S4 further includes: After each nuclear power project subscribes to and synchronizes relevant data, only the changed data of the relevant data is synchronized; if a nuclear power project performs local customization while synchronizing specific data, the customized version will be automatically retained and a conflict will be indicated during synchronization.

[0011] Preferably, the cross-plant data referencing for each nuclear power project in step S4 specifically involves: The nuclear power project references data from other nuclear power projects through the gateway, records the codes of the referenced project and the referenced drawings in the corresponding graphic elements, and routes the data to the referenced project according to the codes of the referenced project and the referenced drawings, while maintaining the user's login status.

[0012] Preferably, step S4 further includes: A joint query interface is provided, allowing users to send data viewing requests across projects. Based on this interface, the gateway requests independent service instances of each nuclear power project in parallel to view the data, and then merges the data from each project and returns it to the user.

[0013] The present invention also provides a nuclear power plant engineering management device across plants, including a memory and a processor, wherein the memory stores a computer program, and the computer program, when executed by the processor, implements the nuclear power plant engineering management method across plants.

[0014] Compared with existing technologies, the advantages of this invention are as follows: This invention deploys an independent physical environment for each nuclear power plant project, while simultaneously deploying a unified gateway and management console. Physical isolation ensures independent and secure data for each project, preventing performance interference. A unified entry point and centralized management avoid information silos. The management console monitors all projects, and operations such as version upgrades and backup / restore can be performed in batches, significantly reducing operation and maintenance costs. Furthermore, a central legend library based on a unified gateway ensures standardization while allowing customization for each project to meet the diverse needs of different power plants. Finally, data sharing is achieved through the gateway and management console, enabling cross-project referencing and retrieval, facilitating group-level technical support and experience feedback. This invention constructs a logically unified and physically isolated architecture, achieving a balance between independent security and unified management of multi-site data, supporting large-scale project deployment at the nuclear power group level. Attached Figure Description

[0015] The accompanying drawings, which are included to provide a further understanding of the invention and form part of this application, illustrate exemplary embodiments of the invention and, together with their description, serve to explain the invention and do not constitute an undue limitation thereof. In the drawings: Figure 1 This is a flowchart of an embodiment of a cross-plant nuclear power engineering management method provided by the present invention. Detailed Implementation

[0016] Preferred embodiments of the present invention will now be described in detail with reference to the accompanying drawings, which form part of this application and are used together with the embodiments of the present invention to illustrate the principles of the present invention, but are not intended to limit the scope of the present invention.

[0017] Example 1

[0018] Please see Figure 1 The cross-plant nuclear power plant engineering management method in this embodiment specifically includes the following steps: Step S1: Deploy an independent physical environment for each nuclear power project. The independent physical environment includes an independent database, an independent service instance, and independent file storage. Step S2: Deploy a unified gateway as the unified access point for all nuclear power projects, and each nuclear power project makes service requests and accesses based on the gateway; Step S3: Deploy a unified management console based on the gateway to centrally manage each of the nuclear power projects; Step S4: Based on the gateway and the management console, realize cross-plant data sharing and data referencing for each of the nuclear power projects.

[0019] The cross-plant nuclear power engineering management method provided in this embodiment adopts a logically unified and physically isolated architecture to achieve a balance between independent security and unified management of multi-site data, supporting large-scale engineering deployment at the nuclear power group level.

[0020] Each step will be explained in detail below.

[0021] Step S1: Multi-project physically isolated deployment architecture For each nuclear power project—that is, a nuclear power base or nuclear power unit—an independent physical environment is deployed, including an independent database, an independent service instance, and independent file storage. The independent database, such as MySQL / Oracle, stores the project's drawing data, legend library, user permissions, etc. The independent service instance, such as a Spring Boot application, handles the project's business logic. The independent file storage, such as a Spring Boot application, stores static resources like SVG drawings and attachments in a separate directory.

[0022] Advantages of physical isolation: data security, an attack on a single project will not affect other projects; performance isolation, high-concurrency queries in one project will not affect the response speed of other projects; independent operation and maintenance, each project can be upgraded, restarted, and backed up independently without interference.

[0023] Step S2, Unified Access Gateway Deploy a unified API gateway, such as Nginx / Kong, as the unified entry point for all projects. The gateway routes requests to the corresponding backend service instance based on the project identifier in the request, such as the domain name prefix or the X-Project-ID in the request header.

[0024] The gateway layer specifically implements the following functions: request routing, dynamically forwarding requests based on project identifiers; unified authentication, connecting to the group's unified identity authentication system, such as ITASK, allowing users to access all authorized projects with a single login; traffic control, enabling the setting of different rate limiting policies for different projects; and log aggregation, collecting access logs from all projects for centralized storage and analysis.

[0025] Step S3: Unified Management Platform Deploy a unified management console to achieve centralized management of multiple projects, including project registration and configuration, unified user permission management, legend library synchronization, system monitoring, and version upgrade management. Project registration and configuration: When a new project goes live, project information is registered on the management platform, including project ID, name, database connection string, service address, etc., and the system automatically completes environment initialization. Unified user permission management: The management platform configures user access permissions for each project; for example, Zhang San can access QS Phase 1 and TW5 / 6, while Li Si can only access FQ. Legend library synchronization: Each project's legend library can be maintained independently or updated synchronously from the central legend library, supporting customized legends for each project, such as differences in valve symbols between different power plants. System monitoring: Centralized monitoring of service status, database load, disk space, etc., for each project, with automatic alarms in case of anomalies. Version upgrade management: Supports batch or canary upgrades of the backend services of each project; automatic data backup during the upgrade process, and one-click rollback in case of failure.

[0026] The management console is also used for unified operation and maintenance and disaster recovery for various nuclear power projects. A unified log center aggregates logs from each project to an Elasticsearch cluster via Filebeat / Logstash, supporting centralized retrieval and analysis; unified monitoring and alerting uses Prometheus + Grafana to monitor metrics such as CPU, memory, disk, and QPS for each project, and sets unified alert rules; disaster recovery backup supports cross-project backup strategies, such as storing backups from the QS base in the TW base's backup system to prevent single points of failure; and drills and switchovers are conducted regularly to quickly switch traffic to a backup environment in the event of a project failure.

[0027] Step S4: Data synchronization and sharing mechanism, inter-project navigation and referencing. For data that needs to be shared across projects, such as standard legend libraries and general specification templates, a data synchronization mechanism is provided. This mechanism includes: a publish-subscribe model, where each project can choose to subscribe to and automatically synchronize when a new version of the central legend library is released; incremental synchronization, which only synchronizes changed data to reduce network overhead; and conflict handling, where if a project has customized the shared data locally, the customized version is automatically retained and a conflict warning is displayed during synchronization. For users who need to view data across projects, such as group experts needing to view drawings from multiple sites simultaneously, a joint query interface is provided. The gateway requests services from each project in parallel, merges the results, and returns them.

[0028] Supports cross-project referencing of drawings; for example, a drawing from the QS base can reference a drawing from the TW base. Implementation: The drawing element records the referenced project ID and drawing ID. When clicking to jump, the gateway routes to the corresponding project based on the project ID, while maintaining the user's logged-in status; the user must have permissions in the target project. When referencing across projects, the system automatically checks user permissions; if permissions are insufficient, a request is prompted.

[0029] Compared with existing technologies, this embodiment has the following advantages: It achieves both data security and performance; physical isolation ensures independent and secure data for each project, with no performance interference; a unified entry point and centralized management avoid information silos. It also enables streamlined operation and maintenance, with a single management platform monitoring all projects. Version upgrades, backups, and recovery operations can be performed in batches, significantly reducing operation and maintenance costs. Furthermore, it balances standardization and personalization, with a central legend library ensuring standardized data while allowing for customization for each project to meet the diverse needs of different power plants. It facilitates cross-project collaboration, supporting cross-project referencing of drawings and cross-project expert access, providing convenience for group-level technical support and experience feedback. Finally, it ensures high availability, with independent disaster recovery backup and traffic switching mechanisms ensuring that a single project failure does not affect the overall service availability.

[0030] The following section will provide a more detailed explanation using a specific deployment scenario as an example.

[0031] Scenario 1: New project goes live The newly completed HN Nuclear Power Plant Units 3 and 4 require the addition of a new project in the digital workflow platform. The administrator logs into the unified management platform, clicks "Add Project," and fills in the project information: Project ID "HN-34," Name "HN Nuclear Power Plant Units 3 / 4," database configuration, server resources, etc. The system automatically initializes the database, deploys service instances, and creates file storage directories on the designated server, taking approximately 30 minutes. In the permission configuration interface, the administrator assigns access permissions for the project to local HN users and "read-only" permissions to group experts. The HN project is then officially launched, and users can access it through a unified portal.

[0032] Scenario 2: Cross-project access Group experts needed to compare the RCV system drawings for QS Phase II and FQ1 / 2. Experts logged into the unified portal, and the system displayed a list of accessible projects based on their permissions: QS Phase II and FQ1 / 2. Experts opened the RCV drawings in the QS Phase II project and simultaneously opened the RCV drawings for the FQ1 / 2 project in a new tab, viewing them side-by-side. The experts discovered a difference in the valve legend between the FQ and QS drawings. Clicking on the legend to view its attributes, the system recorded this difference for subsequent standardization discussions.

[0033] Scenario 3: Legend Library Synchronization and Customization The central legend library released a new version of valve legends, conforming to the latest industry standards. The unified management platform pushed update notifications to all projects. The QS base administrator selected "Synchronize Immediately," the TW base administrator selected "Delay Synchronization" due to ongoing major repairs, and the FQ base administrator selected "Synchronize but Retain Local Customized Version." The FQ base's locally customized valve legends conflicted with the new version; the system automatically marked the conflict and prompted the administrator to manually merge them. After comparing the two versions, the administrator chose to retain the local customized version and ignore the central update, or manually merge both.

[0034] Scenario 4: Disaster Recovery Drill The operations and maintenance team conducted its annual disaster recovery drill, simulating a database failure in Project TW5 / 6. The monitoring system issued an alert, and the administrator initiated a failover process, redirecting traffic to the backup database for Project TW, located in a remote data center. The failover was completed in 5 minutes, with no issues for TW users. After the drill, the system generated a report recording the failover time and data consistency check results.

[0035] Example 2

[0036] This embodiment provides a cross-plant nuclear power engineering management device, including a memory and a processor. The memory stores a computer program, and when the computer program is executed by the processor, it implements the cross-plant nuclear power engineering management method described in Embodiment 1.

[0037] The cross-plant nuclear power engineering management device provided in this embodiment is used to implement the cross-plant nuclear power engineering management method. Therefore, the cross-plant nuclear power engineering management device also possesses the technical effects of the cross-plant nuclear power engineering management method, which will not be elaborated here.

[0038] The above description is only a preferred embodiment of the present invention, but the scope of protection of the present invention 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 the present invention should be included within the scope of the present invention.

Claims

1. A method for managing nuclear power engineering across multiple plants, characterized in that, Includes the following steps: Step S1: Deploy an independent physical environment for each nuclear power project. The independent physical environment includes an independent database, an independent service instance, and independent file storage. Step S2: Deploy a unified gateway as the unified access point for all nuclear power projects, and each nuclear power project makes service requests and accesses based on the gateway; Step S3: Deploy a unified management console based on the gateway to centrally manage each of the nuclear power projects; Step S4: Based on the gateway and the management console, realize cross-plant data sharing and data referencing for each of the nuclear power projects.

2. The cross-plant nuclear power engineering management method according to claim 1, characterized in that, Step S1 specifically involves: The independent database is used to store the drawing data, legend library and user permission information of the corresponding nuclear power project. The independent service instance is used to process the business logic of the corresponding nuclear power project. The independent file storage is used to store the static resources of the corresponding nuclear power project.

3. The cross-plant nuclear power engineering management method according to claim 1, characterized in that, Step S2 specifically involves: A unified API gateway is deployed as the unified access point for all nuclear power projects. Each nuclear power project sends a request based on the gateway, and the gateway routes the request to the corresponding nuclear power project's independent service instance for processing according to the project identifier in the request.

4. The cross-plant nuclear power engineering management method according to claim 1, characterized in that, Step S2 further includes: The gateway is used to authenticate user access to each of the nuclear power plants; the gateway is used to collect access traffic statistics for each of the nuclear power plants and set corresponding rate limiting policies; the gateway is used to collect access logs for all nuclear power plants and centrally store and analyze the access logs.

5. The cross-plant nuclear power engineering management method according to claim 1, characterized in that, Step S3 specifically involves: Based on the management console, new nuclear power projects are registered and their environments initialized. User permissions for each nuclear power project are managed uniformly. The legend library for each nuclear power project is maintained independently. The operating indicators of each nuclear power project are centrally monitored and alarms are triggered when anomalies occur. The independent service instances of each nuclear power project are upgraded and data is automatically backed up. The logs of each nuclear power project are summarized and analyzed. Disaster recovery backups are performed in the backup systems of each nuclear power project itself and other backup systems. Regular disaster recovery drills are conducted for each nuclear power project.

6. The cross-plant nuclear power engineering management method according to claim 1, characterized in that, The cross-plant data sharing of each nuclear power plant project in step S4 specifically involves: The central database is set up to publish new versions of data. Each nuclear power project selects the data that needs to be synchronized from the central database, subscribes to it, and synchronizes it automatically.

7. The cross-plant nuclear power engineering management method according to claim 1, characterized in that, The cross-plant data sharing of each nuclear power plant project in step S4 also includes: After each nuclear power project subscribes to and synchronizes relevant data, only the changed data of the relevant data is synchronized; if a nuclear power project performs local customization while synchronizing specific data, the customized version will be automatically retained and a conflict will be indicated during synchronization.

8. The cross-plant nuclear power engineering management method according to claim 1, characterized in that, The cross-plant data referencing for each nuclear power project in step S4 is specifically as follows: The nuclear power project references data from other nuclear power projects through the gateway, records the codes of the referenced project and the referenced drawings in the corresponding graphic elements, and routes the data to the referenced project according to the codes of the referenced project and the referenced drawings, while maintaining the user's login status.

9. The cross-plant nuclear power engineering management method according to claim 1, characterized in that, Step S4 further includes: A joint query interface is provided, allowing users to send data viewing requests across projects. Based on this interface, the gateway requests independent service instances of each nuclear power project in parallel to view the data, and then merges the data from each project and returns it to the user.

10. A nuclear power plant engineering management device spanning multiple plants, characterized in that, It includes a memory and a processor, wherein the memory stores a computer program that, when executed by the processor, implements the cross-plant nuclear power engineering management method as described in any one of claims 1-9.

Images