Parameter-based construction

Abstract

A computer-implemented method (900) for constructing a building (124), comprising receiving (903) an input specification (104) for the building, the input specification specifying pre-harmonized modules (129', 127', 141') required to construct the building, the pre-harmonized modules being defined by respective pre-harmonized module specifications (103, 102, 101, 147) including respective geometric parameters (1001, 1102, 1201) and respective attributes (1002, 1102, 1202); and identifying (905) pre-harmonized module specifications stored in an electronically accessible database (110), the identified pre-harmonized module specifications a first pre-harmonized module specification having associated geometric parameters and attributes stored in separate sections of a database; harmonizing (300, 400, 500, 600) module specifications of the first pre-harmonized module specification to form a set (120) of harmonized module specifications (129, 127, 141) that specify harmonized modules that (a) will have little or no collisions when used to construct a building (124) and (b) will satisfy attribute criteria specified in the input specification (104) when assembled to form the building (124); and constructing (911) the building (124) using the module specifications (120).

Description

[Technical Field]

[0001] This invention generally relates to the field of building construction methods, and more particularly to improving the efficiency of building construction, from relatively simple single-story buildings to skyscrapers. Furthermore, this invention relates to methods and apparatus for improving the efficiency of building construction, and to computer program products having a computer-readable medium on which a computer program for improving the efficiency of building construction is recorded. [Background technology]

[0002] Numerous Building Information Modeling (BIM) software programs are currently available to assist architecture, engineering, and construction (AEC) professionals in planning, designing, and constructing buildings and infrastructure. However, current building construction methods still require significant on-site adjustments to adapt building modules and meet required specifications. [Overview of the project] [Problems that the invention aims to solve]

[0003] The object of the present invention is to sufficiently eliminate or at least improve one or more drawbacks of existing arrangements. [Means for solving the problem]

[0004] A deployment called Harmonised Parameter Based Design for Manufacture and Assembly (HPDMI) deployment has been disclosed, which attempts to address the aforementioned problems by providing a cloud-based platform through which participants in the entire construction space, from architects to all necessary tradespeople and building certification bodies, can (A) access and populate an electronically accessible construction catalog containing a hierarchical collection of parts, assemblies, master assemblies, etc. that can be used as standard elements of construction; (B) access an industry-approved third-party software platform used to create, analyze, and process such standardized elements; and (C) harmonize elements generated and selected from the catalog for a specific construction project, ensuring that the generated and selected elements (i) have minimal conflicts when used to construct the building and (ii) meet attribute criteria specified in the input specifications when assembled to constitute the building. In other words, the disclosed HPDMI deployment allows building modules to be manufactured remotely and assembled on-site to form the desired building, with significantly less on-site adjustment required to adapt the building modules and meet specified attributes than with current building construction methods.

[0005] According to a first aspect of this disclosure, a computer execution method for constructing a building, A step of receiving input specifications for a building, wherein the input specifications specify the pre-harmonization modules required to construct the building, and the pre-harmonization modules are defined by each pre-harmonization module specification, which includes their respective geometric parameters and respective attributes. A step of identifying pre-harmonization module specifications that are stored in an electronically accessible database, wherein the identified pre-harmonization module specifications are referred to as first pre-harmonization module specifications having relevant geometric parameters and attributes stored in separate sections of the database, (a) Harmonizing the module specifications of a first pre-harmonization module specification in order to form a set of harmonized module specifications that specify harmonized modules that have little to no conflict when used to construct a building, and (b) satisfy attribute criteria specified in the input specification when assembled to form a building, Steps to construct a building using harmonious modular specifications, This provides a method for providing this.

[0006] Another aspect of this disclosure provides an apparatus for carrying out any one of the methods described above.

[0007] Another aspect of this disclosure provides a computer program product having a computer-readable medium recording a computer program for performing any one of the methods described above.

[0008] Other aspects will also be disclosed. [Brief explanation of the drawing]

[0009] Next, preferred embodiments of the present invention will be described only as examples with reference to the drawings.

[0010] [Figure 1] Figure 1 shows a functional block diagram of an example of the disclosed HPDMI configuration.

[0011] [Figure 2A] Figure 2A shows a schematic block diagram of a general-purpose computer system capable of implementing the HPDMI configuration described above. [Figure 2B] Figure 2B shows a schematic block diagram of a general-purpose computer system capable of implementing the HPDMI configuration described above.

[0012] [Figure 3] Figure 3 is an exemplary flowchart of the component-based HPDMI harmonization process.

[0013] [Figure 4] Figure 4 is an example of a flowchart of an assembly-based HPDMI harmonization process.

[0014] [Figure 5] Figure 5 is an exemplary flowchart for a master-assembly-based HPDMI harmonization process.

[0015] [Figure 6] Figure 6 shows an example of a flowchart of an HPDMI geometric parameter and attribute harmonization process used in the processes of FIGS. 3, 4, and 5.

[0016] [Figure 7] Figure 7 shows an exemplary flowchart of a process for executing an HPDMI process using the processes of FIGS. 3, 4, and 5.

[0017] [Figure 8] Figure 8 shows a simplified example of HPDMI in which the harmonization process is applied only to geometric parameters for simplicity of explanation.

[0018] [Figure 9] Figure 9 is a flowchart of an example of a process for executing an HPDMI process. <H

[0019] [Figure 10] Figure 10 shows an example 1000 of a part-based segment of the database 110.

[0020] [Figure 11] Figure 11 shows an example 1100 of an assembly-based segment of the database 110.

[0021] [Figure 12] Figure 12 shows an example 1200 of a master-assembly-based segment of the database 110.

[0022] [Figure 13] Figure 13 is a general representation of building 1300 formed from an arrangement of parts.

[0023] [Figure 14] Figure 14 shows an exemplary flowchart for a component-based HPDMI harmonization process according to another preferred embodiment.

[0024] [Figure 15A] Figure 15A shows an example of the process shown in Figure 14. [Figure 15B] Figure 15B shows an example of the process shown in Figure 14. [Figure 15C] Figure 15C shows an example of the process shown in Figure 14. [Figure 15D] Figure 15D shows an example of the process shown in Figure 14. [Figure 15E] Figure 15E shows an example of the process shown in Figure 14.

[0025] [Figure 16] Figure 16 shows an exemplary flowchart for an assembly-based HPDMI harmonization process according to a preferred embodiment of Figure 14.

[0026] [Figure 17A] Figure 17A shows the assembly created by the process in Figure 16. [Figure 17B] Figure 17B shows the assembly created by the process in Figure 16.

[0027] [Figure 18] Figure 18 shows an exemplary flowchart for a project-based HPDMI harmonization process according to a preferred embodiment of Figure 14.

[0028] [Figure 19] Figure 19 shows an exemplary example of the HPDMI harmonization process of a preferred embodiment shown in Figure 14.

[0029] [Figure 20] Figure 20 shows an example of building a parameter catalog using the HPDMI harmonization process in a preferred embodiment of Figure 14.

[0030] APPENDIX A provides examples of third-party software applications that can be used with the disclosed HPDMI deployment when used to construct a building. [Modes for carrying out the invention]

[0031] Where any one or more of the attached drawings reference a step and / or form having the same reference numeral, that step and / or form shall, unless otherwise intended, have the same function or action for the purposes of this description.

[0032] It should be noted that the discussions included in the "Background" section and the above sections concerning the arrangement of prior art relate to discussions of documents or devices that may form public knowledge through their respective publications and / or use. Such discussions should not be interpreted as a statement by one or more inventors or patent applicants that such documents or devices form in any way part of the common general knowledge in the art.

[0033] Figure 1 shows a functional block diagram 100 of an example of the disclosed HPDMI configuration. In use, in one example, one or more architects (not shown) commissioned to design building 124 create an input specification 104 that specifies the building using one or more of (A) building specification 147, (B) component specification 103, (C) assembly specification 102, and (D) master assembly specification 101.

[0034] Therefore, for example, an architect can provide an input specification 104 for a building 124 (which is a school in this example) in the form of a building specification 147, which includes complete school drawings or, more likely, a 3D model. The building specification 147 may have a wide range of geometric specifications, such as the length of the building, the offset from the boundary, and the height of the building.

[0035] Alternatively, input specification 104 may be provided by the architect at the master assembly level, and therefore, in this example, may consist of drawings of each complete classroom, which may also be master assembly specification 101.

[0036] Therefore, the HPDMI configuration described allows the architect's input specifications 104 for the building to be provided at any one or more of the four levels of the configuration described. However, obviously, different numbers of hierarchical levels can be used depending on the size of the building 124.

[0037] The HPDMI configuration described involves iterative combination / decomposition of specific combinations of building specification 147, master assembly specification 101, assembly specification 102, and component specification to generate components at the atomic level for the parameters. The geometric parameters and attributes for each parameter of the relevant level of specification are stored in the HPDMI database 110 for later use. This allows, for example, the specifications in the database to be used as building blocks to reconstruct the same school or different buildings, as will be explained in more detail later with reference to Figure 1.

[0038] As will be explained in more detail later, specifications 147, 103, 102, and 101 specify parts, assemblies, and master assemblies, respectively, with a degree of preliminary precision that is not yet suitable for the manufacture, assembly, and construction of building 124. Part specification 103, assembly specification 102, and master assembly specification 101 of input specification 104 are referred to as pre-harmonization module specifications.

[0039] To ensure that the part specifications, assembly specifications, and master assembly specifications have the necessary precision for the manufacture, assembly, and construction of building 124, one or more designers 111 use the HPDMI system 100 to process input specifications 104, including pre-harmonization specifications 103 for parts, pre-harmonization specifications 102 for assemblies, and pre-harmonization specifications 101 for master assemblies, and create output specifications specifying part specifications 119, assembly specifications 118, and master assembly specifications 117 with the necessary precision for the manufacture, assembly, and construction of building 124. The part specifications 119, assembly specifications 118, and master assembly specifications 117 of the output module specification 120 are referred to as harmonized module specifications. This process of setting the harmonization of geometric parameters and attributes will be described in more detail later with reference to Figure 6.

[0040] In this specification, unless otherwise expressed, the terms “assemble” and “construct.” While this specification describes an HPDMI configuration example in relation to the construction of building 124, the HPDMI configuration can be used to construct a wider range of articles.

[0041] As described above, HPDMI configuration uses a hierarchical arrangement of modules called parts, assemblies, and master assemblies. An example of a part is part 129, which is a perforated plate. An example of an assembly is assembly 127, which consists of plate 129, two fasteners, and part of a tube. An example of a master assembly is master assembly 141, which is a complete roof section as seen in building 124. Building 124 is constructed from harmonized parts such as 129, harmonized assemblies such as 127, and harmonized master assemblies such as 141.

[0042] The input specification 104 consists of a module specification having a component specification 103 and / or an assembly specification 102 and / or a master assembly specification 101. An example of a component specification is the specification for component 129 in Figure 1. An example of an assembly specification is the specification for assembly 127 in Figure 1. An example of a master assembly specification is the specification for master assembly 141 in Figure 1. The building 124 may be constructed using one or more of the component specification 103, assembly specification 102, and master assembly specification 101.

[0043] A key element of the disclosed HPDMI configuration is the “existing” electronically accessible HPDMI database or catalog 110, which continuously stores part specifications, assembly specifications, and master assembly specifications for future use. Although not shown, the catalog 110 can be formed from harmonized parts 103, assemblies 102, and master assemblies 101, and it is understood that each element of the catalog can be stored in a digital blockchain ledger such as Ethereum. In this way, each cataloged component is stored in a blockchain address that is verified at creation and can be transferred according to the usual non-fungible tokens. In this way, entries in catalog 110 can be used, copied, or transferred, and the authenticity of the data can be transparently verified. For example, an NFT tokenized catalog 110 or entries within it can also be used or owned under license. Since the data in the catalog NFT is verifiable, it is possible to prevent or minimize changes to the catalog or entries that do not meet the requirements for providing a level of certainty and security.

[0044] It is understood that by executing a catalog or its entries as part of a verifiable digital ledger, it is possible to procure, for example, parts or assemblies that can be associated with an assembly, and to allocate payments to correspond to those procured components. In the window example illustrated with respect to Figure 6, it is understood that in the case of a building with multiple windows, each window can be individually verified from design to manufacture and integration. This allows, for example, payment for each window of a building to be made at the time of individual receipt or installation rather than as a set for each window. When executed in a smart contract, ownership of each window can be transferred when payment is completed. This not only helps to ensure that catalog items are not altered, but also helps to finance building projects by allowing NFTs to be transferred.

[0045] Building 124 may be constructed using only parts such as 129, or only assemblies such as 127, or only master assemblies such as 141. However, typically, building 124 is constructed using some parts specified by part specification 103, some assemblies specified by assembly specification 102, and some master assemblies specified by master assembly specification 101.

[0046] Since the new building 124 is typically a new combination of parts, assemblies, and master assemblies assembled in a new way, the specifications may conflict to some extent when the parts, assemblies, and master assemblies drawn from catalog 110 are assembled to form building 124. This means that, depending on their respective geometric parameters, some parts, assemblies, and master assemblies will partially occupy the same space as other parts, assemblies, and master assemblies when assembled. Also, the attributes of building 124, determined by the combined attributes of the parts, assemblies, and master assemblies used to construct building 124 as the specifications are drawn from database 110, may not satisfy the attributes of building 124 specified in input specification 104. This is because the specifications may not exactly match the requirements of specification 104, although the attributes of the parts, assemblies, and master assemblies in catalog 110 may be close to those required by input specification 104.

[0047] When designer 111 receives input specification 104, they use HPDMI to select module specifications from catalog 110 that match the input module specifications 101, 102, and 103 of input specification 104 (referred to as the first pre-harmonization module specifications). As more module specifications are inserted into database 110 over time, designers will find it more frequently to find all the necessary module specifications in database 111. However, if all the necessary module specifications for input specification 104 are not found in database 111, designers may use the HPDMI system 110 and appropriate third-party software applications 146 to generate new module specifications for the desired specifications that do not exist in catalog 110, and these new module specifications for the desired specifications will be referred to as the second pre-harmonization module specifications.

[0048] The HPDMI system allows the designer 111 to harmonize a set of pre-harmonization module specifications, including a first pre-harmonization module specification and a second pre-harmonization module specification, using a third-party software application 146 as needed. The harmonization process generates harmonized parts 119, harmonized assemblies 118, and harmonized master assembly specifications 117, respectively, whose corresponding parts, assemblies, and master assemblies will have little conflict when used to construct the building 124 and will largely satisfy the attribute requirements set by the input specifications 104.

[0049] The construction of building 124 is carried out primarily using pre-harmonization modules such as parts 129, assemblies 127, and master assemblies 141, some of which have their respective pre-harmonization part specifications 103, pre-harmonization assembly specifications 102, and pre-harmonization master assembly specifications 101 stored in the electronically accessible HPDMI database 110 (also referred to as the catalog). The pre-harmonization specifications, which will be described in more detail below with reference to Figures 10-12, include geometric parameters 1001 and attributes 1002.

[0050] An exemplary geometric parameter related to the pre-harmonization part specification of part 129' (which is the pre-harmonization version of part 129) is the thickness (mm) of the plate used in the part. An exemplary attribute related to the pre-harmonization part specification of part 129' is the Young's modulus (N / m) of the plate. 2 )

[0051] An exemplary geometric parameter related to the pre-harmonization specifications of assembly 127' (which is a pre-harmonization version of assembly 127) is the thickness of the pipe wall. An exemplary attribute related to the pre-harmonization specifications of assembly 127' is the shear stress that assembly 127' can tolerate.

[0052] An exemplary geometric parameter related to the pre-harmonization master assembly specification of master assembly 141' (which is the pre-harmonization version of master assembly 141) is the roof slope. An exemplary attribute related to the pre-harmonization master assembly specification of master assembly 141' is the wind load that master assembly 141' can withstand.

[0053] While mechanical attributes have already been provided as an example, it is clear that other attributes can be included in the disclosed HPDMI configuration, including electrical attributes (e.g., resistivity), hydraulic attributes (e.g., Reynolds number), code attributes (e.g., compliance with specific standards), etc.

[0054] In the example in Figure 1, harmonized parts such as 129, harmonized assemblies such as 127, and harmonized master assemblies such as 141 can be effectively designed and manufactured off-site. The originality of the disclosed HPDMI arrangement lies in harmonizing parts, assemblies, and master assemblies during design and manufacturing by harmonizing part specifications, assembly specifications, and master assembly specifications in relation to the output specifications 120 of building 124. As a result of the harmonization, harmonized parts 129, harmonized assemblies 127 and harmonized master assemblies 141 (each relating to a harmonized part specification 119, a harmonized assembly specification 118, and a harmonized master assembly specification 117 of output specification 120) are assembled on site to construct building 124, and (a) the harmonized parts, harmonized assemblies and harmonized master assemblies all fit together geometrically with a very high degree of "fit" (i.e., with almost no "collisions"), and (b) building 124, composed of harmonized parts, harmonized assemblies and harmonized master assemblies, satisfies criteria defined by attributes related to master assemblies such as 141, assemblies such as 127 and parts such as 129.

[0055] During use, the design team 111 receives input specifications 104 created by the architect (not shown) via the communication network 116, and the aforementioned communication takes place between the remote terminal 109 used by the architect and the remote terminal 106 used by the design team 111, as indicated by arrow 107. The architect can also communicate the input specifications 104 to the server 113 via the network 116, as indicated by arrow 108. The design team 111 communicates with the server 113 via the network 116, as indicated by arrow 105. The server 113 runs the HPDMI software application 130, which allows the design team 111 to search the HPDMI catalog 110 for predefined pre-harmonized parts, pre-harmonized assemblies, and pre-harmonized master assemblies that match the requirements of the input specifications 104, as indicated by arrow 114.

[0056] The design team 111 can (a) generate pre-harmonized parts, pre-harmonized assemblies, and pre-harmonized master assemblies (see, for example, part 808 in Figure 8) that are not predefined and not stored in the HPDMI catalog 110, and (b) access a third-party software application such as Rhinoceros 3D 146 via one or more application programming interfaces (APIs) 144, as indicated by arrows 143 and 145, to store these in the HPDMI catalog 110, as indicated by arrow 114.

[0057] The server 113 running the HPDMI software application 130 also allows the design team 111 to harmonize the pre-harmonized part specifications 103, pre-harmonized assembly specifications 102, and pre-harmonized master assembly specifications 101 of the input specifications 104, regardless of whether they are in the HPDMI database 110 or created by the design team 111, as necessary for constructing the building 124, as will be described later in relation to Figures 3-9.

[0058] A server 113 running the HPDMI software application 130 transmits the harmonized HPDMI output specification 120 to the manufacturing, assembly, and construction team 125 via a communication network 116 through one or more remote terminals 122, as indicated by arrows 112 and 121. The manufacturing, assembly, and construction team 125 uses the harmonized HPDMI output specification 120 to manufacture, assemble, and construct a building 124 (indicated by dashed arrow 123) using harmonized parts such as 129 (indicated by dashed arrow 128), harmonized assemblies such as 127 (indicated by dashed arrow 126), and harmonized master assemblies such as 141 (indicated by dashed arrow 142).

[0059] Turning to the structural details of system 100, the server 113, which will be described in more detail later in relation to Figures 2A and 2B, has a computer processor 205 and a computer-executable HPDMI software program 130. The server 113 communicates with the HPDMI catalog 110, as indicated by arrow 114. The catalog (database) 110 can be located locally with respect to the server 113 or remotely. If located remotely, the server 113 communicates with the catalog 110 via a communication network 116. Both the server 113 and the catalog 110 can be implemented in a centralized or distributed configuration, as shown in Figure 1. In the distributed configuration, a number of spatially distributed different server computers (not shown) perform the server function, and a number of spatially distributed different databases (not shown) perform the catalog function.

[0060] Server 113 communicates with one or more third-party software applications 146 running on a remote server (not shown) via a communication network 116 and a corresponding API 144, as indicated by arrows 143 and 145. The specific third-party software applications that can be used depend on the specific purpose for which the HPDMI system is used. In the example of constructing building 124, one or more third-party software applications used in building transactions are used. Examples of such third-party software applications used in the construction industry are described in Appendix A. These include software applications related to fields such as mechanical engineering and electrical engineering.

[0061] As indicated by arrow 108, the server communicates with a remote terminal 109 via a communication network 116, which has a computer processor 133 that executes a computer executable software program (not shown) stored in a non-temporary tangible memory module 134. The software program executed by processor 133 can cooperate with a software program 130 executed by the processor 205 of server 113 and with software programs executed on other remote terminals 106 and 122. Remote terminal 109 facilitates communication of input specification 104 to server 113.

[0062] The input specification 104, prepared by the architect designing building 124, is used to construct building 124 according to the disclosed HPDMI configuration. The input specification 104 comprises several input module specifications, including a pre-harmonized component specification 103 specifying pre-harmonized components to be used when constructing building 124, a pre-harmonized assembly specification 102 specifying pre-harmonized assemblies to be used when constructing building 124, and a pre-harmonized master assembly specification 101 specifying pre-harmonized master assemblies to be used when constructing building 124.

[0063] Server 113 communicates with remote terminal 106 via network 116, as indicated by arrow 105. Remote terminal 106 has a computer processor 135 that executes a computer executable software program (not shown) stored in a non-temporary tangible memory device 136. As indicated by arrow 105, remote terminal 106 allows design team 111 to communicate with server 113 to use the disclosed HPDMI configuration.

[0064] Server 113 outputs a harmonized HPDMI output 120, as indicated by arrow 112. The harmonized HPDMI output 120 comprises a set of harmonized output module specifications, namely a harmonized component specification 119 specifying harmonized components used when constructing building 124, a harmonized assembly specification 118 specifying harmonized assemblies used when constructing building 124, and a harmonized master assembly specification 117 specifying harmonized master assemblies used when constructing building 124.

[0065] The output specification 120 is sent to one or more remote terminals 122, which include a computer processor 139 that runs a computer executable software program (not shown) stored in a non-temporary tangible memory device 140, as indicated by arrow 121. The (one or more) remote terminals 122 can then retrieve the necessary information from the output specification 120 so that the manufacturing, assembly and construction team 125 can design, manufacture and assemble harmonized parts such as 129, harmonized assemblies such as 127, and harmonized master assemblies such as 141 to form a building 124.

[0066] Figure 8 shows a simplified HPDMI example 800, where the harmonization process is applied only to geometric parameters for the sake of clarity, and it is understood that harmonization is provided for parts, assemblies, and master assemblies. In the illustrated example, a number of parts specified by the architect are assembled into assemblies specified by the architect. In practice, harmonization is performed on part specifications, assembly specifications, and master assembly specifications, resulting in harmonized parts, harmonized assemblies, and harmonized master assemblies at the time of manufacture. In the following description of Figure 8, for the sake of clarity, harmonization is described as being performed on the parts and assemblies themselves (rather than on specifications).

[0067] A description of the first example of catalog 110 is shown in 812. This catalog example includes three pre-harmonization parts 801, 802, and 803. It is desired to construct an assembly drawn by a dotted ellipse 814 specified by the architect, as shown in the second example of catalog 813. From 814, it can be seen that the desired assembly specified by the architect (see input specification 104 in Figure 1) consists of three modules: (a) part 801', which is a pre-harmonization (appropriately scaled up) version of pre-harmonization part 801; (b) part 808, which does not exist in database 812 but is newly created in database 813; and (c) part 803', which is a pre-harmonization (appropriately scaled down) version of database 812.

[0068] Similarly, it can be seen that the exemplary parts 801, 802, and 803 are each shown enclosed by a dotted line. This equivalently defines the geometric constraints according to those specified parts. Thus, harmony in geometry and scale is achieved. The region within 814' shows parts scaled to fit geometrically within region 801'. This schematically shows that parts 803, 808, and 801' cooperate with the desired geometric tolerances as described. The components within region 814 are shown to correspond geometrically to one another, indicating that each component is within the geometric tolerances as described. In the preferred embodiments described, it can be seen that Figure 8 can be used to schematically illustrate parts, assemblies, master assemblies, and building specifications in a hierarchical manner.

[0069] Thus, catalog 812 of the first example includes the three parts described above, namely 801, 802, and 803. The desired assembly 814 uses two of these parts 801 and 803 and requires a third part 808. Therefore, the HPDMI system allows the designer 111 to create a new part 808 that exists in catalog 813 of the second example. Part 801 of catalog 812 of the first example also exists in catalog 813 of the second example, as illustrated by the dashed arrow 804. Part 802 of catalog 812 of the first example also exists in catalog 813 of the second example, as illustrated by the dashed arrow 805. Part 803 of catalog 812 of the first example also exists in catalog 813 of the second example, as illustrated by the dashed arrow 806.

[0070] The pre-harmonization part 801 of catalog 813 in the second example is harmonized by designer 111 using the HPDMI system by enlarging its size as shown by the dashed arrow 807, assuming the shape shown by 801', as required by the desired assembly 814. The pre-harmonization part 803 of catalog 813 in the second example is harmonized by designer 111 using the HPDMI system by reducing its size as shown by the dashed arrow 810, assuming the size shown by 803'. The harmonized part 801' is assembled with the new part 808 and the harmonized part 803', as shown by the respective dashed arrows 808, 809, and 811, to form the desired harmonized assembly 814.

[0071] Figures 2A and 2B illustrate a general-purpose computer system capable of implementing the various configurations described.

[0072] As shown in Figure 2A, the computer system 200 includes a computer server module 113, input devices such as a keyboard 202, a mouse point device 203, a scanner 226, a camera 227, and a microphone 280, and output devices such as a printer 215, a display device 214, and a speaker 217. An external modulator-demodulator (modem) transceiver device 216 may be used by the computer module 113 to communicate with remote terminals 106, 109, 115, 122, one or more remote servers and remote databases 110, 290 (not shown) running third-party software applications 146, via a communication network 220, for example, via connection 221. The communication network 220 may be a wide area network (WAN) or a private WAN, such as the Internet and a mobile phone network. If connection 221 is a telephone line, the modem 216 may be a regular "dial-up" modem. Alternatively, if connection 221 is a high-capacity (e.g., cable) connection, the modem 216 may be a broadband modem. Additionally, a wireless modem may be used for wireless connection to the communication network 220.

[0073] The following description is primarily directed towards server module 113, but remote terminals 109, 106, 115, and 122, and one or more remote servers (not shown) running (one or more) third-party software applications, operate in a similar manner and have similar structural and functional attributes.

[0074] The computer server module 113 typically includes at least one processor unit 205 and a memory unit 206. For example, the memory unit 206 may have semiconductor random access memory (RAM) and semiconductor read-only memory (ROM). The computer module 113 has a plurality of input / output (I / O) interfaces, the I / O interfaces of which include an audio-video interface 207 coupled to a video display 214, a speaker 217 and a microphone 280; an input / output interface 213 coupled to a keyboard 202, a mouse 203, a scanner 226, a camera 227 and optionally a joystick or other human interface device (not shown); and an interface 208 for an external modem 216 and a printer 215. In some implementations, the modem 216 may be integrated into the computer module 113, for example, within interface 208. The computer module 113 has a local network interface 211, which allows the computer system 200 to be coupled via a connection 223 to a local area communication network 222 known as a local area network (LAN). As shown in Figure 2A, the local communication network 222 may be coupled to the wide area network 220 via connection 224, which typically includes a so-called "firewall" device or a device with similar functionality. The local network interface 211 can consist of an Ethernet circuit card, a Bluetooth® wireless configuration, or an IEEE 802.11 wireless configuration, but several other types of interfaces may be implemented for interface 211.

[0075] I / O interfaces 208 and 213 can accommodate either or both serial and parallel connections, the former typically implemented according to the Universal Serial Bus (USB) standard and having a corresponding USB connector (not shown). A storage device 209 is provided, typically having a hard disk drive (HDD) 210. Other storage devices such as floppy disk drives and magnetic tape drives (not shown) may also be used. An optical disk drive 212 is typically provided to function as a non-volatile source of data. Portable storage devices such as optical disks (e.g., CD-ROMs, DVDs, Blu-ray® disks), USB-RAMs, portable devices, external hard disks, and floppy disks can be used as suitable data sources to system 200.

[0076] The components 205-213 of computer module 113 typically communicate via an interconnected bus 204 in a manner that brings about the normal operating modes of a computer system 200 known to those skilled in the art. For example, the processor 205 is coupled to the system bus 204 using connection 218. Similarly, the memory 206 and optical disc drive 212 are coupled to the system bus 204 by connection 219. Examples of computers capable of realizing the described configuration include IBM-PC and compatibles, Sun Sparcstations, Apple Mac®, or similar computer systems.

[0077] The HPDMI method can be implemented using a computer system 200, and the processes shown in Figures 3-9 described herein may be implemented as one or more software application programs 130 and one or more APIs 146 executable within the computer system 200. In particular, the steps of the HPDMI method are implemented by instructions 231 (see Figure 2B) within the software 130 executed within the computer system 200. The software instructions 231 are formed as one or more code modules, each performing one or more specific tasks, and may be functionally distributed between the server 113 and remote terminals 109, 106, 115, and 122. The software may be divided into two separate parts, in which case the first part and its corresponding code modules execute the HPDMI method, and the second part and its corresponding code modules manage the user interface between the first part and the user.

[0078] The software may be stored on a computer-readable medium, for example, including a storage device as described later. The software is loaded from the computer-readable medium into the computer system 200 and then executed by the computer system 200. The computer-readable medium on which such software or computer programs are recorded is a computer program product. The use of the computer program product by the computer system 200 preferably affects the advantageous HPDMI device.

[0079] The software 130 and API 146 are typically stored on the HDD 210 or in memory 206. The software is loaded from a computer-readable medium into the computer system 200 and executed by the computer system 200. For example, the software 130 and API 146 may be stored on an optically readable disk storage medium (e.g., a CD-ROM) 225 that is read by an optical disc drive 212. The computer-readable medium on which such software or computer programs are recorded is a computer program product. The use of the computer program product by the computer system 200 preferably affects the HPDMI device.

[0080] In some embodiments, the application program 130 and API 146 may be encoded on one or more CD-ROMs 225 and supplied to the user, read via the corresponding drive 212, or alternatively, read by the user from a network 220 or 222. Furthermore, the software may also be loaded into the computer system 200 from other computer-readable media. Computer-readable storage media means any non-temporary tangible storage medium that provides instructions and / or data recorded in the computer system 200 for execution and / or processing. Examples of such storage media include floppy disks, magnetic tapes, CD-ROMs, DVDs, Blu-ray disks, hard disk drives, ROMs or integrated circuits, USB memory, magneto-optical disks or computer-readable cards such as PCMCIA cards, whether such devices are inside or outside the computer module 113. Examples of non-temporary or non-tangible computer-readable transmission media that may also participate in providing software application programs, instructions, and / or data to the computer module 113 include wireless or infrared transmission channels, network connections to other computers or networking devices, and the Internet or intranets, including email transmissions and information recorded on websites, etc.

[0081] The application program 130 and API 146, as well as the second portion of the corresponding code module described above, may be executed to implement one or more graphical user interfaces (GUIs) that are rendered or represented on the display 214. Typically, a user of the computer system 200 and the application may operate the interface in a functionally adaptable manner to provide control commands and / or inputs to the application associated with the GUI (one or more) through the operation of the keyboard 202 and the mouse 203. Other forms of functionally adaptable user interfaces may be implemented, such as an audio interface that utilizes speech prompts output via the loudspeaker 217 and user voice commands input via the microphone 280.

[0082] Figure 2B is a detailed schematic block diagram of the processor 205 and “memory” 234. Memory 234 represents the logical collection of all memory modules (including the HDD 209 and semiconductor memory 206) accessible by the computer module 113 in Figure 2A.

[0083] When the computer module 113 is first powered on, a power-on self-test (POST) program 250 is executed. The POST program 250 is typically stored in the ROM 249 of the semiconductor memory 206 in Figure 2A. Hardware devices such as ROM 249 that store software are sometimes referred to as firmware. The POST program 250 checks the hardware within the computer module 113 to ensure proper functionality and to check whether the processor 205, memory 234 (209, 206), and the Basic Input / Output System Software (BIOS) module 251, typically stored in ROM 249, are working correctly. If the POST program 250 executes successfully, the BIOS 251 starts the hard disk drive 210 in Figure 2A. The startup of the hard disk drive 210 causes the bootstrap loader program 252 in the hard disk drive 210 to be executed via the processor 205. This loads the operating system 253 into the RAM memory 206, and the operating system 253 begins to operate. Operating System 253 is a system-level application that can be executed by Processor 205 to provide various high-level functions, including processor management, memory management, device management, storage management, software application interfaces, and general user interfaces.

[0084] The operating system 253 manages memory 234(209,206) so that each process or application running on the computer module 113 has enough memory to run without conflicting with memory allocated to other processes. Furthermore, the different types of memory available in system 200 in Figure 2A must be used appropriately so that each process can run effectively. Therefore, the aggregated memory 234 is not intended to describe how specific segments of memory are allocated (unless otherwise noted), but rather to provide an overview of the memory accessible by computer system 200 and how such memory is used.

[0085] As shown in Figure 2B, the processor 205 has several functional modules, including a control unit 239, an arithmetic logic unit (ALU) 240, and local or internal memory 248, sometimes referred to as cache memory. The cache memory 248 typically has several storage registers 244-246 in a register section. One or more internal buses 241 functionally interconnect these functional modules. The processor 205 also typically has one or more interfaces 242 for communicating with external devices via the system bus 204 using connectors 218. Memory 234 is coupled to the bus 204 using connectors 219.

[0086] The application program 130 has an instruction sequence 231 that can include conditional branch instructions and loop instructions. The program 130 may also have data 232 used in the execution of the program 130. The instructions 231 and the data 232 are stored in memory locations 228, 229, 230 and 235, 236, 237, respectively. Depending on the relative size of the instructions 231 and memory locations 228-230, a particular instruction may be stored in a single memory location, as indicated by the instruction shown in memory location 230. Alternatively, the instruction may be segmented into several parts, each stored in a separate memory location, as indicated by the instruction segments shown in memory locations 228 and 229.

[0087] Generally, the processor 205 is given a set of instructions to be executed there. The processor 205 waits for subsequent inputs to which the processor 205 will respond by executing another set of instructions. Each input may be provided from one or more sources, including data generated by one or more input devices 202, 203, data received from an external source via one of the networks 220, 202, data obtained from one of the storage devices 206, 209, or data obtained from a storage medium 225 inserted into the corresponding reader 212, all of which are shown in Figure 2A. The execution of a set of instructions may, in some cases, result in the output of data. Execution may also include the storage of data or variables into memory 234.

[0088] The disclosed HPDMI configuration uses input variables 254 stored in memory 234 in corresponding memory locations 255, 256, and 257. The HPDMI configuration generates output variables 261, which are stored in memory 234 in corresponding memory locations 262, 263, and 264. Intermediate variables 258 may be stored in memory locations 259, 260, 266, and 267.

[0089] Referring to processor 205 in Figure 2B, registers 244, 245, 246, arithmetic logic unit (ALU) 240, and control unit 239 cooperate to execute a sequence of microoperations necessary to perform the "fetch," "decode," and "execute" cycles for all instructions in the instruction set that make up program 130. The fetch, decode, and execute cycles are: A fetch operation to fetch or read instruction 231 from memory locations 228, 229, 230, The control unit 239 performs a decoding operation to determine which instruction has been fetched, The execution operation in which the control unit 239 and / or ALU240 execute the instruction, Each is equipped with one of the following.

[0090] Subsequently, further fetch, decode, and execute cycles may be performed for the next instruction. Similarly, the control unit 239 may perform a storage cycle by storing or writing values ​​to the storage location 232.

[0091] Each step or subprocess in the process shown in Figures 3-9 is associated with one or more segments of program 130 and is executed by the cooperation of the registers 244, 245, 247 of the processor 205, the ALU 240, and the control unit 239 to perform fetch cycles, decode cycles, and execution cycles for all instructions in the instruction set for the segment of program 130 of interest.

[0092] Figure 9 is a flowchart of an exemplary process 900 for executing the HPDMI process. Process 900 starts with a start step 901. The process then proceeds to step 903 following arrow 902. Step 903, executed by processor 205 running software program 130, receives input specification 104 (see Figure 1) as indicated by the dashed arrow 914. The process then proceeds to step 905 following arrow 904. Step 905, executed by processor 205 running software program 130, allows the design team 111 to identify which parts of module specifications 101, 102, and 103 (see, for example, 801, 803 in Figure 8) are stored in database 110, as will be described in more detail later with reference to step 301 in Figure 3, step 401 in Figure 4, and step 501 in Figure 5, respectively. Step 905 outputs information 916 that identifies the required parts of module specifications 101, 102, and 103 stored in database 110, as indicated by the dashed arrow 915. Information 916 identifies the part of the module specifications present in database 110 that is referred to as the first pre-harmonization module specification.

[0093] Next, process 900 proceeds to step 907 according to arrow 906. Step 907, performed by processor 205 running software program 130, allows the design team to access a third-party software application 146, such as Rhinoceros 3D, to generate portions of specifications 101, 102, and 103 that are not stored in database 110 (see, for example, 808 in Figure 8), as will be described in more detail later with reference to step 301 in Figure 3, step 401 in Figure 4, and step 501 in Figure 5, respectively. Step 907 outputs the desired portions of specification 918 that are not stored in the database, as indicated by dashed arrow 917. Specification 918 that is not stored in database 110 is referred to as a second pre-harmonization module specification for portions of module specifications that do not exist in database 110. As can be seen from Figure 9, these pre-cataloged parts are added therewith with predetermined attributes.

[0094] The first pre-harmonization module specification and the second pre-harmonization module specification 918 (identified by information 916) form a set of pre-harmonization module specifications 919. The set of pre-harmonization module specifications 919 is provided in step 909, as indicated by the dashed arrow 920. Step 909, performed by the processor 205 running the software program 130, works in conjunction with the design team, who have access to a third-party software application 146, to harmonize the required set of pre-harmonization module specifications 919, as will be described in more detail later with reference to steps 305, 315, 325 in Figure 3, 405, 415, 425 in Figure 4, and steps 505, 515, 525 in Figure 5. Step 909 outputs a set of harmonized module specifications that constitute the output module specification 120 (also referred to as the digital twin of building 124), as indicated by the dashed arrow 921, from which the harmonized module specification 120 is used to manufacture parts. It can be seen that step 909 is performed using the method described in relation to Figure 6.

[0095] Next, process 900 follows arrow 910 from step 909 to step 911. In step 911, manufacturing, assembly, and construction team 125 manufactures harmonized parts, harmonized assemblies, and harmonized master assemblies according to output module specifications 120, assembles them as needed, and constructs building 124 as shown by dashed arrow 922. After that, process 900 proceeds to termination stop 913 following arrow 912, and the process ends.

[0096] Figure 7 shows a flowchart of an exemplary process 700 for executing the HPDMI process using the processes of Figures 3, 4, and 5. Process 700 starts with a start step 701 and then proceeds to step 703 according to arrow 702. Step 703, executed by a processor 205 running the software program 130, receives an input specification 104 (see Figure 1). The process then proceeds from step 703 to a decision step 705 according to arrow 704.

[0097] As illustrated with reference to Figure 1, the building 124 is typically constructed using several parts specified by part specification 103, several assemblies specified by assembly specification 102, and several master assemblies specified by master assembly specification 101.

[0098] Step 705, performed by the processor 205 running the software program 130, allows the design team 111 to access the relevant third-party software application 146, thereby determining whether the input specification 104 under consideration is at least partially part-based, i.e., whether the input specification 104 includes parts specified by part specification 100. If step 705 returns a false value, the process proceeds from step 705 to determination step 707, following the arrow 706 marked NO. Step 707, performed by the processor 205 running the software program 130, allows the design team 111 to access the relevant third-party software application 146, thereby determining whether the input specification under consideration is at least partially assembly-based, i.e., whether the input specification 104 includes assemblies specified by assembly specification 102. If step 707 returns a false value, the process proceeds from step 707 to step 709, following the arrow 708 marked NO.

[0099] Step 709, performed by the processor 205 running the software program 130, allows the design team 111 to access the relevant third-party software application 146, thereby determining whether the input specification under consideration is at least partially master assembly-based, i.e., whether the input specification 104 includes the master assembly specified by the master assembly specification 101. If step 709 returns true, the process proceeds to step 711 following arrow 710 (as will be further detailed later with reference to process 500 in Figure 5). Step 711, performed by the processor 205 running the software program 130, allows the design team 111 to access the relevant third-party software application 146, thereby identifying and generating the harmonized master assembly specification, harmonized assembly specification and harmonized part specification, as well as the geometric parameters and attributes of the harmonized master assembly, harmonized assembly and harmonized part, and storing them in catalog 110 (as will be further detailed with reference to Figure 5). The process then proceeds to step 713 following arrow 712. If step 709 returns false, an error message is generated.

[0100] Step 713, performed by the processor 205 running the software program 130, receives the harmonized HPDMI output 120 from process 300 in Figure 3, process 400 in Figure 4, and process 5, respectively, and from catalog 110. The process then proceeds from step 713 to step 911 (see Figure 9) according to arrow 714. In step 911, the manufacturing, assembly, and construction team 125 manufactures harmonized parts, harmonized assemblies, and harmonized master assemblies according to the output module specification 120, assembles them as needed, and constructs the building 124. The process then proceeds to termination step 717 according to arrow 716, at which point the process terminates.

[0101] Returning to step 705, if the step returns true, the process proceeds from step 705 to step 719 by following the arrow 718 for YES (as will be explained in more detail later with reference to 300 in Figure 3). Step 719, performed by the processor 205 running the software program 130, allows the design team 111 to access the relevant third-party software application 146, thereby identifying and generating harmonized part, harmonized assembly and harmonized master assembly specifications, as well as the geometric parameters and attributes of the harmonized part, harmonized assembly and harmonized master assembly, and storing them in catalog 110 (as will be explained in more detail later with reference to Figure 3). The process then proceeds to step 713 following the arrow 720.

[0102] Returning to step 707, if the step returns true, the process proceeds from step 707 to step 722 by following the arrow 721 for YES (as will be explained in more detail later with reference to 400 in Figure 4). Step 722, performed by the processor 205 running the software program 130, allows the design team 111 to access the relevant third-party software application 146, thereby identifying and generating the specifications for harmonized assemblies, harmonized parts and harmonized master assemblies, as well as the geometric parameters and attributes of the harmonized assemblies, harmonized parts and harmonized master assemblies, and storing them in the catalog 110 (as will be explained in more detail with reference to Figure 4). The process then proceeds to step 713 following the arrow 723.

[0103] Figures 3, 4, and 5 are illustrative flowcharts of the part-based HPDMI harmonization process 300, the assembly-based HPDMI harmonization process 400, and the master assembly-based HPDMI harmonization process 500, respectively. While Figures 3, 4, and 5 refer to parts, assemblies, and master assemblies for brevity of explanation, the process actually operates with part specifications, assembly specifications, and master assembly specifications, as described below. As stated above, this specification considers an input specification 104 that specifies a building using one or more of the following four hierarchical levels: (A) building specification 147, (B) part specification 103, (C) assembly specification 102, and (D) master assembly specification 101. Figures 3, 4, and 5 show the three hierarchies of parts, assemblies, and master assemblies. However, as stated above, other numbers of hierarchical levels can also be used in the disclosed HPDMI configuration.

[0104] Figure 3 is an example flowchart of the parts-based HPDMI harmonization process 300. In this use case, the input specification 104 comprises at least several parts specifications 103 that specify the pre-harmonization parts to be used when constructing the building 124.

[0105] Process 300 initiates step 301, which is executed by a processor 205 running a software program 130. Given an input specification 104, the design team 111 can access a third-party software application, such as Rhinoceros 3D, which can (A) identify any pre-harmonized part specifications specified by the input part specification 103 (see Figure 1), (B) identify any required part specifications that are pre-stored in catalog 110, and (C) create any required part specifications that are not stored in catalog 110. The sum of the pre-stored and created part specifications is specified as part specification n=1,x, where x is the total number of parts required by the input part specification 103.

[0106] Next, process 300 proceeds to step 303, which is executed by processor 205 running software program 130, following arrow 302, thereby allowing design team 111 to access third-party software applications such as Rhinoceros 3D, for example, thereby making the above-mentioned part specification n=1,x parametric. The term "parametric" means specifying the dimensions of a part by parameters, so for example, part 129 in Figure 1 is defined by the variables t, l, h, d, s, THETA, and w. One way to make the plate specification parametric is to define the above-mentioned variables in terms of each other, for example, t=0.1l, h=0 / 3l, d=0.05l, s=0.6l, w=0.2l, and THETA=1 / h radians. Next, the process proceeds to step 305, which is executed by a processor 205 running a software program 130, which will be described in more detail later with reference to Figure 6, following arrow 304, thereby enabling the design team 111 to access relevant third-party software applications, thereby harmonizing the part specification n=1,x in relation to both its respective geometric parameters and its respective attributes. Step 305 outputs the harmonized part specification n=1,x, as indicated by arrow 310, and also outputs the geometric parameters 307 and attributes 309 of the harmonized part, as indicated by dashed arrows 306 and 308, and stores these in catalog 110.

[0107] Next, process 300 proceeds to step 311, which is performed by processor 205 running software program 130, following arrow 310, thereby enabling design team 111 to access, for example, Tekla software applications, thereby enabling them to combine at least a portion of the aforementioned harmonized part specifications n=1,x into assembly specifications n=1,y, where y is the total number of assembly specifications required by the input assembly specifications 102. Next, process 300 proceeds to step 313, which is performed by processor 205 running software program 130, following arrow 312, thereby enabling design team 111 to access, for example, Rhino3D and Grasshopper software applications, thereby enabling them to parametrically convert the aforementioned assembly specifications n=1,y.

[0108] Next, the process proceeds to step 315, which is executed by a processor 205 running a software program 130, which will be described in more detail later with reference to Figure 6, following arrow 314, thereby enabling the design team 111 to access relevant third-party software applications, thereby enabling them to (a) harmonize assembly specifications n=1,y in relation to both their respective geometric parameters and their respective attributes, and (b) harmonize them in relation to part specifications not linked to assembly specifications n=1,y in step 311. Step 315 outputs the harmonized assembly specifications n=1,y as indicated by arrow 320, and also outputs the harmonized geometric parameters 317 and harmonized assembly attributes 319 related to the assembly described above, as indicated by dashed arrows 316 and 318. Step 315 also updates the catalog 110 with the geometric parameters and part attributes of the parts for part specifications n=1,x that were not linked to assembly specifications n=1,y in step 311.

[0109] Next, process 300 proceeds to step 321, executed by processor 205 running software program 130, following arrow 320, thereby enabling design team 111 to access, for example, the Tekla software application, thereby enabling them to combine at least some of the aforementioned harmonized assembly specifications n=1,y into master assembly specifications n=1,z, where z is the total number of master assemblies required by the input master assembly specification 101. Next, process 300 proceeds to step 323, executed by processor 205 running software program 130, following arrow 322, thereby enabling design team 111 to access, for example, the Rhino3D software application and the Grasshopper software application, thereby enabling them to parametrically modify the aforementioned master assembly specifications n=1,z.

[0110] Next, the process proceeds to step 325, which is executed by a processor 205 running a software program 130, which will be described in more detail later with reference to Figure 6, following arrow 324, thereby enabling the design team 111 to access relevant third-party software applications, thereby harmonizing (a) master assembly specifications n=1,z related to both their respective geometric parameters and respective attributes, (b) assembly specifications not combined with master assembly specifications n=1,z in step 321, and (c) part specifications not combined with assembly specifications n=1,y in step 311. Step 325 outputs the harmonized master assembly specifications n=1,z, and also outputs the harmonized master assembly geometric parameters 327 and harmonized master assembly attributes 329 for the harmonized master assembly specifications, as shown by dashed arrows 326 and 388, and stores these in catalog 110. Furthermore, step 325 updates catalog 110 (a) the geometric parameters and attributes of parts for part specifications n=1,x that were not combined with assembly specification n=1,y in step 311, and (b) the geometric parameters and attributes of assemblies for assembly specifications n=1,y that were not combined with master assembly specification n=1,z in step 321.

[0111] Figure 4 is an example flowchart of the assembly-based HPDMI harmonization process 400. In this use case, the input specification 104 comprises at least several assembly specifications 102 that specify the pre-harmonization assemblies to be used when constructing the building 124.

[0112] The process begins with step 401, which is performed by the processor 205 executing the software program 130. Once the input assembly specification 104 is provided, the design team 111 can access a third-party software application, such as Rhioceros 3D, which allows them to (A) identify pre-harmonized assembly specifications if any exist as required by the input assembly specification 102 (see Figure 1), (B) identify pre-harmonized assembly specifications among the required ones that are already stored in catalog 110, and (C) create pre-harmonized assembly specifications among the required ones that are not stored in catalog 110. The total of pre-stored pre-harmonized assembly specifications and created pre-harmonized assemblies is designated as pre-harmonized assembly specification n=1,y, where y is the total number of assemblies required by the input assembly specification 102.

[0113] Next, process 400 proceeds to step 403, which is performed by processor 205 executing software program 130, following arrow 402, thereby enabling design team 110 to access, for example, Rhino3D and Grasshopper software applications, thereby parametrically modifying the pre-harmonization assembly specification n=1,y described above. Next, the process proceeds to step 405, which is performed by processor 205 executing software program 130, which will be described in more detail later with reference to Figure 6, following arrow 404, thereby enabling design team 111 to access relevant third-party software applications, thereby harmonizing the pre-harmonization assembly specification n=1,y in relation to both its respective geometric parameters and respective attributes. Step 405 outputs the harmonized assembly specification n=1,y, as shown by arrow 410, and also outputs the geometric parameters 407 and attributes 409 of the harmonized part, as shown by dashed arrows 406 and 408, and stores these in catalog 110.

[0114] Next, process 400 proceeds to step 411, which is executed by processor 205 running software program 130, following arrow 410, thereby enabling design team 111 to access, for example, the Tekla software application, thereby enabling them to decompose the aforementioned harmonized assembly specification n=1,y into part specification n=1,x, where x is the total number of parts required by the input part specification 103. Next, process 400 proceeds to step 413, which is executed by processor 205 running software program 130, following arrow 412, enabling design team 111 to access, for example, Rhino3D and Grasshopper software applications, thereby enabling them to parametrically decompose the aforementioned part specification n=1,x.

[0115] Next, the process proceeds to step 415, which is executed by a processor 205 running a software program 130, which will be described in more detail later with reference to Figure 6, following arrow 414, thereby enabling the design team 111 to access relevant third-party software applications, thereby harmonizing the part specification n=1,x in relation to both its respective geometric parameters and its respective attributes. Step 415 outputs the harmonized part specification n=1,x, as shown by arrow 420, and also outputs the harmonized geometric parameters 417 and attributes 419 of the harmonized assembly for the aforementioned part, as shown by dashed arrows 416 and 418, and stores these in catalog 110.

[0116] Next, process 400 proceeds to step 421, executed by processor 205 running software program 130, following arrow 420, thereby allowing design team 111 to access, for example, the Tekla software application, thereby combining the aforementioned harmonized assembly specification n=1,y with the master assembly specification n=1,z, where z is the total number of master assemblies required by the input master assembly specification 101. Next, process 400 proceeds to step 423, executed by processor 205 running software program 130, following arrow 422, thereby allowing design team 111 to access, for example, the Rhino3D software application and the Grasshopper software application, thereby parametrically converting the aforementioned master assembly specification n=1,z.

[0117] Next, the process proceeds to step 425, which is executed by a processor 205 that runs a software program 130, which will be described in more detail below with reference to Figure 6, following arrow 424, thereby enabling the design team 111 to access the relevant third-party software application, thereby harmonizing the master assembly specification n=1,z in relation to both its respective geometric parameters and its respective attributes. Step 425 outputs the harmonized master assembly specification n=1,z, and also outputs the harmonized master assembly geometric parameters 427 and the harmonized master assembly attributes 429 for the master assembly described above, as indicated by dashed arrows 426 and 428, and stores these in catalog 110.

[0118] Figure 5 is an example flowchart of the master assembly-based HPDMI harmonization process 500. In this use case, the input specification 104 comprises at least several master assembly specifications 101 that specify the pre-harmonization master assemblies to be used when constructing the building 124.

[0119] The process begins with step 501, which is performed by a processor 205 that runs a software program 130. Once the input specification 104 is provided, the design team 111 can access a third-party software application, such as Rhioceros 3D, which can (A) identify any pre-harmonized master assembly specifications required by the input master assembly specification 101 (see Figure 1), (B) identify any required pre-harmonized master assembly specifications that are pre-stored in catalog 110, and (C) create any required pre-harmonized master assembly specifications that are not stored in catalog 110. The sum of the pre-stored and created pre-harmonized master assembly specifications is designated as pre-harmonized master assembly specification n=1,z, where z is the total number of master assemblies required by the input master assembly specification 101.

[0120] Next, process 500 proceeds to step 503, performed by processor 205 running software program 130, following arrow 502, thereby enabling design team 111 to access third-party software applications such as Rhinoceros 3D, thereby parametrically modifying the pre-harmonization master assembly specification n=1,z described above. Subsequently, the process proceeds to step 505, performed by processor 205 running software program 130, which will be described in more detail later with reference to Figure 6, following arrow 504, thereby enabling design team 111 to access relevant third-party software applications, thereby harmonizing the pre-harmonization master assembly specification n=1,z in relation to both its respective geometric parameters and respective attributes. Step 505 outputs the harmonized master assembly specification n=1,z, as indicated by arrow 510, and also outputs the geometric parameters 507 and attributes 509 of the harmonized part, as indicated by dashed arrows 506 and 508, and stores these in catalog 110.

[0121] Next, process 500 proceeds to step 511, which is performed by processor 205 executing software program 130 according to arrow 510, thereby enabling design team 111 to access, for example, the Tekla software application, thereby enabling them to decompose the aforementioned harmonized master assembly specification n=1,z into assembly specification n=1,y, where y is the total number of assemblies required by the input assembly specification 102. Next, process 500 proceeds to step 513, which is performed by processor 205 executing software program 130 according to arrow 512, thereby enabling design team 111 to access, for example, the Rhino3D software application and the Grasshopper software application, thereby enabling them to parametrically decompose the aforementioned assembly specification n=1,y.

[0122] Next, the process proceeds to step 515, which is executed by a processor 205 running a software program 130, which will be described in more detail later with reference to Figure 6, following arrow 514, thereby enabling the design team 111 to access relevant third-party software applications, thereby harmonizing the assembly specification n=1,y in relation to both its respective geometric parameters and respective attributes. Step 515 outputs the harmonized assembly specification n=1,y, as shown by arrow 520, and also outputs the harmonized geometric parameters 517 and attributes 519 of the assembly described above, as shown by dashed arrows 516 and 518, and stores these in catalog 110.

[0123] Next, process 500 proceeds to step 521, which is executed by processor 205 running software program 130, following arrow 520, thereby allowing design team 111 to access, for example, the Tekla software application, thereby allowing the aforementioned harmonized assembly specification n=1,y to be broken down into part specification n=1,x, where x is the total number of parts required by the input part specification 103. Next, process 500 proceeds to step 523, which is executed by processor 205 running software program 130, following arrow 522, thereby allowing design team 111 to access, for example, the Rhino3D software application and the Grasshopper software application, thereby allowing the aforementioned part specification n=1,x to be made parametric.

[0124] The process then proceeds to step 525, which is executed by a processor 205 running a software program 130, which will be described in more detail later with reference to Figure 6, following arrow 524, thereby enabling the design team 111 to access relevant third-party software applications, thereby harmonizing the part specification n=1,x in relation to both its respective geometric parameters and its respective attributes. Step 525 outputs the harmonized part specification n=1,x, and also outputs the harmonized master assembly geometric parameters 527 and the harmonized master assembly attributes 529 for the aforementioned harmonized part, as indicated by dashed arrows 526 and 528, and stores these in catalog 110.

[0125] Figure 6 shows an example flowchart of the HPDMI geometric parameters and attribute harmonization process 600 used in steps 305, 315, and 325 of Figure 3, steps 405, 415, and 425 of Figure 4, and steps 505, 515, and 525 of Figure 5.

[0126] When used in Figure 3, process 600 receives, in the starting step 601, the pre-harmonized part specification n=1,x when used in step 305, the pre-harmonized assembly specification n=1,y when used in step 315, and the pre-harmonized master assembly specification n=1,z when used in step 325 as inputs. When used in Figure 4, process 600 receives, in the starting step 601, the pre-harmonized assembly specification n=1,y when used in step 405, the pre-harmonized part specification n=1,x when used in step 415, and the pre-harmonized master assembly specification n=1,z when used in step 425 as inputs. When used in Figure 5, process 600 receives, in the starting step 601, the pre-harmonized master assembly specification n=1,z when used in step 505, the pre-harmonized assembly specification n=1,y when used in step 515, and the pre-harmonized part specification n=1,x when used in step 525 as inputs.

[0127] Process 600 begins with start step 601 as described above and proceeds to determination step 603 following arrow 602. When processing each pre-harmonized part specification n=1,x, step 603, performed by processor 205 running software program 130, allows the design team 111 to access, for example, the Navisworks software application, and since there can be no collisions because each part is a single module, step 603 returns false, and process 600 proceeds from step 603 to step 605 following arrow 604.

[0128] When processing each pre-harmonized assembly specification n=1,y, step 603, performed by the processor 205 running the software program 130, allows the design team 111 to access, for example, the Navisworks software application, thereby determining whether any of the pre-harmonized parts constitute a collision in the pre-harmonized assembly (a collision occurs when any of the parts constituting the assembly occupies the same portion of space as another part constituting the assembly). In this case, the process proceeds from step 603 to step 616 following the YES arrow 601. Step 616, performed by the processor 205 running the software program 130, allows the design team 111 to adjust one or more geometric parameters of the colliding parts to resolve the collision, and then the process returns to step 603 following the arrow 617. On the other hand, if step 603 returns a false value indicating that no collision was detected, the process 600 proceeds from step 603 to step 605 following the NO arrow 604.

[0129] When processing each pre-harmoniz assembly specification n=1,z, step 603, performed by the processor 205 running the software program 130, allows the design team 111 to access, for example, the Navisworks software application, thereby determining whether any of the pre-harmoniz parts constituting the pre-harmoniz assembly or the pre-harmoniz master assembly are in conflict. If a conflict is found, the process proceeds from step 603 to step 616 following the arrow 601 for YES. Step 616, performed by the processor 205 running the software program 130, allows the design team 111 to adjust one or more geometric parameters of the conflicting parts and / or the conflicting assembly to eliminate the conflict, after which the process returns to step 603 following the arrow 617. On the other hand, if step 603 returns a false value indicating that no conflict was detected, the process 600 proceeds from step 603 to step 605 following the arrow 604 for NO.

[0130] Step 605, performed by the processor 205 running the software program 130, allows the design team 111 to access a relevant third-party software application 146, thereby determining whether and what kind of analysis is required for the part, assembly, or master assembly under consideration. Note that the part, assembly, or master assembly under consideration in step 605 has already been processed by step 603 for collision detection, and accordingly, the part, assembly, or master assembly under consideration in step 605 is referred to as the post-collision-detected part, post-collision-detected assembly, or post-collision-detected master assembly, respectively. For example, input specification 104 may specify an interior wall that is not intended to be subjected to loads in either the longitudinal or lateral direction. In this case, the input specification would specify the wall based on a set of rules such as the distance between steel studs for the sheet width, and (structural) analysis is not required. However, if the design team determines that an internal pressure difference will occur in the wall, it will be necessary to analyze the strength of the wall to comply with regulations, and (structural) analysis will be required. Please note that structural analysis is just one example, and other types of analysis, including those related to electricity, hydropower, and legal compliance, can also be considered within the disclosed HPDMI configuration.

[0131] If step 605 returns a true value indicating that analysis is required, the process proceeds from step 605 to step 607, following the arrow 606 for YES. Step 607, performed by the processor 205 running the software program 130, allows the design team 111 to access appropriate attribute catalogs (such as the OneSteel product catalog and other such catalogs relating to structural attributes), thereby enabling them to assign and / or adjust attributes for the module in question (i.e., a part, assembly, or master assembly). Thus, for example, in the case of the interior wall described above, the relevant attributes could include the elastic modulus and yield strength of the steel.

[0132] Next, process 600 proceeds from step 607 to step 609, following arrow 608. Step 609, executed by processor 205 running software program 130, allows the design team 111 to access, for example, the Tekla software application, thereby enabling them to perform the analysis process identified in step 605. Importantly, the analysis performed in the disclosed HPDMI configuration maintains shape and attributes in separate sections of database 110 throughout the analysis process, i.e., from entering analysis step 609 to exiting step 609. Subsequently, process 600 proceeds from step 609 to determination step 611, following arrow 610.

[0133] Step 611, performed by the processor 205 running the software program 130, allows the design team 111 to access, for example, Capterra software, thereby determining whether the results of the analysis are acceptable. For example, if a mechanical structure is being considered in terms of its mechanical performance, a national standards conformity check is typically applied. If step 611 returns a false value, process 600 proceeds from step 611 to step 613 following the arrow 612 for NO. Step 613, performed by the processor 205 running the software program 130, allows the design team 111 to access relevant third-party software application 146, thereby determining whether the attributes or geometric parameters of the post-collision-detected part, post-collision-detected assembly, or post-collision-detected master assembly in question need to be adjusted. If step 613 determines that the attributes need to be adjusted, process 600 returns from step 613 to step 607 following the arrow 614 for Attribute. Therefore, for example, if design team 111 determines in step 613 that the cable guide does not conform to the relevant code, design team 111 can adjust the yield strength of the material from grade 250 to grade 350 in step 607. On the other hand, if it is determined in step 613 that the geometric parameters need to be adjusted, process 600 proceeds from step 613 to step 616 according to the Geometry arrow 615.

[0134] Step 616, performed by the processor 205 running the software program 130, allows the design team 111 to access the relevant third-party software application 146, thereby allowing them to adjust the geometric parameters as needed. For example, if it is determined that the cable guide does not have sufficient strength for code compliance, the design team 111 can adjust the geometry by making the backing plate thicker by adjusting the geometric thickness parameter. Next, process 600 returns from step 616 to step 603 following arrow 617. Returning to step 605, if step 611 determines that no further analysis is needed, process 600 proceeds from step 605 to the end step 619 following arrow 620 for NO. Returning to step 611, if step 611 determines that the results of the analysis are acceptable, process 600 proceeds from step 611 to the end step 619 following arrow 618 for YES.

[0135] Figure 6 illustrates a generalized example of a harmonic element based on shape (in 603), regardless of whether it is a part or an assembly, and then illustrates a harmonic element based on attribute (in 607). In the case of Figure 6, as an example, an assembly or element under the described process may have a window (not shown) harmonized by the process. In 603, when considering geometric collisions, a 'No' response is given if the window fits within a predetermined frame or opening. If the window does not fit, step 616 may allow the window shape to be adjusted as appropriate, or the specification to redefine the shape of the window frame or opening.

[0136] Assuming the window size is accurate and the shape is appropriate, the window analysis is performed against predefined attributes required for the window, such as the window material and structural / load-bearing requirements. Before providing output in 616, modifications are made to the window attributes and tests are performed against the geometric requirements.

[0137] Conversely, referring particularly to step 607 in Figure 6, it can be understood that in some cases, the shape may be adjusted when attributes are changed during implementation so that the shape conflicts with the specification (step 613). Here, since attributes are required, the shape is adjusted accordingly as a result.

[0138] In the window example above, the selected window may need its attributes adjusted (step 607) to provide structural or load-bearing properties that require physically larger (or smaller) window elements (e.g., frames or mounting elements). In such cases, the change in attributes may then necessitate corresponding changes to the harmonized shape again through step 617 (steps 613 to 616).

[0139] While either the shape or attributes can be changed during harmonization, it can be seen that a combination of changes to both shape and attributes may be required, as shown in Figure 6. This can be a composite process in which the shape and attributes are each changed multiple times during the harmonization process in Figure 6. Most advantageously, this allows for modifications to conform to the required specifications. Figure 10 shows an example 1000 of a part-based segment illustrating the data structure of database 110. It can be seen that a particular part 1003 is a specification record for a cable guide in the database, having geometric parameters stored in the geometric parameter section 1001 and attributes stored separately in the attribute section 1002.

[0140] Figure 11 shows an example 1100 of an assembly-based segment in database 110. It can be seen that a particular assembly 1102 relates to a rectangular tray in the database, having geometric parameters stored in the geometric parameters section 1101 and attributes stored separately in the attributes section 1102.

[0141] Figure 12 shows an example 1200 of a segment based on a master assembly in database 110. It can be seen that a particular master assembly 1203 relates to the Marion Street master assembly, which has geometric parameters stored in the geometric parameters section 1201 and attributes stored separately in the attributes section 1202 in the database.

[0142] Figure 13 shows a two-dimensional representation of building 1300 made from a regular rectangular arrangement of 16 parts (reference figures 1301-1316). In one example, the disclosed HPDMI process is applied to a continuous set of contacting parts such as raster scan patterns 1301, 1302, 1303, 1304, 1305, 1306, etc. Part 1301 is in contact with both parts 1302 and 1305, and accordingly, a first harmonic path starting from part 1301 includes parts 1301, 1302, and 1305, as shown in the following relationship. P1 = 1301 / 1302 / 1305 Here, 1301 refers to the portion 1301 that is not constrained by the previous harmonic path, 1302 refers to the portion 1302 that is not constrained by the previous harmonic path, and 1305 refers to the portion 1305 that is not constrained by the previous harmonic path.

[0143] Part 1302 is in contact with parts 1301, 1303 and 1306, and accordingly, the second harmonic path leading to part 1302 includes parts 1302, 1303 and 1306, as expressed by the following relationship. P2 = 1302 1301 / 1303 / 1306 1305 Here 1302 1301 1302 refers to part 1302 which is constrained by the previous harmonic path that includes part 1301, 1303 refers to part 1303 which is not constrained by the previous harmonic path, and 1306 1305 This refers to part 1306, which is constrained by the preceding harmonic path that includes part 1305.

[0144] Portion 1303 contacts portions 1302, 1304, and 1307, and accordingly, a third harmonic path that proceeds to portion 1303 includes portions 1303, 1304, and 1307 as represented by the following relationship. P3 = 1303 1302 / 1304 / 1307 1306 Here 1303 1302 refers to portion 1303 constrained by a previous harmonic path that includes portion 1302, 1304 refers to portion 1304 not constrained by the previous harmonic path, and 1307 1306 refers to portion 1307 constrained by a previous harmonic path that includes portion 1306.

[0145] As described in connection with the above preferred embodiments, a method, system, and apparatus are provided for minimizing both the materials and the efficiency of building construction by using a harmonization process throughout. However, it is understood that in other preferred embodiments, the harmonization process can be employed, for example, to create multi-story buildings.

[0146] Here, the process is first applied to the structural frame, chassis, or backbone of the building. Thereafter, it is applied to all other components and assemblies that make up the entire building. The shape of the backbone is accurately generated as described in the above embodiments, and then becomes a known shape in 3D space in which all other components and assemblies are manufactured to fit, which can advantageously improve the efficiency of the building. An important part of the harmonization process is to perform an analysis (in this case, structural) and ensure the compliance of performance and optimization by changing either the shape or the attributes.

[0147] It can be seen that multi-story generally includes many other components and assemblies such as facades, bathrooms, interior walls, windows, air conditioning systems, stairs, lifts, elevators. Each of these components and assemblies is itself created or disassembled using the process described in the above embodiments and fitted to the backbone (or frame) with a certain tolerance.

[0148] Another preferred embodiment using the process of the embodiments described above may be a multi-story building, but including a data entre where the data rack is the first or most important shape for the building. In such a case, the harmonization process is applied to the data rack, and this shape is used to fix all other parts in 3D space, which are drawn to fit it. For example, the shape of the backbone and the harmonization applied must fit the shape of the data rack, and not the other way around. Also, when harmonization is applied to all other parts and assemblies, they will fit the data rack.

[0149] As a further embodiment, it is understood that the manufacture of a hydroelectric power plant is included, where the main shape requirements are the size, location, and performance of the large inlet pipes. In this case, the shape is governed by fluid analysis and structural performance, and the harmonization process is applied to this critical shape and all other components and assemblies that conform to it. Similarly, as a further embodiment, a substation can also be manufactured. In this case, in a similar manner, the size and performance of the transformers determine the critical shape, and electrical analysis and attributes determine the optimization of this process.

[0150] It is understood that in the preferred embodiment of the harmonization process described above, all harmonization occurs due to geometric requirements and constraints. The fundamental importance of geometric requirements is briefly explained below with reference to Figures 14-20 illustrating the harmonization process.

[0151] Figure 14 is similar to Figures 3 and 10 of the above embodiment and is a diagram illustrating the component harmonization subprocess and the component base database. The right side of Figure 14 shows the process steps in harmonization in flowchart form.

[0152] Continuing the visualization of the HPDMI process set described above with reference to Figure 8, Figures 15A–15E show this step by step. In the first step, designated part 1 is selected as the master part, which is shown with a five-pointed star in Figure 15A for illustrative purposes, but can represent any part. Next, the second part of the process is selected and defined, shown with a triangle in Figure 15B.

[0153] By employing the harmonization process shown in Figure 14, the second part is harmonized with the first master part. This harmonizes the parts to form an assembly, as shown in Figure 15C. It can be seen that this assembly defines its own shape. This shape is used in the HPDMI process, which is used to harmonize other assemblies, master assemblies, and buildings.

[0154] In some embodiments, it is understood that the HPDMI process in Figure 14 needs to introduce a geometric change to the second part (the triangular section) when harmonizing the process analysis, for example, to increase mechanical strength. This is exaggerated in Figure 15D.

[0155] Similarly, this assembly defines its own shape, which can then be used to harmonize with other assemblies, master assemblies, and buildings. However, running the harmony routine may require analysis that results in geometric changes to part 1 (star) when part 2 is designated as the master part (for example, it may no longer have sufficient strength).

[0156] This result is illustrated in Figure 15E, and it is understood that this assembly defines a unique shape that can be used to harmonize with other assemblies, master assemblies, and buildings. The two solutions (depending on designated part 1) are distinct and unique, and therefore produce entirely different assemblies, master assemblies, and buildings. This is advantageous, as it then provides an opportunity to optimize for any desired criteria. This is true when creating trays from parts and assemblies.

[0157] The same HPDMI process for harmony is used for the assembly process of assemblies and parts. This is shown in Figure 16 in a similar manner to the part process in Figure 14. An example of the resulting assembly is schematically shown in Figure 17A. This assembly has its own harmonized shape that must be contained within an ellipse.

[0158] An assembly can be disassembled into its constituent parts. One is an ellipse, all of which must fit together, labeled as the master part, and through which the HPDMI harmonization process can be performed. This process modifies the assembly, allowing it to be combined to form the master assembly and project. This is illustrated in Figure 17B, where the shape of the components is modified to achieve maximum fit, thus improving the efficiency of the construction process. It is then understood that the new assembly in Figure 17B can be combined with the master assembly and project.

[0159] For example, the project is broken down into assemblies, and the assemblies are broken down into parts, in the same manner as described with reference to Figures 4 and 5. This is shown in Figure 18 and is done in the same manner as the parts or assembly processes described above. Referring to Figure 19, the project is schematically illustrated with the same parts and assemblies described above, which are included in an irregular hexagonal shape.

[0160] A project can be broken down into assemblies. Each assembly is labeled as a master assembly, and the HPDMI harmonization process is run. The assembly can have its master label changed, and the harmonization process can be run again. Similarly, it is possible to break down an assembly into parts, label the parts as master parts, and run the harmonization process again.

[0161] Figure 20 shows a flowchart of how to create a parametric catalog of the shapes and attributes of parts, assemblies, and projects. Importantly, at every level of the process, it begins with defining the master assemblies and master parts in combination. The processes and structures created through HPDMI's harmonization process allow for accurate and reliable definitions, significantly improving construction efficiency based on shape and scale. [Industrial applicability]

[0162] The described configuration is applicable to the computer and data processing industries, and in particular, to the construction industry.

[0163] The above describes only some embodiments of the present invention, and modifications and / or variations may be made without departing from the scope and spirit of the invention. The embodiments are illustrative and not limiting.

[0164] In the context of this specification, the word "to prepare" means "to mainly include but not necessarily alone," or "to have," or "to include," and does not mean "to consist only of." Variations of the word "to prepare," such as "prepared," have correspondingly changing meanings. [Table 1]

Claims

1. A computer execution method for constructing a building, A step of receiving the input specifications for the building, wherein the input specifications specify the pre-harmonized modules required to construct the building, and the pre-harmonized modules are defined by the respective pre-harmonized module specifications, which include their respective geometric parameters and respective attributes. A step of identifying pre-harmonized module specifications that are stored in an electronically accessible database, wherein the identified pre-harmonized module specifications are referred to as first pre-harmonized module specifications having relevant geometric parameters and attributes stored in separate sections of the database, (a) Harmonizing the module specifications of the first pre-harmonization module specifications in order to form a set of harmonization module specifications that specify harmonization modules that have little to no conflict when used to construct the building, and (b) satisfy attribute criteria specified in the input specifications when assembled to form the building, The process includes the step of constructing the building using the aforementioned harmonized module specifications, The aforementioned harmonization step is, The steps include determining whether it is necessary to analyze one or more of the problematic post-collision-detection parts, post-collision-detection assemblies, or post-collision-detection master assembly specifications in order to establish whether the attributes of the problematic post-collision-detection parts, post-collision-detection assemblies, or post-collision-detection master assembly specifications satisfy the attribute criteria specified in the input specifications, If it is necessary to analyze one or more of the aforementioned problematic post-collision detection parts, post-collision detection assemblies, or post-collision detection master assembly specifications, Assign the corresponding attribute to one or more of the problematic post-collision detection parts, post-collision detection assemblies, or post-collision detection master assembly specifications. Perform one or more corresponding analysis processes, and throughout the analysis process, maintain one or more shapes and attributes of the problematic post-collision-detection parts, post-collision-detection assemblies, or post-collision-detection master assembly specifications in separate sections of the database. Determine whether one or more attributes of the problematic post-collision detection part, post-collision detection assembly, or post-collision detection master assembly specification satisfy the attribute criteria specified in the input specification. If one or more attributes of the problematic post-collision-detection part, post-collision-detection assembly, or post-collision-detection master assembly specification do not meet the attribute criteria specified in the input specification, it is determined whether the corresponding attribute or geometric parameter assigned to the problematic post-collision-detection part, post-collision-detection assembly, or post-collision-detection master assembly specification needs to be adjusted. If it is necessary to adjust the geometric parameters, adjust the geometric parameters so that the attributes of the problematic post-collision-detection part, post-collision-detection assembly, or post-collision-detection master assembly specification satisfy the attribute criteria specified in the input specification. A method comprising the step of adjusting the attributes of the problematic post-collision-detection part, post-collision-detection assembly, or post-collision-detection master assembly specification so that the attributes of the first pre-harmonization module specification satisfy the attribute criteria specified in the input specification, if it is necessary to adjust the attributes.

2. Before the aforementioned harmonization step, A step of generating the pre-harmonization module specification not stored in the database, the generated module specification further comprises a step referred to as a second pre-harmonization module specification, The first pre-harmonization module specification, together with the second pre-harmonization module specification, forms a set of the pre-harmonization module specifications. The method according to claim 1, wherein the harmonizing step comprises harmonizing a set of pre-harmonization module specifications, the first pre-harmonization specification module together with a second pre-harmonization specification module.

3. The pre-harmonization modules necessary for constructing the said building include one or more of component specifications, assembly specifications, master assembly specifications, and building specifications, and the step of harmonizing the module specifications in order to form a set of said harmonized module specifications is: A step of determining geometric parameters for one or more of the above-mentioned component specifications, assembly specifications, master assembly specifications, and building specifications, A step of determining attributes for at least one part of the above-mentioned part specifications, assembly specifications, master assembly specifications, and building specifications, A step of storing the geometric parameters and attributes in an electronically accessible database, wherein one or more of the geometric parameters and attributes from the part specifications, assembly specifications, master assembly specifications, and building specifications are stored in separate sections of the database. The method according to claim 1, comprising:

4. The method according to claim 2, wherein the first pre-harmonization module specification and the second pre-harmonization module specification are stored as tokens activated in a blockchain network.

5. A device for facilitating the construction of buildings, One or more computer processors, A step of receiving the input specifications for the building, wherein the input specifications specify the pre-harmonized modules required to construct the building, and the pre-harmonized modules are defined by the respective pre-harmonized module specifications, which include their respective geometric parameters and respective attributes. A step of identifying pre-harmonized module specifications that are stored in an electronically accessible database, wherein the identified pre-harmonized module specifications are referred to as first pre-harmonized module specifications having relevant geometric parameters and attributes stored in separate sections of the database, (a) Harmonizing the module specifications of the first pre-harmonization module specifications in order to form a set of harmonization module specifications that specify harmonization modules that have little to no conflict when used to construct the building, and (b) satisfy attribute criteria specified in the input specifications when assembled to form the building, The process includes the step of constructing the building using the aforementioned harmonized module specifications, The aforementioned harmonization step is, The steps include determining whether it is necessary to analyze one or more of the problematic post-collision-detection parts, post-collision-detection assemblies, or post-collision-detection master assembly specifications in order to establish whether the attributes of the problematic post-collision-detection parts, post-collision-detection assemblies, or post-collision-detection master assembly specifications satisfy the attribute criteria specified in the input specifications, If it is necessary to analyze one or more of the aforementioned problematic post-collision detection parts, post-collision detection assemblies, or post-collision detection master assembly specifications, Assign the corresponding attribute to one or more of the problematic post-collision detection parts, post-collision detection assemblies, or post-collision detection master assembly specifications. Perform one or more corresponding analysis processes, and throughout the analysis process, maintain one or more shapes and attributes of the problematic post-collision-detection parts, post-collision-detection assemblies, or post-collision-detection master assembly specifications in separate sections of the database. Determine whether one or more attributes of the problematic post-collision detection part, post-collision detection assembly, or post-collision detection master assembly specification satisfy the attribute criteria specified in the input specification. If one or more attributes of the problematic post-collision-detection part, post-collision-detection assembly, or post-collision-detection master assembly specification do not meet the attribute criteria specified in the input specification, it is determined whether the corresponding attribute or geometric parameter assigned to the problematic post-collision-detection part, post-collision-detection assembly, or post-collision-detection master assembly specification needs to be adjusted. If it is necessary to adjust the geometric parameters, adjust the geometric parameters so that the attributes of the problematic post-collision-detection part, post-collision-detection assembly, or post-collision-detection master assembly specification satisfy the attribute criteria specified in the input specification. If it is necessary to adjust the attributes, one or more non-temporary tangible computer-readable storage media storing computer-executable software programs for instructing a plurality of processors to perform a method comprising: adjusting the attributes of the problematic post-collision-detection part, post-collision-detection assembly, or post-collision-detection master assembly specification so that the attributes of the first pre-harmonization module specification satisfy the attribute criteria specified in the input specification; A device equipped with the following features.

6. A step of receiving input specifications for a building, wherein the input specifications specify pre-harmonized modules required to construct the building, and the pre-harmonized modules are defined by pre-harmonized module specifications, each including their respective geometric parameters and attributes. A step of identifying pre-harmonized module specifications that are stored in an electronically accessible database, wherein the identified pre-harmonized module specifications are referred to as first pre-harmonized module specifications having relevant geometric parameters and attributes stored in separate sections of the database, (a) Harmonizing the module specifications of the first pre-harmonization module specifications in order to form a set of harmonization module specifications that specify harmonization modules that have little to no conflict when used to construct the building, and (b) satisfy attribute criteria specified in the input specifications when assembled to form the building, The process includes the step of constructing the building using the aforementioned harmonized module specifications, The aforementioned harmonization step is, The steps include determining whether it is necessary to analyze one or more of the problematic post-collision-detection parts, post-collision-detection assemblies, or post-collision-detection master assembly specifications in order to establish whether the attributes of the problematic post-collision-detection parts, post-collision-detection assemblies, or post-collision-detection master assembly specifications satisfy the attribute criteria specified in the input specifications, If it is necessary to analyze one or more of the aforementioned problematic post-collision detection parts, post-collision detection assemblies, or post-collision detection master assembly specifications, Assign the corresponding attribute to one or more of the problematic post-collision detection parts, post-collision detection assemblies, or post-collision detection master assembly specifications. Perform one or more corresponding analysis processes, and throughout the analysis process, maintain one or more shapes and attributes of the problematic post-collision-detection parts, post-collision-detection assemblies, or post-collision-detection master assembly specifications in separate sections of the database. Determine whether one or more attributes of the problematic post-collision detection part, post-collision detection assembly, or post-collision detection master assembly specification satisfy the attribute criteria specified in the input specification. If one or more attributes of the problematic post-collision-detection part, post-collision-detection assembly, or post-collision-detection master assembly specification do not meet the attribute criteria specified in the input specification, it is determined whether the corresponding attribute or geometric parameter assigned to the problematic post-collision-detection part, post-collision-detection assembly, or post-collision-detection master assembly specification needs to be adjusted. If it is necessary to adjust the geometric parameters, adjust the geometric parameters so that the attributes of the problematic post-collision-detection part, post-collision-detection assembly, or post-collision-detection master assembly specification satisfy the attribute criteria specified in the input specification. If it is necessary to adjust the attributes, one or more non-temporary, tangible, computer-readable storage media store computer-executable software programs for instructing one or more computer processors to perform a method comprising: adjusting the attributes of the problematic post-collision-detection part, post-collision-detection assembly, or post-collision-detection master assembly specification so that the attributes of the first pre-harmonization module specification satisfy the attribute criteria specified in the input specification.

7. A computer executable software program for constructing a building, A program for causing one or more computer processors to perform the steps of the method described in any one of claims 1 to 4.

Images