Model-based nuclear reactor functional analysis method

Abstract

Embodiments of the present application relate to the technical field of nuclear reactors, and particularly relate to a model-based nuclear reactor function analysis method. The method comprises: S1, determining top-level functions of a nuclear reactor according to a nuclear reactor model requirement; S2, performing function flow analysis on each top-level function to decompose the top-level function into a plurality of sub-functions; S3, performing sub-function failure analysis on the plurality of sub-functions decomposed from the top-level function to identify new sub-functions; S4, determining a complete sub-function composition of the nuclear reactor according to the function flow analysis and the sub-function failure analysis; and S5, performing sub-function interaction scene analysis according to a task scene of all life cycle stages of the nuclear reactor and all sub-functions to determine interfaces between all sub-functions of the nuclear reactor. The method provided by the embodiments of the present application can more comprehensively determine the function composition and function interfaces of the nuclear reactor, and can lay a foundation for subsequent reasonable division of the nuclear reactor system and division of equipment composition.

Description

Technical Field

[0001] The embodiments of this application relate to the field of nuclear reactor technology, and specifically to a model-based method for nuclear reactor functional analysis. Background Technology

[0002] The statements herein are provided merely as background information in connection with this application and do not necessarily constitute prior art.

[0003] Nuclear reactors are complex systems characterized by diverse and complex application scenarios and numerous functional interfaces. Functional analysis, as a crucial part of nuclear reactor research and development, connects with requirements and business scenarios at the top level, and supports the definition of system equipment components and interface division at the bottom level.

[0004] Traditional design often overlooks functional analysis, which can lead to problems such as missing functions and unclear functional interfaces when translating the requirements of a nuclear reactor into its functional components and interfaces. Summary of the Invention

[0005] A brief overview of this application is provided below to offer a basic understanding of certain aspects thereof. It should be understood that this overview is not an exhaustive summary of the application. It is not intended to identify key or essential parts of the application, nor is it intended to limit its scope. Its purpose is merely to present certain concepts in a simplified form as a prelude to the more detailed description that follows.

[0006] To address the aforementioned issues, embodiments of this application provide a model-based nuclear reactor functional analysis method, comprising: S1, determining the top-level functions of the nuclear reactor according to the requirements of the nuclear reactor model; S2, performing functional flow analysis on each top-level function to decompose the top-level function into multiple sub-functions; S3, performing sub-function failure analysis on the multiple sub-functions decomposed from the top-level function to identify newly added sub-functions; S4, determining the composition of all sub-functions of the nuclear reactor based on the functional flow analysis and sub-function failure analysis; and S5, performing sub-function interaction scenario analysis based on the task scenarios and all sub-functions throughout the entire life cycle of the nuclear reactor to determine the interfaces between all sub-functions of the nuclear reactor.

[0007] The functional analysis method provided in the embodiments of this application, taking the model requirements of the nuclear reactor as input, can more comprehensively determine all the top-level functions of the nuclear reactor. From the two aspects of functional flow analysis (corresponding to normal scenarios) and sub-function failure analysis (corresponding to abnormal scenarios), it can more reasonably decompose the functions, thereby more comprehensively determining the functional composition of the nuclear reactor. Furthermore, the method provided in the embodiments of this application can more comprehensively determine the functional interfaces of the nuclear reactor through sub-function interaction scenario analysis, which can lay the foundation for the subsequent reasonable division of the nuclear reactor system and the division of equipment composition. Attached Figure Description

[0008] Other objects and advantages of this application will become apparent from the following description of embodiments of this application with reference to the accompanying drawings, and will help to provide a comprehensive understanding of this application.

[0009] Figure 1 This is a schematic flowchart of a method for nuclear reactor functional analysis provided in an embodiment of this application.

[0010] Figure 2 This is a schematic diagram of a process for analyzing the function of a reactor using a model, provided in an embodiment of this application.

[0011] Figure 3 This is a schematic diagram of a functional flow analysis of the power generation function of a nuclear reactor provided in an embodiment of this application.

[0012] Figure 4 This is a flowchart illustrating a method for determining the sub-functions that need to be added, as provided in an embodiment of this application.

[0013] Figure 5 This is a schematic diagram illustrating a scenario for handling coolant supply power sub-function failure according to an embodiment of this application.

[0014] Figure 6 This is a schematic diagram of the sub-functional interaction scenario under the nuclear reactor power operation scenario.

[0015] Figure 7 This is a flowchart illustrating the nuclear reactor requirements analysis method provided in an embodiment of this application.

[0016] Figure 8 This is a schematic diagram of a process for analyzing reactor requirements using a model, provided in an embodiment of this application.

[0017] Figure 9 This is a schematic diagram of a dynamic interactive scenario for power operation.

[0018] Figure 10 This is a schematic diagram of the external interface for a dynamic interactive scenario of power operation.

[0019] Explanation of reference numerals in the attached figures:

[0020] 31. Power generation control command; 32. Power generation adjustment command; 33. Power generation command; 34. Electrical energy; 35. Seawater; 36. Waste heat; 37. Condition monitoring feedback information; 38. Initial start-up power supply;

[0021] 101. Command Interface; 102. Status Interface; 103. Water Source Interface; 104. Power Supply Interface; 105. Output Power Interface; 106. Waste Heat Dissipation Interface;

[0022] 13. Operations personnel; 15. Power supply; 16. Power grid; 17. Ocean;

[0023] 20. Nuclear reactor.

[0024] It should be noted that the accompanying drawings are not necessarily drawn to scale, but are shown only in a schematic manner without affecting the reader's understanding. Detailed Implementation

[0025] Exemplary embodiments of this application will be described below with reference to the accompanying drawings. For clarity and brevity, not all features of actual implementations are described in the specification. However, it should be understood that many implementation-specific decisions must be made in the development of any such actual embodiment to achieve the developer's specific goals, such as complying with constraints related to the system and business, and these constraints may vary depending on the implementation. Furthermore, it should be understood that while development work can be very complex and time-consuming, such development work is merely a routine task for those skilled in the art who benefit from the content of this application.

[0026] It should also be noted that, in order to avoid obscuring this application with unnecessary details, only the equipment structure and / or processing steps closely related to the solution according to this application are shown in the accompanying drawings, while other details that are not closely related to this application are omitted.

[0027] See Figure 1 The embodiments of this application provide a model-based nuclear reactor functional analysis method, which may include: S1, determining the top-level functions of the nuclear reactor according to the requirements of the nuclear reactor model; S2, performing functional flow analysis on each top-level function to decompose the top-level function into multiple sub-functions; S3, performing sub-function failure analysis on the multiple sub-functions decomposed from the top-level function to identify newly added sub-functions; S4, determining the composition of all sub-functions of the nuclear reactor based on the functional flow analysis and sub-function failure analysis; S5, performing sub-function interaction scenario analysis based on the task scenarios of the entire life cycle of the nuclear reactor and all sub-functions to determine the interfaces between all sub-functions of the nuclear reactor.

[0028] The method provided in the embodiments of this application, taking the model requirements of the nuclear reactor as input, can more comprehensively determine all the top-level functions of the nuclear reactor. From the two aspects of functional flow analysis (corresponding to normal scenarios) and sub-function failure analysis (corresponding to abnormal scenarios), it can more reasonably decompose the functions and thus more comprehensively determine the functional composition of the nuclear reactor.

[0029] The method provided in the embodiments of this application can more comprehensively determine the functional interfaces of a nuclear reactor through functional interaction scenario analysis, which can lay the foundation for the subsequent reasonable division of the nuclear reactor system and the division of equipment composition.

[0030] The method provided in the embodiments of this application can comprehensively determine the interfaces between sub-functions based on the analysis of sub-function interaction scenarios, according to all functional components. Combined with the external interfaces determined by the requirements analysis, the internal and external functional interfaces of the nuclear reactor can be analyzed. At the same time, through the analysis of sub-function interaction scenarios, it is verified that the full-cycle task scenarios are met, thus ensuring that the functional analysis process can meet the requirements analysis process of the nuclear reactor.

[0031] In some embodiments, the nuclear reactor type requirements in step S1 may include: nuclear reactor functional requirements, nuclear reactor performance requirements, nuclear reactor interface requirements, etc., as shown in Table 1.

[0032] The corresponding functional requirements for nuclear reactors include: for example, the reactor's power generation capacity is xx, the reactor can remove waste heat, and the reactor can be controlled and operated; the corresponding performance requirements include: for example, the reactor's weight is xx, the reactor's size is xx, the reactor's reliability is xx, and the reactor's lifespan is xx; the corresponding interface requirements include: for example, the reactor needs to have an interface for discharging waste heat to the external environment, and the reactor needs to have an interface for power supply and distribution. From the functional requirements of the nuclear reactor, top-level functions such as power generation, safety, and operation control functions are identified.

[0033] Table 1. Examples of Nuclear Reactor Model Requirements

[0034]

[0035]

[0036] In some embodiments, in step S2, when performing a function flow analysis on each top-level function to decompose it into multiple sub-functions, the top-level function can be decomposed layer by layer until the lowest-level sub-function can be assigned to an entity for implementation.

[0037] In some embodiments, the multiple sub-functions that decompose the top-level function include both multiple sub-functions that decompose the top-level function according to the type of the object being acted upon, and multiple sub-functions that decompose the top-level function according to changes in the object being acted upon or the process scenario.

[0038] In some embodiments, step S2 may include: decomposing the top-level function into multiple sub-functions according to the type of the object of action. For example, the energy-providing function may be decomposed into providing mechanical energy, providing thermal energy, providing electrical energy, etc.

[0039] In some embodiments, step S2 may further include: decomposing the top-level function into multiple sub-functions according to changes in the target object or process scenario. See also Figure 3For example, a functional flow analysis can be performed on the top-level function "power generation function" to decompose the power generation function into heat generation function, heat transfer function, thermoelectric conversion function and waste heat emission function. Furthermore, the heat transfer function can be further decomposed into a series of functions related to material change processes such as providing power to the coolant and the low-temperature flow of the coolant.

[0040] In some embodiments, step S2 may further include: performing sub-function analysis to identify any missing sub-functions. When performing sub-function analysis to identify missing sub-functions, each sub-function can be analyzed from four dimensions: "who, where, what, and to what extent," to determine the missing sub-functions. This iterative process continuously optimizes the sub-functions. For example, based on the analysis of the coolant cryogenic flow sub-function, missing sub-functions such as coolant gas coverage and coolant impurity removal can be identified.

[0041] In some embodiments, step S3 may further include: performing a sub-function failure analysis based on the sub-function to determine the sub-functions that need to be added. For example, if the power function fails, a waste heat removal function needs to be added.

[0042] See Figure 4 In some embodiments, step S3, which involves performing sub-function failure analysis based on the sub-functions to determine which sub-functions need to be added, may include: S31, determining the failure modes of the multiple sub-functions decomposed from the top-level function; S32, determining the safety impact of each sub-function failure on the nuclear reactor based on the sub-function failure modes; S33, determining whether new sub-functions need to be added to mitigate the safety impact of sub-function failures on the nuclear reactor based on the safety impact of sub-function failures; S34, constructing sub-function failure response scenarios when it is determined that new sub-functions need to be added; and S35, determining the newly added sub-functions based on the sub-function failure response scenarios.

[0043] In some embodiments, step S4 further includes identifying all the sub-functional components of the nuclear reactor based on the sub-functions identified by the functional flow analysis, such as heat generation, heat transfer, thermoelectric conversion, waste heat discharge, power supply to coolant, and coolant cryogenic flow, as well as the functions identified by the sub-function failure analysis, such as residual heat removal.

[0044] In some embodiments, step S5 further includes: performing interaction analysis between various sub-functions based on the task scenarios and all sub-functions of the entire life cycle of the nuclear reactor. The entire life cycle of the nuclear reactor may include: the acquisition phase, the deployment phase, the operation phase, the support phase, and the exit phase.

[0045] Specifically, the task scenarios corresponding to the procurement phase include: transportation scenarios, etc.; the task scenarios corresponding to the deployment phase include: assembly and integration scenarios, debugging and testing scenarios, etc.; the task scenarios corresponding to the operation phase include: reactor start-up scenarios, power increase scenarios, power operation scenarios, etc.; the task scenarios corresponding to the support phase include: maintenance scenarios, etc.; and the task scenarios corresponding to the decommissioning phase include: decommissioning scenarios, etc.

[0046] Taking the sub-functional interaction scenario under the power operation scenario as an example, such as Figure 6 As shown, the analysis examines the coordination between various sub-functions to meet power operation scenarios. For example, with nuclear fuel as input, nuclear reaction generates heat, outputting nuclear reaction heat and nuclear reactor radiation; with nuclear reaction heat as input, the sub-functions of nuclear reaction heat generation and nuclear reaction heat generation reception interact, and the sub-functions of nuclear reaction heat generation reception, heat transfer, and heat output interact, outputting heat transfer energy; with heat transfer energy as input, the sub-functions of heat transfer and heat transfer reception interact, and the sub-functions of heat transfer reception, thermal energy conversion to mechanical energy, and mechanical energy conversion to electrical energy interact, outputting thermal energy and electrical energy; with thermoelectric conversion output heat energy as input, the sub-functions of heat transfer reception and heat reception interact, and the sub-functions of heat reception and waste heat emission interact, outputting waste heat.

[0047] Based on the above sub-functional interaction scenarios, the interfaces between sub-functions are determined, such as nuclear fuel interface, nuclear reaction radiation interface, nuclear reaction heat interface, thermal energy interface, mechanical energy interface, electrical energy interface, waste heat interface, etc.

[0048] In some embodiments, see Figure 2 Step S1 may also include: constructing a model of the nuclear reactor type requirements using SysML requirement diagrams / requirement lists; identifying the top-level functions of the nuclear reactor based on the model of the nuclear reactor type requirements, and constructing a top-level functional model of the nuclear reactor using SysML use case diagrams / module definition diagrams.

[0049] In some embodiments, step S1 may further include: establishing a traceability relationship between nuclear reactor model requirements and top-level functions, and constructing a traceability matrix model of nuclear reactor model requirements and top-level functions using SysML general matrix.

[0050] The embodiments of this application take the model requirements of the nuclear reactor as input, identify the top-level functions of the nuclear reactor, and can clearly establish the correlation and traceability relationship between requirements analysis and functional analysis.

[0051] The embodiments of this application establish a model-based nuclear reactor functional analysis method, providing guidance for the implementation of nuclear reactor functional modeling and analysis, and supporting the tracing of nuclear reactor functional allocation and dynamic scenario demonstration.

[0052] Specifically, the model requirements of the nuclear reactor, represented by a SysML requirement diagram / requirement list, can be used as input to identify top-level functions, such as power generation, safety, and operation control functions, and the top-level functional model of the nuclear reactor, represented by a SysML use case diagram / module definition diagram, can be used as output.

[0053] In some embodiments, see Figure 2 Step S2 may also include: S21, performing functional flow analysis based on the top-level functional model of the nuclear reactor, constructing a functional flow model using SysML activity diagrams, and decomposing the top-level functions into multiple sub-functions; S22, performing sub-function analysis based on the sub-functions, constructing a sub-function analysis model using SysML module definition diagrams, and identifying any missing sub-functions.

[0054] In some embodiments, in step S21, the top-level functional model of the nuclear reactor, represented by a SysML use case diagram / module definition diagram, is used as input, and the function is decomposed in the form of a function flow. The function flow model constructed using a SysML activity diagram is used as output.

[0055] In some embodiments, step S21 may further include: decomposing according to the type of the object of action, such as decomposing the energy-providing function into providing mechanical energy, providing thermal energy, providing electrical energy, etc.

[0056] In some embodiments, step S21 may further include: decomposing the process according to changes in the target or process scenario, such as decomposing the nuclear reactor power generation function into heat generation, heat transfer, thermoelectric conversion, and waste heat emission. Figure 3 As shown. The heat transfer function can be further decomposed into a series of material changes, such as the coolant providing power and the coolant flowing at low temperatures.

[0057] In some embodiments, step S22 may further include: taking the function flow model as input, conducting sub-function analysis based on the sub-functions obtained from the function flow analysis, and identifying missing sub-functions. When identifying missing sub-functions, each sub-function can be analyzed from four dimensions: "who, where, what to do, and to what extent," and the sub-functions can be continuously optimized through this iterative process. A sub-function analysis model constructed using a SysML module definition graph is used as the output.

[0058] In some embodiments, step S3 may further include: S31, determining the failure modes of sub-functions based on multiple sub-functions decomposed from the top-level function and any omitted sub-functions, combined with nuclear reactor engineering design experience; S32, determining the safety impact of each sub-function failure on the nuclear reactor based on the sub-function failure modes; S33, determining whether new sub-functions need to be added to mitigate the safety impact of sub-function failures on the nuclear reactor based on the safety impact of sub-function failures; S34, when it is determined that new sub-functions need to be added, constructing a sub-function failure response scenario model using SysML activity diagrams; S35, determining the newly added sub-functions based on the sub-function failure response scenario model.

[0059] Specifically, the nuclear reactor functional flow represented by a SysML activity diagram and the sub-function analysis model represented by a SysML module definition diagram can be used as inputs. For sub-functions that have a safety impact on the nuclear reactor, failure modes of the sub-functions can be determined by combining nuclear reactor engineering design experience. In some embodiments, examples of the determined sub-function failure modes are shown in Table 2.

[0060] Table 2 Examples of Sub-function Failure Modes

[0061]

[0062]

[0063] For each sub-function failure mode of a nuclear reactor, the safety impact on the reactor is considered. For example, the function of providing power to the coolant; if this function fails, the coolant will stop flowing and cannot remove heat from the reactor, causing the reactor temperature to rise continuously and posing a serious safety hazard.

[0064] For different sub-function failure procedures, this paper considers how to respond and whether new sub-functions need to be added to mitigate the safety impact of functional failures on the nuclear reactor. Sub-function failure response scenario analysis is conducted to determine the addition of new sub-functions. A sub-function failure response scenario model is constructed using SysML activity graphs. The nuclear reactor sub-function failure response scenario model represented by the SysML activity graphs is used as the output.

[0065] Figure 5This diagram illustrates a scenario for handling coolant supply power sub-function failure according to an embodiment of this application. It assesses the impact of coolant supply power sub-function failure. If coolant supply power fails completely, leading to coolant loss of flow, two new sub-functions can be added: emergency shutdown and residual heat removal. On one hand, an emergency shutdown sub-function is needed to prevent the nuclear reactor from continuing to generate heat; on the other hand, a residual heat removal sub-function is needed to remove the heat generated by the nuclear reactor and release it to the external environment to ensure reactor safety. If coolant supply power fails within a controllable range, a coolant supply power control sub-function can be added to ensure reactor safety.

[0066] In some embodiments, see Figure 2 Step S4 may also include: determining all sub-functional components of the nuclear reactor based on the functional flow model, sub-functional analysis model, and sub-functional failure response scenario model; and constructing a model of all sub-functional components of the nuclear reactor using the SysML module definition diagram. The model of all sub-functional components of the reactor is the nuclear reactor functional architecture model.

[0067] Specifically, taking the functional flow model, sub-functional analysis model, and sub-functional failure response scenario model as inputs, we sort out all the sub-functional components of the nuclear reactor, establish a functional architecture, and use the SysML module definition diagram to construct a model of all the sub-functional components of the nuclear reactor as output.

[0068] In some embodiments, step S4 may further include: constructing a traceability matrix model between sub-functions and top-level functions using a SysML general matrix, the traceability matrix model reflecting the association and traceability relationship between sub-functions and top-level functions.

[0069] In some embodiments, see Figure 2 Step S5 may also include: S51, constructing a task scenario model for the entire lifecycle of the nuclear reactor based on the task scenarios for all stages of the nuclear reactor's lifecycle; S52, conducting sub-functional interaction scenario analysis based on the task scenario model corresponding to the entire lifecycle of the nuclear reactor and the composition model of all sub-functions of the nuclear reactor, and constructing a sub-functional interaction scenario model using SysML activity diagrams / internal block diagrams; S53, identifying the interface information between each sub-function based on the sub-functional interaction scenario model, determining the interfaces between all sub-functions of the nuclear reactor; and constructing a complete sub-functional interface model using SysML internal block diagrams / state machine diagrams.

[0070] Specifically, using SysML module definition diagrams or use case diagrams to represent the task scenario models corresponding to all lifecycle stages, and SysML module definition diagrams to represent the composition model of all sub-functions of the nuclear reactor, as inputs, sub-function interaction analysis is conducted to determine the interactions between each sub-function. A sub-function interaction scenario model is constructed using SysML activity diagrams / internal block diagrams as output. Simulation of the sub-function interaction scenario model ensures the correctness of the nuclear reactor's functional logic, verifying that it satisfies the task scenarios of all lifecycle stages of the nuclear reactor.

[0071] Taking the sub-functional interaction scenario under the power operation scenario as an example, such as Figure 6 As shown, the sub-functional interaction scenario model can include heat generation nodes, heat transfer nodes, thermoelectric conversion nodes, and waste heat emission nodes. For example, at the heat generation node, nuclear fuel is used as input to generate heat through nuclear reaction, and the output is nuclear reaction heat and nuclear reactor radiation; at the heat transfer node, nuclear reaction heat is used as input, and the sub-functional interaction between nuclear reaction heat generation and nuclear reaction heat generation reception, and between nuclear reaction heat generation reception, heat transfer, and heat output, results in the output of heat transfer energy; at the thermoelectric conversion node, heat transfer energy is used as input, and the sub-functional interaction between heat transfer and heat transfer reception, and between heat transfer reception, thermal energy conversion to mechanical energy, and mechanical energy conversion to electrical energy, results in the output of thermal energy and electrical energy; at the waste heat emission node, thermoelectric conversion output heat energy is used as input, and the sub-functional interaction between heat transfer reception and heat reception, and between heat reception and waste heat emission, results in the output of waste heat.

[0072] Based on the sub-functional interaction scenario model, the interface information between each sub-function is identified, and the interfaces between all sub-functions of the nuclear reactor are determined. A complete sub-functional interface model is constructed using SysML's internal block diagram / state machine diagram.

[0073] Specifically, using a SysML activity graph / internal block graph to construct a sub-functional interaction scenario model as input, the interface information between each sub-function is identified. In some embodiments, the interface information between sub-functions may include: information flow between sub-functions such as control and monitoring; material flow between sub-functions such as nuclear fuel, coolant, and working fluid; and energy flow between sub-functions such as electrical energy and thermal energy. This defines all sub-functional interfaces of the nuclear reactor, such as nuclear fuel interface, nuclear reaction radiation interface, nuclear reaction heat interface, thermal energy interface, mechanical energy interface, electrical energy interface, and waste heat interface. The output is a SysML internal block graph / state machine diagram to construct a model of all sub-functional interfaces.

[0074] In some embodiments, see Figure 7Before step S1, the functional analysis method may also include: S101, determining the task scenarios for all life stages of the nuclear reactor based on the power supply and heating capacity requirements of the nuclear reactor; S102, determining the stakeholders for each task scenario corresponding to each life stage of the nuclear reactor based on the task scenarios for all life stages of the nuclear reactor; S103, determining the stakeholder requirements of the nuclear reactor based on the stakeholders for each task scenario corresponding to each life stage of the nuclear reactor; S104, conducting dynamic interactive scenario analysis based on the task scenarios for all life stages of the nuclear reactor and the stakeholder requirements of the nuclear reactor to determine the model requirements of the nuclear reactor.

[0075] The above embodiments are essentially based on nuclear reactor requirements analysis to determine the nuclear reactor model. This requirements analysis method can conduct requirements analysis based on power and heat supply capacity needs, considering the entire life cycle of the nuclear reactor, identifying the task scenarios for each life cycle stage, and determining stakeholders based on each task scenario. Then, based on the stakeholders in each task scenario, stakeholder requirements are determined, and dynamic scenario interaction analysis is performed to determine the nuclear reactor model requirements. This facilitates a more comprehensive analysis of nuclear reactor requirements, resulting in clearer and more complete nuclear reactor requirements. This provides nuclear reactor designers with clear design objectives, minimizing the possibility of designs that fail to cover all requirements or neglect certain requirements.

[0076] Furthermore, based on the model requirements of the nuclear reactor determined by the demand analysis, and considering the mission scenarios throughout the entire life cycle, it is possible to more comprehensively determine all the top-level functions of the nuclear reactor.

[0077] In the requirements analysis of related technologies, stakeholders are directly identified based on the entire lifecycle. Compared to identifying stakeholders based on the entire lifecycle, the requirements analysis method of this application starts from the task scenarios of the entire lifecycle. This scenario-based approach can more accurately and comprehensively identify stakeholders and thus sort out their needs. In addition, this application embodiment performs dynamic scenario interaction analysis from the perspective of the entire lifecycle task scenarios, which can comprehensively identify the external interfaces that the nuclear reactor should meet in various scenarios, thereby more comprehensively sorting out the model requirements of the nuclear reactor. In some embodiments, step S101 includes steps S1011 and S1012. S1011: Determine the entire lifecycle stage of the nuclear reactor based on the power supply and heating capacity requirements of the nuclear reactor; S1012: Determine the task scenarios of the entire lifecycle stage of the nuclear reactor based on the entire lifecycle stage of the nuclear reactor.

[0078] In some embodiments, the entire lifecycle phases of the nuclear reactor in step S1011 may include: acquisition phase, deployment phase, operation phase, support phase, and decommissioning phase.

[0079] In some embodiments, the entire lifecycle phases can be further divided according to the nuclear reactor mission requirements. For example, the acquisition phase may include the manufacturing phase and the procurement phase; the deployment phase may include the installation phase, the commissioning phase, and the testing phase; the operation phase may include the start-up phase and the power increase phase; the support phase may include the maintenance phase; and the decommissioning phase may include the retirement phase, etc.

[0080] In some embodiments, when determining the task scenario for each corresponding lifecycle stage in step S1012, the task scenario can be determined based on the five lifecycle stages of acquisition, deployment, operation, support, and exit, taking into account the nuclear reactor “doing something” under each lifecycle stage.

[0081] Specifically, the task scenarios corresponding to the procurement phase include: transportation scenarios, etc.; the task scenarios corresponding to the deployment phase include: assembly and integration scenarios, debugging and testing scenarios, etc.; the task scenarios corresponding to the operation phase include: reactor start-up scenarios, power increase scenarios, power operation scenarios, etc.; the task scenarios corresponding to the support phase include: maintenance scenarios, etc.; and the task scenarios corresponding to the decommissioning phase include: decommissioning scenarios, etc.

[0082] In some embodiments, in step S102, stakeholder identification can be carried out based on the various mission scenarios of the nuclear reactor to determine all stakeholders of the nuclear reactor.

[0083] Specifically, identified stakeholders may include transportation regulatory authorities related to the transportation scenario, installation personnel and nuclear safety regulatory authorities related to the assembly and integration scenario, and nuclear safety regulatory authorities, operators, surrounding residents, the external environment, and the ocean related to the power operation scenario. When identifying stakeholders for each mission scenario at each stage of the nuclear reactor's life cycle, the completeness of stakeholders should be ensured to avoid omissions.

[0084] In some embodiments, step S102 may include: based on the relationship with the nuclear reactor, clustering stakeholders in each task scenario throughout the entire life cycle to abstract high-level stakeholders according to the same type of stakeholders.

[0085] In some embodiments, before abstracting high-level stakeholders by clustering according to the same type of stakeholders in step S102, the method further includes: eliminating unnecessary stakeholders based on the mission requirements of the nuclear reactor. In some embodiments, after determining all stakeholders for each mission scenario corresponding to each life cycle stage, unnecessary stakeholders can be eliminated based on the mission requirements of the nuclear reactor. For example, if a stakeholder such as surrounding residents is identified in a power operation scenario, and considering that there are no residents around the operation site in the actual application scenario, then this stakeholder can be considered for removal.

[0086] In some embodiments, when performing clustering abstraction, attention should be paid to the uniformity of the number of stakeholders, with a typical number of 7 ± 2 high-level stakeholders. In some embodiments, the high-level stakeholders in the cluster can be regulators, while the low-level stakeholders can be nuclear safety regulators, environmental protection departments, transportation regulators, etc. In some embodiments, the above method can be implemented using a model.

[0087] In some embodiments, in step S103, stakeholder needs analysis is performed on stakeholders for each task scenario corresponding to each stage of the nuclear reactor's life cycle to determine the needs of each stakeholder for the nuclear reactor.

[0088] In some embodiments, such as the assembly and integration scenario in the deployment phase, the stakeholders can be installers, whose requirements can be that the nuclear reactor reserve installation space and that the installation size should not be less than a certain size; in the power operation scenario in the operation phase, the stakeholders can be environmental protection departments, whose requirements can be that the nuclear reactor's exhaust gas, waste liquid, and solid waste emissions do not exceed a specific threshold; the stakeholders in the power operation scenario can also be users, whose requirements can be that the nuclear reactor can provide a certain amount of electrical energy; in the maintenance scenario in the support phase, the stakeholders can be maintenance personnel, whose requirements can be that the nuclear reactor reserve maintenance space and that the size of the maintenance space should not be less than a certain size; in the decommissioning scenario in the exit phase, the stakeholders can be decommissioning support departments, whose requirements can be that the nuclear reactor reserve disassembly and assembly interfaces.

[0089] In some embodiments, step S104 includes steps S1041 and S1042. S1041: Based on the task scenarios of all lifecycle stages of the nuclear reactor, perform dynamic scenario interaction analysis to define the external interfaces of the nuclear reactor. S1042: Based on the needs of stakeholders and the external interfaces, determine the model requirements of the nuclear reactor.

[0090] In some embodiments, in step S1042, stakeholder requirements can be converted into nuclear reactor type requirements or external interfaces can be converted into nuclear reactor type requirements to determine the nuclear reactor type requirements. For example, the user requirement that the nuclear reactor can provide a certain amount of electrical energy can be converted into nuclear reactor power generation capacity, or the waste heat emission interface can be converted into the requirement that the nuclear reactor has an external interface to discharge waste heat to the external environment.

[0091] In some embodiments, see Figure 8 Step S101 may further include: S10101, constructing a nuclear reactor lifecycle model using a SysML state machine diagram, wherein the nuclear reactor lifecycle model represents all lifecycle stages of the nuclear reactor using a SysML state machine diagram. In some embodiments, step S101 may further include steps S10102 and S10103. S10102, determining the task scenario corresponding to each lifecycle stage of the nuclear reactor based on the nuclear reactor lifecycle model; S10103, constructing a task scenario model using a SysML module definition diagram / use case diagram.

[0092] Specifically, step S10101 also includes: using the nuclear reactor's power and heat supply capacity requirements as input, identifying the nuclear reactor's life cycle stages, and dividing the life cycle into five categories: acquisition, deployment, operation, support, and decommissioning. Based on the nuclear reactor's mission requirements, these five life cycle categories are further subdivided; for example, the acquisition stage is divided into manufacturing and procurement stages, deployment into installation, commissioning, and testing stages, operation into start-up and power increase stages, support into maintenance stages, and decommissioning into retirement stages. The nuclear reactor life cycle stages represented by a SysML state machine diagram (i.e., constructing a nuclear reactor life cycle model using a SysML state machine diagram) are used as the output.

[0093] In some embodiments, when determining the task scenarios corresponding to each lifecycle stage in step S10102, the nuclear reactor can be considered to "do something" under each lifecycle stage based on five categories of lifecycle stages: acquisition, deployment, operation, support, and exit. Task scenarios such as assembly and integration scenarios, commissioning and testing scenarios, reactor criticality scenarios, power increase scenarios, power operation scenarios, and maintenance scenarios can be identified and represented using SysML module definition diagrams / use case diagrams.

[0094] Specifically, in step S10103, the lifecycle represented by a SysML state machine diagram can be used as input to obtain task scenarios represented by SysML module definition diagrams / use case diagrams. These scenarios include transportation, assembly and integration, debugging and testing, reactor start-up, power increase, maintenance, and decommissioning.

[0095] In some embodiments, step S102 may further include: determining the stakeholders for each life cycle stage of the nuclear reactor based on the task scenario model of the entire life cycle stage of the nuclear reactor; and constructing stakeholder models for each task scenario of the entire life cycle stage of the nuclear reactor using SysML module definition graphs.

[0096] In some embodiments, step S102 may further include: clustering the obtained stakeholders according to the same type of stakeholders to abstract higher-level stakeholders.

[0097] Specifically, the lifecycle stages of a nuclear reactor, represented by a SysML state machine diagram, can be used as input. Based on the task scenarios of each of the five lifecycle stages—procurement, deployment, operation, support, and decommissioning—stakeholders can be identified. These include transportation regulatory departments related to the transportation scenario; installation personnel and nuclear safety regulatory departments related to the assembly and integration scenario; and nuclear safety regulatory departments, operators, surrounding residents, the external environment, and the ocean related to the power operation scenario. To ensure the completeness of stakeholder representation, a stakeholder model for each task scenario is constructed using a SysML module definition diagram. The nuclear reactor stakeholders represented by the SysML module definition diagram are then used as output.

[0098] Subsequently, a large number of stakeholders were identified through task scenario identification. Not all stakeholders are directly related to the nuclear reactor. Based on the nuclear reactor model and task, unnecessary stakeholders were eliminated.

[0099] After identifying stakeholders, they can be clustered and abstracted. Specifically, for stakeholders of the same type, higher-level stakeholders are abstracted from the clusters. An important requirement for clustering is the uniformity of the number of stakeholders, generally with 7 ± 2 higher-level stakeholders being ideal. For example, the higher-level stakeholders in the cluster could be regulators, while the lower-level stakeholders could be nuclear safety regulators, environmental protection departments, transportation regulators, etc.

[0100] In some embodiments, step S102 may further include: establishing a traceability relationship reflecting the nuclear reactor lifecycle and stakeholders, and constructing a traceability matrix model of the nuclear reactor lifecycle and stakeholders using the SysML universal matrix.

[0101] In some embodiments, step S103 may include: determining stakeholder requirements based on the stakeholder model of the task scenario within each life cycle stage of the nuclear reactor; and constructing a stakeholder requirements model using a SysML requirements graph.

[0102] Specifically, the nuclear reactor stakeholders, represented by the SysML module definition diagram, can be used as input. Stakeholder requirements can be defined using a stakeholder requirements template, and the stakeholder requirements model can be represented by a SysML requirements diagram as output.

[0103] When defining stakeholder requirements, a stakeholder requirements template can be used. The stakeholder requirements template can be: <Stakeholder> (who) should be able / must do / get what (what or how) at the <expected performance level> (degree) during the <lifecycle phase> (when and / or where). Nuclear reactor stakeholder requirements can be shown in Table 3.

[0104] Table 3 Examples of Stakeholder Needs

[0105]

[0106] In some embodiments, step S103 may further include: constructing a traceability matrix model between stakeholders and stakeholder needs using a SysML general matrix, the traceability matrix model reflecting the associated traceability relationship between stakeholders and stakeholder needs.

[0107] In some embodiments, step S104 may further include: determining the dynamic interaction process between stakeholders and the nuclear reactor based on the task scenario model, and constructing a dynamic interaction scenario model using SysML sequence diagrams; performing dynamic scenario interaction analysis based on the dynamic interaction scenario model to determine the external interface of the nuclear reactor, and constructing an external interface model using SysML internal block diagrams; determining the type requirements of the nuclear reactor based on the stakeholder requirement model and the external interface model, and constructing a type requirement model of the nuclear reactor using SysML requirement diagrams / requirement lists.

[0108] Specifically, using the task scenario model and stakeholder demand model of the entire life cycle as input, SysML sequence diagrams are used to analyze the dynamic interaction process between stakeholders and nuclear reactors.

[0109] In some embodiments, taking a dynamic interaction scenario of power operation as an example, the dynamic interaction process between stakeholders and the nuclear reactor is analyzed, such as... Figure 9As shown, the operator 13 sends a power generation control command 31 to the nuclear reactor 20; the power source 15 can provide the nuclear reactor 20 with initial start-up power 38; the ocean 17 can provide seawater 35 to the nuclear reactor 20; the nuclear reactor 20 receives the power generation control command 31 and outputs a power generation adjustment command 32 and a power generation command 33 to itself according to the power generation control command 31 to adjust the power generation and generate electricity. After that, the nuclear reactor 20 outputs electrical energy 34 to the power grid 16 and discharges waste heat 36 to the ocean 17; the nuclear reactor 20 can also send status monitoring feedback information 37 to the operator 13.

[0110] Based on the dynamic interaction process between stakeholders and the nuclear reactor, the external interfaces of the nuclear reactor are determined. The external interface model is constructed using SysML internal block diagrams. The determined external interfaces of the nuclear reactor include command interface, status interface, output power interface, waste heat emission interface, water source interface, power source interface, etc.

[0111] In some embodiments, taking the external interface of a dynamic power operation interaction scenario as an example, the schematic diagram of the determined nuclear reactor external interface is as follows: Figure 10 As shown, operator 13 can send commands to nuclear reactor 20 through command interface 101; nuclear reactor 20 can send status information to operator 13 through status interface 102; power supply 15 can provide power to nuclear reactor 20 through power interface 104; ocean 17 can provide water to nuclear reactor 20 through water source interface 103; nuclear reactor 20 can transfer heat to ocean 17 through waste heat emission interface 106; and nuclear reactor 20 can output electrical energy to power grid 16 through power output interface 105.

[0112] In some embodiments, after determining the external interface, a model of the nuclear reactor's type requirements is constructed using the SysML requirement diagram / requirement list as input, along with a stakeholder requirements model represented by a SysML requirement diagram and an external interface model represented by a SysML internal block diagram. The output can be a model of the nuclear reactor's type requirements constructed using the SysML requirement diagram / requirement list.

[0113] In some embodiments, when constructing a nuclear reactor type requirement model using a SysML requirement list, the needs of nuclear reactor stakeholders and external interfaces can be analyzed to determine the nuclear reactor type requirements. Specifically, stakeholder needs can be translated into nuclear reactor type requirements. For example, if a user requires the nuclear reactor to provide electrical energy xx (corresponding to a stakeholder need), this need can be translated into a nuclear reactor power generation capacity of xx (corresponding to a nuclear reactor type requirement). Another example is that the nuclear reactor needs to have an interface for discharging waste heat to the external environment.

[0114] In some embodiments, the identified nuclear reactor model requirements can be categorized according to a requirement classification method, such as functional requirements, performance requirements, and interface requirements. Functional requirements may include a specific power output of the nuclear reactor, the ability to remove waste heat, and operational control capabilities. Performance requirements may include reactor weight, reactor size, reactor reliability requirements, and reactor lifespan. Interface requirements may include interfaces for discharging waste heat to the external environment and interfaces for power supply and distribution. Examples of nuclear reactor model requirements are shown in Table 1.

[0115] In some embodiments, step S104 may further include: constructing a traceability matrix model of the nuclear reactor type requirements and stakeholder needs using a SysML universal matrix; the traceability matrix model can reflect the correlation and traceability relationship between the reactor type requirements and stakeholder needs.

[0116] The method provided by the embodiments of this application can ultimately output a dynamic interactive scenario model represented by a SysML sequence diagram and a nuclear reactor model requirement represented by a SysML requirement diagram / requirement list.

[0117] The requirements analysis method in this application establishes a traceable association between task scenarios, stakeholders, stakeholder needs, and model requirements throughout the entire lifecycle, so that the model requirements of the nuclear reactor can be changed when user requirements or application scenarios change.

[0118] Regarding the embodiments of this application, it should also be noted that, without conflict, the embodiments of this application and the features in the embodiments can be combined with each other to obtain new embodiments.

[0119] The above are merely specific embodiments of this application, but the scope of protection of this application is not limited thereto. The scope of protection of this application shall be determined by the scope of the claims.

Claims

1. A model-based method for nuclear reactor functional analysis, characterized in that, include: S1. Determine the top-level functions of the nuclear reactor according to the requirements of the nuclear reactor model; S2. For each top-level function, perform a function flow analysis to decompose the top-level function into multiple sub-functions; S3. For the multiple sub-functions decomposed from the top-level function, perform sub-function failure analysis and identify newly added sub-functions; S4. Based on the functional flow analysis and the sub-functional failure analysis, determine all sub-functional components of the nuclear reactor; S5. Based on the task scenarios and all sub-functions of the entire life cycle of the nuclear reactor, conduct sub-function interaction scenario analysis to determine the interfaces between all sub-functions of the nuclear reactor. Step S3 further includes: For the multiple sub-functions decomposed from the top-level function, determine the failure modes of the sub-functions; Based on the failure modes of the sub-functions, determine the safety impact of each sub-function failure on the nuclear reactor; Based on the safety impact of the failure of the sub-function on the nuclear reactor, determine whether it is necessary to add a new sub-function to mitigate the safety impact of the failure of the sub-function on the nuclear reactor. When it is determined that a new sub-function needs to be added, construct a failure response scenario for the sub-function; Based on the failure response scenarios of the aforementioned sub-functions, new sub-functions are determined.

2. The method according to claim 1, characterized in that, Step S2 includes: Based on the type of the target object, the top-level function is decomposed into multiple sub-functions.

3. The method according to claim 1, characterized in that, Step S2 includes: Based on changes in the target object or process scenario, the top-level function is decomposed into multiple sub-functions.

4. The method according to claim 1, characterized in that, Step S2 further includes: Based on the aforementioned sub-functions, perform sub-function analysis to identify any missing sub-functions.

5. The method according to claim 1, characterized in that, Step S1 further includes: The model of the nuclear reactor type requirements is constructed using SysML requirement diagrams / requirement lists; Based on the model requirements of the nuclear reactor, determine the top-level functions of the nuclear reactor; The top-level functional model of the nuclear reactor is constructed using SysML use case diagrams / module definition diagrams.

6. The method according to claim 5, characterized in that, Step S2 includes: Based on the top-level functional model of the nuclear reactor, a functional flow analysis is performed, and a functional flow model is constructed using SysML activity diagrams to decompose the top-level function into multiple sub-functions. Based on the sub-functions, perform sub-function analysis, construct a sub-function analysis model using the SysML module definition graph, and identify any missing sub-functions.

7. The method according to claim 6, characterized in that, Step S3 includes: Based on the multiple sub-functions decomposed from the top-level function and the omitted sub-functions, and combined with nuclear reactor engineering design experience, the failure modes of the sub-functions are determined. When it is determined that a new sub-function needs to be added, a SysML activity diagram is used to construct a sub-function failure response scenario model. Based on the aforementioned sub-function failure response scenario model, the newly added sub-functions are determined.

8. The method according to claim 7, characterized in that, The S4 step includes: Based on the functional flow model, the sub-functional analysis model, and the sub-functional failure response scenario model, the composition of all sub-functional components of the nuclear reactor is determined; A model of all sub-functional components of a nuclear reactor is constructed using SysML module definition diagrams.

9. The method according to claim 8, characterized in that, Step S5 includes: Based on the mission scenarios of all stages of the nuclear reactor's life cycle, construct a mission scenario model for all stages of the nuclear reactor's life cycle. Based on the task scenario model corresponding to all life cycle stages of the nuclear reactor and the composition model of all sub-functions of the nuclear reactor, sub-function interaction scenario analysis is performed, and sub-function interaction scenario model is constructed using SysML activity diagram / internal block diagram. Based on the sub-function interaction scenario model, identify the interface information between each sub-function and determine the interfaces between all sub-functions of the nuclear reactor. Construct a complete sub-functional interface model using SysML's internal block diagram / state machine diagram.

Images