Control method applied to batch control system, computing device, storage medium and computer program product

Abstract

The control method applied to the batch control system provided by the embodiments of the present specification sets a corresponding graphical device selection strategy for the production node in the batch production process to describe the device selection logic in a graphical manner. Compared with the pure text or code method, the graphical presentation enables the complex logic conditions, judgment branches and execution paths to be intuitively arranged in the form of visual elements such as nodes and lines to form a flowchart, thereby reducing the cognitive load and time cost of engineers in creating, reviewing and understanding the logic and improving the efficiency from the source. In addition, during the selection of the target device, the execution state of the production node and / or the execution process of the graphical strategy are displayed, the logic calculation process of the internal decision of the system is converted into visual information flow that can be perceived by the operator in real time, the internal process that is originally invisible becomes visible, and the transparency of the execution process is realized.

Description

Technical Field

[0001] This specification relates to the field of computer application technology, specifically to automation control technology within the field of computer application technology, and more specifically to a control method, computing device, storage medium, and computer program product applied to batch control systems. Background Technology

[0002] In the field of batch production automation control, to optimize production processes and resource utilization, it is typically necessary to dynamically select the most suitable production equipment based on the real-time status of the equipment (such as idle time, capacity, cleaning records, etc.) during production execution. Therefore, how to achieve dynamic equipment selection efficiently and transparently is a common technical requirement in this field. Summary of the Invention

[0003] This specification provides a control method, computing device, storage medium, and computer program product for batch control systems, aiming to improve equipment selection efficiency and the transparency of the execution process.

[0004] To achieve the above technical objectives, the embodiments of this specification provide the following technical solutions: Firstly, one embodiment of this specification provides a control method applied to a batch control system, comprising: The batch production process is executed. The batch generation process includes multiple production nodes. At least one production node corresponds to a graphical device selection strategy. The graphical device selection strategy is used to describe the device selection logic of its corresponding production node in a graphical manner. Based on the graphical device selection strategy corresponding to the production node, a target device is selected from multiple devices corresponding to the production node as the device to execute the production node. Displays the execution status of the production node and / or the execution process of the graphical device selection strategy.

[0005] Secondly, one embodiment of this specification provides a batch control system, including: a batch server and an operator station; wherein... The batch server is configured to execute a batch production process, which includes multiple production nodes. At least one production node corresponds to a graphical device selection strategy, which is used to describe the device selection logic of its corresponding production node in a graphical manner. Based on the graphical device selection strategy corresponding to the production node, a target device is selected from multiple devices corresponding to the production node as the device to execute the production node. Based on the operator station, the execution status of the production node and / or the execution process of the graphical device selection strategy are displayed.

[0006] Thirdly, one embodiment of this specification also provides a computing device, 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 control method applied to a batch control system as described above.

[0007] Fourthly, one embodiment of this specification also provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the control method described above for use in a batch control system.

[0008] Fifthly, embodiments of this specification provide a computer program product or computer program, the computer program product including a computer program stored in a computer-readable storage medium; a processor of a computer device reads the computer program from the computer-readable storage medium, and when the processor executes the computer program, it implements the steps of the control method applied to a batch control system described above. Optionally, the computer program may be stored in a computer-readable storage medium or in the cloud; the processor of the computer device reads the computer program from the readable storage medium or in the cloud.

[0009] As can be seen from the above technical solutions, the control method for batch control systems provided in the embodiments of this specification sets a graphical device selection strategy for at least one production node in the batch production process. This graphical device selection strategy is used to describe the device selection logic of the corresponding production node in a graphical manner. Compared to describing the device selection logic in plain text or code, the graphical presentation of the device selection logic allows complex logical conditions, decision branches, and execution paths to be intuitively arranged using visual elements such as nodes and lines, forming a clear flowchart. This directly reduces the cognitive load and time cost for engineers when creating, reviewing, and understanding the device selection logic, improving efficiency from the source of strategy design and maintenance. Furthermore, during the selection of the target device at the production node, the execution status of the production node and / or the execution process of the graphical device selection strategy can be displayed. This transforms the logical calculation process of the system's internal decision-making based on the strategy (such as which decision node is being executed, whether the conditions are met, the current candidate device list, etc.) into a visual information flow that operators can perceive in real time. This makes the originally invisible internal process visible, thereby achieving transparency in the execution process. Attached Figure Description

[0010] To more clearly illustrate the technical solutions in the embodiments or prior art of this specification, the drawings used in the description of the embodiments or prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of this specification. For those skilled in the art, other drawings can be obtained based on the provided drawings without creative effort.

[0011] Figure 1 This is a schematic diagram of a batch control system provided for one embodiment of this specification.

[0012] Figure 2 This is a flowchart illustrating a control method applied to a batch control system, as provided in one embodiment of this specification.

[0013] Figures 3-8 A schematic diagram of the interactive interface provided for the implementation of this specification.

[0014] Figure 9 This is a schematic diagram of the structure of a computing device provided for one embodiment of this specification. Detailed Implementation

[0015] Unless otherwise defined, the technical or scientific terms used in the embodiments of this specification shall have the ordinary meaning understood by one of ordinary skill in the art to which this specification pertains. The terms "first," "second," and similar terms used in the embodiments of this specification do not indicate any order, quantity, or importance, but are merely used to avoid confusion of constituent elements.

[0016] Unless the context otherwise requires, throughout this specification, "a plurality of" means "at least two," and "including" is interpreted as open-ended or encompassing, that is, "including, but not limited to." In the description of this specification, terms such as "one embodiment," "some embodiments," "exemplary embodiment," "example," "specific example," or "some examples" are intended to indicate that a particular feature, structure, material, or characteristic associated with that embodiment or example is included in at least one embodiment or example of this specification. The illustrative representations of the above terms do not necessarily refer to the same embodiment or example.

[0017] The technical solutions in the embodiments of this specification will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this specification, and not all embodiments. Based on the embodiments in this specification, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this specification.

[0018] Overview In related technologies, a text-expression-based configuration method is commonly used to define equipment selection logic. Specifically, in the recipe or unit configuration stage of a batch control system, engineers need to write independent text conditional expressions for each logical device unit. When production reaches a stage requiring dynamic selection, the system parses these scattered configuration expressions, calculates whether the attributes of each physical device meet the conditions, and thus filters out available devices. While this method can achieve basic selection functionality, it lacks centralized and structured expression and management because it embeds the complete equipment selection strategy logic in text form across multiple configuration items. Furthermore, since this logic only manifests as a background data calculation process during execution, its specific decision path, intermediate results, and selection criteria cannot be intuitively perceived and monitored.

[0019] Therefore, the relevant technologies face two interrelated specific technical problems in practical applications: First, due to the decentralized configuration of strategy logic, engineers find it difficult to quickly understand, review, and maintain the complex equipment selection logic as a whole, increasing the risk of configuration errors and the complexity of system maintenance; Second, due to the lack of visualized real-time feedback in the strategy execution process, equipment selection during production becomes a "black box" operation, which is not conducive to operators' status monitoring and rapid diagnosis and location of faults, affecting the observability and operation and maintenance efficiency of the production system.

[0020] In batch control systems, to dynamically select a target device from multiple functionally identical devices during production, a common approach is to configure independent text conditional expressions for each device unit. Specifically, this method achieves dynamic filtering by writing text expressions such as "Device Status == 'Idle' AND Capacity >= 1000" for each logical device group in the recipe or unit alias configuration. The basic principle is that when production reaches this stage, the system obtains a list of candidate devices and calculates whether the attributes of each device satisfy the text expression, thus filtering out the available device set. Its widespread use stems from its ability to define selection conditions in a relatively flexible manner and bind them to variables in the control system.

[0021] However, this solution performs poorly when applied to production scenarios with complex logic and multi-step filtering and sorting processes. The specific reason is that, in pursuit of configuration flexibility and direct binding to underlying devices, its inherently distributed text-based configuration design inevitably compromises the overall manageability of the strategy logic and the visibility of the execution process, even leading to difficulties in operation and maintenance debugging. Specifically, in scenarios requiring filtering by status and capacity followed by sorting by idle time to select devices, engineers must view and integrate different expression fragments in multiple configuration units to understand the complete logic. Furthermore, during production runtime, the system's internal execution progress, unmet conditions, and the resulting intermediate list are completely invisible to operators.

[0022] In-depth analysis reveals that the root cause of the aforementioned contradictions lies in the following: From an information organization perspective, the strategy logic, presented as unstructured text, is scattered and embedded across multiple independent configuration units, lacking a unified, structured data model for centralized representation and management. From a runtime perspective, the execution engine's interpretation and computation of text expressions is an internal process; its steps, branches, and intermediate results are not mapped to an externally perceptible model state, making the execution process a black box. Furthermore, from a human-computer interaction perspective, text expressions, as a subset of programming languages, require high user skills for writing, reading, and debugging, and are not intuitive, further amplifying the maintenance and debugging costs arising from the aforementioned two levels of problems.

[0023] To overcome the aforementioned contradictions, this specification proposes a control method for batch control systems. In this method, a graphical device selection strategy can be set for at least one production node in the batch production process. This graphical device selection strategy describes the device selection logic of its corresponding production node in a graphical manner. Compared to describing the device selection logic using plain text or code, the graphical presentation of the device selection logic allows complex logical conditions, decision branches, and execution paths to be intuitively arranged using visual elements such as nodes and connections, forming a clear flowchart. This directly reduces the cognitive load and time cost for engineers when creating, reviewing, and understanding the device selection logic, improving efficiency from the source of strategy design and maintenance. Furthermore, during the selection of target devices at production nodes, the execution status of the production node and / or the execution process of the graphical device selection strategy can be displayed. This transforms the logical calculation process of the system's internal decision-making based on the strategy (such as which decision node is being executed, whether the conditions are met, the current candidate device list, etc.) into a visual information flow that operators can perceive in real time. This makes the previously invisible internal process visible, thereby achieving transparency in the execution process.

[0024] Based on the above concept, this specification provides a control method for batch control systems. The control method for batch control systems provided in this specification will be described exemplarily below with reference to the accompanying drawings.

[0025] Exemplary methods To be applied to, for example Figure 1 Taking a batch control system as an example, the embodiments in this specification provide a control method for a batch control system, such as... Figure 2 As shown, it includes: The batch production process is executed. The batch generation process includes multiple production nodes. At least one production node corresponds to a graphical device selection strategy. The graphical device selection strategy is used to describe the device selection logic of its corresponding production node in a graphical manner. Based on the graphical device selection strategy corresponding to the production node, a target device is selected from multiple devices corresponding to the production node as the device to execute the production node. Displays the execution status of the production node and / or the execution process of the graphical device selection strategy.

[0026] Combination Figure 1 The technical terms that may be involved in the batch control system and the implementation of this specification are described by way of example.

[0027] exist Figure 1 In a batch control system, a batch control system may include a batch server and an operator station. In some cases, a batch control system may also include a historical station, a network switch, and field control equipment.

[0028] Among them, batch servers (corresponding to) Figure 1 BATCH Server A and BATCH Server B in the diagram are industrial computers or servers that deploy the batch control core service software (batch service). They can be configured with primary and backup redundancy (as shown in BATCH Server A and BATCH Server B in the diagram) to ensure high availability. It is the "brain" of the system, responsible for recipe management, batch scheduling, logic execution, and the storage of the core strategy model (i.e., the graphical device selection strategy) in the methods provided in this specification, as well as the operation of the strategy execution engine and visualization data services.

[0029] Operator station (e.g., may include) Figure 1 The DCS operator station & BATCH dispatch station, DCS engineer station & BATCH editing station, etc., can be a computer used by engineers and operators, providing a graphical human-computer interaction interface, and can be used for strategy editing and production monitoring.

[0030] Historical sites (e.g., may include) Figure 1The DCS historical station A and DCS historical station B can be used to store historical data related to the production process, providing a basis for accident analysis, performance optimization and fault diagnosis.

[0031] Network switches (e.g., may include Figure 1 The A-network switch and B-network switch in the system can provide a highly reliable data communication channel between various devices.

[0032] Field control devices can include programmable logic controllers (PLCs), field control stations of distributed control systems (DCS), etc. They are directly connected to and control physical devices (such as pumps, valves, reactors, etc.), and can also collect and upload the status data of these physical devices.

[0033] After introducing the batch control system, other concepts that may be involved will be explained: Batch production: A production method that involves a series of processes in a limited batch.

[0034] Batch production process: In a batch control system, a predefined and sequentially executed series of process operations are used to produce a batch (or a single batch) of a specific product. It describes the entire production path from raw materials to finished product. For example, in the production of "a certain type of lubricating oil," a typical batch production process might include, in sequence: "feeding" -> "premixing" -> "heating and reaction" -> "cooling" -> "analysis and sampling" -> "finished product packaging." This ordered sequence of steps constitutes a batch production process.

[0035] Recipe: A master recipe that describes the resources, process steps, and parameters required to produce a batch of products.

[0036] Production node: A specific step or stage in a batch production process. It is a building block of the process, representing a relatively independent and identifiable production activity or control phase.

[0037] Equipment selection logic: To complete a certain production node, the rules, conditions and judgment sequence for dynamically determining which equipment to use from multiple physical devices with the same or similar functions.

[0038] Graphical equipment selection strategy: This describes the equipment selection logic for the corresponding production nodes in a graphical way. It is the concrete, visual carrier and implementation form of the equipment selection logic. Specific forms include, but are not limited to, flowcharts, tree diagrams, etc.

[0039] The device / target device that executes the production node: This can refer to the physical device entity that is ultimately selected and assigned to actually execute a specific production node task based on the device selection logic (graphical device selection strategy).

[0040] Unit: The physical device itself used to execute production nodes; it is a specific object on-site that can be controlled by a PLC.

[0041] Unit alias: A logical identifier for a class of units with the same function, that is, an identifier for a physical device that can be used to execute the same production node.

[0042] Configuration: Configuring the system in a non-programming manner using software tools.

[0043] OPC UA (Open Platform Communications Unified Architecture): A cross-platform communication protocol for industrial automation.

[0044] In the control method for batch control systems provided in this embodiment, a graphical device selection strategy is set for at least one production node in the batch production process. This graphical device selection strategy is used to describe the device selection logic of the corresponding production node in a graphical manner. Compared to describing the device selection logic in plain text or code, the graphical presentation of the device selection logic allows complex logical conditions, decision branches, and execution paths to be intuitively arranged using visual elements such as nodes and connections, forming a clear flowchart. This directly reduces the cognitive load and time cost for engineers when creating, reviewing, and understanding the device selection logic, improving efficiency from the source of strategy design and maintenance. Furthermore, during the selection of target devices at a production node, the execution status of the production node and / or the execution process of the graphical device selection strategy can be displayed. This transforms the logical calculation process of the system's internal decision-making based on the strategy (such as which decision node is being executed, whether the conditions are met, the current candidate device list, etc.) into a visual information flow that operators can perceive in real time. This makes the previously invisible internal process visible, thereby achieving transparency in the execution process.

[0045] In one implementation, a feasible generation process for a graphical device selection strategy is provided, specifically including: A graphical editing interface is displayed, which includes a predefined strategy node. The strategy node is used to configure at least one of logical conditions, filtering rules, and selection behaviors. The logical conditions are used to define the state of the equipment required by the production node. The filtering rules are used to define the rules for determining the target equipment from the equipment that meets the logical conditions. The selection behaviors are used to determine the target equipment based on the filtering rules. In response to the user's editing operation on the policy node, the graphical device selection policy is generated.

[0046] In this embodiment, by displaying a graphical editing interface including predefined policy nodes and supporting user editing operations on these policy nodes, a graphical device selection policy is generated, making the configuration process of the graphical device selection policy standardized and visualized. Specifically, the predefined policy nodes abstract the logical elements (conditions, rules, behaviors) required for device selection into reusable graphical components, allowing users to build policies by combining these standardized nodes instead of writing logic from scratch. This significantly reduces the technical threshold and cognitive burden of configuration. At the same time, the graphical editing interface and the editing operations on the nodes transform the originally abstract text expressions into intuitive interactions such as drag-and-drop and connection, enabling users to build and adjust the logical flow in a WYSIWYG manner. This greatly improves the accuracy, efficiency, and maintainability of policy configuration, fundamentally reducing the possibility of errors introduced by manually writing complex expressions.

[0047] In one implementation, generating the graphical device selection strategy in response to a user's edit operation on the strategy node includes: In response to a flowchart input by a user by dragging and connecting the policy nodes, a graphical device selection policy is generated, which describes the relationship between the various policy nodes in the flowchart.

[0048] In this implementation, on the one hand, the connection relationships between strategy nodes are expressed in the form of a flowchart, so that the complex selection logic with multiple steps and branches can be presented in a visual sequential flow that conforms to human thinking habits. This greatly enhances the overall readability, auditability, and logical coherence of the strategy, and reduces the cost of understanding and communication. On the other hand, this structured model based on nodes and connecting lines provides the strategy execution engine with a clear sequence of instructions that can be directly interpreted and executed sequentially. This avoids the complex syntax parsing and ambiguity elimination process required by traditional text expressions, thereby not only improving the reliability of strategy execution, but also laying the data structure foundation for accurate visual feedback of the execution process.

[0049] In one implementation, the process of displaying the execution status of the production node and / or the execution of the graphical device selection strategy includes: During the execution of device selection logic based on the graphical device selection strategy, the strategy execution engine generates visualization data in real time. The visualization data includes the execution status of the production node, the currently active strategy node, the condition judgment result, and at least one of the candidate devices in the list. The candidate device list includes devices obtained by filtering through at least some strategy nodes in the graphical device selection strategy; The strategy node is used to configure at least one of logical conditions, filtering rules, and selection behavior. The logical conditions are used to define the state of the equipment required by the production node. The filtering rules are used to define the rules for determining the target equipment from the equipment that meets the logical conditions. The selection behavior is used to determine the target equipment based on the filtering rules. The visualized data is displayed.

[0050] In this embodiment, by displaying visualized data in real time, the operation interface (e.g., a graphical monitoring interface of the operation station) can dynamically map the progress of internal logic, thus completely breaking the traditional "black box" selection process. The currently active policy nodes and condition judgment results contained in the visualized data transform abstract logical calculations into intuitively perceptible steps and conclusions, making the policy execution path and decision basis fully visible. In particular, the candidate device list includes "devices obtained after filtering through at least some policy nodes," which not only reveals the intermediate filtering results in real time, but more importantly, it can directly locate the fault point in the filtering process when the device selection result is abnormal (e.g., showing that a device is excluded because a certain condition is not met). This transforms the fault diagnosis method from global log backtracking to precise analysis of specific nodes and lists, greatly reducing the manpower cost required for users to analyze faults and improving the efficiency of operation and maintenance debugging and system maintainability.

[0051] In one embodiment, the batch control system includes: a batch server and an operator station, and the display of the visualized data includes: The batch server pushes the visualized data to the operator station; The operator station receives and renders the visualized data on its graphical monitoring interface. The rendering includes at least one of the following: highlighting the currently active strategy node, marking the filtering results on the strategy node that defines the filtering rules, and dynamically updating the candidate device list.

[0052] In this implementation, the client-server architecture of "batch server push - operator station receive rendering" ensures low latency and reliable transmission of the visualized data stream, enabling remote monitoring and centralized scheduling, and enhancing the system's deployment flexibility and scalability. The "highlighting" of the currently active node provides real-time visual focus, allowing operators to quickly locate the system's processing stage and significantly reducing the attention search cost during monitoring. Directly "annotating the filtering results" on policy nodes binds internal data (such as sorting order and filtering count) to logical locations, achieving contextual visualization of the decision-making basis and preventing misinterpretations. Dynamically updating the candidate device list ensures the real-time nature of intermediate states, making changes in the device pool readily apparent.

[0053] In one implementation, the method further includes: The execution process and results of the graphical device selection strategy, along with the corresponding timestamps, are recorded as historical data. In response to the user's playback command, the execution process is reproduced on the graphical monitoring interface based on the historical data.

[0054] In this implementation, the complete execution process and results are recorded along with timestamps, so that the logical path, intermediate state and final decision of each device selection are completely and orderly solidified, providing a data foundation for post-event attribution and inspection; while the function of reproducing the process on the graphical interface based on historical data transforms the static record into a dynamic, scenario-reproducible visual deduction, enabling operators or maintenance personnel to accurately review the whole picture of strategy execution and to trace the cause of the failure.

[0055] In one implementation, selecting a target device from among multiple devices corresponding to the production node based on the graphical device selection strategy corresponding to the production node includes: The structured strategy model corresponding to the graphical device selection strategy is parsed to obtain the execution sequence composed of strategy nodes. The strategy nodes are used to configure at least one of logical conditions, filtering rules and selection behavior. The logical conditions are used to define the state of the device required by the production node. The filtering rules are used to define the rules for determining the target device from the devices that meet the logical conditions. The selection behavior is used to determine the target device based on the filtering rules. According to the execution sequence, the logic defined by each strategy node is executed sequentially.

[0056] In this embodiment, a feasible process for determining a target device is provided. In this process: parsing the structured strategy model converts the graphical strategy into a machine-interpretable instruction set, eliminating the inherent ambiguity of natural language or text expressions; obtaining the execution sequence composed of strategy nodes solidifies the logical progression path, deconstructing the complex multi-step selection and decision-making process into a clear and manageable queue of steps, significantly reducing the scheduling complexity of the execution engine. The combination of these features transforms the target device selection process into a deterministic process with clear steps and predictable results, fundamentally improving the accuracy of batch production equipment scheduling and the overall system stability.

[0057] In one implementation, the step of sequentially executing the logic defined by each strategy node according to the execution sequence includes: For the condition judgment node in the execution sequence, real-time attribute data of the multiple devices are obtained from the field control system, and the real-time attribute data is calculated according to the logical conditions defined by the strategy node to filter out the devices that meet the conditions as candidate devices. Based on the filtering rules and selection behaviors defined by the policy node, the candidate devices are filtered to determine the target device.

[0058] In this implementation, acquiring real-time attribute data from the field control system ensures that the status information (such as idle, fault, and capacity) upon which equipment selection is based is strictly synchronized with the physical world's state. This avoids decision-making biases caused by data lag or disconnection, enabling the selection results to respond in real-time to dynamic changes in the production site. Furthermore, clearly distinguishing the execution process into a mechanism of "first filtering candidate equipment according to logical conditions, then determining the target equipment according to rules and behaviors" decomposes the complex selection logic into clearly defined, standardized stages, reducing overall logical complexity. Thus, while ensuring that the selection results accurately reflect the current production status, it also significantly improves the testability, maintainability, and overall system response reliability of the strategy logic.

[0059] The following will provide an exemplary description of a feasible implementation process of the control method for batch control systems provided in this specification, using a specific implementation method as an example: The control methods for batch control systems provided in this specification can be implemented using corresponding software functional modules, which can work together on the batch server and operator station of the batch control system.

[0060] Specifically, these software functional modules may include a policy configuration module, a policy execution engine, and a runtime visualization module. The policy configuration module can provide a graphical editing interface (located at the operator station), allowing users to build device selection policies by dragging and dropping predefined policy nodes. Policy nodes can be used to configure logical conditions, filtering rules, and selection behaviors. Based on their purpose, policy nodes can be categorized as follows: Start node: The starting point for strategy execution.

[0061] Conditional judgment node: Configure logical conditions (such as device.state == "idle").

[0062] Device filtering node: Configure filtering rules (e.g., sort by "idle time" in descending order).

[0063] Action node: Defines the selection behavior (such as selecting the device ranked first).

[0064] Implementation: The graphical device selection policy edited by the user on the operator station is sent to the batch server via the network. The policy configuration module of the batch server receives it and converts it into a structured policy model (such as JSON or XML format), and finally stores it in the database.

[0065] The policy execution engine can include functions such as interpreting and executing configured structured policy models (i.e., graphical device selection policies) during production runtime.

[0066] The policy execution engine can run as an embedded component of the services provided on the batch server. When the batch production process reaches the associated production node, the policy execution engine can perform the following functions: Load the corresponding structured strategy model from the database; Obtain the current attributes of all candidate devices from field control devices (such as PLCs) through real-time data interfaces (such as OPC UA); Following the logic of the structured strategy model, the equipment screening process is carried out step by step, executing the judgment of logical conditions and the screening rules. The final selected target device identifier is output to the production execution system.

[0067] The runtime visualization module can display the execution process of a graphical device selection strategy in real time. This module can adopt a client-server architecture, where the server (i.e., the batch server) can be integrated into the strategy execution engine, responsible for visualizing the data during the mobile device execution process. The client (on the operator station) can retrieve visualization data from the server via a subscription / push mechanism and render it on a graphical monitoring interface similar to the configuration interface. Examples include highlighting the currently executing strategy node, displaying True or False judgment results next to conditional judgment nodes, and dynamically updating the device list.

[0068] The following describes a feasible process for implementing the control method for batch control systems provided in the embodiments of this specification: S1. Configuration: such as Figure 3 As shown, engineers drag and drop strategy nodes in the graphical editing interface of the operator station to draw a graphical equipment selection strategy (e.g., "first find idle reactors with a capacity ≥1000L, then select the one with the longest idle time"), and associate it with the production node in the recipe. This strategy is converted into a structured strategy model and saved to the database of the batch server. Figure 3 The recipe program on the left represents a batch production process, which may include two production nodes where materials are added to the reactor. The dynamic selection strategy on the right is the interface for configuring the graphical device selection strategy. In this step, engineers can drag and drop different strategy nodes (start node, conditional decision node, device selection node, and action node, etc.) to create a graphical device selection strategy for a specific production node (e.g., the first production node to add materials to the reactor). Figure 3 The dynamic selection strategy interface includes START, which can represent the start node; judgment conditions 1 to 4 can represent different condition judgment nodes; flow Start represents the flow after the start node; and R2101A, R2101B, etc. can represent different physical devices (i.e., units). Figure 3 The connecting lines in the diagram can represent the relationships between physical devices and policy nodes. (See reference) Figure 4 , Figure 4 The configuration condition judgment node is shown (specifically...) Figure 3 The diagram shows a feasible interface for judgment condition 1). In this diagram, unitclass.Idle_Time and unitclass.p1 can represent the attributes of physical devices (i.e., units). The comparison operators (>, >=) and the right-hand value column represent the constituent elements of the logical condition. Together they define a judgment rule, such as: unitclass.idle_time > target value, unitclass.capacity >= 1000, etc.

[0069] S2. Triggering and Loading: The batch production process begins, and the batch server executes the recipe. When the process reaches the production node configured with the graphical device selection strategy, the strategy execution engine is invoked, and the corresponding structured strategy model is loaded from the database.

[0070] S3. Execution and Visualization: Reference Figures 5-8 The strategy execution engine executes the graphical device selection strategy step by step. Figure 5 The image shows a schematic diagram of the graphical monitoring interface on the operator's station during the production operation phase. The table on the left shows the detailed visualization data. The Name column lists the entities participating in the current device selection logic. Condition 1 and Condition 2 correspond to policy nodes (specifically, condition judgment nodes) in the graphical device selection strategy. R2101A and R2101B correspond to physical devices in the candidate device list.

[0071] The Status column displays the execution status of each entity. "Running" indicates that the policy node is being computed by the policy execution engine. "Idle" displays the real-time attributes (status) of the physical devices in the candidate device list.

[0072] The associated unit name column clarifies the logical relationship between the policy node and the physical devices in the candidate device list, such as the judgment condition 1 being that device R2101A is being evaluated.

[0073] The structure of the graphical device selection strategy is shown on the right side of the table, which, together with the table on the left, shows the execution status of the graphical device selection strategy.

[0074] When the execution reaches a strategy node configured with logical conditions (such as "judgment node A"), the engine obtains the device status from the field control device (such as a PLC) and calculates the logical conditions. Figure 6 , Figure 6 The interface for manual mode condition switching is shown. This interface demonstrates the feasible process of real-time calculation and diagnosis of condition judgment nodes. The switching name, "Judgment Condition 1," indicates that the strategy execution engine is executing a strategy node named "Judgment Condition 1." The switching result, "Not Satisfied," indicates that the current state does not meet the filtering rule corresponding to Judgment Condition 1. The actual values ​​in the table, such as 0.0000, represent real-time attribute data. These values ​​can be real-time attribute data from multiple physical devices obtained by the strategy execution engine from the field control system.

[0075] Simultaneously, the operator station's graphical monitoring interface highlights the policy node in real time and displays the condition determination result as True. (Reference) Figure 7 , Figure 7 The results summary interface after executing the graphical device selection strategy is displayed.

[0076] When the engine executes a policy node configured with filtering rules (such as "Filter Node B"), it sorts the candidate devices.

[0077] The operator station interface dynamically updates the sorted list of candidate devices. (Reference) Figure 8 , Figure 8 A schematic diagram of the interface for selecting device operation based on the execution result of the graphical device selection strategy is shown.

[0078] Decision-making and control: The engine executes all policy nodes and outputs the final target device. The batch server sends this instruction to the field control equipment, which then controls the physical equipment to start production.

[0079] Historical records: The entire execution process and results of the graphical device selection strategy, along with the corresponding timestamps, are recorded as historical data and stored in the database for playback and analysis.

[0080] In summary, the control method for batch control systems provided in this specification brings significant technological advancements by introducing centralized graphical device selection strategy configuration and real-time visual monitoring. First, by integrating fragmented and obscure text expressions into an intuitive graphical device selection strategy, engineers no longer need to switch between multiple configuration interfaces or perform complex logic piecing together when configuring, reviewing, and maintaining device selection logic. This greatly improves the efficiency and accuracy of strategy management, fundamentally reducing production risks caused by configuration errors. Second, during production operation, by displaying the execution status and strategy execution process, the original "black box" selection process is transformed into a "white box" visual process. Operators can instantly understand the reasons for device selection, and in case of an anomaly, they can quickly locate the problem as to whether it lies in the device status, strategy logic, or other aspects, significantly shortening fault diagnosis time and improving the reliability and maintainability of the production system.

[0081] Exemplary device In one exemplary embodiment of this specification, a device selection apparatus for a batch control system is also provided, the device selection apparatus for the batch control system comprising: The first module is used to execute the batch production process, which includes multiple production nodes. At least one production node corresponds to a graphical device selection strategy. The graphical device selection strategy is used to describe the device selection logic of its corresponding production node in a graphical manner. The second module is used to select a target device as the device to execute the production node from among multiple devices corresponding to the production node, based on the graphical device selection strategy corresponding to the production node. The third module is used to display the execution status of the production node and / or the execution process of the graphical device selection strategy.

[0082] Specific limitations regarding the device selection mechanism applied to batch control systems can be found in the limitations regarding control methods applied to batch control systems described above, and will not be repeated here. Each module in the aforementioned device selection mechanism for batch control systems can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in or independent of the processor in a computer device in hardware form, or stored in the memory of a computer device in software form, so that the processor can call and execute the operations corresponding to each module.

[0083] Exemplary System One embodiment of this specification also provides a batch control system, comprising: a batch server and an operator station; wherein, The batch server is configured to execute a batch production process, which includes multiple production nodes. At least one production node corresponds to a graphical device selection strategy, which is used to describe the device selection logic of its corresponding production node in a graphical manner. Based on the graphical device selection strategy corresponding to the production node, a target device is selected from multiple devices corresponding to the production node as the device to execute the production node. Based on the operator station, the execution status of the production node and / or the execution process of the graphical device selection strategy are displayed.

[0084] For specific limitations regarding the batch control system performing the control method applied to the batch control system described in any of the above embodiments, please refer to the relevant descriptions above, which will not be repeated here.

[0085] Exemplary computing device Another embodiment of this application also proposes a computing device, see [link to relevant documentation] Figure 9 As shown, an exemplary embodiment of this specification also provides a computing device, including: a memory and a processor, the memory storing a computer program, the processor executing the computer program to perform steps in a control method applied to a batch control system according to various embodiments of this specification as described in the foregoing embodiments.

[0086] The internal structure of the computing device can be as follows: Figure 9As shown, the computing device includes a processor, memory, network interface, and input devices connected via a system bus. The processor provides computing and control capabilities. The memory includes a non-volatile storage medium and internal memory. The non-volatile storage medium stores an operating system and computer programs. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage medium. The network interface is used to communicate with external terminals via a network connection. When the computer program is executed by the processor, it follows the steps of the control method applied to a batch control system according to various embodiments of this specification, as described in the above embodiments.

[0087] The processor may include the main processor, as well as baseband chips, modems, etc.

[0088] It is understood that the processor in the embodiments of this specification can be an integrated circuit chip with signal processing capabilities. In implementation, each step of the above method embodiments can be completed by integrated logic circuits in the processor's hardware or by instructions in software form. The processor can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this specification. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this specification can be directly implemented by a hardware decoding processor, or by a combination of hardware and software modules in the decoding processor. The software modules can reside in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. This storage medium is located in memory; the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above methods.

[0089] It is understood that the memory in the embodiments of this specification may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. Non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory may be random access memory (RAM). It should be noted that the memory in the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0090] Input devices may include devices that receive data and information input by the user, such as keyboards, mice, cameras, scanners, light pens, voice input devices, touch screens, pedometers, or gravity sensors.

[0091] Output devices may include devices that allow information to be output to the user, such as displays, printers, speakers, etc.

[0092] The communication interface may include any transceiver-like device for communicating with other devices or communication networks, such as Ethernet, Radio Access Network (RAN), Wireless Local Area Network (WLAN), etc.

[0093] The computing device may also include a display component and a voice component. The display component may be a liquid crystal display screen or an e-ink display screen. The input device of the computing device may be a touch layer covering the display component, or a button, trackball or touchpad set on the casing of the computing device, or an external keyboard, touchpad or mouse, etc.

[0094] Those skilled in the art will understand that Figure 9 The structures shown are merely block diagrams of some structures related to the solutions in this specification and do not constitute a limitation on the computing devices on which the solutions in this specification are applied. Specific computing devices may include more or fewer components than those shown in the figures, or combine certain components, or have different component arrangements.

[0095] Exemplary computer program products and storage media In addition to the methods and devices described above, the control methods for batch control systems provided in the embodiments of this specification can also be computer program products, which include computer program instructions that, when executed by a processor, cause the processor to perform the steps in the control methods for batch control systems according to various embodiments of this specification as described in the "Exemplary Methods" section above.

[0096] The aforementioned computer program product can be implemented through hardware, software, or a combination thereof. In one optional embodiment, the computer program product is specifically embodied in a computer storage medium; in another optional embodiment, the computer program product is specifically embodied in a software product, such as a software development kit (SDK), etc.

[0097] The computer program product described herein can be written in any combination of one or more programming languages ​​to perform the operations of the embodiments described herein. These programming languages ​​include object-oriented programming languages ​​such as Java and C++, as well as conventional procedural programming languages ​​such as C or similar languages. The program code can be executed entirely on the user's computing device, partially on the user's computing device, as a standalone software package, partially on the user's computing device and partially on a remote computing device, or entirely on a remote computing device or server.

[0098] Furthermore, embodiments of this specification also provide a computer-readable storage medium having a computer program stored thereon, the computer program being executed by a processor of the steps in the control method applied to a batch control system according to various embodiments of this specification as described in the "Exemplary Methods" section above.

[0099] 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 specification 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.

[0100] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0101] The embodiments described above are merely illustrative of several implementation methods outlined in this specification. While the descriptions are specific and detailed, they should not be construed as limiting the scope of the solutions provided in this specification. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this specification, and these all fall within the scope of protection of this specification. Therefore, the scope of protection for this patent should be determined by the appended claims.

Claims

1. A control method applied to a batch control system, characterized in that, include: The batch production process is executed. The batch generation process includes multiple production nodes. At least one production node corresponds to a graphical device selection strategy. The graphical device selection strategy is used to describe the device selection logic of its corresponding production node in a graphical manner. Based on the graphical device selection strategy corresponding to the production node, a target device is selected from multiple devices corresponding to the production node as the device to execute the production node. Displays the execution status of the production node and / or the execution process of the graphical device selection strategy.

2. The method according to claim 1, characterized in that, The generation process of the graphical device selection strategy includes: A graphical editing interface is displayed, which includes a predefined strategy node. The strategy node is used to configure at least one of logical conditions, filtering rules, and selection behaviors. The logical conditions are used to define the state of the equipment required by the production node. The filtering rules are used to define the rules for determining the target equipment from the equipment that meets the logical conditions. The selection behaviors are used to determine the target equipment based on the filtering rules. In response to the user's editing operation on the policy node, the graphical device selection policy is generated.

3. The method according to claim 2, characterized in that, The step of generating the graphical device selection strategy in response to a user's editing operation on the strategy node includes: In response to a flowchart input by a user by dragging and connecting the policy nodes, a graphical device selection policy is generated, which describes the relationship between the various policy nodes in the flowchart.

4. The method according to claim 1, characterized in that, The process of displaying the execution status of the production node and / or the execution of the graphical device selection strategy includes: During the execution of device selection logic based on the graphical device selection strategy, the strategy execution engine generates visualization data in real time. The visualization data includes the execution status of the production node, the currently active strategy node, the condition judgment result, and at least one of the candidate devices in the list. The candidate device list includes devices obtained by filtering through at least some strategy nodes in the graphical device selection strategy; The strategy node is used to configure at least one of logical conditions, filtering rules, and selection behavior. The logical conditions are used to define the state of the equipment required by the production node. The filtering rules are used to define the rules for determining the target equipment from the equipment that meets the logical conditions. The selection behavior is used to determine the target equipment based on the filtering rules. The visualized data is displayed.

5. The method according to claim 4, characterized in that, The batch control system includes a batch server and an operator station, and the display of the visualized data includes: The batch server pushes the visualized data to the operator station; The operator station receives and renders the visualized data on its graphical monitoring interface. The rendering includes at least one of the following: highlighting the currently active strategy node, marking the filtering results on the strategy node that defines the filtering rules, and dynamically updating the candidate device list.

6. The method according to any one of claims 1 to 5, characterized in that, Also includes: The execution process and results of the graphical device selection strategy, along with the corresponding timestamps, are recorded as historical data. In response to the user's playback command, the execution process is reproduced on the graphical monitoring interface based on the historical data.

7. The method according to claim 1, characterized in that, The step of selecting a target device from multiple devices corresponding to the production node based on the graphical device selection strategy corresponding to the production node includes: The structured strategy model corresponding to the graphical device selection strategy is parsed to obtain the execution sequence composed of strategy nodes. The strategy nodes are used to configure at least one of logical conditions, filtering rules and selection behavior. The logical conditions are used to define the state of the device required by the production node. The filtering rules are used to define the rules for determining the target device from the devices that meet the logical conditions. The selection behavior is used to determine the target device based on the filtering rules. According to the execution sequence, the logic defined by each strategy node is executed sequentially.

8. The method according to claim 7, characterized in that, The step of executing the logic defined by each strategy node sequentially according to the execution sequence includes: For the condition judgment node in the execution sequence, real-time attribute data of the multiple devices are obtained from the field control system, and the real-time attribute data is calculated according to the logical conditions defined by the strategy node to filter out the devices that meet the conditions as candidate devices. Based on the filtering rules and selection behaviors defined by the policy node, the candidate devices are filtered to determine the target device.

9. A batch control system, characterized in that, include: Batch servers and operator stations; among them, The batch server is configured to execute a batch production process, which includes multiple production nodes. At least one production node corresponds to a graphical device selection strategy, which is used to describe the device selection logic of its corresponding production node in a graphical manner. Based on the graphical device selection strategy corresponding to the production node, a target device is selected from multiple devices corresponding to the production node as the device to execute the production node. Based on the operator station, the execution status of the production node and / or the execution process of the graphical device selection strategy are displayed.

10. A computing device, characterized in that, It includes 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 control method for a batch control system as described in any one of claims 1 to 8.

11. A storage medium, characterized in that, The storage medium stores a computer program, which, when executed by a processor, implements the control method for batch control systems as described in any one of claims 1 to 8.

12. A computer program product, characterized in that, The computer program product includes a computer program, which, when executed by a processor, implements the control method for batch control systems as described in any one of claims 1 to 8.

Images