Nuclear power work order management system

Abstract

The application provides a nuclear power work order management system, and relates to the technical field of nuclear power. The nuclear power work order management system comprises a plan management subsystem, the plan management subsystem is configured to obtain maintenance plan data and generate corresponding predicted work orders according to the maintenance plan data; and a work order subsystem, the work order subsystem is configured to receive predicted work order data associated with the predicted work orders sent by the plan management subsystem and generate corresponding real work orders according to the predicted work order data, wherein the plan management subsystem is further configured to receive real work order data associated with the real work orders sent by the work order subsystem, display the predicted work orders and the real work orders, perform business operations on the predicted work orders according to operation instructions, and transmit the operation instructions corresponding to the real work orders to the work order subsystem, and the work order subsystem is further configured to perform business operations on the real work orders according to the operation instructions, the business operations including any one or more of triggering operations, modification operations, deletion operations and export operations.

Description

Technical Field

[0001] This application mainly relates to the field of nuclear power technology, and in particular to a nuclear power work order management system. Background Technology

[0002] In nuclear power production management, planning management is of paramount importance. Planning management encompasses the entire process of nuclear power plant maintenance planning, ensuring the smooth implementation of production plans at each power plant, guaranteeing the safe, orderly, effective, and controllable operation of production activities, and ensuring the safe and stable operation of the units. Planning management includes maintenance plans, and each maintenance plan is managed and executed through work orders.

[0003] With the expansion of nuclear power production scale and the increasing demands for refined management, some related technologies' management systems are unable to meet the requirements for refined management of a large number of maintenance plans, and are unable to effectively differentiate related maintenance data to meet the needs of different users.

[0004] Therefore, there is an urgent need for a reliable and sophisticated nuclear power work order management system. Summary of the Invention

[0005] The technical problem to be solved by this application is to provide a nuclear power work order management system that can reliably and meticulously manage work orders related to maintenance plans.

[0006] To address the aforementioned technical problems, this application provides a nuclear power plant work order management system, comprising: a planning management subsystem configured to acquire maintenance plan data and generate corresponding predicted work orders based on the maintenance plan data; and a work order subsystem configured to receive predicted work order data associated with predicted work orders sent by the planning management subsystem and generate corresponding actual work orders based on the predicted work order data. The planning management subsystem is further configured to receive actual work order data associated with actual work orders sent by the work order subsystem, display predicted and actual work orders, perform business operations on predicted work orders according to operation instructions, and transmit operation instructions corresponding to actual work orders to the work order subsystem. The work order subsystem is further configured to perform business operations on actual work orders according to operation instructions, including any one or more of trigger operations, modification operations, deletion operations, and export operations.

[0007] Optionally, the maintenance plan data includes the initial point time, the call period, and the work order generation cycle. The predicted work orders include the overdue date. The plan management subsystem is also configured to: determine the termination point time based on the initial point time and the call period; and generate the overdue date of each predicted work order corresponding to the maintenance plan data based on the termination point time, the plan start time, and the work order generation cycle.

[0008] Optionally, the predicted work order includes a planned start time, and the planning management subsystem is further configured to: generate the planned start time of each predicted work order based on the termination point time, the initial point time, and the work order generation cycle; and generate the overdue date corresponding to each predicted work order based on the corresponding initial point time and the work order generation cycle.

[0009] Optionally, the maintenance plan data also includes the value of the work order created in advance and the time of the work order created in advance. The predicted work order also includes the actual trigger time. The plan management subsystem is also configured as follows: if the value of the work order created in advance is the first judgment value, then the difference between the plan start date and the time of the work order created in advance is used as the actual trigger time; if the value of the work order created in advance is the second judgment value, then the plan start date is used as the actual trigger time.

[0010] Optionally, the forecast work order also includes the work week, and the planning management subsystem is further configured to: obtain the current year; determine the week number of the year in which the plan starts; and generate the work week based on the current year and the week number.

[0011] Optionally, the maintenance plan data also includes the overhaul cycle. The plan management subsystem is also configured to determine the work order generation cycle based on the overhaul cycle if the value of the work order generation cycle is empty and the value of the overhaul cycle is not empty.

[0012] Optionally, the planning management subsystem is further configured to convert the data to be transmitted to the work order subsystem into a JSON string, perform RSA encryption on the JSON string to generate encrypted data, and transmit the encrypted data to the work order subsystem.

[0013] Optionally, the planning management subsystem includes a call list table, which stores data corresponding to predicted work orders and actual work orders. The planning management subsystem is further configured to display predicted work orders and actual work orders based on the call list table.

[0014] Optionally, the modification operation includes adjusting the planned start date. Both the predicted work order and the actual work order include a planned start time. The planning management subsystem is further configured to: obtain the adjustment operation instruction corresponding to the adjusted planned start date operation; and modify the planned start time of the corresponding predicted work order and / or actual work order according to the adjustment operation instruction.

[0015] Optionally, the adjustment operation instructions include adjustment type, adjustment length, and adjustment unit. The adjustment type includes advance adjustment and delayed adjustment, and the adjustment unit includes days, weeks, months, and years.

[0016] Compared with existing technologies, this application has the following advantages: By setting up independent planning management subsystems and work order subsystems, and transforming work orders into real work orders that maintenance personnel can execute, as well as predicted work orders for managing real work orders, different users can obtain the necessary data in their respective subsystems. This achieves refined management while avoiding interference from unnecessary data, thereby reducing the risk of unauthorized personnel mishandling work order data. Furthermore, through the interaction of specific data between the planning management subsystem and the work order subsystem, managers can obtain and process relevant information on real and predicted work orders through the planning management subsystem. This allows managers to comprehensively manage all work orders, ensuring the reliability and comprehensiveness of work order management. Attached Figure Description

[0017] The accompanying drawings are included to provide a further understanding of this application; they are incorporated into and constitute a part of this application. The drawings illustrate embodiments of this application and, together with this specification, serve to explain the principles of this application. In the drawings: Figure 1 This is a block diagram of a nuclear power plant work order management system according to an embodiment of this application; Figure 2 This is a schematic diagram of the internal data processing of the nuclear power plant work order management system; Figure 3 This is a schematic diagram of the business operation interface; and Figure 4 This is a diagram illustrating the modification of the user interface. Detailed Implementation

[0018] To more clearly illustrate the technical solutions of the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are merely some examples or embodiments of this application. For those skilled in the art, these drawings can be applied to other similar scenarios without creative effort. Unless obvious from the context or otherwise specified, the same reference numerals in the drawings represent the same structures or operations.

[0019] As indicated in this application and claims, unless the context clearly indicates otherwise, the words "a," "an," "an," and / or "the" are not specifically singular and may include plural forms. Generally speaking, the terms "comprising" and "including" only indicate the inclusion of explicitly identified steps and elements, which do not constitute an exclusive list, and the method or apparatus may also include other steps or elements.

[0020] Unless otherwise specifically stated, the relative arrangement, numerical expressions, and values ​​of the components and steps described in these embodiments do not limit the scope of this application. It should also be understood that, for ease of description, the dimensions of the various parts shown in the drawings are not drawn to actual scale. Techniques, methods, and devices known to those skilled in the art may not be discussed in detail, but where appropriate, such techniques, methods, and devices should be considered part of the specification. In all examples shown and discussed herein, any specific values ​​should be interpreted as merely exemplary and not as limitations. Therefore, other examples of exemplary embodiments may have different values. It should be noted that similar reference numerals and letters in the following drawings denote similar items; therefore, once an item is defined in one drawing, it need not be further discussed in subsequent drawings.

[0021] Furthermore, it should be noted that the use of terms such as "first" and "second" to define components is merely for the purpose of distinguishing the corresponding components. Unless otherwise stated, these terms have no special meaning and therefore should not be construed as limiting the scope of protection of this application. In addition, although the terminology used in this application is selected from commonly known and used terms, some terms mentioned in this application's specification may have been chosen by the applicant according to his or her judgment, and their detailed meanings are explained in the relevant sections of this description. Moreover, this application should be understood not only through the actual terms used, but also through the meaning implied by each term.

[0022] Reference Figure 1 One embodiment of this application discloses a nuclear power plant work order management system 100. This system is used to generate and manage predicted work orders and actual work orders. Figure 1 As shown, the nuclear power plant work order management system 100 includes a planning management subsystem 11 and a work order subsystem 12. The planning management subsystem 11 is configured to acquire maintenance plan data and generate corresponding predicted work orders based on the maintenance plan data. The work order subsystem 12 is configured to receive predicted work order data associated with the predicted work orders sent by the planning management subsystem 11 and generate corresponding actual work orders based on the predicted work order data. The planning management subsystem 11 is also configured to receive actual work order data associated with the actual work orders sent by the work order subsystem 12, display the predicted work orders and the actual work orders, perform business operations on the predicted work orders according to operation instructions, and transmit the operation instructions corresponding to the actual work orders to the work order subsystem 12. The work order subsystem 12 is also configured to perform the business operations on the actual work orders according to the operation instructions. The business operations include any one or more of trigger operations, modification operations, deletion operations, and export operations.

[0023] It should be noted that actual work orders include information such as the maintenance object and the corresponding maintenance operation, thereby assisting users of the work order subsystem 12 (i.e., work order users) in executing the corresponding maintenance plan. Furthermore, predicted work orders contain time information associated with actual work orders, allowing users of the planning management subsystem 11 (i.e., management users) to adjust the generation node of actual work orders through predicted work orders, thus controlling the work rhythm of subsequent maintenance operations. Therefore, the nuclear power work order management system 100 subdivides work orders into predicted work orders and corresponding actual work orders. This allows for the adjustment of specific maintenance time nodes based on actual conditions when facing long-term maintenance plans, using predicted work orders, while ensuring the effectiveness and accuracy of maintenance operations through actual work orders. Thus, the nuclear power work order management system 100 can achieve refined management of a large number of maintenance plans, enabling different users to obtain necessary information according to their needs while preventing irrelevant users from obtaining or modifying the information of corresponding work orders, thereby reliably managing work order information. Understandably, since the planning management subsystem 11 can display both forecast and actual work orders, and can perform business operations on forecast work orders, as well as transmit operation instructions for actual work orders to the work order subsystem 12, management users can globally manage all actual and forecast work orders, thereby achieving overall management of all work orders and ensuring the reliability and comprehensiveness of work order management.

[0024] Further integration Figure 2 Regarding the generation of maintenance plan data, in this embodiment, the plan management subsystem 11 is further configured to generate initial maintenance plan data based on maintenance outline data, and obtain maintenance plan data based on the initial maintenance plan data and supplementary maintenance plan data. It should be noted that in this embodiment, the maintenance outline data is input to the plan management subsystem 11 by the management user, and each maintenance outline data can generate one or more initial maintenance plan data, meaning each initial maintenance plan data corresponds to a different maintenance object. Furthermore, in this embodiment, supplementary maintenance plan data is input to the plan management subsystem 11 by the management user, and the supplementary maintenance plan data is used to complete the maintenance plan data based on the initial maintenance plan data. It is understood that in this embodiment, the plan management subsystem 11 includes a corresponding display interface and input port, thereby facilitating the management user to confirm the information of the plan management subsystem 11 and input information into the plan management subsystem 11.

[0025] Continue to refer to Figure 2In this embodiment, the plan management subsystem 11 is configured to generate one or more predicted work orders based on the generated maintenance plan data. Furthermore, the plan management subsystem 11 is further configured to perform mandatory field verification on the maintenance plan data in response to a request to generate a predicted work order; if the mandatory field verification is successful, a predicted work order is generated based on the maintenance plan data; if the mandatory field verification fails, a prompt message is generated. Specifically, the mandatory field verification is successful when one or more of the following in the maintenance plan data—maintenance plan category, maintenance plan description, functional location code, work order type, job type, and responsible department—have corresponding values. For example, the prompt message includes "A mandatory field is missing; please check and try again." It should be noted that the maintenance plan corresponding to the maintenance plan data can be a long-term maintenance plan, thus requiring multiple maintenance operations on the maintenance object throughout the maintenance cycle, with each maintenance operation corresponding to a predicted work order.

[0026] In this embodiment, the maintenance plan data includes an initial point time, a call deadline, and a work order generation cycle, and the predicted work orders include an overdue date. Based on this, the plan management subsystem 11 is further configured to: determine an end point time based on the initial point time and the call deadline; and generate the overdue date for each predicted work order corresponding to the maintenance plan data based on the end point time, the initial point time, and the work order generation cycle. Further, the predicted work order includes a plan start time; correspondingly, the plan management subsystem 11 is further configured to: generate the plan start time for each predicted work order based on the end point time, the initial point time, and the work order generation cycle; and for each predicted work order, generate the overdue date corresponding to the predicted work order based on the corresponding initial point time and the work order generation cycle.

[0027] Specifically, in this embodiment, the time period corresponding to the call duration is converted into days, i.e., the call duration days. Based on this, the initial time is added to the call duration days to obtain the termination time. For example, if the call duration corresponds to 3 weeks, and the initial time is January 1st, 00:00:00 milliseconds, then the termination time is 3 weeks from January 1st. 7 = 21 days, meaning the termination time is January 22nd, 00:00:00. It should be noted that the unit of time for the call period also includes days, months, and years, which are converted to the call period according to the above rules. In this embodiment, the time unit for the work order generation cycle is weeks. The planning management subsystem 11 is also configured to determine whether the number of days corresponding to the difference between the termination time and the initial time is greater than the number of days corresponding to the work order generation cycle. If the determination result is yes, then the initial time is used as the planned start time of the first predicted work order, and the planned start time of each subsequent predicted work order is determined at intervals corresponding to the number of days corresponding to the work order generation cycle. The planned start time of the last predicted work order is earlier than the termination time. If the determination result is no, then only one predicted work order with the initial time as the planned start time is generated. In this embodiment, the calculation expression for the overdue date corresponding to each predicted work order is: a = b + c d, where a is the overdue date corresponding to the predicted work order, b is the planned start time corresponding to the predicted work order, d is the work order generation cycle corresponding to the predicted work order, and c is an adjustment parameter. Preferably, the value of c is 0.25.

[0028] In this embodiment, the overdue date is calculated by the planning management subsystem 11 and used as the corresponding data for the predicted work order. This allows management users to confirm the current status of each predicted work order, thereby determining whether any predicted work orders have exceeded their overdue date and have not yet triggered the generation of corresponding actual work orders. This enables timely processing of predicted work orders with serious anomalies, preventing severe impacts on the overall maintenance plan. Therefore, the overdue date allows the nuclear power work order management system 100 to effectively manage a large number of predicted work orders corresponding to a large number of maintenance plans, ensuring that actual work orders are generated on time and used for maintenance operations, thereby improving the reliability and accuracy of nuclear power work order management.

[0029] Continue to refer to Figure 1In this embodiment, the maintenance plan data also includes a pre-creation work order value and a pre-creation work order time, and the predicted work order also includes an actual trigger time. Correspondingly, the plan management subsystem 11 is further configured to: if the pre-creation work order value is a first judgment value, then the difference between the plan start date and the pre-creation work order time is used as the actual trigger time; if the pre-creation work order value is a second judgment value, then the plan start date is used as the actual trigger time. It is understood that management users can set the pre-creation work order value and pre-creation work order time corresponding to each maintenance plan through the plan management subsystem 11, thereby setting the automatic trigger time for predicted work orders. That is, after determining that the current time is not earlier than the actual trigger time, the plan management subsystem 11 transmits the predicted work order data of the corresponding predicted work order to the work order subsystem 12 to generate the actual work order corresponding to the predicted work order. In this embodiment, the planning management subsystem 11 can use the actual trigger time as the basis for the timed trigger instruction. That is, it determines whether the current time is earlier than the actual trigger time of the predicted work order each day, thereby determining whether to automatically promote the generation of the corresponding real work order for the predicted work order.

[0030] Therefore, by setting the advance creation value, advance creation time, and actual trigger time in this embodiment, management users do not need to manually trigger the generation of corresponding real work orders for each predicted work order in the planning management subsystem 11. This significantly reduces manual management costs when dealing with a large number of predicted work orders, while ensuring the accuracy and reliability of the time for generating real work orders from predicted work orders. Furthermore, since management users can adjust the corresponding actual trigger time by setting the advance creation value and advance creation time, they can adjust the generation time of real work orders to a certain extent without modifying the maintenance plan data. This allows for adaptive adjustment of the generation time of corresponding real work orders for specific situations, enabling subsequent maintenance operations to be carried out according to the actual situation, thus improving the flexibility and adaptability of work order management.

[0031] Continue to refer to Figure 1The predicted work order also includes a work week. Correspondingly, the planning management subsystem 11 is configured to: obtain the current year; determine the week number of the year in which the plan starts; and generate the work week based on the current year and the week number. Specifically, the planning management subsystem selects the last two digits of the current year as the year value, then determines the week number based on the plan start time, and appends 0s before week numbers less than 10 to form a week value. Finally, the year value and week value are combined to obtain the work week. For example, if the current year is 2026 and the plan start time is January 3, 2026, then the corresponding year value is 26, and the corresponding week value is 01, resulting in work week 2601. The first day of each week corresponds to Monday, and the first week of the year must occupy at least 4 days in that year.

[0032] Through the above settings, within a weekly planning cycle, management users can easily and quickly compare the current work week with the work week of the predicted work orders, thereby quickly and accurately determining whether the corresponding predicted work orders are in a state requiring prompt triggering. Furthermore, by statistically analyzing the work weeks of each predicted work order, the number of maintenance operations that need to be performed within the same work week can be determined. This helps management users adjust the trigger time for generating actual work orders from the corresponding predicted work orders, optimizing the work rhythm of subsequent work order users in actually executing each actual work order. Therefore, by setting work weeks, the nuclear power work order management system 100 can manage a large number of predicted work orders quickly and effectively, while also optimizing the overall work rhythm of maintenance operations, enabling work order users to execute various maintenance plans more efficiently and improving maintenance effectiveness.

[0033] In some scenarios, nuclear power equipment has both routine maintenance plans and corresponding overhaul plans. However, the routine maintenance plans and overhaul plans differ in their cycles, resulting in differences in the content of predicted work orders. This makes the existing nuclear power work order management system ineffective in ensuring compatibility between work orders corresponding to routine maintenance plans and overhaul maintenance. To address this, the maintenance plan data in this embodiment also includes the overhaul cycle. Accordingly, the plan management subsystem 11 is configured to: determine the work order generation cycle based on the overhaul cycle if the value of the work order generation cycle is empty and the value of the overhaul cycle is not empty. Specifically, in this embodiment, the plan management subsystem 11 is further configured to extract related values ​​from the data corresponding to the overhaul cycle; convert the related values ​​into days to obtain the work order generation cycle. This embodiment simultaneously sets the work order generation cycle and the overhaul cycle, ensuring that the work order generation cycle corresponds to the routine maintenance plan and the overhaul cycle corresponds to the overhaul plan. Based on this, by extracting and converting the related values ​​in the overhaul cycle, and using the converted related values ​​as the work order generation cycle, the predicted work orders corresponding to the overhaul cycle can meet the overhaul plan. Therefore, the planning management subsystem 11 of this embodiment is compatible with both ordinary maintenance plans and overhaul plans, thereby achieving comprehensive management of work orders for various maintenance plans.

[0034] Continue to refer to Figure 2 For the generated predicted work orders, in this embodiment, the planning management subsystem 11 is further configured to send the predicted work order data associated with the corresponding predicted work order to the work order subsystem 12 according to a timed trigger instruction or a manual trigger instruction, thereby enabling the work order subsystem 12 to generate the actual work order corresponding to the predicted work order. The timed trigger instruction is a preset instruction within the planning management subsystem 11, and the manual trigger instruction is an instruction input by the management user into the planning management subsystem 11. That is, in this embodiment, the planning management system 11 can perform trigger operations to generate the actual work order corresponding to the predicted work order through both manual setting and automatic system execution.

[0035] Regarding data transmission between the planning management subsystem 11 and the work order subsystem 12, in this embodiment, the planning management subsystem 11 is further configured to convert the data to be transmitted to the work order subsystem 12 into a JSON string, perform RSA encryption on the JSON string to generate encrypted data, and then transmit the encrypted data to the work order subsystem 12. It can be understood that through the above settings, secure data transmission can be achieved even when the planning management subsystem 11 and the work order subsystem 12 are independent of each other, thereby preventing data leakage from posing a safety hazard to nuclear power equipment. Furthermore, in this embodiment, the data transmitted from the work order subsystem 12 to the planning management subsystem 11 is also processed in the above manner to ensure the security of data interaction. That is, the work order subsystem 12 is further configured to convert the data to be transmitted to the planning management subsystem 11 into a JSON string, perform RSA encryption on the JSON string to generate encrypted data, and then transmit the encrypted data to the planning management subsystem 11.

[0036] Continue to refer to Figure 2 For generated real work orders, the work order subsystem transmits the corresponding real work order data to the planning management subsystem, enabling management users in the planning management subsystem to obtain the relevant information of the real work orders, thereby ensuring the management users' overall management of all work order statuses. In this embodiment, the planning management subsystem 11 includes a call list table. The call list table stores the data corresponding to the predicted work orders and the real work orders. Accordingly, the planning management subsystem 11 is further configured to display the predicted work orders and the real work orders according to the call list table. It can be understood that the planning management subsystem 11 stores the predicted work orders and real work order data required by the management users in the call list table, thereby ensuring that management users have appropriate permissions while facilitating the execution of relevant business operations.

[0037] Regarding the method of managing users to perform business operations, in this embodiment, the plan management subsystem 11 is further configured to display a business operation interface and receive operation instructions through the business operation interface. For example, refer to... Figure 3The business operation interface 20 includes a start time input area 201, an end time input area 202, a maintenance plan code input area 203, a query button 204, a batch trigger button 205, a batch delete button 206, a batch modify button 207, and a work order information display area 208. The system includes the following subsystems: Start Time Input Area 201 for managing user-inputted start times; End Time Input Area 202 for managing user-inputted end times; Maintenance Plan Code Input Area 203 for managing the maintenance plan codes corresponding to user-inputted maintenance plan data; Query Button 204 for instructing the planning management subsystem 11 to display the corresponding predicted and actual work orders in the work order information display area 208 based on one or more of the input start time, end time, and maintenance plan codes; Batch Trigger Button 205 for instructing the planning management subsystem 11 to trigger each predicted work order further selected by the user in the work order information display area 208, thereby achieving batch triggering; Batch Delete Button 206 for instructing the planning management subsystem 11 to delete each predicted and actual work orders further selected by the user in the work order information display area 208, thereby achieving batch deletion; and Batch Modify Button 207 for instructing the planning management subsystem 11 to modify each predicted and actual work order further selected by the user in the work order information display area 208, thereby achieving batch modification. In addition, the business operation interface 20 in this embodiment may also include a batch export button, so that the various predicted work orders and actual work orders further selected by the management user in the work order information display area 208 of the planning management subsystem 11 can be exported in batch.

[0038] It should be noted that, in this embodiment, for the business operations of predicted work orders, the planning management subsystem 11 modifies the corresponding data in the call list table to implement the corresponding business operations, and transmits the relevant information to the work order subsystem 12 so that the data related to predicted work orders in the work order subsystem 12 is updated synchronously. Correspondingly, for the business operations of actual work orders, the planning management subsystem 11 sends the corresponding operation instructions to the work order subsystem 12. After the work order subsystem 12 completes the corresponding business operation, it receives the relevant data of the actual work orders returned by the work order subsystem and updates the call list table, thereby enabling the management user in the planning management subsystem 11 to confirm that the corresponding business operations of the actual work orders have been effectively executed. Through the above settings, the management user can perform corresponding business operations on actual and predicted work orders without using the work order subsystem 12, thereby giving the management user appropriate operation permissions, improving the comprehensiveness and effectiveness of work order information management, and making work order management more refined and reliable.

[0039] The modification operation in this embodiment includes adjusting the planned start date, and both the predicted work order and the actual work order include a planned start time. Accordingly, the planning management subsystem 11 is further configured to: obtain the adjustment operation instruction corresponding to the adjusted planned start date operation; and modify the planned start time of the corresponding predicted work order and / or actual work order according to the adjustment operation instruction. The adjustment operation instruction includes adjustment type, adjustment length, and adjustment unit. The adjustment type includes advance adjustment and postponement adjustment, and the adjustment unit includes days, weeks, months, and years. Specifically, refer to... Figure 4 In this embodiment, the planning management subsystem 11 includes a modification operation interface 30. The modification operation interface 30 includes an adjustment type input area 301, an adjustment length input area 302, an adjustment unit input area 303, a preview button 304, and a modification work order information display area 305. Specifically, the adjustment type input area 301 manages user-inputted adjustment types, the adjustment length input area 302 manages user-inputted adjustment lengths, the adjustment unit input area 303 manages user-inputted adjustment units, and the preview button 304 enables the planning management subsystem 11 to adjust the planned start times of each real and predicted work order in the modification work order information display area 305 according to the input adjustment operation command, and displays the adjusted preview results through a new interface. The modification work order information display area 305, in response to saving the preview results, displays the original and adjusted planned start times of each real and predicted work order. For example, if the original start date of the plan was January 7, 2026, the adjustment type was a postponement adjustment, the adjustment length was 3 days, and the adjustment unit was days, then the corresponding adjusted start date of the plan would be January 10, 2026.

[0040] Through the above settings, management users can conveniently and quickly adjust the planned start times of multiple real and predicted work orders in a unified manner. This avoids the omissions that may occur when adjusting real and predicted work orders one by one, while also improving management efficiency. Therefore, by supporting batch operations and retrieval operations through the planning management subsystem, real and predicted work orders with the same characteristics or related relationships can be processed by management users simultaneously, ensuring the synchronization and accuracy of associated information. This, in turn, improves management efficiency and accuracy when dealing with a large number of work orders.

[0041] The basic concepts have been described above. Obviously, for those skilled in the art, the above disclosure is merely illustrative and does not constitute a limitation of this application. Although not explicitly stated herein, those skilled in the art may make various modifications, improvements, and corrections to this application. Such modifications, improvements, and corrections are suggested in this application, and therefore remain within the spirit and scope of the exemplary embodiments of this application.

[0042] Furthermore, this application uses specific terms to describe embodiments of the application. For example, "an embodiment," "one embodiment," and / or "some embodiments" refer to a particular feature, structure, or characteristic related to at least one embodiment of the application. Therefore, it should be emphasized and noted that "an embodiment," "one embodiment," or "an alternative embodiment" mentioned twice or more in different locations in this specification do not necessarily refer to the same embodiment. In addition, certain features, structures, or characteristics in one or more embodiments of the application can be appropriately combined.

[0043] Similarly, it should be noted that, in order to simplify the description of the present application and thus aid in the understanding of one or more embodiments, the foregoing description of the embodiments of the present application sometimes combines multiple features into a single embodiment, drawing, or description thereof. However, this disclosure method does not imply that the subject matter of the present application requires more features than those mentioned in the claims. In fact, the embodiments contain fewer features than all the features of the single embodiments disclosed above.

[0044] Although this application has been described with reference to specific embodiments, those skilled in the art should recognize that the above embodiments are only used to illustrate this application, and various equivalent changes or substitutions can be made without departing from the spirit of this application. Therefore, any changes or modifications to the above embodiments within the essential spirit of this application will fall within the scope of the claims of this application.

Claims

1. A nuclear power plant work order management system, characterized in that, include: A planning management subsystem is configured to acquire maintenance plan data and generate corresponding predicted work orders based on the maintenance plan data. A work order subsystem is configured to receive predicted work order data associated with the predicted work orders sent by the planning management subsystem, and generate corresponding actual work orders based on the predicted work order data. The planning management subsystem is also configured to receive real work order data associated with the real work order sent by the work order subsystem, display the predicted work order and the real work order, perform business operations on the predicted work order according to operation instructions, and transmit the operation instructions corresponding to the real work order to the work order subsystem. The work order subsystem is also configured to perform the business operation on the real work order according to the operation instruction. The business operation includes any one or more of the following: trigger operation, modification operation, deletion operation, and export operation.

2. The nuclear power plant work order management system as described in claim 1, characterized in that, The maintenance plan data includes the initial point time, call deadline, and work order generation cycle; the predicted work orders include overdue dates; and the plan management subsystem is further configured as follows: The termination point time is determined based on the initial point time and the call duration; The overdue dates of each predicted work order corresponding to the maintenance plan data are generated based on the termination point time, the initial point time, and the work order generation cycle.

3. The nuclear power plant work order management system as described in claim 2, characterized in that, The predicted work order includes a planned start time, and the planning management subsystem is further configured as follows: The planned start time of each of the predicted work orders is generated based on the termination point time, the initial point time, and the work order generation cycle. For each predicted work order, the overdue date corresponding to the predicted work order is generated based on the corresponding planned start time and the work order generation cycle.

4. The nuclear power plant work order management system as described in claim 3, characterized in that, The maintenance plan data also includes the value of pre-created work orders and the time of pre-created work orders. The predicted work orders also include the actual trigger time. The plan management subsystem is further configured as follows: If the value of the pre-created work order is the first judgment value, then the difference between the planned start date and the pre-created work order time is taken as the actual trigger time; If the value of the pre-created work order is the second judgment value, then the planned start date is taken as the actual trigger time.

5. The nuclear power plant work order management system as described in claim 3, characterized in that, The predicted work order also includes a work week, and the planning management subsystem is further configured as follows: Get the current year; Determine the week number in the year in which the plan begins; The work week is generated based on the current year and the week number.

6. The nuclear power plant work order management system as described in claim 2, characterized in that, The maintenance plan data also includes overhaul cycles, and the plan management subsystem is further configured as follows: If the value of the work order generation cycle is empty and the value of the overhaul cycle is not empty, then the work order generation cycle is determined based on the overhaul cycle.

7. The nuclear power plant work order management system as described in claim 1, characterized in that, The planning management subsystem is further configured to convert the data to be transmitted to the work order subsystem into a JSON string, perform RSA encryption on the JSON string to generate encrypted data, and transmit the encrypted data to the work order subsystem.

8. The nuclear power plant work order management system as described in claim 1, characterized in that, The planning management subsystem includes a call list table, which stores data corresponding to the predicted work orders and the actual work orders. The planning management subsystem is further configured to display the predicted work orders and the actual work orders according to the call list table.

9. The nuclear power plant work order management system as described in claim 1, characterized in that, The modification operation includes adjusting the planned start date. Both the predicted work order and the actual work order include a planned start time. The planning management subsystem is further configured as follows: Obtain the adjustment operation instruction corresponding to the start date of the adjustment plan; Modify the planned start time of the corresponding predicted work order and / or actual work order according to the adjustment operation instruction.

10. The nuclear power plant work order management system as described in claim 9, characterized in that, The adjustment operation instructions include adjustment type, adjustment length, and adjustment unit. The adjustment type includes advance adjustment and delayed adjustment, and the adjustment unit includes days, weeks, months, and years.

Images