A low-code bim integrated design system

Abstract

This invention discloses a low-code BIM integrated design system. The data layer comprises a data model layer, a data application layer, and a data flow layer, forming a data flow in the order of data model layer, data application layer, and data flow layer. Functional modules between the three data layers can be decoupled and freely bound, and data flow nodes for similar data within the data layers can be customized. The system implementation method includes: defining data flow nodes for similar data in each data layer; connecting the data flows of the data model layer and the data application layer through a dual-end binding controller; the data flow layer executing the dual-end bound data flow, and outputting application results after approval according to the preset rules of the data application layer blocks. This invention solves the problems of inflexible BIM integrated design and its incompatibility with actual project needs.

Description

Technical Field

[0001] This invention relates to the field of building information modeling data technology, and in particular to a low-code BIM integrated design system. Background Technology

[0002] BIM integrated design generally refers to a design management approach that uses a BIM model for 3D forward design, integrating information from various design stages and disciplines within a building project onto a unified platform, and implementing multi-disciplinary collaborative reference through access control. Its main characteristics include using a 3D model for parallel multi-disciplinary design, reducing design conflicts through a pre-defined, complex design process, and typically utilizing cloud technology to update 3D design information and maintain consistency. However, current mainstream BIM integrated design platforms generally suffer from a fixed integration process, leading to a mismatch between the linear workflow of actual projects and the established collaborative process of the BIM management platform. In project practice, the responsibilities and work interfaces of various stakeholders (design, construction, operation and maintenance) are often difficult to clearly define, resulting in a "collaboration dilemma" in integration processing, making it difficult to effectively reuse the BIM model created in the design phase in subsequent stages.

[0003] Low-code refers to a development approach that rapidly builds applications through a visual interface and with little or no coding. Its characteristics include modular functionality composed of visual drag-and-drop blocks, primarily driven by data flow, with minimal code intervention. When data flows into a node, the engine executes the corresponding pre-defined or custom logic and outputs the result to the next node, until the entire process is complete. This approach offers flexibility, visual adjustment, and ease of maintenance, significantly reducing the barrier to entry and development cycle for applications. However, currently, mainstream low-code technology is primarily used in office automation (OA), customer relationship management (CRM), and human resource management (HR) systems, mainly focusing on decoupling microservice architectures related to formulaic processes. For technical businesses such as engineering buildings, industrial manufacturing products, and hardware equipment, which contain complex data strings and involve multiple disciplines, processes, and strong data correlations, there is limited research on modular decoupling capabilities. Therefore, the application of low-code technology currently has limitations.

[0004] In summary, there is an urgent need for a method that integrates low-code and BIM technology to address the bottlenecks of inflexible and undiversified BIM integrated design and provide users with more convenient BIM integrated design services. Summary of the Invention

[0005] (a) Technical problems to be solved To address the aforementioned issues, this invention provides a low-code BIM integrated design system that solves the problems of inflexibility and mismatch between BIM integrated design and actual project requirements. By integrating low-code technology with BIM technology, it provides users with more convenient BIM integrated design services.

[0006] (II) Technical Solution To address the aforementioned technical problems, this invention provides a low-code BIM integrated design system. The system's data layer comprises a data model layer, a data application layer, and a data flow layer, forming a data flow in the order of data model layer, data application layer, and data flow layer. Functional modules between the three data layers can be decoupled and freely bound, and similar data within the data layers can have custom data flow nodes. The system's implementation method includes: S1. Define the data flow nodes for the same type of data in each data layer; S2, connecting the data flow between the data model layer and the data application layer through a dual-end binding controller; S2 includes: S21. Monitor data signals. When the system detects data interaction between the data model layer and the data application layer, it determines whether the interaction information matches. If so, it proceeds to the next step; otherwise, it terminates the process. The data model layer outputs model attribute information, and the data application layer outputs requirement information. S22. Based on the call instruction of the demand information, trigger the analysis nodes with dependencies in the data model layer, and analyze and store the model attribute information driven by the call instruction; S23. Calculate the propagation priority of each dependent analysis node, sort them from high to low, and filter the stored model attribute information in sequence according to the sorting. S24. Check whether the filtered model attribute information can support the successful execution of the application rules. If yes, the system will perform data flow matching and mapping after passing the conflict detection and proceed to the next step. If no, the system will stop executing the program and record the conflicting application rules after failing the conflict detection. S25. Update and synchronize the detected model attribute information to the data application layer block, complete the two-end binding of the data flow, output the application results according to the preset rules of the data application layer block, and enter the approval stage.

[0007] S3, the data flow after the data flow is bound to both ends in the data flow layer, initiates the data flow selection.

[0008] Furthermore, prior to S21, the following is also included: S20. For the current project, set keywords for adding model attribute information in the BIM model, and set keywords for requirement information through code.

[0009] Furthermore, in S21, determining whether the interaction information matches includes: comparing the keywords of the model attribute information with the keywords of the requirement information for the information that needs to be synchronized; if they match, proceed to the next step; if they do not match, terminate the process.

[0010] Furthermore, in S23, the propagation priority = data value coefficient × correlation impact coefficient × timeliness factor; the data value coefficient is used to measure the importance and value of the data node in the business process, and is determined by the business criticality, security factor, and usage frequency; the correlation impact coefficient is used to measure the degree of impact and propagation scope of the current change on the data node, and is determined by the degree of direct correlation, scope of impact, and business chain reaction; the timeliness factor is used to measure the urgency of the data node needing to be updated, and is determined by business timeliness requirements and the age of the current data state; the data value coefficient, correlation impact coefficient, and timeliness factor are all custom preset according to actual needs.

[0011] Furthermore, when the propagation priority is zero, a rejection process is performed.

[0012] Furthermore, when the propagation priorities are the same, they are processed according to attribute classification.

[0013] Furthermore, in S24, the method for detecting whether the filtered model attribute information can support the successful execution of the application rules includes: determining whether all the output elements of the model attribute information fill the preset types of data elements of the requirement information; if so, the conflict detection is passed; otherwise, the conflict detection is not passed.

[0014] Furthermore, in S25, updating and synchronizing the detected model attribute information to the data application layer block includes: first updating and synchronizing the detected model attribute information to the database, and then pushing the database update result to the data application layer block.

[0015] Furthermore, during the process of updating and synchronizing the detected model attribute information to the database, if there is a data storage anomaly, the synchronization is canceled, the anomaly information is recorded, and it is pushed to a human for resolution before proceeding to step S24.

[0016] (III) Beneficial Effects The above-described technical solution of the present invention has the following advantages: (1) This invention achieves the custom editing of BIM design logic and site management logic by using layered data layer design, forced data flow sequence and custom data flow of similar data in the data layer. This ensures the flow of BIM data and the continuity of design information, avoids the disorder of multi-disciplinary data integration, and enables multi-disciplinary users to have the freedom to process BIM data and simplify the custom processing flow, thereby improving the flexibility and diversity of BIM integrated design. (2) Based on the improved architecture, this invention processes the “large and comprehensive” information data of BIM through a dual-end binding judgment mechanism and mapping method of BIM data flow and application data flow, and provides a “light application” strategy from point to surface. It decomposes the key nodes in the BIM collaboration process, so that the complex data flow of BIM model information triggers the custom decoupled low-code module, realizing the core principle mechanism of low-code BIM integrated design. It effectively solves the problem of mismatch between the linear workflow of BIM integrated design and the actual collaborative process on the project site. It enables users to meet the low-code business application needs of flexible and customizable function combinations in the BIM integrated design process, while ensuring the orderly flow of BIM data. It solves the problem of disordered BIM data calling caused by complex and diverse business application rules, and enables low-code business applications to be executed smoothly according to the target rules. (3) While performing low-code decoupling work based on BIM business applications, this invention maintains the objective law that BIM integrated design is based on BIM model data flow, and reconstructs the architecture of traditional BIM integrated design data flow and low-code business flow, making it more flexible and integrated in application. (4) In the early stages of an engineering project, the present invention clarifies the application requirements and simultaneously implements specific control of BIM integrated design, avoiding redundant applications of the established BIM collaboration platform and making the overall team collaboration more effective. Attached Figure Description

[0017] The features and advantages of the invention will be more clearly understood by referring to the accompanying drawings, which are schematic and should not be construed as limiting the invention in any way. In the drawings: Figure 1 This is a logical principle diagram of the architecture design of the low-code BIM integrated design system according to an embodiment of the present invention; Figure 2 This is a logical principle diagram of the dual-end binding judgment mechanism and mapping method for BIM data stream and application data stream in an embodiment of the present invention. Detailed Implementation

[0018] The specific embodiments of the present invention will be described in further detail below with reference to the accompanying drawings and examples. The following examples are for illustrative purposes only and are not intended to limit the scope of the invention.

[0019] The core objective of this invention is to address how the complex data flow of BIM model information triggers decoupled low-code modules, and to develop a declarative data binding method adapted to BIM design, thereby achieving the effect of modular arbitrary combination of collaborative processes.

[0020] Because BIM integrated design is constrained by the BIM design data itself, and all subsequent business operations are based on BIM data, the data flow needs to be used with certain restrictions, and the transmission of data information cannot be arbitrarily disrupted. However, the purpose of this invention has been clearly stated: to solve the current bottleneck of the rigid process in BIM integrated design. Therefore, it is necessary to separate BIM data from BIM-based business applications, granting users permissions to implement business customization, while maintaining the basic logical order of the overall BIM data flow. Therefore, the low-code BIM integrated design system architecture of this invention is a fundamental condition of this invention.

[0021] The architecture design of this invention involves two steps. First, a layered design is implemented, dividing the data into three main layers: a data model layer (e.g., component attributes), a data application layer (e.g., forms, lists), and a data flow layer (e.g., approval workflow). The platform system enforces data flow processing in the order of "data model layer → data application layer → data flow layer," allowing for unified decoupling and flexible binding between modules in these three layers. Second, for similar data within the data layers, data flow nodes are defined visually. These nodes can be selected and combined as needed to customize the data flow.

[0022] The design methods of "custom data flow of similar data in the data layer" and "forced data flow in three-layer design" ensure the flow of BIM data and the continuity of design information, avoid the chaos of multi-disciplinary data integration, and enable multi-disciplinary users to have the freedom to process BIM data and simplify the customized processing flow.

[0023] In summary, the data layer of this invention comprises a data model layer, a data application layer, and a data flow layer, forming a data flow in the order of the data model layer, data application layer, and data flow layer. The functional modules between the three data layers can be decoupled and freely bound. Data of the same type within the data layer can have custom data flow nodes, thereby allowing for custom configuration parsing and generation of runnable module applications. The specific architecture design and process are as follows: Figure 1 As shown: Data Model Layer: Initiates BIM data model selection, customizes the selection of data flow nodes for similar data based on the attribute type of the data, and parses and generates runnable data model layer blocks according to custom configurations; Data Application Layer: Initiate BIM application task selection, customize the selection of data flow nodes for similar data based on the business type of the data, customize the configuration parsing and generate runnable data application layer blocks; Data Flow Layer: Initiates data flow selection, selects data flow nodes for similar data based on the data flow type, parses custom configurations and generates runnable data flow layer blocks, approves and determines whether the data flow after the two ends are bound, and outputs the application results if it passes; otherwise, it re-initiates data flow selection. Based on the above framework, the implementation method of the low-code BIM integrated design system of the present invention includes: S1. Define the data flow nodes for the same type of data in each data layer; Data of the same type in each data layer can be customized into data flow nodes. The data model layer classifies data according to attribute type, the data application layer classifies data according to business type, and the data process layer classifies data according to process type.

[0024] Taking the data model layer as an example, attribute types include professional attributes, component geometric attributes, component non-geometric attributes, and additional attributes. Professional attributes further include architecture, structure, and mechanical and electrical engineering, etc. Data related to the architecture profession are all of the same type, such as... Figure 1 As shown, under major A, model Aa, model Ab, block Aa-1, and block Aa-3 are all of the same type of data.

[0025] The implementation method of low-code business flow for similar data in each data layer, namely the decoupling of custom modules for similar data in each data layer and custom combination, is existing technology and will not be described in detail.

[0026] This invention does not protect the specific business processes in the BIM integration design of the data model layer, data application layer, and data flow layer, nor does it emphasize the protection of output methods such as various BIM data attribute classifications (architectural, structural, MEP, and other professional attributes, geometric attributes, non-geometric attributes, other labels, etc.), business application rule types (tables, text, Gantt charts, etc.), and process rules (proofreading, review, approval, etc.). Various BIM data attribute classifications, business application rule types, and process rule types can be flexibly customized by customers.

[0027] S2. Connect the data flow between the data model layer and the data application layer through a dual-end binding controller; This step is the core method supporting low-code implementation for three major functional types: BIM model data, BIM business management functions, and BIM approval processes. BIM model data, BIM business management functions, and BIM approval processes correspond to the data model layer, data application layer, and data flow layer, respectively. After resolving the issue of fragmented nodes that allow for customization of similar data in each data layer, a method for determining and mapping the BIM model data flow and application data flow back into a complete data flow is needed to ensure smooth execution of integrated design based on BIM information. For example, "BIM water supply and drainage pipeline model," "equipment statistics," "form output," and "verification and approval" are encapsulated into reusable blocks, and by granting user permissions, a complete data flow is ultimately formed with the output: "Equipment statistics table of BIM water supply and drainage pipeline model." The dual-end binding judgment mechanism and mapping method between the BIM data flow and application data flow are shown in Figure 2, including the following steps: S20. For the current project, set keywords for adding model attribute information in the BIM model, and set keywords for requirement information through code; Before forming the data model layer blocks and data application layer blocks, keywords for model attribute information and requirement information should be pre-set for the current project. This facilitates matching and judgment during subsequent monitoring and data interaction. Keywords for model attribute information are added in the BIM model, while keywords for requirement information are set via code, such as... Figure 1 As shown.

[0028] S21. Monitor data signals. When the system detects data interaction between the data model layer and the data application layer, it determines whether the interaction information matches. If so, it proceeds to the next step; otherwise, it terminates the process. The data model layer outputs model attribute information, and the data application layer outputs requirement information. Matching is performed only for information that needs to be synchronized. The BIM attribute information codes and keywords input into the "two-way binding controller" through the data model layer block are compared with the application requirement attribute information codes and keywords input into the "two-way binding controller" through the data application layer block. If they match, proceed to the next step; otherwise, the process terminates.

[0029] S22. Based on the call instruction trigger node of the demand information, confirm the dependency relationship, and analyze and store the model attribute information driven by the call instruction; After S21 matching and judgment, the system detects key call commands for demand information data elements (pre-set) and triggers nodes. It then analyzes and stores the BIM data information driven by the key call commands before proceeding to the next step. Dependencies are confirmed by determining the relationships involved in the call command keywords of the demand information, which identify the affected nodes. Mapping and triggering of call nodes are then implemented for the associated BIM components and their information.

[0030] S23. Calculate the propagation priority of each triggered node, sort them from high to low, and filter the stored model attribute information in sequence according to the sorting. The system begins calculating the propagation scope and execution order of the BIM model data for each affected node, triggered by the key call instruction in S22. Specifically, it calculates the propagation priority P for each affected node. i This value is determined by three key factors, and the following coefficients can be customized to meet the actual needs of the client's project: Propagation Priority P i =Data value coefficient × correlation impact coefficient × timeliness factor; Among them, the data value coefficient is used to measure the importance and value of the data node in the business process, which is determined by the business criticality, security coefficient and usage frequency; the correlation impact coefficient is used to measure the degree of impact and scope of the current change on the data node, which is determined by the degree of direct correlation, scope of impact and business chain reaction; the timeliness factor is used to measure the urgency of the data node needing to be updated, which is determined by the business timeliness requirements and the age of the current data.

[0031] The system is based on propagation priority P i The affected nodes are sorted according to their propagation priority P. i The component attribute information is filtered and processed in descending order of priority, with priority P propagated. i If the value is zero, remove the affected element; propagate priority P. i When nodes are identical, they are categorized by attribute for processing. This ensures that nodes with higher priority update data first, guaranteeing that critical data is updated first. At the same time, the system checks for and avoids circular dependencies, ensuring the orderliness and stability of the computation process.

[0032] S24. Check whether the filtered model attribute information can support the successful execution of the application rules. If yes, the system will perform data flow matching and mapping after passing the conflict detection and proceed to the next step. If no, the system will stop executing the program and record the conflicting application rules after failing the conflict detection. Before updating and storing the model attribute information data after S23 detection and filtering into the database, the system checks whether the data can support the successful execution of application rules. If no rule problem occurs, the system performs data flow matching and mapping. If a rule problem occurs and cannot be resolved, the system pushes a prompt to the user that a data flow cannot be formed, the model data does not match the business data, stops the program execution, and records the conflicting application rules.

[0033] The method for detecting whether the filtered model attribute information can support the successful execution of application rules includes: comparing the type attributes of the output elements of the model attribute information with the preset types of the data elements of the requirement information, and determining whether the output elements of the model attribute information completely fill the preset types of the data elements of the requirement information. If so, the conflict detection is passed; otherwise, the conflict detection is not passed. The preset types of the data elements of the requirement information are for the types of BIM component attribute information, including professional attributes, component geometric attributes, component non-geometric attributes, and additional attributes.

[0034] S25. Update and synchronize the detected model attribute information to the data application layer block, complete the two-end binding of the data flow, output the application results according to the preset rules of the data application layer block, and enter the approval stage. The system first updates and synchronizes the detected model attribute information to the database; to ensure data integrity, if there is a data storage abnormality during the synchronization process, the synchronization is canceled, the abnormal information is recorded, and pushed to manual resolution before proceeding to step S24. Once database synchronization is complete, the system immediately pushes the updated database results to the application blocks set in the front end, i.e., the data application layer blocks. Through an event notification mechanism, all interfaces displaying this data are ensured to refresh in real time, presenting users with the latest and most accurate data status. Simultaneously, the system records a complete log of this synchronization, including the source of the change, its propagation path, execution results, and performance metrics, providing data support for subsequent analysis and optimization.

[0035] S3. The data flow layer executes the data flow after the two ends are bound, and outputs the application results after approval according to the preset rules of the data application layer blocks.

[0036] After the data push is completed, the complete data stream after the two ends are bound can be executed, and the application results will be output after approval and judgment according to the preset rules of the data application layer block.

[0037] For the low-code BIM integrated design system of this invention, the user's final experience is: defining the combination logic and association rules between BIM components by dragging and dropping blocks through a graphical interface, without having to rewrite existing scripts. When the user configures a business rule flow that utilizes BIM component information, the platform automatically establishes an association between the functional view and the BIM data model, driving BIM-based collaborative workflow operations. Simultaneously, model information and workflow information are updated synchronously. When a component is selected in the 3D model, the associated business data (such as progress and quality inspection records) is automatically presented on the interface. By studying the declarative data binding between BIM data and workflow data, a significant amount of manual coding and debugging work is reduced, which also solves the dilemma of rigid and inflexible BIM collaborative workflows that do not match the actual project requirements.

[0038] If the program is to output results smoothly, it will have strong guidance in development. Its programmers realize that in the process of program development, they need to pay attention in advance: before the "data model layer" and "data application layer" blocks are formed, the custom functional modules decomposed in their respective data layers should have effective strong correlation data elements built in advance in order to make good use of this architecture and provide reliable preconditions for subsequent two-end binding.

[0039] In summary, the low-code BIM integrated design system described above has the following beneficial effects: (1) This invention achieves the custom editing of BIM design logic and site management logic by using layered data layer design, forced data flow sequence and custom data flow of similar data in the data layer. This ensures the flow of BIM data and the continuity of design information, avoids the disorder of multi-disciplinary data integration, and enables multi-disciplinary users to have the freedom to process BIM data and simplify the custom processing flow, thereby improving the flexibility and diversity of BIM integrated design. (2) Based on the improved architecture, this invention processes the “large and comprehensive” information data of BIM through a dual-end binding judgment mechanism and mapping method of BIM data flow and application data flow, and provides a “light application” strategy from point to surface. It decomposes the key nodes in the BIM collaboration process, so that the complex data flow of BIM model information triggers the custom decoupled low-code module, realizing the core principle mechanism of low-code BIM integrated design. It effectively solves the problem of mismatch between the linear workflow of BIM integrated design and the actual collaborative process on the project site. It enables users to meet the low-code business application needs of flexible and customizable function combinations in the BIM integrated design process, while ensuring the orderly flow of BIM data. It solves the problem of disordered BIM data calling caused by complex and diverse business application rules, and enables low-code business applications to be executed smoothly according to the target rules. (3) While performing low-code decoupling work based on BIM business applications, this invention maintains the objective law that BIM integrated design is based on BIM model data flow, and reconstructs the architecture of traditional BIM integrated design data flow and low-code business flow, making it more flexible and integrated in application. (4) In the early stages of an engineering project, the present invention clarifies the application requirements and simultaneously implements specific control of BIM integrated design, avoiding redundant applications of the established BIM collaboration platform and making the overall team collaboration more effective.

[0040] Finally, 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 embodiments of the present invention have been described in conjunction with the accompanying drawings, those skilled in the art can make various modifications and variations without departing from the spirit and scope of the present invention, and such modifications and variations all fall within the scope defined by the appended claims.

Claims

1. A low-code BIM integrated design system, characterized in that, The system's data layer includes a data model layer, a data application layer, and a data flow layer, which form a data flow in the order of the data model layer, data application layer, and data flow layer. The functional modules between the three data layers can be decoupled and freely bound, and the data flow nodes of the same type of data in the data layer can be customized. The system implementation method includes: S1. Define data flow nodes for the same type of data in each data layer. The data model layer classifies data according to attribute type, the data application layer classifies data according to business type, and the data process layer classifies data according to process type. S2, connecting the data flow between the data model layer and the data application layer through a dual-end binding controller; S2 includes: S21. Monitor data signals. When the system detects data interaction between the data model layer and the data application layer, it determines whether the interaction information matches. If so, it proceeds to the next step; otherwise, it terminates the process. The data model layer outputs model attribute information, and the data application layer outputs requirement information. S22. Based on the call instruction trigger node of the demand information, confirm the dependency relationship, and analyze and store the model attribute information driven by the call instruction; S23. Calculate the propagation priority of each triggered node, sort them from high to low, and filter the stored model attribute information in sequence according to the sorting. S24. Check whether the filtered model attribute information can support the successful execution of the application rules. If yes, the system will perform data flow matching and mapping after passing the conflict detection and proceed to the next step. If no, the system will stop executing the program and record the conflicting application rules after failing the conflict detection. S25. Update and synchronize the detected model attribute information to the data application layer block, complete the two-end binding of the data flow, output the application results according to the preset rules of the data application layer block, and enter the approval stage. S3. The data flow layer executes the data flow after the two ends are bound, and outputs the application results after approval according to the preset rules of the data application layer blocks.

2. The low-code BIM integrated design system according to claim 1, characterized in that, The process preceding S21 also includes: S20. For the current project, set keywords for adding model attribute information in the BIM model, and set keywords for requirement information through code.

3. The low-code BIM integrated design system according to claim 1, characterized in that, In S21, determining whether the interaction information matches includes: for the information that needs to be synchronized, comparing the keywords of the model attribute information with the keywords of the requirement information; if they match, proceed to the next step; if they do not match, terminate the process.

4. The low-code BIM integrated design system according to claim 1, characterized in that, In S23, the propagation priority = data value coefficient × correlation impact coefficient × timeliness factor; the data value coefficient is used to measure the importance and value of the data node in the business process, and is determined by the business criticality, security factor, and usage frequency; the correlation impact coefficient is used to measure the degree of impact and propagation scope of the current change on the data node, and is determined by the degree of direct correlation, scope of impact, and business chain reaction; the timeliness factor is used to measure the urgency of the data node needing to be updated, and is determined by business timeliness requirements and the age of the current data state; the data value coefficient, correlation impact coefficient, and timeliness factor are all customized and preset according to actual needs.

5. The low-code BIM integrated design system according to claim 4, characterized in that, When the propagation priority is zero, it is removed.

6. The low-code BIM integrated design system according to claim 4, characterized in that, When the propagation priorities are the same, they are classified and processed according to attributes.

7. The low-code BIM integrated design system according to claim 1, characterized in that, In S24, the method for detecting whether the model attribute information after filtering can support the successful execution of the application rules includes: determining whether the output elements of the model attribute information are all filled with the preset types of data elements of the requirement information; if so, the conflict detection is passed; otherwise, the conflict detection is not passed.

8. The low-code BIM integrated design system according to claim 1, characterized in that, In S25, updating and synchronizing the detected model attribute information to the data application layer block includes: first updating and synchronizing the detected model attribute information to the database, and then pushing the database update result to the data application layer block.

9. The low-code BIM integrated design system according to claim 8, characterized in that, If there is a data storage anomaly during the process of updating and synchronizing the detected model attribute information to the database, the synchronization will be canceled, the anomaly information will be recorded, and the information will be pushed to a human for resolution before proceeding to step S24.

10. The low-code BIM integrated design system according to claim 1, characterized in that, The data model layer includes: initiating BIM data model selection, customizing data flow nodes for similar data based on data attribute types, customizing configuration parsing, and generating runnable data model layer blocks; the data application layer includes: initiating BIM application task selection, customizing data flow nodes for similar data based on data business types, customizing configuration parsing, and generating runnable data application layer blocks; the data process layer includes: initiating data process selection, customizing data flow nodes for similar data based on data process types, customizing configuration parsing, and generating runnable data process layer blocks, approving and determining whether the data flow after dual-end binding is approved. If approved, the application results are output; otherwise, the data process selection is re-initiated.

Images