Structured management method, device, computer equipment and storage medium for BIM data

Abstract

This invention provides a structured management method, apparatus, computer device, and storage medium for BIM data. The method includes: acquiring the correspondence between projects and work units, and storing the correspondence in a remote first storage device; the work unit is a component in the project determined based on preset rules, and the work unit consists of multiple components; acquiring attribute information of the components, and storing the attribute information in a remote second storage device; the attribute information includes any one or more of component type information, component parameter information, component shape information, and component relationship information; acquiring external data related to the components, and storing the external data in a remote third storage device; and in response to a target component acquisition command, acquiring corresponding data of the target component based on the first storage device, the second storage device, or the third storage device.

Description

Technical Field

[0001] The present invention relates to the field of BIM technology, and in particular to a structured management method, device, computer equipment and storage medium for BIM data. Background Art

[0002] BIM technology is gradually penetrating into various construction fields such as design, construction, operation and maintenance, and is playing an increasingly important role. At present, mainstream BIM software still organizes and saves design data in files, relying on files to share results in multi-professional cross-stage design. In addition, the file formats of BIM software from different manufacturers are not interoperable, and special converters need to be developed. The storage method based on files is inefficient when dealing with design changes. File-level sharing has slow transmission speeds due to the large amount of data. The conversion cost of file formats is high and information is easily lost, which largely prevents the interconnection of data in various disciplines and at various stages. The file format of data leads to relative isolation of information, which is not easy to meet the needs of big data consumption scenarios.

[0003] Therefore, how to provide a more flexible and convenient BIM data storage and data sharing method has become an urgent problem to be solved by technical personnel in this field. Summary of the invention

[0004] The purpose of the present invention is to provide a technical solution for structured management of BIM data to solve the above problems existing in the prior art.

[0005] To achieve the above object, the present invention provides a structured management method for BIM data, comprising the following steps:

[0006] Acquire a correspondence between a project and a work unit, and store the correspondence in a remote first storage device; the work unit is a component of the project determined based on a preset rule, and the work unit is composed of a plurality of components;

[0007] Acquire attribute information of the component, and store the attribute information in a remote second storage device; the attribute information includes any one or more of component type information, component parameter information, component shape information, and component relationship information;

[0008] Acquire external data related to the component, and store the external data in a remote third storage device;

[0009] In response to a target component acquisition command, corresponding data of the target component is acquired based on the first storage device, the second storage device or the third storage device.

[0010] According to the structured management method provided by the present invention, the step of acquiring corresponding data of the target component based on the first storage device, the second storage device or the third storage device in response to the target component acquisition command includes:

[0011] Determine the target working unit to which the target component belongs from the first storage device based on the first condition parameter of the target component, and determine the second condition parameter of the target component according to the target working unit;

[0012] querying the target attribute information of the target component from the second storage device based on the second condition parameter;

[0013] Determining target data corresponding to the target component according to the target attribute information; and / or

[0014] Target data corresponding to the target component is acquired from the third storage device according to the target attribute information.

[0015] According to the structured management method provided by the present invention, the step of acquiring corresponding data of the target component based on the first storage device, the second storage device or the third storage device in response to the target component acquisition command includes:

[0016] querying target attribute information of the target component from the second storage device based on a third condition parameter of the target component;

[0017] Determining target data corresponding to the target component according to the target attribute information; and / or

[0018] Target data corresponding to the target component is acquired from the third storage device according to the target attribute information.

[0019] According to the structured management method provided by the present invention, the method further comprises:

[0020] In response to a target work unit acquisition command, acquiring identification information and version information of the target work unit from the first storage device, the version information being used to indicate the number of times a component in the target work unit has been modified;

[0021] Based on the identification information and the version information, determining the latest version of the target component contained in the target work unit from the second storage device;

[0022] Acquire target attribute information of the target component from the second storage device;

[0023] Determining target data corresponding to the target component according to the target attribute information; and / or

[0024] Target data corresponding to the target component is acquired from the third storage device according to the target attribute information.

[0025] According to the structured management method provided by the present invention, the storage content of the target attribute information is coding information or address information, the coding information characterizes the attribute parameters of the component through a preset data dictionary, and the address information characterizes the storage address of the corresponding external data;

[0026] When the storage content of the target attribute information is coding information, the step of determining the target data corresponding to the target component according to the target attribute information includes: determining the target data corresponding to the coding information according to a preset data dictionary;

[0027] When the storage content of the target attribute information is address information, the step of determining the target data corresponding to the target component according to the target attribute information includes: acquiring the target data from a corresponding position of the third storage device according to the address information.

[0028] According to the structured management method provided by the present invention, the method further includes:

[0029] storing the corresponding relationship, the attribute information and the external data in a local cache;

[0030] Comparing the data stored in the local cache with the corresponding data in the client to obtain first verification information; the first verification information includes: whether the corresponding relationship stored in the local cache is consistent with the corresponding relationship stored in the client, whether the attribute information stored in the local cache is consistent with the attribute information stored in the client, and whether the external data stored in the local cache is consistent with the external data stored in the client;

[0031] Compare the data stored in the first storage device, the second storage device and the third storage device with the corresponding data stored in the client to obtain second verification information; the second verification information includes: whether the corresponding relationship stored in the first storage device is consistent with the corresponding relationship stored in the client, whether the attribute information stored in the second storage device is consistent with the attribute information stored in the client, and whether the external data stored in the third storage device is consistent with the external data stored in the client;

[0032] When the first verification information or the second verification information contains inconsistent information, a warning is sent.

[0033] According to the structured management method provided by the present invention, the first storage device is a relational database, the second storage device is a non-relational database, and the third storage device is an object storage device.

[0034] To achieve the above object, the present invention further provides a structured management device for BIM data, applicable to a client, comprising:

[0035] A first storage module is adapted to establish a correspondence between a project and a work unit, and store the correspondence in a remote first storage device; the work unit is a component of the project determined based on a preset rule, and the work unit is composed of a plurality of components;

[0036] A second storage module is adapted to obtain attribute information of the component and store the attribute information in a remote second storage device; the attribute information includes any one or more of component type information, component parameter information, component shape information, and component relationship information;

[0037] A third storage module, adapted to obtain external data related to the component and store the external data in a remote third storage device;

[0038] The data acquisition module is adapted to acquire corresponding data of the target component based on the first storage device, the second storage device or the third storage device in response to a target component acquisition command.

[0039] To achieve the above objectives, the present invention also provides a computer device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the steps of the above method when executing the computer program.

[0040] To achieve the above object, the present invention also provides a computer-readable storage medium on which a computer program is stored, and the computer program implements the steps of the above method when executed by a processor.

[0041] The structured management method, device, computer equipment and storage medium of BIM data provided by the present invention can avoid the drawbacks of traditional file management, greatly improve the efficiency of BIM design, strengthen the advantages of BIM design, and release the potential of BIM data to the maximum extent. Compared with the prior art, the present invention has at least the following beneficial effects:

[0042] 1. Structured storage breaks through the limitations of files and makes deep data consumption possible;

[0043] 2. The incremental mechanism of component granularity can reduce the amount of data transmission and improve the efficiency of design changes;

[0044] 3. Component-level data verification and correction ensure data reliability;

[0045] 4. Standardized data eliminates obstacles to the interconnection and interoperability of data across multiple disciplines and stages. BRIEF DESCRIPTION OF THE DRAWINGS

[0046] Figure 1 This is a flow chart of Embodiment 1 of the structured management method for BIM data of the present invention;

[0047] Figure 2 A schematic diagram of BIM data division granularity according to the first embodiment of the present invention is shown;

[0048] Figure 3 A schematic diagram showing the storage relationship among the first storage device, the second storage device and the third storage device in this embodiment is shown;

[0049] Figure 4 A schematic flow chart of obtaining corresponding data of a target component in Embodiment 1 of the present invention is shown;

[0050] Figure 5 A schematic diagram of a data standard dictionary encoding framework according to a first embodiment of the present invention is shown;

[0051] Figure 6 A schematic diagram of coding information according to the first embodiment of the present invention is shown;

[0052] Figure 7 Another schematic flow chart of obtaining a target component in the first embodiment of the present invention is shown;

[0053] Figure 8 A schematic diagram showing modification of a working unit in the first embodiment of the present invention is shown;

[0054] Fig. 9 A schematic flow chart of data verification in the first embodiment of the present invention is shown;

[0055] Fig.10 A modular schematic diagram of performing data verification in the first embodiment of the present invention is shown;

[0056] Fig.11 A schematic diagram of program modules of a first embodiment of a structured management device of the present invention is shown;

[0057] Fig.12 A schematic diagram of the hardware structure of the first embodiment of the structured management device of the present invention is shown. DETAILED DESCRIPTION

[0058] In order to make the purpose, technical scheme and advantages of the present invention more clearly understood, the present invention is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present invention and are not intended to limit the present invention. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present invention.

[0059] Embodiment 1

[0060] This embodiment is used to manage BIM data from the client to achieve structured storage and sharing. The above-mentioned client provides users with input and output of BIM data, such as receiving BIM data input by the user, or outputting corresponding BIM data to the user. This embodiment provides an API interface with the above-mentioned client to achieve structured storage of BIM data from the client, and return BIM data that meets the user's requirements to the client.

[0061] See also Figure 1 This embodiment proposes a structured management method for BIM data, comprising the following steps:

[0062] S100: Obtain the correspondence between the project and the work unit, and store the correspondence in a remote first storage device; the work unit is a component of the project determined based on a preset rule, and the work unit is composed of multiple components.

[0063] The project can be the overall task of a certain construction project, such as the construction task of building a residential building or an office building. The project can be divided into multiple work units based on different preset rules as needed. For example, according to the floor, a residential building can be divided into the first floor, the second floor, ..., the nth floor. The above residential building corresponds to the project in this embodiment, and the nth floor corresponds to the work unit in this embodiment. For another example, according to the structure, a residential building can be divided into masonry wall structure, beam structure, column structure, etc. The above masonry wall structure, beam structure, and column structure also correspond to different work units respectively. It can be understood that when the preset rules are different, the work units of the same project are also different, and this embodiment does not limit it. Furthermore, each work unit is composed of multiple components, and each component has its own attributes. Figure 2 The schematic diagram of the granularity of BIM data in this embodiment is shown. Figure 2 It can be seen that each engineering project contains one or more work units, each work unit contains one or more components, and each component contains one or more attributes.

[0064] The correspondence between the project and the work unit may include the project number and the numbers of all the work units under the project. For example, a project number is 10, and its divided work units include work unit 101, work unit 102, work unit 103, etc. The mapping relationship between the above work units and projects is the corresponding relationship referred to in this embodiment. Since the memory capacity of the client itself is limited, in order to unify management and maintenance, the increasing BIM data needs to be fixedly stored. After receiving the above correspondence input by the client, this embodiment stores the correspondence in a remote first storage device. Preferably, the first storage device is a relational database, such as a MySQL database. The correspondence between the project and the work unit is stored in a relational database, so that the logical relationship between the project and the work unit is clear and easy to maintain.

[0065] S200: Acquire attribute information of the component, and store the attribute information in a remote second storage device; the attribute information includes any one or more of component type information, component parameter information, component shape information, and component relationship information.

[0066] The attribute information is used to specifically characterize the characteristics of the component, and may specifically include any one of the component type information, component parameter information, component shape information, and component relationship information. Among them, the component type information is used to describe the classification or name of the component, such as masonry wall, beam, column, etc.; the component parameter information is used to describe the size of the component, such as length, width, height, etc.; the component shape information is used to display the spatial three-dimensional shape of the component through graphics; the component relationship information is used to describe the relationship between two components, such as the dependency relationship between a door opening and the wall it depends on, the subtraction relationship between a beam and a column, etc. This embodiment does not limit the specific composition of the relationship.

[0067] It is understandable that the number of components involved in the engineering project is very large, and the amount of data of the corresponding attribute information is also large. In this embodiment, the attribute information of the component obtained by the client is stored in a remote second storage device, preferably a non-relational database, such as a key-value database. Non-relational databases have better scalability than relational databases, and are therefore more suitable for storing attribute information with a higher frequency of changes, which is conducive to real-time modification and maintenance of data.

[0068] It should be noted that each piece of attribute information stored in the second storage device may include work unit ID, component ID, version number, coding information or address information. The work unit ID represents the unique identifier of the work unit to which the component belongs, the component ID represents the unique identifier of the component itself, the version number is used to represent the number of modifications of the corresponding work unit, the coding information represents the attribute parameters of the component through a preset data dictionary, and the address information represents the storage address of the corresponding external data. For the coding information, this embodiment will be described in detail later; for the address information, it is usually related to the component shape information. When the data volume of the component shape information is large, the metadata is not directly stored, but the address information of the corresponding metadata is stored, so that the corresponding metadata can be indirectly obtained according to the address information. By using coding information or address information to represent the attribute information of the component, the amount of data in the second storage device can be effectively reduced and the storage space can be optimized.

[0069] S300: Acquire external data related to the component, and store the external data in a remote third storage device.

[0070] External data related to components may include different three-dimensional model data, such as Mesh data, that is, the graphical expression data of the component. This type of data usually takes up a large storage space, such as the component shape information mentioned above. In addition, external data may also include infrequently used cold data, historical version data, etc., which are not limited in this embodiment. In order to facilitate maintenance and management, this embodiment stores the above-mentioned three-dimensional model data in a remote third storage device. Preferably, the third storage device is an object storage device. Compared with relational databases and non-relational databases, object storage devices have a simpler and more flexible storage method and have the advantages of easy expansion and low cost.

[0071] S400: In response to a target component acquisition command, acquiring corresponding data of the target component based on the first storage device, the second storage device or the third storage device.

[0072] As can be seen from the above, the first storage device, the second storage device and the third storage device contain all information related to the engineering project, including the correspondence between the project and the work unit, the attribute information of the component and the external data. When the user needs to obtain certain target components, a target component acquisition command can be sent to the client. In this embodiment, upon receiving the command, the first storage device, the second storage device or the third storage device can accurately and quickly obtain the corresponding data. Figure 3 FIG. 2 shows a schematic diagram of the storage relationship among the first storage device, the second storage device and the third storage device in this embodiment. Figure 3As shown, the first storage device is used to store projects and work units and their corresponding relationships, the second storage device is used to store component type information, component parameter information, component shape information and component relationship information, etc., and the third storage device is used to store external files or other cold data.

[0073] Through the above steps, this embodiment performs structured management and storage of BIM data at the component granularity. Different users can selectively obtain relevant data of any target component according to their needs, effectively improving the utilization rate of BIM data.

[0074] Figure 4 FIG. 1 shows a schematic flow chart of obtaining a target component in Embodiment 1 of the present invention. Figure 4 As shown, step S400 includes:

[0075] S410: Determine a target working unit to which the target component belongs from the first storage device based on a first condition parameter of the target component, and determine a second condition parameter of the target component according to the target working unit.

[0076] The first conditional parameter may be a query condition in a command to obtain a target component. When the query condition is relatively broad, the target work unit may be first determined through this step. For example, the first conditional parameter is to query all components contained in the first floor of a residential building. In this case, the work unit identifier corresponding to the first floor of the residential building may be first determined from the first storage device according to the correspondence between the project and the work unit, such as GZDY001. This identifier may be used as the second conditional parameter of the target component, that is, all components belonging to the work unit identified as GZDY001.

[0077] S420: Query the target attribute information of the target component from the second storage device based on the second condition parameter.

[0078] As mentioned above, since the attribute information in the second storage device may include work unit ID, component ID, version number, encoding information or address information, etc., the target attribute information of all corresponding components can be obtained through the determined work unit ID, namely GZDY001.

[0079] S430: Determine target data corresponding to the target component according to the target attribute information.

[0080] In the case where the attribute information of the component includes coding information, this step determines the target data corresponding to the coding information according to the preset data dictionary. In order to reduce the barriers to the interconnection and intercommunication of multi-professional and cross-stage data, the present invention standardizes BIM data, and all parties produce and consume data through a data standard dictionary. Figure 5FIG. 1 shows a schematic diagram of a data standard dictionary encoding framework according to an embodiment of the present invention. Figure 5 As shown, the data dictionary encodes the classification system and attributes that need to be exchanged, so that data expression can be unified across disciplines and stages. Taking the structural wall "31-211300" as an example, the beginning "31" represents the entity classification, the following "21" represents the structural discipline, "13" represents the structural wall, and "00" represents the subclass. Taking the attribute "classification code (4311117)" as an example, this code expresses that the attribute is in the "design attribute (43)" and belongs to the attribute in the "element classification (11)" in the "design identification (11)". In this way, based on the encoding information obtained in the attribute information, the user can determine the specific target data based on the data dictionary. Figure 6 FIG. 1 shows a schematic diagram of coding information according to Embodiment 1 of the present invention. Figure 6 It can be seen that different components have different coding information. For example, the coding of the structural wall is 31-211300, and the coding of the structural wall opening is 31-212810, etc.

[0081] S440: Acquire target data corresponding to the target component from the third storage device according to the target attribute information.

[0082] In the case where the attribute information of the component includes address information, this step obtains the target data from the corresponding position of the third storage device according to the address information. As mentioned above, the third storage device can store external data such as component shape information with a large amount of data, and the specific storage address of the component shape information in the third storage device can be included in the attribute information of the second storage device. Thus, according to the address information in the attribute information, the target data corresponding to the target component can be obtained.

[0083] The above steps can realize flexible access to the data stored in the second storage device and the third storage device, thereby quickly acquiring the target component and improving the user experience.

[0084] Figure 7 FIG. 2 shows another schematic flow chart of obtaining a target component in Embodiment 1 of the present invention. Figure 6 As shown, step S400 includes:

[0085] S410′: Query target attribute information of the target component from the second storage device based on the third condition parameter of the target component.

[0086] The third condition parameter may be a query condition in the command to obtain the target component. When the query condition is more specific, the target attribute information corresponding to the target component can be directly obtained through this step. For example, the third condition parameter is a target component whose query component ID is specifically XXX. In this case, the corresponding target attribute information can be directly obtained from the second storage device according to the component ID of XXX.

[0087] S420′: Determine target data corresponding to the target component according to the target attribute information.

[0088] This step is applicable to the case where the attribute information of the component includes coding information, and is similar to step S430, and will not be repeated herein.

[0089] S430′: Acquire target data corresponding to the target component from the third storage device according to the target attribute information.

[0090] This step is applicable to the case where the attribute information of the component includes address information, and is similar to step S440, and will not be repeated herein.

[0091] It is understandable that it is inevitable to modify the attribute information of components during the design and construction process. In this embodiment, the version information corresponding to each modification can be saved in the first storage device at the same time. Specifically, the version information may include a version number and an incremental component corresponding to a certain work unit. The version number is used to characterize the number of modifications, and the incremental component is used to characterize which components have changed in this modification. Changes in components may include component modifications, component additions, and component deletions. In some examples, component modifications and component additions may also be collectively referred to as component changes. In this case, component changes include two categories: component changes and component deletions. Figure 8 FIG. 1 is a schematic diagram showing a modification of a working unit in the first embodiment of the present invention. Figure 8 As shown, work unit A has 3 versions. Version 1 has 6 components, namely E1, E2, E3, E4, E5 and E6. Version 2 has modified E3, deleted E2 and added E11. Then version 2 only needs to save E3 and E11 and mark E2 as deleted. Version 3 has modified E4 and E5 and deleted E6. Then version 3 only needs to save E4 and E5 and mark E6 as deleted. Through the incremental superposition rule, the full components from version 1 to version 3 are E1, E3, E4, E5 and E11. In this way, in the process of each component modification, this embodiment does not need to save all the data of each modified version, but only saves the incremental components that have changed, and determines all the components contained in the latest version of the work unit according to the incremental superposition rule, thereby effectively reducing the amount of data storage and improving data acquisition efficiency.

[0092] In one example, this embodiment further includes a data verification process. Fig. 9 The structured management method of the first embodiment of the present invention further includes:

[0093] S500: Storing the corresponding relationship, the attribute information and the external data in a local cache.

[0094] In order to speed up data synchronization, the present invention also adds cache management, saves the memory data of the design client in the cache in an incremental manner, and then uploads it from the cache to the cloud database asynchronously in segments.

[0095] S600: Compare the data stored in the local cache with the corresponding data in the client to obtain first verification information; the first verification information includes: whether the corresponding relationship stored in the local cache is consistent with the corresponding relationship stored in the client, whether the attribute information stored in the local cache is consistent with the attribute information stored in the client, and whether the external data stored in the local cache is consistent with the external data stored in the client.

[0096] In order to ensure the integrity of the data in the entire transmission link, this embodiment provides a double data verification mechanism, which is based on the design of the client's memory data. The first verification occurs between the client's memory data and the cache. Once data inconsistency is found, the cache can be corrected through the memory model, thereby repairing the human problems that occur during incremental collection and cache processing.

[0097] S700: Compare the data stored in the first storage device, the second storage device and the third storage device with the corresponding data stored in the client to obtain second verification information; the second verification information includes: whether the corresponding relationship stored in the first storage device is consistent with the corresponding relationship stored in the client, whether the attribute information stored in the second storage device is consistent with the attribute information stored in the client, and whether the external data stored in the third storage device is consistent with the external data stored in the client.

[0098] The above steps are the second level of verification of the transmission link, that is, to verify whether the data in the client's memory is consistent with the data in the remote database. If the data is found to be inconsistent, the corresponding version will be marked as unhealthy to prevent the "bad" data from being further used and consumed.

[0099] Fig.10 FIG. 1 shows a modular schematic diagram of data verification in the first embodiment of the present invention. Fig.10As shown, the GCMP model refers to the corresponding relationship, attribute information and external data stored in the client, and the incremental data related to the above corresponding relationship, attribute information and external data are saved to the local cache, and the data in the local cache is automatically corrected with the data in the GCMP memory model to obtain the first verification information. Further, the data in the local cache is uploaded to the remote database (including the first storage device, the second storage device and the third storage device) in segments, and the data in the remote database is compared with the data in the GCMP memory model to obtain the second verification information.

[0100] S800: Send a warning when the first verification information or the second verification information contains inconsistent information.

[0101] Through the above steps, the reliability of data can be further guaranteed, providing strong support for the accurate sharing of BIM data.

[0102] Please continue reading Fig.11 , shows a structured management device for BIM data. In this embodiment, the structured management device 110 may include or be divided into one or more program modules, one or more program modules are stored in a storage medium and executed by one or more processors to complete the present invention and implement the above-mentioned structured management method. The program module referred to in the present invention refers to a series of computer program instruction segments that can complete specific functions, which is more suitable for describing the execution process of the structured management device 110 in the storage medium than the program itself. The following description will specifically introduce the functions of each program module in this embodiment:

[0103] The first storage module 111 is adapted to establish a correspondence between a project and a work unit, and store the correspondence in a remote first storage device; the work unit is a component of the project determined based on a preset rule, and the work unit is composed of a plurality of components;

[0104] The second storage module 112 is adapted to obtain attribute information of the component and store the attribute information in a remote second storage device; the attribute information includes any one or more of component type information, component parameter information, component shape information and component relationship information;

[0105] A third storage module 113, adapted to obtain external data related to the component and store the external data in a remote third storage device;

[0106] The data acquisition module 114 is adapted to acquire corresponding data of the target component based on the first storage device, the second storage device or the third storage device in response to a target component acquisition command.

[0107] This embodiment also provides a computer device, such as a smart phone, tablet computer, laptop computer, desktop computer, rack server, blade server, tower server or cabinet server (including an independent server or a server cluster composed of multiple servers) that can execute programs. The computer device 120 of this embodiment includes at least but is not limited to: a memory 121 and a processor 122 that can communicate with each other via a system bus, such as Fig.12 It should be pointed out that Fig.12 Only computer device 120 is shown with components 121 - 122 , but it should be understood that implementing all of the components shown is not a requirement, and more or fewer components may alternatively be implemented.

[0108] In this embodiment, the memory 121 (i.e., readable storage medium) includes flash memory, hard disk, multimedia card, card-type memory (e.g., SD or DX memory, etc.), random access memory (RAM), static random access memory (SRAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), programmable read-only memory (PROM), magnetic memory, magnetic disk, optical disk, etc. In some embodiments, the memory 121 can be an internal storage unit of the computer device 120, such as a hard disk or memory of the computer device 120. In other embodiments, the memory 121 can also be an external storage device of the computer device 120, such as a plug-in hard disk equipped on the computer device 120, a smart memory card (Smart Media Card, SMC), a secure digital (Secure Digital, SD) card, a flash card (Flash Card), etc. Of course, the memory 121 can also include both the internal storage unit of the computer device 120 and its external storage device. In this embodiment, the memory 121 is generally used to store the operating system and various application software installed on the computer device 120, such as the program code of the structured management device 110 of the first embodiment. In addition, the memory 121 can also be used to temporarily store various types of data that have been output or are to be output.

[0109] In some embodiments, the processor 122 may be a central processing unit (CPU), a controller, a microcontroller, a microprocessor, or other data processing chips. The processor 122 is generally used to control the overall operation of the computer device 120. In this embodiment, the processor 122 is used to run the program code stored in the memory 121 or process data, such as running the structured management device 110 to implement the structured management method of the first embodiment.

[0110] This embodiment also provides a computer-readable storage medium, such as a flash memory, a hard disk, a multimedia card, a card-type memory (e.g., an SD or DX memory, etc.), a random access memory (RAM), a static random access memory (SRAM), a read-only memory (ROM), an electrically erasable programmable read-only memory (EEPROM), a programmable read-only memory (PROM), a magnetic memory, a disk, an optical disk, a server, an App application store, etc., on which a computer program is stored, and the program implements a corresponding function when executed by a processor. The computer-readable storage medium of this embodiment is used to store the structured management device 80, and implements the structured management method of embodiment 1 when executed by the processor.

[0111] The serial numbers of the above embodiments of the present invention are only for description and do not represent the advantages or disadvantages of the embodiments.

[0112] Any process or method description in a flowchart or otherwise described herein may be understood to represent a module, segment or portion of code that includes one or more executable instructions for implementing the steps of a specific logical function or process, and the scope of the preferred embodiments of the present invention includes alternative implementations in which functions may not be performed in the order shown or discussed, including performing functions in a substantially simultaneous manner or in the reverse order depending on the functions involved, which should be understood by those skilled in the art to which the embodiments of the present invention belong.

[0113] A person of ordinary skill in the art can understand that all or part of the steps carried out in the above-mentioned embodiment method can be completed by instructing related hardware through a program, and the program can be stored in a computer-readable medium. When the program is executed, it includes one of the steps of the method embodiment or a combination thereof.

[0114] In the description of this specification, the description with reference to the terms "one embodiment", "some embodiments", "example", "specific example" or "some examples" etc. means that the specific features, structures, materials or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the present invention. In this specification, the schematic representations of the above terms do not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described may be combined in any one or more embodiments or examples in a suitable manner.

[0115] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above embodiment methods can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method.

[0116] The above are only preferred embodiments of the present invention, and are not intended to limit the patent scope of the present invention. Any equivalent structure or equivalent process transformation made using the contents of the present invention specification and drawings, or directly or indirectly applied in other related technical fields, are also included in the patent protection scope of the present invention.

Claims

1. A structured management method for BIM data, characterized in that: The following steps are involved: Acquire a correspondence between the project and the work unit, and store the correspondence in a remote first storage device; The work unit is a component of the project determined based on a preset rule, and the work unit is composed of a plurality of components; Acquire attribute information of the component, and store the attribute information in a remote second storage device; the attribute information includes any one or more of component type information, component parameter information, component shape information, and component relationship information; Acquire external data related to the component, and store the external data in a remote third storage device; In response to a target component acquisition command, acquiring corresponding data of the target component based on the first storage device, the second storage device or the third storage device, comprising: Based on the first condition parameter of the target component, the target working unit to which the target component belongs is determined from the first storage device, and the working unit identifier of the target working unit is used as the second condition parameter of the target component; wherein the first condition parameter is a query condition in a command to obtain the target component; based on the second condition parameter, the target attribute information of the target component is queried from the second storage device; wherein the target attribute information includes at least one of the following: working unit ID, component ID, version number, coding information, address information; when the target attribute information contains coding information, the target data corresponding to the coding information is determined according to a preset data dictionary; when the target attribute information contains address information, the target data is obtained from the corresponding position of the third storage device according to the address information; wherein the target data is component shape information; or, The target attribute information of the target component is queried from the second storage device based on the third condition parameter of the target component; wherein the third condition parameter is a query condition in a command to obtain the target component; the target attribute information includes at least one of the following: work unit ID, component ID, version number, coding information, address information; when the target attribute information includes coding information, the target data corresponding to the coding information is determined according to a preset data dictionary; when the target attribute information includes address information, the target data is obtained from a corresponding position of the third storage device according to the address information; wherein the target data is component shape information.

2. The structured management method according to claim 1, characterized in that: The method further comprises: In response to a target work unit acquisition command, acquiring identification information and version information of the target work unit from the first storage device, the version information being used to indicate the number of times a component in the target work unit has been modified; Based on the identification information and the version information, determining the latest version of the target component contained in the target work unit from the second storage device; Acquire target attribute information of the target component from the second storage device; Determining target data corresponding to the target component according to the target attribute information; and / or Target data corresponding to the target component is acquired from the third storage device according to the target attribute information.

3. The structured management method according to claim 1, characterized in that: The method further comprises: storing the corresponding relationship, the attribute information and the external data in a local cache; Comparing the data stored in the local cache with the corresponding data in the client to obtain first verification information; the first verification information includes: whether the corresponding relationship stored in the local cache is consistent with the corresponding relationship stored in the client, whether the attribute information stored in the local cache is consistent with the attribute information stored in the client, and whether the external data stored in the local cache is consistent with the external data stored in the client; Compare the data stored in the first storage device, the second storage device and the third storage device with the corresponding data stored in the client to obtain second verification information; the second verification information includes: whether the corresponding relationship stored in the first storage device is consistent with the corresponding relationship stored in the client, whether the attribute information stored in the second storage device is consistent with the attribute information stored in the client, and whether the external data stored in the third storage device is consistent with the external data stored in the client; When the first verification information or the second verification information contains inconsistent information, a warning is sent.

4. The structured management method according to claim 1, characterized in that: The first storage device is a relational database, the second storage device is a non-relational database, and the third storage device is an object storage device.

5. A structured management device for BIM data, characterized in that: include: A first storage module, adapted to establish a correspondence between projects and work units, and store the correspondence in a remote first storage device; The work unit is a component of the project determined based on a preset rule, and the work unit is composed of a plurality of components; A second storage module is adapted to obtain attribute information of the component and store the attribute information in a remote second storage device; the attribute information includes any one or more of component type information, component parameter information, component shape information, and component relationship information; A third storage module, adapted to obtain external data related to the component and store the external data in a remote third storage device; A data acquisition module, adapted to acquire corresponding data of the target component based on the first storage device, the second storage device or the third storage device in response to a target component acquisition command; Wherein, the data acquisition module is also applicable to: Based on the first condition parameter of the target component, the target working unit to which the target component belongs is determined from the first storage device, and the working unit identifier of the target working unit is used as the second condition parameter of the target component; wherein the first condition parameter is a query condition in a command to obtain the target component; based on the second condition parameter, the target attribute information of the target component is queried from the second storage device; wherein the target attribute information includes at least one of the following: working unit ID, component ID, version number, coding information, address information; when the target attribute information contains coding information, the target data corresponding to the coding information is determined according to a preset data dictionary; when the target attribute information contains address information, the target data is obtained from the corresponding position of the third storage device according to the address information; wherein the target data is component shape information; or, The target attribute information of the target component is queried from the second storage device based on the third condition parameter of the target component; wherein the third condition parameter is a query condition in a command to obtain the target component; the target attribute information includes at least one of the following: work unit ID, component ID, version number, coding information, address information; when the target attribute information includes coding information, the target data corresponding to the coding information is determined according to a preset data dictionary; when the target attribute information includes address information, the target data is obtained from a corresponding position of the third storage device according to the address information; wherein the target data is component shape information.

6. A computer device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 4 are implemented.

7. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 4 are implemented.

Images