Thermal power plant control logic generation method, device, equipment and medium

Abstract

The invention relates to the technical field of industrial automation, and provides a thermal power plant control logic generation method, device and equipment and a medium, and the method comprises the steps: obtaining a source data file of a target thermal power plant, and generating a target function specification according to the source data file and a preset function specification template library; generating a target structured database file and a card arrangement diagram which can be imported by the DCS according to the target function specification and a preset allocation rule; generating a target logic description file in a uniform format according to the target function specification and the target structured database file; according to the target logic description file and a preset mapping relation, converting the textual logic relation into a visual target logic diagram; and according to the target logic description file and a preset process picture template, generating a target process picture with interaction capability. Through the scheme, the configuration efficiency is improved, human errors are reduced, the workload is reduced, and automatic generation from business requirements to DCS system logic diagrams and process pictures is realized.

Description

Methods, devices, equipment and media for generating control logic in thermal power plants Technical Field

[0001] This application relates to the field of industrial automation technology, and in particular to a method, apparatus, equipment and medium for generating control logic for thermal power plants. Background Technology

[0002] In the field of industrial automation, Distributed Control Systems (DCS) serve as the core support for process control in thermal power plants. Through predefined logical steps and operational procedures, they automate the management and control of key equipment such as boilers, turbines, and auxiliary equipment. This is a crucial technological means to ensure the safe and stable operation of power plants, improve production efficiency, and reduce manual intervention. However, the current configuration process of DCS control logic in thermal power plants still relies on a traditional, manually-led model, presenting several pressing technical challenges: First, the entire process is highly repetitive and involves a massive workload. Control logic configuration requires sequentially completing multiple steps, including writing functional specifications, establishing the DCS system database, describing logical relationships, drawing logic diagrams, and configuring process screens. Each step requires manual work by engineers based on project requirements—functional specifications must be written word by word, the database requires manual allocation of card positions, channels, and terminals and establishment of signal associations, and logic diagrams and process screens require drawing components and binding relationships one by one according to the process logic. This large amount of repetitive work leads to lengthy project cycles and consumes significant human resources.

[0003] Secondly, the risk of human error is high, making it difficult to guarantee system reliability. The control logic of thermal power plants involves a massive number of equipment parameters, measurement point signals, and complex process constraints. Manually writing functional specifications is prone to parameter omissions and ambiguities in logic descriptions. Manually configuring the database is prone to card channel allocation conflicts and signal association errors. Manually drawing logic diagrams and process screens is prone to component binding deviations and incorrect signal flow. These human errors can directly lead to control logic failure, seriously affecting the stability of the DCS system and the safety of the production process.

[0004] Furthermore, modification and maintenance are cumbersome and lack adaptability. In actual projects, due to the needs of process optimization and equipment modification, functional manuals often need to be modified frequently. In the traditional mode, a modification to one part of the manual requires simultaneous manual adjustment of database configuration, logical relationships, logic diagrams and process screens. The modification cost is high and it is easy to cause a chain reaction of problems where one modification leads to omissions in many other places. At the same time, the existing technology lacks a standardized template system and data interaction specifications. The configuration schemes of different projects and different DCS manufacturers are difficult to reuse. Faced with the diverse control scenarios of thermal power plants, similar configuration content needs to be repeatedly developed, which further reduces configuration efficiency.

[0005] Finally, existing technologies struggle to automate the entire process from source data to final implementation. Current technologies can only achieve semi-automation of single steps (such as simple logic diagram drawing or database configuration), but these steps are independent of each other, lacking a unified data-driven and collaborative generation mechanism. Manual intervention is still required for data conversion, format adaptation, and logic verification. This fails to meet the need for fully automated generation of control logic in thermal power plants, from source data input to functional specifications, database files, logic description files, logic diagrams, and process screens, thus hindering the efficient and precise development of DCS configuration.

[0006] In summary, the current control logic configuration of thermal power plants suffers from problems such as low efficiency, susceptibility to errors, cumbersome modification and maintenance, and insufficient automation of the entire process, which seriously affect the project delivery cycle and the reliability of system operation. Summary of the Invention

[0007] This application provides a method, apparatus, equipment, and medium for generating control logic in thermal power plants, aiming to solve many technical problems existing in related technologies, such as low efficiency, susceptibility to errors, cumbersome modification and maintenance, and insufficient automation of the entire process.

[0008] In a first aspect, embodiments of this application provide a method for generating control logic for a thermal power plant. The method includes: acquiring a source data file of a target thermal power plant; generating a target functional specification based on the source data file and a preset functional specification template library; generating a target structured database file and card layout diagram that can be imported into a DCS system based on the target functional specification and preset allocation rules; generating a target logic description file in a unified format based on the target functional specification and the target structured database file; converting textual logical relationships into a visual target logic diagram based on the target logic description file and preset mapping relationships; and generating a target process screen with interactive capabilities based on the target logic description file and preset process screen templates.

[0009] In one embodiment, optionally, the method further includes: editing the target functional specification according to the received specification editing instructions; and editing the target logic description file according to the received file editing instructions.

[0010] In one embodiment, optionally, the source data file includes equipment parameters, measurement point information, control target parameters, and process logic constraints of the target thermal power plant, wherein the equipment parameters include equipment model, rated operating parameters, and interface type, the measurement point information includes measurement point number, signal type, measurement range, and alarm threshold, and the format of the source data file includes a standardized table format.

[0011] In one embodiment, optionally, generating the target functional specification based on the source data file and a preset functional specification template library includes: reading the equipment parameters, measurement point information, control target parameters, and process logic constraints from the source data file, and classifying and extracting them according to data type and organizing them in a structured manner; searching for a target template matching the target thermal power plant control scenario from the preset functional specification template library, wherein the target template includes a fixed field framework of functional overview, parameter configuration, logical relationships, and constraint conditions; establishing the correspondence between the source data in the source data file and the fields of the target template through a field mapping algorithm, automatically filling the organized source data into the target fields corresponding to the target template, and generating the target functional specification.

[0012] In one embodiment, optionally, the target structured database file includes card configuration information and signal association data, wherein the card configuration information includes card location, type, channel and terminal allocation results, and the signal association data includes the mapping relationship between measurement point signals and card channels and control logic elements.

[0013] In one embodiment, optionally, a unified format target logic description file is generated based on the target function specification and the target structured database file, including: extracting control objectives, process logic relationships, equipment interaction rules, and constraints from the target function specification, and reading card configuration information and signal association data from the target structured database file; decomposing the control objective into logical operation content, signal input / output content, and timing control content based on the signal association data; using a preset XML tag system to structurally describe each decomposed content, wherein logical operation content defines the operation type through logical operation tags, signal input / output content binds the corresponding card channel and measurement point signal through equipment association tags and signal transmission tags, and timing control content clarifies the action execution order through control timing tags; and combining the tagged descriptions of each decomposed content according to a preset hierarchical structure to form a unified format target logic description file.

[0014] In one embodiment, optionally, the preset mapping relationship includes the correspondence rules between logical relationships and graphical elements, node layout rules, and connection association rules; the target logic diagram includes the control function architecture, signal flow direction, and parameter configuration information; the preset process screen template includes the APS system template, the equipment monitoring template, and the trend analysis template, each template having built-in visualization components, the visualization components including at least one of the following: buttons, dashboards, indicator lights, line charts, and pie charts.

[0015] Secondly, embodiments of this application provide a control logic generation device for a thermal power plant, comprising: an acquisition module for acquiring source data files of a target thermal power plant and generating a target functional specification based on the source data files and a preset functional specification template library; a first generation module for generating a target structured database file and card layout diagram that can be imported into a DCS system based on the target functional specification and preset allocation rules; a second generation module for generating a target logic description file in a unified format based on the target functional specification and the target structured database file; a conversion module for converting textual logic relationships into a visual target logic diagram based on the target logic description file and preset mapping relationships; and a third generation module for generating a target process screen with interactive capabilities based on the target logic description file and a preset process screen template.

[0016] Thirdly, a computer device is provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the steps of the above-described method for generating control logic for thermal power plants.

[0017] Fourthly, a computer-readable storage medium is provided, which stores a computer program that, when executed by a processor, implements the steps of the above-described method for generating control logic for thermal power plants.

[0018] In the above-described scheme implemented by the method, device, equipment, and medium for generating control logic for thermal power plants, the source data file of the target thermal power plant is obtained; a target functional specification is generated based on the source data file and a preset functional specification template library; a target structured database file and card layout diagram that can be imported into the DCS system are generated based on the target functional specification and preset allocation rules; a target logic description file in a unified format is generated based on the target functional specification and the target structured database file; textual logical relationships are converted into visual target logic diagrams based on the target logic description file and preset mapping relationships; and interactive target process screens are generated based on the target logic description file and preset process screen templates. The technical solution of this invention, on the one hand, relies on the automatic matching and filling of source data and functional specification template library, which greatly reduces the repetitive work of traditional manual specification writing, and the combination of interface editing function ensures the accuracy and adaptability of the specification; on the other hand, it automatically generates structured database files and card layout diagrams through preset allocation rules, which not only avoids allocation conflicts and signal association errors when manually configuring card positions, channels and terminals, but also ensures the consistency between hardware configuration data and visual installation drawings, providing a reliable basis for on-site construction and system configuration; at the same time, it generates a unified format XML logic description file based on functional specifications and structured database files, realizing the structured association between control requirements and hardware configuration, and then automatically converts it into a visual logic diagram that conforms to industrial standards and an interactive process screen through preset mapping relationships and process screen templates, which not only completely solves the problems of logical disconnection and component binding deviation when drawing graphics manually in the traditional way, but also ensures the consistency of data throughout the entire chain of control logic, hardware configuration, graphical presentation and operation interface; in addition, the fully automated generation mode greatly shortens the DCS configuration cycle, reduces the human error rate, and the standardized templates and unified data format improve the efficiency of different projects and different DCS systems. The manufacturer's adaptability and solution reusability reduce the chain adjustment costs during later modifications and maintenance, ultimately significantly improving the efficiency, accuracy, and reliability of the control logic configuration of thermal power plants, and providing strong technical support for the safe and stable operation of power plants. Attached Figure Description

[0019] To more clearly illustrate the technical solutions of the embodiments of this application, the drawings used in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0020] Figure 1 shows a schematic flowchart of a method for generating control logic for a thermal power plant according to an embodiment of this application.

[0021] Figure 2 shows a schematic flowchart of step S101 in a thermal power plant control logic generation method according to an embodiment of this application.

[0022] Figure 3 shows a schematic flowchart of step S103 in a thermal power plant control logic generation method according to an embodiment of this application.

[0023] Figure 4 shows a block diagram of a power plant control logic generation apparatus according to an embodiment of this application.

[0024] Figure 5 shows a block diagram of a computer device according to an embodiment of this application. Detailed Implementation

[0025] To better understand the technical solution of this application, the embodiments of this application will be described in detail below with reference to the accompanying drawings.

[0026] It should be understood that the described embodiments are merely some, not all, of the embodiments in this application. All other embodiments obtained by those skilled in the art based on the embodiments in this application without inventive effort are within the scope of protection of this application.

[0027] The terminology used in the embodiments of this application is for the purpose of describing particular embodiments only and is not intended to be limiting of this application. The singular forms “a,” “the,” and “the” used in the embodiments of this application and the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise.

[0028] The following detailed description of some embodiments of this application is provided in conjunction with the accompanying drawings. Unless otherwise specified, the following embodiments and features can be combined with each other.

[0029] Please refer to Figure 1, which shows a schematic flowchart of a thermal power plant control logic generation method according to an embodiment of this application.

[0030] As shown in Figure 1, the method for generating control logic for a thermal power plant includes: step S101, obtaining the source data file of the target thermal power plant, and generating the target functional specification based on the source data file and the preset functional specification template library; the source data file is a file containing the core basic data required for the configuration of the control logic of the target thermal power plant, and is the source input for generating all subsequent results, covering key information such as equipment, measuring points, and control targets.

[0031] The Functional Specification Template Library is a set of pre-set, standardized templates covering various control scenarios in thermal power plants (such as boiler control and turbine control). Each template contains a fixed field framework for quickly generating functional specifications.

[0032] The target function specification is a technical document generated based on source data files and template library, tailored to the specific control requirements of the target thermal power plant. It clarifies the core contents such as control objectives, process logic, and parameter configuration, and serves as the core basis for subsequent configuration processes.

[0033] This step is the initial stage of control logic generation, and its core is to achieve efficient specification generation through data-driven and template reuse. First, the data parsing module reads various structured data from the source data file to ensure data integrity. Then, based on the control scenario of the target thermal power plant (such as unit capacity and process type), a suitable standardized template is matched from the template library. A field mapping algorithm establishes a one-to-one correspondence between the source data and template fields, automatically filling the corresponding fields of the template with equipment parameters, measurement point information, and other data to generate an initial version. Finally, a target functional specification that meets project requirements is output, supporting subsequent editing and optimization, without requiring manual documentation framework writing throughout the process.

[0034] This approach completely changes the inefficient traditional method of manually writing functional manuals. By reusing templates and automatically filling them in, repetitive work is significantly reduced, and the manual compilation cycle is shortened. Standardized templates ensure the uniformity of document format and the completeness of content, avoiding problems such as parameter omissions and logical ambiguities caused by manual writing. The precise mapping between source data and templates improves the accuracy of the manuals, providing a reliable basis for requirements in subsequent database configuration, logical descriptions, and other stages, and reducing the risk of rework throughout the entire process.

[0035] Step S102: Generate a target structured database file and card layout diagram that can be imported into the DCS system according to the target function specification and preset allocation rules.

[0036] The preset allocation rules are a set of standardized rules developed based on the hardware characteristics and engineering practices of the DCS system in thermal power plants. They are used to guide card configuration and data association to ensure the stable and reliable operation of the system.

[0037] The target structured database file is a standardized data file that can be directly imported into the DCS system. It contains card configuration information and signal association data and is the core data carrier for DCS system software configuration.

[0038] The card layout diagram is a visual hardware installation drawing that intuitively shows the physical layout of the cards in the control cabinet, the correspondence between terminals and cards, etc., and is used to guide on-site construction.

[0039] This step is crucial in connecting control requirements with hardware configuration, automating the transformation from requirements to hardware configuration. First, it analyzes the control requirements, signal types, and device interface requirements in the target functional specification. Based on preset allocation rules (such as card load balancing, signal type matching, and redundancy safety configuration), it automatically assigns corresponding card locations, types, channels, and terminals to each signal and configures spare channels. Simultaneously, it generates two core outputs: a structured database file (e.g., CSV format) containing card configuration information and signal association data, and a visual card layout diagram generated based on card location parameters. During the generation process, it is essential to ensure data consistency between the database file and the card layout diagram to avoid discrepancies between hardware configuration and drawings.

[0040] This avoids issues such as allocation conflicts and signal association errors when manually configuring cards, improving the accuracy of hardware configuration; the structured database file can be directly imported into the DCS system, eliminating the tedious operation of manually creating the database and shortening the configuration cycle; the card layout diagram provides intuitive guidance for on-site installation and wiring, reducing construction difficulty and wiring error rate; the preset allocation rules ensure card load balancing and system redundancy safety, improving the reliability of DCS system operation, while the standardized configuration process improves the adaptability to different projects.

[0041] Step S103: Generate a target logic description file in a unified format based on the target function specification and the target structured database file. The target logic description file is a file that uses a unified format (such as XML) to structurally describe the control logic of a thermal power plant. It is the core intermediate carrier connecting requirements, hardware and graphical results, and contains key information such as logic operations, signal transmission and timing control.

[0042] In this step, the control objectives, process logic relationships, equipment interaction rules, and constraints are first extracted from the target functional specification. Simultaneously, card configuration information and signal association data are read from the target structured database file. Based on the signal association data, a mapping relationship between control logic and hardware is established, breaking down the control objectives into logical operation content, signal input / output content, and timing control content. A pre-defined XML tag system is used to structure and describe each decomposed content, clarifying the operation type, signal binding relationship, and action execution order. Finally, all tagged descriptions are combined according to a pre-defined hierarchical structure to form a target logic description file in a unified format, ensuring that the file is consistent with control requirements and hardware configuration.

[0043] By using a standardized XML tag system, a clear and accurate description of complex control logic is achieved, improving the readability and maintainability of the logic. A direct link between control requirements and hardware configuration is established, ensuring the executableness of the logic description and avoiding the traditional problem of logic being disconnected from hardware. The unified file format provides standardized input for the automatic generation of subsequent logic diagrams and process screens, ensuring the consistency of data throughout the process, while also facilitating the modification and reuse of logic and reducing later maintenance costs.

[0044] Step S104: Based on the target logic description file and the preset mapping relationship, the textual logic relationship is transformed into a visual target logic diagram.

[0045] Preset mapping relationships are a set of rules that define the correspondence between textual logic in a logic description file and visual graphic elements, including the correspondence rules between logical relationships and graphic components, node layouts, and connection relationships.

[0046] The target logic diagram is a visual technical drawing generated based on the logic description file. It intuitively displays information such as the control function architecture, signal flow, and parameter configuration, and serves as the core basis for the logic debugging and maintenance of the DCS system.

[0047] In this step, the tagged data in the target logic description file is first parsed to identify core information such as logic operation types, signal input / output nodes, and timing relationships. Based on preset mapping relationships, textual logic operations (such as AND / OR / NOT, PID control) are converted into corresponding industry standard graphic elements (such as function blocks), signal transmission relationships are converted into graphic connections, and node information is converted into parameter labels. The graphic elements are automatically arranged according to node layout rules to ensure the clarity and readability of the logic diagram. Finally, a target logic diagram containing control function architecture, signal flow, and parameter configuration information is generated, conforming to power engineering drawing standards such as DL / T 5028.3-2015.

[0048] Automatically generated logic diagrams avoid the tedious operations and human errors (such as incorrect connections or missing nodes) of traditional manual drawing, greatly improving drawing efficiency; the logic diagram is directly associated with the logic description file, ensuring consistency between the diagram and the underlying logic and avoiding discrepancies between the diagram and reality; standardized graphic elements and layout rules improve the universality and readability of the logic diagram, making it easier for engineers to debug, maintain, and transfer technology, while providing an intuitive basis for subsequent system verification.

[0049] Step S105: Generate an interactive target process screen based on the target logic description file and the preset process screen template.

[0050] The process screen templates are a set of preset visualization interface templates suitable for different monitoring scenarios in thermal power plants. They include fixed interface styles, layout specifications and visualization components to ensure the uniformity and universality of the screens.

[0051] The target process screen is a human-computer interaction interface generated based on logic description files and templates. It has functions such as data display and operation control, and is the core entry point for operators' daily monitoring and operation.

[0052] In this step, the functional nodes, signal relationships, and control objectives in the target logic description file are first analyzed to clarify the data to be displayed and the operable functions. A suitable template (such as an APS system template or equipment monitoring template) is matched from a pre-set process screen template library. The functional nodes in the logic description file are automatically bound to the visual components (such as buttons, dashboards, indicator lights, and trend charts) in the templates to ensure that the data displayed by the components is consistent with the logical operation results, and that commands to operate the components can trigger the corresponding logical execution. Finally, a target process screen with interactive capabilities such as real-time data display, parameter adjustment, and equipment start / stop is generated, with a unified interface style and clear operation logic.

[0053] The automatic generation of process screens eliminates a significant amount of work involved in traditional manual interface design and data binding, shortening the human-machine interface development cycle. The screens are directly linked to the logic description files, ensuring that the data displayed accurately reflects the logical operation results, and that operation commands can precisely trigger logical execution, avoiding the disconnect between operation and logic. Standardized templates ensure consistency in screen style and operating habits across different scenarios, reducing the learning cost for operators. Interactive screens provide an intuitive and convenient entry point for daily production monitoring and operation in thermal power plants, improving operational efficiency and accuracy, and ensuring the stable operation of the production process.

[0054] In one embodiment, optionally, the method further includes: editing the target function specification according to the received specification editing instructions.

[0055] Manual editing commands are instructions initiated by users through a graphical interface tool to modify, supplement, or delete the manual for a target function, including parameter adjustment, logic description optimization, and constraint supplementation.

[0056] This embodiment provides a channel for manual intervention and optimization in the functional specification generation process. After the target functional specification is automatically generated, users can view the specification content through the system's provided graphical editing tools (such as online editors or local client editors). When inaccurate parameters, incomplete logical descriptions, or the need to adjust constraints according to the actual scenario are found, users can initiate editing commands to modify, supplement, or delete the corresponding content in the specification. The editing operation is synchronized to the system in real time, and after the modification is completed, it is saved to generate an updated target functional specification, which will serve as the input basis for subsequent stages. In this way, the lack of flexibility of the purely automatic generation mode is compensated for, allowing users to make personalized adjustments according to the specific needs of the project, improving the adaptability of the functional specification; the graphical editing tools lower the operation threshold, and users do not need to have professional programming skills to complete the modification; the modified specification is synchronized to subsequent stages in real time, ensuring the consistency of data throughout the process, avoiding rework caused by specification modifications, and retaining modification traces for easy traceability and version management.

[0057] The target logical description file is edited according to the received file editing instructions.

[0058] File editing commands are user-initiated modification commands for a target logic description file, including adjusting logic operation types, modifying signal binding relationships, and optimizing timing control order, used to precisely optimize the automatically generated logic description.

[0059] This embodiment provides precise adjustment capabilities for the logic description stage. After automatically generating the target logic description file, users can view the tagged content of the file using the system-supported XML editor or a dedicated logic editing tool. When it is necessary to optimize the logic operation type, adjust the binding relationship between signals and cards, or modify the execution order of actions, users can initiate file editing commands to modify the corresponding XML tags or fields. During the editing process, the system has a built-in syntax verification mechanism that automatically verifies the tag format and logical relevance to avoid syntax errors caused by editing. After editing, the updated target logic description file is saved for subsequent generation of logic diagrams and process screens.

[0060] This allows users to precisely optimize logic description files based on actual control needs and hardware configuration details, improving the accuracy and adaptability of the logic description; the syntax verification mechanism avoids syntax errors and logical conflicts caused by editing operations, ensuring the usability of the files; the edited files are directly used in the subsequent graphical generation process, ensuring that the logic diagrams and process screens are consistent with the optimized logic description, while supporting version recording, facilitating modification traceability and rollback, and improving the flexibility and reliability of the system.

[0061] In one embodiment, optionally, the source data file includes equipment parameters, measurement point information, control target parameters, and process logic constraints of the target thermal power plant, wherein the equipment parameters include equipment model, rated operating parameters, and interface type, the measurement point information includes measurement point number, signal type, measurement range, and alarm threshold, and the format of the source data file includes a standardized table format.

[0062] Equipment parameters are data that describe the basic characteristics and operating requirements of various equipment in a thermal power plant. They are the basis for equipment control and include equipment model (distinguishing equipment specifications), rated operating parameters (such as rated temperature and pressure), and interface type (connection method with DCS system).

[0063] Measurement point information refers to the data related to physical quantities that need to be monitored during the production process of thermal power plants, including measurement point number (unique identifier), signal type (such as analog quantity, digital quantity), measurement range (upper and lower limits of measurement), and alarm threshold (over-range alarm standard).

[0064] Control target parameters are the target data that need to be achieved in the control process of thermal power plants, such as target temperature, pressure, and flow rate.

[0065] Process logic constraints are the process rules and limitations that must be followed during production, such as operation sequence constraints and parameter linkage constraints.

[0066] Standardized table formats are those that conform to industrial data exchange standards (such as Excel and CSV), facilitating data reading, parsing, and sharing.

[0067] In this embodiment, the explicit data source content ensures the integrity of input for all subsequent configuration steps, avoiding incomplete functionality or logical errors due to missing data; the standardized table format improves data compatibility and parsability, reduces the complexity of system data processing, and improves data processing efficiency; the structured data storage facilitates data modification, supplementation, and reuse, while also providing convenience for data sharing between different projects, enhancing the flexibility and adaptability of configuration.

[0068] As shown in Figure 2, in one embodiment, optionally, step S101 includes: step S201, reading the equipment parameters, measurement point information, control target parameters, and process logic constraints from the source data file, and performing classification extraction and structured organization according to data type; classification extraction involves extracting different types of data (equipment parameters, measurement point information, etc.) from the source data file to form independent data subsets. Structured organization involves organizing the extracted data according to preset formats and rules to give it a unified structure, facilitating matching with template fields.

[0069] This step is the preliminary data processing stage for generating the functional specification. First, the data parsing module reads all data from the source data file, identifying four main categories: equipment parameters, measurement point information, control target parameters, and process logic constraints. Then, these are separated into independent data subsets according to data type to avoid confusion between different data types. Finally, each data subset is structured, such as sorting equipment parameters by equipment type and associating signal types and measurement ranges by measurement point number, ensuring consistent data format and clear associations, laying the foundation for subsequent matching with template fields.

[0070] Categorization and structured organization ensure the orderliness and standardization of source data, avoiding matching errors caused by data disorder; data with a unified structure facilitates automatic system identification and field mapping, improving the accuracy and efficiency of data filling; the structured data source can be reused for matching different templates, improving data reusability and providing convenience for subsequent data verification.

[0071] Step S202: A target template matching the control scenario of the target thermal power plant is searched from a preset functional specification template library. The target template includes a functional overview, parameter configuration, logical relationships, and a fixed field framework of constraints. Control scenario matching involves selecting the most suitable functional specification template from the template library based on factors such as the unit type, capacity, and process characteristics of the target thermal power plant. The fixed field framework consists of preset, unmodifiable core content modules within the template, ensuring the basic structural integrity and format consistency of the functional specification.

[0072] The system first acquires the control scenario information of the target thermal power plant (such as unit capacity, process type, and controlled objects). Then, based on this scenario information, it traverses the functional manual template library, filtering for suitable target templates through keyword matching and scenario feature comparison. Each target template contains four fixed field frameworks: functional overview (core control objectives of the project), parameter configuration (equipment, measuring points, control target parameters), logical relationships (process control logic), and constraints (process limitations), ensuring the completeness of the manual's structure. This scenario-based template matching avoids the problem of insufficient adaptability caused by blindly selecting templates, ensuring that the generated manual meets the specific control requirements of the target thermal power plant. The fixed field framework guarantees the structural uniformity and content completeness of the functional manual, avoiding missing frameworks or formatting issues caused by manual writing. Template reuse significantly reduces the workload of manual preparation and improves configuration efficiency.

[0073] Step S203: Establish the correspondence between the source data in the source data file and the fields of the target template through a field mapping algorithm, automatically fill the sorted source data into the target fields corresponding to the target template, and generate the target function specification.

[0074] Field mapping algorithms are used to establish the correspondence between source data and template fields, and support automatic matching by field name, data type, semantic association, etc.

[0075] The target field is a pre-defined field in the target template used to populate specific data, and it corresponds one-to-one with the type of the source data.

[0076] First, the field mapping algorithm is activated to analyze the field names, data types, and semantics of the source data (e.g., "Equipment Model" corresponds to the "Equipment Specification" field in the template), establishing a one-to-one correspondence between the source data and the target template fields. Then, the structured source data is processed in batches, automatically filling each data item into the target field corresponding to the template, such as filling equipment parameters into the parameter configuration field and process logic constraints into the constraint condition field. After filling, the system automatically verifies the data integrity and format correctness, generating an initial version of the target function specification, supporting subsequent editing and optimization.

[0077] The field mapping algorithm achieves accurate and automatic matching between source data and template fields, avoiding field correspondence errors caused by manual filling and improving the accuracy of data filling; batch automatic filling greatly reduces repetitive work and shortens the manual generation cycle; data integrity and format verification ensure the usability of the manual and provide a reliable input basis for subsequent steps, while the algorithm's flexibility supports the adaptation of different data formats and templates, improving the system's versatility.

[0078] In one embodiment, optionally, the target structured database file includes card configuration information and signal association data, wherein the card configuration information includes card location, type, channel and terminal allocation results, and the signal association data includes the mapping relationship between measurement point signals and card channels and control logic elements.

[0079] Signal association data is a set of data that establishes the correspondence between measurement point signals, card channels, and control logic elements. It is the core association basis for ensuring that the control logic can be executed normally by the hardware. Control logic elements are the indivisible basic units in the control logic, such as logic operation nodes and signal input / output nodes.

[0080] In this step, the target structured database file contains two types of core data: first, card configuration information, which records in detail the physical installation location (rack number, slot number), function type (AI / AO / DI / DO, etc.), available channel number, and terminal allocation results of each card, as well as the configuration of spare channels; second, signal association data, which clarifies the card channel and terminal corresponding to each measurement point signal, as well as the mapping relationship between the signal and the control logic element, ensuring that the input signals required for logic operations can be collected from the designated card channels, and the operation results can be output to the field equipment through the designated channels; the file adopts a format that can be directly imported into DCS systems such as CSV, and the data is stored in a structured manner by field, which facilitates the system to read and parse it quickly.

[0081] Clearly defined document content ensures the integrity of DCS system configuration; card configuration information provides a direct basis for hardware installation and software configuration; signal correlation data establishes a closed-loop correlation between measurement points, hardware, and logic, avoiding control failures caused by missing correlations; structured format supports direct import of files into the DCS system, eliminating the tedious operation of manually configuring the database, shortening the configuration cycle, reducing the error rate of manual configuration, and improving the reliability of system operation.

[0082] As shown in Figure 3, in one embodiment, optionally, step S103 includes: step S301, extracting the control target, process logic relationship, equipment interaction rules and constraints from the target function specification, and reading the card configuration information and signal association data from the target structured database file.

[0083] Equipment interaction rules are the rules governing the collaborative work between different pieces of equipment in a thermal power plant, such as equipment start-up and shutdown sequences and parameter linkage control rules.

[0084] First, the core requirements information in the target functional specification is extracted through the text parsing module, including control objectives (such as maintaining the boiler water level within a set range), process logic relationships (such as AND / OR / NOT logic, PID control logic), equipment interaction rules (such as the linkage rules between the feedwater pump and the boiler water level), and constraints (such as equipment start-up and shutdown temperature limits). Simultaneously, the card configuration information (card location, type, channel, terminal) and signal association data (mapping relationship between measurement points, channels, and logic) from the target structured database file are read through the data reading module. These two types of data are then stored together to ensure that each control requirement corresponds to a specific hardware configuration, providing complete data support for subsequent logic decomposition and description.

[0085] Comprehensive extraction of requirements and hardware data ensures the integrity and executability of the logical description, avoiding logical loopholes caused by missing data; the associated storage of requirements data and hardware data lays the foundation for the subsequent binding of logic and hardware, ensuring that the generated logical description can be executed by the specified hardware; structured data extraction and storage improve the efficiency and accuracy of subsequent logic decomposition.

[0086] Step S302: Based on the signal association data, the control target is decomposed into logical operation content, signal input and output content, and timing control content.

[0087] Logical operations are the computational logic required to achieve control objectives, such as AND / OR / NOT logic, comparison logic, PID control operations, etc.

[0088] The signal input and output content consists of the input signals that need to be collected and the control signals that need to be output during the control process, and is directly related to the card channel.

[0089] Timing control refers to the execution order and time interval of control actions, such as starting the equipment first and opening the valve after a 5-second delay.

[0090] Based on signal correlation data, the measurement point signals and card channels involved in the control target are clearly identified. Then, the control target is functionally broken down into three specific categories: first, logical operation content, which clarifies the operation types and parameters required to achieve the target; second, signal input and output content, which determines the card channels corresponding to the input signals to be collected (such as water level sensor signals) and the channels corresponding to the control signals to be output (such as valve control signals); and third, timing control content, which clarifies the execution order and time requirements of each action. During the decomposition process, it is ensured that each category corresponds to the signal correlation data and control requirements to avoid the decomposition content being out of touch with actual needs.

[0091] Refined decomposition transforms abstract control objectives into concrete, describable content, providing a clear foundation for subsequent structured descriptions. The decomposed content is directly linked to signal-related data, ensuring that the logical description can be applied to specific hardware. Categorized decomposition improves the logical description's coherence and readability, facilitating subsequent modification and maintenance.

[0092] Step S303: A pre-defined XML tag system is used to structurally describe each disassembled content. The logical operation content defines the operation type through logical operation tags, the signal input and output content binds the corresponding card channel and measurement point signal through device association tags and signal transmission tags, and the timing control content clarifies the action execution order through control timing tags.

[0093] The XML tag system is a pre-defined, standardized collection of XML tags used to describe different types of logical content. Each tag corresponds to a specific logical meaning and data format.

[0094] Logical operation tags are XML tags used to define logical operation types, such as... <and>AND operation, <pid>This indicates PID control operations, etc.

[0095] Device association tags are XML tags used to bind signals to devices and card channels, clearly defining the source and destination of the signal.

[0096] Signal transmission tags are XML tags used to describe signal transmission paths and methods.

[0097] Timing control tags are XML tags used to define the execution order and time intervals of actions, such as... <sequence>Indicates the execution order, <delay>Indicates delay time, etc.

[0098] The three categories of content are described using corresponding XML tags: For logical operations, the operation type is defined using logical operation tags, and the operation parameters are configured within the tags; for signal input / output, the device association tag binds the corresponding device and card channel to the signal, and the signal transmission tag describes the signal transmission path; for timing control, the timing control tag specifies the execution order and delay time of the actions. The use of all tags strictly follows the preset syntax rules to ensure the standardization and parsability of the tagged description.

[0099] The standardized XML tag system ensures the uniformity and standardization of logical descriptions, facilitating automatic system parsing and subsequent graphical generation; tag-based descriptions make logical content clear and accurate, avoiding ambiguity and improving the readability and maintainability of the logic; the categorization and use of different types of tags makes the logical structure hierarchical, facilitating the quick location and modification of specific logical content, while the binding of tags to hardware configurations ensures the executability of the logic.

[0100] Step S304: Combine the tagged descriptions of each decomposed content according to a preset hierarchical structure to form a target logic description file with a unified format.

[0101] The default hierarchical structure is the way tags are organized in an XML file. It is arranged in a hierarchy of control target - logical type - specific content to ensure that the file structure is clear and easy to parse.

[0102] First, follow the preset hierarchical structure (such as the root tag). <controllogic>The following includes <logicoperation>(Logical operations) <signalio>(Signal input and output) <timecontrol>(Timing control) has three sub-tag levels, which classify and integrate the tagged descriptions of each decomposed content; then ensure that the nesting relationship between the tags at each level is correct and the data association is consistent, such as signal input and output tags need to be associated with logic operation tags, and timing control tags need to contain corresponding action tags; finally, generate a complete XML format file, with the file header containing information such as namespace and version number, to ensure that the file meets the unified format requirements and can be directly parsed by subsequent modules.

[0103] The pre-defined hierarchical structure ensures that the target logic description file is clear and well-organized, facilitating automatic system parsing and manual review; the integration of tagged descriptions enables scattered logical content to form a complete logical system, ensuring logical coherence and integrity; the unified file format improves the system's compatibility and scalability, supports file sharing and reuse between different modules and projects, and provides standardized input for the automatic generation of subsequent logic diagrams and process screens, ensuring the consistency of data throughout the entire process.

[0104] In one embodiment, optionally, the preset mapping relationship includes the correspondence rules between logical relationships and graphical elements, node layout rules, and connection association rules, and the target logic diagram includes control function architecture, signal flow direction, and parameter configuration information.

[0105] The correspondence rules between logical relationships and graphical elements define the industry-standard graphical elements (such as function block shapes and colors) corresponding to different logical operations (such as AND / OR / NOT, PID control).

[0106] Node layout rules define the arrangement and positional relationships of graphical nodes (such as function blocks and signal nodes) in a logic diagram to ensure that the diagram is clear and does not overlap.

[0107] Connection rules define the style, color, arrow markings, etc. of the connection lines in a logic diagram, and clarify the direction of signal transmission.

[0108] The control function architecture is the overall structure of the control functions shown in the logic diagram, such as the hierarchical relationship between the main control loop and the auxiliary control loop.

[0109] The preset mapping relationship includes three core rules: First, the correspondence between logical relationships and graphical elements, such as assigning rectangular function blocks to AND operations and circular function blocks to PID regulation, ensuring that the graphical elements conform to industry standards; second, node layout rules, such as arranging nodes from left to right according to the control flow and grouping similar functional nodes together to avoid node overlap and line crossing; and third, connection association rules, such as using blue solid lines for input signals and red solid lines for output signals, with arrows indicating the direction of signal flow. The target logic diagram generated based on these rules must clearly show the control function architecture (hierarchical relationship), signal flow (connections and arrows), and parameter configuration information (parameter labels on function blocks), ensuring that engineers can quickly understand the control logic.

[0110] Standardized mapping rules ensure that the logic diagrams generated in different projects and control scenarios have a consistent style and conform to industry standards, improving the universality and readability of the logic diagrams; clear control function architecture, signal flow and parameter configuration information facilitate logic debugging, maintenance and technical handover for engineers, reducing communication costs; regularized graph generation avoids problems such as layout chaos and wiring errors caused by manual drawing, improving the accuracy and generation efficiency of logic diagrams.

[0111] The preset process screen templates include APS system templates, equipment monitoring templates, and trend analysis templates. Each template has built-in visualization components, which include at least one of the following: buttons, dashboards, indicator lights, line charts, and pie charts.

[0112] The APS system template is a process screen template suitable for the Automatic Generation Control (APS) scenario in thermal power plants, which includes visualization components related to unit start-up and shutdown control, load regulation, etc.

[0113] The equipment monitoring template is a process screen template suitable for real-time monitoring scenarios of single or multiple devices, including components such as device operating status and key parameter display.

[0114] The trend analysis template is a process screen template suitable for historical data trend analysis scenarios, which includes trend display components such as line charts and bar charts.

[0115] Visualization components are graphic elements in the process screen used to display data or perform operational functions, such as buttons to trigger operations, dashboards to display real-time parameters, and indicator lights to display equipment status.

[0116] The preset process screen templates cover three core scenarios: the APS system template for overall unit control scenarios, the equipment monitoring template for single or multiple device local monitoring scenarios, and the trend analysis template for data trend viewing scenarios. Each template has built-in corresponding visualization components. For example, the APS system template includes start / stop buttons and load adjustment sliders, the equipment monitoring template includes indicator lights and dashboards, and the trend analysis template includes line charts and pie charts. The style, size, and position of the components are preset in the templates to ensure a consistent interface style, while also supporting adjustments to the component layout according to actual needs.

[0117] Diverse template types meet the needs of different monitoring scenarios in thermal power plants, improving the adaptability of process screens; built-in standardized visualization components ensure the uniformity of interface style and ease of operation, reducing the learning cost for operators; template-based screen generation avoids the tedious work of manually designing interfaces, shortens the screen development cycle, and the automatic binding of components and logic description files ensures the accuracy of screen functions, improving operational efficiency and the stability of the production process.

[0118] Figure 4 shows a block diagram of a power plant control logic generation apparatus according to an embodiment of this application.

[0119] As shown in Figure 4, in a second aspect, this application provides a thermal power plant control logic generation device 40, comprising: an acquisition module 41, used to acquire source data files of a target thermal power plant and generate a target functional specification based on the source data files and a preset functional specification template library; a first generation module 42, used to generate a target structured database file and card layout diagram that can be imported by a DCS system based on the target functional specification and preset allocation rules; a second generation module 43, used to generate a target logic description file in a unified format based on the target functional specification and the target structured database file; a conversion module 44, used to convert textual logic relationships into visual target logic diagrams based on the target logic description file and preset mapping relationships; and a third generation module 45, used to generate a target process screen with interactive capabilities based on the target logic description file and a preset process screen template.

[0120] In one embodiment, optionally, the apparatus further includes: a first editing module, configured to edit the target function specification according to received specification editing instructions; and a second editing module, configured to edit the target logic description file according to received file editing instructions.

[0121] In one embodiment, optionally, the source data file includes equipment parameters, measurement point information, control target parameters, and process logic constraints of the target thermal power plant, wherein the equipment parameters include equipment model, rated operating parameters, and interface type, the measurement point information includes measurement point number, signal type, measurement range, and alarm threshold, and the format of the source data file includes a standardized table format.

[0122] In one embodiment, optionally, the acquisition module includes: a reading unit, used to read equipment parameters, measurement point information, control target parameters, and process logic constraints from the source data file, and to extract and structure them according to data type; a search unit, used to search for a target template matching the target thermal power plant control scenario from a preset functional specification template library, wherein the target template includes a fixed field framework of functional overview, parameter configuration, logical relationship, and constraint conditions; and a filling unit, used to establish the correspondence between the source data in the source data file and the fields of the target template through a field mapping algorithm, and to automatically fill the sorted source data into the target fields corresponding to the target template to generate a target functional specification.

[0123] In one embodiment, optionally, the target structured database file includes card configuration information and signal association data, wherein the card configuration information includes card location, type, channel and terminal allocation results, and the signal association data includes the mapping relationship between measurement point signals and card channels and control logic elements.

[0124] In one embodiment, optionally, the second generation module includes: an extraction unit, used to extract the control target, process logic relationship, equipment interaction rules and constraints from the target function specification, and read the card configuration information and signal association data from the target structured database file; a disassembly unit, used to disassemble the control target into logical operation content, signal input and output content and timing control content according to the signal association data; a description unit, used to perform a structured description of each disassembled content using a preset XML tag system, wherein the logical operation content defines the operation type through logical operation tags, the signal input and output content binds the corresponding card channel and measurement point signal through equipment association tags and signal transmission tags, and the timing control content clarifies the action execution order through control timing tags; and a combination unit, used to combine the tagged descriptions of each disassembled content according to a preset hierarchical structure to form a target logic description file in a unified format.

[0125] In one embodiment, optionally, the preset mapping relationship includes the correspondence rules between logical relationships and graphical elements, node layout rules, and connection association rules; the target logic diagram includes the control function architecture, signal flow direction, and parameter configuration information; the preset process screen template includes the APS system template, the equipment monitoring template, and the trend analysis template, each template having built-in visualization components, the visualization components including at least one of the following: buttons, dashboards, indicator lights, line charts, and pie charts.

[0126] Thirdly, a computer device is provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the steps of the above-described method for generating control logic for thermal power plants.

[0127] Fourthly, a computer-readable storage medium is provided, which stores a computer program that, when executed by a processor, implements the steps of the above-described method for generating control logic for thermal power plants.

[0128] It should be noted that those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the thermal power plant control logic generation device and its modules described above can be referred to the corresponding processes in the aforementioned thermal power plant control logic generation method embodiments, and will not be repeated here.

[0129] It should be noted that those skilled in the art will understand that, for the sake of convenience and brevity, the specific working process of the model training device and each module described above can be referred to the corresponding process in the aforementioned embodiment of the thermal power plant control logic generation method, and will not be repeated here.

[0130] The aforementioned thermal power plant control logic generation device can be implemented as a computer program, which can run on the computer device shown in Figure 5.

[0131] Figure 5 shows a block diagram of a computer device according to an embodiment of this application.

[0132] Referring to Figure 5, the computer device includes a processor, memory, and network interface connected via a system bus, wherein the memory may include storage media and internal memory.

[0133] The storage medium may store an operating system and a computer program. The computer program includes program instructions that, when executed, cause the processor to perform any of the multi-source data power plant control logic generation methods provided in the embodiments of this application.

[0134] The processor provides computing and control capabilities, supporting the operation of the entire computer device.

[0135] The internal memory provides an environment for the execution of a computer program stored in the storage medium. When executed by a processor, this computer program enables the processor to perform any method for generating control logic for a thermal power plant based on multi-source data. The storage medium can be non-volatile or volatile.

[0136] This network interface is used for network communication, such as sending assigned tasks. Those skilled in the art will understand that the structure shown in Figure 5 is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than shown in the figure, or combine certain components, or have different component arrangements.

[0137] It should be understood that the processor can be a Central Processing Unit (CPU), but it can also be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. Among these, a general-purpose processor can be a microprocessor or any conventional processor.

[0138] In addition, embodiments of this application provide a computer-readable storage medium storing computer-executable instructions for performing the steps of the method in the first aspect embodiment.

[0139] It should be noted that the functions or steps that can be implemented by the computer-readable storage medium or electronic device described above can be referred to the relevant descriptions in the foregoing method embodiments. To avoid repetition, they will not be described one by one here.

[0140] It should be understood that the term "and / or" used in this article is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. Additionally, the character " / " in this article generally indicates that the preceding and following related objects have an "or" relationship.

[0141] It should be understood that although the terms "first," "second," etc., may be used to describe the setting units in the embodiments of this application, these setting units should not be limited to these terms. These terms are only used to distinguish the setting units from each other. For example, without departing from the scope of the embodiments of this application, the first setting unit may also be referred to as the second setting unit, and similarly, the second setting unit may also be referred to as the first setting unit.

[0142] Depending on the context, the word "if" as used here can be interpreted as "when" or "when" or "in response to determination" or "in response to detection." Similarly, depending on the context, the phrase "if determination" or "if detection (of the stated condition or event)" can be interpreted as "when determination" or "in response to determination" or "when detection (of the stated condition or event)" or "in response to detection (of the stated condition or event)."

[0143] 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; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0144] 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 in a combination of hardware and software functional units.

[0145] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium. When executed, the computer program can include the processes of the embodiments of the above methods. Any references to memory, storage, databases, or other media used in the embodiments provided in this application can include non-volatile and / or volatile memory. Non-volatile memory may include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory. Volatile memory may include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), dual data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), RAMbus direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM), etc.

[0146] The above-described embodiments are only used to illustrate the technical solutions of the present invention, and are not intended to limit it. Although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention, and should all be included within the protection scope of the present invention.< / timecontrol> < / signalio> < / logicoperation> < / controllogic> < / delay> < / sequence> < / pid> < / and>

Claims

1. A method for generating control logic for a thermal power plant, characterized in that, The method includes: acquiring source data files of the target thermal power plant; generating a target functional specification based on the source data files and a preset functional specification template library; generating a target structured database file and card layout diagram that can be imported into the DCS system based on the target functional specification and preset allocation rules; generating a target logic description file in a unified format based on the target functional specification and the target structured database file; converting textual logical relationships into a visual target logic diagram based on the target logic description file and preset mapping relationships; and generating a target process screen with interactive capabilities based on the target logic description file and preset process screen templates.

2. The method according to claim 1, characterized in that, The method further includes: editing the target function specification according to the received specification editing instructions; and editing the target logic description file according to the received file editing instructions.

3. The method according to claim 1, characterized in that, The source data file includes the equipment parameters, measurement point information, control target parameters, and process logic constraints of the target thermal power plant. The equipment parameters include the equipment model, rated operating parameters, and interface type. The measurement point information includes the measurement point number, signal type, measurement range, and alarm threshold. The format of the source data file includes a standardized table format.

4. The method according to claim 3, characterized in that, The step of generating a target functional specification based on the source data file and a preset functional specification template library includes: reading equipment parameters, measurement point information, control target parameters, and process logic constraints from the source data file, and classifying and extracting them according to data type and organizing them in a structured manner; searching for a target template matching the target thermal power plant control scenario from the preset functional specification template library, wherein the target template includes a fixed field framework of functional overview, parameter configuration, logical relationship, and constraint conditions; establishing the correspondence between the source data in the source data file and the fields of the target template through a field mapping algorithm, automatically filling the organized source data into the target fields corresponding to the target template, and generating the target functional specification.

5. The method according to claim 1, characterized in that, The target structured database file includes card configuration information and signal association data. The card configuration information includes card location, type, channel and terminal allocation results. The signal association data includes the mapping relationship between measurement point signals and card channels and control logic elements.

6. The method according to claim 5, characterized in that, Generate a unified-format target logic description file based on the target function specification and the target structured database file, including: extracting control objectives, process logic relationships, equipment interaction rules, and constraints from the target function specification, and reading card configuration information and signal association data from the target structured database file; decomposing the control objectives into logical operation content, signal input / output content, and timing control content based on the signal association data; using a preset XML tag system to structurally describe each decomposed content, wherein logical operation content defines the operation type through logical operation tags, signal input / output content binds the corresponding card channels and measurement point signals through equipment association tags and signal transmission tags, and timing control content clarifies the action execution order through control timing tags; and combining the tagged descriptions of each decomposed content according to a preset hierarchical structure to form a unified-format target logic description file.

7. The method according to any one of claims 1 to 6, characterized in that, The preset mapping relationship includes the correspondence rules between logical relationships and graphical elements, node layout rules, and connection rules. The target logic diagram includes the control function architecture, signal flow direction, and parameter configuration information. The preset process screen templates include the APS system template, the equipment monitoring template, and the trend analysis template. Each template has built-in visualization components, and the visualization components include at least one of the following: buttons, dashboards, indicator lights, line charts, and pie charts.

8. A control logic generation device for a thermal power plant, characterized in that, include: The acquisition module is used to acquire the source data file of the target thermal power plant and generate the target functional specification based on the source data file and the preset functional specification template library. The first generation module is used to generate a target structured database file and card layout diagram that can be imported by the DCS system according to the target function specification and preset allocation rules. The second generation module is used to generate a target logic description file in a unified format based on the target function specification and the target structured database file; The conversion module is used to convert textual logical relationships into visual target logical diagrams based on the target logical description file and preset mapping relationships; the third generation module is used to generate interactive target process screens based on the target logical description file and preset process screen templates.

9. A computer device, characterized in that, include: At least one processor; And a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, the instructions being configured to perform the method of any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that, The device stores computer-executable instructions for performing the method as described in any one of claims 1 to 7.

Images