MEP Design Coordination - WordPress.com

Assignment 2 – Scheduling & 4D Simulation Group 2

0

This report focuses on exploring BIM-based

mechanical, electrical and plumbing (MEP)

clash detection using Autodesk Navisworks

Manage. The objective is to learn how to

use Navisworks to automatically detect

clashes in the model, as well as analyze

which of the automatically identified

clashes are true positives

MEP Design Coordination

Assignment 3 October 26th, 2017

Katlin Woodburn Jaqueline Martinez Gopika Nandanan Group 2

Assignment 3 – MEP Design Coordination Group 2

1

Table of Contents

CHAPTER 1 INTRODUCTION .......................................................................................................................................... 1

CHAPTER 2 PRESENTATION OF RESULTS AND ANALYSIS ............................................................................... 1

2.1 Electrical and HVAC .................................................................................................................................................... 2

2.2 Plumbing and HVAC ................................................................................................................................................... 3

2.3 Plumbing and Electrical ............................................................................................................................................ 4

2.4 Fire Protection and HVAC ........................................................................................................................................ 4

2.5 Fire Protection and Electrical ................................................................................................................................. 5

2.5 Fire Protection and Plumbing ................................................................................................................................ 6

CHAPTER 3 ADVANTAGES AND LIMITATIONS OF CLASH DETECTION AND PROCESS IMPROVEMENT

IN NAVISWORKS MANAGE .............................................................................................................................................. 6

CHAPTER 4 FALSE NEGATIVES ..................................................................................................................................... 7

CHAPTER 5 CONSIDERATIONS WHEN CREATING A BIM MODEL TO OBTAIN ACCURATE RESULTS IN

AUTOMATIC CLASH DETECTION.................................................................................................................................. 7

List of figures

Figure 1 HVAC & Electrical clashes 1 & 2 ........................................................................................................ 2

Figure 2 HVAC & Electrical clashes 11, 13 & 14. ............................................................................................ 2

Figure 3 HVAC & Electrical clash 12 ................................................................................................................ 3

Figure 4 Fire Protection and Electrical Clashes 1, 2, 3, & 4 ........................................................................... 5

Figure 5 Fire Protection and Electrical Clash 2 .............................................................................................. 6

Figure 6 Fire Protection and HVAC Clashes 24, 25, 26, 27, 29, & 30 ............................................................ 6

List of Tables

Table 1 Count of clashes between pairs of subcontractors. .......................................................................................... 1

Table 2 Precision and recall of clash detection between pairs of subcontractors ............................................... 1

Appendices

Appendix A Clash Report


1

CHAPTER 1

INTRODUCTION

Among one of the uses of BIM technology is MEP design coordination, specifically for clash detection, to identify potential collisions between the various subcontractors involved in the construction project. The implementation of this BIM application is generally done once the construction phase has initiated, as part of the planning phase for the mechanical, electrical and plumbing systems clashing analysis to mitigate the costs and potential delays these collisions could cause if encountered for the first time on the field.

For this assignment, our group explored BIM-based mechanical, electrical and plumbing (MEP) clash detection using Navisworks Manage. Through this assignment, we automatically detected clashes in a model between different pairs of subcontractors and further analysed the automatically identified clashes to categorize them as true or false positive. The model corresponded to the second floor of an academic building in Pennsylvania.

CHAPTER 2 PRESENTATION OF RESULTS AND ANALYSIS Upon completing the automatic clash detection identification in Navisworks Manage, we analyzed

the results to determine which clashes were true positive and which were false positive. The pair of

subcontractors in which we encountered the highest total automatically detected clashes was Fire

Protection and HVAC with 31 clashes. However, the count of true positive clashes was narrowed

down to eight, the rest were just making noise; as a result, this led to a low precision of clash

detection between these subcontractors. The pair of subcontractors that had the least total

automatically detected clashes was Plumbing and Electrical; they had zero.

Table 1 presents the count of clashes between the pairs of subcontractors and table 2 presents the

precision and recall of those detected clashes.

Table 1 Count of clashes between pairs of subcontractors.

Table 2 Precision and recall of clash detection between pairs of subcontractors

AT FP TP AT FP TP AT FP TP AT FP TP

HVAC 15 9 6 23 13 10 31 23 8

Electrical 0 0 0 4 3 1

Plumbing 2 0 2

Fire Protection

HVAC Electrical Plumbing Fire Protection

Precision Recall Precision Recall Precision Recall Precision Recall

HVAC 0.4 1 0.43 1 0.26 1

Electrical 0 0 0.25 1

Plumbing 1 1

Fire Protection

HVAC Electrical Plumbing Fire Protection


2

The results and analysis will be presented per pair of subcontractors for which the tests were

performed.

2.1 Electrical and HVAC Navisworks produced a total of 15 clashes between HVAC and electrical. Upon analysis, 6 clashes

were found to be true positive and the remaining 9 as false positive. Groups were created on the

following basis:

Methodology 1- Clashes that were detected by Navisworks more than once as part of the

same component; therefore, the relocation of one component solves both clashes.

Figure 1 HVAC & Electrical clashes 1 & 2

Note: In figure 1, HVAC is represented in red and Electrical in green.

In example above, two clashes are recorded as part of one component. This overlapping clash is

generated since the light fixture (shown in green) is modeled as more than one object. Therefore,

the two clashes were grouped into one and clash 1 (shown in red in figure 1) was assigned as an

active clash and clash 2 (shown in green in figure 1) was assigned as a resolved clash. Active

clashes were recorded as True Positives (TP) and resolved clashes were recorded as False

Positives (FP) on the table.

Clashes that were grouped on this basis are as follows;

1. Clashes 1 & 2 2. Clashes 3 & 10

Methodology 2- Clashes recorded by Navisworks as occurring in two different components

but are in the same room or at the same level.

These clashes were grouped since they were observed to be of the same kind and can be resolved

by implementing one solution. An example of this type is shown in figure 2 below.

Figure 2 HVAC & Electrical clashes 11, 13 & 14.


3

In Figure 2, the light fixture clashes are observed in a single room. It must, however, be pointed out

that clash 13 is not in the same level as 11 and 14 but was included in the same group as the solution

to resolving all three clashes is the same.

As mentioned above, Clash 11 was assigned as an active clash (shown in red in figure 2) and clashes

13 and 14 were assigned as resolved clashes (shown in yellow in figure 2). Active clashes were

recorded as True Positives (TP) and resolved clashes as False Positives (FP) in the table.

Clashes that were grouped on this basis are as follows;

1. Clashes 4, 5, 6, 7, 8 & 9

2. Clashes 11, 12 & 14

Methodology 3- Clashes that were produced by Navisworks as a single clash and didn’t

require any grouping.

These clashes were assigned as Active Clashes and recorded in the table as a True clash. An

example is shown below.

Figure 3 HVAC & Electrical clash 12

2.2 Plumbing and HVAC Navisworks produced a total of 23 clashes between Plumbing and HVAC. Upon further analysis, 10

clashes were found to be true positive and the remaining 13 as false positive. Groups were created

on the same basis as Electrical and HVAC. The results are presented, an example is provided:

Methodology 1- clashes detected more than once as part of the same component.

1. 4 & 8

2. 5, 10, & 12

3. 6 & 7

4. 9 & 19

5. 11, 15, & 18

6. 16, 20, & 23

7. 21 & 22

Figure 4 Plumbing & HVAC clashes 5, 10 & 12


4

Methodology 2- clashes occurring in two different components but in the same room or at

the same level.

1. 1, 2, 3 & 14

Figure 5 Plumbing & HVAC clashes 1, 2, 3 & 14

Methodology 3- single clashes and didn’t require any grouping.

1. 13

2. 17

Figure 6 Plumbing & HVAC clash 13

2.3 Plumbing and Electrical Navisworks did not detect any clashes between the Plumbing and Electrical systems.

2.4 Fire Protection and HVAC Navisworks produced a total of 31 clashes between Fire Protection and HVAC. Upon further

analysis, 8 clashes were found to be true positive and the remaining 23 as false positive. Groups

were created on the same basis as Electrical and HVAC & Plumbing and HVAC. The results are

presented, an example is provided:

Methodology 1- clashes detected more than once as part of the same component.

1. 5 & 22

Figure 6 Fire Protection & HVAC clashes 5 & 22


5

Methodology 2- clashes occurring in two different components but in the same room or at

the same level.

1. 1, 3 & 6

2. 4, 7, 9, 14, 15, 18, & 23

3. 8, 10, 17, 19, & 20

4. 11, 12, & 28

5. 13, 16, 21, & 31

6. 24, 25, 26, 27, 29, & 30

Figure 7 Fire Protection & HVAC clashes 1, 3 & 6

Methodology 3- single clashes and didn’t require any grouping.

1. 2

Figure 8 Fire Protection & HVAC clash 2

2.5 Fire Protection and Electrical Navisworks produced a total of 4 clashes between Fire Protection and Electrical. Of these 4 clashes,

only one of them was a true positive, the other three false positive. The clashes are shown in the

image below. The fire protection is in green and electrical in red.

Figure 4 Fire Protection and Electrical Clashes 1, 2, 3, & 4


6

2.5 Fire Protection and Plumbing

Navisworks produced a total of 2 clashes between Fire Protection and Plumbing. Both detected clashes are true positives. One of the clashes is shown in the image below. The fire protection is in green and plumbing in red.

Figure 5 Fire Protection and Electrical Clash 2

CHAPTER 3 ADVANTAGES AND LIMITATIONS OF CLASH DETECTION AND PROCESS IMPROVEMENT IN NAVISWORKS MANAGE

There are many advantages of using software systems like Navisworks Manage to detect clashes.

Navisworks allows for multiple models to be imported into a single file while keeping the individuality

of the models to run direct comparisons and analysis on two models at a time. Detecting clashes

before construction begins is important to assure the project is not delayed. Instead of the clashes

being detected at the field during installation, the clash is detected when running the clash detection

test and comparing the two models. Additionally, the different elements of a model can be color

coded to easily distinguish between disciplines. This helps with clarifications and visualization. A

project that is delayed generally leads to an increase in costs due to labor and equipment. Therefore,

the use of clash detection in Navisworks Manage is beneficial to both the schedule and budget of

the project.

Figure 6 Fire Protection and HVAC Clashes 24, 25, 26, 27, 29, & 30

While Navisworks has several advantages that are beneficial to projects, there are also some

limitations in the software. Navisworks detects all clashes that it can find, some of which include

duplicates and multiple clashes that can be fixed with one adjustment. These are classified as false

positives because while the software picks up multiple issues, they only need to be addressed once.


7

For example, in the image above, six clashes are detected. Only one of these would be classified as

a true positive that needs to be addressed, all the others would be classified as false positives and

no longer need to be addressed. The limitation of Navisworks is that a human then needs to go and

analyze every clash detected to see if they are indeed true positive or if they are false positive.

CHAPTER 4 FALSE NEGATIVES

There are likely several false negatives that should have been identified and addressed but were not

because they were not modeled. Some examples of false negatives would be hangers, and cables.

The reason for these examples not being modeled is that models generally only represent objects

greater than ¾ inch, which is larger than most hangers and cables. This issue can be minimized by

either decreasing the size limit for objects modeled or to manually explore the models and make

sure elements aren't in the way of where projected hangers or cables would be installed. While both

alternatives are time consuming, they would help in the long run to assure there are no clashes once

construction begins.

CHAPTER 5 CONSIDERATIONS WHEN CREATING A BIM MODEL TO OBTAIN ACCURATE RESULTS IN AUTOMATIC CLASH DETECTION

As mentioned in Chapter 3, there are several components that cannot be modelled in BIM, such as

the hangers and cables. All such components must be listed down and brought to the notice of the

person creating the BIM model and care should be taken when modelling to allocate space for

objects that cannot be modeled.

As we know, most clashes are a result of noise and single components modelled as more than one

object. This could result in double counting of clashes. Modelling components as a single object

could solve this issue; however, this might not be possible in all cases as the complexity or shape of

the object can make it difficult. The clash detection analysis must therefore focus on not double

counting in such scenarios.

Also, another consideration is that building components must be grouped and named properly.

HVAC, Mechanical, and Electrical systems should be identified and elements within them such as

light fixtures, pipelines should be properly named and assigned different colors to avoid any

ambiguity. This also helps to conduct an easy clash analysis for people who are new to the clash

detection analysis.

Additionally, it would be beneficial if the names of the components were provided along with the

model on screen. Presently, one has to click on the component and then the selection tree to check

the type of component which could get tedious. The modeler must, therefore, take great care in

correctly assigning the component names within disciplines. For example, light fixtures within

electrical.


8

Appendix A: Clash Report

Clash Report

HVACElectrical Tolerance Clashes New Active Reviewed Approved Resolved Type Status0.000m 6 0 6 0 0 0 Hard OK

Item 1 Item 2

Image Clash Group

Clash Name Status Distance Description Date Found Clash

Point Item ID Layer Item Name Item Type Item ID Layer Item Name Item

Type

Clashes 1 & 2 Active 0.158 Hard 2017/10/24

20:15.24

x:70.586, y:42.882, z:280.838

Entity Handle: 28E7B

()HVAC _ducts_return


PolyFace Mesh

Entity Handle: 332A8

()Elect_Fluorescent_LF.EL ()Elect_Fluorescent_LF.EL Subentity

Clashes 1 & 2 Clash1 Active 0.158 Hard 2017/10/24

20:15.24

x:70.586, y:42.882, z:280.838




PolyFace Mesh



Clashes 1 & 2 Clash2 Resolved 0.137 Hard 2017/10/24

20:15.24

x:70.586, y:42.882, z:280.889




PolyFace Mesh




20:15.24

x:63.024, y:40.024, z:281.354

Entity Handle: 13716

()HVAC _Piping _HHWS


PolyFace Mesh

Entity Handle: 332B8



20:15.24

x:63.024, y:40.024, z:281.354




PolyFace Mesh




20:15.24

x:63.042, y:40.048, z:281.405




PolyFace Mesh



Clashes 4, 5, 6, 7, 8 & 9

Active 0.031 Hard 2017/10/24 20:15.24

x:59.781, y:6.981, z:281.226

Entity Handle: 2A9AF

()HVAC _ducts_exhaust


PolyFace Mesh

Entity Handle: 32FC8


Clashes 4, 5, 6, 7, 8 & 9

Clash4 Active 0.031 Hard 2017/10/24 20:15.24

x:59.781, y:6.981, z:281.226




PolyFace Mesh



Page 1 of 3Clashes

10/26/2017file:///C:/Users/pgn239/Desktop/HVAC-Electrical.html

Clashes 4, 5, 6, 7, 8 & 9

Clash5 Resolved 0.031 Hard 2017/10/24 20:15.24

x:59.492, y:7.033, z:281.236




PolyFace Mesh



Clashes 4, 5, 6, 7, 8 & 9


x:59.464, y:9.382, z:281.226

Entity Handle: 27BD1



PolyFace Mesh

Entity Handle: 32F88


Clashes 4, 5, 6, 7, 8 & 9


x:59.187, y:9.346, z:281.257

Entity Handle: 27BD1



PolyFace Mesh



Clashes 4, 5, 6, 7, 8 & 9


x:59.468, y:7.214, z:281.257




PolyFace Mesh



Clashes 4, 5, 6, 7, 8 & 9


x:59.221, y:9.091, z:281.257




PolyFace Mesh



Clashes 11, 13 & 14

Active 0.006 Hard 2017/10/24 20:15.24

x:43.439, y:3.889, z:279.298

Entity Handle: 1AECB

()HVAC _ducts_Equipment


PolyFace Mesh

Entity Handle: 31A3F

()Elect_Incandescent_LF.EL

()Elect_Incandescent_LF.EL Subentity

Clashes 11, 13 & 14


x:43.439, y:3.889, z:279.298

Entity Handle: 1AECB



PolyFace Mesh




Clashes 11, 13 & 14


x:45.548, y:1.485, z:279.171

Entity Handle: 1AE77



PolyFace Mesh




Clashes 11, 13 & 14


x:47.722, y:2.411, z:279.552

Entity Handle: 1AEA1



PolyFace Mesh




Clash12 Active 0.006 Hard Subentity

Page 2 of 3Clashes


2017/10/24 20:15.24

x:64.128, y:6.650, z:280.111

Entity Handle: 10E33



PolyFace Mesh





x:62.356, y:10.624, z:280.034

Entity Handle: 1ACB5



PolyFace Mesh




Page 3 of 3Clashes


Clash Report

PlumbingHVAC Tolerance Clashes New Active Reviewed Approved Resolved Type Status0.000m 10 0 10 0 0 0 Hard OK

Item 1 Item 2

Image Clash Group

Clash Name Status Distance Description Date Found Clash Point Item ID Layer Item Name Item Type Item ID Layer Item Name Item Type

Clashes 1,2,3 & 14 Active 0.189 Hard 2017/10/26

17:51.45

x:64.217, y:18.361, z:280.548


()PLUMB _waste _vent


PolyFace Mesh

Entity Handle: 29A1B

()HVAC _ducts_supply


PolyFace Mesh

Clashes 1,2,3 & 14 Clash1 Active 0.189 Hard 2017/10/26

17:51.45

x:64.217, y:18.361, z:280.548




PolyFace Mesh

Entity Handle: 29A1B



PolyFace Mesh

Clashes 1,2,3 & 14 Clash2 Resolved 0.163 Hard 2017/10/26

17:51.45

x:64.413, y:17.066, z:280.510




PolyFace Mesh




PolyFace Mesh


17:51.45

x:64.052, y:19.434, z:280.532




PolyFace Mesh

Entity Handle: 29FFD



PolyFace Mesh


17:51.45

x:64.374, y:17.363, z:280.509




PolyFace Mesh

Entity Handle: 28C3D



PolyFace Mesh


17:51.45

x:47.664, y:14.755, z:280.532




PolyFace Mesh




PolyFace Mesh


17:51.45

x:47.664, y:14.755, z:280.532




PolyFace Mesh




PolyFace Mesh


17:51.45

x:47.661, y:15.080, z:280.578




PolyFace Mesh




PolyFace Mesh

Clashes 5, 10 & 12

Active 0.048 Hard 2017/10/26 17:51.45

x:63.426, y:12.737, z:281.393

Entity Handle: 2D871

()PLUMB _drain _storm


PolyFace Mesh

Entity Handle: 2E82A

()HVAC _Piping _CHWR


PolyFace Mesh

Page 1 of 4Clashes

10/26/2017file:///C:/Users/pgn239/Desktop/Plumbing-HVAC.html

Clashes 5, 10 & 12 Clash5 Active 0.048 Hard 2017/10/26

17:51.45

x:63.426, y:12.737, z:281.393




PolyFace Mesh

Entity Handle: 2E82A



PolyFace Mesh

Clashes 5, 10 & 12 Clash10 Resolved 0.032 Hard 2017/10/26

17:51.45

x:63.222, y:12.733, z:281.422




PolyFace Mesh




PolyFace Mesh

Clashes 5, 10 & 12 Clash12 Resolved 0.019 Hard 2017/10/26

17:51.45

x:63.309, y:12.650, z:281.635




PolyFace Mesh




PolyFace Mesh


17:51.45

x:65.476, y:13.284, z:280.558

Entity Handle: 2DDFB

()PLUMB _drain _RainWater


PolyFace Mesh

Entity Handle: 12ABE

()HVAC _Piping _CHWS


PolyFace Mesh


17:51.45

x:65.476, y:13.284, z:280.558




PolyFace Mesh

Entity Handle: 12ABE



PolyFace Mesh


17:51.45

x:65.485, y:13.334, z:280.293




PolyFace Mesh

Entity Handle: 12A6A



PolyFace Mesh


17:51.45

x:63.328, y:13.105, z:281.111

Entity Handle: 2DE15



PolyFace Mesh

Entity Handle: 11EE4



PolyFace Mesh


17:51.45

x:63.328, y:13.105, z:281.111




PolyFace Mesh

Entity Handle: 11EE4



PolyFace Mesh


17:51.45

x:63.621, y:13.133, z:281.136




PolyFace Mesh

Entity Handle: 11F4C



PolyFace Mesh

Clashes 11, 15 & 18

Active 0.029 Hard 2017/10/26 17:51.45

x:64.677, y:19.879, z:281.081

Entity Handle: 2B0F3

()PLUMB _waste _Sanitary


PolyFace Mesh

Entity Handle: 128DE



PolyFace Mesh

Clash11 Active 0.029 Hard

Page 2 of 4Clashes


Clashes 11, 15 & 18

2017/10/26 17:51.45

x:64.677, y:19.879, z:281.081




PolyFace Mesh




PolyFace Mesh

Clashes 11, 15 & 18


x:64.676, y:19.837, z:280.927

Entity Handle: 14AB6



PolyFace Mesh




PolyFace Mesh

Clashes 11, 15 & 18


x:64.638, y:19.910, z:281.055




PolyFace Mesh

Entity Handle: 1299A



PolyFace Mesh


x:64.828, y:21.730, z:280.766




PolyFace Mesh




PolyFace Mesh

Clashes 16, 20 & 23

Active 0.006 Hard 2017/10/26 17:51.45

x:73.285, y:35.931, z:275.793

Entity Handle: 2B2AD



PolyFace Mesh

Entity Handle: 1AC85



PolyFace Mesh

Clashes 16, 20 & 23


x:73.285, y:35.931, z:275.793

Entity Handle: 2B2AD



PolyFace Mesh




PolyFace Mesh

Clashes 16, 20 & 23


x:73.364, y:35.859, z:275.793

Entity Handle: 2F2AD



PolyFace Mesh




PolyFace Mesh

Clashes 16, 20 & 23


x:73.448, y:35.197, z:275.793




PolyFace Mesh




PolyFace Mesh


x:70.605, y:21.989, z:275.793




PolyFace Mesh




PolyFace Mesh

Clsahes 21 & 22 Active 0.000 Hard 2017/10/26

17:51.45

x:68.273, y:24.356, z:275.793

Entity Handle: 2F6DE



PolyFace Mesh




PolyFace Mesh

Clsahes 21 & 22 Clash21 Active 0.000 Hard 2017/10/26

17:51.45

x:68.273, y:24.356, z:275.793

Entity Handle: 2F6DE



PolyFace Mesh




PolyFace Mesh

Page 3 of 4Clashes


Clsahes 21 & 22


x:68.207, y:24.437, z:275.793




PolyFace Mesh




PolyFace Mesh

Page 4 of 4Clashes


Clash Report

HVACFP Tolerance Clashes New Active Reviewed Approved Resolved Type Status0.000m 8 0 8 0 0 0 Hard Old

Item 1 Item 2

Image Clash Name Status Distance Description Date Found Clash Point Item ID Layer Item Name Item Type Item ID Layer Item Name Item Type

Clashes 1, 3 & 6 Active 0.305 Hard 2017/10/19 21:30.44

x:63.655, y:19.386, z:279.516

Entity Handle: 29FFD



PolyFace Mesh

Entity Handle: 1C09B

()FP _pipe _SP

()FP _pipe _SP

PolyFace Mesh


x:64.232, y:23.499, z:277.524

Entity Handle: 278CF



PolyFace Mesh

Entity Handle: 1C067

()FP _pipe _SP

()FP _pipe _SP

PolyFace Mesh

Clashes 4,7,9,14,15,18, & 23 Active 0.131 Hard 2017/10/19

21:30.44x:62.598, y:22.202, z:280.153

Entity Handle: 27AD5



PolyFace Mesh

Entity Handle: 1C3D9

()FP _pipe _SP

()FP _pipe _SP

PolyFace Mesh

Clashes 5 & 22 Active 0.020 Hard 2017/10/19 21:30.44

x:68.616, y:42.588, z:280.154

Entity Handle: 12AF2

()HVAC _Piping _HHWR

()HVAC _Piping _HHWR

PolyFace Mesh

Entity Handle: 1BCF1

()FP _pipe _SP

()FP _pipe _SP

PolyFace Mesh

Clashes 8,10,17,19, 20 Active 0.087 Hard 2017/10/19

21:30.44x:64.180, y:24.702, z:277.524

Entity Handle: 28EA5



PolyFace Mesh

Entity Handle: C89D

()FP _pipe _F

()FP _pipe _F

PolyFace Mesh

Clashes 11, 12 & 28 Active 0.075 Hard 2017/10/19 21:30.44

x:63.178, y:15.509, z:280.825

Entity Handle: 27AB9



PolyFace Mesh

Entity Handle: C959

()FP _pipe _F

()FP _pipe _F

PolyFace Mesh

Clashes 13, 16, 21, & 31 Active 0.057 Hard 2017/10/19

21:30.44x:62.763, y:15.488, z:280.922

Entity Handle: 29CB5



PolyFace Mesh

Entity Handle: CC54

()FP _pipe _FSP

()FP _pipe _FSP

PolyFace Mesh

Clashes 24,25,26,27,29 & 30 Active 0.019 Hard 2017/10/19

21:30.44x:56.244, y:11.892, z:280.887




PolyFace Mesh

Entity Handle: CD78

()FP _pipe _FSP

()FP _pipe _FSP

PolyFace Mesh

Page 1 of 2Clashes

10/19/2017file:///C:/Users/pgn239/Downloads/HVAC-FP.html

Clash Report

FPElec Tolerance Clashes New Active Reviewed Approved Resolved Type Status0.000m 1 0 1 0 0 0 Hard OK

Item 1 Item 2

Image Clash Group

Clash Name Status Distance Description Date Found Clash

Point Item ID Layer Item Name

Item Type Item ID Layer Item Name Item

Type

Clashes 1,2, 3 & 4

Active 0.061 Hard 2017/10/26 17:48.20

x:56.194, y:18.376, z:280.360

Entity Handle: CA0B

()FP _pipe _F

()FP _pipe _F

PolyFace Mesh




Clashes 1,2, 3 & 4


x:56.194, y:18.376, z:280.360

Entity Handle: CA0B

()FP _pipe _F

()FP _pipe _F

PolyFace Mesh




Clashes 1,2, 3 & 4


x:56.194, y:18.376, z:280.310

Entity Handle: CA0B

()FP _pipe _F

()FP _pipe _F

PolyFace Mesh




Clashes 1,2, 3 & 4


x:56.520, y:18.380, z:280.360

Entity Handle: 1CA93

()FP _pipe _Drain

()FP _pipe _Drain

PolyFace Mesh




Clashes 1,2, 3 & 4


x:56.520, y:18.380, z:280.310

Entity Handle: 1CA93

()FP _pipe _Drain

()FP _pipe _Drain

PolyFace Mesh




Page 1 of 1Clashes

10/26/2017file:///C:/Users/pgn239/Desktop/FP-Elec.html

Clash Report

FP-Plumbing Tolerance Clashes New Active Reviewed Approved Resolved Type Status0.000m 2 0 2 0 0 0 Hard OK

Item 1 Item 2

Image Clash Name Status Distance Description Date Found Clash Point Item ID Layer Item

Name Item Type Item ID Layer Item Name Item Type


x:63.048, y:12.732, z:280.939

Entity Handle: CC3A

()FP _pipe _FSP

()FP _pipe _FSP

PolyFace Mesh

Entity Handle: 2DB57



PolyFace Mesh


x:51.970, y:1.583, z:279.932

Entity Handle: 1C32D

()FP _pipe _SP

()FP _pipe _SP

PolyFace Mesh




PolyFace Mesh

Page 1 of 1Clashes

10/26/2017file:///C:/Users/pgn239/Desktop/FP-Plumbing.html

Documents

MEP Design Coordination - WordPress.com