Layered process editing method and system based on automatic verification of process steps

Abstract

The application provides a layered process editing method and system based on process step automatic verification, and relates to the technical field of equipment automation. The method comprises the following steps: obtaining process creation information, device configuration data of a target automatic process equipment, and consumable configuration data adapted to the target automatic process equipment; performing layered modeling processing based on the process creation information, the device configuration data, and the consumable configuration data to obtain a layered process model; performing parameter opening processing on the layered process model based on open parameter information to obtain an editable process model; and generating a process data package based on output state descriptions of adjacent sub-processes, input state constraints, the device configuration data, and the consumable configuration data. According to the embodiment of the application, adjacent step connection abnormalities can be identified before equipment execution, and the occurrence probability of process configuration errors and equipment execution abnormalities can be reduced.

Description

Technical Field

[0001] This invention relates to the field of equipment automation technology, and in particular to a hierarchical process editing method and system based on automatic verification of process steps. Background Technology

[0002] Automated process equipment is widely used in biological sample processing, cell preparation, liquid transport, centrifugation, temperature control, and culture. This type of equipment typically includes a pump, control valves, liquid piping, containers, centrifugation mechanisms, temperature control mechanisms, and detection components. It sequentially executes process steps such as liquid inlet, liquid outlet, centrifugation, mixing, temperature control, culture, and venting according to a pre-set process flow. Currently, the process flow of automated process equipment is usually pre-programmed and embedded in the control software by the equipment manufacturer. Users primarily control the equipment by calling the preset processes.

[0003] As the objects being processed, sample types, consumable structures, and process conditions change, users need to adjust process steps, execution sequences, and process parameters. Existing process editing methods typically organize process content in the form of single flows or continuous instructions, making it difficult to clearly distinguish between complete processes, partial processes, and operations that equipment can directly execute. When the process content is complex, the hierarchical and calling relationships between process steps are difficult to maintain, and partial processes are difficult to reuse in different process flows. Furthermore, the lack of effective distinction between underlying control parameters and the process parameters that users need to adjust easily leads to problems such as irrelevant parameters being modified or necessary parameters being difficult to adjust.

[0004] Furthermore, existing process editing methods primarily rely on users' experience to manually judge whether preceding and following process steps can be seamlessly connected. This often lacks automatic verification of the states before and after adjacent process steps, increasing the error rate as the number of processes increases. When the fluid position, fluid volume, pipeline status, or equipment operating status after one step does not meet the requirements of the next step, these problems are often only discovered after the process has been issued to the equipment and is actually running. Simultaneously, the process content may also be inconsistent with the execution capabilities of the target automated process equipment or the structure of applicable consumables, leading to the process failing to execute correctly.

[0005] Therefore, how to hierarchically edit complex processes and automatically verify the connection between adjacent process steps in conjunction with the target automated process equipment and applicable consumables before process execution is a technical problem that needs to be solved by existing technologies. Summary of the Invention

[0006] This invention provides a hierarchical process editing method and system based on automatic verification of process steps. By organizing the process content in layers, editing in a controlled manner, verifying the connection between steps, and generating execution data, the resulting process is matched with the target automated process equipment and applicable consumables. It can also identify abnormal connections between adjacent steps before the equipment is executed, reducing the probability of process configuration errors and equipment execution abnormalities.

[0007] In a first aspect, the present invention provides a layered process editing method based on automatic verification of process steps, comprising the following steps: Acquire process creation information, equipment configuration data of the target automated process equipment, and consumable configuration data adapted to the target automated process equipment; Based on the process creation information, the equipment configuration data, and the consumable configuration data, a hierarchical modeling process is obtained; wherein, the hierarchical process model includes at least a main process, sub-processes, and basic items, the main process includes at least sub-processes arranged in execution order, the sub-processes include at least one of basic items and nested sub-processes, and the basic items are process operations that the target automated process equipment can directly execute; The input state constraints, output state descriptions, and open parameter information of each sub-process in the hierarchical process model are obtained, and the hierarchical process model is processed to open parameters based on the open parameter information to obtain an editable process model. Based on the output state descriptions and input state constraints of adjacent sub-processes, the equipment configuration data, and the consumable configuration data, the editable process model is subjected to step matching verification to obtain the step verification results. When the verification result of the step meets the preset pass conditions, the editable process model is recursively expanded to obtain the basic item execution sequence, and a process data package is generated based on the equipment configuration data, the consumable configuration data and the basic item execution sequence.

[0008] Secondly, the present invention also provides a layered process editing system based on automatic verification of process steps, comprising the following modules: The acquisition module is used to acquire process creation information, equipment configuration data of the target automated process equipment, and consumable configuration data adapted to the target automated process equipment. A hierarchical modeling module is used to perform hierarchical modeling processing based on the process creation information, the equipment configuration data, and the consumable configuration data to obtain a hierarchical process model; wherein, the hierarchical process model includes at least a main process, sub-processes, and basic items, the main process includes at least sub-processes arranged in execution order, the sub-processes include at least one of basic items and nested sub-processes, and the basic items are process operations that the target automated process equipment can directly execute; The parameter opening module is used to obtain the input state constraints, output state descriptions and open parameter information of each sub-process in the hierarchical process model, and to perform parameter opening processing on the hierarchical process model based on the open parameter information to obtain an editable process model. The step verification module is used to perform step matching verification on the editable process model based on the output state description of adjacent sub-processes, input state constraints, equipment configuration data and consumable configuration data, and obtain step verification results. The recursive expansion module is used to recursively expand the editable process model when the step verification result meets the preset pass conditions, to obtain the basic item execution sequence, and to generate a process data package based on the equipment configuration data, the consumable configuration data and the basic item execution sequence.

[0009] Thirdly, the present invention also provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the layered process editing method based on automatic verification of process steps as described above.

[0010] Fourthly, the present invention also provides a non-transitory computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the layered process editing method based on automatic verification of process steps as described above.

[0011] Fifthly, the present invention also provides a computer program product, including a computer program that, when executed by a processor, implements the layered process editing method based on automatic verification of process steps as described above.

[0012] This invention provides a hierarchical process editing method and system based on automatic verification of process steps. The method acquires process creation information, equipment configuration data of the target automated process equipment, and consumable configuration data compatible with the target automated process equipment. Based on the process creation information, equipment configuration data, and consumable configuration data, hierarchical modeling is performed to obtain a hierarchical process model. The hierarchical process model includes at least a main process, sub-processes, and basic items. The main process includes at least sub-processes arranged in execution order. Each sub-process includes at least one of basic items and nested sub-processes. The basic items are process operations that the target automated process equipment can directly execute. The hierarchical process model extracts the input state constraints, output state descriptions, and open parameter information of each sub-process. Based on the open parameter information, the hierarchical process model undergoes parameter opening processing to obtain an editable process model. Based on the output state descriptions, input state constraints, equipment configuration data, and consumable configuration data of adjacent sub-processes, the editable process model undergoes step matching verification to obtain step verification results. When the step verification results meet preset pass conditions, the editable process model undergoes recursive expansion processing to obtain a basic item execution sequence. Based on the equipment configuration data, consumable configuration data, and basic item execution sequence, a process data package is generated. By hierarchically organizing, controlling, verifying, and generating execution data for the process content, the resulting process matches the target automated process equipment and applicable consumables. Furthermore, it can identify abnormalities in the connection between adjacent steps before equipment execution, reducing the probability of process configuration errors and equipment execution anomalies. Attached Figure Description

[0013] To more clearly illustrate the technical solutions in this invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of this invention. For those skilled in the art, other drawings can be obtained from these drawings without creative effort.

[0014] Figure 1 This is a flowchart illustrating the layered process editing method based on automatic verification of process steps provided by the present invention.

[0015] Figure 2 This is a schematic diagram of the structure of the layered process editing system based on automatic verification of process steps provided by the present invention.

[0016] Figure 3 This is a schematic diagram of the structure of the electronic device provided by the present invention. Detailed Implementation

[0017] To make the objectives, technical solutions, and advantages of this invention clearer, the technical solutions of this invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this invention. All other embodiments obtained by those skilled in the art based on the embodiments of this invention without creative effort are within the scope of protection of this invention.

[0018] All actions involving the acquisition of signal information or data in this invention are carried out in accordance with the relevant data protection laws and policies of the country where the location is situated, and with the authorization granted by the relevant system owner.

[0019] The following is combined with Figures 1-3 This invention describes a hierarchical process editing method and system based on automatic verification of process steps. By organizing the process content in layers, editing in a controlled manner, verifying the connection between steps, and generating execution data, the resulting process is matched with the target automated process equipment and applicable consumables. It can also identify abnormal connections between adjacent steps before the equipment is executed, thereby reducing the probability of process configuration errors and equipment execution abnormalities.

[0020] The following description, in conjunction with the automated process equipment, process editing software, and corresponding process execution scenarios involved in this invention, further illustrates the hierarchical process editing method based on automatic verification of process steps of this invention: The automated process equipment can be a cell processing device, a biological sample processing device, a liquid dispensing device, a centrifugation device, or a comprehensive processing device that simultaneously possesses liquid delivery, centrifugation, mixing, temperature control, and culture functions.

[0021] The automated process equipment includes at least an equipment controller and an execution component that is communicatively connected to the equipment controller. The execution component may include one or more of the following: a peristaltic pump, a pinch valve, a rotary valve, a centrifugal mechanism, a mixing mechanism, a temperature control mechanism, a shaking table mechanism, and a gas control mechanism. The equipment controller may also be connected to a bubble sensor, a temperature sensor, a speed sensor, a pressure sensor, and a liquid volume detection component to obtain the actual equipment status during the process operation.

[0022] The hierarchical process editing method based on automatic verification of process steps described in this invention can be executed by process editing software installed in an electronic device, which can be a computer running a Windows operating system. The process editing software is responsible for process creation, process arrangement, parameter configuration, process step verification, simulation operation, process data package generation, and process export. The target automated process equipment is responsible for verifying, parsing, and executing the process data package. The process editing software and the target automated process equipment can transmit the process data package via removable storage media, local area network, serial communication interface, or other data transmission methods.

[0023] Existing process editing methods typically arrange multiple equipment control operations directly according to time sequence, lacking a clear hierarchical division between complete processes, partial processing procedures, and directly executed equipment operations. Furthermore, whether adjacent processing procedures possess continuous fluid, liquid path, and equipment states still largely relies on manual experience for judgment. This invention establishes a hierarchical relationship between the main process, sub-processes, and basic items, and further establishes structured input state constraints and output state descriptions between sub-processes. This enables process arrangement, step verification, simulation operation, and equipment execution to adopt a unified data structure, thereby forming a continuous technical processing flow from process editing to equipment control.

[0024] Figure 1 This is a flowchart illustrating a hierarchical process editing method based on automatic verification of process steps provided by the present invention, as shown below. Figure 1 As shown, the method may include, but is not limited to, steps S100 to S500: S100, acquire process creation information, equipment configuration data of the target automated process equipment, and consumable configuration data adapted to the target automated process equipment; S200, based on the process creation information, the equipment configuration data, and the consumable configuration data, perform hierarchical modeling processing to obtain a hierarchical process model; wherein, the hierarchical process model includes at least a main process, sub-processes, and basic items, the main process includes at least sub-processes arranged in execution order, the sub-processes include at least one of basic items and nested sub-processes, and the basic items are process operations that the target automated process equipment can directly execute; S300, obtain the input state constraints, output state descriptions and open parameter information of each sub-process in the hierarchical process model, and perform parameter opening processing on the hierarchical process model based on the open parameter information to obtain an editable process model; S400, based on the output state description of adjacent sub-processes, input state constraints, equipment configuration data and consumable configuration data, perform step matching verification on the editable process model to obtain step verification results; S500, when the verification result of the step meets the preset pass conditions, the editable process model is recursively expanded to obtain the basic item execution sequence, and a process data package is generated based on the equipment configuration data, the consumable configuration data and the basic item execution sequence.

[0025] In some embodiments of the present invention, after the step of generating a process data package based on the equipment configuration data, the consumable configuration data, and the basic item execution sequence, the method further includes: performing execution processing on the process data package through the target automated process equipment to obtain a process execution result.

[0026] In some embodiments of the present invention, after the process editing software starts, it first loads local basic configuration data and displays function entries such as Create Process, My Processes, and Recent Processes on the main interface. After entering the Create Process interface, the user selects the process type, target equipment model, and target consumable model, and enters the process name. The user can also select an existing process as a reference process. The process editing software summarizes the above information to form process creation information. The process creation information may include process identifier, process name, process type, reference process identifier, target equipment model, target consumable model, software version, and creation time. Among them, the process identifier is used to uniquely identify the current process in process saving, version management, and equipment execution logs.

[0027] The equipment configuration data for the target automated process equipment can be pre-saved in the equipment capability configuration file. This data must at least include the equipment model, actuator type, actuator number, execution capability range, sensor configuration, and control protocol version. For example, for a centrifuge mechanism, the configuration data can include the allowable speed range, allowable acceleration range, allowable deceleration range, allowable rotation direction, and allowable liquid volume range in the centrifuge cup; for a peristaltic pump, the configuration data can include the pump number, allowable speed range, delivery direction, and associated piping; for a pinch valve, the configuration data can include the valve number, control status, and associated piping. The execution capability range refers to the parameter boundaries that the target automated process equipment is allowed to execute. The process editing software adheres to these parameter boundaries to limit the process content during parameter editing, step verification, and simulation operation.

[0028] Consumable configuration data describes the physical structure and liquid transfer relationships of the current consumables. This data can include consumable model, bag identifier, container identifier, container capacity, port identifier, tubing connections, valve-to-tubing correspondence, pump-to-tubing correspondence, and prohibited simultaneous use of fluid path combinations. Taking cell processing consumables as an example, consumables may include sample bags, washing solution bags, culture medium bags, waste liquid bags, and centrifuge cups. Each bag or container is connected via tubing and ports. Pinch valves control the on / off state of the corresponding tubing, and peristaltic pumps provide the power for liquid transfer. After reading the consumable configuration data corresponding to the target consumable model, the process editing software can identify whether there are available fluid paths between containers and determine the pumps and valves that need to be controlled based on the fluid paths.

[0029] Furthermore, the process editing software establishes a hierarchical process model based on process creation information, equipment configuration data, and consumable configuration data. The hierarchical process model is a data structure used to represent the hierarchical relationships, calling relationships, and execution order relationships between process nodes, and includes at least a main process, sub-processes, and basic items. The main process represents a complete set of processing flows that the target automated process equipment needs to complete. For example, the sample processing main process may include sample import sub-processes, washing sub-processes, centrifugation sub-processes, supernatant discharge sub-processes, cell resuspension sub-processes, and temperature-controlled culture sub-processes. Sub-processes represent local processing procedures that can be configured independently and repeatedly invoked. A sub-process may include one or more basic items, and may also nest other sub-processes. Basic items are process operations that the target automated process equipment can directly execute, such as liquid inflow / outflow, centrifugation, mixing, temperature control, waiting, venting, and shaker control.

[0030] In one specific embodiment, the centrifugal separation subprocess includes a liquid inlet basic item, a centrifugation basic item, a waiting basic item, and a liquid discharge basic item. The liquid inlet basic item records the source container, target container, liquid volume, liquid flow rate, pump number, and valve opening / closing relationships; the centrifugation basic item records the target rotational speed, acceleration, centrifugation time, and deceleration; the waiting basic item records the waiting time and waiting termination conditions; and the liquid discharge basic item records the source container, target container, discharge volume, and discharge termination conditions. During the equipment execution phase, each basic item is converted into pump control commands, valve control commands, centrifugation mechanism control commands, or waiting control commands, respectively. Therefore, the basic item is both the smallest arrangement unit in the process editing process and the smallest execution unit in the process data package.

[0031] Furthermore, the process editing software acquires the input state constraints, output state descriptions, and open parameter information for each subprocess. Input state constraints define the fluid, consumable, and equipment states required before the subprocess begins execution, while output state descriptions record the fluid, consumable, and equipment states after the subprocess is completed. Taking the centrifugal separation subprocess as an example, its input state constraints may include a predetermined range of liquid within the centrifuge cup, the centrifuge mechanism being stopped, and the inlet / outlet valves connected to the centrifuge cup being closed. Its output state description may include the liquid still being present in the centrifuge cup, the centrifugation process being completed, and the centrifuge mechanism rotating at zero speed.

[0032] Open parameter information is used to define which fundamental parameters within a sub-process are allowed to be adjusted at the main process level. Sub-processes may include port numbers, valve numbers, pump numbers, fluid path selection methods, and sensor termination conditions directly related to the underlying control logic. Any modification to these parameters could alter verified fluid path control relationships; therefore, they can be kept closed. Parameters that vary with product process requirements, such as centrifuge speed, centrifugation time, liquid volume, and liquid flow rate, can be set to open. The process editing software creates corresponding editable parameter items in the main process editing interface based on the open parameter information and records the access relationships between each editable parameter item and the fundamental parameters within the sub-process, thus forming an editable process model.

[0033] Subsequently, the process editing software performs step matching verification on adjacent sub-processes according to the execution order of the sub-processes in the main process. This step matching verification does not involve a textual comparison of process names, but rather a structured comparison of the output state description of the preceding sub-process and the input state constraints of the following sub-process. It also considers equipment configuration data to determine if the equipment status meets the requirements and consumable configuration data to determine if the liquid path relationship is valid. For example, if the fluid is in the centrifuge cup after the preceding sub-process is completed, and the following sub-process requires the supernatant to be discharged from the centrifuge cup, and there is a liquid path from the centrifuge cup to the waste bag in the consumables, then the adjacent sub-processes can be connected. However, if the fluid is in the sample bag after the preceding sub-process is completed, and the following process requires direct centrifugation of the liquid in the centrifuge cup, there is a lack of liquid transfer between the preceding and following steps, and the corresponding step verification results indicate a mismatch.

[0034] It should be noted that the preset pass conditions can be configured according to the process type and the importance of the steps. In one implementation, when all necessary sub-processes in the main process pass the step matching verification, the step verification result meets the preset pass conditions; when there is a non-blocking prompt between optional sub-processes, the process editing software can allow continued editing, but the corresponding problem handling still needs to be completed before the process data package is generated. Through this processing, problems such as inconsistent fluid positions, unmet liquid volume ranges, unconnected liquid paths, and unmet equipment status can be detected before the equipment actually executes.

[0035] After the step verification results meet the preset pass conditions, the process editing software reads each sub-process and its internal nodes layer by layer, starting from the main process. It then expands the nested sub-processes into basic items arranged according to the actual execution order, forming a basic item execution sequence. Recursive expansion means that when reading a sub-process node, if its subordinate nodes are also sub-processes, it continues reading the subordinate nodes of that sub-process until a basic item node is read. During recursive expansion, the main process, sub-processes, nesting level, and node source path of each basic item are preserved, allowing subsequent equipment execution logs to trace back to the original process structure.

[0036] The process editing software encapsulates the execution sequence of basic items by combining equipment configuration data and consumable configuration data. The process data package can include basic process information, equipment compatibility information, consumable compatibility information, basic item execution data, parameter data, status data, interruption node data, traceability data, and integrity verification data. After reading the process data package, the target automated process equipment controls the corresponding pumps, valves, centrifugal mechanisms, temperature control mechanisms, and sensors to execute each basic item according to the execution sequence recorded in the process data package, and records the actual execution status, abnormal status, and completion status of each basic item as the process execution result.

[0037] The above implementation method unifies the hierarchical structure, step status and equipment control relationship in the process editing process into the same process data system, so that the basic item execution sequence formed by process editing can be consistent with the target equipment capacity and consumable structure. At the same time, it can identify the connection anomalies of adjacent sub-processes before process execution, reducing equipment downtime, liquid delivery errors and process execution interruptions caused by process structure errors.

[0038] In some embodiments of the present invention, the step of performing hierarchical modeling based on the process creation information, the equipment configuration data, and the consumable configuration data to obtain a hierarchical process model includes: Based on the process creation information, the process type of the process to be created is determined, and a main process node or a sub-process node is established according to the process type to obtain the process root node; Based on the equipment configuration data, the basic item types supported by the target automated process equipment are determined, and based on the consumable configuration data, the available ports and available fluid lines corresponding to each basic item type are determined, thus obtaining a set of available process nodes; Based on the process editing instructions, the process nodes to be added are determined from the set of available process nodes, and the hierarchical relationship and execution order relationship between the process nodes to be added are established under the process root node to obtain the initial process model; Circular reference detection is performed on the nested sub-processes in the initial process model, and if no circular reference exists, node identifiers are configured for the main process node, sub-process node, and basic item node in the initial process model to obtain the hierarchical process model.

[0039] Understandably, the process type in the process creation information is used to distinguish between the main process and sub-processes. After reading the process type, the process editing software creates the corresponding process root node. The process root node is the highest-level node in the current process data structure, used to store the process identifier, process name, applicable equipment model, applicable consumable model, process version, and indexes of lower-level nodes. When the process to be created is a main process, the process root node is the main process node, and its lower-level nodes are, in principle, sub-process nodes; when the process to be created is a sub-process, the process root node is a sub-process node, and its lower-level nodes can be basic item nodes or nested sub-process nodes.

[0040] Furthermore, the process editing software reads the functional module information from the equipment configuration data and determines the types of basic items supported by the target automated process equipment. When the equipment is equipped with a peristaltic pump and pipeline control valve, it can support inlet / outlet liquid basic items; when the equipment is equipped with a centrifugal motor, speed detection component, and centrifuge cup, it can support centrifugation basic items; when the equipment is equipped with heating component, cooling component, and temperature sensor, it can support temperature control basic items. Basic items without corresponding execution components are not included in the available process nodes of the current equipment, preventing users from creating process steps that the target equipment cannot execute.

[0041] The process editing software simultaneously reads the port and fluid path relationships from the consumable configuration data and determines the available ports and fluid paths for each basic item type. An available port refers to a port in the current consumable that can serve as a liquid input, liquid output, or equipment connection point. An available fluid path refers to the fluid transmission path that can be formed through the corresponding pump and control valve under the current consumable structure. The process editing software can use containers and ports as nodes in the fluid path topology and pipe connections as connecting edges between nodes, thereby establishing the consumable fluid path topology. The fluid path topology reflects the actual connection relationships between the consumable's containers, ports, and pipes. Inlet / outlet fluid basic items can only select source and target ports with existing connection paths in the fluid path topology.

[0042] In one embodiment, the target consumables include a sample bag, a centrifuge cup, and a waste liquid bag. The sample bag port is connected to the peristaltic pump inlet via a first pipeline and a first clamp valve. The peristaltic pump outlet is connected to the centrifuge cup via a second pipeline and a second clamp valve. The centrifuge cup drain port is connected to the waste liquid bag via a third pipeline and a third clamp valve. The process editing software configures the above consumables to form a first usable liquid path from the sample bag to the centrifuge cup and a second usable liquid path from the centrifuge cup to the waste liquid bag. When editing the inlet basic item, the user can select the sample bag as the source container and the centrifuge cup as the target container. When editing the drain basic item, the user can select the centrifuge cup as the source container and the waste liquid bag as the target container.

[0043] The set of available process nodes is composed of the basic item types determined by equipment configuration data and the available ports and available fluid lines determined by consumable configuration data. Each process node template in the set of available process nodes includes at least the node type, applicable equipment conditions, applicable consumable conditions, parameter definitions, and status definitions. The process editing software filters the node templates according to the current equipment model and consumable model, and only displays process nodes that meet the applicable conditions in the editing interface.

[0044] When users perform operations such as adding, deleting, copying, and adjusting the order in the process editing interface, the process editing software generates process editing instructions. These instructions can record the operation type, target parent node identifier, type of node to be added, insertion position, and initial parameters. The process editing software selects the corresponding process node to be added from the available process node set and attaches it to the process root node or a specified child process node. Simultaneously, it establishes the association between the parent node identifier, child node identifier, and execution position, thereby forming the initial process model.

[0045] Hierarchical relationships describe the inclusion relationships between process nodes. For example, a centrifugal separation subprocess may include a basic inlet item, a basic centrifugation item, and a basic outlet item. Execution order relationships describe the sequential execution relationships of nodes under the same parent node. When a user drags and drops to adjust the step order, the process editing software updates the execution position of each node at the same level without changing the internal parameters of the nodes or the structure of lower-level nodes. By recording hierarchical relationships and execution order relationships separately, the entire subprocess can be moved and reused without disrupting its internal structure.

[0046] Furthermore, the process editing software performs circular reference detection on nested sub-processes in the initial process model. A circular reference occurs when a sub-process directly or indirectly references itself; for example, the first sub-process references the second sub-process, and the second sub-process references the first sub-process. When circular references exist, the recursive expansion process will not reach the termination node, therefore, it needs to be eliminated during the hierarchical process model establishment phase.

[0047] Circular reference detection can be performed using a depth-first traversal approach. The process editing software sets three states for each sub-process: unvisited, being visited, and visited successfully. Starting from the current sub-process, it visits the next level of sub-processes level by level along the nested reference relationship. When visiting a sub-process and finding it is already in the "being visited" state, it means the current reference path has returned to a parent sub-process that has not yet been visited. Based on this, the process editing software determines that a circular reference exists and records the node path forming the cycle. When no circular reference exists, each sub-process is marked as visited successfully after traversal.

[0048] After completing the circular reference detection, the process editing software configures node identifiers for the main process node, sub-process nodes, and basic item nodes. Node identifiers can be formed by combining the process identifier, node type, and node sequence number, or they can use globally unique identifiers. Node identifiers remain unchanged during parameter access, step verification, recursive expansion, version comparison, and equipment execution logs, ensuring that the same process node can be accurately located at different data processing stages. After the above processing, the initial process model becomes a hierarchical process model with a complete structure and no circular references.

[0049] In some embodiments of the present invention, the step matching verification of the editable process model based on the output state description of adjacent sub-processes, input state constraints, equipment configuration data, and consumable configuration data, to obtain step verification results, includes: According to the execution order in the editable process model, the preceding and following sub-processes in adjacent sub-processes are obtained to obtain adjacent sub-process pairs; Based on a preset state type, the output state description of the previous sub-process and the input state constraint of the next sub-process are correlated to obtain the state item to be verified. Based on the equipment configuration data and the consumable configuration data, the input allowed status, liquid circuit connection condition and execution component status condition corresponding to each status item to be verified are determined to obtain the status verification conditions. Based on the output state description of the previous sub-process and the state verification conditions, the adjacent sub-processes are matched to obtain the adjacent step matching results. The step verification result is generated based on the matching results of the corresponding adjacent steps for each adjacent sub-process.

[0050] Understandably, the process editing software reads the sub-process nodes under the main process according to the execution order in the editable process model, and establishes every two consecutively arranged sub-processes as an adjacent sub-process pair. For example, if the main process includes a sample inlet sub-process, a centrifugation sub-process, and a supernatant discharge sub-process in sequence, the process editing software establishes the first adjacent sub-process pair between the sample inlet sub-process and the centrifugation sub-process, and the second adjacent sub-process pair between the centrifugation sub-process and the supernatant discharge sub-process. By processing adjacent sub-processes pair by pair, all the step connections in the main process can be covered.

[0051] Furthermore, the process editing software associates the output state description of the previous sub-process with the input state constraints of the next sub-process according to preset state types. Preset state types are used to unify the description methods of different sub-processes for the same type of process state, and may include fluid position, fluid type, fluid volume, fluid temperature, pipeline status, centrifuge mechanism status, pump status, valve status, and actuator occupancy status. Each state item includes at least one of the following: state type identifier, state value, numerical unit, allowable range, and necessity identifier.

[0052] Taking fluid volume status as an example, the output status description of the previous sub-process can state that the fluid volume in the centrifuge cup is 60 ml, while the input status constraint of the subsequent sub-process can state that the fluid volume in the centrifuge cup should be between 50 ml and 80 ml. The process editing software establishes a relationship between these two status items based on the fluid volume status type. Taking fluid position status as an example, if the output position of the previous sub-process is centrifuge cup, and the input position of the subsequent sub-process is centrifuge cup, the process editing software establishes both as position status items to be verified.

[0053] A status item to be verified is a set of status data from adjacent sub-process pairs that share the same status type and require comparison. An adjacent sub-process pair can generate multiple status items to be verified. For example, the sample inlet sub-process and the centrifugation separation sub-process can simultaneously generate status items for fluid position, fluid volume, centrifuge mechanism status, and valve status to be verified. The necessity flag distinguishes between blocking status items and suggestive status items; if a blocking status item is not satisfied, the generation of process data packages is not allowed.

[0054] Furthermore, the process editing software combines equipment configuration data and consumable configuration data to configure status verification conditions for each status item to be verified. The input allowable status describes the acceptable input range for the subsequent sub-process. For example, the centrifugal separation sub-process requires the liquid volume in the centrifuge cup to be within the allowable centrifugation range, and the centrifuge mechanism to be in a stopped state before startup. The liquid path connectivity condition describes the necessary consumable connection relationship between the output position of the previous sub-process and the processing position of the subsequent sub-process. The execution component status condition describes the state that the relevant pumps, valves, centrifuge mechanisms, or temperature control mechanisms should be in before the startup of the subsequent sub-process.

[0055] Status verification conditions can be stored using rule tables. Each rule in the rule table can include the applicable status type, comparison method, allowed values, allowed range, equipment limitations, consumable limitations, and exception type. Enumerated statuses can be compared using set inclusion, for example, the status of a centrifuge mechanism should belong to the set of stopped statuses; numerical statuses can be compared using range comparison, for example, the fluid volume should be within a predetermined range; and positional statuses can be compared using the same location or fluid path reachability.

[0056] The matching process refers to comparing the output state description of the previous sub-process with the state verification conditions corresponding to the next sub-process according to a preset state type, and combining the equipment configuration data and consumable configuration data to determine whether the state value is within the input allowable range, whether the fluid position meets the subsequent processing requirements, whether the relevant liquid circuit is connected, and whether the status of the execution component meets the start-up conditions, thereby determining whether the adjacent sub-processes are in a matched or mismatched state.

[0057] In one specific embodiment, the first sub-process is the sample inlet sub-process, whose output state description includes the sample being located in the centrifuge cup, the liquid volume in the centrifuge cup being 60 ml, the centrifugation mechanism being in a stopped state, and the inlet valve being in a closed state. The second sub-process is the centrifugal separation sub-process, whose input state constraints require the fluid to be located in the centrifuge cup, the liquid volume in the centrifuge cup being 50 ml to 80 ml, the centrifugation mechanism being in a stopped state, and the inlet and outlet valves connected to the centrifuge cup being in a closed state. The process editing software compares each item to confirm that all necessary states meet the requirements, and the matching results of the corresponding adjacent steps indicate that the matching is successful.

[0058] In another specific embodiment, after the previous sub-process is completed, the fluid is located in the sample bag, and the next sub-process requires the presence of liquid in the centrifuge cup. Although the process editing software confirms the existence of a liquid path between the sample bag and the centrifuge cup after reading the consumable liquid path topology, no liquid inlet operation is set between adjacent sub-processes to complete the liquid transfer. Therefore, the actual output position of the previous sub-process still does not meet the input position requirement of the next sub-process, and the corresponding adjacent step matching result indicates a mismatch in position status.

[0059] It should be noted that the fluid path connectivity condition is used to determine whether the consumable structure provides the corresponding transmission conditions, but the existence of a fluid path does not equate to the completion of a fluid position transition between adjacent sub-processes. Step matching verification is still based on the actual output and input state requirements. Only when the output state of the preceding sub-process has met the input requirements of the following sub-process, or when the adjacent steps explicitly contain a corresponding state transition process, are the steps considered to be able to connect.

[0060] After the process editing software completes the matching process for all adjacent sub-process pairs, it summarizes the matching results of each adjacent step and forms a step verification result. The step verification result may include the main process identifier, adjacent sub-process pair identifiers, matching status, failure status items, anomaly level, and verification time. The step verification result serves as the basis for subsequent anomaly prompts and as a prerequisite for recursive expansion and process data package generation.

[0061] In some embodiments of the present invention, generating the step verification result based on the matching results of corresponding adjacent steps of each adjacent sub-process includes: From the adjacent step matching results, determine the target adjacent sub-process pairs that do not meet the state verification conditions; Based on the corresponding state items to be verified for the target adjacent sub-processes, the output state value of the previous sub-process and the input requirement value of the next sub-process are determined to obtain state difference information. Based on the state difference information, at least one mismatch type is determined, and mismatch cause information is generated based on the mismatch type; wherein, the at least one mismatch type includes: position mismatch, state value mismatch, fluid circuit disconnection, and execution component state mismatch; The mismatch reason information is associated with the next sub-process in the target adjacent sub-process pair, and an abnormal prompt indicator is set for the next sub-process. The step verification result is generated based on the matching status of each adjacent sub-process pair, the mismatch reason information, and the abnormal prompt identifier.

[0062] Understandably, the process editing software reads the matching status from the matching results of adjacent steps and uses adjacent sub-processes whose matching status indicates failure as target adjacent sub-processes. Each target adjacent sub-process is associated with at least the previous sub-process identifier, the next sub-process identifier, and one or more status items that do not meet the status verification conditions. This process can extract the connection points of steps that need modification from the entire main process, avoiding the need for users to check every single process step.

[0063] Furthermore, the process editing software reads the output state value of the preceding subprocess and the input requirement value of the following subprocess for each state item to be verified in the target adjacent subprocess pair, and forms state difference information according to the state type. The state difference information records at least the state type, actual output value, required value or required range, comparison result, and corresponding unit. For example, the actual output value of the fluid position state is sample bag, and the input requirement value is centrifuge cup; the actual output value of the fluid volume state is 30 ml, and the input requirement range is 50 ml to 80 ml; the actual output value of the centrifuge mechanism state is rotating state, and the input requirement value is stopped state.

[0064] The status difference information does not only record verification failures, but also retains the actual state and target state that led to the failure conclusion, enabling process editors to determine the source of the error. For numerical range mismatches, the status difference information can also record the direction of the difference, whether it is below the lower limit or above the upper limit; for equipment status mismatches, it can record the state transition that needs to be completed between the current equipment status and the required status.

[0065] Furthermore, the process editing software identifies mismatch types based on state difference information. Location mismatch refers to the discrepancy between the location of the fluid, sample, or processed object output from the previous sub-process and the location required by the subsequent sub-process. State value mismatch refers to fluid volume, temperature, rotational speed, or other state values ​​not being within the allowable range of the subsequent sub-process. Fluid path disconnection refers to the absence of a usable path connecting the previous and subsequent locations in the consumable fluid path topology, or the pumps and valves required by the existing path not being supported by the target equipment. Execution component state mismatch refers to the state of the pump, valve, centrifugal mechanism, temperature control mechanism, or other execution components after the completion of the previous sub-process not meeting the startup requirements of the subsequent sub-process.

[0066] In one embodiment, after the previous sub-process is completed, the centrifuge mechanism continues to rotate at a low speed. The next sub-process is a centrifuge cup draining operation, and the equipment configuration specifies that the centrifuge mechanism must stop during draining. The process editing software compares the actual output state with the input requirements, identifies a mismatch in the execution component state, and generates information explaining why the centrifuge mechanism is currently rotating while the draining operation requires it to be stopped. Users can add a deceleration and stop baseline between the two sub-processes or modify the output state of the previous sub-process.

[0067] In another embodiment, the output fluid of the preceding subprocess is located in the first liquid bag, while the subsequent subprocess needs to draw fluid from the second liquid bag. There is no connection between the first and second liquid bags in the consumable fluid path topology, and the process editing software identifies this as a fluid path disconnection. The cause information can record the location of the preceding fluid, the location of the subsequent input, the missing fluid path relationship, and the model of the consumable involved.

[0068] The process editing software associates the mismatch reason information with the next subprocess in the target adjacent subprocess pair. The exception is associated with the next subprocess because the input conditions of the next subprocess are not met by the output state of the previous subprocess. The exception indicator can include the exception identifier, exception level, reason information index, and pending status. The process editing interface highlights the next subprocess based on the exception indicator or provides a pop-up dialog box, and displays the corresponding reason information when the user selects that subprocess.

[0069] It should be noted that the error message identifier is part of the structured status data in the step verification result, and the color, highlighted border, or icon in the interface are merely the display form of the error message identifier. Even without using a specific color, the system can still locate the mismatched step and display the reason information based on the error message identifier; therefore, the technical processing of this invention does not depend on a specific interface color.

[0070] The process editing software summarizes the matching status, mismatch reasons, and anomaly alerts for each adjacent subprocess pair, forming a complete step verification result. After all blocking mismatches are corrected, the process editing software re-executes the adjacent step matching process until the step verification result meets the preset pass conditions. This implementation method not only identifies mismatched steps but also explains the differences in the states leading to the mismatch conclusions and their types, facilitating process editors to adjust the process based on actual causes.

[0071] In some embodiments of the present invention, the step of performing parameter opening processing on the hierarchical process model based on the open parameter information to obtain an editable process model includes: Based on the open parameter information, the target open parameter is determined from the control parameters of the basic items within the sub-process; Based on the sub-process identifier of the sub-process, the basic item identifier of the basic item, and the parameter identifier of the target open parameter, determine the parameter access path corresponding to the target open parameter; Based on the parameter access path, an editable parameter item associated with the target open parameter is established in the main process, and the allowable adjustment range of the editable parameter item is determined based on the parameter constraint information of the target open parameter. Obtain the parameter modification value set for the editable parameter item, and associate the parameter modification value with the parameter access path to obtain parameter coverage data; The editable parameter items, the parameter access path, and the parameter overriding data are written into the hierarchical process model, while keeping the original control parameters of the referenced sub-process unchanged, to obtain the editable process model.

[0072] Understandably, subprocess editors can set the open status of control parameters for each basic item when creating a subprocess. Control parameters refer to the data required to control the target automated process equipment to execute the corresponding basic item. Examples include the source port, target port, liquid volume, liquid flow rate, and termination detection method for inlet / outlet liquid basic items, and the target rotational speed, acceleration, centrifugation time, and deceleration for centrifugation basic items. Open parameter information should at least include the parameter identifier, open status, display name, parameter unit, default value, and parameter constraint information.

[0073] After reading the open parameter information, the process editing software selects the parameters that are valid in the open state from the control parameters of the basic items within the sub-process as the target open parameters. For example, the centrifugal separation sub-process can open the target rotation speed and centrifugation time, while keeping the centrifugation direction, acceleration, deceleration, and valve status as closed parameters; the inlet / outlet liquid sub-process can open the liquid volume and fluid velocity, while keeping the source port, target port, and valve opening sequence as closed parameters. By distinguishing between open and closed parameters, the main process editor can avoid modifying the verified underlying liquid path control relationships.

[0074] Furthermore, the process editing software establishes a parameter access path based on the sub-process identifier, the basic item identifier, and the parameter identifier of the target open parameter. The parameter access path is used to locate a specific basic item parameter within a sub-process from a sub-process instance in the main process, and can sequentially include the main process instance identifier, sub-process instance identifier, nested sub-process instance identifier, basic item instance identifier, and parameter identifier. When there is no nested hierarchy in the sub-process, the nested sub-process instance identifier can be omitted from the parameter access path.

[0075] The same sub-process can be called multiple times within a main process, with each call forming an independent sub-process instance. Although these sub-process instances reference the same sub-process template, their sub-process instance identifiers are different, and therefore their corresponding target open parameters have different parameter access paths. Using parameter access paths prevents parameter modifications in one sub-process instance from affecting other sub-process instances.

[0076] The process editing software creates editable parameter items in the main process editing interface according to the parameter access path. Editable parameter items can include parameter name, parameter unit, default value, current value, minimum allowable value, and maximum allowable value. Parameter constraint information is used to limit the allowable value range of the target open parameter, and can include data type, numerical range, step unit, and associated constraints. The process editing software can also perform intersection processing between the parameter constraint information and the execution capability range in the equipment configuration data, using the range allowed by both as the actual allowable adjustment range of the editable parameter item.

[0077] For example, if a sub-process template specifies that the centrifugal speed can be adjusted between 1000 rpm and 3000 rpm, and the centrifugal mechanism of the target automated process equipment allows a speed range of 500 rpm to 2500 rpm, then the editable parameter item in the main process can be adjusted between 1000 rpm and 2500 rpm. When the user inputs a parameter exceeding the above range, the process editing software will not save the parameter value and will prompt that the parameter exceeds the allowable range of the current equipment.

[0078] After a user modifies an editable parameter, the process editing software retrieves the modified value and associates it with the parameter access path to form parameter overwrite data. This data records the parameter access path, original parameter value, modified parameter value, modification time, and parameter status. Parameter overwrite data only applies to a specific sub-process instance within the current main process and does not write back the original control parameters in the sub-process template.

[0079] In one specific embodiment, the main cleaning process calls the same liquid inlet subprocess twice: the first call is used to input the cleaning solution, and the second call is used to input the culture medium. The liquid inlet subprocess allows the liquid volume parameter to be displayed. The parameter overlay data of the first call sets the liquid volume to 100 ml, and the parameter overlay data of the second call sets the liquid volume to 50 ml. The two calls have different parameter access paths, and after recursive expansion, they respectively form two basic item instances with the corresponding liquid volumes, while the original liquid inlet subprocess still retains the default liquid volume.

[0080] The process editing software writes editable parameter items, parameter access paths, and parameter coverage data into the hierarchical process model, forming an editable process model. This editable process model retains both the original parameters of the sub-process templates and the parameter coverage relationships of each sub-process instance, enabling subsequent recursive expansion to accurately restore the actual execution parameters of each basic item instance. This implementation method ensures the reusability of sub-processes while limiting the range of parameters that can be modified in the main process layer, reducing the risk of accidentally modifying the control parameters of underlying equipment.

[0081] In some embodiments of the present invention, when the step verification result meets a preset pass condition, performing recursive expansion processing on the editable process model to obtain a basic item execution sequence includes: According to the execution order in the editable process model, read the process nodes corresponding to each sub-process in sequence; When the process node is a basic item node, the basic item node is written into the candidate execution sequence. When the process node is a nested sub-process node, the next-level process node in the nested sub-process node is recursively expanded to obtain the candidate execution sequence. Based on the parameter access path, the corresponding parameter coverage data is obtained from the editable process model, and the parameter coverage data is written into the corresponding basic item instance to obtain the basic item to be executed; Based on the execution order of each basic item to be executed in the editable process model, an execution sequence number is configured for each basic item to be executed. The execution sequence of the basic items is obtained by associating the execution sequence number, control parameters, input status, output status, and execution component occupancy information of each basic item to be executed.

[0082] Understandably, after the step verification results meet the preset pass conditions, the process editing software starts from the root node of the editable process model and reads the process nodes according to the execution order of each sub-process. A process node includes at least a node type, node identifier, parent node identifier, list of subordinate nodes, and execution position. The node type is used to distinguish between basic item nodes and nested sub-process nodes; the process editing software uses different expansion processing methods based on the node type.

[0083] When the current process node is a basic item node, the process editing software copies the node type, parameter data, input status, output status, and execution component occupancy information of the basic item node, and writes the copied basic item instance into the candidate execution sequence. When the current process node is a nested sub-process node, the process editing software reads the list of subordinate nodes of the nested sub-process node and continues to perform the same processing according to the execution order of the subordinate nodes until the basic item node is read.

[0084] Recursive expansion can be implemented using a depth-first approach, that is, first completing the expansion of all lower-level nodes within the current sub-process, and then reading other sub-processes after the current sub-process. Taking a main process that includes a first sub-process and a second sub-process as an example, the first sub-process includes a first basic item and a nested third sub-process, the third sub-process includes a second basic item and a third basic item, and the second sub-process includes a fourth basic item. Then, the candidate execution sequence after recursive expansion is the first basic item, the second basic item, the third basic item, and the fourth basic item.

[0085] Furthermore, the process editing software records the node source path for each basic item instance during the recursive expansion process. The node source path may include the main process node identifier, the identifiers of each layer's sub-process node, and the original basic item node identifier. The node source path corresponds to the parameter access path described in the aforementioned embodiments, enabling the process editing software to query the parameter coverage data corresponding to the current basic item instance from the editable process model.

[0086] When parameter overriding data exists, the process editing software writes the modified parameter values ​​from the overriding data into the corresponding basic item instance, replacing the default parameter values ​​in the basic item template. When no parameter overriding data exists, the basic item instance continues to use the default parameter values ​​in the sub-process template. The basic item instance after parameter overriding processing becomes the basic item to be executed, and its parameter content is consistent with the actual settings in the main process editing interface.

[0087] In one embodiment, the default centrifugal speed of the basic centrifuge item in the centrifuge sub-process is 2,000 revolutions per minute (rpm). The main process modifies the centrifugal speed of this sub-process instance to 2,300 rpm by opening parameters. When recursively expanding and reading to this basic centrifuge item, the process editing software finds the corresponding parameter overwrite data according to the parameter access path and replaces the speed parameter in the basic item instance with 2,300 rpm. The default speed in the sub-process template remains at 2,000 rpm.

[0088] Furthermore, the process editing software configures execution sequence numbers according to the actual order of each basic item to be executed in the editable process model. The execution sequence number can be a continuously increasing integer starting from the first basic item, and the target automated process equipment reads each basic item sequentially according to the execution sequence number. After nodes are added, deleted, or their order is adjusted, the process editing software reconfigures the execution sequence numbers for the affected basic items to be executed to avoid duplicate, missing, or inconsistent execution sequence numbers with the actual order.

[0089] The process editing software associates the execution sequence number, control parameters, input status, output status, and execution component occupancy information of each basic item to be executed, forming a basic item execution sequence. The execution component occupancy information describes the execution components required during the execution of the basic item and the conditions for continued occupancy. For example, the inlet / outlet liquid basic item occupies the first peristaltic pump, the first clamp valve, and the second clamp valve, while the centrifugation basic item occupies the centrifuge mechanism and requires the relevant inlet / outlet valves to remain closed.

[0090] The basic execution sequence adopts a single-level ordered structure, which no longer retains nested relationships that require further parsing by the equipment. However, it can be traced back to the original hierarchical process model through the node source path. As a result, process editing software can use the hierarchical structure for editing and reuse, while target automated process equipment can use the sequential structure to execute specific control operations. The two data structures establish a correspondence through recursive expansion.

[0091] In some embodiments of the present invention, generating a process data package based on the device configuration data, the consumable configuration data, and the basic item execution sequence includes: Based on the equipment configuration data and the consumable configuration data, a simulated equipment state is established; wherein, the simulated equipment state includes at least the container state, the liquid circuit state, and the actuator state; Based on the execution sequence of the basic items, the state of the simulated device is deduced to obtain the simulation operation results; Based on the simulation results, an execution anomaly is determined, and an execution determination result is obtained; When the execution determination result indicates that there is no preset operational abnormality, the basic item execution sequence is encapsulated to obtain the process data package.

[0092] Understandably, before generating a process data package that can be executed by the target automated process equipment, the process editing software establishes a simulated equipment state based on the equipment configuration data and consumable configuration data. The simulated equipment state is a set of data that digitally represents the state of the target automated process equipment and its consumables during process operation, including at least the container state, fluid circuit state, and actuator state.

[0093] Container status can include container identifier, container name, maximum capacity, current liquid volume, liquid type, current temperature, and occupancy status. Liquid path status can include pipeline identifier, starting port, target port, connection status, flow direction, liquid type within the pipeline, and pipeline occupancy status. Actuator status can include pump start / stop status, pump direction, pump speed, valve open / close status, centrifuge speed, centrifuge direction, temperature control target temperature, and sensor status.

[0094] Before the simulation begins, users can set the initial liquid volume and liquid name for each liquid bag and container. For example, the first liquid bag can be set as a sample bag with an initial volume of 100 ml, the second liquid bag as a cleaning liquid bag with an initial volume of 500 ml, the third liquid bag as a culture medium bag with an initial volume of 300 ml, and the waste liquid bag with an initial volume of 0. The process editing software establishes the association between the above containers, ports, and pipelines according to the consumable configuration data, and establishes the correspondence between the relevant pipelines and pumps and valves according to the equipment configuration data.

[0095] Furthermore, the process editing software performs state simulation of the simulated equipment according to the execution sequence of the basic items. State simulation refers to updating the simulated equipment state sequentially based on the control parameters of the basic items and their state transition rules. When the liquid inlet / outlet basic item is executed, the current liquid volume in the source container decreases, the current liquid volume in the target container increases, the corresponding liquid path becomes occupied, and the relevant valves and pumps enter the operating state; when the centrifugation basic item is executed, the centrifuge mechanism accelerates to the target speed, maintains the predetermined centrifugation time, and then decelerates to the stop state; when the temperature control basic item is executed, the simulated temperature of the target container or centrifuge cup changes according to the temperature control parameters.

[0096] The simulation results are used to record the status of the simulated equipment, execution time, and abnormal information before and after each basic item is executed. It should be noted that the simulation is not simply playing an animation of the process steps; rather, it calculates and records state changes based on equipment parameters, consumable capacity, and fluid circuit relationships. Even without displaying the simulation interface, the process editing software can still perform state deduction and operational anomaly detection in the background.

[0097] The process editing software determines operational anomalies based on the simulation results. Anomaly determination can be based on a preset anomaly rule library, which includes anomaly types, trigger conditions, anomaly levels, and handling requirements. Preset operational anomalies may include insufficient liquid in the source container, excessive capacity of the target container, liquid path disconnection, pipeline flow direction conflict, execution component status conflict, duplicate use of execution components, execution of disallowed liquid inlet / outlet operations during centrifugation, and proceeding to the next step before the required temperature is reached.

[0098] In one specific embodiment, the first basic item in the basic item execution sequence requires transferring 80 ml of sample solution from the sample bag to the centrifuge cup, with the initial volume of the sample bag being 60 ml. When the state is extrapolated to this basic item, the process editing software compares the current volume of the source container with the target delivery volume, confirming that the source container is underfilled, thus creating a blocking operational anomaly. The execution judgment result indicates the existence of a preset operational anomaly, the process editing software suspends the generation of the process data package, and provides the user with the abnormal basic item and the cause of the anomaly for modification.

[0099] In another embodiment, the centrifuge cup has a maximum capacity of 100 ml. The previous step has already added 80 ml of liquid to the centrifuge cup, and the current basic step requires an additional 40 ml of liquid. The process editing software will calculate a centrifuge cup volume of 120 ml, exceeding the maximum capacity recorded in the consumable configuration data. This results in a container capacity over-limit anomaly. The user can modify the inlet volume or add a draining step in the previous step.

[0100] When the execution judgment result indicates that no preset operational anomalies exist, the process editing software encapsulates the basic item execution sequence according to the data format that the target automated process equipment can parse. The encapsulated content may include process identifier, process version, target equipment model, consumable model, control protocol version, basic item data, status data, anomaly handling data, and integrity verification data. The basic item execution sequence, after step matching verification and simulated operation verification, is entered into the process data package, thereby reducing the possibility of fluid volume, fluid circuit, and equipment resource anomalies occurring during actual equipment operation.

[0101] In some embodiments of the present invention, the step of performing state deduction on the simulated device state based on the execution sequence of the basic items to obtain the simulation operation result includes: The current basic item is obtained according to the execution sequence number in the basic item execution sequence, and the basic item type and control parameters corresponding to the current basic item are obtained; The corresponding state transition rule is determined based on the basic item type; wherein, the state transition rule is used to characterize the state change relationship of the simulation device before and after the execution of the current basic item; Based on the control parameters and the state transition rules, the state of the simulation device is updated to obtain the current simulation state; Based on the equipment configuration data and the consumable configuration data, anomaly detection is performed on the current simulation state to obtain simulation anomaly information; wherein, the simulation anomaly information is used to characterize at least one of the following operational anomalies: insufficient fluid, container capacity exceeding limit, fluid circuit disconnection, execution component state conflict, and repeated occupation of execution components; The simulation results are generated based on the current simulation status of each basic item and the simulation anomaly information.

[0102] Understandably, the process editing software reads the current basic item sequentially according to its execution sequence number. The current basic item includes at least the basic item type, control parameters, input status, output status, and execution component occupancy information. The basic item type is used to select the appropriate state transition rule, and the control parameters are used to determine the specific value and duration of the state change.

[0103] Taking the inlet / outlet liquid basic item as an example, its control parameters can include inlet / outlet liquid type, starting port, target port, liquid density, target volume, fluid flow rate, and termination judgment method. Inlet / outlet liquid type can include sample injection, liquid drainage, pipeline evacuation, and formulation liquid input. Termination judgment method can include ending based on target volume, ending based on bubble sensor detection result, or ending based on liquid volume detection result. Taking the centrifugation basic item as an example, its control parameters can include target rotational speed, centrifugation time, acceleration, and deceleration.

[0104] Furthermore, the process editing software reads the corresponding state transition rules based on the basic item type of the current basic item. The state transition rules specify the sequential running states that the current basic item will experience during execution, the execution operations corresponding to each running state, and the switching conditions between adjacent running states. Each running state switches according to a preset execution order. When the switching conditions corresponding to the current running state are met, the next running state is entered, until the current basic item is completed or a running abnormality is detected. Different basic item types correspond to different running states and state transition conditions.

[0105] The set of states corresponding to the basic inlet / outlet liquid items can include preparation state, liquid path establishment state, pumping state, end-of-detection state, and completion state. In the preparation state, the liquid level in the source container, the capacity of the target container, and the idle status of the actuators are checked. In the liquid path establishment state, the relevant valve states are set. In the pumping state, the pump direction and speed are set, and the liquid levels in the source and target containers are updated. In the end-of-detection state, it is determined whether the target volume or sensor termination condition is met. In the completion state, the pump is stopped and the valve states are restored.

[0106] The set of states corresponding to the basic centrifugation items can include start-up check state, acceleration state, constant speed state, deceleration state, and stop confirmation state. The start-up check state is used to confirm that the liquid volume in the centrifuge cup is within the allowable range and that the relevant valves are closed; the acceleration state is used to increase the rotation speed according to the acceleration; the constant speed state is used to maintain the target rotation speed and centrifugation time; the deceleration state is used to decrease the rotation speed according to the deceleration; and the stop confirmation state is used to confirm that the centrifugation mechanism has stopped.

[0107] Furthermore, the process editing software updates the simulated equipment status based on control parameters and state transition rules. For inlet / outlet liquid-based items, the software searches the consumable liquid path topology for available liquid paths from the starting port to the target port, determines the valves that need to be opened and the pumps that need to be started, and updates the liquid volumes in the source and target containers based on the target volume. For centrifugation-based items, the software updates the centrifuge mechanism's rotational speed and duration according to the target rotational speed, acceleration, centrifugation time, and deceleration.

[0108] The simulated equipment state after the current basic item is completed serves as the initial simulated equipment state for the next basic item, thus forming a continuous state transfer. The process editing software saves the pre-execution state and post-execution state for each basic item, enabling subsequent anomaly localization to reconstruct the equipment and consumable states at the time of the anomaly.

[0109] The process editing software performs anomaly detection on the current simulation state based on equipment configuration data and consumable configuration data. Insufficient fluid means the current liquid volume in the source container is less than the volume required by the basic item. Container capacity exceeding limits means the expected liquid volume received by the target container exceeds its maximum capacity. Liquid path disconnection means there is no path in the consumable liquid path topology that meets the current delivery requirements. Execution component state conflict means the current basic item requires a component state that is inconsistent with the existing state; for example, performing drainage while the centrifuge mechanism has not stopped. Duplicate execution component occupation means a basic item has not yet released a pump, valve, or centrifuge mechanism, and a subsequent basic item requests to occupy the same execution component.

[0110] Simulated anomaly information includes at least the anomaly basic item identifier, anomaly type, anomaly location, anomaly state before anomaly, anomaly triggering conditions, and anomaly level. Anomaly levels can include suggestive anomalies and blocking anomalies. Suggestive anomalies allow users to confirm and continue processing, while blocking anomalies require modifications before a process data package can be generated.

[0111] The process editing software summarizes the current simulation status and simulation anomaly information corresponding to each basic item, forming the simulation results. The simulation interface displays real-time liquid flow, container volume, pump direction of travel, valve status, centrifugal speed, current temperature, estimated running time, and current running time based on the simulation results. It also supports starting, pausing, continuing, terminating, and accelerating the simulation at different speeds. The interface display is designed to assist users in understanding the simulation process; however, state extrapolation and anomaly detection are still based on the structured simulation of the equipment's state.

[0112] In some embodiments of the present invention, when the execution determination result indicates that there is no preset operational abnormality, the step of encapsulating the basic item execution sequence to obtain the process data package includes: Candidate interruption nodes are determined based on the execution boundaries of adjacent basic items in the execution sequence of the basic items; Based on the output state of the previous basic item and the input state of the next basic item corresponding to the candidate interrupt node, the device safety status conditions corresponding to each candidate interrupt node are determined. Based on the device safety status conditions, a target interrupt node that allows adjustment of the unexecuted basic item is determined from the candidate interrupt nodes, and an interrupt node identifier is set for the target interrupt node; Process execution data is generated based on the execution sequence of the basic items, and process traceability data is generated based on the hierarchical process model; The process execution data, the process traceability data, the interruption node identifier, and the data integrity verification information are encapsulated to obtain the process data package.

[0113] Understandably, the process editing software identifies the execution boundaries of adjacent basic items within the basic item execution sequence. An execution boundary is a process position where the previous basic item has been completed and the next basic item has not yet begun execution. Execution boundaries can lie between two basic items within the same sub-process, or between basic items corresponding to two sub-processes. The process editing software can use sub-process end boundaries, manually confirmed boundaries, and basic item boundaries where the equipment can be stably paused as candidate interruption nodes.

[0114] Candidate interruption nodes only indicate process locations that may be used for pause or adjustment; whether they can be considered actual interruption nodes requires further judgment based on the equipment safety status. The process editing software reads the output status of the preceding basic item and the input status of the following basic item of the candidate interruption node, and determines the equipment safety status conditions in conjunction with the equipment configuration data.

[0115] Equipment safety status conditions define the actual state that a target automated process device must be in to allow the suspension and modification of subsequent processes. These conditions may include: pumps stopped; valves in predetermined safe open / closed states; centrifugal mechanism at zero speed; temperature control mechanism within permissible temperature range; no liquid delivery in the current liquid path; and confirmation of the execution result of the previous basic item. Different candidate interruption nodes can correspond to different equipment safety status conditions.

[0116] For example, when the candidate interruption node is located after the liquid inlet basic item, the equipment safety condition can require that the pump has stopped, the relevant valves have been closed, and the liquid level in the target container has been measured. When the candidate interruption node is located after the centrifugation basic item, the equipment safety condition can require that the centrifuge mechanism's speed is zero, the braking status is normal, and the relevant valves remain closed. These safety condition conditions are associated with the actual state of the executing components, avoiding adjustments to subsequent processes while the liquid is still being transported or the centrifuge mechanism is still rotating.

[0117] Furthermore, the process editing software selects the target interruption node from the candidate interruption nodes based on the equipment safety status conditions and online editing permissions. Online editing permissions are used to limit the operations allowed at the corresponding interruption node, which may include allowing the addition of basic items, the deletion of unexecuted basic items, the adjustment of the order of unexecuted basic items, and the modification of control parameters for unexecuted basic items. Certain steps involving aseptic processing, equipment calibration, or safety interlocks can be set to disallow online adjustment.

[0118] The process editing software configures an interruption node identifier for the target interruption node and associates the interruption node identifier with the previous basic item identifier, the next basic item identifier, the equipment safety status conditions, and online editing permissions. The interruption node identifier is used to identify adjustable positions of the target automated process equipment during execution. Its technical meaning is not a general program pause position, but a controlled adjustment node jointly defined by process boundaries, equipment safety status, and editing permissions.

[0119] Furthermore, the process editing software generates process execution data based on the basic item execution sequence. This data includes at least the basic item execution sequence number, basic item type, execution component identifier, control parameters, input status, output status, execution component occupancy information, and exception handling methods. The target automated process equipment then generates control commands for the pump, valves, centrifugal mechanism, and temperature control mechanism based on the process execution data.

[0120] The process editing software also generates process traceability data based on the hierarchical process model. This data records the origin of each basic item within the hierarchical process model, including the main process identifier, sub-process identifier, basic item template identifier, node source path, parameter coverage data, and process version. When an anomaly occurs during the execution of a basic item, the corresponding sub-process and basic item in the process editing software can be located based on the process traceability data.

[0121] The process editing software encapsulates process execution data, process traceability data, interruption node identifiers, and data integrity verification information into a process data package. The data integrity verification information is used to determine whether data loss or alteration has occurred during the saving, copying, or transmission of the process data package. This can be achieved using cyclic redundancy check, digest check, or other verification methods capable of detecting data changes. The process data package can also record applicable equipment models, applicable consumable models, software versions, control protocol versions, and data lengths, providing a basis for equipment-side suitability verification.

[0122] In some embodiments of the present invention, after encapsulating the basic item execution sequence to obtain the process data packet when the execution determination result indicates that there is no preset operational abnormality, the method includes: The process data package is subjected to integrity and applicability checks to obtain data package verification results; wherein, the applicability check is used to determine whether the equipment model, consumable model and control protocol version corresponding to the process data package match the target automated process equipment; When the data packet verification result indicates that the verification is successful, the process execution data is parsed to obtain the equipment control sequence; Based on the device control sequence, the corresponding execution component is controlled to execute each basic item, and the running status of the execution component is obtained to obtain the current device status; When execution reaches the interruption node identifier, the node status is determined based on the current device status and the corresponding device security status conditions to obtain the node determination result; If the node determination result indicates that no adjustment has been made, continue running the next node; When the node determination result indicates that adjustment is allowed and a process adjustment request is received, the unexecuted basic items are adjusted based on the process adjustment request to obtain an updated sequence to be executed. The process is then executed based on the updated sequence to be executed or the original sequence to be executed without adjustment to obtain the process execution result.

[0123] Understandably, the target automated process equipment receives process data packets via a mobile storage medium or communication interface. The equipment controller first reads the data integrity verification information and performs integrity verification on the actual data content of the process data packet. If the integrity verification fails, it indicates that the process data packet may have been missing, damaged, or altered during storage or transmission, and the equipment controller refuses to load the process data packet.

[0124] Furthermore, the equipment controller reads the equipment model, consumable model, and control protocol version recorded in the process data packet and performs a suitability check against the current configuration of the target automated process equipment. The equipment model check confirms that the actuators and equipment capabilities required by the process are consistent with the current equipment; the consumable model check confirms that the containers, ports, and fluid lines in the process are consistent with the currently installed consumables; and the control protocol version check confirms that the control fields in the process data can be correctly parsed by the current equipment controller.

[0125] The equipment controller can also read the actuator identifiers in the process execution data and verify whether the actuators actually installed on the current equipment are complete. If the process requires the use of a second peristaltic pump, but the current equipment does not have a second peristaltic pump installed, the suitability check will fail. If both the integrity check and the suitability check pass, the data packet check result indicates that the check has passed.

[0126] The equipment controller then parses the process execution data and converts each basic item into an equipment control sequence according to its type. The equipment control sequence is a set of low-level control instructions arranged in execution order. For example, inlet / outlet liquid basic items can be converted into valve status setting instructions, pump direction setting instructions, pump speed setting instructions, and termination condition detection instructions; centrifugation basic items can be converted into rotation direction setting instructions, acceleration instructions, constant speed holding instructions, and deceleration / stop instructions; and temperature control basic items can be converted into target temperature setting instructions, temperature acquisition instructions, and heat preservation time control instructions.

[0127] Furthermore, the equipment controller sends control commands to the corresponding actuators according to the equipment control sequence, and obtains the operating status through sensors and actuator feedback interfaces. The current equipment status may include the current basic item identifier, pump operating status, valve status, centrifuge speed, container liquid volume, current temperature, liquid circuit status, completed basic items, and equipment abnormal status.

[0128] The equipment controller compares the actual operating status with the output status of the current basic item. When the actual operating status meets the output status requirements, the current basic item is marked as completed and the process proceeds to the next basic item. When the execution time exceeds the allowed time or the actual status does not meet the output status requirements, the equipment controller suspends the process, retryes the current basic item, or terminates the process according to the exception handling method, and writes the corresponding execution status into the process execution result.

[0129] Furthermore, when the node determination result indicates an unchanged state, it means that the target automated process equipment has not received a process adjustment request at the current interruption node, or has received a control instruction to continue executing the original process. In this case, the equipment controller maintains the basic items, control parameters, and execution order in the original sequence to be executed unchanged, releases the waiting state corresponding to the current interruption node, and reads the next basic item according to the execution sequence number in the original sequence to be executed, controlling the corresponding execution component to continue execution. Thus, when no adjustment to subsequent processes is required, the interruption node can avoid causing additional impact on the continuous operation of the process, and maintains consistency between the process execution process and the original process data package.

[0130] When the equipment controller reaches the interrupt node identifier, it reads the equipment safety status conditions corresponding to that interrupt node and compares the current equipment status with each of the equipment safety status conditions. If the centrifugal mechanism speed has not yet returned to zero, the pump is still running, or the liquid circuit is still delivering liquid, the node determination result cannot be adjusted; if all necessary safety conditions are met and the interrupt node has the corresponding online editing permissions, the node determination result can be adjusted.

[0131] When the node determination result indicates that adjustment is allowed and the equipment receives a process adjustment request, the equipment controller pauses the process to proceed to the next basic item and adjusts the unexecuted basic items after the interrupted node. If the adjustment request has not arrived, or if the user chooses to continue executing the original process, the equipment controller continues execution according to the original sequence to be executed. When the adjustment request is processed and the adjusted sequence passes verification, the equipment controller continues execution according to the updated sequence to be executed.

[0132] The process execution results can include the process completion status, the actual start and end times of each basic item, the actual operating parameters of the executed components, sensor detection results, online adjustment records, and anomaly records. By associating the process execution results with the node source paths in the process data package, traceability of the process execution process can be supported.

[0133] In some embodiments of the present invention, when the node determination result indicates that adjustment is allowed and a process adjustment request is received, performing process adjustment processing on the unexecuted basic items based on the process adjustment request to obtain an updated sequence to be executed includes: Based on the interruption node identifier, determine the unexecuted basic items that can be adjusted to obtain a set of basic items to be adjusted; parse the process adjustment request to obtain at least one target adjustment operation among basic item addition operation, basic item deletion operation, execution order adjustment operation, and control parameter modification operation; Based on the target adjustment operation, the set of basic items to be adjusted is updated to obtain candidate sequences to be executed; based on the current device status, the device configuration data, and the consumable configuration data, the candidate sequences to be executed are subjected to step matching verification, fluid circuit connectivity verification, and execution component occupancy verification to obtain adjustment verification results; When the adjustment verification result indicates that the verification is passed, the execution sequence number and interruption node identifier of the candidate sequence to be executed are reconfigured to obtain the updated sequence to be executed.

[0134] Understandably, after the target automated process equipment reaches an interruption point that allows adjustment, the equipment controller determines the next basic item based on the interruption point identifier and includes this basic item, along with other unexecuted basic items whose execution sequence follows it, into the set of basic items to be adjusted. Basic items that have already been executed or are currently being executed are not included in the set of basic items to be adjusted, thereby avoiding modifications to the process content that has already formed the actual equipment state.

[0135] The set of basic items to be adjusted can retain the original execution sequence number, basic item type, control parameters, input status, output status, and execution component occupancy information of each basic item. The online editing permissions of interrupt nodes also limit the types of modifications allowed in the set of basic items to be adjusted. For example, if a certain interrupt node only allows modification of control parameters, the device controller will not accept requests to add or delete basic items at that location.

[0136] Furthermore, the equipment controller or the editing terminal connected to the equipment parses the process adjustment request. The process adjustment request may include the operation type, target basic item identifier, insertion position, basic item data to be added, or parameter data to be modified. Basic item addition operations are used to insert new basic items into an unexecuted sequence; basic item deletion operations are used to remove specified unexecuted basic items; execution order adjustment operations are used to change the arrangement of unexecuted basic items; and control parameter modification operations are used to modify the parameter values ​​of specified unexecuted basic items.

[0137] For example, at the interruption point after centrifugation, the user can insert a waiting basic item before the original draining basic item, allowing the sample to stand for a predetermined time after centrifugation; the user can also modify the mixing time of subsequent mixing basic items. New basic items must belong to a type supported by the target device, their parameters must conform to the execution capability range in the device configuration data, and their ports and fluid paths must conform to the current consumable configuration data.

[0138] The device controller updates the set of basic items to be adjusted based on the target adjustment operation. When adding a basic item, the new basic item is inserted at the specified position, and the order relationship between the new basic item and the basic items before and after it is established; when deleting a basic item, the target basic item is removed from the set of basic items to be adjusted; when adjusting the execution order, the corresponding basic items are rearranged; when modifying control parameters, only the parameter values ​​of the specified basic item instances are updated. The data after the above updates are used as candidate sequences to be executed, but these candidate sequences cannot yet directly control the operation of the device.

[0139] Furthermore, the device controller uses the current device state as the preceding output state of the first basic item in the candidate execution sequence, and performs a matching and verification between the current device state and the input state of the first basic item. The current device state includes the actual fluid position at the interrupt node, the container liquid volume, the liquid circuit state, and the state of the actuator. The input state of the first basic item must be compatible with the above actual states.

[0140] For example, if the fluid is currently in the centrifuge cup and the centrifugation mechanism has stopped, and the user adds a basic item for feeding liquid from the cleaning fluid bag to the centrifuge cup as the first item in the candidate execution sequence, the device controller needs to check the remaining capacity of the centrifuge cup, the liquid volume in the cleaning fluid bag, the liquid path connectivity, and the availability of relevant pumps and valves. If any condition is not met, the calibration result indicates that the calibration has failed.

[0141] The equipment controller then performs step matching checks on each adjacent basic item in the candidate execution sequence and checks the connectivity of the relevant fluid lines according to the consumable configuration data. Execution component occupancy checks determine whether the pumps, valves, centrifugal mechanisms, and temperature control mechanisms required by the candidate execution sequence conflict with currently unreleased execution components. Control parameter modification operations also require parameter range checks based on the equipment configuration data.

[0142] When the adjustment verification result indicates that the verification fails, the equipment controller will not use the candidate execution sequence and will record the reasons such as mismatch status items, hydraulic circuit abnormalities, or execution component conflicts. Users can modify the adjustment request based on the reason information. When the adjustment verification result indicates that the verification passes, the equipment controller will reconfigure the execution sequence number according to the order of priority in the candidate execution sequence.

[0143] When a candidate sequence to be executed undergoes changes such as the addition, deletion, or reordering of basic items, the original interrupt node position may change. Therefore, the device controller needs to re-identify the execution boundaries of adjacent basic items and reconfigure the subsequent interrupt node identifiers according to the device's safety state conditions. After completing the configuration of the execution sequence number and interrupt node identifier, the candidate sequence to be executed becomes the updated sequence to be executed, and the device controller continues to execute subsequent processes according to this sequence.

[0144] The above online adjustment process takes the actual equipment status at the interruption node as the starting point for verification, and continues to use equipment configuration data, consumable configuration data and step status constraints for verification, which can prevent the modification content of the unexecuted process from becoming disconnected from the current equipment status.

[0145] In some embodiments of the present invention, the main interface includes Create Process, My Processes, and Recent Processes. The Recent Processes area can display the name of the most recently edited main process, its associated process library, and the last modification time; the number of processes displayed can be set according to the interface space. After the user selects a recent process, the process editing software reads the corresponding process data and enters the editing interface.

[0146] The process creation interface is used to select a main process or sub-process, and allows users to choose a reference process from their own processes, team library, or standard library. After selecting a reference process, the process editing software reads the equipment model, consumable model, and process hierarchy structure bound to the reference process, and displays the process name, reference process, functional module, equipment model, software version, and consumable model in the information confirmation interface. After the user confirms, the process editing software copies the reference process data and assigns a new process identifier; the original reference process remains unchanged.

[0147] The main process editing interface displays sub-processes in execution order. Users can add, delete, and drag to adjust the order of sub-processes. After selecting a sub-process, the interface displays its description, input status, output status, and open parameters. When an anomaly is detected during step matching verification, the interface provides a prompt to the next sub-process based on the anomaly indicator. Users can select the appropriate prompt to view the actual output status, input requirements, and reasons for the mismatch.

[0148] The subprocess editing interface displays basic items and nested subprocesses in execution order. When the user selects the inlet / outlet liquid basic item, the interface displays the inlet / outlet liquid type, starting port, target port, liquid density, target volume, fluid flow rate, and termination judgment method, and displays the corresponding ports and fluid paths in the consumables illustration area according to the consumables configuration data. When the user selects the centrifugation basic item, the interface displays the target rotation speed, centrifugation time, acceleration, and deceleration, and verifies the parameter range according to the equipment configuration data.

[0149] Furthermore, the sub-process editing interface provides input state constraints, output state descriptions, and parameter open setting areas. Input and output states are saved using structured state items, which not only store text descriptions for user reading but also state type, state value, allowed range, and necessity indicator. The parameter open setting area is used to select whether basic parameters can be edited in the main process; the default state can be set to not open.

[0150] In some embodiments of the present invention, the simulation interface displays the process flow according to the hierarchical relationship between sub-processes and basic items, while using the execution sequence of basic items as the actual simulation order. Before starting the simulation, the user sets the liquid bag name and initial liquid volume, and the process editing software initializes the container state accordingly.

[0151] During the simulation, the interface displays all liquid bags and real-time liquid volume, current liquid path, pump running direction, valve status, centrifuge cup speed and rotation direction, current temperature, estimated running time, and current running time. The displayed data comes from the simulated equipment status derived from the state simulation and does not require driving the actual actuators.

[0152] The simulation operation supports start, pause, resume, and terminate operations, and can advance the simulation time at 1x, 2x, 4x, or 8x speed. The step jump operation can be used to view the simulation status corresponding to different basic items, but when jumping will change the basis of subsequent state calculations, the process editing software needs to re-derive the simulation from the saved simulation status before the corresponding step, and does not directly skip the state changes caused by unexecuted basic items.

[0153] When a simulation anomaly is detected, the process editing software pauses the simulation, associates the abnormal basic items, abnormal equipment components, and abnormal fluid circuits, and displays the status data before and after the anomaly occurred. After the user modifies the process, the simulation equipment status is reinitialized, and the process editing software re-performs the state simulation according to the modified basic item execution sequence.

[0154] In some embodiments of the present invention, process comparison is limited to processes at the same level, with main processes compared to main processes and sub-processes compared to sub-processes. Users can select two processes at the same level from My Processes, Team Library, and Standard Library.

[0155] The process editing software establishes node correspondences based on node identifiers, node types, parent node relationships, and execution positions. Nodes that exist only on one side of two processes are identified as newly added or deleted nodes. Nodes that exist on both sides but differ in control parameters, input states, output states, or open parameters are identified as modified nodes. Nodes with different execution positions are identified as having a change in sequence.

[0156] The comparison results can be displayed in two separate process areas, with different difference identifiers set for the differing nodes. After the user selects a differing node, the process editing software displays the sub-process to which the node belongs, the type of basic item, the data before modification, the data after modification, and the version number. The difference identifiers are part of the structured comparison results, and the interface colors are only used for auxiliary display.

[0157] The hierarchical process editing system based on automatic verification of process steps provided by the present invention will be described below. The hierarchical process editing system based on automatic verification of process steps described below can be referred to in correspondence with the hierarchical process editing method based on automatic verification of process steps described above, and will not be repeated here.

[0158] like Figure 2 The diagram shown is a structural schematic of a hierarchical process editing system based on automatic verification of process steps provided by the present invention. The hierarchical process editing system based on automatic verification of process steps includes the following modules: The acquisition module 210 is used to acquire process creation information, equipment configuration data of the target automated process equipment, and consumable configuration data adapted to the target automated process equipment. The hierarchical modeling module 220 is used to perform hierarchical modeling processing based on the process creation information, the equipment configuration data, and the consumable configuration data to obtain a hierarchical process model; wherein, the hierarchical process model includes at least a main process, sub-processes, and basic items, the main process includes at least sub-processes arranged in execution order, the sub-processes include at least one of basic items and nested sub-processes, and the basic items are process operations that the target automated process equipment can directly execute; The parameter opening module 230 is used to obtain the input state constraints, output state descriptions and open parameter information of each sub-process in the hierarchical process model, and to perform parameter opening processing on the hierarchical process model based on the open parameter information to obtain an editable process model. The step verification module 240 is used to perform step matching verification on the editable process model based on the output state description of adjacent sub-processes, input state constraints, equipment configuration data and consumable configuration data, and obtain step verification results. The recursive expansion module 250 is used to perform recursive expansion processing on the editable process model when the step verification result meets the preset pass conditions, to obtain the basic item execution sequence, and to generate a process data package based on the equipment configuration data, the consumable configuration data and the basic item execution sequence.

[0159] Figure 3 An example is a schematic diagram of the physical structure of an electronic device, such as... Figure 3As shown, the electronic device may include: a processor 310, a communication interface 320, a memory 330, and a communication bus 340, wherein the processor 310, the communication interface 320, and the memory 330 communicate with each other through the communication bus 340. The processor 310 can call logical instructions in the memory 330 to execute a hierarchical process editing method based on automatic verification of process steps. This method includes: acquiring process creation information, equipment configuration data of the target automated process equipment, and consumable configuration data adapted to the target automated process equipment; performing hierarchical modeling processing based on the process creation information, the equipment configuration data, and the consumable configuration data to obtain a hierarchical process model; wherein the hierarchical process model includes at least a main process, sub-processes, and basic items, the main process includes at least sub-processes arranged in execution order, the sub-processes include at least one of basic items and nested sub-processes, and the basic items are those that the target automated process equipment can directly... The process operation is executed; the input state constraints, output state descriptions, and open parameter information of each sub-process in the hierarchical process model are obtained, and parameter opening processing is performed on the hierarchical process model based on the open parameter information to obtain an editable process model; based on the output state descriptions, input state constraints, equipment configuration data, and consumable configuration data of adjacent sub-processes, step matching verification is performed on the editable process model to obtain step verification results; when the step verification results meet the preset pass conditions, the editable process model is recursively expanded to obtain the basic item execution sequence, and a process data package is generated based on the equipment configuration data, the consumable configuration data, and the basic item execution sequence.

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

[0161] On the other hand, the present invention also provides a computer program product, which includes a computer program that can be stored on a non-transitory computer-readable storage medium. When the computer program is executed by a processor, the computer can execute the hierarchical process editing method based on automatic verification of process steps provided by the above methods. This method includes: acquiring process creation information, equipment configuration data of the target automated process equipment, and consumable configuration data adapted to the target automated process equipment; performing hierarchical modeling processing based on the process creation information, the equipment configuration data, and the consumable configuration data to obtain a hierarchical process model; wherein the hierarchical process model includes at least a main process, sub-processes, and basic items, the main process includes at least sub-processes arranged in execution order, and the sub-processes include basic items. The process involves at least one of nested sub-processes, where the basic item is a process operation that the target automated process equipment can directly execute; obtaining the input state constraints, output state descriptions, and open parameter information of each sub-process in the hierarchical process model, and performing parameter opening processing on the hierarchical process model based on the open parameter information to obtain an editable process model; performing step matching verification on the editable process model based on the output state descriptions, input state constraints, equipment configuration data, and consumable configuration data of adjacent sub-processes to obtain a step verification result; when the step verification result meets the preset pass conditions, performing recursive expansion processing on the editable process model to obtain a basic item execution sequence, and generating a process data package based on the equipment configuration data, the consumable configuration data, and the basic item execution sequence.

[0162] In another aspect, the present invention also provides a non-transitory computer-readable storage medium storing a computer program thereon. When executed by a processor, the computer program implements a hierarchical process editing method based on automatic verification of process steps provided by the methods described above. This method includes: acquiring process creation information, equipment configuration data of a target automated process equipment, and consumable configuration data adapted to the target automated process equipment; performing hierarchical modeling processing based on the process creation information, the equipment configuration data, and the consumable configuration data to obtain a hierarchical process model; wherein the hierarchical process model includes at least a main process, sub-processes, and basic items; the main process includes at least sub-processes arranged in execution order; and the sub-processes include at least one of basic items and nested sub-processes. The basic items are the process operations that the target automated process equipment can directly execute; the input state constraints, output state descriptions, and open parameter information of each sub-process in the hierarchical process model are obtained, and the hierarchical process model is processed to open parameters based on the open parameter information to obtain an editable process model; based on the output state descriptions, input state constraints, equipment configuration data, and consumable configuration data of adjacent sub-processes, the editable process model is checked for step matching to obtain a step check result; when the step check result meets the preset pass conditions, the editable process model is recursively expanded to obtain the basic item execution sequence, and a process data package is generated based on the equipment configuration data, the consumable configuration data, and the basic item execution sequence.

[0163] The system embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. Those skilled in the art can understand and implement this without any creative effort.

[0164] Through the above description of the embodiments, those skilled in the art can clearly understand that each embodiment can be implemented by means of software plus necessary general-purpose hardware platforms, and of course, it can also be implemented by hardware. Based on this understanding, the above technical solutions, in essence or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the methods described in the various embodiments or some parts of the embodiments.

[0165] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, and not to limit them; although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features; and these modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims

1. A hierarchical process editing method based on automatic verification of process steps, characterized in that, include: Acquire process creation information, equipment configuration data of the target automated process equipment, and consumable configuration data adapted to the target automated process equipment; Based on the process creation information, the equipment configuration data, and the consumable configuration data, a hierarchical modeling process is obtained; wherein, the hierarchical process model includes at least a main process, sub-processes, and basic items, the main process includes at least sub-processes arranged in execution order, the sub-processes include at least one of basic items and nested sub-processes, and the basic items are process operations that the target automated process equipment can directly execute; The input state constraints, output state descriptions, and open parameter information of each sub-process in the hierarchical process model are obtained, and the hierarchical process model is processed to open parameters based on the open parameter information to obtain an editable process model. Based on the output state descriptions and input state constraints of adjacent sub-processes, the equipment configuration data and the consumable configuration data, the editable process model is subjected to step matching verification to obtain the step verification results. When the verification result of the step meets the preset pass conditions, the editable process model is recursively expanded to obtain the basic item execution sequence, and a process data package is generated based on the equipment configuration data, the consumable configuration data and the basic item execution sequence.

2. The layered process editing method based on automatic verification of process steps according to claim 1, characterized in that, The hierarchical modeling process based on the process creation information, the equipment configuration data, and the consumable configuration data yields a hierarchical process model, including: Based on the process creation information, the process type of the process to be created is determined, and a main process node or a sub-process node is established according to the process type to obtain the process root node; Based on the equipment configuration data, the basic item types supported by the target automated process equipment are determined, and based on the consumable configuration data, the available ports and available fluid lines corresponding to each basic item type are determined, thus obtaining a set of available process nodes; Based on the process editing instructions, the process nodes to be added are determined from the set of available process nodes, and the hierarchical relationship and execution order relationship between the process nodes to be added are established under the process root node to obtain the initial process model; Circular reference detection is performed on the nested sub-processes in the initial process model, and if no circular reference exists, node identifiers are configured for the main process node, sub-process node, and basic item node in the initial process model to obtain the hierarchical process model.

3. The layered process editing method based on automatic verification of process steps according to claim 1, characterized in that, The editable process model is subjected to step matching verification based on the output state description of adjacent sub-processes, input state constraints, equipment configuration data, and consumable configuration data to obtain step verification results, including: According to the execution order in the editable process model, the preceding and following sub-processes in adjacent sub-processes are obtained to obtain adjacent sub-process pairs; Based on the preset state type, the output state description of the previous sub-process and the input state constraint of the next sub-process are associated to obtain the state item to be verified. Based on the equipment configuration data and the consumable configuration data, the input allowed status, liquid circuit connection condition and execution component status condition corresponding to each status item to be verified are determined to obtain the status verification conditions. Based on the output state description of the previous sub-process and the state verification conditions, the adjacent sub-processes are matched to obtain the adjacent step matching results. The step verification result is generated based on the matching results of the corresponding adjacent steps for each adjacent sub-process.

4. The layered process editing method based on automatic verification of process steps according to claim 3, characterized in that, The step verification result is generated based on the matching results of adjacent steps for each adjacent sub-process, including: From the adjacent step matching results, determine the target adjacent sub-process pairs that do not meet the state verification conditions; Based on the corresponding state items to be verified for the target adjacent sub-processes, the output state value of the previous sub-process and the input requirement value of the next sub-process are determined to obtain state difference information. Based on the state difference information, at least one mismatch type is determined, and mismatch cause information is generated based on the mismatch type; wherein, the at least one mismatch type includes: position mismatch, state value mismatch, fluid circuit disconnection, and execution component state mismatch; The mismatch reason information is associated with the next sub-process in the target adjacent sub-process pair, and an abnormal prompt indicator is set for the next sub-process. The step verification result is generated based on the matching status of each adjacent sub-process pair, the mismatch reason information, and the abnormal prompt identifier.

5. The layered process editing method based on automatic verification of process steps according to claim 1, characterized in that, The step of performing parameter opening processing on the hierarchical process model based on the open parameter information to obtain an editable process model includes: Based on the open parameter information, the target open parameter is determined from the control parameters of the basic items within the sub-process; Based on the sub-process identifier of the sub-process, the basic item identifier of the basic item, and the parameter identifier of the target open parameter, determine the parameter access path corresponding to the target open parameter; Based on the parameter access path, an editable parameter item associated with the target open parameter is established in the main process, and the allowable adjustment range of the editable parameter item is determined based on the parameter constraint information of the target open parameter. Obtain the parameter modification value set for the editable parameter item, and associate the parameter modification value with the parameter access path to obtain parameter coverage data; The editable parameter items, the parameter access path, and the parameter overriding data are written into the hierarchical process model, while keeping the original control parameters of the referenced sub-process unchanged, to obtain the editable process model.

6. The layered process editing method based on automatic verification of process steps according to claim 5, characterized in that, When the verification result of the above step meets the preset pass condition, the editable process model is recursively expanded to obtain the basic item execution sequence, including: According to the execution order in the editable process model, read the process nodes corresponding to each sub-process in sequence; When the process node is a basic item node, the basic item node is written into the candidate execution sequence. When the process node is a nested sub-process node, the next-level process node in the nested sub-process node is recursively expanded to obtain the candidate execution sequence. Based on the parameter access path, the corresponding parameter coverage data is obtained from the editable process model, and the parameter coverage data is written into the corresponding basic item instance to obtain the basic item to be executed; Based on the execution order of each basic item to be executed in the editable process model, an execution sequence number is configured for each basic item to be executed. The execution sequence of the basic items is obtained by associating the execution sequence number, control parameters, input status, output status, and execution component occupancy information of each basic item to be executed.

7. The layered process editing method based on automatic verification of process steps according to claim 1, characterized in that, The process data package is generated based on the equipment configuration data, the consumable configuration data, and the basic item execution sequence, including: Based on the equipment configuration data and the consumable configuration data, a simulated equipment state is established; wherein, the simulated equipment state includes at least the container state, the liquid circuit state, and the actuator state; Based on the execution sequence of the basic items, the state of the simulated device is deduced to obtain the simulation operation results; Based on the simulation results, an execution anomaly is determined, and an execution determination result is obtained; When the execution determination result indicates that there is no preset operational abnormality, the basic item execution sequence is encapsulated to obtain the process data package.

8. The layered process editing method based on automatic verification of process steps according to claim 7, characterized in that, The process of performing state deduction on the simulated device state based on the execution sequence of the basic items to obtain the simulation operation results includes: The current basic item is obtained according to the execution sequence number in the basic item execution sequence, and the basic item type and control parameters corresponding to the current basic item are obtained; The corresponding state transition rule is determined based on the basic item type; wherein, the state transition rule is used to characterize the state change relationship of the simulation device before and after the execution of the current basic item; Based on the control parameters and the state transition rules, the state of the simulation device is updated to obtain the current simulation state; Based on the equipment configuration data and the consumable configuration data, anomaly detection is performed on the current simulation state to obtain simulation anomaly information; wherein, the simulation anomaly information is used to characterize at least one of the following operational anomalies: insufficient fluid, container capacity exceeding limit, fluid circuit disconnection, execution component state conflict, and repeated occupation of execution components; The simulation results are generated based on the current simulation status of each basic item and the simulation anomaly information.

9. The layered process editing method based on automatic verification of process steps according to claim 7, characterized in that, When the execution determination result indicates that there is no preset operational abnormality, the basic item execution sequence is encapsulated to obtain the process data package, including: Candidate interruption nodes are determined based on the execution boundaries of adjacent basic items in the execution sequence of the basic items; Based on the output state of the previous basic item and the input state of the next basic item corresponding to the candidate interrupt node, the device safety status conditions corresponding to each candidate interrupt node are determined. Based on the device safety status conditions, a target interrupt node that allows adjustment of the unexecuted basic item is determined from the candidate interrupt nodes, and an interrupt node identifier is set for the target interrupt node; Process execution data is generated based on the execution sequence of the basic items, and process traceability data is generated based on the hierarchical process model; The process execution data, the process traceability data, the interruption node identifier, and the data integrity verification information are encapsulated to obtain the process data package.

10. The layered process editing method based on automatic verification of process steps according to claim 9, characterized in that, When the execution determination result indicates that there is no preset operational abnormality, after encapsulating the basic item execution sequence to obtain the process data packet, the method includes: The process data package is subjected to integrity and applicability checks to obtain data package verification results; wherein, the applicability check is used to determine whether the equipment model, consumable model and control protocol version corresponding to the process data package match the target automated process equipment; When the data packet verification result indicates that the verification is successful, the process execution data is parsed to obtain the equipment control sequence; Based on the device control sequence, the corresponding execution component is controlled to execute each basic item, and the running status of the execution component is obtained to obtain the current device status; When execution reaches the interruption node identifier, the node status is determined based on the current device status and the corresponding device security status conditions to obtain the node determination result; If the node determination result indicates that no adjustment has been made, continue running the next node; When the node determination result indicates that adjustment is allowed and a process adjustment request is received, the unexecuted basic items are adjusted based on the process adjustment request to obtain an updated sequence to be executed. The process is then executed based on the updated sequence to be executed or the original sequence to be executed without adjustment to obtain the process execution result.

11. A hierarchical process editing system based on automatic verification of process steps, characterized in that, include: The acquisition module is used to acquire process creation information, equipment configuration data of the target automated process equipment, and consumable configuration data adapted to the target automated process equipment. A hierarchical modeling module is used to perform hierarchical modeling processing based on the process creation information, the equipment configuration data, and the consumable configuration data to obtain a hierarchical process model; wherein, the hierarchical process model includes at least a main process, sub-processes, and basic items, the main process includes at least sub-processes arranged in execution order, the sub-processes include at least one of basic items and nested sub-processes, and the basic items are process operations that the target automated process equipment can directly execute; The parameter opening module is used to obtain the input state constraints, output state descriptions and open parameter information of each sub-process in the hierarchical process model, and to perform parameter opening processing on the hierarchical process model based on the open parameter information to obtain an editable process model. The step verification module is used to perform step matching verification on the editable process model based on the output state description of adjacent sub-processes, input state constraints, equipment configuration data and consumable configuration data, and obtain the step verification result. The recursive expansion module is used to recursively expand the editable process model when the step verification result meets the preset pass conditions, to obtain the basic item execution sequence, and to generate a process data package based on the equipment configuration data, the consumable configuration data and the basic item execution sequence.

12. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by the processor, it implements the layered process editing method based on automatic verification of process steps as described in any one of claims 1 to 10.

Images