A dynamic management method for a spacecraft assembly process execution sequence

Abstract

The application discloses a dynamic management method for a spacecraft assembly process execution sequence, which combines a unified process template and dynamic parameters and encapsulates the same as a structured process object; a GroupOrder is configured according to a process sequence relationship, and alpha, beta and gamma are configured according to material, tooling fixture and supporting material states obtained by a station terminal; priority is calculated by Imp (process) = gShield * GroupOrder - (alpha + beta + gamma) * sShield, wherein gShield > 6 * sShield; an Imp container is constructed and sorted according to the Imp value, and a SortProList containing a parallel process set and a resource start state identifier is generated. When the resource state changes, the Imp value of the affected process is recalculated, and the container, sequence and locking state are updated. The application realizes in-process matching priority and dynamic sequence updating while maintaining a forced process sequence relationship.

Description

Technical Field

[0001] This invention belongs to the field of intelligent manufacturing and digital assembly technology for spacecraft, specifically relating to a dynamic control method, system, computer equipment, computer-readable storage medium, and computer program product for spacecraft assembly process execution sequence based on the acquisition of resource status at the assembly site, quantification of process priorities, and dynamic updating of the sequence. Background Technology

[0002] Spacecraft assembly is typically characterized by a wide variety of products in small batches, complex assembly objects, strict process sequence requirements, and frequent changes in on-site resource conditions. There may be a mandatory sequence between different assembly processes, and the feasibility of each process is also affected by the availability of components and materials, the occupancy of tooling and fixtures, and the availability of supporting materials.

[0003] In some assembly management methods, the sequence of processes is pre-programmed and fixed by process engineers. When situations arise on the assembly floor such as missing parts, occupied tooling fixtures, or incomplete sets of supporting materials, the pre-fixed process sequence cannot reflect changes in resource status in a timely manner. On-site personnel need to rely on manual judgment and temporary coordination to determine the executable processes, which can easily lead to waiting, repeated verification, and incorrect process selection.

[0004] While some process scheduling methods can adjust the process sequence based on resource status, they lack a hierarchical representation of mandatory process order and resource availability. When different types of constraints directly participate in the same sequencing, low-priority resource status may interfere with high-priority process order; simultaneously, ordinary linear queues struggle to simultaneously represent serial nodes, sets of parallelizable processes, and the locked status of processes with insufficient resources. Therefore, a technical solution is needed that can dynamically generate and update the process execution sequence based on the resource status of the assembly site without disrupting the mandatory process logic. Summary of the Invention

[0005] The purpose of this invention is to provide a dynamic control method for the execution sequence of spacecraft assembly processes, in order to solve the problems that fixed process sequences are difficult to adapt to dynamic changes in assembly site resources, mutual interference between different priority constraints, and difficulty in uniformly expressing serial and parallel processes and resource locking states.

[0006] To achieve the above objectives, this invention provides a dynamic control method for the execution sequence of spacecraft assembly processes. This method constructs a process template library and a dynamic parameter library, binds and combines dynamic parameters with unified process templates, and encapsulates them into structured process objects corresponding to each process to be executed. It configures the process group priority number (GroupOrder) according to the sequential constraints of the spacecraft assembly process, and configures material coefficients α, tooling / fixture coefficients β, and supporting material coefficients γ according to the material availability status, tooling / fixture status, and supporting material availability status.

[0007] The system calculates the process importance priority Imp(process) for each process to be executed according to the following formula: Imp(process)=gShield×GroupOrder-(α+β+γ)×sShield Where Imp(process) is smaller, the sorting priority is higher; gShield is the process group priority constraint masking coefficient, and sShield is the resource priority constraint masking coefficient. When α, β, and γ are 1 or -1 respectively, GroupOrder is an integer greater than or equal to 1, and gShield > 6 × sShield and sShield > 0, the minimum difference between any two different GroupOrders caused by process group priority is greater than the maximum difference caused by resource status, thereby avoiding the reversal of forced process sequence due to resource status changes.

[0008] The system constructs Imp containers using Imp(process) as the key, grouping execution processes with the same Imp(process) into the same Imp container. Different Imp containers are then sorted in ascending order of Imp(process) and expanded sequentially to obtain the dynamic execution sequence SortProList. For multiple resource-available processes within the same Imp container, a set of processes that can be executed in parallel or randomly is output. For processes with insufficient resources, a resource lock flag is set, but they are still retained in the Imp container and SortProList.

[0009] When the status of material availability, tooling / fixture availability, or supporting material availability changes, the system identifies the affected pending processes, updates the corresponding α, β, or γ, recalculates Imp (process), and updates the Imp container, SortProList, and resource start status flags. After resources are replenished, the system releases the resource lock flag for the corresponding process.

[0010] Furthermore, the structured process object includes process ID, process name, product number, workstation ID, process template identifier, dynamic parameter set, bill of materials, tooling and fixture list, supporting material list, GroupOrder, α, β, γ, Imp (process), execution status, and resource start status identifier.

[0011] Furthermore, multiple processes with the same GroupOrder do not have a preset mandatory sequence before resource constraints are considered. The system sorts them within the group according to the Imp (process) and resource availability of each process. Processes with different GroupOrders are sorted according to a mandatory sequence determined in advance by the process engineers.

[0012] Furthermore, the resource status is mainly collected by the workstation scanning terminal, or it can be manually corrected by the scheduler or process engineer in the digital management system; when there is a conflict between the scanning status and the manually corrected status, the manually confirmed corrected status shall be taken as the current valid status.

[0013] Furthermore, sequence updates can be triggered by workstation terminal scanning, manual confirmation in the digital management system, or periodic background polling. Periodic background polling is used to correct inconsistencies in resource status caused by data synchronization delays.

[0014] Compared with the prior art, the present invention has at least the following beneficial effects: First, by combining and encapsulating a unified work step template with dynamic parameters, the process data is stored and processed in the form of structured objects, which facilitates the reuse of work step templates among different assembly objects and workstations, and provides a unified data foundation for resource status matching and dynamic sorting.

[0015] Second, by satisfying the hierarchical shielding relationship of gShield > 6 × sShield, the forced process sequence relationship and resource status are placed in the same computable model, so as to achieve the priority ordering of kitting within the same process group while maintaining the sequence relationship of different process groups.

[0016] Third, by organizing processes with the same Imp value into sequence nodes through the Imp container, the locked state of serial nodes, parallelizable process sets, and resource-unstartable processes can be expressed in the same data structure, avoiding the loss of processes lacking materials or resources from the global sequence.

[0017] Fourth, after the resource status changes, only the coefficients and Imp values ​​of the affected processes are updated, and the sequence is updated by migrating the processes between Imp containers, thereby improving the assembly site's responsiveness to changes in status such as material arrival, tooling release, and replenishment of supporting materials.

[0018] Fifth, by combining data collection via barcode scanning, manual correction, and periodic polling, and stipulating that conflicting states must be confirmed manually, the impact of asynchronous states from multiple sources on the process sequencing results can be reduced. Attached Figure Description

[0019] Figure 1 This is a schematic diagram illustrating the combination and encapsulation of a unified work step template and dynamic parameters into a structured process object in this invention. Figure 2 This is a schematic diagram of the process groups and their sequential relationships in this invention; Figure 3 This is a flowchart illustrating the generation of dynamic process execution sequences based on the Imp container in this invention.

[0020] Figure labeling: 100, Step template library; 101, Positioning step template; 102, Fastening step template; 103, Insertion step template; 104, Adjustment step template; 105, Inspection step template; 200, Dynamic parameter library; 201, Assembly parameters; 202, Torque parameters; 203, Clearance parameters; 204, Datum parameters; 205, Tolerance parameters; 300, Parameter binding module; 400, Step combination; 500, Structured process object; 601, Load information for the current n processes to be executed; 602, Create an empty Imp container set; 603, i=1; 604, Calculate the Imp(process) of the i-th process to be executed; 605, Add the process to be executed to the Imp container; 606, Increment i; 607, Determine if i is greater than n; 608, Sort ProList by Imp value; 609, Obtain the process queue. Detailed Implementation

[0021] The present invention will be further described below with reference to the accompanying drawings and specific embodiments. It should be understood that the following embodiments are used to explain the present invention, and are not intended to limit the scope of protection of the present invention. Without departing from the core concept of the present invention, those skilled in the art can make adaptive adjustments to the specific field names, data interfaces, triggering cycles, and terminal presentation methods.

[0022] In this implementation, "pending execution process" refers to an assembly process that has not yet been completed and entered the current scheduling scope; "resource start status" is used to characterize whether the materials, tooling fixtures, and supporting materials meet the resource conditions of the process. The actual execution of the process should also comply with the mandatory sequence relationship characterized by GroupOrder and the execution status in the structured process object.

[0023] In the actual system, the field used to identify the process group to which a process belongs can be named "Container ID". This Container ID and GroupOrder represent the same process group identifier. To avoid confusion, this specification will uniformly refer to this field as GroupOrder. The Imp container, dynamically created based on Imp(process), is a temporary data structure during the sorting process and is different from the process group identifier mentioned above.

[0024] Example 1: Process Information Encapsulation like Figure 1 As shown, the spacecraft assembly digital management system constructs a process step template library 100. The process step template library 100 is used to store atomic-level unified process step templates, which may include positioning process step template 101, fastening process step template 102, insertion process step template 103, adjustment process step template 104, and detection process step template 105.

[0025] The system also constructs a dynamic parameter library 200 to store personalized parameters corresponding to different spacecraft, different assembly objects, or different assembly stations. Dynamic parameters may include assembly parameters 201, torque parameters 202, clearance parameters 203, datum parameters 204, and tolerance parameters 205.

[0026] When a specific process to be executed is formed, the parameter binding module 300 selects at least one dynamic parameter from the dynamic parameter library 200 according to the process configuration, and binds it with at least one unified process template in the process template library 100. Multiple bound processes can be combined by the process combination 400 to form a process combination result that matches the specific assembly object. The system encapsulates the process combination result into a structured process object 500 and stores it in the process information database.

[0027] A structured process object 500 can include at least the following: process ID, process name, product number, workstation ID, step template identifier, dynamic parameter set, bill of materials, tooling and fixture list, supporting material list, GroupOrder, α, β, γ, Imp(process), execution status, and resource start status identifier. Among these, the bill of materials, tooling and fixture list, and supporting material list are used to establish the association between the process and on-site resources; α, β, γ, and Imp(process) are fields that can be updated according to changes in on-site status.

[0028] Example 2: Process Group Constraints and Resource Status Acquisition like Figure 2 As shown, process engineers configure GroupOrders for each process according to the spacecraft assembly process logic. Figure 2 In this process, process 1 belongs to process group 1, process 2 belongs to process group 2, process 3 and process 4 both belong to process group 3, and process 5 belongs to process group 4; there is a mandatory sequential relationship between process group 1, process group 2, process group 3 and process group 4.

[0029] Multiple processes within the same GroupOrder are not subject to a predetermined mandatory order before resource constraints are considered. For example, processes 3 and 4 belong to the same stage in terms of process logic and can be executed in parallel or arbitrarily in sequence. During actual scheduling, the system calculates their respective Imp(process) based on their α, β, and γ values, thereby forming the group order.

[0030] Material constraints characterize whether the required parts and components for the process to be executed are complete. If the materials are complete, then α=1; if there is a shortage, then α=-1. Tooling and fixture constraints characterize whether the required tooling and fixtures for the process to be executed are complete and unused. If this condition is met, β=1; otherwise, β=-1. Matching material constraints characterize whether matching materials such as consumables are complete. If this condition is met, γ=1; otherwise, γ=-1.

[0031] Resource status is primarily obtained from workstation barcode scanning terminals. After operators scan materials, tooling fixtures, or supporting materials, the terminal sends the corresponding resource identifier and status to the digital management server. Schedulers or process engineers can also manually correct resource statuses within the digital management system. When a conflict arises between the scanned status and the manually corrected status, the manually confirmed corrected status takes precedence.

[0032] When the status of any resource changes, the system matches the resource identifier in the bill of materials, tooling list, or supporting material list of the structured process object to determine the affected process to be executed, and only updates the resource coefficient of the corresponding process.

[0033] Example 3: Imp value calculation and constraint masking The system calculates the priority of each process to be executed according to the following formula: Imp(process)=gShield×GroupOrder-(α+β+γ)×sShield In this context, a smaller Imp(process) value indicates that the corresponding process to be executed appears earlier in the SortProList. gShield is used to maintain the mandatory order between different process groups, while sShield is used to adjust the sorting based on resource availability within the same process group.

[0034] Since α, β, and γ all take values ​​of 1 or -1, the values ​​of α+β+γ are 3, 1, -1, or -3. The maximum difference in Imp(process) caused by resource status between any two processes is 6×sShield. Since GroupOrder is an integer, the minimum difference between different GroupOrders is 1; therefore, when gShield > 6×sShield and sShield > 0, even if all resources of the subsequent process group are complete and all resources of the preceding process group are incomplete, the subsequent process group will not be scheduled before the preceding process group.

[0035] In one specific implementation, gShield is set to 100, and sShield is set to 0.1. If GroupOrder=1 and α=β=γ=1, then Imp(process)=99.7; if GroupOrder=1 and only the materials are not fully matched, i.e., α=-1 and β=γ=1, then Imp(process)=99.9; if two types of resources are not satisfied, then Imp(process)=100.1; if all three types of resources are not satisfied, then Imp(process)=100.3. Thus, under the default parameters, the decimal part of 0.7 can be used to indicate that all three types of resources are fully matched.

[0036] For multiple processes with the same GroupOrder, processes with all resources available have a smaller Imp (process) and are therefore prioritized over processes lacking materials or resources. For processes with different GroupOrders, the priority of process groups takes precedence over the availability of resources.

[0037] Example 4: Imp Container Construction and SortProList Generation like Figure 3 As shown, the system first loads the information of the current n processes to be executed 601, and creates an empty Imp container set 602. The system sets i=1 in step 603, and calculates the Imp(process) of the i-th process to be executed in step 604.

[0038] The system determines whether an Imp container with the key Imp(process) already exists in the Imp container set. If it exists, the i-th process to be executed is added to the corresponding Imp container; if it does not exist, the corresponding Imp container is created, the i-th process to be executed is added to the created Imp container, and the Imp container is added to the Imp container set. The above process corresponds to step 605.

[0039] After classifying the i-th pending process, the system executes step 606, incrementing i, and then checks in step 607 whether i is greater than n. If i is not greater than n, the system returns to step 604 to continue processing the next pending process; if i is greater than n, it means that all pending processes have been classified into the corresponding Imp container.

[0040] The system sorts the Imp containers in the Imp container set in ascending order by Imp(process), and expands them in the sorted order to obtain SortProList step 608 and process queue step 609. Each Imp container is a sequence node in SortProList, and the node data can include at least Imp(process), a set of process IDs, and the resource start status identifier of each process.

[0041] If an Imp container contains multiple resource-available operations, these operations can be output as a set of operations that can be executed in parallel or randomly. If an Imp container contains only one resource-available operation, that operation is output as a serial node. Operations lacking materials or resources are marked as resource-unavailable and have a resource lock flag set, but they are still retained in the corresponding Imp container and SortProList and are not removed from the global sequence due to temporary material or resource shortages.

[0042] The workstation terminal displays or calls the process nodes according to SortProList. When actually starting work, in addition to the resource start status being startable, the mandatory prerequisite conditions determined by GroupOrder and execution status should also be met to avoid skipping mandatory prerequisite processes that have not yet been completed.

[0043] Example 5: Dynamic Sequence Update Dynamic updates can be triggered by at least one of the following methods: First, workstation terminal scanning trigger: When operators scan materials, tooling fixtures, or supporting materials, the resource coefficients of the relevant processes are updated synchronously. Second, manual confirmation trigger: After the scheduler or process engineer modifies the resource status in the digital management system and confirms it, the sequence update is initiated. Third, timed polling trigger: The background polls the resource status according to a preset period to correct inconsistencies caused by data synchronization delays.

[0044] After an update is triggered, the system determines the affected pending processes based on the changed resource identifier, updates the corresponding α, β, or γ, and recalculates Imp(process). If the recalculated Imp(process) differs from the original value, the system removes the process from the original Imp container and adds it to an Imp container with the new Imp(process) as the key; if the new Imp container does not exist, a new Imp container is created; if the original Imp container no longer contains processes, the empty container can be deleted.

[0045] Subsequently, the system reorders the Imp containers in ascending order of Imp (process), and updates SortProList and resource start status flags. For processes that were previously locked due to material or resource shortages, when their α, β, and γ are all updated to 1, the system removes the resource lock flag and updates their resource start status to startable.

[0046] Example 6: Dynamic Sorting Example The following is Figure 2 The following five processes illustrate the dynamic sorting process. Assume gShield = 100 and sShield = 0.1. For process 1, GroupOrder = 1 and all three types of resources are complete, so Imp(process) = 99.7; for process 2, GroupOrder = 2 and all three types of resources are complete, so Imp(process) = 199.7; for process 3, GroupOrder = 3 and all three types of resources are complete, so Imp(process) = 299.7; for process 4, GroupOrder = 3 and materials are incomplete, but tooling, fixtures, and supporting materials are complete, so Imp(process) = 299.9; for process 5, GroupOrder = 4 and all three types of resources are complete, so Imp(process) = 399.7.

[0047] At this point, the Imp containers are, in order: process 1 in container 99.7, process 2 in container 199.7, process 3 in container 299.7, process 4 in container 299.9, and process 5 in container 399.7. Process 4 remains in SortProList but is marked as resource-unstartable. Although process 5 has all its resources, it is still ranked after process group 3, thus maintaining the mandatory priority relationship between process groups.

[0048] Once the materials required for process 4 arrive and are confirmed by barcode scanning, α is updated from -1 to 1, and the Imp (process) value of process 4 changes from 299.9 to 299.7. The system then migrates process 4 to container 299.7. If process 3 is not yet completed at this time, then process 3 and process 4 are in the same Imp container and both are resource-available for execution, and can be output as a set of parallel processes within the same process group; if process 3 has already been completed, then only process 4 is retained in the set of processes to be executed.

[0049] Example 7: System, Equipment, and Program Products The dynamic control system for the execution sequence of spacecraft assembly processes includes a digital management server and workstation terminals. The digital management server may include a process encapsulation module, a status acquisition module, a constraint configuration module, a priority calculation module, a container sorting module, a resource start-up status control module, and a dynamic update module. Each module can be implemented by software, hardware, or a combination of both.

[0050] The computer device may include a processor, memory, and a communication interface. The memory stores computer programs or instructions. When the processor executes these programs or instructions, it performs the aforementioned steps of encapsulating process information, acquiring status, calculating Imp values, sorting Imp containers, locking resources, and dynamically updating. The workstation terminal exchanges resource status, SortProList, and resource start-up status identifiers with the digital management server through the communication interface.

[0051] The above method can also be implemented by a computer program or instructions stored in a computer-readable storage medium, or provided in the form of a computer program product. The computer-readable storage medium can be a non-transitory medium capable of storing program code.

[0052] The above description is merely a preferred embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent substitutions, or improvements made within the spirit and principles of the present invention should be included within the scope of protection of the present invention.

Claims

1. A method for dynamic control of the execution sequence of spacecraft assembly processes, applied to a spacecraft assembly digital management system including a digital management server and workstation terminals, characterized in that, include: S1. Construct a process template library and a dynamic parameter library. Bind and combine the dynamic parameters selected from the dynamic parameter library with the unified process template in the process template library to encapsulate and obtain the structured process object corresponding to each process to be executed. S2. Based on the sequential constraints of the spacecraft assembly process, configure a process group priority number GroupOrder for each structured process object, and configure a material coefficient α, a tooling coefficient β, and a matching material coefficient γ according to the material availability status, tooling fixture status, and matching material availability status obtained by the workstation terminal; wherein, GroupOrder is an integer greater than or equal to 1, α=1 when materials are available, α=-1 when materials are not available, β=1 when tooling fixtures are available and not occupied, otherwise β=-1, γ=1 when matching materials are available, otherwise γ=-1; S3. Calculate the process importance priority Imp(process) of each process to be executed according to Imp(process) = gShield × GroupOrder - (α + β + γ) × sShield. The smaller Imp(process) is, the higher the sorting priority is. gShield is the process group priority constraint masking coefficient and sShield is the resource priority constraint masking coefficient. gShield > 6 × sShield and sShield > 0, so that the sorting of different processes to be executed in GroupOrder is not reversed due to changes in α, β and γ. S4. Construct Imp containers using Imp(process) as the key. Group execution processes with the same Imp(process) into the same Imp container, and group execution processes with different Imp(process) into different Imp containers. Arrange the Imp containers in ascending order of Imp(process) and expand them sequentially to generate a dynamic process execution sequence SortProList. At the same time, generate resource start status identifiers based on α, β, and γ. When α=β=γ=1, mark the corresponding execution process as resource startable. Otherwise, mark the corresponding execution process as resource unstartable and set a resource lock identifier. Execution processes with unstartable resources are still retained in the corresponding Imp container and SortProList. S5. Output the SortProList and resource start status flag to the workstation terminal; when the material set status, tooling fixture status, or supporting material set status changes, determine the affected pending process, update the corresponding α, β, or γ, recalculate the Imp(process) of the affected pending process, and update the Imp container, SortProList, and resource start status flag accordingly; when the affected pending process satisfies α=β=γ=1, release its resource lock flag.

2. The dynamic control method for the execution sequence of spacecraft assembly processes according to claim 1, characterized in that, The process step template library includes at least one of positioning process step templates, fastening process step templates, insertion process step templates, adjustment process step templates, and inspection process step templates; the dynamic parameter library includes at least one of assembly parameters, torque parameters, clearance parameters, datum parameters, and tolerance parameters; the structured process object includes at least process ID, process name, product number, workstation ID, process template identifier, dynamic parameter set, bill of materials, tooling and fixture list, supporting material list, GroupOrder, α, β, γ, Imp (process), execution status, and resource start status identifier.

3. The dynamic control method for the execution sequence of spacecraft assembly processes according to claim 1, characterized in that, The sequential constraints include at least one of the following: sequential constraints between a single process and another single process, sequential constraints between a process group and another process group, and sequential constraints between a process group and a single process; multiple processes to be executed with the same GroupOrder do not have a preset mandatory sequential order, and are sorted within the process group according to their respective Imp (process) and resource start status.

4. The dynamic control method for the execution sequence of spacecraft assembly processes according to claim 2, characterized in that, When the status of any material, tooling fixture, or supporting material changes, the material list, tooling fixture list, or supporting material list of each structured process object is matched according to the resource identifier of the status change to determine the affected pending process.

5. The dynamic control method for the execution sequence of spacecraft assembly processes according to claim 1, characterized in that, The default value of gShield is 100, and the default value of sShield is 0.

1. When α=β=γ=1, Imp(process)=100×GroupOrder-0.3, and the decimal part of Imp(process) is 0.7, which is used to indicate that the materials, tooling fixtures and supporting materials of the corresponding process to be executed are all in a complete set.

6. The dynamic control method for the execution sequence of spacecraft assembly processes according to claim 1, characterized in that, The steps for constructing the Imp container include: loading the information of the current n processes to be executed and creating an empty set of Imp containers; setting i=1 and calculating the Imp(process) of the i-th process to be executed; determining whether there is an Imp container with the Imp(process) as the key in the set of Imp containers; if it exists, adding the i-th process to be executed to the corresponding Imp container; if it does not exist, creating the corresponding Imp container and adding the i-th process to be executed to the created Imp container; incrementing i and repeating the process until the classification of the n processes to be executed is completed.

7. The dynamic control method for the execution sequence of spacecraft assembly processes according to claim 1, characterized in that, Each Imp container serves as a sequence node in the SortProList; for an Imp container containing multiple executable processes with available resources, the multiple executable processes are output as a set of processes that can be executed in parallel or randomly; for an Imp container containing a single executable process with available resources, the executable process is output as a serial process node; executable processes with unavailable resources remain in the corresponding Imp container and are not considered as executable candidates.

8. The method for dynamic control of the execution sequence of spacecraft assembly processes according to claim 1, characterized in that, The status of material completeness, tooling and fixture status, and supporting material completeness are collected by the workstation barcode scanning terminal and / or manually corrected by the scheduler or process engineer in the spacecraft assembly digital management system; when there is a conflict between the status collected by barcode scanning and the status corrected manually, the corrected status confirmed by manual verification shall be taken as the current valid status.

9. The method for dynamic control of the execution sequence of spacecraft assembly processes according to claim 1, characterized in that, The methods for triggering updates to the Imp container and SortProList include at least one of the following: workstation terminal scanning trigger, manual confirmation trigger in the digital management system, and background periodic polling trigger; the background periodic polling is used to correct resource status inconsistencies caused by data synchronization delays.

10. A dynamic control system for the execution sequence of spacecraft assembly processes, comprising a digital management server and workstation terminals, characterized in that, The digital management server includes: a process encapsulation module, used to bind and combine dynamic parameters with a unified process template to encapsulate a structured process object corresponding to the process to be executed; a status acquisition module, used to acquire the material availability status, tooling and fixture status, and matching material availability status; a constraint configuration module, used to configure GroupOrder, α, β, and γ; a priority calculation module, used to calculate Imp(process) according to Imp(process) = gShield × GroupOrder - (α + β + γ) × sShield, where gShield > 6 × sShield and sShield > 0; a container sorting module, used to construct Imp containers with Imp(process) as the key, sort each Imp container in ascending order, and expand it to generate SortProList; a resource start-up status control module, used to generate resource start-up status identifiers according to α, β, and γ, and output SortProList and resource start-up status identifiers to the workstation terminal; and a dynamic update module, used to recalculate the Imp(process) of the affected process to be executed and update the Imp container, SortProList, and resource start-up status identifiers when any resource status changes.

Images