ENVIRONMENT

RELATED APPLICATIONS

[0001] The present application claims priority to U.S. Provisional Application No.

61/576,921 (filed December 16, 2011) and to U.S. Provisional Application No. 61/576,892 (filed December 16, 2011), both of which are fully incorporated herein by reference.

[0002] The present application is related to U.S. Patent Application No. entitled

"Method and Apparatus for Representing 3D Thumbnails" (Attorney Docket No. GTI-0200) filed on an even date herewith and fully incorporated herein by reference.

BACKGROUND

Field of the Invention

[0001] The disclosure relates to method and apparatus for detecting interference in a design. More specifically, the disclosure relates to novel method and apparatus for identifying when elements of computer design physically interfere or clash with each other.

Description of Related Art

[0002] The use of 3D models built by computer aided modeling design (CAD) tools has improved the ability to design and build three dimensional structures. CAD models enable structural, mechanical, electrical and plumbing designs with great efficiency. The electronic design files may also be used to control machine operations. Such designs may be for buildings, ships, automobiles and the like. The design typically includes the overall structure as well as the individual parts of the structure. CAD tools have alleviated the need for hand- drawn plans and have vastly improved design efficiency and accuracy.

[0003] Conventional CAD models typically include different files with each file defining an aspect of the design. For example, a building's CAD model may include a structural CAD file, an electrical CAD file, a plumbing CAD file and a mechanical CAD file. Different designers may collaborate or be independently responsible for each aspect of the design. It is important to detect interference between different components (objects) of the design. For example, a building's 3D model may include clash points between structural and plumbing components. It is important to identify and remedy such clashes before investing in the actual constructions.

[0004] The design files are complex data files consuming much of the processor's bandwidth. Moreover, conventional design files have different formats such that a project coordinator may have to facilitate information transfer between design files with

incompatible formats. Thus, there is a need for a method and system for detecting interferences (e.g., clashes) between design components. There is also a need for a precision tool that enables material, inventory, project prioritization and cost control.

SUMMARY

[0005] Three-dimensional models allow accurate visualization of a structure before it is built. Such models accurately illustrate the placement of various components in relation to each other. The components can be objects in the 3D model. Depending on the design criteria, it may be desirable to have predefined distances (tolerance) between certain components. In one embodiment, the disclosure relates to method and apparatus for detecting interference between physical components of a design model. In another embodiment, the disclosure relates to identifying clashes between components of a model. In still another embodiment, the disclosure provides method and apparatus for identifying where certain design parameters have been violated.

[0006] In still another embodiment, the disclosure relates to an apparatus for detecting interference between components in a design, the apparatus comprising: a processor circuit in communication with a memory circuit, the memory circuit providing instructions for the processor to: (1) receive a first file containing a plurality of first design components, the plurality of first design components defining a first design aspect; (2) receive a second file containing a plurality of second design components, the plurality of second design components defining a second design aspect; (3) convert the first file and the second file to a neutral format; (4) identify a reference point common to the plurality of first design components and the plurality of second design components; (5) overlay the first plurality of components over the second plurality of components; (6) identify an interference between at least one of the first plurality of components and one of the second plurality of components; and (7) report the identified interference. [0007] In still another embodiment, the disclosure is directed to an apparatus for detecting interference between components in a design, the apparatus comprising: a processor circuit in communication with a memory circuit, the memory circuit providing instructions for the processor to: receive a first file containing a plurality of first design components, the plurality of first design components defining a first design aspect; receive a second file containing a plurality of second design components, the plurality of second design components defining a second design aspect; identify a reference point common to the plurality of first design components and the plurality of second design components; resolve the first plurality of components over the second plurality of components to form a compiled file; partition the complied file into a plurality of spatially independent portions, each portions defining at least one of the first or the second plurality of components; defining a bounding box for each of the plurality of the first components and the second components; identify an interference between two discrete components when the distance between two adjacent bounding boxes is below a minimum threshold value.

[0008] In still another embodiment, the disclosure provides a method for detecting interference between components in a design, the apparatus comprising: at a processor circuit in communication with a memory circuit, receiving a design file containing a plurality of discrete components resolved relative to each other; partitioning the design components into a first spatially independent partitions, each of the first partitions containing at least one of the plurality of discrete components; subdividing one of the first spatially independent partitions into second spatially independent partitions; forming a plurality of bounding boxes to enclose each respective components of the first and the second spatially independent partitions; and identifying an interference between two discrete components when a distance between two adjacent bounding boxes is below a threshold value.

[0009] In an embodiment of the disclosure, multiple design files of a model are combined to form a master file. The master file is then partitioned according to an algorithm such that each partition includes one or more component (objects). Partitioning can be implemented using 3D partitioning algorithms such as Octree. Once partitioned to multiple segments, each segment is assigned to an independent processor for clash/interference detection, or multiple segments can be assigned to one processor. Alternatively, the assignment may be done so as to have an overlapping assignment to processors such that two processors work on overlapping portions of the model. The processors may work independently of each other, or the processors may work conjunctively during or after the clash detection process. The interference results from all the processors are compiled to form a clash/interference report for the entire 3D model.

[0010] In still another embodiment of the disclosure, multiple design files of a 3D model are combined to form a master file. The master file is then subdivided into multiple parts. Each part is assigned to a separate processor for further processing. Alternatively, the assignment may be done so as to have overlapping assignment to processors, such that two processors work on overlapping portions of the model. Each processor then independently partitions its respective portion of the 3D file into segments. Each processor may implement a 3D partitioning algorithms such as Octree to partition its respective portion of the 3D design into segments. Next, each processor implements clash/interference detection to identify clashing or interfering components in a segment or in between different

segments. The processors may work independently of each other, or the processors may work conjunctively with each other during or after the clash detection process. The interference results from all the processors is then compiled to form a clash/interference report for the entire 3D model.

BRIEF DESCRIPTION OF THE DRAWINGS

[0011] These and other embodiments of the disclosure will be discussed with reference to the following exemplary and non-limiting illustrations, in which like elements are numbered similarly, and where:

[0012] Fig. 1 A is a flow diagram for implementing an embodiment of the disclosure;

[0013] Fig. IB is a flow diagram showing step 150 of Fig. 1;

[0014] Fig. 2 schematically illustrates partitioning a 3D model for efficient clash detection;

[0015] Fig. 3 is an exemplary clash detection flow diagram;

[0016] Fig 4 schematically illustrates a clash detection system; and

[0017] Fig. 5 is an exemplary clash detection report.

DETAILED DESCRIPTION

[0018] The disclosure provides a solution for clash detection in three-dimensional designs by allowing multiple members to work on a centrally-controlled version of the model. The disclosure also provides massively-parallel processing of the design file which, among others, enables rapid processing and version control. The model can be maintained at a remote server with significantly higher processing capability. Implementing clash detection on the remote server allows the system to take advantage of parallel processing. Complex 3D models can be readily identified and divided across multiple computational units. Each computational unit can be addressed to significantly increase processing speed.

[0019] Fig. 1 is a flow diagram for implementing an embodiment of the disclosure. The flow diagram of Fig. 1 may be implemented at a computer, at a remote server or as an application on a web-browser. The flow diagram may be implemented as an application software (or firmware) residing on a memory circuit in communication with a processor circuit. Each of the memory circuit or the processor circuit may comprise multiple memory modules and processor modules.

[0020] At step 110, the application receives CAD files relating to the design. The CAD files may comprise multiple files with varying formats. For example, the files may include electrical, mechanical or structural models which contribute to the overall design. Each of file may have a different format. Accordingly, at step 115, the received files are converted into a common format, i.e. , neutralized. The neutral format can be any format suitable for the application. After neutralization, the various design files may be combined to form a master file (i.e., compiled model).

[0021] At step 120, the master file is examined to determine the file's preliminary clash detection processing requirements. This can be evaluated, for example, by examining the size of the master file and processing resources required to run clash detection for such file. If the master file is large, the application executes a series of steps as shown in Fig. 2. On the other hand, if the master file is not extensive enough to warrant additional processing resources, at step 160, standard clash detection is run.

[0022] Fig. IB is a flow diagram of step 150 shown in Fig. 1. At step 152, the master file is partitioned into segments. Each segment may include one or more components. In one implementation, the master file is partitioned into segment (interchangeably, threads) with each segment having one or more components. A component can be any device, material or formation. For example, a component may be a door, a sump pump or a heating unit. Next, a bounding box is provided for each component of the master file. A bounding box is the smallest geometrical enclosure that can contain the entire component.

[0023] At step 154, processing resources are assigned to different segments of the master file for clash detection. Each segment may include one or more components. Segment selection can be automated by software or, as discussed below, can be controlled by the project coordinator. At step 156 clash detection is done. Clash detection can be performed, for example, on the basis of proximity of the components. Clash detection may also be used to identify physical interference between components. For example, a particular design may require sufficient repair space adjacent a mechanical unit. Clash detection can identify whether nearby objects protrude in the clearance space of the mechanical unit. Clash and interference detection can cover all dimensions. Finally, the clash detection results are reported at step 158.

[0024] Fig. 2 schematically illustrates partitioning a 3D model into parallel processing units for efficient clash detection. In Fig. 2, model 200 may be a building, an airplane or any other structural system. As shown in Fig. 2, the model is divided into threads 210 using bounding boxes 1 - n. Each thread may include one or more bounding boxes. In addition, different threads may have different bounding boxes.

[0025] At step 220, independent processing resources are applied to each of the respective threads. The resources may be massively parallel processing systems, each processing system computing clash probability for a respective thread or a portion thereof. The massively-parallel processing system may or may not be co-located with each other. In an exemplary embodiment, processing is done using cloud technology in which different cloud resources are allocated to different threads. At step 230, collision detection results are gathered from the parallel processing systems. As stated, the results may identify collision between components or impingement on allotted space at or near the various components. Collision detection is not limited to 2D detection and may include overhead space and other design intangibles. Interference detection may be directed at adjacent objects or at objects within a given proximity. For example, a fire emergency area may be monitored for obstacles which impede egress. Finally, the collision detection reports are compiled and the result is displayed. [0026] In an exemplary system for implementing clash detection, a processor circuit communicates with a memory circuit. The processor circuit and the memory circuit may be at remote servers, for example, on a distributed cloud network. Each of the processor and memory circuits may include functional elements needed for complex mathematical calculations. A processor circuit and memory may include computer system accessible through a network.

[0027] The memory circuit provides instructions for the processor to receive multiple CAD files. Each file containing a particular aspect of the design (e.g., mechanical, electrical, structural). Each file also includes multiple design components (e.g., doors, windows, pumps). Thus, the design components of the first file may represent the structural aspect of the model, showing doors and windows within the structure. The clash detection system also receives a second file containing the mechanical aspect of the model, including placement of mechanical components within the structure. The first file and the second file may have different, incompatible and vendor-specific formats. The clash detection application converts both design files to a neutral format suitable for parallel processing. The application also identifies a common reference point for each of the design models.

[0028] Using the common reference point, the clash detection system then resolves the structural components (components from the first file) over the mechanical components (components from the second file) to form a master file. In a non- limiting implementation, the first file is saved while the objects in the second file are not saved; rather, they are tested for clash one-by-one against the objects in the saved file.

[0029] The processing requirement for clash-detection of the master file can easily exhaust local resources. To address this problem, the clash detection application may partition the master file into a plurality of spatially independent portions or segments. An exemplary algorithm for partitioning 3D graphics of the master file is the octree algorithm.

[0030] The octree algorithm applies a tree structure in which each internal node has exactly eight sub-nodes or children. Octree is used to partition a three dimensional space by recursively subdividing it into eight octants where the octants are three-dimensional analogs of quadtrees. In this manner a complex 3D model is recursively subdivided until a plurality of simpler octants or independent segments are formed. Each independent segment defines at least one structural or mechanical component. [0031] A bounding box is then formed around each of the plurality of the partitioned components. An interference or a clash point can be identified when the distance between two proximal objects are below a predefined threshold value. Since numerous clash detections are processed independently of each other, interferences can be identified efficiently and accurately.

[0032] The task of partitioning a file into spatially independent segments may be done iteratively such that each segment is further sub-divided until such time that each component is entirely enclosed in a bounding box. In this implementation, the bounding box is the smallest spatial enclosure that completely encapsulates a particular component.

[0033] Fig 4 schematically illustrates a clash detection system. The exemplary system of Fig. 4 shows project coordinator 410. Project coordinator 410 includes an operator and a workstation. Project coordinator 410 communicates through cloud-based- network 420 with collaborators 412 and 414. Each collaborator may be a project team member or an external contributor. By way of example, collaborator 412 may comprise a team of structural design engineers and collaborator 414 may comprise a team of electrical engineers cooperating to design a warehouse (not shown).

[0034] Project coordinator 410 receives project plans from each of collaborators 412 and 414. The project plans may include 2D or 3D design files for the structural and electrical components of the warehouse. Project plans may also include cost estimate, expected completion date and any other project information. The project plans can be stored locally at coordinator's workstation 410 or can be stored at database (memory) 422 on the cloud server. If stored at database 422, coordinator 420 may grant access to collaborators 412 and 414 to access the individual design files or the maser file. The project coordinator may also organize the files so as to maintain version control, record history of changes or apply any other project management rule.

[0035] The design files may have format native to each of the collaborator. To compile a master file, project coordinator 410 converts the collaborators' files into neutral format file and determines whether the compiled file is complex enough to require significant clash detection resources. If the master file is deemed complex, the project coordinator may access parallel processing at the cloud for clash detection. Fig. 4 shows an exemplary embodiment where memory circuit 422 communicates with four processors, P1-P4. It is noted that the processor number is not limited to four and may include as few or as many processors needed to conduct complex mathematical calculations.

[0036] With simultaneous reference to Figs. 3 and 4, the clash detection application divides the 3D model captured in the master file into four threads based on, for example, the number of bounding boxes encapsulating the respective objects in the master file. Each thread is then assigned to one of processors P1-P4 for analysis. The processors work independently of each other and in a massively parallel mode to simultaneously process significant clash detection algorithms. The detected clashes are then compiled and reported back to coordinator 410.

[0037] The project coordinator may optionally change software control variables. For example, project coordinator 410 may give access to one or more of the collaborators. The access can be full or limited (e.g., limited in time or scope). Project coordinator may also track changes by controlling and creating new versions of the software. In another exemplary embodiment, the project coordinator may reset clash detection variables That is, the clearance distance between different objects may be changed in real-time to observe the effect on the 3D model.

[0038] The clash detection report may include different fields selected by the project coordinator. In an exemplary embodiment, the clash report includes a clash list, classification of the clashing objects (e.g., window, door, etc.), the actual and desired tolerance between the clashing objects and the priority assigned to each clash (e.g. , low, medium or critical). A 3D model may be included in the clash report showing the interfering objects. Fig. 5 is an exemplary clash report according to an embodiment of the disclosure. Specifically, Fig. 5 shows an exemplary clash detection application running on a web browser. As seen in Fig. 5, the clash detection application provides a background and a foreground dialog box. The background dialog box provides a file directory as well as action buttons (Upload,

Download, Check In/Out, Delete, New Folder, Message and View 3D). The foreground dialog box is a clash detection report showing nine detected clashes, of which one is identified as critical. In addition, the clash detection report provides a 3D visual

representation of the selected clash. The foreground dialog box states that there is an interference between a slab and a plate. The user may select other identified clashes from the selection box for visual display. The menu of the foreground dialog also provides action buttons including, zoon, 3D, snapshot, etc. [0039] The clash detection application may additionally keep track of various equipment, their locations and service parameters. For example, the application may be queried to identify locations of the heating units in the design. The report may consist of an itemized list and/or 3D thumbnail illustration of the queried equipment. Once displayed, the project coordinator can further query the unit' s service history or operation manual which may be stored on the same database.

[0040] In still another embodiment, the web-based application enables cost control. That is, project coordinator 410 can readily determine the cost associated with each design change. For example, replacement or relocation of a heating unit may have an immediate financial impact on the project budget. Using massively parallel processing capability disclosed herein, the budgetary impact of every design change can be immediately assessed. Finally, the application provides processing capability beyond clash detection allowing post- construction changes to viewed.

[0041] While the principles of the disclosure have been illustrated in relation to the exemplary embodiments shown herein, the principles of the disclosure are not limited thereto and include any modification, variation or permutation thereof.