A data center prefabricated module collaborative assembly method and system

Abstract

This invention discloses a collaborative assembly method and system for prefabricated modules in data centers, relating to the field of digital assembly control technology. The method includes generating electronic assembly process packages using on-site data acquisition devices; establishing inter-module references, closed-face references, and work surface occupancy relationships based on the process packages, generating process access results, collaborative assembly sequence, and electronic process tickets; during on-site assembly, comparing the collected execution data with installation reference edges, adjacent closed faces, and allowable deviation ranges, writing back the positioning and closing status, and controlling the issuance of permanently fixed process tickets accordingly; after assembly, updating the subsequent assembly sequence and process tickets based on on-site feedback. The method of this invention, through the linkage between electronic assembly process packages and on-site status write-back, achieves prefabricated module access assignment, positioning verification, fixed control, and dynamic updates of subsequent processes, reducing assembly conflicts, interface misalignments, and rework, and improving the efficiency and construction controllability of modular assembly in data centers.

Description

Technical Field

[0001] This invention relates to the field of digital assembly control technology, specifically to a collaborative assembly method and system for prefabricated modules in a data center. Background Technology

[0002] As critical infrastructure supporting cloud computing, artificial intelligence training, financial transactions, and the operation of government and enterprise information systems, data centers are undergoing a shift in construction methods from traditional decentralized on-site construction to modular, prefabricated, and digitally assembled approaches. Prefabricated modular construction allows electromechanical units such as power supply and distribution, cooling, pipeline supports, low-voltage communication, fire protection, and monitoring and data acquisition to be processed, integrated, and initially tested in the factory, followed by rapid deployment through on-site hoisting, positioning, connection, and commissioning. With the application of technologies such as BIM detailed design, RFID identification, on-site measurement, hoisting positioning, and mobile construction terminals, the construction management of prefabricated data center modules has gradually acquired a data-driven, status-based, and traceable technological foundation, providing conditions for improving assembly accuracy, shortening construction cycles, and reducing the risks of overlapping on-site construction.

[0003] Existing data center prefabricated module assembly methods primarily focus on module processing, transportation planning, or installation schedule management. They typically schedule prefabricated modules as a whole construction project, lacking an assembly control mechanism that unifies and links module identity status, location status, work surface occupancy status, installation reference edges, adjacent closed surfaces, and procedures that cannot be pre-executed. Especially in actual construction, prefabricated modules often have multiple relationships, including reference points, adjacent fits, interface connections, maintenance allowances, and shared hoisting paths. Relying solely on manual experience or static construction plans for installation can easily lead to problems such as arranging attachment modules for hoisting before the reference module's positioning is confirmed, performing permanent fixing without verifying adjacent closed surfaces, and issuing subsequent installation tasks before the work surface is released. This results in module re-disassembly, interface misalignment, occupied maintenance space, and assembly cycle interruptions. Existing methods also struggle to write back on-site measurement data, hoisting execution data, and procedure completion status to subsequent assembly plans in real time. They cannot update procedure access results, coordinate assembly sequences, and electronic procedure tickets based on the reference edge positioning status, adjacent closed surface status, and work surface release status. Therefore, existing technologies are insufficient to achieve closed-loop collaborative assembly control of prefabricated data center modules, from process packaging, access assignment, on-site verification to feedback updates, and are unable to meet the requirements for positioning accuracy, process constraints, and continuous construction of multiple modules in high-density electromechanical module assembly scenarios. Summary of the Invention

[0004] In view of the above-mentioned problems, the present invention is proposed.

[0005] Therefore, the technical problem solved by this invention is that existing data center prefabricated module assembly methods lack a unified correlation between module assembly data and on-site status, making it difficult to participate in process access control based on the reference relationship, closed surface relationship, and work surface occupancy relationship between modules, and the on-site assembly feedback cannot be linked to update the subsequent assembly sequence and electronic process tickets. It also addresses the problem of how to achieve closed-loop control of prefabricated module collaborative assembly based on electronic assembly process packages, on-site data collection, and status write-back mechanisms.

[0006] To address the aforementioned technical problems, this invention provides the following technical solution: a collaborative assembly method for prefabricated data center modules, comprising acquiring design data, factory data, hoisting operation data, and on-site work surface data of the prefabricated data center modules; acquiring the identity status, location status, and work surface occupancy status of the prefabricated modules using an on-site acquisition device; generating an electronic assembly process package corresponding to each prefabricated module; establishing reference relationships, closed-face reference relationships, and work surface occupancy relationships between the prefabricated modules based on the electronic assembly process package; and generating process admission results and... The system coordinates the assembly sequence and issues electronic work tickets to the assembly execution terminal. Prefabricated modules are assembled on-site according to these electronic work tickets. The assembly execution data collected on-site is compared with the installation reference edge, adjacent closed surfaces, and allowable deviation range in the electronic assembly work package. The system generates and writes back the reference edge positioning status and adjacent closed surface status. Based on the reference edge positioning status, adjacent closed surface status, and processes that cannot be executed in advance, the system controls the issuance of permanently fixed work tickets. Based on the on-site execution feedback after prefabricated module assembly, the system updates the status feedback fields in the electronic assembly work package, and simultaneously updates the prefabricated module's process access results, coordinated assembly sequence, and electronic work tickets.

[0007] As a preferred embodiment of the data center prefabricated module collaborative assembly method described in this invention, the electronic assembly process package includes: module basic fields, spatial positioning fields, assembly operation fields, site status fields, and linkage control fields; the module basic fields include module number, module type, module version number, module external dimensions, module weight, lifting point position, interface type, interface position, and factory acceptance status; the spatial positioning fields include installation area number, installation coordinates, installation elevation, installation reference edge, adjacent closed surface, site measurement point, allowable deviation range, and adjacent module number; the assembly operation fields include preceding process number, process number, lifting path number, temporary stacking area number, personnel operation area number, maintenance reserved area number, and processes that cannot be executed in advance; the site status fields include identity status, work surface occupancy status, reference edge positioning status, adjacent closed surface status, fixed process access status, and work surface release status; the linkage control fields include reference reference module number, reference closed surface number, affected module number, electronic process ticket number, and electronic process ticket write-back status.

[0008] As a preferred embodiment of the data center prefabricated module collaborative assembly method described in this invention, the establishment of reference relationships, closed-face reference relationships, and work surface occupancy relationships among prefabricated modules includes: marking the prefabricated module as a reference module when its installation reference edge is referenced by the electronic assembly process package of other prefabricated modules; marking the prefabricated module as an attached module when its installation coordinates, installation direction, or adjacent closed surface requires reference to the measurement results of the reference module; marking the prefabricated module as a closed module when the release state of the hoisting path, personnel operation area, or maintenance reserved area is changed after the prefabricated module is permanently fixed; and marking the prefabricated module as an independent module when there are no installation reference edges, adjacent closed surfaces, or work surface release conditions referenced by other prefabricated modules, and writing the module marking results into the corresponding electronic assembly process package.

[0009] As a preferred embodiment of the collaborative assembly method for prefabricated data center modules described in this invention, the generation of process access results includes: generating an allowable hoisting result for the reference module when the identity status of the prefabricated module is verified, its preceding process status is satisfied, and the required work surface occupancy status is satisfied; generating an allowable hoisting result for the dependent module when the reference edge positioning status of the reference module referenced by the dependent module is confirmed, and the identity status, preceding process status, and work surface occupancy status of the dependent module are all satisfied; generating a waiting reference edge confirmation result when the reference edge positioning status referenced by the dependent module is pending confirmation, pending adjustment, or unconfirmed; generating a waiting closed surface confirmation result when the adjacent closed surface status referenced by the prefabricated module is pending confirmation, pending adjustment, or unconfirmed; and generating a post-installation result when the work surface occupied by the closed module after permanent fixing is still referenced by an incomplete electronic assembly process package.

[0010] As a preferred embodiment of the collaborative assembly method for prefabricated data center modules described in this invention, the on-site assembly of prefabricated modules according to the electronic work order includes: the assembly execution terminal reading the module number and module version number of the prefabricated module and comparing them with the module number and module version number in the electronic assembly work package; when the module number is consistent, the module version number is consistent, the transportation damage review status is passed, the on-site acceptance status is passed, the lifting point acceptance status is passed, and the lifting path, temporary storage area, installation area, and personnel operation area are in an available or released state, a lifting permission signal is output; when any state is not met, no lifting permission signal is output, and a corresponding identity review, lifting point review, or work surface release review work order is generated.

[0011] As a preferred embodiment of the collaborative assembly method for prefabricated data center modules described in this invention, the generation and writing back of the reference edge positioning status and adjacent closed surface status includes: collecting the actual boundary position, actual elevation, levelness, verticality, and orientation data of the prefabricated module through a field measurement device; comparing the collected data with the installation reference edge, field measurement points, and allowable deviation range in the electronic assembly process package; when the comparison result is within the allowable deviation range, the reference edge positioning status is updated to confirmed; when the comparison result exceeds the allowable deviation range and there is a corresponding adjustment method in the electronic assembly process package, the reference edge positioning status is updated to pending adjustment and an adjustment process ticket is issued; when the comparison result exceeds the allowable deviation range and there is no corresponding adjustment method, the reference edge positioning status is updated to unconfirmed; after the reference edge positioning status is confirmed, the actual spacing, interface reserved position, hole position correspondence status, maintenance reserved distance, and work passage status between the current prefabricated module and adjacent modules, structural foundations, supports, pipelines, or equipment interfaces are reviewed, and adjacent closed surface status is generated accordingly.

[0012] As a preferred embodiment of the collaborative assembly method for prefabricated data center modules described in this invention, the following steps are included: When the reference edge positioning status of the current prefabricated module is updated to "confirmed," query the prefabricated modules referencing the installation reference edge and update the corresponding process access result to "can be re-admitted"; when the adjacent closed surface status of the current prefabricated module is updated to "confirmed," query the prefabricated modules referencing the adjacent closed surface and re-determine whether to issue an interface connection process ticket or a permanent fixed process ticket; when the work surface release status of the current prefabricated module is updated to "released," query the prefabricated modules waiting for the work surface and regenerate the corresponding electronic process ticket; when the reference edge positioning status, adjacent closed surface status, or work surface release status changes from "confirmed" or "released" to "pending adjustment," "unconfirmed," or "unreleased," suspend the electronic process tickets referencing the corresponding status fields; when the on-site execution feedback includes an assembly interruption event, freeze the electronic process tickets of the current prefabricated module and related modules.

[0013] Another objective of this invention is to provide a collaborative assembly system for prefabricated data center modules. This system can perform on-site assembly of prefabricated modules according to the electronic work order, compare the assembly execution data collected on-site with the installation reference edge, adjacent closed surfaces, and allowable deviation range in the electronic assembly work package, generate and write back the reference edge positioning status and adjacent closed surface status, and solve the problem that current data center prefabricated module assembly methods have closed surface relationships and work surface occupancy relationships that are difficult to participate in process access control.

[0014] As a preferred embodiment of the data center prefabricated module collaborative assembly system of the present invention, it includes: a process package creation module, an access dispatch module, and an execution write-back module; the process package creation module is used to collect design data, factory data, hoisting operation data, and on-site work surface data of the prefabricated modules, and obtain the module identity, location, and work surface occupancy status by combining the on-site acquisition device, and generate electronic assembly process packages corresponding to each prefabricated module; the access dispatch module is used to establish the reference relationship, closed surface reference relationship, and work surface occupancy relationship between prefabricated modules based on the electronic assembly process packages, and generate process access results and collaborative assembly sequence according to the module identity status, work surface occupancy status, reference edge positioning status, and adjacent closed surface status; the execution write-back module is used to execute the on-site assembly of prefabricated modules according to the electronic process ticket, and write back the on-site measurement data, reference edge positioning status, adjacent closed surface status, fixed process execution status, and work surface release status to the electronic assembly process package.

[0015] A computer device includes a memory and a processor, the memory storing a computer program, and the processor executing the computer program as a step in implementing a method for collaborative assembly of prefabricated data center modules.

[0016] A computer-readable storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements the steps of a method for collaborative assembly of prefabricated data center modules.

[0017] The beneficial effects of this invention are as follows: The collaborative assembly method for prefabricated data center modules provided by this invention, through the step of generating electronic assembly process packages, unifies and links the design data, factory data, hoisting operation data, on-site work surface data, as well as identity status, location status, and work surface occupancy status of the prefabricated data center modules. This transforms the prefabricated modules from single installation objects into identifiable, verifiable, and rewritable digital process objects, providing a consistent data foundation for subsequent access judgment, assembly assignment, and status tracking, thereby avoiding inconsistencies in assembly basis caused by the dispersion of design, processing, transportation, and on-site information. By establishing benchmark reference relationships, closed surface reference relationships, and work surface occupancy relationships and generating process access results, the method achieves linked judgment of inter-module positioning dependencies, adjacent assembly relationships, and on-site work resource occupancy relationships. This is used to determine whether a module has the conditions for hoisting, connection, or post-installation, thereby improving the rationality of the collaborative assembly sequence and the accuracy of on-site assignment. By executing on-site assembly according to electronic work orders and comparing the assembly execution data with the installation reference edge, adjacent closed surfaces, and allowable deviation ranges, on-site confirmation of the reference edge positioning status and adjacent closed surface status is achieved. This ensures that modules meet the requirements for positioning, fitting, connection, and maintenance before proceeding to subsequent processes, thereby reducing interface misalignment, inability of adjacent modules to close, and assembly rework. By controlling the issuance of permanently fixed work orders based on the reference edge positioning status, adjacent closed surface status, and processes that cannot be executed prematurely, and by updating the subsequent process access results, collaborative assembly sequence, and electronic work orders in conjunction with on-site execution feedback, dynamic constraints and closed-loop updates of assembly execution results for subsequent modules are achieved. This prevents problems such as premature module fixing and continued construction before the work surface is released, thereby improving the continuity, accuracy, and construction controllability of data center prefabricated module assembly. Attached Figure Description

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

[0019] Figure 1 The first embodiment of the present invention provides an overall flowchart of a data center prefabricated module collaborative assembly method. Detailed Implementation

[0020] To make the above-mentioned objects, features, and advantages of the present invention more apparent and understandable, specific embodiments of the present invention will be described in detail below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of the present invention, and not all of them. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort should fall within the protection scope of the present invention.

[0021] Example 1, referring to Figure 1 As an embodiment of the present invention, a method for collaborative assembly of prefabricated data center modules is provided, comprising: S1: Obtain design data, factory data, hoisting operation data and on-site work surface data of the data center prefabricated modules, and combine them with on-site acquisition devices to obtain the identity status, location status and work surface occupancy status of the prefabricated modules, and generate electronic assembly process packages corresponding to each prefabricated module.

[0022] Furthermore, the design data, factory data, transportation arrival data, hoisting equipment data, site layout data, and construction zoning data of the prefabricated modules in the data center are collected and imported into the assembly management server. The assembly management server then generates electronic assembly process packages corresponding to each prefabricated module according to a unified module number, a unified coordinate reference, and a unified process field format.

[0023] The design data includes the BIM detailed model, prefabricated module installation coordinates, installation elevation, module outer contour boundary, module installation reference edge, adjacent closed surfaces, interface reserved positions, maintenance reserved space, bracket installation positions, pipeline passage areas, and equipment maintenance channels. The installation coordinates, installation elevation, module outer contour boundary, interface reserved positions, and maintenance reserved space are all sourced from the BIM detailed model or approved construction detailed drawings, and are converted to data within the same engineering coordinate system when imported into the assembly management server.

[0024] The factory data includes module number, module type, module version number, module dimensions, module weight, lifting point location, center of gravity location, interface type, interface location, interface direction, factory acceptance status, packaging status, and a list of accessories included in the box. Module types include prefabricated power distribution modules, UPS modules, battery modules, refrigeration equipment modules, integrated pipeline support modules, cabinet foundation modules, fire protection pipeline network modules, low-voltage communication modules, and monitoring and acquisition modules. The module factory data is provided by the prefabrication unit and is linked to RFID tags, QR code tags, or electronic nameplates on the modules.

[0025] The transportation arrival data includes module arrival time, transport vehicle number, unloading location, temporary storage area number, transportation damage review status, arrival acceptance status, and secondary transfer requirements. The transportation damage review status includes at least three states: "not reviewed," "review passed," and "review failed." The arrival acceptance status includes at least three states: "not accepted," "accepted," and "accepted failed." When generating electronic assembly process packages, the assembly management server uses the transportation damage review status and arrival acceptance status as prerequisite fields for determining whether a module is allowed to enter the hoisting process.

[0026] The lifting equipment data includes the lifting equipment number, equipment type, rated lifting capacity, boom length, allowable lifting radius, lifting slewing area, lifting path number, lifting gear number, lifting gear compatibility status, and equipment occupancy status. The lifting equipment data is generated jointly by the lifting plan, equipment parameter table, and lifting equipment positioning device. The positioning device is used to collect the real-time location of the lifting equipment, the occupancy status of the lifting path, and the occupancy status of the slewing area, and sends the collection results to the assembly management server.

[0027] The site layout data includes hoisting entrances, horizontal transport channels, temporary storage areas, module installation areas, personnel operation areas, maintenance reserve areas, adjacent connection work areas, material turnover areas, and safety isolation areas. The site layout data is managed according to area numbers. Each area has an area type, area boundaries, available work processes, release conditions, and associated module number. Area numbers are used to generate the occupancy status of work surfaces, preventing multiple assembly processes from simultaneously occupying the same hoisting path, temporary storage area, or personnel operation area.

[0028] At the construction site, RFID identification devices or QR code identification terminals are used to read the module number, module version number, and factory acceptance status of prefabricated modules; total stations, laser rangefinders, or visual measurement devices are used to collect data on the actual boundary position, elevation, levelness, and orientation of the modules; hoisting equipment positioning devices are used to collect data on the position of hoisting equipment, the occupancy status of the hoisting path, and the status of the hoisting slewing area; and work surface status collection devices are used to collect data on the occupancy status of temporary storage areas, installation areas, personnel operation areas, and maintenance reserved areas. The work surface status collection devices can be implemented using electronic fences, positioning tags, area scanning terminals, or a combination of manual confirmation and position verification at the construction terminal.

[0029] The assembly management server performs consistency processing on the collected data. First, it matches the module numbers in the BIM detailed model with the module numbers in the factory data; second, it converts the installation coordinates, installation elevations, and module boundaries of the prefabricated modules to the same engineering coordinate system; third, it maps the hoisting path numbers, temporary storage area numbers, installation area numbers, and personnel operation area numbers to the site layout data; finally, it writes the module numbers, work surface numbers, hoisting path numbers, installation reference edge numbers, and adjacent closed surface numbers into the same electronic assembly process package.

[0030] Each electronic assembly process package includes at least the following fields: module basic field, spatial positioning field, assembly operation field, on-site status field, and linkage control field.

[0031] The basic fields of the module include module number, module type, module version number, module dimensions, module weight, lifting point location, center of gravity location, interface type, interface location, interface direction, factory acceptance status, transportation damage review status, and on-site acceptance status.

[0032] The spatial positioning fields include installation area number, installation coordinates, installation elevation, installation reference edge, adjacent closed surfaces, on-site measurement points, allowable deviation range, interface reserved location, maintenance reserved space, and adjacent module number. Among them, the installation reference edge is used to determine the module installation direction, boundary position, or elevation reference; the adjacent closed surfaces are used to determine the fit, connection, gap, or maintenance reserved relationship between the current module and adjacent modules, structural foundations, supports, pipelines, or equipment interfaces.

[0033] Assembly operation fields include the preceding process number, subsequent process number, hoisting path number, temporary storage area number, personnel operation area number, maintenance reserved area number, corresponding construction terminal, hoisting terminal, measurement and verification terminal, processes that cannot be performed in advance, and permitted adjustment methods. Processes that cannot be performed in advance include permanent fixing, plate sealing installation, pipeline wrapping, cable bundling, and bracket locking. Permitted adjustment methods include shim adjustment, support fine-tuning, flexible connector adjustment, connector replacement, partial module reset, and re-measurement and verification. The specific adjustment methods shall be based on the methods described in the prefabricated module processing drawings, equipment installation instructions, special construction plans, or technical disclosure documents.

[0034] The on-site status fields include module identity status, work surface occupancy status, reference edge positioning status, adjacent closed surface status, fixed process access status, interface connection status, work surface release status, and abnormal impact status. Module identity status indicates whether the module number, module version number, factory acceptance status, and transportation verification status are consistent with the electronic assembly process package; work surface occupancy status indicates whether the hoisting path, temporary storage area, installation area, personnel operation area, and maintenance reserved area are in an accessible, occupied, or released state; reference edge positioning status indicates whether the module's installation reference edge has been measured and confirmed; adjacent closed surface status indicates whether the current module meets the closed surface requirements with adjacent modules or adjacent structures; fixed process access status indicates whether permanent fixing, plate sealing installation, pipeline wrapping, cable bundling, or bracket locking processes are permitted; and abnormal impact status indicates whether an abnormality affects the current module, adjacent modules, work surface release, or subsequent assembly processes.

[0035] The linkage control fields include the reference baseline module number, the reference closed surface number, the affected subsequent module number, the work ticket number, the work ticket issuance status, the work ticket write-back status, the paused work number, the frozen work number, and the bypass assembly candidate module number. By setting the linkage control fields, when the reference edge positioning status, adjacent closed surface status, or work surface release status of a certain module changes, the assembly management server can use it to update the electronic work tickets and collaborative assembly sequence of subsequent modules.

[0036] It should be noted that the allowable deviation range is recorded according to the data source. When the allowable deviation range originates from the BIM detailed model, the corresponding model component number and model version number are recorded; when it originates from the prefabricated module fabrication drawing, the fabrication drawing number and version are recorded; when it originates from the equipment manufacturer's installation instructions, the instruction manual name, equipment model, and page or chapter number are recorded; when it originates from the construction acceptance specification, the specification name and clause number are recorded; when it originates from the approved special construction plan, the plan name, approval date, and corresponding chapter are recorded. By recording the source of the allowable deviation range, subsequent benchmark edge positioning and adjacent closed surface verification have a clear data basis.

[0037] The assembly management server establishes reference relationships between prefabricated modules based on the installation reference edge, adjacent closed surfaces, work surface numbers, and subsequent process numbers in the electronic assembly process package. When the installation reference edge of a module is referenced by the electronic assembly process package of another module, the module is marked as a reference module; when the installation coordinates, installation direction, or adjacent closed surface of a module needs to reference the measurement results of the reference module, the module is marked as an attached module; when a module will change the lifting path, personnel operation area, or maintenance reserved area release status after it is permanently fixed, the module is marked as a closed module; when a module does not have an installation reference edge, adjacent closed surface, or work surface release condition referenced by other modules, the module is marked as an independent module.

[0038] After the module type is marked, the assembly management server generates an initial state for each electronic assembly process package. The module identity state is generated based on the RFID identification results, module version number, factory acceptance status, and transportation damage verification status; the work surface occupancy status is generated based on the on-site collection results of the hoisting path, temporary storage area, installation area, personnel operation area, and maintenance reserved area; the reference edge positioning status is set to "pending confirmation" before the on-site measurement is completed; the adjacent closed surface status is set to "pending confirmation" before the closed surface verification is completed; the fixed process access status is set to "fixing not allowed" before both the reference edge positioning status and the adjacent closed surface status are confirmed; and the abnormal impact status is set to "not triggered" before any abnormal event is collected.

[0039] After the electronic assembly process package is generated, the assembly management server associates it with the construction terminal, hoisting terminal, and measurement verification terminal, respectively. The construction terminal is used to receive tasks for module arrival acceptance, temporary stacking, coarse positioning, interface connection, and process handover; the hoisting terminal is used to receive tasks for hoisting, hoisting transfer, and hoisting release; and the measurement verification terminal is used to receive tasks for benchmark edge positioning measurement, adjacent closed surface verification, and deviation verification. After executing the corresponding task, each terminal sends the execution result back to the status feedback field in the electronic assembly process package.

[0040] S2: Based on the electronic assembly process package, establish the reference relationship, closed surface reference relationship and work surface occupancy relationship between prefabricated modules. According to the identity status, work surface occupancy status, reference edge positioning status and adjacent closed surface status, generate process access results and collaborative assembly sequence, and issue electronic process tickets to the assembly execution terminal.

[0041] Furthermore, the assembly management server reads the electronic assembly process package corresponding to each prefabricated module, and calls the module identity status, module type, previous process status, work surface occupancy status, reference edge positioning status, adjacent closed surface status, fixed process access status and abnormal impact status in the electronic assembly process package to generate the process access results of each prefabricated module, and forms a collaborative assembly sequence based on the process access results.

[0042] The process access result indicates whether the current prefabricated module is allowed to enter the hoisting, positioning, connection, or fixing processes in the current assembly batch. Process access results include at least: allowed hoisting, awaiting identity verification, awaiting completion of the preceding process, awaiting release of the work surface, awaiting confirmation of the reference edge, awaiting confirmation of the closed surface, subsequent installation, allowed parallel assembly, paused assembly, and frozen assembly. Each process access result is triggered by the status field in the electronic assembly process package and corresponds to an electronic process ticket that can be issued, paused, or updated.

[0043] The assembly management server first performs access control on the module identity status. The module identity status is composed of module number consistency, module version number consistency, factory acceptance status, transportation damage review status, and on-site acceptance status. When the module number read by the RFID reader or QR code reader matches the module number in the electronic assembly process package, the module version number read matches the module version number in the electronic assembly process package, and the factory acceptance status, transportation damage review status, and on-site acceptance status are all "passed," the module identity status is written as "Identity Confirmation Passed." If any of the above fields are not met, the module identity status is written as "Identity Pending Review," and a pending identity review result is generated; no hoisting process ticket is issued to the construction terminal or hoisting terminal.

[0044] After the module's identity status is "Identity Confirmed," the assembly management server continues to read the status of the preceding processes. The status of the preceding processes is determined by the execution results corresponding to the preceding process numbers in the electronic assembly process package. When the status of all processes corresponding to the preceding process number is "Completed" or "Released," the preceding process status is written as "Precedence Satisfied." When any preceding process number has a status of "Incomplete," "Pending Adjustment," "Unconfirmed," or "Frozen," the preceding process status is written as "Precedence Not Satisfied," and a result awaiting the completion of the preceding process is generated. Precedence processes include, but are not limited to, installation area cleanup, temporary storage area confirmation, hoisting path confirmation, baseline module positioning, adjacent module connection verification, and safety isolation settings.

[0045] After the preceding process status is satisfied, the assembly management server reads the work surface occupancy status. Work surface occupancy status includes the hoisting path status, horizontal transport channel status, temporary storage area status, module installation area status, personnel operation area status, maintenance reserved area status, and adjacent connected work area status. The status of each work surface is recorded as "Available," "Occupied," "Released," "Not Released," and "Entry Prohibited." When the hoisting path, temporary storage area, installation area, and personnel operation area required for the current prefabricated module are all "Available" or "Released," the work surface occupancy status is written as "Work Surface Satisfied"; when any work surface is "Occupied," "Not Released," or "Entry Prohibited," the work surface occupancy status is written as "Work Surface Not Satisfied," and a pending work surface release result is generated.

[0046] For prefabricated modules marked as baseline modules, the assembly management server reads their installation area status, hoisting path status, temporary storage area status, preceding process status, and work surface occupancy status. When the module's identity status is "Identity Confirmed Passed," the preceding process status is "Prerequisite Satisfied," and the work surface occupancy status is "Work Surface Satisfied," the process access result for the baseline module is written as "Hoisting Allowed," and a corresponding hoisting process ticket is generated. If any status is not satisfied, no hoisting process ticket is generated, and the unsatisfied field is written to the process access record of the baseline module.

[0047] For prefabricated modules marked as dependent modules, the assembly management server reads the referenced benchmark module number from its electronic assembly process package and queries the benchmark edge positioning status of the referenced benchmark module. When the benchmark edge positioning status of the referenced benchmark module is "confirmed," and the module identity status, preceding process status, and work surface occupancy status of the dependent module are all satisfied, the process access result of the dependent module is written as "lifting allowed." When the benchmark edge positioning status of the referenced benchmark module is "pending confirmation," "pending adjustment," or "unconfirmed," the process access result of the dependent module is written as "awaiting benchmark edge confirmation," and the generation of lifting process tickets for the dependent module is prohibited. When the benchmark edge positioning status of the referenced benchmark module is confirmed, but the required work surface of the dependent module is not satisfied, the process access result of the dependent module is written as "awaiting work surface release."

[0048] It should be noted that for prefabricated modules that need to form a closed connection with adjacent modules, the assembly management server reads the referenced closed surface number in its electronic assembly process package and queries the status of the corresponding adjacent closed surface. When the status of the adjacent closed surface is "confirmed," the module is allowed to enter the interface connection access judgment; when the status of the adjacent closed surface is "pending confirmation," "pending adjustment," or "unconfirmed," the process access result of the module is written as "waiting for closed surface confirmation," and no interface connection process ticket or permanent fixed process ticket is generated. The status of adjacent closed surfaces is formed by the subsequent on-site measurement and verification results and is used to control the fitting, connection, gap, and maintenance reservation relationships between adjacent modules.

[0049] For prefabricated modules marked as closed modules, the assembly management server reads the hoisting path, personnel operation area, maintenance reserved area, and adjacent connection work area that will be occupied or have their release status changed after the module is permanently fixed. It then checks if any incomplete electronic assembly process packages still reference the aforementioned work surfaces. If no incomplete electronic assembly process packages reference the aforementioned work surfaces, and the closed module's module identity status, preceding process status, and work surface occupancy status are all satisfied, the process access result for the closed module is written as "hoisting allowed." If incomplete electronic assembly process packages still reference the aforementioned work surfaces, the process access result for the closed module is written as "post-installation," and the generation of permanent fixing process tickets for the closed module is prohibited.

[0050] For prefabricated modules marked as independent modules, the assembly management server reads the status of the module's hoisting path, temporary stacking area, installation area, and personnel operation area, and compares it with the work surface occupancy records of other modules in the current assembly batch. If the work surface required by the independent module is not occupied by other modules in the current assembly batch, and both the module's identity status and the status of its preceding processes are satisfied, the process access result for the independent module is written as "parallel assembly allowed," and the independent module is added to the current parallel assembly batch. If the work surface required by the independent module is already occupied by other modules in the current assembly batch, its process access result is written as "waiting for work surface release," and it is carried over to subsequent assembly batches.

[0051] After generating the process access results for each prefabricated module, the assembly management server forms a collaborative assembly sequence based on these results. The collaborative assembly sequence is organized according to assembly batches. Each assembly batch records the module number, module type, electronic assembly process package number, process access result, hoisting path number, temporary storage area number, installation area number, referenced benchmark module number, referenced closed surface number, preceding process number, subsequent process number, prohibited processes for early execution, corresponding construction terminal, and corresponding hoisting terminal.

[0052] The generation process of the collaborative assembly sequence is constrained by the status fields in the electronic assembly process package. The reference module enters the assembly batch first to form the positioning reference for subsequent modules; the dependent module enters the assembly batch after its positioning status on the reference edge is "confirmed"; the closed module enters the assembly batch after its occupied hoisting path, personnel operation area or maintenance reserved area is no longer referenced by the incomplete process package; the independent module enters the parallel assembly batch when its required working surface does not conflict with other modules in the current batch.

[0053] To ensure that the collaborative assembly sequence can be written back and updated by subsequent on-site assembly processes, the assembly management server sets writeable fields in the collaborative assembly sequence. These writeable fields include module identity write-back field, reference edge positioning write-back field, adjacent closed surface write-back field, interface connection write-back field, fixed process execution write-back field, work surface release write-back field, and abnormal impact write-back field. After executing their respective processes, the construction terminal, hoisting terminal, measurement verification terminal, and work surface status acquisition device write the execution results into the aforementioned writeable fields.

[0054] Electronic work order tickets are generated based on the collaborative assembly sequence. Each electronic work order ticket includes at least the work order number, module number, name of the executed work order, execution terminal, execution work surface, prerequisite status requirements, permitted execution status, prohibited execution status, measurement verification requirements, result write-back field, and exception reporting field. The name of the executed work order includes incoming inspection, temporary stacking, hoisting and splicing, hoisting and transfer, coarse positioning, reference edge positioning, adjacent closed surface verification, interface connection, permanent fixing, single item testing, and work order handover.

[0055] When the process access result is "Lifting Allowed," the assembly management server issues lifting and connection process tickets and lifting and transfer process tickets to the lifting terminal, and installation area confirmation process tickets to the construction terminal. When the process access result is "Waiting for Identity Verification," only the identity verification process ticket is issued to the construction terminal. When the process access result is "Waiting for Work Surface Release," the assembly management server does not issue lifting process tickets and adds the corresponding module to the work surface waiting list. When the process access result is "Waiting for Baseline Confirmation," the assembly management server does not issue lifting process tickets and binds the module to its referenced baseline module number. When the process access result is "Waiting for Closed Surface Confirmation," interface connection process tickets and permanent fixing process tickets are not issued. When the process access result is "Post-installation," permanent fixing process tickets are not issued, but the post-assembly mark of the module is retained. When the process access result is "Parallel Assembly Allowed," the assembly management server issues parallel assembly process tickets to the corresponding construction terminal, lifting terminal, and measurement verification terminal, respectively.

[0056] Before issuing electronic work orders, the assembly management server compares the work surface occupancy records within the same assembly batch. The comparison includes checking for duplicate hoisting path numbers, temporary storage area numbers, installation area numbers, personnel operation area numbers, and maintenance reserved area numbers. If the occupancy process corresponding to the same work surface number appears repeatedly within the same time period, the later generated electronic work order will be set to "to be issued after release"; if the process corresponding to the same work surface number starts only after the previous process is completed, issuance is allowed in the order of completion.

[0057] The assembly management server also imposes access restrictions on permanent fixing, plate sealing installation, pipeline wrapping, cable bundling, and bracket locking processes based on the "cannot be executed in advance" process field. Permanent fixing process tickets are not generated until the reference edge positioning status of the current module is updated to "confirmed"; plate sealing installation, pipeline wrapping, and cable bundling process tickets are not generated until the adjacent closed surface status of the current module is updated to "confirmed"; and subsequent module process tickets referencing the current work surface are not released until the work surface release status of the current module is updated to "released".

[0058] After generating the collaborative assembly sequence, the assembly management server sends the sequence to the construction terminal, hoisting terminal, measurement and verification terminal, and site management terminal. The construction terminal displays the work order, prerequisite status requirements, and result write-back items for the current module; the hoisting terminal displays the hoisting path, hoisting equipment number, hoisting connection status, and hoisting release requirements; the measurement and verification terminal displays the reference edge measurement points, adjacent closed surface verification items, and allowable deviation ranges; and the site management terminal displays the current assembly batch, waiting list, subsequent installation list, parallel assembly list, and paused assembly list.

[0059] The collaborative assembly sequence is not fixed after it is generated. When the reference edge positioning status, adjacent closed surface status, fixed process execution status, work surface release status, or abnormal impact status of any prefabricated module changes, the assembly management server reads the changed status fields and re-triggers the process admission result generation process. The regenerated process admission result is used to update the issuance, suspension, release, freeze, or postponement status of subsequent electronic process tickets.

[0060] S3: Perform on-site assembly of prefabricated modules according to the electronic work ticket, compare the assembly execution data collected on-site with the installation reference edge, adjacent closed surface and allowable deviation range in the electronic assembly work package, generate and write back the reference edge positioning status and adjacent closed surface status; control the issuance of permanent fixed work tickets based on the reference edge positioning status, adjacent closed surface status and work that cannot be executed in advance.

[0061] Furthermore, after receiving the electronic work order from the assembly management server, the construction terminal, hoisting terminal, and measurement verification terminal execute the on-site assembly of the prefabricated modules according to the module number, execution process name, execution work surface, hoisting path number, prerequisite status requirements, measurement verification requirements, and result write-back fields recorded in the electronic work order. The on-site assembly process includes module identity verification, hoisting access confirmation, hoisting and transportation, coarse positioning, reference edge positioning, adjacent closed surface verification, interface connection, permanent fixing, and assembly result write-back.

[0062] Before the prefabricated modules enter the hoisting and transportation stage, the construction terminal uses RFID identification devices, QR code identification terminals, or electronic nameplates to read the module number, module version number, and module factory acceptance information, and uploads the reading results to the assembly management server. The assembly management server compares the read module number with the module number in the electronic assembly process package, compares the read module version number with the module version number in the electronic assembly process package, and reads the transportation damage verification status, on-site acceptance status, hoisting point acceptance status, and accompanying accessories verification status.

[0063] When the module number, module version number, transportation damage verification status, on-site acceptance status, lifting point acceptance status, and accompanying accessories verification status are all consistent, the assembly management server will update the module's identity status to "Identity Confirmation Passed." If any of the above fields are inconsistent or the status is not "Passed," the assembly management server will update the module's identity status to "Identity Pending Verification," will not output a lifting permission signal to the lifting terminal, and will issue the corresponding identity verification procedure ticket or on-site verification procedure ticket to the construction terminal.

[0064] After a module's identity status is "Identity Confirmed," the assembly management server reads the corresponding hoisting path status, temporary storage area status, installation area status, personnel operation area status, and safety isolation area status. These statuses are generated by the hoisting equipment positioning device, work surface status acquisition device, electronic fence, positioning tags, or on-site barcode scanning terminal. When the hoisting path status is "Released" or "Available," the temporary storage area status is "Available," the installation area status is "Open," the personnel operation area status is "Released," and the safety isolation area status is "Set," the assembly management server outputs a hoisting permission signal to the hoisting terminal and updates the hoisting connection and hoisting transfer work tickets to "Permission to Execute." When any status is "Occupied," "Not Released," "Entry Prohibited," or "Not Set," the assembly management server does not output a hoisting permission signal and writes the corresponding field to the module's work ticket anomaly reporting field.

[0065] After receiving the lifting permission signal, the lifting terminal performs lifting and attachment and lifting transfer according to the lifting equipment number, lifting tool number, lifting point position, lifting path number, and lifting release requirements recorded in the electronic work order. During the lifting process, the lifting equipment positioning device continuously uploads the lifting equipment position, lifting slewing area status, and lifting path occupancy status; when the lifting equipment position enters the lifting path range recorded in the electronic work order, the assembly management server updates the lifting path status to "occupied"; when the lifting transfer is completed and the lifting equipment leaves the lifting path range, the lifting path status is updated to "awaiting release confirmation".

[0066] After the prefabricated modules are hoisted to the installation area, the construction terminal performs a coarse positioning process. This process ensures the modules are positioned within the installation area specified in the electronic assembly process package and that their outer contours fall within the pre-defined installation range. Upon completion of coarse positioning, the measurement verification terminal retrieves the field measurement points, installation coordinates, installation elevation, installation reference edge, and allowable deviation range from the electronic assembly process package. It then uses a total station, laser rangefinder, or visual measurement device to collect data on the module's actual boundary position, actual elevation, levelness, verticality, orientation, and the position of the installation reference edge.

[0067] The measurement verification terminal uploads the collected data on actual boundary positions, actual elevations, levelness, verticality, and orientation to the assembly management server. The assembly management server converts the on-site measurement data to an engineering coordinate system consistent with the BIM detailed model, prefabricated module fabrication drawings, and electronic assembly process packages, and compares each on-site measurement point recorded in the electronic assembly process package. The comparison includes whether the module installation coordinates are within the allowable deviation range from the design installation coordinates, whether the actual elevation is within the allowable deviation range from the design elevation, whether the positional relationship between the module boundary line and the installation reference edge is within the allowable deviation range, and whether the module orientation is consistent with the installation direction recorded in the electronic assembly process package.

[0068] When all on-site measurement data are within the allowable deviation range recorded in the electronic assembly process package, the assembly management server updates the baseline positioning status to "Confirmed" and writes the baseline positioning measurement results into the baseline positioning write-back field. If any measurement data exceeds the allowable deviation range, but the allowable adjustment method field in the electronic assembly process package records a corresponding adjustment method, the assembly management server updates the baseline positioning status to "Pending Adjustment" and issues an adjustment process ticket to the construction terminal. The adjustment process ticket records the measurement points to be adjusted, the fields exceeding the allowable deviation range, the corresponding adjustment method, and the post-adjustment verification requirements. If any measurement data exceeds the allowable deviation range, and the electronic assembly process package does not record a corresponding adjustment method, the assembly management server updates the baseline positioning status to "Unconfirmed" and suspends interface connection process tickets and permanently fixed process tickets.

[0069] It should be noted that when the reference edge positioning status is updated to "Pending Adjustment," the construction terminal performs shim adjustment, support fine-tuning, flexible connector adjustment, connector replacement, module partial reset, or re-measurement and verification according to the adjustment procedure ticket. After the adjustment procedure is completed, the measurement and verification terminal re-collects the data of the corresponding measurement points and uploads it to the assembly management server. The assembly management server performs measurement data comparison again; when the re-collected data is within the allowable deviation range, the reference edge positioning status is updated from "Pending Adjustment" to "Confirmed"; when the re-collected data is still not within the allowable deviation range, the "Pending Adjustment" status is maintained or updated to "Unconfirmed" according to the processing method in the electronic assembly procedure package.

[0070] After the baseline positioning status is updated to "Confirmed," the assembly management server reads the adjacent closed surface number, adjacent module number, interface connection object, maintenance reserved space, gap requirements, connection reserved position, and subsequent work space requirements from the electronic assembly process package, and issues an adjacent closed surface verification process ticket to the measurement verification terminal. The adjacent closed surface verification process ticket includes at least the closed surface number, adjacent module number, verification point, verification item, allowable deviation range, verification result write-back field, and handling procedures for failure.

[0071] During the verification of adjacent closed surfaces, the measurement and verification terminal collects closed surface data between the current module and adjacent modules, structural foundations, supports, pipelines, or equipment interfaces using a total station, laser rangefinder, visual measurement device, or construction terminal. The closed surface data includes the actual spacing between adjacent connection surfaces, mating positions, reserved interface positions, hole correspondences, pipeline crossing positions, maintenance reserved distances, personnel operating space status, and subsequent work passage status. This data is then compared item by item with the adjacent closed surface requirements, interface connection objects, maintenance reserved space, and allowable deviation ranges specified in the electronic assembly process package.

[0072] When the actual spacing, reserved interface positions, hole correspondence, maintenance reserved distance, and subsequent operation channel status of adjacent connection surfaces all meet the requirements recorded in the electronic assembly process package, the assembly management server updates the status of adjacent closed surfaces to "Confirmed". When a verification item does not meet the requirements, but the allowed adjustment method field in the electronic assembly process package records a corresponding adjustment method, the assembly management server updates the status of adjacent closed surfaces to "Pending Adjustment" and issues a closed surface adjustment process ticket and a re-verification process ticket to the construction terminal. When a verification item does not meet the requirements, and the electronic assembly process package does not record a corresponding adjustment method, the assembly management server updates the status of adjacent closed surfaces to "Unconfirmed" and locks the permanent fixing, plate installation, pipeline wrapping, cable bundling, and bracket locking processes.

[0073] After the status of adjacent closed surfaces is updated to "Confirmed," the assembly management server issues interface connection work tickets to the construction terminal based on the interface connection objects and interface types in the electronic assembly work package. Interface connection work tickets are differentiated according to interface type, and at least include electrical interface connection work tickets, piping interface connection work tickets, communication interface connection work tickets, fire protection interface connection work tickets, and control interface connection work tickets. Each type of interface connection work ticket includes an interface number, connection object, connection location, connection direction, connection tool, connection completion confirmation items, test items, and result write-back fields.

[0074] After the electrical interface connection is completed, the construction terminal uploads the grounding connection status, insulation test status, phase sequence verification status, and cable termination status; after the pipeline interface connection is completed, the construction terminal uploads the pipe connection status, valve group connection status, pressure test status, and leak detection status; after the communication interface connection is completed, the construction terminal uploads the link connectivity status, equipment address identification status, and data acquisition status; after the fire protection interface connection is completed, the construction terminal uploads the fire signal connection status, alarm test status, and linkage response status; after the control interface connection is completed, the construction terminal uploads the control point identification status, remote start / stop status, and status feedback acquisition status. The assembly management server writes the above results into the interface connection write-back field respectively.

[0075] After the interface connection status meets the connection completion requirements of the corresponding interface in the electronic assembly process package, the assembly management server reads the fixed process admission status. The fixed process admission status is jointly determined by the reference edge positioning status, adjacent closed surface status, interface connection status, and the field of processes that cannot be executed in advance. When the reference edge positioning status is "confirmed", the adjacent closed surface status is "confirmed", and the interface connection status that needs to be completed in advance is "completed" or "test passed", the assembly management server updates the fixed process admission status to "fixed allowed" and issues a permanent fixed process ticket to the construction terminal.

[0076] When the baseline positioning status is not "confirmed", the adjacent closed surface status is not "confirmed", or the interface connection status that needs to be completed beforehand is not "completed" or "test passed", the assembly management server will keep the fixed process access status as "fixing not allowed" and will not issue a permanent fixed process ticket. Before the permanent fixed process ticket is issued, the construction terminal will not display the execution entry points for permanent fixing, plate sealing installation, pipeline wrapping, cable bundling, and bracket locking; if the field terminal uploads the early execution record of the above processes, the assembly management server will update the abnormal impact status to "assembly interruption event" and lock the subsequent process tickets of the current module.

[0077] After receiving the permanent fixing work order, the construction terminal performs the permanent fixing according to the fixing location, fixing part number, tightening sequence, verification items, and result write-back fields recorded on the work order. After the permanent fixing is completed, the construction terminal uploads the fixing part installation status, tightening completion status, verification photos or verification records, fixing completion time, and the terminal number of the executor. The assembly management server writes the execution status of the permanent fixing work order into the fixed work order execution write-back field and updates the status of work orders that cannot be executed in advance from "not executed" to "executed according to the order".

[0078] After permanent fixing, the measurement and verification terminal performs a post-fixation retest of the module's installation coordinates, elevation, levelness, orientation, adjacent closed surfaces, and maintenance reserved space according to the retest requirements in the electronic assembly process package. When the post-fixation retest result is within the allowable deviation range, the assembly management server updates the module's post-fixation retest status to "Retest Passed"; when the post-fixation retest result is not within the allowable deviation range, the post-fixation retest status is updated to "Retest Failed," and the server determines whether to generate an adjustment process, reset process, or subsequent process suspension result based on the exception field.

[0079] After the module completes interface connection and permanent fixation, the construction terminal performs work handover, the hoisting terminal uploads the release status of the hoisting equipment, and the work surface status acquisition device uploads the release status of the hoisting path, installation area, personnel operation area, maintenance reserved area, and adjacent connected work areas. When the hoisting equipment has exited the corresponding hoisting path, the construction personnel have completed the work handover, temporary supports and tools have been removed from the corresponding work surface, and all work surface release items recorded in the electronic assembly work package have been confirmed, the assembly management server updates the work surface release status to "Released". When any work surface release item is not confirmed, the work surface release status is updated to "Not Released", and subsequent modules referencing that work surface are kept in a waiting state.

[0080] During on-site assembly, the construction terminal, hoisting terminal, and measurement verification terminal upload the execution results according to the write-back fields in the electronic work order. The execution results include at least the module identity verification result, hoisting permission signal status, hoisting completion status, reference edge positioning status, adjacent closed surface status, interface connection status, fixing process execution status, post-fixing re-measurement status, work surface release status, and abnormal event number. The assembly management server writes the above execution results into the write-back fields in the collaborative assembly sequence, enabling subsequent electronic work orders to be released, paused, frozen, bypassed, or reissued based on the current module's actual status.

[0081] S4: Based on the on-site execution feedback after the prefabricated module is assembled, update the status feedback field in the electronic assembly process package, and update the process access result, collaborative assembly sequence and electronic process ticket of the prefabricated module in a linked manner.

[0082] Furthermore, after the prefabricated modules have completed hoisting, positioning, closed-face verification, interface connection, permanent fixing, post-fixing re-measurement, or process handover, the construction terminal, hoisting terminal, measurement verification terminal, hoisting equipment positioning device, and work surface status acquisition device respectively upload on-site execution feedback to the assembly management server. The assembly management server updates the status fields in the corresponding electronic assembly process package based on the on-site execution feedback, and based on the changes in the status fields, performs release, suspension, freezing, bypass generation, or reissue processing on subsequent electronic process tickets.

[0083] On-site execution feedback includes module identity verification results, hoisting execution results, reference edge positioning results, adjacent closed surface verification results, interface connection results, permanent fixing execution results, post-fixing retest results, work surface release results, individual test results, and abnormal event records. Each piece of on-site execution feedback corresponds to a result write-back field in the electronic assembly process package, and verbal confirmation or manual remarks are not used as the sole basis for judgment.

[0084] Module identity verification results include module number consistency results, module version number consistency results, factory acceptance status, transportation damage verification status, on-site acceptance status, lifting point acceptance status, and accompanying accessories verification status. Lifting execution results include lifting permission signal status, lifting connection status, lifting path occupancy status, lifting and transfer completion status, and lifting equipment release status. Reference edge positioning results include actual installation coordinates, actual installation elevation, module boundary position, levelness, verticality, orientation, measurement point number, and allowable deviation range comparison results. Adjacent closed surface verification results include closed surface number, adjacent module number, actual spacing, interface reserved position, hole position correspondence status, maintenance reserved distance, subsequent operation channel status, and closed surface confirmation status. Interface connection results include interface number, interface type, connection object, connection completion status, test status, and interface anomaly record. Permanent fixing execution results include fixing process ticket number, fixing component number, fastening completion status, fixing completion time, post-fixing retest status, and non-advanceable process execution status. The release status of the work area includes the release status of the hoisting path, the horizontal transport channel, the temporary storage area, the installation area, the personnel operation area, the maintenance reserved area, and the adjacent connected work area.

[0085] After receiving on-site execution feedback, the assembly management server first determines the feedback object based on the module number and electronic assembly process package number, and then writes the on-site execution feedback into the corresponding status feedback field. The status feedback field includes at least the module identity status, reference edge positioning status, adjacent closed surface status, interface connection status, fixed process execution status, post-fixing retest status, work surface release status, and abnormal impact status. Each status field retains the original status, updated status, status update time, status source terminal, and corresponding process ticket number.

[0086] When a status feedback field changes, the assembly management server determines the subsequent electronic work tickets that need to be updated based on the changed field. Subsequent electronic work tickets include attachment module work tickets that reference the current module's installation reference edge, interface connection work tickets that reference the current module's adjacent closed surface, hoisting work tickets that reference the current module's release work surface, test work tickets that depend on the current module's interface connection results, and sealing, wrapping, binding, or bracket locking work tickets that depend on the current module's permanent fixing results.

[0087] For the write-back of the reference edge positioning status, the assembly management server processes it as follows: When the reference edge positioning status of the current module is updated from "pending confirmation" or "pending adjustment" to "confirmed," the assembly management server queries all subsequent electronic assembly process packages that reference the installation reference edge and updates the process access result of the corresponding module from "waiting for reference edge confirmation" to "can be re-accessed." Then, it reads the module identity status, preceding process status, and work surface occupancy status of the subsequent module and re-determines whether to generate a hoisting process ticket. When the reference edge positioning status of the current module is updated from "confirmed" to "pending adjustment" or "unconfirmed," the assembly management server suspends all unexecuted hoisting process tickets, reference edge positioning process tickets, and interface connection process tickets that reference the installation reference edge, and issues a reference verification task to the corresponding construction terminal.

[0088] For the write-back of adjacent closed surface status, the assembly management server processes it as follows: When the status of the adjacent closed surface of the current module is updated from "Pending Confirmation" or "Pending Adjustment" to "Confirmed", the assembly management server queries all subsequent electronic work tickets referencing that closed surface number and updates the corresponding module's work access result from "Waiting for Closed Surface Confirmation" to "Can Re-access Judgment"; when the interface connection object, work surface occupancy status, and preceding work status of the corresponding module all meet the requirements of the electronic assembly work package, an interface connection work ticket is issued. When the status of the adjacent closed surface of the current module is updated from "Confirmed" to "Pending Adjustment" or "Unconfirmed", the assembly management server suspends all interface connection work tickets, permanent fixing work tickets, plate sealing installation work tickets, pipeline wrapping work tickets, and cable bundling work tickets referencing that closed surface number and not yet executed.

[0089] For the write-back of interface connection status, the assembly management server handles it as follows: When the interface connection status of the current module is updated to "Completed" or "Test Passed", the assembly management server queries all subsequent single test work tickets, linked test work tickets, and permanent fixed work tickets that depend on the interface connection result; if other prerequisite states specified in the corresponding electronic assembly work package have also been met, then the subsequent work ticket is issued. When the interface connection status of the current module is updated to "Connection Incomplete", "Test Failed", or "Interface Pending Review", the assembly management server suspends subsequent test work tickets and fixed work tickets that depend on the interface connection result, and issues an interface review work ticket to the construction terminal.

[0090] For the write-back of fixed process execution status, the assembly management server handles it as follows: When the fixed process execution status of the current module is updated to "Executed by Ticket" and the post-fixed retest status is "Retest Passed," the assembly management server treats this module as a fixed module for subsequent assembly admission judgment and releases the subsequent module process tickets that depend on the fixed result. When the fixed process execution status is "Not Executed," the sealing, wrapping, binding, bracket locking, or adjacent module closure process tickets that depend on the fixed result are not released. When the fixed process execution status is "Executed Ahead of Schedule," the assembly management server updates the abnormal impact status to "Assembly Interruption Event," freezes the subsequent electronic process tickets of the current module and directly related modules, and generates a fixed status review task.

[0091] For the write-back of the work surface release status, the assembly management server handles it as follows: When the status of a work surface referenced by subsequent modules in the hoisting path, horizontal transport channel, temporary stacking area, installation area, personnel operation area, maintenance reserved area, and adjacent connected work area changes from "occupied" or "not released" to "released," the assembly management server queries the electronic assembly process packages waiting for that work surface and re-executes the process access judgment. If the module identity status, preceding process status, reference edge positioning status, and closed surface status of the subsequent module all meet the requirements, the corresponding electronic process ticket is issued. If the work surface release status changes from "released" to "not released" or "entry prohibited," all electronic process tickets referencing that work surface and not yet executed are suspended, and the corresponding module is added to the work surface waiting list.

[0092] For abnormal event records, the assembly management server determines the abnormal impact status based on the affected object and executes corresponding linkage processing. Abnormal impact status includes adjustment events in this module, adjacent related events, work surface blockage events, and assembly interruption events.

[0093] It should be noted that when an anomaly only corresponds to the current module's reference edge positioning status, temporary fixing status, interface connection status, or post-fixing retest status, and does not change the installation reference edge status referenced by other modules, the adjacent closed surface status, or the work surface release status, the anomaly's impact status will be written as "Module Adjustment Event". For Module Adjustment Events, the assembly management server adds adjustment and review work tickets to the current module's electronic assembly work package, and subsequent module electronic work tickets maintain their original status; after the adjustment and review work are completed and passed, the corresponding status field of the current module is updated.

[0094] When an anomaly causes the status of an installation reference edge referenced by other modules to change from "confirmed" to "pending adjustment" or "unconfirmed," or causes the status of a referenced adjacent closed surface to change from "confirmed" to "pending adjustment" or "unconfirmed," the anomaly's impact status is written as an "adjacent involvement event." For adjacent involvement events, the assembly management server queries subsequent modules that have reference relationships, closed surface reference relationships, or interface connection relationships with the current module, suspends their unexecuted hoisting, interface connection, and permanent fixing work tickets, and issues review tasks to adjacent modules.

[0095] When an anomaly causes the release status of the hoisting path, horizontal transport channel, temporary storage area, installation area, personnel operation area, or maintenance reserved area to change from "released" to "not released" or "entry prohibited," the anomaly's impact status is recorded as a "work surface blocking event." For work surface blocking events, the assembly management server reads the work surface numbers of all pending electronic assembly process packages, filters out modules that do not reference the blocked work surface, and generates bypass assembly batches based on their module identity status, preceding process status, reference edge positioning status, and closed surface status; modules that still reference the blocked work surface are updated to "awaiting work surface release."

[0096] When an anomalies are due to module version inconsistency, incorrect installation direction, failure to pass hoisting point acceptance, premature execution of permanent fixing, premature installation of sealing plates, premature execution of pipeline wrapping, premature execution of cable bundling, premature execution of bracket locking, or inability to restore adjacent closed surfaces, the impact of the anomaly will be recorded as an "Assembly Interruption Event." For assembly interruption events, the assembly management server freezes the subsequent electronic work tickets for the current module and directly related modules, and generates rework tasks, reset tasks, re-hoisting tasks, or design review tasks. Frozen electronic work tickets will not be issued to the construction terminal, hoisting terminal, or measurement review terminal until the freeze is lifted.

[0097] Release, pause, freeze, bypass generation, and reissue are executed as follows: Release means the prerequisite status requirements for the electronic work ticket have been met. The assembly management server updates the electronic work ticket from "awaiting issuance" to "allowed execution" and sends it to the corresponding terminal. Pause means the electronic work ticket has not yet been executed, but its dependent status fields have changed from satisfied to pending confirmation, pending adjustment, unconfirmed, not released, or failed. The assembly management server updates the electronic work ticket from "allowed execution" to "paused execution." Freeze means the module corresponding to the electronic work ticket has an assembly interruption event. The assembly management server updates the electronic work ticket to "frozen execution" and prohibits the generation of subsequent work tickets for the same module. Bypass generation means that when a work surface blocking event occurs, the assembly management server selects modules from the pending execution modules that do not reference the blocked work surface and generates a new assembly batch. Reissue means that after the exception handling is completed, the assembly management server regenerates the electronic work ticket based on the updated status fields and establishes a replacement relationship between the new electronic work ticket number and the original electronic work ticket number.

[0098] During bypass generation, the assembly management server filters the modules to be executed using the following criteria: the module's identity status is "Identity Confirmed"; the preceding process status is "Prerequisites Fulfilled"; the required hoisting path, temporary storage area, installation area, and personnel operation area are not part of the blocked work surface; the reference edge positioning status referenced by the attached module is "Confirmed"; the adjacent closed surface status of the module requiring closed surface confirmation is "Confirmed"; and the fixed process access status matches the process to be executed. Modules that meet the above conditions are added to the bypass assembly batch, while modules that do not meet any of the conditions are kept in the waiting list, and the reason for not adding them is recorded.

[0099] When reissuing electronic work orders, the assembly management server assigns a new work order number to the newly generated electronic work order, while retaining the original work order number, suspension reason, freeze reason, bypass generation reason, or reissuance reason. The reissued electronic work order includes at least the module number, execution work name, execution terminal, execution work surface, prerequisite status requirements, measurement verification requirements, allowed execution status, prohibited execution status, and result write-back field. Upon receiving the reissued electronic work order, the corresponding construction terminal, hoisting terminal, and measurement verification terminal use the new work order number as the basis for on-site execution and write the execution results back to the new result write-back field.

[0100] After each electronic work order update, the assembly management server synchronously updates the electronic assembly process package, work surface occupancy status table, collaborative assembly sequence table, waiting list, paused list, frozen list, bypass assembly batch table, and exception handling record table. The work surface occupancy status table records the current status of each work surface, the occupying module, the occupying process, the released process, and the release time; the collaborative assembly sequence table records the assembly batch, current work order status, subsequent work order status, and associated modules for each module; and the exception handling record table records the exception event number, exception source, exception impact status, associated modules, processing task, and processing result.

[0101] Once an anomaly handling task is completed, the construction terminal or measurement verification terminal uploads the completion result. The assembly management server writes the completion result into the anomaly handling record table and reads the reference edge positioning status, adjacent closed surface status, interface connection status, post-fixation retest status, and work surface release status of the corresponding module. If the above statuses are restored to the executable status specified in the electronic assembly process package, the suspension or freeze status of the corresponding electronic process ticket is lifted, and the process access judgment is re-executed; if there are still unconfirmed, unreleased, unpassed, or pending adjustment statuses, the suspension or freeze status is maintained, and the corresponding handling task is retained.

[0102] The electronic work order update results are simultaneously sent to the construction terminal, hoisting terminal, measurement verification terminal, and site management terminal. The construction terminal receives the updated construction tasks, suspended tasks, verification tasks, and rework tasks; the hoisting terminal receives the updated hoisting permission signals, hoisting paths, and hoisting release requirements; the measurement verification terminal receives the updated measurement points, closed-plane verification items, and allowable deviation ranges; and the site management terminal receives the updated current assembly batch, bypass assembly batch, waiting list, suspended list, and frozen list.

[0103] Example 2, one embodiment of the present invention, provides a method for collaborative assembly of prefabricated modules for data centers. To verify the beneficial effects of the present invention, scientific demonstration is carried out through economic benefit calculations and simulation experiments.

[0104] First, a newly built data center Phase I project was selected as the implementation scenario. The computer room building area is approximately 8600 square meters. The test area was divided into three typical areas: power distribution and UPS assembly area, cooling and piping assembly area, and rack foundation and low-voltage assembly area. All three areas adopted a prefabricated modular construction method. The power distribution and UPS assembly area involved 18 prefabricated modules, the cooling and piping assembly area involved 16 prefabricated modules, and the rack foundation and low-voltage assembly area involved 20 prefabricated modules. For ease of comparison, a conventional construction group and a method implementation group were set up for each area. The conventional construction group mainly carried out module hoisting, positioning, and fixing based on the construction schedule, work orders, and coordination results of on-site management personnel. The method implementation group implemented the data center prefabricated module collaborative assembly method. Before implementation, BIM detailed models, prefabricated module processing drawings, manufacturer's list, hoisting equipment parameter tables, site layout drawings, construction zoning plans, and module arrival acceptance records were collected. Each prefabricated module was also equipped with an RFID tag or QR code tag. On-site equipment includes a total station, laser rangefinder, hoisting equipment positioning terminal, work surface status acquisition terminal, and construction mobile terminal. These are used to acquire module identity status, actual location status, hoisting path status, temporary storage area status, installation area status, and personnel operation area status. Subsequently, an electronic assembly process package is generated for each prefabricated module. This package includes the module number, module version number, installation reference edge, adjacent closed surfaces, work surface number, allowable deviation range, non-pre-executed processes, and status feedback fields. The assembly management server establishes reference relationships, closed surface reference relationships, and work surface occupancy relationships based on the electronic assembly process package. For example, the cabinet foundation module serves as the positioning reference for subsequent low-voltage cable tray modules, the main chilled water pipeline module serves as the closed surface reference object for branch pipeline modules, and the power distribution module hoisting path has a work surface occupancy relationship with the UPS module temporary storage area. During assembly, the assembly management server generates process access results based on the identity status, work surface occupancy status, reference edge positioning status, and adjacent closed surface status, and issues electronic process tickets to the construction terminal, hoisting terminal, and measurement verification terminal. After the module is hoisted to the installation area, the measurement and verification terminal collects the actual boundary position, elevation, levelness, and orientation data, and compares them with the installation reference edge, adjacent closed surface, and allowable deviation range in the electronic assembly process package. Only when the reference edge positioning status and the adjacent closed surface status meet the requirements can a permanent fixed process ticket be issued. If there are situations such as the work surface not being released, the closed surface needing adjustment, or the reference edge not being confirmed, the assembly management server suspends or reorders the corresponding electronic process ticket and generates bypass assembly batches for unaffected modules. The conventional construction team uses the same number of modules, the same hoisting equipment, the same number of construction teams, and the same acceptance criteria to ensure the comparability of the comparison results.

[0105] Table 1 Experimental Data

[0106] As shown in Table 1, this method exhibits relatively stable improvement effects in all three assembly areas. Firstly, the completeness rate of the electronic assembly process package increased from 58%–65% in the conventional construction group to 97%–99% in the method group. This indicates that by uniformly writing design data, factory data, hoisting operation data, and on-site work surface data into the electronic assembly process package, module identity, installation reference edge, adjacent closed surfaces, work surface number, non-pre-executed processes, and status feedback fields can form a complete data carrier, avoiding the problem of incomplete execution basis caused by module data being scattered across drawings, manufacturer documents, and manual work orders in conventional construction. Secondly, the number of incorrect process entry assignments decreased from 6–8 times in the conventional construction group to 0–1 times, and the number of work surface conflicts decreased from 5–7 times to 1–2 times. This indicates that after reference relationships, closed surface reference relationships, and work surface occupancy relationships are involved in the entry judgment, states such as "reference not confirmed," "work surface not released," and "closed modules should not be fixed in advance" can be identified before module hoisting, avoiding invalid hoisting and on-site waiting caused by directly assigning work based on manual experience. Furthermore, the average positioning deviation decreased from 7.8mm to 9.6mm to 1.9mm to 2.7mm, and the first-time confirmation rate of the closed surface increased from 68% to 74% to 94% to 97%. This indicates that after comparing the boundary position, elevation, levelness, and orientation data collected on-site with the installation reference edge, adjacent closed surface, and allowable deviation range in the electronic assembly process package, positioning verification and closed surface confirmation can be completed before permanent fixing, thereby reducing problems such as adjacent modules not fitting properly, interface hole offset, and insufficient maintenance clearance. Further, the conventional construction team did not form an effective record of intercepting the risk of premature execution of permanent fixing, while this method team intercepted it 5, 4, and 6 times respectively. This demonstrates that by controlling the issuance of permanent fixing process tickets through the fixed process access status, the "whether fixing is allowed" can be transformed into a technical control process driven by the reference edge positioning status, adjacent closed surface status, and processes that cannot be executed prematurely. The interface first-pass yield increased from 78%-85% to 94%-98%, and the number of reworks decreased from 4-6 times to 0-1 times, further demonstrating that pre-fixation baseline edge and closed-face verification can improve interface connection quality. Finally, the electronic work ticket rescheduling response time was shortened from 39-48 minutes to 7-10 minutes, and the bypass assembly maintenance rate increased from 45%-52% to 82%-89%. This indicates that after on-site execution feedback is written to the status feedback field, it can link and update the subsequent module's work entry results, collaborative assembly sequence, and electronic work tickets, preventing local anomalies from necessarily causing overall assembly stagnation. Therefore, compared to conventional manual scheduling and static construction plans, this method not only improves the integrity of assembly data and the accuracy of on-site positioning, but also forms a closed-loop collaborative control effect suitable for high-density prefabricated module assembly scenarios in data centers through the electronic work ticket's entry, pause, rescheduling, and bypass mechanisms.

[0107] Example 3, one embodiment of the present invention, provides a collaborative assembly system for prefabricated modules of a data center, including a process packaging module, an access dispatch module, and an execution write-back module.

[0108] The process package creation module is used to collect design data, factory data, hoisting operation data, and on-site work surface data of prefabricated modules. Combined with the on-site acquisition device, it obtains the module identity, location, and work surface occupancy status, and generates electronic assembly process packages corresponding to each prefabricated module. The access and dispatch module is used to establish the reference relationship, closed surface reference relationship, and work surface occupancy relationship between prefabricated modules based on the electronic assembly process packages. According to the module identity status, work surface occupancy status, reference edge positioning status, and adjacent closed surface status, it generates process access results and collaborative assembly sequence. The execution and write-back module is used to execute the on-site assembly of prefabricated modules according to the electronic process ticket, and write back the on-site measurement data, reference edge positioning status, adjacent closed surface status, fixed process execution status, and work surface release status to the electronic assembly process package.

[0109] If a function is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this invention, or the part that contributes to the prior art, or a part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of this invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0110] The logic and / or steps represented in the flowchart or otherwise described herein, for example, can be considered as a sequenced list of executable instructions for implementing logical functions, and can be embodied in any computer-readable medium for use by, or in conjunction with, an instruction execution system, apparatus, or device (such as a computer-based system, a processor-including system, or other system that can fetch and execute instructions from, an instruction execution system, apparatus, or device). For the purposes of this specification, "computer-readable medium" can be any means that can contain, store, communicate, propagate, or transmit programs for use by, or in conjunction with, an instruction execution system, apparatus, or device.

[0111] More specific examples (a non-exhaustive list) of computer-readable media include: electrical connections (electronic devices) having one or more wires, portable computer disk drives (magnetic devices), random access memory (RAM), read-only memory (ROM), erasable and editable read-only memory (EPROM or flash memory), fiber optic devices, and portable optical disc read-only memory (CDROM). Furthermore, computer-readable media can even be paper or other suitable media on which programs can be printed, because programs can be obtained electronically, for example, by optically scanning the paper or other media, followed by editing, interpreting, or otherwise processing as necessary, and then stored in computer memory.

[0112] It should be understood that various parts of the present invention can be implemented using hardware, software, firmware, or a combination thereof. In the above embodiments, multiple steps or methods can be implemented using software or firmware stored in memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, it can be implemented using any one or a combination of the following techniques known in the art: discrete logic circuits having logic gates for implementing logical functions on data signals, application-specific integrated circuits (ASICs) having suitable combinational logic gates, programmable gate arrays (PGAs), field-programmable gate arrays (FPGAs), etc. It should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention and are not intended to limit it. Although the present invention has been described in detail with reference to preferred embodiments, those skilled in the art should understand that modifications or equivalent substitutions can be made to the technical solutions of the present invention without departing from the spirit and scope of the technical solutions of the present invention, and all such modifications or substitutions should be covered within the scope of the claims of the present invention.

[0113] It should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention and are not intended to limit it. Although the present invention has been described in detail with reference to preferred embodiments, those skilled in the art should understand that modifications or equivalent substitutions can be made to the technical solutions of the present invention without departing from the spirit and scope of the technical solutions of the present invention, and all such modifications or substitutions should be covered within the scope of the claims of the present invention.

Claims

1. A method for collaborative assembly of prefabricated modules for data centers, characterized in that, include: The system acquires design data, factory data, hoisting operation data, and on-site work surface data of the data center prefabricated modules. It also uses on-site acquisition devices to obtain the identity status, location status, and work surface occupancy status of the prefabricated modules, and generates electronic assembly process packages corresponding to each prefabricated module. Based on the electronic assembly process package, establish the reference relationship, closed surface reference relationship and work surface occupancy relationship between prefabricated modules. According to the identity status, work surface occupancy status, reference edge positioning status and adjacent closed surface status, generate process access results and collaborative assembly sequence, and issue electronic process tickets to the assembly execution terminal. According to the electronic process ticket, the prefabricated module is assembled on site. The assembly execution data collected on site is compared with the installation reference edge, adjacent closed surface and allowable deviation range in the electronic assembly process package. The reference edge positioning status and adjacent closed surface status are generated and written back. Based on the positioning status of the reference edge, the status of adjacent closed surfaces, and the procedures that cannot be executed in advance, control the issuance of permanently fixed procedure tickets; Based on the on-site execution feedback after the prefabricated module assembly, update the status feedback field in the electronic assembly process package, and update the process access results, collaborative assembly sequence, and electronic process ticket of the prefabricated module in a linked manner.

2. The data center prefabricated module collaborative assembly method as described in claim 1, characterized in that: The electronic assembly process package includes module basic fields, spatial positioning fields, assembly operation fields, on-site status fields, and linkage control fields; The basic fields of the module include module number, module type, module version number, module dimensions, module weight, lifting point location, interface type, interface location, and factory acceptance status. The spatial positioning fields include installation area number, installation coordinates, installation elevation, installation reference edge, adjacent closed surface, on-site measurement points, allowable deviation range, and adjacent module number; The assembly operation fields include the preceding process number, process number, hoisting path number, temporary storage area number, personnel operation area number, maintenance reserved area number, and processes that cannot be performed in advance; The on-site status fields include identity status, work surface occupancy status, reference edge positioning status, adjacent closed surface status, fixed process access status, and work surface release status. The linkage control fields include the reference benchmark module number, the reference closure surface number, the affected module number, the electronic work ticket number, and the electronic work ticket write-back status.

3. The data center prefabricated module collaborative assembly method as described in claim 2, characterized in that: The establishment of reference relationships, closed surface reference relationships, and work surface occupancy relationships between prefabricated modules includes marking the prefabricated module as a reference module when the installation reference edge of a prefabricated module is referenced by the electronic assembly process package of other prefabricated modules; When the installation coordinates, installation direction, or adjacent closed surface of a prefabricated module needs to reference the measurement results of a reference module, the prefabricated module is marked as an attached module. When the release status of the hoisting path, personnel operation area, or maintenance reserved area is changed after the prefabricated module is permanently fixed, the prefabricated module will be marked as a closed module. When a prefabricated module does not have an installation reference edge, adjacent closed surface, or work surface release condition referenced by other prefabricated modules, the prefabricated module is marked as an independent module, and the module marking result is written into the corresponding electronic assembly process package.

4. The data center prefabricated module collaborative assembly method as described in claim 3, characterized in that: The process access result includes generating a lifting permission result for the reference module when the identity status of the prefabricated module is "identity confirmed" and its preceding process status is "precedence satisfied" and the required work surface occupancy status is "work surface satisfied". When the reference edge positioning status of the reference module referenced by the attached module is confirmed, and the identity status, preceding process status and work surface occupancy status of the attached module are all satisfied, a lifting permission result is generated for the attached module. When the positioning status of the reference edge referenced by the attached module is pending confirmation, pending adjustment, or unconfirmed, a result awaiting reference edge confirmation is generated. When the status of the adjacent closed surface referenced by the prefabricated module is pending confirmation, pending adjustment, or unconfirmed, a result awaiting confirmation of the closed surface is generated. When the work surface occupied by the closed module after it has been permanently fixed is still referenced by an unfinished electronic assembly process package, a post-installation result is generated.

5. The data center prefabricated module collaborative assembly method as described in claim 4, characterized in that: The on-site assembly of prefabricated modules according to the electronic work ticket includes the assembly execution terminal reading the module number and module version number of the prefabricated module and comparing them with the module number and module version number in the electronic assembly work package; When the module number is consistent, the module version number is consistent, the transportation damage review status is passed, the on-site acceptance status is passed, the lifting point acceptance status is passed, and the lifting path, temporary storage area, installation area and personnel operation area are available or released, the lifting permission signal is output. If any state is not met, no hoisting permission signal will be output, and a corresponding identity verification, hoisting point verification, or work surface release verification procedure ticket will be generated.

6. The data center prefabricated module collaborative assembly method as described in claim 5, characterized in that: The process of generating and writing back the reference edge positioning status and adjacent closed surface status includes collecting the actual boundary position, actual elevation, levelness, verticality and orientation data of the prefabricated module through an on-site measuring device, and comparing the collected data with the installation reference edge, on-site measurement points and allowable deviation range in the electronic assembly process package; When the comparison result is within the allowable deviation range, update the reference edge positioning status to confirmed. When the comparison result exceeds the allowable deviation range and there is a corresponding adjustment method in the electronic assembly process package, the reference edge positioning status will be updated to pending adjustment and an adjustment process ticket will be issued. When the comparison result exceeds the allowable deviation range and there is no corresponding adjustment method, the reference edge positioning status will be updated to unconfirmed. After the baseline positioning status is confirmed, the actual spacing, reserved interface position, hole position correspondence status, maintenance reserved distance and work passage status between the current prefabricated module and adjacent modules, structural foundation, support, pipeline or equipment interface are reviewed, and the adjacent closed surface status is generated accordingly.

7. The data center prefabricated module collaborative assembly method as described in claim 6, characterized in that: The linkage update of the prefabricated module's process access results, collaborative assembly sequence, and electronic process ticket includes querying the prefabricated module that references the installation reference edge when the current prefabricated module's reference edge positioning status is updated to confirmed, and updating the corresponding process access results to be re-accessible. When the status of the adjacent closed face of the current prefabricated module is updated to confirmed, query the prefabricated modules that reference the adjacent closed face and re-determine whether to issue an interface connection work ticket or a permanent fixed work ticket. When the release status of the current prefabricated module's work surface is updated to "released", query the prefabricated modules waiting for that work surface and regenerate the corresponding electronic work ticket; When the status of the reference edge positioning, adjacent closed surface, or work surface release changes from confirmed or released to pending adjustment, unconfirmed, or unreleased, the electronic work ticket referencing the corresponding status field is suspended. When the on-site execution feedback includes an assembly interruption event, freeze the electronic process tickets for the current prefabricated module and related modules.

8. A system employing the data center prefabricated module collaborative assembly method as described in any one of claims 1 to 7, characterized in that: Includes a process packaging module, an access assignment module, and an execution write-back module; The process package module is used to collect design data, factory data, hoisting operation data and on-site work surface data of prefabricated modules, and combine the module identity, location and work surface occupancy status with the on-site acquisition device to generate electronic assembly process packages corresponding to each prefabricated module; The access and dispatch module is used to establish reference relationships, closed surface reference relationships, and work surface occupancy relationships between prefabricated modules based on electronic assembly process packages. It generates process access results and collaborative assembly sequence according to module identity status, work surface occupancy status, reference edge positioning status, and adjacent closed surface status. The execution write-back module is used to perform on-site assembly of prefabricated modules according to the electronic work ticket, and write back the on-site measurement data, reference edge positioning status, adjacent closed surface status, fixed process execution status and work surface release status to the electronic assembly process package.

9. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the data center prefabricated module collaborative assembly method according to any one of claims 1 to 7.

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

Images