Industrial internet motor vehicle production collaborative scheduling method and system

Abstract

The application discloses an industrial internet motor vehicle production collaborative scheduling method and system, the method comprises the following steps: acquiring vehicle production, material distribution, station operation and process connection state data; establishing a plan binding relationship between the vehicle and a single-vehicle material package; and establishing a passing point binding record and a field binding record when the vehicle passes through a point and the material package arrives at a line side; judging a synchronous arrival condition based on a vehicle station arrival window and a single-vehicle material package arrival window, and judging a binding consistent condition in combination with the plan binding relationship, the passing point binding record and the field binding record; when vehicle and material synchronization abnormalities occur, sequentially performing vehicle waiting disposal, material package temporary storage disposal, material package binding change disposal and replacement vehicle release disposal judgment; when the scheduling disposal cannot be completed, generating a previous flow limiting instruction, and generating an abnormal freezing instruction or a manual review prompt according to execution feedback, and updating the binding state. The method can reduce the risk of vehicle and material mismatch and local abnormal diffusion.

Description

Technical Field

[0001] This invention relates to the fields of industrial internet and motor vehicle production scheduling technology, and in particular to an industrial internet method and system for collaborative scheduling of motor vehicle production. Background Technology

[0002] Motor vehicle production typically involves multiple stages, including welding, painting, final assembly, testing, logistics and distribution, and quality management. In mixed-flow production scenarios with multiple vehicle models and configurations, the type, quantity, and timing of materials required for the same target workstation vary depending on the vehicle configuration. The production site usually needs to coordinate vehicle flow, material distribution, and workstation assembly through single-vehicle material delivery, line-side temporary storage, and workstation cycle control.

[0003] Existing production management or logistics distribution methods can typically perform material matching, kitting checks, or error prevention alarms based on vehicle production sequence, vehicle configuration, bill of materials, or estimated vehicle arrival time. However, their focus is mainly on detecting whether materials are correct, missing, or meet planned requirements. In actual production, vehicles may be moved earlier, later, or paused due to quality checks, preceding release controls, buffer area reordering, or changes in the target workstation's cycle time. Individual vehicle material packages may also be moved earlier, later, or unable to be put into production due to delivery routes, delivery equipment, line-side temporary storage space occupancy, unclosed materials, or abnormal seals. This results in anomalies such as vehicles before materials, materials before vehicles, inconsistencies between vehicles and materials, or unclosed material packages. Existing methods often lack continuous verification between planned binding, point binding, and on-site binding, making it difficult to dynamically determine the vehicle-material synchronization status through vehicle workstation arrival windows and single vehicle material package arrival windows. After anomalies occur, they also rely heavily on alarms, manual coordination, or local waiting, lacking a closed-loop processing mechanism that handles vehicle waiting, material package temporary storage, material package rebinding, alternative vehicle release, and preceding flow restriction in a step-by-step scheduling manner. This can easily lead to waiting at target workstations, line-side congestion, vehicle-material mismatch, and expansion of the anomaly scope.

[0004] Therefore, it is necessary to propose an industrial internet-based collaborative scheduling method and system for motor vehicle production to dynamically identify, hierarchically schedule and handle, and perform closed-loop scheduling of abnormal vehicle-material synchronization in motor vehicle production. Summary of the Invention

[0005] To address the aforementioned shortcomings of existing technologies, this invention provides an industrial internet-based collaborative scheduling method and system for motor vehicle production. By utilizing industrial internet status data, triple binding verification, dual time window judgment, and tiered anomaly scheduling and handling, it solves the problems of asynchronous vehicle and individual vehicle material packages, and the reliance on manual coordination for anomaly handling, which can easily expand the scope of impact.

[0006] To achieve the above objectives, the present invention is implemented through the following technical solution:

[0007] In a first aspect, the present invention provides an industrial internet-based method for collaborative scheduling of motor vehicle production, comprising:

[0008] Acquire industrial internet status data from the motor vehicle production site, including vehicle production status data, material delivery status data, workstation operation status data, and process connection status data;

[0009] Establish a planning binding relationship between vehicles and individual vehicle material packages based on the industrial internet status data;

[0010] When a vehicle with an established plan binding relationship passes through a preset passing point, a passing point binding record is established; when a single vehicle with an established plan binding relationship arrives at the target workstation line edge position, a field binding record is established.

[0011] Based on the industrial internet status data, a vehicle workstation arrival window and a single vehicle material package arrival window are generated. It is determined whether the two meet the synchronous arrival conditions. Based on the plan binding relationship, the passing point binding record and the on-site binding record, it is determined whether the vehicle to be assembled at the target workstation and the single vehicle material package to be put on the line meet the binding consistency conditions.

[0012] When the conditions for synchronous arrival or binding consistency are not met, identify the abnormal type of vehicle-material synchronization and the abnormal scheduling and handling restrictions, and make abnormal scheduling and handling judgments for vehicle waiting, material package temporary storage, material package rebinding and alternative vehicle release according to preset priorities.

[0013] When any abnormal scheduling handling method meets the conditions, subsequent judgments are stopped and corresponding scheduling instructions are generated;

[0014] When all preset exception scheduling and handling methods for the current material synchronization anomaly type are not met, a preceding flow limiting instruction is generated.

[0015] Based on the execution feedback of the preceding flow restriction command, it is determined whether the abnormality of the vehicle-material synchronization has been resolved. If it has not been resolved and the duration of the abnormality exceeds the preset safety threshold, an abnormality freeze command is generated. If it has not been resolved and the duration of the abnormality does not exceed the preset safety threshold, a manual review prompt is generated.

[0016] Send scheduling instructions, abnormal freeze instructions, or manual review prompts to the corresponding systems, and update the binding status of vehicles and single-vehicle material packages based on execution feedback.

[0017] Secondly, the present invention also provides an industrial internet-based vehicle production collaborative scheduling system, applied to the industrial internet-based vehicle production collaborative scheduling method as described in the first aspect, the system comprising:

[0018] The status data acquisition module is used to acquire industrial internet status data at the motor vehicle production site. The industrial internet status data includes vehicle production status data, material delivery status data, workstation operation status data, and process connection status data.

[0019] The plan binding module is used to establish the plan binding relationship between vehicles and single-vehicle material packages;

[0020] The passpoint binding module is used to create passpoint binding records;

[0021] The on-site binding module is used to establish on-site binding records;

[0022] The window generation module is used to generate vehicle workstation arrival windows and single-vehicle material package arrival windows;

[0023] The condition judgment module is used to determine whether the arrival window of the vehicle workstation and the arrival window of the single vehicle material package meet the synchronous arrival condition, and to determine whether the vehicle to be assembled at the target workstation and the single vehicle material package to be put on the line meet the binding consistency condition.

[0024] The anomaly identification module is used to identify the types of anomalies in material synchronization and the constraints on anomaly scheduling and handling.

[0025] The handling judgment module is used to determine whether the corresponding abnormal scheduling and handling method meets the conditions according to the abnormality identification module and the abnormality scheduling and handling restrictions. When all the preset abnormality scheduling and handling methods for the current abnormality type of abnormality are not met, the preceding flow limit judgment is triggered, and the abnormality of abnormality is determined based on the execution feedback of the preceding flow limit instruction.

[0026] The instruction generation and issuance module is used to generate and issue vehicle waiting instructions, material package temporary storage instructions, material package rebinding instructions, alternative vehicle release instructions, preceding flow restriction instructions and abnormal freeze instructions to the corresponding systems, or send manual review prompts to the corresponding systems.

[0027] The binding status update module is used to update the binding status between vehicles and single-vehicle material packages based on execution feedback.

[0028] This invention establishes planned binding relationships, transit binding records, and on-site binding records based on industrial internet status data. It also combines vehicle workstation arrival windows and single-vehicle material package arrival windows to determine vehicle-material synchronization status, improving the dynamism and accuracy of determining the correspondence between vehicles and single-vehicle material packages. When anomalies such as vehicle-first-material, material-first-vehicle, vehicle-material inconsistency, or unclosed material packages occur, this invention handles vehicle waiting, material package temporary storage, material package rebinding, and alternative vehicle release according to preset priorities, prioritizing the handling of local anomalies without global rescheduling. If the aforementioned anomaly scheduling methods fail to resolve the anomaly, it limits the further spread of the anomaly through pre-processing flow control, anomaly freezing, or manual review prompts, and updates the binding status based on execution feedback. This reduces the risks of target workstation waiting, line-side temporary storage congestion, and vehicle-material mismatch, improving the continuity and stability of motor vehicle production collaborative scheduling. Attached Figure Description

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

[0030] Figure 1 A schematic diagram of the overall process of the industrial internet motor vehicle production collaborative scheduling method provided in an embodiment of the present invention;

[0031] Figure 2 This is a schematic diagram of the module structure of the industrial internet motor vehicle production collaborative scheduling system provided in an embodiment of the present invention;

[0032] Figure 3 This is a schematic diagram of the material synchronization anomaly identification and primary scheduling and handling process in an embodiment of the present invention;

[0033] Figure 4 This is a schematic diagram of the material package re-binding and alternative vehicle release process in an embodiment of the present invention;

[0034] Figure 5 This is a schematic diagram of the pre-processing flow control and abnormal closed-loop processing in an embodiment of the present invention. Detailed Implementation

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

[0036] The specific embodiments of the present invention will be described below with reference to the accompanying drawings. It should be understood that the following embodiments are used to illustrate the technical solutions of the present invention and are not intended to limit the scope of protection of the present invention. Without departing from the concept of the present invention, those skilled in the art can make adaptive adjustments to the data acquisition method, communication method, and instruction execution object according to the workstation layout, material distribution method, line-side temporary storage rules, vehicle release rules, and system deployment method of the motor vehicle production site.

[0037] This implementation focuses on the dynamic collaborative scheduling between vehicles and individual vehicle material packages in motor vehicle production. The individual vehicle material package is a combination of materials pre-packaged according to the vehicle configuration corresponding to the target workstation and used for assembly on the corresponding vehicle. For ease of description, and without ambiguity, the term "material package" below refers to the individual vehicle material package. This individual vehicle material package corresponds to vehicle configuration, target workstation, planned vehicle binding, and line-side deployment timing. Figure 1 The overall flow of the method provided in the embodiments of the present invention is shown. Figure 2 The system module structure provided in the embodiment of the present invention is shown. Figure 3 This illustrates the process for identifying and handling material synchronization anomalies and the initial scheduling procedures in an embodiment of the present invention. Figure 4 This illustrates the material package re-binding and alternative vehicle release disposal process in an embodiment of the present invention. Figure 5 The preceding current limiting and abnormal closed-loop processing flow in an embodiment of the present invention is shown.

[0038] In this embodiment of the invention, the industrial internet motor vehicle production collaborative scheduling method can be executed by the industrial internet motor vehicle production collaborative scheduling system, and the method includes the following steps.

[0039] Step 10: Obtain industrial internet status data from the motor vehicle production site.

[0040] In step 10, the system acquires industrial internet status data from the motor vehicle production site. This industrial internet status data includes vehicle production status data, material delivery status data, workstation operation status data, and process connection status data. This step forms the data foundation for vehicle-material collaborative scheduling, enabling subsequent plan binding, point-of-care binding, site binding, window generation, and anomaly scheduling and handling judgments to be processed based on the same group of vehicle, material, workstation, and process statuses.

[0041] The industrial internet status data is not simply production plan data, but a unified collection and correlation of data on actual vehicle movement, actual material package delivery, target workstation operation, line-side temporary storage space occupancy, vehicle quality status, and the connection status between preceding and following processes. Through this data set, the system can determine whether a vehicle is approaching its target workstation, whether a material package has arrived at the line, whether the target workstation is ready to receive the package, and whether the vehicle and material package can continue to participate in scheduling.

[0042] Furthermore, after acquiring industrial internet status data, the system can associate the data according to vehicle identifier, material package identifier, target workstation identifier, line-side temporary storage identifier, and time stamp, so that data from different systems or acquisition nodes can be identified as the same vehicle, the same single-vehicle material package, and the same scheduling event under the same target workstation. See steps 101 to 105 for details.

[0043] Step 20: Establish a planning binding relationship between vehicles and single-vehicle material packages based on the industrial internet status data.

[0044] In step 20, the system establishes a planned binding relationship between vehicles and individual vehicle-packages based on the industrial internet status data. This planned binding relationship is used to characterize that in the assembly task at the target workstation, a certain vehicle corresponds to a certain individual vehicle-package at the planning level. It serves as the basis for subsequent point-of-care binding records, on-site binding records, binding consistency condition judgments, and material package rebinding disposal judgments.

[0045] This step does not simply match vehicles and material packages sequentially according to the vehicle production sequence. Instead, it combines the vehicle production sequence, vehicle configuration, and single-vehicle material package identification data to determine whether the material code, quantity, and compatible vehicle configuration within the single-vehicle material package match the single-vehicle material requirement list for the corresponding vehicle at the target workstation. Simultaneously, it also determines whether the vehicle is already bound to other single-vehicle material packages, and whether the single-vehicle material package is already bound to other vehicles, to avoid planning conflicts such as one vehicle with multiple packages or one package with multiple vehicles.

[0046] Furthermore, after the plan binding relationship is established, the system retains the vehicle identifier, material package identifier, target workstation identifier, and plan binding status. This plan binding relationship does not directly determine whether the target workstation is ready for assembly, but rather serves as the basis for comparison between subsequent actual checkpoint visits and on-site arrival. See steps 201 to 204 for details.

[0047] Step 30: When a vehicle with the established plan binding relationship passes through a preset passing point, a passing point binding record is established; when a single vehicle material package with the established plan binding relationship arrives at the target workstation line edge position, a field binding record is established.

[0048] In step 30, the system establishes a passing-point binding record when a vehicle with an established plan binding relationship passes a preset passing point, and establishes a field binding record when a single vehicle-sized material package with an established plan binding relationship arrives at the target workstation line edge. This step extends the vehicle-to-material package correspondence at the planning level to the actual vehicle flow status and the actual arrival status of the material package.

[0049] The transit point binding record is used to characterize the monitorable flow area before a vehicle enters the target workstation. It includes the vehicle identifier, actual transit time, estimated arrival time at the target workstation, and the target workstation identifier. The on-site binding record is used to characterize the material package of a single vehicle entering the available area at the line edge of the target workstation. It includes the material package identifier, arrival time, line edge temporary storage location identifier, and planned binding vehicle identifier.

[0050] Furthermore, the transit point binding record and the on-site binding record reflect the on-site status of the vehicle and materials, respectively. Even if the vehicle and material package are bound at the planning level, if the vehicle has not yet passed the preset transit point or the material package has not yet reached the target workstation line edge, it cannot be directly determined that the target workstation has the conditions for normal assembly. See steps 301 to 303 for details.

[0051] Step 40: Generate a vehicle station arrival window and a single vehicle material package arrival window based on the industrial internet status data, determine whether the two meet the synchronous arrival conditions, and determine whether the vehicle to be assembled at the target station and the single vehicle material package to be put on the line meet the binding consistency conditions based on the planned binding relationship, the passing point binding record and the on-site binding record.

[0052] In step 40, the system generates a vehicle station arrival window and a single-vehicle material package arrival window based on the industrial internet status data, and determines whether the two meet the synchronous arrival conditions. The vehicle station arrival window is used to characterize the time range within which the vehicle is in an reachable, waiting, or receiveable state at the target station; the single-vehicle material package arrival window is used to characterize the time range within which the material package can reach the edge of the target station line and meet the online requirements.

[0053] The synchronization determination in this step does not require the vehicle and the material package to arrive at the same time, but rather to determine whether their available time windows overlap to support assembly at the target workstation. If the two windows overlap, it means that the vehicle and the material package are synchronized in the time dimension; if the two windows do not overlap, an anomaly of vehicle arriving before material or material arriving before vehicle may occur.

[0054] Furthermore, the system also determines the binding consistency condition based on the planned binding relationship, the passing point binding record, and the on-site binding record. The synchronous arrival condition is used to determine whether the time matches, and the binding consistency condition is used to determine whether the objects match; together, they determine whether the current material status of the target workstation meets the normal assembly requirements. See steps 401 to 406 for details.

[0055] Step 50: When the conditions for synchronous arrival or binding consistency are not met, identify the abnormal type of vehicle-material synchronization and the abnormal scheduling and handling restrictions, and make abnormal scheduling and handling judgments for vehicle waiting, material package temporary storage, material package rebinding and alternative vehicle release according to preset priorities.

[0056] In step 50, when the vehicle station arrival window and the single-vehicle material package arrival window do not meet the synchronous arrival condition, or when the vehicle to be assembled at the target station and the single-vehicle material package to be put on the line do not meet the binding consistency condition, the system identifies the vehicle-material synchronization anomaly type and the anomaly scheduling and handling restrictions. The vehicle-material synchronization anomaly type is used to determine the anomaly manifestation, and the anomaly scheduling and handling restrictions are used to determine whether a certain anomaly scheduling and handling method is allowed to be executed.

[0057] In this embodiment, the types of vehicle-material synchronization anomalies include vehicle-first-material-later anomalies, material-first-vehicle-later anomalies, vehicle-material inconsistency anomalies, and material package unclosed anomalies. Anomaly scheduling and handling constraints include conditions that material packages cannot be re-bound, conditions that material packages cannot be put online, and conditions that vehicles cannot wait. The anomaly type and constraints together determine the execution order and scope of subsequent vehicle waiting handling, material package temporary storage handling, material package re-bound handling, and alternative vehicle release handling.

[0058] In this embodiment, the preset priority is as follows: first, determine vehicle waiting disposal and material package temporary storage disposal; then, determine material package rebinding disposal; and finally, determine alternative vehicle release disposal. Among them, vehicle waiting disposal mainly corresponds to the vehicle-first-material-later anomaly, material package temporary storage disposal mainly corresponds to the material-first-vehicle-later anomaly, and material package rebinding disposal and alternative vehicle release disposal are used to continue local scheduling disposal when the aforementioned disposal methods cannot resolve the anomaly.

[0059] Furthermore, the system performs anomaly scheduling and handling judgments according to the preset priority, prioritizing the handling method with the least impact on production order. If the previous anomaly scheduling and handling method cannot resolve the anomaly, the system proceeds to the next anomaly scheduling and handling method. Specifically, as described in steps 501 to 506, the material package re-binding handling is further described in steps 507 and 5071 to 5075, and the replacement vehicle release handling is further described in steps 508 and 5081 to 5084.

[0060] Step 60: When any abnormal scheduling handling method meets the conditions, stop the subsequent judgment and generate the corresponding scheduling instruction.

[0061] In step 60, when the system determines that any of the abnormal scheduling handling methods among vehicle waiting handling, material package temporary storage handling, material package rebinding handling, and alternative vehicle release handling meets the conditions, it stops subsequent abnormal scheduling handling judgments and generates corresponding scheduling instructions. This step is used to avoid continuing to execute scheduling actions with a higher level of intervention when the abnormality can already be resolved with a lower level of intervention.

[0062] For example, when the conditions for vehicle waiting are met, a vehicle waiting instruction is generated; when the conditions for material package temporary storage are met, a material package temporary storage instruction is generated; when the conditions for material package rebinding are met, a material package rebinding instruction is generated; and when the conditions for alternative vehicle release are met, an alternative vehicle release instruction is generated. Different instructions act on different systems or field objects, but all are used to resolve the current vehicle-material synchronization anomaly or reduce the impact of the anomaly on the continuous production of the target workstation.

[0063] Furthermore, after the corresponding scheduling instruction is generated, the system obtains the instruction execution feedback and updates the binding status between the vehicle and the single vehicle material package based on the execution feedback. This execution feedback is also used to determine whether it is necessary to re-execute the synchronization arrival condition and binding consistency condition judgment. See steps 601 to 604 for details.

[0064] Step 70: When all preset abnormal scheduling and handling methods for the current material synchronization abnormality type do not meet the conditions, a preceding flow limiting instruction is generated.

[0065] In step 70, when all preset exception scheduling and handling methods for the current vehicle-material synchronization exception type fail to meet the conditions, the system generates a preceding flow restriction instruction. This step is used to constrain the behavior of releasing vehicles in the preceding process when vehicle waiting, material package temporary storage, material package rebinding, and alternative vehicle release all fail to resolve the exception, thereby reducing the possibility of the exception continuing to expand to the target workstation.

[0066] The preceding flow control instructions include limited release instructions and prohibited release instructions. Limited release instructions limit the maximum number of vehicles released by the preceding process towards the target workstation within a preset time period; prohibited release instructions prohibit the continued release of vehicles corresponding to material packages that have not arrived, are not closed, or cannot be put into service. Through preceding flow control, the system can prevent abnormal vehicles from continuously entering the target workstation direction, reducing the risks of waiting at the target workstation, line-side congestion, and continuous obstruction of subsequent vehicles.

[0067] Furthermore, the generation of the preceding flow restriction instruction is based on the target workstation cycle time, the status of the line-side temporary storage position, the type of vehicle-material synchronization anomaly, the preceding release status, and the subsequent receiving status. The preceding flow restriction is not a permanent prohibition of normal vehicle release, but rather a constraint on the preceding release behavior when the current anomaly has not been fully resolved through scheduling. See steps 701 to 703 for details.

[0068] Step 80: Determine whether the abnormality of the vehicle-material synchronization has been resolved based on the execution feedback of the preceding flow restriction command. If it has not been resolved and the duration of the abnormality exceeds the preset safety threshold, generate an abnormality freeze command. If it has not been resolved and the duration of the abnormality does not exceed the preset safety threshold, generate a manual review prompt.

[0069] In step 80, the system determines whether the vehicle-material synchronization anomaly has been resolved based on the execution feedback of the preceding flow restriction command. The execution feedback can reflect changes in the preceding release quantity, changes in the target station receiving status, changes in the line-side temporary storage status, the arrival status of a single vehicle's material package, whether the unclosed status of the material package has been resolved, and whether the binding status between the vehicle and the single vehicle's material package has been updated.

[0070] If the execution feedback determines that the material synchronization anomaly has been resolved, the system removes the preceding flow restriction command and re-evaluates the synchronization arrival condition and binding consistency condition based on the updated binding status. If the material synchronization anomaly has not been resolved, the system further determines the duration of the anomaly. If the anomaly duration exceeds a preset safety threshold, an anomaly freeze command is generated; if the anomaly duration does not exceed the preset safety threshold, a manual review prompt is generated.

[0071] Furthermore, the abnormal freeze command can be applied to the corresponding vehicle or the corresponding single vehicle material package to prevent it from continuing to enter the target workstation's online process; the manual verification prompt is used to remind the corresponding system or on-site personnel to check the vehicle, material package, line-side temporary storage location, target workstation, and material package closure status. See the descriptions in steps 801 to 804 for details.

[0072] Step 90: Send the scheduling instruction, abnormal freeze instruction, or manual review prompt to the corresponding system, and update the binding status of the vehicle and the single vehicle material package based on the execution feedback.

[0073] In step 90, the system sends scheduling instructions, abnormal freeze instructions, or manual review prompts to the corresponding systems, and updates the binding status of vehicles and single-vehicle material packages based on execution feedback. The corresponding system 310 may include a production execution system, a material distribution system, a target workstation control system, or a quality management system, and the specific recipient is determined according to the instruction type.

[0074] This step is used to form a closed loop. For vehicle waiting instructions, the execution feedback is used to confirm whether the vehicle has completed waiting; for material package temporary storage instructions, the execution feedback is used to confirm whether the material package has entered the line-side temporary storage position; for material package rebinding instructions, the execution feedback is used to confirm whether the planned bound vehicle has been updated; for substitute vehicle release instructions, the execution feedback is used to confirm whether the substitute vehicle has been released and whether the original vehicle to be assembled has been marked as pending; for preceding flow restriction instructions, the execution feedback is used to confirm whether the anomaly has been resolved.

[0075] Furthermore, the updated binding state re-enters step 40 to re-determine the synchronization arrival condition and binding consistency condition. Thus, the system forms a closed-loop scheduling process from state acquisition, binding verification, window judgment, anomaly scheduling and handling, preceding rate limiting, anomaly freezing or manual review, to binding state updating. See steps 901 to 903 for details.

[0076] This embodiment establishes planned binding relationships, transit binding records, and on-site binding records based on industrial internet status data. It also combines vehicle workstation arrival windows and single-vehicle material package arrival windows to determine the vehicle-material synchronization status, which improves the dynamism and accuracy of determining the correspondence between vehicles and single-vehicle material packages. When anomalies such as vehicle-first-material, material-first-vehicle, vehicle-material inconsistency, or unclosed material packages occur, this embodiment handles vehicle waiting, material package temporary storage, material package rebinding, and alternative vehicle release according to preset priorities, prioritizing the handling of local anomalies without global rescheduling. When the aforementioned anomaly scheduling and handling methods cannot resolve the anomaly, it limits the further spread of the anomaly through pre-processing flow restriction, anomaly freezing, or manual review prompts, and updates the binding status based on execution feedback, thereby reducing the risks of target workstation waiting, line-side temporary storage congestion, and vehicle-material mismatch, and improving the continuity and stability of motor vehicle production collaborative scheduling.

[0077] In one embodiment, steps 101 to 105 are described as follows:

[0078] Step 101: Obtain vehicle production status data.

[0079] Vehicle production status data includes vehicle production sequence, vehicle configuration, vehicle transit data, and vehicle quality status data. The vehicle production sequence determines the order in which vehicles enter the target workstation; vehicle configuration determines the type, quantity, and compatibility of materials to be assembled at the target workstation; vehicle transit data determines whether a vehicle has passed a preset transit point and the actual transit time; and vehicle quality status data determines whether a vehicle is allowed to continue moving, whether it is allowed to remain stationary, and whether it needs to be excluded from the workstation arrival window calculation.

[0080] Furthermore, vehicle production status data is associated with at least the vehicle identifier and the target workstation identifier. The vehicle identifier is used to group the production sequence, vehicle configuration, checkpoint data, and quality status data of the same vehicle into the same object; the target workstation identifier is used to determine the workstation location where the vehicle needs to undergo synchronized vehicle-material judgment. If the vehicle quality status indicates that the vehicle is not allowed to be transferred, the corresponding vehicle workstation arrival window is marked as invalid during the subsequent window generation process.

[0081] Step 102: Obtain material delivery status data.

[0082] Material delivery status data includes single-vehicle material package identification data, single-vehicle material package arrival data, single-vehicle material package current location data, material delivery path data, and delivery equipment status data. Single-vehicle material package identification data is used to determine the material package identifier, material code, material quantity, compatible vehicle configuration, and seal status; single-vehicle material package arrival data is used to determine whether the material package has reached the target workstation lineside location and its arrival time; single-vehicle material package current location data, material delivery path data, and delivery equipment status data are used to determine the reachability status of the material package from its current location to the target workstation lineside location.

[0083] Furthermore, the seal status is used to characterize whether a single vehicle's material package remains closed before entering the target workstation line position. The seal status is one of the status data for determining whether a single vehicle's material package has formed a material package unclosed anomaly. A material package unclosed anomaly can also be formed when the material code or quantity corresponding to the target workstation does not meet the single vehicle's material requirement list.

[0084] Optionally, the identification data for a single vehicle's material package can be derived from the material package identification code, delivery task record, line-side scanning record, seal scanning record, or target workstation arrival record. The specific data collection device is not limited here, as long as it can determine the material package's identity, material contents, compatible vehicle configuration, and seal status. Material delivery status data is used in subsequent steps to establish plan binding relationships, generate single vehicle material package arrival windows, and identify unclosed material package anomalies.

[0085] Step 103: Obtain workstation operation status data.

[0086] The workstation operation status data includes line-side temporary storage location status data and target workstation cycle time data. Line-side temporary storage location status data is used to determine whether there are available temporary storage locations in the line-side area corresponding to the target workstation, whether the temporary storage locations are occupied, and whether the line-side temporary storage location identifier corresponds to the target workstation identifier. Target workstation cycle time data is used to determine the standard production cycle time of the target workstation, the allowable waiting time, the target workstation's required time, and the current receiving status.

[0087] Furthermore, the status data of the temporary storage location at the line edge is used not only to determine the temporary storage and disposal of material packages, but also to determine the latest allowed time for material packages to be put online. The cycle time data of the target workstation is used not only to calculate the arrival window of the vehicle workstation, but also to determine whether the waiting for vehicle disposal will affect the continuous assembly of the target workstation.

[0088] Step 104: Obtain process connection status data.

[0089] The process connection status data includes preceding release status data and subsequent receiving status data. Preceding release status data is used to determine whether the preceding process allows the continued release of vehicles towards the target workstation, and to identify the queue of vehicles waiting to enter and the queue of vehicles that can be released before the target workstation. Subsequent receiving status data is used to determine whether subsequent workstations after the target workstation have the necessary receiving capabilities, preventing continuous obstruction at subsequent workstations after the release of replacement vehicles.

[0090] Furthermore, the preceding release status data is used when generating the preceding current limiting command, and the subsequent received status data is used when determining whether the alternative vehicle can be released. Both are used together to limit the scope of the anomaly and prevent the material-vehicle synchronization anomaly from expanding from a single target workstation to multiple processes before and after it.

[0091] Step 105: Associate objects with industrial internet status data.

[0092] The system associates the data acquired in steps 101 to 104 according to vehicle identifier, material package identifier, target workstation identifier, line-side temporary storage identifier, and time stamp to form an industrial internet status data set for subsequent processing. This industrial internet status data set does not change the meaning of the original data, but rather enables data from different acquisition nodes to point to the same vehicle, the same single vehicle material package, and the same target workstation.

[0093] Furthermore, the timestamp is used to determine the correspondence between the same vehicle status, the same material package status, and the same target workstation status within the same scheduling cycle, avoiding incorrect association of data collected at different times. The result of step 105 is used in step 20 to establish the plan binding relationship, and in step 30 to establish the over-point binding record and the on-site binding record. If there is a conflict in the data corresponding to the same vehicle identifier or the same material package identifier, the system can mark the object as pending review and generate a manual review prompt, preventing the object from directly entering the normal binding process.

[0094] In one embodiment, steps 201 to 204 are described as follows:

[0095] Step 201: Determine the vehicle sequence to enter the target workstation based on the vehicle production sequence.

[0096] The vehicle production sequence can come from the production plan, the buffer queue before the target workstation, the previous release record, or the vehicle transit record. The vehicle sequence to enter the target workstation is used to determine the relative order of the vehicles entering the target workstation and to provide the vehicle-side basis for establishing a plan binding relationship between the vehicles and the single vehicle material package.

[0097] Furthermore, when determining the vehicle sequence to enter the target workstation, the system can exclude vehicles whose quality status does not allow for transfer, or mark them as vehicles that cannot enter the target workstation and are pending processing. This can prevent vehicles with quality defects from being incorrectly assigned to single-vehicle material packages, thereby reducing the sources of anomalies in subsequent binding consistency condition judgments.

[0098] Step 202: Determine the single-vehicle material requirement list for each vehicle at the target workstation based on the vehicle configuration.

[0099] The vehicle-specific material requirements list includes the material codes, quantities, and compatible configurations required for the corresponding vehicle at the target workstation. This list is used to compare with the vehicle-specific material package identification data to determine whether a particular vehicle-specific material package can meet the assembly requirements of the corresponding vehicle at the target workstation.

[0100] Furthermore, the single-vehicle material requirement list is only used for the assembly task corresponding to the target workstation and is not required to cover all materials for the entire vehicle. This allows the planning binding relationship to focus on the synchronous scheduling of materials for the target workstation, avoiding the impact of material differences at non-target workstations on the binding judgment of this target workstation.

[0101] Step 203: Compare the vehicle-specific material requirements list with the vehicle-specific material package identification data.

[0102] The system compares the BOM (Bill of Materials) for the target vehicle with the material codes, quantities, and compatible vehicle configurations in the candidate BOM packages. When the material codes, quantities, and compatible vehicle configurations all match the BOM for the corresponding vehicle, it is determined that the BOM package has the material basis for establishing a planning relationship with the target vehicle.

[0103] Optionally, the comparison process can be performed item by item for each target workstation, that is, only the assembly materials corresponding to the target workstation are compared, without considering the materials required by other workstations as a necessary condition for binding the target workstation. This approach makes the planning binding relationship more aligned with the synchronous scheduling needs of the target workstation's materials and machinery.

[0104] Step 204: Establish the planning binding relationship between the vehicle and the single vehicle material package.

[0105] When the material code, quantity, and compatible vehicle configuration within a single vehicle material package match the corresponding vehicle's single vehicle material requirement list, and the vehicle is not bound to any other single vehicle material package, and the single vehicle material package is not bound to any other vehicle, a planned binding relationship is established between the vehicle and the single vehicle material package. The planned binding relationship includes at least the vehicle identifier, material package identifier, target workstation identifier, and planned binding status.

[0106] Furthermore, this step employs an exclusive binding method. The same vehicle will not be repeatedly bound to multiple single-vehicle material packages at the same target workstation, nor will the same single-vehicle material package be repeatedly bound to multiple vehicles. If a vehicle or single-vehicle material package already has a valid planned binding relationship, no new planned binding relationship will be established, and the vehicle or single-vehicle material package will be marked as a binding conflict pending review, with a manual review prompt generated. This exclusive binding is used to reduce the risk of multiple packages per vehicle or multiple vehicles per package at the planning level, and provides a clear basis for subsequent checkpoint binding records, on-site binding records, and binding consistency condition judgments.

[0107] In one embodiment, steps 301 to 303 are described as follows:

[0108] Step 301: Establish a point binding record.

[0109] When a vehicle with an established plan binding relationship passes a preset transit point, the system reads the vehicle's identifier, actual transit time, estimated arrival time at the target workstation, and target workstation identifier, and establishes a transit binding record. The preset transit point is a location located in front of the target workstation that reflects the vehicle's imminent entry into the target workstation's scheduling range.

[0110] Furthermore, the transit point binding record is used to transition a vehicle from a planned state to an actual flow state. If a vehicle has not passed the preset transit point, although it may already have a planned binding relationship, its actual flow state is insufficient to support the current scheduling judgment of the target workstation. After the transit point binding record is generated, its actual transit time is used to calculate the earliest arrival time of subsequent vehicles, and its target workstation identifier is used to determine the consistency condition of subsequent bindings. The estimated arrival time at the target workstation can be determined based on the vehicle's actual transit time, the state of the transport path between the preset transit point and the target workstation, and the transport cycle time before the target workstation.

[0111] Step 302: Establish on-site binding records.

[0112] When a single vehicle-sized material package with an established plan binding relationship arrives at the target workstation lineside location, the system reads the material package identifier, arrival time, lineside temporary storage location identifier, and planned binding vehicle identifier, and establishes a field binding record. The target workstation lineside location includes the corresponding online location or lineside temporary storage location.

[0113] Furthermore, the on-site binding record is used to transition a single vehicle's material package from the delivery state to the line-side available state. If the single vehicle's material package has not arrived at the target workstation's line-side location, the material package cannot directly participate in the target workstation's assembly; if the material package has arrived but the line-side temporary storage location identifier does not correspond to the target workstation identifier, it cannot be considered that it meets the binding consistency condition of the target workstation.

[0114] Step 303: Associate the point binding record and the on-site binding record.

[0115] Based on the planned binding relationship, the system associates the vehicle identifier and target workstation identifier in the point-to-point binding record with the planned bound vehicle identifier and line-side temporary storage location identifier in the on-site binding record. This association result is used in step 40 to determine whether the vehicle currently to be assembled at the target workstation and the material package to be put into service on the line meet the binding consistency condition.

[0116] Furthermore, if the point binding record exists but the on-site binding record does not exist, a "vehicle first, material later" anomaly may occur; if the on-site binding record exists but the corresponding vehicle has not yet arrived at the target workstation's scheduling range, a "material first, vehicle later" anomaly may occur; if both exist but the vehicle identifier is inconsistent with the planned bound vehicle identifier, a "vehicle-material inconsistency" anomaly may occur.

[0117] In one embodiment, steps 401 to 406 are described as follows:

[0118] Step 401: Generate the vehicle workstation arrival window.

[0119] The vehicle arrival window is formed by the earliest arrival time and the latest permitted arrival time of the vehicle, representing the time range within which the vehicle is in an acceptable or waiting state at the target workstation. The earliest arrival time of the vehicle is determined based on the vehicle's actual transit time and the fastest conveyor cycle from the preset transit position to the target workstation, while the latest permitted arrival time of the vehicle is determined based on the standard production cycle of the target workstation and the vehicle's quality status.

[0120] In this embodiment, the vehicle station arrival window is shown in the following formula:

[0121]

[0122] In the formula, Indicates that the vehicle has arrived at the workstation window; Indicates the earliest arrival time of the vehicle; This indicates the latest allowed arrival time for the vehicle. The actual vehicle arrival time comes from the arrival time binding record. The fastest conveying cycle time comes from the conveying status between the vehicle's arrival point and the target workstation. The standard production cycle time of the target workstation comes from the workstation's operating status data. The vehicle quality status comes from the vehicle's production status data. The vehicle workstation arrival window is used to synchronize arrival condition judgment with the single vehicle material package arrival window.

[0123] Furthermore, the earliest arrival time of a vehicle represents the earliest moment when the vehicle arrives at the target workstation without additional waiting and according to the currently available transport status; the latest allowed arrival time of a vehicle represents the latest moment when the vehicle can still be received by the target workstation without disrupting the target workstation's cycle time constraints. When the vehicle's quality status does not allow for transport, the effective latest allowed arrival time for that vehicle is no longer calculated; instead, the vehicle's workstation arrival window is directly marked as invalid. Invalid windows do not participate in the synchronous arrival condition judgment, nor are they considered as candidate vehicle windows in the alternative vehicle release process.

[0124] Step 402: The generated vehicle-sized material package arrives at the window.

[0125] The arrival window for a single vehicle's material package is formed by the earliest arrival time and the latest allowed online time of the material package, representing the time range within which the material package can reach the target workstation line and meet the online requirements. The earliest arrival time of the material package is determined based on the current location of the single vehicle's material package, the material delivery path, and the status of the delivery equipment. The latest allowed online time of the material package is determined based on the status of the lineside temporary storage location and the time required by the target workstation.

[0126] In this embodiment, the arrival window for a single vehicle's material package is shown in the following formula:

[0127]

[0128] In the formula, This indicates that a single vehicle's material package has arrived at the window; Indicates the earliest arrival time of the material package; This indicates the latest allowed time for a material package to be uploaded. The current location of a single vehicle's material package, the material delivery path, and the delivery equipment status are derived from material delivery status data, while the status of the line-side temporary storage location and the target workstation's required time are derived from workstation operation status data. The single vehicle's material package arrival window is used for synchronous comparison with the vehicle workstation arrival window.

[0129] Furthermore, the earliest arrival time of the material package indicates the earliest time that a single vehicle's material package can reach the target workstation lineside position under the current delivery route and delivery equipment status; the latest allowed online time of the material package indicates the latest time that the material package can still meet the target workstation's time requirements without causing abnormal occupation of the lineside temporary storage space. The target workstation's required time is determined based on the target workstation's standard production cycle time, the current order of vehicles to be assembled, and the target workstation's receiving status, and is used to indicate the time required for the target workstation to meet the online requirements for the corresponding single vehicle's material package. If the material package is in an abnormally frozen state, it will not be considered as a material package meeting the online requirements and will not be included in the normal synchronous arrival condition judgment.

[0130] Step 403: Determine the conditions for synchronization.

[0131] The synchronous arrival condition is used to determine whether there is a time overlap between the vehicle station arrival window and the single-vehicle material package arrival window, and whether this time overlap can support the assembly at the target station. During the determination, the system calculates the intersection of the vehicle station arrival window and the single-vehicle material package arrival window.

[0132] In this embodiment, the synchronization arrival condition is as follows:

[0133]

[0134] In the formula, This indicates the overlap time between the vehicle's arrival window and the arrival window of a single vehicle's material package; and These represent the earliest arrival time and the latest permitted arrival time of the vehicle, respectively. and These represent the earliest arrival time and the latest allowed online time for the material package, respectively. When, it is determined that the two have a temporal overlap and meet the condition of synchronous arrival; when If the condition for synchronous arrival is not met, the result is entered into step 50 to identify either a "car first, material later" or "material first, car later" anomaly.

[0135] Step 404: Determine if the binding is consistent.

[0136] Based on the planned binding relationship, the point-of-care binding record, and the on-site binding record, the system reads the vehicle identifier of the vehicle currently to be assembled at the target workstation, the planned bound vehicle identifier of the single-vehicle material package to be delivered to the line, the line-side temporary storage location identifier, and the target workstation identifier. When the vehicle identifier of the vehicle currently to be assembled at the target workstation matches the planned bound vehicle identifier of the single-vehicle material package to be delivered to the line, the line-side temporary storage location identifier corresponds to the target workstation identifier, and the single-vehicle material package is not in an abnormally frozen state, the binding consistency condition is determined to be met.

[0137] Step 405: When both the synchronization arrival condition and the binding consistency condition are met, determine that the current vehicle and the corresponding single-vehicle material package can enter the normal assembly process of the target workstation.

[0138] At this time, the system maintains the current plan binding relationship and the on-site binding status, and can send the current material status to the target workstation control system so that the target workstation can maintain a normal receiving status.

[0139] Step 406: When the synchronization arrival condition is not met or the binding consistency condition is not met, the system outputs the abnormal trigger result of the vehicle material synchronization.

[0140] The trigger result includes vehicle identifier, material package identifier, target workstation identifier, abnormal trigger reason, current binding status, and window judgment result. The vehicle-material synchronization abnormal trigger result is intermediate data for entering the vehicle-material synchronization abnormal type identification. The output of step 406 enters step 50, which is used to identify the vehicle-material synchronization abnormal type and abnormal scheduling and handling restrictions.

[0141] In one embodiment, steps 501 to 506 are described as follows:

[0142] Step 501: Identify the abnormal type of material synchronization.

[0143] Based on the results of the synchronization arrival condition judgment, the binding consistency condition judgment, the unclosed status of the material package, and the status of the temporary storage position at the line edge, the system identifies the abnormalities of "car first, material later", "material first, car later", "car-material inconsistency" and "material package unclosed".

[0144] When the arrival window of the vehicle workstation and the arrival window of the single-vehicle material package do not meet the synchronous arrival condition, and the earliest arrival time of the vehicle is earlier than the earliest arrival time of the material package, it is identified as a vehicle-first-material-later anomaly; when the arrival window of the vehicle workstation and the arrival window of the single-vehicle material package do not meet the synchronous arrival condition, and the earliest arrival time of the single-vehicle material package is earlier than the earliest arrival time of the vehicle, resulting in the single-vehicle material package occupying or about to occupy the temporary storage space at the line edge corresponding to the target workstation, it is identified as a material-first-vehicle-later anomaly; when the vehicle to be assembled at the target workstation is inconsistent with the vehicle bound to the single-vehicle material package to be put on the line edge, it is identified as a vehicle-material inconsistency anomaly; when the material code, quantity, or seal status of the single-vehicle material package corresponding to the target workstation does not meet the single-vehicle material requirement list of the corresponding vehicle, it is identified as a material package not closed anomaly.

[0145] Step 502: Identify the constraints for handling abnormal scheduling.

[0146] The system identifies abnormal scheduling and handling restrictions based on the status of the material package, vehicle, and target workstation. These restrictions include conditions such as "material package cannot be re-bound," "material package cannot be put online," and "vehicle cannot wait." A material package cannot be re-bound when it has been opened, entered the target workstation's online position, or completed on-site binding confirmation. A material package cannot be put online when it is in an abnormally frozen state. A vehicle cannot wait when it has entered the target workstation's continuous transport area or when its quality status does not allow it to remain in place.

[0147] Step 503: Determine if the vehicle is waiting for processing.

[0148] When the vehicle-material synchronization anomaly type is "vehicle first, material later" anomaly, and the difference between the earliest arrival time of the vehicle and the earliest arrival time of the material package does not exceed the allowable waiting time at the target workstation and the vehicle's quality status allows for continued operation, the vehicle waiting action is deemed to meet the conditions, and a vehicle waiting instruction is generated. The vehicle waiting instruction is used to keep the target vehicle in a waiting state within the allowable waiting range, waiting for the corresponding single-vehicle material package to arrive at the target workstation line edge position.

[0149] Furthermore, the difference between the earliest arrival time of the vehicle and the earliest arrival time of the material package refers to the delay in the earliest arrival time of the material package relative to the earliest arrival time of the vehicle under the abnormal situation of "vehicle first, material later". This delay is used to determine whether the target vehicle can wait for the corresponding single-vehicle material package to arrive within the allowed waiting time at the target workstation.

[0150] Step 504: Perform a reassessment after the vehicle waiting instruction is executed.

[0151] After the vehicle wait instruction is executed, the system re-acquires the vehicle status and material package status, and re-determines whether the vehicle workstation arrival window and the single vehicle material package arrival window meet the synchronous arrival conditions. If they are met again, the system proceeds to the binding status update; if they are still not met, the system proceeds to the material package rebinding processing judgment.

[0152] Furthermore, the re-judgment can be triggered when the vehicle waiting instruction is completed, the arrival status of the corresponding single-vehicle material package changes, or the receiving status of the target workstation changes. The data used for the re-judgment comes from updated vehicle production status data, material delivery status data, and workstation operation status data.

[0153] Step 505: Determine the temporary storage and disposal of the material package.

[0154] When the material synchronization anomaly type is "material first, then vehicle later" anomaly, and there is an empty space in the line-side temporary storage position while the material package has not entered the target workstation's online position, the material package temporary storage disposal condition is determined to be met, and a material package temporary storage instruction is generated. The material package temporary storage instruction is used to temporarily store the material package that arrived in advance in the single-vehicle temporary storage position corresponding to the target workstation, preventing it from directly entering the target workstation's online position and causing material mismatch.

[0155] Step 506: Re-evaluate after executing the material package temporary storage instruction.

[0156] After the material package temporary storage instruction is executed, the system re-evaluates whether the arrival conditions of the vehicle workstation and the single vehicle material package meet the synchronous arrival conditions. If the conditions are met again, the binding status is updated; if the conditions are still not met, and the temporarily stored single vehicle material package has not been unpacked, has not entered the target workstation online position, and has not completed on-site binding confirmation, the system proceeds to the material package rebinding processing judgment.

[0157] Furthermore, the re-judgment can be triggered when the material package is temporarily stored, the vehicle workstation arrival window is updated, or the target workstation's required time is updated. If the temporarily stored material package has already been unpacked, entered the target workstation's online position, or completed on-site binding confirmation, then the material package rebinding processing judgment will no longer be initiated.

[0158] Step 507: Make a judgment on the re-binding of material packages.

[0159] Material package rebinding is used when vehicle waiting or temporary storage of material packages cannot restore the synchronous arrival conditions between the vehicle's workstation arrival window and the single-vehicle material package arrival window. It determines whether a single-vehicle material package that has not yet entered the target workstation's online position, has not been unpacked, and has not yet completed on-site binding confirmation can be rebinded to another vehicle that meets the configuration and time window requirements before reaching the target workstation. This step is not simply replacing the vehicle corresponding to the material package, but rather, without affecting the vehicle flow sequence in the continuous transport area of ​​the target workstation, it continuously assesses the rebinding availability status of the material package to be rebinded, the vehicle configuration of the candidate vehicles, the material requirements list of the candidate vehicles, the quality status of the candidate vehicles, and the synchronous arrival conditions between the candidate vehicles and the material package to be rebinded.

[0160] Furthermore, the judgment result of the material package rebinding process is used to determine whether to generate a material package rebinding instruction. When a candidate vehicle that meets the conditions exists, the system updates the planned vehicle bound to the material package to be rebinded to the candidate vehicle, and uses the updated binding status for subsequent re-judgment of synchronization arrival conditions and binding consistency conditions; when no candidate vehicle that meets the conditions is found, or when the candidate vehicle and the material package to be rebinded do not meet the synchronization arrival conditions, the system determines that the material package rebinding process judgment does not meet the conditions, and proceeds to the alternative vehicle release process judgment. See steps 5071 to 5075 for details.

[0161] Step 508: Determine whether to release the alternative vehicle.

[0162] The alternative vehicle release procedure is used when the material package corresponding to the vehicle currently awaiting assembly at the target workstation has not arrived, is not closed, or cannot be put into operation, and the material package rebinding procedure cannot resolve the current vehicle-material synchronization anomaly. It determines whether a vehicle that has completed planned binding, whose vehicle quality status allows for flow, and whose planned bound material package meets the synchronization arrival conditions can be selected from the releaseable vehicle queue in front of the target workstation, and releases it as a substitute vehicle towards the target workstation. The key point of this step is to alleviate the current anomaly by releasing a vehicle that already meets the vehicle-material synchronization conditions, rather than reordering vehicles that have already entered the continuous transport area of ​​the target workstation.

[0163] Furthermore, the release and disposal of replacement vehicles must simultaneously meet two requirements: First, the replacement vehicle itself must arrive synchronously with its planned single-vehicle material package to avoid new discrepancies between vehicle and material due to the release; second, the release of the replacement vehicle must not alter the existing flow sequence of vehicles already in the continuous conveying area of ​​the target workstation. If the above conditions are met, the system generates a replacement vehicle release instruction, marks the original vehicle to be assembled as a vehicle to be processed, and stops its release to the target workstation; if the above conditions are not met, the preceding flow restriction process is initiated. See steps 5081 to 5084 for details.

[0164] In one embodiment, step 507, namely the determination of the re-binding of the material package, includes steps 5071 to 5075.

[0165] Step 5071: Determine whether the material package to be re-bound meets the preconditions for re-bound.

[0166] The system reads the unpacking status, online location status, and on-site binding confirmation status of the material package to be re-bound. If the material package to be re-bound is not unpacked, has not entered the target workstation online location, and has not completed on-site binding confirmation, it is determined that the material package to be re-bound meets the preconditions for re-bound. If any condition is not met, it is determined that the material package has formed a condition that the material package cannot be re-bound, and the re-bound process for the material package is stopped.

[0167] Furthermore, the fact that the material package to be re-bound meets the preconditions for re-bound only indicates that it has the basis for being re-bound, and does not directly mean that the re-bound can be completed. The system still needs to determine whether there are candidate vehicles that are compatible with the material package, and whether the candidate vehicles and the material package to be re-bound meet the condition of arriving at the same time.

[0168] Step 5072: Determine the queue of vehicles waiting to enter in front of the target workstation.

[0169] The queue of vehicles waiting to enter the target workstation is a collection of vehicles that have not yet entered the continuous conveying area of ​​the target workstation and may enter the target workstation direction later. This queue can be determined based on the vehicle production sequence, previous release status data, vehicle transit data, and vehicle quality status data.

[0170] Furthermore, vehicles already in the continuous transport area of ​​the target workstation will not be considered as candidate vehicles for repackaging, to avoid altering the established flow sequence within the continuous transport area through material package repackaging. Vehicles whose quality status does not allow for transfer or are in an abnormally frozen state will also not be considered as candidate vehicles.

[0171] Step 5073: Filter candidate vehicles.

[0172] The system filters candidate vehicles from the queue of vehicles waiting to enter the target workstation. These vehicles are those that have not entered the continuous conveying area of ​​the target workstation, whose configuration is consistent with the compatible vehicle configuration of the material package to be re-bound, whose material code and quantity of the material package to be re-bound are consistent with the single-vehicle material requirement list of the vehicle, whose on-site binding confirmation of other material packages has not been completed, and whose vehicle quality status allows for circulation and is not in an abnormal frozen state.

[0173] In this embodiment, the initial screening set of candidate vehicles is shown in the following formula:

[0174]

[0175] In the formula, Indicates the material package to be re-bundled The initial set of matched candidate vehicles; This refers to the vehicles in the queue waiting to enter the target workstation. Indicates vehicle The vehicle has not entered the continuous conveying area of ​​the target workstation and its quality status allows for transfer. This indicates that the vehicle configuration is consistent with the compatible vehicle configuration of the material package to be re-bundled, and the material code and quantity of the material package to be re-bundled are consistent with the vehicle configuration. The material requirements list for each vehicle is consistent; Indicates vehicle Other material packages have not been confirmed for on-site binding. Indicates vehicle Not in an abnormally frozen state. This set is used to determine whether there are candidate vehicles for further synchronization arrival condition checks.

[0176] Step 5074: Determine whether the candidate vehicle and the material package to be re-bundled meet the condition of synchronous arrival.

[0177] For the initial screening set of candidate vehicles obtained in step 5073, the system generates the vehicle workstation arrival window for each candidate vehicle and performs a synchronization arrival condition judgment between it and the arrival window of the material package to be re-bundled. Vehicles that meet the conditions in step 5073 are only initial screening candidate vehicles. Only after their vehicle workstation arrival window and the arrival window of the material package to be re-bundled meet the synchronization arrival condition are they considered as vehicles eligible for re-bundling.

[0178] Furthermore, if multiple candidate vehicles meet the synchronous arrival condition, the system determines the candidate vehicles sequentially according to their distance from the target workstation in the vehicle production sequence, from closest to furthest. If the candidate vehicle closest to the target workstation would affect the flow order of vehicles already in the continuous conveying area of ​​the target workstation, the next candidate vehicle is considered sequentially. This selection does not change the basic conditions for candidate vehicle screening, and the result is used to generate material package rebinding instructions.

[0179] Step 5075: Generate material package rebinding instruction.

[0180] When a candidate vehicle meets the conditions, and the arrival window of the candidate vehicle's workstation and the arrival window of the material package to be re-bound meet the condition of synchronous arrival, the system generates a material package re-binding instruction. The material package re-binding instruction includes at least the identifier of the material package to be re-bound, the identifier of the originally planned vehicle, the identifier of the candidate vehicle, the identifier of the target workstation, and the re-binding status.

[0181] Furthermore, after the material package rebinding instruction is executed, the system updates the planned bound vehicle of the material package to be rebinded to a candidate vehicle and sends the update result to the binding status update process. If no candidate vehicle that meets the conditions is found, or if the candidate vehicle and the material package to be rebinded do not meet the synchronous arrival condition, the material package rebinding process is determined to be unsatisfactory, and the process proceeds to the alternative vehicle release process.

[0182] In one embodiment, step 508, namely the specific process of the alternative vehicle release disposal judgment, includes steps 5081 to 5084.

[0183] Step 5081: Determine the queue of vehicles that can be released.

[0184] The releasable vehicle queue consists of vehicles that have not yet entered the continuous transport area of ​​the target workstation and have been marked as eligible for release towards the target workstation by the preceding release status data. Vehicles in the releasable vehicle queue should not be in an abnormally frozen state, and their quality status should allow for transfer.

[0185] Furthermore, the releasable vehicle queue differs from the waiting-to-enter vehicle queue. The waiting-to-enter vehicle queue is used for screening candidate vehicles for material package re-bundling, while the releasable vehicle queue is used to determine if there are vehicles that can replace the currently awaiting assembly vehicle to enter the target workstation. The purpose of releasing replacement vehicles is not to reorder all vehicles, but to release available vehicles without altering the existing flow sequence in the continuous transport area.

[0186] Step 5082: Select alternative vehicles.

[0187] When the material package corresponding to the vehicle to be assembled at the target workstation has not arrived, has not been closed, or cannot be put into operation, the system selects vehicles from the releaseable vehicle queue in front of the target workstation that have completed the plan binding, have not entered the continuous conveying area of ​​the target workstation, have a vehicle quality status that allows flow, and whose vehicle workstation arrival window meets the synchronous arrival condition with the single vehicle material package arrival window of the plan binding as replacement vehicles.

[0188] Furthermore, the replacement vehicle must meet the synchronization condition with its own planned single-vehicle material package, not with the material package corresponding to the currently assembled vehicle. This restriction is to avoid introducing new vehicle-material inconsistencies through replacement releases.

[0189] Step 5083: Determine whether releasing the replacement vehicle changes the flow sequence of vehicles in the continuous transport area.

[0190] The system determines whether releasing a replacement vehicle will insert it between vehicles already in the continuous transport area of ​​the target workstation, or whether it will change the existing flow order of vehicles within the continuous transport area. If releasing a replacement vehicle will not change the flow order of vehicles already in the continuous transport area of ​​the target workstation, the system determines that the replacement vehicle release condition has been met.

[0191] Furthermore, when determining whether to change the flow order of vehicles that have entered the continuous transport area of ​​the target workstation, the system reads the entrance identifier of the continuous transport area, the vehicle sequence identifier within the continuous transport area, and the current position identifier of the substitute vehicle. If the substitute vehicle has not yet entered the continuous transport area of ​​the target workstation, and its release action only affects the queue of releaseable vehicles before the entrance of the continuous transport area, without changing the order of vehicles within the continuous transport area, then it is determined that releasing the substitute vehicle does not change the flow order of vehicles that have entered the continuous transport area of ​​the target workstation.

[0192] If releasing a replacement vehicle requires changing the order of vehicles in the continuous transport area, or if it would cause vehicles that have already entered the continuous transport area of ​​the target workstation to be cut in line, backed up, or reordered, then the replacement vehicle release is deemed to be unsatisfactory and will proceed to the preceding flow restriction process.

[0193] Step 5084: Generate a replacement vehicle release command and process the original vehicle to be assembled.

[0194] The system generates a replacement vehicle release command when releasing a replacement vehicle does not change the flow sequence of vehicles already in the continuous transport area of ​​the target workstation. The replacement vehicle release command includes at least the replacement vehicle identifier, the identifier of the single-vehicle material package it is planned to be bound to, the target workstation identifier, and the release status.

[0195] Furthermore, the system marks the vehicle originally scheduled for assembly as a vehicle awaiting processing and stops its release to the target workstation. This process prevents the vehicle scheduled for assembly from continuing to enter the target workstation if the corresponding material package has not arrived, is not closed, or is not ready for production, thereby reducing vehicle-material mismatch and waiting time at the target workstation.

[0196] In one embodiment, steps 601 to 604 are described as follows:

[0197] Step 601: Generate vehicle waiting instructions.

[0198] A vehicle waiting instruction includes at least the vehicle identifier, target workstation identifier, waiting status, and waiting trigger reason. This instruction is used to keep the target vehicle in a waiting state within the allowable waiting range and to continue monitoring the arrival status of the corresponding single vehicle material package during the waiting period.

[0199] Step 602: Generate a material package temporary storage instruction.

[0200] The material package temporary storage instruction includes at least the material package identifier, target workstation identifier, line-side temporary storage location identifier, and temporary storage status. This instruction is used to temporarily store the material packages of a single vehicle that arrive early to the corresponding line-side temporary storage location, preventing them from directly entering the target workstation and causing material mismatch.

[0201] Step 603: Generate material package rebinding instruction.

[0202] The material package rebinding instruction includes at least the material package identifier to be rebinded, the originally planned vehicle identifier, the candidate vehicle identifier, and the target workstation identifier. This instruction is used to update the planned vehicle of the material package to be rebinded to a candidate vehicle, and to incorporate this update result into the subsequent binding status update process.

[0203] Step 604: Generate a replacement vehicle release command.

[0204] The replacement vehicle release instruction includes at least the replacement vehicle identifier, the identifier of the single-vehicle material package it is planned to be bound to, the target workstation identifier, and the processing status of the original vehicle to be assembled. This instruction is used to release replacement vehicles that meet the synchronous arrival conditions, mark the original vehicle to be assembled as a vehicle to be processed, and stop its release to the target workstation.

[0205] Furthermore, after the various scheduling instructions generated in steps 601 to 604 are executed, the system obtains the corresponding system execution feedback. The execution feedback proceeds to step 90, which is used to update the binding status between the vehicle and the single vehicle material package, and is used to subsequently re-determine the synchronization arrival condition and binding consistency condition.

[0206] In one embodiment, steps 701 to 703 are described as follows:

[0207] Step 701: Generate the preceding rate limiting instruction.

[0208] When the aforementioned abnormal scheduling and handling methods cannot resolve the current material synchronization anomaly, the system generates a preceding rate limiting instruction based on the target workstation cycle time, the line-side temporary storage status, the material synchronization anomaly type, the preceding release status, and the subsequent receiving status. The preceding rate limiting instruction includes a limited release instruction and a prohibited release instruction.

[0209] Furthermore, when the system generates the preceding flow restriction command, it does not change the flow order of vehicles that have already entered the continuous conveying area of ​​the target workstation, but releases the constraints on vehicles that have not yet entered the continuous conveying area of ​​the target workstation and are still within the preceding release control range.

[0210] Step 702: Determine the execution range of the preceding rate limiting instruction.

[0211] The limited release command restricts the maximum number of vehicles released by the preceding process towards the target workstation within a preset time period; the prohibited release command prohibits the continued release of vehicles corresponding to material packages that have not arrived, are not closed, or cannot be put into operation. The scope of execution can be determined based on the target workstation identifier, abnormal vehicle identifier, corresponding single-vehicle material package identifier, and the status of the preceding release.

[0212] Furthermore, the maximum number of vehicles to be released is determined based on the number of vehicles that the target workstation can receive within a preset time period, the remaining availability of the line-side temporary storage space, the number of vehicles corresponding to the current material synchronization anomaly, and the subsequent receiving status. If the current release status shows that there are vehicles corresponding to material packages that have not arrived, are not closed, or cannot be put online, these vehicles are included in the prohibited release list; if the current release status shows that the target workstation still has some receiving capacity, vehicles unaffected by the current anomaly are allowed to continue to be released according to the limited release instruction.

[0213] Step 703: Record the result of the preceding rate limiting trigger.

[0214] The preceding flow restriction trigger result should include at least the target workstation identifier, the anomaly type, the content of the limited release instruction, the content of the prohibited release instruction, the trigger time, and the corresponding vehicle or material package identifier. This result is used in step 80 to determine whether the vehicle-material synchronization anomaly has been resolved based on the execution feedback.

[0215] In one embodiment, steps 801 to 804 are described as follows:

[0216] Step 801: Obtain the execution feedback of the preceding rate limiting instruction.

[0217] Execution feedback includes changes in the quantity released in the preceding sequence, changes in the receiving status of the target workstation, changes in the occupancy of the line-side temporary storage space, changes in the arrival status of the corresponding single-vehicle material package, whether the unclosed status of the material package has been released, and whether the binding status between the vehicle and the single-vehicle material package has been updated. Execution feedback is used to determine whether the preceding flow restriction has alleviated or resolved the abnormal state.

[0218] Step 802: Determine whether the material synchronization anomaly has been resolved based on the execution feedback.

[0219] The system reads the corresponding execution feedback based on the current anomaly type and re-evaluates the synchronization arrival condition and binding consistency condition. When the corresponding single-vehicle material package arrives, the unclosed state of the material package is released, the line-side temporary storage position is restored to idle, or the binding status between the vehicle and the single-vehicle material package is updated, and the release condition corresponding to the current anomaly type is met after re-evaluation, the preceding flow restriction instruction is released.

[0220] Furthermore, for the "car first, material later" anomaly, if the corresponding single-car material package arrives and the synchronization arrival condition is met again, the anomaly is determined to be resolved; for the "material first, car later" anomaly, if the line-side temporary storage position becomes available again or the vehicle station arrival window is updated and the synchronization arrival condition is met again, the anomaly is determined to be resolved; for the "car-material inconsistency" anomaly, if the binding status of the vehicle and the single-car material package is updated and the binding consistency condition is met, the anomaly is determined to be resolved; for the "material package not closed" anomaly, if the unclosed state of the material package is resolved and the material package is not in an abnormal frozen state, the anomaly is determined to be resolved.

[0221] Step 803: When the material synchronization abnormality is not resolved, determine the duration of the abnormality.

[0222] The abnormal duration indicates the time from when the material synchronization abnormality is identified to the current judgment time, and is used to determine whether to generate an abnormal freeze command or a manual review prompt.

[0223] In this embodiment, the duration of the anomaly is as follows:

[0224]

[0225] In the formula, Indicates the duration of the anomaly; Indicates the current judgment time; This indicates the start time at which the material-vehicle synchronization anomaly was detected. If... If the preset safety threshold is exceeded, an abnormal freeze command will be generated; if If the preset safety threshold is not exceeded, a manual review prompt will be generated. The preset safety threshold can be pre-set based on the target workstation's standard production cycle time, the availability of temporary storage positions along the line, and production plan requirements.

[0226] Step 804: Generate an abnormal freeze command or a manual review prompt.

[0227] An abnormal freeze command can be applied to the corresponding vehicle or the corresponding material package to prevent it from continuing its journey to the target workstation. A manual verification prompt is used to remind the corresponding system or on-site personnel to check the vehicle identifier, material package identifier, line-side temporary storage status, target workstation status, and material package closure status. The execution feedback of the abnormal freeze command or manual verification prompt proceeds to step 90, which updates the binding status between the vehicle and the material package.

[0228] In one embodiment, steps 901 to 903 are described as follows:

[0229] Step 901: Send the scheduling instruction, abnormal freeze instruction, or manual review prompt to the corresponding system.

[0230] Vehicle waiting instructions and alternative vehicle release instructions can be sent to the production execution system or target workstation control system in the corresponding system 310; material package temporary storage instructions and material package rebinding instructions can be sent to the material distribution system or target workstation control system in the corresponding system 310; abnormal freeze instructions and manual review prompts can be sent to the production execution system, target workstation control system, or quality management system in the corresponding system 310. The specific recipient is determined based on the instruction type.

[0231] Step 902: Obtain the execution feedback from the corresponding system.

[0232] Execution feedback can include vehicle waiting status, material package temporary storage status, material package rebinding completion status, substitute vehicle release status, preceding flow restriction execution status, abnormal freeze status, and manual review results. This execution feedback is used to confirm whether the scheduling instruction has been executed and to update the binding status between the vehicle and the single vehicle-specific material package.

[0233] Step 903: Update the binding status of the vehicle and the single vehicle material package based on the execution feedback.

[0234] Binding status can include planned binding status, on-site binding status, rebinding status, frozen status, and pending status. The updated binding status triggers the next round of synchronization arrival and binding consistency condition checks. Through this update process, a closed loop is formed between vehicle-material synchronization anomaly identification, anomaly scheduling handling, preceding flow limiting, freezing or review, and subsequent scheduling judgments.

[0235] Furthermore, after the binding status is updated, the system retains the vehicle identifier, material package identifier, target workstation identifier, and update time stamp before and after the update, so that the latest binding status can be used in the next round of synchronization arrival condition and binding consistency condition judgment.

[0236] like Figure 2 As shown in the figure, this embodiment of the invention also provides an industrial internet-based motor vehicle production collaborative scheduling system. The system includes a status data acquisition module 210, a plan binding module 220, a point-of-flight binding module 230, a site binding module 240, a window generation module 250, a condition judgment module 260, an anomaly identification module 270, a handling judgment module 280, an instruction generation and issuance module 290, and a binding status update module 300.

[0237] The status data acquisition module 210 is used to acquire industrial internet status data from the motor vehicle production site.

[0238] The planning binding module 220 is used to establish the planning binding relationship between vehicles and single-vehicle material packages.

[0239] The passpoint binding module 230 is used to establish passpoint binding records.

[0240] The on-site binding module 240 is used to establish on-site binding records.

[0241] The window generation module 250 is used to generate vehicle workstation arrival windows and single-vehicle material package arrival windows.

[0242] The condition judgment module 260 is used to determine the synchronization arrival condition and the binding consistency condition.

[0243] The anomaly identification module 270 is used to identify the types of anomalies in the synchronization of materials and vehicles and the restrictions on anomaly scheduling and handling.

[0244] The handling judgment module 280 is used to determine whether the abnormal scheduling handling method meets the conditions according to the preset priority, and to determine whether the abnormal vehicle-material synchronization is resolved based on the execution feedback of the preceding flow limiting instruction.

[0245] The instruction generation and issuance module 290 is used to generate and issue vehicle waiting instructions, material package temporary storage instructions, material package rebinding instructions, alternative vehicle release instructions, preceding flow restriction instructions and abnormal freeze instructions, or send manual review prompts.

[0246] The binding status update module 300 is used to update the binding status between the vehicle and the single vehicle material package based on the execution feedback.

[0247] In this embodiment, the system also interacts with the corresponding system 310, which is an external execution system or downstream execution system that receives scheduling instructions, abnormal freeze instructions or manual review prompts and provides feedback on the execution results.

[0248] The corresponding system 310 includes one or more of a production execution system, a material distribution system, a target workstation control system, and a quality management system. It is used to receive scheduling instructions, abnormal freeze instructions, or manual review prompts issued by the instruction generation and issuance module 290, and to feed back the execution results to the binding status update module 300.

[0249] Specifically, the status data acquisition module 210 executes steps 10 and 101 to 105; the plan binding module 220 executes steps 20 and 201 to 204; the point binding module 230 and the on-site binding module 240 execute steps 30 and 301 to 303; the window generation module 250 and the condition judgment module 260 execute steps 40 and 401 to 406; the anomaly identification module 270 and the handling judgment module 280 execute steps 50 and 501 to 5084; the instruction generation and issuance module 290 executes steps 60 to 80 and 601 to 804; and the binding status update module 300 executes steps 90 and 901 to 903.

[0250] Furthermore, the output of the status data acquisition module 210 serves as the input to the plan binding module 220, the window generation module 250, and the anomaly identification module 270; the output of the plan binding module 220 serves as the input to the point binding module 230, the field binding module 240, and the condition judgment module 260; the output of the window generation module 250 serves as the input to the condition judgment module 260 and the handling judgment module 280; the output of the anomaly identification module 270 serves as the input to the handling judgment module 280; the output of the handling judgment module 280 serves as the input to the instruction generation and issuance module 290; the output of the instruction generation and issuance module 290 is sent to the corresponding system 310; the execution feedback of the corresponding system 310 is sent to the binding status update module 300; and the output of the binding status update module 300 is returned to the condition judgment module 260 for the next round of judgment.

[0251] The specific execution process of each module in this system embodiment can be found in the corresponding descriptions of steps 10 to 90 and steps 101 to 903 in the above method embodiment. The data transmission relationship between modules corresponds to the data processing order in the above method embodiment. Each module in this system embodiment can be implemented by software programs, industrial control systems, servers, edge computing nodes, or functional units of existing systems in the production site. The modules can interact with each other through industrial internet communication, as long as they can complete the corresponding functions in the above method embodiment.

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

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

[0254] The above embodiments are only used to illustrate the technical solutions of the present invention, and are not intended to limit it. Although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions will not cause the essence of the corresponding technical solutions to deviate from the protection scope of the technical solutions of the embodiments of the present invention.

Claims

1. An industrial internet-based method for collaborative scheduling of motor vehicle production, characterized in that, include: Acquire industrial internet status data from the motor vehicle production site, including vehicle production status data, material delivery status data, workstation operation status data, and process connection status data; Establish a planning binding relationship between vehicles and individual vehicle material packages based on the industrial internet status data; When a vehicle with an established plan binding relationship passes through a preset passing point, a passing point binding record is established; when a single vehicle with an established plan binding relationship arrives at the target workstation line edge position, a field binding record is established. Based on the industrial internet status data, a vehicle workstation arrival window and a single vehicle material package arrival window are generated. It is determined whether the two meet the synchronous arrival conditions. Based on the plan binding relationship, the passing point binding record and the on-site binding record, it is determined whether the vehicle to be assembled at the target workstation and the single vehicle material package to be put on the line meet the binding consistency conditions. When the conditions for synchronous arrival or binding consistency are not met, identify the abnormal type of vehicle-material synchronization and the abnormal scheduling and handling restrictions, and make abnormal scheduling and handling judgments for vehicle waiting, material package temporary storage, material package rebinding and alternative vehicle release according to preset priorities. When any abnormal scheduling handling method meets the conditions, subsequent judgments are stopped and corresponding scheduling instructions are generated; When all preset exception scheduling and handling methods for the current material synchronization anomaly type are not met, a preceding flow limiting instruction is generated. Based on the execution feedback of the preceding flow restriction command, it is determined whether the abnormality of the vehicle-material synchronization has been resolved. If it has not been resolved and the duration of the abnormality exceeds the preset safety threshold, an abnormality freeze command is generated. If it has not been resolved and the duration of the abnormality does not exceed the preset safety threshold, a manual review prompt is generated. Send scheduling instructions, abnormal freeze instructions, or manual review prompts to the corresponding systems, and update the binding status of vehicles and single-vehicle material packages based on execution feedback.

2. The method according to claim 1, characterized in that, The vehicle production status data includes vehicle production sequence, vehicle configuration, vehicle check-through data, and vehicle quality status data. The material delivery status data includes single-vehicle material package identification data, single-vehicle material package arrival data, single-vehicle material package current location data, material delivery path data, and delivery equipment status data; The workstation operation status data includes line-side temporary storage status data and target workstation cycle time data; The process connection status data includes the preceding release status data and the subsequent receiving status data; The single-vehicle material package is a combination of materials pre-packaged according to the vehicle configuration corresponding to the target workstation and used for the assembly of the corresponding vehicle.

3. The method according to claim 2, characterized in that, Establishing the aforementioned plan binding relationship includes: The sequence of vehicles to enter the target workstation is determined based on the vehicle production sequence. Based on the vehicle configuration, determine the single-vehicle material requirement list for each vehicle at the target workstation; When the material code, quantity, and compatible vehicle configuration in a single vehicle material package are consistent with the single vehicle material requirement list of the corresponding vehicle, and the vehicle is not bound to other single vehicle material packages and the single vehicle material package is not bound to other vehicles, a planning binding relationship is established between the vehicle and the single vehicle material package.

4. The method according to claim 1, characterized in that, The point-passing binding record includes vehicle identification, actual point-passing time, estimated arrival time at the target workstation, and target workstation identification. The on-site binding record includes material package identifier, arrival time, line-side temporary storage location identifier, and planned binding vehicle identifier; When the vehicle identifier of the vehicle to be assembled at the target workstation is consistent with the planned vehicle identifier of the single-vehicle material package to be put on the line, the temporary storage location identifier at the line corresponds to the identifier of the target workstation, and the single-vehicle material package is not in an abnormal frozen state, the binding consistency condition is determined to be met.

5. The method according to claim 1, characterized in that, The vehicle workstation arrival window is determined by the earliest arrival time and the latest permitted arrival time of the vehicle. The earliest arrival time of the vehicle is determined based on the vehicle's actual transit time and the fastest conveying cycle from the preset transit position to the target workstation. The latest allowable arrival time of the vehicle is determined based on the standard production cycle of the target workstation and the vehicle's quality status. When the vehicle's quality status does not allow for transfer, the corresponding vehicle's arrival window will be marked as invalid. The arrival window of a single vehicle's material package is formed by the earliest arrival time and the latest allowed online time of the material package. The earliest arrival time and the latest allowed online time of the material package are determined based on the current location of the single vehicle's material package, the material delivery path, the status of the delivery equipment, the status of the line-side temporary storage location, and the time required by the target workstation. The synchronous arrival condition is that there is a time overlap between the vehicle workstation arrival window and the single vehicle material package arrival window, and the latest allowed online time of the single vehicle material package is not earlier than the earliest arrival time of the vehicle, and the latest allowed arrival time of the vehicle is not earlier than the earliest arrival time of the single vehicle material package.

6. The method according to claim 1, characterized in that, The types of abnormalities in vehicle-material synchronization include abnormalities such as vehicle-first-material-later, material-first-vehicle-later, vehicle-material inconsistency, and unclosed material package. The unclosed material package is an abnormality caused by the material code, quantity, or seal status of the material in a single vehicle's material package not meeting the single vehicle's material requirement list for the target workstation. The abnormal scheduling and handling restrictions include the conditions that the material package cannot be rebound, the material package cannot be put online, and the vehicle cannot wait. Among them, the following conditions are considered as follows: material package cannot be re-bound when it has been opened, entered the target workstation online position, or completed on-site binding confirmation; material package cannot be put online when it is in an abnormal frozen state; and vehicle cannot wait when it has entered the target workstation continuous conveying area or the vehicle's quality status does not allow it to stay.

7. The method according to claim 1, characterized in that, When the vehicle-material synchronization anomaly type is vehicle-first-material-later anomaly, and the difference between the earliest arrival time of the vehicle and the earliest arrival time of the material package does not exceed the allowed waiting time of the target workstation and the allowed dwell time of the vehicle quality status, a vehicle waiting instruction is generated. When the vehicle waiting instruction cannot make the vehicle workstation arrival window and the single vehicle material package arrival window meet the synchronous arrival conditions again, the material package rebinding process is judged. When the material synchronization anomaly type is material first, then vehicle anomaly, and there is an empty position in the line-side temporary storage position and the material package has not entered the target workstation online position, a material package temporary storage instruction is generated. When the material package temporary storage instruction cannot make the vehicle workstation arrival window and the single vehicle material package arrival window meet the synchronous arrival conditions again, and the temporarily stored single vehicle material package has not been unsealed, has not entered the target workstation online position, and has not completed the on-site binding confirmation, the material package rebinding disposal judgment is entered. If the material package rebinding disposal judgment does not meet the conditions, the disposal judgment for releasing the alternative vehicle will be initiated.

8. The method according to claim 1, characterized in that, The repackaging of the material packages includes: It was confirmed that the material package to be re-bound was unopened, had not entered the target workstation online position, and had not been confirmed for on-site binding. From the queue of vehicles waiting to enter the target workstation, select candidate vehicles that have not entered the continuous conveying area of ​​the target workstation, whose vehicle configuration is consistent with the compatible vehicle configuration of the material package to be re-bound, whose material code and quantity of the material package to be re-bound are consistent with the single vehicle material requirement list of the vehicle, whose on-site binding confirmation of other material packages has not been completed, and whose vehicle quality status allows for transfer and is not in an abnormal frozen state. When the arrival window of the candidate vehicle's workstation and the arrival window of the material package to be re-bound meet the synchronous arrival condition, a material package re-binding instruction is generated.

9. The method according to claim 1, characterized in that, The release and disposal of the alternative vehicles includes: When the material package corresponding to the vehicle to be assembled at the target workstation has not arrived, not closed, or cannot be put into operation, select the vehicle that has completed the plan binding, has not entered the continuous conveying area of ​​the target workstation, has the vehicle quality status that allows the flow, and whose vehicle workstation arrival window meets the synchronous arrival condition with the single vehicle material package arrival window of its plan binding from the release vehicle queue in front of the target workstation as the replacement vehicle. When releasing a replacement vehicle does not change the flow order of vehicles that have entered the continuous conveying area of ​​the target workstation, a replacement vehicle release command is generated, and the original vehicle to be assembled is marked as a vehicle to be processed, and its release to the target workstation is stopped. The preceding flow restriction instructions include a limited release instruction for limiting the maximum number of vehicles released by the preceding process to the target workstation within a preset time period, and a prohibit release instruction for prohibiting the continued release of vehicles corresponding to material packages that have not arrived, have not been closed, or cannot be put into service. After the preceding flow restriction command is executed, when the corresponding single vehicle material package arrives, the unclosed state of the material package is released, the temporary storage position at the line edge is restored to free, or the binding status between the vehicle and the single vehicle material package is updated, and the release condition corresponding to the current vehicle-material synchronization anomaly type is met after re-judgment, the preceding flow restriction command is released, and the synchronization arrival condition and binding consistency condition are re-judged based on the updated binding status.

10. An industrial internet-based vehicle production collaborative scheduling system, characterized in that, The system is used to implement the industrial internet-based motor vehicle production collaborative scheduling method according to any one of claims 1 to 9, the system comprising: The status data acquisition module is used to acquire industrial internet status data at the motor vehicle production site. The industrial internet status data includes vehicle production status data, material delivery status data, workstation operation status data, and process connection status data. The plan binding module is used to establish the plan binding relationship between vehicles and single-vehicle material packages; The passpoint binding module is used to create passpoint binding records; The on-site binding module is used to establish on-site binding records; The window generation module is used to generate vehicle workstation arrival windows and single-vehicle material package arrival windows; The condition judgment module is used to determine whether the arrival window of the vehicle workstation and the arrival window of the single vehicle material package meet the synchronous arrival condition, and to determine whether the vehicle to be assembled at the target workstation and the single vehicle material package to be put on the line meet the binding consistency condition. The anomaly identification module is used to identify the types of anomalies in material synchronization and the constraints on anomaly scheduling and handling. The handling judgment module is used to determine whether the corresponding abnormal scheduling and handling method meets the conditions according to the abnormality identification module and the abnormality scheduling and handling restrictions. When all the preset abnormality scheduling and handling methods for the current abnormality type of abnormality are not met, the preceding flow limit judgment is triggered, and the abnormality of abnormality is determined based on the execution feedback of the preceding flow limit instruction. The instruction generation and issuance module is used to generate and issue vehicle waiting instructions, material package temporary storage instructions, material package rebinding instructions, alternative vehicle release instructions, preceding flow restriction instructions and abnormal freeze instructions to the corresponding systems, or send manual review prompts to the corresponding systems. The binding status update module is used to update the binding status between vehicles and single-vehicle material packages based on execution feedback.

Images