Model-based nuclear reactor function analysis method

Abstract

The embodiment of the invention relates to the technical field of nuclear reactors, in particular to a nuclear reactor function analysis method based on a model. The method comprises the following steps: S1, determining a nuclear reactor top layer function according to a nuclear reactor model requirement; s2, for each top-layer function, performing function flow analysis, and decomposing the top-layer function into a plurality of sub-functions; s3, performing sub-function failure analysis on a plurality of sub-functions decomposed from the top-layer function, and identifying newly added sub-functions; s4, determining all sub-function compositions of the nuclear reactor according to function flow analysis and sub-function failure analysis; and S5, according to the task scenes and all the sub-functions of all the life cycle stages of the nuclear reactor, performing sub-function interaction scene analysis, and determining interfaces among all the sub-functions of the nuclear reactor. According to the method provided by the embodiment of the invention, the functional composition and the functional interface of the nuclear reactor can be more comprehensively determined, and a foundation can be laid for subsequent reasonable division of a nuclear reactor system and division of equipment composition.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of nuclear reactor technology, and in particular to a model-based nuclear reactor function analysis method. Background Art

[0002] The statements herein merely provide background information related to the present application and do not necessarily constitute prior art.

[0003] As a complex system, nuclear reactors have the characteristics of complex and changeable application scenarios and multiple functional interfaces. Functional analysis is an important part of nuclear reactor R&D and design. It undertakes demand indicators and business scenarios upward and supports the definition of system equipment composition and interface division downward.

[0004] Functional analysis is easily overlooked in traditional design, resulting in some missing functions and unclear functional interfaces in the process of converting the requirements of a nuclear reactor into its functional composition and functional interface. Summary of the invention

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

[0006] In response to the above problems, an embodiment of the present application provides a model-based nuclear reactor function analysis method, which includes: S1. Determine the top-level function of the nuclear reactor according to the nuclear reactor model requirements; S2. Perform function flow analysis on each top-level function and decompose the top-level function into multiple sub-functions; S3. Perform sub-function failure analysis on the multiple sub-functions decomposed from the top-level function and identify newly added sub-functions; S4. Determine the composition of all sub-functions of the nuclear reactor based on function flow analysis and sub-function failure analysis; S5. Perform sub-function interaction scenario analysis based on the task scenarios and all sub-functions of the entire life cycle stage of the nuclear reactor to determine the interfaces between all sub-functions of the nuclear reactor.

[0007] The functional analysis method provided in the embodiment of the present application takes the model requirements of the nuclear reactor as input, and 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 perform functional decomposition, and then more comprehensively determine the functional composition of the nuclear reactor; and the method provided in the embodiment of the present application can more comprehensively determine the functional interface 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. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0009] Figure 1 It is a schematic flow chart of a method for nuclear reactor function analysis provided in an embodiment of the present application.

[0010] Figure 2 It is a flow chart of analyzing the function of a reactor using a model provided in an embodiment of the present application.

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

[0012] Figure 4 It is a flowchart of a method for determining a sub-function that needs to be added provided in an embodiment of the present application.

[0013] Figure 5 It is a schematic diagram of a scenario in which the coolant provides a power sub-function failure response provided in an embodiment of the present application.

[0014] Figure 6 It is a schematic diagram of the sub-function interaction scenario in the nuclear reactor power operation scenario.

[0015] Figure 7 It is a flow chart of the nuclear reactor demand analysis method provided in the embodiment of the present application.

[0016] Figure 8 It is a flow chart of analyzing the requirements of a reactor using a model provided in an embodiment of the present application.

[0017] Fig. 9 It is a schematic diagram of the dynamic interaction scenario of power operation.

[0018] Fig.10 It is a schematic diagram of the external interface of the power operation dynamic interaction scenario.

[0019] Description of reference numerals:

[0020] 31. Power generation control command; 32. Power generation adjustment command; 33. Power generation command; 34. Electric energy; 35. Seawater; 36. Waste heat; 37. Status monitoring feedback information; 38. Initial startup power supply;

[0021] 101. Command interface; 102. Status interface; 103. Water source interface; 104. Power interface; 105. Output power interface; 106. Waste heat discharge interface;

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

[0023] 20. Nuclear reactor.

[0024] It should be noted that the drawings are not necessarily drawn to scale, but are merely shown in a schematic manner that does not affect the reader's understanding. DETAILED DESCRIPTION

[0025] Exemplary embodiments of the present application will be described below in conjunction with the accompanying drawings. For the sake of clarity and conciseness, not all features of the actual implementation are described in the specification. However, it should be understood that many implementation-specific decisions must be made in the process of developing any such actual implementation in order to achieve the developer's specific goals, such as meeting those constraints related to the system and business, and these constraints may vary from implementation to implementation. In addition, it should be understood that although the development work may be very complex and time-consuming, it is only a routine task for those skilled in the art who benefit from the content of this application.

[0026] It is also necessary to explain here that, in order to avoid obscuring the present application due to unnecessary details, only the device structure and / or processing steps closely related to the scheme according to the present application are shown in the accompanying drawings, while other details that are not very relevant to the present application are omitted.

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

[0028] The method provided in the embodiment of the present application takes the model requirements of the nuclear reactor as input, and 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 perform functional decomposition, and thus more comprehensively determine the functional composition of the nuclear reactor.

[0029] The method provided in the embodiment of the present application can more comprehensively determine the functional interface of the nuclear reactor through functional interaction scenario analysis, and can lay the foundation for the subsequent reasonable division of the nuclear reactor system and the division of equipment components.

[0030] The method provided in the embodiment of the present application is composed according to all functions. Through the analysis of sub-function interaction scenarios, the interfaces between sub-functions can be comprehensively determined. Combined with the external interfaces determined by the demand 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, thereby ensuring that the functional analysis process can meet the demand analysis process of the nuclear reactor.

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

[0032] The corresponding nuclear reactor functional requirements include: for example, the power generation of the nuclear reactor is xx, the nuclear reactor can discharge waste heat, the nuclear reactor can operate and control, etc.; the corresponding nuclear reactor performance requirements include: for example, the weight of the nuclear reactor is xx, the size of the nuclear reactor is xx, the reliability of the nuclear reactor is xx, the life of the nuclear reactor is xx, etc.; the corresponding interface requirements include: for example, the nuclear reactor needs to have an interface for discharging waste heat to the external environment, the nuclear reactor needs to have an interface for power supply and distribution, etc. Identify the top-level functions such as power generation function, safety function, operation control function, etc. from the nuclear reactor functional requirements.

[0033] Table 1 Examples of model requirements for nuclear reactors

[0034]

[0035]

[0036] In some embodiments, in step S2, when performing 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 decomposed from the top-level function include both the multiple sub-functions decomposed from the top-level function according to the type of the action object and the multiple sub-functions decomposed from the top-level function according to the change of the action object 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, decomposing the energy providing function into providing mechanical energy, providing thermal energy, providing electrical energy, etc. according to the type of the object of action.

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

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

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

[0042] See also Figure 4 In some embodiments, in step S3, performing sub-function failure analysis based on the sub-functions, and determining the sub-functions that need to be added may include: S31, determining sub-function failure modes for multiple sub-functions decomposed from the top-level functions; S32, determining the safety impact of each sub-function failure on the nuclear reactor based on the sub-function failure modes; S33, determining whether it is necessary to add new sub-functions to reduce the safety impact of sub-function failure on the nuclear reactor based on the safety impact of sub-function failure on the nuclear reactor; S34, when it is determined that a new sub-function needs to be added, constructing a sub-function failure response scenario; S35, determining the sub-function to be added based on the sub-function failure response scenario.

[0043] In some embodiments, step S4 also includes sorting out all the sub-functional components of the nuclear reactor based on the sub-functionalities analyzed from the functional flows, such as heat generation function, heat transfer function, thermoelectric conversion function, waste heat discharge function, providing power to the coolant, low-temperature flow of the coolant, etc., as well as the functions analyzed from the sub-functional failures, such as the residual heat extraction function.

[0044] In some embodiments, step S5 also includes: performing interaction analysis between each sub-function based on the task scenarios and all sub-functions of the entire life cycle stages of the nuclear reactor. The entire life cycle stages of the nuclear reactor may include: procurement stage, deployment stage, operation stage, support stage and exit stage.

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

[0046] Take the sub-function interaction scenario in the power operation scenario as an example. Figure 6 As shown, the coordination between each sub-function is analyzed to meet the power operation scenario. For example, with nuclear fuel as input, nuclear reaction heat is generated, and nuclear reaction heat and nuclear reactor radiation are output; with nuclear reaction heat as input, nuclear reaction heat generation and nuclear reaction heat generation reception interact with each other, and nuclear reaction heat generation reception, heat transfer, and heat output interact with each other, and heat transfer energy is output; with heat transfer energy as input, heat transfer and heat transfer reception interact with each other, and heat transfer reception, heat energy conversion to mechanical energy, and mechanical energy conversion to electrical energy interact with each other, and heat energy and electrical energy are output; with thermoelectric conversion output heat energy as input, heat transfer reception interacts with heat reception, and heat reception and waste heat discharge interact with each other, and waste heat is output.

[0047] According to the above sub-function interaction scenarios, determine the interfaces between sub-functions 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: using a SysML requirement diagram / requirement list to construct a model requirement model of a nuclear reactor; identifying the top-level functions of the nuclear reactor based on the model requirement model of the nuclear reactor, and using a SysML use case diagram / module definition diagram to construct a top-level function model of the nuclear reactor.

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

[0050] The embodiment of the present application uses the model requirements of the nuclear reactor as input, identifies the top-level functions of the nuclear reactor, and can clearly establish the correlation and traceability relationship between the demand analysis and the functional analysis.

[0051] The embodiments of the present application provide guidance for the implementation of nuclear reactor function modeling and analysis by establishing a model-based nuclear reactor function analysis method to support nuclear reactor demand function allocation tracing, function dynamic scenario demonstration, etc.

[0052] Specifically, the model requirements of the nuclear reactor represented by the SysML requirement diagram / requirement list can be used as input to identify top-level functions, such as power generation function, safety function, operation control function, etc., and the top-level functional model of the nuclear reactor represented by the 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 function flow analysis based on the top-level function model of the nuclear reactor, building a function flow model using SysML activity diagram, and decomposing the top-level function into multiple sub-functions; S22. Performing sub-function analysis based on the sub-functions, building a sub-function analysis model using SysML module definition diagram, and determining the missing sub-functions.

[0054] In some embodiments, in step S21, the top-level functional model of the nuclear reactor represented by the SysML use case diagram / module definition diagram is used as input, functional decomposition is performed in the form of functional flow, and the functional flow model constructed using the 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 according to the change of the object of action or the process scenario, such as decomposing the power generation function of a nuclear reactor into heat generation, heat transfer, thermoelectric conversion, and waste heat discharge, such as Figure 3 As shown. The heat transfer function can be further decomposed into a series of material change processes such as the coolant providing power and the coolant flowing at low temperature.

[0057] In some embodiments, step S22 may also include: taking the function flow model as input, and conducting sub-function analysis based on the sub-functions obtained by the function flow analysis to determine the missing sub-functions. When determining the missing sub-functions, each sub-function may be analyzed from the four dimensions of "who, where, what, and to what extent", and the sub-functions are continuously optimized through this iterative process. The sub-function analysis model is constructed using the SysML module definition diagram as output.

[0058] In some embodiments, step S3 may also include: S31, determining the sub-function failure mode based on the multiple sub-functions decomposed from the top-level function and the omitted sub-functions, combined with the 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 mode; S33, determining whether it is necessary to add new sub-functions to reduce the safety impact of sub-function failure on the nuclear reactor based on the safety impact of the sub-function failure on the nuclear reactor; S34, when it is determined that a new sub-function needs to be added, using a SysML activity diagram to construct a sub-function failure response scenario model; S35, determining the newly added sub-function based on the sub-function failure response scenario model.

[0059] Specifically, the nuclear reactor function flow represented by the SysML activity diagram and the sub-function analysis model represented by the SysML module definition diagram can be used as inputs, and the sub-function failure mode can be determined for the sub-functions that have a safety impact on the nuclear reactor in combination with the 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 the failure modes of nuclear reactor sub-functions, consider the safety impact of each sub-function failure on the nuclear reactor. For example, when the sub-function of providing power to the coolant fails, the coolant cannot flow and cannot take away the heat of the nuclear reactor, causing the temperature of the nuclear reactor to continue to rise, causing a more serious safety impact on the nuclear reactor.

[0064] Consider how to deal with different sub-function failure procedures, whether it is necessary to add new sub-functions to reduce the safety impact of functional failures on nuclear reactors, and determine the new sub-functions by analyzing the sub-function failure response scenarios. Use SysML activity diagrams to build sub-function failure response scenario models. Take the nuclear reactor sub-function failure response scenario model represented by the SysML activity diagram as the output.

[0065] Figure 5A schematic diagram of a scenario for coping with failure of the coolant power sub-function provided in accordance with an embodiment of the present application is shown. In view of the failure of the coolant power sub-function, the failure impact of the coolant power sub-function is determined. If the coolant power completely fails, resulting in loss of coolant flow, two new sub-functions, emergency shutdown and residual heat extraction, can be added; on the one hand, a new emergency shutdown sub-function needs to be added to prevent the nuclear reactor from continuing to generate heat; on the other hand, a new residual heat extraction sub-function needs to be added to extract the heat generated by the nuclear reactor and discharge it to the external environment to ensure the safety of the reactor. If the coolant power fails within a controllable range, a coolant power control sub-function can be added to ensure the safety of the reactor.

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

[0067] Specifically, with the functional flow model, sub-function analysis model and sub-function failure response scenario model as input, all sub-function components of the nuclear reactor are sorted out, the functional architecture is established, and the SysML module definition diagram is used to construct the model of all sub-function components of the nuclear reactor as output.

[0068] In some embodiments, step S4 may further include: using the SysML general matrix to construct a traceability matrix model between the sub-functions and the top-level functions, where the traceability matrix model may reflect the associated traceability relationship between the sub-functions and the top-level functions.

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

[0070] Specifically, the task scenario models corresponding to all life cycle stages represented by SysML module definition diagrams or use case diagrams and the nuclear reactor sub-function composition models represented by SysML module definition diagrams are used as inputs to carry out sub-function interaction analysis, determine the interactions between each sub-function, and use SysML activity diagrams / internal block diagrams to construct sub-function interaction scenario models as outputs. The correctness of the nuclear reactor function logic is ensured through sub-function interaction scenario model simulation to verify that each task scenario that meets all life cycle stages of the nuclear reactor is met.

[0071] Take the sub-function interaction scenario in the power operation scenario as an example. Figure 6 As shown. The sub-function interaction scenario model may include heat generation nodes, heat transfer nodes, thermoelectric conversion nodes, and waste heat emission nodes. For example, under the heat generation node, nuclear fuel is used as input to generate nuclear reaction heat, and nuclear reaction heat and nuclear reactor radiation are output; under the heat transfer node, nuclear reaction heat is used as input, and sub-functions of nuclear reaction heat generation and nuclear reaction heat generation reception are interacted, and sub-functions of nuclear reaction heat generation reception, heat transfer, and heat output are interacted, and heat transfer energy is output; under the thermoelectric conversion node, heat transfer energy is used as input, and sub-functions of heat transfer and heat transfer reception are interacted, and sub-functions of heat transfer reception, heat energy conversion into mechanical energy, and mechanical energy conversion into electrical energy are interacted, and heat energy and electrical energy are output; under the waste heat emission node, the output heat energy of thermoelectric conversion is used as input, and sub-functions of heat transfer reception and heat reception are interacted, and sub-functions of heat reception and waste heat emission are interacted, and waste heat is output.

[0072] According to the sub-function 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. The SysML internal block diagram / state machine diagram is used to build the interface model of all sub-functions.

[0073] Specifically, the sub-function interaction scenario model is constructed with SysML activity diagram / internal block diagram as input, and 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, working fluid, etc.; energy flow between sub-functions such as electrical energy and thermal energy, and all sub-function interfaces of the nuclear reactor are defined, 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. The SysML internal block diagram / state machine diagram is used to construct the interface model of all sub-functions as output.

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

[0075] The above embodiment is essentially to determine the model of the nuclear reactor based on the nuclear reactor demand analysis. The above demand analysis method can carry out demand analysis according to the power supply and heating capacity demand, taking into account the entire life cycle stage of the nuclear reactor, determine the task scenarios of all life cycle stages, and determine the stakeholders according to the task scenarios of all life cycle stages, and then determine the stakeholder needs according to the stakeholders of each task scenario, and perform dynamic scenario interaction analysis to determine the model requirements of the nuclear reactor, which is conducive to a more comprehensive analysis of the needs of the nuclear reactor, and determine clearer and more complete nuclear reactor requirements, thereby providing clear design goals for the designers of the nuclear reactor, so as to avoid the designed nuclear reactor from not covering all needs or some needs being ignored, etc.

[0076] In addition, the model requirements of the nuclear reactor determined according to the demand analysis can more comprehensively determine all the top-level functions of the nuclear reactor because they take into account the mission scenarios of the entire life cycle stage.

[0077] In the demand analysis of related technologies, stakeholders are directly identified based on the entire life cycle. Compared with identifying stakeholders based on the entire life cycle, the demand analysis method of the embodiment of the present application starts with the analysis of the task scenarios of the entire life cycle. The method of using scenarios can more accurately and comprehensively identify stakeholders, and then sort out the needs of stakeholders. In addition, the embodiment of the present application performs dynamic scenario interaction analysis from the perspective of the task scenarios of the entire life cycle, and 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 step S1011 and step S1012. S1011. Determine the entire life cycle stages 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 life cycle stages of the nuclear reactor based on the entire life cycle stages of the nuclear reactor.

[0078] In some embodiments, all life cycle stages of the nuclear reactor in step S1011 may include: a procurement stage, a deployment stage, an operation stage, a support stage, and a withdrawal stage.

[0079] In some embodiments, all life cycle stages can be further divided according to the nuclear reactor mission requirements. For example, the acquisition stage may include the manufacturing stage and the purchasing stage; the deployment stage may include the installation stage, the commissioning stage, and the test stage; the operation stage may include the start-up stage and the power increase stage; the support stage may include the maintenance stage; and the exit stage may include the decommissioning stage.

[0080] In some embodiments, in step S1012, when determining the corresponding mission scenario for each life cycle stage, the mission scenario can be determined based on the five life cycle stages of acquisition, deployment, operation, support, and exit, considering that the nuclear reactor "does something" in each life cycle stage.

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

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

[0083] Specifically, the identified stakeholders may include transportation regulatory authorities related to transportation scenarios, installers and nuclear safety regulatory authorities related to assembly and integration scenarios, and nuclear safety regulatory authorities, operators, surrounding residents, external environment, and oceans related to power operation scenarios. When identifying stakeholders for each mission scenario corresponding to each life cycle stage of a nuclear reactor, the integrity of the stakeholders should be ensured to avoid missing any stakeholders.

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

[0085] In some embodiments, in step S102, before clustering and abstracting high-level stakeholders according to the same type of stakeholders, it also includes: eliminating unnecessary stakeholders according to the task requirements of the nuclear reactor. In some embodiments, after determining all stakeholders of each task scenario corresponding to each life cycle stage, unnecessary stakeholders can be eliminated in combination with the task requirements of the nuclear reactor. For example, in the power operation scenario, a stakeholder of surrounding residents is identified. In combination with the actual application scenario, if there are no residents around the operation site, this stakeholder is considered to be removed.

[0086] In some embodiments, when clustering and abstracting, attention should be paid to the uniformity of the number, and the number of high-level stakeholders is generally 7±2. In some embodiments, the high-level stakeholders of the cluster may be regulators, and the low-level stakeholders may be nuclear safety regulators, environmental protection departments, transportation regulatory departments, etc. In some embodiments, the above method can be implemented using a model.

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

[0088] In some embodiments, for example, the stakeholders of the assembly and integration scenario in the deployment phase may be installers, and the installer requirements may be requirements for the installers to reserve installation space for the nuclear reactor, and the installation size may be proposed to be no less than a certain size; the stakeholders of the power operation scenario in the operation phase may be the environmental protection department, and the environmental protection department requirements may be requirements for the environmental protection department to require that the emissions of nuclear reactor waste gas, waste liquid, and waste solid do not exceed a specific threshold value; the stakeholders of the power operation scenario may also be users, and the user requirements may be requirements for users to require that the nuclear reactor can provide a certain amount of electrical energy; the stakeholders of the maintenance scenario in the support phase may be maintenance personnel, and the maintenance personnel requirements may be requirements for the maintenance personnel to reserve maintenance space for the nuclear reactor, and the size of the maintenance space may be no less than a certain size; the stakeholders of the decommissioning scenario in the exit phase may be the decommissioning support department, and the decommissioning support department requirements may be requirements for the decommissioning support department to reserve a disassembly and assembly interface for the nuclear reactor.

[0089] In some embodiments, step S104 includes step S1041 and step S1042. S1041. According to the mission scenarios of all life cycle stages of the nuclear reactor, dynamic scenario interaction analysis is performed to define the external interface of the nuclear reactor. S1042. According to the stakeholder needs and external interface of the nuclear reactor, the model requirements of the nuclear reactor are determined.

[0090] In some embodiments, in step S1042, the requirements of stakeholders may be converted into model requirements of nuclear reactors or the external interface may be converted into model requirements of nuclear reactors to determine the model requirements of nuclear reactors. For example, the user's requirement that the nuclear reactor can provide a certain amount of electrical energy may be converted into the power generated by the nuclear reactor, or the waste heat discharge interface may be converted into an external interface requirement that the nuclear reactor must have to discharge waste heat to the external environment.

[0091] In some embodiments, see Figure 8 , step S101 may also include: S10101, constructing a nuclear reactor life cycle model using a SysML state machine diagram, wherein the nuclear reactor life cycle model uses the SysML state machine diagram to represent all life cycle stages of the nuclear reactor. In some embodiments, step S101 may also include steps S10102 and S10103. S10102, determining the task scenarios corresponding to each life cycle stage of the nuclear reactor according to the nuclear reactor life cycle model; S10103, constructing a task scenario model using a SysML module definition diagram / use case diagram.

[0092] Specifically, step S10101 also includes: using the power supply and heating capacity requirements of the nuclear reactor as input, identifying the life cycle stages of the nuclear reactor, and dividing the life cycle into five categories: acquisition, deployment, operation, support, and exit. According to the mission requirements of the nuclear reactor, the five life cycles are further divided, such as the acquisition stage is divided into the manufacturing stage, the procurement stage, etc., the deployment is divided into the installation stage, the commissioning stage, the test stage, etc., the operation is divided into the start-up stage, the power increase stage, etc., the support is divided into the maintenance stage, etc., and the exit is divided into the decommissioning stage, etc. The nuclear reactor life cycle stages represented by the SysML state machine diagram (i.e., the nuclear reactor life cycle model is constructed using the SysML state machine diagram) are used as output.

[0093] In some embodiments, in step S10102, when determining the task scenarios corresponding to each life cycle stage, it is possible to consider the nuclear reactor "doing something" in each life cycle stage based on the five life cycle stages of acquisition, deployment, operation, support and exit, identify task scenarios, such as assembly and integration scenarios, debugging test scenarios, reactor criticality scenarios, power increase scenarios, power operation scenarios, maintenance scenarios, etc., and use SysML module definition diagrams / use case diagrams to represent them.

[0094] Specifically, in step S10103, the life cycle represented by the SysML state machine diagram can be used as input to obtain the task scenario represented by the SysML module definition diagram / use case diagram, such as transportation scenario, assembly integration scenario, debugging test scenario, stack startup scenario, power increase scenario, maintenance scenario, decommissioning scenario, etc.

[0095] In some embodiments, step S102 may also include: determining the stakeholders of the task scenarios of the nuclear reactor corresponding to each life cycle stage based on the task scenario model of all life cycle stages of the nuclear reactor; and constructing the stakeholder model of each task scenario of the nuclear reactor corresponding to all life cycle stages using the SysML module definition diagram.

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

[0097] Specifically, the nuclear reactor life cycle stage represented by the SysML state machine diagram can be used as input, and based on the task scenarios of the five life cycle stages of the nuclear reactor, such as procurement, deployment, operation, support, and exit, stakeholders can be identified, such as the transportation regulatory department related to the transportation scenario, the installers and nuclear safety regulatory department related to the assembly and integration scenario, and the nuclear safety regulatory department, operators, surrounding residents, external environment, and ocean related to the power operation scenario. To ensure the integrity of the stakeholders, the SysML module definition diagram is used to build the stakeholder model for each task scenario. The nuclear reactor stakeholders represented by the SysML module definition diagram are used as output.

[0098] Afterwards, a large number of stakeholders were obtained through task scenario identification. Not all stakeholders are directly related to nuclear reactors. Combined with the nuclear reactor model task, unnecessary stakeholders were eliminated.

[0099] After screening the stakeholders, the obtained stakeholders can be clustered and abstracted. Specifically, for stakeholders of the same type, high-level stakeholders are clustered and abstracted. An important requirement for clustering is the uniformity of quantity, and generally 7±2 high-level stakeholders are appropriate. For example, the high-level stakeholders of the cluster are regulators, and the low-level stakeholders are nuclear safety regulators, environmental protection departments, transportation regulators, etc.

[0100] In some embodiments, step S102 may further include: establishing a traceability relationship that reflects the association between the nuclear reactor life cycle and stakeholders, and using the SysML general matrix to construct a traceability matrix model of the nuclear reactor life cycle and stakeholders.

[0101] In some embodiments, step S103 may include: determining stakeholder requirements according to a stakeholder model of task scenarios in each life cycle stage of the nuclear reactor; and constructing a stakeholder requirement model using a SysML requirement diagram.

[0102] Specifically, the nuclear reactor stakeholders represented by the SysML module definition diagram can be used as input, the stakeholder requirements template can be used to define the stakeholder requirements, and the stakeholder requirements model can be represented by the SysML requirement diagram as output.

[0103] When defining stakeholder requirements, the stakeholder requirements template can be used to define stakeholder requirements. The stakeholder requirements template can be: <stakeholder> (who) should be able to / need to <do / get> (what or how) at <life cycle stage> (when and / or where) with <expected performance level> (degree). The 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: using a SysML general matrix to construct a traceability matrix model between stakeholders and their requirements, where the traceability matrix model may reflect the associated traceability relationship between stakeholders and their requirements.

[0107] In some embodiments, step S104 may also include: determining the dynamic interaction process between the stakeholders and the nuclear reactor according to the task scenario model, and constructing the dynamic interaction scenario model using the SysML sequence diagram; performing dynamic scenario interaction analysis according to the dynamic interaction scenario model, determining the external interface of the nuclear reactor, and constructing the external interface model using the SysML internal block diagram; determining the model requirements of the nuclear reactor according to the stakeholder requirement model and the external interface model, and constructing the model requirement model of the nuclear reactor using the SysML requirement diagram / requirement list.

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

[0109] In some embodiments, taking the power operation dynamic interaction scenario as an example, the dynamic interaction process between stakeholders and the nuclear reactor is analyzed, such as Fig. 9As shown, the operator 13 sends a power generation control instruction 31 to the nuclear reactor 20; the power supply 15 can provide the nuclear reactor 20 with an initial startup power supply 38; the ocean 17 can provide seawater 35 to the nuclear reactor 20; the nuclear reactor 20 receives the power generation control instruction 31, and outputs a power generation adjustment instruction 32 and a power generation instruction 33 to itself according to the power generation control instruction 31, so as to adjust the power generation power and generate electricity, and then the nuclear reactor 20 outputs electric 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] According to the dynamic interaction process between stakeholders and the nuclear reactor, the external interface of the nuclear reactor is determined, and the external interface model is constructed using the SysML internal block diagram. The external interfaces of the nuclear reactor are determined, such as the command interface, status interface, output power interface, waste heat discharge interface, water source interface, power supply interface, etc.

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

[0112] In some embodiments, after the external interface is determined, the stakeholder requirement model represented by the SysML requirement diagram and the external interface model represented by the SysML internal block diagram are used as inputs to construct the model requirement model of the nuclear reactor using the SysML requirement diagram / requirement list. The model requirement model of the nuclear reactor can be constructed using the SysML requirement diagram / requirement list as output.

[0113] In some embodiments, when using the SysML requirement list to construct a model requirement model for a nuclear reactor, the requirements of stakeholders and external interfaces of the nuclear reactor can be sorted out to determine the model requirements of the nuclear reactor. Specifically, the requirements of stakeholders can be converted into the model requirements of the nuclear reactor. For example, if a user requires that the nuclear reactor can provide electrical energy xx (corresponding to the requirements of stakeholders), the requirement can be converted into the power generation of the nuclear reactor xx (corresponding to the model requirements of the nuclear reactor). For another example, the nuclear reactor needs to have an interface for discharging waste heat to the external environment.

[0114] In some embodiments, the model requirements of the sorted nuclear reactors can be classified with reference to the demand classification method, for example, they can be divided into functional requirements, performance requirements, interface requirements, etc. Among them, the functional requirements may include that the power generation power of the nuclear reactor is a certain power, the nuclear reactor can discharge residual heat, and the nuclear reactor can operate and control; the performance requirements may include the weight of the nuclear reactor, the size of the nuclear reactor, the reliability requirements of the nuclear reactor, and the life of the nuclear reactor; the interface requirements may include that the nuclear reactor must have an interface for discharging waste heat to the external environment, and the nuclear reactor must have an interface for power supply and distribution. Examples of model requirements for nuclear reactors are shown in Table 1.

[0115] In some embodiments, step S104 may further include: using SysML general matrix to construct a traceability matrix model of nuclear reactor model requirements and stakeholder requirements; the traceability matrix model may reflect the associated traceability relationship between the reactor model requirements and stakeholder requirements.

[0116] The method provided according to the embodiment of the present application can finally output a dynamic interaction scenario model represented by a SysML sequence diagram and a model requirement of a nuclear reactor represented by a SysML requirement diagram / requirement list.

[0117] The demand analysis method of the embodiment of the present application establishes the associated traceability of task scenarios, stakeholders, stakeholder requirements, and model requirements throughout the entire life cycle, so that the model requirements of the nuclear reactor can be changed when user requirements or application scenarios change.

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

[0119] The above are only specific implementation methods of the present application, but the protection scope of the present application is not limited thereto. The protection scope of the present application shall be based on the protection scope of the claims.

Claims

1. A model-based nuclear reactor function analysis method, characterized in that: include: S1. Determine the top-level function of the nuclear reactor according to the requirements of the nuclear reactor model; S2. Perform function flow analysis on each top-level function and decompose the top-level function into multiple sub-functions; S3. Perform sub-function failure analysis on multiple sub-functions decomposed from the top-level functions and identify newly added sub-functions; S4. Determine all sub-function components of a nuclear reactor according to the functional flow analysis and the sub-function failure analysis; S5. According to the mission scenarios and all sub-functions of the entire life cycle stage of the nuclear reactor, conduct sub-function interaction scenario analysis to determine the interfaces between all sub-functions of the nuclear reactor.

2. The method according to claim 1, characterized in that The S2 step includes: According to the type of the object being acted upon, the top-level function is decomposed into a plurality of sub-functions.

3. The method according to claim 1, characterized in that The S2 step includes: According to the changes in the objects of action or the process scenarios, the top-level function is decomposed into multiple sub-functions.

4. The method according to claim 1, characterized in that: The S2 step further includes: According to the sub-functions, sub-function analysis is performed to determine the missing sub-functions.

5. The method according to claim 1, characterized in that The S3 step further includes: Determine the failure modes of the sub-functions decomposed from the top-level functions; Determining the safety impact of each sub-function failure on the nuclear reactor according to the sub-function failure mode; According to the safety impact of the sub-function failure on the nuclear reactor, determining whether it is necessary to add a new sub-function to mitigate the safety impact of the sub-function failure on the nuclear reactor; When it is determined that a new sub-function needs to be added, construct a sub-function failure response scenario; Determine the newly added sub-function based on the sub-function failure response scenario.

6. The method according to claim 1, characterized in that The S1 step further includes: Using SysML requirement diagram / requirement list to build the model requirement model of the nuclear reactor; Determining the top-level functions of the nuclear reactor according to the model requirement model of the nuclear reactor; The top-level functional model of the nuclear reactor is constructed using SysML use case diagrams / module definition diagrams.

7. The method according to claim 6, characterized in that The S2 step includes: According to the top-level functional model of the nuclear reactor, a functional flow analysis is performed, a functional flow model is constructed using a SysML activity diagram, and the top-level function is decomposed into a plurality of sub-functions; According to the sub-functions, sub-function analysis is performed, and a sub-function analysis model is constructed using a SysML module definition diagram to determine the missing sub-functions.

8. The method according to claim 7, characterized in that The S3 step includes: Determine sub-function failure modes according to the multiple sub-functions decomposed from the top-level function and the omitted sub-functions in combination with nuclear reactor engineering design experience; Determining the safety impact of each sub-function failure on the nuclear reactor according to the sub-function failure mode; According to the safety impact of the sub-function failure on the nuclear reactor, determining whether it is necessary to add a new sub-function to mitigate the safety impact of the sub-function failure on the nuclear reactor; When it is determined that a new sub-function needs to be added, a SysML activity diagram is used to build a sub-function failure response scenario model; Based on the sub-function failure response scenario model, a newly added sub-function is determined.

9. The method according to claim 8, characterized in that The S4 step includes: Determining all sub-function components of the nuclear reactor according to the functional flow model, the sub-function analysis model and the sub-function failure response scenario model; The SysML module definition diagram is used to construct a model of all sub-function components of a nuclear reactor.

10. The method according to claim 9, characterized in that The S5 step includes: According to the mission scenarios of all life cycle stages of nuclear reactors, a mission scenario model of all life cycle stages of nuclear reactors is constructed; According to the task scenario models corresponding to all life cycle stages of the nuclear reactor and the composition models of all sub-functions of the nuclear reactor, sub-function interaction scenario analysis is performed, and a sub-function interaction scenario model is constructed using SysML activity diagrams / internal block diagrams; According to the sub-function interaction scenario model, identifying interface information between the sub-functions, and determining interfaces between all sub-functions of the nuclear reactor; Use SysML internal block diagram / state machine diagram to build all sub-function interface models.

Images