Real-time front-end and back-end synchronization and conflict reminding method and device of industrial production scheduling system

Abstract

The application provides a real-time front-end and back-end synchronization and conflict reminding method and device of an industrial scheduling system, and relates to the technical field of industrial systems. The method comprises the following steps: receiving and analyzing an incremental operation instruction sent by the front end, wherein the incremental operation instruction is generated by the front end according to an affected process after the front end listens to the operation of a process block corresponding to a target process in a Gantt chart; determining a current scheduling version according to an operation serial number, generating a candidate scheduling version based on the change attribute of the affected process, determining a local check range in the candidate scheduling version, determining a corresponding constraint check rule according to the operation type, performing constraint check on the local check range to obtain a check result, and sending the check result to the front end for conflict reminding. Through the application, real-time front-end and back-end synchronization and timely conflict feedback in the industrial scheduling process can be realized, and the data transmission efficiency and back-end processing efficiency in a high-frequency interaction scenario can be improved.

Description

Technical Field

[0001] This invention relates to the field of industrial systems technology, and in particular to a method and apparatus for real-time front-end and back-end synchronization and conflict alerting in an industrial production scheduling system. Background Technology

[0002] In the field of industrial production scheduling, Gantt charts, as a time-axis-based visual scheduling tool, are widely used in Advanced Planning and Scheduling (APS), Manufacturing Execution Systems (MES), and other production scheduling management systems. Through Gantt charts, users can intuitively view the arrangement of various processes, work orders, or equipment over different time periods, understand the start and end times, durations, resource allocation relationships, and process sequence of processes, and perform editing operations such as moving, adjusting, inserting, deleting, and locking production tasks based on a graphical interface. Because Gantt charts can simultaneously present information in the time, resource, and task dimensions, they have become a common human-computer interaction medium in industrial production scheduling scenarios.

[0003] In existing industrial scheduling systems, Gantt charts are typically used more as a static or semi-dynamic display and editing interface. Specifically, after users drag, stretch, delete, lock, modify planned quantities, or adjust priorities of process blocks on the front-end interface, the system often does not immediately send the corresponding data to the back-end for verification and processing. Instead, the user needs to click "Save" or "Submit" before the overall result of the current scheduling adjustment is sent to the back-end, which then processes and verifies the data based on constraints such as equipment capacity, process routes, resource usage, material availability, personnel scheduling, and order delivery dates.

[0004] However, the aforementioned "save or submit after editing" approach can easily lead to a lack of synchronization between the front-end and back-end states and delayed conflict feedback in industrial production scheduling scenarios. First, if the editing status in the front-end interface is not synchronized to the back-end in a timely manner during multiple Gantt chart editing operations by the user, there may be a discrepancy between the production scheduling results displayed on the front-end and the actual production scheduling logic accepted by the back-end, causing subsequent user operations to be based on an inaccurate state. For example, if a process is moved from the afternoon to the morning on the front-end Gantt chart, but this adjustment has not yet been sent to the back-end for verification, on-site operators may have already reported work based on the original production schedule or an unconfirmed new production schedule, resulting in inconsistencies between the reported work progress and the production plan. Another example is if the demand department temporarily increases the planned quantity of a production order on the front end; if this change is not promptly transmitted to the back end, the resulting changes in equipment load, material requirements, or subsequent process timing cannot be identified in a timely manner. Furthermore, in multi-person collaborative scheduling scenarios, different schedulers may simultaneously adjust the same workshop or related production lines based on their respective front-end local states. If one party's modification has not been synchronized and confirmed by the system in a timely manner, another party may continue to schedule processes even when existing resources are already occupied. Only when the unified submission is completed later will it be discovered that multiple operations have created resource or timing conflicts, leading to a decrease in collaborative efficiency.

[0005] Secondly, in the traditional post-submission validation model, the system typically performs constraint checks on the modified results only after the user has completed a series of editing operations. This means that users may only discover, after performing multiple drag-and-drop, sorting, or insertion operations, that an earlier step violated production logic constraints such as the unique task limit for a single time period of equipment, process sequence constraints, equipment downtime maintenance constraints, material availability constraints, or delivery date constraints. In this case, users often need to backtrack through multiple operation steps and readjust the scheduling plan, which not only increases the cost of manual troubleshooting but also reduces the smoothness and usability of scheduling interactions.

[0006] To address the aforementioned issues, an intuitive improvement approach is to have the system respond in real-time to each user's operation request while the user is editing the Gantt chart, sending the corresponding data to the backend for verification and feedback. This allows for real-time conflict alerts during the editing process and maintains consistency between the front-end and back-end. However, in industrial scheduling scenarios, Gantt charts typically carry a large amount of data, involving numerous work orders, processes, equipment, time windows, and their interdependencies. When users frequently perform high-frequency editing operations such as dragging, stretching, deleting, and locking, transmitting complete scheduling data or triggering large-scale recalculations with each operation would significantly increase network bandwidth usage, server communication overhead, and backend processing load. This could easily lead to increased response latency, decreased system throughput, and even negatively impact the front-end user experience and overall system stability. Therefore, how to achieve real-time response during Gantt chart editing while reducing data transmission and backend processing pressure under high-frequency interactions has become a pressing technical problem to be solved in industrial scheduling systems.

[0007] Therefore, a new industrial scheduling solution is needed to achieve real-time response and timely conflict feedback between the front end and back end during the Gantt chart editing process, while taking into account the data transmission efficiency and back-end processing efficiency in high-frequency interaction scenarios. Summary of the Invention

[0008] The purpose of this invention is to provide a method and apparatus for real-time front-end and back-end synchronization and conflict alerting in an industrial production scheduling system, in order to solve the above-mentioned technical problems in the prior art.

[0009] On the one hand, in order to achieve the above objectives, the present invention provides a method for real-time front-end and back-end synchronization and conflict alerting of an industrial production scheduling system.

[0010] The real-time front-end and back-end synchronization and conflict alert method of this industrial production scheduling system includes: receiving and parsing incremental operation instructions sent by the front end, wherein the front end is used to monitor the user's operation on the corresponding process block of the target process in the Gantt chart and identify the affected process, and generate incremental operation instructions based on the affected process. The incremental operation instructions include operation sequence number, operation type, identifier of the affected process, change attribute of the affected process, and identifier of the work order to which the affected process belongs. The change attribute includes information on the change in execution time of the affected process before and after the operation and / or change information on the execution equipment. The affected process includes the target process and the processes that change in conjunction with the change of the target process. The system determines the current production scheduling version corresponding to the incremental operation instruction based on the operation sequence number; changes the current production scheduling version using the change attribute to obtain a candidate production scheduling version; determines the local verification range in the candidate production scheduling version based on the identifier of the affected process and the identifier of the work order to which the affected process belongs; determines the constraint verification rule corresponding to the operation type in a preset constraint verification rule set; executes the constraint verification rule on the local verification range to obtain the verification result; and sends the verification result to the front end so that the front end can issue a conflict alert based on the verification result.

[0011] Furthermore, the front end uses the following steps to determine the processes that change in tandem with the target process: when the change attribute of the target process only includes execution time change information, the processes whose execution time is adjusted according to the preset translation rules are determined based on the process scheduling order in the swimlane of the equipment where the corresponding process block of the target process is located; when the change attribute of the target process includes execution equipment change information, the processes whose execution time is adjusted according to the preset replacement rules in the original swimlane of the equipment where the corresponding process block of the target process is located before the operation are determined, as well as the processes whose execution time is adjusted according to the preset translation rules in the new swimlane of the equipment where the corresponding process block of the target process is located after the operation are determined, as well as the processes whose execution time is adjusted according to the preset translation rules in the new swimlane of the equipment where the corresponding process block of the target process is located after the operation are determined, as well as the processes whose execution time is adjusted according to the preset translation rules in the new swimlane of the equipment where the corresponding process block of the target process is located after the operation are determined.

[0012] Furthermore, the steps for determining the scope of local verification in the candidate production scheduling version based on the identifier of the affected process and the identifier of the work order to which the affected process is located include: taking the affected process as the initial process for local verification; supplementing the processes that are adjacent to the affected process in the scheduling order in the candidate production scheduling version; supplementing the processes that have a pre-dependency or post-dependency relationship with the affected process based on the process route data corresponding to the work order to which the affected process is located; merging the initial process for local verification and the supplemented processes and removing duplicates to obtain the scope of local verification.

[0013] Furthermore, the constraint verification rules include hard constraint verification rules and soft constraint verification rules. Hard constraint verification rules include at least one of the following: equipment capacity matching rules, equipment single-time period unique task rules, process sequence rules, and equipment calendar rules. Soft constraint verification rules include at least one of the following: material completeness rules, personnel scheduling coverage rules, and delivery date risk rules. The steps for the front end to provide conflict reminders based on the verification results include: when the verification result indicates that the operation only has hard constraint conflicts, the front end overlays a hard constraint conflict label on the corresponding process block and restricts the user's operation range through interactive effects; when the verification result indicates that the operation only has soft constraint conflicts and no hard constraint conflicts, the front end overlays a soft constraint prompt label on the corresponding process block and outputs a non-blocking reminder; when the verification result indicates that the operation does not have constraint conflicts, the display state of the Gantt chart after the operation is maintained. When the verification result indicates that the operation only has soft constraint conflicts and no hard constraint conflicts, or when the operation does not have constraint conflicts, the front end is also used to update the version information of the production scheduling version. The operation sequence number includes version information and operation number.

[0014] Furthermore, after obtaining the verification result, the method also includes: when the verification result indicates that the operation only has hard constraint conflicts, maintaining the current production scheduling version; when the verification result indicates that the operation only has soft constraint conflicts and no hard constraint conflicts, or when the operation has no constraint conflicts, updating the current production scheduling version with the candidate production scheduling version, and sending the version information of the candidate production scheduling version to the front end.

[0015] Furthermore, the step of determining the constraint verification rule corresponding to the operation type in the preset constraint verification rule set includes: pre-establishing a correspondence table between the operation type and the constraint verification rules in the constraint verification rule set; and searching for one or more constraint verification rules corresponding to the operation type from the correspondence table according to the operation type.

[0016] Furthermore, the steps for executing constraint verification rules for a local verification range to obtain verification results include: obtaining constraint verification data corresponding to the local verification range, wherein the constraint verification data includes at least one of equipment capacity data, equipment calendar data, resource occupancy data, process route data, material availability data, and personnel scheduling data; executing constraint verification rules item by item on the affected processes within the local verification range based on the execution time change information and / or execution equipment change information of the affected processes in the candidate production scheduling version; and generating verification results based on the execution results of each constraint verification rule.

[0017] On the other hand, in order to achieve the above objectives, the present invention provides a real-time front-end and back-end synchronization and conflict alert device for an industrial production scheduling system.

[0018] The real-time front-end and back-end synchronization and conflict alert device of the industrial production scheduling system includes: a receiving and parsing module, used to receive and parse incremental operation instructions sent by the front end, wherein the front end is used to monitor the user's operation on the corresponding process block of the target process in the Gantt chart and determine the affected process, and generate the incremental operation instructions based on the affected process. The incremental operation instructions include an operation sequence number, an operation type, an identifier of the affected process, a change attribute of the affected process, and an identifier of the work order to which the affected process belongs. The change attribute includes information on the change in execution time of the affected process before and after the operation and / or information on the change in execution equipment. The affected process includes the target process and the processes that change in tandem due to the change in the target process. The system comprises: a first determining module for determining the current production scheduling version corresponding to the incremental operation instruction based on the operation sequence number; a changing module for changing the current production scheduling version using the changing attribute to obtain a candidate production scheduling version; a second determining module for determining a local verification range in the candidate production scheduling version based on the identifier of the affected process and the identifier of the work order to which the affected process is located; a third determining module for determining the constraint verification rule corresponding to the operation type in a preset constraint verification rule set; an execution module for executing the constraint verification rule on the local verification range to obtain a verification result; and a sending module for sending the verification result to the front end so that the front end can provide a conflict reminder based on the verification result.

[0019] On the other hand, to achieve the above objectives, the present invention also provides a computer device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the steps of the above method.

[0020] On the other hand, to achieve the above objectives, the present invention also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of the above method.

[0021] The present invention provides a method and apparatus for real-time front-end and back-end synchronization and conflict alerting in an industrial production scheduling system. The front-end identifies affected processes based on operations around the corresponding process blocks of the target process in the Gantt chart and generates incremental operation instructions based on these affected processes. The back-end receives and parses these incremental operation instructions, determines the corresponding current production scheduling version based on the operation sequence number, and forms candidate production scheduling versions based on the change attributes of the affected processes. Subsequently, a local verification range is determined in the candidate production scheduling versions based on the identifiers of the affected processes and the work orders to which they reside. Constraint verification rules corresponding to the operation type are determined from a preset set of constraint verification rules, and constraint verification is performed on the local verification range to obtain the verification result. The verification result is then sent to the front-end for conflict alerting. Through this invention, front-end editing operations are organized into incremental operation instructions around the affected processes, and after the back-end forms candidate production scheduling versions based on the current production scheduling version, constraint verification is performed only on the local verification range. This avoids repeatedly transmitting full production scheduling data and performing full verification on the entire production scheduling scheme during high-frequency editing of the Gantt chart, thereby ensuring real-time response and timely conflict feedback between the front-end and back-end while reducing data transmission volume and back-end processing overhead. Attached Figure Description

[0022] Various other advantages and benefits will become apparent to those skilled in the art upon reading the following detailed description of preferred embodiments. The accompanying drawings are for illustrative purposes only and are not intended to limit the invention. Furthermore, the same reference numerals denote the same parts throughout the drawings. In the drawings: Figure 1 A flowchart of a real-time front-end and back-end synchronization and conflict alert method for an industrial production scheduling system provided in Embodiment 1 of the present invention; Figure 2 This is a block diagram of the real-time front-end and back-end synchronization and conflict reminder device for the industrial production scheduling system provided in Embodiment 2 of the present invention; Figure 3 This is a hardware structure diagram of a computer device provided in Embodiment 3 of the present invention. Detailed Implementation

[0023] To make the objectives, technical solutions, and advantages of this invention clearer, the invention will be further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the invention. All other embodiments obtained by those skilled in the art based on the embodiments of this invention without inventive effort are within the scope of protection of this invention.

[0024] Example 1 This invention provides a method for real-time front-end and back-end synchronization and conflict alerting in an industrial production scheduling system. This method enables real-time response and timely conflict feedback between the front-end and back-end during Gantt chart editing, while simultaneously ensuring data transmission efficiency and back-end processing efficiency in high-frequency interaction scenarios. Specifically, Figure 1 The flowchart of the real-time front-end and back-end synchronization and conflict alert method of the industrial production scheduling system provided in Embodiment 1 of the present invention is as follows: Figure 1 As shown, the real-time front-end and back-end synchronization and conflict alert method for the industrial production scheduling system provided in this embodiment includes the following steps S101 to S107.

[0025] Step S101: Receive and parse the incremental operation command sent by the front end.

[0026] The front end is used to monitor the user's operation on the corresponding process block of the target process in the Gantt chart and determine the affected process, and generate incremental operation instructions based on the affected process. The incremental operation instructions include operation sequence number, operation type, identifier of the affected process, change attribute of the affected process, and identifier of the work order to which the affected process is located. The change attribute includes the change information of the execution time of the affected process before and after the operation and / or the change information of the execution equipment. The affected process includes the target process and the processes that change in conjunction with the change of the target process.

[0027] In one embodiment, the industrial scheduling system may include a front-end and a back-end. The front-end may be a browser page, a client page, or other human-computer interaction interface with graphical interaction capabilities, while the back-end may be a scheduling server, a business server, or a scheduling processing service related to scheduling. The front-end is used to display a Gantt chart. The time axis in the Gantt chart is used to represent the execution time interval of a process. Each type of equipment may include several specific devices, corresponding to different device names. Each device has a device swimlane, which is used to represent the device executing the process. A process block is used to represent an editable process scheduling object. The target process refers to the process corresponding to the process block that the user is currently directly operating on in the Gantt chart.

[0028] In one embodiment, the user can perform operations such as dragging, stretching, deleting, or locking on the process block corresponding to the target process in the Gantt chart. The drag operation can move the process block to different positions within the same equipment swimlane to change the start and end times of the target process, and can also move the process block to different equipment swimlanes to change the start and / or end times of the target process. The stretch operation can be used to change at least one of the start or end times of the target process. The delete operation removes the process block corresponding to the target process from the equipment swimlane. The lock operation locks the process block of the target process within the current execution time of the current swimlane. After these operations are applied to the target process, the front end, based on preset translation rules or fill-in rules, further determines other processes that will change in tandem with the target process, thereby obtaining the affected processes. That is, the affected processes in this embodiment are not limited to the target process itself, but also include processes whose execution time is adjusted within the same equipment swimlane due to changes in the target process, or whose positions change due to fill-in or insertion caused by the migration of the target process.

[0029] After identifying the affected processes, the front-end encapsulates relevant information to form incremental operation instructions. The operation sequence number identifies the operation instance corresponding to the current operation and can be associated with the version information of the Gantt chart before the operation for subsequent location of the corresponding production scheduling version. The identifier of the affected process uniquely identifies the changed process object, and the identifier of the work order to which the affected process belongs uniquely identifies the work order to which each affected process belongs. The change attributes of the affected process characterize the time and / or equipment status before and after the change. For example, the change attributes may include at least one change in the start time, end time, or executing equipment of an affected process before and after the operation. Optionally, for deletion or locking operations, the specific time value after deletion or locking can be a specific time symbol representing deletion or locking, and the specific equipment value after deletion or locking can also be a specific equipment symbol representing deletion or locking.

[0030] Optionally, the front-end and back-end can transmit incremental operation instructions and subsequent verification results via a long-lived connection. Further, the long-lived connection can be a persistent full-duplex connection based on the WebSocket protocol. Compared to uploading the entire Gantt chart state after each operation, in this embodiment, the front-end only constructs incremental operation instructions around the target process and linked changing processes, thereby avoiding the transmission of unchanged process data. This helps reduce the amount of data transmitted in high-frequency interaction scenarios and improves real-time interaction performance.

[0031] When the backend receives an incremental operation command, it parses it to obtain information about each field carried by the command.

[0032] Step S102: Determine the current production scheduling version corresponding to the incremental operation instruction based on the operation sequence number.

[0033] In this embodiment, the current production schedule version can be understood as the production schedule draft version currently maintained by the backend, or as the version status of the current production schedule simulation plan. That is, before the user edits the process block in the Gantt chart, the backend has already maintained a production schedule version corresponding to the current display status of the frontend. This version is used to represent the latest valid status of the production schedule plan at the current moment.

[0034] In one embodiment, the operation sequence number includes version-related information and an operation number. Upon receiving an incremental operation instruction, the backend can parse the operation sequence number and determine the current production version corresponding to this operation based on the version-related information it carries. That is, the backend does not directly execute subsequent processing on any production version, but first determines the base version targeted by this incremental operation instruction to ensure that the candidate production versions subsequently built are consistent with the production status used by the frontend during the operation. Alternatively, based on the version-related information carried by the incremental operation instruction, the backend's current production version is verified. If the version information indicated by the operation sequence number is inconsistent with the production version currently saved by the backend, the backend can return the version inconsistency result to the frontend to prompt the frontend to reload the latest production version or re-initiate the operation. This approach helps avoid state discrepancies caused by different production versions used by the frontend and backend in scenarios involving multi-person collaboration or continuous high-frequency operations.

[0035] Step S103: Change the current production scheduling version using the change attribute to obtain the candidate production scheduling version.

[0036] In this embodiment, the candidate production scheduling version refers to the transient version obtained by updating the current production scheduling version according to the changes represented by the incremental operation instruction. The candidate production scheduling version is not necessarily the final effective version, but rather the version to be verified when performing local constraint verification later.

[0037] Specifically, the backend can read the affected process identifier and corresponding change attributes in the incremental operation instruction, locate each affected process in the current production scheduling version, and replace, shift or fill in the corresponding process scheduling data in the current production scheduling version based on the change information of execution time and / or change information of execution equipment of each affected process before and after the operation, thereby obtaining a candidate production scheduling version.

[0038] For example, when the execution time of the target process changes and the front end has determined that several processes within the same equipment swimlane need to be postponed according to the preset translation rules, the back end can update the start and end times of the target process and the corresponding linked processes in sequence according to the change attributes. As another example, when the target process is migrated to the new equipment swimlane and the front end has determined that several processes within the original equipment swimlane need to be supplemented according to the preset supplementation rules and that several processes within the new equipment swimlane need to be postponed according to the preset translation rules, the back end can update the linked processes in the original equipment swimlane and the linked processes in the new equipment swimlane simultaneously according to the change attributes, thereby forming a candidate production scheduling version that includes the results of this partial change.

[0039] Optionally, candidate production versions can be temporarily stored in backend memory for subsequent quick verification; or they can be saved as temporary objects in the backend draft library to support rollback after verification failure or official version updates after verification success.

[0040] Step S104: Determine the local verification range in the candidate production scheduling version based on the identifier of the affected process and the identifier of the work order to which the affected process is located.

[0041] In this embodiment, the local validation scope refers to the set of process objects that the backend needs to focus on when performing constraint validation. Compared with performing a global scan on the entire production schedule, this embodiment does not perform constraint validation on all processes, but instead constructs a local validation scope around the affected processes, thereby reducing the set of validation objects and lowering backend processing overhead.

[0042] Specifically, the affected process can be used as the initial process for local verification. Since the affected process already includes the target process and the processes that change in tandem with the target process, the initial process for local verification already covers the core process objects that directly cause changes in the production scheduling results. Furthermore, processes that are adjacent to the affected process in the candidate production scheduling version in terms of scheduling order, as well as processes that have pre- or post-dependencies with the affected process, can be added.

[0043] In this context, adjacent processes in the scheduling sequence can be understood as processes located before or after the affected process within the same execution device's swimlane. By adding such processes, even if they are not identified as linked change processes at the front end, they can still be included in the constraint verification scope at the back end. This means that processes that create new boundary relationships due to this operation are also included in the verification scope. Furthermore, processes that are determined to have pre- or post-dependent relationships with the affected process based on process route data are considered related processes in the process chain. Although their positions may not change, their process sequence may be affected by this operation, and therefore, they also need to be included in the local verification scope.

[0044] By merging and deduplicating the initial and supplementary processes for local verification, the scope of local verification can be obtained. Therefore, the backend can perform constraint verification around the actually affected local areas in the candidate production scheduling version without needing to perform a full scan of the entire production scheduling plan.

[0045] Step S105: Determine the constraint verification rule corresponding to the operation type from the preset constraint verification rule set.

[0046] In this embodiment, the constraint validation rule set is used to store various constraint validation rules that the backend can select and execute. The backend does not necessarily execute all constraint validation rules after every operation, but selects the constraint validation rules that are truly relevant to the current operation based on the operation type, thereby reducing unnecessary constraint validation.

[0047] Specifically, a mapping table between operation types and constraint verification rules can be pre-established. After determining the operation type for this operation, the backend can look up one or more constraint verification rules corresponding to that operation type from the mapping table. For example, when the operation type is a stretching operation, constraint verification rules related to changes in execution time can be prioritized; when the operation type is a dragging operation, constraint verification rules related to changes in the execution device can be prioritized, and rules related to changes in execution time can be further superimposed when there are time changes.

[0048] In one embodiment, the constraint verification rules include hard constraint verification rules and soft constraint verification rules. Hard constraint verification rules may include at least one of the following: equipment capacity matching rules, equipment single-time-period unique task rules, process sequence rules, and equipment calendar rules. Soft constraint verification rules may include at least one of the following: material availability rules, personnel scheduling coverage rules, and delivery date risk rules. Specifically, the equipment capacity matching rule is used to determine whether the executing equipment for the target process or the affected process, after modification, has the capability to complete the corresponding process; the equipment single-time-period unique task rule is used to determine whether the same executing equipment is repeatedly occupied within the same time interval; the process sequence rule is used to determine whether the start time of the subsequent process is earlier than the end time of the preceding process; the equipment calendar rule is used to determine whether the process is scheduled during a period of equipment downtime, maintenance, or unavailability. The material availability rule is used to determine whether the process scheduling time meets the corresponding material availability requirements; the personnel scheduling coverage rule is used to determine whether the process execution time interval falls within the corresponding personnel's scheduling time; and the delivery date risk rule is used to determine whether the work order has a risk of delay after this partial adjustment.

[0049] Optionally, in one implementation, material matching can be treated as a soft constraint by default; when a user pre-sets a matching time for a work order or process and requires the process to be executed after the matching time, the material matching rule can be treated as a hard constraint. This allows for tiered switching of constraint rules under different business configuration conditions.

[0050] Step S106: Execute constraint verification rules for the local verification range to obtain the verification result.

[0051] In this embodiment, after determining the local verification range and constraint verification rules, the backend can execute the constraint verification rules item by item for each process within the local verification range to obtain the verification result corresponding to this operation.

[0052] Specifically, the backend can first obtain constraint verification data corresponding to the local verification scope. Constraint verification data may include at least one of the following: equipment capacity data, equipment calendar data, resource usage data, process route data, material availability data, and personnel scheduling data. Optionally, to improve processing efficiency in high-frequency interaction scenarios, constraint verification data can be provided by a backend memory cache. That is, for data frequently involved in verification, such as equipment capacity, equipment calendar, resource usage, process route, material availability, and personnel scheduling, the backend can pre-load it into memory to reduce the overhead of repeatedly reading from the database for each operation.

[0053] After obtaining constraint verification data, the backend can apply constraint verification rules to each affected process within the local verification scope based on the changes in execution time and / or execution equipment in the candidate production scheduling versions. For example, for processes where the execution equipment changes, equipment capacity matching rules are applied; for processes where the execution time changes, equipment single-period unique task rules, process sequence rules, and equipment calendar rules are applied; and material availability rules, personnel shift coverage rules, and delivery date risk rules are further applied when necessary.

[0054] Based on the execution results of each constraint verification rule, the backend can generate the verification result corresponding to this operation. Specifically, if any hard constraint verification rule is not satisfied, it can be determined that there is a hard constraint conflict in this operation; if all hard constraint verification rules are satisfied and at least one soft constraint verification rule is not satisfied, it can be determined that there is a soft constraint conflict and no hard constraint conflict in this operation; if both hard constraint verification rules and soft constraint verification rules are satisfied, it can be determined that there is no constraint conflict in this operation.

[0055] In one implementation, the verification result may also include conflict cause information, conflict process identifier, conflict work order identifier, and corresponding production scheduling version information, so that the front end can provide more targeted interface feedback.

[0056] Step S107: Send the verification result to the front end so that the front end can issue a conflict alert based on the verification result.

[0057] In this embodiment, after receiving the verification result, the backend can send the verification result to the frontend to drive the frontend to perform corresponding interface feedback and interaction restriction processing. After receiving the verification result, the frontend can mark, prompt, or restrict the corresponding process block according to the conflict type represented by the verification result.

[0058] For example, when the verification result indicates that only hard constraint conflicts exist in this operation, the front end can overlay a hard constraint conflict label on the corresponding process block and restrict the user's operation range through interactive effects. Interactive effects can include disabling drag-and-drop operations, disabling right-click operations, and disabling editing operations at least one of the following: In a more specific approach, when hard constraint conflicts exist, the front end can only retain one-click adjustment operations or intelligent recalculation operations, thereby guiding the user to restore scheduling consistency through automatic adjustment, and no longer allowing further normal editing based on the current conflict state.

[0059] When the verification result indicates that the operation only has soft constraint conflicts and no hard constraint conflicts, the front end can overlay a soft constraint warning label on the corresponding process block and output a non-blocking reminder. At this time, the display state of the corresponding process block after the operation can be maintained, and the production scheduling version information can be updated synchronously. That is, soft constraint conflicts will not prevent the current candidate production scheduling version from being adopted, but will remind the user that there is room for further optimization in the current production scheduling plan.

[0060] When the verification result indicates that there are no constraint conflicts in this operation, the front end can maintain the display state of the corresponding process block after the operation and update the production scheduling version information. Thus, the front end's display state remains consistent with the updated production scheduling version on the back end.

[0061] In one implementation, when the verification result indicates that the operation only has hard constraint conflicts, the backend can keep the current production scheduling version unchanged; when the verification result indicates that the operation only has soft constraint conflicts and no hard constraint conflicts, or when the operation has no constraint conflicts, the backend can update the current production scheduling version using a candidate production scheduling version and send the updated production scheduling version information to the frontend. In this way, the frontend and backend can continuously perform subsequent editing and verification around a unified production scheduling version, thereby maintaining a real-time synchronization state.

[0062] In the real-time front-end and back-end synchronization and conflict alert method of the industrial production scheduling system provided in this embodiment, the front end determines the affected process based on the operation of the process block corresponding to the target process in the Gantt chart, and generates incremental operation instructions based on the affected process; after receiving and parsing the incremental operation instructions, the back end determines the corresponding current production scheduling version according to the operation sequence number, and forms a candidate production scheduling version on the current production scheduling version according to the change attributes of the affected process; subsequently, in the candidate production scheduling version, the local verification range is determined according to the identifier of the affected process and the identifier of the work order to which the affected process is located, the constraint verification rule corresponding to the operation type is determined from the preset constraint verification rule set, the constraint verification is performed on the local verification range to obtain the verification result, and the verification result is sent to the front end for conflict alert. The real-time front-end and back-end synchronization and conflict alert method of the industrial production scheduling system provided in this embodiment organizes the front-end editing operations into incremental operation instructions around the affected process, and performs constraint checks only on the local verification range after the back-end forms candidate production scheduling versions based on the current production scheduling version. This avoids repeatedly transmitting the full production scheduling data and performing full checks on the entire production scheduling plan during the high-frequency editing process of the Gantt chart. As a result, while ensuring real-time response and timely conflict feedback between the front-end and back-end, the amount of data transmission and back-end processing overhead are reduced.

[0063] Optionally, in one embodiment, the front end uses the following steps to determine the processes that change in conjunction with the target process: when the change attribute of the target process only includes execution time change information, the process whose execution time is adjusted according to the preset translation rule is determined based on the process scheduling order in the swimlane of the equipment where the corresponding process block of the target process is located; when the change attribute of the target process includes execution equipment change information, the process whose execution time is adjusted according to the preset replacement rule in the original swimlane of the equipment where the corresponding process block of the target process is located before the operation, due to the migration of the target process, is determined, as well as the process whose execution time is adjusted according to the preset translation rule in the new swimlane of the equipment where the corresponding process block of the target process is located after the operation, due to the insertion of the target process, is determined.

[0064] Specifically, in this embodiment, after the front end detects the user's operation on the process block corresponding to the target process in the Gantt chart, it first determines the change information of the target process, including the changes in the execution time and execution device of the target process before and after the operation. If the target process only experiences a change in execution time, such as when the user performs a drag-and-drop or stretch operation on the process block corresponding to the target process, and the target process is still located in the original device swimlane, the front end can determine the processes with sequential linkage with the target process within that device swimlane according to the current candidate scheduling order. The preset translation rule can be: when the target process moves backward or is lengthened, processes that are scheduled after the target process and have a time connection with it are postponed as a whole; when the target process moves forward or is shortened, processes that were originally located after it are moved forward in sequence or refitted to the new time boundary. Based on this, the front end can determine which processes have their execution time adjusted accordingly due to the change in the target process's execution time and identify these processes as linked change processes.

[0065] When the change information of the target process includes the change information of the executing equipment, it indicates that the target process has migrated from the original equipment swimlane to the new equipment swimlane. In this case, the linked changes in processes are typically distributed in two regions. One type is located in the original equipment swimlane; that is, after the target process moves out, its original position is released, and subsequent processes in the original swimlane can move forward according to a preset replacement rule to fill the time gap left by the target process's migration. The other type is located in the new equipment swimlane; that is, after the target process is inserted into the new equipment swimlane, it will occupy the time interval of subsequent processes in the new position. The corresponding processes in this swimlane can move backward according to a preset translation rule. In one feasible approach, the front end can, based on the process block sequence list corresponding to each equipment swimlane, locate the adjacent processes after the original position of the target process in the original equipment swimlane, and the adjacent processes after the insertion position of the target process in the new equipment swimlane, and sequentially update the start and end times of these processes, thereby obtaining the set of processes linked to the target process migration.

[0066] In practice, the front-end adds the target process and the linked change processes to the set of affected processes, generates corresponding change attributes for each process, and sends incremental operation instructions to the back-end. Since the front-end has already determined the scope of the linked change processes in the graphical context of the equipment swimlane, the back-end does not need to search the entire production scheduling plan again from the full production scheduling data. Instead, it can directly build subsequent versions and perform local constraint verification around these affected processes.

[0067] The real-time front-end and back-end synchronization and conflict alert method of the industrial production scheduling system provided in this embodiment allows the front-end to quickly identify the process objects that are truly affected by the current operation after the Gantt chart is edited. This eliminates the need for the back-end to perform indiscriminate processing on all processes, thereby improving the efficiency of real-time front-end and back-end synchronization and the timeliness of conflict feedback.

[0068] Optionally, in one embodiment, the step of determining the local verification range in the candidate production scheduling version based on the identifier of the affected process and the identifier of the work order to which the affected process is located includes: taking the affected process as the initial process for local verification; supplementing processes that are adjacent to the affected process in the scheduling order in the candidate production scheduling version; supplementing processes that have a pre-dependency or post-dependency relationship with the affected process based on the process route data corresponding to the work order to which the affected process is located; merging the initial process for local verification and the supplemented processes and removing duplicates to obtain the local verification range.

[0069] Specifically, in this embodiment, the local verification scope is not obtained by traversing all processes in the entire candidate production schedule version, but rather by gradually expanding around the affected processes. First, the affected processes passed in by the front end through incremental operation commands are taken as the initial processes for local verification. Since these affected processes already include the target process and the processes that change in conjunction with the target process, they constitute the set of processes directly affected by this editing and are the core part of the local verification scope.

[0070] Building upon this, processes that are adjacent to the affected process in the candidate production schedule version are added. Adjacent in scheduling order refers to processes located before or after the affected process within the same execution device's swimlane. By adding these adjacent processes, processes that haven't changed position but form new time boundary relationships with the affected process are also included in the local verification. For example, after the execution device of the target process changes, the connection, sequence, or resource usage boundaries between the affected process and its adjacent processes may change. Including these changes in the same local verification improves the reliability of the local verification.

[0071] Furthermore, based on the process route data corresponding to the work order containing the affected process, processes with pre- or post-process dependencies on the affected process are added. The process route data characterizes the sequential execution relationships between processes within the work order; for example, a process must start only after the previous process is completed, or a subsequent process must finish later than the current process. By adding these dependent processes, processes whose process dependencies are not in the same equipment swimlane but whose process sequence constraints are affected by this editing operation can be included in the local verification scope, thus improving the reliability of local verification.

[0072] Finally, the initial process of the local verification, adjacent processes in the scheduling sequence, and process-dependent processes are merged and deduplicated to obtain the final local verification scope. The backend can then execute subsequent constraint verification rules only within this local verification scope, without having to perform a full scan of all processes in the entire production scheduling plan.

[0073] The real-time front-end and back-end synchronization and conflict alert method of the industrial scheduling system provided in this embodiment further supplements the scheduling sequence with adjacent processes and process-dependent processes on the basis of the affected processes. The local verification scope is refined into a set of processes that dynamically expand around the area affected by this editing. This not only ensures effective coverage of equipment boundary relationships and process sequence relationships, but also avoids unnecessary calculations caused by global scheduling verification. It achieves the technical effect of balancing verification integrity and back-end processing efficiency in the high-frequency Gantt chart editing process.

[0074] Optionally, in one embodiment, the constraint verification rules include hard constraint verification rules and soft constraint verification rules. The hard constraint verification rules include at least one of equipment capacity matching rules, equipment single-time period unique task rules, process sequence rules, and equipment calendar rules. The soft constraint verification rules include at least one of material completeness rules, personnel scheduling coverage rules, and delivery date risk rules. The step of the front end providing conflict reminders based on the verification results includes: when the verification result indicates that the operation only has hard constraint conflicts, the front end overlays a hard constraint conflict label on the corresponding process block and restricts the user's operation range through interactive effects; when the verification result indicates that the operation only has soft constraint conflicts and no hard constraint conflicts, the front end overlays a soft constraint prompt label on the corresponding process block and outputs a non-blocking reminder; when the verification result indicates that the operation does not have constraint conflicts, the display state of the Gantt chart after the operation is maintained. Wherein, when the verification result indicates that the operation only has soft constraint conflicts and no hard constraint conflicts, or when the operation does not have constraint conflicts, the front end is also used to update the version information of the production scheduling version. The operation sequence number includes version information and operation number.

[0075] Specifically, in this embodiment, constraint verification rules are divided into hard constraint verification rules and soft constraint verification rules to achieve hierarchical processing of different conflict levels. Hard constraint verification rules are used to determine whether the current candidate production schedule version violates the production scheduling boundary that cannot be broken in the actual production process. For example, equipment capacity matching rules can be used to determine whether a new equipment has the processing capacity to complete a certain process after it is switched to a certain process; equipment single-time period unique task rules can be used to determine whether the same equipment is repeatedly scheduled for multiple processes in the same time period; process sequence rules can be used to determine whether the start time of a process is earlier than the end time of the preceding process; equipment calendar rules can be used to determine whether a process is scheduled into a period of equipment downtime, maintenance, or unavailability.

[0076] Soft constraint validation rules are primarily used to determine whether the current candidate production schedule version has risk warnings or room for optimization, rather than necessarily constituting an absolutely unexecutable scheduling error. For example, material availability rules can be used to determine whether the process execution time matches the availability time of the corresponding materials; personnel scheduling coverage rules can be used to determine whether the process scheduling time falls within the available personnel scheduling window; and delivery risk rules can be used to determine whether the work order has a risk of delay after the current adjustment. In one feasible approach, material availability rules can be used as soft constraints by default to provide alerts when there is availability risk but manual intervention is still acceptable; in another scenario, when the user pre-sets the availability time of a certain work order or process, requiring the system to schedule the process after the availability time, material availability rules can also be switched to hard constraints.

[0077] After receiving the verification results, the front-end can provide different levels of feedback in the Gantt chart based on the conflict type. When the verification results indicate only hard constraint conflicts, the front-end can overlay hard constraint conflict labels on the corresponding process block, such as red highlighting, warning icons, or other obvious conflict markers, and restrict the user's operation range through interactive effects. In a more specific implementation, the interactive effects may include disabling at least one of drag-and-drop operations, disabling right-click operations, and disabling editing operations; further optionally, only one-click adjustment operations or intelligent recalculation operations are retained to guide users to restore data consistency through automatic adjustment in the event of a conflict.

[0078] When the verification results indicate only soft constraint conflicts and no hard constraint conflicts, the front-end can overlay soft constraint warning labels (e.g., yellow or orange) on the corresponding process block and output a non-blocking reminder. This non-blocking reminder means the front-end will not force the user to interrupt the current operation or revert to the process block's display state. Instead, it retains the editing results while indicating that the current production schedule has room for further optimization, such as risks related to material availability, scheduling, or delivery time. In this case, the front-end synchronously updates the production schedule version information to ensure that both the front-end and back-end continue editing and verification based on the same updated version.

[0079] When the verification results indicate that there are no constraint conflicts in the operation, the front-end can maintain the display state of the Gantt chart after the operation, that is, maintain the display position and time interval of the target process and related change processes after the operation, while updating the version information of the production scheduling version. The operation sequence number can include version information and operation number, where the version information is used to identify the production scheduling version corresponding to the current operation, and the operation number is used to identify the position of the current operation in the continuous operation sequence. In this way, the front-end can not only provide interface feedback based on the verification results, but also continuously maintain version synchronization with the back-end.

[0080] The real-time front-end and back-end synchronization and conflict alert method for the industrial scheduling system provided in this embodiment divides constraint verification rules into two categories: hard constraints and soft constraints. Different front-end feedback and version synchronization mechanisms are designed for different verification results, enabling conflict alerts to form a hierarchical response mode that matches the actual production feasibility. Specifically, hard constraint conflicts prevent users from continuing to edit in an illegal scheduling state by restricting interactive operations. Soft constraint conflicts balance continuous editing experience with risk warnings through non-blocking alerts. When there are no conflicts, the editing results are maintained and version information is updated synchronously. This ensures the correctness of the scheduling logic while improving the real-time performance, interactivity, and system availability during the Gantt chart editing process.

[0081] Optionally, in one embodiment, after obtaining the verification result, the method further includes: when the verification result indicates that the operation only has hard constraint conflicts, maintaining the current production scheduling version; when the verification result indicates that the operation only has soft constraint conflicts and no hard constraint conflicts, or when the operation has no constraint conflicts, updating the current production scheduling version with a candidate production scheduling version, and sending the version information of the candidate production scheduling version to the front end.

[0082] Specifically, in this embodiment, after the backend completes the local constraint verification and generates the verification result, it further determines whether the candidate production version can be adopted as the new current production version based on the verification result. When the verification result indicates that there is only a hard constraint conflict in this operation, that is, at least one insurmountable production constraint in the candidate production version is not satisfied, the backend keeps the current production version unchanged and does not use the candidate production version to cover the current production version. Since the current production version remains unchanged, after receiving the corresponding verification result, the frontend can maintain the production status corresponding to the original valid version and guide the user to make corrections through hard constraint conflict tags and interaction restrictions.

[0083] When the verification result indicates that the operation only has soft constraint conflicts and no hard constraint conflicts, that is, although the candidate production version has risk warnings or room for optimization, it does not violate the constraints that cannot be broken in actual production, the backend uses the candidate production version to update the current production version and sends the version information of the candidate production version to the frontend so that the frontend can use the version as the base version for subsequent editing and verification.

[0084] When the verification result indicates that there are no constraint conflicts in this operation, meaning that all selected constraint verification rules in the candidate production version are satisfied, the backend also updates the current production version using the candidate production version and sends the updated version information to the frontend. In this way, the frontend and backend can always maintain consistency around the same confirmed production version.

[0085] In one feasible approach, after the candidate production version updates the current production version, the backend can further push the updated version number, version timestamp, or other version identification information to the frontend. When the frontend subsequently generates incremental operation instructions, it can again incorporate this version information into the operation sequence number, forming a continuous version update chain. Thus, multiple consecutive Gantt chart edits can establish a clear version transfer relationship between the frontend and backend, supporting state tracking and consistency maintenance under high-frequency interactions.

[0086] The real-time front-end and back-end synchronization and conflict alert method of the industrial production scheduling system provided in this embodiment can prevent illegal candidate versions from entering the formal production scheduling version when there is a hard constraint conflict. When there is a soft constraint conflict or no conflict, the candidate version can be converted into a new current version and synchronized to the front end in a timely manner. In addition to real-time front-end and back-end synchronization and conflict feedback, the consistency, validity and continuous editability of the production scheduling version status are further guaranteed.

[0087] Optionally, in one embodiment, the step of determining the constraint verification rule corresponding to the operation type in the preset constraint verification rule set includes: pre-establishing a correspondence table between the operation type and the constraint verification rules in the constraint verification rule set; and searching for one or more constraint verification rules corresponding to the operation type from the correspondence table according to the operation type.

[0088] Specifically, in this embodiment, the backend does not uniformly execute all constraint verification rules for every Gantt chart editing operation. Instead, it pre-establishes a correspondence table between operation types and constraint verification rules, and selects the truly relevant subset of rules based on the current operation type during actual verification. This reduces unnecessary constraint verification, lowers backend processing overhead, and improves real-time feedback speed.

[0089] Optionally, during the system initialization or rule configuration phase, a mapping table between operation types and constraint verification rules can be pre-established. This mapping table can represent the constraint verification range and rule set that different editing operations may trigger. For example, for drag-and-drop horizontal operations or stretch operations that mainly cause changes in execution time, they can be preferentially mapped to one or more of the following: equipment single-time period unique task rules, process sequence rules, equipment calendar rules, material availability rules, personnel scheduling coverage rules, and delivery risk rules. For drag-and-drop vertical operations that include information on changes in the executed equipment, they can be preferentially mapped to one or more of the following: equipment capacity matching rules, equipment single-time period unique task rules, equipment calendar rules, and, if necessary, process sequence rules, material availability rules, personnel scheduling coverage rules, and delivery risk rules.

[0090] During actual execution, the backend searches the aforementioned correspondence table for one or more constraint verification rules that match the operation type in the incremental operation instruction. For example, when the operation type is a stretching operation accompanied by equipment switching, the backend can skip the equipment capacity matching rules and only execute the equipment single-period unique task rules, process sequence rules, and equipment calendar rules related to time boundaries. In this way, the backend can selectively filter constraint verification rules based on the operation type, rather than indiscriminately executing all rules.

[0091] The real-time front-end and back-end synchronization and conflict alert method of the industrial production scheduling system provided in this embodiment is adopted. By pre-establishing a correspondence table between operation types and constraint verification rules, and selecting one or more truly relevant constraint verification rules according to the operation type during actual verification, the method avoids the repeated execution of all constraint rules in high-frequency Gantt chart editing scenarios, further reducing unnecessary back-end computation and improving the real-time response efficiency of the front-end and back-end.

[0092] Optionally, in one embodiment, the step of executing constraint verification rules for a local verification range to obtain verification results includes: obtaining constraint verification data corresponding to the local verification range, wherein the constraint verification data includes at least one of equipment capacity data, equipment calendar data, resource occupancy data, process route data, material availability data, and personnel scheduling data; executing constraint verification rules item by item on the affected processes within the local verification range based on the execution time change information and / or execution equipment change information of the affected processes in the candidate production scheduling version; and generating verification results based on the execution results of each constraint verification rule.

[0093] Specifically, in this embodiment, when the backend performs local constraint verification, it first needs to obtain constraint verification data corresponding to the local verification range. This constraint verification data includes basic factual data to support the backend's rule-based judgment. Equipment capacity data characterizes the types of processes, processing capabilities, or resource attributes that each executing device can handle; equipment calendar data characterizes the available time periods, downtime periods, or maintenance periods of each executing device; resource occupancy data characterizes the occupancy status of each executing device in each time interval of the candidate production schedule version or the current production schedule version; process route data characterizes the sequential dependencies between processes within each work order; material availability data characterizes the availability time of materials corresponding to each work order or process; and personnel scheduling data characterizes the availability of personnel corresponding to each process execution time period.

[0094] In one feasible approach, to improve the real-time performance of partial validation, at least a portion of the aforementioned constraint validation data can be pre-cached in backend memory. This way, when the backend executes rules based on the partial validation range, it doesn't need to reread the entire dataset from the database each time; instead, it can directly read the data corresponding to the partial validation range from the cache, supporting fast validation.

[0095] After obtaining the aforementioned constraint verification data, the backend, based on the execution time change information and / or execution equipment change information of the affected processes in the candidate production scheduling version, executes constraint verification rules item by item on the affected processes within the local verification scope. After completing the above item-by-item verification, the verification result of this operation is generated according to the execution result of each constraint verification rule. Optionally, when any hard constraint verification rule is not satisfied, this operation can be determined as having a hard constraint conflict; when all hard constraint verification rules are satisfied, but at least one soft constraint verification rule is not satisfied, this operation can be determined as having a soft constraint conflict and no hard constraint conflict; when all hard constraint verification rules and soft constraint verification rules are satisfied, this operation can be determined as having no constraint conflict.

[0096] The real-time front-end and back-end synchronization and conflict alert method for the industrial production scheduling system provided in this embodiment enables a clear data support chain and result generation chain for the back-end partial verification process. This not only ensures the implementation basis and executability of partial verification but also achieves more efficient and controllable conflict determination and real-time front-end and back-end synchronization in high-frequency editing scenarios.

[0097] Example 2 Corresponding to Embodiment 1 above, Embodiment 2 of the present invention provides a method and apparatus for real-time front-end and back-end synchronization and conflict alerting of an industrial production scheduling system. The technical features and corresponding technical effects can be referred to Embodiment 1 above, and will not be repeated in this embodiment. Figure 2 This is a block diagram of the real-time front-end and back-end synchronization and conflict alert device for the industrial production scheduling system provided in Embodiment 2 of the present invention, as shown below. Figure 2 As shown, the device includes: a receiving and parsing module 201, a first determining module 202, a changing module 203, a second determining module 204, a third determining module 205, an execution module 206, and a sending module 207.

[0098] The receiving and parsing module 201 is used to receive and parse the incremental operation instructions sent by the front end. The front end is used to monitor the user's operation on the corresponding process block of the target process in the Gantt chart and determine the affected process, and to generate the incremental operation instructions based on the affected process. The incremental operation instructions include an operation sequence number, an operation type, an identifier of the affected process, a change attribute of the affected process, and an identifier of the work order to which the affected process belongs. The change attribute includes information on the change in execution time of the affected process before and after the operation and / or information on the change in execution equipment. The affected process includes the target process and processes that change in tandem due to the change in the target process. The first determining module 202 is used to determine the operation instructions based on the specified operations. The sequence number is used to determine the current production scheduling version corresponding to the incremental operation instruction; the change module 203 is used to change the current production scheduling version using the change attribute to obtain a candidate production scheduling version; the second determination module 204 is used to determine the local verification range in the candidate production scheduling version according to the identifier of the affected process and the identifier of the work order to which the affected process is located; the third determination module 205 is used to determine the constraint verification rule corresponding to the operation type in a preset constraint verification rule set; the execution module 206 is used to execute the constraint verification rule for the local verification range to obtain the verification result; the sending module 207 is used to send the verification result to the front end so that the front end can provide a conflict reminder based on the verification result.

[0099] Optionally, in one embodiment, the front end uses the following steps to determine the processes that change in conjunction with the target process change: when the change attribute of the target process only includes execution time change information, the processes whose execution time is adjusted according to the preset translation rules are determined based on the process scheduling order in the swimlane of the equipment where the corresponding process block of the target process is located; when the change attribute of the target process includes execution equipment change information, the processes whose execution time is adjusted according to the preset replacement rules in the original equipment swimlane where the corresponding process block of the target process is located before the operation are determined, and the processes whose execution time is adjusted according to the preset translation rules in the new equipment swimlane where the corresponding process block of the target process is located after the operation are determined, due to the insertion of the target process.

[0100] Optionally, in one embodiment, the second determining module includes: a determining unit, used to take the affected process as the initial process for local verification; a first supplementing unit, used to supplement processes that are adjacent to the affected process in the scheduling order in the candidate production version; a second supplementing unit, used to supplement processes that have a pre-dependency or subsequent dependency relationship with the affected process based on the process route data corresponding to the work order where the affected process is located; and a merging unit, used to merge the initial process for local verification and the supplemented processes and remove duplicates to obtain the local verification range.

[0101] Optionally, in one embodiment, the constraint verification rules include hard constraint verification rules and soft constraint verification rules. The hard constraint verification rules include at least one of equipment capacity matching rules, equipment single-time period unique task rules, process sequence rules, and equipment calendar rules. The soft constraint verification rules include at least one of material completeness rules, personnel scheduling coverage rules, and delivery date risk rules. The step of the front end providing conflict reminders based on the verification results includes: when the verification result indicates that the operation only has hard constraint conflicts, overlaying a hard constraint conflict label on the corresponding process block and restricting the user's operation range through interactive effects; when the verification result indicates that the operation only has soft constraint conflicts and no hard constraint conflicts, overlaying a soft constraint prompt label on the corresponding process block and outputting a non-blocking reminder; when the verification result indicates that the operation does not have constraint conflicts, maintaining the display state of the Gantt chart after the operation; wherein, the front end is also used to update the version information of the production scheduling version when the verification result indicates that the operation only has soft constraint conflicts and no hard constraint conflicts, or when the operation does not have constraint conflicts, and the operation sequence number includes version information and operation number.

[0102] Optionally, in one embodiment, the device further includes: a holding module, configured to hold the current production scheduling version when the verification result characterization operation has only hard constraint conflicts; an updating module, configured to update the current production scheduling version with a candidate production scheduling version when the verification result characterization operation has only soft constraint conflicts and no hard constraint conflicts, or when the operation has no constraint conflicts; and a sending module, configured to send the version information of the candidate production scheduling version to the front end.

[0103] Optionally, in one embodiment, the third determining module includes: an establishing unit, configured to pre-establish a correspondence table between operation types and constraint verification rules in the constraint verification rule set; and a searching unit, configured to search for one or more constraint verification rules corresponding to the operation type from the correspondence table according to the operation type.

[0104] Optionally, in one embodiment, the execution module includes: an acquisition unit, configured to acquire constraint verification data corresponding to the local verification range, wherein the constraint verification data includes at least one of equipment capacity data, equipment calendar data, resource occupancy data, process route data, material availability data, and personnel scheduling data; an execution unit, configured to execute constraint verification rules item by item on the affected processes within the local verification range based on the execution time change information and / or execution equipment change information of the affected processes in the candidate production scheduling version; and a generation unit, configured to generate verification results based on the execution results of each constraint verification rule.

[0105] Example 3 This embodiment also provides a computer device, such as a smartphone, tablet computer, laptop computer, desktop computer, rack server, blade server, tower server, or cabinet server (including a standalone server or a server cluster composed of multiple servers), etc., capable of executing programs. Figure 3 As shown, the computer device 01 in this embodiment includes, but is not limited to, a memory 012 and a processor 011 that are communicatively connected to each other via a system bus. It should be noted that... Figure 3 Only a computer device 01 with component memory 012 and processor 011 is shown; however, it should be understood that it is not required to implement all of the components shown, and more or fewer components may be implemented instead.

[0106] In this embodiment, the memory 012 (i.e., the readable storage medium) includes flash memory, hard disk, multimedia card, card-type memory (e.g., SD or DX memory), random access memory (RAM), static random access memory (SRAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), programmable read-only memory (PROM), magnetic memory, disk, optical disk, etc. In some embodiments, the memory 012 may be an internal storage unit of the computer device 01, such as the hard disk or memory of the computer device 01. In other embodiments, the memory 012 may also be an external storage device of the computer device 01, such as a plug-in hard disk, smart media card (SMC), secure digital (SD) card, flash card, etc., equipped on the computer device 01. Of course, the memory 012 may include both the internal storage unit and the external storage device of the computer device 01. In this embodiment, the memory 012 is typically used to store the operating system and various reference software installed on the computer device 01, such as the program code of the real-time front-end and back-end synchronization and conflict reminder device of the industrial scheduling system in Embodiment 2. In addition, memory 012 can also be used to temporarily store various types of data that have been output or will be output.

[0107] In some embodiments, processor 011 may be a central processing unit (CPU), controller, microcontroller, microprocessor, or other data processing chip. This processor 011 is typically used to control the overall operation of computer device 01. In this embodiment, processor 011 is used to run program code stored in memory 012 or process data, such as a real-time front-end and back-end synchronization and conflict alert method for an industrial production scheduling system.

[0108] Example 4 This embodiment also provides a computer-readable storage medium, such as flash memory, hard disk, multimedia card, card-type memory (e.g., SD or DX memory), random access memory (RAM), static random access memory (SRAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), programmable read-only memory (PROM), magnetic memory, disk, optical disk, server, App reference store, etc., which stores computer programs. When the program is executed by a processor, it implements the corresponding functions. The computer-readable storage medium of this embodiment is used to store a real-time front-end and back-end synchronization and conflict alert device for an industrial production scheduling system. When executed by a processor, it implements the real-time front-end and back-end synchronization and conflict alert method for the industrial production scheduling system of Embodiment 1.

[0109] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element.

[0110] The sequence numbers of the above embodiments of the present invention are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0111] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method.

[0112] The above are merely preferred embodiments of the present invention and do not limit the scope of the patent. Any equivalent structural or procedural transformations made based on the description and drawings of the present invention, or direct or indirect applications in other related technical fields, are similarly included within the scope of patent protection of the present invention.

Claims

1. A method for real-time front-end and back-end synchronization and conflict alerting in an industrial production scheduling system, characterized in that, include: The system receives and parses incremental operation instructions sent by the front end. The front end is used to monitor the user's operation on the corresponding process block of the target process in the Gantt chart and determine the affected process. It also generates the incremental operation instructions based on the affected process. The incremental operation instructions include an operation sequence number, an operation type, an identifier of the affected process, a change attribute of the affected process, and an identifier of the work order to which the affected process is located. The change attribute includes information on the change in execution time of the affected process before and after the operation and / or information on the change in execution equipment. The affected process includes the target process and the processes that change in tandem with the change of the target process. The current production scheduling version corresponding to the incremental operation instruction is determined based on the operation sequence number; The candidate production version is obtained by changing the current production version using the changed attributes; In the candidate production scheduling version, the local verification range is determined based on the identifier of the affected process and the identifier of the work order to which the affected process belongs; Determine the constraint verification rule corresponding to the operation type from the preset constraint verification rule set; The constraint verification rule is executed over the local verification range to obtain the verification result; and The verification result is sent to the front end so that the front end can issue a conflict alert based on the verification result.

2. The method for real-time front-end and back-end synchronization and conflict alerting in an industrial production scheduling system according to claim 1, characterized in that, The front end uses the following steps to determine the processes that change in tandem with the change in the target process: When the change attribute of the target process only includes execution time change information, the process whose execution time is adjusted according to the preset translation rule is determined based on the process scheduling order in the swimlane of the equipment where the corresponding process block of the target process is located; When the change attribute of the target process includes the execution equipment change information, determine the processes in the original equipment swimlane where the corresponding process block of the target process was located before the operation that had their execution time adjusted according to the preset replacement rule due to the migration of the target process, and the processes in the new equipment swimlane where the corresponding process block of the target process was located after the operation that had their execution time adjusted according to the preset translation rule due to the insertion of the target process.

3. The method for real-time front-end and back-end synchronization and conflict alerting in an industrial production scheduling system according to claim 2, characterized in that, The step of determining the local verification range in the candidate production scheduling version based on the identifier of the affected process and the identifier of the work order to which the affected process belongs includes: The affected process is used as the initial process for local verification. Supplement the processes that are adjacent to the affected processes in the scheduling order of the candidate production version; Based on the process route data corresponding to the work order of the affected process, supplement the processes that have a preceding or subsequent dependency relationship with the affected process; The initial and supplementary steps of the local verification are merged and deduplicated to obtain the local verification range.

4. The method for real-time front-end and back-end synchronization and conflict alerting in an industrial production scheduling system according to claim 1, characterized in that, The constraint verification rules include hard constraint verification rules and soft constraint verification rules. The hard constraint verification rules include at least one of the following: equipment capacity matching rules, equipment single-time period unique task rules, process sequence rules, and equipment calendar rules. The soft constraint verification rules include at least one of the following: material availability rules, personnel shift scheduling coverage rules, and delivery date risk rules. The step of the front end providing conflict alerts based on the verification results includes: When the verification result indicates that the operation only has hard constraint conflict, the front end superimposes a hard constraint conflict label on the corresponding process block and restricts the user's operation range through interactive effects. When the verification result indicates that the operation only has soft constraint conflicts and no hard constraint conflicts, the front end overlays a soft constraint prompt label on the corresponding process block and outputs a non-blocking reminder. When the verification result indicates that there are no constraint conflicts in the operation, the display state of the Gantt chart after the operation is maintained. Wherein, when the verification result indicates that the operation only has soft constraint conflicts and no hard constraint conflicts, or when the operation has no constraint conflicts, the front end is also used to update the version information of the production scheduling version, and the operation sequence number includes the version information and the operation number.

5. The method for real-time front-end and back-end synchronization and conflict alerting in an industrial production scheduling system according to claim 4, characterized in that, After obtaining the verification result, the method further includes: When the verification result indicates that the operation only has hard constraint conflicts, the current production scheduling version is maintained. When the verification result indicates that the operation only has soft constraint conflicts and no hard constraint conflicts, or when the operation has no constraint conflicts, the current production scheduling version is updated using the candidate production scheduling version, and the version information of the candidate production scheduling version is sent to the front end.

6. The method for real-time front-end and back-end synchronization and conflict alerting in an industrial production scheduling system according to claim 1, characterized in that, The steps for determining the constraint verification rule corresponding to the operation type from the preset constraint verification rule set include: A table is pre-established to map operation types to constraint verification rules in the constraint verification rule set; Based on the operation type, search the corresponding relationship table for one or more constraint verification rules that correspond to the operation type.

7. The method for real-time front-end and back-end synchronization and conflict alerting in an industrial production scheduling system according to claim 1, the step of executing the constraint verification rule for the local verification range to obtain the verification result includes: Obtain constraint verification data corresponding to the local verification range, wherein the constraint verification data includes at least one of equipment capacity data, equipment calendar data, resource occupancy data, process route data, material availability data, and personnel scheduling data; Based on the execution time change information and / or execution equipment change information of the affected processes in the candidate production scheduling version, the constraint verification rules are executed item by item for the affected processes within the local verification range; The verification result is generated based on the execution result of each of the constraint verification rules.

8. A real-time front-end and back-end synchronization and conflict alert device for an industrial production scheduling system, characterized in that, include: The receiving and parsing module is used to receive and parse the incremental operation instructions sent by the front end. The front end is used to monitor the user's operation on the corresponding process block of the target process in the Gantt chart and determine the affected process, and generate the incremental operation instructions based on the affected process. The incremental operation instructions include the operation sequence number, operation type, the identifier of the affected process, the change attribute of the affected process, and the identifier of the work order to which the affected process is located. The change attribute includes the execution time change information and / or execution equipment change information of the affected process before and after the operation. The affected process includes the target process and the processes that change in conjunction with the change of the target process. The first determining module is used to determine the current production scheduling version corresponding to the incremental operation instruction based on the operation sequence number; The change module is used to modify the current production scheduling version using the change attributes to obtain a candidate production scheduling version; The second determining module is used to determine the local verification range in the candidate production scheduling version based on the identifier of the affected process and the identifier of the work order to which the affected process is located; The third determining module is used to determine the constraint verification rule corresponding to the operation type from the preset constraint verification rule set; The execution module is used to execute the constraint verification rules on the local verification range to obtain the verification result; and The sending module is used to send the verification result to the front end so that the front end can issue a conflict alert based on the verification result.

9. A computer device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 7.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 7.

Images