A method and system for processing changeover scheduling of robot chip heat dissipation modules
By generating a set of changeover jobs and reviewing unexecuted jobs, the problem of inconsistency between actual and planned configurations was resolved, reducing repetitive operations and usage conflicts, and ensuring smooth production.
Patent Information
- Application Number
- CN202611603156.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-10-16
- Publication Date
- 2026-11-17
AI Technical Summary
In scenarios involving partial tooling adjustments, replacement of compatible components, or interruptions due to model changes, the actual configuration of the existing production scheduling scheme may differ from the planned configuration, leading to issues such as repeated disassembly and assembly, omission of necessary operations, tooling conflicts, and mismatches in production start conditions.
By comparing the model tooling requirements of production tasks with the initial configuration of the switchover, a set of changeover jobs is generated, the preconditions of the jobs and the configuration change results are associated, changeover and production are arranged, execution feedback is received and the actual configuration is confirmed, unexecuted changeover jobs are reviewed, unnecessary jobs are canceled, missing jobs are regenerated, and the plan is updated.
This reduces repetitive disassembly and assembly and unnecessary operational omissions, avoids tooling conflicts, and allows for simultaneous correction of production start conditions, ensuring smooth production.
Smart Images

Figure CN123117728A_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of computer-aided production scheduling and manufacturing execution data processing technology, and in particular to a method and system for processing changeover scheduling of robot chip heat dissipation modules. Background Technology
[0002] The production of multiple models of robot chip heat dissipation modules involves the switching of positioning, clamping, and assembly tooling. Existing production scheduling schemes typically arrange the production sequence and start time based on the tooling requirements of the production task, the current tooling at the workstation, changeover time, and available resource periods. The Manufacturing Execution System can also arrange changeover preparation based on differences in process elements, query the preparation completion status, and revise the production plan based on work reports, changeover confirmations, and resource changes.
[0003] In scenarios involving partial tooling adjustments, replacement of compatible components, or interruptions in the changeover process, the actual on-site configuration may differ from the planned configuration. For processing methods that primarily adjust the plan based on preset changeover times or overall completion status, corrections to time and task locations may not synchronously reflect changes in the changeover work content. Some operations originally planned may no longer be necessary, some preconditions for certain operations may no longer be met, and operations required under the actual configuration may not have been included in the original plan.
[0004] Furthermore, planned reservations and actual occupancy have different state boundaries. The cancellation of a changeover operation or the end of a planned usage period does not mean that installed or used tooling has been released; the completion of partial changeover operations does not mean that the target configuration is ready for production. If subsequent arrangements continue to use the original planned configuration and occupancy relationships, it is easy to encounter issues such as repeated disassembly and assembly, omission of necessary operations, tooling usage conflicts, and inconsistencies between production start conditions and the actual on-site conditions. Therefore, it is necessary to address the problems of unexecuted changeover operations, tooling occupancy, and mismatches between production start conditions and actual configurations when the actual configuration differs from the planned configuration. Summary of the Invention
[0005] To address the aforementioned technical problems, this invention provides a method for processing the production scheduling of robot chip heat dissipation modules, comprising: S100: Compare the tooling requirements of the production task with the initial configuration of the switchover, and generate a set of changeover jobs based on the configuration differences; associate the preconditions, configuration change results and dependency configurations of each changeover job. S200. Based on the set of changeover tasks, arrange changeover and production according to task prerequisites, task duration, and available resource periods; use the expected configuration formed by the task configuration change results as the starting configuration for subsequent switchovers to generate production and changeover plans. S300: Receive execution feedback and confirm the actual configuration based on the production and changeover plan; when the actual configuration is inconsistent with the expected configuration at the same switchover location and corresponding execution stage, review the preconditions and configuration change results of the unexecuted changeover operations according to the job dependency configuration, and generate job review results; S400. Based on the job review results, cancel the unexecuted changeover jobs whose actual configurations have met the job configuration change results; for jobs that have not been canceled, retain the jobs whose preconditions have been met or can be formed by still valid preceding jobs, regenerate the jobs according to the configuration differences to replace the original jobs whose preconditions are not met, and supplement the missing jobs; cancel the planned reservation of the canceled jobs, maintain the actual occupation of the unreleased tooling, and sequentially correct the subsequent expected configurations, tooling occupations and production start conditions according to the updated changeover job set, and output the updated production and changeover plan.
[0006] Furthermore, the tooling requirements for the model include tooling application conditions, tooling component requirements, and setting requirements; the switching start configuration includes the tooling instance on the workstation, the installed tooling components, and the current settings; The installed tooling components and current settings are compared with the corresponding tooling component requirements and setting requirements, and the configuration items that do not meet the requirements of the tooling model are recorded to form the configuration differences; The job dependency configuration includes the job prerequisites for the corresponding job change and the configuration items and values involved in the job configuration change results; For switchovers that have already completed configuration confirmation, the actual configuration is used as the starting configuration for the switchover. For switchovers that have not yet been executed, the expected configuration formed by the job configuration change results of the preceding transformation job is used as the starting configuration for the switchover.
[0007] Furthermore, the generation of the transformation job set based on configuration differences includes: If the current configuration item meets the tooling requirements of the corresponding model, it is determined to be used; if the tooling requirements of the model include confirmation requirements, a confirmation job is generated. If the current settings do not meet the setting requirements, and the current tooling component meets the tooling application conditions and the setting requirements are within the allowable adjustment range of the tooling component, an adjustment operation is generated. If the current tooling component does not meet the tooling application conditions, or the setting requirements exceed the allowable adjustment range, match a tooling component that meets the tooling application conditions, and generate a replacement operation and an adjustment operation corresponding to the setting requirements; The adjusted or replaced configuration item values are associated with the corresponding changeover operation configuration change results; if there are no tooling parts that meet the applicable conditions of the tooling, the corresponding production task is recorded as unexecutable and no start time is scheduled for the production task.
[0008] Furthermore, the replacement operation includes disassembly and installation operations; The installation position state formed after disassembly is taken as the prerequisite for the installation operation, the tooling component state after installation is taken as the prerequisite for the adjustment operation, and the adjusted settings are taken as the prerequisite for the confirmation operation. The aforementioned prerequisite relationships for each task are formed based on the prerequisite conditions described above. According to the aforementioned job prerequisite relationship, the job configuration change results of each changeover job are sequentially written into the corresponding configuration items. The configuration items that are not changed by the changeover job retain the configuration item values in the initial switch configuration, thus forming the expected configuration.
[0009] Furthermore, when arranging the changeover and production, the configuration items changed by each changeover operation, the resources occupied, and the configuration items used by the preceding production task are read; If a changeover operation does not change the configuration items used by the preceding production task, and the required resources are within the available resource period, the changeover operation shall be scheduled before the end of the preceding production task. When a changeover operation alters the configuration items used by a preceding production task, or when the required resources are occupied by a preceding production task, the changeover operation should be scheduled after the preceding production task has ended and the required resources have been released. If a changeover operation is completed ahead of schedule but still occupies the tooling, the actual occupancy of the tooling will be retained until the release condition is met.
[0010] Furthermore, the plan reserves corresponding tooling arrangements that have not yet been actually used, and the actual occupation corresponds to tooling that has been installed or used but has not yet been released; When canceling a changeover operation, the planned reservation is canceled based on the tooling instance corresponding to the operation; if the tooling instance is still in the installation or use state, its actual occupation is not canceled. After the tooling instance is disassembled from the workstation and a release confirmation is obtained, the available time period of the resource is updated according to the actual time corresponding to the release confirmation. When a new replacement job uses the same tooling instance, the job will be scheduled within the updated resource availability period.
[0011] Furthermore, the execution feedback includes workstation identification, tooling instance, changeover operation, actual completion time, and configuration confirmation result; According to the workstation identifier, tooling instance, and changeover operation, associate the configuration confirmation result with the corresponding configuration item; write the confirmed configuration item value into the actual configuration; According to the job dependency configuration, for jobs that have never been executed and depend on configuration items that have changed, the corresponding configuration item values in the actual configuration are compared with the job prerequisites and the job configuration change results to form the job review results. If a configuration item does not receive a configuration confirmation result, the configuration item will be recorded as having an unknown status, and the production start conditions that depend on the configuration item will not be recorded as having been met.
[0012] Furthermore, when a changeover interruption or confirmation failure occurs, the execution feedback is used to distinguish between completed and incomplete changeover operations. The actual configuration corresponding to the completed changeover operation is retained. The actual configuration is compared with the tooling requirements of the model, and the remaining changeover operations corresponding to the unmet configuration items are generated. The completed changeover operations are not generated again. For configuration items with unknown status, generate a confirmation job, and after obtaining the configuration confirmation result, generate the remaining replacement jobs corresponding to the configuration item. The remaining changeover operations are included in the updated changeover operation set; if the tooling has not yet met the release conditions, its actual occupancy is maintained.
[0013] Furthermore, the step of regenerating jobs based on configuration differences to replace original jobs where preconditions are not met and to supplement missing jobs includes: Compare the actual configuration with the tooling requirements of the model corresponding to the current switch, and regenerate the model change job for any unmet configuration items; compare the regenerated model change job with the retained unexecuted model change jobs, retain the jobs whose preconditions and configuration change results are consistent, and supplement the jobs that do not exist in the model change job set; According to the production task sequence, the expected configuration formed by the updated changeover operation set is used as the starting configuration for the next changeover, and subsequent unexecuted changeover operations are reviewed in turn. When changes in tooling occupancy involve planned reservations for another workstation using the same tooling instance, the changeover operation and production start time for that workstation will be rescheduled based on the updated resource availability period. When the subsequent changeover operation set, expected configuration, tooling occupancy, and production start conditions are all consistent with the original plan, the corresponding plan update will be stopped.
[0014] This invention also provides a robot chip heat dissipation module changeover scheduling system, comprising: The configuration comparison and job generation module is used to compare the model tooling requirements of production tasks with the initial configuration of the switchover, generate a set of changeover jobs based on the configuration differences, and associate the job preconditions, job configuration change results, and job dependency configurations of each changeover job. The production scheduling module, connected to the configuration comparison and job generation module, is used to arrange changeover and production based on the changeover job set, according to job prerequisites, job duration, and available resource periods; and to use the expected configuration formed by the job configuration change results as the starting configuration for subsequent switchovers to generate production and changeover plans. The configuration feedback and job review module is connected to the production scheduling module. It is used to receive execution feedback and confirm the actual configuration based on the production and changeover plan. When the actual configuration is inconsistent with the expected configuration at the same switchover position and corresponding execution stage, the module reviews the preconditions and job configuration change results of the job that has not been executed according to the job dependency configuration, and generates job review results. The job reconstruction and plan update module, connected to the configuration feedback and job review module and the production scheduling module, is used to cancel unexecuted changeover jobs whose actual configuration has met the job configuration change results based on the job review results; for jobs that are not canceled, jobs whose preconditions have been met or can be formed by still valid preceding jobs are retained, and jobs are regenerated according to configuration differences to replace the original jobs whose preconditions are not met, and missing jobs are supplemented; the planned reservation of canceled jobs is canceled, the actual occupation of unreleased tooling is maintained, the subsequent expected configuration, tooling occupation and production start conditions are corrected in sequence according to the updated changeover job set, the updated production and changeover plan is output, and the updated production and changeover plan is provided to the production scheduling module.
[0015] The key innovations of this invention include: (1) Associate the preconditions and configuration change results of the transformation operation with the operation's dependent configuration; when the actual configuration deviates from the expected configuration, review the non-executed transformation operation according to the association relationship, distinguish the operation whose configuration change result has been met but whose preconditions are not met, cancel unnecessary operations, regenerate the operations whose conditions have failed, and supplement the missing operations.
[0016] (2) The update of the changeover operation content and the update of tooling occupancy adopt different status criteria: the planned reservation corresponding to the canceled operation is canceled along with the operation, and the actual occupancy of the unreleased tooling continues to be maintained; the updated changeover operation set rearranges the resource usage time according to the actual occupancy constraints.
[0017] (3) The configuration change results of the changeover operation are used as the source of the expected configuration for subsequent switching; after the actual configuration feedback causes changes in the operation set, the subsequent expected configuration is corrected in sequence according to the production task order, and the tooling occupation and production start conditions are corrected simultaneously.
[0018] The following are its main beneficial effects: (1) In cases where the original replacement operation is no longer applicable after the actual configuration changes, the preconditions and configuration change results of the operation are checked respectively, so that the operation that has met the target will not be repeated, the operation that failed under the initial condition will be replaced, and the necessary operation missing under the new configuration will be supplemented, thereby reducing repeated disassembly and assembly and the omission of necessary operations.
[0019] (2) Distinguish between planned cancellation and actual occupancy release, so that the cancellation of the plan does not change the status of the physical resources that have not yet been released, and reduce the use conflict caused by the pre-allocation of installed or used tooling to another task.
[0020] (3) Subsequent switching adopts the expected configuration formed by the updated job, and the production start conditions are adjusted synchronously with the changes in job and occupation, reducing the production connection deviation caused by subsequent tasks continuing to reference invalid configurations, old jobs or old resource periods. Attached Figure Description
[0021] Figure 1 A flowchart illustrating a method for scheduling and processing a robot chip heat dissipation module for model changeover, provided in an embodiment of this application; Figure 2 This is a structural block diagram of a robot chip heat dissipation module changeover scheduling system provided in an embodiment of this application. Detailed Implementation
[0022] Example 1: Refer to Figure 1 This is a flowchart illustrating a method for changing the production schedule of a robot chip heat dissipation module according to an embodiment of the present invention. The process may include at least steps S100-S400: S100: Compare the tooling requirements of the production task with the initial configuration of the switchover, and generate a set of changeover jobs based on the configuration differences; associate the preconditions, configuration change results and dependency configurations of each changeover job. S200. Based on the set of changeover tasks, arrange changeover and production according to task prerequisites, task duration, and available resource periods; use the expected configuration formed by the task configuration change results as the starting configuration for subsequent switchovers to generate production and changeover plans. S300: Receive execution feedback and confirm the actual configuration based on the production and changeover plan; when the actual configuration is inconsistent with the expected configuration at the same switchover location and corresponding execution stage, review the preconditions and configuration change results of the unexecuted changeover operations according to the job dependency configuration, and generate job review results; S400. Based on the job review results, cancel the unexecuted changeover jobs whose actual configurations have met the job configuration change results; for jobs that have not been canceled, retain the jobs whose preconditions have been met or can be formed by still valid preceding jobs, regenerate the jobs according to the configuration differences to replace the original jobs whose preconditions are not met, and supplement the missing jobs; cancel the planned reservation of the canceled jobs, maintain the actual occupation of the unreleased tooling, and sequentially correct the subsequent expected configurations, tooling occupations and production start conditions according to the updated changeover job set, and output the updated production and changeover plan.
[0023] S100: Compare the tooling requirements of the production task with the initial configuration of the switchover, and generate a set of changeover jobs based on the configuration differences; associate the preconditions, configuration change results and dependency configurations of each changeover job.
[0024] After a production task enters the execution queue or the workstation completes initial configuration confirmation, the configuration comparison and job generation module reads the tooling requirements of the production task to be connected to the workstation and compares and switches the initial configuration according to the production task sequence. In this embodiment, the calculation system receives production tasks and on-site changeover feedback. The changeover action is performed by on-site operators or changeover equipment; the calculation system does not use the planned job completion time to replace on-site confirmation. Tooling requirements are derived from the corresponding model's process requirements and tooling adaptation configuration, including tooling applicability conditions, tooling component requirements, and setting requirements. The workstation's initial configuration is derived from completed configuration confirmations, including the currently used tooling instance, installed tooling components, and current settings. For subsequent switchover positions that have not yet been reached, the module uses the expected configuration formed by the preceding planned job for comparison and retains the preceding job relationship corresponding to the expected configuration. If the model provided by the production task does not correspond to valid tooling requirements, or if the workstation's initial configuration lacks confirmation content affecting clamping, the task remains pending confirmation, and the missing content is not interpreted as meeting the target requirements.
[0025] Each tooling instance corresponds to a set of actual, occupied tooling. The tooling configuration represents the installation and setup status of the instance at the workstation. Both participate in resource allocation and configuration comparison. In one implementation, the robot chip heat dissipation module is positioned at the assembly station by positioning components and held in the assembly posture by clamping components. Different models have different requirements for positioning components and clamping settings. The module first checks whether the current tooling is suitable for the assembly process of the model, and then compares the installed components and the current settings item by item. The tooling applicability conditions restrict the connection relationship between the components and the workstation and their corresponding operating range. The component requirements specify the component configuration accepted by the target production task, and the setting requirements specify the configuration value or allowable range to be used during clamping. When a setting is within the target allowable range, it is not directly adjusted because it differs from the recommended value; a corresponding configuration difference is formed only when it exceeds the allowable range or the installed component does not belong to the target accepted configuration. When multiple target requirements involve the same configuration item but are incompatible with each other, the module retains the original configuration and stops the job generation for that task, and compares again after the model tooling requirements are corrected.
[0026] For configuration items that already meet the tooling requirements of the model, the module will retain them, and this retention itself will not involve disassembly, installation, or adjustment operations. If the tooling requirements also stipulate pre-work confirmation, the confirmation operation will be retained; confirmation cannot be omitted simply because the components are identical. When there are setting differences, first check if the current component meets the tooling applicability conditions, then check if the target setting falls within the component's allowable adjustment range; if both conditions are met, an adjustment operation will be formed based on the settings to be changed. If a component is inapplicable or the target setting exceeds the allowable adjustment range, the module will match a replacement component from the compatible configurations and verify the installation conditions and allowable setting range of the replacement component. If the setting range of the replacement component still cannot cover the target requirements, the component will not be included in the valid replacement object. Production tasks without a valid replacement object are recorded as unexecutable and will not be included in subsequent start time scheduling. If a replacement object is compatible but currently occupied, the corresponding replacement operation will be retained and scheduled by S200 based on resource availability time periods; temporary unavailability and tooling inapplicability should not be confused as the same exception.
[0027] The relationships between disassembly, installation, adjustment, and confirmation are formed based on configuration changes, not just by job name. For switching requiring replacement of positioning components, the disassembly operation is conditional upon the existence of a specified old component in the previous configuration, and the configuration change result is that the old component is removed from the installation position. The installation operation is conditional upon the installation position status and the availability of the target component established by the previous operation, and the configuration change result is that the target component is installed in place. The component status after installation serves as a prerequisite for the adjustment operation, and the adjusted settings serve as a prerequisite for the confirmation operation. The module uses these conditions to associate the prerequisite relationships of the operations, so that subsequent operations reference the actual configuration changes generated in the preceding sequence. The completion of disassembly only indicates that the old component has been removed from the installation position, not that the component has been returned or released; the completion of installation does not directly indicate that all tooling requirements for the model have been confirmed. The former is updated by resource release feedback, and the latter is continued by the corresponding adjustment and confirmation operations, which respectively enter the subsequent occupancy arrangement and start-up inspection.
[0028] Each changeover operation, in addition to its corresponding production task, is associated with its tooling, preconditions, configuration change results, and dependency configurations. The dependency configuration retains the preconditions and change results of the operation, along with their values, enabling subsequent feedback to pinpoint operations affected by configuration changes. For example, disassembling an old component at a dependent installation location, installing a dependent installation location with its status and target component, and adjusting an already installed component and its current settings. The module stores these configuration relationships separately, not just a single overall changeover completion state. Preconditions describe the states that should exist before execution, while configuration change results describe the states that should be formed after execution. When a precondition is met after a preceding operation, the module establishes a sequential relationship, rather than treating it as a currently unexecutable exception. For configuration items that haven't been changed by any operation, the values in the initial switch configuration are retained; subsequent expected configurations consist of both changed and retained items.
[0029] In one continuous implementation, the same assembly station sequentially executes the robot chip heat dissipation module tasks for models 1, 2, and 3. After model 1 is completed, positioning component 1 is retained; model 2 accepts positioning component 2 or positioning component 3; and model 3 requires positioning component 3. Each model also has corresponding clamping settings. The initial plan selects positioning component 2 to execute model 2. Therefore, switching from model 1 to model 2 involves disassembling positioning component 1, installing positioning component 2, adjusting clamping, and confirming the process. Switching from model 2 to model 3 involves disassembling positioning component 2, installing positioning component 3, and adjusting and confirming the corresponding settings for model 3. Here, the model and component names refer to the corresponding objects in the embodiment and do not imply unconditional compatibility between different components. The compatibility relationship is given by the model tooling requirements. If the station has already actually installed positioning component 2, the model 2 changeover operation will no longer include repeated installation; only unmet setting adjustments and necessary confirmations are retained. The resulting changeover operation set is handed over to the production scheduling module, which arranges the execution time according to the prerequisite relationships, functional resources, and configuration change results. The operation dependency configuration is retained with the plan for S300 to review after receiving actual feedback.
[0030] S200. Based on the set of changeover tasks, arrange changeover and production according to task prerequisites, task duration, and available resource periods; use the expected configuration formed by the task configuration change results as the starting configuration for subsequent switching to generate production and changeover plans.
[0031] After receiving the changeover job set generated by S100, the production scheduling module first checks whether the preconditions for each job have actual confirmation basis or are provided by the scheduled preceding jobs, and then arranges the job execution interval. The job duration adopts the standard job duration of the corresponding operation or the confirmed execution record, and the production duration adopts the process time corresponding to the production task; both are included in the calculation of changeover completion time and production completion time, respectively. When a job lacks duration, the module maintains its preconditions and configuration results, but does not schedule the job with zero duration in the plan, and arranges it after the available duration is supplemented. When the workstation and tooling have different available time periods, the module uses the interval allowed by both, and not only checks whether the workstation is idle. The completion of preceding production, the completion of preceding jobs, and resource release constitute different constraints for the start of the job. The module checks these constraints separately and does not use a single total changeover duration to replace the specific job arrangement.
[0032] Specifically, the production scheduling module starts scheduling changeover operations when the preconditions are met or can be provided by preceding operations, and reads the workstations, tooling instances, and execution resources required for the operation. The candidate start time is taken from the start of the resource availability period after the preconditions are met, and then the candidate completion time is calculated based on the operation's duration. If a candidate interval intersects with existing occupancy, or if the resource availability interval is insufficient to cover the operation, it moves to the next available interval, and the timing of subsequent operations dependent on this operation is simultaneously corrected. In this implementation, disassembly, installation, and adjustment operations are arranged according to complete operation intervals, without arbitrarily splitting them when there is a lack of actual operational basis; for operations with segmented execution rules, they are arranged according to their segmented precondition relationships. When an installed tooling is continued to be used by the current workstation, its actual occupancy is associated with the production task of this workstation and does not constitute a conflict for continued use by this workstation; when another workstation requests to use the same instance, this actual occupancy constitutes an unallocable condition. This distinguishes between the continuation of the same occupancy relationship and contention for the same resource by multiple incompatible tasks.
[0033] Whether a changeover operation can be executed ahead of schedule depends on the relationship between the configuration items changed in the changeover operation and the configuration required by the preceding production. The module reads the positioning components, clamping settings, and corresponding tooling used by the preceding production task, and then compares them with the changeover operation's changed objects and occupied resources. Operations that do not change the preceding production configuration and whose required resources have available intervals can be scheduled before the preceding production ends; operations that change the configuration currently being used in the preceding production, or occupy resources used in the preceding production, are scheduled after the preceding production ends and the resources are released. For cases where tooling components have a cooperative relationship, the changed object also includes the cooperative configuration directly affected by the action, and cannot be allowed to be executed ahead of schedule simply because the operation name does not mention the preceding used components. In one implementation, a spare positioning component completes an adaptation check in an independent preparation position, does not change the online positioning state, and the check resources are not used by the preceding production, so it is scheduled ahead of schedule; online clamping setting adjustments will change the clamping state of the preceding production and must be performed after the preceding production ends. Operations scheduled ahead of schedule must still meet their own prerequisites and cannot skip necessary preceding operations due to resource availability.
[0034] The completion time of the changeover operation and the release time of the tooling are respectively included in the planning. When a spare tooling is inspected and remains in the preparation position and is retained by a subsequent task, the preparation operation has ended, but the tooling does not re-enter the allocable state. When an old tooling has been disassembled from the workstation but has not yet received release confirmation, the installation position has become vacant, and the actual occupancy of the old tooling instance remains; only when both the disassembly state and release confirmation are established are the resource availability time period updated according to the time corresponding to the release confirmation. For allocations that have not yet actually occurred, the module sets a planned reservation, the start and end intervals of which reflect the resource usage arrangements in the plan; after the tooling begins actual installation or use, the corresponding relationship is converted to actual occupancy. In the case of actual occupancy, the planned end time is only used as an estimated value, and the actual release is confirmed by execution feedback. When another workstation needs the same tooling instance, the scheduling module arranges according to the above occupancy boundaries, and does not directly allocate the instance because the preparation operation has been completed or the original production task has ended.
[0035] After each changeover operation is scheduled, the module applies the configuration changes to the initial switchover configuration item by item according to the operation's prerequisite relationship. Disassembly operations change the state of components in the installation location, installation operations change already installed components, and adjustment operations change corresponding settings. The module confirms whether the configuration changes have passed the specified confirmation; configuration items that have not changed are retained. This process forms a projected configuration, but it is only used within the planned scope and does not cover the actual configuration on site. The projected configuration of the current task becomes the starting configuration for the next switchover, and the next task's operation is further estimated based on this configuration. Therefore, configuration changes between multiple tasks are passed along the production sequence. In this implementation, the production process does not automatically change the tooling configuration used for subsequent comparisons; this configuration is retained after production ends. If the production process does require changing a setting, the task process configuration specifies the state to be retained at the end, and the starting configuration for the next switchover is corrected accordingly. Independently setting unconnected projected states between different tasks is prohibited.
[0036] Production starts after the completion of preceding production and necessary changeover operations, and within the permitted usage range of equipment and required tooling. The module associates the completion of preceding processes, confirmation of target configuration completion, and resource occupancy relationships in the production start conditions, saving the planned start time and actual start conditions separately. If the planned start time arrives but the target configuration has not yet been confirmed, the production task does not enter the ready state. For configuration changes other than those requiring confirmation, the module also checks whether they render the original confirmation inapplicable; if the installation component or clamping setting is changed again after confirmation, it needs to be reconfirmed according to the model requirements. In the overall implementation, after the installation, clamping adjustment, and confirmation of positioning component 2 for model 2 are completed, model 2 has a planned start time; positioning component 2 is expected to be retained after model 2 ends, therefore the changeover operation for model 3 depends on this expected configuration. Production and changeover plans associate these operations, expected configurations, tooling occupancy, and production start conditions. The execution end calls these operations according to their preceding relationships, and the configuration feedback and operation verification modules check subsequent feedback accordingly.
[0037] S300: Receive execution feedback and confirm the actual configuration based on the production and changeover plan; when the actual configuration is inconsistent with the expected configuration at the same switchover location and corresponding execution stage, review the preconditions and configuration change results of the unexecuted changeover operation according to the operation dependency configuration, and generate the operation review result.
[0038] Upon receiving execution feedback from a field changeover operation, the configuration feedback and job verification module reads the production and changeover plan generated by S200. It first verifies the workstation, tooling instance, and changeover operation to which the feedback belongs, and then confirms its corresponding configuration item. Execution feedback includes the actual completion time and configuration confirmation result. The feedback source can be a field operation terminal or a changeover device with a status return interface. In the operation terminal implementation, the operator confirms the actual installed components and current settings according to the specific operation, without replacing each configuration result with an overall changeover completion button. In the device return implementation, the component arrival or setting completion result is associated with the corresponding operation. When the feedback object is inconsistent with the planned workstation or tooling instance, the feedback does not directly overwrite the current actual configuration; instead, the feedback content is retained and an object verification is initiated. When the feedback belongs to the same completed operation and the content is repeated, the configuration change result is not applied repeatedly. When the feedback time is earlier than the most recent confirmed change for that configuration item, the old result is not directly overwritten with the current status; instead, it is verified whether a new configuration operation occurred during the verification period.
[0039] The actual configuration is updated based on the confirmed results, not supplemented according to the planned completion time. When component installation is confirmed but clamping adjustment is not, the actual configuration retains the installation result, and clamping settings are still expressed as known values or unknown states. The overall changeover should not be directly marked as completed. When the disassembly result is clear, the installation position is recorded as the component has been removed; if the feedback only indicates that the disassembly operation was interrupted without specifying whether the component has been removed, the installation position remains pending confirmation. If there are conflicting feedbacks for a configuration item, and their sequential states cannot be identified based on the corresponding operation relationships, the module records the item as an unknown state and retains the confirmation operation. Production start conditions dependent on this item are not recorded as met. In this way, the actual configuration can simultaneously contain confirmed installation status, unconfirmed settings, and unreleased resources status, with each item continuing to participate in different operations and resource judgments, without being merged into a single ambiguous changeover anomaly state.
[0040] The comparison between actual and expected configurations is conducted at the same workstation, the same switchover location, and the same execution phase. If a planned task has not yet been executed, and its target result has not yet been achieved on-site, this is considered normal progress and is not directly considered a configuration deviation. Only when the completed feedback configuration result differs from the expected result for that phase, or when the execution end confirms the use of different compatible components, does it constitute a configuration change requiring review. The module searches for unexecuted tasks referencing changed configuration items based on the task's dependent configuration. It first checks the replacement tasks immediately following the current actual state, and subsequent switchover locations are reviewed after the updated expected configuration is obtained from S400. The current actual installation state cannot be directly compared with the target configuration of all future tasks; otherwise, normal future replacements may be misjudged as already met or with invalid prerequisites. When the actual completion time changes but the configuration result is consistent with the expectation, the task content is maintained, and the schedule is adjusted according to resources and prerequisite relationships. Only when configuration deviations affect task conditions or target results are the task review results required for content reconstruction generated.
[0041] For unexecuted replacement jobs, the module first compares the job configuration change result with the actual configuration. If the actual configuration has met the component or setting requirements of the job, the job is classified as having met the configuration result; if the actual configuration has not yet met the change result, the job's preconditions are checked. If the preconditions are met, or can be formed as planned by a still valid preceding job, the job content is retained; if the original job's required starting component does not exist, the installation conditions have changed, or the preceding configuration change result is no longer formed, the job is classified as needing to be regenerated. Jobs that have not yet reached their execution time due to unreleased resources are not directly classified as having failed configuration conditions, but are rescheduled by the resource time slot. Confirmation jobs also need to verify whether the targeted components and settings are consistent with the current actual configuration; confirmations under the old configuration cannot automatically overwrite the new configuration. The job review result is used to distinguish between "configuration result met," "preconditions still met," "preconditions not met," and "status unknown," and then the S400 performs the corresponding update.
[0042] In the implementation process, it was originally planned that Model 2 would use positioning component 2, but the execution end actually selected positioning component 3, which is accepted by Model 2, and returned a confirmation result that positioning component 3 had been installed. The module first checks whether the replacement component is an acceptable configuration according to the tooling requirements of Model 2, and then checks the clamping settings and confirmation results of Model 2. It cannot assume that Model 2 is fully ready simply because component 3 has been installed. Model 3, which follows Model 2, was originally planned to include the disassembly of positioning component 2 and the installation of positioning component 3. The former depends on component 2 at the installation position, and the latter is considered a change result based on the installation of component 3. The actual installed component has become component 3, the starting conditions of the original disassembly operation are no longer met, and the target state of the original installation operation has been achieved; if the clamping settings required for Model 3 have not yet been formed, their adjustment and confirmation are still necessary. The module retains these different judgments and does not replace the review of the operation content with a uniform time deviation. The attribution of tooling instances is also checked with actual feedback, and the originally planned reserved component 2 and the already used component 3 are respectively sent to S400 to update resource relationships.
[0043] When a changeover is interrupted or confirmation fails, the module distinguishes between completed and incomplete configuration changes based on the actual feedback from each task. In the intermediate state where the old component has been confirmed to have been disassembled but the new component has not yet been installed, the old component is no longer considered part of the installation location configuration, and the new component is not considered to be installed successfully; the workstation cannot continue to use the complete old configuration or the expected new configuration as the actual state. When overall confirmation fails but installation and adjustment have been confirmed separately, the implemented configuration values are retained, and checks or remaining tasks are arranged according to the configuration items involved in the failure; all completed actions are not restored to unexecuted states. For items with unknown states, the confirmation task first ascertains the on-site state, obtains the results, and then compares the model tooling requirements; before obtaining confirmation, it is not presumed that disassembly, installation, or setting changes have occurred. The task review results carry these known configurations and unconfirmed relationships, and S400 retains the actual results, reconstructs unexecuted tasks, and maintains the occupancy of unreleased tooling.
[0044] S400. Based on the job review results, cancel the unexecuted changeover jobs whose actual configurations have met the job configuration change results; for jobs that have not been canceled, retain the jobs whose preconditions have been met or can be formed by still valid preceding jobs, regenerate the jobs according to the configuration differences to replace the original jobs whose preconditions are not met, and supplement the missing jobs; cancel the planned reservation of the canceled jobs, maintain the actual occupation of the unreleased tooling, and sequentially correct the subsequent expected configurations, tooling occupations and production start conditions according to the updated changeover job set, and output the updated production and changeover plan.
[0045] After receiving the job review results from S300, the job reconstruction and plan update module updates the plan starting from the actual confirmed configuration at the feedback switchover location. First, it cancels unexecuted jobs whose configuration change results have already been met by the actual configuration. Confirmation results must correspond to the same tooling, the same configuration, and the current model requirements; inapplicable historical confirmations cannot be used to cancel existing confirmed jobs. For jobs that are not canceled, if the configuration prerequisites are met, or if they are still formed by valid preceding jobs, their job content is retained; if resource time periods change, only the execution interval is rescheduled. Jobs whose prerequisite configurations have expired are not directly extended in duration; instead, the operation is re-determined based on the difference between the actual configuration and the current model tooling requirements. Completed jobs are not included in the plan cancellation scope; their resulting actual configurations are retained. Jobs in execution are not directly deleted as unexecuted jobs; instead, after returning to a completed or interrupted status, the subsequent parts are reconstructed based on the already formed configuration results.
[0046] During regeneration, the module uses S100's configuration comparison and job generation rules to reselect, adjust, or replace paths for currently unmet configuration items, and checks the installation conditions and setting range of the new job. The regenerated job is compared with the retained unexecuted jobs, including the tooling instance, configuration items, job preconditions, and job configuration change results; if these are consistent, the original valid job is retained, and no new identical operation is added. If the new actual component can meet the requirements through adjustment, the original replacement path is converted into an adjustment path; if the new actual component is not applicable, the replacement component is rematched, and the corresponding disassembly, target component installation, and necessary adjustments for that actual component are generated. If a new difference does not have a corresponding valid job rule, the task's commencement is stopped, and the confirmed on-site configuration is retained. Original jobs with invalid preconditions, even if not listed as having met the target, should be removed from the valid job set and replaced by regenerated jobs; original jobs and new jobs should not be dispatched simultaneously.
[0047] Resource updates resulting from job cancellation first distinguish between planned reservations and actual occupancy. Reservations for tooling not yet used are cancelled upon job cancellation, while tooling already installed or used for preparation remains occupied until release confirmation is obtained. In the continuous implementation, after the positioning component 3 is actually used for Model 2, the planned re-installation job for Model 3 is cancelled, and the corresponding unexecuted preparation reservation is also cancelled; the positioning component 3 remains installed at the current workstation and cannot be allocated to another workstation due to the cancellation of the installation job. If the planned positioning component 2 is not actually used, its reservation can be cancelled; if the positioning component 2 has been moved to the preparation position and is actually occupied by the task, it remains occupied until the release result is returned and the available time period is updated. Actual old components involved in the replaced disassembly job are also handled according to the on-site release status. When a new job requests the same instance, the module first checks the updated available range and does not use the planned reservation cancellation time as the physical release time.
[0048] Remaining replacement tasks will continue to be scheduled according to the actual configuration, and completed changes will not be re-executed due to the failure of the overall replacement plan. In interruption scenarios where old components have been disassembled but new components have not yet been installed, the reconstruction starting point is the vacant installation location. The remaining set includes the installation of the new component, target setting adjustments, and confirmations, but no longer includes the disassembly of the old component that has already been completed. If the new component is no longer available during the interruption, a compatible and available instance will be re-matched, and the remaining tasks will be generated according to the allowed setting range of that instance. If no compatible instance exists, the task will remain in an unschedulable state and cannot continue to start with the old component configuration. When the installation location status is unknown, a confirmation task will be scheduled first. After it is confirmed that there is actually an old component, a vacancy, or a new component, the corresponding remaining path will be generated. Tooling occupancy that has been confirmed but not yet released will always be retained. This process updates the actual configuration, remaining tasks, and occupancy boundaries separately, and does not simply interpret a replacement interruption as requiring all actions to be restarted.
[0049] Once the set of valid jobs for the current switchover is formed, the module rearranges the job time slots according to the job prerequisites and applies the configuration change results item by item to obtain the expected configuration after the switchover is completed. In the overall implementation, the actual completed configuration of Model 2 retains the positioning component 3. Model 3 no longer requires the disassembly of the positioning component 2 and the installation of the positioning component 3, but the clamping settings still need to be adjusted and confirmed according to the requirements of Model 3. The new expected configuration of Model 3 is composed of the already installed component 3 and the newly arranged adjustment results, rather than directly copying all the settings of Model 2. Subsequently, the expected configuration after the completion of Model 3 is used as the starting point for the next switchover, and the tooling requirements of the next production task are compared. The actual configuration is only used for the current update starting point, and the expected configuration is still estimated item by item for future states that have not yet occurred; this sequential transmission ensures that configuration changes of intermediate tasks are not skipped. For confirmation conditions that have not been executed, their expected completion relationships are retained, and the actual fulfillment status is still given by subsequent feedback.
[0050] Changes in tooling occupancy may also affect the production and changeover plans of another workstation. The module reads the shared usage relationship by tooling instance and checks whether the changed occupancy range conflicts with the planned reservation of another workstation. If a conflict exists, the preparation, installation, and production start times of that workstation are adjusted according to the new resource availability period. If another workstation has already actually occupied the instance, this fact serves as a constraint on the current arrangement and cannot be overridden by canceling the reservation of another workstation. When multiple workstations request the same instance, in one implementation, tasks that have already started occupying the instance maintain their usage relationship, while unexecuted tasks select available ranges according to the existing planned sequence. If an adapter is unavailable but a compatible replacement instance exists, the work path for that workstation can be regenerated according to the corresponding model requirements. Replacement instances must have their configurations rechecked and ranges adjusted, not only changing the resource identifier. Time changes may continue to affect subsequent shared occupancy. The module repeatedly checks along the instance usage relationship until no more range conflicts caused by this change occur, or outputs the tasks that cannot be scheduled and the reasons for their occupancy.
[0051] After each rebuild, production start conditions are rechecked based on valid changeover jobs and occupancy relationships. When necessary adjustments, installations, or confirmation jobs change, the old jobs referenced in the original start conditions are replaced with the new valid jobs; confirmations that have been completed and are still applicable to the current configuration are retained, while confirmations that lose their applicability due to further configuration changes are rescheduled. If preceding production has not ended, or the required tooling has not been released, the production task is not recorded as ready, even if the configuration target has been met. The module compares the updated job set, expected configuration, tooling occupancy, and production start conditions with the original plan item by item. If all four remain consistent, the corresponding configuration propagation stops at subsequent locations. If the configuration has been restored to consistency but the occupancy range has changed, the resource and time impacts continue to be processed; if shared tooling is no longer conflicting but the subsequent configuration of this workstation has changed, rebuilding continues along the production task sequence. The cessation criteria are determined by the actual unchanged processing objects, and the ongoing impact is not truncated by a fixed number of tasks.
[0052] The updated production and changeover plans are invoked by the execution end. Changeover operations in the plan retain their corresponding production tasks, workstations, tooling instances, prerequisites, and execution periods. Production tasks retain their updated start conditions. Before invoking a job that has not yet started, the execution end checks whether the job still belongs to the current valid set; old jobs that have been canceled or replaced are not reissued. During the plan update, affected but not yet started jobs are temporarily suspended, while already executed actions continue to return actual results. After the update is completed, invocation is resumed according to the new prerequisites to avoid old and new disassembly / assembly tasks occurring simultaneously at the same installation location. Occupancy without release confirmation continues to be retained with the new plan; resource availability periods are adjusted when subsequent release feedback arrives. After the plan enters execution, new job completion, configuration confirmation, and interruption results re-enter S300. Actual configuration and expected configuration continue to be checked at the corresponding stages, and subsequent job content and production connections are updated according to the new field status.
[0053] Example 2: Figure 2 This diagram illustrates a structural block diagram of a robot chip heat dissipation module changeover scheduling system according to an embodiment of the present invention. Figure 2 As shown, the structure may include: The configuration comparison and job generation module 01 compares the model tooling requirements of production tasks with the initial switchover configuration, generating a set of switchover jobs based on configuration differences. It associates the preconditions, configuration change results, and dependent configurations of each switchover job. After a production task enters the execution queue or the initial workstation configuration is confirmed, this module reads the applicable conditions, tooling component requirements, and setting requirements for the corresponding model tooling. Already executed switchover positions use the actual confirmed configuration, while unexecuted switchover positions use the projected configuration from the preceding plan. The two types of configurations retain their respective sources and do not overwrite each other. The module compares installed components with current settings item by item. If the configuration meets the model tooling requirements, it is determined to continue using it. If there are setting differences and the target setting is within the allowable adjustment range of the current component, an adjustment job is generated. If the current component is not applicable or the target setting exceeds the allowable adjustment range, a suitable replacement component is matched, generating disassembly, installation, and necessary adjustment jobs. The installation position status, component installation status, and adjusted settings constitute the preconditions for subsequent jobs. Changes in configuration items after job completion serve as the job configuration change result. The job dependency configuration retains the configuration items and values related to these conditions and results, allowing for the location of affected jobs upon receiving actual feedback. When the configuration specified by the model tooling requirements is confirmed, the corresponding confirmed job is retained in the changeover job set; if there is a lack of valid tooling requirements or no compatible parts, the corresponding production task remains in a pending confirmation or unexecutable state and is not scheduled at the start time. The resulting changeover job set provides the scheduling module with job prerequisites and the basis for configuration changes, and configuration items not changed by the jobs are retained along with the initial switchover configuration.
[0054] The production scheduling module 02, connected to the configuration comparison and job generation module, is used to arrange changeover and production based on the changeover job set, according to job prerequisites, job duration, and resource availability time periods. It uses the projected configuration resulting from the job configuration change as the starting configuration for subsequent switchovers, generating production and changeover plans. After the configuration comparison and job generation module provides the job set, this module first checks whether the prerequisites for each job are met, or whether they are provided by valid preceding jobs, and then selects a resource availability interval based on the job duration. If a candidate interval conflicts with an existing occupied interval, it moves to the next available interval and corrects the timing of subsequent jobs dependent on that job. For preparatory jobs that do not change the preceding production configuration and have available resources, they are scheduled before the preceding production ends; jobs involving online positioning components, clamping settings, or preceding occupied resources are scheduled after the preceding process ends and the corresponding resources are released. Tooling that has not yet been actually used is reserved in the plan; tooling that has been installed or actually used remains actually occupied; the completion of a preparatory job does not directly indicate that the tooling has been released. The module applies configuration changes item by item to the switchover start configuration according to the job prerequisites, forming the expected configuration after the current task is completed, and then passes this configuration to the next switchover. Production start conditions are linked to the completion of preceding production, confirmation of necessary changeover operations, and tooling usage. If the planned start time arrives but the configuration has not yet been confirmed, the task does not enter the actual ready state. Production and changeover plans are provided to the configuration feedback and job verification module, where the association between jobs, workstations, tooling instances, and expected configurations serves as the basis for feedback verification. Upon receiving the updated plan from the job reconstruction and plan update module, the updated valid jobs and their occupancy relationships are used for scheduling, and the original planned intervals of canceled jobs are no longer used.
[0055] The configuration feedback and job verification module 03, connected to the production scheduling module, is used to receive execution feedback and confirm the actual configuration based on the production and changeover plan. When the actual configuration is inconsistent with the expected configuration at the same switchover location and corresponding execution stage, the module verifies the preconditions and configuration changes of the unexecuted changeover jobs according to the job-dependent configuration, and generates a job verification result. Execution feedback is returned from the field operation terminal or changeover equipment. This module first checks the feedback object based on the workstation identifier, tooling instance, and changeover job, and then associates the configuration confirmation result with the corresponding configuration item. When the feedback only confirms component installation but not clamping settings, the actual configuration only updates the confirmed installation status and does not consider the overall changeover as complete. When the feedback object does not match, the configuration results conflict, or there is a lack of confirmation basis, the corresponding configuration item remains pending confirmation or in an unknown state, and the production start condition dependent on this configuration item is not recorded as met. When comparing the actual configuration and the expected configuration at the same switchover location and corresponding execution stage, the fact that the preliminary work that has not yet been executed has not reached the target state is considered normal progress and is not directly considered a configuration failure. Upon encountering a valid configuration deviation, the module reads the affected unexecuted jobs according to the job dependency configuration. It first checks whether the configuration change result has been satisfied by the actual configuration, and then checks whether the original preconditions still hold or are still provided by valid preceding jobs. Jobs with existing target results are cancelled; jobs with changed initial configurations and no longer meeting their original preconditions are regenerated; jobs whose conditions and results are unaffected are retained. When the actual completion time changes while the configuration remains the same, the job content is not changed; only the time change is handled by the plan update. The job review results, along with the actual confirmed configuration, are provided to the job reconstruction and plan update module. Subsequent switchover reviews use the projected configurations generated sequentially after reconstruction, and the current actual state is not directly used for all future switches.
[0056] The job reconstruction and plan update module 04, connected to the configuration feedback and job review module and the production scheduling module, is used to cancel unexecuted changeover jobs whose actual configuration already meets the job configuration change results based on the job review results. For jobs that are not canceled, jobs with preconditions that are met or can be formed by still valid preceding jobs are retained, and jobs are regenerated according to configuration differences to replace the original jobs with unmet preconditions and to supplement missing jobs. The planned reservations of canceled jobs are canceled, the actual occupancy of unreleased tooling is maintained, and the subsequent expected configurations, tooling occupancy, and production start conditions are sequentially corrected according to the updated changeover job set. The updated production and changeover plan is output and provided to the production scheduling module. This module takes the actual configuration at the switch position where the feedback is located as the starting point for reconstruction, and uses the configuration comparison rules adopted by the configuration comparison and job generation module to re-examine the components and setting requirements that are not yet met for the current model. The regenerated jobs and retained jobs are compared based on the tooling instance, configuration items, preconditions, and configuration change results. If the content is consistent, the original job is retained; if the corresponding operation is missing, a new job is added. Jobs with invalid preconditions are replaced by new paths, but are not retained as valid operations simultaneously with the replacement job. After a job is canceled, only the resource reservations that have not yet been actually used are cancelled. Tooling that has been installed or used for preparation continues to be occupied, and its available time period is updated only after disassembly and release confirmation is obtained. When a partial changeover is completed, the configuration changes that have been implemented continue to be the actual state, and the remaining jobs are generated from this state, without repeating the disassembly or installation that has already been completed. Configuration items with unknown states are first scheduled for confirmation, and then the remaining paths are formed based on the confirmation results. After the current job set is updated, the module estimates the subsequent configurations according to the production task sequence and checks whether the occupation of shared tooling affects the planned reservation of another workstation. If there is an impact, the corresponding jobs and production start times are corrected according to the updated available time periods. When the subsequent job set, expected configuration, tooling occupation, and production start conditions are all consistent with the original plan, the corresponding update stops. After the updated plan returns to the production scheduling module, the affected unexecuted jobs continue to be called according to the new valid set, and the old jobs that were canceled or replaced are no longer called; the new execution feedback re-enters the configuration feedback and job review module to participate in the next round of configuration verification and plan correction.
Claims
1. A method for processing production scheduling changes in robot chip heat dissipation modules, characterized in that, Performed by the computing system, including: S100: Compare the tooling requirements of the production task with the initial configuration of the switchover, and generate a set of changeover jobs based on the configuration differences; associate the preconditions, configuration change results and dependency configurations of each changeover job. S200. Based on the set of changeover tasks, arrange changeover and production according to task prerequisites, task duration, and available resource periods; use the expected configuration formed by the task configuration change results as the starting configuration for subsequent switchovers to generate production and changeover plans. S300: Receive execution feedback and confirm the actual configuration based on the production and changeover plan; when the actual configuration is inconsistent with the expected configuration at the same switchover location and corresponding execution stage, review the preconditions and configuration change results of the unexecuted changeover operations according to the job dependency configuration, and generate job review results; S400. Based on the job review results, cancel the unexecuted changeover jobs whose actual configurations have met the job configuration change results; for jobs that have not been canceled, retain the jobs whose preconditions have been met or can be formed by still valid preceding jobs, regenerate the jobs according to the configuration differences to replace the original jobs whose preconditions are not met, and supplement the missing jobs; cancel the planned reservation of the canceled jobs, maintain the actual occupation of the unreleased tooling, and sequentially correct the subsequent expected configurations, tooling occupations and production start conditions according to the updated changeover job set, and output the updated production and changeover plan.
2. The method according to claim 1, characterized in that, The tooling requirements for the model include the applicable conditions for the tooling, the requirements for tooling components, and the setting requirements; the switching start configuration includes the tooling instance on the workstation, the installed tooling components, and the current settings. The installed tooling components and current settings are compared with the corresponding tooling component requirements and setting requirements, and the configuration items that do not meet the requirements of the tooling model are recorded to form the configuration differences; The job dependency configuration includes the job prerequisites for the corresponding job change and the configuration items and values involved in the job configuration change results; For switchovers that have already completed configuration confirmation, the actual configuration is used as the starting configuration for the switchover. For switchovers that have not yet been executed, the expected configuration formed by the job configuration change results of the preceding transformation job is used as the starting configuration for the switchover.
3. The method according to claim 2, characterized in that, The process of generating a set of replacement jobs based on configuration differences includes: If the current configuration item meets the tooling requirements of the corresponding model, it is determined to be used; if the tooling requirements of the model include confirmation requirements, a confirmation job is generated. If the current settings do not meet the setting requirements, and the current tooling component meets the tooling application conditions and the setting requirements are within the allowable adjustment range of the tooling component, an adjustment operation is generated. If the current tooling component does not meet the tooling application conditions, or the setting requirements exceed the allowable adjustment range, match a tooling component that meets the tooling application conditions, and generate a replacement operation and an adjustment operation corresponding to the setting requirements; The adjusted or replaced configuration item values are associated with the corresponding changeover operation configuration change results; if there are no tooling parts that meet the applicable conditions of the tooling, the corresponding production task is recorded as unexecutable and no start time is scheduled for the production task.
4. The method according to claim 3, characterized in that, The replacement operation includes disassembly and installation. The installation position state formed after disassembly is taken as the prerequisite for the installation operation, the tooling component state after installation is taken as the prerequisite for the adjustment operation, and the adjusted settings are taken as the prerequisite for the confirmation operation. The aforementioned prerequisite relationships for each task are formed based on the prerequisite conditions described above. According to the aforementioned job prerequisite relationship, the job configuration change results of each changeover job are sequentially written into the corresponding configuration items. The configuration items that are not changed by the changeover job retain the configuration item values in the initial switch configuration, thus forming the expected configuration.
5. The method according to claim 1, characterized in that, When scheduling the changeover and production, read the configuration items changed by each changeover operation, the resources occupied, and the configuration items used by the preceding production task; If a changeover operation does not change the configuration items used by the preceding production task, and the required resources are within the available resource period, the changeover operation shall be scheduled before the end of the preceding production task. When a changeover operation alters the configuration items used by a preceding production task, or when the required resources are occupied by a preceding production task, the changeover operation should be scheduled after the preceding production task has ended and the required resources have been released. If a changeover operation is completed ahead of schedule but still occupies the tooling, the actual occupancy of the tooling will be retained until the release condition is met.
6. The method according to claim 1, characterized in that, The plan reserves corresponding tooling arrangements that have not yet been actually used, and the actual occupation corresponds to tooling that has been installed or used and has not yet been released; When canceling a changeover operation, the planned reservation is canceled based on the tooling instance corresponding to the operation; When a tooling instance is still in the installation or use state, its actual occupancy is not cancelled; After the tooling instance is disassembled from the workstation and a release confirmation is obtained, the available time period of the resource is updated according to the actual time corresponding to the release confirmation. When a new replacement job uses the same tooling instance, the job will be scheduled within the updated resource availability period.
7. The method according to claim 1, characterized in that, The execution feedback includes workstation identification, tooling instance, changeover operation, actual completion time, and configuration confirmation result; According to the workstation identifier, tooling instance, and changeover operation, associate the configuration confirmation result with the corresponding configuration item; Write the confirmed configuration item values into the actual configuration; According to the job dependency configuration, for jobs that have never been executed and depend on configuration items that have changed, the corresponding configuration item values in the actual configuration are compared with the job prerequisites and the job configuration change results to form the job review results. If a configuration item does not receive a configuration confirmation result, the configuration item will be recorded as having an unknown status, and the production start conditions that depend on the configuration item will not be recorded as having been met.
8. The method according to claim 7, characterized in that, When a changeover interruption or confirmation failure occurs, the execution feedback is used to distinguish between completed and incomplete changeover operations. The actual configuration corresponding to the completed changeover operation is retained. The actual configuration is compared with the tooling requirements of the model, and the remaining changeover operations corresponding to the unmet configuration items are generated. The completed changeover operations are not generated again. For configuration items with unknown status, generate a confirmation job, and after obtaining the configuration confirmation result, generate the remaining replacement jobs corresponding to the configuration item. The remaining replacement jobs are included in the updated replacement job set; If the tooling does not meet the release conditions, it remains in actual use.
9. The method according to claim 1, characterized in that, The process of regenerating jobs based on configuration differences to replace original jobs where preconditions are not met and to supplement missing jobs includes: Compare the actual configuration with the tooling requirements of the model corresponding to the current switch, and regenerate the model change job for any unmet configuration items; compare the regenerated model change job with the retained unexecuted model change jobs, retain the jobs whose preconditions and configuration change results are consistent, and supplement the jobs that do not exist in the model change job set; According to the production task sequence, the expected configuration formed by the updated changeover operation set is used as the starting configuration for the next changeover, and subsequent unexecuted changeover operations are reviewed in turn. When changes in tooling occupancy involve planned reservations for another workstation using the same tooling instance, the changeover operation and production start time for that workstation will be rescheduled based on the updated resource availability period. When the subsequent changeover operation set, expected configuration, tooling occupancy, and production start conditions are all consistent with the original plan, the corresponding plan update will be stopped.
10. A robot chip heat dissipation module changeover scheduling system, applied to the method of any one of claims 1 to 9, characterized in that, include: The configuration comparison and job generation module is used to compare the model tooling requirements of production tasks with the start configuration of the switchover, and generate a set of changeover jobs based on the configuration differences. Associate the preconditions, configuration change results, and dependency configurations of each transformation operation; The production scheduling module, connected to the configuration comparison and job generation module, is used to arrange changeover and production based on the changeover job set, according to job prerequisites, job duration, and available resource periods; and to use the expected configuration formed by the job configuration change results as the starting configuration for subsequent switchovers to generate production and changeover plans. A configuration feedback and job verification module is connected to the production scheduling module and is used to receive execution feedback and confirm the actual configuration based on the production and changeover plan. When the actual configuration is inconsistent with the expected configuration at the same switching location and corresponding execution stage, the preconditions and configuration change results of the unexecuted job change job are reviewed according to the job dependency configuration, and a job review result is generated. The job reconstruction and plan update module connects the configuration feedback and job review module and the production scheduling module. Based on the job review results, it cancels unexecuted changeover jobs whose actual configurations meet the job configuration change results. For jobs that are not canceled, it retains jobs whose preconditions are met or can be formed by still valid preceding jobs, and regenerates jobs according to configuration differences to replace the original jobs whose preconditions are not met and to supplement missing jobs. Cancel the planned reservation of the cancelled job, maintain the actual occupation of the unreleased tooling, and sequentially modify the subsequent expected configuration, tooling occupation and production start conditions according to the updated changeover job set. Output the updated production and changeover plan and provide the updated production and changeover plan to the scheduling module.
