Integrated management system for regular tests of nuclear power station
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-10-23
- Publication Date
- 2026-04-03
Smart Images
Figure CN121788046A_ABST
Abstract
Description
Technical Field
[0001] This application belongs to the field of nuclear power plant periodic test management technology, and in particular relates to a comprehensive management system for nuclear power plant periodic tests. Background Technology
[0002] Currently, due to the involvement of multiple departments, numerous processes, and complex interfaces in periodic testing, manual management suffers from inefficiency and ineffective data sharing, resulting in insufficient capacity for managing multiple reactors undergoing periodic testing. Therefore, nuclear power plants should establish a comprehensive periodic testing management system to fully manage all periodic tests, verify the performance of power plant production systems and equipment, and improve their reliability. Summary of the Invention
[0003] The purpose of this application is to overcome the shortcomings of the prior art and provide a comprehensive management system for the periodic testing of nuclear power plants, so as to realize the electronic process of periodic testing, achieve information management, and improve the efficiency of periodic testing management.
[0004] A comprehensive management system for periodic testing of a nuclear power plant, comprising: The presentation layer is used to interact with users, optimize interface layout, improve user experience, and display data. It builds user-friendly, fault-tolerant information by supporting dynamic data visualization, enhancing interface stability, and improving error detection capabilities. The client layer provides the operation interface to implement its business functions; The application layer is used to integrate Redis caching, achieve loosely coupled communication between services, and break down complex business processes into independent, fine-grained services. The data layer is used for centralized management of the storage, access, and persistence of business data such as periodic test outlines. By adopting a centralized and distributed architecture, it provides data services to upper-layer applications and supports horizontal scaling and resource optimization of the system.
[0005] In some embodiments, the presentation layer includes: The Periodic Test Outline Management Module is used for the full-process digital management of the periodic test outlines of nuclear power plants. The periodic test project management module is used for the digital management, adjustment, and query of the entire process of periodic test projects in nuclear power plants; The periodic test data management module is used for the full-process digital management, approval, and query of periodic test reports, evaluation forms, test results, and result trends; The Periodic Test and Inspection Plan module is used for the digital management, approval, and information display of the entire process of periodic test inspection plans, special plans, problems found, and experience feedback. The regularly updated outline management module is used to display, query, and manage changes to regularly updated outlines; The outline maintenance module is used to update and maintain the information of the planning column, execution column, and planning content of the periodic test outline; The system management module is used to uniformly process user and organizational information by calling the external user management system, and integrates the permission system to complete role authorization and dynamic menu configuration.
[0006] In some embodiments, periodic test items of the unit are imported in batches through the periodic test outline management module, and automatic error correction and deduplication functions are set for the batch-imported data.
[0007] In some embodiments, the periodic test measurement points can be queried through the periodic test project management module. The points can be filtered according to the selected conditions such as custom point package, location name, historical time, start time or end time, and the points, real-time values, historical values, maximum values of time periods, minimum values of time periods and average values of time periods can be displayed.
[0008] In some embodiments, the periodic test project management module can be used to query periodic test plans, compile periodic test contracts, apply for periodic test margins, apply for equivalent periodic test work, and apply to cancel periodic test work.
[0009] In some embodiments, the periodic test evaluation form information can be queried and displayed through the periodic test data management module. The information can be filtered according to the test project theme, work order number, applicant or execution team selection criteria, and the work order number, test project theme, planned start time, planned end time, actual start time, actual end time, execution team, applicant, creation time and status can be displayed.
[0010] In some embodiments, problems are identified through regular testing and inspections via the regular testing and inspection plan module, including internal and external experience feedback. The system can query and display information on the types of internal and external experience feedback identified in regular testing and inspections, as well as information on the types of management actions taken to address the problems identified in regular testing and inspections.
[0011] In some embodiments, the "Execution Column Outline" maintenance function of the outline maintenance module can be used to query the business information of the periodic test execution column outline. For example, the application can be filtered by selecting conditions such as subject, application number, applicant, application start time, application end time, applicant department or KKS code, and the application number, subject, status, applicant, application department and application time can be displayed. The execution column short process application can be initiated to compare and maintain relevant information.
[0012] In some embodiments, role management is performed through the system management module, which filters based on the role name selection criteria and displays the role code, role name, remarks, and creation time.
[0013] In some embodiments, the application layer processes the core business logic and process integration of the system based on a microservice architecture. It adopts Spring or Servlet frameworks and Redis caching, and uses XML, Web Service or SOAP to make the various application systems relatively independent and loosely coupled, so that each application system can be upgraded, modified and extended independently.
[0014] Compared with existing technologies, the integrated management system for periodic testing of nuclear power plants provided in this application has the following advantages: This application digitizes the processes of periodic test project planning, test approval, and project changes, and integrates with the production management system (SAP system) to obtain information on periodic test projects and test result evaluation.
[0015] This application enables online compilation of periodic test reports and statistical analysis of periodic test data, allowing for display and aggregation by type, thereby improving work efficiency.
[0016] This application aims to implement the regular test management and inspection plan, collect data according to different departments and offices, track and statistically analyze the problems found during inspections and the implementation of rectification feedback, and improve the management level of regular test projects.
[0017] This application implements an electronic outline for periodic testing, the content of which is consistent with the nuclear power plant maintenance outline and the ERMs periodic testing outline.
[0018] This application utilizes information technology to integrate periodic test management operations and processes, developing a user-friendly integrated management platform for periodic test management, thus realizing the periodic test management tasks for multi-reactor units. The platform possesses strong compatibility, scalability, and portability, enabling easy modification, association, and matching of data. Attached Figure Description
[0019] To more clearly illustrate the technical solution of this application, the accompanying drawings used in the technical description will be briefly introduced below.
[0020] Figure 1 The integrated management system architecture diagram for the periodic testing of nuclear power plants provided in this application; Figure 2 The functional architecture diagram provided for this application; Figure 3 A schematic diagram of the logical architecture provided for this application; Figure 4 Data load design for this application—system cluster schematic diagram; Figure 5 Data load design—data caching diagram provided for this application; Figure 6The data exchange system architecture diagram provided in this application; Figure 7 The physical architecture design diagram provided for this application. Detailed Implementation
[0021] The following detailed description provides further details on specific implementation methods.
[0022] like Figures 1 to 7 As shown, this application provides a comprehensive management system for periodic testing of nuclear power plants, including: The presentation layer is used for direct interaction between the system and the user. It optimizes the interface layout, improves the user experience, and efficiently displays data. It builds user-friendly fault-tolerant information by supporting dynamic data visualization, enhancing interface stability and error capture capabilities. The ultimate goal is to significantly improve the overall interaction efficiency and user experience. At the customer level, a unified user platform provides dedicated operation interfaces for different roles in the system (such as ordinary users, planning engineers, administrators, etc.) to realize their specific business functions. For example, ordinary users can view and enter periodic test outlines, initiate processes, and import / export related template outline data of different types; planning engineers can maintain the content of periodic test plans; and administrators can set system function menu permissions and configure standard static dictionary data, thereby ensuring that each role can independently and accurately complete its work tasks in various business areas. The application layer is used for the core business logic and process integration of the system based on a microservice architecture. It improves performance by using frameworks such as Spring, Servlet, and MVC and integrating Redis caching. In terms of processes, it integrates BPM business processes to achieve process visualization and traceability. At the same time, it uses interface protocols such as XML and Web Service to achieve loosely coupled communication between services, decomposing complex business into independent, fine-grained services, thereby providing the system with high flexibility, scalability, and low operational risks due to decoupling. It also integrates BPM business processes.
[0023] The data layer is used for centralized management of the storage, access, and persistence of business data such as periodic test outlines. By adopting a centralized and three-tier architecture and using a variety of database technologies, it provides efficient data services for upper-layer applications while ensuring data reliability and security, and supports horizontal scaling and resource optimization of the system.
[0024] The presentation layer includes: The Periodic Test Outline Management Module is used for full-process digital management of the periodic test outlines of nuclear power plants, including prediction of periodic tests during overhauls, query and display of effective outlines, batch import of outline items (including automatic error correction and deduplication), data comparison with SAP system, and batch modification of acceptance criteria to ensure the accuracy of test data. The periodic test project management module is used for the full-process digital management, adjustment and query of periodic test projects in nuclear power plants. It covers functions such as outline project changes, starting point adjustment, measurement point and plan query, qualification status statistics, equipment / system operability evaluation, periodic test margin application, equivalence application and work application cancellation. It ensures the accuracy of test data and compliance of operation procedures through standardized approval process. The periodic test data management module is used for the full-process digital management, approval and query of periodic test reports, evaluation forms, test results and result trends. The accuracy of the data and the compliance of the process are ensured through standardized processes such as compilation, verification, review and approval. The Periodic Test Inspection Plan module is used for the digital management, approval and information display of the entire process of periodic test inspection plans, special inspection plans and experience feedback. It ensures the standardization of data and the effectiveness of the process through standardized processes such as preparation, verification, review and approval. The scheduled changeout management module is used to display, query, and manage changes to scheduled changeouts. It supports filtering effective changeout information based on conditions such as unit and KKS code and tracing historical records. It also processes changeout requests and achieves data integration with the SAP system through processes such as compilation, verification, review, and approval. The outline maintenance module is used to synchronize, compare, update, and maintain the planning column, execution column, and planning content (such as risk indicators and remarks) of the periodic test outline. It supports filtering and querying by topic, application number, KKS code, and other conditions. After being reviewed through processes such as compilation, verification, and auditing, the data is automatically synchronized to the SAP system, the supervision outline system, and the nuclear safety supervision system to form a complete periodic test data chain. The system management module is used to call external systems (unified user platform) to obtain user and organizational information, process user and organizational information in a unified and planned manner, and complete role authorization and dynamic menu configuration in conjunction with the periodic test system permission management function. It is also used to manage the execution of scheduled tasks, maintain the hierarchical storage of various data dictionaries, and record system logs to provide real-time feedback on status and assist in problem localization.
[0025] Through the periodic test outline management module, users can predict periodic overhaul tests and select an overhaul cycle from a dropdown menu to query and display the outline data for that cycle. Due to different query logic, this function offers two query methods: "Periodic Tests" and "Overhaul Management," with "Periodic Tests" used by default. The displayed content includes: KKS code, outline category, execution status, unit, test cycle, cycle unit, process status, standard work package number, equipment name, executing department, risk indicator, test technical procedure, test item, availability criteria (acceptance criteria), test item overview, executing specialty, executing team, preparation engineer, standard working hours, number of personnel, total working hours, start date, offset, and SAP plan number.
[0026] The Periodic Test Outline Management module is used for outline display and allows users to query currently effective electronic outline information (including periodic test outline projects / entries). It filters based on unit, KKS code, process status, outline category, start date, end date, executing department, and execution status information, displaying historical electronic outline information and grouping it by project type for traceability. Query results display the following: KKS code, outline category, execution status, unit, test cycle, cycle unit, process status, standard work package number, equipment name, executing department, risk indicator, test technical procedure, test item, availability criteria (acceptance criteria), test item overview, executing specialty, executing team, preparation engineer, standard working hours, number of personnel, total working hours, start date, offset, and SAP plan number.
[0027] The Periodic Test Outline Management module is used for batch import of outlines and periodic test items for the unit. It includes automatic error correction and deduplication functions for the imported data. After the information in the periodic test item outline columns is entered, it undergoes compilation, proofreading, review (and countersigning), and approval processes within the periodic test management platform. After the platform initiates the review process for the periodic test item execution and plan columns, the entered information is automatically transferred to SAP and returned to the periodic test management platform via the SAP system plan number, forming the complete periodic test data information together with the periodic test outline project information. The overhaul periodic test prediction module queries the outline item information for the overhaul cycle.
[0028] The Periodic Test Project Management module is used for periodic test outline project change orders. Users can submit change requests based on their needs. If an application is rejected, it is returned to the applicant for resubmission. This approval process can be synchronized on mobile devices. Before modifying the periodic test outline, a periodic test project change order must be submitted. The main content of the change order can be found in the "Periodic Test Organization Management" program. The change order includes a periodic test item selection function with selection criteria such as (KKS code, outline category, executing department, preparation engineer, test technical procedure, unit, execution status). Applicants can modify, delete, convert routine to overhaul, or overhaul to routine items. New items can also be added. Finally, the system automatically merges relevant items into the change order for submission and review. After the periodic test change order is approved, the periodic test management platform automatically extracts the change information and updates the information on the periodic test outline interface. The change order contains basic information such as application number, subject, application status, applicant, applicant's department, and application time. You can also search for change orders by subject, application number, applicant, application start time, application end time, and applicant's department. Click to enter the change order to view the details of all items involved in this change order.
[0029] The Periodic Test Project Management module is used for periodic test start point adjustment forms. Users can submit requests to adjust the start point of periodic test outline projects as needed. The adjustment form allows users to select specific items for start point adjustment by choosing information such as KKS code, unit number, item status, outline category, start date, end date, executing department, executing team, and execution status. If an application is rejected, the form is returned to the applicant. When resubmitting, the applicant can choose to submit to the returned node or submit for approval by all personnel. This approval process can be synchronized on mobile devices. The start point of the periodic test plan can be permanently modified within a certain margin. For permanent modifications, users need to fill out a periodic test item execution start point adjustment form in the "Periodic Test Organization Management" program. After review and approval by relevant departments, the Production Planning Department / Overhaul Management Department modifies the start point of the periodic test project in the production management system based on the effective adjustment form. Start point adjustment form application information can be filtered by fields such as application number, applicant department, application status, application start time, application end time, applicant, and subject. The single page has been adjusted to include basic record information such as application number, subject, application status, applicant, applicant's department, and application time.
[0030] The Periodic Test Project Management module is used for querying periodic test measurement points. It can filter by selecting conditions such as custom point package, location name, historical time, start time, and end time, and displays the point, real-time value, historical value, maximum value of time period, minimum value of time period, and average value of time period.
[0031] The Periodic Test Project Management module is used for querying periodic test plans. This module should display the following information for periodic test projects: unit number, KKS code, periodic test project name, work application number, work package number, work plan start date, planned completion date, test status (not implemented, in progress, completed), executing specialty, and test result evaluation. This module offers two query modes: daily mode and overhaul mode. Daily mode allows filtering by unit number, KKS code, executing specialty, and completion status to find a list of periodic test projects started within a specific timeframe (e.g., today / 3 days / 7 days / 1 month). Overhaul mode allows filtering by unit number, overhaul cycle, KKS code, executing specialty, and completion status to find the completion status of overhaul periodic tests within a selectable time range.
[0032] The Periodic Test Project Management module is used for periodic test contract statistics. Within this module, the statistical information on the passing of periodic tests can be queried and displayed. This information should include the following: you can select and filter by execution status, work order number, work application number, preparing engineer, unit number, and test passing status. The displayed information includes the unit number, work application number, outline category, executing department, number of executions, passing status, KKS code, planned start time, and planned end time.
[0033] The Periodic Test Project Management module is used for equipment and system operability evaluation. This module allows users to query and display periodic test equipment and system operability evaluation information, which should include the following: Users can filter by test name, work application number, and applicant information, and the displayed information includes test name, work application number, execution date, test procedure code, cycle, equipment registration, status, and applicant. When a periodic test fails and cannot be resolved within the test margin, an operability evaluation of the relevant equipment and system can be conducted for non-supervised test items. The evaluation form includes: test name, work application number, execution date, test procedure code, technical responsible department, system department, cycle, safety level, and application status. The department responsible for implementing the periodic test submits the periodic test equipment and system operability evaluation form in the "Periodic Test Organization and Management" procedure. After the evaluation form becomes effective, the Production Planning Department / Overhaul Management Department arranges troubleshooting work and plans for re-periodic testing according to the evaluation form's conclusions.
[0034] The Periodic Test Project Management module is used for periodic test margin applications. This module can query and display periodic test margin application information, which should include the following: It can filter applications based on unit group number, work application number, equipment type, execution status, test name, process status, KKS code, applicant, and application time. The displayed information includes the work application number, unit group number, KKS code, equipment level, execution status, base date, equipment type, expected execution date, applicant, and test name. Periodic test work plans can be adjusted. Before adjusting the plan, the responsible department for periodic implementation needs to fill out the "Periodic Test Organization Management" procedure's Periodic Test Work Application Margin Utilization Application Form. After the margin utilization application form is approved, the Production Planning Department / Overhaul Management Department adjusts the periodic test plan according to the effective margin utilization application form. The Periodic Test Work Application Margin Utilization Application Form has been developed within the Production Planning platform. When clicking "Add this Application Form" in the Periodic Test Integrated Management Platform, the relevant page from the Production Planning Platform is automatically retrieved, seamlessly integrating into the Periodic Test Integrated Management Platform.
[0035] The Periodic Test Project Management module is used for periodic test equivalence applications. This module can query and display periodic test equivalence application information, which should include the following: It can filter applications based on unit group number, equivalent work application number, equipment type, execution status, test name, process status, KKS code, applicant, and application time. The displayed information includes the equivalent work application number, unit group number, KKS code, equipment level, execution status, base date, equipment type, execution date, number of execution rounds, applicant, and test name. The content includes the equivalent work application number, unit group number, KKS code, equipment level, execution status, base date, execution date, number of execution rounds, applicant, test name, and process status.
[0036] The Periodic Test Project Management module is used for canceling periodic test work applications. It can query and display information on canceled periodic test work applications, including the following: filters can be made based on unit number, work order number, equipment type, execution status, test name, process status, KKS code, applicant, and application time. The displayed information includes the work order number, unit number, KKS code, equipment level, execution status, actual execution cycle, base date, test name, and cancellation reason. If the unit status continuously fails to meet the conditions for periodic testing, the periodic test work application can be canceled. The department responsible for implementing the periodic test submits a cancellation form in the "Periodic Test Organization Management" procedure. After the cancellation form takes effect, the Production Planning Department / Overhaul Management Department cancels the corresponding periodic test plan in the backend. When clicking "Add New Application" in the Periodic Test Integrated Management Platform, the relevant page from the Production Planning Platform is automatically retrieved, seamlessly integrating the system into the Periodic Test Integrated Management Platform.
[0037] The periodic test data management module is used for periodic test report management. This module can query and display periodic test report management information, which should include the following: it can filter reports by name, work order number, and applicant, displaying the report name, work order number, status, applicant, and creation time. After the periodic test report management information is entered, it undergoes a process of compilation, verification, review (and countersigning), and approval within the periodic test management platform before becoming effective.
[0038] The periodic test data management module is used for evaluation form entry. It can query and display periodic test evaluation form information, which should include the following: it can be filtered based on selected criteria such as test project theme, work order number, applicant, and executing team. The displayed information includes the work order number, test project theme, planned start time, planned end time, actual start time, actual end time, executing team, applicant, creation time, and status. After the periodic test evaluation form information is entered, it undergoes a process of compilation, verification, review (and countersigning), and approval within the periodic test management platform before becoming effective.
[0039] The periodic test data management module is used for test result entry and can query and display periodic test result information. This information should include the following: it can be filtered based on KKS code, outline category, applicant, unit, and performing specialty, displaying the unit, KKS code, test project theme, performing specialty, performing team, outline category, performing team, entry status, outline status, and applicant. After the periodic test result information is entered, it undergoes a compilation, verification, review (and countersigning), and approval process within the periodic test management platform before becoming effective.
[0040] The periodic test data management module is used for querying test result trends. It can query and display the trend information of periodic test results, which should include the following: it can be filtered by KKS code, outline category, applicant, unit, execution specialty, execution team, test project theme, and acceptance criteria, and displays the test item, latest test time, and number of tests.
[0041] The Periodic Test and Inspection Plan module is used for periodic test and inspection plans. It allows users to query and display information on these plans, which should include the following: users can filter by plan name, and the plan name, description, application date, verification date, approval date, and status will be displayed. After the periodic test and inspection plan information is entered, it undergoes a process of preparation, verification, review (and countersigning), and approval within the periodic test management platform before becoming effective.
[0042] The Periodic Test and Inspection Plan module is used for periodic test and inspection plans. It allows users to query and display information on these plans, which should include the following: users can filter by unit number, inspection time, inspection content, and feedback provider. The displayed information includes the unit number, inspection object, inspection time, inspection content, feedback provider, and status. After the periodic test and inspection plan information is entered, it undergoes a process of compilation, verification, review (and countersigning), and approval within the periodic test management platform before becoming effective.
[0043] The Periodic Testing and Inspection Plan module is used to identify problems during periodic testing and inspections. It is divided into two types: internal and external experience feedback and management actions. The first type allows querying and displaying information on problems identified during periodic testing and inspections. Internal and external experience feedback information should include the following: it can be filtered by CR number, occurrence date, and selected criteria, displaying the CR number, CR topic, occurrence time, occurrence location, equipment KKS code, equipment name, equipment level, whether isolation maintenance is required, status description, consequences and potential consequences, and data source. The second type allows querying and displaying information on problems identified during periodic testing and inspections. Management action information should also include the following: it can be filtered by CR number, occurrence date, equipment KKS code, equipment name, CR topic, and equipment level, displaying the following: CR number, CR topic, occurrence time, occurrence location, equipment KKS code, equipment name, equipment level, whether isolation maintenance is required, status description, consequences and potential consequences, and data source.
[0044] The Periodic Test Inspection Plan module is used for periodic test experience feedback. It allows users to query and display periodic test experience feedback that should include the following: users can filter by topic, creation time, and creator; the displayed information includes the topic, feedback document, status, creator, and creation time. The module also compiles periodic test management and inspection experience feedback manuals compiled over the years and displays typical experience feedback cases from the current year's manual. Each time a feedback document is updated, the system automatically pushes it to the periodic test liaisons in each department for experience feedback learning.
[0045] The Periodic Switching Outline Management module is used to display periodic switching outlines, including currently active periodic switching outline information (including periodic switching outline projects / entries). It filters outlines based on factors such as unit, KKS code, entry status, outline category, preparation engineer, test procedure, executing department, and execution status information. It also displays historical periodic switching outline information and categorizes it by project type, enabling traceability.
[0046] The Periodic Switching Outline Management module is used for periodic switching outline changes. It can query and display the following information that should be included in a periodic test switching outline change: It can be filtered by subject, application number, applicant, application start time, application end time, and applicant's department, displaying the application number, subject, status, applicant, application department, and application time. Within the periodic test management platform, the process involves compilation, verification, review (and countersigning), and approval. After the review process is initiated on the platform, the information in the periodic switching item execution column and plan column is automatically transferred to SAP and returned to the periodic test management platform via the SAP system plan number, forming the complete periodic test data information together with the periodic test outline project information.
[0047] The outline maintenance module is used for maintaining the plan outline. It can query and display the following information for periodic test plan outline maintenance: It can filter by subject, application number, applicant, application start time, application end time, applicant's department, and KKS code, displaying the application number, subject, status, applicant, application department, and application time. It updates the information in the plan columns of the periodic test outline. After the periodic test item plan column information is edited, it undergoes an editing, proofreading, and review process within the periodic test management platform. After the periodic test item plan column information entry platform initiates the review process, the entered information is automatically transferred to SAP and returned to the periodic test management platform via the SAP system plan number, forming complete periodic test data information together with the periodic test outline project information.
[0048] The outline maintenance module is used for maintaining the execution column outline. It can query and display the following information that should be included in the periodic test execution column outline maintenance: It can be filtered by subject, application number, applicant, application start time, application end time, applicant's department, and KKS code, displaying the application number, subject, status, applicant, application department, and application time. It updates the information in the execution columns of the periodic test outline entries. After the information in the periodic test entry execution column is edited, it undergoes an editing, proofreading, and review process within the periodic test management platform. After the periodic test entry execution column information entry platform initiates the review process, the entered information is automatically transferred to SAP and returned to the periodic test management platform via the SAP system plan number, forming the complete periodic test data information together with the periodic test outline project information.
[0049] The outline maintenance module is used for maintaining plan content. It can query and display the following content that should be included in the maintenance of periodic test plans: It can filter by maintenance order number, subject, maintainer, start and end dates of maintenance, and the maintainer's department, displaying the maintenance order number, maintenance subject, maintenance reason, status, maintainer, maintainer's department, and maintenance time. It also updates the risk labels and remarks in the periodic test outline items, and can update the risk label and remarks information of outline items in batches.
[0050] The system management module is used for user management. The system does not store user information; instead, it calls upon information from the user management system for unified processing. User roles and role authorization are fully integrated with the Tianwan Permission Management System, allowing user authorization within the permission management system.
[0051] The system management module is used for organizational structure management. The system does not store organizational structure information; instead, it calls upon information from the user management system for unified processing. User roles and role authorization are fully integrated with the Tianwan Permission Management System, and authorization can be performed within the permission management system.
[0052] The system management module is used for menu management. It can dynamically generate navigation menus for users, making the interface simpler and the operation more efficient. Different roles can be configured with corresponding menus to distinguish data.
[0053] The system management module is used for role management. It can query and display the following information for role management: roles can be filtered by name, displaying role code, role name, remarks, and creation time. It also allows assigning different menu permissions to different roles for easier user access later.
[0054] The system management module is used for scheduled tasks. It can query and display scheduled tasks, which should include the following information: tasks can be filtered by method name, displaying BEAN name, method name, CRON expression, remarks, and status. Different tasks can be added to facilitate feedback on subsequent function execution.
[0055] The system management module is used for the data dictionary, which includes platform fields such as a general basic dictionary, a periodic test outline dictionary, a periodic test project dictionary, a periodic test data dictionary, a periodic test plan dictionary, a top ten defect dictionary, a periodic test experience feedback dictionary, a periodic switch outline dictionary, a maintenance outline dictionary, and a periodic outline dictionary. Dictionary values of the types required by the project can be added later. The data structures used in the project are managed hierarchically for easy storage and use.
[0056] The system management module is used for system logs. Logs can be filtered based on input time criteria and downloaded to the local environment for viewing.
[0057] It is used to provide real-time feedback on system status, record the time, location, and context of errors, help developers quickly locate the root cause of problems, and identify potential issues in advance through logs to avoid system failures. It is an indispensable foundation for projects.
[0058] This application separates data from presentation, enabling the data to truly become an information repository, facilitating its use by other systems, providing better services to users, and allowing for the extraction of more useful information after mining, thus gaining a competitive advantage.
[0059] Another benefit of separating data and presentation is that the presentation can be changed frequently, just like human skin can have different colors, which can greatly reduce the maintenance cost of the system.
[0060] The intermediate data processing layer can make the system more flexible because user needs often change. When needs change, we can modify the processing layer to meet them without changing the presentation layer. When there are new requirements, modules can be added to the processing layer without affecting the existing functions.
[0061] like Figure 3 As shown, the system's logical hierarchy follows the design theory of web applications, helping enterprises to expand and modify future applications, while also facilitating the division of functional logic and project implementation from an architectural perspective.
[0062] like Figure 4 As shown, this application first adopts a cluster deployment method for the platform, and the load balancing device automatically distributes user requests.
[0063] Static page data caching: Cache static data such as HTML pages, images, CSS, and JS to significantly improve the user experience and reduce response time.
[0064] Application cluster deployment: Based on factors such as performance, business volume, business nature, scale, response speed, and security, application servers are reasonably separated and shared, and one or more application server groups are established to achieve load balancing through horizontal scaling and elastic scaling technologies.
[0065] Dynamic data caching: This technique uses caching technology to cache data dynamically requested by users. It can also significantly reduce the number of requests that pass through the database layer, thereby greatly improving response time.
[0066] Database cluster deployment (distributed database): This method uses a distributed database deployment approach to establish a cluster, ensuring a rapid response to requests that flow to the database layer.
[0067] This application adopts a data load design—data caching design, such as Figure 5 As shown, Redis is a high-performance distributed in-memory caching server. Its typical purpose is to improve the speed and scalability of dynamic web applications by caching database query results and reducing the number of database accesses. Redis caches individual objects in a key / value format.
[0068] This application adopts a data load design—data query design, including: Querying data: First, the system retrieves data from the Redis intermediate cache using the specified key. If the data exists, it is retrieved directly without querying the database. If the data does not exist, the database is queried, and the query result is stored in the Redis cache as a key-value pair. The result is then returned to the query statement.
[0069] Update data: First update the database data, then delete the relevant Redis data.
[0070] Adding data: First, delete the relevant Redis cached data, and then add the database data.
[0071] Delete data: Deletes the database data and also deletes the Redis data.
[0072] A self-developed in-memory data caching service.
[0073] A caching service using an independent process approach.
[0074] For some frequently used dynamic data, we can cache it in memory through the development program service and provide it to other business applications for use. The following data can be cached in this way.
[0075] A buffer for basic user information and status.
[0076] List caching, like a list of posts in a forum.
[0077] Cache the number of records, such as how many posts are in a forum section, to facilitate pagination.
[0078] More complex group, sum, and count queries, such as ranking points by category.
[0079] Memory caching integrated into web applications.
[0080] In web applications, for frequently accessed functions, consider loading them entirely into memory to ensure absolute response speed. For frequently accessed hot data, use centralized caching (multiple caches can be load-balanced) to reduce the pressure on the database. Examples include configuration information, operator information, etc.
[0081] Data distribution: OLTP: Stores 1-2 years of data. Historical data is stored in a dedicated space and is not used in business operations. ODS: Data is synchronized from OLTP and lightly aggregated and reorganized, mainly used for querying and statistics; OLAP: Decision support applications where data is highly aggregated.
[0082] like Figure 6 As shown, the system receives data from the basic business database or the basic business application system, converts it into a unified format for data storage, and provides shared exchange or counterpart business data exchange through a unified data exchange service interface module.
[0083] Various information exchanges are achieved through a unified exchange database. The data stored in this database is of two types: public and private. Public data refers to data accessible to all users entering the system; private information refers to information accessible only to relevant business entities. The scope of access to private data can be controlled. Therefore, the exchange database employs a mandatory access control strategy, setting the access scope for each piece of exchanged information.
[0084] Direct data exchange and indirect data exchange form standardized exchange data packets through the message receiving module and feedback information retrieval module, respectively. Then, the data is stored in the exchange database through the data parsing, format conversion, and data loading modules, thus facilitating the selection of multiple exchange methods.
[0085] In terms of data exchange services, the application system uses XML-based query data packets, with the data query module responsible for retrieving the required content and returning the query results in XML-based data packets.
[0086] When the query module receives a batch information query request, if the data to be queried does not exist in the exchange database, the batch data query module is started via a message to load the data to be queried; if the batch information query request is a request to update the exchange data, the batch data query module is started directly via a message to load the data to be queried.
[0087] Since all exchanged information is based on XML data packets, the relevant applications will parse the data packets through standard data interfaces to obtain the required data.
[0088] like Figure 7 As shown, based on the analysis of requirements and business needs, JN_PTCMS will be responsible for the approval and data recording of various tasks in the field of periodic testing of nuclear power plants, and will optimize and improve the functions of existing systems. At the same time, a mobile application development platform will be used to realize the management of plans, the approval process of each stage of the project, the execution of approvals, and the display of queries and statistical analysis to facilitate the smooth work of periodic testing staff.
[0089] In the intranet platform deployed on the intranet server, authorized nuclear power users can log in via VPN dedicated line and access the intranet platform's resource information. To enhance the reliability and availability of the intranet platform, relevant services are deployed independently for easier management, and critical services are deployed in clusters.
[0090] The above description is only a specific embodiment of this application, but the protection scope 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 protection scope of this application.
Claims
1. A comprehensive management system for periodic testing of a nuclear power plant, characterized in that, include: The presentation layer is used to interact with users, optimize interface layout, improve user experience, and display data. It builds user-friendly, fault-tolerant information by supporting dynamic data visualization, enhancing interface stability, and improving error detection capabilities. The client layer provides the operation interface to implement its business functions; The application layer is used to integrate Redis caching, achieve loosely coupled communication between services, and break down complex business processes into independent, fine-grained services. The data layer is used to centrally manage the storage, access, and persistence of business data. By adopting a centralized and distributed architecture, it provides data services to upper-layer applications and supports horizontal scaling and resource optimization of the system.
2. The integrated management system for periodic testing of nuclear power plants according to claim 1, characterized in that, The presentation layer includes: The Periodic Test Outline Management Module is used for the full-process digital management of the periodic test outlines of nuclear power plants. The periodic test project management module is used for the digital management, adjustment, and query of the entire process of periodic test projects in nuclear power plants; The periodic test data management module is used for the full-process digital management, approval, and query of periodic test reports, evaluation forms, test results, and result trends; The Periodic Test and Inspection Plan module is used for the digital management, approval, and information display of the entire process of periodic test inspection plans, special plans, problems found, and experience feedback. The regularly updated outline management module is used to display, query, and manage changes to regularly updated outlines; The outline maintenance module is used to update and maintain the information of the planning column, execution column, and planning content of the periodic test outline; The system management module is used to uniformly process user and organizational information by calling the external user management system, and integrates the permission system to complete role authorization and dynamic menu configuration.
3. The integrated management system for periodic testing of nuclear power plants according to claim 2, characterized in that, Import the unit's periodic test items in batches through the periodic test outline management module, and set up automatic error correction and deduplication functions for the batch-imported data.
4. The integrated management system for periodic testing of nuclear power plants according to claim 2, characterized in that, The periodic test project management module allows users to query periodic test measurement points and filter them based on custom point packages, location names, historical times, start times, or end times. The system displays point locations, real-time values, historical values, maximum values for a given time period, minimum values for a given time period, and average values for a given time period.
5. The integrated management system for periodic testing of nuclear power plants according to claim 2, characterized in that, The periodic test project management module allows users to query periodic test plans, compile periodic test contracts, apply for periodic test margin work, apply for equivalent periodic test work, and apply to cancel periodic test work.
6. The integrated management system for periodic testing of nuclear power plants according to claim 2, characterized in that, The periodic test data management module allows users to query and view periodic test evaluation forms. The system can filter data based on the test project theme, work order number, applicant, or execution team. The displayed information includes the work order number, test project theme, planned start time, planned end time, actual start time, actual end time, execution team, applicant, creation time, and status.
7. The integrated management system for periodic testing of nuclear power plants according to claim 2, characterized in that, The regular testing and inspection plan module identifies problems through regular testing and inspection, including internal and external experience feedback. It also displays information on the types of internal and external experience feedback and management actions taken to address the problems identified during regular testing and inspection.
8. The integrated management system for periodic testing of nuclear power plants according to claim 2, characterized in that, The outline maintenance module allows users to query the business information of the periodic trial execution column outline. Users can filter the information based on the selected conditions, such as topic, application number, applicant, application start time, application end time, applicant's department, or KKS code. The module displays the application number, topic, status, applicant, application department, and application time. Users can also initiate a short-process application for the execution column to compare and maintain relevant information.
9. The integrated management system for periodic testing of nuclear power plants according to claim 2, characterized in that, Role management is performed through the system management module. Users can filter by role name based on selected criteria and view the role code, role name, remarks, and creation time.
10. The integrated management system for periodic testing of nuclear power plants according to claim 1, characterized in that, The application layer is based on a microservice architecture to handle the core business logic and process integration of the system. It uses Spring or Servlet frameworks and Redis caching. By using XML, Web Service or SOAP, the application systems are relatively independent and loosely coupled, so that each application system can be upgraded, modified and extended independently.