Management systems and methods for nuclear power plant operation processes

Abstract

This application provides a management system and method for nuclear power plant operation processes, relating to the field of nuclear power plant operation and maintenance technology. The management system for nuclear power plant operation processes includes: a data support module storing multiple inherent state sequences corresponding to various operation scenarios, each inherent state sequence comprising multiple sequentially set inherent states; a user application module for receiving template configuration instructions; and a configuration and driving module including a process configuration unit, which generates a corresponding state flow template based on the template configuration instructions and the corresponding inherent state sequences. The state flow template includes multiple sequentially connected custom node groups, each custom node group of the state flow template corresponding to each inherent state of the corresponding inherent state sequence. The configuration and driving module stores the business rules corresponding to the inherent states, generates process instances corresponding to the state flow templates, and advances process instances according to the business rules.

Description

Technical Field

[0001] This application mainly relates to the field of nuclear power plant operation and maintenance technology, and in particular to a management system and method for nuclear power operation processes. Background Technology

[0002] In existing business process management systems, state machines are a mainstream technical solution. State machines focus on the transitions between states, with state transitions triggered by external events, and are suitable for describing simple, deterministic state change processes.

[0003] Production management during nuclear power plant operation is extremely important, requiring numerous procedural operations. Therefore, state machines can be applied to manage the operational processes of nuclear power plants. However, in scenarios involving the joint management of multiple nuclear reactors across multiple nuclear power plants—a cluster of plants and reactors scenario—the management methods of different nuclear power plants vary, leading to potential differences in the operational processes for each reactor. State machines are generally rigid structures that struggle to support dynamic configuration. Once deployed, they cannot provide tailored operational processes for newly introduced reactors in new nuclear power plants, or efficiently accommodate the operational requirements of various reactors.

[0004] Therefore, there is an urgent need for a management system and method that can be applied to the nuclear power operation process in the scenario of multiple plants and multiple reactors. Summary of the Invention

[0005] The technical problem to be solved by this application is to provide a management system and method for nuclear power plant operation processes, which solves the problem that existing state machines cannot meet the operation process requirements in the scenario of multiple plants and multiple reactors.

[0006] To address the aforementioned technical problems, this application provides a management system for nuclear power plant operation processes, suitable for managing the operation processes of multiple nuclear reactors in multiple nuclear power plants. The system includes: a data support module storing inherent state sequences corresponding to multiple operation scenarios, each inherent state sequence comprising multiple sequentially set inherent states, constructed based on the operational business requirements data of multiple nuclear reactors; a user application module for receiving template configuration instructions corresponding to nuclear reactors in different operation scenarios; and a configuration and driving module including a process configuration unit for generating corresponding state flow templates based on template configuration instructions and corresponding inherent state sequences. Each state flow template includes multiple sequentially connected custom node groups, with each custom node group corresponding to a specific inherent state in the inherent state sequence. Each custom node group includes at least one custom node. The configuration and driving module stores business rules corresponding to inherent states, generates process instances corresponding to state flow templates, and advances process instances based on business rules.

[0007] Optionally, a process instance includes multiple entry states, each corresponding to a custom node in the corresponding state flow template. The user application module is also used to receive instance event instructions corresponding to the process instance. The configuration and driver module also includes: a rule executor, which stores business rules corresponding to inherent states; and a state transition engine, which transmits the current entry state and instance event instructions corresponding to the process instance to the rule executor. The rule executor generates feedback results based on the instance event instructions, the current entry state, and the business rules. The state transition engine also updates the current entry state of the process instance based on the feedback results.

[0008] Optionally, the data support module includes a state flow trace table, which is configured to store the current entry state of the process instance. The state transition engine is also used to update the current entry state of the corresponding process instance in the state flow trace table based on the feedback results.

[0009] Optionally, the rule executor is also used to determine whether there is a corresponding business rule for the custom node corresponding to the current entry status. If the determination result is yes, the business rule corresponding to the current entry status is executed.

[0010] Optionally, the business rules include mandatory business rules and optional business rules. The user application module includes a rule configuration interface. The user application module is also used to display optional business rules through the rule configuration interface and use the selected optional business rules as the specific business rules of the corresponding nuclear reactor. The rule executor is used to execute the mandatory business rules and specific business rules corresponding to the current entry status.

[0011] Optionally, the user application module includes an instance configuration interface. The user application module is also used to display the inherent state sequence through the instance configuration interface and receive the template configuration instruction corresponding to the inherent state sequence, transmit the template configuration instruction to the process configuration unit, receive the state flow template sent by the process configuration unit, and display the state flow template through the instance configuration interface.

[0012] Optionally, the running scenario includes an isolation scenario. The multiple inherent states in the inherent state sequence corresponding to the isolation scenario include a first inherent state and a second inherent state connected in sequence. The business rules corresponding to the first inherent state include: performing conflict verification on the process instance before the process instance changes from the current first item state to the second item state. The first item state corresponds to the last custom node in the state flow template that corresponds to the first inherent state, and the second item state corresponds to the first custom node in the state flow template that corresponds to the second inherent state.

[0013] Optionally, the running scenario includes an isolation scenario. The multiple inherent states in the inherent state sequence corresponding to the isolation scenario include an isolation execution inherent state, an intermediate inherent state, and an isolation release inherent state. The intermediate inherent state and the isolation release inherent state are connected sequentially. The state flow template corresponding to the isolation scenario includes multiple isolation execution nodes, each corresponding to an isolation execution inherent state. The business rules corresponding to the intermediate inherent state include: when the process instance changes to the third item state, multiple custom nodes corresponding to the release isolation inherent state are generated based on all isolation execution nodes. The third item state corresponds to the last custom node in the state flow template that corresponds to the intermediate inherent state.

[0014] Optionally, the data support module includes a state flow configuration table, which is configured to store inherent state sequences and state flow templates.

[0015] To address the aforementioned technical problems, this invention provides a management method for nuclear power plant operation processes, suitable for managing the operation processes of multiple nuclear reactors in multiple nuclear power plants. The management method includes: constructing multiple inherent state sequences corresponding to different operation scenarios based on the operational business requirement data of multiple nuclear reactors, each inherent state sequence including multiple sequentially set inherent states; storing the inherent state sequences; acquiring and storing the business rules corresponding to the inherent states; acquiring template configuration instructions corresponding to the nuclear reactors under different operation scenarios; generating corresponding state flow templates based on the template configuration instructions and the corresponding inherent state sequences, each state flow template including multiple sequentially connected custom node groups, each custom node group of the state flow template corresponding to each inherent state of the corresponding inherent state sequence, each custom node group including at least one custom node; generating process instances corresponding to the state flow templates; and advancing the process instances according to the business rules.

[0016] Optionally, a process instance includes multiple entry states, and each entry state corresponds one-to-one with a custom node in the corresponding state flow template. The steps for advancing the process instance according to business rules further include: obtaining the instance event instruction corresponding to the process instance; generating feedback results based on the instance event instruction, the current entry state corresponding to the process instance, and the business rules; and updating the current entry state of the process instance based on the feedback results.

[0017] Compared with existing technologies, this application has the following advantages: It stores inherent state sequences corresponding to multiple operating scenarios through a data support module, and obtains template configuration instructions corresponding to a specific nuclear reactor and a specific operating scenario through a user application module. Based on this, a configuration and drive module generates a state flow template for the nuclear reactor in the operating scenario according to the template configuration instructions and the corresponding inherent state sequences. Furthermore, the configuration and drive module drives the process instances generated from the state flow template according to the business rules corresponding to the inherent states, thereby enabling the management of the operating process of any nuclear reactor in any scenario. Attached Figure Description

[0018] 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 management system for a nuclear power plant operation process according to an embodiment of this application; Figure 2 This is a schematic diagram showing the correspondence between the inherent state sequence A and the state flow template ABC; Figure 3 This is a flowchart illustrating a management method for nuclear power plant operation according to an embodiment of this application; and Figure 4 yes Figure 3 A flowchart illustrating the sub-step of step S7. Detailed Implementation

[0019] 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.

[0020] 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.

[0021] 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.

[0022] In the description of this application, it should be understood that the orientation or positional relationship indicated by directional terms such as "front, back, up, down, left, right", "horizontal, vertical, horizontal" and "top, bottom" is usually based on the orientation or positional relationship shown in the accompanying drawings, and is only for the convenience of describing this application and simplifying the description. Unless otherwise stated, these directional terms do not indicate or imply that the device or element referred to must have a specific orientation or be constructed and operated in a specific orientation, and therefore should not be construed as a limitation on the scope of protection of this application; the directional terms "inner" and "outer" refer to the inner and outer contours relative to the outline of each component itself.

[0023] For ease of description, spatial relative terms such as "above," "on top of," "on the upper surface of," "above," etc., are used herein to describe the spatial positional relationship of a device or feature as shown in the figures to other devices or features. It should be understood that spatial relative terms are intended to encompass different orientations in use or operation beyond the orientation of the device as described in the figures. For example, if the device in the figures were inverted, a device described as "above" or "on top of" other devices or structures would subsequently be positioned as "below" or "under" other devices or structures. Thus, the exemplary term "above" can include both "above" and "below." The device may also be positioned in other different ways (rotated 90 degrees or in other orientations), and the spatial relative descriptions used herein will be interpreted accordingly.

[0024] 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.

[0025] It should be understood that when a component is referred to as "on another component," "connected to another component," "coupled to another component," or "in contact with another component," it can be directly on, connected to, coupled to, or in contact with that other component, or there may be an intervening component. In contrast, when a component is referred to as "directly on another component," "directly connected to," "directly coupled to," or "directly in contact with" another component, there is no intervening component. Similarly, when a first component is referred to as "electrically contacting" or "electrically coupled to" a second component, there is an electrical path between the first and second components that allows current to flow. This electrical path may include capacitors, coupled inductors, and / or other components that allow current to flow, even if there is no direct contact between the conductive components.

[0026] Reference Figure 1 One embodiment of this application proposes a nuclear power plant operation process management system 100, which is suitable for managing the operation processes of multiple nuclear reactors in multiple nuclear power plants. For example... Figure 1 As shown, the management system 100 includes a data support module 11, a user application module 12, and a configuration and driving module 13. In this embodiment, the data support module 11 is used to store data related to the operation process, the user application module 12 is used to interact with the user, and the configuration and driving module 13 is used to generate and advance process instances associated with the operation process based on the data stored in the data support module 11 and the interaction instructions received by the user application module 12.

[0027] Continue to refer to Figure 1 Specifically, the data support module 11 stores multiple inherent state sequences corresponding to different operating scenarios. Each inherent state sequence includes multiple sequentially set inherent states. In this embodiment, the inherent state sequences are constructed based on the operational business requirement data of multiple nuclear reactors. More specifically, developers collect the operational business requirement data of each nuclear reactor in each nuclear power plant corresponding to the management system 100 to determine the main process path, i.e., the inherent state sequence, that can be executed by all nuclear reactors in each operating scenario. (Continue referring to...) Figure 1The user application module 12 is used to receive template configuration instructions corresponding to different operating scenarios of the nuclear reactor. It is understood that different nuclear reactors have corresponding template configuration instructions for different operating scenarios. The configuration and drive module 13 includes a process configuration unit 131, which is used to generate a corresponding state flow template based on the template configuration instructions and the corresponding inherent state sequence. The state flow template includes multiple sequentially connected custom node groups, each custom node group of the state flow template corresponding to each inherent state of the corresponding inherent state sequence, and each custom node group includes at least one custom node. Further, in this embodiment, the data support module includes a state flow configuration table. The state flow configuration table is configured to store inherent state sequences and state flow templates, thereby enabling the state flow templates and inherent state sequences to be correlated and stored uniformly, improving data integrity and calling efficiency.

[0028] For example, further refer to Figure 2 First, the developers, through the operational business requirement data of each nuclear reactor in each nuclear power plant corresponding to the management system 100 under operational scenario A, determine the inherent state sequence A under operational scenario A and store it in the data support module 11. The inherent state sequence A includes sequentially connected inherent states A1, A2, A3, and A4. Subsequently, users in nuclear power plant B input template configuration instructions through the user application module 12 for the specific requirements of nuclear reactor C under operational scenario A. These template configuration instructions include setting corresponding custom nodes ABC1 and ABC2 for inherent state A1, ABC3 and ABC4 for inherent state A2, ABC5 and ABC6 for inherent state A3, and ABC7 and ABC8 for inherent state A4. Finally, the process configuration unit 131 generates the corresponding state flow template ABC for nuclear reactor C under operational scenario A based on the above template configuration instructions and inherent state sequence A. The state flow template ABC includes custom nodes ABC1, ABC2, ABC3, ABC4, ABC5, ABC6, ABC7, and ABC8 connected sequentially. It should be noted that this application does not limit the number of custom nodes corresponding to each inherent state; in some embodiments, each different inherent state corresponds to a different number of custom nodes.

[0029] To facilitate user operation of the management system 100, the user application module 12 in this embodiment includes an instance configuration interface. The user application module 12 is also used to display inherent state sequences through the instance configuration interface, receive template configuration instructions corresponding to the inherent state sequences, transmit the template configuration instructions to the process configuration unit, receive state flow templates sent by the process configuration unit, and display the state flow templates through the instance configuration interface. For example, users can add, modify, or delete custom nodes according to the inherent state sequences in the instance configuration interface, thereby generating a series of sequentially connected custom nodes that meet their needs, thus forming a state flow template. The template configuration instructions include any one or more of participating roles and personnel, thereby setting corresponding personnel and / or participating roles for each custom node.

[0030] In this embodiment, developers can construct inherent state sequences that meet the actual operational needs of all nuclear reactors in all nuclear power plants under different operational scenarios, based on the real operational requirements of all nuclear reactors within the management system 100. Subsequently, users can further adjust the specific settings and number of custom nodes corresponding to each inherent state according to the actual needs of the nuclear reactors, based on the inherent state sequences through the management system 100. This ensures that the final generated state flow template fully corresponds to the actual operational process of the corresponding nuclear reactor. It is understood that by pre-storing inherent state sequences that users cannot modify in the management system 100, developers in this embodiment can ensure that all nuclear reactors in all nuclear power plants adhere to the same general framework, avoiding oversights in operational process management and improving safety and effectiveness. Based on this, users can generate state flow templates that fit the operational process of the corresponding nuclear reactors through the management system 100, enabling the management system 100 to simultaneously meet the different operational process requirements of different nuclear reactors in different nuclear power plants.

[0031] The above briefly explains the setup of the state flow templates for different nuclear reactors in different nuclear power plants using the management system 100. Next, we will further explain the setup for the management system 100 to generate and advance process instances based on interactive instructions and state flow templates. (Continue referring to...) Figure 1In this embodiment, the configuration and driving module 13 is used to store the business rules corresponding to the inherent states, generate process instances corresponding to the state flow templates, and advance the process instances according to the business rules. Further, in this embodiment, developers construct business rules based on operational business requirement data and bind each business rule to its corresponding inherent state. It is understood that when a user calls the state flow template through the management system 100 to execute a specific operational process, the management system 100 generates a process instance for that operational process based on the corresponding state flow template and advances the process instance to complete the entire operational process. Accordingly, in this embodiment, the process instance includes multiple item states, and each item state corresponds one-to-one with a custom node of the corresponding state flow template. It is understood that when a process instance advances from the corresponding custom node A1 to the custom node B1, the current item state of the process instance will also be updated from item state A2 corresponding to custom node A1 to item state B2 corresponding to custom node B1.

[0032] Specifically, the user application module 12 is also used to receive instance event instructions corresponding to the process instance, and the configuration and driving module 13 further includes a rule executor 132 and a state transition engine 133. The rule executor 132 stores business rules. In this embodiment, the state transition engine 133 is used to transmit the current entry state and instance event instructions corresponding to the process instance to the rule executor 132. Based on this, the rule executor 132 is used to generate feedback results according to the instance event instructions, the current entry state, and the business rules. Further, the rule executor 132 is also used to determine whether the custom node corresponding to the current entry state has corresponding business rules; if the determination result is yes, the business rules corresponding to the current entry state are executed. In some embodiments, the management system 100 also has a programmable node interface, and the rule executor 132 is also used to obtain relevant data from the outside through the programmable node interface to execute rule judgments. In addition, in this embodiment, the state transition engine 133 is also used to update the current entry state of the process instance according to the feedback results. Further, in this embodiment, the data support module 11 includes a state flow tracking table. The state flow tracking table is configured to store the current entry state of the process instance. Based on this, the state transition engine is also used to update the current entry state of the corresponding process instance in the state flow trace table according to the feedback results.

[0033] It should be noted that the various business rules in this embodiment include the conditions and operations for transforming a custom node corresponding to an entry state into another custom node corresponding to a destination state. Based on this, this embodiment binds all business rules to inherent states and advances process instances through business rules and instance event instructions. This ensures that users can freely define and execute process instances that fit the running process, while preventing users from adjusting business rules. Consequently, the management system 100 can meet users' changing business needs while maintaining the security and reliability of the running process. Furthermore, this embodiment advances process instances by executing business rules and changing entry states to achieve the running process, significantly simplifying the corresponding code in the management system 100 and enabling the construction of a lightweight process engine. It eliminates the need to define complex gateways, events, and sequence flows, while maintaining basic process tracing capabilities. In some scenarios, it reduces runtime overhead by 60% compared to a workflow engine. Based on this, developers can further allocate the code used for the process engine to the rule executor 132, thereby enhancing the performance of the rule executor. The management system 100 of this embodiment can also reduce the frequency of code modification or redeployment of existing templates due to user needs through the above settings. In some cases, it can reduce the frequency of code modification by 50% to 70% compared with the fixed templates preset by developers of existing state machines, which significantly reduces maintenance costs.

[0034] In one example, an isolation scenario is an operational scenario that a nuclear reactor needs to face. In an isolation scenario, certain equipment associated with the reactor needs to be isolated before subsequent operations can be performed. Furthermore, the isolation scenario must satisfy the business rule of "mandatory conflict verification before allowing the printing of isolation tags." Understandably, failing to consider and resolve conflicts with other ongoing isolation operations before implementing a new isolation operation could potentially lead to serious safety incidents. However, in a cluster of nuclear power plants, each plant develops its own procedures based on its own practices. Developers do not know the specific nodes included in the plant's procedures, nor which node prints the isolation tag and performs the isolation. Therefore, it is impossible to effectively control the process by setting conflict verification before the node printing the isolation tag using the existing state machine.

[0035] In some embodiments, the inherent states in the inherent state sequence corresponding to the isolation scenario include a first inherent state and a second inherent state connected sequentially. Based on this, the business rule corresponding to the first inherent state includes: performing conflict verification on the process instance before the process instance changes from the current first entry state to the second entry state. Specifically, the first entry state corresponds to the last custom node in the state flow template that corresponds to the first inherent state, and the second entry state corresponds to the first custom node in the state flow template that corresponds to the second inherent state. Through this setting, developers in these embodiments can directly limit the conflict verification business rule to the last custom node corresponding to the first inherent state. This allows users to simply associate the custom node corresponding to "print isolation sign" with the second inherent state, without requiring developers to explicitly know which custom node the user operates on, providing users with a more flexible state flow template setting method. Meanwhile, when executing the corresponding process instance, before advancing to the custom node corresponding to "print isolation sign", the management system 100 can execute the corresponding business rules through the rule executor 132 to perform conflict verification. Only after the rule executor 132 completes the conflict verification and provides a "success" feedback result to the state transition engine 133 will the state transition engine 133 change the entry state of the process instance to advance the process instance to the next custom node. Therefore, regardless of how the user configures the state flow template, the management system 100 in this embodiment can ensure that the process instance generated according to the state flow template must pass conflict verification before printing the isolation sign, thereby ensuring the safety and reliability of the entire operation process.

[0036] In another example, the isolation scenario requires not only isolation operations but also isolation release operations after maintenance and other operations are completed. The release instructions for the isolation release operation should be the reverse of the isolation instructions for the isolation operation, executed in reverse order. When building state flow templates, users may encounter inconsistencies between the custom nodes corresponding to the isolation release operation and the custom nodes corresponding to the isolation operation, such as omitting custom nodes for intermediate steps, thus increasing the safety risks of the operational process. Therefore, corresponding mandatory settings are necessary. However, in multi-plant / multi-reactor scenarios, each nuclear power plant will develop its own processes according to its own habits, and developers do not know at which custom node to trigger the generation of the custom node sequence corresponding to the isolation release operation.

[0037] In some embodiments, the inherent states in the inherent state sequence corresponding to the isolation scenario include an isolation execution inherent state, an intermediate inherent state, and an isolation release inherent state. The intermediate inherent state and the isolation release inherent state are sequentially connected. Furthermore, the state flow template corresponding to the isolation scenario includes multiple isolation execution nodes, and each isolation execution node corresponds to an isolation execution inherent state. Based on this, the business rules corresponding to the intermediate inherent state include: when the process instance changes to the third entry state, multiple custom nodes corresponding to the release isolation inherent state are generated based on all isolation execution nodes. The third entry state corresponds to the last custom node in the state flow template that corresponds to the intermediate inherent state. Through the above settings, in these embodiments, users associate each custom node corresponding to the isolation operation (i.e., the isolation execution node) with the isolation execution inherent state, thereby enabling accurate generation of each custom node corresponding to the isolation release operation subsequently, avoiding human error caused by manual settings, and improving setup efficiency. Further, in some embodiments, the user application module 12 is also used to receive fine-tuning instructions, and the configuration and driving module 13 is also used to fine-tune the multiple custom nodes corresponding to the release isolation inherent state according to the fine-tuning instructions.

[0038] Understandably, due to differences in the operating procedures of different nuclear reactors in different nuclear power plants, there is a problem that the operating procedures of some nuclear reactors are not entirely consistent with the business rules followed by the operating procedures of others. To address this, in some embodiments, the business rules include mandatory business rules and optional business rules. Based on this, the user application module 12 includes a rule configuration interface, and the user application module 12 is also used to display optional business rules through the rule configuration interface and use the selected optional business rules as the specific business rules for the corresponding nuclear reactor. Furthermore, the rule executor 132 is also used to execute the mandatory business rules and specific business rules corresponding to the current entry status. Through the above settings, the business rules that all nuclear reactors in all nuclear power plants follow can be made mandatory business rules, ensuring basic safety during the operation process. Based on this, users of different nuclear power plants can freely choose whether to comply with each optional business rule, thereby further improving the safety and reliability of the corresponding operation process through the subsequent execution of specific business rules by the rule executor 132. Understandably, the above settings can improve the compatibility and practicality of the management system 100 in a multi-plant, multi-reactor scenario.

[0039] Reference Figure 3 Another aspect of this application proposes a management method 200 for nuclear power plant operation processes. This application's... Figure 3Flowcharts are used to illustrate the operations performed by the system according to embodiments of this application. It should be understood that the preceding or following operations are not necessarily performed precisely in sequence. Instead, various steps can be processed in reverse order or simultaneously. Furthermore, other operations may be added to these processes, or one or more steps may be removed from them. Figure 3 As shown, management method 200 includes the following steps: Step S1 is to construct multiple inherent state sequences corresponding to different operating scenarios based on the operational business requirement data of multiple nuclear reactors. The inherent state sequence includes multiple sequentially set inherent states. Step S2 is to store the inherent state sequences. Step S3 is to obtain and store the business rules corresponding to the inherent states. Step S4 is to obtain the template configuration instructions corresponding to the nuclear reactors in different operating scenarios. Step S5 is to generate a corresponding state flow template based on the template configuration instructions and the corresponding inherent state sequences. The state flow template includes multiple sequentially connected custom node groups, each custom node group of the state flow template corresponding to each inherent state of the corresponding inherent state sequence, and each custom node group includes at least one custom node. Step S6 is to generate a process instance corresponding to the state flow template. The process instance includes multiple item states, each item state corresponding one-to-one with each custom node of the corresponding state flow template. Step S7 is to advance the process instance according to the business rules. Further reference... Figure 4 Step S7 includes the following sub-steps: Step S71 is to obtain the instance event command corresponding to the process instance. Step S72 is to generate a feedback result based on the instance event command, the current entry status of the process instance, and the business rules. Step S73 is to update the current entry status of the process instance based on the feedback result.

[0040] 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.

[0041] 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.

[0042] 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.

[0043] In some embodiments, numbers describing the quantity of components and attributes are used. It should be understood that such numbers used in the description of embodiments are modified in some examples with the terms "approximately," "approximately," or "generally." Unless otherwise stated, "approximately," "approximately," or "generally" indicates that the numbers are allowed to vary by ±20%. Accordingly, in some embodiments, the numerical parameters used in the specification and claims are approximate values, which may be changed depending on the characteristics required by individual embodiments. In some embodiments, numerical parameters should take into account specified significant digits and employ a general method of digit reservation. Although the numerical ranges and parameters used to confirm their breadth of scope in some embodiments of this application are approximate values, in specific embodiments, such values ​​are set as precisely as feasible.

[0044] Some aspects of this application can be executed entirely by hardware, entirely by software (including firmware, resident software, microcode, etc.), or by a combination of hardware and software. The aforementioned hardware or software may be referred to as a "data block," "module," "engine," "unit," "component," or "system." The processor may be one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DAPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), processors, controllers, microcontrollers, microprocessors, or combinations thereof. Furthermore, aspects of this application may manifest as computer products residing in one or more computer-readable media, including computer-readable program code. For example, computer-readable media may include, but are not limited to, magnetic storage devices (e.g., hard disks, floppy disks, magnetic tapes, etc.), optical discs (e.g., compressed CDs, digital multifunction DVDs, etc.), smart cards, and flash memory devices (e.g., cards, sticks, key drives, etc.).

[0045] 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 system for managing a nuclear power operation flow, characterized by, Suitable for managing the operation process of a plurality of nuclear reactors in a plurality of nuclear power plants, comprising: A data support module, wherein a plurality of inherent state sequences corresponding to a plurality of operation scenarios are stored, and the inherent state sequence comprises a plurality of sequentially arranged inherent states, and the inherent state sequence is constructed according to operation business requirement data of the plurality of nuclear reactors; A user application module, configured to receive template configuration instructions corresponding to the nuclear reactors under different operation scenarios; A configuration and driving module, comprising a process configuration unit, configured to generate a corresponding state flow template according to the template configuration instructions and the corresponding inherent state sequence, wherein the state flow template comprises a plurality of sequentially connected custom node groups, each custom node group of the state flow template corresponds to each inherent state of the corresponding inherent state sequence in sequence, and each custom node group comprises at least one custom node. The configuration and driving module is configured to store business rules corresponding to the inherent states, generate a process instance corresponding to the state flow template, and advance the process instance according to the business rules.

2. The nuclear power operation flow management system according to Claim 1, wherein The process instance comprises a plurality of entry states, which one-to-one correspond to each custom node of the corresponding state flow template, and the user application module is further configured to receive instance event instructions corresponding to the process instance, and the configuration and driving module further comprises: A rule executor, configured to store the business rules; A state conversion engine, configured to transmit the current entry state of the process instance and the instance event instructions to the rule executor. The rule executor is configured to generate a feedback result according to the instance event instructions, the current entry state and the business rules, and the state conversion engine is further configured to update the current entry state of the process instance according to the feedback result.

3. The nuclear power operation flow management system according to Claim 2, wherein The data support module comprises a state flow tracking table configured to store the current entry state of the process instance, and the state conversion engine is further configured to update the current entry state of the corresponding process instance in the state flow tracking table according to the feedback result.

4. The nuclear power operation flow management system according to Claim 2, wherein The rule executor is further configured to determine whether the custom node corresponding to the current entry state has a corresponding business rule, and if the determination result is yes, execute the business rule corresponding to the current entry state.

5. The nuclear power operation flow management system according to Claim 4, wherein The business rules comprise mandatory business rules and optional business rules, the user application module comprises a rule configuration interface, and the user application module is further configured to display the optional business rules through the rule configuration interface and select the optional business rules as specific business rules of the corresponding nuclear reactors. The rule executor is configured to execute the mandatory business rules and the specific business rules corresponding to the current entry state.

6. The nuclear power operation flow management system according to Claim 2, wherein The user application module comprises an instance configuration interface, and is further configured to display the inherent state sequence through the instance configuration interface, receive the template configuration instruction corresponding to the inherent state sequence, transmit the template configuration instruction to the process configuration unit, receive the state flow template sent by the process configuration unit, and display the state flow template through the instance configuration interface.

7. The nuclear power operation flow management system according to Claim 2, wherein The running scenarios comprise an isolation scenario, and the inherent state sequence corresponding to the isolation scenario comprises a plurality of inherent states which are sequentially connected, the first inherent state and the second inherent state, The business rule corresponding to the first inherent state comprises: performing conflict checking on the process instance before the process instance is changed from a current first entry state to a second entry state, wherein the first entry state corresponds to the last self-defined node corresponding to the first inherent state in the state flow template, and the second entry state corresponds to the first self-defined node corresponding to the second inherent state in the state flow template.

8. The nuclear power operation flow management system according to Claim 2, wherein The running scenarios comprise an isolation scenario, and the inherent state sequence corresponding to the isolation scenario comprises a plurality of inherent states which are sequentially connected, the first inherent state and the second inherent state, The state flow template corresponding to the isolation scenario comprises a plurality of isolation execution nodes, and the isolation execution nodes correspond to the isolation execution inherent state, The business rule corresponding to the first inherent state comprises: performing conflict checking on the process instance before the process instance is changed from a current first entry state to a second entry state, wherein the first entry state corresponds to the last self-defined node corresponding to the first inherent state in the state flow template, and the second entry state corresponds to the first self-defined node corresponding to the second inherent state in the state flow template.

9. The nuclear power operation flow management system according to Claim 1, wherein The data support module comprises a state flow configuration table configured to store the inherent state sequence and the state flow template.

10. A method of managing a nuclear power operation flow, characterized by, The management method is suitable for managing running processes of a plurality of nuclear reactors in a plurality of nuclear power plants, and the management method comprises: constructing inherent state sequences corresponding to a plurality of running scenarios according to operation business requirement data of the plurality of nuclear reactors, wherein the inherent state sequences comprise a plurality of sequentially arranged inherent states; storing the inherent state sequences; acquiring and storing business rules corresponding to the inherent states; acquiring template configuration instructions corresponding to the nuclear reactors under different running scenarios; generating corresponding state flow templates according to the template configuration instructions and the corresponding inherent state sequences, wherein the state flow templates comprise a plurality of sequentially connected self-defined node groups, each self-defined node group of the state flow template corresponds to each inherent state of the corresponding inherent state sequence in sequence, and each self-defined node group comprises at least one self-defined node; generating process instances corresponding to the state flow templates; advancing the process instances according to the business rules.

11. The method of claim 10, wherein the method further comprises: The flow instance includes a plurality of entry states, which one-to-one correspond to respective self-defined nodes of the state flow template, and the step of advancing the flow instance according to the business rule further includes: obtaining an instance event instruction corresponding to the flow instance; generating a feedback result according to the instance event instruction, the current entry state of the flow instance and the business rule; updating the current entry state of the flow instance according to the feedback result.

Images