Analyzing and structuring method for nuclear power operation regulation digitalization

Abstract

The invention relates to the technical field of nuclear power operation digitization, in particular to an analysis and structuring method for nuclear power operation regulation digitization. The method comprises the following steps: constructing a basic service and resource library, and configuring a rule template for structured conversion; uploading a rule file to be digitalized, and selecting one or more rule templates to analyze the rule file to obtain a structured rule; the operation of the structured regulation is converted into the operation on the space on the HTML canvas, and online editing of the structured regulation is achieved; the method comprises the following steps: acquiring an HTML canvas, storing a structured regulation, instantiating a control on the HTML canvas, reloading a control event, and debugging the structured regulation based on the instantiated HTML canvas layout control. The method is high in digitization degree and high in editing and searching efficiency, and human errors during conversion are reduced.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of nuclear power operation digitization, and particularly relates to a parsing and structuring method for nuclear power operation procedure digitization. BACKGROUND

[0002] Nuclear safety is the lifeline of nuclear power development, and its guarantee is highly dependent on a set of extremely rigorous, complex and logically strict procedure file system. These procedures are the highest action guidelines for nuclear power plant operators and maintenance personnel when performing operations, handling abnormalities and responding to accidents, and are directly related to the state control of the unit and the maintenance of the nuclear safety level.

[0003] Generally, the operation procedure file system of a nuclear power plant is a complex system with multiple levels and types, mainly including but not limited to the following categories:

[0004] System Procedures: The operation steps for starting, stopping, testing and isolating specific systems or equipment in the plant.

[0005] General Operating Procedures: Covers standard operations and monitoring requirements during normal operation of the plant.

[0006] Abnormal Operating Procedures (AOPs): Used to guide operators in diagnosing and handling equipment failures or system abnormalities.

[0007] Emergency Operating Procedures (EOPs): Used to respond to design basis accidents and beyond design basis accidents, aiming to mitigate the consequences of accidents and restore the plant to a safe state.

[0008] Alarm Response Procedures (ARPs): Provide preliminary diagnosis and response guidance for specific alarm signals in the control room.

[0009] However, the current management mode of most nuclear power plants at home and abroad is still in the relatively primary "digitization" stage, i.e., the so-called "electronicization of paper documents". Its specific performance is that the procedure files are usually stored in the computer system in the form of unstructured or semi-structured electronic documents such as PDF, Word or plain text. Although this management mode has made some progress in document retrieval, distribution and archiving compared to pure paper documents, its essence has not changed, and it has many inherent defects and limitations, which constitute potential risk sources for human error. SUMMARY

[0010] The technical problem solved by the present application is to provide a method for analyzing and structuring nuclear power operation regulations, which has high digitalization degree and high editing and searching efficiency.

[0011] The present application provides a method for analyzing and structuring nuclear power operation regulations, which comprises the following steps:

[0012] Step S1: constructing a basic service and resource library, and configuring a rule template for structured conversion;

[0013] Step S2: uploading a regulation file to be digitized, selecting one or more rule templates to analyze the regulation file, and obtaining a structured regulation;

[0014] Step S3: converting the operation of the structured regulation into an operation on a space on an HTML canvas, and realizing online editing of the structured regulation;

[0015] Step S4: saving the structured regulation, instantiating a control on the HTML canvas, reloading a control event, and debugging the structured regulation based on the instantiated HTML canvas control.

[0016] In an embodiment of the present application, the step S1 specifically comprises:

[0017] Step S1-1: constructing a basic service and resource library;

[0018] deploying a file storage service;

[0019] deploying a regulation file management service;

[0020] constructing a control library;

[0021] Step S1-2: configuring a rule template for structured conversion.

[0022] In an embodiment of the present application, in the step S1-2, the rule template comprises document basic information configuration, document structure analysis configuration, whether a line can be added or deleted, operation dynamic parameters, document special symbols, and control matching rules.

[0023] In an embodiment of the present application, the step S2 specifically comprises:

[0024] Step S2-1: uploading and managing an original regulation file;

[0025] Step S2-2: applying a rule template for automatic analysis and conversion;

[0026] Step S2-3: generating structured data.

[0027] In an embodiment of the present application, the step S2-1: the user uploads the original procedure file in DOC / DOCX format through the interface provided by the procedure file management service, renames the file during the uploading, the service records the file meta information and stores it in the file storage service, and marks the structured state of the file as unstructured;

[0028] The step S2-2: the user selects one or more rule templates from the rule templates created in the step S1-2 and applies them to the uploaded procedure file, parses the file content according to the instructions in the rule templates, and extracts the text, style, table, and picture;

[0029] The step S2-3: the parsed elements are automatically mapped and converted into the machine-readable JSON data structure composed of the control objects defined in the control library according to the rules, and after the conversion, the procedure file management service updates the file state to structured success.

[0030] In an embodiment of the present application, the step S3 specifically includes:

[0031] The step S3-1: the structured procedure is loaded and rendered in the editor, and the procedure editor is run, the core components of which include the navigation bar, the HTML canvas, the control bar, and the attribute and event bar;

[0032] The step S3-2: the editing and enhancement are performed based on the control library;

[0033] The editing operation includes the rendering and direct editing, the control management, the attribute configuration, and the event binding.

[0034] In an embodiment of the present application, the step S4 specifically includes:

[0035] The step S4-1: the structured data and the procedure file are saved;

[0036] The saving of the structured data specifically includes saving all the configurations of the final JSON data on the canvas back to the database;

[0037] The saving of the procedure file specifically includes forming the structured version of the procedure file in addition to the original procedure file if it is the first structured, the file format being DOC / DOCX, and the structured editing changes can be written back to the document; if it is not the first structured, selecting to update the previous version of the structured procedure file or generating a new version;

[0038] The step S4-2: the control on the HTML canvas is instantiated, the control event is reloaded, and the structured procedure is debugged based on the instantiated HTML canvas control.

[0039] The application provides a kind of for nuclear power operation regulation digitization resolution and structured system, comprising: application layer, service layer and core layer;

[0040] The application layer is used for direct interaction with users, including regulation file management module, for providing regulation file upload, download, version comparison, delete function operation;

[0041] Regulation template management module provides the interface of regulation template increase, delete, modification, query operation, and user configures each matching rule through visual form or editor;

[0042] Visual rule editing module is used for running regulation editor;

[0043] Regulation execution and debugging module is used for debugging running environment;

[0044] Service layer provides general, reusable background service support for application layer, including file storage module, for binary file physical storage, version management and quick access;

[0045] Real-time data service module is used for data interaction with other systems of power plant;

[0046] Core layer is used for calculation and processing data, including structured analysis engine, for receiving original regulation file and user-selected rule template, executing analysis algorithm, and cutting, identifying and converting document according to rules in template, finally outputting structured JSON data;

[0047] Control library management engine is a core engine for dynamically managing control library;

[0048] Event processing engine is an embedded JavaScript execution environment.

[0049] In a specific embodiment of the application, the visual rule editing module includes:

[0050] Navigation bar: display document directory tree;

[0051] Toolbar: provide save, debug, preview and other buttons;

[0052] Control bar: all available controls in control library are displayed in the form of icon list;

[0053] HTML canvas: main area for rendering and editing regulations;

[0054] Property and event panel: used for configuring properties and binding events of currently selected control.

[0055] In a specific embodiment of the application, the event processing engine processes the following two types of events.

[0056] Interaction event response: handle user clicks, input operations;

[0057] State event listening: listen to power plant data changes through real-time data services and trigger corresponding style updates.

[0058] Compared with the prior art, the parsing and structuring method for nuclear power operation regulation digitization has the following beneficial effects:

[0059] First, a major breakthrough has been achieved in the efficiency and accuracy of nuclear power regulation digitization. Traditional methods usually rely on manual parsing and semi-automatic tools, which are slow, have high error rates, and are difficult to adapt to multiple types and versions of regulation files. The present invention realizes the automatic structured parsing of DOC / DOCX format files through predefined rule templates (supporting JSON or visual form configuration), which can efficiently extract text, tables, pictures, format attributes and other elements and convert them into standardized JSON data. This process not only greatly improves the parsing efficiency, but also reduces the structured errors caused by subjective misjudgment through template rules. In contrast, existing technologies often lack a unified parsing standard, resulting in inconsistent digitization results, while the present invention achieves a highly repeatable and extensible parsing process through configurable templates.

[0060] Second, innovation has been made in the interactivity and dynamic response capability of the regulation. Traditional digitized regulations are mostly static documents or simple electronic forms, lacking integration capability with real-time data. The present invention uses HTML5 canvas technology to map structured data to interactive controls and supports drag-and-drop low-code editing. More importantly, the controls support two-way binding with unit measurement point data, and state events and interaction events are realized through JavaScript scripts. This makes the regulation not only static display, but also dynamic response to unit operation state changes, such as automatic highlighting of abnormal measurement point values or automatic updating of data through timer events. Existing technologies usually cannot achieve such real-time monitoring and dynamic interaction, thus cannot effectively assist operators to respond to abnormal states quickly, while the present invention significantly improves the practicality and safety of the regulation through control design.

[0061] Third, it provides a comprehensive solution for the editing, maintenance, and version management of procedures. In the traditional model, modifying a procedure requires reprocessing the entire document, which is inefficient and prone to errors. This invention, through the separation of structured data and control objects, supports online visual editing, event binding, and version control. Users can flexibly add, delete, or adjust controls, and the modified results can be written back to the original document without destroying the format. Simultaneously, the system manages multi-version structured data through file storage services, ensuring that historical versions are traceable and reusable. In contrast, existing technologies often lack integrated version management functions, leading to chaotic procedure updates or compatibility issues, while this invention achieves refined management of the entire procedure lifecycle through a systematic design.

[0062] Fourth, it has significant advantages in reducing human error and improving operational safety. Nuclear power plant regulations are extremely complex and require real-time updates. Traditional paper or simple electronic regulations are prone to accidents due to human error, such as misreading or missing steps. This invention automates and standardizes key operational steps through event-driven mechanisms and status monitoring of controls, reducing the risk of human error. For example, warning controls can display pop-up prompts when the mouse hovers over the device, or verify operational conditions in real time by binding measurement point data. Existing technologies typically lack such intelligent verification functions, while this invention, through deep integration of business logic and real-time data, constructs an error-proofing mechanism, reducing the probability of human-caused events at the source.

[0063] Finally, it demonstrates significant advantages in system compatibility and scalability. This invention supports multiple procedure types and custom control libraries, and can flexibly adapt to different file structures through rule templates. Furthermore, it achieves seamless integration with external systems through standardized interfaces, supporting future functional expansion. In contrast, existing technologies are mostly limited to specific file formats or fixed processes, lacking universality and adaptability. The template-based and modular design of this invention enables it to quickly adapt to the evolution of nuclear power procedures, providing long-term support for digital transformation.

[0064] In summary, the parsing and structuring method for digitizing nuclear power plant operation procedures provided by this invention can identify and parse nuclear power plant operation procedure documents, including system procedures, overall procedures, EOP procedures, and alarm procedures, to form structured data. It can identify specified content in the digitized documents online as special controls through custom structured conversion rules, achieving document structuring and complete control-based functionality. This allows users to edit structured procedures online using a drag-and-drop low-code approach, configuring events and attributes for controls to achieve real-time binding of unit data and behavioral logic control. The method also allows for debugging and verification of the dynamic effects of the structured procedure pages. Furthermore, it provides standardized data interfaces, stores execution logs, forming a traceable and complete data chain. Through behavioral logic control, it helps reduce the probability of human-caused events, achieving data-driven quality control. BRIEF DESCRIPTION OF DRAWINGS

[0065] Figure 1 A flow chart showing a parsing and structuring method for digitalization of nuclear power operation procedures. DETAILED DESCRIPTION

[0066] For a further understanding of the present application, the embodiments thereof will be described in conjunction with examples, it being understood that these descriptions are intended not to limit the present application but to serve as a means to further illustrate the features and advantages thereof.

[0067] The embodiments of the present application disclose a parsing and structuring method for digitalization of nuclear power operation procedures, as shown in Figure 1 The method comprises the following steps:

[0068] Step S1: constructing a basic service and resource library, and configuring a rule template for structured conversion;

[0069] Specifically, the method comprises the following steps:

[0070] Step S1-1: constructing a basic service and resource library;

[0071] Deploying a file storage service: used for centralized management of all procedure file versions, including different versions of original procedure files and structured procedure files generated after processing and uploaded subsequently.

[0072] Deploying a procedure file management service: based on the file storage service, the service provides upper-layer application functions, including functions of the name of a procedure file, a procedure type, a structured state, version management, and file uploading and downloading.

[0073] The procedure type comprises a general procedure, a system procedure, an EOP procedure, an alarm procedure, and the like;

[0074] The structured state comprises three states of unstructured, structured success, and structured failure;

[0075] The version management is different from the original procedure file, and is used for management of different versions of structured procedure files;

[0076] The file uploading: used for procedure file uploading, the file name can be renamed when uploading the file, and the procedure file after uploading needs to be saved in the file storage service;

[0077] The file downloading: providing functions of downloading or batch downloading of an original version procedure file; providing functions of downloading or batch downloading of a structured version procedure file.

[0078] Control library construction: define and manage all available control objects, including control name, control icon, page element type, control state, etc. Each control object is encapsulated based on HTML form elements, and its configurable properties and allowed event types are predefined. The role of this library is to constrain and standardize editing behavior, ensuring that only predefined safe and compliant controls can be used.

[0079] The HTML form elements include text, picture, input box, button, hyperlink, time selector, checkbox, upload;

[0080] Different form elements have their own specific properties to control their appearance and state, as shown in Table 1.

[0081] Table 1

[0082]

[0083] The allowed event types include interactive events or state events;

[0084] The interactive events: add event listeners to the control to respond to various events such as single click, double click, mouse over, mouse out, and use timers to create timing events. Add scripts to these events using JavaScript to achieve different effects such as pop-up, jump, flash, modify background color, HTTP call, etc. User-triggered behavior. For example, bind the mouse click event to the button and write JavaScript scripts to achieve pop-up, jump, HTTP call (save data), flash, etc.

[0085] The state events: bind the control to the power plant real-time data. The control can be bidirectionally bound to the unit measurement point. When the value comparison, value threshold, etc. are defined in advance, when the measurement point value changes, the change can be listened to through JavaScript, and the CSS style associated with the value can be updated accordingly, such as value color, value gradient, or value text.

[0086] When the control object defines the control event, the default JavaScript script for the control event can be written to achieve more rich effects, as shown in Table 2.

[0087] Table 2

[0088]

[0089]

[0090] Step S1-2: Configure the rule template of structured conversion;

[0091] The rule template is the core basis for realizing the structure, which is configured in JSON format or visual form, ensuring flexibility and scalability.

[0092] The rule template includes document basic information configuration, document structure analysis configuration, whether to add or delete lines, running dynamic parameters, document special symbols, and control matching rules.

[0093] The document basic information configuration defines the extraction rules of the document main body and file number metadata, and realizes accurate identification by positioning chapter numbers, table numbers, line numbers, and cell numbers.

[0094] The document structure analysis configuration divides the document into several parts according to the digital analysis method, such as cover, table of contents, instruction page, digital operation sheet, and appendix page, and defines the identification rules to ensure clear data hierarchy after analysis.

[0095] Editing permission configuration: Set whether the structured document allows users to add or delete lines to balance automation processing and human flexibility.

[0096] Running dynamic parameter configuration: Predefine parameters such as interface address that the system depends on during running, such as API address for querying unit measurement point data, URL for file upload service, etc.; support subsequent data binding and interaction functions;

[0097] Document special symbol mapping: Establish a mapping table between special symbols in Word documents that are not supported by HTML and alternative characters to avoid rendering errors.

[0098] Control matching rule: Define the rule of automatically identifying and converting specific text or style to corresponding control. The rule can be based on text content, regular expression, font color, background color, cell position, etc.

[0099] For example:

[0100] The text content is "__________" -> identified as a text input box control.

[0101] The text content is "[]" -> identified as a checkbox control.

[0102] The text matches the regular expression <[A-Za-z0-9-]+> and the color is red -> identified as a hyperlink jump control.

[0103] The cell background is red and the text is white -> identified as a warning control.

[0104] Step S2: Upload the procedure file to be digitized, select one or more rule templates to analyze the procedure file, and obtain the structured procedure.

[0105] In particular, the method comprises:

[0106] Step S2-1: uploading and managing original procedure files. A user uploads original procedure files in DOC / DOCX format through the interface provided by the procedure file management service. The file can be renamed during uploading. The service records the file meta information and stores it in the file storage service, and marks its structured state as "unstructured";

[0107] Step S2-2: applying rule templates for automatic parsing and conversion. The user selects one or more rule templates from those created in step S1-2 to apply to the uploaded procedure files. The system parses the file content according to the instructions in the rule templates, especially the control matching rules, and extracts elements such as text, style, table, and picture;

[0108] Step S2-3: generating structured data. The system automatically maps and converts the parsed elements into machine-readable JSON data structures composed of control objects defined in the control library according to the rules. This JSON data describes the document content, style, and preliminary control logic. After successful conversion, the procedure file management service updates the file status to "structured successfully";

[0109] Step S3: converting the operations of the structured procedure into operations on the space of the HTML canvas to realize online editing of the structured procedure;

[0110] This phase checks, refines, and deeply configures the results of automatic conversion in the running procedure editor.

[0111] In particular, the method comprises:

[0112] Step S3-1: loading and rendering the structured procedure in the editor. The procedure editor is run, and its core components include:

[0113] Navigation bar: displays the document directory generated from the JSON data.

[0114] HTML canvas: the core area for rendering JSON data, WYSIWYG, and consistent appearance with the original document.

[0115] Control bar: lists all defined control objects in the control library, such as text, input box, button, hyperlink, time selector, picture, upload, checkbox, etc.

[0116] Property and event bar: used to configure the properties and events of the currently selected control.

[0117] The HTML is preferably HTML5.

[0118] Step S3-2: editing and enhancing based on the control library. The user edits the control on the canvas, and all operations are subject to the constraints predefined in the control library:

[0119] The editing operation includes:

[0120] Rendering and direct editing: the canvas content has been fully controlled. The user can directly edit the text content and its style (font, color, etc.), just like operating in Word.

[0121] Control management: including adding and deleting;

[0122] Add: add new controls such as signature buttons and data storage buttons to the specified position of the canvas by drag and drop from the control bar.

[0123] Delete: any control on the canvas or converted from text can be directly deleted.

[0124] Property configuration: after selecting the control, its specific properties can be configured in the property bar. These properties have been defined when the control object is defined, which guarantees the standardization and security. For example:

[0125] Text control: background color, font color, font, size, etc. can be configured.

[0126] Picture control: width, height, path can be configured.

[0127] Hyperlink control: target URL can be configured.

[0128] Event binding: after selecting the control, bind the behavior in the event bar. The event type must be within the allowed range of the control library, and the event effect of the control object only takes effect in the debugging case;

[0129] The event includes an interactive event or a state event;

[0130] Configuration of the interactive event: one of the control events can be selected for the control object, such as including mouse click event and mouse double-click event when the control object is defined. Therefore, the mouse click event can be selected as the dynamic effect of the selected control object at any position of the HTML5 canvas, and the mouse double-click event can be selected as the dynamic effect of the same control object at another position of the HTML5 canvas. If the control object interactive event is not changed, i.e. the JavaScript script is rewritten to change the control interactive event, the interactive event effect of the control object is the default effect.

[0131] The configuration of the state event: the state event definition is generally related to values, and is usually operated as a control object binding a unit measurement point. By setting a calculation method, including value comparison, value threshold, etc., when the unit measurement point data reaches the trigger condition, the control attribute changes, including value color, value gradient or value text; for example, a digital display control, selecting the TEST_A measurement point, when the data is obtained, the text content changes from the default text to the actual value, setting the value color to red in hexadecimal when the value is greater than 80; when the value is less than 30, the value text changes to “abnormal value”; step S4: saving the structured procedure, instantiating the control on the HTML canvas, reloading the control event, and debugging the structured procedure based on the instantiated HTML canvas control.

[0132] Specifically includes:

[0133] Step S4-1: saving structured data and procedure files;

[0134] The saving of structured data specifically includes saving all configurations of the final JSON data on the canvas back to the database;

[0135] The saving of procedure files specifically includes: if it is the first structuring, forming a structured version of the procedure file in addition to the original procedure file, the file format is DOC / DOCX, and the structured edited changed content can be written back to the document, without causing damage to the document style; if it is not the first structuring, selecting to update the last version of the structured procedure file or generating a new version.

[0136] Step S4-2: instantiating the control on the HTML canvas, reloading the control event, and debugging the structured procedure based on the instantiated HTML canvas control;

[0137] After clicking “debug”, the system instantiates the JSON data: reloads the event JavaScript script of all controls, and the canvas switches from “edit mode” to “run mode”.

[0138] In this mode, all dynamic effects are verified:

[0139] Interactive events: test button clicks, pop-ups, jumps, data submission, etc.

[0140] State events: simulate or wait for real measurement point data changes, and verify whether the control style (color, text) is automatically updated according to the preset rules.

[0141] If the debugging is passed, it means that a static procedure has been successfully converted into a safe, interactive and intelligent application.

[0142] Through the above steps, the application successfully converts the static procedure into a dynamic, interactive, and intelligent operation guidance system that can be linked with real power plant data, forming a closed-loop digital management process.

[0143] Embodiments of the application disclose a parsing and structuring system for nuclear power operation procedure digitalization, comprising:

[0144] An application layer is used for direct interaction with a user.

[0145] Specifically, the application layer comprises:

[0146] A procedure file management module is used for providing operation of uploading, downloading, version comparison, and deleting function of the procedure file.

[0147] A procedure template management module provides an interface for adding, deleting, modifying, and querying operation of the procedure template, and the user configures each matching rule through a visual form or an editor.

[0148] A visual rule editing module is used for running a procedure editor, and specifically comprises:

[0149] A navigation bar is used for displaying a document directory tree.

[0150] A toolbar is used for providing buttons of saving, debugging, previewing, and the like.

[0151] A control bar is used for displaying all available controls in the control library in the form of an icon list.

[0152] An HTML canvas is used for rendering and editing a main area of the procedure.

[0153] An attribute and event panel is used for configuring attributes and binding events of a currently selected control.

[0154] A procedure execution and debugging module is used for debugging a running environment, and when the user clicks on the “debug” button, the module takes over the canvas, loads all event scripts, simulates or connects a real data environment, and lets the user verify dynamic effects of the procedure.

[0155] A service layer provides general and reusable background service support for the application layer.

[0156] Specifically, the service layer comprises:

[0157] A file storage module is used for physical storage, version management, and quick access of binary files, and provides a unified API for calling by the procedure file management module.

[0158] A real-time data service module is used for data interaction with other systems of the power plant, encapsulates all external data interface calls (such as querying measurement point data), and provides a unified and safe API for the event processing engine.

[0159] Core layer, for computing and processing data;

[0160] Specifically includes:

[0161] Structured parsing engine, for receiving "original procedure file" and user-selected "rule template", executing parsing algorithm, cutting, identifying and converting the document according to the rules in the template, and finally outputting structured JSON data;

[0162] Control library management engine, the core engine of dynamically managing the control library. It is responsible for providing a control list to the control bar of the "visual procedure editing module" when the editor starts; when the user configures the control, it verifies the legality of its operation (such as whether an undefined attribute is used); and instantiates the control during debugging and running.

[0163] Event processing engine, an embedded JavaScript execution environment. It is responsible for parsing, loading and executing the JavaScript script configured by the user for the control in the debugging and running modes. It handles two types of events:

[0164] Interaction event response: handles user clicks, input operations, etc.

[0165] State event listening: listens to power plant data changes through "real-time data service" and triggers corresponding style updates.

[0166] The workflow of the system is:

[0167] Initialization: the administrator defines the parsing rules through the rule template management module.

[0168] Entry: the engineer uploads the original procedure through the procedure file management module.

[0169] Conversion: the user triggers the operation, and the structured parsing engine automatically converts the procedure into a JSON structure.

[0170] Editing: the user edits and binds events to the procedure in the visual procedure editing module based on the control library.

[0171] Saving: the editing result is saved, and the new version file is stored in the file storage service.

[0172] Debugging / execution: the user verifies the function in the procedure execution and debugging module, the event processing engine obtains data through the real-time data service, and drives the interface to dynamically change.

[0173] Embodiments of the application also disclose an electronic device comprising a processor and a memory, wherein the processor is configured to execute the parsing and structuring method for nuclear power operation procedure digitization described in the above technical solutions; and

[0174] a memory for storing executable instructions of the processor.

[0175] The embodiment of the present application also discloses a computer readable storage medium, which stores executable instructions of a computer, and the executable instructions are executed by a processor to realize the method for analyzing and structuring nuclear power operation procedure digitalization.

[0176] The embodiment of the present application also discloses a computer program product, which comprises computer programs / instructions, and the computer programs / instructions are executed by a processor to realize the method for analyzing and structuring nuclear power operation procedure digitalization.

[0177] The above description of the embodiments is only used for helping to understand the method of the present application and its core idea. It should be noted that, for those skilled in the art, some improvements and modifications can be made to the present application without departing from the principle of the present application, and these improvements and modifications also fall within the protection scope of the claims of the present application.

[0178] The above description of the disclosed embodiments enables those skilled in the art to implement or use the present application. Various modifications to the embodiments will be apparent to those skilled in the art, and the general principles defined herein can be implemented in other embodiments without departing from the spirit or scope of the present application. Therefore, the present application will not be limited to the embodiments shown herein, but will conform to the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for parsing and structuring nuclear power plant operation procedures for digitalization, characterized in that, Includes the following steps: Step S1: Build basic services and resource repositories, and configure rule templates for structured transformation; Step S2: Upload the procedure file to be digitized, select one or more rule templates to parse the procedure file, and obtain the structured procedure; Step S3: Convert the operations of the structured procedure into operations on the space of the HTML canvas to realize online editing of the structured procedure; Step S4: Save the structured procedure, instantiate the controls on the HTML canvas, reload the control events, and debug the structured procedure based on the instantiated HTML canvas controls.

2. The parsing and structuring method for digitizing nuclear power plant operation procedures according to claim 1, characterized in that, Step S1 specifically includes: Step S1-1: Build basic services and resource library; Deploy file storage services; Deployment procedure document management service; Build a control library; Step S1-2: Configure the rule template for structured transformation.

3. The parsing and structuring method for digitizing nuclear power plant operation procedures according to claim 2, characterized in that, In steps S1-2, the rule template includes basic document information configuration, document structure parsing configuration, whether lines can be added or deleted, dynamic running parameters, special symbols in the document, and control matching rules.

4. The parsing and structuring method for digitizing nuclear power plant operation procedures according to claim 1, characterized in that, Step S2 specifically includes: Step S2-1: Upload and manage the original procedure files; Step S2-2: Apply rule templates for automated parsing and transformation; Step S2-3: Generate structured data.

5. The parsing and structuring method for digitizing nuclear power plant operation procedures according to claim 4, characterized in that, Step S2-1: The user uploads the original procedure file in DOC / DOCX format through the interface provided by the procedure file management service; the file is renamed during upload, the service records the file metadata and stores it in the file storage service, and marks its structured status as unstructured; Step S2-2: The user selects one or more rule files to be applied to the upload from the rule template created in step S1-2; according to the instructions in the rule template, the file content is parsed and text, styles, tables, and images are extracted; Step S2-3: The parsed elements are automatically mapped and converted into a machine-readable JSON data structure composed of control objects defined in the control library according to the rules. After successful conversion, the procedure file management service updates the file status to "structured successfully".

6. The parsing and structuring method for digitizing nuclear power plant operation procedures according to claim 1, characterized in that, Step S3 specifically includes: Step S3-1: Load and render the structured procedure in the editor; run the procedure editor, whose core components include: navigation bar, HTML canvas, control bar, properties and events bar; Step S3-2: Edit and enhance based on the control library; Editing operations include: rendering and direct editing, control management, property configuration, and event binding.

7. The parsing and structuring method for digitizing nuclear power plant operation procedures according to claim 1, characterized in that, Step S4 specifically includes: Step S4-1: Save the structured data and procedure files; The specific steps of saving structured data include: saving all configurations of the final JSON data on the canvas back to the database; The specific steps for saving the procedure file include: if it is the first time the procedure file is structured, a structured version of the procedure file is created in addition to the original procedure file, with the file format being DOC / DOCX, and the content changed by the structured editing can be written back into the document; if it is not the first time the procedure file is structured, the option is to overwrite and update the previous version of the structured procedure file or generate a new version. Step S4-2: Instantiate the controls on the HTML canvas, reload the control events, and debug the structured procedure based on the instantiated HTML canvas controls.

8. A system for parsing and structuring nuclear power plant operation procedures, characterized in that, include: Application layer, service layer, and core layer; The application layer is used to interact directly with users, including a procedure file management module, which provides functions for uploading, downloading, comparing versions, and deleting procedure files. The procedure template management module provides an interface for adding, deleting, modifying, and querying procedure templates. Users can configure various matching rules through a visual form or editor. The visual rule editing module is used to run the procedure editor; The procedure execution and debugging module is used to debug the runtime environment; The service layer provides general and reusable backend service support for the application layer, including a file storage module for physical storage, version management and fast access of binary files; The real-time data service module is used for data interaction with other systems in the power plant; The core layer is used for computing and processing data, including a structured parsing engine, which receives the original procedure file and the rule template selected by the user, executes the parsing algorithm, segments, identifies and transforms the document according to the rules in the template, and finally outputs structured JSON data. The control library management engine is the core engine for dynamically managing the control library. An event handling engine is an embedded JavaScript execution environment.

9. The parsing and structuring system for digitizing nuclear power plant operation procedures according to claim 8, characterized in that, The visualization rule editing module includes: Navigation bar: Displays the document directory tree; Toolbar: Provides buttons for saving, debugging, previewing, etc. Control Bar: Displays all available controls in the control library as an icon list; HTML canvas: The main area for rendering and editing procedures; Properties and Events panel: Used to configure the properties and bind events to the currently selected control.

10. The parsing and structuring system for digitizing nuclear power plant operation procedures according to claim 8, characterized in that, The event handling engine processes the following two types of events; Interactive event handling: Handling user clicks and input operations; Status event monitoring: Monitor changes in power plant data through real-time data services and trigger corresponding style updates.

Images