A work order list custom view management system and method for nuclear power plant group reactor

Abstract

The application discloses a work order list self-defined view management system and method for nuclear power plant group reactor group. The system comprises a front-end interaction layer, a business logic layer, a data access layer and a plant group reactor group adaptation layer. The front-end interaction layer is used for realizing the interaction between a user and the system, and comprises a view configuration panel, a list display module and a permission verification component. The business logic layer comprises a view self-defined engine and a configuration persistence module. The data access layer comprises a view configuration library and a work order business library. The view configuration library is used for storing view configuration information and associating user and organizational structure information. The work order business library is used for storing nuclear power work order full-field data. The plant group reactor group adaptation layer is used for adapting the nuclear power plant group reactor group management mode, and comprises a reactor type identification component, a unit attribution component, a power plant isolation component and a user permission identification component. The application solves the problems of field redundancy and repeated configuration, realizes fine data isolation and permission control and realizes fine management.

Description

Technical Field

[0001] This invention relates to the field of nuclear power information management technology, specifically to a custom view management system and method for work order lists of nuclear power plants and reactors, applicable to the display and management of work order information in scenarios involving multiple nuclear power plants, multiple units, and multiple reactor types. Background Technology

[0002] In the operation and maintenance of nuclear power production equipment, the work order system serves as the core business support carrier, encompassing all categories of business processes such as equipment defects, maintenance operations, periodic testing, and isolation operations. It is a crucial information tool for ensuring the safe and stable operation of nuclear power plants. Nuclear power work orders, designed to adapt to the needs of multiple disciplines and full-process management, contain as many as 70-80 fields, covering nuclear power-specific fields such as equipment function location code, work order type, professional category, responsible department, executing power plant, scheduling, issuing department, safety level, reactor type, isolation status, maintenance team, risk level, radiation dose, isolation permit, administrative permit, and completion status.

[0003] Existing nuclear power plant work order systems generally suffer from the following technical pain points, failing to meet the management requirements of high safety, strong isolation, specialization, and clustered operation in nuclear power plants: 1. Redundant fields and information overload: The list displays all work order fields by default, resulting in a bloated interface and the burying of key information. Different professionals (such as maintenance, operation, safety, and technical management) have significantly different fields of interest. The general list cannot meet personalized needs, increases the cost of information filtering for users, and is prone to misoperation due to information complexity.

[0004] 2. Inefficient repetitive configuration: Traditional nuclear power plant work order systems only support temporarily hiding / showing fields. The configuration is automatically invalidated after the page is closed. Users need to repeatedly adjust the field display status every time they log in to the system, which is cumbersome, time-consuming and error-prone. Although some systems support simple view saving, they do not implement default view fixation, hierarchical management of shared / private permissions, and cross-stack data isolation capabilities, resulting in extremely poor adaptability.

[0005] 3. Lack of data isolation among multiple power plants and reactors: Currently, nuclear power groups generally adopt a management model of "multiple power plants, multiple units, and multiple reactor types" (such as pressurized water reactors, heavy water reactors, and fast reactors coexisting). The existing work order view does not have a refined data isolation mechanism based on power plant / unit / reactor type. Shared views are prone to cross-reactor and cross-power plant data leakage problems, and private views cannot adapt to cross-power plant collaborative office scenarios, which is seriously inconsistent with the requirements for nuclear power data security management.

[0006] 4. Insufficient permission and scenario adaptation: It lacks core functions such as view sharing / private hierarchical management, custom field display order, and default view persistence, and cannot meet the multi-level management needs of "personal exclusive view, department shared view, power plant public view, and cross-power plant authorized view", and cannot adapt to the business characteristics of nuclear power professional division of labor and hierarchical control. Summary of the Invention

[0007] To address the shortcomings of existing technologies, the present invention aims to provide a custom view management system and method for work order lists of nuclear power plant clusters and reactors. The core objective is to achieve full-dimensional customization of work order list fields, multi-level permission management of views, persistence of default configurations, and fine-grained data isolation for clusters of plants and reactors. This addresses the pain points of work order information display in multi-disciplinary, multi-power plant, and multi-reactor scenarios in nuclear power, improves user operation efficiency, data security, and system adaptability, and meets the high safety, strong isolation, and professional management requirements of nuclear power.

[0008] To achieve the above objectives, the present invention provides a custom view management system for work order lists for nuclear power plant clusters and reactors, characterized in that it includes a front-end interaction layer, a business logic layer, a data access layer, and a cluster adaptation layer. The front-end interaction layer is used to realize the interaction between users and the system, including a view configuration panel, a list display module, and a permission verification component; the view configuration panel is used to configure custom views; the list display module is used to display work order data according to the custom views configured by the view configuration panel; the permission verification component is used for permission verification to block unauthorized operations; The business logic layer includes a view customization engine and a configuration persistence module. The view customization engine is used to parse user configuration instructions from the view configuration panel and complete field arrangement. The configuration persistence module is used to encrypt and store the view configuration and retrieve it. The data access layer includes a view configuration library and a work order business library. The view configuration library is used to store encrypted view configuration information from the view configuration panel and associate it with user and organizational structure information. The work order business library is used to store nuclear power work order full-field data to support the configuration of custom views. The cluster plant / refueling adaptation layer is used to adapt to the cluster plant / refueling management mode of nuclear power plants. It includes: a reactor type identification component, used to identify the reactor type to which the work order belongs; a unit affiliation component, used to determine the unit to which the work order belongs; a power plant isolation component, used to filter and intercept cross-power plant data by matching and verifying the codes of each nuclear power plant with the power plant to which the work order belongs; and a user permission identification component, used to identify the user's permissions for configuring, editing, and accessing views.

[0009] As one aspect of the aforementioned system, the front-end interaction layer further includes a view management menu for saving, naming, editing, deleting, setting as default, and sharing management of views. The business logic layer also includes an access control module and a data isolation module; the access control module determines the user's access and editing permissions to the view based on the verification and control of the access model, and the data isolation module implements data isolation based on a filtering model. The data access layer also includes a user permission library, which stores user information, organizational structure, crew permissions, and role information, providing support for the permission control module to perform permission verification and the data isolation module to perform data isolation.

[0010] As another approach to the aforementioned system, the feature is that the permission model is a four-level permission model of "private - team shared - power plant public - cross-power plant authorization"; "Private" permission means that a private view can only be accessed and edited by the person who created it; "Group sharing" permission refers to the view shared by users within the same work group; "Power Plant Public" permissions refer to views shared by users within the same power plant; "Cross-plant authorization" permission refers to a view that a user in one power plant authorizes to a user in another power plant to share. Among them, the shared view in the "team sharing" permission, "power plant public" permission and "cross-power plant authorization" permission is further subdivided into viewing and editing dual permission control.

[0011] As another approach to the aforementioned system, the feature is that the filtering model is a four-dimensional filtering model constructed based on the user's power plant, generating unit, stack type, and permission role. When configuring the view, the corresponding data range is automatically bound, realizing a triple binding of "view-permission-data".

[0012] As another approach to the aforementioned system, the feature is that the configuration persistence module uses the AES encryption algorithm to convert the view configuration information into JSON format and then encrypt and store it; the view configuration information includes field selection, display order, column width, header alias, permission type, and data range.

[0013] As another aspect of the aforementioned system, the view customization engine is characterized by adapting to nuclear power-specific fields, which include at least one of reactor type, unit number, safety level, isolation status, radiation risk, maintenance specialty, test category, radiation dose, and isolation permit.

[0014] As a further embodiment of the above system, the group plant and group reactor adaptation layer further includes a basic data management module; the basic data management module is used to manage data of users, power plants, units, and reactor types, including adding, editing, and deleting data of users, power plants, units, and reactor types, and is used to identify and describe users, power plants, units, and reactor types.

[0015] This invention also provides a method for managing custom view views of work order lists for nuclear power plant clusters, characterized in that, when implemented on the system, it includes the following steps: Step S1, Field Initialization and Optional List Generation: After the user logs into the system, the system combines the user's power plant, unit, reactor type, and role information to load all fields of the nuclear power work order, display them by professional category, filter fields without permission, and generate a field optional list exclusive to the user. Step S2, View Customization Configuration: Users configure custom views through the view configuration panel; Step S3, View Saving and Default Settings: The system encrypts the view information configured by the user and stores it in the view configuration library, and associates it with user and organizational structure information; when the user sets the view as the default view, the system will automatically load the default view through the configuration persistence module when the user logs in subsequently. Step S4, Permission verification and data isolation: When a user accesses the view, the system's permission verification component verifies whether the user has the corresponding permissions. After the permission verification is passed, the work order data is filtered based on the filtering model, and only data within the authorized scope is displayed. Step S5, View Management and Linkage: The front-end interaction layer edits, deletes, shares, and manages the views in batches, and links the views with the work order filtering, pagination display, work order sorting, and export functions.

[0016] Step S6, Dynamic Update and Adaptation: When the cluster plant and cluster reactor adaptation layer adds a nuclear power field, the front-end interaction layer includes it in the field selectable list; when user permissions change, the front-end interaction layer refreshes the view visible fields and data range in real time; when the cluster plant and cluster reactor adaptation layer adds a power plant, unit, or reactor type, the power plant isolation component of the cluster plant and cluster reactor adaptation layer adapts it to the data isolation rules.

[0017] As one aspect of the above method, the configuration of a custom view includes: displaying or hiding fields, dragging and dropping fields in order, adjusting column width, modifying header aliases, and setting the view name, permission type, and data range.

[0018] As another way of the above method, the permission type includes private, team shared, power plant public, and cross-power plant authorization; the data range includes personal unit, all units of the power plant, specified stack type, and specified unit. In step S4, the shared view isolates data according to the power plant to which the creator belongs, and users across power plants do not have permission to access it; the private view filters data according to the user's unit and stack type permissions. In step S5, the sharing management includes single view sharing and batch sharing. When sharing, access objects and access permissions are set, and access permissions include viewing or editing the view.

[0019] Compared with the prior art, the present invention has the following beneficial effects: 1. Solve the pain points of field redundancy and repetitive configuration: By customizing and permanently saving views, users are prevented from repeatedly adjusting fields every time they log in, which greatly improves operational efficiency, reduces the risk of misoperation, and adapts to the personalized needs of multiple disciplines in nuclear power.

[0020] 2. Achieve refined data isolation across multiple power plants and reactors: The pioneering four-dimensional (power plant + unit + reactor type + responsible person) data isolation model achieves triple binding of "view-permission-data", completely solving the problem of cross-reactor and cross-power plant data leakage in existing systems and meeting the high safety management requirements of nuclear power.

[0021] 3. Adapt to nuclear power scenario requirements: Specifically adapted to nuclear power-specific fields, displayed by professional category, supports modification of table header aliases, fits the characteristics of nuclear power professional division of labor, and solves the problem that general systems cannot adapt to nuclear power scenarios.

[0022] 4. Refined access control: The four-level access control model (view, create, edit, delete) covers the needs of individuals, work groups, power plants, and cross-power plants. It supports dual access control (1. view only, 2. view and edit) to adapt to the hierarchical management requirements of nuclear power plants and improve the flexibility and security of view management.

[0023] 5. High scalability and low maintenance cost: As the business scale expands in the future, such as adding power plants, new units, or new professional business fields, the view configuration can be dynamically updated to adapt without secondary development. This adapts to the needs of expanding the scale of nuclear power plant clusters and reduces system operation and maintenance costs.

[0024] 6. Enhance user experience: Drag-and-drop operation, automatic loading of default view, and linkage between view and filter / export conform to user operation habits, improve user experience, and reduce training costs. Attached Figure Description

[0025] Figure 1 A diagram illustrating the overall architecture of a custom view management system for work order lists of nuclear power plant clusters, as described in a specific implementation. Figure 2 A schematic diagram of the view customization configuration process for a specific implementation method; Figure 3 A schematic diagram of the view permission verification process for a specific implementation method; Figure 4 This is a schematic diagram of the data isolation logic for a group of factories and a group of stacks in a specific implementation method; Figure 5 A schematic diagram of the front-end view configuration interface for a specific implementation method; Figure 6 This is a schematic diagram of the user view switching interface for a specific implementation method. Detailed Implementation

[0026] This invention discloses a custom view management system and method for work order lists in nuclear power plant clusters, aiming to solve the technical pain points of existing nuclear power work order systems, such as redundant fields, repetitive configurations, lack of data isolation for clusters of plants and reactors, and insufficient permission adaptation. The system includes a front-end interaction layer, a business logic layer, a data access layer, and a cluster adaptation layer. The method includes steps such as field initialization and optional list generation, custom view configuration, view saving and default settings, permission verification and data isolation, view management and linkage, and dynamic updates and adaptation. This invention innovatively designs a nuclear power scenario-based custom view engine, a four-level permission model, and a four-dimensional data isolation mechanism for clusters of plants and reactors. It achieves integrated management of work order list field display / hiding, work order list field order adjustment, custom view saving / default / shared / private, and data isolation. It is adaptable to multi-professional, multi-power plant, and multi-reactor scenarios in nuclear power, improving operational efficiency and data security, and possesses significant novelty, inventiveness, and practicality.

[0027] A specific implementation provides a customizable view management system for work order lists of nuclear power plant clusters and reactors, such as... Figure 1 As shown, it includes a front-end interaction layer, a business logic layer, a data access layer, and a group factory / group stack adaptation layer. These layers work together to implement functions such as view customization, access control, data isolation, and persistent loading. The specific structure is described below: (1) Front-end interaction layer: Deployed on the user terminal to enable interaction between the user and the system; the user terminal can be a web browser or a terminal application, and the front-end interaction layer can be embedded in the user terminal.

[0028] The front-end interaction layer includes a view configuration panel, a list display module, a view management menu, and a permission verification component; among which, such as Figure 5 As shown, the view configuration panel is used to configure custom views, such as configuring field selection, dragging and dropping field order, adjusting field column width, modifying view header aliases, setting view access permissions, and selecting the view display data range. Here, the data range refers to the visible data boundary selected by the user in the custom view, including four optional viewing ranges for work order information records: the user's responsible unit, all units in the power plant, a specified stack type, and a specified unit. This limits the boundaries of the work order data that can be displayed in the current view. The list display module is used to display work order data according to the custom view configured in the view configuration panel. The view management menu is used to perform operations such as saving, naming, editing, deleting, setting as default, and setting sharing mode for views. The permission verification component is used for initial front-end permission verification to block unauthorized operations.

[0029] (2) Business logic layer: Deployed on the nuclear power plant cluster server cluster, it is the core processing layer of the system; This business logic layer includes a view customization engine, an access control module, a data isolation module, and a configuration persistence module. The view customization engine receives data from the front-end interaction layer and parses user configuration commands to perform operations such as field filtering, sequential arrangement, column width calculation, and header alias mapping for configuring custom views. The access control module implements a four-level access control model to verify and manage user access and editing permissions for views. The four-level access control model is "private - team shared - power plant public - cross-power plant authorized." Teams include business teams, departments, and sections.

[0030] The data isolation module is used to filter and isolate work order data by power plant, generating unit, and stack type based on user permissions and organizational structure. Filtering refers to filtering and displaying work order information records according to the user's power plant, department, and responsible generating unit. Isolation means that system users can only view work order information records within their authorized scope; work orders from unauthorized power plants or generating units will be hidden. The configuration persistence module is used to encrypt, store, update, and retrieve view configurations for display through the list display module, achieving configuration persistence.

[0031] (3) Data access layer: used to implement data storage and retrieval; The data access layer includes a view configuration library, a work order business library, and a user permission library. The view configuration library stores user-defined view configuration information (e.g., encrypted JSON-formatted view configuration information) and associates this information with user identifiers (IDs), organizational structure identifiers (IDs), and data scope information. The work order business library stores all fields of nuclear power work orders, including basic fields and nuclear power-specific fields. Basic fields are common, inherent fields for work orders, regardless of nuclear power specialty or general business requirements. These include: work order number, equipment code, equipment name, creation time, work order status, responsible person, remarks, planned start time, and planned end time. Nuclear power-specific fields are dedicated fields specific to nuclear power plant / reactor scenarios and not found in ordinary industrial work orders. These include: unit number, reactor type, functional location code, whether it is an SPV, safety level, radiation risk level, isolation permit status, maintenance specialty category, risk level, test category, and isolation status—all nuclear power-specific control fields. The user permission library stores user information, organizational structure, unit permissions, role information, etc., providing support for the permission control module to perform permission verification and the data isolation module to perform data isolation. User information includes basic identity profile information such as the user's unique identifier ID, user name, login account, department, position, contact information, and account status. Unit permissions refer to the set of unit numbers and stack type access permissions pre-configured by the system for each user, restricting users to viewing work order data only within authorized units and stack types; data outside the authorized scope is automatically isolated and blocked. Role information includes maintenance engineers, operation engineers, safety engineers, technical engineers, isolation engineers, and testing engineers.

[0032] (4) Cluster plant and cluster reactor adaptation layer: used to adapt to the management mode of nuclear power cluster plants and cluster reactors; The cluster-plant / cluster-adaptation layer includes a basic data management module, a reactor type identification component, a unit affiliation component, a power plant isolation component, and a user permission identification component. The reactor type identification component identifies the reactor type (pressurized water reactor, heavy water reactor, etc.) to which the work order belongs. The unit affiliation component determines the unit and power plant to which the work order belongs. The power plant isolation component achieves data isolation between different power plants. The power plant isolation component works by uniquely identifying each nuclear power plant and matching the user's power plant code with the work order's power plant code. It only allows work order data from the user's own power plant and automatically filters and blocks cross-plant data, achieving physical and logical data isolation and security control between different nuclear power plants. The user permission identification component identifies user permissions. The basic data management module manages the basic data for users, power plants, units, and reactor types, including adding, editing, and deleting basic data for these entities. Basic data refers to the data used to identify and describe users, power plants, units, and reactor types.

[0033] A power plant refers to a power generation enterprise. For example, a certain group includes four nuclear power plants: North China Nuclear Power Plant, Central China Nuclear Power Plant, South China Nuclear Power Plant, and East China Nuclear Power Plant.

[0034] A specific implementation also provides a method for managing custom view views of work order lists for nuclear power plant clusters and reactors, such as... Figure 2 As shown, it includes the following steps: Step 1: Field initialization and optional list generation; After a user logs into the system, the system obtains the user's power plant, unit, reactor type, and role information through the group plant and group reactor adaptation layer. Combined with the permission configuration in the user permission library, the system loads all fields of the nuclear power work order (including basic fields and nuclear power-specific fields). The system displays the fields according to professional categories such as maintenance, operation, safety, technology, isolation, and testing, automatically filters fields that the user does not have permission to access (such as radiation safety-related fields that are only visible to safety professionals), and generates a field selection list exclusive to the user.

[0035] User permission configuration is a set of power plant, unit, stack type, professional role, and field access permissions pre-assigned to users by the system; New user information is created and entered by the administrator in the backend. Permissions are uniformly assigned and bound by the administrator according to position, unit, and profession, and stored in the user permission database, which is automatically retrieved and taken effect when logging in.

[0036] Step 2: View Custom Configuration Users can customize view configurations through the view configuration panel in the front-end interaction layer, including: ① selecting fields to be displayed and deselecting fields not to be displayed; ② adjusting the display order of fields by dragging and dropping; ③ customizing the column width and alignment of each field; ④ modifying field header aliases (adapting to different professional terminology, such as changing "security level" to "security control level"); ⑤ setting the view name and description; ⑥ selecting the view permission type (private / team shared / power plant public / cross-power plant authorization); ⑦ selecting the data range (own unit / all units in this power plant / specified stack type / specified unit).

[0037] Cross-power plant authorization is defined by the view creator, who specifies the authorized objects and access scope, and sets the authorization validity period. The authorization validity period is consistent with the user account permission validity period, and automatically expires upon expiration. The access scope refers to the business data fields that the authorized objects can view.

[0038] Step 3: View saving and default settings After the user completes the configuration and clicks the save button, the front-end interaction layer sends the configuration command to the business logic layer. The configuration persistence module uses the AES encryption algorithm to convert the view configuration information (field selection, display order, column width, permission type, data range, etc.) into JSON format, encrypts it, and stores it in the view configuration library, associating it with the user ID and organization structure ID. The user can choose to set this view as the default view, and the system marks the view with a default identifier in the view configuration library. When the user logs in later, the system will automatically load the default view.

[0039] Step 4: Permission verification and data isolation like Figure 3 As shown, when a user accesses a view, the system performs a permission verification and data isolation process: ① The permission control module reads the user information and view permission configuration, and verifies whether the user has the necessary access permissions for the view (private views can only be accessed by the user themselves, and shared views require matching corresponding power plant or department permissions); ② After the permission verification is successful, as... Figure 4 As shown, the data isolation module is based on four dimensions: the user's power plant, generating unit, stack type, and job role. Combined with the data range selected by the user in the view configuration, it integrates and automatically generates four-dimensional data filtering conditions to accurately filter work order data, achieving automatic isolation and control of permissions and data in multi-power plant / multi-stall scenarios. During the four-dimensional data isolation process for multi-power plant / multi-stall systems, if the user's power plant permissions cover a wider range than the generating unit permissions, resulting in overlapping permission ranges, the system follows a filtering logic of prioritizing narrower ranges and then prioritizing generating unit permissions. The generating unit's limited range is used as the final constraint condition to narrow the visible data boundary, ensuring the accuracy of data isolation and adhering to the principle of least privilege. For example, when power plant permissions and generating unit permissions overlap, generating unit permissions take precedence as the filtering condition. For instance, if a professional view is run and a power plant permission is granted to an operations engineer but not a specific generating unit, the operations engineer can still view work order records for all generating units within the power plant. Overlapping scenarios: ① The professional view is run, and the operation engineer is authorized with both power plant permissions and permissions only for Unit 1 of the power plant. The operation engineer can only view the work order record information of Unit 1 of the power plant; ② The data access layer reads the work order data within the authorized scope from the work order business database according to the filtering conditions to ensure cross-stack and cross-power plant data isolation; ③ The front-end interaction layer displays the filtered work order data according to the configuration of the custom view.

[0040] Step 5: View Management and Linkage The system supports full lifecycle management of views, including: ① Editing views: Users can modify the configuration of saved views (fields, order, permissions, etc.), and the view configuration library is automatically updated after modification; ② Deleting views: Users can delete views they create. Private views cannot be recovered after deletion, while shared views require editing permissions to delete; ③ Shared view management: Supports single view sharing and batch sharing. When sharing, access users / departments / power plants and viewing / editing permissions can be set (" / " means "or"); ④ Linked management: Custom views are linked with work order filtering conditions, pagination settings, and sorting rules (work order filtering conditions refer to querying and filtering based on fields such as work order number, keywords, work order status, planned start / completion time, and actual start / completion time. Pagination settings can display 10, 50, 100 records per page or a custom number of records. Sorting rules refer to sorting based on a certain field in ascending or descending order). The filtering and sorting results are displayed in real time in the view; views can be exported as independent files, and the view and export functions are linked, with the fields and order of the exported file completely consistent with the view configuration.

[0041] like Figure 6 The diagram illustrates the user's view switching interface. Users can switch between views during their access. Users can switch between multiple authorized views. For example, a shift supervisor in the operations department is authorized to access the operations department view, the planning department view, the safety department view, and the maintenance department view. Figure 4 For each business department's view, the value columnist can use the view switching function to select the corresponding business department's view field information displayed on the current interface.

[0042] Step 6: Dynamic Updates and Adaptation The system's dynamic adaptation includes: ① Field update adaptation: When a new field (such as the "Equipment Health Level" field) is added to the database work order business table of the nuclear power work order system (e.g., the database work order business table is stored in the work order business database), the system reads all field metadata from the business table, automatically includes it in the field selectable list, and displays it according to the professional classification of the set field, without the need for additional development; ② Permission update adaptation: When user permissions change (e.g., a user is changed from an operation position to a safety position), the system's view configuration panel refreshes the custom view list in real time according to the change in position permissions, ensuring that the view is consistent with the user's permissions; ③ Group plant and group reactor adaptation: When users of the nuclear power group add power plants, units, and reactor types through the system's basic data management module, the group plant and group reactor adaptation layer automatically obtains the latest power plant, unit, and reactor type information, and the view configuration can directly select the newly added unit or reactor type as the data range, without the need for system upgrades.

[0043] The following describes how the present invention is implemented using a specific application scenario.

[0044] (I) Overview of Implementation Scenarios This embodiment uses the work order management system of a nuclear power group (including 3 nuclear power plants, 12 units, and 2 types of reactors: 4 pressurized water reactors and 8 heavy water reactors) as the application scenario. The system users cover 8 types of professionals, including maintenance, operation, safety, and technical management, with a total of more than 4,000 users. There are 72 work order fields (38 of which are nuclear power-specific fields). After implementing the technical solution of this invention, integrated management of view customization, access control, and data isolation of multiple plants and reactors can be achieved.

[0045] (II) Specific Implementation Details 1. System Deployment Front-end interaction layer: Deployed on user terminals (computers, tablets), developed using the Vue.js framework, supports responsive layout, and adapts to different terminal sizes; business logic layer is deployed on the nuclear power group's server cluster, developed using the Spring Boot framework, and supports high concurrency (peak concurrency of 500+). Data access layer: MySQL database (master-slave architecture) is used, and the view configuration library, work order business library, and user permission library are deployed independently to ensure data security; Cluster plant / reactor adaptation layer: Adopts a microservice architecture and interfaces with the nuclear power group's existing organizational structure system and access control system to achieve data synchronization.

[0046] 2. Field initialization and optional list generation The system loads 72 nuclear power work order fields, categorized into 8 specialties: ① Maintenance (18 fields: work order number, equipment code, functional location code, SPV type, fault description, fault type, maintenance specialty, unit number, reactor type, isolation permit status, administrative permit status, planned start time, planned completion time, actual start time, actual completion time, maintenance status, maintenance supervisor, maintenance personnel); ② Operations (15 fields: work order number, unit number, reactor type, isolation type, equipment operating status, operating risk level, isolation status, work permit status, operation instruction, operation type, execution completion status, whether decommissioning verification is required, executor, execution time, remarks); ③ The Safety specialty has 18 fields: Work Order Number, Work Order Description, Risk Level, Risk Category, Nuclear Safety Risk Type, Unit Operation Risk Type, Environmental Safety Risk Type, Radiation Safety Risk Type, Work Safety Risk Type, Fire Safety Risk Type, Physical Protection Risk Type, Radiation Dose Value, Isolation Permit Status, Administrative Permit Status, Risk Description, Risk Response Measures, Work Supervisor, and Work Order Status; the other 5 specialties each have 7-9 fields.

[0047] Example: After a maintenance worker (User ID: U1001, Power Plant: Power Plant A, Unit: Unit 1, Reactor Type: Pressurized Water Reactor, Role: Maintenance Engineer) logs in, the system automatically filters out fields such as radiation dose and isolation permits that are not accessible to them, and only displays the 58 fields that they can access, prioritized by maintenance specialty. Different roles have set access permissions for certain fields.

[0048] 3. View Custom Configuration and Saving Maintenance personnel U1001 configure the view as follows: ① Select 10 commonly used fields (Work Order Number, Equipment Code, Maintenance Specialty, Fault Description, Unit Number, Stack Type, Maintenance Team, Planned Duration, Safety Level, Maintenance Status); ② Drag and drop to adjust the order (e.g., Work Order Number → Equipment Code → Fault Description → Maintenance Team → Planned Duration → Safety Level → Unit Number → Stack Type → Maintenance Specialty → Maintenance Status); ③ Customize column widths (e.g., Work Order Number 100px (px represents pixels), Equipment Code 150px, Fault Description 200px); ④ Change the header alias of "Safety Level" to, for example, "Safety Control Level"; ⑤ Name the view, for example, "Maintenance Engineer Exclusive View", and describe it as "Common View for Unit 1 Maintenance Work Orders"; ⑥ Select the permission type as "Private"; ⑦ Select the data range as "Work Orders for Unit 1 under my responsibility".

[0049] After configuration, click Save. The system uses the AES encryption algorithm to convert the view configuration into JSON format, encrypts and stores it in the view configuration library, and associates it with user ID: U1001 and organizational structure ID: O001 (Power Plant A).

[0050] 4. Implementation of permission verification and data isolation (1) Private View Access: After maintenance personnel U1001 logs in, the system automatically loads their default view, "Maintenance Engineer Exclusive View". The data isolation module generates filter conditions: orgId='O001' AND unit='1' ANDreactorType='PWR' AND maintainer='U1001', indicating that all work order data records belonging to Nuclear Power Plant A, Unit 1, pressurized water reactor type, and managed by maintenance personnel U1001 with the number "O001" are filtered out. Only maintenance work orders for Unit 1 (pressurized water reactor) under their management are displayed; work orders for other power plants and units cannot be viewed.

[0051] (2) Shared view access: The safety manager of power plant A (user ID: U2001) creates the "Power Plant A Safety Shared View", sets the permission type to "Power Plant Public", and the data range to "All Unit Work Orders of Power Plant A"; After all safety professionals of power plant A log in, they can view this view. The data isolation module generates the filter condition: orgId='O001', which means: only the data of power plant A with the number 0001 can be queried, and only the work orders of power plant A are displayed; After the user of power plant B logs in, the permission control module verifies that its orgId≠O001, intercepts the access request, and cannot view the shared view.

[0052] 5. View Management and Linkage Implementation (1) View editing: Maintenance personnel U1001 need to add the "Actual construction period" field. Enter the view editing interface, check the "Actual construction period" field, adjust its order to the 6th position, and save. The view configuration library will automatically update the JSON configuration of the view and display the field synchronously the next time it is loaded.

[0053] (2) Batch sharing: The maintenance supervisor of Power Plant A creates a “Power Plant A Maintenance Department Shared View”, which needs to be shared with all maintenance departments of Power Plant A. Through the “Batch Sharing” function, select the “Power Plant A Maintenance Department” role and set the permission to “View”. The system will automatically authorize the view to all users with this role, without the need for individual operation.

[0054] (3) View and export linkage: In the "Power Plant A Safety Shared View", the user filters the work order with "safety level 1" and clicks to export to Excel. The fields and order of the exported file are completely consistent with the view, and there is no need to adjust the field order.

[0055] 6. Dynamic updates and adaptation implementation (1) Field update adaptation: The system adds a "Equipment Health Level" field (a field unique to nuclear power). The system automatically includes it in the field selection list and displays it according to maintenance and technical specialties. Maintenance personnel can select this field in the view configuration without system upgrade.

[0056] (2) Permission update adaptation: The access view permission of maintenance personnel U1001 is adjusted to "responsible for maintenance of Units 1 and 2". The system refreshes its field selection list in real time (no new / deleted fields), and the data range is automatically updated to "work orders of Units 1 and 2". When its default view is loaded, the work order data of Units 1 and 2 is automatically displayed.

[0057] (3) Plant and reactor group adaptation: The nuclear power group adds a new power plant C (2 pressurized water reactor units). The plant and reactor group adaptation layer automatically identifies the organizational structure and unit information of power plant C and updates the data isolation rules. After logging in, users of power plant C can create a dedicated view and select the units of power plant C as the data range to achieve data isolation with other power plants.

[0058] (III) Implementation Results After applying the technical solution of the present invention in this embodiment, the following significant effects are achieved: 1. Efficiency Improvement: Each user does not need to repeatedly configure the view upon login, saving an average of 1-2 minutes per operation. Based on 800 users and each user logging in twice a day, this can save 3200-4000 minutes per day, significantly improving work efficiency.

[0059] 2. Precise Adaptation: Different professionals can obtain exclusive views, key information is directly accessible, and the error rate is significantly reduced. In particular, it solves the pain point of safety professionals filtering radiation-related fields and maintenance personnel filtering equipment and fault-related fields.

[0060] 3. Safety and Compliance: Achieve four-dimensional data isolation across multiple power plants and reactors, with no data leakage across power plants and units, fully meeting the requirements for graded control of nuclear power data security, and passing the nuclear power industry safety and compliance testing.

[0061] 4. Flexible expansion: When adding new fields, generating units, or power plants, no additional development is required. The system automatically adapts, reducing operation and maintenance costs and significantly shortening the adaptation cycle.

[0062] 5. Experience optimization: Features such as drag-and-drop configuration, automatic loading of default view, and real-time refresh are tailored to the operating habits of nuclear power users, resulting in high user satisfaction.

[0063] As can be seen from the above detailed description of the present invention, the technical innovations and beneficial effects of the present invention include: Based on existing technologies and combined with the specific needs of the nuclear power industry, this invention forms the following five core technological innovations, significantly improving technical effectiveness and demonstrating patent novelty and inventiveness: 1. Nuclear Power Scenario-Based View Custom Engine: Specifically adapted to nuclear power-specific fields (reactor type, unit number, safety level, isolation status, radiation risk, maintenance specialty, test category, radiation dose, isolation permit, etc.), supports field display / hiding, sequential drag-and-drop sorting, column width customization, field alignment adjustment, and header alias modification. Fields are categorized into 8 nuclear power specialties, including maintenance, operation, safety, technology, isolation, and testing, accurately matching the personalized needs of different professionals and solving the problem that general custom engines cannot adapt to nuclear power-specific scenarios.

[0064] 2. Multi-level view permissions and lifecycle management: It is the first to create a four-level permission model based on the number of users: "private - team shared - power plant public - cross-power plant authorized", breaking through the limitation of existing technologies that only support two-level permissions of "private / shared"; it supports saving, naming, editing, deleting and setting as default for views, and the default view is automatically loaded upon login, solving the problem of repetitive configuration; shared views support dual permission control of viewing / editing, and private views can only be accessed and edited by the user, perfectly adapting to the hierarchical management and control requirements of nuclear power.

[0065] 3. Dynamic Data Isolation Mechanism for Multiple Power Plants and Reactors: A four-dimensional isolation model is constructed based on the user's power plant, unit, reactor type, and permission role. Views are automatically bound to the corresponding data range during configuration, achieving a triple binding of "view-permission-data." Shared views are isolated by the "power plant to which the creator belongs," preventing users across power plants from viewing them. Private views automatically filter unit and reactor type data outside the user's permission scope, completely resolving data isolation issues in multiple power plant and reactor scenarios and meeting nuclear power data security requirements. When power plant permissions and unit permissions overlap, unit permissions are prioritized for filtering, ensuring accurate data isolation.

[0066] 4. View Configuration Persistence and Intelligent Loading: View configurations (including field selection, display order, column width, permission type, and data range) are stored in the database using AES encryption. The encryption key is associated with and bound to the user ID and organizational structure ID, ensuring independent encryption for different user configurations. Views are decrypted in real-time upon access, and the decrypted data is used only in memory, not persisted to the database, ensuring configuration security. Configuration information is deeply associated with user ID and organizational structure information. When a user logs in, the system automatically matches their default view; if no default view is available, the system's standard view is loaded. View import / export, batch sharing, and batch permission changes are supported, adapting to the management needs of large-scale nuclear power users (thousands of users) and reducing operational costs.

[0067] 5. View Linkage and Dynamic Refresh: Custom views are deeply linked with work order filtering conditions, pagination settings, sorting rules, and export formats. Exported files (Excel, PDF) automatically match view fields without additional adjustments. Real-time view refresh is supported, and the view updates synchronously when work order data is updated. When a nuclear power-specific field is added, the system automatically includes it in the view's optional field list without additional development. When user permissions change, the visible fields and data range of the view are refreshed in real time to ensure consistency between the view and user permissions and business data.

[0068] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention and are not intended to limit it. Although the present invention has been described in detail with reference to the embodiments, those skilled in the art should understand that modifications or equivalent substitutions to the technical solutions of the present invention do not depart from the spirit and scope of the technical solutions of the present invention, and all such modifications or substitutions should be covered within the scope of the claims of the present invention.

Claims

1. A custom view management system for work order lists of nuclear power plant clusters, characterized in that, It includes the front-end interaction layer, business logic layer, data access layer, and cluster factory / cluster adaptation layer; The front-end interaction layer is used to realize the interaction between users and the system, including a view configuration panel, a list display module, and a permission verification component; the view configuration panel is used to configure custom views; the list display module is used to display work order data according to the custom views configured by the view configuration panel; The permission verification component is used for permission verification to intercept unauthorized operations; The business logic layer includes a view customization engine and a configuration persistence module. The view customization engine is used to parse user configuration instructions from the view configuration panel and complete field arrangement. The configuration persistence module is used to encrypt and store the view configuration and retrieve it. The data access layer includes a view configuration library and a work order business library. The view configuration library is used to store encrypted view configuration information from the view configuration panel and associate it with user and organizational structure information. The work order business database is used to store all fields of nuclear power work orders to support the configuration of custom views; The cluster plant / refueling adaptation layer is used to adapt to the cluster plant / refueling management mode of nuclear power plants. It includes: a reactor type identification component, used to identify the reactor type to which the work order belongs; a unit affiliation component, used to determine the unit to which the work order belongs; a power plant isolation component, used to filter and intercept cross-power plant data by matching and verifying the codes of each nuclear power plant with the power plant to which the work order belongs; and a user permission identification component, used to identify the user's permissions for configuring, editing, and accessing views.

2. The system according to claim 1, characterized in that, The front-end interaction layer also includes a view management menu for saving, naming, editing, deleting, setting as default, and sharing of views; The business logic layer also includes an access control module and a data isolation module; The permission control module determines a user's access and editing permissions to the view based on the verification and control of the permission model, and the data isolation module implements data isolation based on the filtering model. The data access layer also includes a user permission library, which stores user information, organizational structure, crew permissions, and role information, providing support for the permission control module to perform permission verification and the data isolation module to perform data isolation.

3. The system according to claim 2, characterized in that, The permission model is a four-level permission model: "private - team shared - power plant public - cross-power plant authorization"; "Private" permission means that a private view can only be accessed and edited by the person who created it; "Group sharing" permission refers to the view shared by users within the same work group; The "Power Plant Public" permission refers to a view shared by users within the same power plant; "Cross-plant authorization" permission refers to a view that a user in one power plant authorizes to a user in another power plant to share. Among them, the "team sharing" permission, "power plant public" permission, and "cross-power plant authorization" permission, the shared view is further subdivided into viewing and editing dual permission control.

4. The system according to claim 2, characterized in that, The filtering model is a four-dimensional filtering model built based on the user's power plant, unit, stack type, and permission role. When configuring the view, the corresponding data range is automatically bound to achieve a triple binding of "view-permission-data".

5. The system according to claim 1, characterized in that, The configuration persistence module uses the AES encryption algorithm to convert the view configuration information into JSON format and then encrypt and store it. The view configuration information includes field selection, display order, column width, table header alias, permission type, and data range.

6. The system according to claim 1, characterized in that, The view customization engine is adapted to nuclear power-specific fields, which include at least one of the following: reactor type, unit number, safety level, isolation status, radiation risk, maintenance specialty, test category, radiation dose, and isolation permit.

7. The system according to claim 1, characterized in that, The cluster plant / cluster adaptation layer also includes a basic data management module; the basic data management module is used to manage data of users, power plants, units, and reactor types, including adding, editing, and deleting data of users, power plants, units, and reactor types, and is used to identify and describe users, power plants, units, and reactor types.

8. A method for managing custom view views of work order lists for nuclear power plant clusters and reactors, characterized in that, Implementing the system according to claim 1 includes the following steps: Step S1, Field Initialization and Optional List Generation: After the user logs into the system, the system combines the user's power plant, unit, reactor type, and role information to load all fields of the nuclear power work order, display them by professional category, filter fields without permission, and generate a field optional list exclusive to the user. Step S2, View Customization Configuration: Users configure custom views through the view configuration panel; Step S3, View Saving and Default Settings: The system encrypts the view information configured by the user and stores it in the view configuration library, and associates it with user and organizational structure information; when the user sets the view as the default view, the system will automatically load the default view through the configuration persistence module when the user logs in subsequently. Step S4, Permission verification and data isolation: When a user accesses the view, the system's permission verification component verifies whether the user has the corresponding permissions. After the permission verification is passed, the work order data is filtered based on the filtering model, and only data within the authorized scope is displayed. Step S5, View Management and Linkage: The front-end interaction layer edits, deletes, shares, and manages the views in batches, and links the views with the work order filtering, pagination display, work order sorting, and export functions; Step S6, Dynamic Update and Adaptation: When the cluster plant and cluster reactor adaptation layer adds a nuclear power field, the front-end interaction layer includes it in the field selectable list; when user permissions change, the front-end interaction layer refreshes the view visible fields and data range in real time; when the cluster plant and cluster reactor adaptation layer adds a power plant, unit, or reactor type, the power plant isolation component of the cluster plant and cluster reactor adaptation layer adapts it to the data isolation rules.

9. The method according to claim 8, characterized in that, Configuring custom views includes: showing or hiding fields, dragging and dropping field order, adjusting column width, modifying header aliases, and setting the view name, permission type, and data range.

10. The method according to claim 9, characterized in that, The permission types include private, team shared, power plant public, and cross-power plant authorization; the data scope includes personal unit, all units in the power plant, specified reactor type, and specified unit. In step S4, the shared view isolates data according to the power plant to which the creator belongs, and users across power plants do not have permission to access it; the private view filters data according to the user's unit and stack type permissions. In step S5, the sharing management includes single view sharing and batch sharing. When sharing, access objects and access permissions are set, and access permissions include viewing or editing the view.

Images