A platform-based BIM twin and online collaboration-based industrialized construction whole-process management method, system, device and medium

Abstract

This invention discloses a platform-based BIM twin and online collaborative industrialized construction process management method, system, equipment, and medium, belonging to the field of digital construction engineering technology. It includes: receiving project plan information uploaded by a first participant, decomposing it into multiple construction task nodes according to a preset hierarchical relationship, with each construction task node having corresponding construction area information; receiving building information model data and component list data uploaded by a second participant, generating a component dataset; establishing the association relationship between components in the component dataset and construction task nodes; receiving a component acquisition request initiated by a third participant for a specified construction task node, determining the corresponding components and their required quantities based on the association relationship, and sending them to a fourth participant; receiving component processing information feedback from the fourth participant, and updating the component status. This invention automatically establishes association relationships based on construction area information, realizing automatic determination of component requirements and improving the efficiency of multi-party collaborative management.

Description

Technical Field

[0001] This invention relates to the field of digital technology in building engineering, specifically to a platform-based BIM twin and online collaborative industrialized construction process management method, system, equipment, and medium. Background Technology

[0002] Prefabricated buildings, due to their industrialized production and on-site assembly, have significant advantages in improving construction efficiency and ensuring project quality. However, prefabricated building projects involve multiple stages and participating entities, including design, production, transportation, and construction. Poor information flow and severe data silos between stages lead to low collaboration efficiency.

[0003] In existing construction project management methods, construction schedules are often disconnected from component production plans. Construction companies struggle to obtain the necessary components in a timely manner based on actual construction progress, and factories also cannot accurately grasp construction needs, easily leading to component backlogs or supply shortages. Furthermore, while BIM models contain rich component information, they have not been effectively linked to construction plans in practical applications, failing to achieve full lifecycle tracking of components from design and production to installation.

[0004] Meanwhile, the various parties involved typically communicate and coordinate using traditional methods such as telephone and email, resulting in delayed information transmission and untimely updates on component status, which affects construction progress and resource allocation efficiency. The lack of a unified digital management platform makes it difficult for project managers to monitor overall progress in real time and respond quickly to plan changes.

[0005] Therefore, a digital management method for building projects is needed that enables multi-party collaboration, dynamic association between plans and components, and real-time status tracking. Summary of the Invention

[0006] In view of the above-mentioned problems, the present invention provides a platform-based BIM twin and online collaborative industrial construction process management method, system, equipment and medium.

[0007] Therefore, the technical problem solved by this invention is: how to automatically establish the association between components in the component dataset and construction task nodes based on construction area information, and realize the automatic determination of component requirements for a specified construction task node based on the association, while supporting cross-party transmission of component processing information and automatic updating of component status.

[0008] To address the aforementioned technical problems, this invention provides the following technical solution: a platform-based BIM twin and online collaborative industrial construction process management method, comprising, Receive project plan information uploaded by the first participant, decompose the project plan information into multiple construction task nodes according to a preset hierarchical relationship, each construction task node has corresponding construction area information, and set the execution order relationship of the multiple construction task nodes; Receive building information model data and component list data uploaded by the second participant, and generate a component dataset based on the building information model data and the component list data. Each component in the component dataset includes a component identifier and a component status. Establish the association between the components in the component dataset and the construction task nodes; Receive a component acquisition request initiated by a third party for a specified construction task node, and determine the corresponding component and its required quantity from the component dataset according to the association relationship; The component identifier and required quantity of the corresponding component are sent to the fourth participating party; Receive component processing information from the fourth participant, and update the component status of the corresponding component in the component dataset according to the component identifier in the component processing information.

[0009] As a preferred embodiment of the platform-based BIM twin and online collaborative industrialized construction process management method described in this invention, the step of setting the execution order relationship of the multiple construction task nodes includes: Select a first construction task node and a second construction task node from the plurality of construction task nodes; Set the dependency relationship between the first construction task node and the second construction task node; Monitor the execution status of the second construction task node, and generate a start notification for the first construction task node in response to the second construction task node's execution status being updated to complete.

[0010] As a preferred embodiment of the platform-based BIM twin and online collaborative industrialized construction process management method described in this invention, the generation of the component dataset based on the building information model data and the component list data includes: Parse the building information model data to obtain the model attribute data for each component; Parse the component list data to obtain the list attribute data for each component; Match the model attribute data of the same component with the list attribute data; Based on the matching results, a unique component identifier is generated for each component, and the initial component state is set to form the component dataset.

[0011] The beneficial effects of this preferred technical solution are as follows: by matching the model attribute data and the list attribute data of the same component, the integration of BIM model information in the design phase and component list information in the production phase is achieved. Building Information Model (BIM) data contains design information such as the component's geometry, dimensions, and spatial location, while the component list data contains production information such as the component's number, production specifications, and processing parameters. Matching allows the design information and production information to be associated with the same component, solving the problem that the BIM model and component list are independent and cannot be correlated, thus enabling the component dataset to simultaneously contain complete information from both design and production dimensions.

[0012] As a preferred embodiment of the platform-based BIM twin and online collaborative industrialized construction process management method described in this invention, the construction area information includes a first area dimension and a second area dimension, the model attribute data includes component spatial location data, and the establishment of the association between components in the component dataset and the construction task nodes includes: Extract the component spatial location data for each component from the component dataset; Extract the first region dimension and the second region dimension from the construction task nodes; The spatial location data of the component is matched with the first region dimension and the second region dimension; For components and construction task nodes that are successfully matched in the region, establish the association between the components and the construction task nodes.

[0013] The beneficial effects of this preferred technical solution are as follows: By establishing the association between components and construction task nodes through an automatic matching mechanism based on construction area information, the association between components and construction task nodes can be established without manual determination of the construction task node corresponding to each component. The construction area information of the construction task node includes a first area dimension and a second area dimension, such as building identifiers and floor identifiers. The spatial location data of the component includes its building and floor location information. By matching the two areas, the construction task node to which the component belongs can be automatically identified, avoiding the process of manual searching and matching, and improving the efficiency and accuracy of association establishment.

[0014] As a preferred embodiment of the platform-based BIM twin and online collaborative industrial construction process management method described in this invention, the component status includes a first state, a second state, and a third state, and updating the component status of the corresponding component in the component dataset according to the component identifier in the component processing information includes: Extract the component identifier and the current stage identifier from the component processing information; The corresponding component is located in the component dataset based on the component identifier; The component status of the corresponding component is updated to the first state, the second state, or the third state according to the current stage identifier.

[0015] As a preferred embodiment of the platform-based BIM twin and online collaborative industrialized construction process management method described in this invention, the component processing information includes production stage processing information and transportation stage processing information, and the component processing information received from the fourth participant includes: Receive production stage processing information from the fourth participant, the production stage processing information including the component identifier and production progress data; The system receives transportation phase processing information from the fourth participant, which includes the component identifier and transportation status data.

[0016] As a preferred embodiment of the platform-based BIM twin and online collaborative industrialized construction process management method described in this invention, the preset hierarchical relationship includes multiple decomposition levels, and the decomposition of the project plan information into multiple construction task nodes according to the preset hierarchical relationship includes: The project plan information is decomposed level by level according to the multiple decomposition levels. Each decomposition breaks down the task of the previous level into multiple sub-tasks of the next level. When decomposed to the lowest level, the subtasks of the lowest level are taken as the construction task nodes.

[0017] This invention provides a platform-based BIM twin and online collaborative industrial construction process management system.

[0018] To address the aforementioned technical problems, this invention provides the following technical solution: a platform-based BIM twin and online collaborative industrialized construction process management system, comprising: The planning management module is used to receive project plan information uploaded by the first participant, decompose the project plan information into multiple construction task nodes according to a preset hierarchical relationship, each construction task node has corresponding construction area information, and set the execution order relationship of the multiple construction task nodes; The component data management module is used to receive building information model data and component list data uploaded by the second participant, and generate a component dataset based on the building information model data and the component list data. Each component in the component dataset includes a component identifier and a component status. The association processing module is used to establish the association relationship between the components in the component dataset and the construction task nodes; The demand processing module is used to receive a component acquisition request initiated by a third party for a specified construction task node, determine the corresponding component and its required quantity from the component dataset according to the association relationship, and send the component identifier and required quantity of the corresponding component to the fourth party. The status update module is used to receive component processing information fed back by the fourth participant, and update the component status of the corresponding component in the component dataset according to the component identifier in the component processing information.

[0019] The present invention provides a computer device, including a memory and a processor. The memory stores a computer program, and the processor executes the computer program to implement the steps of the platform-based BIM twin and online collaborative industrial construction process management method.

[0020] The present invention provides a computer-readable storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements the steps of a platform-based BIM twin and online collaborative industrialized construction process management method.

[0021] The beneficial effects of this invention are as follows: By parsing Building Information Modeling (BIM) data and component list data to generate a component dataset, this invention achieves the integration of BIM model information and component production information, solving the problem of their disconnect. By establishing a correlation, when a third party initiates a component acquisition request for a specified construction task node, the corresponding component and its required quantity can be automatically determined based on this correlation, eliminating the need for manual searching and statistics, and improving the accuracy of component requirement determination.

[0022] This invention connects the first, second, third, and fourth participants through a cloud platform, enabling cross-party data transfer. The component processing information fed back by the fourth participant automatically updates the component status of the corresponding component in the component data set, allowing all participants to monitor the component status in real time and avoiding the information lag problem of traditional communication methods. Attached Figure Description

[0023] To more clearly illustrate the technical solutions of the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying 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.

[0024] Figure 1 This is an overall flowchart of a platform-based BIM twin and online collaborative industrial construction process management method provided in one embodiment of the present invention. Detailed Implementation

[0025] To make the present invention more apparent and understandable, the 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, 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.

[0026] Example 1, referring to Figure 1 This is one embodiment of the present invention, which provides a platform-based BIM twin and online collaborative industrial construction process management method, including: Step S1: Receive project plan information uploaded by the first participant, decompose the project plan information into multiple construction task nodes according to a preset hierarchical relationship, each construction task node has corresponding construction area information, and set the execution order relationship of the multiple construction task nodes; Step S2: Receive the building information model data and component list data uploaded by the second participant, and generate a component dataset based on the building information model data and the component list data. Each component in the component dataset includes a component identifier and a component status. Step S3: Establish the association between the components in the component dataset and the construction task nodes; Step S4: Receive a component acquisition request initiated by a third party for a specified construction task node, and determine the corresponding components and their required quantities from the component dataset according to the association relationship; Step S5: Send the component identifier and required quantity of the corresponding component to the fourth participant; Step S6: Receive the component processing information fed back by the fourth participant, and update the component status of the corresponding component in the component dataset according to the component identifier in the component processing information.

[0027] In this embodiment, the first participant is the project owner or general contractor, responsible for formulating and uploading the overall project plan information; the second participant is the architectural design unit, responsible for providing building information model data and component list data; the third participant is the construction unit, responsible for on-site construction and initiating component acquisition requests; and the fourth participant is the prefabricated component manufacturer, responsible for component production, transportation, and feedback of component processing information.

[0028] The project planning information includes the overall project duration target, key milestones, and planned targets for each stage. In a specific example, the project planning information includes a total project duration of 18 months, the main structure capping date, the final acceptance date, and the planned start and end dates for each construction stage.

[0029] The preset hierarchical relationship includes multiple decomposition levels. In one specific example, the preset hierarchical relationship includes three decomposition levels: the first level is the stage task level, the second level is the professional task level, the third level is the process task level, and the process task at the lowest level is the construction task node. In another specific example, the preset hierarchical relationship includes two decomposition levels: the first level is the general contracting task level, the second level is the subcontracting task level, and the subcontracting task at the lowest level is the construction task node.

[0030] The construction task nodes are the executable task units obtained after decomposing the project plan to the lowest level. Each construction task node has corresponding construction area information, which is recorded in the construction task node data. The construction task node data also includes the task name, planned start time, planned end time, and responsible unit.

[0031] The construction area information includes a first area dimension and a second area dimension. In one specific example, the first area dimension is the building identifier, and the second area dimension is the floor identifier; for example, the construction area information for a certain construction task node is "Building 3, 2nd floor". In another specific example, the first area dimension is the construction section identifier, and the second area dimension is the axis range identifier.

[0032] The execution order relationship includes pre- and post-deployment relationships. These pre- and post-deployment relationships indicate that a certain construction task node can only begin after another construction task node has been completed. For example, if the first construction task node is "Construction of the main structure of the 3rd floor of Building 3," and the second construction task node is "Construction of the main structure of the 2nd floor of Building 3," the pre- and post-deployment relationship indicates that the first construction task node can only begin after the second construction task node has been completed. The start notification is a task reminder message generated for the first construction task node and sent to the responsible unit or person for that construction task node.

[0033] The Building Information Modeling (BIM) data is a 3D model file containing component geometry and attribute information. In a specific example, the BIM data is a Revit .rvt file or an IFC .ifc file. The component list data is a structured data file containing component production information. In a specific example, the component list data is an Excel .xlsx file or a CSV .csv file.

[0034] The model attribute data includes component design information parsed from building information model (BIM) data. In a specific example, the model attribute data includes component geometry, component dimensions, component 3D coordinates, component type, building to which the component belongs, and floor to which the component belongs. The bill of quantities attribute data includes component production information obtained from the component bill of quantities data. In a specific example, the bill of quantities attribute data includes component number, production specifications, processing parameters, and manufacturer information.

[0035] The component spatial location data refers to location-related information contained in the model attribute data. In a specific example, the component spatial location data includes the building identifier and the floor identifier to which the component belongs.

[0036] The component identifier is a code or mark used to uniquely identify the component. In one specific example, the component identifier is in the form of a QR code, containing information such as component number, building, floor, and component type. In another specific example, the component identifier is in the form of an RFID electronic tag.

[0037] The component dataset is a collection of data containing information about all components, stored in the cloud platform's database. Each component record includes a component identifier, component status, model attribute data, and inventory attribute data.

[0038] The association records are the correspondence records between components and construction task nodes, stored in the cloud platform's database. Each association record includes a component identifier and a construction task node identifier.

[0039] The component acquisition request is a component demand application initiated by a third party. In a specific example, the component acquisition request includes a specified construction task node identifier, a planned construction date, an estimated quantity required, and applicant information. The third party selects the construction task node, enters the planned construction date and the estimated quantity required through the cloud platform's client interface, and generates a component acquisition request upon submission.

[0040] The required quantity refers to the number of components needed for a specific construction task node. In one specific example, the required quantity is determined based on the estimated required quantity entered by the third party in the component acquisition request. In another specific example, the required quantity is automatically calculated based on the number of components associated with the construction task node and the workload of that task node.

[0041] The component status includes a first state, a second state, and a third state. In one specific example, the first state is in production, the second state is in transportation, and the third state is hoisted. In another specific example, the first state is not in production, the second state is in production, and the third state is accepted. The initial component status can be set to not in production.

[0042] The component processing information includes production stage processing information and transportation stage processing information. The production stage processing information includes component identification and production progress data, which includes the component's production completion rate and production node status. In a specific example, the production progress data includes the percentage of pouring completed, the status of rebar tying, and the curing progress. The transportation stage processing information includes component identification and transportation status data, which includes vehicle location information, transportation status identifiers, and estimated arrival time. In a specific example, the transportation status identifiers include "departed," "en route," and "arrived."

[0043] The current stage identifier is a marker that indicates the current production or transportation stage of the component. In a specific example, the current stage identifier includes "Production Stage," "Transportation Stage," and "Lifting Stage." The cloud platform determines whether the component status should be updated to the first, second, or third state based on the current stage identifier.

[0044] The system interface configuration information consists of pre-configured interface parameters for the fourth participant system within the cloud platform, including the interface address, interface protocol type, and authentication method. In a specific example, the fourth participant provides the system interface configuration information when registering to access the cloud platform, and the cloud platform stores this configuration information in the system configuration table.

[0045] Example 2, an embodiment of the present invention, provides a platform-based BIM twin and online collaborative industrialized construction process management method based on the previous embodiment, including: In step S1, the project plan information uploaded by the first participant is received, and the project plan information is decomposed into multiple construction task nodes according to a preset hierarchical relationship. Each construction task node has corresponding construction area information, and the execution order relationship of the multiple construction task nodes is set, including the following steps S1.1-S1.5: S1.1: The preset hierarchical relationship includes multiple decomposition levels. The project plan information is decomposed level by level according to the multiple decomposition levels. Each decomposition decomposes the task of the upper level into multiple sub-tasks of the lower level. S1.2: When decomposed to the last level, the sub-tasks of the last level are taken as the construction task nodes. S1.3: Select a first construction task node and a second construction task node from the plurality of construction task nodes; S1.4: Set the dependency relationship between the first construction task node and the second construction task node; S1.5: Monitor the execution status of the second construction task node, and in response to the execution status of the second construction task node being updated to completed, generate a start notification for the first construction task node.

[0046] In step S1.1, the cloud platform reads a pre-configured hierarchical relationship, which is stored in a configuration file and includes parameters for the number of levels and the name of each level. The cloud platform extracts the overall project goal from the project plan information as the initial task. The cloud platform decomposes the initial task according to the first-level decomposition rules, which are: the initial task is split into several first-level subtasks based on the task type, and each subtask inherits the project identifier of the initial task. For each subtask generated at the first level, the cloud platform repeats the above decomposition process, further splitting it into several second-level subtasks according to the second-level decomposition rules. This decomposition process continues until the final level defined by the pre-configured hierarchical relationship is reached.

[0047] In step S1.2, the cloud platform records the level depth value of the current task during each decomposition. The level depth value of the overall project goal is 0. The level depth value of each subtask generated after each decomposition is increased by 1 based on the level depth value of its parent task. The cloud platform reads the level quantity parameter from the preset level relationship. When the level depth value of the current task equals the level quantity parameter, it determines that the task is at the last level. The cloud platform marks all subtasks at the last level as construction task nodes, assigns a unique task identifier to each construction task node, and creates a construction task node record. This record includes the task identifier, task name, planned start time, planned end time, responsible unit identifier, and construction area information. The cloud platform extracts construction area information based on keywords in the task name or task description. For example, it extracts the building identifier "Building 3" and the floor identifier "2nd floor" from the task name "Construction of the Main Structure of Building 3, 2nd Floor," which are used as the first and second area dimensions, respectively.

[0048] In step S1.3, the cloud platform provides a construction task node selection interface, which displays the task name, planned time, and responsible unit for all construction task nodes. Users select two construction task nodes from the interface, and the cloud platform records the task identifiers of the two selected nodes. The construction task node that needs to be completed first is marked as the second construction task node, and the construction task node that needs to start later is marked as the first construction task node.

[0049] In step S1.4, the cloud platform creates a relationship record in the execution order relationship table of the database. This record includes the preceding task identifier, the subsequent task identifier, and the dependency type. The cloud platform writes the task identifier of the second construction task node into the preceding task identifier, writes the task identifier of the first construction task node into the subsequent task identifier, and sets the dependency type to start after completion.

[0050] In step S1.5, the cloud platform queries the execution status of all construction task nodes in the database through a periodic monitoring mechanism. Execution statuses include not started, in progress, and completed. The cloud platform identifies construction task nodes whose execution status has changed by comparing the current query result with the previous query result. When a construction task node's execution status changes from in progress to completed, the cloud platform uses the task identifier of that construction task node as a query condition, searches the execution order relationship table for all records where the preceding task identifier is equal to that task identifier, extracts the subsequent task identifier from the query results, and obtains the first construction task node that needs to be started. The cloud platform generates a start notification message, the message content of which includes the task name, planned start time, and construction area information of the first construction task node. The cloud platform sends the start notification to the contact person of the responsible unit of the first construction task node through a message push interface, including in-system messages, SMS, email, and push notifications from third-party collaboration tools.

[0051] In step S2, a component dataset is generated based on the building information model data and the component list data, including the following steps S2.1-S2.4: S2.1: Parse the building information model data to obtain the model attribute data of each component; S2.2: Parse the component list data to obtain the list attribute data for each component; S2.3: Match the model attribute data of the same component with the list attribute data; S2.4: Generate a unique component identifier for each component based on the matching results, and set the initial component state to form the component dataset.

[0052] In step S2.1, after receiving the Building Information Model (BIM) data file uploaded by the second participant, the cloud platform identifies the file format. For Revit format files, the cloud platform calls the BIM model parsing interface to open the file, traverses the component objects in the model, and reads the attribute parameters of each component object. For IFC format files, the cloud platform calls the IFC standard parsing interface to open the file, traverses the component entities in the model, and reads the attribute information of each component entity. The extracted model attribute data includes component name, component type, component size specifications, building to which the component belongs, floor to which the component belongs, and component 3D coordinates. The cloud platform stores the extracted model attribute data in a temporary data table, with each record corresponding to one component.

[0053] In step S2.2, after receiving the component list data file uploaded by the second participant, the cloud platform identifies the file format. For tabular files, the cloud platform calls the tabular data parsing interface to open the file, reads the data rows in the table, and parses the field values ​​according to the predefined column order. The fields include component number, component name, component type, production specifications, processing parameters, and manufacturer. For text files, the cloud platform reads the text content line by line, splits each line of text with a delimiter, and parses the field values ​​according to the column order. The cloud platform stores the read list attribute data in a temporary data table, with each record corresponding to one component.

[0054] In step S2.3, the cloud platform performs a matching operation on the temporary table of model attribute data and the temporary table of list attribute data. The matching rule is as follows: For each record in the temporary table of model attribute data, the cloud platform extracts its component name and component type, and queries the temporary table of list attribute data for records where both the component name and component type are equal. A string matching method is used for comparison. When the component name of the model attribute data record is the same as the component name of the list attribute data record, and the component type of the model attribute data record is the same as the component type of the list attribute data record, a successful match is determined. If a unique matching record is found, the cloud platform creates a matching relationship record. If multiple records are found, the cloud platform further compares the size specifications and selects the record with the smallest size specification difference as the matching result. If no record is found, the cloud platform marks the model attribute data record as unmatched.

[0055] In step S2.4, the cloud platform iterates through all matching relationship records. For each matching relationship record, the cloud platform generates a unique component identifier and merges the component identifier, model attribute data, and list attribute data to create a component record. The component record includes the component identifier, component name, component type, component size specifications, building to which the component belongs, floor to which the component belongs, component number, production specifications, processing parameters, and component status. The cloud platform sets the initial value of the component status to "not in production." The cloud platform inserts all component records into the component dataset table, completing the generation of the component dataset. For model attribute data records marked as "not matched," the cloud platform either does not generate a component record or generates a component record containing only model attribute data and marks it as "pending completion."

[0056] It should be noted that the construction area information includes a first area dimension and a second area dimension, and the model attribute data includes component spatial location data; In step S3, the association between the components in the component dataset and the construction task nodes is established, including the following steps S3.1-S3.4: S3.1: Extract the spatial location data of each component from the component dataset; S3.2: Extract the first region dimension and the second region dimension from the construction task node; S3.3: Perform region matching between the spatial location data of the component and the first region dimension and the second region dimension; S3.4: For components and construction task nodes that are successfully matched in the region, establish the association between the components and the construction task nodes.

[0057] In step S3.1, the cloud platform queries the component dataset table, reads the building to which the component belongs and the floor to which the component belongs for each component record, and uses the values ​​of these two fields as the component's spatial location data.

[0058] In step S3.2, the cloud platform queries the construction task node table, reads the construction area information of each construction task node record, and extracts the values ​​of the first area dimension and the second area dimension from the construction area information.

[0059] In step S3.3, the cloud platform performs a region matching operation on the spatial location data of components and the regional dimensions of construction task nodes. The region matching rule is as follows: For each component, the cloud platform extracts the building and floor to which the component belongs, and queries the construction task nodes for which the first regional dimension equals the building to which the component belongs and the second regional dimension equals the floor to which the component belongs. A string matching method is used for comparison. When the building to which the component belongs is the same as the first regional dimension of the construction task node, and the floor to which the component belongs is the same as the second regional dimension of the construction task node, the region matching is considered successful. The cloud platform records all successfully matched component identifiers and task identifier pairs.

[0060] In step S3.4, the cloud platform creates an association record in the association table of the database for each successfully matched component and construction task node. This record includes the component identifier and the construction task node identifier. For components that fail to match in a region, the cloud platform does not create an association record.

[0061] In step S4, a component acquisition request for a specified construction task node initiated by a third party is received, and the corresponding component and its required quantity are determined from the component dataset according to the association relationship.

[0062] In step S4, the cloud platform provides a component acquisition request interface, which displays a list of construction task nodes accessible to the third party. The third party selects a construction task node as the designated construction task node through this interface, and the cloud platform records its task identifier. The third party enters the planned construction date and the estimated quantity required, or selects the automatic calculation option. After the third party submits, the cloud platform generates a component acquisition request record, which includes the designated construction task node identifier, the planned construction date, the method for determining the required quantity, the applicant identifier, and the application time.

[0063] The cloud platform, based on component acquisition request records and using a specified construction task node identifier as the query condition, searches the association table for all records where the construction task node identifier equals that identifier. From the query results, it extracts the component identifiers to obtain a list of all component identifiers associated with that construction task node. Then, using this list of component identifiers as the query condition, the cloud platform searches the component dataset table for all records where the component identifier is in that list, obtaining complete information about the corresponding component.

[0064] The cloud platform processes the demand quantity based on the method used to determine it. If the demand quantity is determined manually, the cloud platform uses the estimated demand quantity input by the third party as the demand quantity. If the demand quantity is determined automatically, the cloud platform groups the corresponding component list by component type and counts the quantity, using the counted quantity for each component type as the demand quantity for that type of component. The cloud platform stores the corresponding component list and the corresponding demand quantity in the component demand result table.

[0065] In step S5, the component identifier and required quantity of the corresponding component are sent to the fourth participant.

[0066] In step S5, the cloud platform reads the component identifiers and required quantities of all corresponding components from the component requirement result table, generating component requirement order data. This order data includes the order number, the specified construction task node name, the planned construction date, the applicant information, and a detailed list of components, which includes the component identifier, component name, component type, and required quantity.

[0067] The cloud platform queries the system interface configuration information of the fourth participant, which includes the interface address, interface protocol type, and authentication method. Based on the interface protocol type, the cloud platform selects the sending method and sends the component requirement order data to the fourth participant's system via the network communication interface. The cloud platform records the sending result, including the sending time, sending status, and the response information returned by the fourth participant's system.

[0068] It should be noted that the component states include a first state, a second state, and a third state; In step S6, the component processing information fed back by the fourth participant is received, and the component status of the corresponding component in the component dataset is updated according to the component identifier in the component processing information, including the following steps S6.1-S6.5: S6.1: Receive production stage processing information fed back by the fourth participant, the production stage processing information including the component identifier and production progress data; S6.2: Receive the transportation stage processing information fed back by the fourth participant, the transportation stage processing information including the component identifier and transportation status data. S6.3: Extract the component identifier and the current stage identifier from the component processing information; S6.4: Locate the corresponding component in the component dataset according to the component identifier; S6.5: Update the component status of the corresponding component to the first status, the second status, or the third status according to the current stage identifier.

[0069] In step S6.1, the cloud platform provides a data receiving interface for the fourth participant to call. During component production, the fourth participant's production management system sends production stage processing information through this interface. This information includes the component identifier and production progress data. The production progress data includes the production node name and completion status. After receiving the data, the cloud platform records the data source identifier as production stage processing information and stores the component identifier and production progress data in the component processing information buffer table.

[0070] In step S6.2, the cloud platform provides a data receiving interface for the fourth participant to call. During the component transportation process, the fourth participant's logistics management system sends transportation stage processing information through this interface. The information includes component identification and transportation status data. The transportation status data includes transportation status identification, vehicle location information, and estimated arrival time. After receiving the data, the cloud platform records the data source identification as transportation stage processing information and stores the component identification and transportation status data in the component processing information buffer table.

[0071] In step S6.3, the cloud platform periodically queries the component processing information buffer table for unprocessed records. For each record, the cloud platform reads the component identifier and the data source identifier. The cloud platform determines the current stage identifier based on the data source identifier. If the data source identifier indicates production stage processing information, the current stage identifier is production stage; if the data source identifier indicates transportation stage processing information, the current stage identifier is transportation stage. The cloud platform stores the component identifier and the current stage identifier in a temporary variable.

[0072] In step S6.4, the cloud platform uses the component identifier as the query condition to query the record in the component dataset table where the component identifier is equal to the identifier, and obtains the primary key value of the record as the location identifier of the corresponding component.

[0073] In step S6.5, the cloud platform determines the target component status based on the current stage identifier and predefined stage-state mapping rules. The mapping rules are as follows: when the current stage identifier is the production stage, the target component status is the first state; when the current stage identifier is the transportation stage, the target component status is the second state; and when the current stage identifier is the hoisting stage, the target component status is the third state. The cloud platform performs a database update operation, using the primary key value of the corresponding component as the update condition, and updates the component status of the record in the component dataset table to the target component status. The cloud platform marks the corresponding record in the component processing information buffer table as processed.

[0074] Example 3, an embodiment of the present invention, provides a platform-based BIM twin and online collaborative industrial construction process management method based on the previous embodiment, including: In this embodiment, the preset hierarchical relationship adopts two decomposed levels: the first level is the general contracting task level, and the second level is the subcontracting task level. The first area dimension of the construction area information is the construction section identifier, and the second area dimension is the axis range identifier. The component identifier adopts the form of RFID electronic tag. The component status includes non-production status, production status, and acceptance status.

[0075] In step S1.1, the cloud platform reads a pre-configured hierarchical relationship with a level parameter of 2. The first level is named "General Contracting Task," and the second level is named "Subcontracting Task." The cloud platform extracts the overall project objective from the project plan information as the initial task, with a hierarchical depth of 0. The cloud platform decomposes the initial task according to the decomposition rules of the first level, breaking it down into several general contracting tasks based on the scope of contracting. In a specific application, the overall project objective "Prefabricated Housing Construction Project" is broken down into civil engineering general contracting tasks, mechanical and electrical general contracting tasks, and decoration general contracting tasks according to the scope of contracting, with a hierarchical depth of 1 for these general contracting tasks.

[0076] The cloud platform further decomposes each general contracting task according to the second-level decomposition rules, breaking it down into several subcontracting tasks based on the construction area or project content. In a specific application, the civil engineering general contracting task is divided into subcontracting tasks for section A (main structure), section B (main structure), and section C (main structure), with a level depth of 2 for these subcontracting tasks.

[0077] In step S1.2, when the current task's level depth value equals the level quantity parameter 2, it is determined that the task is at the last level. The cloud platform marks all subcontracted tasks at the last level as construction task nodes, assigns a unique task identifier to each construction task node, and creates a construction task node record. The cloud platform configures construction area information for each construction task node. The first area dimension of this construction area information is the construction section identifier, and the second area dimension is the axis range identifier.

[0078] In a specific application, the construction section identifier is used to identify the construction sections divided into projects, such as section A, section B, and section C. The axis range identifier is used to identify the axis range within each construction section, using start and end axis numbers, such as "axis 1 to axis 5". The construction area information for a certain construction task node "section A main structure subcontracting task" is configured with the construction section identifier "section A" and the axis range identifier "axis 1 to axis 5".

[0079] The cloud platform extracts construction area information based on keywords in the task name or task description. In a specific application, the construction section identifier "Section A" and the axis range identifier "Axis 1 to 5" are extracted from the task name "Section A Main Structure Subcontracting Task (Axis 1 to 5)" and used as the first and second area dimensions, respectively.

[0080] In step S2.1, when the cloud platform parses the building information model (BIM) data, the extracted model attribute data includes the construction section to which the component belongs and the axis position to which the component belongs. The cloud platform reads the design position coordinates of each component from the BIM data and determines the construction section identifier to which the component belongs based on the project's construction section division scheme. The construction section division scheme is pre-stored in the cloud platform and contains the spatial range coordinates of each construction section. The cloud platform determines whether the component's design position coordinates fall within the spatial range of a certain construction section; if so, it identifies that construction section as the construction section to which the component belongs.

[0081] The cloud platform determines the axial position of a component based on its design coordinates. Building Information Modeling (BIM) data contains building grid information; the cloud platform reads the component's design coordinates within the grid to determine which axis (or between which axes) the component is located on. In a specific application, if a precast beam component is designed to be located at axis 3 of the building grid, the cloud platform will mark the component's axial position as "axis 3".

[0082] In step S2.4, the cloud platform generates a unique component identifier for each component using an RFID electronic tag. The cloud platform generates data containing the component number, its construction section, its axis location, and component type, and writes this data into the RFID electronic tag's data storage area. After component production is complete, the fourth participating party affixes the RFID electronic tag to the component surface or embeds it inside the component. The cloud platform sets the initial value of the component's status to the unproduced state.

[0083] In step S3.1, the cloud platform queries the component dataset table, reads the construction section to which the component belongs and the axis position to which the component belongs for each component record, and uses the values ​​of these two fields as the component spatial location data.

[0084] In step S3.2, the cloud platform queries the construction task node table, reads the construction area information of each construction task node record, and extracts the construction section identifier and axis range identifier from the construction area information.

[0085] In step S3.3, the cloud platform performs a region matching operation on the spatial location data of components and the regional dimensions of construction task nodes. The region matching rule is as follows: for each component, the cloud platform extracts the construction segment to which the component belongs and the axis position to which the component belongs, and queries the construction task nodes whose construction segment identifier is equal to the construction segment to which the component belongs.

[0086] For construction task nodes whose construction section identifiers match successfully, the cloud platform further determines whether the component's axis position falls within the range defined by the axis range identifier of the construction task node. The cloud platform parses the axis range identifier and extracts the start and end axis numbers. In a specific application, the start axis number for the axis range identifier "Axis 1 to Axis 5" is 1, and the end axis number is 5. The cloud platform parses the component's axis position and extracts the axis number. If the axis number of the component's axis position is between the start and end axis numbers (including the boundary), then the component's axis position is determined to fall within that axis range.

[0087] When the construction segment to which a component belongs has the same identifier as the construction segment of a construction task node, and the axis position of the component falls within the range defined by the axis range identifier of the construction task node, the region is considered to be successfully matched. The cloud platform records all successfully matched component identifiers and task identifier pairs.

[0088] In step S3.4, the cloud platform creates an association record in the association table of the database for each successfully matched component and construction task node. This record contains the component identifier and the construction task node identifier.

[0089] In step S4, when the cloud platform determines the required quantity using automatic calculation, it groups the corresponding component list by component type and counts the quantity, using the counted quantity for each component type as the required quantity for that type of component. In this embodiment, since the construction task node is a subcontracted task, the number of components associated with it is usually large, covering a large construction area. In a specific application, a certain construction task node "Section A Main Structure Subcontracted Task" is associated with all prefabricated components within the range of axes 1 to 5 of Section A, including 50 prefabricated beams, 30 prefabricated columns, and 200 prefabricated slabs, with automatically calculated required quantities of 50, 30, and 200 respectively.

[0090] In step S6.1, the fourth participant sends production stage processing information to the cloud platform through the production management system during the component production process. The production progress data includes the production node names and completion statuses. The production node names include rebar tying, concrete pouring, vibration, and curing. When the completion status of all production nodes in the production progress data returned by the fourth participant is "completed," the cloud platform determines in step S6.3 that the current stage is identified as the production completion stage. In step S6.5, based on the current stage being identified as the production completion stage, the cloud platform updates the component status from "unproduced" to "produced."

[0091] In step S6.2, the fourth participant sends transportation stage processing information to the cloud platform through the logistics management system during component transportation. The transportation status data includes transportation status identifiers, which include "departed," "in transit," and "arrived." When the cloud platform receives transportation stage processing information with a transportation status identifier of "arrived," the cloud platform does not directly update the component status but waits for acceptance confirmation from the third participant.

[0092] In this embodiment, since the construction task node is at the subcontracting level, the third participant is the subcontractor, who is responsible for organizing the acceptance after the components arrive at the construction site. The third participant submits acceptance confirmation information through the cloud platform's client interface. The acceptance confirmation information includes the component identifier, acceptance status, acceptance time, and acceptance personnel. The acceptance personnel are the quality manager of the subcontractor. If the acceptance status is qualified, the cloud platform determines in step S6.3 that the current stage is marked as the acceptance completion stage, and in step S6.5, updates the component status from the "produced" state to the "accepted" state based on the current stage being marked as the acceptance completion stage. If the acceptance status is unqualified, the cloud platform does not update the component status, but generates a quality problem record and pushes it to the fourth participant, while also copying it to the first participant and the general contractor.

[0093] In this embodiment, the method further includes an on-site inspection function based on RFID electronic tags. A third party uses a mobile terminal equipped with RFID reading capabilities at the construction site to scan the RFID electronic tags on the components. The mobile terminal reads the component identifier from the RFID electronic tag and uploads the component identifier to the cloud platform via the network, generating a query request. Upon receiving the query request, the cloud platform retrieves detailed information about the component from the component dataset based on the component identifier, including the component name, component type, component dimensions, the construction section to which the component belongs, the component's axial position, and the component's status. The cloud platform also extracts the component's 3D model data and design location coordinates from the building information model data.

[0094] The cloud platform returns detailed information about the component, 3D model data, and design location coordinates to the mobile terminal. The mobile terminal displays detailed information about the component on its screen, including the construction section and axis position to which the component belongs, enabling third-party participants to quickly confirm which construction section and axis position the component should be installed in. The mobile terminal displays 3D model drawings of the component, marking its design position in the overall building structure and showing its specific location in the grid.

[0095] In this embodiment, the method further includes an automatic component processing information collection process based on IoT devices. In step S6.1, the fourth participant deploys RFID readers at key production nodes on the production line. Key production nodes include rebar binding completion points, concrete pouring completion points, vibration completion points, and curing completion points. When a component passes a key production node, the RFID reader automatically reads the RFID electronic tag on the component to obtain the component identification, records the current time and node location information, and sends it to the cloud platform via the network communication module. After receiving the data uploaded by the RFID reader, the cloud platform determines the current stage identifier based on the node location information. The cloud platform pre-stores the mapping relationship between node location information and production node names, determines the currently completed production node of the component based on the mapping relationship, and records the completion status of the corresponding production node as "completed" in the component's production progress data.

[0096] In step S6.2, the fourth participant installs a GPS positioning device on the transport vehicle, which collects the vehicle's location coordinates in real time. The fourth participant associates the transport vehicle with the loaded components, and the association information includes the vehicle identifier and a list of component identifiers loaded on the vehicle. After collecting the vehicle's location, the GPS positioning device sends the vehicle identifier, location coordinates, and timestamp to the cloud platform via a network communication module.

[0097] After receiving data uploaded by the GPS positioning device, the cloud platform queries the list of component identifiers loaded on the vehicle based on the vehicle's identifier. The cloud platform reads the construction area information of the components loaded on the vehicle to obtain the construction section identifier to which these components belong. The cloud platform queries the construction site location based on the construction section identifier, which is determined by the geographic coordinates corresponding to the construction section identifier. The cloud platform pre-stores the geographic coordinate range of each construction section. The cloud platform calculates the distance between the vehicle's current location and the construction site location. When the cloud platform detects that the distance between the vehicle's location and the construction site location meets the arrival determination criteria, the cloud platform sets the transportation status identifier to "arrived" and records the arrival time in the component's transportation status data.

[0098] In this embodiment, the method further includes a plan change processing procedure. The cloud platform receives a plan change application submitted by the first participant. The plan change application includes the changed construction task node identifier and the changed content, including changes to the task name, planned start time, planned end time, construction area information, and responsible unit.

[0099] In this embodiment, since the construction task node is at the subcontracting task level, the responsible unit is the subcontractor. When the construction area information changes, it may involve changes to the construction section identifier or axis range identifier. In a specific application, the original axis range identifier of a certain construction task node "Section A Main Structure Subcontracting Task" was "Axis 1 to 5". Due to the adjustment of the construction organization, it was changed to "Axis 1 to 8", thus expanding the construction scope.

[0100] The cloud platform sends the change request to the approval process, which includes multiple approval nodes, each approved by designated approvers. In this embodiment, the approvers include the project manager of the first participating party and the planning manager of the general contractor. Approvers view the detailed information of the change request through the cloud platform's approval interface and choose to approve or reject. If all approvers at all approval nodes select "approve," the change request is approved.

[0101] Upon approval of the change request, the cloud platform updates the construction task node records based on the changes. If the construction area information changes, the cloud platform triggers a recalculation of the association relationships. Following the association establishment method in step S3, the cloud platform re-executes the area matching operation using the changed construction area information to identify newly associated components and de-associated components. The cloud platform creates newly associated records and deletes de-associated records in the association relationship table.

[0102] The cloud platform queries other construction task nodes that have dependencies on the modified construction task node based on the execution order, and generates a change notification message. The message content includes the name of the modified construction task node, the content of the change, the names of other affected construction task nodes, and the changes in the relationships. The cloud platform sends the change notification to the responsible unit, second participant, third participant, and fourth participant of the affected construction task node through a message push interface.

[0103] In this embodiment, the cloud platform includes a web server, an application server, and a database server. The web server receives client access requests from various participants and provides a user interface. When the first, second, and third participants access the cloud platform through a browser or mobile application, the web server receives the access request and returns the corresponding interface page. The web server also receives data submitted by each participant through the client interface, including project plan information, building information model data, component list data, component acquisition requests, and acceptance confirmation information.

[0104] The application server is used to execute the data processing logic of steps S1 to S6 above, including project plan decomposition, building information model data parsing, component list data parsing, component dataset generation, relationship establishment, component requirement determination, and component status updating. The application server is also responsible for executing scheduled monitoring tasks, generating notification messages, and calling message push interfaces. The application server reads data from the database server, processes it, and writes the processing results back to the database server.

[0105] The database server stores construction task node records, component datasets, relationship records, execution order records, component acquisition request records, component processing information records, and system configuration information. It also stores auxiliary information such as construction section division schemes, axis range definitions, and construction site geographic coordinates. The database server employs a relational database management system, providing persistent data storage, query, and update functions.

[0106] The cloud platform also includes an object storage server and an authentication server. The object storage server stores building information model (BIM) data files, component list data files, and 3D model data files. When a second participant uploads a BIM data file, the web server receives the file upload request, stores the file in the object storage server, and obtains the file's storage path. The application server then reads the file content from the object storage server based on the storage path and performs parsing and processing.

[0107] The authentication server is used to authenticate the identities of each participant. Each participant needs to authenticate through the authentication server when accessing the cloud platform. The authentication server uses a domain account system, and each participant logs in using a username and password. The authentication server verifies the correctness of the username and password, and generates an access token upon successful verification, returning it to the client. The client carries this access token when subsequently accessing the cloud platform, and the application server uses the access token to identify the current user's identity and permissions.

[0108] The cloud platform also integrates third-party collaboration tool message push interfaces. When generating startup notifications and change notifications, the application server calls the third-party collaboration tool message push interface to push the message to the collaboration tools used by each participant. In a specific example, the cloud platform integrates the Lark API interface, pushing messages to the Lark application via the Lark API, enabling each participant to receive real-time notification messages in Lark.

[0109] Example 4 is an embodiment of the present invention, which provides a platform-based BIM twin and online collaborative industrialized construction process management system, including: The planning management module is used to receive project plan information uploaded by the first participant, decompose the project plan information into multiple construction task nodes according to a preset hierarchical relationship, each construction task node has corresponding construction area information, and set the execution order relationship of the multiple construction task nodes; The component data management module is used to receive building information model data and component list data uploaded by the second participant, and generate a component dataset based on the building information model data and the component list data. Each component in the component dataset includes a component identifier and a component status. The association processing module is used to establish the association relationship between the components in the component dataset and the construction task nodes; The demand processing module is used to receive a component acquisition request initiated by a third party for a specified construction task node, determine the corresponding component and its required quantity from the component dataset according to the association relationship, and send the component identifier and required quantity of the corresponding component to the fourth party. The status update module is used to receive component processing information fed back by the fourth participant, and update the component status of the corresponding component in the component dataset according to the component identifier in the component processing information.

[0110] This embodiment also provides an electronic device applicable to a platform-based BIM twin and online collaborative industrial construction process management method, comprising: a memory and a processor; the memory is used to store computer-executable instructions, and the processor is used to execute the computer-executable instructions to realize the platform-based BIM twin and online collaborative industrial construction process management method proposed in the above embodiment.

[0111] This embodiment also provides a storage medium storing a computer program that, when executed by a processor, implements a platform-based BIM twin and online collaborative industrial construction process management method as proposed in the above embodiments.

[0112] The storage medium proposed in this embodiment belongs to the same inventive concept as the method for implementing a platform-based BIM twin and online collaborative industrial construction process management proposed in the above embodiments. Technical details not described in detail in this embodiment can be found in the above embodiments, and this embodiment has the same beneficial effects as the above embodiments.

[0113] Based on the above description of the implementation methods, those skilled in the art can clearly understand that the present invention can be implemented using software and necessary general-purpose hardware, and of course, it can also be implemented using hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a computer-readable storage medium, such as a computer floppy disk, read-only memory (ROM), random access memory (RAM), flash memory, hard disk, or optical disk, etc., including several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the methods of the various embodiments of the present invention.

[0114] It should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention and not 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 platform-based BIM twin and online collaborative industrial construction process management method, characterized in that, include: Receive project plan information uploaded by the first participant, decompose the project plan information into multiple construction task nodes according to a preset hierarchical relationship, each construction task node has corresponding construction area information, and set the execution order relationship of the multiple construction task nodes; Receive building information model data and component list data uploaded by the second participant, and generate a component dataset based on the building information model data and the component list data. Each component in the component dataset includes a component identifier and a component status. Establish the association between the components in the component dataset and the construction task nodes; Receive a component acquisition request initiated by a third party for a specified construction task node, and determine the corresponding component and its required quantity from the component dataset according to the association relationship; The component identifier and required quantity of the corresponding component are sent to the fourth participating party; Receive component processing information from the fourth participant, and update the component status of the corresponding component in the component dataset according to the component identifier in the component processing information.

2. The method for managing the entire industrial construction process based on platform-based BIM twins and online collaboration as described in claim 1, characterized in that, The execution order relationship of the multiple construction task nodes is set as follows: Select a first construction task node and a second construction task node from the plurality of construction task nodes; Set the dependency relationship between the first construction task node and the second construction task node; Monitor the execution status of the second construction task node, and generate a start notification for the first construction task node in response to the second construction task node's execution status being updated to complete.

3. The method for managing the entire industrial construction process based on platform-based BIM twins and online collaboration as described in claim 2, characterized in that, The process of generating a component dataset based on the building information model data and the component list data includes: Parse the building information model data to obtain the model attribute data for each component; Parse the component list data to obtain the list attribute data for each component; Match the model attribute data of the same component with the list attribute data; Based on the matching results, a unique component identifier is generated for each component, and the initial component state is set to form the component dataset.

4. The method for managing the entire industrial construction process based on platform-based BIM twins and online collaboration as described in claim 3, characterized in that, The construction area information includes a first area dimension and a second area dimension; the model attribute data includes component spatial location data; and establishing the association between components in the component dataset and the construction task nodes includes: Extract the component spatial location data for each component from the component dataset; Extract the first region dimension and the second region dimension from the construction task nodes; The spatial location data of the component is matched with the first region dimension and the second region dimension; For components and construction task nodes that are successfully matched in the region, establish the association between the components and the construction task nodes.

5. The method for managing the entire industrial construction process based on platform-based BIM twins and online collaboration as described in claim 4, characterized in that, The component state includes a first state, a second state, and a third state. Updating the component state of the corresponding component in the component dataset based on the component identifier in the component processing information includes: Extract the component identifier and the current stage identifier from the component processing information; The corresponding component is located in the component dataset based on the component identifier; The component status of the corresponding component is updated to the first state, the second state, or the third state according to the current stage identifier.

6. The method for managing the entire industrial construction process based on platform-based BIM twins and online collaboration as described in claim 5, characterized in that, The component processing information includes production stage processing information and transportation stage processing information. The component processing information received from the fourth participant includes: Receive production stage processing information from the fourth participant, the production stage processing information including the component identifier and production progress data; The system receives transportation phase processing information from the fourth participant, which includes the component identifier and transportation status data.

7. The method for managing the entire industrial construction process based on platform-based BIM twins and online collaboration as described in claim 6, characterized in that, The preset hierarchical relationship includes multiple decomposition levels, and the step of decomposing the project plan information into multiple construction task nodes according to the preset hierarchical relationship includes: The project plan information is decomposed level by level according to the multiple decomposition levels. Each decomposition breaks down the task of the previous level into multiple sub-tasks of the next level. When decomposed to the lowest level, the subtasks of the lowest level are taken as the construction task nodes.

8. A platform-based BIM twin and online collaborative industrialized construction process management system, employing the platform-based BIM twin and online collaborative industrialized construction process management method as described in any one of claims 1 to 7, characterized in that, include: The planning management module is used to receive project plan information uploaded by the first participant, decompose the project plan information into multiple construction task nodes according to a preset hierarchical relationship, each construction task node has corresponding construction area information, and set the execution order relationship of the multiple construction task nodes; The component data management module is used to receive building information model data and component list data uploaded by the second participant, and generate a component dataset based on the building information model data and the component list data. Each component in the component dataset includes a component identifier and a component status. The association processing module is used to establish the association relationship between the components in the component dataset and the construction task nodes; The demand processing module is used to receive a component acquisition request initiated by a third party for a specified construction task node, determine the corresponding component and its required quantity from the component dataset according to the association relationship, and send the component identifier and required quantity of the corresponding component to the fourth party. The status update module is used to receive component processing information fed back by the fourth participant, and update the component status of the corresponding component in the component dataset according to the component identifier in the component processing information.

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 any one of claims 1 to 7: a platform-based BIM twin and online collaborative industrialized construction process management method.

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 any one of claims 1 to 7 of the platform-based BIM twin and online collaborative industrialized construction process management method.

Images