Multi-type multi-ship parallel construction collaborative scheduling management and control system and method

Abstract

The application provides a multi-type multi-ship parallel construction collaborative scheduling management and control system and method. The system comprises: a bottom layer global support base unit, which is connected with an Aveva Marine ship design system, an SAP supply chain system and / or a workshop terminal externally, and is connected with an upper layer business domain unit internally, and stores all generated business data in a unified database; the upper layer business domain unit, a production plan domain, is used for generating corresponding process level engineering decomposition standards, standardized engineering quantities and work hour calculation results, simultaneously obtaining resource allocation schemes including site equipment, materials and team manpower, and outputting resource constraint conditions to generate multi-level production plans; a site execution domain, which implements production plans according to execution benchmarks including production plans, standardized engineering quantities, work hour calculation results and resource allocation schemes, collects site performance data and returns all production plan domains, and drives dynamic iteration optimization of execution benchmarks.

Description

Technical Field

[0001] This invention relates to the fields of digital shipbuilding, production scheduling and computer data processing technology, specifically to a collaborative scheduling and control system and method for parallel construction of multiple types of ships. Background Technology

[0002] Shipbuilding is a typical discrete and complex manufacturing industry, characterized by the parallel production of multiple ship types, sections, and processes. Existing construction management systems have the following technical deficiencies: (1) The data standards for quantity, time and planning are not consistent, and the system has a one-way and fragmented interaction: Traditional quantity statistics rely on manual input. The quantity software only outputs data to the planning module in one direction. After the production plan is completed, it cannot send the process decomposition standard back to the quantity and time system. The quantity and time calculation lack a unified process benchmark, and the deviation of the quantity and time calculation is large.

[0003] (2) Resource scheduling is independent and fragmented, and conflicts between multiple ships cannot be predicted: The four core resource subsystems of site, crane, steel plate material and labor are independently managed and lack a unified collaborative optimization model; when multiple ships are built in parallel, conflicts such as shipyard / column occupancy, crane hoisting queues, steel plate shortages, and imbalance between supply and demand of labor for different types of work are likely to occur, resulting in both idle resources and resource shortages, and a longer construction cycle.

[0004] (3) The plan is disconnected from the working hours and the control is coarse: Traditional production planning only compiles monthly / major node overall plans without linking real-time data on material quantity, manpower, and site; working hours rely on post-event statistics, lacking automatic matching of standard working hours, prediction of planned working hours, and early warning mechanism for working hour deviation, making it impossible to accurately calculate the construction cost of a single ship or a single process.

[0005] (4) The two-way disconnect between on-site execution and planning: The workshop production process lacks real-time data collection and automatic progress feedback channels. Plan adjustments rely solely on manual issuance, resulting in on-site delays and the inability to identify process bottlenecks in real time, thus failing to achieve closed-loop management of "plan issuance - on-site execution - data feedback - dynamic optimization".

[0006] (5) No integrated full-chain collaborative architecture: The ship management tools on the market only cover a single business scenario (e.g., only yard / only planning / only manpower), and there is no integrated system covering the entire chain of material collection, resource optimization, multi-level planning, time management and workshop site monitoring. It cannot support global overall planning and scheduling in the scenario of batch synchronous construction of multiple types of ships.

[0007] Existing technical descriptions, reports, and domestic and international materials only address localized business optimization for a single shipyard and do not construct a seven-layer integrated collaborative architecture. This fails to solve the challenge of global linkage and scheduling of multi-dimensional resources, plans, and on-site data in multi-ship parallel scenarios. Summary of the Invention

[0008] To address the aforementioned shortcomings in the existing technology, this invention provides a collaborative scheduling and control system and method for the parallel construction of multiple types of ships.

[0009] According to a first aspect of the present invention, a collaborative scheduling and control system for parallel construction of multiple types of ships is provided, comprising: a bottom-level global support base unit and an upper-level business domain unit; wherein: The underlying global support base unit interfaces with the Aveva Marine ship design system, SAP supply chain system and / or workshop terminals externally, and communicates with the upper-level business domain unit internally. It stores all business data generated by the upper-level business domain unit into a unified database, and issues collaborative scheduling instructions to the upper-level business domain unit based on the global data to drive the upper-level business domain unit to recalculate the specified production plan and / or resource allocation scheme. The upper-level business domain unit includes: a production planning domain subunit and a field execution domain subunit; wherein: The production planning sub-unit is used to generate corresponding process-level engineering decomposition standards, standardized engineering quantities, and time calculation results based on the total construction period of multiple ships and ship design data files. At the same time, it obtains resource allocation schemes including site equipment, steel plate issuance, and team manpower based on resource requirements, and uses site load, steel plate inventory, and team manpower load as resource constraints. It integrates engineering quantities and time calculation coupling constraints with resource constraints to generate multi-level production plans. The multi-level production plans, standardized engineering quantities, time calculation results, and resource allocation schemes are sent to the field execution sub-unit as execution benchmarks. The on-site execution domain subunit is used to implement the production plan according to the execution benchmark. It uses the workshop terminal to collect on-site performance data in real time, including start and finish times, finished quantity, actual working hours, site and equipment occupancy, steel plate requisition, and team manpower on duty, and feeds the data back to the production plan domain to drive dynamic iterative optimization of various execution benchmarks.

[0010] According to a second aspect of the present invention, a method for collaborative scheduling and control of parallel construction of multiple types of ships is provided, comprising: Based on the total construction period of multiple ships and ship design data files, corresponding process-level engineering decomposition standards, standardized engineering quantities and time calculation results are generated. Based on resource requirements, a resource allocation plan is obtained, including site and equipment, steel plate outbound and team manpower, and site load, steel plate inventory and team manpower load are used as resource constraints. By integrating standardized engineering quantities and time calculation results, coupling constraints between engineering quantities and time calculation are obtained, and multi-level production plans are generated in combination with the resource constraints. The execution benchmark is formed by utilizing the multi-level production plan, standardized engineering quantities, time calculation results, and resource allocation scheme. Production plans are implemented based on the aforementioned execution benchmarks, and real-time data on on-site performance, including start and completion times, completed quantities, actual working hours, site and equipment occupancy, steel plate requisition, and on-duty personnel in work teams, are collected to drive dynamic iterative optimization of various execution benchmarks. Generate collaborative scheduling instructions based on global data, and recalculate the specified production plan and / or resource allocation scheme based on the collaborative scheduling instructions.

[0011] According to a third aspect of the present invention, a computer device for collaborative scheduling and management of parallel construction of multiple types of ships is provided, comprising a cloud server cluster as the backend and a local terminal as the frontend; the cloud server cluster is deployed with the collaborative scheduling and management system for parallel construction of multiple types of ships described above; wherein, the underlying global support base unit, production planning domain subunit, and field execution domain subunit of the collaborative scheduling and management system for parallel construction of multiple types of ships adopt a Spring Cloud microservice architecture to implement backend business services, and form a bidirectional interconnection link relying on Dubbo RPC and RocketMQ; the local terminal is used to provide access clients for the production planning domain subunit and the field execution domain subunit, as well as field interaction frontend and workshop terminal client; wherein, the access client is used to access the corresponding business services in the cloud server cluster, and display production plans, standardized engineering quantities, work hour calculation results, and resource configuration schemes; the field interaction frontend is used to display field performance data; the workshop terminal client is used to obtain field performance data and send the data to the cloud server cluster.

[0012] By adopting the above technical solution, the present invention has at least one of the following beneficial effects compared with the prior art: This invention constructs a support base that combines a unified underlying database with global scheduling, solving the problems of data dispersion and inconsistent scheduling instructions in multiple subsystems. Data from the same source is achieved throughout the system, and data interoperability efficiency is greatly improved.

[0013] This invention adopts a microservice loosely coupled architecture, with seven subsystems that can be deployed independently, split and expanded as needed, and adapted to the application of various ship assembly plants of all sizes.

[0014] This invention achieves fully automated analysis and verification of work quantities, eliminating human error. By docking with the ship's 3D design model, it automatically extracts four-level layered quantities and incorporates multiple intelligent verification rules to replace manual data entry, improving the accuracy of quantity data by over 95% and ensuring the accuracy of plans, work hours, and resource calculations from the source.

[0015] This invention achieves intelligent optimization of global resources for multiple objectives, significantly reducing resource conflicts. By integrating three-dimensional optimization algorithms for site equipment, steel plate materials, and manpower, it automatically avoids competition for tire positions, cranes, materials, and manpower in multi-ship parallel scenarios, greatly improving site utilization, reducing idle manpower hours, and significantly reducing the time spent on steel plate stacking and handling.

[0016] This invention achieves closed-loop management by combining hierarchical linkage planning with standardized work hours. By automatically generating three-level plans (plant, workshop, and work team) based on material quantity and resource constraints, and automatically calculating the work hours of the entire process using a standard library, it realizes full-process cost control, including pre-budgeting, in-process monitoring, and post-analysis, significantly improving the controllability of the single-ship construction period.

[0017] This invention achieves two-way real-time closed-loop control between the field and the dispatching system. By collecting execution data in real time through workshop terminals and using it to drive dynamic adjustments to resources and plans, it automatically identifies production bottlenecks and issues early warnings, eliminating the need for manual reporting at each level and significantly improving plan response efficiency.

[0018] This invention is adaptable to scenarios involving the parallel construction of multiple ship types. It supports the simultaneous coordinated production scheduling and resource allocation of multiple ships of different tonnages and types, solving the global scheduling problem when multiple ships are being built simultaneously in a single shipyard, significantly improving the shipyard's final assembly capacity and reducing overall construction costs. Attached Figure Description

[0019] Other features, objects, and advantages of this application will become more apparent from the following detailed description of non-limiting embodiments with reference to the accompanying drawings: Figure 1 This is a block diagram of the overall architecture of a multi-type, multi-ship parallel construction collaborative scheduling and control system in a preferred embodiment of the present invention.

[0020] Figure 2 This is a schematic diagram of the data interaction flow of each subsystem in a preferred embodiment of the present invention.

[0021] Figure 3 This is a flowchart of a preferred embodiment of the collaborative management and control method for parallel construction of multiple ships according to the present invention. Detailed Implementation

[0022] The present application will now be described in detail with reference to specific embodiments. These embodiments will help those skilled in the art to further understand the present application, but do not limit the present application in any way. It should be noted that those skilled in the art can make several modifications and improvements without departing from the concept of the present application, and these all fall within the protection scope of the present application. Parts not described in detail in the following embodiments can be implemented using existing technology.

[0023] Existing shipbuilding management and control systems typically suffer from problems such as data fragmentation, resource conflicts, inefficient planning, disconnected on-site management, and the lack of a comprehensive collaborative system. To address these issues, one embodiment of the present invention provides a collaborative scheduling and management system for the parallel construction of multiple ship types. This system is designed for the comprehensive collaborative scheduling and management of the simultaneous construction of multiple ship types, achieving the technical goals of breaking down data silos between different business processes, resolving issues of large errors in manual statistics and measurement distortions, automatically predicting and avoiding resource contention conflicts among multiple ships, dynamically updating material quantity verification rules / work hour standards / resource allocation / production plans, and adapting to the overall planning scenarios of simultaneous batch construction of multiple tonnage and multiple ship types.

[0024] Specifically, such as Figure 1 As shown, the multi-type, multi-ship parallel construction collaborative scheduling and control system provided in this embodiment may include: a bottom-level global support base unit for data communication connection and an upper-level business domain unit; wherein: The underlying global support base unit interfaces with the Aveva Marine ship design system, SAP supply chain system and / or workshop terminals (including workshop workstation barcode scanning terminals and workshop equipment sensors and other data acquisition terminals) externally, and communicates with the subsystems of the upper-level business domain unit internally. It also stores the various business data generated by the subsystems of the upper-level business domain unit into a unified database. At the same time, it issues collaborative scheduling instructions to the upper-level business domain unit based on the global data, which is used to drive the upper-level business domain unit to recalculate the specified production plan and / or resource allocation scheme. The upper-level business domain unit may further include: a production planning domain subunit and a field execution domain subunit; wherein: The production planning sub-unit is used to generate corresponding process-level engineering decomposition standards, standardized engineering quantities, and time calculation results based on the total project duration of multiple ships and ship design data files. At the same time, it obtains resource allocation plans including site equipment, material issuance, and team manpower based on production plan requirements, and uses site load, material inventory, and team manpower limits as resource constraints. It integrates standardized engineering quantities, time calculation results, and resource constraints to generate multi-level production plans. The multi-level production plans, standardized engineering quantities, time calculation results, and resource allocation plans are then sent to the field execution sub-unit as execution benchmarks. The on-site execution domain subunit is used to implement the production plan based on the execution benchmark. It uses the workshop terminal to collect on-site performance data in real time, including start and completion time, completed quantity, actual working hours, site and equipment occupancy, steel plate requisition, and team manpower on duty, and feeds the data back into the production planning domain to drive dynamic iterative optimization of working hour calculation results, standardized engineering quantities, resource allocation schemes, and / or production plans.

[0025] The following is combined Figure 1 and Figure 2The preferred embodiments are described in further detail, providing a detailed explanation of the specific technical solutions for implementing the multi-type, multi-ship parallel construction collaborative scheduling and control system provided in this embodiment.

[0026] In some preferred embodiments, the aforementioned underlying global support base unit may further include: a unified database module, a unified planning and resource scheduling service module (hereinafter referred to as the global scheduling module), a microservice gateway module, a message middleware module, an authentication module, a log auditing module, and an internal and external bidirectional API interface module; wherein: The unified database module is used to uniformly store various business data issued by the upper-level business domain units, including: material quantity, working hours, production plan, resources, and on-site performance data, which constitute the full-domain data. The global scheduling module is used to read the plan conflict list, resource overload warning, on-site resource scheduling application, and plan execution deviation record from the global data, and generate collaborative events accordingly. These collaborative events are then encapsulated into collaborative scheduling instructions containing event number, source subsystem, target subsystem, associated task, resource category, demand, time window, and triggering reason. These instructions are sent to the target subsystem of the upper-layer business domain unit via the message middleware module, triggering the target subsystem to call its existing computing module to recalculate the affected unexecuted tasks or resource configuration schemes. The global scheduling module is only responsible for collaborative event identification and instruction distribution; it does not replace the generation of production plans or resource configuration schemes by the business subsystems, nor does it directly generate production plans or resource configuration schemes. The microservice gateway module is used to uniformly manage access permissions for all subsystem interfaces and to route and distribute internal and external requests. The message middleware module is used to asynchronously transmit real-time business data streams from various modules, ensuring stable data interaction in high-concurrency scenarios. The access control module is used to configure system functions and data access permissions by department and position. The log auditing module records all data modifications, plan changes, and scheduling operations, ensuring traceability. The internal and external bidirectional API interface module is used to connect externally to the Aveva Marine ship design system, SAP supply chain system, workshop workstation barcode scanning terminal / workshop equipment sensor acquisition terminal, and internally to connect to all upper-level business subsystems.

[0027] In some preferred embodiments, the aforementioned upper-level business domain unit may further include: a production planning management subsystem, a material quantity data control subsystem, a work hour control subsystem, a site and equipment resource management subsystem, a steel plate storage yard management subsystem, a labor resource management subsystem, and / or a workshop execution control subsystem located in the field execution domain; wherein: In the production planning domain, the production planning management subsystem issues process-level engineering decomposition standards to the material quantity data control subsystem and the time control subsystem. At the same time, it receives standardized engineering quantities and time calculation results from the two subsystems and generates a multi-ship, multi-level production plan by combining various resource constraints. The site and equipment resource management subsystem, the steel plate yard management subsystem, and the labor resource management subsystem receive the resource requirement list issued by the production planning management subsystem, generate resource allocation schemes, and send back basic data on site load, material inventory, and team human resource allocation as resource constraints. In the on-site execution domain, the workshop execution control subsystem receives execution benchmarks regarding production plans, quantities, working hours, and resources from various subsystems in the production planning domain. It utilizes workshop terminals to collect real-time on-site performance data, including start and completion times, completed quantities, actual working hours, site and equipment occupancy, steel plate requisition, and team manpower availability, and feeds this data back into the production planning domain. This drives dynamic iterative optimization of working hour calculations, standardized work quantities, resource allocation schemes, and production plans. The data flow between subsystems, such as… Figure 2 As shown.

[0028] Furthermore: The Production Planning domain subunit is used for planning. Within this domain, there are no hierarchical relationships between subsystems; all communication is bidirectional. It includes three types of business components: The global central business component includes: the digital final assembly and construction production planning management subsystem (referred to as the production planning management subsystem). Parallel data support business components at the same level include: Automatic extraction and verification of material quantity data for ship assembly and construction operations (referred to as the material quantity data management and control subsystem) and ship assembly and construction time management and control subsystem (referred to as the time management and control subsystem). The resource collaborative configuration cluster business components include: the site and equipment resource digital collaborative optimization configuration subsystem (hereinafter referred to as the site and equipment resource management subsystem), the steel plate yard digital management subsystem (hereinafter referred to as the steel plate yard management subsystem), and the labor resource scheduling and management subsystem (hereinafter referred to as the labor resource management subsystem).

[0029] In this production planning domain, the interaction logic between the aforementioned subsystems includes: the production planning management subsystem, as the core of the domain linkage, can issue process-level engineering decomposition standards to the material quantity data control subsystem and the time control subsystem, and simultaneously receive standardized engineering quantities and time calculation results output by the material quantity data control subsystem and the time control subsystem as engineering quantity and time coupling constraints. It also combines the resource configuration basic data obtained by each subsystem in the resource collaborative configuration cluster business component as resource constraints to generate a multi-ship, multi-level production plan; the site / steel plate / human resources management subsystem receives resource requirements and sends back the site load, material inventory, and team manpower resource configuration basic data to the production planning management subsystem to form various resource constraints.

[0030] The on-site execution domain subunit includes: the shipbuilding workshop manufacturing process monitoring and planning control subsystem (hereinafter referred to as the workshop execution control subsystem). This subsystem serves as the terminal for on-site data acquisition and dynamic scheduling, establishing a two-way data flow with all subsystems in the production planning domain. It receives execution benchmarks issued by the production planning management subsystem, the material / work hour control subsystem, and the site / steel plate / human resources management subsystem, obtains actual start and completion times, completed work items (quantities), actual working hours, equipment and site conditions, steel plate materials, and team manpower data on-site, and feeds them back to all upstream subsystems in full, driving the dynamic iterative optimization of calculation results and production plans.

[0031] In some preferred embodiments, the aforementioned production planning management subsystem, serving as the global central hub and a multi-level production planning collaborative management link, may further include: 1. Component Modules: Multi-ship type basic data module, overall plan module, multi-level workshop plan module for hull / painting / outfitting, plan conflict verification module, accumulated load calculation module, plan version approval module, and full-domain two-way data interface module; among which: The multi-ship type basic data module is used to maintain ship type, ship number, section, region, process, milestone and work calendar, and generate unique identifiers for planning objects of different ship types according to the set hierarchical combination rules of "ship type code-ship number code-section code-region code-process code", forming planning basic data with unified coding for multiple ship types; The overall planning module is used to establish a milestone network based on the contract delivery date and the total duration of multiple ships. It decomposes milestone tasks level by level according to the preset hierarchy of ships, sections, regions, main jobs, auxiliary jobs, processes and process elements, and generates process-level engineering decomposition standards that include unified codes, operation levels, input quantity types, predecessor and successor relationships and responsible workshops. The process-level engineering decomposition standards are used as decomposition rules to form the initial planned tasks and resource requirements list for ships, sections and processes. The hull / painting / outfitting multi-level workshop planning module is used to receive initial planning tasks, standardized engineering quantities, process planning time and resource constraints, and generate plant-level, workshop-level and team-level production plans step by step; The plan conflict verification module is used to perform conflict detection on multi-level production plans and output a plan conflict list based on the sequential relationship of processes, time windows, and the availability of site equipment, steel plates, and work groups. The load calculation module is used to summarize the planned working hours and resource requirements of each ship and each process according to time period, compare them with the available resource capacity, and generate load curves and overload warnings. The plan version approval module is used to freeze, submit, approve and release the plan version after conflict resolution, and save version differences and approval records; The global bidirectional data interface module serves as the internal business data interface for the production planning and management subsystem. It is used to issue process-level engineering decomposition standards generated by the overall planning module to the material quantity data control subsystem and the time control subsystem, issue resource requirement lists to the three types of resource management subsystems, and issue production plans to the workshop execution control subsystem. It also receives standardized engineering quantities, time calculation results, various resource constraints, and on-site execution feedback composed of actual on-site performance data. Furthermore, it receives and forwards collaborative scheduling instructions sent by the global scheduling module according to the target module identifier to trigger multi-level workshop planning modules, planning conflict verification modules, and / or accumulated load calculation modules to reschedule, review conflicts, and / or recalculate loads for affected unexecuted tasks.

[0032] 2. Connection relationship: (1) Through the full-domain bidirectional data interface module, bidirectional communication with material quantity and working hours is realized: the process-level engineering decomposition data is sent to the [Material Quantity Data Management Subsystem] and the [Working Hour Management Subsystem], and the standardized engineering quantity (material quantity) and working hour calculation results are received from the two. (2) Through the full-domain bidirectional data interface module, bidirectional communication with the three major resource clusters is realized: material (steel plate) requirements, segmented tire occupancy, and labor plans are issued to the [Site Equipment Resource Management Subsystem], [Steel Plate Yard Management Subsystem], and [Labor Resource Management Subsystem], and the site load, material inventory, and basic data of team human resource configuration are received back from the three types of resource management subsystems; (3) The full-domain bidirectional data interface module realizes bidirectional communication with the workshop monitoring: it issues workshop execution plans to the [Workshop Execution Control Subsystem], and the plan version approval module provides the published execution version; it also receives the workshop's feedback data on plan execution. (4) All business data are aggregated downwards to a unified database, receiving the underlying unified plan and resource scheduling global tasks (plan adjustment and resource scheduling tasks formed by the overall state, driving the corresponding subsystems to re-verify, match and update the task status).

[0033] 3. Core Technology Logic: M1: Input multi-type ship construction bus list, generate plant-level master plan, workshop monthly plan, and team weekly / daily execution plan in layers, covering hull processing / small group / large group / assembly, painting before and after the sea, and all stages of outfitting process; M2: Generate standardized process-level engineering decomposition data and simultaneously distribute it to the material quantity data management subsystem and the time management subsystem to unify the granularity of material quantity decomposition and time calculation between the two. M3: Integrates resource constraint data from the three resource management subsystems of steel plates, site, and manpower. It incorporates a built-in plan conflict detection algorithm to automatically identify conflicts related to multiple parallel ship deployments, materials, and manpower, completing online plan approval and generating an approved workshop execution plan. Specifically, the plan conflict detection algorithm: checks for time logic conflicts based on the sequential relationship of work processes; checks for duplicate occupancy and capacity overruns based on site and equipment occupancy time windows; checks for material shortages based on steel plate demand dates and available inventory; checks for manpower overload based on job type demand and available shift personnel; and calculates the earliest feasible start time for conflicting tasks and generates adjustment suggestions. M4: Issue the approved workshop execution plan to the workshop execution control subsystem; simultaneously receive the plan execution deviations returned by the workshop execution control subsystem, and dynamically iterate and adjust the production plans at each level; the plan execution deviations are calculated in the following ways: for tasks that have started, calculate the difference between the actual start time and the planned start time; for tasks that have been completed, calculate the difference between the actual completion time and the planned completion time; for tasks that are in progress, calculate the difference between the actual completed quantity ratio and the planned completed quantity ratio, and summarize them according to the task weights to form the progress deviations at the workshop and ship levels.

[0034] 4. Interaction Logic: This subsystem serves as the sole central hub for full-domain linkage within the entire system, establishing direct bidirectional data flow with all other 6 subsystems. It coordinates the entire data chain of planning, material quantity, working hours, steel plate / site / human resources, and workshop execution. All subsystems directly or indirectly use the planning constraints issued by this subsystem as prerequisites for business calculations.

[0035] In some preferred embodiments, the above-mentioned time management subsystem may further include: 1. Component Modules: Time Standard Library Management Module, Ship Section Correction Coefficient Module, Planned Time Calculation Module, Actual Time Comparison Module, Production Efficiency Evaluation Module, Two-Way Interactive Interface Module; Among them: The standard work time library management module is used to maintain the benchmark work time and version of the unit project quantity according to job type, main job type, auxiliary job type, process and process element; The ship section correction coefficient module is used to read historical performance data from a unified database, including existing project work packages, work orders, personnel work reports and workshop terminals, and to perform sample classification and sample cleaning. It calculates the ratio of actual working hours to unit benchmark working hours for each type of sample, and generates correction coefficients after statistics and review (manual review can be used). The planned work time calculation module is used to match standardized work quantities, unit base work hours and correction factors according to the project decomposition standard, and calculate the planned work time of each segment and process. The actual working hours comparison module is used to receive start and completion times and personnel work reports collected from the workshop, generate actual working hours and compare them with planned working hours; The production efficiency evaluation module is used to evaluate the production efficiency of ship type, section, process and team based on the deviation rate between planned man-hours and actual man-hours, and to feed back valid samples to the standard library. The two-way interactive interface module is used to receive process-level engineering decomposition standards issued by the production planning management subsystem, standardized engineering quantities output by the material quantity data control subsystem, and actual working hour feedback data returned by the workshop execution control subsystem; send working hour calculation results to the production planning management subsystem and the workshop execution control subsystem; receive collaborative scheduling instructions with the working hour control subsystem as the target subsystem; and call the planned working hour calculation module and / or actual working hour comparison module to recalculate the working hour calculation results or working hour deviation rate according to the associated tasks.

[0036] 2. Connection Relationship: Receives process-level engineering breakdown data from the Production Planning Management Subsystem; unidirectionally receives standardized engineering quantities output from the Material Quantity Data Control Subsystem, automatically calculates planned working hours for each process; feeds back working hour calculation results to the Production Planning Management Subsystem; sends working hour calculation results to the Workshop Execution Control Subsystem and receives actual working hour feedback data from the Workshop Execution Control Subsystem; all data converges to a unified database; receives unified scheduling tasks from the underlying layer. 3. Core Technology Logic: M1: Built-in full-process time standard library and multi-ship type correction coefficients, receiving process-level engineering decomposition data to determine the granularity of time calculation; specifically: parsing the main job, sub-job, process and process element codes in the process-level engineering decomposition data, matching them with the quota objects in the time standard library level by level; prioritizing the use of process element-level benchmark time, and if missing, falling back to the process, sub-job or main job level in sequence, and using the lowest effective level matched as the calculation granularity; M2: Based on the planned working hours and material quantity data output by the material quantity data management and control subsystem, the standard planned working hours for each section and each process are automatically calculated; specifically: the standardized engineering quantities are summarized according to the calculation granularity, each material quantity is multiplied by the corresponding unit benchmark working hours, ship type section correction factor and team efficiency correction factor, and then the material quantity items under the same process are summed to obtain the process planned working hours, and the planned working hours of the sections and ships are summarized level by level; M3: Receives actual working hours data transmitted from the workshop, automatically compares the deviation between planned working hours and actual working hours, identifies inefficient processes, outputs efficiency deviation data, and can also generate efficiency analysis reports. M4: The system feeds back the calculation of working hours and efficiency deviation data to the production planning management subsystem to support iterative optimization of the plan.

[0037] 4. Interaction Logic: It operates at the same level as the Material Quantity Data Control Subsystem, and both receive process-level engineering decomposition data from the Production Planning Management Subsystem. It relies solely on the Material Quantity Data Control Subsystem to calculate the completion time of the project and does not directly connect to the three types of resource management subsystems. It indirectly shares time load data with the resource cluster through a unified database.

[0038] In some preferred embodiments, the above-mentioned material quantity data management subsystem may further include: 1. Components: The design includes a data synchronization module, a multi-source quantity extraction module, a hierarchical quantity generation module, an intelligent verification rule base module, a quantity database management module, and a two-way data interface module; among which: The design data synchronization module is used to synchronize the ship's 3D model, segmented BOM and related design list from the Aveva Marine ship design system, and to complete the version and object code mapping; The multi-source quantity extraction module is used to extract the work quantity and attributes of parts, welds, painting areas and outfitting components from the model, BOM and heterogeneous design list according to the quantity selection guide document; The intelligent verification rule base module is used to verify the extracted work quantity for missing items, duplicates, out-of-bounds, and BOM inconsistencies by using process logic, numerical thresholds, and material matching rules, and outputs the verified extracted quantity. The hierarchical quantity generation module is used to collect the verified extracted quantities according to the main job, sub-job, process and process element based on the engineering decomposition standard, and form a standardized quantity dataset. The material quantity database management module is used to store the original material quantity, cleaning results, hierarchical aggregation relationship, version and verification records; The bidirectional data interface module is used to receive process-level engineering decomposition standards issued by the production planning management subsystem, send standardized engineering quantities and material quantity execution benchmarks to the production planning management subsystem, time control subsystem, and workshop execution control subsystem, and receive workshop completed material quantity feedback; it also receives collaborative scheduling instructions from the material quantity data control subsystem as the target subsystem, and calls the multi-source material quantity extraction module and / or intelligent verification rule base module to re-extract and / or verify the material quantity data of the corresponding design object according to the associated task.

[0039] 2. Connection Relationship: It bidirectionally interfaces with the Aveva Marine ship design system for synchronizing 3D models, segmented BOMs, and design lists; performing object coding, version mapping, and multi-source work quantity extraction; receiving process-level engineering decomposition data from the Production Planning Management Subsystem; unidirectionally outputting standardized engineering quantities to the Time Management Subsystem; issuing planned time and quantity benchmarks to the Workshop Execution Management Subsystem; receiving completed work quantity feedback data from the Workshop Execution Management Subsystem; all business data is aggregated downwards to the underlying unified database; and receiving global collaborative tasks issued by the underlying unified planning and resource scheduling systems. 3. Core Technology Logic: M1: Secondary development and docking with the AM ship design platform, synchronizing multiple sources of original design data such as hull, outfitting, painting 3D models, BOM list, and section process drawings; M2: Receives process-level engineering decomposition standards issued by the production planning and management subsystem, builds hierarchical extraction rules according to process granularity, automatically decomposes the four levels of work materials: main job, auxiliary job, work package, and process element, and counts the steel plate weight, total weld length, coating area, and number of pipe fittings. M3: Built-in process logic, numerical threshold, and material matching triple quantity verification rules, automatically identify missing, duplicate, abnormal (including out-of-bounds and BOM inconsistencies) quantities, and process logic contradictions and mark them with warnings; M4: After cleaning and verification are completed, a standardized engineering quantity dataset is generated and stored in a dedicated material quantity database. It is then pushed to the time management subsystem and the workshop execution management subsystem. Simultaneously, it receives the actual work performance data returned by the workshop execution management subsystem and iteratively optimizes the material quantity verification rules. 4. Interaction Logic: This subsystem only provides planned quantity benchmarks for time management and workshop monitoring, and is not the only quantitative data source for the entire system; it relies on the production planning management subsystem to provide process-level engineering decomposition standards to determine the granularity of quantity breakdown; it only outputs quantities unidirectionally to the time management subsystem and the workshop execution management subsystem, and does not directly push data to the three resource management subsystems of steel plate, site, and manpower; it relies on a unified database to achieve indirect data exchange with the resource cluster.

[0040] In some preferred embodiments, the above-mentioned site equipment resource management subsystem may further include: 1. Component Modules: Digital ledger module for site equipment, gridded site modeling module, multi-objective genetic optimization algorithm module, tire position / dock layout module, crane and flatbed truck scheduling module, resource conflict detection module, and bidirectional interface module; among which: The site equipment digital ledger module is used to maintain the spatial dimensions, load-bearing capacity, available time and real-time status of junk locations, docks, storage yards, cranes and flatbed trucks; The gridded site modeling module is used to discretize the site area into grid cells with attributes such as coordinates, size, load-bearing capacity, and occupancy period, and to establish a mapping between the segmented shape envelope and the grid cells. The multi-objective genetic optimization algorithm module is used to encode, select, crossover, mutate, and iteratively optimize the segmented locations, work periods, and equipment combinations with the objective functions of plan delay, site vacancy, transportation distance, and equipment conflict. The tire position / dock layout module is used to generate segmented tire placement, overall assembly, and dock usage plans based on the optimization results; The crane flatbed truck scheduling module is used to generate lifting and transfer task sequences based on segment weight, start and end positions, operation time windows and equipment capacity; The resource conflict detection module is used to detect overlapping site occupancy, duplicate equipment allocation, overload exceeding limits, and disjointed process times at the same time, and outputs the conflict objects and time periods. The bidirectional interface module is used to receive the segmented tire occupancy, painting, and pallet placement plans from the production planning and management subsystem, return basic data on site equipment load, issue site equipment configuration schemes to the workshop execution and control subsystem, and receive its real-time site equipment requirements; it also receives collaborative scheduling instructions from the site equipment resource management subsystem as the target subsystem, and calls the multi-objective genetic optimization algorithm module and / or resource conflict detection module to recalculate the site equipment configuration scheme based on associated tasks, demand, and time windows.

[0041] 2. Connection Relationship: Receives segmented tire occupancy, painting, and track fixing plans from the Production Planning Management Subsystem; transmits basic data on site and crane resource configuration back to the Production Planning Management Subsystem; interacts bidirectionally with the Workshop Execution Control Subsystem: receives workshop site / crane scheduling requests and issues site and equipment scheduling results; data is uniformly aggregated into the underlying database; receives globally unified scheduling tasks; 3. Core Technology Logic: M1: Complete the digital ledger and spatial grid modeling of the dock, assembly jig, painting workshop, crane, and flatbed truck, and update the equipment occupancy and site availability status in real time. The specific modeling process includes: obtaining site boundaries, obstacles, passages, load-bearing capacity, and available calendars; dividing the planar area into grids according to preset step sizes and assigning coordinates and status attributes; calculating the occupied grid set based on the segment shape envelope, safety distance, and work direction; and establishing the relationship between segments, grids, time periods, and supporting equipment. M2: Reads the segmented construction sequence and tire occupancy plan issued by the production planning and management subsystem, and calls a multi-objective optimization algorithm to generate the optimal solution for tire position layout, crane lifting, and on-site transportation; automatically identifies and adjusts the sequence of overlapping and conflicting site occupancy times for multiple vessels; the multi-objective optimization algorithm for generating the optimal solution specifically includes: chromosome encoding of segmented site locations, start times, crane and flatbed truck combinations, using the weighted sum of delay time, site vacancy rate, transportation distance, and conflict penalty as the fitness function, and outputting non-dominated candidate solutions after selection, crossover, mutation, and iteration, and selecting the solution with the smallest objective value according to preset weights; automatic identification specifically includes: checking whether spatial envelopes overlap, whether occupancy times overlap, whether equipment capacity meets segment weight, whether the same equipment is repeatedly allocated, and whether the work sequence relationship is satisfied. M3: Receive temporary site and crane scheduling requests initiated by the workshop monitoring site, dynamically rearrange the scheduling plan (including tire position / dock layout results and crane and flatbed truck task sequences, i.e. site equipment resource allocation plan) and send the results to the workshop; M4: The system transmits basic resource data such as site load and equipment availability constraints back to the production planning management subsystem as resource constraints to assist in balancing production scheduling.

[0042] 4. Interaction Logic: This subsystem directly connects to the production planning management subsystem and the workshop execution control subsystem; it does not directly connect to the material quantity data control subsystem or the time control subsystem. Instead, it reads the segmented project quantities from a unified database to assist in site duration calculation.

[0043] In some preferred embodiments, the steel plate yard management subsystem may further include: 1. Component Modules: Steel Plate Basic File Module, RFID Inbound / Outbound Data Acquisition Module, Yard Gridded Spatial Model Module, Segmented Steel Plate Demand Matching Module, Inventory Early Warning Module, Stacking Optimization Scheduling Module, and Two-Way Interface Module; Among them: The steel plate basic file module is used to maintain the steel plate number, specifications, material, batch, processing series, and scheduled usage time; The RFID inbound / outbound data acquisition module is used to collect data on steel plate arrival, warehousing, pallet transfer, outbound, and shipment events and update the inventory status. The yard gridded spatial model module is used to create a three-dimensional coordinate index according to the yard area, stack position, and layer number, and associate the stack position size, height, capacity, and steel plate position. The segmented steel plate demand matching module is used to match steel plate demand with the material, specifications, batch and processing series in the inventory based on the segmented BOM, the monthly steel plate demand plan formed by summarizing the published multi-level production plans on a monthly basis, and the daily steel plate delivery plan formed by decomposing the monthly steel plate demand plan according to the segmented start date. The inventory alert module compares demand dates, available inventory, and safety stock to generate alerts for material shortages, overstocking, and overdue items. The stacking optimization scheduling module is used to generate inbound, stacking, and outbound sequences with the goal of minimizing the number of stacking operations and handling distance, while satisfying constraints such as stacking capacity, same-series aggregation, first-in-first-out, and planned usage order. The bidirectional interface module is used to receive steel plate requirements and segmented production plans from the production planning management subsystem, return basic steel plate inventory data, issue steel plate configuration schemes to the workshop execution control subsystem, and receive its real-time steel plate requisition requirements; it also receives collaborative scheduling instructions from the target subsystem, the steel plate yard management subsystem, and calls the segmented steel plate demand matching module and / or stacking optimization scheduling module to recalculate the steel plate (steel plate outbound) configuration scheme based on associated tasks, steel plate demand, and time windows.

[0044] 2. Connection Relationship: Receives steel plate demand and segmented production plans from the Production Planning Management Subsystem; transmits steel plate inventory and resource allocation basic data back to the Production Planning Management Subsystem; interacts bidirectionally with the Workshop Execution Control Subsystem: receives workshop steel plate requisition and scheduling requests, and issues steel plate outbound scheduling results; all business data is migrated to a unified database; receives underlying unified plans and resource scheduling tasks; 3. Core Technology Logic M1: Based on RFID data collection of the entire process of steel plate warehousing, relocation, and outbound, a three-dimensional grid-based positioning model of the storage yard is built to update the storage location, specifications, and inventory balance of each steel plate in real time. Specifically, the three-dimensional grid-based positioning model of the storage yard includes: dividing the storage yard into three spatial units: area, stack, and layer number; configuring planar coordinates, length, width, height limit, and capacity for each stack; binding stack number, layer number, specifications, batch, and expected usage date for each steel plate; and updating the occupancy status in real time based on warehousing, relocation, and outbound events. M2: Reads the steel plate demand plans for each segment issued by the production planning and management subsystem, automatically matches the existing inventory of steel plates, and generates a batch steel plate outbound plan; automatically generates a material shortage warning when the inventory is below the threshold. M3: Receives on-site steel plate requisition and scheduling requests initiated by the workshop execution control subsystem, dynamically adjusts the outbound and stacking schemes, and synchronously transmits the scheduling results back to the workshop; M4: Resource-based data such as yard inventory and plate supply sequence are pushed back to the production planning management subsystem as resource constraints to constrain the segmented start-up and production scheduling sequence. 4. Interaction Logic: This subsystem only interacts directly and bidirectionally with the production planning management subsystem and the workshop execution control subsystem; it does not directly read data from the material quantity control subsystem and the time control subsystem, but relies on a unified database to obtain segmented material quantities to indirectly calculate the board material demand.

[0045] In some preferred embodiments, the above-mentioned labor resource management subsystem may further include: 1. Component Modules: Worker Skill File Module, Job Efficiency Coefficient Database Module, Manpower Load Calculation Module, Medium- and Long-Term Employment Planning Module, Flexible Work Team Scheduling Module, and Two-Way Interactive Interface Module; Among them: The worker skills file module is used to maintain information such as the worker's work group, primary and secondary job types, skill level, qualification certificate, available time slots, and historical work records. The job efficiency coefficient library module is used to calculate efficiency coefficients based on skill level evaluations and historical ratios of planned and actual working hours for similar tasks, and then publish them by job type and work group after review. The manpower load calculation module is used to convert the planned working hours of each process in each time period into the required number of workers according to the type of work and efficiency coefficient, and compare it with the available number of workers on duty to form the load and gap; The medium- and long-term employment planning module is used to summarize the manpower needs of multiple ship projects on a monthly and weekly basis, and generate suggestions for recruitment, outsourcing, shift adjustment and training. The flexible scheduling module for work teams is used to allocate tasks to work teams and personnel under constraints such as skill matching, qualifications, working hour limits, rest time, and work team availability. The two-way interactive interface module is used to receive the labor demand plan from the production planning and management subsystem, return the basic data of manpower load, issue the team manpower allocation plan to the workshop execution and control subsystem, and receive its real-time manpower demand; it also receives the collaborative scheduling instructions from the target subsystem, the labor resource management subsystem, and calls the manpower load calculation module and / or the team flexible scheduling module to recalculate the manpower load and / or the team manpower allocation plan based on the associated tasks, job types, number of people required, and time windows.

[0046] 2. Connection Relationship: Receives painting and segmented construction labor demand plans from the Production Planning Management Subsystem; transmits basic data on team manpower and labor resource allocation back to the Production Planning Management Subsystem; interacts bidirectionally with the Workshop Execution Control Subsystem: receives workshop manpower support scheduling requests and issues team manpower allocation results; all data is routed to a unified database; receives unified scheduling instructions from the underlying layer. 3. Core Technology Logic M1: Establish digital archives of worker skill levels and work efficiency for each type of work, and build a standard calculation model for manpower load; specifically, building a standard calculation model for manpower load includes: M2: Reads the labor demand plans issued by each workshop from the production planning and management subsystem, and combines them with the process material quantity and working hour data stored in the unified database to automatically calculate the short-term and medium-term overall manpower load of the entire plant and complete flexible scheduling across workshops and shifts. Specifically, the automatic calculation of the short-term and medium-term overall manpower load of the entire plant includes: summarizing the planned working hours of each process by day, week and month, breaking down the working hour demand according to job type and skill requirements, and then dividing it by the corresponding shift efficiency coefficient and the available working hours per person to obtain the required number of people; comparing the required number of people with the available number of people formed by scheduling, leave and on-duty data, and outputting the manpower load rate and gap for each time period, job type and workshop. M3: Receive on-site manpower support requests initiated by the workshop monitoring system, dynamically adjust the manpower allocation plan for the work team, and push the allocation results to the workshop; M4: The resource data such as the manpower shortage and manpower load constraints of the work team are sent back to the production planning management subsystem as resource constraints for the purpose of adjusting the planned schedule.

[0047] 4. Interaction Logic: This subsystem is directly connected to the production planning management subsystem and the workshop execution control subsystem in both directions; it does not directly connect to the material quantity data control subsystem and the work hour control subsystem, but relies on a unified database to read the engineering quantity and work hour data to complete the calculation of manpower requirements.

[0048] In some preferred embodiments, the above-mentioned workshop execution control subsystem may further include: 1. Component Modules: Multi-terminal data acquisition interface module, process progress tracking module, online work dispatch management module, production bottleneck early warning module, dynamic planning fine-tuning module, resource scheduling request initiation module, and two-way interactive interface module; among which: The on-site multi-terminal data acquisition interface module is used to connect with workstation barcode scanners, equipment sensors, and mobile terminals to collect data on start-up and completion, completed material quantity, personnel work reports, equipment occupancy, and material requisition. The process progress tracking module is used to summarize the planned and actual start and completion times, completed quantities and actual working hours of the tasks, and calculate the completion rate and progress deviation. The online work dispatch management module is used to receive published workshop plans and resource allocation results, and to assign work processes, personnel, equipment and materials to workstations; The production bottleneck early warning module is used to identify events such as schedule delays, work-in-process backlogs, resource overload, and material and manpower shortages, and outputs the bottleneck type, location, and affected tasks. The dynamic planning fine-tuning module is used to adjust the start and end times and sequence of unstarted production plans based on on-site deviations without changing the frozen milestones. The resource scheduling request initiation module is used to generate scheduling requests with tasks, demand quantities, and time windows for situations such as material shortages, manpower shortages, and site and equipment conflicts. The two-way interactive interface module is used to receive workshop production plans from the production planning management subsystem, standardized engineering quantities from the material quantity data control subsystem, time calculation results from the time control subsystem, and resource allocation schemes from the three types of resource management subsystems; it provides on-site execution feedback to the production planning management subsystem, consisting of actual start time, actual completion time, completed material quantity, actual working hours, site and equipment occupancy, steel plate requisition, and personnel on-duty data, and provides completed material quantity and actual working hours to the material quantity and time control subsystems respectively; it receives collaborative scheduling instructions from the target subsystem, which is the workshop execution control subsystem, updates online work assignments based on related tasks, and calls the dynamic planning fine-tuning module to adjust the production plan that has not yet started.

[0049] 2. Connection relationship: (1) Receive the workshop execution plan issued by the Production Planning Management Subsystem and send the plan execution feedback back to the Production Planning Management Subsystem; (2) Receive planned working hours and material quantities data issued by the [Material Quantity Data Management and Control Subsystem] and working hour benchmarks issued by the [Working Hour Control Subsystem] in one direction; and send actual working hour feedback data back to the [Material Quantity Data Management and Control Subsystem] and the [Working Hour Control Subsystem]. (3) Two-way communication with the three major resource management subsystems of steel plate, site and manpower: Initiate resource scheduling requests to the [site and equipment resource management subsystem], [steel plate yard management subsystem] and [labor resource management subsystem], and receive scheduling and allocation results issued by the [site and equipment resource management subsystem], [steel plate yard management subsystem] and [labor resource management subsystem]; (4) Collect all actual performance data on site and aggregate it into a unified database to receive unified scheduling tasks from the underlying global database.

[0050] 3. Core Technology Logic: M1: Connects to workstation barcode scanning, crane sensors, and worker mobile check-in terminals to collect real-time data on segmented completion progress, actual working hours, steel plate issuance, equipment occupancy, and the full range of on-site data for work teams. M2: Automatically compares the actual progress on site with the workshop plan, material quantity and time benchmark issued in the plan, identifies lagging processes and production bottlenecks and issues pop-up warnings; M3: When there is a shortage of materials, personnel, or conflict in the use of site and equipment on site, the system initiates resource scheduling requests to the steel plate, site, and human resource management subsystems respectively, and receives the scheduling and allocation results returned by the resource management subsystem to update the on-site work assignment. M4: The collected actual working hours and completed material quantities are sent back to the material quantity data control subsystem and the working hour control subsystem, respectively, to support the iterative verification of rules and working hour standards; and the overall execution deviation is fed back to the production planning management subsystem simultaneously. 4. Interaction Logic: This subsystem serves as the on-site data feedback terminal for the entire system; it directly connects bidirectionally to the production planning management subsystem and the three major resource management subsystems; it receives the material quantity and work hour execution benchmarks issued by the material quantity data control subsystem and the work hour control subsystem, and receives the resource allocation benchmarks issued by the site equipment resource management subsystem, the steel plate yard management subsystem, and the labor resource management subsystem; it reversely transmits the completed material quantity and actual work hours back to the material quantity data control subsystem and the work hour control subsystem, and transmits the site equipment occupancy, material requisition, and personnel performance back to the three types of resource management subsystems; it does not directly participate in resource calculation or planning, but only serves as the exit point for execution collection and scheduling application.

[0051] Based on the same inventive concept, another embodiment of the present invention provides a method for collaborative scheduling and control of parallel construction of multiple types and multiple ships. This method can be executed based on any of the collaborative scheduling and control systems for parallel construction of multiple types and multiple ships in the above embodiments of the present invention, forming a complete closed-loop process.

[0052] Specifically, such as Figure 3 As shown, the multi-type, multi-ship parallel construction collaborative scheduling and management method provided in this embodiment may include: S1 generates corresponding process-level engineering decomposition standards, standardized engineering quantities, and time calculation results based on the total construction period of multiple ships and ship design data files; S2, based on resource requirements, obtain resource allocation plans including site equipment, steel plate outbound and team manpower, and take site load, steel plate inventory and team manpower load as resource constraints; S3 integrates standardized engineering quantities and time calculation results to obtain coupling constraints between engineering quantities and time calculations, and combines them with resource constraints to generate multi-level production plans; S4 utilizes multi-level production plans, standardized engineering quantities, time calculation results, and resource allocation schemes to form execution benchmarks; production plans are implemented based on execution benchmarks, and real-time data on on-site material quantities, actual working hours, and actual performance data on site equipment, steel plates, and manpower requirements are collected to drive dynamic iterative optimization of various execution benchmarks.

[0053] In some preferred embodiments, the above method may further include: S5 generates collaborative scheduling instructions based on global data, and recalculates the specified production plan and / or resource allocation scheme based on the collaborative scheduling instructions.

[0054] In some preferred embodiments, the above-mentioned S1 may further include: S11, Synchronous Analysis of Design Data: The ship AM 3D model, segment BOM and multi-source heterogeneous design data are connected to the material quantity data management and control subsystem. Multi-level operational material quantities are extracted in layers and multiple verifications are performed to obtain the extracted material quantities. S12, Process Standard Issuance: The production planning management subsystem, in conjunction with the total construction period of multiple ships, generates process-level engineering decomposition standards and pushes them bidirectionally to the material quantity data control subsystem and the time control subsystem, unifying the granularity of material quantity data and time data calculation. Specifically, generating process-level engineering decomposition standards includes: establishing a work decomposition tree based on ship type, section, region, and construction stage; decomposing work tasks sequentially to primary work type, secondary work type, process, and process element; and configuring unified codes, inputting material quantity types, predecessor and successor relationships, and responsible workshops for each node. Unifying the granularity of material quantity data and time data calculation specifically includes: the material quantity data control subsystem aggregating design quantities to corresponding processes or process elements according to codes; and the time control subsystem matching unit benchmark time with the same code, ensuring a one-to-one correspondence between quantities and time at the same operational level.

[0055] S13, Collaborative Calculation of Work Quantity and Working Hours: The material quantity data management subsystem outputs tiered standardized work quantities based on the process-level engineering decomposition standards and sends them to the working hour management subsystem. Combined with working hour coefficients (such as ship type and team skill coefficients), it automatically calculates the planned working hours for each process. Specifically, the automatic calculation of the planned working hours for each process includes: summarizing standardized work quantities according to the engineering decomposition code, matching the corresponding unit benchmark working hours, multiplying the work quantity, unit benchmark working hours, ship type section correction coefficient, and team efficiency correction coefficient, and summing the material quantity items under the same process to obtain the planned working hours for the process.

[0056] In some preferred embodiments, the above-mentioned S2 may further include: S21, Multi-dimensional Intelligent Resource Optimization: The site equipment resource management subsystem, steel plate yard management subsystem, and labor resource management subsystem read planned production requirements and segmented material quantities, generating conflict-free site layout, material issuance, and shift scheduling resource allocation schemes. Site load, material inventory, and shift manpower shortages are used as resource load constraints and fed back to the production planning management subsystem. Specifically, generating conflict-free site layout, material issuance, and shift scheduling resource allocation schemes includes: generating a resource requirement list according to the planned task's object, quantity, time window, and capacity requirements; matching available site equipment, inventory steel plates, and qualified shifts; detecting space overlap, duplicate equipment occupation, insufficient inventory, skill mismatch, and excessive manpower hours; adjusting resource combinations or start times for conflicting tasks until all constraints are met before outputting the resource allocation scheme.

[0057] In some preferred embodiments, the above-mentioned S3 may further include: S31, Multi-level Collaborative Planning: The production planning management subsystem integrates four types of constraints: engineering quantity and time coupling constraints, site and equipment constraints, steel plate material constraints, and team manpower constraints. It generates multi-level production plans at the plant, workshop, and team levels, and performs conflict verification and online approval. The conflict verification rules specifically include: subsequent tasks cannot start if the preceding tasks of a process are not completed; the same site or equipment cannot be repeatedly allocated during overlapping periods and cannot exceed the capacity limit; the available steel plate inventory and delivery time should meet the task requirements; and the team's job types, skills, available number of personnel, and continuous working hours should meet the operational requirements.

[0058] In some preferred embodiments, the above-mentioned S4 may further include: S41, the production plan is issued to the workshop unit and workshop field data is collected: the approved production plan, standardized engineering quantity and process plan man-hour are pushed to the workshop execution control subsystem as the execution benchmark. S42, Workshop Real-time Data Acquisition and Scheduling Response: The workshop data acquisition terminal collects work data (quantity), actual working hours, and data on site equipment and materials, automatically identifies production bottlenecks, and initiates resource scheduling requests online. Specifically, automatic identification of production bottlenecks includes comparing actual start and finish times, completed quantities, actual working hours, and resource performance with the execution benchmark. When progress deviations, work-in-process waiting times, site equipment load rates, material shortages, or manpower gaps exceed the corresponding thresholds, the bottleneck task, bottleneck resources, and scope of impact are determined, and warnings and scheduling requests are generated.

[0059] S7, full-link data feedback iteration: all on-site performance data collected in the workshop is synchronously fed back to all subsystems of material quantity, working hours, resources, and planning, and the conflict verification rules, working hour coefficients, and resource configuration schemes are automatically updated; S8, repeating S2~S7, continuously and dynamically balances the construction resources and plans of multiple types of ships until the project is completed.

[0060] It should be noted that the steps in the method provided by the present invention can be implemented using the corresponding components in the system. Those skilled in the art can refer to the technical solution of the system to implement the steps and flow of the method, and can also refer to the technical solution of the method to implement the composition of the system. That is, the embodiments in the system and the embodiments in the method can be understood as preferred examples of each other, which will not be elaborated here.

[0061] Based on the same inventive concept, other embodiments of the present invention also provide a computer device for collaborative scheduling and management of parallel construction of multiple types and multiple ships, including a cloud server cluster as the backend and a local terminal as the frontend; wherein: The cloud server cluster is deployed with the multi-type and multi-ship parallel construction collaborative scheduling and control system of any of the above embodiments of the present invention; wherein, the underlying global support base unit, production planning domain subunit and field execution domain subunit of the multi-type and multi-ship parallel construction collaborative scheduling and control system adopt the Spring Cloud microservice architecture to implement backend business services, and rely on Dubbo RPC and RocketMQ to form a bidirectional interconnection link; The local terminal provides access clients for the production planning domain subunit and the field execution domain subunit, as well as field interaction front-ends and workshop terminal clients. The access clients access corresponding business services in the cloud server cluster, displaying production plans, standardized engineering quantities, time calculation results, and resource allocation schemes. The field interaction front-end displays actual field performance data. The workshop terminal clients acquire actual field performance data and send it to the cloud server cluster. In some preferred embodiments, the local terminal adopts a multi-terminal working structure, including: PCs, tablets, and / or smart mobile terminals.

[0062] The multi-type, multi-ship parallel construction collaborative scheduling and control system and method provided in the above embodiments of the present invention establishes a supporting foundation combining a unified underlying database and global scheduling, realizing unified data aggregation and unified distribution of scheduling instructions across the entire system, breaking down data silos in various business links. A standardized architecture combining the underlying foundation and dual upper-level business domains is constructed, deploying material quantity extraction and time management in parallel at the same level. The planning center can reversely issue process decomposition standards, unifying the calculation methods for engineering quantities and time, and solving the problems of large errors and inaccurate calculations in manual statistics. A two-way data linkage mechanism is established between three types of resources—site, steel plates, and labor—and the plan, with resource load, inventory, and manpower constraints constraining production scheduling in real time, automatically predicting and avoiding resource contention conflicts among multiple ships in parallel. A closed-loop link for full data feedback from the workshop site is established, with process progress, actual working hours, materials, and equipment performance being transmitted back to all upstream subsystems in real time, dynamically updating material quantity verification rules, time standards (time coefficients), resource allocation, and production plans. The system integrates seven subsystems, covering the entire business chain from design quantity analysis and work hour calculation to multi-dimensional resource optimization of site / steel plate / human resources, multi-level collaborative planning, and real-time workshop monitoring. It is suitable for the overall planning of simultaneous batch construction of multi-tonnage and multi-model ships.

[0063] The technical solutions provided by the above embodiments of the present invention will be further described in detail below with reference to the accompanying drawings and a specific application implementation.

[0064] In this specific application example, the scenario involves a shipyard simultaneously commissioning the batch construction of three main types of vessels: a 700TEU container ship, a 114k bulk carrier, and a 16,000TEU methanol-powered container ship. The invention's multi-type, multi-ship parallel construction collaborative scheduling and control system is fully deployed, and corresponding control methods are implemented. The specific implementation steps are as follows: Step 1, System Deployment and Initialization of the Underlying Global Support Base (corresponding to) Figure 1 (Mid-to-lower base module) The entire collaborative management and control system was deployed based on the shipyard's private cloud server cluster. The underlying global support base shown in Figure 1 was built, and the registration of microservices for 7 subsystems, Dubbo bidirectional interfaces, RocketMQ message middleware, unified database, permission authentication platform, and external API interfaces were completed in sequence. Through the external API interfaces of the base, the AvevaMarine ship design system, SAP supply chain system, and workshop MES sensor / barcode collection terminal were connected to establish a two-way data interaction channel between internal and external systems.

[0065] Complete the initial data entry of basic business files for the entire industry: complete construction parameters for three types of ships, standard division of sections for the entire series, process decomposition benchmarks, production line ledgers for each workshop (small assembly, large assembly, painting, dock, wharf), equipment ledgers for cranes / flatbed trucks / elevated trucks, grid-based zoning files for steel plate storage yards, skill level databases for workers of each trade, and standard working hour coefficient databases for the entire process.

[0066] in accordance with Figure 2 A unified global data hub establishes interaction rules and connects the system's basic data links: the material quantity data control subsystem outputs standardized engineering quantities to the global data hub; the three resource subsystems for site equipment, steel plate storage yard, and labor upload site load, steel plate inventory, and manpower constraint data to the global data hub; the workshop execution control subsystem is configured with a performance feedback interface, and the actual working hours, completed material quantity, and equipment occupancy data collected on-site are pushed to the global data hub in full through the dotted feedback link, and simultaneously distributed to all other subsystems.

[0067] Step 2, the material quantity data management and control subsystem initiates full-scale standardized material quantity analysis (corresponding to...) Figure 3 Process S1): The material quantity data management and control subsystem is activated to execute the hierarchical material quantity extraction and verification process, providing a unified quantitative benchmark for the entire system. Step 21: Synchronize multi-source heterogeneous design data such as complete 3D design models of three types of ships, section BOMs, processing / assembly / painting / outfitting process drawings, and process lists through secondary development interfaces; Step 22: Automatically extract the quantities of the four levels of work according to the work breakdown specifications, and automatically calculate the weight of steel plates, total length of welds, coating and sandblasting area, number of pipe fittings, and scaffolding work. Step 23: The built-in intelligent verification rules of process matching, numerical threshold and process logic automatically identify dirty data such as abnormal steel plate weight, missing weld data, logical contradictions before and after the process, and mismatch of outfitting materials, and generate an anomaly list to push to the design end for verification and correction. Step 24: After cleaning and verification, the standardized structured quantities are stored in a dedicated quantity database and pushed to [the relevant authorities] in real time. Figure 2 The global unified data hub synchronously distributes data to the other 6 subsystems, serving as a unified quantitative benchmark for resource load calculation, multi-level production planning and scheduling, process time calculation, and workshop team work assignment.

[0068] Step 3: The three major resource subsystems conduct multi-dimensional intelligent resource optimization and allocation in parallel (corresponding to...) Figure 3 Process S4): The global data hub distributes standardized material quantity datasets downwards to three resource collaboration cluster subsystems: the site and equipment resource management subsystem, the steel plate yard management subsystem, and the labor resource management subsystem. These three subsystems perform resource optimization calculations in parallel, and the resource constraint results are then fed back to the global data hub's supply planning module for use. 1. Site and Equipment Resource Management Subsystem The system reads the construction cycle, external dimensions, and process quantity data of each section of three types of ships, calls the built-in multi-objective genetic optimization algorithm, and automatically allocates No. 1 and No. 2 docks, each group of jig positions, sandblasting and painting workshops, cranes, flatbed trucks, and overhead trucks; it automatically identifies overlapping and conflicting jig and hoisting operation times for multiple ship sections, automatically adjusts the section start-up sequence, outputs conflict-free jig position layout, crane hoisting, and site transportation scheduling plans, generates a site load accumulation map to intuitively display the occupancy saturation of each site, and uploads site load constraint data to the global data center.

[0069] 2. Steel Plate Yard Management Subsystem The system reads the required quantity of steel plates for each ship section from the global central hub, matches it with the steel plate inventory specifications and storage locations collected in real time by RFID, and automatically generates the optimal plan for batch steel plate outbound and in-yard stacking based on the gridded spatial model of the storage yard. It also automatically generates procurement warnings for steel plate specifications with inventory shortages and pushes them to the materials management department. The system also uploads the steel plate supply sequence and inventory constraints to the global data central hub in sync to avoid the problem of work stoppage due to material shortages in the section processing process.

[0070] 3. Labor Resource Management Subsystem By combining the material quantities of each process and the pre-stored worker skill coefficient database issued by the global central hub, the system automatically calculates the short-term and medium-to-long-term manpower load of welding, assembly, painting, and pipe processing jobs; it enables flexible manpower allocation across workshops and work groups, balances the peak demand for manpower in multiple ships and the low point of manpower idleness, outputs work group scheduling plans and short-term outsourcing labor needs, and sends manpower load constraint data back to the global data central hub.

[0071] Step 4: The production planning management subsystem generates multi-level collaborative production plans (corresponding to...) Figure 3 Processes S2 and S5): The global unified data hub synchronously pushes four-dimensional data—standardized material quantities, site and equipment constraints, steel plate inventory constraints, and manpower load constraints—to the production planning and management subsystem (global hub module); the software first issues process-level engineering decomposition standards (corresponding to) to the material quantity extraction subsystem and the time control subsystem. Figure 2 (Data flow is marked below the planning module) to unify the granularity of material quantity and time data calculation across the entire system; then, integrate material quantity and multi-dimensional resource constraints to generate a plant-wide integrated collaborative production plan in a hierarchical manner. 1. Top-level overall plan: Output the overall milestone plan for the entire life cycle of steel laying, section construction, dock loading, ship water intake, dock sea trials, and completion and delivery for three types of ships; 2. Mid-level workshop monthly plan: Generate monthly production plans for each workshop, including internal processing, small assembly, large assembly, segment painting, dock loading, and dock outfitting. 3. Grassroots team execution plan: broken down and refined into workshop weekly plan and team daily work assignment execution plan; The built-in intelligent algorithm for detecting planning conflicts automatically identifies planning conflicts such as multiple ships vying for tire positions, overload in the painting workshop, manpower shortages in work teams, and delays in steel plate supply, and automatically outputs time sequence adjustment and optimization solutions. After the plan completes the online approval process, it is synchronously distributed to the time management system and the workshop manufacturing process monitoring subsystem through the global data hub.

[0072] Step 5: The ship assembly and construction time control system performs process time calculation and deviation analysis (corresponding to...) Figure 3 (Process S3 in the middle) The global data hub synchronously pushes standardized hierarchical quantities and planned process decomposition standards to the time management system, which then performs automatic time calculation, performance comparison, and efficiency analysis. Step 51: Retrieve the system's pre-stored standard working hours database for the entire process, working hour correction coefficients for different ship types, and worker skill coefficients for work teams, and automatically calculate the standard planned working hours for each segment and each process in combination with the graded work quantity. Step 52: Receive the actual working hours data uploaded by workers clocking in from the mobile terminal in the workshop, automatically compare the planned working hours with the actual completed working hours, and calculate the working hour deviation rate for each work package and work order. Step 53: Automatically pop up a warning for lagging processes with deviations exceeding the preset threshold, and break down the root causes of the lag (four categories: insufficient manpower, waiting in the field, material shortage, and complex process). Step 54: The time deviation report and production efficiency analysis data are fed back to the production planning management subsystem and the labor resource management subsystem through the global data center for the next production plan adjustment and team manpower reallocation optimization.

[0073] Step 6: The shipbuilding workshop manufacturing process monitoring subsystem achieves real-time closed-loop control on-site (corresponding to...) Figure 3Mid-process S6): The workshop execution control subsystem, acting as the on-site execution terminal, receives multi-level daily / weekly execution plans, process plan quantities, and standard working hour benchmarks from the global data hub. It also connects with workstation barcode scanning terminals, crane GPS positioning, workshop equipment sensors, and worker mobile check-in terminals to achieve real-time data collection and control across the entire process. 1. Real-time collection of full on-site data including segmented start / completion status, equipment start / stop operation, steel plate issuance and warehousing, and on-duty status of work teams; 2. Automatically match and compare on-site performance with the issued work team execution plan, automatically identify production bottlenecks such as process delays, long-term idle sites, crane idling, and material shortages, and push the results to production management personnel through system pop-ups and mobile messages. 3. Supports online fine-tuning of daily and weekly execution plans, and allows one-click initiation of three types of resource scheduling requests: site allocation, steel plate material ordering, and manpower support. Scheduling requests are pushed to the corresponding resource subsystems. 4. All collected data on completed work volume, actual working hours, equipment occupancy, and material requisition records must be verified through [the relevant documentation / process]. Figure 2 The dashed line performance feedback link is pushed to the global unified data center, and simultaneously distributed to the material quantity data control subsystem, the three resource management subsystems, the production planning management subsystem, and the time control subsystem, triggering the recalculation of system parameters and the iteration of solutions.

[0074] Step 7, System dynamic iterative optimization (corresponding to) Figure 3 (Mid-process S7 loop logic): The continuous feedback of on-site performance data from the workshop updates the global data center in real time, including material quantity verification thresholds, time correction coefficients, site occupancy load, steel plate inventory ledgers, and manpower team load. The system automatically re-executes step 3 (multi-dimensional resource optimization calculation), step 4 (multi-level planning), step 5 (time deviation analysis), and step 6 (workshop on-site management), iteratively executing steps 3 to 6, and continuously and dynamically adjusting the site layout, steel plate material issuance sequence, team manpower scheduling, and workshop weekly / daily production plan for the parallel construction of three types of ships. The project process terminates when all ship section processing, dock loading, and dock outfitting processes are completed.

[0075] This application example relies on Figure 1 A unified underlying data platform eliminates data silos across multiple systems, relying on Figure 2 A unified global data hub enables standardized two-way data interaction across seven subsystems, relying on Figure 3The seven-step closed-loop iterative process enables dynamic collaboration across the entire chain of planning, material quantity, working hours, resources, and on-site operations. Compared to the traditional manual decentralized management model, the manual workload for material quantity and working hour calculation is reduced by 96%, the manual coordination workload for conflicts in site, manpower, and steel plate resources among multiple ships operating in parallel is reduced by 70%, and the response speed for dynamic adjustment of production plans is increased by 65%. This achieves balanced, continuous, and lean production for the batch construction of multiple types of ships, fully realizing the invention's objectives of improving the execution capability of ship construction plans, balancing resource allocation, reducing manufacturing costs, and shortening the construction cycle.

[0076] Any matters not covered in the above embodiments of the present invention are well-known in the art.

[0077] The foregoing has described some specific embodiments of this application. It should be understood that this application is not limited to the specific embodiments described above, and those skilled in the art can make various modifications or variations within the scope of the claims, which do not affect the substantive content of this application. The above-described preferred features can be used in any combination without conflict.

Claims

1. A collaborative scheduling and control system for parallel construction of multiple types and multiple ships, characterized in that, include: The underlying global support base unit and the upper-layer business domain unit; wherein: The underlying global support base unit interfaces with the Aveva Marine ship design system, SAP supply chain system and / or workshop terminals externally, and communicates with the upper-level business domain unit internally. It stores all business data generated by the upper-level business domain unit into a unified database, and issues collaborative scheduling instructions to the upper-level business domain unit based on the global data to drive the upper-level business domain unit to recalculate the specified production plan and / or resource allocation scheme. The upper-level business domain unit includes: a production planning domain subunit and a field execution domain subunit; wherein: The production planning sub-unit is used to generate corresponding process-level engineering decomposition standards, standardized engineering quantities, and time calculation results based on the total construction period of multiple ships and ship design data files. At the same time, it obtains resource allocation schemes including site equipment, steel plate issuance, and team manpower based on resource requirements, and uses site load, steel plate inventory, and team manpower load as resource constraints. It integrates engineering quantities and time calculation coupling constraints with resource constraints to generate multi-level production plans. The multi-level production plans, standardized engineering quantities, time calculation results, and resource allocation schemes are sent to the field execution sub-unit as execution benchmarks. The on-site execution domain subunit is used to implement the production plan according to the execution benchmark. It uses the workshop terminal to collect on-site performance data in real time, including start and finish times, finished quantity, actual working hours, site and equipment occupancy, steel plate requisition, and team manpower on duty, and feeds the data back to the production plan domain to drive dynamic iterative optimization of various execution benchmarks.

2. The multi-type, multi-ship parallel construction collaborative scheduling and control system according to claim 1, characterized in that, The underlying global support base unit includes: a unified database module, a global scheduling module, a microservice gateway module, a message middleware module, an authentication module, a log auditing module, and an internal and external bidirectional API interface module; wherein: The unified database module is used to uniformly store various business data issued by the upper-level business domain units, including: material quantity, working hours, production plan, resources and on-site performance data, which constitute the whole domain data; The global scheduling module is used to identify the list of plan conflicts, resource overload warnings, on-site resource scheduling requests and plan execution deviation records from the global data to form collaborative events; the collaborative events are encapsulated into collaborative scheduling instructions and distributed to the target subsystem of the upper-layer business domain unit through the message middleware module to trigger the target subsystem to call its existing modules to recalculate the affected unexecuted production plans and / or resource configuration schemes; The microservice gateway module is used to uniformly manage the access permissions of all business interfaces of the upper-layer business domain unit and realize the routing and distribution of internal and external requests; The message middleware module is used to asynchronously transmit the real-time business data stream of the upper-layer business domain unit, enabling stable data interaction in high-concurrency scenarios. The permission authentication module is used to configure system functions and data access permissions by department and position; The log auditing module is used to record all data modification, plan change, and scheduling operation logs, and these logs are traceable. The internal and external bidirectional API interface module is used to connect externally to the Aveva Marine ship design system, SAP supply chain system, and workshop terminal, and internally to all business subsystems of the upper-level business domain unit.

3. The multi-type, multi-ship parallel construction collaborative scheduling and control system according to claim 1, characterized in that, The upper-level business domain units include: a production planning management subsystem, a material quantity data control subsystem, a work hour control subsystem, a site and equipment resource management subsystem, a steel plate yard management subsystem, a labor resource management subsystem, and / or a workshop execution control subsystem located in the field execution domain; wherein: In the production planning domain, the production planning management subsystem issues process-level engineering decomposition standards to the material quantity data control subsystem and the time control subsystem to unify the granularity of material quantity data and time data calculation. Simultaneously, it receives standardized engineering quantities and time calculation results from the two subsystems as coupling constraints for engineering quantities and time. Combined with various resource constraints, it generates a multi-ship, multi-level production plan. The site equipment resource management subsystem, steel plate yard management subsystem, and labor resource management subsystem receive resource requirements from the production planning management subsystem to generate resource allocation schemes, and then transmit back basic data on site load, steel plate inventory, and team human resource allocation as resource constraints. In the field execution domain, the workshop execution control subsystem receives execution benchmarks regarding production plans, quantities, working hours, and resource allocation from various subsystems in the production planning domain. It uses workshop terminals to collect real-time field performance data, including start and finish times, completed quantities, actual working hours, site and equipment occupancy, steel plate requisition, and on-duty personnel in work teams, and feeds all the data back into the production planning domain to drive dynamic iterative optimization of various execution benchmarks.

4. The multi-type, multi-ship parallel construction collaborative scheduling and control system according to claim 3, characterized in that, The production planning management subsystem includes: a multi-ship type basic data module, a line table master plan module, a multi-level workshop plan module, a plan conflict verification module, a mountain load calculation module, a plan version approval module, and a full-domain two-way data interface module; wherein: The multi-ship type basic data module is used to maintain ship type, ship number, section, region, process, milestone and work calendar, and generate unique identifiers for planning objects of different ship types according to the set hierarchical combination rules, forming planning basic data with unified codes for multiple types of ships. The overall planning module is used to establish a milestone network based on the contract delivery period and the total construction period of multiple ships, decompose the milestone tasks step by step according to the preset hierarchy, generate the process-level engineering decomposition standard, and decompose the initial planned tasks and resource requirements list based on the process-level engineering decomposition standard. The multi-level workshop planning module is used to receive initial planning tasks and integrate standardized engineering quantities, time calculation results and resource constraints as constraints to generate plant-level, workshop-level and team-level production plans step by step. The plan conflict verification module is used to perform conflict detection on multi-level production plans and output a plan conflict list based on the sequential relationship of processes, time windows, and the availability of site equipment, steel plates, and work groups. The mountain load calculation module is used to summarize the working hours and resource requirements of each ship and each process according to time period, compare them with the available resource capacity, and generate load curves and overload warnings. The plan version approval module is used to receive the conflict list, adjust the start time, end time, execution order or resource combination of unexecuted tasks according to the priority relationship of conflicting tasks and the available resource time window, call the plan conflict verification module to re-verify until the conflict is eliminated, obtain the production plan after the conflict is resolved, freeze, submit, approve and release the execution version of the production plan, and save the version differences and approval records. The full-domain bidirectional data interface module is used to issue process-level engineering decomposition standards to the material quantity data management and control subsystem and the time management subsystem, issue resource requirement lists to the three types of resource management subsystems, issue production plans to the workshop execution management and control subsystem, and receive standardized engineering quantities, time calculation results, various resource constraints, and on-site performance data; at the same time, it receives collaborative scheduling instructions to trigger the multi-level workshop planning module, planning conflict verification module, and / or load calculation module to perform plan rearrangement, conflict review, and / or load recalculation on the specified production plan.

5. The multi-type, multi-ship parallel construction collaborative scheduling and control system according to claim 3, characterized in that, The time management subsystem includes: a time standard library management module, a ship type section correction coefficient module, a planned time calculation module, an actual time comparison module, a production efficiency evaluation module, and a two-way interactive interface module; wherein: The time standard library management module is used to maintain the unit benchmark time and version of the unit project quantity according to job type, main job type, sub-job type, process and process element; The ship section correction coefficient module is used to read historical performance data from a unified database, perform sample classification and sample cleaning, calculate the ratio of actual working hours to unit benchmark working hours for each type of sample, and generate correction coefficients after statistical analysis and review. The planned working hours calculation module is used to match standardized engineering quantities, unit base working hours and correction coefficients according to the engineering decomposition standard, calculate the planned working hours of each segment and each process, and obtain the working hours calculation results. The actual working hours comparison module is used to receive the start and end times and personnel work reports collected by the workshop, form the actual working hours and compare them with the planned working hours to obtain the deviation rate between the planned working hours and the actual working hours. The production efficiency evaluation module is used to evaluate the production efficiency of ship type, section, process and team based on the deviation rate between planned working hours and actual working hours, and to feed back valid samples to the standard library to update the unit benchmark working hours. The bidirectional interactive interface module is used to receive process-level engineering decomposition standards issued by the production planning management subsystem, standardized engineering quantities output by the material quantity data control subsystem, and actual working hour feedback data returned by the workshop execution control subsystem, and to send working hour calculation results to the production planning management subsystem and the workshop execution control subsystem; at the same time, it receives collaborative scheduling instructions to trigger the planned working hour calculation module and / or the actual working hour comparison module to recalculate the planned working hours and / or the deviation rate between the planned working hours and the actual working hours for the corresponding process. The material quantity data management and control subsystem includes: a design data synchronization module, a multi-source material quantity extraction module, a hierarchical material quantity generation module, an intelligent verification rule base module, a material quantity database management module, and a two-way data interface module; wherein: The design data synchronization module is used to synchronize the ship's 3D model, segmented BOM and related design list from the Aveva Marine ship design system, and to complete the version and object code mapping. The multi-source material quantity extraction module is used to extract the work material quantity and attributes of parts, welds, painting areas and outfitting components from the ship's three-dimensional model, section BOM and multi-source heterogeneous design data according to the material quantity selection guide document. The intelligent verification rule base module is used to verify the extracted work quantity for missing items, duplicates, out-of-bounds, and BOM inconsistencies using process logic, numerical thresholds, and material matching rules, and outputs the verified extracted quantity. The hierarchical quantity generation module is used to collect the verified extracted quantities according to the main job, sub-job, process and process element according to the engineering decomposition standard to form a standardized engineering quantity dataset. The material quantity database management module is used to store original material quantities, data cleaning results, hierarchical aggregation relationships, version and verification result records; The bidirectional data interface module is used to receive process-level engineering decomposition standards issued by the production planning management subsystem, send standardized engineering quantities to the production planning management subsystem, time control subsystem and workshop execution control subsystem, and receive workshop completed material quantity feedback; at the same time, it receives collaborative scheduling instructions, triggers the multi-source material quantity extraction module and / or intelligent verification rule base module to re-extract and / or verify the material quantity data of the corresponding design object, and updates the standardized engineering quantities.

6. The multi-type, multi-ship parallel construction collaborative scheduling and control system according to claim 3, characterized in that, The site equipment resource management subsystem includes: a site equipment digital ledger module, a gridded site modeling module, a multi-objective genetic optimization algorithm module, a tire position / dock layout module, a crane and flatbed truck scheduling module, a resource conflict detection module, and a two-way interface module; wherein: The site equipment digital ledger module is used to maintain the spatial dimensions, load-bearing capacity, available time and real-time status of tire positions, docks, storage yards, cranes and flatbed trucks; The gridded site modeling module is used to discretize the yard area into grid cells with coordinate, size, load and occupancy period attributes, and establish a mapping between the segmented shape envelope and the grid cells to obtain the segmented position. The multi-objective genetic optimization algorithm module is used to encode, select, crossover, mutate and iteratively optimize the segment location, operation period and equipment combination with the objective functions of plan delay, yard vacancy, handling distance and equipment conflict. The tire position / dock layout module is used to generate a site configuration scheme for segmented tire placement, overall assembly, and dock use based on the optimization results and site requirements. The crane flatbed truck scheduling module is used to generate a lifting and transfer task sequence based on the segment weight, start and end positions, operation time window, equipment capacity and crane requirements, and obtain an equipment configuration scheme. The resource conflict detection module is used to detect situations such as overlapping site occupancy, duplicate equipment allocation, overload exceeding limits, and disjointed process times at the same time, and outputs the conflict objects and time periods. The bidirectional interface module is used to receive the initial planned tasks and resource requirement list from the production planning and management subsystem, obtain the initial site and crane requirements for tire positions, docks, yards, cranes, and flatbed trucks, and return the basic data of site and crane resource configuration loads. It also issues site and equipment configuration schemes to the workshop execution and control subsystem and receives real-time workshop site and / or equipment requirements from the workshop. Simultaneously, it receives collaborative scheduling instructions, triggers the multi-objective genetic optimization algorithm module and / or resource conflict detection module, and recalculates the site and equipment configuration scheme. The steel plate yard management subsystem includes: a steel plate basic file module, an RFID inbound / outbound data acquisition module, a yard gridded spatial model module, a segmented steel plate demand matching module, an inventory early warning module, a stacking optimization scheduling module, and a two-way interface module; wherein: The steel plate basic file module is used to maintain the steel plate number, specifications, material, batch, processing series, and scheduled usage time. The RFID inbound / outbound data acquisition module is used to collect events related to steel plate arrival, warehousing, pallet transfer, outbound, and shipment, and to update the inventory status. The gridded spatial model module for the stockyard is used to establish a three-dimensional coordinate index according to the stockyard area, stack position and layer number, and associate the stack position size, height, capacity and steel plate position. The segmented steel plate demand matching module is used to match steel plate demand with the material, specifications, batch and processing series in the inventory based on the segmented BOM, the monthly steel plate demand plan formed by summarizing the published multi-level production plans on a monthly basis, and the daily steel plate delivery plan formed by decomposing the monthly steel plate demand plan according to the segmented start date. The inventory early warning module is used to compare demand date, available inventory and safety stock, generate early warnings for material shortage, overstocking and overdue, and obtain basic data on steel plate inventory. The stacking optimization scheduling module is used to generate the scheduling results of the inbound, stacking and outbound sequences with the goal of minimizing the number of stacking times and the handling distance, under the constraints of stacking capacity, same series aggregation, first-in-first-out and planned use order, so as to obtain the steel plate configuration scheme. The bidirectional interface module is used to receive the initial planned tasks and resource requirement list from the production planning and management subsystem, obtain the steel plate requirements and the initial segmented production plan, return the basic steel plate inventory data, issue the steel plate configuration plan to the workshop execution and control subsystem, and receive the real-time steel plate requisition requirements from the workshop; at the same time, it receives collaborative scheduling instructions to trigger the segmented steel plate requirement matching module and / or the stacking optimization scheduling module to recalculate the steel plate matching and / or steel plate configuration plan. The labor resource management subsystem includes: a worker skills file module, a job efficiency coefficient database module, a manpower load calculation module, a medium- and long-term employment planning module, a flexible shift scheduling module, and a two-way interactive interface module; wherein: The worker skill file module is used to maintain the worker's work group, primary and secondary job types, skill level, qualification certificate, available time period, and historical work records. The job efficiency coefficient library module is used to calculate efficiency coefficients based on skill level evaluations and historical ratios of planned and actual working hours for similar tasks, and then publish them by job type and work group after review. The manpower load calculation module is used to convert the planned working hours of each process in each time period into the required number of workers according to the type of work and efficiency coefficient, and compare it with the available number of workers on duty to form the load and gap, and obtain the basic data of manpower load. The medium- and long-term employment planning module is used to summarize the manpower needs of multiple ship projects on a monthly and weekly basis, and generate suggestions for recruitment, outsourcing, shift adjustment and training. The flexible scheduling module for work teams is used to allocate work tasks to work teams and personnel under constraints such as skill matching, qualifications, working hour limits, rest time, and work team availability, thereby obtaining a work team manpower allocation plan. The bidirectional interactive interface module is used to receive the initial planned tasks and resource requirement list from the production planning and management subsystem, obtain the initial manpower requirement plan, return the basic manpower load data, issue the team manpower configuration plan to the workshop execution and control subsystem, and receive the real-time team manpower requirements fed back by the workshop; at the same time, it receives the collaborative scheduling instruction, triggers the manpower load calculation module and / or the team flexible scheduling module, and recalculates the basic manpower load data and / or the team manpower configuration plan.

7. The multi-type, multi-ship parallel construction collaborative scheduling and control system according to claim 3, characterized in that, The workshop execution control subsystem includes: a multi-terminal data acquisition interface module, a process progress tracking module, an online work dispatch management module, a production bottleneck early warning module, a dynamic plan fine-tuning module, a resource scheduling request initiation module, and a two-way interactive interface module; wherein: The on-site multi-terminal data acquisition interface module is used to connect to the workshop terminal and acquire data on actual working hours, completed work volume, personnel work reports, site and equipment occupancy, and material requisition. The process progress tracking module is used to calculate the completion rate and progress deviation by summarizing the planned and actual start and completion times, completed quantities and actual working hours of the tasks. The online work dispatch management module is used to receive published production plans and resource allocation schemes, and to assign process tasks, personnel, equipment and materials to workstations; The production bottleneck early warning module is used to identify events such as schedule delays, work-in-process backlogs, resource overload, and material and manpower shortages, and outputs the bottleneck type, location, and affected tasks. The dynamic planning fine-tuning module is used to adjust the start and end times and sequence of the unstarted production plan based on the on-site progress deviation without changing the frozen milestones. The resource scheduling request initiation module is used to generate scheduling requests with tasks, demand quantities, and time windows for material shortages, manpower shortages, and site and equipment conflicts. The bidirectional interactive interface module is used to receive production plans issued by the production planning management subsystem, standardized engineering quantities sent by the material quantity data control subsystem, and time calculation results sent by the time control subsystem. It also feeds back on-site performance data to the production planning management subsystem, completed material quantities to the material quantity data control subsystem, actual working hours to the time control subsystem, initiates resource requests to the three types of resource management subsystems, and receives resource allocation schemes from the three types of resource management subsystems. At the same time, it receives collaborative scheduling instructions to trigger the dynamic planning fine-tuning module to adjust the start and end times and execution order of the production plans that have not yet started.

8. A method for collaborative scheduling and control of parallel construction of multiple types and multiple ships, characterized in that, include: Based on the total construction period of multiple ships and ship design data files, corresponding process-level engineering decomposition standards, standardized engineering quantities and time calculation results are generated. Based on resource requirements, a resource allocation plan is obtained, including site and equipment, steel plate outbound and team manpower, and site load, steel plate inventory and team manpower load are used as resource constraints. By integrating standardized engineering quantities and time calculation results, coupling constraints between engineering quantities and time calculation are obtained, and multi-level production plans are generated in combination with the resource constraints. The execution benchmark is formed by utilizing the multi-level production plan, standardized engineering quantities, time calculation results, and resource allocation scheme. Production plans are implemented based on the aforementioned execution benchmarks, and real-time data on on-site performance, including start and completion times, completed quantities, actual working hours, site and equipment occupancy, steel plate requisition, and on-duty personnel in work teams, are collected to drive dynamic iterative optimization of various execution benchmarks. Generate collaborative scheduling instructions based on global data, and recalculate the specified production plan and / or resource allocation scheme based on the collaborative scheduling instructions.

9. A computer device for collaborative scheduling and management of parallel construction of multiple types and multiple ships, comprising a cloud server cluster as the backend and local terminals as the frontend; characterized in that, The cloud server cluster is deployed with the multi-type, multi-ship parallel construction collaborative scheduling and control system as described in any one of claims 1-7; wherein, the underlying global support base unit, production planning domain subunit, and field execution domain subunit of the multi-type, multi-ship parallel construction collaborative scheduling and control system adopts the Spring Cloud microservice architecture to implement backend business services, and relies on Dubbo RPC and RocketMQ to form a bidirectional interconnection link; the local terminal is used to provide access clients for the production planning domain subunit and the field execution domain subunit, as well as field interaction front-end and workshop terminal client; wherein, the access client is used to access the corresponding business services in the cloud server cluster, and display production plans, standardized engineering quantities, work hour calculation results, and resource configuration schemes; the field interaction front-end is used to display field performance data; the workshop terminal client is used to obtain field performance data and send the data to the cloud server cluster.

10. The computer equipment for collaborative scheduling and control of parallel construction of multiple types and multiple ships according to claim 9, characterized in that, The local terminal adopts a multi-terminal working structure, including: PC, tablet computer and / or smart mobile terminal.

Images