A data center electromechanical module prefabrication checking method and system

Abstract

The application discloses a kind of data center electromechanical module prefabrication checking method and system, it is related to data center electromechanical module prefabrication checking technical field, including by dividing electromechanical prefabrication module and establishing module prefabrication state package, further generate project checking benchmark table;According to state package and benchmark table, interface handshake locking of module is carried out, field countercheck and implementation window checking, form processing boundary control result, prefabricable range correction result and hierarchical release result;Based on hierarchical release result, module state atlas is established, when design, processing, field or plan change occurs, directional determination is affected module return review.The method described in the application is linked by state package, benchmark table and state atlas, realizes the branch checking of interface, field and implementation window, clearly defines the processing boundary, corrects the prefabricable range, controls the release level, and after change, the affected module is reviewed directionally, reduces rework, improves the coordination reliability of prefabrication processing, transportation approach and field installation.

Description

Technical Field

[0001] This invention relates to the field of prefabrication verification technology for data center electromechanical modules, specifically a method and system for prefabrication verification of data center electromechanical modules. Background Technology

[0002] As data center construction continues to expand, the electromechanical systems of data centers are increasingly characterized by high-density integration, cross-disciplinary collaboration, and rapid delivery. To shorten on-site construction cycles and reduce interference from overlapping operations, electromechanical components such as power distribution, busbars, cable trays, chilled water piping, precision air conditioning interface sections, and integrated supports are gradually shifting from on-site assembly to a combination of factory prefabrication and on-site assembly. Simultaneously, digital technologies such as BIM modeling, construction detailing, manufacturer drawing collaboration, on-site re-measurement, and schedule management are widely used in the prefabrication management of electromechanical modules. These technologies assist in spatial collision checks, component disassembly, interface verification, transportation and hoisting calibration, and installation schedule coordination, thereby improving the industrialized construction level of data center electromechanical engineering.

[0003] Existing methods for verifying the prefabrication of data center electromechanical modules largely rely on single-model collision checks, drawing parameter verification, or manual approval processes. They lack a stateful processing mechanism that unifies data from the design, manufacturer, site, and planning ends to the same prefabricated module object. This results in a lack of continuous transmission relationships between interface parameters, site retest results, processing boundaries, and installation windows. Even if existing technologies can identify interface inconsistencies or site space conflicts, they typically only output a problem list, failing to determine whether the module should be fully prefabricated, partially prefabricated, delayed for shipment, or prohibited from prefabrication. This makes it difficult to establish actionable control over the manufacturer's processing scope. Furthermore, site retest data often exists as post-acceptance documentation and cannot be used to influence prefabrication boundaries, interface retention areas, and adjustable processing ranges. This can lead to problems such as inability to transport or hoist modules after processing, inability to connect interfaces, or unsuitable site installation conditions. Furthermore, when design changes, manufacturer processing changes, changes in site conditions, or adjustments to the construction plan occur, existing methods typically rely on manual re-screening of affected modules. This can easily lead to overlooking adjacent interfaces, space occupancy, and installation sequence relationships, and may also result in repeated verification of unrelated modules. It is difficult to achieve targeted impact transmission and closed-loop verification control based on the module status map. Therefore, existing technologies struggle to achieve the technical effects of controllable prefabricated module processing boundaries, reverse verification of site conditions, coordinated implementation of window-based release, and verification of the minimum scope of change impact. 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 electromechanical module prefabrication verification methods lack unified state-based association between design, manufacturer processing, on-site retesting, and construction plan data; interface verification results are difficult to convert into executable processing boundary controls; changes in on-site conditions and project modifications are difficult to be directed to affected modules and form closed-loop verification; and there is the problem of how to achieve branch verification, hierarchical release, and change closed-loop control of electromechanical prefabrication modules based on module prefabrication status packages, project verification benchmark tables, and module status diagrams.

[0006] To solve the above-mentioned technical problems, the present invention provides the following technical solution: a method for prefabricated verification of electromechanical modules in a data center, comprising: acquiring design data, manufacturer processing data, on-site re-measurement data, transportation and hoisting data, and construction progress data of a data center project; dividing the electromechanical prefabricated modules and establishing a module prefabricated status package; generating a project verification benchmark table associated with the module prefabricated status package based on project documents, on-site re-measurement data, transportation and hoisting schemes, and construction progress plans; performing prefabricated access branch determination on the electromechanical prefabricated modules according to the module prefabricated status package and the project verification benchmark table, forming an interface handshake locking branch, an on-site counter-verification verification branch, and an implementation window verification branch; and, under the interface handshake locking branch, verifying adjacent electromechanical modules... The interface parameters of the prefabricated modules are locked, retained, adjustable, or rolled back to generate processing boundary control results. Under the on-site verification branch, the on-site retest data is mapped with the processing boundary control results to determine the affected parts and correct the prefabrication range of the electromechanical prefabricated modules. Under the implementation window verification branch, based on the design freeze time, manufacturer processing time, transportation time, on-site receiving time, and planned installation time, a graded release result is generated in combination with the prefabrication range. Based on the graded release result, a module status map is established. When changes in design, processing, on-site, transportation, or installation plans are detected, the affected modules are determined according to the module status map, and the data is sent back to the corresponding verification branch for review and updating of the graded release result.

[0007] As a preferred embodiment of the data center electromechanical module prefabrication verification method described in this invention, the establishment of the module prefabrication status package includes determining the module division boundary according to the installation area, prefabrication boundary and on-site assembly sequence of the electromechanical object, binding the data generated by the same electromechanical prefabrication module at the design end, manufacturer end, on-site end and planning end to the same module index; when any data source is updated, the updated field is written into the corresponding module prefabrication status package, and the field values ​​and data sources before and after the update are retained.

[0008] As a preferred embodiment of the data center electromechanical module prefabrication verification method of the present invention, the following steps are included: generating a project verification benchmark table associated with the module prefabrication status package includes extracting benchmark data of dimensional deviations, interface deviations, installation deviations, and adjustable quantities from project documents, manufacturer processing documents, equipment installation documents, and construction acceptance documents, and converting data from different sources into a unified unit; when multiple sources of data exist for the same verification project, the value that limits the prefabrication processing range is selected as the adopted value; and the remaining transportation passage volume, remaining hoisting weight volume, remaining temporary storage capacity, and implementation window time relationship are calculated based on on-site re-measurement data, transportation and hoisting schemes, and construction schedules, and written into the project verification benchmark table.

[0009] As a preferred embodiment of the data center electromechanical module prefabrication verification method of the present invention, the prefabrication access branch determination of the electromechanical prefabrication module includes reading the connection relationship, spatial proximity relationship, transportation and hoisting relationship and installation sequence relationship in the module prefabrication status package; when the electromechanical prefabrication module has adjacent connected objects, an interface handshake lock branch is triggered; when the electromechanical prefabrication module has a re-measurement verification relationship with on-site structures, passages or installed components, an on-site counter-verification verification branch is triggered; when the electromechanical prefabrication module is restricted by the transportation, hoisting, stacking or pre-installation sequence, an implementation window verification branch is triggered; when the same electromechanical prefabrication module triggers more than one branch, it is executed in the order of interface handshake, on-site counter-verification and implementation window, and the results of each branch are continuously written back to the module prefabrication status package.

[0010] As a preferred embodiment of the data center electromechanical module prefabrication verification method of the present invention, the following steps are performed under the interface handshake locking branch: locking, retaining, adjusting, or reverting the interface parameters of adjacent electromechanical prefabrication modules to generate processing boundary control results. This includes establishing an interface handshake unit between the current electromechanical prefabrication module and adjacent electromechanical prefabrication modules under the interface handshake locking branch, comparing the specifications, connection methods, centerlines, elevations, and orientation angles of the interfaces on both sides with the project verification benchmark table; when the interfaces on both sides meet the corresponding adopted values, the interface status is written to the double-sided lock and a complete processing boundary is generated; when only one side of the interface is confirmed, the confirmed side is written to the interface retain boundary; when the interface deviation falls within the adjustable range, an adjustable processing boundary is generated; when the interface deviation exceeds the adjustable range or the interface specifications do not correspond, a prohibited processing boundary is generated, and the corresponding module is reverted to the interface verification state.

[0011] As a preferred embodiment of the data center electromechanical module prefabrication verification method of the present invention, the following steps are included: Under the on-site counter-verification branch, mapping the on-site re-measurement data with the processing boundary control results to determine the affected parts and correct the prefabrication range of the electromechanical prefabrication module includes: Under the on-site counter-verification branch, converting the on-site re-measurement data to a project coordinate system consistent with the electromechanical prefabrication module, mapping the re-measurement differences to the main body section, interface end, on-site adjustment section, temporarily unfixed section, or prohibited processing section in the processing boundary control results; when the re-measurement difference corresponds to the on-site adjustment section or temporarily unfixed section, the prefabrication range of the main body section is retained; when the re-measurement difference corresponds to the interface end, the corresponding interface is sent back to the interface handshake locking branch; when the re-measurement difference corresponds to the main body section, transportation entry path, hoisting path, or prohibited processing section, the corresponding electromechanical prefabrication module is corrected to prohibit complete prefabrication.

[0012] As a preferred embodiment of the data center electromechanical module prefabrication verification method of the present invention, the step of generating a graded release result based on the design freeze time, manufacturer processing time, transportation time, on-site receiving time, and planned installation time under the implementation window verification branch, combined with the prefabrication range, includes: firstly, forming an implementation window chain according to the design freeze time, manufacturer processing time, transportation time, on-site receiving time, and planned installation time under the implementation window verification branch; then, combining and judging the implementation window chain with the interface handshake result, on-site verification result, and prefabrication range; when the interface is locked, the on-site verification is passed, and the implementation window chain is established, a complete prefabrication release result is generated; when only the main body section has processing conditions, a partial prefabrication release result is generated; when the processing conditions are met but the on-site receiving conditions have not yet been met, a processing-prohibited-shipment result is generated; when there is an interface conflict, the on-site verification fails, or the implementation window chain is not established, a prohibited prefabrication result is generated; when there are changes in the design, processing, on-site, transportation, or installation plans, the affected modules are sent back to the corresponding verification branch for re-judgment based on the module status diagram.

[0013] Another objective of this invention is to provide a data center electromechanical module prefabrication verification system, which can map on-site retest data with processing boundary control results under the on-site reverse verification branch to determine the affected parts and correct the prefabrication range of electromechanical modules. This solves the problem that current data center electromechanical module prefabrication verification methods lack a unified state-based correlation between on-site retest data and construction plan data.

[0014] As a preferred embodiment of the data center electromechanical module prefabrication verification system of the present invention, it includes: a state modeling module, a branch verification module, and a graph closed-loop module; the state modeling module is used to complete the object-oriented management of the data center electromechanical prefabrication module; the branch verification module is used to determine whether the electromechanical prefabrication module has the conditions for prefabrication processing; the graph closed-loop module is used to realize the prefabrication release and the review control after changes.

[0015] A computer device includes a memory and a processor, the memory storing a computer program, and the processor executing the computer program to implement a method for prefabricating and verifying electromechanical modules in a data center.

[0016] A computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of a data center electromechanical module prefabrication verification method.

[0017] The beneficial effects of this invention are as follows: The data center electromechanical module prefabrication verification method provided by this invention constructs a module prefabrication status package and a project verification benchmark table, uniformly binding design data, manufacturer processing data, on-site re-measurement data, transportation and hoisting data, and construction progress data to the same electromechanical prefabrication module object. This achieves integrated expression of the prefabrication object, verification basis, and status fields, providing a traceable data foundation for subsequent interface verification, on-site verification, and release control, thereby avoiding inconsistencies in verification basis caused by fragmented data from multiple sources. Through the interface handshake locking step, the interface specifications, location, elevation, direction, and adjustable range of adjacent electromechanical prefabrication modules are confirmed on both sides. This realizes the branching processing of interface status from unidirectional verification to mutual locking, retention, adjustment, and rollback, directly generating complete processing boundaries, interface retention boundaries, and prohibited processing boundaries, thereby improving the certainty of manufacturer processing boundaries and reducing the risk of interface connection failures. Through on-site verification steps, differences from on-site re-measurements are mapped to the main body, interface, on-site adjustment, and prohibited processing sections. This enables reverse correction of the prefabrication scope based on actual on-site conditions, determining whether a module is suitable for complete prefabrication, partial prefabrication, or rejection for re-verification. This reduces rework issues such as modules being unable to be transported, hoisted, or installed after processing. By implementing a window-linked judgment step, the design freeze, manufacturer processing, transportation arrival, on-site receipt, and planned installation are formed into a continuous time chain. This transforms technical verification results into processing, factory release, and installation control results, generating results for complete prefabrication release, partial prefabrication release, delayed factory release, prohibited prefabrication, or priority scheduling. This improves the matching between the prefabrication plan and the on-site construction rhythm. Through module status diagrams and change closed-loop verification steps, the impact of changes is directionally transmitted along interface relationships, spatial adjacency relationships, transportation batch relationships, and installation sequence relationships. This determines the minimum verification scope and updates release results, avoiding omissions of affected modules and repeated verification of unrelated modules. This improves the collaborative accuracy of data center electromechanical module prefabrication verification and the reliability of project implementation. 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 electromechanical module prefabrication verification 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 prefabricating and verifying data center electromechanical modules is provided, comprising: S1: Obtain design data, manufacturer processing data, on-site re-measurement data, transportation and hoisting data, and construction progress data for the data center project; divide the electromechanical prefabrication modules and establish module prefabrication status packages; based on project documents, on-site re-measurement data, transportation and hoisting plans, and construction schedules, generate a project verification benchmark table associated with the module prefabrication status packages.

[0022] Furthermore, this involves acquiring the electromechanical design model, detailed construction drawings, manufacturer's fabrication drawings, equipment and materials list, equipment installation manuals, manufacturer's fabrication process documents, construction and acceptance documents used in the project, on-site re-measurement data, transportation and hoisting plans, and construction schedule for the data center project. The electromechanical design model provides the design and installation locations, professional categories, connection relationships, and space occupancy of electromechanical components; the detailed construction drawings provide prefabrication boundaries, interface reservation locations, and on-site installation sequence; the manufacturer's fabrication drawings provide factory fabrication dimensions, interface fabrication dimensions, and component disassembly methods; and the equipment and materials list provides equipment models, component specifications, and quantities. The equipment installation manual provides information on equipment interface dimensions, installation direction, maintenance requirements, and adjustable range of connectors. The manufacturer's processing technology documents provide allowable processing deviations and processable boundaries. The construction and acceptance documents provide installation deviations, clearance requirements, and acceptance standards. The on-site re-measurement data provides information on the handover status of equipment foundations, reserved openings, doorways, transportation channels, beam and column boundaries, and work surfaces. The transportation and hoisting plan provides information on transportation routes, hoisting equipment, hoisting radius, rated lifting capacity, and hoisting tool parameters. The construction schedule provides information on design freeze time, manufacturer processing time, factory transportation time, on-site receiving time, and planned installation time.

[0023] The above data undergoes unified coding and unit conversion processing, associating module names, equipment numbers, drawing numbers, model component numbers, and manufacturer processing numbers from different sources with the same prefabricated electromechanical module object. For data from different sources but describing the same object, a module code is composed of project number, floor number, machine room area number, professional category number, module type number, connection object number, and prefabrication batch number; the module code serves as a unique index for subsequent data writing, status updates, interface associations, and change transfer. If a data field is missing in the design model, construction detail drawings, manufacturer processing drawings, or on-site remeasurement data, this field is not directly used as the pass / fail criterion. Instead, a "data to be supplemented" mark is written to the corresponding module status, recording the missing field name, responsible source, and object to be supplemented.

[0024] The focus is on electromechanical objects within the data center server room that can be prefabricated in the factory and assembled on-site. These objects include power distribution cabinet connection sections, UPS supporting sections, busbar sections, cable tray sections, chilled water pipe sections, precision air conditioning interface sections, integrated support and hanger sections, fire protection piping sections, and low-voltage cabling sections. Based on factory processing boundaries, transportation unit boundaries, on-site installation unit boundaries, and interface connection boundaries, the electromechanical objects are divided into multiple prefabricated electromechanical modules. The division into prefabricated modules is based on the fundamental condition that they can form units that can be independently processed, transported, hoisted, or installed. When the same electromechanical object spans different server room areas, different installation elevations, different transportation routes, different hoisting routes, or different installation sequences, it is split into different prefabricated electromechanical modules according to the corresponding boundaries. When multiple components need to be pre-assembled in the factory and then transported and installed as a whole, these multiple components are combined into a single prefabricated electromechanical module.

[0025] A module prefabrication status package is established for each electromechanical prefabrication module. The module prefabrication status package includes module basic information, prefabrication boundary information, interface constraint information, site constraint information, manufacturer processing information, implementation window information, and verification branch markers. The module basic information includes module code, room area, discipline, module name, equipment or component specifications, installation coordinates, installation elevation, installation direction, planned installation location, and responsible unit; prefabrication boundary information includes main section range, interface end range, on-site adjustment section range, temporarily unfixed section range, factory processing range, and on-site fixed range; interface constraint information includes upstream connection module, downstream connection module, interface type, interface specifications, interface centerline, interface elevation, interface direction, connection method, interface confirmation status, and allowable adjustment amount; on-site constraint information includes equipment foundation location, reserved opening location, beam and column boundary, wall boundary, door opening size, clear width of transportation channel, hoisting path, occupancy status of installed components, and handover status of installation work surface; manufacturer processing information includes manufacturer name, detailed status, processing status, processable range, processing batch, factory status, and packaging dimensions; implementation window information includes design freeze time, manufacturer planned processing start time, manufacturer planned processing completion time, planned factory delivery time, transportation cycle, on-site receiving time, planned installation time, and pre-installed module number.

[0026] After the prefabricated module status package is established, a project verification benchmark table is generated. The various verification benchmark values ​​in the project verification benchmark table are not generated using a separate setting method, but are extracted and recorded from existing project documents and on-site measured data. Each verification benchmark item includes the benchmark item name, applicable discipline, applicable module type, source document name, source drawing number or clause number, original value, unit conversion result, adopted value, adoption rule, and effective version. Allowable deviations for dimensions, coordinates, elevation, and interface direction are extracted from project design documents, construction acceptance documents, manufacturer's processing technology documents, and equipment installation manuals. When multiple source values ​​exist for the same verification item, all source values ​​are converted to the same unit, and the smaller value is taken as the adopted value for that verification item. Unadopted values ​​and their sources are written into the remarks field of the project verification benchmark table. The adjustable margin of the interface is extracted from the reserved adjustment section length in the construction detail drawing, the adjustable range of the connector in the equipment installation manual, the expansion and contraction of the flexible connection, the stroke of the expansion joint, and the adjustment stroke of the adjustable bracket. When there are multiple adjustable sources for the same interface, only the adjustment amount that can act on the same interface direction is accumulated, and the adjustment amount that cannot act on the same interface direction is recorded separately and is not included in the adjustment amount calculation for that direction.

[0027] The transport passage baseline value is calculated based on the clear width and height of the doorway, the clear width of the transport passage, the clear dimensions of the turning area, the dimensions occupied by the transport vehicle, and the length, width, and height of the module after packaging, all obtained from on-site re-measurement. The remaining transport passage space is obtained by subtracting the module packaging dimensions and the transport vehicle's dimensions from the on-site clear passage dimensions. When the remaining transport passage space is greater than or equal to 0, it is recorded as transport passage conditions being met; when the remaining transport passage space is less than 0, it is recorded as transport passage conditions not being met. The lifting weight baseline value is calculated based on the rated lifting capacity of the lifting equipment, the weight of the lifting gear, the weight of the module packaging, and the weight of the module itself, as specified in the transport lifting plan at the corresponding lifting radius. The remaining lifting weight is obtained by subtracting the weight of the lifting gear, the weight of the module packaging, and the weight of the module itself from the rated lifting capacity at the corresponding lifting radius. When the remaining lifting weight is greater than or equal to 0, it is recorded as lifting weight conditions being met; when the remaining lifting weight is less than 0, it is recorded as lifting weight conditions not being met. The temporary storage capacity is calculated based on the on-site temporary storage area's dimensions, the already occupied storage area, the area occupied by the intended module packaging, and the stacking layer limit. The remaining temporary storage capacity is calculated by subtracting the occupied storage area from the available storage area and then subtracting the area occupied by the intended module packaging. When the remaining temporary storage capacity is greater than or equal to 0, it is recorded as the temporary storage condition being met; when the remaining temporary storage capacity is less than 0, it is recorded as the temporary storage condition not being met.

[0028] The implementation window baseline value is formed based on the construction schedule, manufacturer's production schedule, transportation plan, and site handover plan. The manufacturer's planned processing start time, manufacturer's planned processing completion time, planned delivery time, transportation cycle, site acceptance time, and planned installation time are read from the corresponding plan files. The installation buffer time is obtained by adding the factory acceptance time, the on-site secondary transfer time, the pre-installation handover acceptance time, and the on-site unpacking inspection time. If any time field is missing, the implementation window information of the corresponding module is written to the unclosed state of the time field, and this state is synchronously written to the module's prefabrication status package.

[0029] After establishing a link between the project verification benchmark table and the module prefabrication status package, a prefabrication access branch judgment is performed for each electromechanical prefabrication module. For electromechanical prefabrication modules of the same type, their length difference, width difference, height difference, installation coordinate difference, and interface specification code are calculated. When the length difference is less than or equal to the corresponding length allowable deviation value in the project verification benchmark table, the width difference is less than or equal to the corresponding width allowable deviation value, the height difference is less than or equal to the corresponding height allowable deviation value, the installation coordinate difference is less than or equal to the corresponding coordinate allowable deviation value, and the interface specification code is consistent, the verification branch mark of the corresponding electromechanical prefabrication module is written into the batch prefabrication access branch.

[0030] When the number of upstream or downstream connected modules of the electromechanical prefabricated module is greater than 0, and the interface type is any one of electrical interface, pipeline interface, cable tray interface, busbar interface, equipment connection interface, or support and hanger connection interface, the verification branch mark of the corresponding electromechanical prefabricated module is written into the interface handshake locking branch, and an interface handshake object list is generated in the module prefabrication status package. The interface handshake object list includes the current module interface number, adjacent module number, interface type, interface specification, interface centerline, interface elevation, interface direction, and connection method.

[0031] When the minimum distance between the outer contour of the electromechanical prefabricated module and the wall, beam, column, opening, equipment foundation, maintenance passage, transportation passage or installed components is less than or equal to the corresponding net distance value extracted from the construction acceptance documents, construction detail drawings or equipment installation manual in the project verification benchmark table, the verification branch mark of the corresponding electromechanical prefabricated module is written into the on-site counter-verification branch, and a list of on-site re-measurement objects is generated in the module prefabrication status package; the list of on-site re-measurement objects includes the foundation location, opening location, beam and column boundary, wall boundary, transportation passage, door opening size, the occupancy status of installed components and the handover status of the installation work surface that need to be re-measured.

[0032] When the remaining transport capacity of the electromechanical prefabricated module is less than 0, the remaining hoisting weight is less than 0, the remaining temporary storage capacity is less than 0, or the electromechanical prefabricated module has a pre-installation module number, the corresponding electromechanical prefabricated module's verification branch mark is written into the implementation window verification branch, and an implementation window verification object list is generated in the module prefabrication status package; the implementation window verification object list includes the design freeze time, the manufacturer's planned processing start time, the manufacturer's planned processing completion time, the planned delivery time, the transportation cycle, the on-site receiving time, the planned installation time, and the pre-installation module number.

[0033] If the same electromechanical prefabrication module has multiple verification branch markers, the execution order field is written in the order of interface handshake locking branch, on-site counter-verification verification branch, implementation window verification branch, and batch prefabrication access branch. Among them, the judgment result of the interface handshake locking branch is used to determine whether the module interface can be processed, the judgment result of the on-site counter-verification verification branch is used to determine the prefabrication range of the module body section, interface end, and on-site adjustment section, the judgment result of the implementation window verification branch is used to determine whether the module can enter the processing, delivery, and installation plan, and the judgment result of the batch prefabrication access branch is used to determine whether the same type of module can use the same processing template.

[0034] After completing the prefabrication access branch judgment, the module prefabrication status package, project verification benchmark table, interface handshake object list, on-site retest object list, and implementation window verification object list are associated and stored, and an initial verification status is generated. The initial verification status includes pending interface handshake, pending on-site verification, pending window verification, batch prefabrication candidate, data pending supplementation, and prohibition of direct release. The initial verification status serves as the input for subsequent interface handshake locking, on-site verification, implementation window linkage judgment, and status graph review, enabling the prefabrication verification of electromechanical prefabrication modules to form a traceable status chain from the data establishment stage.

[0035] S2: Based on the module prefabrication status package and the project verification benchmark table, perform prefabrication access branch determination for electromechanical prefabrication modules, forming interface handshake locking branch, on-site counter-verification verification branch and implementation window verification branch.

[0036] Furthermore, the system reads the established module prefabrication status package, project verification benchmark table, and interface handshake object list. For each connection relationship recorded in the interface handshake object list, an interface handshake unit is established. This unit processes the current electromechanical prefabrication module and adjacent electromechanical prefabrication modules, recording the correspondence between the two modules in terms of interface location, interface specifications, connection method, and processing boundary. Each interface handshake unit includes at least the following: current module code, adjacent module code, current module interface number, adjacent module interface number, interface type, interface specification code, connection method code, interface centerline coordinates, interface elevation, interface direction angle, interface end boundary, interface data confirmation flag, interface responsible unit, allowable deviation value, adjustable margin, interface handshake status, and processing boundary status.

[0037] The interface type is determined based on the interface constraint information in the module prefabrication status package, including electrical interfaces, conduit interfaces, cable tray interfaces, busbar interfaces, equipment connection interfaces, support / hanger interfaces, and control cable interfaces. For electrical interfaces, interface parameters include circuit number, terminal position, incoming / outgoing direction, cable specification, grounding connection position, and connection method code. For conduit interfaces, interface parameters include pipe diameter, flange specification, connection centerline, interface elevation, connection direction, connection method code, and reserved adjustment section length. For cable tray interfaces, interface parameters include cable tray width, cable tray height, connection piece position, elbow angle, cover opening direction, and bridging grounding position. For busbar interfaces, interface parameters include phase sequence identifier, connection end position, connection end direction, connection section specification, and reserved end length. For equipment connection interfaces, interface parameters include equipment interface centerline, anchor hole position, vibration damping foundation dimensions, maintenance side direction, and connection reference plane. For support / hanger interfaces, interface parameters include lifting point coordinates, anchor bolt specification, load-bearing direction, support / hanger connection hole position, and structural connection position.

[0038] When establishing an interface handshake unit, the source of the interface parameters on both sides is confirmed. The current module interface parameters are derived from the detailed construction drawings, manufacturer's processing drawings, or module prefabrication status packages; the adjacent module interface parameters are derived from the detailed construction drawings, manufacturer's processing drawings, or module prefabrication status packages corresponding to the adjacent modules; the allowable deviation values ​​are derived from the records in the project verification benchmark table corresponding to the interface type, professional category, and connection method; the adjustable margin is derived from the reserved adjustment section length in the detailed construction drawings, the adjustable range of connectors in the equipment installation manual, the expansion and contraction of flexible connections, the stroke of expansion joints, or the adjustment stroke of adjustable supports. If there are multiple adjustable sources for the same interface, only the adjustment amount that can act in the same direction is included in the adjustable margin for that direction; the adjustment amounts in different directions are recorded separately and are not accumulated across directions.

[0039] Perform a data integrity check on the interface handshake unit. If the current module's interface specification code, connection method code, interface centerline, interface elevation, interface direction angle, or corresponding field of an adjacent module contains null values, mark the corresponding interface handshake unit as having interface data pending data entry, and record the missing field name, field source, responsible unit, and object to be entered. Before the interface data pending data entry status is lifted, the corresponding interface must not enter a double-sided interface lock state, and the corresponding module must not generate a complete processing boundary. If both sides of the interface parameters contain valid fields, proceed to the interface handshake lock check.

[0040] The specifications and connection methods of the interfaces on both sides are determined. If the specification code of the current module interface is the same as that of the adjacent module interface, and the connection method code of the current module is also the same as that of the adjacent module, then the position and direction are determined. If the interface specification codes or connection method codes are different, the interface handshake unit is marked as an interface conflict state, and the processing boundary state corresponding to the interface is written to the prohibited processing boundary. The interface specification code is used to indicate the size specification, model specification, pipe diameter specification, cable tray specification, busbar connection section specification, or terminal specification of the interface; the connection method code is used to indicate the flange connection, bolt connection, plug connection, crimp connection, welded connection, flexible connection, or bracket fixed connection method.

[0041] The centerline, elevation, and direction of both interfaces are determined. The centerline difference is calculated based on the current module interface centerline and the adjacent module interface centerline; the elevation difference is calculated based on the current module interface elevation and the adjacent module interface elevation; and the direction angle difference is calculated based on the current module interface direction angle and the adjacent module interface direction angle. The centerline difference is represented by the spatial distance between the centerlines of the two interfaces in a unified coordinate system; the elevation difference is represented by the absolute value of the difference between the elevation values ​​of the two interfaces; and the direction angle difference is represented by the angle between the normal directions or connection directions of the two interfaces. The unified coordinate system is based on the project's reference coordinate system in the project's electromechanical design model or construction detailing model. If the manufacturer's fabrication drawings use an independent coordinate system, coordinate transformation is first performed based on the module installation reference point and installation direction before the difference calculations are performed.

[0042] When the interface specification codes are the same, the connection method codes are the same, the difference in interface centerlines is less than or equal to the allowable deviation value for interface centerlines in the project verification benchmark table, the difference in interface elevation is less than or equal to the allowable deviation value for elevation in the project verification benchmark table, and the difference in interface direction angle is less than or equal to the allowable deviation value for interface direction in the project verification benchmark table, the corresponding interface handshake unit is marked as a double-sided interface locked state. After the double-sided interface locked state is formed, the locked interface specification code, connection method code, interface centerline, interface elevation, interface direction angle, and locked version number are simultaneously written into the module prefabrication status package of the current module and the adjacent module, and the processing boundary status corresponding to the interface is written into the complete processing boundary. For interfaces in the double-sided interface locked state, their interface specifications, connection methods, interface centerlines, interface elevations, and interface direction angles serve as fixed verification bases for subsequent manufacturer processing, on-site retesting, and change transfer.

[0043] When one side of the interface has a data confirmation mark while the other side does not, the side with the data confirmation mark is written to the single-side interface confirmation status, and the side without the data confirmation mark is written to the interface pending confirmation status. The data confirmation mark is generated from the design freeze document, manufacturer's detailed confirmation document, equipment arrival confirmation document, or on-site retest confirmation document. For modules in the single-side interface confirmation status, their main body and non-interface sections can proceed to subsequent processing judgment, but the interface end is written to the interface reserved boundary. The interface reserved boundary includes interface end connection holes, connection flanges, busbar end connection sections, cable tray connection pieces, pipe end welded sections, final fixing holes for supports and hangers, and final crimp ends for cables. The final fixing processing of the interface reserved boundary must not be completed before the adjacent side interface is confirmed.

[0044] When the interface specification codes and connection method codes are the same, but the difference in the interface centerline is greater than the allowable deviation value of the interface centerline and less than or equal to the sum of the allowable deviation value of the interface centerline and the adjustable margin of the centerline, or the difference in the interface elevation is greater than the allowable elevation deviation value and less than or equal to the sum of the allowable elevation deviation value and the adjustable margin of the elevation, or the difference in the interface direction angle is greater than the allowable deviation value of the interface direction and less than or equal to the sum of the allowable deviation value of the interface direction and the adjustable margin of the direction, the corresponding interface handshake unit will be marked as an adjustable interface reserved state. After the adjustable interface reserved state is formed, an adjustable processing boundary is generated in the module prefabrication state package; the adjustable processing boundary includes the reserved length, reserved direction, type of adjustment component, on-site re-measurement point, temporarily unfixed part, and final fixing conditions. The reserved length comes from the reserved adjustment section length recorded in the construction detailing drawing or equipment installation manual, the reserved direction is consistent with the difference direction, and the type of adjustment component corresponds to flexible connection, expansion joint, adjustable bracket, adjusting short pipe, cable tray adjustment section, or busbar adjustment. The "not fixed" part is used to indicate that the manufacturer must not perform closed welding, final drilling, final crimping, end sealing plate fixation, or irreversible connection during processing.

[0045] When interface specification codes, connection method codes, or interface centerline differences exceed the sum of the allowable deviation of the interface centerline and the adjustable margin of the centerline, or interface elevation differences exceed the sum of the allowable elevation deviation and the adjustable margin of the elevation, or interface direction angle differences exceed the sum of the allowable direction deviation and the adjustable margin of the direction, the corresponding interface handshake unit is marked as an interface conflict state. After an interface conflict state is formed, both modules are not immediately rolled back. Instead, the adjustment target is determined based on the procurement status, processing status, and site foundation status of both modules. If the procurement status of the associated equipment on a certain interface side is "procurement complete," or the processing status of the corresponding module is "fully processed," or the site foundation status of the corresponding interface connection is "immovable," then that interface side is written as the "unadjustable side." Modules not written as "unadjustable side" are the adjustment targets. If both sides are written as "unadjustable side," then the interface handshake unit is written as a design review target, and a design review mark is generated in the corresponding module's prefabricated status package. Once the target to be adjusted is determined, the adjustment content is written into the interface adjustment task, including the fields to be adjusted, the values ​​before adjustment, the values ​​locked on adjacent sides, the corresponding source files, and the review order.

[0046] During the interface handshake lock determination process, when multiple interfaces exist for the same electromechanical prefabricated module, multiple interface handshake units are generated, and the handshake states of each interface are summarized into a module interface comprehensive state. If all interfaces of the module are in a double-sided interface locked state, the module interface comprehensive state is written as "interface fully locked"; if at least one adjustable interface is reserved and there is no interface conflict state, the module interface comprehensive state is written as "interface adjustable reserved"; if at least one unilateral interface is confirmed and there is no interface conflict state, the module interface comprehensive state is written as "interface partially confirmed"; if at least one interface is in a conflict state, the module interface comprehensive state is written as "interface conflict"; if there is an interface data pending entry state, the module interface comprehensive state is written as "interface data pending entry". The module interface comprehensive state is used to determine whether the module can form a complete processing boundary, a partial processing boundary, an adjustable processing boundary, an interface reserved boundary, or a prohibited processing boundary.

[0047] Based on the judgment result of the interface handshake unit, processing boundary control results are generated. These results are formed in units of module body section, interface end, field adjustment section, and temporarily unfixed section. Specifically, a complete processing boundary corresponds to a double-sided interface locked state, indicating that the corresponding interface end can enter the factory for final processing; a non-interface processing boundary corresponds to the module body section and standard section, indicating that parts unaffected by the interface pending confirmation state can enter the factory for processing; an adjustable processing boundary corresponds to an adjustable interface reserved state, indicating that the corresponding part is only allowed to complete prefabrication processing that does not affect field adjustment; an interface reserved boundary corresponds to a single-sided interface confirmed or interface pending confirmation state, indicating that the interface end will not undergo final fixing processing for the time being; and a prohibited processing boundary corresponds to an interface conflict, interface data pending supplementation, or design review object state, indicating that this part must not be processed before the interface review is completed.

[0048] After the processing boundary control results are generated, the corresponding results are written back to the prefabrication boundary information, interface constraint information, and manufacturer processing information in the module prefabrication status package. The prefabrication boundary information records the spatial range and component range of each boundary; the interface constraint information records the interface handshake status, lock version number, adjustable processing boundaries, and interface responsible party; and the manufacturer processing information records the allowed processing range, prohibited processing range, pending confirmation range, and adjustable reserved range. If the interface handshake result causes changes in the interface parameters, prefabrication boundaries, or adjustable range of adjacent modules, the module prefabrication status package of the adjacent modules is updated synchronously, and the corresponding interface handshake unit of the adjacent module is written to the pending review status.

[0049] After completing the interface handshake lock judgment, output the interface handshake result list and the processing boundary control list. The interface handshake result list includes the module code, adjacent module codes, interface number, interface type, interface handshake status, lock parameters, fields to be added, adjustment objects, and responsible units. The processing boundary control list includes the module code, complete processing boundary, non-interface processing boundary, adjustable processing boundary, interface reserved boundary, prohibited processing boundary, and corresponding source interface. The processing boundary control list serves as input for the on-site retest verification judgment, used to determine whether the on-site differences affect the main segment, interface end, adjustable segment, temporarily unfixed segment, or prohibited processing segment when subsequent on-site retest data arrives.

[0050] S3: Under the interface handshake lock branch, lock, retain, adjust or roll back the interface parameters of adjacent electromechanical prefabricated modules to generate processing boundary control results; under the on-site verification branch, map the on-site retest data with the processing boundary control results to determine the affected parts and correct the prefabrication range of the electromechanical prefabricated modules.

[0051] Furthermore, the system reads the module prefabrication status package, project verification benchmark table, interface handshake result list, processing boundary control list, and on-site retest object list. The on-site retest object list is generated by the preceding prefabrication access branch judgment and is used to determine the scope of objects requiring on-site verification. The processing boundary control list is generated by the interface handshake lock judgment and is used to determine the boundary range of the main body section, interface end, on-site adjustment section, temporarily unfixed section, and prohibited processing section in the electromechanical prefabrication module. After the on-site retest data arrives, the system does not directly determine whether the module can be prefabricated based on the on-site retest results. Instead, it first maps the on-site retest data to the processing boundary control list to determine the specific parts affected by the on-site differences, and then adjusts the module's prefabrication range based on the affected parts.

[0052] The on-site re-measurement data includes the actual dimensions of the equipment foundation, the actual coordinates of the equipment foundation, the actual location and dimensions of the reserved openings, the actual boundaries of beams and columns, the actual boundaries of walls, the actual elevation of floor slabs, the clear width and height of the machine room doorway, the clear width of the transport passage, the clear dimensions of the turning area of ​​the transport passage, the occupied area of ​​the hoisting path, the occupancy status of installed components, the handover status of the installation work surface, the available area of ​​the temporary storage area, the occupied area of ​​the temporary storage area, and the on-site re-measurement time. The on-site re-measurement data is provided by on-site measurement records, 3D scanning results, total station measurement results, construction unit handover records, civil engineering handover and acceptance records, and on-site transport passage verification records; each piece of on-site re-measurement data records the data source, measurement time, measurement personnel, measurement equipment number, and the corresponding machine room area.

[0053] Before writing the on-site remeasurement data, the data undergoes object matching and coordinate unification. Object matching uses module code, machine room area number, floor number, grid position, equipment foundation number, opening number, and adjacent component number as matching fields. When an on-site remeasurement object can correspond to an equipment foundation, opening, beam-column boundary, transport channel, or installation work surface in the module prefabrication status package, the corresponding on-site remeasurement field is written into that module prefabrication status package. If an on-site remeasurement object cannot correspond to an object in the module prefabrication status package, the on-site remeasurement object is added to the list of objects to be matched, and the name of the unmatched field and the source of responsibility are recorded.

[0054] Coordinate unification is performed using the project's reference coordinate system in the project's electromechanical design model or construction detailing model. If the on-site re-measurement data uses the on-site measurement coordinate system, coordinate transformation is performed based on the on-site reference points, axis control points, and floor elevation reference points. If the module coordinates in the manufacturer's fabrication drawings use a local coordinate system, they are transformed to the project's reference coordinate system based on the module installation reference points, installation direction, and installation elevation. After coordinate transformation, the differences in equipment foundation positions, reserved opening positions, beam-column boundary differences, wall boundary differences, floor slab elevation differences, remaining doorway clearance, and remaining transport passage clearance are calculated.

[0055] The difference in equipment foundation location is calculated based on the spatial distance between the center coordinates of the foundation measured on-site and the center coordinates of the foundation designed in the prefabricated module package; the difference in reserved opening location is calculated based on the spatial distance between the center coordinates of the opening measured on-site and the center coordinates of the opening designed; the difference in beam-column boundary is calculated based on the minimum distance between the beam-column boundary line measured on-site and the design boundary line; the difference in wall boundary is calculated based on the minimum distance between the wall boundary line measured on-site and the design wall boundary line; the difference in floor slab elevation is calculated based on the absolute value of the difference between the floor slab elevation measured on-site and the design floor slab elevation. The remaining passage space for doorways is obtained by subtracting the corresponding dimensions after module packaging from the net width or net height of the doorway, and then subtracting the corresponding dimensions occupied by the transport vehicle; the remaining passage space for transport aisles is obtained by subtracting the module packaging dimensions from the net width or net clearance dimensions of the transport aisle or turning area, and then subtracting the dimensions occupied by the transport vehicle.

[0056] After completing the on-site remeasurement data matching and difference calculation, the completeness of the on-site remeasurement data is judged. If any of the required fields in the following categories is empty: equipment foundation dimensions, equipment foundation coordinates, reserved opening location, beam and column boundaries, wall boundaries, floor slab elevation, door opening dimensions, transportation channel dimensions, occupancy status of installed components, or handover status of installation work surface, the on-site constraint information of the corresponding module is written into the on-site data pending supplementation status, and the empty field, data source, responsible unit, and supplementation object are recorded. Modules in the on-site data pending supplementation status cannot enter the complete prefabrication release judgment; if its interface handshake result is that both interfaces are locked or the adjustable interface is retained, it only retains the qualification to enter the partial processing candidate.

[0057] After the on-site re-measurement data is complete, on-site counter-evidence judgment is performed based on the project verification benchmark table. The allowable deviations for foundation dimensions, opening locations, boundaries, and elevations, as well as the calculation rules for remaining transport capacity, temporary storage capacity, and installation work surface status fields in the project verification benchmark table, are all used as the basis for on-site counter-evidence judgment. Each allowable deviation value is derived from the project design documents, construction acceptance documents, equipment installation manuals, or manufacturer's processing technology documents. When multiple sources exist for the same verification item, the adopted value recorded in the project verification benchmark table is used, and the source documents and adoption rules are retained.

[0058] When the differences in equipment foundation dimensions are less than or equal to the allowable deviation values ​​in the project verification benchmark table, the differences in equipment foundation positions are less than or equal to the allowable deviation values ​​in foundation positions, the differences in reserved opening positions are less than or equal to the allowable deviation values ​​in opening positions, the differences in beam-column boundaries are less than or equal to the allowable deviation values ​​in boundary conditions, the differences in wall boundaries are less than or equal to the allowable deviation values ​​in boundary conditions, the differences in floor slab elevations are less than or equal to the allowable deviation values ​​in elevation conditions, the remaining passageway capacity for doorways is greater than or equal to 0, the remaining passageway capacity for transportation channels is greater than or equal to 0, and the handover status of the installation work surface is "handed over," the on-site constraint information in the module prefabrication status package is written into the on-site acceptable status. For modules in the on-site acceptable status, the on-site remeasurement data does not change the boundary relationships of the main section, interface end, on-site adjustment section, and temporarily unfixed section in the processing boundary control list, and the corresponding modules maintain the prefabrication range formed by the previous interface handshake judgment.

[0059] When at least one difference in the on-site retest data exceeds the corresponding allowable deviation value in the project verification benchmark table, but all affected parts corresponding to this difference fall within the adjustable processing boundary in the processing boundary control list, and the difference is less than or equal to the sum of the corresponding allowable deviation value and the corresponding adjustable margin, the on-site constraint information in the module prefabrication status package is written into the on-site adjustable receiving status. Affected parts within the adjustable processing boundary include on-site adjustment sections, temporarily unfixed sections, reserved connection sections, flexible connection sections, expansion joint sections, adjustable support sections, cable tray adjustment sections, busbar adjustment joints, or pipeline adjustment short pipes. For modules in the on-site adjustable receiving status, the main body section, standard section, and non-interface section can be retained as prefabricable sections; the interface end, end connection section, final fixed section, and on-site adjustment section are written into the fixed range after on-site confirmation.

[0060] When at least one difference in the on-site retest data exceeds the sum of the corresponding allowable deviation value and the corresponding adjustable margin in the project verification benchmark table, or when the affected part corresponding to this difference belongs to the main section, transportation entry path, hoisting path, prohibited processing boundary, or non-adjustable side connection range in the processing boundary control list, the on-site constraint information in the module prefabrication status package will be written to the on-site verification failure status. For modules in the on-site verification failure status, the prefabrication range will be corrected to prohibit complete prefabrication, and a return verification mark will be generated in the module prefabrication status package. The return verification mark includes at least one of design verification, interface re-handshake, module splitting, transportation path verification, or installation sequence verification; the specific return type is determined according to the affected field.

[0061] When the installation work surface is not handed over, the transportation channel is impassable, the occupancy status of the installed components is inconsistent with the occupancy status in the design model, or the measurement time of the on-site re-measurement data is earlier than the time of the most recent design change for the corresponding area, the on-site constraint information in the module prefabrication status package will be written into the on-site condition unclosed state. Modules in the on-site condition unclosed state shall not enter the complete prefabrication release judgment; if there are non-interface processing boundaries in the processing boundary control list, and the non-interface processing boundaries are not affected by the unclosed field, the corresponding module can retain the local processing candidate state.

[0062] To determine the affected locations corresponding to differences in on-site measurements, a mapping relationship between on-site differences and processing boundaries was established. Differences in equipment foundation locations are mapped to equipment connection interfaces, anchor fixing sections, vibration damping foundation sections, and main equipment installation sections; differences in reserved opening locations are mapped to through-wall pipe sections, through-slab pipe sections, cable tray crossing sections, busbar crossing sections, and fireproof sealing sections; differences in beam-column boundaries are mapped to support and hanger fixing sections, pipeline avoidance sections, cable tray turning sections, and maintenance passage boundaries; differences in floor slab elevations are mapped to support and hanger rod lengths, pipe slope sections, equipment base sections, and cable tray elevation sections; remaining passage space in transportation channels is mapped to module packaging dimensions, transportation posture, transfer path, and on-site entry direction; and the occupancy status of installed components is mapped to module installation paths, installation sequences, and temporary avoidance spaces. These mapping relationships are written into the module prefabrication status package to determine whether the on-site differences affect the main body section, interface ends, on-site adjustment sections, temporarily unfixed sections, or sections where processing is prohibited.

[0063] If the on-site remeasurement difference only affects the on-site adjustment section, the corresponding adjustment section will be written into the on-site unconfirmed boundary, and the processing status of the main body section will be retained. If the on-site remeasurement difference affects the interface end, the corresponding interface handshake unit will be written into the unverified status, and the relevant module of the interface will be returned to the interface handshake lock judgment. If the on-site remeasurement difference affects the main body section, the main body section will be written into the prohibited complete processing boundary, and a design verification object will be generated. If the on-site remeasurement difference affects the transportation entry path or hoisting path, the module will be written into the implementation window verification object. If the on-site remeasurement difference affects the pre-installation module or the occupancy status of adjacent installed components, the module and its adjacent modules will be written into the status map unverified object.

[0064] The linkage between on-site retest data and interface handshake results is updated. If the on-site retest data changes the equipment foundation coordinates, reserved opening positions, wall boundaries, beam-column boundaries, or floor slab elevations, resulting in changes to the interface centerline, interface elevation, or interface direction of locked interfaces, the double-sided interface locking status of the corresponding interface handshake unit is released, the interface handshake status is updated to pending verification, and the module prefabrication status packets of the current module and adjacent modules are synchronously written to the interface verification flag. If the on-site retest data does not change the locked interface parameters but only changes the on-site fixed position of the adjustable section, the interface locking status is maintained, and the on-site retest points and final fixed conditions in the adjustable processing boundary are updated.

[0065] On-site verification is performed to determine the temporary storage conditions. The remaining temporary storage capacity is calculated by subtracting the occupied storage area from the available storage area, and then subtracting the area occupied by the packaging of the modules to be delivered. When the remaining temporary storage capacity is greater than or equal to 0, and both the moisture-proof and dust-proof measures and the finished product protection measures are configured, the temporary storage condition is set to "true". When the remaining temporary storage capacity is less than 0, or either the moisture-proof and dust-proof measures or the finished product protection measures are not configured, the temporary storage condition is set to "false". The validity or invalidity of the temporary storage condition does not directly change whether the module can be processed, but it serves as input for the "processable but temporarily delayed" status in subsequent window linkage judgments.

[0066] On-site verification is performed to confirm the transport entry conditions. If the remaining capacity of the doorway, transport passage, and turning area are all greater than or equal to 0, the transport entry condition is set to "true". If any of these remaining capacities is less than 0, the transport entry condition is set to "false", and the module is added to the transport path verification object. If the transport entry condition is false, but the packaging dimensions of each split unit after module splitting ensure that the remaining capacity is greater than or equal to 0, a module splitting candidate flag is generated in the module prefabrication status package. If the splitting process still fails to achieve a remaining capacity greater than or equal to 0, the module is set to "prohibited from leaving the factory" candidate status, awaiting confirmation through subsequent implementation window linkage.

[0067] After the on-site counter-evidence assessment is completed, the prefabrication range of the module is corrected. The corrected prefabrication range is recorded separately for the main body section, standard section, non-interface section, interface end, end connection section, on-site adjustable section, final fixed section, and prohibited processing section. For the on-site acceptable state, the previous processing boundary control results are maintained; for the on-site adjustable and acceptable state, the main body section, standard section, and non-interface section are written into the allowable processing range, and the interface end, end connection section, on-site adjustable section, and final fixed section are written into the processing range after on-site confirmation; for the on-site counter-evidence failure state, the affected main body section, the structure corresponding to the transportation entry path, the structure corresponding to the hoisting path, or the prohibited processing boundary are written into the prohibited processing range; for the on-site conditions not closed, the non-interface processing boundary is written into the local processing candidate range, and the complete processing boundary is not written into the complete prefabrication release range for the time being.

[0068] After completing the on-site counter-evidence judgment, the on-site constraint information, the set of affected parts, the mapping relationship between on-site differences and processing boundaries, the correction results of the prefabrication range, the on-site boundaries to be confirmed, the interface verification markers, the transportation route verification objects, the module splitting candidate markers, and the temporary condition status are written back to the module prefabrication status package. If the on-site counter-evidence judgment triggers interface verification, the interface handshake result list is updated synchronously; if it triggers transportation route verification or module splitting candidates, the implementation window verification object list is updated synchronously; if it triggers adjacent module verification, the adjacent relationship markers in the module status graph are updated synchronously.

[0069] After the on-site counter-evidence assessment is completed, an on-site counter-evidence result list and a prefabrication range correction list are output. The on-site counter-evidence result list includes the module code, on-site re-measurement object, re-measurement field, design value, measured value, difference, adopted benchmark value, affected parts, on-site constraint status, and responsible unit. The prefabrication range correction list includes the module code, allowed processing range, processing range after on-site confirmation, prohibited processing range, interface verification object, transportation route verification object, module splitting candidate object, and temporary condition status. The prefabrication range correction list serves as input for the implementation window linkage assessment, used to subsequently determine whether a module enters the status of complete prefabrication release, partial prefabrication release, processing with delayed delivery, prohibited prefabrication, or priority production scheduling.

[0070] It should be noted that the process involves reading the module prefabrication status package, project verification benchmark table, interface handshake result list, processing boundary control list, on-site counter-evidence result list, and prefabrication range correction list. The implementation of window-linked judgment uses the previously generated interface handshake status, on-site constraint status, and prefabrication range as input to determine the specific status of the electromechanical prefabricated module: complete processing, partial processing, processing with delayed delivery, prohibited prefabrication, or production scheduling adjustment. This step does not make a release decision solely based on the construction schedule; instead, it continuously verifies the design freeze, interface lock, on-site acceptance, manufacturer processing, transportation arrival, and installation plans, ensuring that the technical verification results in the module prefabrication status package are converted into execution control results for manufacturer processing, logistics delivery, and on-site installation.

[0071] The data required for implementing window-linked judgment includes design freeze time, manufacturer's planned processing start time, manufacturer's planned processing completion time, planned delivery time, transportation cycle, on-site receiving time, planned installation time, installation buffer time, maximum temporary storage period, remaining temporary storage capacity, status of moisture-proof and dust-proof measures, status of finished product protection measures, pre-installation module number, manufacturer's remaining processing cycle, transportation batch number, and installation sequence number. The design freeze time is derived from design management documents or design freeze confirmation records; the manufacturer's planned processing start time and planned processing completion time are derived from the manufacturer's production schedule; the planned delivery time is derived from the logistics plan or the manufacturer's delivery plan; the transportation cycle is derived from the transportation route, loading and unloading methods, and transportation duration recorded in the transportation plan; the on-site receiving time is derived from the on-site handover plan or regional receiving plan; the planned installation time is derived from the construction progress plan; and the status of moisture-proof and dust-proof measures and the status of finished product protection measures are derived from the finished product protection plan or on-site temporary storage inspection records.

[0072] The installation buffer time is calculated by adding the factory acceptance time, on-site unloading time, on-site secondary transfer time, unpacking and inspection time, and pre-installation handover and acceptance time. These times are extracted from the manufacturer's factory acceptance process, transportation and hoisting plan, on-site transfer plan, and construction acceptance process, respectively. If a timeframe is not recorded in the corresponding document, the field is written to the "pending supplementation" status, and the missing field name and responsible unit are recorded. The maximum temporary storage period is read from the finished product protection plan. If the finished product protection plan does not record the maximum temporary storage period, the maximum temporary storage period field is written to the "pending supplementation" status, and the corresponding module is marked as having an unclosed temporary storage period. Electromechanical prefabricated modules with fields requiring supplementation must not directly enter the complete prefabrication release state.

[0073] After reading the implementation window data, a module implementation window chain is first established. This chain includes a design freeze node, a manufacturer processing node, a factory shipping node, a site receiving node, and a site installation node. The design freeze node confirms whether the design data is frozen before manufacturer processing; the manufacturer processing node confirms whether the manufacturer can complete processing before the planned shipment; the factory shipping node confirms whether the module can arrive at the site before the scheduled receipt time; the site receiving node confirms whether the site has the conditions for receiving, temporarily storing, or directly installing the module; and the site installation node confirms whether the module can be installed according to the planned installation time after arrival. Each node records the node time, the node source document, the responsible unit for the node, and the node confirmation status.

[0074] A completeness check is performed on the implementation window chain. If any of the following are missing values: design freeze time, manufacturer's planned processing start time, manufacturer's planned processing completion time, planned delivery time, transportation cycle, on-site receiving time, or planned installation time, the module implementation window status is recorded as "unclosed in time field," and a time field supplementation task is generated. Modules in the "unclosed in time field" state are not allowed to enter the complete prefabrication release state; however, if the module's interface status is "both sides locked," its on-site constraint status is "on-site acceptable" or "on-site adjustable acceptable," and there are non-interface processing boundaries in the prefabrication range correction list, then it retains the qualification to enter the partial prefabrication release check.

[0075] After the window chain is completed, a window matching judgment is performed. If the design freeze time is less than or equal to the manufacturer's planned processing start time, the manufacturer's planned processing completion time is less than or equal to the planned delivery time, the sum of the planned delivery time and the transportation cycle is less than or equal to the on-site receiving time, and the sum of the on-site receiving time and the installation buffer time is less than or equal to the planned installation time, then the implementation window status is written into the window matching. Window matching indicates that there is a sequential relationship in time between design freeze, manufacturer processing, transportation arrival, on-site receiving, and planned installation.

[0076] If the manufacturer's planned processing completion time is less than the difference between the on-site receiving time and the maximum temporary storage period, and the remaining temporary storage capacity is less than the area occupied by the module's temporary storage, then the implementation window status will be marked as premature prefabrication risk. The remaining temporary storage capacity is derived from the on-site counter-evidence list, and is calculated by subtracting the occupied storage area from the available storage area and then subtracting the area occupied by the module's packaging. This status indicates that the module's processing completion time is earlier than the on-site receiving time, and the on-site temporary storage space is insufficient to accommodate the module.

[0077] If the sum of the manufacturer's planned processing completion time and transportation cycle is greater than the difference between the planned installation time and the installation buffer time, the implementation window status will be set to prefabrication delay risk. This status indicates that, based on the current manufacturer's processing and transportation cycles, the module cannot be delivered and handed over before the planned installation time.

[0078] If the design freeze time, manufacturer's planned processing start time, manufacturer's planned processing completion time, planned delivery time, site acceptance time, and planned installation time cannot simultaneously meet the window matching conditions, and this does not fall under a single scenario of premature prefabrication risk or prefabrication delay risk, then the implementation window status will be recorded as a window conflict. The window conflict record specifies the invalid time relationships, including at least one of the following: design freeze time is later than manufacturer's planned processing start time; manufacturer's planned processing completion time is later than planned delivery time; the sum of planned delivery time and transportation period is later than site acceptance time; and the sum of site acceptance time and installation buffer time is later than planned installation time.

[0079] After the implementation window status is determined, the design status, interface status, on-site constraint status, prefabrication range correction results, processing boundary control results, and number of unclosed abnormal tasks in the module prefabrication status package are read, and a graded release judgment is performed. The graded release results include five categories: complete prefabrication release, partial prefabrication release, processing available but temporarily suspended, prefabrication prohibited, and priority scheduling. Each category of result is written into the release level field of the module prefabrication status package.

[0080] When the design status is frozen or design review completed, the interface status is locked on both sides, the site constraint status is acceptable on site, the implementation window status is window matched, the number of unclosed abnormal tasks is 0, and there is no prohibited processing range in the prefabrication range correction list, the module is determined to be fully prefabricated and released. After the full prefabrication release is formed, a complete processing instruction is output to the manufacturer. The complete processing instruction includes the module code, allowed processing range, locked interface parameters, processing drawing version, planned processing start time, planned processing completion time, and planned delivery time. A delivery plan is output to the logistics end. The delivery plan includes the module code, packaging dimensions, module weight, transportation route, planned delivery time, and on-site receiving time. An installation and receiving plan is output to the construction end. The installation and receiving plan includes the module code, installation area, planned receiving time, planned installation time, pre-installed module number, and installation work surface number.

[0081] When the design status is "Design Frozen," the intersection of the affected parts set and the main body segment range is empty, the interface status is "Single-sided Interface Confirmed" or "Adjustable Interface Reserved," the field constraint status is "Field Adjustable Acceptable" or "Field Conditions Not Closed," and there are non-interface processing boundaries in the processing boundary control list, this module is judged as a partial prefabrication release. After the partial prefabrication release is formed, a partial processing instruction is output to the manufacturer. The partial processing instruction restricts the manufacturer to only process the main body segment, standard segment, or non-interface segment, and prohibits the processing of interface ends, end connection segments, field adjustment segments, and final fixed segments. The partial processing instruction also records the prohibited processing parts, fields to be confirmed, objects to be retested, and the conditions triggering re-judgment. After the fields to be confirmed are completed, the field constraint status changes to "Field Acceptable," or the interface status changes to "Double-sided Interface Locked," this module re-enters the hierarchical release judgment.

[0082] When a module is deemed "processable" and its processing status is "ready to be processed," the on-site receiving time is greater than the sum of the planned delivery time and the transportation cycle, the remaining temporary storage capacity is greater than or equal to the temporary storage area occupied by the module, the moisture-proof and dust-proof measures are configured, the finished product protection measures are configured, and the implementation window status is not conflicting, the module is determined to be "processable but temporarily deferred from delivery." After the "processable but temporarily deferred from delivery" status is established, the manufacturer is allowed to generate processing tasks, but the logistics department must not generate delivery tasks. The module prefabrication status package includes the reason for the deferred delivery, the conditions for lifting the deferred delivery, and the next window review time. The conditions for lifting the deferred delivery include at least one of the following: the on-site receiving time has arrived, the on-site temporary storage conditions have been updated, the installation work surface handover status has been updated, or the construction schedule has been updated.

[0083] When the design status is "Design not frozen" or "Design under change," or the interface status is "Interface conflict," or the site constraint status is "Site verification failed," or the implementation window status is "Window conflict," or the corresponding module's main body section is written into the prohibited processing range in the prefabrication scope correction list, the module is determined to be prohibited from prefabrication. After the prohibition on prefabrication is established, the module's processing order, factory delivery plan, and site installation plan are suspended, and a review task is generated. Review tasks are generated according to the reason for prohibition on prefabrication: a design review task is generated when the design status is not closed; an interface review task is generated when the interface status is "Interface conflict"; a site retest or module splitting task is generated when the site constraint status is "Site verification failed"; a progress window coordination task is generated when the implementation window status is "Window conflict"; and a processing boundary review task is generated when the main body section is written into the prohibited processing range.

[0084] When the implementation window status is "prefabrication delay risk," the design status is not "design change in progress," the interface status is not "interface conflict," the site constraint status is not "site verification failed," and the prefabrication scope correction list does not contain any prohibited processing areas affecting the main body, the module is determined to be prioritized for production. After priority production is formed, production adjustment information is generated based on the planned installation time, the manufacturer's remaining processing cycle, the transportation cycle, the number of pre-installed modules, and the installation area to which the module belongs. The production adjustment information includes suggestions for adjusting the manufacturer's production order, suggestions for adjusting the on-site installation order, suggestions for adjusting the arrival batches, or suggestions for module splitting. The manufacturer's production order adjustment is based on the planned installation time from earliest to latest, the number of pre-installed modules from fewest to most, and the manufacturer's remaining processing cycle from shortest to longest to form a sorting value; the sorting value is written into the module prefabrication status package for the manufacturer to rearrange the processing order.

[0085] When the same prefabricated electromechanical module simultaneously meets two or more release criteria, the final release level is determined in the following order: prohibited prefabrication, complete prefabrication release, partial prefabrication release, workable but temporarily withheld from shipment, and priority production scheduling. Prohibited prefabrication has the highest priority; when a prohibited prefabrication condition exists, complete workable instructions, partial workable instructions, or shipment plans are no longer output. When no prohibited prefabrication condition exists, if the complete prefabrication release condition is met, complete prefabrication release is output; if the complete prefabrication release condition is not met but the partial prefabrication release condition is met, partial prefabrication release is output; if the module is workable but on-site receiving or temporary storage conditions restrict shipment, workable but temporarily withheld from shipment is output; if the time chain causes a prefabrication delay but the technical status is not negated, priority production scheduling is output.

[0086] After the tiered release results are generated, the release level, implementation window status, trigger conditions, prohibited processing scope, permitted processing scope, conditions for delayed shipment, review tasks, and planned instructions are written back to the module prefabrication status package. For modules with complete prefabrication release, the manufacturer's processing status is updated to "Complete Processing Allowed," the shipment status is updated to "Shipment Candidate," and the field installation status is updated to "Acceptable Candidate." For modules with partial prefabrication release, the manufacturer's processing status is updated to "Partial Processing Allowed," the shipment status remains "Not Shipped," and the interface and field adjustment sections remain "Pending Confirmation." For modules with processed but delayed shipment, the manufacturer's processing status is updated to "Processing Allowed," and the shipment status is updated to "Delayed Shipment." For modules with prohibited prefabrication, the manufacturer's processing status is updated to "Processing Prohibited," the shipment status is updated to "Shipment Prohibited," and the installation status is updated to "Pending Review." For modules with priority production scheduling, the manufacturer's processing status is updated to "Production Scheduling Adjustment Candidate," and the installation status is updated to "Installation Sequence Review Candidate."

[0087] While writing back the module prefabrication status packet, linked markers are applied to adjacent modules, pre-installation modules, and modules in the same transport batch. If a module is determined to be prohibited from prefabrication and has downstream connected modules, the downstream connected modules are added to the interface dependency review candidate. If a module is determined to be partially prefabricated and its interface is a connection reference for adjacent modules, the corresponding interface handshake unit of the adjacent modules is added to the pending interface confirmation. If a module is determined to be processable but temporarily deferred from shipment and belongs to the same transport batch as other modules, the modules in the same batch are added to the transport batch review candidate. If a module is determined to be prioritized for production and has a pre-installation module number, the pre-installation module is added to the installation order review candidate.

[0088] After the window linkage judgment is completed, a tiered release result list and a plan control list are output. The tiered release result list includes module code, design status, interface status, on-site constraint status, implementation window status, release level, permitted processing range, prohibited processing range, conditions for delayed shipment, review task type, and responsible unit. The plan control list includes complete processing instructions, partial processing instructions, delayed shipment instructions, prohibited processing instructions, manufacturer production scheduling adjustment information, logistics shipment control information, and on-site installation and acceptance information. The tiered release result list and plan control list serve as inputs for subsequent module status map establishment, change impact transmission, and closed-loop review judgment, and are used to continuously manage the status changes of modules between design, manufacturer processing, shipment, and on-site installation.

[0089] S4: Under the implementation window verification branch, based on the design freeze time, manufacturer processing time, transportation time, on-site receiving time and planned installation time, and combined with the prefabrication range, generate graded release results; based on the graded release results, establish a module status map; when changes in design, processing, on-site, transportation or installation plans are detected, determine the affected modules according to the module status map, send them back to the corresponding verification branch for review and update the graded release results.

[0090] Furthermore, the system reads the tiered release result list, plan control list, module prefabrication status package, project verification benchmark table, interface handshake result list, on-site counter-evidence result list, prefabrication scope correction list, and implementation window linkage judgment results to establish a module status graph. The module status graph uses electromechanical prefabrication modules as nodes and the interface connection relationships, installation sequence relationships, spatial adjacency relationships, transportation batch relationships, plan dependencies, and responsible unit relationships between modules as edges. This graph records the status associations and change impact paths between different electromechanical prefabrication modules. Each node corresponds to one electromechanical prefabrication module, and each edge corresponds to a traceable association. Node status and edge relationships are derived from data records already formed during the previous verification process; manual verbal confirmation is not used as the basis for status updates.

[0091] The node information in the module status graph includes module code, data center area, discipline, prefabrication boundary, interface status, on-site constraint status, implementation window status, release level, manufacturer processing status, factory status, on-site installation status, number of unclosed tasks, locked version number, and the most recent status update time. Interface status is derived from the interface handshake result list, on-site constraint status from the on-site counter-evidence result list, implementation window status from the implementation window linkage judgment result, and release level from the tiered release result list. Each status field is associated with its corresponding source file, source list number, and generation time, used to determine the status source that needs to be traced back when subsequent changes occur.

[0092] The edge relationships in the module state graph are established according to different association sources. Interface connection relationship edges are generated based on the interface handshake result list, recording the current module number, adjacent module number, interface number, interface type, interface handshake status, interface lock version number, and interface responsible unit; installation sequence relationship edges are generated based on the construction schedule and the preceding installation module number, recording the preceding module number, subsequent module number, installation area, planned installation time, and installation sequence number; spatial adjacency relationship edges are generated based on the electromechanical design model, construction detail drawings, and on-site verification results, recording the minimum distance between the outer contours of two modules, adjacent boundary type, and affected parts; transportation batch relationship edges are generated based on the logistics plan and transportation batch number, recording the module number in the same batch, transportation vehicle number, planned delivery time, transportation route, and on-site receiving time; responsible unit relationship edges are generated based on the responsible unit field in the module prefabrication status package, recording the design responsible unit, manufacturer responsible unit, construction responsible unit, and logistics responsible unit.

[0093] After the module status map is established, the release level of each module is written to the corresponding node. Release levels include complete prefabrication release, partial prefabrication release, processing permitted but delayed shipment, prefabrication prohibited, and priority production scheduling. For complete prefabrication release nodes, a complete processing permitted flag, a shipment candidate flag, and a field acceptance candidate flag are written to the map; for partial prefabrication release nodes, a partial processing permitted flag, an interface end pending confirmation flag, and a field adjustment section pending confirmation flag are written; for processing permitted but delayed shipment nodes, a processing permitted flag and a delayed shipment flag are written; for prohibited prefabrication nodes, a processing prohibited flag, a shipment prohibited flag, and a review task flag are written; for priority production scheduling nodes, a production scheduling adjustment candidate flag and an installation sequence review candidate flag are written. All of the above flags are synchronously written back to the module prefabrication status package, ensuring that the status map and the module status package are of the same version.

[0094] When any prefabricated electromechanical module undergoes design changes, manufacturer processing changes, on-site re-measurement changes, transportation condition changes, construction schedule changes, or installation plan changes, a change record is generated first. The change record includes the change number, change source, changed fields, values ​​before the change, values ​​after the change, change effective time, corresponding module code, corresponding drawing version, corresponding model version, and responsible unit. Change sources include design change orders, manufacturer processing modification orders, on-site re-measurement records, transportation route adjustment records, construction schedule adjustment records, and installation plan adjustment records. Change fields are not directly determined by textual descriptions but are instead categorized into interface fields, site fields, window fields, processing fields, or non-critical parameter fields according to a field classification table.

[0095] The field classification table is stored together with the project verification benchmark table. Interface fields include interface specifications, connection method, interface centerline, interface elevation, interface direction angle, interface number, adjacent module number, and allowable adjustment amount; site fields include equipment foundation location, reserved opening location, beam and column boundary, wall boundary, floor slab elevation, clear width of transportation channel, door opening size, handover status of installation work surface, occupancy status of installed components, and temporary stacking conditions; window fields include design freeze time, manufacturer's planned processing start time, manufacturer's planned processing completion time, planned delivery time, transportation cycle, on-site receiving time, planned installation time, and pre-installed module number; processing fields include manufacturer's processing drawing version, processing status, packaging dimensions, module weight, main section range, interface end range, on-site adjustment section range, and temporarily unfixed section range; non-critical parameter fields include material remarks, non-connection part identification, non-interface part surface treatment information, and record fields that do not participate in interface connection, on-site installation, and transportation hoisting judgment.

[0096] After classifying the changed fields, the system performs a change impact propagation judgment based on the module status graph. When a changed field is a non-critical parameter field, and it does not belong to interface, field, window, or processing fields, the current module is only marked as a single-module review state. In the single-module review state, the system only performs field consistency review on the module's pre-built status package, does not open interface handshake units of adjacent modules, and does not change the release level of adjacent modules. If the review passes, the status update time of the current module is updated to the review completion time, and the original release level is retained; if the review fails, the corresponding review task is rewritten based on the failed fields.

[0097] When the changed field belongs to an interface type field, the adjacent modules connected to the current module are found along the interface connection relationship edge in the module status graph, and the current module and the adjacent modules are jointly marked as interface review status. After the interface review status is formed, the double-sided interface lock status of the corresponding interface handshake unit is released, the interface handshake status is written to pending review, and the interface handshake lock judgment is called to recalculate the interface specification code, connection method code, interface centerline difference, interface elevation difference, and interface direction angle difference. After re-judgment, if the interface status is restored to double-sided interface lock, the interface lock version number is updated, and the interface review status of the current module and the adjacent module is turned off; if the interface status changes to adjustable interface retention, single-sided interface confirmation, interface pending confirmation, or interface conflict, the processing boundary control result is updated according to the corresponding status, and the release level candidate status of the relevant module is modified.

[0098] When the changed field belongs to the field-related field, the system searches for modules that are spatially adjacent to the current module along the spatial adjacency edges in the module status graph, and marks the current module and its spatially adjacent modules as being in the field-based counter-evidence verification status. After the field-based counter-evidence verification status is established, the retest objects corresponding to the changed field in the field retest object list are written to the pending retest or pending confirmation status, and the field-based counter-evidence judgment is called to recalculate the differences in basic position, opening position, boundary, elevation, remaining passage capacity of doorways, remaining passage capacity of transportation channels, and remaining temporary storage capacity. After reassessment, if the on-site constraint status is "acceptable on-site," the prefabrication range of the corresponding module is retained or restored; if the on-site constraint status is "acceptable on-site," the affected part is written into the processing range after on-site confirmation; if the on-site constraint status is "failed on-site verification," the affected module is written into the candidate for prohibiting complete prefabrication, and design review, interface re-handshake, module splitting, transportation route review, or installation sequence review tasks are generated; if the on-site constraint status is "on-site conditions not closed," the candidate for complete prefabrication release is closed, and only the candidate status for partial processing is retained.

[0099] When a changed field belongs to a window-type field, the associated modules are searched along the installation sequence and transportation batch relationships in the module status graph. The current module, the preceding installation module, the following installation module, and modules in the same transportation batch are marked as implementing window review status. After the implementation window review status is established, the time relationship between the design freeze time, the manufacturer's planned processing start time, the manufacturer's planned processing completion time, the planned delivery time, the transportation cycle, the on-site receiving time, and the planned installation time is recalculated. If the recalculation results in a window match, the release level of the corresponding module is retained or restored; if the recalculation results in a risk of premature prefabrication, the delay delivery order is updated; if the recalculation results in a risk of prefabrication lag, the priority scheduling mark and scheduling ranking value are updated; if the recalculation results in a window conflict, the corresponding module is added to the prohibited prefabrication candidate and a progress window coordination task is generated.

[0100] When a changed field is a processing-related field, first determine whether the processing-related field affects the already generated processing boundary control results. If the changed field is packaging size, module weight, main body segment range, interface end range, field adjustment segment range, or temporarily unfixed segment range, then simultaneously trigger field verification and implementation window verification. If the changed field is the manufacturer's processing drawing version or processing status, then verify the release level according to the processing status. When the manufacturer's processing status changes from unprocessed to fully processed, if the corresponding module still has an interface pending confirmation, interface conflict, field verification failure, or window conflict status, then write the module into the processing exception task. When the manufacturer's processing status changes from unprocessed to partially processed, if the processing range exceeds the main body segment, standard segment, or non-interface segment limited by the partial processing instruction, then the excess part is written into the processing boundary verification task.

[0101] When the same change record contains two or more types of fields from interface, field, and window categories, a joint review group is generated in the module status diagram. The joint review group includes the current module, modules associated with interface connections, modules associated with spatial adjacency, modules associated with installation sequence, and modules associated with transportation batches. The joint review group executes the review sequentially: interface handshake review, field verification review, and implementation window review. The result of the interface handshake review is used to update the processing boundary control results; the field verification review determines the prefabrication range based on the updated processing boundary control results; and the implementation window review determines the release level based on the updated prefabrication range. Before the joint review is completed, no module within the joint review group may be directly changed from a prohibited prefabrication candidate, partial prefabrication candidate, or temporarily suspended factory release status to a complete prefabrication release status.

[0102] During the impact propagation process, the scope of affected modules is determined layer by layer according to the edge relationships in the graph. The first layer consists of modules that have direct interface connections, spatial adjacencies, installation sequence relationships, or transportation batch relationships with the current module. The second layer consists of modules in the first layer whose interface connections, installation sequences, transportation batches, or on-site occupancy status have changed due to changes in release levels. If no changes have occurred in the interface status, on-site constraint status, implementation window status, or release level after review of the first-layer modules, the impact is not propagated to the second layer. If any of the above status changes occur after review of the first-layer modules, the impact is propagated only along the edge types that have changed, and not along the edge types that have not changed.

[0103] Each change's impact propagation generates an impact propagation record. This record includes the change number, starting module, affected modules, triggering edge type, triggering field, propagation level, review type, pre-review status, post-review status, and whether propagation continues. The impact propagation record is written into the edge relationship history of the module state graph for subsequent queries regarding the impact path of a change on module prefabrication, manufacturer processing, transportation, and on-site installation.

[0104] After the review is completed, a closed-loop review judgment is performed on the affected modules. The closed-loop review judgment includes task closure judgment, status consistency judgment, release level restoration judgment, and version consistency judgment. The task closure judgment is used to confirm whether all interface review tasks, field retesting tasks, window coordination tasks, processing boundary review tasks, and design review tasks corresponding to the current module are closed; when the number of unclosed tasks is 0, the task closure judgment is successful. The status consistency judgment is used to confirm whether the interface status, field constraint status, implementation window status, and release level in the module's prefabricated status package are consistent with the node records in the module's status graph; when the four types of status fields are consistent and the status update time is the same, the status consistency judgment is successful. The version consistency judgment is used to confirm that the design drawing version, manufacturer processing drawing version, field retesting record version, and release list version recorded in the module's prefabricated status package are consistent with the currently effective version; when each version number is the same as the currently effective version number, the version consistency judgment is successful.

[0105] When the task closure judgment, status consistency judgment, and version consistency judgment are all true, the release level is re-determined based on the reviewed interface status, on-site constraint status, and implementation window status. If the re-determined release level is complete prefabrication release, the complete processing, factory delivery, and installation acceptance status are synchronized with the manufacturer, logistics, and construction ends. If the re-determined release level is partial prefabrication release, the partial processing scope and prohibited processing scope are synchronized. If the re-determined release level is processing permitted but factory delivery is delayed, the processing permitted and factory delivery delayed status are synchronized. If the re-determined release level is prohibited prefabrication, the prohibited processing, prohibited factory delivery, and pending review status are synchronized. If the re-determined release level is priority production scheduling, the production scheduling adjustment information and installation sequence review candidate status are synchronized.

[0106] If any of the task closure, status consistency, or version consistency checks fails, the corresponding review process will not be closed, and the unclosed review status will be retained in the module's prefabricated status package. The unclosed review status record includes the reason for the unclosed status, the unclosed fields, the responsible unit, the associated task number, and the trigger condition for the next review. The trigger condition for the next review includes at least one of the following: missing field completion, task status closure, drawing version update, on-site re-measurement record update, manufacturer processing status update, logistics plan update, or construction plan update.

[0107] The module status graph is updated synchronously after each review. Updates include node status, edge relationship status, release level, review task status, lock version number, impact propagation records, and plan control instructions. If a module changes from prohibited prefabrication to partial prefabrication release or full prefabrication release, the prohibition propagation flag for downstream connected modules is removed, and the interface review status of downstream connected modules is recalculated. If a module changes from full prefabrication release to partial prefabrication release or prohibited prefabrication, affected modules are marked along interface connection relationships and installation sequence relationships, and the corresponding review is re-executed. If a module changes from being processable but temporarily deferred to full prefabrication release, the transport batch review candidate flag for modules in the same transport batch is simultaneously removed. If a module changes from priority scheduling to window matching, the manufacturer's production sorting value and the on-site installation sequence candidate status are updated.

[0108] After completing the change impact propagation and closed-loop verification, the module status map update results and closed-loop verification result list are output. The module status map update results include a module node list, interface connection edge list, spatially adjacent edge list, installation sequence edge list, transportation batch edge list, node status change records, edge relationship change records, and impact propagation records. The closed-loop verification result list includes module code, change number, verification type, release level before verification, release level after verification, number of unclosed tasks, version consistency results, status consistency results, responsible unit, and subsequent control instructions. Subsequent control instructions include complete processing recovery instructions, partial processing restriction instructions, temporary factory release maintenance instructions, processing prohibition instructions, interface re-handshake instructions, on-site retesting instructions, implementation window verification instructions, transportation batch adjustment instructions, and installation sequence adjustment instructions. These results are then written back to the module prefabrication status package and module status map, ensuring a traceable closed-loop record of the status changes of the electromechanical prefabrication modules during design, manufacturer processing, transportation to the site, and on-site installation.

[0109] Example 2, one embodiment of the present invention, provides a prefabrication verification method for data center electromechanical modules. In order to verify the beneficial effects of the present invention, scientific demonstration is carried out through economic benefit calculation and simulation experiments.

[0110] First, Area A of a newly built data center project was selected as the implementation target. This area includes a main server room, a UPS power distribution room, a chilled water main corridor, a comprehensive cable tray corridor, and several through-wall fire protection pipes and low-voltage cabling sections. Before implementation, the electromechanical design model, detailed construction drawings, manufacturer's fabrication drawings, equipment and material lists, on-site re-measurement records, transportation and hoisting plans, and construction schedules for this area were collected. The power distribution cabinet connection section, UPS busbar section, chilled water main section, cable tray bend section, precision air conditioning interface section, comprehensive support and hanger section, fire protection through-wall pipe section, and low-voltage cabling section were divided into 8 electromechanical prefabrication modules. A module prefabrication status package was established for each module, and the installation coordinates from the design end, the interface fabrication dimensions from the manufacturer, the foundation and opening re-measurement data from the site, the packaging dimensions and transportation routes from the logistics end, and the processing and installation time from the planning end were all uniformly bound to the same module index. Subsequently, benchmark data such as dimensional deviations, elevation deviations, interface direction deviations, and adjustable margins were extracted from project construction and acceptance documents, manufacturer processing documents, and equipment installation documents. These were then combined with on-site doorway dimensions, clear width of transport channels, rated lifting capacity of hoisting equipment, and temporary storage area area to form a project verification benchmark table. During implementation, interface handshake locking was first performed on modules with adjacent connections to determine whether adjacent interfaces could be completely locked, whether interface ends needed to be retained, whether they could be handled through reserved adjustment sections, or whether a rollback to the verification state was necessary. Next, on-site remeasurement data was mapped to processing boundary control results to determine whether on-site differences fell into the main body section, interface end, on-site adjustment section, transport path, or prohibited processing section. Finally, an implementation window chain was formed by combining design freeze time, manufacturer processing time, transport time, on-site receiving time, and planned installation time, outputting graded results such as complete prefabrication release, partial prefabrication release, processing-allowed delay, or prohibited prefabrication. To demonstrate the effectiveness of this method, a conventional prefabrication verification method was used as a comparison. The conventional method primarily relies on detailed drawings and BIM clash checks to uniformly and completely release modules, without linking the interface handshake status, on-site verification results, and implementation window status. Implementation data is shown in Table 1 below.

[0111]

[0112] As shown in Table 1, the conventional method provides complete release results for all eight modules. However, this method does not differentiate between interface deviations, on-site differences, and implementation window constraints. For example, the centerline deviation of the interface of the M02 UPS busbar section is 8mm, which is within the adjustable margin. However, the on-site difference corresponds to the interface end. If it is directly prefabricated, once the interface end is finally fixed in the factory, it will be difficult to eliminate the deviation on-site through adjustment sections. Therefore, the conventional method corresponds to an estimated rework time of 18 hours. However, with this solution, it is judged as partial prefabrication release, allowing only the main body section and non-interface section to be processed. The interface end is retained until it is confirmed and fixed on-site, reducing the estimated rework time to 4 hours. Although the interface deviation of the M05 precision air conditioner interface section itself does not cause interface conflict, the on-site difference corresponds to the main body section. This difference has already affected the installation position of the module body. Therefore, this solution directly outputs "prefabrication prohibited" and enters the design review, avoiding the 28-hour rework situation that would occur after the conventional method of complete release. The remaining transport clearance for the M06 integrated support section is -40mm, indicating that the combined dimensions of the module packaging and the transport vehicle exceed the net clearance dimensions on site. Conventional methods, relying solely on drawings and collision checks for release, would prevent the module from entering the installation area after leaving the factory. This solution identifies it as processable and postpones shipment, separating factory processing from logistics control, reducing the estimated rework time from 16 hours to 3 hours. Overall, the conventional method estimates a total rework time of 123 hours for 8 modules, while this solution estimates a total rework time of 21 hours, a reduction of approximately 82.9%. Conventional methods typically require repeated verification of all 8 modules for each anomaly, while this solution identifies affected modules through module status diagrams, interface relationships, on-site differences, and implementation windows, limiting the verification scope to 1 to 3 modules in most cases. The results demonstrate that this solution can not only identify problems, but also transform interface handshake results, on-site verification results, and implementation window results into executable processing boundaries and release levels, demonstrating stronger state linkage, boundary control, and closed-loop verification effects compared to conventional drawing verification and collision checks.

[0113] Example 3, one embodiment of the present invention, provides a data center electromechanical module prefabrication verification system, including a state modeling module, a branch verification module, and a graph closed-loop module.

[0114] The state modeling module is used to complete the object-oriented management of the electromechanical prefabrication module of the data center; the branch verification module is used to determine whether the electromechanical prefabrication module has the conditions for prefabrication; and the map closed-loop module is used to realize the prefabrication release and the review control after changes.

[0115] 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.

[0116] 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.

[0117] 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.

[0118] 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.

[0119] 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 prefabricating and verifying electromechanical modules for data centers, characterized in that, include: Acquire design data, manufacturer processing data, on-site re-measurement data, transportation and hoisting data, and construction progress data for the data center project; divide the electromechanical prefabrication modules and establish module prefabrication status packages; Based on project documents, on-site re-measurement data, transportation and hoisting plans, and construction schedules, a project verification benchmark table associated with the module prefabrication status package is generated. Based on the module prefabrication status package and project verification benchmark table, the electromechanical prefabrication module is prefabrication access branch judgment is performed, forming interface handshake locking branch, on-site counter-verification verification branch and implementation window verification branch; Under the interface handshake locking branch, the interface parameters of adjacent electromechanical prefabrication modules are locked, retained, adjustable, or rolled back to generate processing boundary control results. Under the on-site counter-evidence verification branch, the on-site retest data is mapped with the processing boundary control results to determine the affected parts and correct the prefabrication range of the electromechanical prefabrication module; Under the implementation window verification branch, based on the design freeze time, manufacturer processing time, transportation time, on-site receiving time, and planned installation time, and combined with the prefabrication range, a graded release result is generated; Based on the tiered release results, a module status map is established. When changes in design, processing, site, transportation, or installation plans are detected, the affected modules are determined according to the module status map, and the data is sent back to the corresponding verification branch for review and updating of the tiered release results.

2. The data center electromechanical module prefabrication verification method as described in claim 1, characterized in that: The establishment of the module prefabrication status package includes determining the module division boundary according to the installation area, prefabrication boundary and on-site assembly sequence of the electromechanical object, and binding the data generated by the same electromechanical prefabrication module at the design end, manufacturer end, on-site end and planning end to the same module index; When any data source is updated, the updated field is written to the corresponding module's pre-built state package, preserving the field values ​​and data source before and after the update.

3. The data center electromechanical module prefabrication verification method as described in claim 2, characterized in that: The project verification benchmark table associated with the module prefabrication status package includes benchmark data for dimensional deviations, interface deviations, installation deviations, and adjustable amounts extracted from project documents, manufacturer processing documents, equipment installation documents, and construction acceptance documents, and converts data from different sources into a unified unit; When there are multiple data sources for the same verification project, the value that limits the range of prefabrication should be selected as the adopted value. Based on the on-site re-measurement data, transportation and hoisting plan, and construction schedule, calculate the remaining transportation capacity, remaining hoisting weight, remaining temporary storage capacity, and implementation window time relationship, and write them into the project verification benchmark table.

4. The data center electromechanical module prefabrication verification method as described in claim 3, characterized in that: The prefabrication access branch determination for electromechanical prefabrication modules includes reading the connection relationship, spatial proximity relationship, transportation and hoisting relationship, and installation sequence relationship in the module prefabrication status package; When there are adjacent connected objects in the electromechanical prefabrication module, an interface handshake is triggered to lock the branch. When there is a re-measurement and verification relationship between the electromechanical prefabricated module and the on-site structure, passageway or installed component, the on-site counter-proof verification branch is triggered. When the electromechanical prefabricated modules are restricted by the sequence of transportation, hoisting, stacking, or pre-installation, the implementation window verification branch is triggered. When the same electromechanical prefabrication module triggers more than one branch, it is executed in the order of interface handshake, on-site verification and implementation window, and the results of each branch are continuously written back to the module prefabrication status packet.

5. The data center electromechanical module prefabrication verification method as described in claim 4, characterized in that: Under the interface handshake locking branch, the interface parameters of adjacent electromechanical prefabricated modules are locked, retained, adjustable, or rolled back. The processing boundary control results are generated by establishing an interface handshake unit between the current electromechanical prefabricated module and the adjacent electromechanical prefabricated module under the interface handshake locking branch, and comparing the specifications, connection methods, center lines, elevations, and orientation angles of the interfaces on both sides with the project verification benchmark table. When the interfaces on both sides meet the corresponding adoption values, the interface status is written to both sides and a complete processing boundary is generated. When only one side of the interface is confirmed, the confirmed side is written to the interface reserved boundary; When the interface deviation falls within the adjustable range, an adjustable machining boundary is generated; When the interface deviation exceeds the adjustable range or the interface specifications do not match, a prohibited processing boundary is generated, and the corresponding module is rolled back to the interface verification state.

6. The data center electromechanical module prefabrication verification method as described in claim 5, characterized in that: Under the on-site counter-evidence verification branch, the on-site re-measurement data is mapped with the processing boundary control results to determine the affected parts and correct the prefabrication range of the electromechanical prefabrication module. Under the on-site counter-evidence verification branch, the on-site re-measurement data is converted to the project coordinate system consistent with the electromechanical prefabrication module, and the re-measurement differences are mapped to the main body section, interface end, on-site adjustment section, temporarily unfixed section or prohibited processing section in the processing boundary control results. When the difference in the retest corresponds to the on-site adjustment section or the section that is not yet fixed, the prefabrication range of the main section is retained; When retesting the interface corresponding to the difference, the corresponding interface will be sent back to the interface handshake lock branch; When the retest results for the main body section, transportation entry path, hoisting path, or prohibited processing section, the corresponding electromechanical prefabrication module will be corrected to prohibit complete prefabrication.

7. The data center electromechanical module prefabrication verification method as described in claim 6, characterized in that: The process described in the implementation window verification branch involves generating tiered release results based on the design freeze time, manufacturer processing time, transportation time, on-site receiving time, and planned installation time, combined with the prefabrication range. This includes first forming an implementation window chain according to the design freeze time, manufacturer processing time, transportation time, on-site receiving time, and planned installation time, and then combining the implementation window chain with the interface handshake results, on-site verification results, and prefabrication range for judgment. When the interface is locked, on-site verification is passed, and the implementation window chain is established, a complete prefabrication release result is generated; when only the main body segment has the processing conditions, a partial prefabrication release result is generated. When the processing conditions are met but the on-site receiving conditions have not yet been met, a result indicating that processing is temporarily suspended from shipment is generated; when there is an interface conflict, the on-site counter-proof fails, or the implementation window chain is not established, a result prohibiting prefabrication is generated. When changes occur in the design, processing, site, transportation, or installation plans, the affected modules are sent back to the corresponding verification branch for reassessment based on the module status diagram.

8. A system employing the data center electromechanical module prefabrication verification method as described in any one of claims 1 to 7, characterized in that: Includes a state modeling module, a branch verification module, and a graph closure module; The state modeling module is used to complete the object-oriented management of the data center electromechanical prefabrication module; The branch verification module is used to determine whether the electromechanical prefabrication module has the conditions for prefabrication. The map closed-loop module is used to realize the pre-production release and the review control after changes.

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 electromechanical module prefabrication verification 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 electromechanical module prefabrication verification method according to any one of claims 1 to 7.

Images