A method for checking and closed-loop management of multi-source data of kiln production scheduling

Abstract

The application discloses a kiln production scheduling multi-source data verification and closed-loop management method, relates to the technical field of kiln production line production scheduling and data management, and comprises the following steps: collecting production task data, equipment state data, kiln car state data, station state data and task execution feedback data, and constructing kiln production scheduling basic data; performing multi-source consistency verification based on task association analysis and production process rule matching to generate scheduling task data, and generating a task operation permission result; collecting task execution process data, identifying an execution stage, an execution sequence and execution integrity, generating a task execution result and updating production resource states; performing closed-loop verification to generate a production scheduling closed-loop result and a triggering condition of a next scheduling task. Through task association analysis, multi-source consistency verification, execution state analysis and production resource closed-loop updating, the data consistency of kiln production scheduling, the task execution reliability and the production process connection are improved.

Description

Technical Field

[0001] This invention relates to the field of kiln production line scheduling and data management technology, specifically a method for multi-source data verification and closed-loop management of kiln production scheduling. Background Technology

[0002] In recent years, kiln production lines have gradually adopted digital production scheduling systems to manage production tasks, equipment resources, kiln car resources, and workstation resources in a unified manner. Each production stage relies on production scheduling data to coordinate tasks and allocate resources. A kiln production line includes multiple production stages such as raw material processing, forming, conveying, drying, firing, and finished product transfer. These stages require collaborative management of kiln car resources, production tasks, and workstation status through production scheduling information. Existing production scheduling systems typically generate scheduling tasks based on single production requests or equipment feedback information, lacking a unified method for verifying production scheduling data, equipment status data, kiln car quantity data, and task execution result data.

[0003] In existing kiln production scheduling management, equipment feedback information is typically used to assist in determining the execution status of production tasks. However, due to the different sources of production scheduling data, inconsistencies between scheduled task data and actual production status can easily arise. In multi-station, multi-channel, and multi-equipment linkage scenarios, if consistency verification before task execution, confirmation of task execution status, and resource status updates rely primarily on a single signal, issues such as no kiln cars at the source location, a full kiln car at the target location, inconsistent kiln car loading status on shuttle cars, equipment feedback indicating completion but kiln cars not fully transferred, and inconsistencies between the number of kiln cars in the channel and the actual on-site status can easily occur. Furthermore, if the updated number of kiln cars in the channel is not linked to the production scheduling information in a closed loop, it can easily lead to untimely triggering of the next shuttle task, repeated triggering, or incorrect triggering conditions, affecting the scheduling and coordination of continuous kiln production lines.

[0004] Therefore, the field of kiln production scheduling management still needs a verification method for multi-source production data. By integrating production task data, equipment status data, kiln car status data, and task execution result data, it is possible to achieve consistency verification of production scheduling tasks, execution status tracking, and anomaly closed-loop management. Summary of the Invention

[0005] Based on the shortcomings of the prior art described above, the purpose of this invention is to provide a method for multi-source data verification and closed-loop management of kiln production scheduling to solve the above-mentioned technical problems.

[0006] To achieve the above objectives, the present invention provides the following technical solution: a method for multi-source data verification and closed-loop management of kiln production scheduling, comprising: S1: Collect basic data for kiln production scheduling. The basic data for kiln production scheduling includes: production task data, equipment status data, kiln car status data, workstation status data, and task execution feedback data. S2: Based on the basic data of kiln production scheduling, perform task association analysis and production process rule matching to construct a production task dataset, and generate scheduling task data based on the production task dataset. The scheduling task data includes: task type, task source location, task target location, task associated equipment, and task execution conditions. S3: Based on the scheduling task data, perform multi-source consistency verification on the kiln production scheduling basic data before operation, and generate task operation permission results containing whether scheduling is allowed or prohibited. S4: Collect task execution process data based on task execution permission results, analyze the execution status of the task execution process data, associate the execution order and confirm the execution integrity, and generate task execution status information; S5: Based on the task execution status information, determine the task completion status and identify abnormal status, generate the task execution result, and update the production resource status data by association based on the equipment status data, kiln car status data and workstation status data. S6: Perform correlation consistency analysis and closed-loop integrity verification on the updated production resource status data and task execution results, generate production scheduling closed-loop results, and match scheduling trigger conditions based on the production scheduling closed-loop results and the updated production resource status data to generate the trigger conditions for the next scheduling task.

[0007] The present invention is further configured such that the production task data includes: current production request information, production request information to be triggered, request type, request workstation, request time, request equipment number, and task priority; Equipment status data includes: equipment number, equipment type, equipment availability status, equipment fault status, and equipment feedback status; Kiln car status data includes: kiln car type, kiln car location, kiln car occupancy status, and kiln car circulation status; Workstation status data includes: workstation number, workstation type, workstation capacity, current number of occupants, and receiving capacity; Task execution feedback data includes: task number, execution stage, execution feedback time, execution feedback status, and exception feedback information.

[0008] The present invention is further configured such that constructing the production task dataset includes: Identify the task type corresponding to the current production request based on production task data; Based on task type, candidate equipment, candidate kiln cars, and candidate workstations related to the current production request are extracted from equipment status data, kiln car status data, and workstation status data. Establish candidate association relationships between the task source location and the task target location based on the location of the requesting workstation, the location of the candidate kiln car, and the receiving capacity of the candidate workstation; The production task dataset is generated by combining task type, candidate equipment, candidate kiln car, candidate workstation, and candidate relationships.

[0009] The present invention is further configured such that generating scheduling task data includes: The production task dataset is matched with the preset production process rules to determine the task source location, task target location, and task execution conditions corresponding to the task type. The associated devices for a task are determined based on the task's source location, target location, and device status data. The execution order of scheduled task data is determined based on task priority and request time. The task type, source location, target location, associated device, execution conditions, and execution order are combined to generate scheduling task data.

[0010] The present invention further specifies that the multi-source consistency verification before operation includes: Perform consistency verification of the source kiln car based on the task source location and kiln car status data in the scheduling task data; Perform a consistency check of target workstation capacity based on the task target location and workstation status data in the scheduling task data; Perform availability consistency verification of associated devices based on task-related devices and device status data in the scheduling task data; Perform a consistency check of task conditions based on the task execution conditions, kiln car status data, and workstation status data in the scheduling task data. The consistency verification results of source kiln cars, target workstation capacity, associated equipment availability, and task conditions are summarized to generate multi-source consistency verification results before operation.

[0011] The present invention is further configured such that generating the task execution license result includes: When the multi-source consistency verification results before execution all meet the task execution conditions corresponding to the scheduling task data, a task execution permit result that allows scheduling is generated. If any result in the multi-source consistency check before execution does not meet the task execution conditions corresponding to the scheduled task data, a task execution permission result that prohibits scheduling is generated, and an exception prompt message is generated. The error message includes: the type of abnormal data, the location of the abnormal task, the number of the abnormal equipment, the status of the abnormal kiln car, the status of the abnormal workstation, and the reason for the abnormality.

[0012] The present invention is further configured such that generating task execution status information includes: When the task execution permission result indicates that scheduling is allowed, collect task execution process data according to the scheduled task data; Identify the current task execution stage based on task execution process data; Associate the current task execution phase with the execution order in the scheduled task data to generate an execution order association result; Based on task execution feedback data, determine whether the current task execution phase is complete and generate an execution integrity confirmation result; The task execution status information is generated by combining the current task execution stage, execution order association results, and execution integrity confirmation results.

[0013] The present invention is further configured such that generating the task execution result includes: Determine whether the task corresponding to the scheduled task data has been completed based on the task execution status information; When the task execution status information indicates that each execution stage has been completed and no abnormal feedback information has occurred, a task completion status is generated. When the task execution status information indicates that any execution stage is not completed, the execution order is inconsistent, or there is abnormal feedback information, an abnormal task status is generated. Associate the task completion status or task exception status with the task number, task type, task source location, and task target location to generate the task execution result.

[0014] The present invention is further configured such that generating updated production resource status data includes: When the task execution result represents the task completion status, the kiln car location and kiln car circulation status in the kiln car status data are updated based on the task source location. Update the current occupied quantity and receiving capacity of the workstation status data based on the task target location; Update the device availability status and device feedback status in the device status data based on the task-associated device; The updated equipment status data, updated kiln car status data, and updated workstation status data are combined to generate updated production resource status data. When the task execution result indicates an abnormal state, maintain the current valid state of the equipment status data, kiln car status data, and workstation status data, and record the abnormal state association information.

[0015] The present invention is further configured such that the triggering conditions for generating the production scheduling closed-loop result and the next scheduling task include: Based on the updated production resource status data and task execution results, perform consistency checks on task completion, resource quantity, and status change. When the task completion consistency check, resource quantity consistency check, and state change consistency check all pass, a production scheduling closed-loop result is generated. If any check fails, a closed-loop exception message containing data anomalies, status anomalies, or task anomalies is generated. Based on the production scheduling closed-loop results, available equipment, available kiln cars, available workstations, and pending production requests are extracted from the updated production resource status data. The available equipment, available kiln cars, available workstations, and pending production requests are matched with preset production process rules to generate the trigger conditions for the next scheduling task. The trigger conditions for the next scheduling task include: the type of the next task, the source location of the next task, the target location of the next task, and the trigger reason.

[0016] This invention provides a method for multi-source data verification and closed-loop management of kiln production scheduling. The method comprises: S1: collecting basic kiln production scheduling data, including production task data, equipment status data, kiln car status data, workstation status data, and task execution feedback data; S2: performing task association analysis and production process rule matching based on the basic kiln production scheduling data to construct a production task dataset, and generating scheduling task data based on the production task dataset. The scheduling task data includes: task type, task source location, task target location, associated equipment, and task execution conditions; S3: performing multi-source consistency verification on the basic kiln production scheduling data before operation, generating a task operation permission result containing whether scheduling is allowed or prohibited. 4. Based on the task execution permission result, collect task execution process data, analyze the execution status, associate the execution order, and confirm the execution integrity of the task execution process data to generate task execution status information; S5. Based on the task execution status information, determine the task completion status and identify abnormal states to generate task execution results, and update the data based on equipment status data, kiln car status data, and workstation status data to generate updated production resource status data; S6. Perform correlation consistency analysis and closed-loop integrity verification on the updated production resource status data and task execution results to generate production scheduling closed-loop results, and match scheduling trigger conditions based on the production scheduling closed-loop results and updated production resource status data to generate the trigger conditions for the next scheduling task. The beneficial effects include: Improve the reliability of data verification before production scheduling: By incorporating production task data, equipment status data, kiln car status data, workstation status data, and task execution feedback data into multi-source verification before operation, it is possible to uniformly confirm the task source location, task target location, resource availability status, workstation capacity status, and task execution conditions before execution, and generate task operation permission results that allow or prohibit scheduling. This helps to reduce situations such as inconsistent resource status, unmet task conditions, or abnormal resources participating in scheduling, thereby improving the accuracy and reliability of production scheduling data.

[0017] Improve the traceability of task execution: By collecting task execution process data and analyzing the execution status, associating the execution order, and confirming the execution integrity of the data, task execution status information is formed, enabling full-process tracking of production scheduling task execution. This helps to promptly detect execution anomalies, execution order anomalies, and incomplete execution, thereby improving the ability to manage task execution status.

[0018] Improve the consistency of production resource status: By updating the equipment status data, kiln car status data and workstation status data based on the task execution results, and combining the updated production resource status data to carry out correlation consistency analysis and closed-loop integrity verification, the synchronous update between task execution results and production resource status can be achieved, which helps to reduce resource status recording errors, status omissions or inconsistent resource information. Improve the continuity of production scheduling: By matching scheduling trigger conditions based on the closed-loop results of production scheduling and the updated production resource status data, the trigger conditions for the next scheduling task are generated, realizing the data connection between the current task execution results and subsequent production tasks. This helps to reduce situations such as repeated task triggering, missed triggering, or inconsistent trigger conditions, thereby improving the continuity and coordination of the production scheduling process.

[0019] The above description is only an overview of the technical solution of this application. In order to better understand the technical means of this application and to implement it in accordance with the contents of the specification, and to make the above and other objects, features and advantages of this application more obvious and understandable, the following are specific embodiments of this application. Attached Figure Description

[0020] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort. In the drawings: Figure 1The flowchart illustrates a method for multi-source data verification and closed-loop management of kiln production scheduling, which is an exemplary embodiment of the present invention. Detailed Implementation

[0021] The embodiments of the present invention will be described below with reference to the accompanying drawings and preferred embodiments. Those skilled in the art can easily understand other advantages and effects of the present invention from the content disclosed in this specification. The present invention can also be implemented or applied through other different specific embodiments, and various details in this specification can also be modified or changed based on different viewpoints and applications without departing from the spirit of the present invention. It should be understood that the preferred embodiments are only for illustrating the present invention and not for limiting the scope of protection of the present invention.

[0022] It should be noted that the illustrations provided in the following embodiments are only schematic representations of the basic concept of the present invention. Therefore, the drawings only show the components related to the present invention and are not drawn according to the actual number, shape and size of the components in the actual implementation. In the actual implementation, the form, quantity and proportion of each component can be arbitrarily changed, and the layout of the components may also be more complex.

[0023] In the following description, numerous details are explored to provide a more thorough explanation of embodiments of the invention. However, it will be apparent to those skilled in the art that embodiments of the invention may be practiced without these specific details. In other embodiments, well-known structures and devices are shown in block diagram form rather than in detail to avoid obscuring embodiments of the invention.

[0024] Example: A method for multi-source data verification and closed-loop management of kiln production scheduling, such as Figure 1 As shown, it includes: S1: Collect basic data for kiln production scheduling. The basic data for kiln production scheduling includes: production task data, equipment status data, kiln car status data, workstation status data, and task execution feedback data. S2: Based on the basic data of kiln production scheduling, perform task association analysis and production process rule matching to construct a production task dataset, and generate scheduling task data based on the production task dataset. The scheduling task data includes: task type, task source location, task target location, task associated equipment, and task execution conditions. S3: Based on the scheduling task data, perform multi-source consistency verification on the kiln production scheduling basic data before operation, and generate task operation permission results containing whether scheduling is allowed or prohibited. S4: Collect task execution process data based on task execution permission results, analyze the execution status of the task execution process data, associate the execution order and confirm the execution integrity, and generate task execution status information; S5: Based on the task execution status information, determine the task completion status and identify abnormal status, generate the task execution result, and update the production resource status data by association based on the equipment status data, kiln car status data and workstation status data. S6: Perform correlation consistency analysis and closed-loop integrity verification on the updated production resource status data and task execution results, generate production scheduling closed-loop results, and match scheduling trigger conditions based on the production scheduling closed-loop results and the updated production resource status data to generate the trigger conditions for the next scheduling task.

[0025] The present invention is further configured such that the production task data includes: current production request information, production request information to be triggered, request type, request workstation, request time, request equipment number, and task priority; Equipment status data includes: equipment number, equipment type, equipment availability status, equipment fault status, and equipment feedback status; Kiln car status data includes: kiln car type, kiln car location, kiln car occupancy status, and kiln car circulation status; Workstation status data includes: workstation number, workstation type, workstation capacity, current number of occupants, and receiving capacity; Task execution feedback data includes: task number, execution stage, execution feedback time, execution feedback status, and abnormal feedback information. Specifically, the central control room connects to the kiln production line control cabinets, shuttle car control cabinets, traction machine control cabinets, beat machine control cabinets, stepper machine control cabinets, kiln door control cabinets, stop door control cabinets, and inner top mechanism control cabinets via industrial Ethernet. It uses programmable logic controller register mapping, equipment address mapping, periodic scanning, and event triggering to collect production task data, equipment status data, kiln car status data, workstation status data, and task execution feedback data. Production requests trigger data collection when status changes. Equipment status data, kiln car status data, and workstation status data are collected according to a default 100-millisecond scan cycle. When there are many industrial network nodes or slow on-site feedback, the scan cycle is adjusted to 100-millisecond to 500-millisecond. Task execution feedback data is generated immediately when the feedback status changes and is reconfirmed in subsequent scan cycles. The central control room uses the central control room system clock to unify data time. The control cabinets upload local time and incrementing data sequence numbers. The central control room deletes duplicate data based on the incrementing data sequence number and corrects the control cabinet time deviation based on the data reception time. Production task data is used to record kiln production scheduling needs. Current production request information indicates production requests that have met the basic triggering conditions and entered task association analysis. Production request information awaiting triggering indicates production requests that have not yet entered task association analysis because the preceding task has not yet closed the loop, the target workstation does not have the receiving capability, the associated equipment is unavailable, or the task priority is low. Once the preconditions are met, the production request information awaiting triggering will be updated to the current production request information. Request types include billet line shortage request, billet completion request, wet billet conveying line kiln entry request, drying kiln exit request, calcining kiln exit request, and finished billet conveying line receiving request. The central control room converts these requests into billet line replenishment requests using a preset request type lookup table. The process includes: billet transfer, wet billet entering the kiln, billet exiting the drying kiln, billet exiting the firing kiln, and receiving the finished product line. A unique workstation number indicates the location where the production request was generated or served. The request time is the time the production request is first identified. The requesting device number is the unique number of the device that generated or uploaded the production request. Task priorities are set to three levels: Normal, Priority, and Emergency. Normal is the default. Emergency is set when the kiln door is already open, kiln cars are transferring across workstations, or preceding process equipment needs to be released immediately. Priority is set when there are missing kiln cars at the kiln inlet, backlogged kiln cars at the kiln outlet, or further delays may affect the production cycle. When multiple production requests exist simultaneously, they are arranged sequentially according to task priority, request time, and requesting device number.Equipment status data describes whether field equipment can participate in scheduling tasks. Equipment number is a unique identification code for field equipment. Equipment types include shuttle equipment, traction equipment, cycle equipment, positioning equipment, kiln door equipment, stop door equipment, inner jacking mechanism, and detection equipment. Shuttle equipment specifically refers to shuttle vehicles, traction equipment to traction machines, cycle equipment to cycle machines, positioning equipment to precision positioning stepper machines, kiln door equipment to kiln doors, stop door equipment to stop doors, and detection equipment to detection sensors. Each device connects to the central control room through its corresponding control cabinet. The central control room binds equipment numbers to programmable logic controller (PLC) addresses, status register addresses, and feedback signal addresses through an equipment address mapping table. Equipment is considered available when communication is online, the fault status is "no fault," and the feedback status is "standby" or "reset." Otherwise, it is considered unavailable. Whether equipment is occupied by an incomplete task is determined separately through the task resource locking record. Equipment is considered available even if it is still occupied by an incomplete task. When a previous task is locked, it does not participate in matching other scheduled tasks; equipment fault states include no fault, communication fault, drive fault, sensor fault, action timeout, and state conflict; equipment feedback states include not triggered, standby, executing, execution completed, reset, and execution abnormal. When the field equipment has not yet received a task, it is recorded as not triggered; when the field equipment has the conditions to execute the task and is not occupied by a task, it is recorded as standby; when the field equipment has received a task but has not completed the current execution stage, it is recorded as executing; when the current execution stage is completed, it is recorded as execution completed; when the task ends and is reset, it is recorded as reset; when the feedback timeout, feedback sequence error, or feedback signal conflict occurs, it is recorded as execution abnormal; the default setting for equipment feedback response timeout is 30 seconds. When the rated action time of the equipment exceeds 30 seconds, it is set to 1.2 times the rated action time of the equipment. When the equipment operating environment fluctuates greatly, it is set to 1.5 times the rated action time of the equipment. The feedback must arrive within the equipment feedback response timeout and remain stable for 200 milliseconds.Kiln car status data describes the kiln car type, current location, resource occupancy, and production process progress. Kiln car types include empty car, half-car, full car, wet billet car, dried kiln car, and fired kiln car. The kiln car type is preferentially read from production task data or the results of previous tasks. If the production task data does not carry the kiln car type, it is determined based on the kiln car's location, the type of the source workstation, and process completion feedback. The central control room determines the kiln car's location by combining workstation detection sensors, shuttle car front and rear sensors, current occupancy quantity, and task execution feedback data. When both the shuttle car's front and rear sensors are disconnected and the source workstation detection sensor is valid, the source workstation is maintained. The shuttle car's front and rear sensors are configured according to... The preset sequence is updated to the shuttle position when the kiln car changes from the disconnected state to the connected state and remains connected for 200 milliseconds. The target workstation is updated when the sensors before and after the shuttle car change from the connected state to the disconnected state and the target workstation detection sensor is valid. When the detection results conflict, the location of the kiln car that passed the consistency check most recently is retained and position status conflict information is generated. The kiln car occupancy status includes idle, task occupied, shuttle occupied and abnormal lock. The kiln car is prohibited from participating in the next scheduling task matching until the abnormal lock is released. The central control room uses a finite state machine to update the kiln car flow status to pending scheduling, pending source transfer, source transfer in progress, shuttle transfer in progress, target transfer in progress, arrived or flow abnormal.Workstation status data describes the resource attributes and receiving conditions of production workstations. The workstation number is a unique code for each production workstation. Workstation types are set according to loading workstation, billet-making workstation, billet-storage workstation, wet billet conveying workstation, kiln inlet workstation, kiln outlet workstation, and finished billet conveying line receiving workstation. Workstation status data also includes workstation position calibration data and position confirmation range. The workstation position calibration data represents the position reference data when the shuttle equipment completes docking with the production workstation. The position confirmation range represents the allowable position interval for determining when the shuttle equipment reaches the corresponding production workstation. The workstation position calibration data and position confirmation range use the encoder calibration table established during the production line commissioning phase. If on-site calibration is not completed, the corresponding production workstation will not participate in scheduling task matching. Workstation capacity is calibrated based on the effective length of the aisle, the length of the kiln car, and the safe distance between adjacent kiln cars. For example, if the aisle can safely accommodate a maximum of six kiln cars, the workstation capacity is set to six cars. The current occupancy quantity is based on the most recent closed-loop passage. The integrity verification is based on the number of kiln cars. One kiln car is removed after it completely leaves the source station, and one kiln car is added after it completely enters the target station. When transferring multiple kiln cars in one task, the number of kiln cars is updated according to the actual number transferred. Before updating, the task number and station number are locked. The default locking time is 2 seconds, which can be adjusted to 1 to 5 seconds according to the industrial network communication latency. The receiving capability is determined to be capable when the current occupied number is less than the station capacity, the associated equipment is available, the station is not locked by another task, the station detection status is consistent with the no-car or car-car status corresponding to the current occupied number, and the kiln car type conforms to the production process rules. Otherwise, it is determined to be unable to receive kiln cars and the reason is recorded. When the current occupied number is zero, the station detection status should be no-car. When the current occupied number is greater than zero, the station detection status should be car-car. The full position status is determined based on the current occupied number equaling the station capacity. The station detection sensor is not directly used to count the exact number of kiln cars in the channel.Task execution feedback data is used to record the actual execution process of the scheduled tasks. The task number serves as a unique identifier for the scheduled task data and is synchronously written to the associated equipment control cabinet, kiln car status data, workstation status data, and feedback records. The central control room uses a preset task phase table and a finite state machine to identify the execution phases. The general execution phases include task permission confirmation, source workstation preparation, source transfer, transfer, target workstation preparation, target transfer, and task completion confirmation. For kiln entry and exit tasks, kiln door status confirmation, stop door status confirmation, and inner top mechanism status confirmation are added. The execution feedback time is the time when the equipment feedback status, sensor status, or workstation status first enters a stable state after being continuously stable for 200 milliseconds. Feedback status includes pending feedback, valid feedback, feedback timeout, abnormal feedback order, conflicting feedback status, and phase completion; abnormal feedback information records the abnormality type, abnormal equipment number, abnormal workstation number, abnormal execution phase, abnormal occurrence time, abnormal status value, and abnormal cause, and is bound to the task number; when the abnormality is not resolved, the kiln car location, kiln car circulation status, and current workstation occupancy quantity are not modified based on the feedback data of uncompleted execution phases or conflicting tasks, the business fact status of the most recent one that passed consistency verification is retained, and the equipment availability status, kiln car occupancy status, and workstation receiving capacity are updated based on independent and valid equipment fault feedback, kiln car location conflict feedback, and workstation status conflict feedback. The complete processing procedure involves the central control room loading a request type lookup table, equipment address mapping table, workstation parameter table, task stage table, and production process rules. It collects production requests and distinguishes between current and pending production requests. The processing order is determined based on task priority, request time, and request equipment number. The status of associated equipment is then read to determine equipment availability. Combining the source workstation type, previous task execution results, and sensor status, the kiln car type, kiln car location, kiln car occupancy status, and kiln car flow status are determined. Workstation capacity and current occupancy are read to determine receiving capacity. After a task begins, equipment feedback status and sensor changes are collected according to the task number. The execution stage is identified using the task stage table and finite state machine, and the execution order is verified. If feedback timeouts, sequence errors, location conflicts, insufficient capacity, or inconsistent quantities are detected, abnormal feedback information is generated, and the most recent valid resource status is retained. Finally, production task data, equipment status data, kiln car status data, workstation status data, and task execution feedback data are combined according to a unified task number and time base to generate basic kiln production scheduling data, which is then sent to the task association analysis and production process rule matching steps.

[0026] The present invention is further configured such that constructing the production task dataset includes: Identify the task type corresponding to the current production request based on production task data; Based on task type, candidate equipment, candidate kiln cars, and candidate workstations related to the current production request are extracted from equipment status data, kiln car status data, and workstation status data. Establish candidate association relationships between the task source location and the task target location based on the location of the requesting workstation, the location of the candidate kiln car, and the receiving capacity of the candidate workstation; The production task dataset is generated by combining task types, candidate equipment, candidate kiln cars, candidate workstations, and candidate relationships. Specifically, the central control room constructs the production task dataset using relational database conditional queries, request type lookup tables, equipment address mapping tables, production process rule tables, and production flow diagram adjacency matching. The task type represents the production business category corresponding to the current production request. The central control room reads the request type, request workstation, request equipment number, and task priority. Through the request type lookup table, it identifies the following requests in sequence: billet line shortage request, billet completion request, wet billet conveyor kiln entry request, drying kiln exit request, calcining kiln exit request, and finished product conveyor car receiving request as billet line replenishment, billet completion transfer, wet billet entering kiln, drying kiln exit, calcining kiln exit, and finished product line car receiving. When a request type cannot be matched, the construction of the production task dataset is paused, and the current production request is converted into a pending production request information. Candidate equipment represents the field equipment that can participate in the current production request. The central control room queries the equipment address mapping table by task type and requesting workstation to extract the corresponding shuttle equipment, traction equipment, cycle equipment, positioning equipment, kiln door equipment, stop door equipment, inner top mechanism, and detection equipment. It retains equipment with the available status as available, the fault status as fault-free, and the feedback status as standby or reset and not occupied by incomplete tasks. For example, the billet line replenishment corresponds to the upper traction machine, the billet line end traction machine, the precision positioning stepper, the shuttle car, and the detection sensor. The wet billet entering the kiln corresponds to the wet billet conveying line traction machine, the drying kiln door, the stop door, the inner top mechanism, the shuttle car, and the detection sensor. Candidate kiln cars represent records of kiln cars that meet the requirements of the task type. The central control room filters kiln car records based on kiln car type, location, occupancy status, and circulation status. For replenishing kiln cars on the billet-making line, empty or half-car cars located at the empty car loading station or half-car loading station are selected. For transferring kiln cars after billet-making, half-car or full-car cars located at the billet-making line loading station are selected. For wet billet entering the kiln, wet billet cars located at the wet billet conveying station are selected. For kiln exiting the drying kiln, dried kiln cars located at the drying kiln outlet station are selected. For kiln exiting the calcining kiln and receiving kiln cars on the finished product line, kiln cars located at the calcining kiln outlet station or... After firing, the kiln car at the intermediate transfer station is retained as a candidate kiln car when its occupation status is idle or bound to the current production request, its flow status is pending scheduling or has arrived, and its location is not conflicting. The kiln car is excluded when its occupation status is shuttle occupied or abnormally locked, or its flow status is abnormal. The location of the kiln car is confirmed by the station detection sensor and the front and rear sensors of the shuttle car. The detection signal is considered valid after being continuously stable for 200 milliseconds. When the detection results conflict, the location that passed the consistency check most recently is retained.Candidate workstations represent production workstations that can serve as task source or task target locations. The central control room reads the permitted workstation number and workstation type from the production process rule table based on the task type. Workstations whose type matches the task type and whose current occupancy is greater than zero are retained as source candidate workstations. When a source workstation is equipped with a workstation detection sensor, the workstation detection sensor must continuously maintain a vehicle presence status for 200 milliseconds. If the current occupancy is inconsistent with the workstation detection status, it is not retained as a source candidate workstation, and a source workstation status conflict is recorded. Workstations with receiving capability, current occupancy less than workstation capacity, available associated equipment, not locked by incomplete tasks, and whose kiln car type matches the production process rules are retained as target candidate workstations. Candidate associations represent the production task paths formed by the flow of candidate kiln cars from the source candidate workstation to the target candidate workstation. The central control room performs association queries based on task type, requesting workstation, candidate kiln car location, and candidate workstation number, and confirms allowed paths through adjacency matching in the production flow chart. For example, adding a kiln car to the billet-making line corresponds to the empty car loading workstation or the half-car loading workstation leading to the end workstation of the billet-making line; transferring a completed billet corresponds to the transfer from the billet-making line loading workstation to the half-car or full-car billet storage workstation; and wet billet entering the kiln corresponds to the wet billet conveying workstation. The kiln car exiting the dryer corresponds to the kiln exit station, which then leads to the subsequent firing station or intermediate transfer station. The kiln car exiting the calcining kiln corresponds to the kiln exit station, which leads to the finished product conveying line receiving station. The finished product conveying line receiving request serves as the target acceptance condition for the calcining kiln exit task. The same kiln car at the calcining kiln exit station will no longer generate a separate finished product line receiving task. The finished product line receiving task only applies to calcined kiln cars whose source location is an intermediate transfer station, and corresponds to the intermediate transfer station leading to the finished product conveying line receiving station. If the requested station does not match, the candidate kiln car's location is inconsistent with the source location, the target candidate station does not have receiving capacity, or there is no allowed path in the production process rule table, or not all the equipment required for the path has entered the candidate equipment, no candidate association relationship will be generated and the reason for exclusion will be recorded. When multiple candidate association relationships meet the conditions simultaneously, they are first arranged according to the preset station priority order in the production process rule table, for example, half-car priority is associated with half-car billet storage station, and full-car priority is associated with full-car billet storage station, and then arranged according to the request time from earliest to latest. The complete processing procedure is as follows: the central control room first identifies the task type, then filters candidate equipment, candidate kiln cars, source candidate workstations, and target candidate workstations. Subsequently, it verifies the location of the requested workstation, the candidate kiln car, the receiving capacity of the target candidate workstation, the allowed path, and the integrity of the path equipment. After verification, a candidate association number is generated. The task type, candidate equipment, candidate kiln cars, source candidate workstations, target candidate workstations, and candidate associations are combined according to the current production request number to generate a production task dataset. If no candidate association is formed, the current production request is converted into a pending production request information, and the reasons for no available equipment, no available kiln cars, no receiving workstations, or mismatched production process paths are recorded.

[0027] The present invention is further configured such that generating scheduling task data includes: The production task dataset is matched with the preset production process rules to determine the task source location, task target location, and task execution conditions corresponding to the task type. The associated devices for a task are determined based on the task's source location, target location, and device status data. The execution order of scheduled task data is determined based on task priority and request time. The scheduling task data is generated by combining task type, task source location, task target location, associated equipment, task execution conditions, and execution order. Specifically, the central control room uses relational database rule matching, equipment address mapping, finite state machines, and stable sorting methods to generate scheduling task data. Pre-set production process rules are stored in the central control room database, and the database records the allowed task source location, task target location, task execution conditions, execution stage order, and rule priority using task type and kiln car type as query indexes. Task execution conditions include the existence of kiln cars matching the task type at the task source location, the current number of occupied kiln cars at the task target location being less than the workstation capacity, the task target location having receiving capability, the associated equipment being available, the kiln car occupancy status not being abnormally locked, and the preceding task having been completed. The closed-loop integrity check and the request station conform to the production process rules. The default judgment condition for the existence of kiln cars at the task source location is that the current number of occupied kiln cars is greater than zero. When configuring station detection sensors at the task source location, the station detection sensors also need to continuously maintain a car-occupied state for 200 milliseconds. If the current number of occupied kiln cars is inconsistent with the station detection state, the source station state conflict is recorded and it is determined that the condition for the existence of kiln cars at the task source location is not met. The default judgment condition for the task-associated equipment to be in an available state is that the equipment communication is online, the equipment fault status is fault-free, and the equipment feedback status is standby or reset. The task-associated equipment also needs to not have resource locks caused by other unfinished tasks. The central control room reads the task type, candidate kiln cars, candidate workstations, and candidate relationships from the production task dataset. It then queries the production process rules by task type and kiln car type, matching the requested workstation, the location of the candidate kiln car, the source candidate workstation, and the target candidate workstation against each production process rule. Once a match is found, the source candidate workstation is determined as the task source location, and the target candidate workstation is determined as the task target location. For billet loading on the billet line, the process corresponds to loading an empty or half-car onto the billet car and moving it to the end of the billet loading line. For billet transfer after billet loading, the process corresponds to transferring the billet from the loading workstation on the billet loading line to the half-car or full-car billet storage station. For wet billets entering the kiln, the process corresponds to wet billet conveying. The process is as follows: from the kiln exit to the drying kiln inlet station; from the kiln outlet to the subsequent firing station or intermediate transfer station; from the calcining kiln outlet to the finished product conveying line receiving station; and from the intermediate transfer station to the finished product conveying line receiving station. The receiving request generated by the finished product conveying line for the calcining kiln outlet station serves as the target receiving condition for the calcining kiln exit task, and no longer generates a separate finished product line receiving task for the same kiln car. When it is found that the same kiln car is already bound to the calcining kiln exit task, the finished product line receiving request will be kept as a pending production request information until the calcining kiln exit task is closed or the task is abnormally resolved.Task-associated equipment represents the set of equipment that needs to provide execution feedback when completing the production process from the task source location to the task target location. The central control room queries the equipment address mapping table by task type, task source location, and task target location to extract source location associated equipment, target location associated equipment, and shared equipment. Then, it combines equipment status data to filter equipment that is in an available state and records the equipment number, equipment type, feedback signal address, and corresponding execution stage. The billet line replenishment corresponds to the upper traction equipment, billet line end traction equipment, precision positioning stepping equipment, shuttle car, and detection sensors. The wet billet entering the kiln corresponds to the wet billet conveying line traction machine, drying kiln door equipment, stop door equipment, inner top mechanism, shuttle car, and detection sensors. When any necessary equipment is unavailable, the candidate association is marked as pending recovery, and the unavailable equipment number and the reason for unavailability are recorded. The central control room uses a priority queue and stable sorting method to determine the execution order, arranging tasks in the order of urgent, priority, and normal. When tasks have the same priority, they are arranged from earliest to latest request time. When request times are the same, the order is determined by the order of the requesting device number in the device address mapping table. When a subsequent task depends on the execution result of a preceding task, the subsequent task is set to a waiting state until the preceding task passes the closed-loop integrity check. The complete processing procedure is as follows: The central control room first queries the production process rules by task type and kiln car type, verifying the location of the requesting workstation, candidate kiln car, source candidate workstation, target candidate workstation, and the receiving capacity of the target candidate workstation. After verification, the task source location, task target location, and task execution conditions are determined. Then, the device address mapping table is queried and task-related devices are filtered. Subsequently, the execution order is determined according to task priority, request time, and requesting device number. Finally, a unique task number is generated, and the task type, task source location, task target location, task-related devices, task execution conditions, and execution order are written into the same data record to generate scheduling task data. The task status is set to pending verification and sent to the pre-run multi-source consistency verification step.

[0028] The present invention further specifies that the multi-source consistency verification before operation includes: Perform consistency verification of the source kiln car based on the task source location and kiln car status data in the scheduling task data; Perform a consistency check of target workstation capacity based on the task target location and workstation status data in the scheduling task data; Perform availability consistency verification of associated devices based on task-related devices and device status data in the scheduling task data; Perform a consistency check of task conditions based on the task execution conditions, kiln car status data, and workstation status data in the scheduling task data. The consistency verification of source kiln cars, target workstation capacity, associated equipment availability, and task conditions is summarized to generate a pre-operation multi-source consistency verification result. Specifically, the central control room uses timestamp snapshots, relational database association queries, production process rule matching, finite state machines, and Boolean logic summarization methods to complete the pre-operation multi-source consistency verification. The central control room uses the time when the scheduling task data enters the verification state as a benchmark to extract the latest valid record from equipment status data, kiln car status data, and workstation status data. The interval between the status record and the verification time is not more than 2 seconds by default, and can be adjusted within the range of 1 to 5 seconds according to the industrial network communication cycle. If the set interval is exceeded, the status record is marked as data timeout. The sensor signal is considered valid after 200 milliseconds of continuous stability. The source kiln car consistency check is used to confirm that there are kiln cars at the task source location that meet the requirements of the current task. The central control room queries the kiln car status data based on the task source location and verifies the kiln car location, kiln car type, kiln car occupancy status, and kiln car circulation status. The check is considered successful when the kiln car location matches the task source location, the kiln car type matches the task type, the kiln car occupancy status is idle or already bound to the current task, and the kiln car circulation status is pending scheduling or has arrived. When the source workstation is configured with detection sensors, the current occupancy quantity of the source workstation must be greater than zero and the detection sensors must confirm the presence of kiln cars. If there is a conflict between the kiln car location, the detection sensor status, and the current occupancy quantity, the valid status of the most recent closed-loop integrity check is retained, and the check is considered unsuccessful. The target station capacity consistency check is used to confirm that the target location has remaining capacity to receive kiln cars. The central control room reads the station capacity, current number of occupants, receiving capability, task lock status, and station detection results corresponding to the target location. The check is considered successful when the current number of occupants is less than the station capacity, the receiving capability is available, the target location is not locked by an incomplete task, and the station detection result is consistent with the no-car or car-car ...The associated equipment availability consistency check is used to confirm that the associated equipment for a task is complete and can participate in the current task. The central control room queries the equipment address mapping table by task type, task source location, and task target location to obtain a list of necessary equipment. Then, the list of necessary equipment is compared with the associated equipment for the task. The check is considered successful if there are no missing necessary equipment, the equipment is online, the equipment fault status is fault-free, the equipment feedback status is standby or reset, and the equipment is not locked by other incomplete tasks. For example, the task of feeding wet billets into the kiln requires a wet billet conveyor traction machine, drying kiln door equipment, stop door equipment, inner top mechanism, ferry car, and detection sensors. If any necessary equipment is missing, communication times out, faulty, not reset, or occupied by an incomplete task, the check is considered unsuccessful, and the equipment number and the reason for the abnormality are recorded. The task condition consistency check is used to confirm that the task execution conditions in the scheduling task data are consistent with the current kiln car status data and workstation status data. The central control room checks the requested workstation and task type, kiln car type and task target location, kiln car status at the task source location, receiving capacity at the task target location, closed-loop status of preceding tasks, and resource occupation relationship according to the production process rule table. For example, half-car is matched with half-car billet storage workstation, and full-car is matched with full-car billet storage workstation. The wet billet entering the kiln task requires the wet billet car to be located at the wet billet conveying workstation and the drying kiln inlet workstation to have receiving capacity. When all task execution conditions are met, the check is deemed to have passed. If any task execution condition is not met, the condition name, actual status, and reason for the abnormality are recorded. The complete processing procedure involves the central control room first establishing a status snapshot and verifying data timeliness and sensor stability. Then, it checks the kiln car location, kiln car type, kiln car occupancy status, kiln car circulation status, current number of occupied kiln cars at the source workstation, and the status of detection sensors to generate a source kiln car consistency verification result. Next, it checks the current number of occupied kiln cars, workstation capacity, receiving capability, task lock status, and workstation detection results at the target workstation location to generate a target workstation capacity consistency verification result. Finally, it compares the necessary equipment list with the task-related equipment and verifies the equipment communication status, equipment fault status, equipment feedback status, and task... The system checks the availability of related equipment to determine the task occupancy status and generates a consistency verification result. Then, based on the production process rule table, it verifies the requested workstation, kiln car type, task source location, task target location, closed-loop status of preceding tasks, and resource occupancy relationships to generate a task condition consistency verification result. If all four verification results pass, a passed pre-run multi-source consistency verification result is generated; if any verification result fails, a failed pre-run multi-source consistency verification result is generated. The abnormal data type, abnormal task location, abnormal equipment number, abnormal kiln car status, abnormal workstation status, and abnormal reason are written into the verification details and sent to the task run permission result generation step.

[0029] The present invention is further configured such that generating the task execution license result includes: When the multi-source consistency verification results before execution all meet the task execution conditions corresponding to the scheduling task data, a task execution permit result that allows scheduling is generated. If any result in the multi-source consistency check before execution does not meet the task execution conditions corresponding to the scheduled task data, a task execution permission result that prohibits scheduling is generated, and an exception prompt message is generated. The anomaly alert information includes: abnormal data type, abnormal task location, abnormal equipment number, abnormal kiln car status, abnormal workstation status, and abnormal cause. Specifically, the central control room uses a rule engine, Boolean logic aggregation, finite state machine, and task status locking method to generate task execution permission results. These results indicate whether the scheduled task data can enter the task execution phase, including both allowed and prohibited scheduling states. The central control room reads the source kiln car consistency verification results, target workstation capacity consistency verification results, associated equipment availability consistency verification results, and task condition consistency verification results according to the task number, and confirms that the interval between the verification data and the verification time does not exceed the default 2 seconds. For industrial network communication cycles that are longer, this interval can be adjusted within the range of 1 to 5 seconds. Sensor signals need to be continuously stable for 200 milliseconds before they can be considered valid verification data. A successful source kiln car consistency verification indicates that there is a matching kiln car type at the task source location, the kiln car's location is valid, the kiln car's occupancy status is idle, or it is already bound to the current task and its flow status is normal. A successful target workstation capacity consistency verification indicates that the current number of kiln cars occupied at the task target location is less than the workstation capacity, and the location has receiving capability. Furthermore, if the task is not locked by incomplete tasks, and the consistency check of the availability of associated equipment passes, it means that the associated equipment is not missing, is online, has no faults, has been reset, and is not occupied by incomplete tasks. If the consistency check of the task conditions passes, it means that the requested workstation, kiln car type, task source location, task target location, closed-loop status of the preceding task, and resource occupation relationship all comply with the production process rules. When all four types of checks pass and each task execution condition has valid data support, the central control room uses a database transaction lock or a programmable logic controller interlock flag to lock the task number, task source location, task target location, kiln car, and task associated equipment. After successful locking, the task status is updated from pending verification to allowed scheduling, and a task execution permission result for allowed scheduling is generated. If any check result fails, the task execution condition lacks valid data, the check data times out, the sensor signal does not reach a stable time, or the resource lock fails, the central control room updates the task status to prohibited scheduling, generates a task execution permission result for prohibited scheduling, and stops releasing the task execution phase.Anomaly alerts are used to record the reasons for prohibiting scheduling. The anomaly data type indicates the category of data that is abnormal, including abnormal production task data, abnormal equipment status data, abnormal kiln car status data, abnormal workstation status data, and abnormal task execution conditions. The abnormal task location indicates the source location, target location, or production process node corresponding to the anomaly. The abnormal equipment number indicates the unique number of the equipment experiencing missing equipment, communication interruption, malfunction, failure to reset, or resource conflict. Abnormal kiln car status records kiln car type mismatch, inconsistent kiln car locations, abnormal kiln car occupancy status, or abnormal kiln car flow status. Abnormal workstation status records insufficient workstation capacity, conflicting current occupancy quantities, invalid receiving capacity, or task lock conflict. The anomaly cause is generated through a preset anomaly cause lookup table, including no kiln car at the source location, kiln car type mismatch, insufficient target workstation capacity, target workstation status conflict, missing necessary equipment, abnormal equipment communication, equipment malfunction, and equipment failure to reset. When multiple anomalies occur simultaneously, such as resource duplication, incomplete closure of preceding tasks, and timeout of verification data, all anomalies are retained and arranged in the default order of resource usage conflict, equipment failure, insufficient target workstation capacity, abnormal source kiln car, and timeout of verification data. The complete processing procedure is as follows: the central control room first checks the task number and the timeliness of the verification data, then judges the four types of verification results and task execution conditions item by item. If all conditions are met, resource locking is performed and a task execution permit result that allows scheduling is generated. If any condition is not met, a task execution permit result that prohibits scheduling is generated. The abnormal data type, abnormal task location, abnormal equipment number, abnormal kiln car status, and abnormal workstation status are extracted from the verification details. The cause of the anomaly is determined by the anomaly cause comparison table and an anomaly prompt message is generated. After the anomaly disappears, the equipment status data, kiln car status data, and workstation status data are re-collected and the multi-source consistency verification before operation is re-executed. The historical verification results are not directly used to generate new task execution permit results.

[0030] The present invention is further configured such that generating task execution status information includes: When the task execution permission result indicates that scheduling is allowed, collect task execution process data according to the scheduled task data; Identify the current task execution stage based on task execution process data; Associate the current task execution phase with the execution order in the scheduled task data to generate an execution order association result; Based on task execution feedback data, determine whether the current task execution phase is complete and generate an execution integrity confirmation result; The task execution status information is generated by combining the current task execution stage, execution sequence association results, and execution integrity confirmation results. Specifically, the central control room uses industrial Ethernet communication, programmable logic controller register mapping, event flow association, finite state machine, and sequence rule matching to generate task execution status information. Task execution process data includes task number, feedback device number, feedback status, feedback time, kiln car location, shuttle car location data, status of sensors before and after the shuttle car, workstation detection status, current number of source workstations occupied, and current number of target workstations occupied. When the task execution permission result is "allowed for scheduling" and the task resources are successfully locked, the central control room updates the task status to "in execution." A task execution data channel is established according to the task number, task source location, task target location, associated equipment, and execution order. Equipment feedback is collected via event triggering, and shuttle vehicle location data and sensor status are collected via periodic scanning. The default scanning period is 100 milliseconds, which can be adjusted to 100 to 500 milliseconds depending on the industrial network communication cycle. The central control room associates and arranges the task execution process data according to the task number, feedback time, and incrementing data sequence number. Data with inconsistent task numbers, duplicate data sequences, or feedback times earlier than the task start time is deleted. A feedback signal is considered valid after 200 milliseconds of continuous stability. The feedback stabilization time can be adjusted to 100 to 500 milliseconds depending on the sensor response speed.The current task execution stage represents the production process node where the scheduled task has arrived. The central control room reads the preset task stage table according to the task type and uses a finite state machine to divide the task execution process into task permission confirmation, task source location preparation, kiln car source transfer, kiln car shuttle transfer, task target location preparation, kiln car target transfer, and task completion confirmation. For wet billet entering the kiln, drying kiln exiting the kiln, and firing kiln exiting the kiln, it also includes kiln door status confirmation, stop door status confirmation, and inner top mechanism status confirmation. When the source location associated equipment generates effective feedback, it is identified as task source location preparation. When the source location traction equipment generates effective feedback and the sensors before and after the shuttle car change from the disconnected state to the connected state in a preset sequence, it is identified as kiln car source transfer. The preset change sequence of the sensors before and after the shuttle car is read from the sensor sequence mapping table according to the task source location, task target location, and kiln car movement direction. The sensor sequence mapping table is used during the production line debugging stage according to the kiln car's movement direction. The installation direction of the sensors before and after the shuttle car is established, and the first and last sensors to change are recorded for different task paths. When the location of the kiln car is updated to the shuttle location and the shuttle car position data obtained in two consecutive acquisition cycles both indicate that the distance between the shuttle car and the task target location has decreased, it is identified as a kiln car shuttle transfer. The default acquisition cycle is 100 milliseconds, and two consecutive acquisition cycles correspond to 200 milliseconds. After the acquisition cycle is adjusted, two consecutive acquisition cycles are still used as the location change confirmation condition. When the shuttle car position data enters the location confirmation range corresponding to the task target location and the target location associated equipment is in standby or reset state, it is identified as task target location preparation. When the target location associated equipment generates effective feedback and the sensors before and after the shuttle car change from the on state to the off state in a preset order, it is identified as kiln car target transfer. When the target station detection status confirms the existence of the kiln car and all necessary equipment completes effective feedback, it is identified as task completion confirmation. The central control room associates the current task execution phase with the execution order in the scheduling task data. When all preceding phases have been completed, the current task execution phase has not been repeatedly confirmed, and subsequent phases have not generated effective feedback in advance, the execution order association result is "consistent order". When the preceding phase has not been completed but subsequent phases have generated feedback, the execution order association result is "phase ahead". When the preset phase has not generated effective feedback, the execution order association result is "phase missing". When the same phase generates completion feedback repeatedly, the execution order association result is "phase duplicate". When the actual feedback order is the opposite of the preset execution order, the execution order association result is "order abnormal".The execution integrity verification result indicates whether the equipment feedback, sensor changes, and final state required for the current task execution phase meet the phase completion conditions. The central control room establishes a necessary feedback list based on the task phase table and compares the task execution feedback data with the necessary feedback list item by item. Equipment completion feedback needs to arrive within the equipment feedback response time limit and remain stable for 200 milliseconds. The default equipment feedback response time limit is set to 30 seconds. If the equipment's rated action time exceeds 30 seconds, it should be set to 1.2 times the rated action time. If the equipment's operating environment fluctuates significantly, it should be set to 1.5 times the rated action time. Kiln car source transfer requires that the source location be associated with the equipment completion feedback. The front and rear sensors of the shuttle car change from the off state to the on state in a preset sequence and remain on. For kiln car target transfer, the target location associated equipment must provide valid feedback, and the front and rear sensors of the shuttle car must change from the on state to the off state in a preset sequence and remain off. The time interval between the state changes of the two sensors is no more than 5 seconds by default, but can be set to 2 to 10 seconds depending on the kiln car's moving speed. For kiln car shuttle transfer, the shuttle car's position data must continuously change towards the target location, remain stable after entering the location confirmation range corresponding to the target location, and there should be no instances of invalid position data change, incorrect position change direction, or exceeding the location confirmation range. When all necessary feedback is valid, the feedback sequence is correct, the feedback time meets the set time limit, and the final state meets the stage completion conditions, the execution integrity confirmation result is stage complete. If any condition is not met, the execution integrity confirmation result is stage incomplete, and the missing feedback, abnormal equipment number, actual feedback status, and abnormal reason are recorded. The complete processing procedure is as follows: First, the central control room confirms the task execution permission result and resource lock status. Then, it collects and organizes task execution process data, identifies the current task execution stage through a task stage table and a finite state machine, associates the current task execution stage with the execution sequence, and generates an execution sequence association result. Next, it compares the task execution feedback data with the necessary feedback list and generates an execution integrity confirmation result. Finally, it combines the current task execution stage, the execution sequence association result, and the execution integrity confirmation result according to the task number to generate task execution status information. When the execution sequence association result is consistent and the execution integrity confirmation result is a complete stage, the process proceeds to the next task execution stage. When the execution sequence association result is abnormal or the execution integrity confirmation result is an incomplete stage, the current task execution stage is maintained and task execution abnormality information is recorded.

[0031] The present invention is further configured such that generating the task execution result includes: Determine whether the task corresponding to the scheduled task data has been completed based on the task execution status information; When the task execution status information indicates that each execution stage has been completed and no abnormal feedback information has occurred, a task completion status is generated. When the task execution status information indicates that any execution stage is not completed, the execution order is inconsistent, or there is abnormal feedback information, an abnormal task status is generated. The task completion status or abnormal status is associated with the task number, task type, task source location, and task target location to generate task execution results. Specifically, the central control room uses finite state machines, event flow association, task stage table matching, and Boolean logic summarization methods to generate task execution results. The task execution results are used to characterize whether the task corresponding to the scheduled task data is completed according to the preset production process, including task completion status and task abnormal status. The central control room collects task execution status information according to the task number and reads the expected execution stage and execution sequence from the task stage table according to the task type. For tasks such as billet line replenishment, billet completion transfer, and finished product line receiving, there are corresponding task permission confirmation, task source location preparation, kiln car source transfer, kiln car transfer, task target location preparation, kiln car target transfer, and task completion confirmation. For wet billet entering the kiln, drying kiln exiting the kiln, and firing kiln exiting the kiln, there are also corresponding kiln door status confirmations. The status of the gate and the inner top mechanism are confirmed. The central control room arranges the task execution status information according to the execution feedback time, and checks the execution sequence association results, execution integrity confirmation results, and abnormal feedback information of each expected execution stage. When the execution sequence association result is consistent and the execution integrity confirmation result is complete and there are no unresolved abnormal feedback information, the corresponding expected execution stage is marked as completed. The equipment completion feedback needs to arrive within the equipment feedback response time limit and remain stable for 200 milliseconds. The default equipment feedback response time limit is set to 30 seconds. When the rated action time of the equipment exceeds 30 seconds, it is set to 1.2 times the rated action time of the equipment. When the equipment operating environment fluctuates greatly, it is set to 1 / 3 times the rated action time of the equipment.With a 5x setting, the status of the sensors before and after the shuttle car needs to remain stable for 200 milliseconds. During the kiln car source transfer phase, the sensors before and after the shuttle car must change from off to on in a preset sequence. During the kiln car target transfer phase, the sensors before and after the shuttle car must change from on to off in a preset sequence. The time interval between the status changes of the two sensors should not exceed 5 seconds by default, but can be adjusted within the range of 2 to 10 seconds depending on the kiln car's moving speed. The central control room generates a task when all expected execution phases are marked as completed, the actual execution sequence conforms to the execution sequence, the task target location detection status confirms that the kiln car has arrived, and the task execution feedback data does not contain any unresolved equipment faults, feedback timeouts, location anomalies, sensor status conflicts, or resource status conflicts. Completion status; Abnormal feedback information generated during task execution but resolved and re-verified is retained in the event log and no longer prevents the generation of task completion status; If any expected execution stage is not completed, the execution sequence association result is stage ahead of schedule, stage missing, stage duplicated, or sequence abnormal, the execution integrity confirmation result is stage incomplete, or there is unresolved abnormal feedback information in the task execution feedback data, the central control room generates a task abnormal status and records the abnormal execution stage, abnormal equipment number, actual feedback status, and abnormal cause; When multiple abnormalities occur simultaneously, all abnormal information is retained and arranged in the default order of equipment failure, execution sequence abnormality, stage feedback timeout, position status abnormality, and sensor status conflict; Task abnormal status generation Subsequently, the location of the kiln car, its circulation status, and the current number of workstations are not modified based on feedback data from incomplete or conflicting task execution phases; the business fact status that passed the most recent consistency check is retained. Equipment availability, kiln car occupancy, and workstation receiving capacity are updated based on independent and valid equipment fault feedback, kiln car location conflict feedback, and workstation status conflict feedback. This is used to restrict abnormal production resources from participating in subsequent scheduling. Unconfirmed task execution feedback data is not used to update production resource status. The complete process involves the central control room first reading the scheduling task data and task execution status information based on the task number, then extracting the expected execution phase and execution order based on the task type, and checking each expected execution phase for corresponding records and execution. The system checks whether the sequential association results are consistent, whether the execution integrity confirmation results are complete at each stage, and whether there are any unresolved abnormal feedback messages. Once all conditions are met, it continues to verify the task target location detection status, the final status of the sensors before and after the shuttle car, and the completion feedback of necessary equipment. If the verification passes, a task completion status is generated. If a missing execution stage, an incomplete execution stage, an inconsistent execution order, equipment feedback timeout, abnormal kiln car position, or sensor status conflict is detected, a task abnormal status is generated. Finally, the task completion status or task abnormal status, along with the task number, task type, task source location, task target location, task end time, and abnormal feedback information, are written into the same data record. The task execution result is then generated and sent to the production resource status data update step.

[0032] The present invention is further configured such that generating updated production resource status data includes: When the task execution result represents the task completion status, the kiln car location and kiln car circulation status in the kiln car status data are updated based on the task source location. Update the current occupied quantity and receiving capacity of the workstation status data based on the task target location; Update the device availability status and device feedback status in the device status data based on the task-associated device; The updated equipment status data, updated kiln car status data, and updated workstation status data are combined to generate updated production resource status data. When the task execution result indicates an abnormal state, the current valid state of equipment status data, kiln car status data, and workstation status data is maintained, and the abnormal state association information is recorded. Specifically, the central control room uses task number association, finite state machine, database transaction, version number verification, and event log methods to generate updated production resource status data. The equipment status data, kiln car status data, and workstation status data that passed the pre-run multi-source consistency verification before the task started are saved as a resource status baseline version. The resource status baseline version includes the task number, generation time, and incrementing version number. When the task execution result is a task completion state, the central control room determines the target kiln car based on the task number, task source location, task target location, and task execution feedback data. The task target location detection sensor is continuously valid for 200 milliseconds, the sensors before and after the shuttle car are both disconnected, and the task target location... When the associated equipment completes the feedback and it is valid, the location of the target kiln car is updated from the task source location to the task target location, the kiln car circulation status is updated to "arrived", and the kiln car occupancy status is updated to "idle". The stabilization time of the detection sensor can be set within the range of 100 milliseconds to 500 milliseconds according to the sensor response speed. The central control room updates the workstation status data according to the actual number of transfers confirmed by the task execution feedback data. When transferring one kiln car at a time, the current occupancy number at the task source location is reduced by one and the current occupancy number at the task target location is increased by one. When transferring multiple kiln cars at a time, the data is updated according to the actual number of cars transferred. The current occupancy number at the task source location must not be less than zero, and the current occupancy number at the task target location must not be less than zero. The number of vehicles occupied must not exceed the workstation capacity. If, after the update, the current occupied number is less than the workstation capacity, the associated equipment for the task target location is available, and the task target location is not locked by any incomplete task other than the current task, the receiving capacity will be updated to have receiving capability. Resource locking formed by the current task is not considered an abnormal receiving capability, but the task target location must not participate in matching with other scheduling tasks before the production scheduling closed-loop result is generated; otherwise, the receiving capability will be updated to not have receiving capability, and the reason for full capacity, unavailable equipment, or resource occupation conflict will be recorded. For example, if the workstation capacity is six vehicles, the current occupied number before the update is five vehicles and one kiln car is transferred in, and the current occupied number after the update is six vehicles, the receiving capability will be updated to not have receiving capability. Before updating the workstation status data, the task source location and task target location are locked through database transactions. The default locking time is 2 seconds, which can be set within the range of 1 to 5 seconds depending on the industrial network communication latency. The update is committed when the resource status baseline version is consistent with the current database version; if the versions are inconsistent, the update is revoked and the workstation status data is reread. The central control room then updates the equipment status data based on the reset feedback and equipment fault status of the task-related equipment. When the task-related equipment has completed the reset and is fault-free, the equipment feedback status is updated from "execution completed" to "reset" and the equipment availability status is updated to "available". After the production scheduling closed-loop result is generated and the task resource lock is released, the equipment feedback status is updated from "reset" to "standby".When a reset timeout occurs, communication is interrupted, or a fault code exists, the equipment feedback status is updated to "execution abnormal" and the equipment availability status is updated to "unavailable." The central control room generates updated production resource status data by combining updated equipment status data, updated kiln car status data, and updated workstation status data according to the same task number, resource status version, and update time. The updated status, post-update status, task number, update time, and update basis are recorded in the resource status change log. When the task execution result is an abnormal status, the central control room does not modify the kiln car location, kiln car circulation status, and current workstation occupancy based on incomplete or conflicting task execution feedback data, retaining the most recently verified business fact status. The central control room can update the equipment availability status, kiln car occupancy status, and workstation receiving capacity based on independent and valid equipment fault feedback, kiln car location conflict feedback, and workstation status conflict feedback to restrict abnormal production resources from participating in subsequent scheduling. Abnormal status associated information includes task number... The process involves several steps: First, the central control room reads the task execution results and resource status baseline version. Upon task completion, it verifies the arrival conditions of the target kiln car. After successful verification, it updates the kiln car status data, workstation status data, and equipment status data. All updates are committed via database transaction to generate updated production resource status data. In cases of task anomalies, inconsistent resource status versions, or incomplete target kiln car arrival conditions, uncommitted updates are revoked, the most recent valid production resource status is maintained, and anomaly-related information is recorded. If the kiln car's location cannot be confirmed, its occupancy status is updated to "abnormally locked," and the most recent valid kiln car location is retained. If the workstation detection status conflicts with the current occupancy quantity, the most recent valid current occupancy quantity is retained, and the receiving capability is updated to "no receiving capability." If the task-related equipment is faulty, the equipment availability status is updated to "unavailable" based on the fault feedback. The complete process involves the central control room first reading the task execution results and resource status baseline version. Upon task completion, it verifies the arrival conditions of the target kiln car. After successful verification, it updates the kiln car status data, workstation status data, and equipment status data. All updates are committed via database transaction to generate updated production resource status data. In cases of task anomalies, inconsistent resource status versions, or incomplete target kiln car arrival conditions, uncommitted updates are revoked, the most recent valid production resource status is maintained, and anomaly status association information is recorded.

[0033] The present invention is further configured such that the triggering conditions for generating the production scheduling closed-loop result and the next scheduling task include: Based on the updated production resource status data and task execution results, perform consistency checks on task completion, resource quantity, and status change. When the task completion consistency check, resource quantity consistency check, and state change consistency check all pass, a production scheduling closed-loop result is generated. If any check fails, a closed-loop exception message containing data anomalies, status anomalies, or task anomalies is generated. Based on the production scheduling closed-loop results, available equipment, available kiln cars, available workstations, and pending production requests are extracted from the updated production resource status data.The available equipment, available kiln cars, available workstations, and pending production requests are matched with preset production process rules to generate the trigger conditions for the next scheduling task. The trigger conditions for the next scheduling task include: the type of the next task, the source location of the next task, the target location of the next task, and the trigger reason. Specifically, the central control room uses a method of task number association, resource status version comparison, production process rule matching, finite state machine and Boolean logic aggregation to generate production scheduling closed-loop results and trigger conditions for the next scheduling task. Task completion consistency verification confirms that the task execution result, task execution status information, and updated production resource status data are consistent. The task completion consistency verification passes when the task execution result is a completed task, all execution stages are complete, the execution sequence association results are consistent, the task target location detection sensor confirms the arrival of the kiln car, the kiln car's location is updated to the task target location, and there are no unresolved abnormal feedback messages. The task target location detection sensor is considered valid after 200 milliseconds of continuous stabilization; the stabilization time can be set within the range of 100 to 500 milliseconds depending on the sensor's response speed. Resource quantity consistency verification confirms that the changes in the current occupied quantity at the task source location and task target location are consistent with the actual transferred quantity. When transferring one kiln car at a time, the current occupied quantity at the task source location decreases by one car, and the current occupied quantity at the task target location increases by one car. When multiple kiln cars are involved, the actual number of cars transferred is verified according to the task execution feedback data. The current number of cars occupied at the task source location must not be less than zero, and the current number of cars occupied at the task target location must not exceed the workstation capacity. For example, if the task source location had three cars before the update, the task target location had five cars before the update, the workstation capacity was six, and one kiln car was transferred, the updated numbers would be two and six respectively. The consistency verification of status changes is used to confirm that the equipment status data, kiln car status data, and workstation status data conform to the production process rules. After the task is completed, the location of the kiln car should be updated to the task target location, the kiln car flow status should be updated to "arrived," the kiln car occupancy status should be updated to "idle," and the workstation receiving capacity should be re-determined based on the current number of cars occupied and the workstation capacity. The workstation detection status should be consistent with the "no car" or "car" status corresponding to the current number of cars occupied. When the task-related equipment has been reset and is fault-free, the equipment feedback status should be "reset" and the equipment availability status should be "available." If the equipment is still being reset or has a fault, the equipment availability status should remain "unavailable," and the reason should be recorded. After the production scheduling closed-loop result is generated and the task resource lock is released, the equipment feedback status is updated from "reset" to "standby."When all three consistency checks—task completion, resource quantity, and status change—pass, the central control room generates a production scheduling closed-loop result containing the task number, task type, task completion identifier, closed-loop completion time, resource status version, and resource lock release status, and releases the task resource lock. If any check fails, a closed-loop anomaly message is generated. This message includes the anomaly type, anomaly data item, actual status, expected status, anomaly location, anomaly equipment number, anomaly time, and anomaly cause. Anomaly types include data anomalies caused by inconsistent task numbers, conflicting resource status versions, or missing quantity records, as well as the kiln car's location and kiln car circulation status. Status anomalies caused by conflicts between equipment feedback status, current occupancy quantity, or receiving capacity; and task anomalies caused by incomplete execution phases, inconsistent execution order, inconsistent task execution results with on-site status, or unresolved anomaly feedback information. Before the closed-loop anomaly information is resolved, associated equipment, associated kiln cars, and associated workstations are prohibited from participating in the next scheduling task matching. After the production scheduling closed-loop result is generated, the central control room extracts available equipment from the updated production resource status data that is online, fault-free, has a standby or reset feedback status, and is available and not locked by incomplete tasks. It also extracts kiln car locations that are valid, kiln car occupancy status that is idle, and kiln car flow. Available kiln cars whose status changes to pending scheduling or arrived and whose type conforms to the production process rules are identified. Acceptable workstations with a current occupied quantity less than the workstation capacity, receiving capability, available associated equipment, and not locked by incomplete tasks are extracted. Newly generated current production request information and pending production request information whose preconditions have been met are extracted from the production task data as pending production requests. The central control room uses relational database queries and production process rule matching to match available equipment, available kiln cars, acceptable workstations, and pending production requests. For example, if the billet line generates a kiln car shortage request and there are empty or half-full kilns, and the end workstation of the billet line has receiving capability... Furthermore, when the associated equipment for replenishing the billet is available, the replenishment trigger condition for the billet line is generated. When there is a wet billet car at the wet billet conveying station, the drying kiln inlet station has receiving capability, and the drying kiln door equipment, stop door equipment, and inner top mechanism are available, the wet billet entering the kiln trigger condition is generated. When there is a kiln car after roasting at the roasting kiln outlet station, the finished billet conveying line receiving station has receiving capability, and the finished billet conveying line cycle timer is available, the roasting kiln exit trigger condition is generated. When there is a kiln car after roasting at the intermediate transfer station, the finished billet conveying line receiving station has receiving capability, and the finished billet conveying line cycle timer is available, the finished line receiving trigger condition is generated. When there is an unclosed-loop roasting kiln exit task, the finished line receiving request is kept in a pending trigger state.After the matching result remains valid for two consecutive acquisition cycles, the central control room generates the triggering conditions for the next scheduling task, which include the next task type, the source location of the next task, the target location of the next task, and the triggering reason. The acquisition cycle is set to 100 milliseconds by default, but can be adjusted within the range of 100 to 500 milliseconds according to the industrial network communication cycle. Triggering reasons include the generation of a new production request, completion of a preceding task, release of capacity at the target location of the task, restoration of availability of associated equipment, kiln car arrival at a schedulable location, or the fulfillment of the preconditions for the production request to be triggered. After the triggering conditions for the next scheduling task are generated, the production request status is updated to "triggered" and bound to the preceding task number and resource status version to prevent the same production request from being triggered repeatedly.

[0034] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method for multi-source data verification and closed-loop management of kiln production scheduling, characterized in that, include: S1: Collect basic data for kiln production scheduling. The basic data for kiln production scheduling includes: production task data, equipment status data, kiln car status data, workstation status data, and task execution feedback data. S2: Based on the basic data of kiln production scheduling, perform task association analysis and production process rule matching to construct a production task dataset, and generate scheduling task data based on the production task dataset. The scheduling task data includes: task type, task source location, task target location, task associated equipment, and task execution conditions. S3: Based on the scheduling task data, perform multi-source consistency verification on the kiln production scheduling basic data before operation, and generate task operation permission results containing whether scheduling is allowed or prohibited. S4: Collect task execution process data based on task execution permission results, analyze the execution status of the task execution process data, associate the execution order and confirm the execution integrity, and generate task execution status information; S5: Based on the task execution status information, determine the task completion status and identify abnormal status, generate the task execution result, and update the production resource status data by association based on the equipment status data, kiln car status data and workstation status data. S6: Perform correlation consistency analysis and closed-loop integrity verification on the updated production resource status data and task execution results, generate production scheduling closed-loop results, and match scheduling trigger conditions based on the production scheduling closed-loop results and the updated production resource status data to generate the trigger conditions for the next scheduling task.

2. The method for multi-source data verification and closed-loop management of kiln production scheduling according to claim 1, characterized in that, Production task data includes: current production request information, production request information to be triggered, request type, request workstation, request time, request equipment number, and task priority; Equipment status data includes: equipment number, equipment type, equipment availability status, equipment fault status, and equipment feedback status; Kiln car status data includes: kiln car type, kiln car location, kiln car occupancy status, and kiln car circulation status; Workstation status data includes: workstation number, workstation type, workstation capacity, current number of occupants, and receiving capacity; Task execution feedback data includes: task number, execution stage, execution feedback time, execution feedback status, and exception feedback information.

3. The method for multi-source data verification and closed-loop management of kiln production scheduling according to claim 2, characterized in that, Building the production task dataset includes: Identify the task type corresponding to the current production request based on production task data; Based on task type, candidate equipment, candidate kiln cars, and candidate workstations related to the current production request are extracted from equipment status data, kiln car status data, and workstation status data. Establish candidate association relationships between the task source location and the task target location based on the location of the requesting workstation, the location of the candidate kiln car, and the receiving capacity of the candidate workstation; The production task dataset is generated by combining task type, candidate equipment, candidate kiln car, candidate workstation, and candidate relationships.

4. The method for multi-source data verification and closed-loop management of kiln production scheduling according to claim 3, characterized in that, The generated scheduling task data includes: The production task dataset is matched with the preset production process rules to determine the task source location, task target location, and task execution conditions corresponding to the task type. The associated devices for a task are determined based on the task's source location, target location, and device status data. The execution order of scheduled task data is determined based on task priority and request time. The task type, source location, target location, associated device, execution conditions, and execution order are combined to generate scheduling task data.

5. The method for multi-source data verification and closed-loop management of kiln production scheduling according to claim 1, characterized in that, Pre-run multi-source consistency verification includes: Perform consistency verification of the source kiln car based on the task source location and kiln car status data in the scheduling task data; Perform a consistency check of target workstation capacity based on the task target location and workstation status data in the scheduling task data; Perform availability consistency verification of associated devices based on task-related devices and device status data in the scheduling task data; Perform a consistency check of task conditions based on the task execution conditions, kiln car status data, and workstation status data in the scheduling task data. The consistency verification results of source kiln cars, target workstation capacity, associated equipment availability, and task conditions are summarized to generate multi-source consistency verification results before operation.

6. The method for multi-source data verification and closed-loop management of kiln production scheduling according to claim 1, characterized in that, The generated task run license results include: When the multi-source consistency verification results before execution all meet the task execution conditions corresponding to the scheduling task data, a task execution permit result that allows scheduling is generated. If any result in the multi-source consistency check before execution does not meet the task execution conditions corresponding to the scheduled task data, a task execution permission result that prohibits scheduling is generated, and an exception prompt message is generated. The error message includes: the type of abnormal data, the location of the abnormal task, the number of the abnormal equipment, the status of the abnormal kiln car, the status of the abnormal workstation, and the reason for the abnormality.

7. The method for multi-source data verification and closed-loop management of kiln production scheduling according to claim 1, characterized in that, The generated task execution status information includes: When the task execution permission result indicates that scheduling is allowed, collect task execution process data according to the scheduled task data; Identify the current task execution stage based on task execution process data; Associate the current task execution phase with the execution order in the scheduled task data to generate an execution order association result; Based on task execution feedback data, determine whether the current task execution phase is complete and generate an execution integrity confirmation result; The task execution status information is generated by combining the current task execution stage, execution order association results, and execution integrity confirmation results.

8. The method for multi-source data verification and closed-loop management of kiln production scheduling according to claim 1, characterized in that, The generated task execution results include: Determine whether the task corresponding to the scheduled task data has been completed based on the task execution status information; When the task execution status information indicates that each execution stage has been completed and no abnormal feedback information has occurred, a task completion status is generated. When the task execution status information indicates that any execution stage is not completed, the execution order is inconsistent, or there is abnormal feedback information, an abnormal task status is generated. Associate the task completion status or task exception status with the task number, task type, task source location, and task target location to generate the task execution result.

9. The method for multi-source data verification and closed-loop management of kiln production scheduling according to claim 8, characterized in that, The updated production resource status data includes: When the task execution result represents the task completion status, the kiln car location and kiln car circulation status in the kiln car status data are updated based on the task source location. Update the current occupied quantity and receiving capacity of the workstation status data based on the task target location; Update the device availability status and device feedback status in the device status data based on the task-associated device; The updated equipment status data, updated kiln car status data, and updated workstation status data are combined to generate updated production resource status data. When the task execution result indicates an abnormal state, maintain the current valid state of the equipment status data, kiln car status data, and workstation status data, and record the abnormal state association information.

10. The method for multi-source data verification and closed-loop management of kiln production scheduling according to claim 1, characterized in that, The triggering conditions for generating the production scheduling closed-loop result and the next scheduling task include: Based on the updated production resource status data and task execution results, perform consistency checks on task completion, resource quantity, and status change. When the task completion consistency check, resource quantity consistency check, and state change consistency check all pass, a production scheduling closed-loop result is generated. If any check fails, a closed-loop exception message containing data anomalies, status anomalies, or task anomalies is generated. Based on the production scheduling closed-loop results, available equipment, available kiln cars, available workstations, and pending production requests are extracted from the updated production resource status data. The available equipment, available kiln cars, available workstations, and pending production requests are matched with preset production process rules to generate the trigger conditions for the next scheduling task. The trigger conditions for the next scheduling task include: the type of the next task, the source location of the next task, the target location of the next task, and the trigger reason.

Images