Basic information management method and device, equipment and medium

Abstract

The embodiment of the invention discloses a basic information management method and device, equipment and a medium, and can be applied to the field of nuclear power station DCS engineering design. In response to a signal list generation operation of a target project, initial signal information of the target project can be generated, a signal identifier in the initial signal information is used for indicating a hard wiring signal in a project file, channel topology information of the target project is displayed in a channel display area of a design page, and in response to a board card channel association signal identifier, channel topology information of the target project is displayed in a channel display area of the design page. And adding associated board card channel information to the signal identifier in the initial signal information, and in response to the design completion operation, generating a basic signal list according to the initial signal information. In this way, in the design process of the basic signal list, a correlation function of visual channel topology information and visual channel information is provided for a user, the generated basic signal list comprises the channel information, ready-to-use complete data is provided for the follow-up process, an artificial transcription link is eliminated, the signal list generation efficiency is improved, and distribution errors are reduced.

Description

Technical Field

[0001] This invention relates to the field of nuclear power plant DCS (Distributed Control System) engineering design, and in particular to a basic information management method, device, equipment and medium. Background Technology

[0002] In current engineering practice, the design of basic input / output (IO) lists typically relies on manual operation: engineering designers need to export raw IO variable data from the project files of the engineering software design platform to an Excel file, then manually fill in attribute information such as descriptions, IO types, and station numbers, and finally output the corresponding basic IO list. In subsequent work, this data also needs to be copied or re-entered into a "detailed IO list," and channel information such as racks, chassis, boards, and board channels need to be manually assigned.

[0003] This results in the inability to reuse the basic I / O manifest, requiring editing in multiple files, which is inefficient and error-prone. Summary of the Invention

[0004] To address the aforementioned technical problems, embodiments of this application provide a basic information management method, apparatus, device, and medium. In the design process of the basic signal list, there is no need for a subsequent manual transcription step to allocate channel information using additional files, thereby improving the efficiency of signal list generation, simplifying the process, and reducing allocation errors.

[0005] In a first aspect, embodiments of this application provide a basic information management method, the method comprising: In response to the signal list generation operation of the target project, initial signal information of the target project is generated, wherein the signal identifiers in the initial signal information are used to indicate hard-wired signals in the target project; The channel display area on the design page displays the channel topology information of the target project, which includes station number, cabinet, chassis, board, and the relationship between board channels. In response to associating the signal identifier with the board channel, the channel information of the associated board channel is added to the initial signal information for the signal identifier; In response to the design completion operation, a basic signal list is generated based on the initial signal information.

[0006] In some possible implementations, the method further includes: In response to a trigger operation on the board, the channel identifier of the board channel is displayed on the channel allocation page of the design page; In response to adding a second identifier from the signal identifier to the signal information corresponding to the first identifier in the channel identifier, the second identifier is associated with the first identifier, as well as the board, chassis, cabinet and station number to which the second identifier belongs.

[0007] In some possible implementations, the method further includes: The initial signal information is displayed on the signal display page of the design page; In response to an editing operation on the initial signal information in the design page, the initial signal information is updated according to the editing operation.

[0008] In some possible implementations, the method further includes: Configure a field-level edit lock on the variable information in the initial signal information to prevent the variable information from being edited; the variable information includes at least the signal identifier; and / or, The design page displays multiple category labels, and the signal display page is used to display the initial signal information under the selected current label among the multiple category labels. The basic signal list includes the signal list under multiple category labels.

[0009] In some possible implementations, the generation of initial signal information for the target project in response to the signal list generation operation includes: If the list generation operation includes a selection operation for a target version of the signal list, then the initial signal information of the target project is generated based on the target version of the signal list, and the version of the basic signal list is an updated version of the target version; If the list generation operation does not include the selection operation of the signal list for the target version, then the initial signal information of the target project is generated based on the project file of the target project.

[0010] In some possible implementations, the method further includes: In response to a file-level edit lock on the initial signal information, a configuration file-level edit lock is applied to the signal manifest for the target version, preventing the signal manifest for the target version from being edited by other users; and / or, In response to the file-level editing unlock of the initial signal information, the file-level editing lock is released for the signal list of the target version; and / or, In response to the edit comparison operation, the content revision information of the initial signal information relative to the target version of the signal list is displayed.

[0011] In some possible implementations, the method further includes: In response to the design completion operation, the basic signal list is submitted to the approval system by calling the management platform interface.

[0012] Secondly, embodiments of this application provide a basic information management device, which is used to implement the methods and functions as described in the first aspect or any possible implementation of the first aspect. The device specifically includes: The first generation unit is configured to generate initial signal information of the target project in response to the signal list generation operation of the target project, wherein the signal identifier in the initial signal information is used to indicate hard-wired signals in the target project; The first display unit is used to display the channel topology information of the target project in the channel display area of ​​the design page. The channel topology information includes station number, cabinet, chassis, board, and the relationship between board channels. The association unit is configured to, in response to associating the signal identifier with the board channel, add the associated board channel information to the signal identifier in the initial signal information; The second generation unit is used to generate a basic signal list based on the initial signal information in response to the design completion operation.

[0013] Optionally, the device further includes: A trigger unit is used to respond to a trigger operation on the board and display the channel identifier of the board channel in the channel allocation page of the design page. The association unit is specifically used to respond to adding a second identifier from the signal identifier to the signal information corresponding to the first identifier in the channel identifier, associating the second identifier with the first identifier, and the board, chassis, cabinet and station number to which the second identifier belongs.

[0014] Optionally, the device further includes: The second display unit is used to display the initial signal information on the signal display page of the design page; An editing unit is configured to update the initial signal information in response to an editing operation on the design page, based on the editing operation.

[0015] Optionally, the device further includes: The field-level edit lock configuration unit is specifically used to configure a field-level edit lock for the variable information in the initial signal information, so that the variable information cannot be edited, and the variable information includes at least the signal identifier.

[0016] The category label display is used to display multiple category labels on the design page. The signal display page is used to display the initial signal information under the selected current label among the multiple category labels. The basic signal list includes the signal list under multiple category labels.

[0017] Optionally, the first generation unit is specifically used for: If the list generation operation includes a selection operation for a target version of the signal list, then the initial signal information of the target project is generated based on the target version of the signal list, and the version of the basic signal list is an updated version of the target version; if the list generation operation does not include a selection operation for a target version of the signal list, then the initial signal information of the target project is generated based on the project file of the target project.

[0018] Optionally, the device further includes: A locking unit is configured to, in response to a file-level edit lock on the initial signal information, apply a configuration file-level edit lock to the target version of the signal manifest, preventing the target version of the signal manifest from being edited by other users; and / or, The unlocking unit is configured to, in response to file-level editing unlocking of the initial signal information, release the file-level editing lock on the signal list of the target version; and / or, The comparison unit is used to display the content revision information of the initial signal information relative to the target version of the signal list in response to the edit comparison operation.

[0019] Optionally, the device further includes: The submission unit is used to submit the basic signal list to the approval system by calling the management platform interface in response to the design completion operation.

[0020] Thirdly, embodiments of this application disclose a computer device, which includes a processor and a memory: The memory is used to store program code and transmit the program code to the processor; The processor is used to execute the basic information management method as described in the first aspect according to the instructions in the program code.

[0021] Fourthly, embodiments of this application disclose a computer-readable storage medium for storing a computer program, which, when executed by a processor, performs the basic information management method as described in the first aspect.

[0022] This application provides a basic information management method, apparatus, and related equipment. In response to a signal list generation operation for a target project, initial signal information for the target project can be generated. Signal identifiers in the initial signal information indicate hard-wired signals in the project files. The channel topology information of the target project can be displayed in the channel display area of ​​the design page. Channel topology signals can include station numbers, cabinets, chassis, boards, and the relationships between board channels. In response to associating signal identifiers with board channels, the associated board channel information is added to the initial signal information. In response to a design completion operation, a basic signal list is generated based on the initial signal information. This provides users with intuitive channel topology information and a visualized channel information association function during the basic signal list design process. The generated basic signal list includes channel information, providing ready-to-use complete data for subsequent manual transcription and channel information allocation, improving signal list generation efficiency, simplifying the process, and reducing allocation errors. Attached Figure Description

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

[0024] Figure 1 A flowchart for drawing a functional diagram is provided in an embodiment of this application; Figure 2 A diagram showing the correspondence between analog I / O list information provided in this application embodiment; Figure 3 A flowchart illustrating a basic information management method provided in this application embodiment; Figure 4 This application provides an example of an operational implementation and its effect diagram. Figure 5 A schematic diagram of relevant form data provided in an embodiment of this application; Figure 6 A schematic diagram of a channel allocation page provided in an embodiment of this application; Figure 7 This application provides an embodiment of a multi-tab working representation corresponding to the initial signals of different labels. Figure 8 A database relationship diagram provided for embodiments of this application; Figure 9 A schematic diagram of a signal manifest file lock identifier provided in an embodiment of this application; Figure 10 (a), (b), and (c) are schematic diagrams corresponding to deleting data, adding data, and modifying data, respectively, provided in the embodiments of this application. Figure 11 A data flow diagram provided for an embodiment of this application; Figure 12 A schematic diagram of a task execution device provided in an embodiment of this application; Figure 13 This is a structural block diagram of a computer device for basic information management provided in an embodiment of this application. Detailed Implementation

[0025] To make the above-mentioned objectives, features and advantages of this application more apparent and understandable, the specific embodiments of this application will be described in detail below with reference to the accompanying drawings.

[0026] Many specific details are set forth in the following description in order to provide a full understanding of this application. However, this application may also be implemented in other ways different from those described herein. Those skilled in the art can make similar extensions without departing from the spirit of this application. Therefore, this application is not limited to the specific embodiments disclosed below.

[0027] In current engineering practice, the design of basic input / output lists (also known as signal lists or I / O lists) typically relies on manual operation: engineering designers need to export raw I / O variable data from the project files of the engineering software design platform to an Excel file, then manually fill in attribute information such as descriptions, I / O types, and station numbers, and finally output the corresponding basic I / O list. In subsequent work, this data also needs to be copied or re-entered into a "detailed I / O list," and channel information such as cabinets, chassis, boards, and board channels need to be manually assigned.

[0028] The inventors discovered through research that the basic IO list output by existing tools only includes a list of basic variables and does not include key engineering information such as channel topology. The output data structure is incomplete and cannot support direct reuse by downstream modules. As a result, the basic IO list cannot be reused and requires manual import or copying. Subsequent detailed IO design modules still need to be manually re-entered or mapped, failing to achieve "design once, reuse in multiple places". Channel information needs to be manually filled in through text or tables in another separate file. The channel allocation function is missing, the data output is incomplete, and there is a lack of an interactive allocation interface. Designers need to fill in the rack / chassis / board / channel from scratch, which is inefficient and error-prone.

[0029] The following section uses a nuclear power plant distributed control system platform as an example to introduce the specific method for generating the basic safety-level I / O list of existing nuclear power plant DCS platforms.

[0030] The engineering documents include functional diagrams. Creating these functional diagrams is a crucial step in the ES1.2 functional interface requirements phase of the security-grade DCS engineering design process. (See also...) Figure 1 The diagram shown is a flowchart for drawing a functional diagram according to an embodiment of this application. The upstream input may include IO requirements, logical requirements, setpoint requirements, application software requirements specifications, hardware requirements specifications, etc. The specifications may include security-level DCS (e.g., FirmSys) functional interface design specifications, etc. According to the upstream input of the security-level DCS system and various specifications, logical design, interface design and variable design are performed, thereby transforming the interface information, logical information and functional requirements of each security-level system into a logical functional diagram determined by the system structure and module symbols based on the FirmSys product.

[0031] Once the function diagram is completed, a basic I / O list can be created based on the project files. The project files may include the function diagram, or they may include both the function diagram and I / O requirement files. The following section describes information related to the basic I / O list and its corresponding existing manual creation process. (See [link to relevant documentation]). Figure 2 The diagram shows the correspondence between the analog I / O list information.

[0032] See Figure 2 The diagram shown is a mapping of analog I / O list information provided in an embodiment of this application. Taking the analog I / O list as an example, it can be seen that each signal's information must be filled in with reference to the I / O requirement document and the corresponding function diagram. This step can be done manually, item by item.

[0033] Based on the above technical problems, embodiments of this application provide a basic information management method, apparatus, and related equipment. Responding to the signal list generation operation of the target project, initial signal information of the target project can be generated. Signal identifiers in the initial signal information are used to indicate hard-wired signals in the project file. In the channel display area of ​​the design page, the channel topology information of the target project can be displayed. Channel topology signals can include station numbers, cabinets, chassis, boards, and the relationships between board channels. Responding to associating signal identifiers with board channels, the channel information of the associated board channels is added to the initial signal information. Responding to the design completion operation, a basic signal list is generated based on the initial signal information. In this way, during the design process of the basic signal list, intuitive channel topology information is provided to the user, and a visualized channel information association function is provided. The generated basic signal list includes channel information, providing ready-to-use complete data for subsequent manual transcription and allocation of channel information using additional files, improving signal list generation efficiency, simplifying the process, and reducing allocation errors.

[0034] The following detailed description, in conjunction with the accompanying drawings, illustrates the specific implementation of a basic information management method, apparatus, device, and medium provided in this application through embodiments.

[0035] refer to Figure 3 The flowchart shown is a basic information management method provided in an embodiment of this application. The flowchart of a basic information management method provided in an embodiment of this application may include the following steps.

[0036] S301, in response to the signal list generation operation of the target project, generates the initial signal information of the target project. The signal identifiers in the initial signal information are used to indicate the hard-wired signals in the target project.

[0037] In this embodiment, the target project is the project that requires signal list generation, and can be selected by the user. One project can correspond to one basic signal list.

[0038] The signal identifier in the initial signal information is used to indicate hardwired signals in the target project. Different hardwired signals can be indicated by different signal identifiers. The signal identifier can also be called a variable name (varname) or identifier code (Id_code), used to uniquely identify a hardwired signal. As a type of variable information, the signal identifier in the initial signal information can also include other variable information, such as description (IO_statement), information type (iotype), etc.

[0039] Hardwired signals can have different categories. For example, initial signal information can include all hardwired interface signals of a safety-grade DCS system, i.e., all hardwired signals in the project file. Hardwired signals can include signal categories such as analog input (AI), analog output (AO), digital input (DI), digital output (DO), pulse input (CI), and pulse output (CO) (except for CI and CO which are only used for experimental and diagnostic purposes).

[0040] The initial signal information is generated in response to the signal list generation operation, which may include triggering the signal list generation control, such as the ReoGrid control.

[0041] In response to the signal list generation operation of the target project, the initial signal information of the target project can be generated.

[0042] The signal list generation operation can include design operations, which can be trigger operations on the "basic IO design" of the design control. In response to the design operation, the design page can be displayed.

[0043] Specifically, the user opens the target project in the engineering software design platform, clicks the menu "Basic IO Design", and then a configuration window, i.e. the design page, will pop up.

[0044] The configuration window is a dedicated interface in an engineering software design platform used to adjust and set various parameters and function options.

[0045] After the configuration window pops up, the user can select the project, file list, and target version. Then, the system loads the IO variables and displays the generated initial signal information based on the user's selection and historical data.

[0046] The signal manifest generation operation can include selecting files from the target version's signal manifest (different categories can correspond to different files). The design page can include a project selection control to trigger the project selection operation, a baseline version (i.e., target version) control to trigger the selection operation on the target version's signal manifest, and a file manifest control to trigger the selection operation on the file manifest within the target version's signal manifest.

[0047] See Figure 2 As shown, taking the analog I / O list as an example, it can be seen that the information for each signal must be filled in with reference to the I / O requirement file and the corresponding function diagram. This step can be automatically identified and filled in.

[0048] S302, in the channel display area of ​​the design page, displays the channel topology information of the target project. The channel topology information includes station number, cabinet, chassis, board, and the relationship between board channels.

[0049] In this embodiment of the application, after generating the initial signal information of the target project, the channel topology of the target project can be displayed in the channel display area of ​​the design page.

[0050] The channel display area refers to the structured interface unit in the design page used to centrally display the channel topology information of the target project.

[0051] The relative positions of the channel display area and the signal display page can be set according to actual needs, such as being located on the left or right side of the signal display page.

[0052] The channel topology information includes the channel topology structure of the target project. This topology structure can be a tree structure with multiple nodes. This tree-like channel topology structure visually displays the relationships within the channel topology information to the user (each node, from the root node to the leaf node, can include: Station → Cabinet → Chassis → Module → Channel)). Specifically, the channel topology structure is loaded from the project design management platform or local offline files onto the channel allocation page. A tree diagram control is embedded on the left side of the design page, displaying the structure hierarchically in a tree structure, for example: Station → Cabinet → Chassis → Module → Channel. The tree structure can be a TreeView or a third-party WPF TreeList.

[0053] Nodes in the topology can function as touch-sensitive controls. When a control (such as a target node) is triggered, the channel identifier of the board channel under that node can be displayed on the channel allocation page of the design page. For example, if the target node is a board, the channel identifier of the board channel under that board can be displayed on the channel allocation page of the design page.

[0054] In this embodiment, signal management information can also be displayed in the channel display area of ​​the design page. The signal management information is, for example, an unsigned list. The unsigned list can be displayed as a control. When the control of the unsigned list is triggered, the signal identifier of the unassociated board channel can be displayed. Alternatively, when the control of the unsigned list is triggered, the variable configured under the control can be displayed. The variable can be, for example, a signal category. When the corresponding signal category is triggered, the signal identifier of the unassociated board channel of that category can be displayed.

[0055] To more intuitively demonstrate the relationship between channel topology information and visualized channel information, the signal display page and channel allocation page can be displayed in the same area according to different situations.

[0056] S303, in response to associating a signal identifier with a board channel, adds the associated board channel information to the initial signal information.

[0057] In this embodiment, a signal identifier can be associated with a board channel. In response to associating a signal identifier with a board channel, it indicates that an association relationship has been established between the board channel and the signal identifier. Therefore, the channel information of the associated board channel can be added to the initial signal information, so that the initial signal information can contain the channel information before generating the basic signal list. In this way, the channel allocation function is integrated in the basic IO design stage, and the allocation result is output as a structured field, providing "ready-to-use" complete data for subsequent detailed IO modules and eliminating the manual transcription step.

[0058] S304, in response to the design completion operation, generates a basic signal list based on the initial signal information.

[0059] In this embodiment of the application, after adding the associated board channel information to the signal identifier in the initial signal information, a basic signal list is generated based on the initial signal information.

[0060] The design completion action can be a trigger action on the "Complete Design" control, which can be displayed on the design page. Figure 4 The diagram shown is an example of the operation and effect of this application embodiment. Clicking the "Complete Design" control 30 can generate a basic signal list for the target project, and the system saves the structured data file.

[0061] Figure 5 This is a schematic diagram of relevant form data provided in an embodiment of this application. 04 represents the menu bar, and 05 represents the detailed information under the corresponding option. The menu bar is used for process management, and the detailed information is used to display the detailed information of each process. The submitted basic list can be displayed in the completed processes.

[0062] In this way, the output basic signal list data has a complete structure, clear field bindings, and includes channel topology information, allowing downstream modules to directly reuse it without manual transcription or remapping. Channel allocation functionality is added during the design process, providing visual interaction. A visual tree structure assists engineers in completing allocations, integrating channel allocation information upfront into the basic list data design phase, avoiding repetitive data entry in subsequent stages. The basic signal list includes complete engineering attributes and channel topology; its data structure can be, for example, JSON or structured CSV, supporting direct transmission to subsequent modules via API or file interface, improving system integration. This solves the problem of siloed output data and lack of system collaboration capabilities.

[0063] In this embodiment of the application, in response to the triggering operation of the board, the channel identifier of the board channel is displayed in the channel allocation page of the design page; in response to adding the second identifier of the signal identifier to the signal information corresponding to the first identifier in the channel identifier, the first identifier is associated with the second identifier, as well as the board, chassis, cabinet and station number to which the second identifier belongs.

[0064] Channel identifiers are used to uniquely identify channels among multiple channels and map them to specific channels. For example, Figure 6 The diagram shown is a schematic of a channel allocation page provided in an embodiment of this application. Numbers 1-16 in the diagram represent the channel identifiers of the channels included in the board (board 1-AI) selected by the user under the target project.

[0065] Signal identifiers are used to identify specific signals within a given signal type. For example, you can refer to... Figure 4 Each row in the column corresponding to the variable name corresponds to a signal identifier. Each signal identifier has its corresponding board channel information. For example, the channel information corresponding to the signal identifier with the variable name HXDXS311MT in the first row is: Station number P3C1 → Rack 1 → Chassis 1 → Board 1-AI → Channel 1.

[0066] Adding a second identifier to the signal information corresponding to the first identifier can be achieved by assigning a second identifier to the signal information. In practice, the second identifier can be filled in the signal information. For example, the user can open the board node and manually input the signal to be assigned.

[0067] To add a second identifier to the signal information corresponding to the first identifier, a selection control corresponding to the signal information can be displayed. Users can select the second identifier using this control. For example, a user could select a row (representing a channel) in a ReoGrid table displayed on the channel allocation page of the design page, and then select unassigned signals. (See reference...) Figure 6 The "Select" control 10 in the middle can be clicked to trigger the selection operation of unassigned signals. After the selection is completed, the assignment is completed. The assignment result is stored as a structured field in each record of the initial signal information, including information such as station number, cabinet number, chassis number, board number, and channel number.

[0068] In this way, the channel allocation function is integrated into the basic signal design stage, the channel information is visualized and bound through a tree diagram, and the allocation results are output as structured fields, providing "ready-to-use" complete data for subsequent detailed signal modules and eliminating the manual transcription step.

[0069] In this embodiment of the application, the initial signal information is displayed on the signal display page of the design page, and in response to the editing operation of the initial signal information on the design page, the initial signal information is updated according to the editing operation.

[0070] The signal display page is used to display all initial signal information under the target project. This page includes information such as variable name, signal source / destination, description, and IO type.

[0071] The signal display page and the channel allocation page can be displayed in the same area, but in different situations.

[0072] The initial signal information can be edited, and the initial signal information is updated based on the edits. In other words, designers can edit fields that are in an editable state. (See reference...) Figure 7 This is a schematic diagram of multi-page variable information for a signal display page provided in an embodiment of this application. The information in the white area of ​​the diagram is the editable area.

[0073] In this way, the system only allows editing of areas that are not automatically generated. Designers can edit areas with editing permissions, which improves the scalability of the basic signal list.

[0074] In this embodiment, a field-level edit lock can be configured for the variable information in the initial signal information to prevent the variable information from being edited. The variable information includes at least the signal identifier.

[0075] Field-level edit lock is a setting that locks automatically generated fields. It can lock the content corresponding to automatically generated variable information in a read-only state, making it uneditable, such as signal identifiers, descriptions, and information types.

[0076] Specifically, the system can distinguish between "automatically generated fields" and "manually filled fields." By configuring a field-level edit lock for automatically generated fields, it makes these fields read-only, preventing the editing of the variable information corresponding to their columns, such as the variable information corresponding to signal identifiers. Manually filled fields, on the other hand, are editable, and the initial signal information is updated based on the editing operation. Manually filled fields are not subject to a field-level edit lock, allowing them to be edited by the user. They can be automatically identified and filled in in response to the signal list generation operation of the target project, and then checked and modified by the user. Alternatively, they can be left unfilled and filled in manually by the user.

[0077] See Figure 7The gray areas are locked and cannot be edited by the user. Examples include columns for serial number, variable name, signal source / destination, and description. The white areas can be automatically generated or filled in by the user, such as columns for safety level, sensor type, and power supply method. Field-level edit locks can be set through variable information attribute values. For example, when initial signal information is displayed through an information table (ReoGrid), field-level edit locks can be implemented using the `Worksheet.SetRangeStyle` or `Cell.Locked` properties of ReoGrid to set automatically generated columns to read-only.

[0078] This provides a field-level editing protection mechanism. By implementing differentiated editing protection between automatically generated fields and manually filled fields during the basic signal design phase, modifications are restricted, preventing data source contamination caused by accidental modification of basic data (such as variable names and signal types), and ensuring data source consistency.

[0079] In this embodiment of the application, multiple category labels can be displayed on the design page, and the signal display page is used to display the initial signal information under the selected current label among the multiple category labels. The basic signal list includes the signal list under multiple category labels.

[0080] In one possible implementation, the signal identifier in the initial signal information can correspond to multiple categories of hardwired signals, and multiple category labels can be displayed on the design page.

[0081] Category labels can include analog I / O signal types, digital I / O signal types, CIO signal types, etc., making the basic signal list include: analog I / O list, digital I / O list, and CIM variable list (or actuator list). The initial signal information from different labels can form a multi-tab worksheet. In the signal display page, each row represents a hardwired signal, indicated by a signal identifier, and each column represents an attribute field. (Reference) Figure 6 The image shows the signal display page under the corresponding analog I / O signal label. 02 corresponds to the AIO signal type page, and 03 corresponds to the DIO signal type page. The signal display page shows the initial signal information for the selected label from multiple category labels. The basic signal list includes signal lists from multiple category labels.

[0082] In this way, by labeling and classifying basic signal information, the category of the signal can be indicated, and the signal information and channel information in the basic signal list corresponding to different signal types can be displayed intuitively, thereby improving the efficiency and readability of data management.

[0083] In this embodiment of the application, if the list generation operation includes a selection operation for the target version of the signal list, then the initial signal information of the target project is generated based on the signal list of the target version, and the version of the basic signal list is an updated version of the target version; if the list generation operation does not include a selection operation for the target version of the signal list, then the initial signal information of the target project is generated based on the project file of the target project.

[0084] When generating a signal list, including selecting a target version of the signal list, the initial signal information for the target project can be generated based on the target version's signal list. This is equivalent to inheriting the content of the target version's signal list. Specifically, the system will automatically inherit the same "manually filled field" and "automatically generated field" values ​​from the target version to the current version. Newly added signal points will be left blank to be filled or extracted and filled from the project file. Therefore, the basic signal list saved after this modification will be an updated version of the target version.

[0085] Specifically, after the user selects a project, the system automatically scans the project file pages under the selected node in the engineering software design platform, extracting information point variable information, including variable names, etc. Specifically, the user selects a baseline version in the interface, and the target version is used as the baseline version. The signal list for the target version can be obtained by calling the engineering design management platform interface. Then, the system downloads the signal list data for that baseline version, which includes automatically generated fields and manually entered fields. By implementing baseline version attribute inheritance and constructing a data inheritance mechanism linked to the engineering baseline system, efficient, controllable, and traceable version management is achieved, improving version iteration efficiency and meeting the mandatory requirements for traceability of design changes in nuclear power projects.

[0086] When the signal list generation operation does not include the selection of a target version of the signal list, the initial signal information of the target project can be generated based on the project file of the target project. Specifically, taking an analog I / O list as an example, refer to... Figure 2 As shown, each signal's information must be filled in according to the IO requirement document and the corresponding function diagram. Specifically, relevant field information can be automatically filled in based on the IO requirement document and function diagram. For example, variable names and IO categories can be determined based on the function diagram, and descriptions can be determined based on the IO requirement document. Special fields have open editing interfaces, such as security level. Semantic structured modeling of security-level DCS projects has been implemented, converting and mapping the corresponding underlying diagram information to the corresponding IO structure model.

[0087] See Figure 8The database relationship diagram provided in this embodiment illustrates the association between file lists, file versions, project information, file templates, and basic I / O. Project information stores information corresponding to each project ID; file templates define file types for the signal list; the file list indicates different versions of the signal list; file versions manage file versions; and basic I / O stores various basic I / O lists. The data relationships can be queried through the engineering design management platform interface to obtain the signal list of the target version.

[0088] This enables the engineering design management platform to link versions, eliminating the need for a complete rework or manual comparison during version upgrades. By connecting to the engineering design management platform's baseline system via API, it supports "inheriting manual attributes from the previous version," improving change management efficiency and providing traceability.

[0089] In this embodiment, the user can perform file-level editing lock on the initial signal information. In response to the file-level editing lock on the initial signal information, a file-level editing lock is applied to the target version of the signal list. This locks the target version of the signal list and sets it to read-only, preventing other users from editing it. This ensures that the target version of the signal list can only be edited by the user who selected it, thus avoiding editing conflicts between different users. This is suitable for scenarios where users need to edit and submit the signal list. In the file-level editing lock state, a lock icon can be displayed to visually indicate the locked or unlocked status of the target version of the signal list. Specifically, the locked or unlocked state can be toggled using a "lock" control. (See reference...) Figure 9 The diagram shown is a schematic of a signal list file lock identifier provided in an embodiment of this application. The "Lock" control 20 is displayed on the design page and is currently in a locked state.

[0090] In this embodiment, in response to unlocking the file-level editing of the initial signal information, the file-level editing lock is released for the target version of the signal list. Thus, the target version of the signal list is not locked and can be edited by other users, which is suitable for scenarios where users only view and do not submit.

[0091] Specifically, in the subsequent user submission process, after the engineering design management platform locks the current signal list file (i.e., the signal list of the target version) (Locked = true), the system will monitor this state. If the file is locked, the entire signal list worksheet (ReoGrid) will be set to read-only mode (`Worksheet.Protect()`); after unlocking, it will be restored to the editable state (only fields can be manually filled in).

[0092] In this way, by using a two-layer locking mechanism at the field level and the file level, we can prevent critical data from being modified accidentally and ensure the integrity and authority of the design data.

[0093] In this embodiment of the application, in response to the edit comparison operation, the content revision information of the initial signal information relative to the target version of the signal list is displayed.

[0094] Content revision information is a complete record of all changes made, including modifications, additions, and deletions, based on the baseline list. Content revision information can have different types, such as modification, addition, and deletion, and different types of content revision information can correspond to different display styles.

[0095] The edit comparison operation can be a trigger action on an edit comparison control, such as a "Compare" button. Content revision information can include at least one of the following: deleted data, added data, and modified data.

[0096] Users can click the "Compare" button to trigger an editing comparison operation, for example, referring to... Figure 4 As shown, the "upgrade mark" control 20 can be triggered to view the differences with the target version. Specifically, the system compares the current version with the baseline version line by line, uses a text difference algorithm to compare each line and column, marks the differences, and displays the content revision information. Referring to Figures 10(a), (b), and (c), these are schematic diagrams of data deletion, data addition, and data modification provided in this application embodiment. As shown in Figure 10(a), the gray or yellow filled part corresponds to deleted data, that is, the signal information corresponding to the original row is deleted; as shown in Figure 10(b), the red or gray font part corresponds to added data, that is, a new row is added to display new signal information; as shown in Figure 10(c), the red or gray font part corresponds to modified data, that is, the corresponding parameters of the original data of the baseline version are updated and modified. The modification is limited to the white area, that is, the white area can be modified, it can be empty, or it can have content to be updated, thus displaying the content revision information of the signal list of the initial signal information relative to the target version. The upgrade difference mark achieves efficient, controllable, and traceable version management. In this way, by connecting to the baseline system of the engineering design management platform via API, "version upgrade difference marking" can be supported, enabling efficient, controllable, and traceable version management.

[0097] In this embodiment of the application, in response to the design completion operation, the management platform interface is called to submit a basic signal list to the approval system, thereby realizing an automated integration mechanism and achieving seamless delivery of design results.

[0098] The "Complete Design" action can be triggered by the "Complete Design" control, which can be displayed on the design page. (For reference...) Figure 6The “Complete Design” control 30 is shown.

[0099] Specifically, users can click "Complete Design" and confirm. The system will automatically abstract the signal list of the completed design into a class list, automatically call the engineering design management platform API to initiate the process, upload relevant data to the backend database and initiate the approval process, and then receive feedback from the engineering design management platform, recording it in the local log. A "process initiated" message in the interface log indicates success. After the user clicks "Complete Design" and confirms, the system will automatically call the engineering design management platform API to initiate the approval process and return the process status. In this way, the submitted basic signal list can be automatically consumed by the subsequent "detailed IO design module" to generate the final detailed IO list, realizing closed-loop management of "design as delivery". This achieves seamless connection from design to delivery and avoids the problems of human error or delay caused by engineers manually logging into the information platform to initiate the process after the design is completed.

[0100] In this embodiment, the aforementioned basic information management method can be implemented through an automated design tool. This automated design tool is an embedded plug-in module of an engineering software design platform, and its operating environment includes a front-end interface layer, a business logic layer, a data interface layer, and an external system. The business logic layer is used to implement the aforementioned basic information management method.

[0101] The front-end UI layer can be built based on the ReoGrid open-source table control, supporting multi-tab categorized display, column-level permission control, and tree diagram interaction. The business logic layer includes modules for automatic variable extraction and presentation, dual-layer data locking, baseline version management and difference comparison, visualization channel allocation, and automatic process triggering. The business logic layer can control the front-end UI layer to display corresponding content.

[0102] The data interface layer includes: A. Read internal I / O variable data of the engineering software design platform (project file parsing); B. Call the engineering design management platform's REST API to obtain / submit baseline version information and initiate file processes; C. Output structured database tables for subsequent detailed IO module calls.

[0103] External systems include: A. Engineering software design platform (data source); B. Engineering design management platform (baseline control, process engine).

[0104] like Figure 11The diagram shown is a data flow diagram provided in an embodiment of this application, which includes an automatic variable extraction and presentation module, a two-layer data locking module, a baseline version management and difference comparison module, a visualization channel allocation module, and an automatic process triggering module.

[0105] The automatic variable extraction and presentation module is used to respond to the signal list generation operation of the target project, generate the initial signal information of the target project, and display the initial signal information on the signal display page of the design page. Specifically, after the user selects a project, the system automatically scans the function diagram pages under the selected node of the project in the project software design platform, extracts the variable information of IO points, including variable name, description, signal type, etc., and creates multi-page worksheets (corresponding to different category labels) through the ReoGrid control to present them according to variable type.

[0106] The automatic variable extraction and presentation module also responds to editing operations on initial signal information in the design page, updating the initial signal information based on the editing operations. The design page displays multiple category labels, and the signal display page shows the initial signal information under the currently selected label from these multiple category labels. The basic signal list includes signal lists under multiple category labels. If the list generation operation does not include a selection operation for the target version's signal list, then the initial signal information for the target project is generated based on the target project's project files.

[0107] The dual-layer data locking module is used to configure field-level edit locks for variable information in the initial signal, preventing the variable information from being edited. Specifically, the system identifies "automatically generated fields" and "manually filled fields," and uses the ReoGrid's `Worksheet.SetRangeStyle` or `Cell.Locked` property to set automatically generated columns to read-only, preventing users from modifying these columns and thus preventing data source contamination.

[0108] The dual-layer data locking module is also used to lock the initial signal list at the file level in response to a file-level edit lock on the initial signal information, and to lock the target version of the signal list at the file level, preventing the initial signal list from being edited by other users. It is also used to unlock the initial signal list at the file level in response to a file-level edit lock on the initial signal information, thereby removing the file-level edit lock from the target version of the signal list.

[0109] Specifically, this module monitors the status of the target version file. If the file is locked, the entire ReoGrid worksheet is set to read-only mode (`Worksheet.Protect()`). After unlocking, it can be restored to editable mode (manual columns only). By establishing a "field-level + file-level" dual-layer locking mechanism, it distinguishes between automatically generated data and editable attributes, and links with the file status of the engineering design management platform to dynamically control editing permissions, ensuring data security and consistency.

[0110] The baseline version management and difference comparison module is used to generate the initial signal information of the target project based on the target version's signal list when the list generation operation includes the selection operation of the target version's signal list. The version of the basic signal list is the updated version of the target version. Specifically, the system will automatically inherit the same "manually filled field" values ​​and "automatically generated field" values ​​from the target version to the current version, and leave newly added signal points blank to be filled.

[0111] The baseline version management and difference comparison module is also used to respond to edit comparison operations by displaying content revision information of the initial signal information relative to the target version of the signal list. The content revision information may include at least one of deleted data, added data, and modified data.

[0112] By connecting to the baseline system of the engineering design management platform via API, it supports "inheriting manual attributes from the previous version" and "upgrade difference marking", realizing version linkage of the engineering design management platform and achieving efficient, controllable and traceable version management.

[0113] The visual channel allocation module is used to display the channel topology information of the target project in the channel display area of ​​the design page. The channel topology information includes station number, cabinet, chassis, board, the relationship between board channels, and channel information of the associated board channel added to the initial signal information in response to associating signal identifiers with board channels.

[0114] The visualization channel allocation module is also used to respond to the trigger operation of the target node in the channel topology information, display the channel identifier of the board channel in the target node in the channel allocation page of the design page, add the second identifier of the signal identifier to the signal information corresponding to the first identifier in the channel identifier, associate the second identifier with the first identifier, and associate the second identifier with the board, chassis, cabinet and station number to which the first identifier belongs.

[0115] Specifically, a tree diagram control can be embedded on the left side of the ReoGrid to display the tree-like channel topology, thereby integrating the channel allocation function in the basic IO design stage as described in this application embodiment. The channel information is bound visually through the tree diagram, and the allocation results are output as structured fields, providing "ready-to-use" complete data for subsequent detailed IO modules and eliminating the manual transcription step.

[0116] The automatic process triggering module is used to generate a basic signal list based on the initial signal information in response to the design completion operation, and to call the management platform interface to submit the basic signal list to the approval system in response to the design completion operation.

[0117] Specifically, when a user clicks "Complete Design" and confirms the completion of the design, the system abstracts the current design completion IO list into a class list, calls the engineering design management platform interface, uploads relevant data to the backend database, initiates the approval process, and then receives feedback from the engineering design management platform and records it to the local log. The interface log prompts "Process initiated," realizing the closed-loop management of "design as delivery."

[0118] In summary, this embodiment constructs an integrated closed loop of "design-allocation-comparison-process," possessing collaborative design capabilities centered on an engineering data model. This basic information management method is an integrated design capable of automating the generation of basic IO lists, intelligent attribute inheritance, visual channel allocation, version difference comparison, and automatic process initiation. It is suitable for IO list design and version control in security-grade DCS control system projects, improving engineering design efficiency and data quality.

[0119] In this application embodiment, addressing the high integrity, high traceability, and strong structured requirements of the IO inventory in nuclear power safety-grade DCS engineering, a data organization and generation method based on engineering semantics is proposed. This method reconstructs the originally discrete, planar IO variable information into a multi-dimensional structured data model containing device hierarchy, channel topology, security attributes, and version baselines. Furthermore, it ensures compliance and consistency in the design process through visual interaction and constraint mechanisms. The core lies in achieving intelligent, standardized, and closed-loop design of basic IO processes in industrial automation projects through an integrated interface, intelligent data locking mechanism, baseline version linkage, visual channel allocation, structured data output, and automatic process triggering.

[0120] This invention chooses to be developed within the native engineering environment of the engineering software design platform, combining the ReoGrid high-performance table control, the engineering design management platform API, the tree-structured allocator, and the dual-layer locking mechanism. This is a solution that achieves the best balance between "engineering integration, interactive experience, performance scalability, system security, and data consistency".

[0121] This application provides a basic information management method. In response to a signal list generation operation for a target project, initial signal information for the target project can be generated. Signal identifiers in the initial signal information indicate hard-wired signals in the project files. The channel topology information of the target project can be displayed in the channel display area of ​​the design page. Channel topology signals can include station numbers, cabinets, chassis, boards, and the relationships between board channels. In response to associating signal identifiers with board channels, the associated board channel information is added to the initial signal information. In response to a design completion operation, a basic signal list is generated based on the initial signal information. This provides users with intuitive channel topology information and a visualized channel information association function during the basic signal list design process. The generated basic signal list includes channel information, providing ready-to-use complete data for subsequent manual transcription and channel information allocation, improving signal list generation efficiency, simplifying the process, and reducing allocation errors.

[0122] Based on the above basic information management methods, this application also provides a basic information management device, as described above. Figure 12 The diagram shown is a schematic diagram of a task execution device provided in an embodiment of this application, and a structural block diagram of a basic information management device provided in an embodiment of this application, including: The first generation unit is used to generate initial signal information of the target project in response to the signal list generation operation of the target project. The signal identifier in the initial signal information is used to indicate the hard-wired signals in the target project. The first display unit is used to display the channel topology information of the target project in the channel display area of ​​the design page. The channel topology information includes station number, cabinet, chassis, board, and the relationship between board channels. The association unit is used to add the associated board channel information to the signal identifier in the initial signal information in response to associating the board channel with the signal identifier; The second generation unit is used to generate a basic signal list based on the initial signal information in response to the design completion operation.

[0123] Optionally, the device further includes: The trigger unit is used to respond to the trigger operation of the board and display the channel identifier of the board channel in the channel allocation page of the design page; The association unit is specifically used to respond to adding a second identifier from the signal identifier to the signal information corresponding to the first identifier in the channel identifier, associating the second identifier with the first identifier, and the board, chassis, cabinet and station number to which the second identifier belongs.

[0124] Optionally, the device further includes: The second display unit is used to display the initial signal information on the signal display page of the design page; The editing unit is used to respond to editing operations on the initial signal information in the design page and update the initial signal information according to the editing operation.

[0125] Optionally, the device further includes: The field-level edit lock configuration unit is specifically used to configure a field-level edit lock for the variable information in the initial signal information, so that the variable information cannot be edited. The variable information includes at least the signal identifier.

[0126] The category label display unit is used to display multiple category labels on the design page. The signal display page is used to display the initial signal information under the selected current label among multiple category labels. The basic signal list includes the signal list under multiple category labels.

[0127] Optionally, the first generating unit is specifically used for: If the list generation operation includes selecting a signal list for the target version, then the initial signal information of the target project is generated based on the signal list for the target version, and the version of the basic signal list is an updated version of the target version; if the list generation operation does not include selecting a signal list for the target version, then the initial signal information of the target project is generated based on the project file of the target project.

[0128] Optionally, the device further includes: The locking unit is configured to, in response to a file-level edit lock on the initial signal information, configure a configuration file-level edit lock for the target version of the signal manifest, preventing the target version of the signal manifest from being edited by other users; and / or, The unlocking unit is configured to, in response to file-level editing unlocking of initial signal information, release the file-level editing lock on the signal list for the target version; and / or, The comparison unit, in response to an edit comparison operation, displays the content revision information of the initial signal information relative to the target version of the signal list.

[0129] Optionally, the device further includes: The submission unit is used to respond to the design completion operation by calling the management platform interface to submit a basic signal list to the approval system.

[0130] Please see Figure 13 , Figure 13 This is a structural block diagram of a computer device for basic information management, provided as an embodiment of this application. The computer device includes a processor 1301 and a memory 1302. Memory 1301 is used to store program code and transfer program code to processor 1302; The processor 1301 is used to execute the basic information management method of any of the above embodiments according to the instructions in the program code.

[0131] This application provides a basic information management device that, in response to a signal list generation operation for a target project, generates initial signal information for the target project. The signal identifiers in the initial signal information indicate hard-wired signals in the project files. The channel topology information of the target project can be displayed in the channel display area of ​​the design page. Channel topology signals can include station numbers, cabinets, chassis, boards, and the relationships between board channels. In response to associating signal identifiers with board channels, the associated board channel information is added to the initial signal information. In response to a design completion operation, a basic signal list is generated based on the initial signal information. This provides users with intuitive channel topology information and a visualized channel information association function during the basic signal list design process. The generated basic signal list includes channel information, providing ready-to-use complete data for subsequent manual transcription and channel information allocation, improving signal list generation efficiency, simplifying the process, and reducing allocation errors.

[0132] This application also discloses a computer-readable storage medium for storing a computer program, which, when executed by a processor, performs a basic information management method according to any of the above-described embodiments.

[0133] As can be seen from the above description of the embodiments, those skilled in the art can clearly understand that all or part of the steps in the methods of the above embodiments can be implemented by means of software plus a general-purpose hardware platform. Based on this understanding, the technical solution of this application can be embodied in the form of a software product. This computer software product can be stored in a storage medium, such as a read-only memory (ROM) / RAM, magnetic disk, optical disk, etc., including several instructions to cause a computer device (which may be a personal computer, a server, or a network communication device such as a router) to execute the methods of various embodiments or some parts of the embodiments of this application.

[0134] It should be noted that the various embodiments in this specification are described in a progressive manner, with each embodiment focusing on the differences from other embodiments. Similar or identical parts between embodiments can be referred to interchangeably. For the apparatus disclosed in the embodiments, since it corresponds to the method disclosed in the embodiments, the description is relatively simple; relevant parts can be referred to in the method section.

[0135] It should also be noted that, in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes the element.

[0136] The above are merely preferred embodiments of this application. Although this application has disclosed preferred embodiments above, they are not intended to limit this application. Any person skilled in the art can make many possible variations and modifications to the technical solutions of this application using the methods and techniques disclosed above, or modify them into equivalent embodiments with equivalent changes, without departing from the scope of the technical solutions of this application. Therefore, any simple modifications, equivalent changes, and modifications made to the above embodiments based on the technical essence of this application without departing from the content of the technical solutions of this application shall still fall within the protection scope of the technical solutions of this application.

Claims

1. A basic information management method, characterized in that, include: In response to the signal list generation operation of the target project, initial signal information of the target project is generated, wherein the signal identifiers in the initial signal information are used to indicate hard-wired signals in the target project; The channel display area on the design page displays the channel topology information of the target project, which includes station number, cabinet, chassis, board, and the relationship between board channels. In response to associating the signal identifier with the board channel, the channel information of the associated board channel is added to the initial signal information for the signal identifier; In response to the design completion operation, a basic signal list is generated based on the initial signal information.

2. The method according to claim 1, characterized in that, The method further includes: In response to a trigger operation on a target node in the channel topology information, the channel identifier of the board channel in the target node is displayed on the channel allocation page of the design page. In response to adding a second identifier from the signal identifier to the signal information corresponding to the first identifier in the channel identifier, associating the second identifier with the first identifier, and associating the second identifier with the board, chassis, cabinet and station number to which the first identifier belongs.

3. The method according to claim 1, characterized in that, The method further includes: The initial signal information is displayed on the signal display page of the design page; In response to an editing operation on the initial signal information in the design page, the initial signal information is updated according to the editing operation.

4. The method according to claim 3, characterized in that, The method further includes: Configure a field-level edit lock on the variable information in the initial signal information to prevent the variable information from being edited; the variable information includes at least the signal identifier; and / or, The design page displays multiple category labels, and the signal display page is used to display the initial signal information under the selected current label among the multiple category labels. The basic signal list includes the signal list under multiple category labels.

5. The method according to claim 1, characterized in that, The signal list generation operation in response to the target project generates initial signal information for the target project, including: If the list generation operation includes a selection operation for a target version of the signal list, then the initial signal information of the target project is generated based on the target version of the signal list, and the version of the basic signal list is an updated version of the target version; If the list generation operation does not include the selection operation of the signal list for the target version, then the initial signal information of the target project is generated based on the project file of the target project.

6. The method according to claim 5, characterized in that, The method further includes: In response to a file-level edit lock on the initial signal information, a configuration file-level edit lock is applied to the signal manifest for the target version, preventing the signal manifest for the target version from being edited by other users; and / or, In response to the file-level editing unlock of the initial signal information, the file-level editing lock is released for the signal list of the target version; and / or, In response to the edit comparison operation, the content revision information of the initial signal information relative to the target version of the signal list is displayed.

7. The method according to claim 1, characterized in that, The method further includes: In response to the design completion operation, the basic signal list is submitted to the approval system by calling the management platform interface.

8. A basic information management device, characterized in that, The device includes: The first generation unit is configured to generate initial signal information of the target project in response to the signal list generation operation of the target project, wherein the signal identifier in the initial signal information is used to indicate hard-wired signals in the target project; The first display unit is used to display the channel topology information of the target project in the channel display area of ​​the design page. The channel topology information includes station number, cabinet, chassis, board, and the relationship between board channels. An association unit is configured to, in response to associating the signal identifier with the board channel, add the associated board channel information to the signal identifier in the initial signal information; The second generation unit is used to generate a basic signal list based on the initial signal information in response to the design completion operation.

9. A computer device, characterized in that, The computer device includes a processor and memory: The memory is used to store program code and transmit the program code to the processor; The processor is used to execute the basic information management method according to any one of claims 1-7 according to the instructions in the program code.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium is used to store a computer program, which, when executed by a processor, is used to perform the basic information management method according to any one of claims 1-7.

Images