Direct analysis and rendering method and system for revit model

Abstract

The application provides a revit model direct analysis and rendering method and system, the method comprises the following steps: extracting model original data through a plug-in API; analyzing the model original data to generate model analysis data; transmitting the analysis data to a server end for scene processing, including reconstructing the spatial structure of the model, generating hierarchical scene features, and establishing an index to form a model scene file; loading the model scene file through a multi-threaded download mechanism of a front-end page; and rendering the downloaded model scene file in real time. The application realizes direct analysis and rendering of a revit model by targeting a revit plug-in API, provides basic data support for flexible use of model data throughout the life cycle, has good reusability and expandability, greatly improves the stability of revit analysis and the efficiency of rendering, and provides a new method and idea for building an independent revit model application platform.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of three-dimensional model analysis, in particular to a revit model direct analysis and rendering method and system. BACKGROUND

[0002] With the rapid development of digital twin technology, the landing application of BIM revit model in the water conservancy industry has formed a consensus. How to make the value of BIM model in the whole life cycle of water conservancy project be reflected, the basic data of BIM model needs to be connected with business, and the revit model direct analysis needs to be standardized to process the professional data of the model, and the model data needs to be applied to the whole life cycle of the project, which provides a data platform for the design, construction and operation management of water conservancy projects, and provides data support for the application of each link of the project. However, the existing Revit model analysis technology still has many limitations, which seriously restricts the efficient application of BIM model in the whole life cycle of the project.

[0003] The current mainstream analysis methods can be divided into two modes: direct upload analysis and conversion analysis. Direct upload analysis relies on third-party platforms, and users need to upload complete RVT files for online analysis. This method has the following problems: first, Revit models are usually large in size, the uploading process is time-consuming and easy to be interrupted due to network fluctuations, resulting in low analysis efficiency; second, the analysis engine of the third-party platform has limited compatibility with the internal data format of Revit, often resulting in loss of component properties, decrease in geometric accuracy, or missing of material textures, affecting the integrity and accuracy of the data; in addition, uploading the original model to an external platform poses a risk of data leakage, making it difficult to meet the compliance requirements of classified projects.

[0004] The conversion analysis mode realizes model analysis by exporting intermediate formats such as IFC, FBX, etc., but it also has the following defects. On the one hand, the format conversion of large models (such as more than 10 million faces) requires high local hardware, which is easy to cause Revit to crash due to memory overflow or excessive GPU load, and the conversion time is uncontrollable; on the other hand, the parameterized components, complex material layers and spatial topological relationships specific to Revit may be simplified or lost during the conversion process, resulting in disconnection between the model and the business data. In addition, the converted model needs to be adapted to specific rendering engines (such as Unity, Three.js), and different engines have different support for intermediate formats, which requires additional development of adaptation logic, increasing the technical complexity and maintenance cost.

[0005] In addition to the above two types of analysis methods, the prior art also has the problem of insufficient universality. Most solutions only focus on visual display and lack support for dynamic requirements in design, construction, operation and maintenance stages (such as version comparison and attribute batch editing), making it difficult to realize the full life cycle value of BIM data. At the same time, the traditional analysis logic is strongly coupled with the business scene, and the extensibility is poor. New functions (such as lightweight offline package generation and two-dimensional and three-dimensional linkage) need to reconstruct the underlying analysis process, which is low in development efficiency.

[0006] In terms of performance, the unoptimized model data has a lot of redundancy (such as repeated geometric vertices and unmerged materials) when rendering, resulting in low data transmission efficiency and high GPU load, making it difficult to meet the needs of large-scale engineering real-time interaction. The prior art generally lacks an efficient data reuse mechanism, making the parsing and rendering efficiency a bottleneck, which restricts the large-scale application of digital twin technology.

[0007] In summary, the existing Revit model analysis technology cannot meet the four core requirements of efficiency (analysis / rendering speed), integrity (data lossless), security (local processing), and extensibility (business flexibility). SUMMARY

[0008] The present application provides a revit model direct analysis and rendering method and system, which can solve the technical problems of long time consumption and instability in uploading and analyzing large original models in the prior art, or the technical problems of high requirements for machine configuration of exported models and easy loss of part of data in indirect analysis.

[0009] In a first aspect, the present application provides a revit model direct analysis and rendering method, comprising the following steps:

[0010] extracting model original data through a plug-in API;

[0011] analyzing the model original data to generate model analysis data;

[0012] transmitting the analysis data to a server side for scene processing to form a model scene file;

[0013] loading the model scene file through a multi-threaded download mechanism of a front-end page;

[0014] real-time rendering of the downloaded model scene file.

[0015] As a preferred embodiment of the present application, the step of extracting model original data through a plug-in API specifically comprises the following steps:

[0016] encapsulating a revit model interface through a plug-in API to obtain model original data including geometric data, attribute parameters and material information.

[0017] As a preferred embodiment of the present application, the model original data obtained is parsed through the plug-in API, and model parsed data is obtained, specifically including the following steps:

[0018] The model original data is identified, and component data is obtained;

[0019] The component data is subjected to geometric instantiation processing and model reorganization to obtain model parsed data.

[0020] As a preferred embodiment of the present application, the model original data is identified, and component data is obtained, specifically including the following steps:

[0021] The revit model components in the model original data are traversed, and the corresponding properties, geometry, and material of the revit model components are written into the linked list object. The component geometry object is compared with the linked list data, and repeated data is not written in.

[0022] The material texture map is stored as a picture.

[0023] The corresponding relationship between the material texture map and the revit model component face sheet is established.

[0024] The drawing file in the model original data is exported using the Dwg plug-in.

[0025] As a preferred embodiment of the present application, the component data is subjected to geometric instantiation processing, specifically including the following steps:

[0026] The same material and geometry components are subjected to geometric instantiation processing.

[0027] The conversion matrix is used to record the component position difference.

[0028] The same material and different geometry components are merged into one component.

[0029] As a preferred embodiment of the present application, the parsed data is transmitted to the server end for scene processing to form a model scene file, specifically including the following steps:

[0030] When the number of components in the model parsed data exceeds the component number threshold or the memory data amount occupied by the model parsed data exceeds the memory data amount threshold, the model parsed data is persisted and exported to a file, and a call to the backend service scene interface is initiated to transmit the data to the backend server.

[0031] The model parsed data is subjected to scene processing based on the backend server to obtain a model scene file.

[0032] The model scene file is stored.

[0033] As a preferred embodiment of the present application, the backend server-based model parsing data is scene-processed to obtain a model scene file, specifically including the following steps:

[0034] Parsing the component data in the model parsing data;

[0035] When the component data is parsed, updating the revit bounding box data of the revit model;

[0036] Updating the space tree, system tree and professional tree.

[0037] As a preferred embodiment of the present application, the component data in the model parsing data is parsed, specifically including the following steps:

[0038] Using multi-threading to parse the information required for component association;

[0039] Using multi-threading to parse the components, performing node merging to merge the nodes with the same material in a component into one node data; based on the geometry index in the original node and the matrix hascode value of the node, performing geometry reuse of the entire model.

[0040] In a second aspect, the present application provides a revit model direct parsing and rendering system, characterized in that it comprises:

[0041] A model original data acquisition module for extracting model original data through a plug-in API;

[0042] A model original data parsing module in communication connection with the model original data acquisition module, for parsing the model original data to generate model parsing data;

[0043] A scene processing module in communication connection with the plug-in initialization parsing module, for transmitting the parsing data to the server end for scene processing to form a model scene file;

[0044] A model scene file loading module in communication connection with the scene processing module, for loading the model scene file through the multi-threaded download mechanism of the front-end page;

[0045] A model rendering module in communication connection with the model scene file loading module, for real-time rendering of the downloaded model scene file.

[0046] As a preferred embodiment of the present application, the model original data acquisition module comprises:

[0047] A model original data acquisition unit for encapsulating the revit model interface through a plug-in API to acquire model original data.

[0048] The technical scheme provided by the embodiments of the present application has at least the following beneficial effects:

[0049] The revit model direct analysis and rendering are realized by aiming at the revit plug-in API, which provides basic data support for flexible use of model data in the whole life cycle.

[0050] The method has good reusability and expandability, greatly improves the stability of revit analysis and the efficiency of rendering, and provides a new method and idea for building an independent revit model application platform. BRIEF DESCRIPTION OF DRAWINGS

[0051] Figure 1 The figure is a flowchart of the revit model direct analysis and rendering method of the present application.

[0052] Figure 2 The figure is a functional module diagram of the revit model direct analysis and rendering system of the present application. DETAILED DESCRIPTION

[0053] In order to enable personnel in the art to better understand the present application, the technical solutions in the embodiments of the present application will be described clearly and completely below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative labor fall within the scope of the present application.

[0054] The terms "include" and "have" and any variations thereof in the specification and claims of the present application and the above-described drawings are intended to cover non-exclusive inclusion. For example, a process, method, system, product or device including a series of steps or units is not limited to the listed steps or units, but can optionally include steps or units not listed, or can optionally include other steps or units inherent to the process, method, product or device. The terms "first", "second" and "third" and the like descriptions are used to distinguish different objects, and do not represent the order or limit the types of "first", "second" and "third".

[0055] In the description of the embodiments of the present application, "exemplary", "for example" or "for instance" is used to mean as an example, illustration or description. Any embodiment or design scheme described as "exemplary", "for example" or "for instance" in the embodiments of the present application should not be interpreted as more preferred or more advantageous than other embodiments or design schemes. On the contrary, the words "exemplary", "for example" or "for instance" are intended to present the relevant concept in a specific way.

[0056] In the description of the embodiments of the present application, unless otherwise specified, " / " represents the meaning of or, for example, A / B can represent A or B; "and / or" in the text only describes the association relationship of the associated objects, which means that there can be three relationships, for example, A and / or B, which can represent: A exists alone, A and B exist together, and B exists alone, in addition, in the description of the embodiments of the present application, "multiple" means two or more than two.

[0057] In some processes described in the embodiments of the present application, a plurality of operations or steps are included in a specific order, but it should be understood that these operations or steps can be executed or executed in parallel without the order in which they appear in the embodiments of the present application, and the serial number of the operation is only used to distinguish different operations, and the serial number itself does not represent any execution order. In addition, these processes can include more or fewer operations, and these operations or steps can be executed in sequence or in parallel, and these operations or steps can be combined.

[0058] In order to make the purpose, technical scheme and advantages of the present application clearer, the embodiments of the present application will be further described in detail below with reference to the drawings.

[0059] In a first aspect, as Figure 1 The revit model direct analysis and rendering method provided by the embodiments of the present application specifically includes the following steps:

[0060] Step S1: Extracting model original data through plug-in API;

[0061] Step S2: Analyzing the model original data to generate model analysis data;

[0062] Step S3: Transmitting the analysis data to the server side for scene processing to form a model scene file;

[0063] Step S4: Loading the model scene file through the multi-threaded download mechanism of the front-end page;

[0064] Step S5: Real-time rendering of the downloaded model scene file.

[0065] The present application realizes direct analysis and rendering of revit model by aiming at revit plug-in API, which provides basic data support for flexible use of model data full life cycle;

[0066] The method has good reusability and expandability, greatly improves the stability of revit analysis and rendering efficiency, and provides a new method and idea for building an independent revit model application platform.

[0067] In an embodiment, the present application realizes direct parsing of the Revit model by secondary development of the plug-in API in step S1: extracting geometric data, attribute parameters and material information in the model through the plug-in API, and performing instantiation processing and optimized reorganization on these data to generate standardized model parsing data. Before the above steps, the following steps are further included:

[0068] Step S0: Secondary development of the plug-in API, which further includes the following steps:

[0069] Step S01: Configure the secondary development environment of the plug-in API; specifically, first install the software environment matching the target Revit version to ensure API compatibility. The development tool is Visual Studio, and.NET Framework 4.8 or compatible version is configured. In the project, reference the Revit core assembly RevitAPI.dll and RevitAPIUI.dll, which are located in the Revit installation directory, to provide basic support for subsequent API calls;

[0070] Step S02: Initialize the plug-in project in the configured plug-in API secondary development environment to build a Revit interaction framework; specifically, create a class library project in Visual Studio to implement the IExternalCommand interface as the main entrance of the plug-in. Establish an interaction channel with the Revit process through the Document object to obtain the current active Revit document context. The project needs to be configured as an x64 platform to be consistent with the Revit process architecture.

[0071] Step S03: Based on the built Revit interaction framework, develop the core algorithm and function of Revit model parsing; specifically, traverse the model components through the Element class to extract geometric data (vertex coordinates, normal vectors), attribute parameters (family type, instance parameters) and material information. Inherit the ICustomExporter interface to implement custom parsing logic and override the Export method to output data to the memory buffer. For large model processing, set up a separate monitoring thread to automatically save the progress and release resources when the memory usage exceeds the threshold, ensuring the stability of the parsing.

[0072] Step S04: Through plug-in integration and deployment, the core algorithm and function of the developed Revit model analysis are converted into a plug-in API after secondary development, and the analysis function is integrated into the Revit menu bar through RibbonPanel to support one-key triggering by users. After compiling to generate a.dll plug-in file, an.addin manifest file is created to configure the loading path, ensuring that the plug-in is automatically loaded when Revit starts. When deploying, the compatibility of the plug-in in the target Revit version needs to be verified, and an exception handling mechanism needs to be provided.

[0073] In an embodiment, the step S1 of extracting model original data through a plug-in API specifically includes the following steps:

[0074] The revit model interface is encapsulated through the plug-in API to obtain the model original data.

[0075] In an embodiment, the step S2 of analyzing the model original data to generate model analysis data specifically includes the following steps:

[0076] Step S21: The model original data obtained is analyzed through the plug-in API to obtain model analysis data;

[0077] Step S22: The model analysis data is stored.

[0078] In an embodiment, the step S21 of analyzing the model original data obtained through the plug-in API to obtain model analysis data specifically includes the following steps:

[0079] Step S211: The model original data is identified to obtain component geometric data, including geometric, attribute, material, texture, drawing, version, etc.

[0080] Step S212: The component geometric data is subjected to geometric instantiation processing to obtain model analysis data.

[0081] In an embodiment, the step S211 of identifying the model original data to obtain component geometric data specifically includes the following steps:

[0082] The revit model components in the model original data are iterated, and the attributes, geometry, and material corresponding to the revit model components are written into the linked list object. The component geometry object is compared with the linked list data, and repeated data is not written.

[0083] The material texture map is stored as a picture.

[0084] The correspondence between the material texture map and the revit model component face sheet is established.

[0085] The drawing file in the model original data is exported using a Dwg plug-in.

[0086] In an embodiment, the step S212 of performing geometric instantiation on the component geometry data specifically includes the following steps:

[0087] The same material and geometric components are subjected to geometric instantiation, specifically, the same material and geometric components are instantiated, and the same material and different geometric components are merged, for subsequent geometric and material reuse, reducing the model data size;

[0088] The transformation matrix is used to record the position difference of the components;

[0089] The same material and different geometric components are merged into one large component, reducing the number of data transmissions and data size between CPU, memory and GPU.

[0090] In an embodiment, the step S22 of storing the model analysis data specifically includes the following steps:

[0091] The model analysis data is stored in the memory using a linked list method.

[0092] In an embodiment, the step S3 of transmitting the analysis data to the server side for scene processing to form a model scene file specifically includes the following steps:

[0093] Step S31: When the number of components in the model analysis data exceeds the component quantity threshold or the memory data size occupied by the model analysis data exceeds the memory data size threshold, the model analysis data is persisted and exported to a file and a call to the backend service scene interface is initiated, the data is transmitted to the backend server, and export progress information is recorded to support breakpoint resume and progress synchronization;

[0094] Step S32: Based on the backend server, the model analysis data is subjected to scene processing to obtain a model scene file;

[0095] Step S33: Store the model scene file.

[0096] In an embodiment, the step S32 of performing scene processing on the model analysis data based on the backend server to obtain a model scene file specifically includes the following steps:

[0097] The component geometry data in the model analysis data is analyzed to generate model outline, axis network, offline data package, default and custom scene data, and store them in the database. When the component geometry data is analyzed, the revit bounding box data of the model is updated;

[0098] The space tree, system tree and professional tree are updated.

[0099] The model data preprocessing and scene processing logic are separated in the present application, which facilitates expansion according to business needs.

[0100] In one embodiment, the component geometric data in the analytical model analytical data specifically includes the following steps:

[0101] Multi-threading is used to parse the information required for component association;

[0102] Multi-threaded component parsing is used to merge nodes, combining nodes of the same material within a component into a single node data; geometric reuse of the entire model is based on the geometric index and matrix hash code value of the original node.

[0103] In one embodiment, step S4: loading the model scene file through the multi-threaded download mechanism of the front-end page specifically includes the following steps:

[0104] Asynchronously load component, material, and texture data into memory and perform simple conversion processing.

[0105] In one embodiment, step S5: Real-time rendering of the downloaded model scene file specifically includes the following steps:

[0106] The geometry files are rendered one by one using a design that reuses geometry and materials.

[0107] Secondly, such as Figure 2 As shown, this application provides a Revit model direct parsing and rendering system, including a model raw data acquisition module 100, a model raw data parsing module 200, a scene processing module 300, a model scene file loading module 400, and a model rendering module 500; the model raw data acquisition module 100 is used to extract the model raw data through the plugin API; the model raw data parsing module 200 is communicatively connected to the model raw data acquisition module 100 and is used to parse the model raw data to generate model parsing data; the scene processing module 300 is communicatively connected to the plugin initialization parsing module 200 and is used to transmit the parsed data to the server for scene processing to form a model scene file;

[0108] The module can also provide a customized interface for personalized model scene data processing, such as an outer contour, a graticule, and a small map. The module uses a message middleware framework rabbitmq for message processing, multiple execution machines are registered to the rabbitmq and subscribe to message types, when the rabbitmq receives a message and puts it into a specified message queue, the registered execution machine receives a subscription message and starts processing the request task; the model scene file loading module 400 is in communication connection with the scene processing module 300, and is used for loading the model scene file through the multi-threaded download mechanism of the front-end page; the model rendering module 500 is in communication connection with the model scene file loading module 400, and is used for real-time rendering of the downloaded model scene file. Specifically, the model rendering module downloads model scene data in parallel, preferentially downloads material data, according to the material reuse and geometry reuse mechanism, the geometry data file is downloaded and real-time rendering is performed, model face data is organized, and is transmitted to the GPU for rendering and display, and the display framework uses webgl.

[0109] In an embodiment, the plug-in initialization analysis module comprises:

[0110] A model original data acquisition unit is configured to encapsulate a revit model interface through a plug-in API to acquire model original data;

[0111] A model analysis data acquisition unit is in communication connection with the model original data acquisition unit, and is configured to analyze the acquired model original data through a plug-in API to acquire model analysis data;

[0112] An analysis data storage unit is in communication connection with the model analysis data acquisition unit, and is configured to store the model analysis data.

[0113] The functions of each module in the revit model direct analysis and rendering system correspond to the steps in the revit model direct analysis and rendering method embodiments, and the functions and implementation processes will not be repeated here.

[0114] In a third aspect, the embodiments of the present application provide a revit model direct analysis and rendering device. The revit model direct analysis and rendering device can be a personal computer (PC), a notebook computer, a server, or other devices with data processing functions.

[0115] The communication interface includes an input / output (I / O) interface, a physical interface, and a logical interface, and the like, which are used to realize the interface for directly parsing and rendering the device interconnection inside the revit model, and the interface for realizing the interconnection between the revit model and other devices (for example, other computing devices or user devices). The physical interface can be an Ethernet interface, a fiber interface, an ATM interface, and the like; and the user device can be a display (Display), a keyboard (Keyboard), and the like.

[0116] The memory can be various types of storage media, such as random access memory (RAM), read-only memory (ROM), non-volatile RAM (NVRAM), flash memory, optical storage, hard disk, programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), and the like.

[0117] The processor can be a general-purpose processor, which can call the revit model direct parsing and rendering program stored in the memory and execute the revit model direct parsing and rendering method provided by the embodiments of the present application. For example, the general-purpose processor can be a central processing unit (CPU). The method executed by the revit model direct parsing and rendering program when called can refer to various embodiments of the revit model direct parsing and rendering method of the present application, which will not be described here.

[0118] In a fourth aspect, the embodiments of the present application further provide a readable storage medium.

[0119] The revit model direct parsing and rendering program is stored on the readable storage medium of the present application, and when the revit model direct parsing and rendering program is executed by the processor, the steps of the revit model direct parsing and rendering method as described above are realized.

[0120] The method realized by the revit model direct parsing and rendering program when executed can refer to various embodiments of the revit model direct parsing and rendering method of the present application, which will not be described here.

[0121] It should be noted that the above-mentioned serial numbers of the embodiments of the present application are only for description, and do not represent the advantages and disadvantages of the embodiments.

[0122] Those skilled in the art can clearly understand the above-mentioned embodiment method can be realized by means of software and the necessary general hardware platform, of course, can also be realized by hardware, but in many cases, the former is a better embodiment. Based on such understanding, the technical solutions of the present application can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) as described above, and includes a plurality of instructions for making a terminal device execute the method described in each embodiment of the present application.

[0123] The above is only the preferred embodiment of the present application, and does not limit the patent scope of the present application, and any equivalent structure or equivalent process transformation using the content of the specification and drawings, or direct or indirect application in other related technical fields, are also included in the patent protection scope of the present application.

Claims

1. A method for directly parsing and rendering a Revit model, characterized in that, The method comprises the following steps: extracting model original data through a plug-in API; parsing the model original data to generate model parsed data; transmitting the parsed data to a server end for scenario processing to form a model scenario file; loading the model scenario file through a multi-threaded download mechanism of a front-end page; real-time rendering of the downloaded model scenario file; The transmitting the parsed data to the server end for scenario processing to form the model scenario file comprises the following steps: when the number of components in the model parsed data exceeds a component number threshold or the memory data amount occupied by the model parsed data exceeds a memory data amount threshold, persistently exporting the model parsed data to a file and initiating a call to a backend service scenario interface to transmit the data to a backend server; scenario processing of the model parsed data based on the backend server to obtain the model scenario file; storing the model scenario file; The scenario processing of the model parsed data based on the backend server to obtain the model scenario file comprises the following steps: parsing component data in the model parsed data; when the component data is parsed, updating revit bounding box data of the revit model; updating a space tree, a system tree and a professional tree; The parsing of the component data in the model parsed data comprises the following steps: using multi-threading to parse information required by components; using multi-threading to parse components, performing node merging to merge nodes with the same material in a component into one node data; based on geometry index in the original node and matrix hascode value of the node, geometry reuse of the entire model is performed.

2. The method of claim 1, wherein, The extracting of the model original data through the plug-in API comprises the following steps: encapsulating a revit model interface through the plug-in API to obtain model original data including geometry data, attribute parameters and material information.

3. The method of claim 2, wherein the revit model is directly parsed and rendered. The parsing of the obtained model original data through the plug-in API to obtain the model parsed data comprises the following steps: identifying the model original data to obtain component data; performing geometry instantiation processing and model recombination on the component data to obtain the model parsed data.

4. The method of claim 3, wherein the revit model is directly parsed and rendered. The identifying of the model original data to obtain the component data comprises the following steps: traversing revit model components in the model original data, writing attributes, geometry and material of the revit model components into a linked list object, and comparing component geometry objects with linked list data, and repeated data is not written in; storing material texture maps as pictures; establishing a correspondence between the material texture maps and revit model component patches; using a Dwg plug-in to export drawing files in the model original data.

5. The method of claim 3, wherein the revit model is directly parsed and rendered. The geometry instantiation processing of the component data comprises the following steps: performing geometry instantiation processing on components with the same material and geometry; using a conversion matrix to record component position differences; merging components with the same material and different geometry into one component.

6. A revit model direct analysis and rendering system using the revit model direct analysis and rendering method according to any one of claims 1 to 5, characterized in that, The method comprises: a model original data obtaining module for extracting model original data through a plug-in API; a model original data parsing module in communication connection with the model original data obtaining module, for parsing the model original data to generate model parsed data; The scenario processing module is in communication connection with the plug-in initialization analysis module, and is configured to transmit analysis data to a server end for scenario processing to form a model scene file; The model scene file loading module is in communication connection with the scenario processing module, and is configured to load the model scene file through a multi-threaded download mechanism of a front-end page; The model rendering module is in communication connection with the model scene file loading module, and is configured to perform real-time rendering on the downloaded model scene file.

7. The Revit model direct parsing and rendering system of claim 6, wherein, The model original data acquisition module includes: The model original data acquisition unit is configured to encapsulate a revit model interface through a plug-in API to acquire model original data.

Images