Method and system for dynamic coordination management of printing resource operation and information flow

Abstract

The application provides a printing resource operation and maintenance and information flow dynamic collaborative management method and system, relates to the technical field of data processing, and the method comprises the following steps: extracting an order node in a to-be-promoted state and front and subsequent nodes thereof, identifying an already propagated field and a to-be-propagated field and determining a propagation boundary, determining a cutting-in range of an operation and maintenance record in the order node, identifying a lock control degree of whether the order node can continue to circulate when the operation and maintenance record cuts into an order flow, obtaining a node restraint value, identifying a process back-connection degree of a lock control node continuing to execute after the operation and maintenance record is closed, obtaining a re-investment back-connection value, identifying and constructing an original order flow path, an original equipment back-connection path, a replacement resource path and a continuous lock control path, and obtaining a printing collaborative management scheme. The application can realize dynamic collaborative management between a printing resource operation and maintenance state and an order information flow, avoids continuous promotion of an order node when equipment cannot be put into production, and avoids incorrect calling of related resources.

Description

Technical Field

[0001] This invention relates to the field of collaborative management technology for printing production information and resource operation and maintenance, and in particular to a method and system for dynamic collaborative management of printing resource operation and maintenance and information flow. Background Technology

[0002] Existing methods for dynamic collaborative management of printing resource operation and information flow generally establish printing resource files such as orders, equipment, materials, personnel, and process parameters through a production management platform. Production tasks are generated based on order delivery dates, equipment capacity, and process routes. At the same time, equipment operating status, maintenance records, fault alarms, and material entry and exit information are collected. Then, business nodes such as production scheduling, material preparation, quality inspection, and maintenance are linked and managed through workflow or message notification mechanisms.

[0003] However, existing solutions may encounter issues with the timely constraint of maintenance status on the production process during multi-system information linkage. Taking continuous scheduling of short-run printing orders as an example, when a printing press enters maintenance or debugging status due to registration deviation, although the maintenance system has recorded that the equipment is in a pending state, the production process may still issue the next batch of orders to the equipment according to the original production schedule, and simultaneously trigger material preparation, process parameter loading, and personnel assignment, resulting in the order process node having been advanced, but the corresponding equipment actually not being able to be put into production. Summary of the Invention

[0004] The purpose of this invention is to provide a method and system for dynamic collaborative management of printing resource operation and maintenance and information flow, aiming to solve the problems mentioned in the background art.

[0005] To solve the above-mentioned technical problems, the technical solution of the present invention is as follows:

[0006] Firstly, a method for dynamic collaborative management of printing resource operation and information flow, the method comprising:

[0007] Obtain order node data, equipment operation and maintenance data, and resource usage data to obtain basic printing data;

[0008] Based on the basic printing data, the order nodes in the pending state, their predecessor nodes and successor nodes are extracted, the propagated fields and the fields to be propagated are identified and the propagation boundaries are determined to obtain the process propagation trajectory data.

[0009] Based on the target device number of each order node in the process propagation trajectory data, the operation and maintenance record is extracted and embedded into the propagation boundary to determine the entry range of the operation and maintenance record in the order node, thus obtaining the operation and maintenance entry domain data.

[0010] Based on the operation and maintenance entry domain data, identify the degree of control over whether the order node can continue to flow when the operation and maintenance record enters the order process, and obtain the node restraint value;

[0011] Identify the locking and advancing nodes based on the node constraint value and the preset constraint value, retain the resource occupancy relationship in the propagated fields, freeze the resource call relationship in the fields to be propagated, and obtain the locking path data;

[0012] Based on the lock control path data, identify the degree of process reconnection after the operation and maintenance record is closed, and obtain the reconnection value;

[0013] Based on the resubmission and return value, the original order process path, the original equipment return path, the replacement resource path, and the continuous lock control path are identified and constructed to obtain a printing collaborative management solution.

[0014] Furthermore, based on the printing baseline data, order nodes in the pending progress stage, along with their predecessor and successor nodes, are extracted. Already propagated fields and fields to be propagated are identified, and propagation boundaries are determined to obtain process propagation trajectory data, including:

[0015] Based on the order node data, extract the order nodes whose node status is pending, and extract the predecessor and successor nodes of each order node according to the order number to obtain the node adjacency data.

[0016] Based on the node adjacency data, extract the business fields that form resource occupancy relationships in each order node, and write them into the propagated fields according to their positions in the order nodes to obtain the propagated field data.

[0017] Based on the node adjacency data, extract the business fields that subsequent nodes need to call but for which order nodes have not yet formed a resource occupation relationship, and write them into the fields to be propagated according to their positions in the order nodes to obtain the data of the fields to be propagated.

[0018] Based on the data of the propagated fields and the data of the fields to be propagated, the handover position between the propagated fields and the fields to be propagated is determined according to the node order, the preceding node and the subsequent node, and the handover position is marked as the propagation boundary of the order node, thus obtaining the process propagation trajectory data.

[0019] Furthermore, based on the target device number of each order node in the process propagation trajectory data, maintenance records are extracted and embedded into the propagation boundary to determine the entry range of the maintenance record in the order node, thus obtaining maintenance entry domain data, including:

[0020] Based on the process propagation trajectory data, the target device number and propagation boundary of each order node are extracted, and the target device number is associated with the propagation boundary to obtain the device boundary data;

[0021] Based on the equipment boundary data and equipment operation and maintenance data, extract the operation and maintenance records that correspond to the target equipment number and do not have a closure mark, and write the operation and maintenance records into the order node to obtain the operation and maintenance data to be embedded;

[0022] Based on the operation and maintenance data to be embedded, identify the starting position of the operation and maintenance record in the business field of the order node, and embed the starting position of the record into the node position of the propagation boundary to obtain the operation and maintenance boundary embedding data.

[0023] Based on the embedded data of the operation and maintenance boundary, the business fields covered from the record start position to the unclosed state are extracted along the node sequence of the order node, and the business fields are marked as the entry range of the operation and maintenance record in the order node to obtain the operation and maintenance entry domain data.

[0024] Furthermore, based on the operation and maintenance entry domain data, the degree of control over whether an order node can continue to flow when the operation and maintenance record enters the order process is identified, resulting in a node constraint value, including:

[0025] Based on the operation and maintenance entry domain data, calculate the proportion of the number of business fields covered by the entry range relative to the total number of business fields in the order node, identify the coverage degree formed by the operation and maintenance records within the current order node, and obtain the entry coverage item; calculate the interaction clamping degree between the business fields on the propagated side and the business fields on the side to be propagated within the same entry range, and obtain the boundary clamping item.

[0026] Based on the operation and maintenance entry domain data, calculate the correlation ratio of the operation and maintenance record to adjacent order nodes, identify the degree of connection between the operation and maintenance record and the preceding and following process nodes other than the current order node, and obtain the node connection items.

[0027] By integrating the entry coverage item, boundary clamping item, and node connection item, the degree of locking formed by the continued flow of order nodes when the operation and maintenance record enters the order process is identified, and the node restraint value is obtained.

[0028] Furthermore, based on the node constraint value and the preset constraint value, the locking node and the advancing node are identified, and the resource occupancy relationship in the propagated fields is retained, while the resource call relationship in the fields to be propagated is frozen, thus obtaining the locking path data, including:

[0029] By marking order nodes whose node restraint values ​​reach the preset restraint value as lock control nodes and order nodes whose node restraint values ​​do not reach the preset restraint value as advance nodes, node splitting data is obtained;

[0030] Based on the node distribution data, extract the propagated fields of the lock control node and the resource occupancy relationship that has been formed, bind the resource occupancy relationship with the lock control node, and obtain the occupancy retention data;

[0031] Based on the node distribution data, extract the fields to be propagated of the lock control node and the resource call relationships that have not yet been executed, and mark the resource call relationships with the lock control node to obtain the call freeze data;

[0032] Based on the reserved data and the frozen data, the advancing nodes, locking nodes, resource occupancy relationships, and resource call relationships are written into the locking path according to the node order of the order nodes. The path status of the advancing nodes is marked as continue advancing, and the path status of the locking nodes is marked as locking waiting, thus obtaining the locking path data.

[0033] Furthermore, based on the lock control path data, the degree of process reconnection after the operation and maintenance record closure is identified, and the re-connection value is obtained, including:

[0034] Based on the maintenance record closure marker in the equipment maintenance data, identify the gating degree of the maintenance record closure status on the locking node's entry into the reconnection process, and obtain the closure gating item; identify the degree of restoration between the retained resource occupation relationship and the frozen resource call relationship of the locking node after the maintenance record is closed, and obtain the reconnection matching item.

[0035] Based on the occupancy retention data and the call freeze data, calculate the number of relationships between the original resource number and the original business field after the operation and maintenance record is closed, identify the degree to which the original materials and personnel of the lock control node are still in a reconnectable state when the lock control node is re-entered, and obtain the state retention item; based on the lock control path data, identify whether the lock control node can maintain the degree of process connection with the subsequent order node after the lock control node is reconnected, and obtain the path continuity item;

[0036] By integrating the closing gating item, the acceptance matching item, the state maintenance item, and the path continuity item, the degree of process reconnection is identified, and the lock control node continues to execute the original process after the operation and maintenance record is closed, thus obtaining the reconnection value.

[0037] Furthermore, based on the resubmission return value, the original order process path, original equipment return path, replacement resource path, and continuous lockout path are identified and constructed to obtain a printing collaborative management solution, including:

[0038] Based on the lock control path data, the advancement nodes with the path status of "continue advancing" and the lock control nodes with the path status of "lock control waiting" are extracted. The order nodes are then divided into process advancement nodes, equipment return nodes, resource replacement nodes, and continuous lock control nodes according to the node status and re-deployment return value, thus obtaining the path node allocation data.

[0039] Based on the path node allocation data, extract the order number, node order and resource usage relationship of the process advancement node, and write the process advancement node into the original order process path according to the node order.

[0040] Based on the path node allocation data, extract the device reconnection nodes whose reconnection value reaches the preset reconnection value, and write the target device number, reserved resource occupancy relationship and frozen resource call relationship of the device reconnection node into the original device reconnection path;

[0041] Based on the path node allocation data, extract the resource replacement nodes whose reconnection value has not reached the preset reconnection value, and search for unoccupied resource relationships in the resource occupancy data according to the business field of the resource replacement node. Write the resource replacement nodes with unoccupied resource occupancy relationships into the replacement resource path. For resource replacement nodes with no available resource relationships, mark them as continuous lock control nodes and write them into the continuous lock control path.

[0042] By writing the original order process path, original equipment return path, replacement resource path, and continuous lockout path into the same collaborative processing record according to the order number and node sequence, a printing collaborative management solution is obtained.

[0043] Secondly, a dynamic collaborative management system for printing resource operation and information flow, the system comprising:

[0044] The data module is used to acquire order node data, equipment operation and maintenance data, and resource usage data to obtain basic printing data;

[0045] The propagation trajectory module is used to extract the order nodes in the pending state, their predecessor nodes and successor nodes, based on the printing basic data, identify the propagated fields and the fields to be propagated, and determine the propagation boundary to obtain the process propagation trajectory data.

[0046] The entry domain module is used to extract maintenance records and embed them into the propagation boundary based on the target device number of each order node in the process propagation trajectory data, determine the entry range of the maintenance record in the order node, and obtain maintenance entry domain data.

[0047] The restraint module is used to identify the degree of control over whether an order node can continue to flow when the operation and maintenance records enter the order process, based on the operation and maintenance entry domain data, and to obtain the node restraint value;

[0048] The lock control path module is used to identify lock control nodes and advance nodes based on node constraint values ​​and preset constraint values, retain the resource occupancy relationships in the propagated fields, freeze the resource call relationships in the fields to be propagated, and obtain lock control path data;

[0049] The reconnection module is used to identify the degree of process reconnection of the lock control node after the operation and maintenance record is closed, based on the lock control path data, and to obtain the reconnection value.

[0050] The collaborative management module is used to identify and construct the original order process path, the original equipment return path, the replacement resource path, and the continuous lock-in path based on the resubmission return value, so as to obtain the printing collaborative management solution.

[0051] The above-described solution of the present invention has at least the following beneficial effects:

[0052] This invention extracts order nodes in the pending progress state, along with their predecessor and successor nodes, identifies propagated and pending propagation fields, and determines propagation boundaries. It transforms the order process from a simple record of node status into a data structure containing relationships between preceding and succeeding nodes, propagated business information, pending propagation business information, and propagation boundaries. Order nodes not only represent a specific business step but also include their position in the order process and their association with adjacent nodes. Fields that have resulted in resource usage or business flow are categorized as propagated, while fields that have not yet generated resource usage or propagated to subsequent processes are categorized as pending propagation. The intersection between these two categories is used as the propagation boundary. The system can represent, at the data level, which business scope the order process has progressed to and which subsequent business fields have not yet been triggered. This transforms the original order process, which proceeded sequentially according to the production schedule, into a business data structure with identifiable propagation status and marked propagation boundaries.

[0053] This invention extracts maintenance records by identifying the target device number at each order node and embeds them into the propagation boundary. This determines the scope of the maintenance record within the order node, ensuring that device maintenance events have a clear target, node, and scope in the order process data. The maintenance record is converted into maintenance entry domain data. Within the order node, the system can indicate which business fields the maintenance record covers, which propagation boundaries it affects, and which target device number it corresponds to. This provides clear input for calculating the constraint value of subsequent nodes, transforming device maintenance data from external status prompts into a computable entry domain in the order process data.

[0054] This invention obtains a node constraint value by identifying the degree of control over order nodes when maintenance records are integrated into the order process. Whether a process node continues to flow typically depends on business status, resource status, and constraints. By using the node constraint value, the impact of a maintenance record on an order node after being integrated into the order process is no longer simply described as equipment malfunction or unavailability, but rather forms a data result that can be compared with a preset constraint value. This node constraint value serves as the basis for subsequent identification of locked and advancing nodes, providing a unified data judgment standard for order process control. For the same equipment maintenance record, different order nodes may be at different propagation stages, and the distribution of propagated and pending propagation fields may also differ. Therefore, the node constraint value can transform the relationship between the maintenance integration scope and the order node flow status into numerical or hierarchical control data, compressing the complex relationship between equipment maintenance events, order node status, and process propagation boundaries into data indicators.

[0055] This invention identifies locking and advancing nodes and retains resource occupancy relationships in the propagated fields while freezing resource call relationships in the fields to be propagated. This prevents the system from completely halting or releasing the order process. Instead, it uses node constraint values ​​as the basis for dividing order nodes into locking and advancing nodes and applies different data processing to resource relationships at different propagation stages. Retaining resource occupancy relationships in the propagated fields indicates that the relevant business data has already formed occupancy results in the process, preventing the data relationship from being erroneously released during the locking process. Freezing resource call relationships in the fields to be propagated indicates that unexecuted resource calls will no longer propagate to subsequent nodes, preventing the generation of subsequent business data such as material preparation, equipment tasks, personnel dispatch, or parameter loading. The order process is thus split at the data level into parts that can continue to advance and parts that need to be processed, providing a data foundation for subsequent re-entry and reconnection calculations.

[0056] This invention obtains a re-entry reconnection value by identifying the degree of process reconnection of the lock control node after the maintenance record is closed. The system not only generates a lock control path when the equipment maintenance record is not closed, but also continues to use the lock control path data to calculate whether the lock control node has the data conditions to continue execution along the original process after the maintenance record is closed. Maintenance closure does not necessarily mean that the original order node can be directly resumed, because there may have been changes in resource usage, frozen pending calls, changes in the order process, or changes in resource availability. The system uses these data states formed during the lock control period as input to generate the re-entry reconnection value. This indicates the reconnection relationship between the lock control node and the original process after the maintenance is closed. This reconnection value is not a judgment on the equipment maintenance result itself, but a processing result of the connection relationship between order process data, resource usage data, and frozen call data. This transforms the business question of whether the order returns to the original process after the maintenance is closed into a data indicator that can participate in path selection. It can connect the lock control path data formed in the previous stage with the collaborative management scheme in the next stage, so that the lock control data when the anomaly occurs and the recovery data after the anomaly is closed are in the same processing chain, forming a data connection relationship from process blockage to process reconnection. Attached Figure Description

[0057] Figure 1 This is a flowchart of the printing resource operation and maintenance and information flow dynamic collaborative management method provided in the embodiments of the present invention. Detailed Implementation

[0058] Exemplary embodiments of the present disclosure will now be described in more detail with reference to the accompanying drawings. While exemplary embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be implemented in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.

[0059] like Figure 1 As shown, embodiments of the present invention propose a method for dynamic collaborative management of printing resource operation and maintenance and information flow, the method comprising:

[0060] Obtain order node data, equipment operation and maintenance data, and resource usage data to obtain basic printing data;

[0061] Based on the basic printing data, the order nodes in the pending state, their predecessor nodes and successor nodes are extracted, the propagated fields and the fields to be propagated are identified and the propagation boundaries are determined to obtain the process propagation trajectory data;

[0062] Based on the target device number of each order node in the process propagation trajectory data, the operation and maintenance record is extracted and embedded into the propagation boundary to determine the entry range of the operation and maintenance record in the order node, thus obtaining the operation and maintenance entry domain data.

[0063] Based on the operation and maintenance entry domain data, identify the degree of control over whether the order node can continue to flow when the operation and maintenance record enters the order process, and obtain the node restraint value;

[0064] Identify the locking and advancing nodes based on the node constraint value and the preset constraint value, retain the resource occupancy relationship in the propagated fields, freeze the resource calling relationship in the fields to be propagated, and obtain the locking path data;

[0065] Based on the lock control path data, identify the degree of process reconnection after the operation and maintenance record is closed, and obtain the reconnection value;

[0066] Based on the resubmission and return value, the original order process path, the original equipment return path, the replacement resource path, and the continuous lock control path are identified and constructed to obtain a printing collaborative management solution.

[0067] In this embodiment of the invention, order node data, equipment operation and maintenance data, and resource usage data are acquired to obtain printing basic data, providing a unified data source for subsequent identification of process propagation trajectory, operation and maintenance entry scope, node constraint value, and collaborative handling path. Based on the printing basic data, order nodes in the pending advancement state, along with their predecessor and successor nodes, are extracted. Propagated fields and fields to be propagated are identified, and propagation boundaries are determined to obtain process propagation trajectory data, representing the business position that the order process has advanced to, and the data range that subsequent processes have not yet spread. Based on the target device number of each order node in the process propagation trajectory data, operation and maintenance records are extracted and embedded into the propagation boundary to determine the entry scope of the operation and maintenance record in the order node, obtaining operation and maintenance entry domain data. This determines which order nodes, business fields, and resource call relationships to be propagated are specifically affected by the operation and maintenance record, providing a clear data range for subsequent node constraint value calculation.

[0068] Based on the operation and maintenance (O&M) entry domain data, the degree of control over order nodes when O&M records enter the order process is identified, resulting in node constraint values. These values ​​allow for the identification of controlled and advancing nodes, rather than solely relying on equipment status fields or manual judgment to determine order continuation. Controlled and advancing nodes are identified based on node constraint values ​​and preset constraint values. Resource occupancy relationships in the propagated fields are retained, while resource call relationships in the fields to be propagated are frozen, resulting in control path data and providing a data foundation for callback judgment. Based on the control path data, the degree of process callback for controlled nodes after O&M record closure is identified, resulting in re-delivery callback values. This ensures that order re-delivery after O&M closure no longer depends solely on equipment status fields. Based on the re-delivery callback values, the original order process path, original equipment callback path, replacement resource path, and continuous control path are identified and constructed, resulting in a printing collaborative management solution. This solution enables the routing, callback, replacement, and control record generation of order nodes based on data paths when equipment O&M status changes.

[0069] This involves acquiring order node data, equipment operation and maintenance data, and resource usage data to obtain basic printing data, specifically including:

[0070] The system determines the scope of orders currently requiring collaborative management. This scope can be a single printing order, or multiple printing orders under the same production batch, shift, target equipment, or process route. Based on the order number, batch number, production plan number, or process route number, the system retrieves the corresponding order process record from the order management database and reads the order node data from the record. The order node data includes at least the order number, order batch, customer delivery date, product type, printing process type, node number, node name, node sequence, node status, preceding node identifier, subsequent node identifier, target equipment number, target workstation number, planned start time, planned end time, current progress time, node business field, and resource requirement field corresponding to that node. The system further reads the content of the fields in each order node that have formed a business status. The fields mentioned below refer to business fields, i.e., the locations of business data fields contained in the order node. The content of these fields may include equipment allocation fields, material requirement fields, ink or paper specification fields, plate information fields, process parameter fields, quality inspection requirement fields, personnel dispatch fields, production task issuance fields, equipment parameter loading fields, and node flow status fields. Based on the node status identifier, field write time, resource binding identifier, and process flow record, the system determines that the order node is currently in one or more combined states such as not started, pending, executing, completed, paused, locked and waiting, or abnormal and pending. For order nodes in the pending state, the system retains their node sequence, target equipment number, and the relationship between preceding and subsequent nodes; for nodes that have been completed or are being executed, the system retains their established resource occupancy relationships and node execution results; for subsequent nodes that have not yet been initiated, the system retains their pending resource requirements and subsequent business triggering conditions.

[0071] The system reads corresponding equipment operation and maintenance data from the equipment operation and maintenance management database, equipment status acquisition system, or equipment monitoring interface based on the target equipment number, target workstation number, or process route equipment requirement field in the order node data. This equipment operation and maintenance data may include equipment number, equipment name, production line to which the equipment belongs, current operating status, equipment availability status, equipment start / stop status, equipment alarm status, operation and maintenance record number, operation and maintenance type, operation and maintenance level, operation and maintenance trigger time, operation and maintenance start time, operation and maintenance processing status, operation and maintenance closure marker, operation and maintenance closure time, maintenance work order number, debugging record number, maintenance record number, fault alarm number, overprinting deviation record, color difference abnormality record, downtime record, and equipment recovery confirmation record. When reading equipment operation and maintenance data, the system uses the target equipment number as the primary index to match the equipment pointed to in the order node with the equipment operation and maintenance records, and prioritizes reading operation and maintenance records that have an overlap with the current time, the current production batch, or the planned execution time of the current order node. For situations where multiple maintenance records exist for the same equipment, the system can filter the maintenance records based on whether the record is closed, the record start time, the maintenance status level, and the affected process segment. Data that is not closed or still constrains the equipment's production operation will be designated as maintenance data to be associated. Since different equipment, monitoring systems, or maintenance modules may describe equipment status differently—for example, status fields such as "under maintenance," "awaiting repair," "under commissioning," "fault confirmed," "out of service," "unschedulable," and "awaiting verification" may originate from different data tables or interfaces—the system uniformly converts these status fields into maintenance status identifiers that can be used for order process judgment. These maintenance status identifiers include at least an unclosed maintenance identifier, a closed maintenance identifier, an equipment ready for operation identifier, an equipment unavailable identifier, and an equipment status pending confirmation identifier. For maintenance data lacking a closure time but with a recovery confirmation record, the system can associate the recovery confirmation record with the maintenance record number to form a pending verification status. For data with alarms but no generated maintenance work order, the system associates the alarm number with the equipment number and writes it as abnormal equipment status data into the equipment maintenance data set.

[0072] The system reads resource occupancy data based on the order number, node number, target equipment number, material requirements, personnel dispatch, and process parameter fields in the order node data. This resource occupancy data can originate from warehouse management systems, material management databases, personnel scheduling systems, equipment scheduling systems, process parameter management systems, and production task execution systems. Resource occupancy data may include resource number, resource type, resource name, resource specifications, resource location, current resource status, resource occupancy status, resource lock status, resource call status, resource release status, the order number to which the resource belongs, the node number to which the resource belongs, the planned resource occupancy time, the actual resource occupancy time, the estimated resource release time, and a resource replaceable identifier. Resource types may include printing equipment, auxiliary equipment, paper, ink, printing plates, die-cutting or laminating equipment, quality inspection equipment, operators, quality inspectors, maintenance personnel, process parameter templates, and production workstations, etc. The system uses a combined index of resource number, order number, and node number to determine which resources are currently occupied by the order node, which resources are only in a pending call state, which resources are occupied by other order nodes, and which resources are still available. For material, personnel, equipment, or parameter data that have been triggered by the preceding node and written into the resource occupancy table, the system marks them as occupied resource relationships. For resources that the current order node has not yet actually invoked but need to be prepared in advance according to the process route or subsequent nodes, the system marks them as pending resource relationships. For resources that have been locked or occupied by other order nodes, the system marks them as externally occupied resource relationships. For resources that are not occupied and meet the resource requirements of the order node, the system marks them as candidate available resource relationships. The system can also determine whether resource occupation will cause a time conflict for the current order node based on the overlap between the resource occupation time and the planned execution time of the order node; determine whether the resource is a receivable resource based on the matching relationship between the resource specifications and the process requirements of the order node; and determine whether the resource can participate in the construction of subsequent replacement resource paths or original equipment reconnection paths based on the correlation between the resource release status and the operation and maintenance closure status.

[0073] The system performs field standardization, time standardization, and index standardization on three types of data. Field standardization refers to converting fields with the same meaning in different business systems into unified field names. For example, it maps machine numbers in the production system, equipment codes in the maintenance system, and equipment resource numbers in the resource system to target equipment numbers. Time standardization refers to converting the planned time of order nodes, start time of maintenance records, maintenance closure time, resource occupation time, and resource release time into the same time format. Index standardization refers to establishing an association index between order nodes and equipment maintenance records and resource occupation relationships, using the order number, node number, target equipment number, and resource number as primary or composite keys. The system uses the order number and node number as the master data object for order node data and writes the equipment maintenance data and resource occupation data into the data fields corresponding to the order node. For each order node, the system writes the target equipment number, the current maintenance status of the equipment, the unclosed maintenance record corresponding to the target equipment, the closed maintenance record, the occupied resource relationship, the resource relationship to be called, the external occupied resource relationship, and the candidate available resource relationship into its node data field. If an order node corresponds to multiple target devices, the system establishes device association sub-data between the order node and each target device respectively; if a target device corresponds to multiple order nodes, the system establishes occupancy order data between the device and multiple order nodes based on the node's planned execution time and node priority; if a resource is associated with multiple order nodes simultaneously, the system establishes resource conflict data based on the resource's occupancy time and resource locking status.

[0074] The preset constraint value can be determined based on historical lock control samples or set as the quantile of the historical distribution of node constraint values. Different thresholds can be configured for different order types, equipment types, or process types. The preset reconnection value is determined based on the original equipment recovery success samples, resource integrity, and path continuity success rate. When the reconnection value reaches this threshold, the freeze can be lifted and the original equipment reconnection path can be written. The preset constraint value can be calculated by collecting order node samples from historical production batches where equipment maintenance interruptions occurred, calculating the node constraint value of each sample, and recording whether the node actually caused production interruption due to maintenance. With the goal of maximizing the F1-score, the optimal binary classification threshold is searched on the distribution of node constraint values ​​in historical samples, and this threshold is used as the preset constraint value. The preset reconnection value can be calculated by collecting lock control node samples that successfully resumed execution along the original process after historical maintenance closure, calculating the reconnection value of each sample, and determining the preset reconnection value as the 10th percentile of the reconnection values ​​of historical successful samples, with the criterion that at least 90% of the successful reconnection samples have reconnection values ​​not lower than this threshold.

[0075] In a preferred embodiment of the present invention, based on printing basic data, order nodes in the pending progress state, along with their predecessor and successor nodes, are extracted; propagated fields and fields to be propagated are identified and propagation boundaries are determined to obtain process propagation trajectory data, including:

[0076] Based on the order node data, extract the order nodes whose node status is pending, and extract the predecessor and successor nodes of each order node according to the order number to obtain the node adjacency data.

[0077] Based on the node adjacency data, extract the business fields that form resource occupancy relationships in each order node, and write them into the propagated fields according to their positions in the order nodes to obtain the propagated field data.

[0078] Based on the node adjacency data, extract the business fields that subsequent nodes need to call but for which order nodes have not yet formed a resource occupation relationship, and write them into the fields to be propagated according to their positions in the order nodes to obtain the data of the fields to be propagated.

[0079] Based on the data of the propagated fields and the data of the fields to be propagated, the handover position between the propagated fields and the fields to be propagated is determined according to the node order, the preceding node and the subsequent node, and the handover position is marked as the propagation boundary of the order node, thus obtaining the process propagation trajectory data.

[0080] In this embodiment of the invention, based on order node data, order nodes in the pending state are extracted, and the preceding and subsequent nodes of each order node are extracted according to the order number to obtain node adjacency data, providing a node-level infrastructure for generating the process propagation trajectory; based on the node adjacency data, business fields that form resource occupancy relationships in each order node are extracted, and written into the propagated fields according to the position of the business fields in the order node to obtain propagated field data, which can distinguish between data that has already had a business impact and data that is still in the pending trigger state; based on the node adjacency data, subsequent nodes that need to be called but for which order nodes have not yet formed resource occupancy relationships are extracted. The business fields are entered into the propagation field according to their position in the order node, thus obtaining the propagation field data. This allows for the identification of which resource calls have not yet actually occurred and which business fields can still be blocked, frozen, or reallocated when making operational record entry or node constraint judgments. Based on the propagated field data and the propagation field data, the handover position between the propagated field and the propagation field is determined according to the node order, preceding node, and subsequent node order. This handover position is marked as the propagation boundary of the order node, resulting in process propagation trajectory data. This provides data coordinates for the subsequent generation of operational entry domain data, node constraint values, and lock control path data.

[0081] Specifically, based on node adjacency data, business fields that form resource occupancy relationships are extracted from each order node, and these business fields are written into the propagated fields according to their positions within the order nodes, resulting in propagated field data, which includes:

[0082] The system reads the business fields of the current order node and its predecessor nodes from the node adjacency data and checks whether each business field has formed a resource occupancy relationship. These business fields may include equipment allocation fields, production task fields, material requirement fields, paper specification fields, ink formula fields, plate information fields, personnel dispatch fields, quality inspection requirement fields, process parameter fields, equipment parameter loading fields, warehouse material storage fields, process handover fields, and node execution result fields. The system can determine whether a business field has formed a resource occupancy relationship based on the order number, node number, resource number, resource type, resource occupancy status, resource lock status, and resource binding time in the resource occupancy data. If a business field has been bound to equipment, materials, personnel, process parameters, or other printing resources, or if the field has triggered business results such as material preparation, dispatching, parameter issuance, or task queueing, the system identifies the field as a business field that has been propagated. When a preceding node has completed its task and written its execution result to the current order node (e.g., paper specification confirmation, plate material confirmation, process parameter confirmation, or material pre-occupancy), the system identifies the field in the current node that received this preceding data as a propagated field. If the current node has not yet started actual production but has received and locked the equipment, materials, or personnel resources passed from the preceding node, this field is also written as a propagated field. For resources that have been occupied but not yet consumed, the system still treats them as propagated fields because these fields have already generated resource constraints in the business process. The system writes propagated fields into the propagated field data according to the position of the business field in the order node, the node to which the field belongs, the resource type to which the field belongs, and the order in which the field is written.

[0083] Specifically, based on node adjacency data, business fields that subsequent nodes need to call but for which order nodes have not yet formed resource occupancy relationships are extracted. These business fields are then written into the fields to be propagated according to their positions within the order nodes, resulting in the data for the fields to be propagated. This data includes:

[0084] The system reads the business requirement fields of the current order node to be advanced and its subsequent nodes, and identifies the business fields that subsequent nodes need to receive or call from the current node when continuing execution. These fields to be propagated may include unexecuted equipment call fields, unissued production task fields, unprocessed material outbound fields, unconfirmed personnel assignment fields, unloaded equipment process parameter fields, untriggered quality inspection task fields, and process handover fields that have not yet been passed to the next process. The system compares resource usage data to determine whether these business fields have not yet formed actual resource usage relationships. If a field is referenced by subsequent nodes in the process route, but there is no corresponding resource binding record, usage record, locking record, or call execution record in the resource usage data, the system identifies this field as a field to be propagated. The system matches the resource requirements of subsequent nodes with the business output of the current node. For example, if a subsequent node needs to call the target equipment number, process parameter template, printed material list, or quality inspection standard determined by the current node, but the current node has not yet written an actual usage relationship to the resource management system, the system writes these fields that have not yet been triggered into the fields to be propagated. If subsequent nodes need to automatically trigger material preparation, equipment task queuing, or personnel dispatch after the current node's progress, but this triggering action has not yet occurred, the corresponding field is also identified as a field to be propagated. For situations where multiple subsequent nodes depend on the same field, the system can record the set of subsequent nodes corresponding to that field in the field to be propagated data. For situations where different subsequent nodes call different resource types, the system can record the fields to be propagated separately according to resource type and node order. The system writes the business field into the field to be propagated data according to the business field's position in the order node, the direction of propagation, the corresponding subsequent node, the type of resource to be called, and the triggering condition. Within a single order node, after arranging the business fields according to their execution order, a boundary naturally forms between propagated fields and fields to be propagated. The former is the field segment occupied by triggered resources, and the latter is the field segment that has not yet been triggered. The two are adjacent in the node order direction, and their boundary is the propagation boundary.

[0085] Specifically, based on the propagated field data and the field data to be propagated, the handover position between the propagated field and the field to be propagated is determined according to the node order, preceding node, and subsequent node order. This handover position is then marked as the propagation boundary of the order node, resulting in process propagation trajectory data, which specifically includes:

[0086] The system first reads the propagated and unpropagated field data corresponding to the current order node, and sorts them according to the field's position in the order node, business execution order, process route order, and node sequence. The system designates the data area containing the propagated fields as the propagated side and the data area containing the unpropagated fields as the unpropagated side, then searches for the intersection between them. This intersection can be between two adjacent business fields within the order node, the process connection between the current node and subsequent nodes, or the state position after the preceding node has transmitted data but before the current node triggers a resource call to subsequent nodes. If a preceding field in an order node has already established a resource occupancy relationship, but the subsequent field has not yet established a resource call relationship, the system marks the position between the occupied field and the unclaimed field as the propagation boundary of that node. If the current node has received business data transmitted by the preceding node but has not yet triggered task issuance, material release, or personnel dispatch to subsequent nodes, the system marks the business handover position between the current node and subsequent nodes as the propagation boundary. If there are multiple propagated fields and multiple fields to be propagated, the system can determine the propagated field closest to the subsequent node according to the node order and business execution order, and use the position between this propagated field and the field to be propagated that needs to be called by the subsequent node first as the propagation boundary. The system combines node adjacency data, propagated field data, field to be propagated data, and propagation boundary data. The process propagation trajectory data includes at least the order number, current order node, predecessor node, successor node, node order, set of propagated fields, set of field to be propagated, propagation boundary position, propagation direction, established resource occupancy relationship, and established resource call relationship. For orders with multiple nodes to be promoted, the system generates process propagation trajectory data for each node to be promoted, and forms a process propagation trajectory set according to the order number and node order.

[0087] In a preferred embodiment of the present invention, based on the target device number of each order node in the process propagation trajectory data, maintenance records are extracted and embedded into the propagation boundary to determine the entry range of the maintenance record in the order node, thereby obtaining maintenance entry domain data, including:

[0088] Based on the process propagation trajectory data, the target device number and propagation boundary of each order node are extracted, and the target device number is associated with the propagation boundary to obtain the device boundary data;

[0089] Based on the equipment boundary data and equipment operation and maintenance data, extract the operation and maintenance records that correspond to the target equipment number and do not have a closure mark, and write the operation and maintenance records into the order node to obtain the operation and maintenance data to be embedded;

[0090] Based on the operation and maintenance data to be embedded, identify the starting position of the operation and maintenance record in the business field of the order node, and embed the starting position of the record into the node position of the propagation boundary to obtain the operation and maintenance boundary embedding data.

[0091] Based on the embedded data of the operation and maintenance boundary, the business fields covered from the record start position to the unclosed state are extracted along the node sequence of the order node, and the business fields are marked as the entry range of the operation and maintenance record in the order node to obtain the operation and maintenance entry domain data.

[0092] In this embodiment of the invention, based on the process propagation trajectory data, the target device number and propagation boundary of each order node are extracted, and the target device number is associated with the propagation boundary to obtain device boundary data. This clearly identifies which order node, which propagation boundary, and which business field position a particular device corresponds to. Based on the device boundary data and device operation and maintenance data, operation and maintenance records corresponding to the target device number and without closure markers are extracted, and these records are written into the order node to obtain the operation and maintenance data to be embedded. This allows for direct reading of the corresponding operation and maintenance records based on the order node without the need for cross-system searches during the lock control judgment stage. Based on the operation and maintenance data to be embedded, the starting position of the operation and maintenance record in the order node is identified. The system extracts business fields and embeds the record's starting position into the node position of the propagation boundary to obtain operation and maintenance boundary embedding data. This data can distinguish whether the operation and maintenance record occurred after the order process has already formed resource occupancy, before subsequent resource calls, or at the junction of the two. Based on the operation and maintenance boundary embedding data, the system extracts the business fields covered from the record's starting position to the unclosed state along the node sequence of the order node, and marks these business fields as the entry range of the operation and maintenance record in the order node to obtain operation and maintenance entry domain data. This data clarifies that the operation and maintenance record does not affect the entire order in a general way, nor does it only affect a certain device number, but rather affects the specific set of business fields covered from the record's starting position to the unclosed state in the order node.

[0093] Specifically, based on equipment boundary data and equipment operation and maintenance data, operation and maintenance records corresponding to the target equipment number and lacking closure markers are extracted, and these records are written into the order node to obtain the operation and maintenance data to be embedded, which specifically includes:

[0094] The system uses the target device number in the device boundary data as the search key to access the device operation and maintenance data set and search for operation and maintenance records that match the target device number. When extracting operation and maintenance records, the system prioritizes filtering records without a closure marker, or records with an empty closure marker, an empty closure time, or whose operation and maintenance status is still pending, under maintenance, under debugging, under fault confirmation, suspended, or unschedulable. If multiple unclosed operation and maintenance records exist for the same target device, the system can write each record to a corresponding order node based on its start time, operation and maintenance status level, affected process segment, overlap with the planned execution time of the order node, and device boundary location. Alternatively, it can select the operation and maintenance record with the highest correlation to the current order node as the record to be embedded. The system does not change the original process state of the order node; instead, it adds an operation and maintenance record reference field or an operation and maintenance record sub-data field to the order node data field. This sub-data field can record the target device number, maintenance record number, maintenance type, maintenance status, maintenance start time, maintenance start location, unclosed flag, maintenance impact range description, associated propagation boundary number, and corresponding order node number. For cases where an order node corresponds to multiple target devices and multiple devices have unclosed maintenance records, the system can create multiple sub-records to be embedded under the order node, maintaining the mapping relationship between each sub-record and the corresponding device boundary association record. For cases where the maintenance record corresponding to the target device number is already closed, the system will not write this record as maintenance data to be embedded into the order node, or will only retain it as historical maintenance data, not participating in subsequent scope identification. The maintenance data to be embedded includes the correspondence between the order node, target device number, propagation boundary, and unclosed maintenance records.

[0095] Specifically, based on the operation and maintenance data to be embedded, the starting position of the operation and maintenance record is identified in the business field of the order node, and the starting position of the record is embedded into the node position of the propagation boundary to obtain the operation and maintenance boundary embedding data, which includes:

[0096] The system reads the start time, start position, maintenance type, affected process segment, fault alarm source, debugging object, target equipment number, and associated propagation boundary number of the maintenance record to be embedded in the maintenance data, and matches these fields with the business fields in the order node. If the maintenance record originates from an equipment fault alarm, the system can determine the corresponding business field in the order node based on the equipment operation stage, production task number, or node execution time corresponding to the fault alarm. If the maintenance record originates from equipment debugging or overprint deviation correction, the system can determine the record start position based on the equipment parameter loading field, process parameter field, or quality verification field corresponding to the debugging record. If the maintenance record originates from equipment repair or maintenance, the system can determine the record start position based on the equipment occupancy field, equipment task field, or production execution field corresponding to the repair work order. The system then positions the start status of the maintenance record to the specific business field in the order node. When embedding the record start position into the node position of the propagation boundary, the system needs to determine the relative relationship between the maintenance record start position and the propagation boundary. If the record's starting position is on one side of an already propagated field, it indicates that when the maintenance record occurred, some resource occupancy relationships or device task relationships had already been formed in the order node. If the record's starting position is on one side of a field to be propagated, it indicates that the maintenance record occurred before subsequent resource calls were triggered. If the record's starting position coincides with or is adjacent to the propagation boundary, it indicates that the maintenance record precisely enters the node position where the order process transitions from propagated data to data to be propagated. The system writes the above relative relationships into the maintenance boundary embedded data and records the field number, field name, field order, boundary front and back attributes, target device number, and associated order node corresponding to the maintenance record's starting position. For maintenance records that cannot be directly located based on a single field, the system can combine the time relationship between the record's start time and the order node's planned time, device task issuance time, and resource occupancy time to locate the maintenance record to the nearest business field or propagation boundary position. The system further transforms the association relationship between the maintenance record to be embedded and the propagation boundary into an embedding relationship. This embedding relationship not only indicates that a certain unclosed maintenance record corresponds to a certain target device and order node, but also indicates from which business field of the order node the maintenance record begins to affect the process propagation. The maintenance boundary embedding data includes the order number, order node number, node sequence, target device number, maintenance record number, record starting position, starting business field, propagation boundary position, direction of the starting position relative to the propagation boundary, affected fields on the already propagated side, affected fields on the side to be propagated, and the current unclosed state of the maintenance record.

[0097] Specifically, based on the embedded data of the operation and maintenance boundary, the business fields covered from the record's starting position to the unclosed state are extracted along the node sequence of the order node, and these business fields are marked as the entry range of the operation and maintenance record in the order node, thus obtaining the operation and maintenance entry domain data, which specifically includes:

[0098] The system reads the starting position and current state of the record in the embedded data of the operation and maintenance boundary, and determines whether the operation and maintenance record is still in an open state. When the operation and maintenance record is still open, the system starts from the business field corresponding to the starting position of the record and extracts the business fields affected by the operation and maintenance record along the order of business fields within the order node and the node sequence between order nodes. The extracted business fields may include equipment task fields, equipment occupancy fields, equipment parameter loading fields, material call fields, personnel dispatch fields, quality inspection fields, process handover fields, and resource fields to be called by subsequent nodes. If the starting position of the operation and maintenance record is located within the current order node, the system first extracts the business fields from the starting field to the end of the node or behind the propagation boundary in the current node; if the operation and maintenance record continues to affect subsequent nodes along the node sequence, the system continues to extract the business fields related to the same target equipment or the same resource call link in subsequent nodes; if the starting position of the operation and maintenance record is located before the propagation boundary, the system can simultaneously mark the affected fields that have formed resource occupancy relationships on the propagated side and the affected fields that have not yet triggered resource calls on the side to be propagated. Since an unclosed state indicates that the equipment maintenance record has not yet been closed and confirmed, the system will use the range of fields within the current order node that have not yet been unconstrained, starting from the record's starting position, as the coverage area of ​​that maintenance record. If the unclosed maintenance record persists into subsequent order nodes, the system can continue to extract business fields with the same target equipment number, connected resource call relationships, or inherited process routes along the subsequent node sequence. If a subsequent node has switched to other equipment or no longer depends on the target equipment, the system can limit the scope to the nodes or fields before the equipment switch. For the case of multiple unclosed maintenance records in the same order node, the system can generate the scope corresponding to each maintenance record separately and mark different maintenance record numbers on the business fields; for the case of multiple maintenance records covering the same business field, the system can mark the field as a multiple maintenance entry field and record the corresponding set of maintenance records. The system will uniformly mark the business fields covered by the maintenance record as the scope of that maintenance record in the order node. The operation and maintenance entry domain data includes order number, order node number, node sequence, target device number, operation and maintenance record number, record start position, propagation boundary position, entry start field, entry end field, entry field set, propagated side entry field, unpropagated side entry field, associated subsequent nodes, unclosed state identifier, and the relationship between entry scope and resource usage.

[0099] In a preferred embodiment of the present invention, based on the operation and maintenance entry domain data, the degree of control over whether an order node can continue to flow when the operation and maintenance record enters the order process is identified, and a node constraint value is obtained, including:

[0100] Based on the operation and maintenance entry domain data, calculate the proportion of the number of business fields covered by the entry range relative to the total number of business fields in the order node, identify the coverage degree formed by the operation and maintenance records within the current order node, and obtain the entry coverage item; calculate the interaction clamping degree between the business fields on the propagated side and the business fields on the side to be propagated within the same entry range, and obtain the boundary clamping item.

[0101] Based on the operation and maintenance entry domain data, calculate the correlation ratio of the operation and maintenance record to adjacent order nodes, identify the degree of connection between the operation and maintenance record and the preceding and following process nodes other than the current order node, and obtain the node connection items.

[0102] By integrating the entry coverage item, boundary clamping item, and node connection item, the degree of locking formed by the continued flow of order nodes when the operation and maintenance record enters the order process is identified, and the node restraint value is obtained.

[0103] In this embodiment of the invention, based on the operation and maintenance entry domain data, the proportion of the number of business fields covered by the entry range relative to the total number of business fields in the order node is calculated. The coverage degree of the operation and maintenance record within the current order node is identified, resulting in an entry coverage item. This clarifies how many business fields the operation and maintenance record covers within an order node, which business fields are covered, and whether the covered fields are directly related to the continued flow of the order node. The interaction clamping degree between the already propagated business fields and the business fields to be propagated within the same entry range is calculated, resulting in a boundary clamping item. This determines whether the operation and maintenance record only affects resource occupancy relationships that have already occurred, only affects resource call relationships that have not yet been triggered, or whether... Simultaneously, it clamps both propagated data and data to be propagated; based on the operation and maintenance entry domain data, it calculates the correlation ratio of the operation and maintenance record to adjacent order nodes, identifies the degree of involvement of the operation and maintenance record to the preceding and following process nodes outside the current order node, and obtains node involvement items. It can identify whether the operation and maintenance record is limited to the current order node or has already affected the preceding or subsequent nodes along the order process sequence; by integrating the entry coverage item, boundary clamping item and node involvement item, it identifies the degree of locking formed by the operation and maintenance record when entering the order process and continuing to flow through the order node, and obtains the node restraint value, which provides a direct basis for subsequently retaining the occupied relationship of propagated resources, freezing the called relationship of resources to be propagated, and generating locking path data.

[0104] The formula for calculating the node restraint value is as follows: ,

[0105] in, For the first The node constraint value of each order node. This refers to the number of business fields covered by the scope of operations and maintenance records. For the first Total number of business fields in each order node. This is the propagation boundary hit value. It is set to 1 when the propagation boundary is within the scope of the operation and maintenance record, and to 0 when the propagation boundary is not within the scope of the operation and maintenance record. This refers to the number of business fields located on the propagated side of the propagation boundary within the scope of the operation and maintenance records. This refers to the number of business fields located on the propagation boundary side within the scope of the operation and maintenance records. This refers to the number of preceding and subsequent nodes associated with the same scope of operations and maintenance records. For the first The total number of preceding and subsequent nodes corresponding to each order node.

[0106] Specifically, based on the operation and maintenance entry domain data, the degree of control over whether an order node can continue to flow when the operation and maintenance record enters the order process is identified, and the node constraint value is obtained, which specifically includes:

[0107] The system determines the first domain based on the operation and maintenance entry data. The set of business fields covered by operation and maintenance records in each order node, and the number of business fields in this set is counted. At the same time, the system reads the quantity of all business fields in this order node to obtain... The system will and Substitution The basic coverage portion for generating node constraint values. This portion represents the data range occupied by the operation and maintenance record's scope within the current order node. The formula uses... and Incrementing by 1 ensures a stable calculation structure even when the number of business fields is zero or the data boundary is small, preventing the denominator from being zero and creating continuous data differences between uncovered, partially covered, and widely covered areas. The system determines whether the propagation boundary of the current order node falls within the entry range of the maintenance record. If the propagation boundary is within the entry range, it means that the maintenance record not only covers some business fields in the order node, but also involves the intersection area between already propagated fields and fields to be propagated. In this case, [the system will...]. The value is 1; when the propagation boundary is not within the cut-in range, it indicates that the operation and maintenance record did not hit the junction between the propagated side and the side to be propagated. In this case, The value is 0. When the value is 1, the system further counts the number of business fields located on the propagation boundary within the scope of the operation and maintenance records. And the number of business columns located on the side of the propagation boundary awaiting propagation. Then according to Calculate the clamping relationship between the propagated side column and the side column to be propagated within the same cut-in range. In this part of the structure, This indicates the combination relationship formed when the cut-in range simultaneously covers the columns on both sides of the propagation boundary. This is used to normalize the data by using the total coverage of the cut-in range as a benchmark, thus limiting the combined influence of the columns on both sides of the boundary to the data range corresponding to the current cut-in range. The system then links this clamping relationship to the boundary hit value. Multiply and write the whole thing into the database. Therefore, when the propagation boundary is not hit, This part degenerates to 1, without generating additional amplification to the basic coverage area; when the propagation boundary is hit, the formula generates the boundary clamping increment based on the number of propagated side columns and the number of side columns to be propagated. The system identifies whether the operation and maintenance record is associated with the predecessor and successor nodes of the current order node based on the operation and maintenance entry domain data. The system counts the number of predecessor and successor nodes associated with the same operation and maintenance record entry range. And statistics of the first The total number of preceding and subsequent nodes corresponding to each order node is obtained. The system will and Substitution This part represents the scope of association between the same maintenance record and adjacent process nodes outside the current order node. The formula uses... Adding 1 is used to avoid the denominator being zero when the current node has no predecessor or successor nodes, and also to ensure that the connection between adjacent nodes can participate in the overall calculation of the node constraint value in a proportional manner. The system multiplies and fuses the basic coverage part, the propagation boundary clamping part, and the node connection part to obtain the first... Node constraint value of each order node .in, As a basic item, it indicates the extent to which maintenance records are covered within the current order node; As a boundary clamping item, it indicates whether the operation and maintenance record cuts into the propagation boundary between the propagated field and the field to be propagated, and the distribution of the cut-in range on both sides of the boundary. As a node connection item, it indicates the degree of association between the operation and maintenance record and the preceding and subsequent nodes.

[0108] In a preferred embodiment of the present invention, locking nodes and advancing nodes are identified based on node constraint values ​​and preset constraint values, and the resource occupancy relationships in the propagated fields are retained, while the resource call relationships in the fields to be propagated are frozen, to obtain locking path data, including:

[0109] By marking order nodes whose node restraint values ​​reach the preset restraint value as lock control nodes and order nodes whose node restraint values ​​do not reach the preset restraint value as advance nodes, node splitting data is obtained;

[0110] Based on the node distribution data, extract the propagated fields of the lock control node and the resource occupancy relationship that has been formed, bind the resource occupancy relationship with the lock control node, and obtain the occupancy retention data;

[0111] Based on the node distribution data, extract the fields to be propagated of the lock control node and the resource call relationships that have not yet been executed, and mark the resource call relationships with the lock control node to obtain the call freeze data;

[0112] Based on the reserved data and the frozen data, the advancing nodes, locking nodes, resource occupancy relationships, and resource call relationships are written into the locking path according to the node order of the order nodes. The path status of the advancing nodes is marked as continue advancing, and the path status of the locking nodes is marked as locking waiting, thus obtaining the locking path data.

[0113] In this embodiment of the invention, order nodes whose node constraint values ​​reach a preset constraint value are marked as lock control nodes, and order nodes whose node constraint values ​​do not reach the preset constraint value are marked as advance nodes, thus obtaining node partitioning data. This enables subsequent resource retention, resource freezing, and path status writing to be performed separately for different node states. Based on the node partitioning data, the propagated fields of the lock control nodes and their established resource occupancy relationships are extracted, and the resource occupancy relationships are bound to the lock control nodes to obtain occupancy retention data. This provides a data foundation for subsequent original equipment reconnection, original resource takeover, or process re-deployment after the maintenance record closure. Based on the node partitioning data, lock control data is extracted. The nodes' pending propagation fields and their unexecuted resource call relationships are frozen with the lock control nodes to obtain call freeze data. This provides a data basis for subsequent judgments on whether to unfreeze, switch to a replacement resource path, or continue locking. Based on the occupancy retention data and call freeze data, the advancing nodes, lock control nodes, resource occupancy relationships, and resource call relationships are written into the lock control path according to the node order of the order nodes. The path status of the advancing nodes is marked as "continue advancing," and the path status of the lock control nodes is marked as "lock control waiting," to obtain lock control path data. This provides a data foundation for subsequent identification of the re-deployment and reconnection degree after the operation and maintenance record closure.

[0114] Specifically, based on the node distribution data, the propagated fields of the lock control node and their established resource occupancy relationships are extracted. These resource occupancy relationships are then bound to the lock control node to obtain occupancy retention data, which includes:

[0115] The system filters out order nodes marked as lock control nodes from the node distribution data. Based on the order number and node number of the lock control node, it reads the set of propagated fields corresponding to that node from the process propagation trajectory data. The system further reads the resource occupancy relationships already formed in the propagated fields based on resource occupancy data. The system matches the order number, node number, field number, resource number, and resource occupancy status. If a propagated field has established an occupancy or task queuing relationship with a target device, the system writes the device occupancy relationship into the occupancy retention data. If a propagated field has triggered material reservation, paper locking, ink batch locking, or plate preparation, the system writes the material occupancy relationship into the occupancy retention data. If a propagated field has generated a personnel dispatch record, the system writes the personnel occupancy relationship into the occupancy retention data. If a propagated field has completed process parameter template binding or equipment parameter preloading, the system writes the parameter occupancy relationship into the occupancy retention data. For cases where there are multiple resource occupancy relationships in the propagated fields, the system generates corresponding occupancy retention sub-records and maintains the mapping relationship between them and the lock control node, business field, and resource type. The system writes a lock node identifier, an occupation reservation identifier, and a reservation source identifier to the resource occupation relationship. The lock node identifier indicates that the resource occupation relationship currently belongs to the locked order node; the occupation reservation identifier indicates that the resource occupation relationship will not be automatically released during the lock period; the reservation source identifier indicates that the resource occupation relationship originates from the propagated field, and the occupation reservation data includes the binding relationship between the lock node and the propagated resource occupation relationship.

[0116] Specifically, based on the node distribution data, the fields to be propagated for the lock control node and its unexecuted resource call relationships are extracted. The resource call relationships are then frozen with the lock control node to obtain call freeze data, which includes:

[0117] The system reads the lock control node from the node distribution data and extracts the set of fields to be propagated for that lock control node based on the process propagation trajectory data. Based on resource occupancy data and resource call records, it determines whether these fields have not yet generated actual resource occupancy or completed execution, and identifies eligible resource call relationships as objects to be frozen. The system processes resources according to their type: for production tasks not yet assigned to equipment, it marks the corresponding equipment call relationship as frozen, preventing the task from entering the target equipment's task queue; for materials not yet shipped or delivered to workstations, it marks the corresponding material call relationship as frozen, preventing the generation of shipping execution records; for personnel assignments not yet confirmed for execution, it marks the corresponding personnel call relationship as frozen, preventing the personnel scheduling system from generating execution assignments; and for process parameters not yet loaded into equipment, it marks the parameter call relationship as frozen, preventing the parameters from being sent to the target equipment. The system can write a freeze flag, freeze node number, freeze reason identifier, associated maintenance record number, freeze time, pre-freeze status, and post-freeze status into each resource call relationship. The system records the subsequent node number, the field number to be propagated, the resource requirement conditions, and the unfreezing conditions corresponding to the resource call relationship. The unfreezing conditions can be related to data states such as the closure of subsequent maintenance records, the re-connection value reaching the preset connection value, the formation of a replacement resource path, or the release of a persistent lock control path. In the case where a field to be propagated is jointly called by multiple subsequent nodes, the system writes each subsequent call relationship corresponding to that field into the call freeze data. In the case where a subsequent node needs to call multiple resources, the system can freeze each resource call relationship separately and retain their correspondence with the same lock control node. The call freeze data includes the frozen mapping between the lock control node, the field to be propagated, and the unexecuted resource call relationships.

[0118] Specifically, based on the reserved data and the frozen data, the advancing nodes, locking nodes, resource occupancy relationships, and resource call relationships are written into the locking path according to the node order of the order nodes. The path status of the advancing nodes is marked as "continue advancing," and the path status of the locking nodes is marked as "lock waiting," thus obtaining the locking path data, which specifically includes:

[0119] The system reads the advance nodes and lock control nodes from the node distribution data, and also reads the occupancy reservation data and call freeze data. The system uses order number as the aggregation unit and node sequence as the sorting basis, arranging the order nodes under the same order according to the process order. For order nodes marked as advance nodes, the system writes their node number, node sequence, target device number, associated resource relationship, and path status into the lock control path, and marks the path status of the node as "continue advance". For order nodes marked as lock control nodes, the system writes their node number, node sequence, target device number, associated maintenance record, occupancy reservation data, and call freeze data into the lock control path, and marks the path status of the node as "lock control waiting". The system generates a lock control path master record for each order, and creates multiple node path sub-records under this master record. Each node path sub-record can include order number, node number, node sequence, node type, path status, target device number, node restraint value, preset restraint value, associated maintenance record number, set of propagated fields, set of fields to be propagated, set of occupancy reservation relationships, and set of call freeze relationships. For advancing nodes, the system retains their continuing state and records their normal flow relationships with preceding and subsequent nodes. For locked nodes, the system records their waiting state and binds this waiting state to the reserved resource occupancy relationship and the frozen resource call relationship. If both advancing and locked nodes exist in the same order, the system maintains their node order relationship in the locked path data, decomposing the order process into a continuing advancing segment and a locked waiting segment at the data level. Based on the preceding and following connections between order nodes, the system connects advancing nodes, locked nodes, resource occupancy relationships, and resource call relationships into a path structure. This path structure can be represented as a node order chain under the order number or as a path graph containing nodes, fields, and resource relationships. The continuing advancing nodes correspond to node segments that can still be executed along the original order process; the locked waiting nodes correspond to node segments affected by maintenance records and requiring a pause for propagation; the reserved occupancy relationship is attached to the propagated side of the locked node; and the frozen call relationship is attached to the unpropagated side of the locked node. The system stores this path structure as locked path data.

[0120] In a preferred embodiment of the present invention, based on the lock control path data, the degree of process reconnection of the lock control node after the maintenance record is closed is identified, and the reconnection value is obtained, including:

[0121] Based on the closure marker of the operation and maintenance record in the equipment operation and maintenance data, identify the gating degree of the closure status of the operation and maintenance record on the locking node entering the reconnection process, and obtain the closure gating item; identify the degree of restoration between the existing resource occupation relationship and the frozen resource call relationship of the locking node after the operation and maintenance record is closed, and obtain the acceptance matching item.

[0122] Based on the occupancy retention data and the call freeze data, calculate the number of relationships between the original resource number and the original business field after the operation and maintenance record is closed, identify the degree to which the original materials and personnel of the lock control node are still in a reconnectable state when the lock control node is re-entered, and obtain the state retention item; based on the lock control path data, identify whether the lock control node can maintain the degree of process connection with the subsequent order node after the lock control node is reconnected, and obtain the path continuity item;

[0123] By integrating the closing gating item, the acceptance matching item, the state maintenance item, and the path continuity item, the degree of process reconnection is identified, and the lock control node continues to execute the original process after the operation and maintenance record is closed, thus obtaining the reconnection value.

[0124] In this embodiment of the invention, based on the maintenance record closure marker in the equipment maintenance data, the gating degree of the maintenance record closure status on the locking node's entry into the callback process is identified, resulting in a closure gating item. This distinguishes between states such as maintenance record not closed, closure pending confirmation, and closed and verifiable, preventing the locking node from directly participating in the original process recovery when the equipment maintenance status is not yet closed. Furthermore, the degree of restoration of the original process is identified between the retained resource occupancy relationship and the frozen resource call relationship after the maintenance record closure, resulting in a connection matching item. This allows the locking node to determine whether it can continue to use the previously retained resource occupancy relationship after the maintenance record closure and restore the frozen resource call relationship to the subsequent execution relationship of the original process. Based on the occupancy retention data and call freeze data, the relationship number of the original resource number and original business field is calculated after the maintenance record closure. The quantity identifies the extent to which the original materials and personnel remain accessible during re-entry at the lock control node, resulting in a status retention item. This item identifies whether the original materials, personnel, equipment, or parameter relationships remain under the original order node and business field. Based on the lock control path data, the item identifies the degree to which the lock control node can maintain process continuity with subsequent order nodes after re-entry, resulting in a path continuity item. This item identifies whether the lock control node can still access the original subsequent process even if it meets the equipment closure and resource retention conditions. By integrating the closure gate control item, acceptance matching item, status retention item, and path continuity item, the item identifies the degree to which the lock control node continues to execute the original process after the maintenance record is closed, resulting in a re-entry re-entry value. This value represents the degree to which the lock control node continues to execute the original process after the maintenance record is closed, serving as a data bridge connecting the lock control path data and the subsequent printing collaborative management solution.

[0125] The formula for calculating the reconnection value is as follows: ,

[0126] in, For the first The reconnection value of each locking node. This is the closure flag value for the operations and maintenance record. It is set to 1 when the operations and maintenance record has a closure flag, and to 0 when the operations and maintenance record does not have a closure flag. To reserve data for use in the first The number of resource occupancy relationships bound to each lock node. To call the frozen data and the first The number of resource call relationships bound to each lock node. To determine the number of inheritance relationships corresponding to resource type, business field, and node order in both reserved data and frozen data, This refers to the number of resource occupancy relationships that retain the original resource number and the original occupying entity in the reserved data after the operation and maintenance record is closed. This refers to the number of resource call relationships in the frozen data that retain the original call target and original business field after the operation and maintenance record is closed. For the lock control path data from the first Starting from the first locking node, the number of consecutive nodes that maintain a locking wait state in sequence along the subsequent nodes. For the lock control path data from the first Starting from the first locking node, the number of nodes that have been marked as continuing the progress state in the subsequent node sequence.

[0127] Specifically, based on the lock control path data, the degree of process reconnection of the lock control node after the operation and maintenance record is closed is identified, and the reconnection value is obtained, which includes:

[0128] The system reads the first The operation and maintenance record of each lock control node is closed, and the closed gating factor is determined based on the closed status. When the maintenance record associated with the lock control node does not yet have a closing marker, The value is set to 0. At this point, regardless of subsequent changes in retained data, frozen data, or continuous path data, the entire re-deployment return value remains unchanged. If all values ​​are gated to 0, it indicates that the locking node has not yet entered the reconnection calculation results; when the maintenance record already has a closure marker, ... A value of 1 ensures that subsequent matching relationships, state maintenance relationships, and path continuity relationships will be included in the calculation of the re-deployment return value. The system reads the occupied and reserved data related to the first... The number of resource occupancy relationships bound to each lock node is obtained. And read the frozen data related to the first The number of resource call relationships bound to each lock node is obtained. The system matches the occupied and reserved data with the accessed frozen data, identifying the number of corresponding relationships where resource type, business field, and node order all correspond. For example, if a material occupancy relationship exists in the occupancy and retention data, and a corresponding pending recovery call relationship exists in the frozen call data, then this relationship can be included. If the relationships between the equipment, personnel, or process parameters in the retained data can correspond to the frozen subsequent call relationships in terms of resource type, business field, and node priority, they can also be included. The system will , and Substitution This section indicates the degree of compatibility between the reserved data and the frozen data. This indicates the number of corresponding succession relationships that can be formed between the retained data and the frozen data, and the square structure reflects the characteristic that the succession relationship is simultaneously corresponding to both the retained side and the frozen side. Indicates the first The overall relationship scale formed by the number of resource occupancy relationships and resource access relationships in each locking node. The formula... , and Incrementing by 1 is used to maintain the continuity of the calculation structure when the number of relations is small or a certain type of relation is empty, and to avoid calculation interruption due to empty data.

[0129] The number of resources whose resource occupancy relationships remain unchanged after the system reads and closes the maintenance record, while still retaining the original resource number and the original occupant, is obtained. And obtain the number of resource call relationships that still maintain the original call target and original business field after the operation and maintenance record is closed. .in, This reflects whether the original resource occupancy relationship is still maintained on the side of the data retention after the operation and maintenance is closed. For example, whether the original equipment number, original material number, original personnel number or original parameter number is still bound to the original occupant. This reflects whether the original calling targets and business fields are still maintained after the operation and maintenance is closed on the side that calls frozen data. For example, whether the original equipment to be called, the original material calling targets, the original personnel dispatch targets, or the original parameter loading fields have been rewritten. The system will and Substitution This section indicates the degree to which the state of the reservation side and the call freeze side remains balanced after the operation and maintenance is closed. This represents the overall baseline indicating that the relationship between the two sides remains unchanged. This indicates the difference in the amount of state maintained between the holding side and the calling frozen side. When and The closer they get, The smaller the value, the closer the term is to 1, indicating that the original resource occupancy relationship and the original resource allocation relationship are relatively balanced on both sides; when and When the difference is large, this item decreases accordingly, indicating that although one side may maintain more original state relationships, the other side cannot form a corresponding maintenance, thereby reducing the state consistency of the original process re-entry and reconnection.

[0130] The system continues to read from the lock path data from the first... Starting from the first locking node, the number of consecutive nodes that maintain a locking waiting state in sequence along the subsequent nodes is obtained. And read the number of nodes that have been marked as continuing the process along the subsequent node sequence to obtain the result. .in, This indicates the number of consecutive nodes still in the locking waiting chain when looking backward from the current locking node; This indicates the number of nodes within the same subsequent observation range that have broken free from lock-control waiting and been marked as continuing. If subsequent nodes maintain the same lock-control waiting state as the current lock-control node, it means that the current lock-control node may still serve as the reconnection point for subsequent lock-control segments after the maintenance record is closed; if many subsequent nodes have been marked as continuing, it means that the original lock-control path has been partially diverted, and the original path waiting relationship between the current lock-control node and subsequent nodes has been reduced accordingly. The system will... and Substitution This section is used to represent the locking path from the first... The degree of continuity of subsequent locking waits starting from each locking node. This represents the current locking node and the basis of all subsequent nodes that remain in a locking waiting state. This represents the path observation range formed by the current locking node, subsequent locking waiting nodes, and continuing advancement nodes. The system can convert the path state relationship between the current locking node and subsequent nodes into path continuum items. Compared to When the value is large, this value is higher, indicating that subsequent nodes remain more likely to remain in the locking wait chain related to the current locking node; when When the value is large, the value of this item decreases, indicating that many subsequent nodes have been marked as continuing to advance, and the continuity of the current locking node reconnecting along the original locking path is reduced.

[0131] The system multiplies and fuses the closing gating term, the connecting matching term, the state-preserving term, and the path continuity term to obtain the first term. The reconnection value of each locking node .in, This is used to prevent the re-connection value from being generated when the operation and maintenance record is not closed; Used to indicate the degree of matching between the original process of occupying and retaining data and calling frozen data; This is used to indicate the degree to which the original resource occupancy relationship and the original resource call relationship remain balanced after the operation and maintenance is closed; Used to indicate the degree of continuity of locking wait between the current locking node and subsequent nodes in the locking path.

[0132] In a preferred embodiment of the present invention, based on the resubmission return value, the original order process path, the original equipment return path, the replacement resource path, and the continuous lock control path are identified and constructed to obtain a printing collaborative management scheme, including:

[0133] Based on the lock control path data, the advancement nodes with the path status of "continue advancing" and the lock control nodes with the path status of "lock control waiting" are extracted. The order nodes are then divided into process advancement nodes, equipment return nodes, resource replacement nodes, and continuous lock control nodes according to the node status and re-deployment return value, thus obtaining the path node allocation data.

[0134] Based on the path node allocation data, extract the order number, node order and resource usage relationship of the process advancement node, and write the process advancement node into the original order process path according to the node order.

[0135] Based on the path node allocation data, extract the device reconnection nodes whose reconnection value reaches the preset reconnection value, and write the target device number, reserved resource occupancy relationship and frozen resource call relationship of the device reconnection node into the original device reconnection path;

[0136] Based on the path node allocation data, extract the resource replacement nodes whose reconnection value has not reached the preset reconnection value, and search for unoccupied resource relationships in the resource occupancy data according to the business field of the resource replacement node. Write the resource replacement nodes with unoccupied resource occupancy relationships into the replacement resource path. For resource replacement nodes with no available resource relationships, mark them as continuous lock control nodes and write them into the continuous lock control path.

[0137] By writing the original order process path, original equipment return path, replacement resource path, and continuous lockout path into the same collaborative processing record according to the order number and node sequence, a printing collaborative management solution is obtained.

[0138] In this embodiment of the invention, based on the lock control path data, the advancing nodes with the path status of continuing to advance and the lock control nodes with the path status of lock control waiting are extracted. The order nodes are divided into process advancing nodes, equipment return nodes, resource replacement nodes and continuous lock control nodes according to the node status and re-deployment return value, thus obtaining path node allocation data. The order nodes in the lock control path are further converted into process advancing nodes, equipment return nodes, resource replacement nodes and continuous lock control nodes.

[0139] Based on the path node allocation data, the order number, node order and resource usage relationship of the process advancement node are extracted, and the process advancement node is written into the original order process path according to the node order. This enables the collaborative management solution to record abnormal locked nodes and unaffected normal advancement nodes at the same time, avoiding the entire order process data being uniformly set to a waiting state due to the impact of a certain device maintenance record on some nodes.

[0140] Based on the path node allocation data, extract the device reconnection nodes whose reconnection value reaches the preset reconnection value, and write the target device number, reserved resource occupancy relationship, and frozen resource call relationship of the device reconnection node into the original device reconnection path. This indicates that the lock control node can still take over the original target device, original occupancy relationship, and original frozen call relationship after the maintenance record is closed. Based on the path node allocation data, extract the resource replacement nodes whose reconnection value does not reach the preset reconnection value, and search for unoccupied resource relationships in the resource occupancy data according to the business field of the resource replacement node. Write the resource replacement nodes with the retrieved unoccupied resource occupancy relationships into the replacement resource path. For those without retrieved unoccupied resource occupancy relationships, the path is closed. By using resource replacement nodes in resource relationships, marking them as continuous lock control nodes and writing them into continuous lock control paths, the system can further convert data objects where the original equipment failed to be reconnected or the original resource status does not meet the reconnection requirements into replacement resource paths. At the same time, continuous lock control paths are formed for nodes where no suitable resources can be found. By writing the original order process path, the original equipment reconnection path, the replacement resource path, and the continuous lock control path into the same collaborative handling record according to the order number and node order, a printing collaborative management scheme is obtained. This ensures that the order process, equipment operation and maintenance status, and resource occupancy status can maintain a corresponding relationship in the same collaborative management scheme, and determines the path-level flow relationship and the resource-level binding relationship.

[0141] Specifically, based on the lock control path data, the advancement nodes with a path status of "continue advancing" and the lock control nodes with a path status of "lock control waiting" are extracted. Then, according to the node status and re-engagement value, the order nodes are divided into process advancement nodes, equipment re-engagement nodes, resource replacement nodes, and continuous lock control nodes, resulting in path node allocation data, specifically including:

[0142] The system reads the order number, node number, node sequence, target device number, path status, propagated fields, pending propagation fields, occupied and reserved data, frozen data, associated maintenance record number, and re-deployment / reconnection value of each order node recorded in the lock control path data. The system aggregates the lock control path data according to the order number, then sorts the nodes under the same order according to node sequence, and reads the path status field of each node. When the path status of an order node is "continue," the system initially identifies it as a process advancement node. When the path status of an order node is "lock control waiting," the system further reads the re-deployment / reconnection value of that node and compares it with a preset re-deployment / reconnection value to determine whether the lock control node has the conditions to continue execution along the original device or process. For order nodes with a path status of "continue," the system marks them as process advancement nodes and records the node sequence and resource usage relationship for continuing execution along the original order process. For order nodes whose path status is locked and waiting, and whose reconnection value reaches the preset reconnection value, the system marks them as device reconnection nodes. This indicates that after the maintenance record is closed, the node has retained the data conditions for the original device reconnection, including resource occupancy, frozen resource call relationships, and subsequent path continuity. For order nodes whose path status is locked and waiting, but whose reconnection value does not reach the preset reconnection value, the system temporarily marks them as nodes awaiting resource retrieval and determines whether they can enter the resource replacement path based on resource occupancy data in subsequent steps. For nodes that cannot reconnect to the original device and cannot retrieve unoccupied resources, the system marks them as continuously locked nodes. The order number, node number, node sequence, path status, reconnection value, preset reconnection value, node allocation type, and allocation basis are written into the path node allocation data.

[0143] Specifically, based on the path node allocation data, the order number, node order, and resource allocation relationship of the process advancement nodes are extracted, and the process advancement nodes are written into the original order process path according to the node order. This includes:

[0144] The system filters order nodes with the node allocation type of "process advancement node" from the path node allocation data, and reads the order number, order batch, node number, node name, node sequence, preceding node identifier, succeeding node identifier, target equipment number, propagated fields, resource occupancy relationships, and current path status of each node. The system groups process advancement nodes under the same order according to order number and arranges them from front to back according to node sequence, forming a node sequence consistent with the original order's process route. For each process advancement node, the system reads its established resource occupancy relationships, such as equipment occupancy relationships, material occupancy relationships, personnel dispatch relationships, process parameter binding relationships, or quality inspection task relationships, and writes these resource occupancy relationships along with the node sequence into the original order's process path. The system retains the original connection relationships between process advancement nodes and preceding and succeeding nodes. If neither the preceding nor succeeding nodes of a process advancement node are affected by locking, the system directly connects that node to the original order process path. If the succeeding node of a process advancement node is a locking waiting node, the system still writes the process advancement node into the original order process path, but records a locking path reference at its subsequent connection position, enabling subsequent handling plans to identify whether there is a device reconnection, resource replacement, or continuous locking branch after the process advancement node. If there are multiple consecutive advancement nodes in an order, the system forms these nodes into continuous segments of the original order process path according to their node order. If there are situations where advancement nodes are separated by locking nodes, the system can form multiple sub-paths of the original order process and maintain their connection positions with the locking nodes in the collaborative handling record. The original order process path may include the order number, path number, set of process advancement nodes, node order, set of resource occupancy relationships, target device number, and path status.

[0145] Specifically, based on the path node allocation data, the device reconnection nodes whose reconnection values ​​reach the preset reconnection value are extracted, and the target device number, reserved resource occupancy relationship, and frozen resource call relationship of the device reconnection nodes are written into the original device reconnection path. This includes:

[0146] The system filters order nodes with the node allocation type of "equipment return node" from the path node allocation data. For each equipment return node, the system reads its re-entry return value, preset return value, target equipment number, associated maintenance record number, maintenance record closure marker, occupancy reservation data, call freeze data, node sequence, and subsequent node associations. Once the system confirms that the maintenance record corresponding to the equipment return node has been closed and the re-entry return value has reached or exceeded the preset return value, it includes the node in the original equipment return path construction scope. The system reads the target equipment number of the equipment return node and confirms that this target equipment number is consistent with the original equipment number bound to the order node before the lockout. The system reads the reserved resource occupancy relationships bound to this node from the occupancy reservation data, including the original equipment occupancy relationship, the original material locking relationship, the original personnel dispatch relationship, the original process parameter binding relationship, and other resource relationships formed before the lockout. The system simultaneously reads the frozen resource call relationships bound to the node from the frozen call data, including production tasks not yet issued to the original equipment, material calls not yet executed, process parameters not yet loaded, personnel execution not yet triggered, and business data not yet passed to subsequent nodes. The system uses the retained resource occupancy relationships as the front-end receiving data of the callback path and the frozen resource call relationships as the back-end call data to be unfrozen and continued execution, establishing the original equipment callback relationship between the two. The system generates a callback sub-path record for each equipment callback node. This record includes the order number, node number, node sequence, target equipment number, maintenance record number, re-entry callback value, preset callback value, set of retained resource occupancy relationships, set of frozen resource call relationships, callback triggering conditions, and post-call path status. The system records the order of unfreezing call relationships in this path, for example, first restoring equipment task issuance, then restoring process parameter loading, material calls, and personnel execution, and finally restoring the process handover relationship with subsequent nodes. If multiple device reconnection nodes correspond to the same target device, the system sorts the reconnection nodes according to their node order and device availability time, and writes them into the same original device reconnection path.

[0147] Specifically, based on the path node allocation data, resource replacement nodes whose reconnection values ​​have not reached the preset reconnection value are extracted. Then, according to the business field of the resource replacement node, unoccupied resource relationships are retrieved from the resource occupancy data. Resource replacement nodes with retrieved unoccupied resource occupancy relationships are written into the replacement resource path. For resource replacement nodes with no retrieved available resource relationships, they are marked as continuously locked nodes and written into the continuously locked path. This includes:

[0148] The system filters order nodes from the path node allocation data whose path status is locked and waiting and whose re-connection value has not reached the preset re-connection value, and uses these nodes as resource replacement judgment objects. The system reads the business field, resource requirement conditions, original target equipment number, original material requirement, original personnel requirement, original process parameter requirement, node priority, and subsequent node input requirements for each resource replacement judgment object. Based on the business field and resource requirement conditions of that node, the system searches the resource occupancy data for unoccupied resources that meet the requirements of that business field. The system performs queries separately for equipment resources, material resources, personnel resources, process parameter resources, and quality inspection resources. For equipment resources, the system searches for alternative equipment that matches the process type, equipment capacity, production line location, and availability time of the order node and is currently not occupied. For material resources, the system searches for paper, ink, printing plates, or auxiliary materials whose specifications, batches, quantities, and process requirements meet the needs of the order node and are not locked by other orders. For personnel resources, the system searches for operators or quality inspectors with corresponding job positions, shifts, and skill identifiers and that are not occupied by other nodes. For process parameter resources, the system searches for parameter templates, parameter versions, or equipment parameter sets that are compatible with the alternative equipment or the process requirements of the current node. The system matches the search results with the business fields of the resource replacement node to determine whether a replacement resource occupancy relationship can be formed. If an unoccupied resource that meets the conditions is found, the system marks the node as a resource replacement node and writes the replacement resource number, replacement resource type, replacement business field, replacement source, and target equipment or resource relationship after replacement into the replacement resource path.

[0149] For nodes where no unused resources matching the business field conditions are found, the system marks them as continuously locked nodes and writes them into the continuously locked path. The continuously locked path records the node's order number, node number, node priority, original target equipment number, re-call value (not reaching the preset call-back value), reason for empty resource search results, still-frozen resource call relationships, and continuously locked status. If a node only partially retrieves resources (e.g., alternative equipment is available but the original material is unavailable, or alternative materials are available but personnel resources are unavailable), the system can determine whether to enter the replacement resource path based on preset complete replacement rules. When the critical resource relationships required for replacement are incomplete, the system can temporarily write the node into the continuously locked path and record candidate resources that have been retrieved but have not yet formed a complete replacement relationship. The system writes replaceable nodes and non-replaceable nodes into the replacement resource path and the continuously locked path, respectively.

[0150] Embodiments of the present invention also provide a dynamic collaborative management system for printing resource operation and maintenance and information flow, the system comprising:

[0151] The data module is used to acquire order node data, equipment operation and maintenance data, and resource usage data to obtain basic printing data;

[0152] The propagation trajectory module is used to extract the order nodes in the pending state, their predecessor nodes and successor nodes, based on the printing basic data, identify the propagated fields and the fields to be propagated, and determine the propagation boundary to obtain the process propagation trajectory data.

[0153] The entry domain module is used to extract maintenance records and embed them into the propagation boundary based on the target device number of each order node in the process propagation trajectory data, determine the entry range of the maintenance record in the order node, and obtain maintenance entry domain data.

[0154] The restraint module is used to identify the degree of control over whether an order node can continue to flow when the operation and maintenance records enter the order process, based on the operation and maintenance entry domain data, and to obtain the node restraint value;

[0155] The lock control path module is used to identify lock control nodes and advance nodes based on node constraint values ​​and preset constraint values, retain the resource occupancy relationships in the propagated fields, freeze the resource call relationships in the fields to be propagated, and obtain lock control path data;

[0156] The reconnection module is used to identify the degree of process reconnection of the lock control node after the operation and maintenance record is closed, based on the lock control path data, and to obtain the reconnection value.

[0157] The collaborative management module is used to identify and construct the original order process path, the original equipment return path, the replacement resource path, and the continuous lock-in path based on the resubmission return value, so as to obtain the printing collaborative management solution.

[0158] It should be noted that this system is a system corresponding to the above method. All implementation methods in the above method embodiments are applicable to this embodiment and can achieve the same technical effect.

[0159] Embodiments of the present invention also provide a computing device, including: a processor and a memory storing a computer program, wherein the computer program, when executed by the processor, performs the method described above. All implementations in the above method embodiments are applicable to this embodiment and can achieve the same technical effects.

[0160] Embodiments of the present invention also provide a computer-readable storage medium storing instructions that, when executed on a computer, cause the computer to perform the method described above. All implementations in the above method embodiments are applicable to this embodiment and can achieve the same technical effects.

[0161] The above description represents the preferred embodiments of the present invention. It should be noted that those skilled in the art can make various improvements and modifications without departing from the principles of the present invention, and these improvements and modifications should also be considered within the scope of protection of the present invention.

Claims

1. A method for dynamic collaborative management of printing resource operation and maintenance and information flow, characterized in that, The method includes: Obtain order node data, equipment operation and maintenance data, and resource usage data to obtain basic printing data; Based on the basic printing data, the order nodes in the pending state, their predecessor nodes and successor nodes are extracted, the propagated fields and the fields to be propagated are identified and the propagation boundaries are determined to obtain the process propagation trajectory data; Based on the target device number of each order node in the process propagation trajectory data, the operation and maintenance record is extracted and embedded into the propagation boundary to determine the entry range of the operation and maintenance record in the order node, thus obtaining the operation and maintenance entry domain data. Based on the operation and maintenance entry domain data, identify the degree of control over whether the order node can continue to flow when the operation and maintenance record enters the order process, and obtain the node restraint value; Identify the locking and advancing nodes based on the node constraint value and the preset constraint value, retain the resource occupancy relationship in the propagated fields, freeze the resource calling relationship in the fields to be propagated, and obtain the locking path data; Based on the lock control path data, identify the degree of process reconnection after the operation and maintenance record is closed, and obtain the reconnection value; Based on the resubmission and return value, the original order process path, the original equipment return path, the replacement resource path, and the continuous lock control path are identified and constructed to obtain a printing collaborative management solution.

2. The method for dynamic collaborative management of printing resource operation and maintenance and information flow according to claim 1, characterized in that, Based on the printing baseline data, order nodes in the pending progress stage, along with their predecessor and successor nodes, are extracted. The propagated and pending fields are identified, and propagation boundaries are determined, yielding process propagation trajectory data, including: Based on the order node data, extract the order nodes whose node status is pending, and extract the predecessor and successor nodes of each order node according to the order number to obtain the node adjacency data. Based on the node adjacency data, extract the business fields that form resource occupancy relationships in each order node, and write them into the propagated fields according to their positions in the order nodes to obtain the propagated field data. Based on the node adjacency data, extract the business fields that subsequent nodes need to call but for which order nodes have not yet formed a resource occupation relationship, and write them into the fields to be propagated according to their positions in the order nodes to obtain the data of the fields to be propagated. Based on the data of the propagated fields and the data of the fields to be propagated, the handover position between the propagated fields and the fields to be propagated is determined according to the node order, the preceding node and the subsequent node, and the handover position is marked as the propagation boundary of the order node, thus obtaining the process propagation trajectory data.

3. The method for dynamic collaborative management of printing resource operation and maintenance and information flow according to claim 2, characterized in that, Based on the target device number of each order node in the process propagation trajectory data, the operation and maintenance record is extracted and embedded into the propagation boundary to determine the entry range of the operation and maintenance record in the order node, thus obtaining the operation and maintenance entry domain data, including: Based on the process propagation trajectory data, the target device number and propagation boundary of each order node are extracted, and the target device number is associated with the propagation boundary to obtain the device boundary data; Based on the equipment boundary data and equipment operation and maintenance data, extract the operation and maintenance records that correspond to the target equipment number and do not have a closure mark, and write the operation and maintenance records into the order node to obtain the operation and maintenance data to be embedded; Based on the operation and maintenance data to be embedded, identify the starting position of the operation and maintenance record in the business field of the order node, and embed the starting position of the record into the node position of the propagation boundary to obtain the operation and maintenance boundary embedding data. Based on the embedded data of the operation and maintenance boundary, the business fields covered from the record start position to the unclosed state are extracted along the node sequence of the order node, and the business fields are marked as the entry range of the operation and maintenance record in the order node to obtain the operation and maintenance entry domain data.

4. The method for dynamic collaborative management of printing resource operation and maintenance and information flow according to claim 3, characterized in that, Based on the operation and maintenance entry domain data, identify the degree of control over whether the order node can continue to flow when the operation and maintenance record enters the order process, and obtain the node constraint value, including: Based on the operation and maintenance entry domain data, calculate the proportion of the number of business fields covered by the entry range relative to the total number of business fields in the order node, identify the coverage degree formed by the operation and maintenance records within the current order node, and obtain the entry coverage item; calculate the interaction clamping degree between the business fields on the propagated side and the business fields on the side to be propagated within the same entry range, and obtain the boundary clamping item. Based on the operation and maintenance entry domain data, calculate the correlation ratio of the operation and maintenance record to adjacent order nodes, identify the degree of connection between the operation and maintenance record and the preceding and following process nodes other than the current order node, and obtain the node connection items. By integrating the entry coverage item, boundary clamping item, and node connection item, the degree of locking formed by the continued flow of order nodes when the operation and maintenance record enters the order process is identified, and the node restraint value is obtained.

5. The method for dynamic collaborative management of printing resource operation and maintenance and information flow according to claim 4, characterized in that, Based on the node constraint value and preset constraint value, lock control nodes and advance nodes are identified, and the resource occupancy relationships in the propagated fields are retained, while the resource call relationships in the fields to be propagated are frozen, thus obtaining lock control path data, including: By marking order nodes whose node restraint values ​​reach the preset restraint value as lock control nodes and order nodes whose node restraint values ​​do not reach the preset restraint value as advance nodes, node splitting data is obtained; Based on the node distribution data, extract the propagated fields of the lock control node and the resource occupancy relationship that has been formed, bind the resource occupancy relationship with the lock control node, and obtain the occupancy retention data; Based on the node distribution data, extract the fields to be propagated of the lock control node and the resource call relationships that have not yet been executed, and mark the resource call relationships with the lock control node to obtain the call freeze data; Based on the reserved data and the frozen data, the advancing nodes, locking nodes, resource occupancy relationships, and resource call relationships are written into the locking path according to the node order of the order nodes. The path status of the advancing nodes is marked as continue advancing, and the path status of the locking nodes is marked as locking waiting, thus obtaining the locking path data.

6. The method for dynamic collaborative management of printing resource operation and maintenance and information flow according to claim 5, characterized in that, Based on the lock control path data, identify the degree of process reconnection after the operation and maintenance record is closed, and obtain the re-connection value, including: Based on the maintenance record closure marker in the equipment maintenance data, identify the gating degree of the maintenance record closure status on the locking node's entry into the reconnection process, and obtain the closure gating item; identify the degree of restoration between the retained resource occupation relationship and the frozen resource call relationship of the locking node after the maintenance record is closed, and obtain the reconnection matching item. Based on the occupancy retention data and the call freeze data, calculate the number of relationships between the original resource number and the original business field after the operation and maintenance record is closed, identify the degree to which the original materials and personnel of the lock control node are still in a reconnectable state when the lock control node is re-entered, and obtain the state retention item; based on the lock control path data, identify whether the lock control node can maintain the degree of process connection with the subsequent order node after the lock control node is reconnected, and obtain the path continuity item; By integrating the closing gating item, the acceptance matching item, the state maintenance item, and the path continuity item, the degree of process reconnection is identified, and the lock control node continues to execute the original process after the operation and maintenance record is closed, thus obtaining the reconnection value.

7. The method for dynamic collaborative management of printing resource operation and maintenance and information flow according to claim 6, characterized in that, Based on the resubmission and return values, the original order process path, original equipment return path, replacement resource path, and continuous lockout path are identified and constructed to obtain a printing collaborative management solution, including: Based on the lock control path data, the advancement nodes with the path status of "continue advancing" and the lock control nodes with the path status of "lock control waiting" are extracted. The order nodes are then divided into process advancement nodes, equipment return nodes, resource replacement nodes, and continuous lock control nodes according to the node status and re-deployment return value, thus obtaining the path node allocation data. Based on the path node allocation data, extract the order number, node order and resource usage relationship of the process advancement node, and write the process advancement node into the original order process path according to the node order. Based on the path node allocation data, extract the device reconnection nodes whose reconnection value reaches the preset reconnection value, and write the target device number, reserved resource occupancy relationship and frozen resource call relationship of the device reconnection node into the original device reconnection path; Based on the path node allocation data, extract the resource replacement nodes whose reconnection value has not reached the preset reconnection value, and search for unoccupied resource relationships in the resource occupancy data according to the business field of the resource replacement node. Write the resource replacement nodes with unoccupied resource occupancy relationships into the replacement resource path. For resource replacement nodes with no available resource relationships, mark them as continuous lock control nodes and write them into the continuous lock control path. By writing the original order process path, original equipment return path, replacement resource path, and continuous lockout path into the same collaborative processing record according to the order number and node sequence, a printing collaborative management solution is obtained.

8. A dynamic collaborative management system for the operation and maintenance of printing resources and information flow, characterized in that: The system is used to perform the method as described in any one of claims 1 to 7, the system comprising: The data module is used to acquire order node data, equipment operation and maintenance data, and resource usage data to obtain basic printing data; The propagation trajectory module is used to extract the order nodes in the pending state, their predecessor nodes and successor nodes, based on the printing basic data, identify the propagated fields and the fields to be propagated, and determine the propagation boundary to obtain the process propagation trajectory data. The entry domain module is used to extract maintenance records and embed them into the propagation boundary based on the target device number of each order node in the process propagation trajectory data, determine the entry range of the maintenance record in the order node, and obtain maintenance entry domain data. The restraint module is used to identify the degree of control over whether an order node can continue to flow when the operation and maintenance records enter the order process, based on the operation and maintenance entry domain data, and to obtain the node restraint value; The lock control path module is used to identify lock control nodes and advance nodes based on node constraint values ​​and preset constraint values, retain the resource occupancy relationships in the propagated fields, freeze the resource call relationships in the fields to be propagated, and obtain lock control path data; The reconnection module is used to identify the degree of process reconnection of the lock control node after the operation and maintenance record is closed, based on the lock control path data, and to obtain the reconnection value. The collaborative management module is used to identify and construct the original order process path, the original equipment return path, the replacement resource path, and the continuous lock-in path based on the resubmission return value, so as to obtain the printing collaborative management solution.

9. A computing device, characterized in that, include: One or more processors; A storage device for storing one or more programs, which, when executed by one or more processors, cause the one or more processors to implement the method as described in any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a program that, when executed by a processor, implements the method as described in any one of claims 1 to 7.

Images