MBSE-based nuclear power plant instrument control system design method and device
The MBSE method for designing instrumentation and control systems in nuclear power plants solves the problem of cross-disciplinary design, achieves clear division of system requirements and clarification of functional boundaries, and improves design efficiency and reliability.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-12-30
- Publication Date
- 2026-04-10
AI Technical Summary
In nuclear power plant design, the instrumentation and control system involves complex cross-disciplinary design requirements. The inconsistent research progress of each discipline leads to frequent interface integration and a large workload, making it difficult to effectively integrate and optimize.
The MBSE-based systems engineering approach is adopted to conduct instrumentation and control system requirements analysis through a top-down, layer-by-layer decomposition process, including overall instrumentation and control requirements capture, architecture analysis, and subsystem partitioning. This ensures that the top-level design requirements are implemented in the instrumentation and control system and avoids 'patchwork' design.
It achieves efficient integration and optimization of instrumentation and control system design, ensures accurate transmission of professional requirements and clear boundaries of system functions, and improves the reliability and efficiency of the design.
Smart Images
Figure CN121835525A_ABST
Abstract
Description
Technical Field
[0001] This disclosure relates to the field of nuclear power plant instrumentation and control system design technology based on MBSE, and particularly to a design method and apparatus for a nuclear power plant instrumentation and control system based on MBSE. Background Technology
[0002] Gas-cooled microreactor nuclear power units are vehicle-mounted, portable, megawatt-class nuclear power sources. Due to their compact structure, flexible deployment, safety and reliability, and ability to generate high-quality electricity, they have attracted widespread attention and can meet the needs of microgrid applications in remote mountainous areas and border bases, as well as power supply for emergency disaster relief.
[0003] As a crucial component of gas-cooled microreactor nuclear power plants, the instrumentation and control system (ICS) provides essential monitoring and control functions to ensure the safe and efficient operation of the nuclear power plant. In nuclear power plant design, the ICS involves numerous upstream disciplines, such as overall engineering, process engineering, ventilation, and electrical engineering. Regarding inter-system boundaries and coordination, the design requirements provided by these disciplines to the ICS often overlap, necessitating a comprehensive evaluation by the ICS specialist. Furthermore, due to the varying research progress of each discipline, interface integration is frequent and the workload is substantial. Summary of the Invention
[0004] This disclosure provides a design method and apparatus for nuclear power plant instrumentation and control systems based on Model-Based Systems Engineering (MBSE), as well as electronic equipment, computer-readable storage media, and computer program products.
[0005] Firstly, this disclosure provides a design method for a nuclear power plant instrumentation and control system based on MBSE (Mechanical, Instrumentation, and SE) model. This method includes: S1, capturing overall instrumentation and control requirements, analyzing overall instrumentation and control requirements, and analyzing the overall instrumentation and control architecture to obtain an overall instrumentation and control system model. Based on the subsystem partitioning principle, the functions of the instrumentation and control system are allocated to various instrumentation and control subsystems according to the overall instrumentation and control system model, thus determining the functions of each subsystem. S2, performing requirements analysis and scheme design for each subsystem within each instrumentation and control subsystem according to their respective functions to obtain models for each subsystem. Each subsystem model in each instrumentation and control subsystem model corresponds one-to-one with each subsystem within the respective instrumentation and control subsystem.
[0006] Optionally, the design method for the instrumentation and control system of a nuclear power plant also includes: S3, completing the software and hardware design and manufacturing based on the models of each instrumentation and control subsystem to obtain each instrumentation and control subsystem; S4, verifying each instrumentation and control subsystem using verification methods, obtaining verification results, and analyzing the performance and behavior of each subsystem based on the verification results. Verification methods include review and examination, prototyping and simulation, and modeling and simulation.
[0007] Optionally, S1 includes: S11. Identifying stakeholders related to the instrumentation and control system in various operating scenarios of the nuclear power plant through scenario analysis and task analysis, obtaining stakeholder requirements, and the functions that the instrumentation and control system should perform in each operating scenario, in order to capture the overall requirements of the nuclear power plant's instrumentation and control system. S12. Using scenario analysis, functional data flow analysis, and architecture analysis methods, performing overall requirements analysis on the captured requirements and architecture analysis on the overall instrumentation and control system, determining the boundary scope of the instrumentation and control system, and determining the overall model of the instrumentation and control system based on the boundary scope of the instrumentation and control system and the results of the overall requirements analysis and architecture analysis. S13. Based on the overall model of the instrumentation and control system, allocating the functions of the instrumentation and control system to various instrumentation and control subsystems according to the subsystem division principle, and determining the functions of each instrumentation and control subsystem.
[0008] Optionally, S12 includes: S121. Under various operating scenarios, perform functional data flow analysis, entity relationship analysis, and constraint analysis on the instrumentation and control system. Combine this with the captured requirements to obtain the preliminary requirements of the instrumentation and control system under each operating scenario, and perform an architecture analysis on the overall instrumentation and control system to determine its boundary range. S122. Determine whether there is any overlap in the preliminary requirements of the instrumentation and control system under each operating scenario, and determine the final requirements of the instrumentation and control system under each operating scenario based on the determination results, obtaining the final requirement analysis results for the overall instrumentation and control system. S123. Determine the overall model of the instrumentation and control system based on its boundary range, the final requirement analysis results, and the architecture analysis results. The architecture analysis includes entity relationship analysis and constraint analysis.
[0009] Optionally, S121 includes: S1211, analyzing various operating scenarios from the perspective of instrumentation and control professionals, clarifying the functional and performance requirements of the instrumentation and control system in each operating scenario. S1212, using functional data flow analysis, analyzing the interaction relationships between the functional and performance requirements of the instrumentation and control system in each operating scenario, determining the interaction relationships between the functions of the instrumentation and control system in each operating scenario. S1213, using functional architecture diagrams, analyzing entity relationships based on the interaction relationships between the functions of the instrumentation and control system in each operating scenario, clarifying the functional interaction relationships and forms between the instrumentation and control system and external systems, obtaining the overall architecture analysis results of the instrumentation and control system, and determining the boundary scope of the instrumentation and control system. S1214, combining the captured requirements, performing constraint analysis on the functional and performance requirements of the instrumentation and control system in each operating scenario, determining the performance characteristics of the instrumentation and control system as the preliminary requirements for the instrumentation and control system in each operating scenario. Performance characteristics include response time, accuracy, and security limitations.
[0010] Optionally, S122 includes: S1221. If the preliminary requirements of the instrumentation and control system in each operating scenario do not overlap, the preliminary requirements of the instrumentation and control system in each operating scenario are determined as the final requirements of the instrumentation and control system in each operating scenario. S1222. If the preliminary requirements of the instrumentation and control system in each operating scenario overlap, it is determined whether the overlapping requirements are completely identical. S1223. If the overlapping requirements are completely identical, the overlapping requirements are merged into one requirement, and the merged requirement is taken as the final requirement of the overlapping part of the instrumentation and control system in each operating scenario. S1224. If the overlapping requirements are not completely identical, the different requirements among the overlapping requirements are identified, and each different requirement is further refined, and the result of the further refinement is taken as the final requirement of the overlapping part of the instrumentation and control system in each operating scenario. S1225. Keeping the other preliminary requirements of the instrumentation and control system in each operating scenario unchanged, the final requirements of the instrumentation and control system in each operating scenario include the other preliminary requirements of the instrumentation and control system in each operating scenario and the final requirements of the overlapping part of the instrumentation and control system in each operating scenario. Among them, other preliminary requirements are the preliminary requirements other than the overlapping requirements when there is overlap in the preliminary requirements of the instrumentation and control system under various operating scenarios.
[0011] Optionally, S13 includes: according to the principle of functional similarity, dividing the similar functions of the instrumentation and control system in various operating scenarios into a subsystem, so as to determine the functions of each instrumentation and control subsystem.
[0012] Optionally, S2 includes: S21, capturing the requirements of each subsystem in each instrumentation and control subsystem through scenario analysis, task analysis, and external interaction analysis; S22, performing requirement analysis on the captured requirements of each subsystem in each instrumentation and control subsystem using scenario analysis, functional data flow analysis, and architecture analysis methods, and obtaining the requirement analysis results; S23, performing personalized design on each subsystem in each instrumentation and control subsystem based on the requirement analysis results, and obtaining the model of each instrumentation and control subsystem.
[0013] Secondly, this disclosure provides a design apparatus for a nuclear power plant instrumentation and control system based on MBSE (Mechanical, Instrumentation, and SE). This apparatus includes an overall design module and a subsystem design module. The overall design module is used to capture, analyze, and analyze the overall instrumentation and control requirements and architecture, resulting in an overall model of the instrumentation and control system. Following subsystem partitioning principles, the overall instrumentation and control system functions are allocated to various instrumentation and control subsystems based on the overall model, thus determining the functions of each subsystem. The subsystem design module is used to perform requirements analysis and scheme design for each subsystem within each instrumentation and control subsystem, based on their respective functions, resulting in models for each subsystem. Each subsystem model corresponds one-to-one with each subsystem within the respective instrumentation and control subsystem.
[0014] Thirdly, this disclosure provides an electronic device comprising: at least one processor; and a memory communicatively connected to the at least one processor. The memory stores one or more computer programs executable by the at least one processor, which in turn execute the at least one processor to enable the at least one processor to perform the aforementioned MBSE-based nuclear power plant instrumentation and control system design method.
[0015] Fourthly, this disclosure provides a computer-readable storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements the above-described design method for a nuclear power plant instrumentation and control system based on MBSE.
[0016] Fifthly, this disclosure provides a computer program product that includes computer-readable code or a non-volatile computer-readable storage medium carrying computer-readable code. When the computer-readable code is run in the processor of an electronic device, the processor in the electronic device executes the above-described design method for the instrumentation and control system of a nuclear power plant based on MBSE.
[0017] The embodiments provided in this disclosure perform instrumentation and control system requirements analysis according to a top-down, layer-by-layer decomposition process, realizing layer-by-layer decomposition and traceability from "requirements" to "solutions" and from "overall instrumentation and control" to "subsystems of instrumentation and control", so as to ensure that the top-level design requirements are implemented in the instrumentation and control system and avoid "patching" design optimization problems.
[0018] It should be understood that the description in this section is not intended to identify key or essential features of the embodiments of this disclosure, nor is it intended to limit the scope of this disclosure. Other features of this disclosure will become readily apparent from the following description. Attached Figure Description
[0019] The accompanying drawings are provided to further illustrate the present disclosure and form part of the specification. They are used together with the embodiments of the present disclosure to explain the disclosure and do not constitute a limitation thereof. The above and other features and advantages will become more apparent to those skilled in the art from the detailed description of exemplary embodiments with reference to the accompanying drawings, in which: Figure 1 A flowchart illustrating a design method for a nuclear power plant instrumentation and control system based on MBSE, provided for embodiments of this disclosure; Figure 2 A flowchart illustrating another MBSE-based nuclear power plant instrumentation and control system design method provided for embodiments of this disclosure; Figure 3 A flowchart illustrating yet another MBSE-based design method for nuclear power plant instrumentation and control systems provided in this disclosure; Figure 4 A schematic diagram of the operation analysis of an instrumentation and control system provided in this embodiment of the present disclosure; Figure 5 This is a schematic diagram of the task analysis of the instrumentation and control system for the reactor start-up process provided in an embodiment of the present disclosure; Figure 6 An external interaction diagram of a reactor start-up process instrumentation and control system provided in an embodiment of this disclosure; Figure 7 A flowchart of instrumentation and control system requirements analysis provided for embodiments of this disclosure; Figure 8 A flowchart illustrating yet another MBSE-based design method for nuclear power plant instrumentation and control systems provided in this disclosure; Figure 9 A flowchart illustrating yet another MBSE-based design method for nuclear power plant instrumentation and control systems provided in this disclosure; Figure 10 A schematic diagram illustrating the operation scenario analysis of an instrumentation and control system provided in this embodiment of the present disclosure; Figure 11 A schematic diagram of functional data flow analysis of an instrumentation and control system provided in this embodiment of the present disclosure; Figure 12 A schematic diagram of entity relationship analysis for an instrumentation and control system provided in this embodiment of the present disclosure; Figure 13 A schematic diagram of constraint analysis for an instrumentation and control system provided in an embodiment of this disclosure; Figure 14 A flowchart illustrating yet another MBSE-based design method for nuclear power plant instrumentation and control systems provided in this disclosure; Figure 15 This is a schematic diagram of the function allocation and interface allocation of an instrumentation and control system provided in an embodiment of the present disclosure; Figure 16 A flowchart illustrating yet another MBSE-based design method for nuclear power plant instrumentation and control systems provided in this disclosure; Figure 17 This is a schematic diagram of an operating scenario for a reactor coolant control system provided in an embodiment of the present disclosure; Figure 18 This is a schematic diagram of a reactor coolant control system task during a reactor start-up scenario, provided by an embodiment of the present disclosure. Figure 19 A schematic diagram of external tasks of a reactor coolant control system in a startup scenario provided by an embodiment of this disclosure; Figure 20 A schematic diagram illustrating the equipment-level control function requirements analysis of a reactor coolant control system provided in this embodiment of the present disclosure; Figure 21 A schematic diagram of a main circuit pressure regulation logic provided in an embodiment of this disclosure; Figure 22 A flowchart illustrating yet another MBSE-based design method for nuclear power plant instrumentation and control systems provided in this disclosure; Figure 23 A block diagram of a design device for a nuclear power plant instrumentation and control system based on MBSE, provided for embodiments of this disclosure; Figure 24 This is a block diagram of an electronic device provided in an embodiment of the present disclosure. Detailed Implementation
[0020] To enable those skilled in the art to better understand the technical solutions of this disclosure, exemplary embodiments of this disclosure are described below with reference to the accompanying drawings, including various details of the embodiments of this disclosure to aid understanding. These should be considered merely exemplary. Therefore, those skilled in the art should recognize that various changes and modifications can be made to the embodiments described herein without departing from the scope and spirit of this disclosure. Similarly, for clarity and conciseness, descriptions of well-known functions and structures are omitted in the following description.
[0021] Where there is no conflict, the various embodiments of this disclosure and the features thereof in the embodiments may be combined with each other.
[0022] As used herein, the term “and / or” includes any and all combinations of one or more related enumerated entries.
[0023] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit this disclosure. As used herein, the singular forms “a” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that when the terms “comprising” and / or “made of” are used in this specification, the presence of the stated feature, integral, step, operation, element, and / or component is specified, but the presence or addition of one or more other features, integrals, steps, operations, elements, components, and / or groups thereof is not excluded. Words such as “connected” or “linked” are not limited to physical or mechanical connections but can include electrical connections, whether direct or indirect.
[0024] Unless otherwise specified, all terms used herein (including technical and scientific terms) have the same meaning as commonly understood by one of ordinary skill in the art. It will also be understood that terms such as those defined in commonly used dictionaries should be interpreted as having a meaning consistent with their meaning in the context of the relevant art and this disclosure, and will not be interpreted as having an idealized or overly formal meaning, unless expressly so defined herein.
[0025] The MBSE-based nuclear power plant instrumentation and control system design method according to embodiments of this disclosure can be executed by electronic devices such as terminal devices or servers. Terminal devices can be vehicle-mounted devices, user equipment (UE), mobile devices, user terminals, terminals, cellular phones, cordless phones, personal digital assistants (PDAs), handheld devices, computing devices, vehicle-mounted devices, wearable devices, etc. The method can be implemented by a processor calling computer-readable program instructions stored in memory. Alternatively, the method can be executed by a server.
[0026] Understandably, the design process of a nuclear power plant is divided into different design phases, including the feasibility study / overall design phase, the preliminary design phase, and the construction design phase, each with different objectives. In the embodiments of this disclosure, the design model of the nuclear power plant instrumentation and control system based on MBSE theory is as follows: Figure 1 As shown, it is a multi-dimensional V-model with vertical and horizontal dimensions. It includes four parts: in the feasibility study / overall design section, the instrumentation and control system mainly completes the overall instrumentation and control design; in the preliminary design section, it mainly completes the design of the instrumentation and control subsystems; in the construction design section, it mainly completes the product software and hardware design; and in the verification section, it mainly completes the system verification.
[0027] Figure 2A flowchart illustrating a design method for a nuclear power plant instrumentation and control system based on MBSE, provided for embodiments of this disclosure. (Refer to...) Figure 2 The method includes: In step S1, overall instrumentation and control requirements are captured, analyzed, and analyzed to obtain the overall model of the instrumentation and control system. Based on the overall model and following the subsystem partitioning principle, the functions of the instrumentation and control system are allocated to each subsystem, thus determining the functions of each subsystem.
[0028] In step S2, requirements analysis and scheme design are performed on each subsystem of each instrumentation and control subsystem according to the functions of each instrumentation and control subsystem, and the models of each instrumentation and control subsystem are obtained.
[0029] In step S2, each subsystem model in each instrumentation and control subsystem model corresponds one-to-one with each subsystem in each instrumentation and control subsystem.
[0030] Step S1 implements the overall instrumentation and control system design. During the feasibility study / overall design phase, the overall instrumentation and control system design is primarily completed. This design treats the entire instrumentation and control system as a "black box," analyzing its required functions, performance, and interactions with external systems from an external perspective. The design process includes requirements capture, overall instrumentation and control system requirements analysis, and overall instrumentation and control system architecture analysis, resulting in an overall instrumentation and control system model. In the overall instrumentation and control system architecture design, based on the overall model and following subsystem partitioning principles, the functions of the instrumentation and control system are allocated to corresponding subsystems.
[0031] Step S2 implements the instrumentation and control subsystem design. Based on the functional requirements allocated in the overall instrumentation and control model in step S1, and combined with the detailed design of the process system, a detailed instrumentation and control subsystem design is carried out, including instrumentation and control subsystem requirements analysis, instrumentation and control subsystem scheme design, and instrumentation and control subsystem design verification, forming an instrumentation and control subsystem model.
[0032] According to the embodiments of this disclosure, the requirements analysis of the instrumentation and control system can be carried out in a top-down, layer-by-layer decomposition process, realizing the layer-by-layer decomposition and traceability from "requirements" to "solutions" and from "overall instrumentation and control" to "subsystems of instrumentation and control", so as to ensure that the top-level design requirements are implemented in the instrumentation and control system and avoid the problem of "patching" design optimization.
[0033] In some embodiments, such as Figure 3 As shown, the implementation method of step S1 includes: In step S11, through scenario analysis and task analysis, stakeholders related to the instrumentation and control system are identified in various operating scenarios of the nuclear power plant, stakeholder needs are obtained, and the functions that the instrumentation and control system should perform in each operating scenario are obtained, so as to capture the overall instrumentation and control requirements of the nuclear power plant's instrumentation and control system.
[0034] Understandably, requirements capture involves determining the functions and boundaries of the instrumentation and control system from an external perspective. Through scenario analysis and task analysis, it identifies stakeholders related to the instrumentation and control system in various nuclear power plant scenarios, obtains stakeholder requirements, and defines the functions the instrumentation and control system should perform in each scenario.
[0035] For example, the operation analysis of the instrumentation and control system is as follows: Figure 4 As shown, scenarios include factory operation, transportation / retransportation, power generation, accident operation, and abnormal operation. Taking the accident operation scenario within the power generation scenario as an example, the task analysis of the instrumentation and control system is as follows: Figure 5 As shown in the diagram. In this scenario, the instrumentation and control system should ensure power plant safety and provide emergency shutdown control functions. The corresponding analysis of the interaction between the instrumentation and control system and external systems is as follows: Figure 6 As shown, this analysis reveals that the instrumentation and control system sends control signals to other external systems (e.g., reactor control commands, main loop control commands, secondary loop control commands, and energy management system control commands), and receives feedback signals from external systems (e.g., power signals).
[0036] In step S12, scenario analysis, functional data flow analysis, and architecture analysis methods are used to conduct overall requirements analysis of the instrumentation and control system, as well as architecture analysis of the overall instrumentation and control system, and to determine the boundary range of the instrumentation and control system. Based on the boundary range of the instrumentation and control system and the requirements analysis results and architecture analysis results of the overall instrumentation and control system, the overall model of the instrumentation and control system is determined.
[0037] For example, the requirements analysis process for instrumentation and control systems is as follows: Figure 7 As shown. First, an operational scenario analysis is performed. Under a defined scenario, functional analysis, entity relationship analysis, and other constraint analysis are conducted on the instrumentation and control system (i.e., step S121 below). The functional analysis should also be iterated with the functions obtained from other scenarios (i.e., step S122 below). After the above analysis activities are completed, it is confirmed whether any out-of-scope situations (i.e., exceeding the pre-assumed scenario range) occurred during the analysis process. If so, the operational scenario needs to be redefined and iterated; otherwise, the requirements analysis activity ends.
[0038] In some embodiments, such as Figure 8 As shown, the implementation method of step S12 includes: In step S121, under each operating scenario, functional data flow analysis, entity relationship analysis, and constraint analysis are performed on the instrumentation and control system. Combined with the captured requirements, the preliminary requirements of the instrumentation and control system under each operating scenario are obtained. Furthermore, the overall architecture of the instrumentation and control system is analyzed, and the boundary range of the instrumentation and control system is determined.
[0039] In step S121, the architecture analysis includes entity relationship analysis and constraint analysis.
[0040] In some embodiments, such as Figure 9 As shown, the implementation method of step S121 includes: In step S1211, the analysis of various operating scenarios is carried out from the perspective of instrumentation and control professionals, and the functional and performance requirements of the instrumentation and control system under various operating scenarios are clarified.
[0041] For example, taking a nuclear power project accident handling scenario as an example, the operation scenario analysis of the instrumentation and control system is as follows: Figure 10 As shown, when the reactor experiences a first set of control rod uncontrolled extraction accidents, reactivity increases. When the instrumentation and control system detects that the reactivity has reached the shutdown threshold, it generates an emergency shutdown signal. This signal is sent to the electrical system, which disconnects the shutdown circuit breaker, enabling the control rod insertion function. The response time for handling this shutdown accident is 10 seconds, with 1 second allocated to the instrumentation and control system. In other words, the instrumentation and control system's functionality and performance requirement for handling this shutdown accident is a response time of 1 second.
[0042] In step S1212, functional data flow analysis is used to analyze the interaction relationship between the functions and performance requirements of the instrumentation and control system under various operating scenarios, and to determine the interaction relationship between the functions of the instrumentation and control system under various operating scenarios.
[0043] Understandably, based on step S1211, step S1212 uses functional data flow analysis to conduct a detailed analysis of the functions obtained from the operation scenario analysis, and determines the interaction relationships between the functions.
[0044] For example, taking the central control rod control function of a nuclear power project as an example, the data flow analysis of the instrumentation and control system functions is as follows: Figure 11 As shown. In an accident handling scenario, when the automatic emergency shutdown control function fails, the central control rod diversified shutdown function is triggered, and the control rod position is adjusted. In a power operation scenario, when the user-tracked load changes significantly (such as load shedding), the central control rod diversified shutdown function is triggered, and the control rod position is adjusted.
[0045] In step S1213, the functional architecture diagram is used to perform entity relationship analysis based on the interaction relationship between the functions of the instrumentation and control system in various operating scenarios. The functional interaction relationship and functional interaction form between the instrumentation and control system and external systems are sorted out to obtain the overall architecture analysis results of the instrumentation and control system and determine the boundary range of the instrumentation and control system.
[0046] Understandably, based on step S1212, step S1213 uses a functional architecture diagram to perform entity relationship analysis based on the interaction relationships between the functions of the instrumentation and control system in various operating scenarios. This is mainly used to sort out the functional interactions between the instrumentation and control system and external systems, as well as the forms of functional interactions, in order to clarify the scope and boundaries of the instrumentation and control system.
[0047] Understandably, clearly defining the scope and boundaries of the instrumentation and control system means: within the entire system, drawing the functions belonging to the instrumentation and control system into a separate scope (e.g., Figure 12 As shown, the scope and boundaries of the instrumentation and control system can be clearly defined by the frame in the middle.
[0048] For example, taking a nuclear power project as an example, the entity relationship analysis of the instrumentation and control system is as follows: Figure 12 As shown, this analysis clarifies the functions that the instrumentation and control system should achieve, and the communication methods between the instrumentation and control system and the reactor, energy management system, heat sink system, energy conversion system, reactor cooling system, electrical system, and reactor pressure regulation system.
[0049] In step S1214, the functional and performance requirements of the instrumentation and control system under various operating scenarios are constrained by the captured requirements to determine the performance characteristics of the instrumentation and control system as the preliminary requirements of the instrumentation and control system under various operating scenarios.
[0050] In step S1214, performance characteristics include response time, accuracy, and security limitations.
[0051] Understandably, based on step S1213, step S1214 performs a constraint analysis on the function to obtain the performance characteristics of the instrumentation and control system, including limitations on response time, accuracy, and safety.
[0052] For example, taking the response time constraint analysis of a nuclear power project as an example, such as... Figure 13 As shown, the response time of the entire instrumentation and control system is 1 second, of which the response time of the power range instrument detection is 100 ms, and the time for power range calculation and processing, power range threshold comparison and automatic triggering of emergency shutdown logic judgment is 900 ms.
[0053] In step S122, it is determined whether there is any overlap in the preliminary requirements of the instrumentation and control system under each operating scenario, and the final requirements of the instrumentation and control system under each operating scenario are determined based on the determination results.
[0054] It is understandable that instrumentation and control systems may have overlapping requirements in different operating scenarios. To avoid resource waste and simplify system processes, iterative analysis of requirements under different operating scenarios can be performed during requirements analysis.
[0055] In some embodiments, such as Figure 14 As shown, the implementation method of step S122 includes: In step S1221, if there is no overlap in the preliminary requirements of the instrumentation and control system under each operating scenario, the preliminary requirements of the instrumentation and control system under each operating scenario are determined as the final requirements of the instrumentation and control system under each operating scenario.
[0056] For example, overlapping requirements refer to situations where both scenarios require controlling the pressure on a certain device, but the specific pressure values may be the same or different in different operating scenarios. This will be discussed in detail below.
[0057] In step S1222, if the initial requirements of the instrumentation and control system overlap in various operating scenarios, it is determined whether the overlapping requirements are completely identical.
[0058] In step S1223, if the overlapping requirements are exactly the same, the overlapping requirements are merged into one requirement, and the merged requirement is taken as the final requirement of the overlapping part of the instrumentation and control system in each operating scenario.
[0059] For example, overlapping requirements being exactly the same means that, in two or more different operating scenarios, the pressure value of a certain device must be controlled at a first pressure value (a specific pressure value).
[0060] In step S1224, if the overlapping requirements are not completely identical, the different requirements among the overlapping requirements are identified, and each of the different requirements is further refined. The results of the further refinement are taken as the final requirements of the overlapping part of the instrumentation and control system in each operating scenario.
[0061] For example, overlapping requirements that are not entirely the same mean that, under different operating scenarios, the pressure value of a certain device is always the first pressure value (a specific pressure value).
[0062] In step S1225, the other preliminary requirements of the instrumentation and control system under each operating scenario remain unchanged. The final requirements of the instrumentation and control system under each operating scenario include the other preliminary requirements of the instrumentation and control system under each operating scenario and the final requirements of the overlapping parts of the requirements of the instrumentation and control system under each operating scenario.
[0063] In step S1215, other preliminary requirements are the preliminary requirements other than the overlapping requirements when there is overlap in the preliminary requirements of the instrumentation and control system under various operating scenarios.
[0064] Understandably, the initial requirements for non-overlapping parts do not require special processing and can therefore remain unchanged. By merging the adjusted requirements with these unchanged initial requirements, we can obtain the final requirements of the instrumentation and control system under various operating scenarios.
[0065] In step S123, the overall model of the instrumentation and control system is determined based on the boundary range of the instrumentation and control system and the final requirements analysis and architecture analysis results of the overall instrumentation and control system.
[0066] In step S13, based on the overall model of the instrumentation and control system and according to the subsystem division principle, the functions of the instrumentation and control system are allocated to each instrumentation and control subsystem, and the functions of each instrumentation and control subsystem are determined.
[0067] Understandably, step S13 involves allocating the instrumentation and control system functional requirements obtained in step S1212, the entity relationships obtained in step S1213, and the performance characteristics obtained in step S1214 to each instrumentation and control subsystem.
[0068] In some embodiments, the implementation method of step S13 includes: according to the principle of functional similarity, dividing the similar functions of the instrumentation and control system in various operating scenarios into a subsystem, so as to determine the functions of each instrumentation and control subsystem.
[0069] Understandably, other principles can also be followed for allocation, depending on the application scenario. For example, according to the principle of local control and centralized control, all functions that require local operation can be centralized into a unified local control system, and all centralized operation functions can be allocated to a centralized control system.
[0070] For example, taking a nuclear power project as an example, the division of the instrumentation and control subsystem is shown in Table 1.
[0071] Table 1 Division of Instrumentation and Control Subsystem
[0072] In the aforementioned system, the main control system, reactor coolant control system, energy conversion control system, auxiliary control system, rod control and rod positioning system, reactor protection system, and human-machine interface system primarily fulfill the system control logic requirements and human-machine interface design requirements. Specific hardware functions are implemented by the signal acquisition, processing, and monitoring system. The corresponding instrumentation and control system function allocation and interface allocation are as follows: Figure 15 As shown in Table 1, the specific functions implemented by the main control system, reactor coolant control system, energy conversion control system, auxiliary control system, rod control and rod position system, reactor protection system, human-machine interface system, external nuclear measurement system, and integrated measurement system are as follows. The interfaces between these systems include both hard-wiring and communication methods. The interface between the instrumentation and control system and the energy management system is implemented by the signal acquisition, processing, and monitoring system, and the interface methods include both hard-wiring and communication methods.
[0073] Based on step S1, step S2, namely the design of the instrumentation and control subsystem, is executed. The design methods for the main control system, reactor coolant control system, energy conversion control system, auxiliary control system, rod control and rod position system, reactor protection system, and human-machine interface system are the same: all involve requirement capture, requirement analysis, and scheme design based on the functions allocated from the overall instrumentation and control system in step S1. In addition to inheriting the functions allocated from the overall instrumentation and control system, the signal acquisition, processing, and monitoring system also needs to collect specific requirements from the main control system, reactor coolant control system, energy conversion control system, auxiliary control system, rod control and rod position system, reactor protection system, and human-machine interface system to complete the implementation of hardware functions.
[0074] The implementation method of step S2 will be described in detail below, taking the reactor coolant control system and signal acquisition, processing and monitoring system as examples.
[0075] In some embodiments, such as Figure 16 As shown, the implementation method of step S2 includes: In step S21, requirements are captured for each subsystem in each instrumentation and control subsystem by running scenario analysis, task analysis, and external interaction analysis.
[0076] Understandably, the method of step S21 is similar to that of step S11.
[0077] Taking the reactor coolant control system of a nuclear power project as an example, the operating scenario analysis of this system is as follows: Figure 17 As shown, the main operational scenarios this system participates in include plant operation, transport / retransport, abnormal operation, and power generation. Taking the reactor start-up scenario as an example, the tasks that the reactor coolant control system should complete are as follows: Figure 18 As shown, it mainly performs main loop boundary isolation control, shaft sealing gas control, and main helium blower control. The reactor coolant system interacts with external tasks as follows: Figure 19 As shown, during the reactor start-up process, the reactor coolant control system receives function group call instructions from the main control system and provides control instructions to specific control devices of the reactor coolant system, such as valves and fans.
[0078] In step S22, scenario analysis, functional data flow analysis, and architecture analysis methods are used to perform requirement analysis on the requirements of each subsystem in each captured instrumentation and control subsystem, and the requirement analysis results are obtained.
[0079] Understandably, based on step S21, step S22 uses scenario analysis, functional data flow analysis, architecture analysis and other means to complete the requirements analysis of the instrumentation and control subsystem. The analysis method is similar to that of step S12.
[0080] For example, taking the reactor coolant system of a nuclear power project as an example, a functional data flow analysis is performed on it, such as... Figure 20 As shown, the main control system calls the corresponding sub-function group (numbered CRH-1FC-0901) of the reactor coolant control system according to the power plant's operating mode. The reactor coolant control system then calls the corresponding equipment-level control function (numbered CRH-1FC-0902) to complete the corresponding control logic, sends the corresponding control commands to the execution structure (e.g., valves, fans), and completes the corresponding status parameter display (numbered CRH-1FC-0903).
[0081] For example, taking the signal acquisition, processing, and monitoring system of a nuclear power project as an example, the signal acquisition, processing, and monitoring system mainly realizes functions such as isolation distribution, signal acquisition, signal output, data communication, logic control, data processing, data storage, and configuration maintenance. Among them, signal acquisition, signal output, and control logic come from the system function requirements in step S21. Taking the signal acquisition function as an example, the detailed signal acquisition requirements are shown in Table 2.
[0082] Table 2 Detailed Signal Acquisition Requirements
[0083] In step S23, each subsystem of each instrumentation and control subsystem is individually designed based on the requirements analysis results to obtain the model of each instrumentation and control subsystem.
[0084] Understandably, each subsystem needs to be customized according to its own requirements.
[0085] For example, a reactor coolant control system requires detailed control logic design for each function. Taking the main loop pressure regulation in a reactor coolant control system as an example, the simplified control logic diagram is as follows: Figure 21As shown. The goal of main loop pressure regulation is to maintain the main loop pressure within a certain range during various operating stages of the gas-cooled microreactor. This is achieved by opening the exhaust isolation valve 10KBB10AA119 to release the main loop pressure to the low-pressure tank, thus reducing the main loop pressure. Helium is then introduced into the main loop by opening the charging isolation valve 10KBB10AA117 and simultaneously calculating the opening degree of the regulating valve 10KBB10AA206 based on the deviation between the main loop pressure and the setpoint. The pressure control objectives differ under different operating scenarios. During the cold start-up phase, the pressure is kept within limits, and only the exhaust isolation valve is used. During the hot power-up phase, the main loop pressure setpoint is adjusted according to the pressure setting value of the main control module; the pressure setting value determination scheme is detailed in the main control module control instructions. During steady-state operation, the pressure setpoint is the pressure required for reactor-machine coordination control, derived from the main control module. The main loop pressure measurement value is acquired by the protection system. The main loop pressure setpoint is selected according to the main control command and can also be modified in the human-machine interface module.
[0086] For example, in a signal acquisition, processing, and monitoring system, the signal interaction function needs to be allocated to a single physical device to reduce the number of cables required for signal transmission between different devices. Taking a nuclear power project as an example, the signal function allocation in the power generation scenario is shown in Table 3.
[0087] Understandably, after completing the design according to the above steps, the product software and hardware design and design verification phase can begin. In some embodiments, such as... Figure 22 As shown, the MBSE-based design methodology for nuclear power plant instrumentation and control systems also includes: In step S3, the hardware and software design and manufacturing are completed based on the models of each instrumentation and control subsystem to obtain each instrumentation and control subsystem.
[0088] Step S3 involves the product's hardware and software design. Based on the typical functional requirements of the instrumentation and control subsystem model in step S2, and combined with the product's characteristics, detailed hardware and software design, as well as processing and manufacturing, are completed.
[0089] In step S4, verification methods are used to verify each instrumentation and control subsystem, and the verification results are obtained. Based on the verification results, the performance and behavior of each subsystem are analyzed. Verification methods include review and examination, prototyping and simulation, and modeling and simulation.
[0090] Step S4 involves design verification, commonly employing methods such as review and examination, prototyping and simulation, and modeling and simulation. Review and examination are frequently used methods, involving stakeholders and industry experts through pre-defined checklists to thoroughly discuss and review the requirements' content, objectives, expected effects, consistency, and the feasibility, logical flaws, and technical implementation difficulties of the technical solutions. This ensures the accuracy and completeness of the requirements and the consistency between the requirements and the proposed solutions. Prototyping and simulation involve building simulators for key functions, using these simulators to simulate the system's operation in different scenarios. This allows stakeholders to intuitively experience some of the system's functions and operational processes, promptly identifying discrepancies between requirements and actual expectations. Modeling and simulation involve establishing corresponding mathematical models to describe the system's behavior and characteristics for systems with clear mathematical relationships and performance requirements. Simulation analysis is then performed using these mathematical models, employing computer software to simulate the system's operation. By changing the model's parameters and input conditions, the system's output results are observed, and the system's performance and behavior are analyzed.
[0091] It is understood that the various method embodiments mentioned above in this disclosure can be combined with each other to form combined embodiments without violating the principle and logic. Due to space limitations, this disclosure will not elaborate further. Those skilled in the art will understand that in the above methods of specific implementation, the specific execution order of each step should be determined by its function and possible internal logic.
[0092] In addition, this disclosure also provides a design device, electronic equipment, and computer-readable storage medium for a nuclear power plant instrumentation and control system based on MBSE. All of the above can be used to implement any of the design methods for a nuclear power plant instrumentation and control system based on MBSE provided in this disclosure. The corresponding technical solutions and descriptions are described in the corresponding descriptions in the method section and will not be repeated here.
[0093] Table 3 Signal Function Allocation for Power Generation Scenarios
[0094] Figure 23 This is a block diagram of a design device for a nuclear power plant instrumentation and control system based on MBSE, provided for embodiments of this disclosure.
[0095] Reference Figure 23 This disclosure provides a design device for a nuclear power plant instrumentation and control system based on MBSE. The MBSE-based nuclear power plant instrumentation and control system design device 2300 includes an overall design module 2301 and a subsystem design module 2302.
[0096] The overall design module 2301 is used to capture, analyze, and analyze the overall instrumentation and control requirements and architecture, thereby obtaining the overall model of the instrumentation and control system. Based on the overall model and following the subsystem partitioning principle, the functions of the instrumentation and control system are allocated to each subsystem, and the functions of each subsystem are determined.
[0097] The subsystem design module 2302 is used to perform requirements analysis and scheme design for each subsystem in each instrumentation and control subsystem according to the functions of each instrumentation and control subsystem, and to obtain the model of each instrumentation and control subsystem. Among them, each subsystem model in each instrumentation and control subsystem model corresponds one-to-one with each subsystem in the instrumentation and control subsystem.
[0098] Figure 24 This is a block diagram of an electronic device provided in an embodiment of the present disclosure.
[0099] Reference Figure 24 This disclosure provides an electronic device comprising: at least one processor 2401; at least one memory 2402; and one or more I / O interfaces 2403 connected between the processor 2401 and the memory 2402; wherein the memory 2402 stores one or more computer programs executable by the at least one processor 2401, and the one or more computer programs are executed by the at least one processor 2401 to enable the at least one processor 2401 to execute the above-described design method for a nuclear power plant instrumentation and control system based on MBSE.
[0100] This disclosure also provides a computer-readable storage medium storing a computer program thereon, wherein the computer program, when executed by a processor, implements the aforementioned MBSE-based nuclear power plant instrumentation and control system design method. The computer-readable storage medium may be volatile or non-volatile.
[0101] This disclosure also provides a computer program product, including computer-readable code, or a non-volatile computer-readable storage medium carrying computer-readable code. When the computer-readable code is run in a processor of an electronic device, the processor in the electronic device executes the above-described design method for a nuclear power plant instrumentation and control system based on MBSE.
[0102] Those skilled in the art will understand that all or some of the steps, systems, and apparatuses disclosed above, and their functional modules / units, can be implemented as software, firmware, hardware, or suitable combinations thereof. In hardware implementations, the division between functional modules / units mentioned above does not necessarily correspond to the division of physical components; for example, a physical component may have multiple functions, or a function or step may be performed collaboratively by several physical components. Some or all physical components may be implemented as software executed by a processor, such as a central processing unit, digital signal processor, or microprocessor, or as hardware, or as an integrated circuit, such as an application-specific integrated circuit (ASIC). Such software can be distributed on a computer-readable storage medium, which may include computer storage media (or non-transitory media) and communication media (or transient media).
[0103] As is known to those skilled in the art, the term computer storage medium includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storing information, such as computer-readable program instructions, data structures, program modules, or other data. Computer storage media includes, but is not limited to, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), static random access memory (SRAM), flash memory or other memory technologies, portable compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical disc storage, magnetic cartridges, magnetic tape, disk storage or other magnetic storage devices, or any other medium that can be used to store desired information and is accessible to a computer. Furthermore, it is known to those skilled in the art that communication media typically contain computer-readable program instructions, data structures, program modules, or other data in modulated data signals such as carrier waves or other transmission mechanisms, and may include any information delivery medium.
[0104] The computer-readable program instructions described herein can be downloaded from computer-readable storage media to various computing / processing devices, or downloaded via a network, such as the Internet, local area network, wide area network, and / or wireless network, to an external computer or external storage device. The network may include copper transmission cables, fiber optic transmission, wireless transmission, routers, firewalls, switches, gateway computers, and / or edge servers. A network adapter card or network interface in each computing / processing device receives the computer-readable program instructions from the network and forwards them to the computer-readable storage media in the respective computing / processing device.
[0105] Computer program instructions used to perform the operations of this disclosure may be assembly instructions, instruction set architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, firmware instructions, status setting data, or source code or object code written in any combination of one or more programming languages, including object-oriented programming languages such as Smalltalk, C++, etc., and conventional procedural programming languages such as the "C" language or similar programming languages. The computer-readable program instructions may execute entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving a remote computer, the remote computer may be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or may be connected to an external computer (e.g., via the Internet using an Internet service provider). In some embodiments, electronic circuitry, such as programmable logic circuitry, field-programmable gate arrays (FPGAs), or programmable logic arrays (PLAs), is personalized by utilizing the status information of the computer-readable program instructions to implement various aspects of this disclosure.
[0106] The computer program product described herein can be implemented specifically through hardware, software, or a combination thereof. In one alternative embodiment, the computer program product is specifically embodied in a computer storage medium; in another alternative embodiment, the computer program product is specifically embodied in a software product, such as a software development kit (SDK), etc.
[0107] Various aspects of this disclosure are described herein with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this disclosure. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer-readable program instructions.
[0108] These computer-readable program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus to produce a machine such that, when executed by the processor of the computer or other programmable data processing apparatus, they create means for implementing the functions / actions specified in one or more blocks of the flowchart and / or block diagram. These computer-readable program instructions can also be stored in a computer-readable storage medium that causes a computer, programmable data processing apparatus, and / or other device to operate in a particular manner; thus, the computer-readable medium storing the instructions comprises an article of manufacture that includes instructions for implementing aspects of the functions / actions specified in one or more blocks of the flowchart and / or block diagram.
[0109] Computer-readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable data processing apparatus, or other device to produce a computer-implemented process, thereby causing the instructions executed on the computer, other programmable data processing apparatus, or other device to perform the functions / actions specified in one or more boxes of a flowchart and / or block diagram.
[0110] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present disclosure. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of an instruction containing one or more executable instructions for implementing a specified logical function. In some alternative implementations, the functions marked in the blocks may occur in a different order than those shown in the drawings. For example, two consecutive blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, may be implemented using a dedicated hardware-based system that performs the specified function or action, or using a combination of dedicated hardware and computer instructions.
[0111] Example embodiments have been disclosed herein, and while specific terminology has been used, it is for illustrative purposes only and should be construed as such, and is not intended to be limiting. In some instances, it will be apparent to those skilled in the art that features, characteristics, and / or elements described in connection with particular embodiments may be used alone, or in combination with features, characteristics, and / or elements described in connection with other embodiments, unless otherwise expressly indicated. Therefore, those skilled in the art will understand that various changes in form and detail may be made without departing from the scope of this disclosure as set forth by the appended claims.
Claims
1. A design method for a nuclear power plant instrumentation and control system based on MBSE, characterized in that, include: S1. Perform overall instrumentation and control requirements capture, overall instrumentation and control requirements analysis, and overall instrumentation and control architecture analysis to obtain the overall instrumentation and control system model; and according to the subsystem division principle, allocate the functions of the instrumentation and control system to each instrumentation and control subsystem based on the overall instrumentation and control system model, and determine the functions of each instrumentation and control subsystem. S2. Based on the functions of each instrumentation and control subsystem, perform requirements analysis and scheme design for each subsystem in each instrumentation and control subsystem to obtain an instrumentation and control subsystem model; each subsystem model in each instrumentation and control subsystem model corresponds one-to-one with each subsystem in each instrumentation and control subsystem.
2. The design method for a nuclear power plant instrumentation and control system based on MBSE according to claim 1, characterized in that, Also includes: S3. Based on the models of each instrumentation and control subsystem, complete the software and hardware design and manufacturing to obtain each instrumentation and control subsystem; S4. Verify each instrumentation and control subsystem using verification methods, obtain verification results, and analyze the performance and behavior of each subsystem based on the verification results; the verification methods include review and examination, prototyping and simulation, modeling and simulation.
3. The design method for a nuclear power plant instrumentation and control system based on MBSE according to claim 1, characterized in that, S1 includes: S11. Through operational scenario analysis and task analysis, identify the stakeholders related to the instrumentation and control system in various operational scenarios of the nuclear power plant, obtain the stakeholders' needs, and the functions that the instrumentation and control system should perform in each operational scenario, so as to capture the overall requirements of the nuclear power plant's instrumentation and control system. S12. Using scenario analysis, functional data flow analysis, and architecture analysis methods, perform overall requirements analysis on the captured requirements and architecture analysis on the overall instrumentation and control system, determine the boundary range of the instrumentation and control system, and determine the overall model of the instrumentation and control system based on the boundary range of the instrumentation and control system and the requirements analysis results and architecture analysis results of the overall instrumentation and control system. S13. Based on the overall model of the instrumentation and control system, the functions of the instrumentation and control system are allocated to each instrumentation and control subsystem according to the subsystem division principle, and the functions of each instrumentation and control subsystem are determined.
4. The design method for a nuclear power plant instrumentation and control system based on MBSE according to claim 3, characterized in that, S12 includes: S121. Under various operating scenarios, perform functional data flow analysis, entity relationship analysis, and constraint analysis on the instrumentation and control system. Combine the captured requirements to obtain the preliminary requirements of the instrumentation and control system under various operating scenarios, and perform overall architecture analysis on the instrumentation and control system to determine the boundary range of the instrumentation and control system; the architecture analysis includes entity relationship analysis and constraint analysis. S122. Determine whether there is any overlap in the preliminary requirements of the instrumentation and control system under various operating scenarios, and determine the final requirements of the instrumentation and control system under various operating scenarios based on the judgment results, and obtain the final requirement analysis results of the overall instrumentation and control system. S123. Determine the overall model of the instrumentation and control system based on the boundary range of the instrumentation and control system and the final requirements analysis and architecture analysis results of the overall instrumentation and control system.
5. The design method for a nuclear power plant instrumentation and control system based on MBSE according to claim 4, characterized in that, S121 includes: S1211. Analyze various operating scenarios from the perspective of instrumentation and control professionals, and clarify the functional and performance requirements of the instrumentation and control system in each operating scenario; S1212. Using functional data flow analysis, the interaction relationship between the functions and performance requirements of the instrumentation and control system under various operating scenarios is analyzed to determine the interaction relationship between the functions of the instrumentation and control system under various operating scenarios. S1213. Using the functional architecture diagram, perform entity relationship analysis based on the interaction relationship between the functions of the instrumentation and control system in various operating scenarios, sort out the functional interaction relationship and functional interaction form between the instrumentation and control system and external systems, obtain the overall architecture analysis results of the instrumentation and control system, and determine the boundary range of the instrumentation and control system. S1214. Based on the captured requirements, perform constraint analysis on the functional and performance requirements of the instrumentation and control system under various operating scenarios to determine the performance characteristics of the instrumentation and control system as the preliminary requirements of the instrumentation and control system under various operating scenarios; the performance characteristics include response time, accuracy and security limitations.
6. The design method for a nuclear power plant instrumentation and control system based on MBSE according to claim 4, characterized in that, S122 includes: S1221. If there is no overlap in the preliminary requirements of the instrumentation and control system under each operating scenario, the preliminary requirements of the instrumentation and control system under each operating scenario shall be determined as the final requirements of the instrumentation and control system under each operating scenario. S1222. If the initial requirements of the instrumentation and control system overlap in various operating scenarios, determine whether the overlapping requirements are completely identical. S1223. If the overlapping requirements are exactly the same, the overlapping requirements shall be merged into one requirement, and the merged requirement shall be used as the final requirement of the overlapping part of the instrumentation and control system in each operating scenario. S1224. If the overlapping requirements are not completely the same, identify the different requirements among the overlapping requirements, further refine each of the different requirements, and take the results of further refinement as the final requirements of the overlapping part of the instrumentation and control system in each operating scenario. S1225. Keep the other preliminary requirements of the instrumentation and control system unchanged in each operating scenario. The final requirements of the instrumentation and control system in each operating scenario include the other preliminary requirements of the instrumentation and control system in each operating scenario and the final requirements of the overlapping part of the requirements of the instrumentation and control system in each operating scenario. The other preliminary requirements are the part of the preliminary requirements of the instrumentation and control system other than the overlapping requirements when there is a part of overlapping requirements in the preliminary requirements of the instrumentation and control system in each operating scenario.
7. The design method for a nuclear power plant instrumentation and control system based on MBSE according to claim 3, characterized in that, S13 includes: according to the principle of functional similarity, dividing the similar functions of the instrumentation and control system in various operating scenarios into a subsystem, so as to determine the functions of each instrumentation and control subsystem.
8. The design method for a nuclear power plant instrumentation and control system based on MBSE according to claim 1, characterized in that, S2 include: S21. Through scenario analysis, task analysis, and external interaction analysis, requirements are captured for each subsystem in each instrumentation and control subsystem. S22. Using scenario analysis, functional data flow analysis, and architecture analysis methods, perform requirement analysis on the requirements of each subsystem in the captured instrumentation and control subsystems to obtain the requirement analysis results. S23. Based on the requirements analysis results, each subsystem of the instrumentation and control subsystem is individually designed to obtain the model of each instrumentation and control subsystem.
9. A design device for a nuclear power plant instrumentation and control system based on MBSE, characterized in that, include: The overall design module is used to capture, analyze, and analyze the overall instrumentation and control requirements and architecture to obtain the overall model of the instrumentation and control system. Based on the overall model of the instrumentation and control system, the module allocates the functions of the instrumentation and control system to each instrumentation and control subsystem according to the subsystem division principle, and determines the functions of each instrumentation and control subsystem. The subsystem design module is used to perform requirements analysis and scheme design for each subsystem in each instrumentation and control subsystem according to the functions of each instrumentation and control subsystem, and to obtain the model of each instrumentation and control subsystem; each subsystem model in each instrumentation and control subsystem model corresponds one-to-one with each subsystem in each instrumentation and control subsystem.
10. An electronic device, characterized in that, include: At least one processor; as well as A memory communicatively connected to the at least one processor; wherein, The memory stores one or more computer programs that can be executed by the at least one processor, and the one or more computer programs are executed by the at least one processor to enable the at least one processor to execute the MBSE-based nuclear power plant instrumentation and control system design method as described in any one of claims 1-8.
11. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the design method of the nuclear power plant instrumentation and control system based on MBSE as described in any one of claims 1-8.
12. A computer program product, characterized in that, Includes computer-readable code, or a non-volatile computer-readable storage medium carrying computer-readable code, wherein when the computer-readable code is run in a processor of an electronic device, the processor in the electronic device executes the MBSE-based nuclear power plant instrumentation and control system design method as described in any one of claims 1-8.