Method and apparatus for digitizing system flow diagram of nuclear power plant, and related device

Abstract

The present application provides a method and apparatus for digitizing a system flow diagram of a nuclear power plant, and a related device. The method comprises: acquiring a plurality of flow diagram files corresponding to a target nuclear power plant and item attributes of a plurality of items, wherein each flow diagram file comprises a plurality of pieces of graphic symbol information, and each piece of graphic symbol information is used to represent a type of item; constructing a flow diagram directory tree on the basis of the plurality of flow diagram files and the item attribute of the item corresponding to each piece of graphic symbol information, wherein the flow diagram directory tree comprises a diagram directory level and an item directory level, the diagram directory level comprises at least one flow diagram file, and the item directory level comprises at least one item; determining a corresponding target digitized element from the diagram directory level or the item directory level; and displaying the target digitized element in a preset diagram display area. The present application can improve the analysis efficiency of various operations in nuclear power plant systems by means of a digitized flow diagram.

Description

Methods, devices and related equipment for digitizing nuclear power plant system flowcharts Technical Field

[0001] This application relates to the field of nuclear power plant digitization, and in particular to a method, apparatus and related equipment for digitizing nuclear power plant system flowcharts. Background Technology

[0002] Nuclear power plant system flowcharts are crucial technical documents in the design, construction, and operation of nuclear power plants. They serve as the core carrier reflecting the technological processes, equipment layout, and control logic of each system within the plant. From design to on-site construction, commissioning, and maintenance, every stage requires adherence to the system flowcharts. The way these flowcharts are presented and the efficiency of their application directly impact the overall quality of work throughout the nuclear power plant's lifecycle.

[0003] In related technologies, nuclear power plants use paper documents or static formats such as PDFs to transmit system flowcharts. This approach suffers from problems such as low document retrieval efficiency, difficulty in real-time updating of drawing information, and ineffective data correlation. While digitizing flowcharts by vectorizing PDF drawings is an option, this method not only increases manpower and economic costs but also easily leads to inconsistencies between on-site and design data. Therefore, how to improve the analytical efficiency of various operations in nuclear power plant systems through digitized flowcharts is a pressing technical problem that needs to be solved. Summary of the Invention

[0004] This application aims to address at least one of the technical problems existing in the prior art. To this end, this application provides a method, apparatus, and related equipment for digitizing nuclear power plant system flowcharts, which helps improve the analysis efficiency of various operations in nuclear power plant systems.

[0005] In a first aspect, embodiments of this application provide a method for digitizing a nuclear power plant system flowchart, including:

[0006] Obtain multiple process drawing files and multiple item attributes corresponding to the target nuclear power plant; wherein, each process drawing file includes multiple symbol information, and each symbol information is used to represent a type of item;

[0007] Based on the multiple process drawing files and the item attributes corresponding to each of the symbol information, a process drawing directory tree is constructed; wherein, the process drawing directory tree includes a drawing directory level and an item catalog level, the drawing directory level includes at least one of the process drawing files, and the item catalog level includes at least one of the items.

[0008] Determine the corresponding target digitized element from the drawing catalog level or the item catalog level;

[0009] The target digitized element is displayed in the preset drawing display area.

[0010] In some embodiments, the flowchart directory tree further includes a project directory level, a unit directory level, a system directory level, an item type directory level, and a sub-item directory level. The project directory level includes at least one unit directory level, the unit directory level includes at least one system directory level, the system directory level includes at least one flowchart drawing file directory level, the flowchart drawing file directory level includes at least one item type directory level, and the item type directory level includes at least one item level. Based on the plurality of flowchart drawing files and the item attributes corresponding to each symbol information for the item, a flowchart directory tree is constructed, including:

[0011] Obtain the drawing number of each process drawing file, and obtain the unit number and system information corresponding to each process drawing file based on the drawing number;

[0012] The project directory hierarchy is constructed based on the target nuclear power plant;

[0013] The unit directory hierarchy is constructed under the project directory hierarchy based on each of the aforementioned unit numbers;

[0014] Based on the system information corresponding to each process drawing file, the system directory hierarchy is constructed under the corresponding unit directory hierarchy;

[0015] Based on each drawing number, the drawing directory hierarchy is constructed under the corresponding system directory hierarchy;

[0016] Based on the item attributes corresponding to each item, construct the item type directory hierarchy under the corresponding drawing directory hierarchy;

[0017] Based on the item attributes of each item, construct the item catalog level under the corresponding item type catalog level;

[0018] When the item attribute of the item includes sub-item information, the sub-item catalog level is constructed under the corresponding item catalog level based on the sub-item information.

[0019] In some embodiments, the method further includes:

[0020] The search box is displayed in a preset position within the preset directory tree display area;

[0021] In response to the input of a search value in the search box, a query is performed in the flowchart directory tree based on the search value;

[0022] When a directory level that matches the search value is found, the directory level that matches the search value is determined as the target directory level.

[0023] Jump the content displayed in the directory tree display area to the target directory level.

[0024] In some embodiments, the flowchart drawing file is stored in a flowchart database. When no directory level matching the search value is found, the method further includes:

[0025] The process diagram file corresponding to the search value is obtained by querying the process diagram database.

[0026] Update the flowchart directory tree based on the flowchart drawing file corresponding to the search value;

[0027] In the updated flowchart directory tree, a query is performed based on the value to be searched, and the queried directory level is determined as the target directory level;

[0028] Jump the content displayed in the directory tree display area to the target directory level.

[0029] In some embodiments, when the value to be searched is the code of the target item, the method further includes:

[0030] The target item code is used to search the flowchart database to identify multiple flowchart drawing files;

[0031] The first obtained process drawing file is displayed as the main display drawing in the drawing display area, and the item corresponding to the target item code is located and highlighted in the main display drawing;

[0032] The remaining process drawing files will be displayed sequentially in the drawing display area in tab format;

[0033] In response to selecting any of the tabs, the flowchart paper file corresponding to the tab is switched and displayed, and the item is positioned and highlighted.

[0034] In some embodiments, the method further includes:

[0035] In response to selecting a process drawing file in the directory tree display area and triggering a logic diagram generation operation, the connection relationship data of pipes and equipment in the process drawing file is obtained according to the item attributes of each item;

[0036] An undirected topology graph is generated based on the connection relationship data;

[0037] The undirected topological graph is converted into a directed logical graph using a preset conversion rule, wherein the preset conversion rule is based on the preset upstream and downstream relationships of the items in the item attributes.

[0038] In some embodiments, the symbol information includes pipe connectors, and the method further includes:

[0039] In response to selecting a pipe cross-drawing connector in the drawing display area, obtain the associated drawing information and associated pipe name information of the pipe cross-drawing connector;

[0040] Based on the associated drawing information, the associated drawings are displayed in the drawing display area;

[0041] Based on the associated pipe name information, the associated pipe is located and highlighted in the associated drawing.

[0042] In some embodiments, the method further includes:

[0043] In response to selecting a target process drawing file in the drawing display area, obtain the location information of all pipe interfaces in the target process drawing file;

[0044] Iterate through the item attributes of the pipe interfaces to obtain the associated drawings for each pipe interface;

[0045] The target process drawing file and the associated drawings are combined to form a merged drawing;

[0046] The pipe interfaces with connection relationships are identified in the merged drawings.

[0047] In some embodiments, the method further includes:

[0048] In response to the selection of the symbol information in the drawing display area, menu options are generated according to the item type of the symbol information;

[0049] In response to the selection of the menu option, the identification information of the corresponding item is displayed in the preset item attribute display area;

[0050] Perform an identifier addition operation based on the identifier information, and add a target identifier to the symbol information in the drawing display area;

[0051] The item attributes of the corresponding items in the flowchart database are updated synchronously based on the target identifier.

[0052] In some embodiments, the method further includes:

[0053] Receive an identifier addition instruction, wherein the identifier addition instruction includes a target item and a target state;

[0054] An isolation boundary list is calculated based on the item attributes of the target item. The isolation boundary list includes multiple boundary devices and their corresponding isolation states.

[0055] Iterate through each boundary device in the isolation boundary list and identify multiple flowchart paper files containing the boundary devices;

[0056] Locate the symbol information corresponding to the boundary device in the process drawing file;

[0057] The format of the target identifier is determined based on the isolation status of the boundary device;

[0058] Add the target identifier around the symbol information, and synchronously update the corresponding isolation status information of the target identifier to the corresponding item attribute.

[0059] In some embodiments, calculating the isolation boundary list based on the item attributes of the target item includes:

[0060] Determine the equipment type of the target item based on the item attributes;

[0061] Obtain the corresponding isolation rules based on the device type, wherein the isolation rules include:

[0062] The isolation boundary of passive devices is the isolation valves upstream and downstream;

[0063] The isolation boundary of active devices includes the power isolation point and the gas supply isolation point;

[0064] Starting with the target item, a graph traversal algorithm is used to traverse the corresponding flowchart until an item that meets the isolation rules is found.

[0065] The items that conform to the isolation rules are used as boundary devices to generate the isolation boundary list.

[0066] In some embodiments, after adding the target identifier around the symbol information and synchronously updating the corresponding identifier information of the target identifier to the corresponding item attribute, the method further includes:

[0067] Obtain the historical isolation status corresponding to the item;

[0068] Compare the target state with the historical isolation state;

[0069] When the target state is inconsistent with the historical isolation state, the target identifier is updated and displayed based on the target state and the historical isolation state;

[0070] Control the target identifier to flash at a preset frequency.

[0071] Secondly, embodiments of this application provide a device for digitizing nuclear power plant system flowcharts, comprising:

[0072] The acquisition module is used to acquire multiple process drawing files corresponding to the target nuclear power plant and multiple item attributes; wherein, each process drawing file includes multiple symbol information, and each symbol information is used to represent a type of item;

[0073] A construction module is used to construct a flowchart directory tree based on the plurality of flowchart drawing files and the item attributes corresponding to each of the symbol information; wherein, the flowchart directory tree includes a drawing directory level and an item catalog level, the drawing directory level includes at least one of the flowchart drawing files, and the item catalog level includes at least one of the items.

[0074] The determination module is used to determine the corresponding target digital element from the drawing catalog level or the item catalog level;

[0075] The display module displays the target digitized element in a preset drawing display area.

[0076] Thirdly, embodiments of this application provide an electronic device, including: a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the nuclear power plant system flowchart digitization method as described in any one of the embodiments of the first aspect of this application.

[0077] Fourthly, embodiments of this application provide a computer-readable storage medium storing a program that is executed by a processor to implement the nuclear power plant system flowchart digitization method as described in any one of the embodiments of the first aspect of this application.

[0078] The method for digitizing nuclear power plant system flowcharts according to the embodiments of this application has at least the following beneficial effects:

[0079] The method for digitizing a nuclear power plant system flowchart according to an embodiment of this application includes: acquiring multiple flowchart drawing files corresponding to a target nuclear power plant and multiple item attributes; wherein each flowchart drawing file includes multiple symbol information, and each symbol information is used to represent a type of item; constructing a flowchart directory tree based on the multiple flowchart drawing files and the item attributes corresponding to each symbol information; wherein the flowchart directory tree includes a drawing directory level and an item catalog level, the drawing directory level includes at least one flowchart drawing file, and the item catalog level includes at least one item; determining the corresponding target digitized element from the drawing directory level or the item catalog level; and displaying the target digitized element in a preset drawing display area. This application can improve the analysis efficiency of various operations in a nuclear power plant system by digitizing the flowchart.

[0080] This application first establishes a unified digital data foundation by acquiring multiple process flow diagram files and their corresponding item attribute information from a nuclear power plant. Each process flow diagram file's symbol information is associated with a specific item type, achieving a mapping between graphics and data. This avoids the problem of the separation between diagram information and actual equipment data in traditional PDF format, laying the foundation for subsequent digital applications. Secondly, based on the acquired process flow diagram files and item attributes, a hierarchical process flow directory tree is constructed. This directory tree includes not only a diagram directory level but also an item directory level, forming a complete digital information index system. This hierarchical organization allows users to quickly locate and access the required diagrams or equipment information from different dimensions, greatly improving information retrieval efficiency. Compared to traditional folder-based management, the directory tree structure better suits the hierarchical characteristics of a nuclear power plant system, facilitating information classification management and rapid location. Thirdly, by flexibly selecting target digital elements in the directory tree and displaying them in a preset diagram display area, dynamic visualization of the process flow is achieved. This interactive display method breaks through the limitations of traditional static PDFs, making the display of diagram information more flexible and intuitive. This application realizes the transformation of nuclear power plant system flowcharts from static documents to a dynamic digital platform. By establishing a unified data model, constructing an intelligent retrieval system, and providing a flexible display interface, it significantly improves the work efficiency of various operational processes in nuclear power plants.

[0081] Additional aspects and advantages of this application will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of this application. Attached Figure Description

[0082] The above and / or additional aspects and advantages of this application will become apparent and readily understood from the description of the embodiments taken in conjunction with the following drawings, in which:

[0083] Figure 1 is a flowchart of an optional method for digitizing a nuclear power plant system flow chart according to an embodiment of this application;

[0084] Figure 2 is a flowchart of another optional method for digitizing the nuclear power plant system flowchart provided in an embodiment of this application;

[0085] Figure 3 is a schematic diagram of the drawing number composition structure provided in the embodiment of this application;

[0086] Figure 4 is a flowchart of another optional method for digitizing the nuclear power plant system flowchart provided in an embodiment of this application;

[0087] Figure 5 is a flowchart of another optional method for digitizing the nuclear power plant system flowchart provided in an embodiment of this application;

[0088] Figure 6 is a flowchart of another optional method for digitizing the nuclear power plant system flowchart provided in an embodiment of this application;

[0089] Figure 7 is a flowchart of another optional method for digitizing the nuclear power plant system flowchart provided in an embodiment of this application;

[0090] Figure 8 is a schematic diagram of the display interface provided in an embodiment of this application;

[0091] Figure 9 is a flowchart of another optional method for digitizing the nuclear power plant system flowchart provided in an embodiment of this application;

[0092] Figure 10 is a flowchart of another optional method for digitizing the nuclear power plant system flowchart provided in an embodiment of this application;

[0093] Figure 11 is a schematic diagram of multi-image linkage provided in an embodiment of this application;

[0094] Figure 12 is a flowchart of another optional method for digitizing the nuclear power plant system flowchart provided in an embodiment of this application;

[0095] Figure 13 is a schematic diagram of the menu options provided in an embodiment of this application;

[0096] Figure 14 is a schematic diagram of another menu option provided in an embodiment of this application;

[0097] Figure 15 is a flowchart of another optional method for digitizing the nuclear power plant system flowchart provided in an embodiment of this application;

[0098] Figure 16 is a schematic diagram of the isolation boundary marker provided in an embodiment of this application;

[0099] Figure 17 is a flowchart of another optional method for digitizing the nuclear power plant system flowchart provided in an embodiment of this application;

[0100] Figure 18 is a flowchart of another optional method for digitizing the nuclear power plant system flowchart provided in an embodiment of this application;

[0101] Figure 19 is a schematic diagram of the digital device for digitizing the nuclear power plant system flowchart provided in an embodiment of this application;

[0102] Figure 20 is a schematic diagram of the hardware structure of the electronic device provided in an embodiment of this application. Detailed Implementation

[0103] The embodiments of this application are described in detail below. Examples of the embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions throughout. The embodiments described below with reference to the accompanying drawings are exemplary and are only used to explain this application, and should not be construed as limiting this application.

[0104] In the description of this application, "several" means one or more, "more than" means two or more, "greater than," "less than," "exceeding," etc. are understood to exclude the stated number, while "above," "below," "within," etc. are understood to include the stated number. Where "first" or "second" is mentioned, it is only for the purpose of distinguishing technical features and should not be construed as indicating or implying relative importance, or implicitly indicating the number of indicated technical features, or implicitly indicating the sequential relationship of the indicated technical features.

[0105] In the description of this application, it should be understood that the orientation descriptions, such as up, down, left, right, front, and back, are based on the orientation or positional relationship shown in the accompanying drawings. They are only for the convenience of describing this application and simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, or be constructed and operated in a specific orientation. Therefore, they should not be construed as limitations on this application.

[0106] In the description of this specification, the references to terms such as "one embodiment," "some embodiments," "illustrative embodiment," "example," "specific example," or "some examples," etc., indicate that a specific feature, structure, material, or characteristic described in connection with that embodiment or example is included in at least one embodiment or example of this application. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples.

[0107] In the description of this application, it should be noted that, unless otherwise explicitly defined, terms such as "setting," "installation," and "connection" should be interpreted broadly. Those skilled in the art can reasonably determine the specific meaning of the above terms in this application based on the specific content of the technical solution. Furthermore, the identification of specific steps in the following text does not imply a limitation on the order of steps or execution logic. The execution order and logic between each step should be understood and inferred from the content described in the embodiments.

[0108] As nuclear power plants continue to grow in scale and complexity, system flowcharts play an increasingly important role throughout the entire lifecycle of a nuclear power plant. Traditional paper documents or static formats such as PDFs have many shortcomings in practical applications: on the one hand, these static document formats make drawing retrieval inefficient, requiring technicians to spend a lot of time switching between multiple documents to obtain the required information; on the other hand, due to the lack of a unified data association mechanism, drawing information is difficult to update in real time, easily leading to data version confusion and information inconsistencies.

[0109] To address the aforementioned issues, existing technologies employ vector-based redrawing of PDF drawings to digitize flowcharts. However, this approach not only requires significant manpower for drawing conversion, increasing economic costs, but also easily introduces data errors during the conversion process, leading to inconsistencies between on-site and design data. Furthermore, the lack of unified data standards and interface specifications hinders effective data sharing and interaction between different systems, impacting the efficiency of various aspects of nuclear power plant operations.

[0110] Based on this, this application provides a method for digitizing flowcharts in a nuclear power plant system, comprising: acquiring multiple flowchart drawing files corresponding to a target nuclear power plant and multiple item attributes; wherein each flowchart drawing file includes multiple symbol information, each symbol information being used to represent a type of item; constructing a flowchart directory tree based on the multiple flowchart drawing files and the item attributes corresponding to each symbol information; wherein the flowchart directory tree includes a drawing directory level and an item catalog level, the drawing directory level including at least one flowchart drawing file, and the item catalog level including at least one item; determining the corresponding target digitized element from the drawing directory level or the item catalog level; and displaying the target digitized element in a preset drawing display area. This application can improve the analysis efficiency of various operations in a nuclear power plant system by digitizing flowcharts.

[0111] This application first establishes a unified digital data foundation by acquiring multiple process flow diagram files and their corresponding item attribute information from a nuclear power plant. Each process flow diagram file's symbol information is associated with a specific item type, achieving a mapping between graphics and data. This avoids the problem of the separation between diagram information and actual equipment data in traditional PDF format, laying the foundation for subsequent digital applications. Secondly, based on the acquired process flow diagram files and item attributes, a hierarchical process flow directory tree is constructed. This directory tree includes not only a diagram directory level but also an item directory level, forming a complete digital information index system. This hierarchical organization allows users to quickly locate and access the required diagrams or equipment information from different dimensions, greatly improving information retrieval efficiency. Compared to traditional folder-based management, the directory tree structure better suits the hierarchical characteristics of a nuclear power plant system, facilitating information classification management and rapid location. Thirdly, by flexibly selecting target digital elements in the directory tree and displaying them in a preset diagram display area, dynamic visualization of the process flow is achieved. This interactive display method breaks through the limitations of traditional static PDFs, making the display of diagram information more flexible and intuitive. This application realizes the transformation of nuclear power plant system flowcharts from static documents to a dynamic digital platform. By establishing a unified data model, constructing an intelligent retrieval system, and providing a flexible display interface, it significantly improves the work efficiency of various operational processes in nuclear power plants.

[0112] Please refer to Figure 1. An embodiment of this application provides a method for digitizing a nuclear power plant system flowchart, which may include, but is not limited to, the following steps 101 to 104:

[0113] Step 101: Obtain multiple process drawing files corresponding to the target nuclear power plant and the item attributes of multiple items.

[0114] Step 102: Construct a flowchart directory tree based on multiple flowchart drawing files and the item attributes corresponding to each symbol information;

[0115] Step 103: Determine the corresponding target digitized element from the drawing catalog level or the item catalog level.

[0116] Step 104: Display the target digitized element in the preset drawing display area.

[0117] Specifically, in step 101 of this embodiment, the flowchart drawing files and item attributes are stored in different databases of the flowchart database. The flowchart database includes a drawing information database and an item attribute database.

[0118] The drawing information repository is primarily used to store process flow diagram files and related information. The repository includes a drawing information table to store basic information for each process flow diagram file, including but not limited to: drawing number, drawing name, system code, unit number, version number, and binary drawing data. The drawing number uniquely identifies a process flow diagram file and can be in the format: System three-letter code - Unit number - Three-digit serial number. For example, the drawing number "RRI-1101" indicates that the drawing belongs to the RRI system, the unit number is 1, and the serial number is 101. The system code identifies the system to which the process flow diagram file belongs; for example, RRI represents the equipment cooling water system, SEC represents the important plant water system, etc. The unit number identifies the unit to which the process flow diagram file belongs. The version number identifies the version information of the process flow diagram file, supporting version management. The binary drawing data stores the actual content of the drawing.

[0119] The item attribute library stores attribute information for various items in the flowchart. It includes multiple tables for storing attribute data for different types of items. These include, but are not limited to:

[0120] Item Information Table: This table stores basic information about items, including item code, item type, and item name. The item code uniquely identifies an item and can be in the format of: Unit Number + System Three-letter Code + Equipment Type Code + Serial Number. For example, item code "1RRI1101BA" indicates that the item belongs to tank number 1101 in the RRI system of Unit 1.

[0121] Equipment Table: Used to store the proprietary attributes of equipment items, including equipment model, technical parameters, operating parameters, etc. For example, for pump equipment, it can include parameters such as rated flow rate, rated head, and motor power.

[0122] Piping Table: Used to store the proprietary attributes of pipe items, including pipe specifications, material, design pressure, etc. For example, pipe specifications may include information such as nominal diameter and wall thickness.

[0123] Instrumentation: Used to store the proprietary attributes of instrument-type items, including measurement range, accuracy, etc. For example, for a pressure gauge, parameters such as measurement range and accuracy class can be included.

[0124] Valve Table: Used to store the specific attributes of valve items, including valve type, nominal pressure, and actuation method. For example, the valve type can be a gate valve, ball valve, butterfly valve, etc.

[0125] Actuator table: Used to store the unique attributes of actuators, including drive type, control method, etc. For example, the drive type can be electric, pneumatic, or manual.

[0126] Each item is represented on the drawing by a specific symbol. To establish the association between symbols and items, the drawing information database also includes a symbol information table, which stores the drawing information of the symbols, including symbol type, symbol coordinates, symbol size, associated items, etc. Through the associated item field in the symbol information table, a one-to-one correspondence can be established between the symbols on the drawing and the items in the item attribute database.

[0127] In step 102 of some embodiments, the drawing directory hierarchy is used to display the process drawing files in a hierarchical manner. In the drawing directory hierarchy, each node represents a process drawing file, and the node's display content includes the drawing number and drawing name. The item catalog hierarchy is used to display the various items contained in the process drawing files, and the item catalog hierarchy is located below the corresponding drawing directory hierarchy. In the item catalog hierarchy, each node represents a specific item, and the node's display content includes the item code and item name.

[0128] Specifically, the process of constructing a flowchart directory tree includes the following steps:

[0129] First, the basic information of all process diagram files is obtained by accessing the drawing information repository of the flowchart database. Based on the obtained drawing information, a drawing directory hierarchy is established in the directory tree, with each process diagram file as a directory node.

[0130] Secondly, for each process drawing file, retrieve all symbol information contained in that drawing through the symbol information table. Based on the associated item field in the symbol information, query the corresponding item information in the item attribute library. Create an item catalog hierarchy under the corresponding drawing node in the directory tree for the retrieved item information.

[0131] For example, when the process drawing file "RRI-1101" contains multiple items, corresponding item nodes will be created under the directory node corresponding to the drawing, such as storage tank "1RRI1101BA" and valve "1RRI1101VA". Users can easily browse the hierarchical relationship between drawings and items by expanding or collapsing the directory tree nodes.

[0132] This hierarchical directory tree structure has the following characteristics:

[0133] Clear hierarchy: The flowchart clearly displays its content structure through two levels: drawings and items.

[0134] Easy navigation: Users can quickly locate the drawings or items they need;

[0135] Complete information: The directory tree nodes contain key information about drawings and items, making them easy to identify and select.

[0136] The flowchart directory tree constructed in this embodiment provides users with an intuitive navigation interface, which helps improve the efficiency of drawing review and information retrieval. At the same time, this structured organization also provides a good foundation for subsequent functional expansion.

[0137] Referring to Figure 2, in some embodiments, the flowchart directory tree further includes a project directory level, a unit directory level, a system directory level, an item type directory level, and a sub-item directory level. The project directory level includes at least one unit directory level, the unit directory level includes at least one system directory level, the system directory level includes at least one flowchart drawing file directory level, and the flowchart drawing file directory level includes at least one item type directory level. Step 102 may include, but is not limited to, steps 201 to 208:

[0138] Step 201: Obtain the drawing number of each process drawing file, and obtain the unit number and system information corresponding to each process drawing file based on the drawing number.

[0139] Step 202: Construct a project directory hierarchy based on the target nuclear power plant.

[0140] Step 203: Construct a unit directory hierarchy under the project directory hierarchy based on each unit number.

[0141] Step 204: Based on the system information corresponding to each process drawing file, construct the system directory hierarchy under the corresponding unit directory hierarchy.

[0142] Step 205: Based on each drawing number, construct a drawing directory hierarchy under the corresponding system directory hierarchy.

[0143] Step 206: Based on the item attributes corresponding to each item, construct an item type directory hierarchy under the corresponding drawing directory hierarchy.

[0144] Step 207: Based on the item attributes of each item, construct the item catalog level under the corresponding item type catalog level.

[0145] Step 208: When the item attributes include sub-item information, construct the sub-item catalog level under the corresponding item catalog level based on the sub-item information.

[0146] In step 201 of some embodiments, the drawing number of each process drawing file is first obtained and then parsed. As shown in Figure 3, the drawing name is composed of "system three-letter code" + "-" + "unit number" + "three-letter serial number". For example, for the drawing number "RRI-1101", the system three-letter code is "RRI", the unit number is "1", and the serial number is "101" after parsing.

[0147] In step 202 of some embodiments, the project information of the target nuclear power plant is first obtained by traversing the database names. For example, when the database name is "tes", the project directory level name is set to "TES". It should be noted that there is one and only one project directory level.

[0148] In step 203, the fifth character value from the left (i.e., the unit number) is extracted by traversing the drawing names in the drawing information table of the database. The extracted character set is then deduplicated, and each element of the resulting set represents the unit number value in each unit directory level. The unit directory level is set as: "unit number value" + "unit number" (e.g., Unit 1).

[0149] In step 204, the unit number in the drawing name is extracted by traversing the drawing information table in the database and compared with the unit number value in the unit directory level. When the comparison result is the same, the first three characters of the current drawing name (i.e., the system three-letter code) are extracted, and the system three-letter code set is deduplicated. Each element of the processed set is the system directory level, such as "RRI", "SEC", etc.

[0150] In step 205, the unit number and system number are extracted from the drawing names in the drawing information table of the database by traversing the drawing names. The system number is compared with the system number at the system directory level, and the unit number is compared with the unit number value at the unit directory level. When the comparison results are the same, the current drawing name is read and used as the drawing directory level, such as "RRI-1101", "RRI-1102", etc.

[0151] In step 206, a search is performed in the drawing name column of the database view based on the drawing catalog level. When a matching value is found, the type value of the current row in the view is retrieved. The correspondence between the type values ​​and the item type descriptions is shown in Table 1.

[0152] Table 1 Mapping Relationship Between Type Values ​​and Item Type Descriptions

[0153] The item type description corresponding to the currently extracted type value is matched and used as the fifth-level directory name. For example, the type value "SCPLIN" corresponds to the item description "pipe", "SCHVAC" corresponds to "hvac", and "SCEQUI" corresponds to "equipment", etc.

[0154] In step 207, a search is performed in the drawing name column of the database view based on the drawing catalog level. When a match is found, the type value and name of the current row in the view are retrieved, and the type value is compared with the type value corresponding to the item. If the comparison results match, the name extracted from the view is used as the item type catalog level. For example, the "pipe" type may contain specific pipes such as "1RRI1101TY" and "1RRI1102TY".

[0155] In step 208, since pipelines and equipment also have sub-items, only pipelines and equipment have a seven-level directory. Specifically: when the item directory level is pipeline, a search is performed in the item name column of the pipeline table in the database, using the item name as the condition. When a matching value is found, the value of the pipeline logical field column of the current row is taken. This value represents all online devices arranged from left to right in the flow direction on the pipeline. If this value is not empty, the specific format is "type1_device1^type2_device2...". The device names are extracted sequentially from left to right as the sub-item directory level of the current pipeline.

[0156] The hierarchical relationship of the above directory is shown in Table 2. For example, for the drawing "RRI-1101" in "RRI System" under "Unit 1", it contains item types such as "pipe", "equipment", "instrument", "actuator", etc. Each item type contains specific items, such as "1RRI1101TY", "1RRI1101BA", etc. Some items may also contain sub-items.

[0157] Table 2 Directory Tree Structure

[0158] Please refer to Figure 4. In some embodiments, the method provided by this application may also include, but is not limited to, steps 401 to 404.

[0159] Step 401: Display the search box at a preset position in the preset directory tree display area.

[0160] Step 402: In response to entering a search value in the search box, a search is performed in the flowchart directory tree based on the search value.

[0161] Step 403: When a directory level that matches the search value is found, the directory level that matches the search value is determined as the target directory level.

[0162] Step 404: Jump the content displayed in the directory tree display area to the target directory level.

[0163] In step 401 of some embodiments, a preset directory tree display area is located on the left side of the web page. A search box is preset above the directory tree display area, where users can enter the name of the drawing, item code, or other identification information they wish to search for. The search box provides real-time input response functionality, supporting users in performing quick search operations.

[0164] In step 402 of some embodiments, after the user enters the value to be searched in the search box, the system automatically reads the value in the search box and uses it to traverse the directory tree. The traversal process proceeds sequentially according to the hierarchical structure of the directory tree, including project level, unit level, system level, drawing level, item type level, item level, and sub-item level. In each level, the system matches and compares the displayed content of the node with the value to be searched.

[0165] In step 403 of some embodiments, when a node matching the search value is found in a directory level, the system records the directory level location of that node. This location information includes the complete path of the node in the directory tree, such as "TES / Unit 1 / RRI / RRI-1101 / equipment / 1RRI1101BA". The system determines the directory level corresponding to this path as the target directory level.

[0166] In step 404 of some embodiments, based on the recorded location information, the system automatically expands all parent nodes from the root node to the target directory level and automatically scrolls the content of the directory tree display area to the location of the target directory level. Simultaneously, the system highlights or uses other prominent methods to identify the target directory level, allowing users to quickly identify search results. The target directory level remains within the visible range of the directory tree display area for easy viewing and operation by the user.

[0167] Through the above steps, this embodiment provides a convenient flowchart directory tree search function, enabling users to quickly locate the required drawings or item information and improving the efficiency of information retrieval. When a user needs to find a specific drawing or item, there is no need to manually expand and browse multiple directory levels; they can simply enter the relevant information in the search box to quickly locate it.

[0168] Please refer to Figure 5. In some embodiments, when no directory level matching the search value is found, the method provided in this application embodiment may also include, but is not limited to, steps 501 to 504.

[0169] Step 501: Query the value to be searched in the flowchart database to obtain the flowchart paper file corresponding to the value to be searched.

[0170] Step 502: Update the flowchart directory tree based on the flowchart paper file corresponding to the value to be searched.

[0171] Step 503: In the updated flowchart directory tree, perform a query based on the value to be searched, and determine the queried directory level as the target directory level.

[0172] Step 504: Jump the content displayed in the directory tree display area to the target directory level.

[0173] In step 501 of some embodiments, when a directory level matching the search value cannot be found in the current directory tree, the search scope can be automatically expanded to the flowchart database. Specifically, a query will be performed in the database view, and the query objects include, but are not limited to, drawing information tables, item information tables, etc. By querying the database view, all relevant flowchart drawing files containing the search value can be found.

[0174] In step 502 of some embodiments, the directory tree is dynamically updated based on the flowchart paper file information retrieved from the database. The update process includes the following steps:

[0175] First, obtain the drawing name of the retrieved flowchart paper file;

[0176] Parse the drawing name and extract information such as system code and unit number;

[0177] Based on the rules for building a directory tree, the corresponding directory hierarchy is automatically generated using this information.

[0178] Add the newly generated directory hierarchy to the corresponding position in the existing directory tree.

[0179] In step 503 of some embodiments, after the directory tree update is completed, a new search is performed in the newly added directory levels. When a directory level matching the search value is found, the system identifies it as the target directory level. To facilitate subsequent location, the complete path information of this directory level can be recorded.

[0180] In step 504 of some embodiments, the content of the directory tree display area is automatically located to the target directory level based on the recorded path information. Specifically, this includes:

[0181] Expand all parent nodes from the root node to the target directory level;

[0182] The display area will scroll to the target directory level.

[0183] Use highlighting or other prominent methods to identify the target directory level.

[0184] Through the above steps, this embodiment provides an extended search mechanism. When the content a user searches for does not exist in the current directory tree, the system automatically performs a broader search in the database and dynamically updates the directory tree structure to ensure that the user can find the information they need. This mechanism is particularly suitable for the following scenarios:

[0185] When the current directory tree has not fully loaded all drawing information;

[0186] When the content that the user needs to find is located in other systems or units;

[0187] The drawing information has just been updated in the database, but the directory tree has not yet been synchronized.

[0188] This dynamic update and query mechanism improves the system's flexibility and usability, enabling users to more easily access and search for various types of information within the nuclear power plant system.

[0189] Please refer to Figure 6. In some embodiments, when the value to be searched is the target item code, the method provided in this application embodiment may further include, but is not limited to, steps 601 to 604.

[0190] Step 601: Search the flowchart database according to the target item code to identify multiple flowchart drawing files.

[0191] Step 602: Display the first obtained process drawing file as the main display drawing in the drawing display area, and locate and highlight the item corresponding to the target item code in the main display drawing.

[0192] Step 603: Display the remaining process drawing files sequentially in the drawing display area using tabs.

[0193] Step 604: In response to selecting any of the tabs, switch and display the flowchart paper file corresponding to the tab, and locate and highlight the item.

[0194] In step 601 of some embodiments, when the search value is a target item code, a search is first performed in the flowchart database. Taking the target item code "1RRI1101BA" as an example, this code indicates that it is a device located in the RRI system of Unit 1. The system searches for this item code in the flowchart database of the directory tree. Since the same device may appear in multiple flowcharts, the system continues to traverse until all flowchart paper files containing the device are obtained. This comprehensive search method ensures that no flowchart containing the target item is missed.

[0195] In step 602 of some embodiments, the system prioritizes displaying the first retrieved flowchart drawing file as the main display drawing. In the main display drawing, the target item is prominently marked, for example, by using a red border or a highlighted background. Simultaneously, the system automatically adjusts the display scale and position of the drawing to center the target item within the drawing display area for easy viewing by the user. Furthermore, the basic attribute information of the target item is also simultaneously displayed in the attribute display area, allowing the user to easily understand the item's detailed information.

[0196] In step 603 of some embodiments, in addition to the main display drawing, other flowchart files containing target items are neatly arranged as tabs at the top of the drawing display area. Each tab is clearly labeled with the corresponding flowchart number or name, and these tabs are sorted according to specific rules, such as by drawing number or by system type. The tab corresponding to the currently displayed main display drawing is identified with different colors or styles, so that the user can clearly know which flowchart is currently being viewed.

[0197] In step 604 of some embodiments, when a user needs to view target items in other flowcharts, they simply click the corresponding tab, and the system automatically switches to that flowchart. After the new flowchart loads, the target items are immediately highlighted in the same way and automatically adjusted to their appropriate display positions. This seamless switching experience allows users to easily compare and analyze different flowcharts, which is particularly suitable for scenarios requiring the study of a device's connections across different systems. For example, when analyzing the system interfaces of an important device, users can quickly switch between tabs to gain a comprehensive understanding of the device's connections with other systems.

[0198] This multi-map linked display method based on item coding provides strong support for the design, analysis, and maintenance of nuclear power plant systems. Users can quickly locate the equipment of interest and gain a comprehensive understanding of its application within the entire nuclear power plant system through tab switching, greatly improving work efficiency. Especially during system analysis or fault diagnosis, this convenient multi-map viewing method helps technicians more quickly understand the overall system structure and the relationships between equipment.

[0199] Please refer to Figure 7. In some embodiments, when the value to be searched is the target item code, the method provided in this application embodiment may further include, but is not limited to, steps 701 to 703.

[0200] Step 701: In response to selecting the process drawing file in the directory tree display area and triggering the logic diagram generation operation, the connection relationship data of pipes and equipment in the process drawing file is obtained according to the item attributes of each item.

[0201] Step 702: Generate an undirected topology graph based on the connection relationship data.

[0202] Step 703: Convert the undirected topological structure graph into a directed logical simplified graph using preset conversion rules, wherein the preset conversion rules are based on the preset upstream and downstream relationships of items in the item attributes.

[0203] In step 701 of some embodiments, after selecting the flowchart drawing file in the directory tree display area, the logic diagram generation operation can be triggered via the right-click menu. This step reads the attribute information of all items in the flowchart drawing file from the flowchart database, focusing on obtaining the connection relationship data between items. This connection relationship data is mainly stored in the tblink data table, which records the connection information between each item and its adjacent items, centered on the link_node. By analyzing the device sequence recorded in the link_sequence, the complete connection topology between pipes and devices can be obtained.

[0204] In step 702 of some embodiments, a complete undirected topology graph can be constructed based on the acquired connection relationship data. In this topology graph, each node represents a device item, and the connecting lines between nodes represent the pipe connections between them. Specifically, each device acts as a central node, and its adjacent devices are connected by undirected connecting lines. These adjacent devices, in turn, each act as a central node, connected to their adjacent devices, ultimately forming a complete device connection network. This undirected topology intuitively shows the connection relationships between devices, but it does not yet reflect the directionality of medium flow.

[0205] In step 703 of some embodiments, the undirected topology diagram is converted into a directed logical diagram according to preset conversion rules. These conversion rules are primarily based on preset upstream and downstream relationships in the item attributes, which can be determined through the functional characteristics of the equipment and the system flow. For example, the equipment connected to the outlet of a pump is its downstream equipment, and the equipment connected to its inlet is its upstream equipment; the equipment connected to the outlet valve of a storage tank is its downstream equipment, and the equipment connected to the inlet valve is its upstream equipment. These rules determine the direction of medium flow between the equipment and represent it with directed arrows in the logical diagram. Simultaneously, during the generation of the logical diagram, pipelines, pipe fittings, pipe interfaces, instruments, nozzles, and all attributeless labels and shapes in the original diagram are omitted, retaining only the main equipment and their logical relationships, making the system's functional structure clearer.

[0206] This transformation from complex flowcharts to simplified logic diagrams effectively demonstrates the system's functional structure and media flow patterns. Especially for complex process systems, the simplified logic diagrams can intuitively present the system's main functions and the interrelationships between equipment, providing strong support for system analysis, fault diagnosis, and operator training. Furthermore, these automatically generated logic diagrams are not only suitable for analyzing single flowcharts but can also be extended to the analysis of equipment logic relationships across the entire system or even the entire plant.

[0207] In step 103 of some embodiments, the corresponding target digitized element is determined from the drawing directory level or the item catalog level of the flowchart directory tree. When a user needs to view a flowchart drawing, they can select the flowchart drawing file under the drawing directory level in the directory tree display area to determine the flowchart drawing file as the target digitized element. When a user needs to view specific item information, they can select the item under the item catalog level in the directory tree display area to determine the item as the target digitized element.

[0208] In step 104 of some embodiments, the target digitized element is displayed in a preset drawing display area. This drawing display area is located on a web page and includes different functional areas such as a main display area, a toolbar area, an attribute display area, and a directory tree area. The main display area is used to display the flowchart content; the toolbar area contains basic operation buttons such as zoom and pan; the attribute display area is used to display the attribute information of the selected item; and the directory tree area is used to display the flowchart directory structure.

[0209] Please refer to Figure 8. When the target digitized element is a process flow drawing file, the complete content of the process flow drawing will be displayed in the main display area (center of Figure 8). Various items in the process flow drawing are represented by different symbols, such as equipment, pipes, instruments, and valves. These symbols are associated with the item data in the database. The drawing content supports zooming and panning operations, allowing you to adjust the viewing scale and position as needed. Furthermore, by selecting a symbol in the drawing, you can view the detailed attribute information of the corresponding item in the attribute display area (right side of Figure 8), and expand the directory tree hierarchy corresponding to the drawing and items (left side of Figure 8).

[0210] When the target digitized element is a specific item, the flowchart in which the item is located will be automatically positioned and displayed, and the item will be prominently identified. At this point, you can not only view the graphic representation of the item, but also its detailed attribute information in the attribute display area, including basic attributes, technical attributes, location attributes, and related attributes. For items appearing in multiple flowcharts simultaneously, you can switch between different flowchart representations using tabs in the main display area.

[0211] This intuitive display method, combined with the directory tree navigation, allows for easy browsing and retrieval of flowcharts and item information within the nuclear power plant system, improving work efficiency. This web-based display method is particularly advantageous when frequently needing to consult different drawings or analyze the relationships between items.

[0212] Please refer to Figure 9. In some embodiments, the symbol information includes pipe connectors. The method provided in this application embodiment may also include, but is not limited to, steps 901 to 903.

[0213] Step 901: In response to selecting the pipe cross-drawing connector in the drawing display area, obtain the associated drawing information and associated pipe name information of the pipe cross-drawing connector.

[0214] Step 902: Display the associated drawings in the drawing display area based on the associated drawing information.

[0215] Step 903: Locate and highlight the associated pipe in the associated drawing based on the associated pipe name information.

[0216] In step 901 of some embodiments, pipe connectors within the drawing display area are used to represent pipes connected across drawings. When a pipe connector across drawings is selected in the drawing display area, the associated drawing information and associated pipe name information can be obtained through the item attributes of the connector. Specifically, each pipe connector across drawings contains two key attributes: one is the "associated drawing" attribute, which points to another flowchart of the pipe connection; the other is the "associated pipe name" attribute, which identifies the target pipe to be located in the associated drawing. For example, when a pipe connects from drawing "RRI-1101" to drawing "RRI-1102", the associated drawing information of the pipe connector across drawings is "RRI-1102", and the associated pipe name information is the identifier name of the pipe in drawing "RRI-1102".

[0217] In step 902 of some embodiments, after obtaining the associated drawing information, the content of the associated drawing is automatically read from the flowchart database and displayed in the drawing display area. During the display process, the original drawing will be replaced by the associated drawing, or the associated drawing will be displayed as a new tab. This function of automatically jumping to the associated drawing makes viewing the pipeline connection relationship across drawings simple and intuitive.

[0218] In step 903 of some embodiments, the target pipe is quickly located in the displayed associated drawings based on the acquired associated pipe name information. The located pipe is highlighted in a prominent manner, such as by using specific color markings or flashing prompts, so that the user can intuitively see the pipe's connection status. In this way, the routing and connection relationships of pipes across different drawings can be clearly tracked.

[0219] The cross-drawing connection function, implemented through the above steps, effectively solves the problem that traditional paper drawings or PDF files are insufficient to display cross-drawing connections. This convenient cross-drawing navigation method greatly improves the work efficiency of engineering technicians when performing piping system analysis, piping layout design, and system maintenance. Especially when analyzing complex piping systems, this function helps to quickly understand the complete piping route, aiding in overall system understanding and problem localization. For example, during system isolation analysis or leak analysis, this method can quickly trace the complete piping path, ensuring the accuracy and completeness of the analysis.

[0220] Furthermore, this feature supports bidirectional navigation, meaning it allows users to jump not only from the starting drawing to related drawings but also back from related drawings to the starting drawing, forming a complete pipeline connection path tracing. This bidirectional navigation feature provides greater convenience for system analysis and fault diagnosis, making system maintenance and operation management more efficient.

[0221] Please refer to Figure 10. In some embodiments, the method provided in this application may also include, but is not limited to, steps 1001 to 1004.

[0222] Step 1001: In response to selecting the target process drawing file in the drawing display area, obtain the location information of all pipe interfaces in the target process drawing file.

[0223] Step 1002: Traverse the item attributes of the pipe interfaces and obtain the associated drawings for each pipe interface.

[0224] Step 1003: Combine the target process drawing file with the associated drawings to form a merged drawing.

[0225] Step 1004: Identify the pipe interfaces with connection relationships in the merged drawings.

[0226] In step 1001 of some embodiments, after selecting the target flowchart drawing file in the drawing display area, it is first necessary to obtain the location information of all pipe interfaces in the flowchart drawing file. Pipe interfaces are important nodes in the flowchart representing pipe connections across diagrams, and each pipe interface has specific spatial coordinate information. This location information records the specific location of the pipe interface in the drawing, including the X and Y coordinates, which is crucial for subsequent drawing splicing and connection relationship identification.

[0227] In step 1002 of some embodiments, all detected pipe interfaces in the target process flow drawing file are traversed, and the item attributes of each pipe interface are read. The item attributes of the pipe interface contain key connection information, especially the "associated drawing" attribute, which indicates other process flow drawings connected to the current pipe interface. In this way, all associated drawing information that has a pipe connection relationship with the target process flow drawing file can be obtained.

[0228] In step 1003 of some embodiments, based on the acquired associated drawing information, the target process drawing file is stitched together with these associated drawings to form a complete merged drawing. As shown in the figure, the stitching process needs to consider the relative positional relationship of each drawing to ensure that the pipe interfaces can be correctly matched. The merged drawing should maintain the scale of the original drawings, and a certain transition area should be retained at the joints of the drawings to make the connection relationship between the drawings clearer. The stitched merged drawing can provide a larger viewing range, allowing users to view multiple related drawings or systems at once.

[0229] This method of displaying merged drawings is particularly suitable for scenarios requiring the analysis of cross-system connections. For example, when analyzing the piping layout of a complex system, traditional single-sheet viewing methods often fail to capture the complete connectivity. Merged display, however, allows for a clear view of the connection paths between different systems within a larger view, helping engineers better understand and analyze the overall system structure. Furthermore, all elements in the merged drawings retain their selectable and viewable attributes, allowing users to zoom in or view attributes of areas of interest, further enhancing the convenience of drawing review and analysis.

[0230] In step 1004 of some embodiments, the pipe interfaces with connections need to be highlighted in the resulting merged drawings. Interrelated pipe interfaces can be identified using dashed lines, the style and color of which can be differentiated based on the type of pipe or the medium. This identification method allows users to visually see the connection relationships between pipes in different drawings. Furthermore, special visual markings or annotations can be added to the pipe interfaces at the connection points to provide more detailed connection descriptions.

[0231] As shown in Figure 11, when the target drawing is displayed, dashed lines can be used to identify the connection relationships of related pipelines. As shown, the dashed lines are drawn in red, with their starting and ending points connecting to the corresponding pipeline cross-drawing connectors in the drawing. This dashed line representation visually demonstrates the connection path of pipelines between different drawings. Dashed lines can span multiple drawing areas, forming a complete pipeline connection path indication. The style of each dashed line can be differentiated according to the characteristics of the pipeline; for example, different colors, different dashed line intervals, or different line widths can be used to represent pipeline connections of different types or media.

[0232] Please refer to Figure 12. In some embodiments, the method provided by this application may also include, but is not limited to, steps 1201 to 1204.

[0233] Step 1201: In response to the selected symbol information in the drawing display area, generate menu options based on the item type of the symbol information.

[0234] Step 1202: In response to the selection of a menu option, the identification information of the corresponding item is displayed in the preset item attribute display area.

[0235] Step 1203: Perform the label addition operation based on the label information, and add the target label for the symbol information in the drawing display area.

[0236] Step 1204: Synchronously update the item attributes of the corresponding items in the flowchart database according to the target identifier.

[0237] In step 1201 of some embodiments, when a symbol is selected in the drawing display area, a corresponding right-click menu option is generated based on the object type of the symbol. As shown in Figures 13 and 14, for valve-type symbols, the menu options include, but are not limited to, "Open (Valve)," "Close (Valve)," "Close Lock (Valve)," and "Cancel Boundary." In particular, for pneumatic valves, by reading the name of the selected valve and querying the associated valve field (sciref) column in the actuator database table (tbactuator), when the symbol name (symbol_name) is found to be "Pneumatic," the right-click menu will also include an additional "Neutral Point (Valve)" option.

[0238] In step 1202 of some embodiments, after a specific menu option is selected, corresponding identification information is displayed in a preset item attribute display area. Each identification option corresponds to a specific display specification, including the identification type, status code, and display style. For example, as shown in Figure 13, selecting the "Open (Valve)" option corresponds to status code "O", and "Close (Valve)" corresponds to status code "C"; as shown in Figure 14, "Neutral Point (Valve)" corresponds to status code "N". In addition, "Close Lock (Valve)" and "Open Lock (Valve)" correspond to status codes "LC" and "LO", respectively.

[0239] In step 1203 of some embodiments, corresponding target identifiers are added to the symbols in the drawing display area according to different identifier information. The specific identifier formats are as follows:

[0240] On status: A red box is added around the symbol, marked with "O";

[0241] When closed: A red box is added around the symbol, labeled "C";

[0242] Neutral point status: Add a red box around the symbol and label it "N";

[0243] To disable the locked state: Add a red box and a lock icon around the symbol, and label it "LC";

[0244] To enable the locked state: Add a red box and a lock icon around the symbol, marked "LO".

[0245] In step 1204 of some embodiments, after adding the target identifier, the identifier status information needs to be synchronously updated to the status field of the corresponding item in the flowchart database. The update process includes obtaining the item code and type of the icon, determining the corresponding database table based on the item type, and updating the status information of the corresponding item in that table. This synchronization mechanism ensures the consistency between the graphical display and the database records, providing a reliable data foundation for status query and analysis.

[0246] This right-click menu-based labeling mechanism is not only convenient to use, but also provides differentiated labeling options based on the item type, effectively supporting status labeling needs in various scenarios. Especially in scenarios such as system isolation analysis, this precise labeling mechanism can effectively improve work efficiency and accuracy.

[0247] Please refer to Figure 15. In some embodiments, the method provided by this application may also include, but is not limited to, steps 1501 to 1507.

[0248] Step 1501: Receive the identifier addition instruction.

[0249] Step 1502: Calculate the isolation boundary list based on the item attributes of the target item. The isolation boundary list includes multiple boundary devices and their corresponding isolation states.

[0250] Step 1503: Iterate through each boundary device in the isolation boundary list and identify multiple flowchart paper files containing the boundary devices.

[0251] Step 1504: Locate the symbol information corresponding to the boundary equipment in the process drawing file.

[0252] Step 1505: Determine the format of the target identifier based on the isolation status of the boundary device.

[0253] Step 1506: Add target identifiers around the symbol information and synchronously update the corresponding isolation status information of the target identifiers to the item attributes of the corresponding items.

[0254] In step 1501 of some embodiments, the identifier addition instruction includes two key pieces of information: the target item and the target status. The target item can be a device code (such as "1RRI1101BA"), and the target status indicates the desired isolation status of the item. The identifier addition instruction can be passed in as an interface function, with the parameter format: {"drawing_name1":[{"name1":"LC"},{"name2":"C"},{"name3":"LO"}]}, where "drawing_name" represents the drawing name, "name" represents the item name, and the corresponding value represents the target status.

[0255] In step 1502 of some embodiments, the system calculates an isolation boundary list associated with the target item based on the item attribute information. The isolation boundary list includes all boundary devices that need to be operated to ensure the secure isolation of the target item, as well as the isolation states that these boundary devices should be in. As shown in Figure 15, different isolation states may need to be set for different boundary devices, such as "C" (off) and "O" (on).

[0256] In steps 1503 to 1505 of some embodiments, the system iterates through each boundary device in the isolation boundary list, determines the corresponding flowchart paper file for each boundary device, and locates the flowchart paper file containing these boundary devices in the flowchart directory tree. For each located flowchart paper file, the system further locates the symbol information corresponding to the boundary device. As shown in Figure 16, the drawing contains multiple valve symbols with identification marks; these valves are the isolation boundary devices.

[0257] In step 1506 of some embodiments, the specific format of the target identifier is determined according to the isolation status of the boundary device, with different isolation statuses corresponding to different identifier formats:

[0258] "C" status: A red box is displayed with the letter "C" on it;

[0259] "O" status: A red box is displayed with the letter "O" on it;

[0260] "LC" status: Displays a red box and a lock icon, marked with the letters "LC";

[0261] "LO" status: Displays a red box and a lock icon, along with the letters "LO";

[0262] In step 1507 of some embodiments, a target identifier is added around the corresponding symbol information according to the determined identifier format. As shown in Figure 16, a target identifier is added around the valve symbol. After the identifier is added, the system will synchronously update the status field of the corresponding item in the flowchart database to ensure the consistency between the graphical display and the database record.

[0263] This automated isolation boundary identification mechanism greatly improves the efficiency and accuracy of system isolation analysis. Through a unified identifier format and automated identifier addition process, errors that may arise from manual operation can be effectively avoided, while also facilitating subsequent status queries and analysis.

[0264] Please refer to Figure 17. In some embodiments, step 1502 may also include, but is not limited to, steps 1701 to 1704.

[0265] Step 1701: Determine the equipment type of the target item based on the item attributes.

[0266] Step 1702: Obtain the corresponding isolation rules based on the device type.

[0267] Step 1703: Starting from the target item, use a graph traversal algorithm to traverse the corresponding flowchart until an item that meets the isolation rules is found.

[0268] Step 1704: Select items that meet the isolation rules as boundary devices and generate an isolation boundary list.

[0269] In step 1701 of some embodiments, in order to accurately calculate the isolation boundary list, it is first necessary to determine the equipment type based on the item attributes of the target items. The determination of equipment type is mainly based on item coding rules, such as "BA" representing storage tank equipment, "TK" representing water pool equipment, etc. At the same time, more detailed equipment type information can be obtained by querying the item attribute table of the equipment, including whether the equipment is an active device, the driving method of the equipment, and other key characteristics.

[0270] In step 1702 of some embodiments, appropriate isolation rules can be automatically matched based on the determined device type. For passive devices, the isolation boundary mainly considers upstream and downstream isolation valves, which can effectively cut off the flow of process media and ensure the safe isolation of the device. For active devices, in addition to considering the isolation of the process piping system, power isolation points and gas supply isolation points also need to be considered. Power isolation points typically include electrical switches, circuit breakers, etc., while gas supply isolation points include gas source valves, regulating valves, etc. The isolation of these auxiliary systems is crucial to ensuring the safe isolation of active devices.

[0271] In step 1703 of some embodiments, after the isolation rules are determined, a graph traversal algorithm is used to systematically search the flowchart, starting from the target item. During the search, the system expands upstream and downstream along the pipeline connections, recording all potential isolation devices along the search path. For each searched branch, it is determined whether the devices on it meet the isolation rules. In particular, for active devices, it is also necessary to search the power supply path and air supply path of the device to determine the isolation points of each auxiliary system. This comprehensive search strategy ensures that no critical isolation points are missed.

[0272] In step 1704 of some embodiments, all items that meet the isolation rules are collected and used to generate an isolation boundary list as boundary devices. When generating the list, the system records in detail the isolation state that each boundary device should be in. For example, isolation valves on process pipelines typically need to be closed, while some discharge valves may need to be open, power isolation points need to be disconnected, and gas source isolation points need to be closed, etc. These boundary devices are categorized and organized according to device type and location to form a standard-format isolation boundary list, which includes important information such as the item code, location information, required isolation state, and system information of the boundary devices.

[0273] This automated boundary calculation method, based on equipment type and isolation rules, can not only accurately and quickly determine the system isolation range, but also effectively avoid the risk of missing critical isolation points due to human error. This systematic calculation method provides reliable technical support for safe isolation operations in nuclear power plants, improving the accuracy and efficiency of isolation operations.

[0274] Please refer to Figure 18. In some embodiments, steps 1801 to 1804 may be included after step 1507.

[0275] Step 1801: Obtain the historical isolation status corresponding to the item.

[0276] Step 1802: Compare the target state with the historical isolation state.

[0277] Step 1803: When the target state is inconsistent with the historical isolation state, update the displayed target identifier based on the target state and the historical isolation state.

[0278] Step 1804: Control the target identifier to flash at a preset frequency.

[0279] In step 1801 of some embodiments, obtaining the historical isolation status corresponding to the item requires querying historical status records in the flowchart database. The historical isolation status reflects the device's status information during previous operations, and may be different states such as "C" (off), "O" (on), "LC" (locked / closed), "LO" (locked / open), and "N" (neutral point). This historical status information is crucial for assessing changes in device status and ensuring operational safety.

[0280] In step 1802 of some embodiments, the current target state to be set is compared with the acquired historical isolation states. The comparison process records the changes in state in detail. For example, when the historical state of a valve is "C" (closed) and the target state is "O" (open), the system will recognize this change in state; similarly, when the historical state is "LC" (closed and locked) and the target state is "LO" (open and locked), the system will also capture this state transition.

[0281] In step 1803 of some embodiments, when an inconsistency is found between the target state and the historical isolation state, the system uses a special display method to highlight this change. As shown in Figure 18, the updated target identifier reflects information from both the historical and target states. The identifier display includes two aspects: first, it identifies the historical state through a specific border style and color; second, it identifies the target state through the style and color of the internal fill. This dual visual expression makes the change in state immediately apparent.

[0282] In step 1804 of some embodiments, to further highlight the devices undergoing status changes, the system controls the target identifiers of these devices to flash at a preset frequency. Specifically, the flashing frequency is set to 1Hz, that is, flashing once per second. The flashing content includes a frame and a status icon on the frame. This dynamic visual effect can effectively attract the operator's attention and remind them to pay attention to the devices whose status has changed. For example, when a valve changes from a closed state to an open state, its identifier frame and status icon will flash synchronously, clearly indicating this status change.

[0283] This historical status comparison and dynamic display mechanism helps operators clearly identify which equipment statuses have changed, avoiding overlooking important status changes. Secondly, intuitive visual cues reduce the risk of operational errors. Finally, this mechanism provides an effective technical means for tracking and managing equipment status, contributing to ensuring the safe operation of nuclear power plant systems. Through status comparison and dynamic display, operators can better understand changes in equipment status and make accurate operational decisions.

[0284] In some embodiments, this application also provides a linkage mechanism with external application systems, which is mainly implemented through two methods: functional interfaces and database interfaces.

[0285] In terms of functional interfaces, the flowchart engine provides a rich set of functional interface functions for external application systems. These systems can embed the flowchart engine into their own system interfaces and use these interface functions to achieve data interaction and functional control. Simultaneously, the flowchart engine also provides a data feedback interface, enabling external application systems to obtain feedback information from the engine, thus achieving bidirectional data transfer.

[0286] Specifically, the flowchart engine provides functional interfaces covering multiple aspects:

[0287] Graphic element control interfaces include highlight (xGaoliang), unhighlight (xUnGaoliang), blink (xFlash), and stop blinking (xStopFlash), which are used to control the display effects of graphic elements.

[0288] View operation interfaces include zoom in (xZoomIn), zoom out (xZoomOut), and refresh (xInvalidate), which are used to control the display scale and update of drawings.

[0289] Attribute operation interfaces include getting element attributes (xGetPropValue), modifying element attributes (xUpdateProp), and getting item database attributes (xGetV), which are used to access and modify item attribute information.

[0290] Isolation operation interfaces include adding isolation boundaries (xGeLi), adding historical isolation states (xHisGeLi), comparing isolation states (xDisGeLi), adding maintenance states (xWeixiu), canceling maintenance (xUnWeixiu), and resetting identifiers (xReset), which are used for system isolation analysis-related operations.

[0291] Interface control interfaces include showing or hiding toolbars (xShowLeftBar), directory trees (xShowTreeBar), property boxes (xShowPropBar), etc., used to control the display state of interface elements.

[0292] Drawing operation interfaces include opening drawings (xOpenFile), opening and locating drawing elements (xOpenAndPos), and updating the directory tree (xUpdateTree), which are used for opening and navigating drawings.

[0293] Intelligent application interfaces include intelligent drawing query (xNewSearch), logical diagram (xlogic), and drawing information download (xImage), which are used for database and drawing interaction and business identification screen archiving applications.

[0294] Operation feedback interfaces include maintenance status (xCurWeiXiu), isolation status (xCurGeLi), selected elements, switching drawings, and switching drawing tabs (SendMsg), which are used to provide feedback on operation and element identification status.

[0295] Regarding the database interface, since the flowchart database and the flowchart engine component are independent of each other, external application systems can choose to directly access the flowchart database through the database interface. In this way, the application system can read and process the data in the database according to actual needs, and then pass the processed data to the flowchart engine through the functional interface to achieve the display effect on the diagram.

[0296] This dual-interface design offers strong flexibility and scalability. The functional interface provides a standardized calling method, enabling external systems to easily control the display and operation of the flowchart, while the database interface offers greater freedom in data processing, allowing external systems to process data according to specific needs.

[0297] Furthermore, these interfaces can be expanded according to specific application needs, adding new functional interfaces or data processing methods to adapt to constantly changing application scenarios. This interface mechanism provides a solid technical foundation for the integrated application of flowchart digitization systems, enabling the system to better serve the various business needs of nuclear power plants.

[0298] Please refer to Figure 19. This application embodiment also provides a nuclear power plant system flowchart digitization device that can implement the above-mentioned nuclear power plant system flowchart digitization method, including:

[0299] The acquisition module is used to acquire multiple process drawing files corresponding to the target nuclear power plant and multiple item attributes; wherein, each process drawing file includes multiple symbol information, and each symbol information is used to represent a type of item;

[0300] A construction module is used to construct a flowchart directory tree based on the plurality of flowchart drawing files and the item attributes corresponding to each of the symbol information; wherein, the flowchart directory tree includes a drawing directory level and an item catalog level, the drawing directory level includes at least one of the flowchart drawing files, and the item catalog level includes at least one of the items.

[0301] The determination module is used to determine the corresponding target digital element from the drawing catalog level or the item catalog level;

[0302] The display module displays the target digitized element in a preset drawing display area.

[0303] The method for digitizing a nuclear power plant system flowchart according to an embodiment of this application includes: acquiring multiple flowchart drawing files corresponding to a target nuclear power plant and multiple item attributes; wherein each flowchart drawing file includes multiple symbol information, and each symbol information is used to represent a type of item; constructing a flowchart directory tree based on the multiple flowchart drawing files and the item attributes corresponding to each symbol information; wherein the flowchart directory tree includes a drawing directory level and an item catalog level, the drawing directory level includes at least one flowchart drawing file, and the item catalog level includes at least one item; determining the corresponding target digitized element from the drawing directory level or the item catalog level; and displaying the target digitized element in a preset drawing display area. This application can improve the analysis efficiency of various operations in a nuclear power plant system by digitizing the flowchart.

[0304] This application first establishes a unified digital data foundation by acquiring multiple process flow diagram files and their corresponding item attribute information from a nuclear power plant. Each process flow diagram file's symbol information is associated with a specific item type, achieving a mapping between graphics and data. This avoids the problem of the separation between diagram information and actual equipment data in traditional PDF format, laying the foundation for subsequent digital applications. Secondly, based on the acquired process flow diagram files and item attributes, a hierarchical process flow directory tree is constructed. This directory tree includes not only a diagram directory level but also an item directory level, forming a complete digital information index system. This hierarchical organization allows users to quickly locate and access the required diagrams or equipment information from different dimensions, greatly improving information retrieval efficiency. Compared to traditional folder-based management, the directory tree structure better suits the hierarchical characteristics of a nuclear power plant system, facilitating information classification management and rapid location. Thirdly, by flexibly selecting target digital elements in the directory tree and displaying them in a preset diagram display area, dynamic visualization of the process flow is achieved. This interactive display method breaks through the limitations of traditional static PDFs, making the display of diagram information more flexible and intuitive. This application realizes the transformation of nuclear power plant system flowcharts from static documents to a dynamic digital platform. By establishing a unified data model, constructing an intelligent retrieval system, and providing a flexible display interface, it significantly improves the work efficiency of various operational processes in nuclear power plants.

[0305] Referring to Figure 20, which illustrates the hardware structure of an electronic device according to another embodiment, the electronic device includes:

[0306] The processor 2001 can be implemented using a general-purpose CPU (Central Processing Unit), microprocessor, application-specific integrated circuit (ASIC), or one or more integrated circuits, and is used to execute relevant programs to implement the technical solutions provided in the embodiments of this application.

[0307] The memory 2002 can be implemented as a read-only memory (ROM), static storage device, dynamic storage device, or random access memory (RAM). The memory 2002 can store the operating system and other application programs. When the technical solutions provided in the embodiments of this specification are implemented through software or firmware, the relevant program code is stored in the memory 2002 and is called and executed by the processor 2001 using the nuclear power plant system flowchart digitization method of the embodiments of this application.

[0308] Input / output interface 2003 is used to implement information input and output;

[0309] The communication interface 2004 is used to enable communication and interaction between this device and other devices. Communication can be achieved through wired means (such as USB, network cable, etc.) or wireless means (such as mobile network, Wi-Fi, Bluetooth, etc.).

[0310] Bus 2005 transmits information between various components of the device (e.g., processor 2001, memory 2002, input / output interface 2003, and communication interface 2004);

[0311] The processor 2001, memory 2002, input / output interface 2003 and communication interface 2004 are connected to each other within the device via bus 2005.

[0312] This application also provides a computer program product, which includes a computer program. A processor of a computer device reads and executes the computer program, causing the computer device to perform the above-described method for digitizing the nuclear power plant system flowchart.

[0313] The terms “first,” “second,” “third,” “fourth,” etc. (if present) in the specification and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented, for example, in orders other than those illustrated or described herein. Furthermore, the terms “comprising” and “including,” and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or apparatus that includes a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatuses.

[0314] It should be understood that in this application, "at least one (item)" means one or more, and "more than" means two or more. "And / or" is used to describe the relationship between related objects, indicating that three relationships can exist. For example, "A and / or B" can represent three cases: only A exists, only B exists, and both A and B exist simultaneously, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can represent: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, and c can be single or multiple.

[0315] It should be understood that in the description of the embodiments of this application, "multiple" means two or more, "greater than", "less than", "exceeding" etc. are understood to exclude the number itself, and "above", "below", "within" etc. are understood to include the number itself.

[0316] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces, or indirect coupling or communication connection between apparatuses or units, and may be electrical, mechanical, or other forms.

[0317] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0318] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0319] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0320] It should also be understood that the various implementation methods provided in this application can be combined arbitrarily to achieve different technical effects.

[0321] The above is a detailed description of the embodiments of this application. However, this application is not limited to the above embodiments. Those skilled in the art can make various equivalent modifications or substitutions without departing from the spirit of this application. All such equivalent modifications or substitutions are included within the scope defined by the claims of this application.

Claims

1. A method for digitizing a nuclear power plant system flowchart, characterized in that, The method includes: Obtain multiple process drawing files and multiple item attributes corresponding to the target nuclear power plant; wherein, each process drawing file includes multiple symbol information, and each symbol information is used to represent a type of item; Based on the multiple process drawing files and the item attributes corresponding to each of the symbol information, a process drawing directory tree is constructed; wherein, the process drawing directory tree includes a drawing directory level and an item catalog level, the drawing directory level includes at least one of the process drawing files, and the item catalog level includes at least one of the items. Determine the corresponding target digitized element from the drawing catalog level or the item catalog level; The target digitized element is displayed in the preset drawing display area.

2. The method according to claim 1, characterized in that, The flowchart directory tree further includes project directory levels, unit directory levels, system directory levels, item type directory levels, and sub-item directory levels. The project directory levels include at least one unit directory level, the unit directory level includes at least one system directory level, the system directory level includes at least one flowchart drawing file directory level, the flowchart drawing file directory level includes at least one item type directory level, and the item type directory level includes at least one item level. Based on the multiple flowchart drawing files and the item attributes corresponding to each symbol information for each item, the flowchart directory tree is constructed, including: Obtain the drawing number of each process drawing file, and obtain the unit number and system information corresponding to each process drawing file based on the drawing number; The project directory hierarchy is constructed based on the target nuclear power plant; The unit directory hierarchy is constructed under the project directory hierarchy based on each of the aforementioned unit numbers; Based on the system information corresponding to each process drawing file, the system directory hierarchy is constructed under the corresponding unit directory hierarchy; Based on each drawing number, the drawing directory hierarchy is constructed under the corresponding system directory hierarchy; Based on the item attributes corresponding to each item, construct the item type directory hierarchy under the corresponding drawing directory hierarchy; Based on the item attributes of each item, the item catalog level is constructed under the corresponding item type catalog level; When the item attribute of the item includes sub-item information, the sub-item catalog level is constructed under the corresponding item catalog level based on the sub-item information.

3. The method according to claim 2, characterized in that, The method further includes: The search box is displayed in a preset position within the preset directory tree display area; In response to the input of a search value in the search box, a query is performed in the flowchart directory tree based on the search value; When a directory level that matches the search value is found, the directory level that matches the search value is determined as the target directory level. Jump to the target directory level from the content displayed in the directory tree display area.

4. The method according to claim 3, characterized in that, The flowchart drawing file is stored in a flowchart database. When no directory level matching the search value is found, the method further includes: The process diagram file corresponding to the search value is obtained by querying the process diagram database. Update the flowchart directory tree based on the flowchart drawing file corresponding to the search value; In the updated flowchart directory tree, a query is performed based on the value to be searched, and the queried directory level is determined as the target directory level; Jump to the target directory level from the content displayed in the directory tree display area.

5. The method according to claim 3, characterized in that, When the value to be searched is the code of the target item, the method further includes: The target item code is used to search the flowchart database to identify multiple flowchart drawing files; The first obtained process drawing file is displayed as the main display drawing in the drawing display area, and the item corresponding to the target item code is located and highlighted in the main display drawing; The remaining process drawing files will be displayed sequentially in the drawing display area in tab format; In response to selecting any of the tabs, the flowchart paper file corresponding to the tab is switched and displayed, and the item is positioned and highlighted.

6. The method according to claim 3, characterized in that, The method further includes: In response to selecting a process drawing file in the directory tree display area and triggering a logic diagram generation operation, the connection relationship data of pipes and equipment in the process drawing file is obtained according to the item attributes of each item; An undirected topology graph is generated based on the connection relationship data; The undirected topological graph is converted into a directed logical graph using a preset conversion rule, wherein the preset conversion rule is based on the preset upstream and downstream relationships of the items in the item attributes.

7. The method according to claim 1, characterized in that, The symbol information includes pipe connectors, and the method further includes: In response to selecting a pipe cross-drawing connector in the drawing display area, obtain the associated drawing information and associated pipe name information of the pipe cross-drawing connector; Based on the associated drawing information, the associated drawings are displayed in the drawing display area; Based on the associated pipe name information, the associated pipe is located and highlighted in the associated drawing.

8. The method according to claim 1, characterized in that, The method further includes: In response to selecting a target process drawing file in the drawing display area, obtain the location information of all pipe interfaces in the target process drawing file; Iterate through the item attributes of the pipe interfaces to obtain the associated drawings for each pipe interface; The target process drawing file and the associated drawings are combined to form a merged drawing; The pipe interfaces with connection relationships are identified in the merged drawings.

9. The method according to claim 1, characterized in that, The method further includes: In response to the selection of the symbol information in the drawing display area, menu options are generated according to the item type of the symbol information; In response to the selection of the menu option, the identification information of the corresponding item is displayed in the preset item attribute display area; Perform an identifier addition operation based on the identifier information, and add a target identifier to the symbol information in the drawing display area; The item attributes of the corresponding items in the flowchart database are updated synchronously based on the target identifier.

10. The method according to claim 1, characterized in that, The method further includes: Receive an identifier addition instruction, wherein the identifier addition instruction includes a target item and a target state; An isolation boundary list is calculated based on the item attributes of the target item. The isolation boundary list includes multiple boundary devices and their corresponding isolation states. Iterate through each boundary device in the isolation boundary list and identify multiple flowchart paper files containing the boundary devices; Locate the symbol information corresponding to the boundary device in the process drawing file; The format of the target identifier is determined based on the isolation status of the boundary device; Add the target identifier around the symbol information, and synchronously update the corresponding isolation status information of the target identifier to the corresponding item attribute.

11. The method according to claim 10, characterized in that, The step of calculating the isolation boundary list based on the item attributes of the target item includes: Determine the equipment type of the target item based on the item attributes; Obtain the corresponding isolation rules based on the device type, wherein the isolation rules include: The isolation boundary of passive devices is the isolation valves upstream and downstream; The isolation boundary of active devices includes the power isolation point and the gas supply isolation point; Starting with the target item, a graph traversal algorithm is used to traverse the corresponding flowchart until an item that meets the isolation rules is found. The items that conform to the isolation rules are used as boundary devices to generate the isolation boundary list.

12. The method according to claim 10, characterized in that, After adding the target identifier around the symbol information and synchronously updating the corresponding identifier information of the target identifier to the corresponding item attribute, the method further includes: Obtain the historical isolation status corresponding to the item; Compare the target state with the historical isolation state; When the target state is inconsistent with the historical isolation state, the target identifier is updated and displayed based on the target state and the historical isolation state; Control the target identifier to flash at a preset frequency.

13. A device for digitizing a nuclear power plant system flow chart, characterized in that, include: The acquisition module is used to acquire multiple process drawing files corresponding to the target nuclear power plant and multiple item attributes; wherein, each process drawing file includes multiple symbol information, and each symbol information is used to represent a type of item; A construction module is used to construct a flowchart directory tree based on the plurality of flowchart drawing files and the item attributes corresponding to each of the symbol information; wherein, the flowchart directory tree includes a drawing directory level and an item catalog level, the drawing directory level includes at least one of the flowchart drawing files, and the item catalog level includes at least one of the items. The determination module is used to determine the corresponding target digital element from the drawing catalog level or the item catalog level; The display module displays the target digitized element in a preset drawing display area.

14. An electronic device, characterized in that, include: A memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the nuclear power plant system flowchart digitization method as described in any one of claims 1 to 12.

15. A computer-readable storage medium, characterized in that, The storage medium stores a program that is executed by a processor to implement the nuclear power plant system flowchart digitization method as described in any one of claims 1 to 12.

Images