DDC 1 Elizabeth Lau ModelCoordinationReport
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
16212 – Digital Design and Construction<br />
Assessment Task; UTS Central Project<br />
Model Coordination Audit<br />
16212 Digital Design and Construction 1<br />
Autumn 2017 - Assessment Task 2<br />
UTS Building 2 Central Model Coordination Review<br />
Lecturer: Julie Jupp<br />
Student: <strong>Elizabeth</strong> <strong>Lau</strong> – 12609842<br />
0
16212 – Digital Design and Construction<br />
Assessment Task; UTS Central Project<br />
Model Coordination Audit<br />
Contents<br />
1.0 Executive Summary ................................................................ 2<br />
2.0 Federated Model Review Outcomes ....................................... 4<br />
Model Coordination Reporting ................................................................................... 4<br />
UTS BIM MODEL AND CO-ORDINATION REVIEW TEMPLATE ...................................... 4<br />
PROJECT OVERVIEW ..................................................................................................... 4<br />
MODEL SUMMARY ......................................................................................................... 4<br />
Level 15 – UTS Building ............................................................................................... 5<br />
Roof Level ................................................................................................................... 22<br />
3.0 Summary of Findings ............................................................ 43<br />
4.0 Appendices .......................................................................... 44<br />
1
16212 – Digital Design and Construction<br />
Assessment Task; UTS Central Project<br />
Model Coordination Audit<br />
1.0 Executive Summary<br />
This independent model audit report has been produced on the behalf of the Client<br />
University of Technology Sydney (UTS) to identify the most significant critical elements and<br />
services clashes within a federated model (LAU_Task02-Building2_Lv15+LvRoof[C]) of UTS’<br />
Building 2 Central Project.<br />
This federated model includes the following models:<br />
‣ Structural Building Model;<br />
‣ Architectural Building Model;<br />
‣ Architectural Façade Building Model;<br />
‣ Mechanical Building Model;<br />
‣ Electrical Building Model;<br />
‣ Hydraulic (Drainage) Building Model;<br />
‣ Hydraulic (Water & Gas) Building Model;<br />
‣ Fire Building Model.<br />
The UTS Central Project is redevelopment<br />
project involving the demolition of the<br />
existing precast Building 2 on Broadway<br />
Road and the design and construction of a<br />
new glass clad reinforced concrete<br />
building. The building is 17 stories high and<br />
will be the new location of UTS’ library in<br />
addition to the new teaching facilities.<br />
Figure 1: Site map of the new Building 2<br />
Background and BIM Benefits<br />
Building Information Models are Multi-dimensional, data rich and intelligent models that are<br />
changing modern day construction projects. BIM offers amplitude of opportunities such as<br />
improved visualisation and the efficient identification and analysis of clashes between multidisciplined<br />
systems. In doing so this enables a range of project benefits from cost savings,<br />
time savings and risk minimization upon construction phase of projects.<br />
This audit report focuses on the investigation and findings of a BIM which has been<br />
processed through Navisworks to determine a range of varying clashes and potential<br />
resolution opportunities. During the audit, clash instances were located, identified, and an<br />
assessment was made on their severity and resolution strategies.<br />
The process behind this audit involved the use of Naviswork’s internal clash detection<br />
function and the manual inspection of the automated results in a range of different viewing<br />
options including ghosted line models, exported tables and solid 3D component models.<br />
2
16212 – Digital Design and Construction<br />
Assessment Task; UTS Central Project<br />
Model Coordination Audit<br />
BIM Limitations<br />
Although the use BIM provides great opportunities for resolving clashes in an efficient<br />
manner, the relevancy of its opportunities was hindered by the issue of resolving<br />
constructability issues, but potentially creating design compliancy issues. For example, if a<br />
set of fire sprinkler were intersecting a network of mechanical ducts and resolved by shifting<br />
1000mm from its original location, this may alter the originally compliant distancing of fire<br />
sprinklers.<br />
Compliancy issues could be resolved by the inclusion of additional information libraries such<br />
as the NCC and compliancy detection functions in following versions of Naviswork.<br />
Another limitation identified during this audit was that identification and proposed resolution<br />
of building clashes is redundant unless all design consultants are using federated models<br />
with real time changes to model being viewable by all. This would decrease the chances of<br />
new changes creating further knock-on effects with the next model revision release.<br />
Figure 2: Federated Building 2 Model in Navisworks<br />
3
16212 – Digital Design and Construction<br />
Assessment Task; UTS Central Project<br />
Model Coordination Audit<br />
2.0 Federated Model Review Outcomes<br />
Model Coordination Reporting<br />
UTS BIM MODEL AND CO-ORDINATION REVIEW TEMPLATE<br />
PROJECT OVERVIEW<br />
Project Details<br />
Project Name: UTS Central Project – Building 2<br />
Project Address: 15 Broadway Ultimo NSW 2007<br />
Client Name:<br />
University of Technology (UTS)<br />
Date of Audit: (Commenced) 6/04/2017<br />
MODEL SUMMARY<br />
Federated Model File Name Size Rev. No. Rev. Date<br />
Co-ordination Model LAU_Task02-Building2_Lv15+LvRoof[C] 21,902KB 1 6/04/2017<br />
Discipline Models File Name Size Rev. No. Rev. No.<br />
Architectural CB02_A-FJMT-Architecture-IFC[AE] 7,673 KB 1 6/04/2017<br />
Facade CB02_A-FJMT-Façade-IFC[AE] 11,255 KB 1 6/04/2017<br />
Structure CB02 Structure IFC2x3 2,186 KB 1 6/04/2017<br />
Mechanical CB02_M-SVA-Mechanical-RVT[AA] 10,086 KB 1 6/04/2017<br />
Hydraulic<br />
CB02_H-ERB-Drainage-NWC[O]<br />
4,413 KB<br />
CB02_H-ERB-Pressure-NWC[O]<br />
5,010 KB<br />
1 6/04/2017<br />
Electrical CB02_E-JHA-Electrical-NWC[AC] 1,290 KB 1 6/04/2017<br />
Fire CB02_R-ERB-Fire-NWC[O] 15,756 KB 1 6/04/2017<br />
4
16212 – Digital Design and Construction<br />
Assessment Task; UTS Central Project<br />
Model Coordination Audit<br />
Level 15 – UTS Building<br />
Visual Hot Spots Check by #12609842 for Level 15<br />
Item<br />
No.<br />
Location Model Image Clash<br />
Type<br />
(Hard/<br />
Soft)<br />
Description of<br />
Clash and/or<br />
Root Cause<br />
Suggested<br />
Action /<br />
Comments<br />
Disciplines<br />
responsible/<br />
Assigned to<br />
Severity of Clash and<br />
Why<br />
Clashed Systems<br />
Count of<br />
clashes in<br />
local area<br />
1.0 Navisworks Clash Detection<br />
1.1 Level 15<br />
1.1.1 LVL.15 Hard<br />
Drainage system<br />
is intersecting a<br />
section of rigid<br />
mechanical<br />
duct, with<br />
pressurized fire<br />
pipes also<br />
intersecting duct<br />
in that area.<br />
A coordination<br />
design<br />
meeting<br />
between<br />
mechanical,<br />
fire and<br />
hydraulic to be<br />
arranged. The<br />
architect may<br />
also need to<br />
be invited to<br />
this meeting<br />
due to<br />
potential<br />
requirement of<br />
dropping<br />
ceiling height<br />
below to<br />
accommodat<br />
e necessary<br />
drainage runs.<br />
Disciplines that<br />
would be<br />
involved in the<br />
resolution of<br />
these identified<br />
clashes would<br />
include the<br />
Mechanical, Fire,<br />
Hydraulic<br />
Engineers, and<br />
also the project<br />
Architect.<br />
Clash severity for this<br />
hotspot is high due to<br />
the complexity of<br />
these clashes and the<br />
knock on effects such<br />
as ceiling height<br />
changes that may<br />
arise when resolving<br />
this hotspot.<br />
Hydraulic Building<br />
System<br />
Mechanical<br />
Building System<br />
Fire Building System<br />
. 6 - Clashes<br />
identified<br />
by visual<br />
inspection<br />
of the area.<br />
1.1.2<br />
LVL.15 Hard Fire pipe<br />
intersecting with<br />
Mechanical<br />
HVAC System in<br />
multiple<br />
locations.<br />
The root cause<br />
includes height<br />
of the Wet Fire<br />
Fire System to<br />
be lifted by<br />
800mm to<br />
wrap under<br />
Level 16 slab<br />
soffit.<br />
Cable trays<br />
can’t be<br />
shifted or<br />
Fire Engineer to<br />
coordinate with<br />
Mechanical<br />
Engineer.<br />
Electrical<br />
Engineer to<br />
consult with<br />
Mechanical<br />
Engineer.<br />
Moderate clash<br />
severity due to ease<br />
of adjusting the<br />
different system<br />
heights to resolve the<br />
hard clashes.<br />
Electrical Building<br />
System<br />
Mechanical<br />
Building System<br />
Fire Building System<br />
14<br />
identified<br />
clash<br />
instances in<br />
this area of<br />
the level<br />
based on a<br />
manual,<br />
visual<br />
inspection.<br />
5
16212 – Digital Design and Construction<br />
Assessment Task; UTS Central Project<br />
Model Coordination Audit<br />
systems.<br />
Electrical cable<br />
trays also<br />
intersecting<br />
through the<br />
HVAC System<br />
around the same<br />
location as fire<br />
intersection.<br />
lowered, but<br />
instead can be<br />
lifted 600mm.<br />
1.1.3 LEVEL 15,<br />
LVL.15<br />
Hard<br />
Root cause =<br />
height of the<br />
Wet Fire system<br />
and Electrical<br />
system.<br />
Structural<br />
concrete beams<br />
intersecting with<br />
mechanical<br />
HVAC system<br />
and electrical<br />
cable tray<br />
network.<br />
NB: a pressurized<br />
fire pipe is also<br />
clashing with the<br />
HVAC System.<br />
Root cause: lack<br />
of space in<br />
ceiling cavity to<br />
adjust<br />
intersecting units.<br />
Coordination<br />
meeting<br />
between<br />
Mechanical,<br />
Fire, Electrical<br />
and Structural<br />
Engineers, and<br />
also the<br />
architect to<br />
confirm<br />
whether the<br />
ceiling can be<br />
lowered and if<br />
smaller<br />
mechanical<br />
duct work will<br />
still achieve<br />
compliancy.<br />
Mechanical,<br />
Structural,<br />
Electrical and Fire<br />
Engineers would<br />
need to<br />
coordinate<br />
together to<br />
resolve these<br />
issues.<br />
NB: Potential<br />
knock-on effects<br />
would include<br />
Architect<br />
lowering the<br />
ceiling level, and<br />
or the<br />
Mechanical<br />
Engineer<br />
determining<br />
whether smaller<br />
sized duct work<br />
would be<br />
compliant.<br />
Clash severity is high<br />
as the resolution of<br />
these clashes are<br />
difficult and would<br />
require the ceiling to<br />
be dropped by<br />
potentially 200mm.<br />
Structural Building<br />
System<br />
Electrical Building<br />
System<br />
Mechanical<br />
Building System<br />
Fire Building System<br />
4 – Clashes<br />
identified<br />
by visual<br />
inspection<br />
of the area.<br />
6
16212 – Digital Design and Construction<br />
Assessment Task; UTS Central Project<br />
Model Coordination Audit<br />
Automated Critical Elements Check by #12609842 for Level 15<br />
Item<br />
No.<br />
Location Model Image Clash<br />
Type<br />
Description<br />
of Clash<br />
and/or Root<br />
Cause<br />
Suggested<br />
Action /<br />
Comments<br />
Disciplines<br />
responsible/<br />
Assigned to<br />
Severity of Clash<br />
Clashed<br />
System A<br />
Clashed<br />
System B<br />
Count<br />
2.0 Navisworks Clash Detection<br />
2.1 Level 15<br />
2.1.1<br />
2.1.2<br />
LEVEL 14-<br />
15,<br />
CORE<br />
LVL.14-<br />
LVL.15<br />
LEVEL 14-<br />
15,<br />
CORE<br />
LVL.14-<br />
LVL.15<br />
2.1.3 LEVEL 15,<br />
CORE,<br />
LVL.15<br />
Hard<br />
NB: is<br />
an<br />
Illegal<br />
Clash<br />
Hard<br />
NB: is<br />
an<br />
Illegal<br />
Clash<br />
Hard<br />
NB: is<br />
an<br />
Illegal<br />
Clash<br />
Hydraulic<br />
pipe<br />
intersecting<br />
with<br />
structural<br />
concrete<br />
slab.<br />
Root cause =<br />
poor location<br />
of hydraulic<br />
pipes.<br />
Hydraulic<br />
pipe<br />
intersecting<br />
with<br />
structural<br />
concrete<br />
slab.<br />
Root cause =<br />
poor location<br />
of<br />
Pressurised<br />
wet fire pipe<br />
clashing<br />
against a<br />
structural,<br />
concrete<br />
wall.<br />
No action; as is<br />
an illegal clash.<br />
No action; as is<br />
an illegal clash.<br />
No action; as is<br />
an illegal clash.<br />
Assigned<br />
disciplines are<br />
Structural and<br />
Hydraulic,<br />
however no<br />
further actions<br />
are required for<br />
this clash type.<br />
Assigned<br />
disciplines are<br />
Structural and<br />
Hydraulic,<br />
however no<br />
further actions<br />
are required for<br />
this clash type.<br />
Assigned<br />
disciplines are<br />
Structural and<br />
Fire, however no<br />
further actions<br />
are required for<br />
this clash type.<br />
This is an example<br />
of an Illegal Clash.<br />
It’s of low level<br />
severity and would<br />
normally be<br />
disregarded by the<br />
consultant team.<br />
This is an example<br />
of an Illegal Clash.<br />
It’s of low level<br />
severity and would<br />
normally be<br />
disregarded by the<br />
consultant team.<br />
This is an example<br />
of an Illegal Clash.<br />
It’s of low level<br />
severity and would<br />
normally be<br />
disregarded by the<br />
consultant team.<br />
Structural<br />
Building<br />
System<br />
Structural<br />
Building<br />
System<br />
Structural<br />
Building<br />
System<br />
Hydraulic<br />
(Drainage)<br />
Building<br />
System<br />
Hydraulic<br />
(Drainage)<br />
Building<br />
System<br />
Fire Building<br />
System<br />
4 – Based on<br />
automated<br />
clash<br />
detection<br />
between<br />
structure and<br />
hydraulic<br />
building<br />
models.<br />
11 – Based<br />
on<br />
automated<br />
clash<br />
detection<br />
between<br />
structure and<br />
hydraulic<br />
building<br />
models.<br />
1 – Based on<br />
automated<br />
clash<br />
detection<br />
between<br />
Structural<br />
and Fire<br />
Building<br />
Models.<br />
7
16212 – Digital Design and Construction<br />
Assessment Task; UTS Central Project<br />
Model Coordination Audit<br />
2.1.4 LEVEL 15,<br />
CORE,<br />
LVL.15<br />
2.1.5 LEVEL 15,<br />
PLATE,<br />
LVL.15<br />
Hard<br />
Hard<br />
A 100mm<br />
pressurized<br />
fire pipe is<br />
intersecting a<br />
concrete<br />
wall by 7mm.<br />
The fire pipe<br />
is also<br />
intersecting<br />
the nearby<br />
fire tray<br />
along its<br />
entirety for<br />
this section of<br />
the floor.<br />
Root cause =<br />
poor location<br />
of the fire<br />
pipes.<br />
Electrical<br />
cable tray<br />
intersecting<br />
with<br />
structural<br />
beam in<br />
multiple<br />
locations.<br />
Root cause =<br />
poor location<br />
of the<br />
electrical<br />
cables<br />
without<br />
federation of<br />
other models<br />
during design<br />
stage.<br />
This clash would<br />
most likely be<br />
resolved by<br />
dropping the<br />
100mm fire pipe<br />
by 150mm so<br />
that it would no<br />
longer intersect<br />
either the wall or<br />
the existing<br />
cable trays. This<br />
proposed<br />
solution would<br />
take advantage<br />
of the existing<br />
300mm deep<br />
wall cutout (see<br />
corresponding<br />
image).<br />
Electrical<br />
Engineer to<br />
review whether<br />
this upper<br />
network of cable<br />
trays is essential<br />
and if the<br />
cabling can be<br />
redirected to the<br />
lower trays.<br />
Lower trays<br />
would need to<br />
be wider than<br />
currently<br />
specified. Issue<br />
to be raised at<br />
next<br />
coordination<br />
meeting as the<br />
upper trays can’t<br />
be lowered,<br />
raised, or shifted<br />
due to collisions<br />
with the HVAC<br />
system (which is<br />
already clashing<br />
with structure).<br />
Fire and<br />
Structural<br />
Engineers would<br />
be the main<br />
disciplines<br />
responsible to<br />
resolve this clash.<br />
The Electrical<br />
Engineer would<br />
also be involved<br />
in the process<br />
due to a nearby<br />
clash between<br />
the fire pipe and<br />
cable tray<br />
heights which<br />
would also need<br />
consideration.<br />
Electrical,<br />
Structural and<br />
Mechanical<br />
Engineers to<br />
discuss clashes<br />
over phone calls<br />
and emails,<br />
ahead of<br />
coordination<br />
meeting.<br />
Architect to be<br />
in attendance at<br />
this meeting.<br />
Low severity due<br />
to relative ease of<br />
resolution and very<br />
few instances in<br />
the model.<br />
This clash is of high<br />
severity as it<br />
involves a whole<br />
network of trays<br />
(ie: high number of<br />
clashes), and its<br />
resolution is one of<br />
significant difficulty<br />
and limited<br />
options.<br />
Structural<br />
Building<br />
System<br />
Structural<br />
Building<br />
System<br />
Fire Building<br />
System<br />
Electrical<br />
Building<br />
System<br />
5 – Based on<br />
a visual<br />
inspection of<br />
the<br />
automated<br />
clash results<br />
that have<br />
been<br />
overlaid with<br />
the other unclashed<br />
disciplines of<br />
that level.<br />
37 – Based<br />
on<br />
automated<br />
clash<br />
detection<br />
between<br />
Structural<br />
and<br />
Electrical<br />
Building<br />
Models.<br />
8
16212 – Digital Design and Construction<br />
Assessment Task; UTS Central Project<br />
Model Coordination Audit<br />
2.1.6 LEVEL 15,<br />
CORE,<br />
LVL.15<br />
2.1.7 LEVEL 15,<br />
PLATE<br />
NW,<br />
LVL.15<br />
Hard<br />
Hard<br />
Electrical<br />
cable tray<br />
intersecting<br />
with<br />
structural<br />
beam and<br />
fire pipes<br />
about Lv15<br />
core.<br />
Mech HVAC<br />
ducts<br />
intersecting<br />
with<br />
structural<br />
beams in<br />
multiple<br />
locations.<br />
Ceiling may<br />
need to be<br />
lowered by 100<br />
to 150mm<br />
depending on<br />
other sizing<br />
factors.<br />
This section of<br />
cable tray on<br />
level 15 to be<br />
lowered by<br />
572mm to avoid<br />
intersection with<br />
beam, fire pipes<br />
and mechanical<br />
duct.<br />
NB: This solution<br />
would require 3<br />
downturned tray<br />
connections for<br />
the 3 points that<br />
feed into this<br />
area of the level.<br />
Coordination<br />
meeting<br />
between<br />
Mechanical,<br />
Structural, Fire<br />
and Electrical<br />
Engineers to<br />
determine<br />
resolution options<br />
and potential<br />
knock-on effects.<br />
NB: Duct may<br />
need to be<br />
ordered in a<br />
smaller<br />
compliant size (if<br />
possible), or will<br />
have to discuss<br />
with the<br />
architect if<br />
ceiling can be<br />
Electrical<br />
consultant to<br />
make changes<br />
to their model<br />
revision and<br />
confirm no<br />
potential knockon<br />
impacts with<br />
invitees at the<br />
next<br />
coordination<br />
meeting.<br />
Mechanical,<br />
Structural, Fire,<br />
Electrical<br />
Engineers and<br />
Architect to<br />
coordinate<br />
resolution<br />
options.<br />
These clash<br />
instances are of<br />
low severity due to<br />
the ease of<br />
resolving the issue<br />
with minimal flow<br />
on impacts.<br />
The clash severity<br />
of these instances<br />
are high as the<br />
structural<br />
components will<br />
either have to be<br />
further reinforced<br />
for decreased<br />
beam size, or<br />
smaller ducts be<br />
ordered, or ceiling<br />
lowered by<br />
potentially 300mm.<br />
Structural<br />
Building<br />
System<br />
Structural<br />
Building<br />
System<br />
Electrical<br />
Building<br />
System.<br />
Mechanical<br />
Building<br />
System<br />
1 – Based on<br />
visual<br />
inspection of<br />
automated<br />
clash results.<br />
NB: This clash<br />
instance is<br />
quite similar<br />
to the one<br />
discussed<br />
above,<br />
1 – Based on<br />
visual<br />
inspection of<br />
automated<br />
clash results.<br />
9
16212 – Digital Design and Construction<br />
Assessment Task; UTS Central Project<br />
Model Coordination Audit<br />
2.1.8 LEVEL 15,<br />
CORE,<br />
LVL.15<br />
2.1.9 LEVEL 15,<br />
CORE,<br />
LVL.15<br />
Hard<br />
Hard<br />
NB: is<br />
an<br />
Illegal<br />
Clash<br />
Mech HVAC<br />
ducts<br />
intersecting<br />
with<br />
structural<br />
concrete<br />
beam.<br />
Hydraulic<br />
pipe<br />
intersecting<br />
with<br />
architectural<br />
composite<br />
walls.<br />
lowered.<br />
Shift duct to the<br />
right by 100mm.<br />
No action; is an<br />
illegal clash.<br />
Mechanical<br />
Engineer to<br />
make changes<br />
to their model<br />
and confirm<br />
changes with<br />
the consultant<br />
team at next<br />
coordination<br />
meeting that<br />
their changes<br />
won’t produce<br />
knock-on<br />
impacts.<br />
Assigned<br />
disciplines are<br />
Architecture and<br />
Hydraulic,<br />
however no<br />
further actions<br />
are required for<br />
this clash type.<br />
Clash severity of<br />
this is low due to<br />
the singular<br />
instance and ease<br />
of rectification.<br />
This is an example<br />
of an Illegal Clash.<br />
It’s of low level<br />
severity and would<br />
normally be<br />
disregarded by the<br />
consultant team.<br />
Structural<br />
Building<br />
System<br />
Architect<br />
ural<br />
Building<br />
System<br />
Mechanical<br />
Building<br />
System<br />
Hydraulic<br />
(Drainage)<br />
Building<br />
System<br />
1<br />
50 - Based on<br />
the<br />
automated<br />
clash<br />
detection<br />
between the<br />
Architectural<br />
and<br />
Hydraulic<br />
Building<br />
Models.<br />
NB: This was<br />
the only type<br />
of clash<br />
between<br />
Hydraulic<br />
and<br />
Architectural<br />
and all are<br />
illegal<br />
clashes.<br />
10
16212 – Digital Design and Construction<br />
Assessment Task; UTS Central Project<br />
Model Coordination Audit<br />
2.1.11 LEVEL 15,<br />
PLATE &<br />
CORE,<br />
LVL.15<br />
Hard<br />
NB: is<br />
an<br />
Illegal<br />
Clash<br />
Pressurised<br />
wet fire pipe<br />
clashing<br />
against wall.<br />
No action; is an<br />
illegal clash.<br />
Assigned<br />
disciplines are<br />
Architecture and<br />
Fire, however no<br />
further actions<br />
are required for<br />
this clash type.<br />
This is an example<br />
of an Illegal Clash.<br />
It’s of low level<br />
severity and would<br />
normally be<br />
disregarded by the<br />
consultant team.<br />
Architect<br />
ural<br />
Building<br />
System<br />
Fire Building<br />
System<br />
48 - Based on<br />
the<br />
automated<br />
clash<br />
detection<br />
between<br />
Architecture<br />
and Fire<br />
Building<br />
Models.<br />
2.1.12 LEVEL 15,<br />
CORE,<br />
LVL.15<br />
Hard<br />
NB: is<br />
an<br />
Illegal<br />
Clash<br />
Dry fire cable<br />
tray clashing<br />
against a<br />
concrete<br />
wall.<br />
No action; is an<br />
illegal clash.<br />
Assigned<br />
disciplines are<br />
Architecture and<br />
Fire, however no<br />
further actions<br />
are required for<br />
this clash type.<br />
This is an example<br />
of an Illegal Clash.<br />
It’s of low level<br />
severity and would<br />
normally be<br />
disregarded by the<br />
consultant team.<br />
Architect<br />
ural<br />
Building<br />
System<br />
Fire Building<br />
System<br />
2 – Instances<br />
based on the<br />
automated<br />
clash<br />
detection<br />
between<br />
Architecture<br />
and Fire<br />
Building<br />
Models.<br />
2.1.13 LEVEL 15,<br />
CORE,<br />
LVL.15<br />
2.1.14 LEVEL 15,<br />
CORE,<br />
LVL.15<br />
?<br />
Hard<br />
Hard<br />
NB: is<br />
an<br />
Illegal<br />
Clash<br />
Electrical<br />
cable tray<br />
intersecting<br />
against<br />
concrete<br />
wall.<br />
Electrical<br />
cable tray<br />
clashing<br />
against a<br />
concrete<br />
wall.<br />
Shift cable tray<br />
to the left by<br />
50mm to ovoid<br />
intersection with<br />
the wall. Also<br />
lower the cable<br />
tray by 25mm so<br />
cable tray so it<br />
wraps under the<br />
nearby network<br />
of rigid HVAC<br />
duct.<br />
No action; is an<br />
illegal clash.<br />
Electrical<br />
consultant to<br />
make changes<br />
and confirm with<br />
the Architect<br />
and mechanical<br />
engineer that no<br />
new changes in<br />
their<br />
corresponding<br />
models will<br />
impact the<br />
proposed<br />
resolution option.<br />
Assigned<br />
disciplines are<br />
Architecture and<br />
Electrical,<br />
however no<br />
further actions<br />
are required for<br />
this clash type.<br />
This clash is of low<br />
severity due to the<br />
ease of its<br />
resolution.<br />
This is an example<br />
of an Illegal Clash.<br />
It’s of low level<br />
severity and would<br />
normally be<br />
disregarded by the<br />
consultant team.<br />
Arch.<br />
Building<br />
System<br />
Arch.<br />
Building<br />
System<br />
Electrical<br />
Building<br />
System<br />
Electrical<br />
Building<br />
System.<br />
6 – Instances<br />
based on the<br />
automated<br />
clash<br />
detection<br />
between<br />
Architecture<br />
and<br />
Electrical<br />
Building<br />
Models.<br />
2 – Instances<br />
based on the<br />
automated<br />
clash<br />
detection<br />
between<br />
Architecture<br />
and<br />
Electrical<br />
Building<br />
11
16212 – Digital Design and Construction<br />
Assessment Task; UTS Central Project<br />
Model Coordination Audit<br />
2.1.15 LEVEL 15,<br />
CORE,<br />
LVL.15<br />
2.1.16 LEVEL 15,<br />
CORE,<br />
LVL.15<br />
Hard<br />
NB: is<br />
an<br />
Illegal<br />
Clash<br />
Hard<br />
NB: is<br />
an<br />
Illegal<br />
Clash<br />
Mechanical<br />
rigid duct<br />
clashing<br />
against a<br />
concrete<br />
wall.<br />
Mechanical<br />
rigid duct<br />
clashing<br />
against Level<br />
15 ceiling in<br />
multiple<br />
locations.<br />
No action; is an<br />
illegal clash.<br />
No action; is an<br />
illegal clash.<br />
Assigned<br />
disciplines are<br />
Architecture and<br />
Mechanical,<br />
however no<br />
further actions<br />
are required for<br />
this clash type.<br />
Assigned<br />
disciplines are<br />
Architecture and<br />
Mechanical,<br />
however no<br />
further actions<br />
are required for<br />
this clash type.<br />
This is an example<br />
of an Illegal Clash.<br />
It’s of low level<br />
severity and would<br />
normally be<br />
disregarded by the<br />
consultant team.<br />
This is an example<br />
of an Illegal Clash.<br />
It’s of low level<br />
severity and would<br />
normally be<br />
disregarded by the<br />
consultant team.<br />
Arch.<br />
Building<br />
System<br />
Arch.<br />
Building<br />
System<br />
Mechanical<br />
Building<br />
System<br />
Mechanical<br />
Building<br />
System<br />
Models.<br />
3 – Instances<br />
based on the<br />
automated<br />
clash<br />
detection<br />
between<br />
Architecture<br />
and<br />
Mechanical<br />
Building<br />
Models.<br />
8 – Instances<br />
detected<br />
clashes of this<br />
instance<br />
upon<br />
interrogation<br />
of<br />
automated<br />
clash<br />
detection.<br />
12
16212 – Digital Design and Construction<br />
Assessment Task; UTS Central Project<br />
Model Coordination Audit<br />
2.1.17<br />
2.1.18<br />
As shown in the image on the right, the Hydraulic (water<br />
and gas) Building System does not branch out on level<br />
15 (Level 15 is under the blue transparent slab, pipes<br />
above the slab are on level 16).<br />
Instead, the Hydraulic (Water and Gas) Building System<br />
travels down isolated risers and in doing so it doesn’t<br />
clash with any of the other Building Systems on Level 15<br />
(the assigned floor for this project). Hence, 0 clashes<br />
were detected between the Hydraulic (Water & Gas)<br />
Building System and the Architectural Building System.<br />
Arch.<br />
Building<br />
System<br />
Hydraulic<br />
(Water&<br />
Gas) Building<br />
System<br />
0 – Instances<br />
were<br />
identified by<br />
the<br />
automated<br />
clash<br />
detection of<br />
the two<br />
systems.<br />
2.1.19<br />
2.1.20<br />
As shown in the image on the right, the Hydraulic (water<br />
and gas) Building System does not branch out on level<br />
15 (Level 15 is under the blue transparent slab, pipes<br />
above the slab are on level 16).<br />
Instead, the Hydraulic (Water and Gas) Building System<br />
travels down isolated risers and in doing so it doesn’t<br />
clash with any of the other Building Systems on Level 15<br />
(the assigned floor for this project). Hence, 0 clashes<br />
were detected between the Hydraulic (Water & Gas)<br />
Building System and the Structural Building System<br />
Structural<br />
Building<br />
System<br />
Hydraulic<br />
(Water &<br />
Gas) Building<br />
System<br />
0 – Instances<br />
were<br />
identified by<br />
the<br />
automated<br />
clash<br />
detection of<br />
the two<br />
systems.<br />
13
16212 – Digital Design and Construction<br />
Assessment Task; UTS Central Project<br />
Model Coordination Audit<br />
Automated Services Check by #12609842 for Level 15<br />
Item<br />
No.<br />
Location Model Image Clash<br />
Type<br />
Description of<br />
Clash and/or<br />
Root Cause<br />
Suggested<br />
Action /<br />
Comments<br />
Disciplines<br />
responsible/<br />
Assigned to<br />
Severity of<br />
Clash<br />
Clashed<br />
System A<br />
Clashed<br />
System B<br />
Count<br />
3.0 Navisworks Clash Detection<br />
3.1 Level 15<br />
3.1.1 LEVEL 15,<br />
CORE,<br />
LVL.15<br />
3.1.2 LEVEL 15,<br />
CORE,<br />
LVL.15<br />
Hard<br />
Hard<br />
Hydraulic<br />
drainage pipes<br />
intersecting a<br />
section of<br />
Mechanical<br />
Duct.<br />
NB: Fire<br />
services are<br />
also<br />
intersecting<br />
same section<br />
of HVAC.<br />
Root cause =<br />
poor location<br />
of the<br />
hydraulic pipes<br />
outside of a<br />
federated<br />
models during<br />
design stage.<br />
Hydraulic pipe<br />
work<br />
intersecting<br />
through a<br />
section of<br />
mechanical<br />
HVAC.<br />
Root cause =<br />
poor location<br />
of the<br />
hydraulic pipes<br />
in an unfederated<br />
An urgent design<br />
coordination<br />
meeting<br />
between the<br />
Mechanical and<br />
Hydraulic<br />
Engineers to be<br />
organized, with<br />
the Fire Engineer<br />
and Architect to<br />
also be invited<br />
due to knock on<br />
effects on their<br />
disciplines.<br />
Shift hydraulic<br />
pipes in this area<br />
to the right by<br />
400mm so that<br />
the 100mm pipe<br />
will be relocated<br />
in the 300mm<br />
space between<br />
the two local<br />
HVAC networks.<br />
Disciplines<br />
responsible<br />
to resolve<br />
these clash<br />
instances are<br />
primarily the<br />
Mechanical<br />
and<br />
Hydraulic<br />
Engineer;<br />
however the<br />
Fire<br />
consultant<br />
and<br />
architect will<br />
also be<br />
involved in its<br />
resolution.<br />
Hydraulic<br />
and<br />
mechanical<br />
are the two<br />
disciplines<br />
that would<br />
be<br />
responsible<br />
with resolving<br />
this clash<br />
type.<br />
As this is a<br />
relative<br />
complex<br />
clash with<br />
multiple<br />
disciplines<br />
involved, it<br />
is<br />
categorize<br />
d as of high<br />
severity.<br />
This clash is<br />
of low<br />
severity as<br />
there are<br />
only two<br />
instances<br />
identified,<br />
and the<br />
resolution<br />
strategy is<br />
relatively<br />
simple. This<br />
is in<br />
compariso<br />
Mechanical<br />
Building<br />
System<br />
Mechanical<br />
Building<br />
System<br />
Hydraulic<br />
(Drainage)<br />
Building<br />
System<br />
Hydraulic<br />
(Drainage)<br />
Building<br />
System<br />
3 – Instances<br />
of this type of<br />
clash based<br />
on a manual<br />
inspection of<br />
the<br />
automated<br />
clash results<br />
between<br />
Mechanical<br />
and<br />
Hydraulic<br />
Building<br />
Models.<br />
2 – Instances<br />
of this type of<br />
clash based<br />
on a manual<br />
inspection of<br />
the<br />
automated<br />
clash results<br />
between<br />
Mechanical<br />
and<br />
Hydraulic<br />
Building<br />
Models.<br />
14
16212 – Digital Design and Construction<br />
Assessment Task; UTS Central Project<br />
Model Coordination Audit<br />
3.1.3<br />
3.1.4<br />
model.<br />
n to the<br />
other type<br />
of clashes<br />
between<br />
Mech and<br />
Hydraulic<br />
which has<br />
been<br />
identified<br />
above.<br />
As shown in the image on the right, the Hydraulic<br />
(water and gas) Building System does not<br />
branch out on level 15 (Level 15 is under the<br />
blue transparent slab, pipes above the slab are<br />
on level 16).<br />
Instead, the Hydraulic (Water and Gas) Building<br />
System travels down isolated risers and in doing<br />
so it doesn’t clash with any of the other Building<br />
Systems on Level 15 (the assigned floor for this<br />
project). Hence, 0 clashes were detected<br />
between the Hydraulic (Water & Gas) Building<br />
System and the Mechanical Building System,<br />
Mechanical<br />
Building<br />
System<br />
Hydraulic<br />
(Water &<br />
Gas)<br />
Building<br />
System<br />
0 – Instances<br />
were<br />
identified by<br />
the<br />
automated<br />
clash<br />
detection<br />
test<br />
3.1.5 LEVEL 15,<br />
PLATE,<br />
LVL.15<br />
Hard<br />
Cable tray is<br />
intersecting<br />
rigid<br />
mechanical<br />
duct by 25mm.<br />
Root cause =<br />
poor location<br />
of the<br />
electrical<br />
cable trays.<br />
Drop cable tray<br />
by 40mm so that<br />
the cable tray<br />
will be 35mm<br />
above the<br />
ceiling and<br />
15mm below the<br />
mechanical<br />
duct.<br />
NB: This would<br />
only resolve the<br />
immediate clash<br />
between the<br />
ducts and cable<br />
trays, but a<br />
The Electrical<br />
consultant<br />
would be<br />
responsible<br />
to resolve the<br />
issue by<br />
amending<br />
their model,<br />
after<br />
consulting<br />
the<br />
mechanical<br />
engineer first.<br />
These<br />
clashes are<br />
of<br />
moderate<br />
instances<br />
due the<br />
numerable<br />
instances<br />
produced<br />
by the root<br />
cause.<br />
However,<br />
the<br />
immediate<br />
issue is low<br />
difficulty to<br />
Mechanical<br />
Building<br />
System<br />
Electrical<br />
Building<br />
System<br />
10 - Instances<br />
were<br />
identified by<br />
the<br />
automated<br />
clash<br />
detection<br />
test and the<br />
visual<br />
inspection of<br />
the results.<br />
15
16212 – Digital Design and Construction<br />
Assessment Task; UTS Central Project<br />
Model Coordination Audit<br />
3.1.6 LEVEL 15,<br />
PLATE,<br />
LVL.15<br />
Hard<br />
The upper<br />
network of<br />
cable trays is<br />
intersecting the<br />
HVAC system<br />
duct, and both<br />
services are<br />
intersecting a<br />
structural<br />
concrete<br />
beam.<br />
Root cause =<br />
poor location<br />
of the<br />
electrical<br />
cable trays.<br />
coordination<br />
meeting would<br />
still need to be<br />
arranged for<br />
other nearby<br />
clashes like the<br />
fire pipe through<br />
the duct<br />
(shown).<br />
A design<br />
coordination<br />
meeting will<br />
need to be<br />
arranged as the<br />
combined<br />
intersection<br />
height (HVAC +<br />
trays) is 175mm<br />
into the beam.<br />
The distance<br />
between the<br />
HVAC and the<br />
lower network of<br />
trays is currently<br />
108mm. Upon<br />
lowering the<br />
bottom trays by<br />
40mm as<br />
suggested in the<br />
previous clash,<br />
the new space<br />
dimensions will<br />
be 148mm,<br />
however this is<br />
still insufficient to<br />
resolve the<br />
clashes with the<br />
beam.<br />
The<br />
Structural,<br />
Mechanical<br />
and<br />
Electrical<br />
Engineers will<br />
be<br />
responsible<br />
to<br />
coordinate<br />
with the<br />
architect<br />
and Fire<br />
consultant in<br />
the resolution<br />
of this issue<br />
due to the<br />
magnitude<br />
of knock on<br />
effects.<br />
fix. As<br />
discussed in<br />
previous<br />
columns,<br />
nearby<br />
clashes<br />
may have<br />
knock on<br />
effects and<br />
the cable<br />
trays be<br />
further<br />
lowered if<br />
the ceiling<br />
is lowered.<br />
This clash is<br />
of high<br />
severity<br />
due to<br />
complexity<br />
of the clash<br />
and the<br />
likelihood<br />
of either<br />
compromisi<br />
ng the<br />
upper<br />
network of<br />
cable trays<br />
and or<br />
dropping<br />
the ceiling<br />
height.<br />
Mechanical<br />
Building<br />
System<br />
Electrical<br />
Building<br />
System<br />
4 - Instances<br />
were<br />
identified by<br />
the<br />
automated<br />
clash<br />
detection<br />
test and the<br />
visual<br />
inspection of<br />
the results.<br />
16
16212 – Digital Design and Construction<br />
Assessment Task; UTS Central Project<br />
Model Coordination Audit<br />
3.1.7 LEVEL 15,<br />
PLATE,<br />
LVL.15<br />
3.1.8 LEVEL 15,<br />
CORE,<br />
LVL.15<br />
Hard<br />
Hard<br />
Fire pipe<br />
intersecting<br />
rigid<br />
mechanical<br />
duct.<br />
NB: only a<br />
25mm<br />
clearance<br />
above the<br />
duct, 75mm<br />
below the<br />
duct, and the<br />
fire pipe has a<br />
diameter<br />
of166mm.<br />
Root cause =<br />
poor<br />
coordination of<br />
services<br />
design.<br />
Clearance<br />
Zone<br />
intersecting a<br />
section of<br />
mechanical<br />
duct by<br />
250mm.<br />
Root cause =<br />
poor<br />
coordination of<br />
fire system with<br />
other services.<br />
A design<br />
coordination<br />
meeting to be<br />
arranged<br />
between the<br />
Mechanical, Fire<br />
Consultants,<br />
Electrical and<br />
Architectural<br />
Consultants.<br />
Mech Consultant<br />
to determine if a<br />
smaller size can<br />
be used and<br />
achieve<br />
compliancy. As<br />
the fire pipes<br />
can’t be shifted,<br />
lifted or lowered,<br />
the ceiling may<br />
likely be lowered<br />
or alternative<br />
solutions<br />
explored.<br />
The clearance<br />
zone (green)<br />
and the related<br />
structures<br />
(connecting fire<br />
pipes and<br />
intersection<br />
point) to be<br />
shifted to the<br />
right by 500mm<br />
so that it is<br />
relocated into<br />
the 617mm of<br />
clear space<br />
between the<br />
Disciplines<br />
that will be<br />
involved in<br />
the resolution<br />
of this clash<br />
type<br />
includes: Fire<br />
Engineer,<br />
Mechanical<br />
Engineer,<br />
Architect<br />
and the<br />
Electrical<br />
Engineer.<br />
The Fire and<br />
Mechanical<br />
Engineers are<br />
the only two<br />
consultants<br />
impacted by<br />
this clash.<br />
The Fire<br />
Engineer will<br />
be<br />
responsible<br />
for resolving<br />
the issue by<br />
making<br />
changes to<br />
This clash is<br />
of high<br />
severity as<br />
the<br />
alternative<br />
solutions<br />
may need<br />
to be<br />
utilised or<br />
else the<br />
ceiling<br />
height will<br />
need to be<br />
lowered to<br />
accommo<br />
date these<br />
units.<br />
There are<br />
also<br />
multiple<br />
instances<br />
which are<br />
affected<br />
by these<br />
circumstan<br />
ces.<br />
This clash is<br />
low severity<br />
due to the<br />
ease of<br />
resolving<br />
the issue<br />
and the<br />
low number<br />
of<br />
instances<br />
(5).<br />
Mechanical<br />
Building<br />
System<br />
Mechanical<br />
Building<br />
System<br />
Fire<br />
Building<br />
System<br />
Fire<br />
Building<br />
System<br />
14 - Instances<br />
were<br />
identified by<br />
the<br />
automated<br />
clash<br />
detection<br />
test and the<br />
visual<br />
inspection of<br />
the results.<br />
5 – Instances<br />
can be<br />
resolved<br />
using the<br />
proposed<br />
solution. The<br />
5 instances<br />
are shown in<br />
the second<br />
image and<br />
were<br />
identified<br />
upon visual<br />
inspection of<br />
the<br />
17
16212 – Digital Design and Construction<br />
Assessment Task; UTS Central Project<br />
Model Coordination Audit<br />
HVAC units. their model. automated<br />
test results.<br />
3.1.9 N/A N/A<br />
3.1.10 N/A N/A<br />
3.1.11 LEVEL 15,<br />
CORE,<br />
LVL.15<br />
NB: No Clashes detected.<br />
NB: No Clashes detected.<br />
N/A N/A N/A N/A N/A Hydraulic<br />
(Drainage)<br />
Building<br />
System<br />
N/A N/A N/A N/A N/A Hydraulic<br />
(Drainage)<br />
Building<br />
System<br />
Hard<br />
A section of<br />
pressurized fire<br />
pipe is<br />
intersecting<br />
with the<br />
nearby<br />
hydraulic<br />
drainage pipe.<br />
This clash can be<br />
resolved by<br />
lowering the fire<br />
pipe by 200mm<br />
to avoid<br />
intersection with<br />
the drainage<br />
pipe.<br />
The Hydraulic<br />
and Fire<br />
consultant<br />
are the two<br />
disciplines<br />
responsible<br />
for resolving<br />
this clash.<br />
Clash<br />
severity of<br />
this<br />
instance is<br />
low due to<br />
the limited<br />
instances<br />
and<br />
relative<br />
ease of<br />
resolution.<br />
Hydraulic<br />
(Drainage)<br />
Building<br />
System<br />
Electrical<br />
Building<br />
System<br />
Electrical<br />
Building<br />
System<br />
Fire<br />
Building<br />
System<br />
0 – Instances<br />
were<br />
identified by<br />
the<br />
automated<br />
clash<br />
detection of<br />
the two<br />
systems.<br />
0 – Instances<br />
were<br />
identified by<br />
the<br />
automated<br />
clash<br />
detection of<br />
the two<br />
systems.<br />
1 – This<br />
Instance was<br />
identified<br />
visual<br />
inspection of<br />
the<br />
automated<br />
clash<br />
detection<br />
result.<br />
18
16212 – Digital Design and Construction<br />
Assessment Task; UTS Central Project<br />
Model Coordination Audit<br />
3.1.12 LEVEL 15,<br />
CORE,<br />
LVL.15<br />
3.1.13<br />
3.1.14<br />
Hard<br />
A section of<br />
pressurized fire<br />
pipe is<br />
intersecting<br />
with the<br />
nearby<br />
hydraulic<br />
drainage pipe.<br />
This clash can be<br />
resolved by<br />
lowering the fire<br />
pipe by 100mm<br />
to avoid<br />
intersection with<br />
the drainage<br />
pipe.<br />
The Hydraulic<br />
and Fire<br />
consultant<br />
are the two<br />
disciplines<br />
responsible<br />
for resolving<br />
this clash.<br />
Clash<br />
severity of<br />
this<br />
instance is<br />
low due to<br />
the limited<br />
instances<br />
and<br />
relative<br />
ease of<br />
resolution.<br />
As shown in the image on the right, the<br />
Hydraulic (water and gas) Building System does<br />
not branch out on level 15 (Level 15 is under the<br />
blue transparent slab, pipes above the slab are<br />
on Level 16).<br />
Instead, the Hydraulic (Water and Gas) Building<br />
System travels down isolated risers and in doing<br />
so it doesn’t clash with any of the other Building<br />
Systems on Level 15 (the assigned floor for this<br />
project). Hence, 0 clashes were detected<br />
between the Hydraulic (Water & Gas) Building<br />
System and the Electrical Building System.<br />
Hydraulic<br />
(Drainage)<br />
Building<br />
System<br />
Hydraulic<br />
(Water & Gas)<br />
Building<br />
System<br />
Fire<br />
Building<br />
System<br />
Electrical<br />
Building<br />
System<br />
1 – This<br />
Instance was<br />
identified<br />
visual<br />
inspection of<br />
the<br />
automated<br />
clash<br />
detection<br />
result.<br />
0 – Instances<br />
were<br />
identified by<br />
the<br />
automated<br />
clash<br />
detection of<br />
the two<br />
systems.<br />
19
16212 – Digital Design and Construction<br />
Assessment Task; UTS Central Project<br />
Model Coordination Audit<br />
3.1.15<br />
3.1.16<br />
As shown in the image on the right, the<br />
Hydraulic (water and gas) Building System does<br />
not branch out on level 15 (Level 15 is under the<br />
blue transparent slab, pipes above the slab are<br />
on Level 16).<br />
Instead, the Hydraulic (Water and Gas) Building<br />
System travels down isolated risers and in doing<br />
so it doesn’t clash with any of the other Building<br />
Systems on Level 15 (the assigned floor for this<br />
project). Hence, 0 clashes were detected<br />
between the Hydraulic (Water & Gas) Building<br />
System and the Fire Building System.<br />
Hydraulic<br />
(Water & Gas)<br />
Building<br />
System<br />
Fire<br />
Building<br />
System<br />
0 – Instances<br />
were<br />
identified by<br />
the<br />
automated<br />
clash<br />
detection of<br />
the two<br />
systems.<br />
3.1.17 LEVEL 15,<br />
HALL,<br />
LVL.15<br />
Hard<br />
Fire pipe is<br />
intersecting an<br />
electrical<br />
cable tray<br />
along its<br />
entirety.<br />
Root cause =<br />
poor<br />
coordination of<br />
services<br />
design.<br />
This clash type<br />
can be resolved<br />
by dropping this<br />
section of the fire<br />
pipe network by<br />
300mm (NB: gap<br />
below is 675mm)<br />
and shortening<br />
the length of the<br />
fire pipe so that it<br />
wraps in front of<br />
the HVAC system<br />
down the clash.<br />
The<br />
disciplines<br />
responsible<br />
for the<br />
resolution of<br />
this clash<br />
include the<br />
Fire,<br />
Electrical,<br />
and<br />
Mechanical<br />
Consultants.<br />
The severity<br />
of this clash<br />
is high as it<br />
affects<br />
significant<br />
lengths of<br />
the<br />
Electrical<br />
Building<br />
System,<br />
and would<br />
involve<br />
multiple<br />
consultants<br />
to resolve<br />
the clash<br />
and any<br />
knock on<br />
effects.<br />
Electrical<br />
Building<br />
System<br />
Fire<br />
Building<br />
System<br />
3 - Instances<br />
that could<br />
be resolved<br />
by the<br />
proposed<br />
solution were<br />
identified<br />
upon visual<br />
inspection of<br />
the<br />
automated<br />
clash<br />
detection<br />
results.<br />
20
16212 – Digital Design and Construction<br />
Assessment Task; UTS Central Project<br />
Model Coordination Audit<br />
3.1.18 LEVEL 15,<br />
CORE,<br />
LVL.15<br />
Hard<br />
Fire pipe and<br />
sprinkler<br />
attachment<br />
are<br />
intersecting<br />
two networks<br />
of electrical<br />
cable trays<br />
Both services<br />
are<br />
intersecting a<br />
structural<br />
concrete<br />
beam. Fire<br />
pipe is also<br />
intersecting the<br />
HVAC system<br />
A design<br />
coordination<br />
meeting<br />
between the<br />
Fire, Electrical,<br />
Structural and<br />
Mechanical<br />
Engineers to be<br />
arranged with<br />
great urgency.<br />
NB: The project<br />
Architect may<br />
also become<br />
involved in case<br />
the ceiling gets<br />
dropped to<br />
accommodate<br />
services in this<br />
local area.<br />
The<br />
disciplines<br />
responsible<br />
for the<br />
coordinated<br />
resolution of<br />
this clash<br />
include: the<br />
Structural<br />
Engineer, the<br />
Mechanical<br />
Engineer, the<br />
Electrical<br />
Engineer, the<br />
Fire Engineer<br />
and possibly<br />
the project<br />
Architect.<br />
The severity<br />
of this clash<br />
instance is<br />
of high<br />
classificatio<br />
n due to<br />
the great<br />
complexity<br />
of the clash<br />
and<br />
numerable<br />
consultants<br />
who will<br />
need to<br />
resolve it.<br />
Electrical<br />
Building<br />
System<br />
Fire<br />
Building<br />
System<br />
1 - Instance<br />
of this type of<br />
clash (ie:<br />
double<br />
clash) and its<br />
magnitude<br />
upon manual<br />
inspection of<br />
the<br />
automated<br />
clash<br />
detection<br />
results.<br />
21
16212 – Digital Design and Construction<br />
Assessment Task; UTS Central Project<br />
Model Coordination Audit<br />
Roof Level<br />
Visual Hot Spots Check by #12609842 for Level Roof<br />
Item<br />
No.<br />
Location<br />
Model Image<br />
Clash<br />
Type<br />
Description of<br />
Clash and/or Root<br />
Cause<br />
Suggested<br />
Action /<br />
Comments<br />
Disciplines<br />
responsible/<br />
Assigned to<br />
Severity of Clash<br />
Clashed Systems<br />
Count of<br />
clashes in<br />
local area<br />
4.0 Navisworks Clash Detection<br />
4.1 Roof Level<br />
LVL.<br />
ROOF<br />
4.1.1<br />
4.1.2<br />
LVL.<br />
ROOF<br />
Hard<br />
Hard<br />
Fire pipe system<br />
intersecting a<br />
section of<br />
mechanical duct<br />
and then<br />
intersecting<br />
several structural<br />
members in the<br />
nearby area.<br />
Structural member<br />
is intersecting the<br />
same section of<br />
duct as the fire<br />
pipe, and so is the<br />
nearby network of<br />
electrical cable<br />
trays.<br />
Electrical cable<br />
trays are<br />
intersecting<br />
themselves and<br />
the nearby<br />
mechanical units,<br />
a partially<br />
intersecting a<br />
structural steel<br />
member.<br />
Fire system to<br />
be lifted by<br />
500mm. Pink<br />
Mechanical<br />
duct to be<br />
shortened to<br />
end right of the<br />
structural<br />
member.<br />
Electrical<br />
cable tray to<br />
be shifted<br />
towards the<br />
centre of the<br />
level<br />
(backwards)<br />
by 250mm.<br />
A design<br />
coordination<br />
meeting<br />
between all<br />
the services<br />
consultants<br />
and the<br />
structural<br />
consultant.<br />
NB: other<br />
consultants are<br />
to be invited to<br />
confirm no<br />
knock-on<br />
effects by the<br />
proposed<br />
solution.<br />
Structural<br />
Engineer;<br />
Mechanical<br />
Engineer;<br />
Fire Engineer;<br />
Electrical<br />
Engineer.<br />
Structural<br />
Engineer;<br />
Mechanical<br />
Engineer;<br />
Electrical<br />
Engineer.<br />
This clash is of high<br />
severity due to<br />
complexity of the<br />
hotspot and the<br />
many influential<br />
disciplines<br />
involved.<br />
There is also a high<br />
risk of knock on<br />
effects if not the<br />
solution isn’t<br />
coordinated<br />
among the<br />
involved<br />
disciplines.<br />
This clash is of high<br />
severity due to<br />
complexity of the<br />
hotspot and the<br />
many influential<br />
disciplines<br />
involved.<br />
There is also a high<br />
risk of knock on<br />
effects if not the<br />
solution isn’t<br />
coordinated<br />
among the<br />
involved<br />
disciplines.<br />
Structural Building<br />
System<br />
Mechanical<br />
Building System<br />
Fire Building System<br />
Electrical Building<br />
System<br />
Structural Building<br />
System;<br />
Mechanical<br />
Building System;<br />
Electrical Building<br />
System.<br />
6<br />
7<br />
22
16212 – Digital Design and Construction<br />
Assessment Task; UTS Central Project<br />
Model Coordination Audit<br />
4.1.3<br />
LVL.<br />
ROOF<br />
Hard<br />
Fire system is<br />
intersecting<br />
nearby<br />
mechanical ducts<br />
in multiple<br />
locations. Fire<br />
system is also<br />
intersecting the<br />
steel structural<br />
member. Electrical<br />
cable tray system<br />
also intersecting<br />
the large<br />
mechanical ducts<br />
in multiple<br />
locations.<br />
Lift the fire<br />
system up by<br />
500mm then<br />
shift it to the<br />
right and<br />
shorten it by<br />
500mm.<br />
Cable tray<br />
system to also<br />
be shifted to<br />
the right by<br />
500mm.<br />
Structural<br />
Engineer;<br />
Mechanical<br />
Engineer;<br />
Fire Engineer;<br />
Electrical<br />
Engineer.<br />
This clash is of high<br />
severity due to<br />
complexity of the<br />
hotspot and the<br />
many influential<br />
disciplines<br />
involved.<br />
There is also a high<br />
risk of knock on<br />
effects if not the<br />
solution isn’t<br />
coordinated<br />
among the<br />
involved<br />
disciplines.<br />
Structural Building<br />
System<br />
Mechanical<br />
Building System<br />
Fire Building System<br />
Electrical Building<br />
System<br />
6<br />
23
16212 – Digital Design and Construction<br />
Assessment Task; UTS Central Project<br />
Model Coordination Audit<br />
Automated Critical Elements Check by #12609842 for Level Roof<br />
Item<br />
No.<br />
Location Model Image Clash<br />
Type<br />
Description of<br />
Clash and/or<br />
Root Cause<br />
Suggested<br />
Action /<br />
Comments<br />
Disciplines<br />
responsible/<br />
Assigned to<br />
Severity of<br />
Clash<br />
Clashed<br />
System A<br />
Clashed<br />
System B<br />
Count<br />
5.0 Navisworks Clash Detection<br />
5.1 Roof Level<br />
5.1.1 LVL.<br />
ROOF,<br />
Hard<br />
Hydraulic pipe<br />
intersecting a<br />
section of<br />
structural<br />
roofing (made<br />
of concrete).<br />
No action as this<br />
is an illegal clash.<br />
The<br />
disciplines<br />
responsible<br />
for this clash<br />
are Hydraulic<br />
and<br />
Structural;<br />
however as it<br />
is an illegal<br />
clash- no<br />
further action<br />
will be<br />
required.<br />
N/A – is an<br />
illegal clash.<br />
Structural<br />
Building<br />
System<br />
Hydraulic<br />
(Drainage)<br />
Building<br />
System<br />
6 – Instances<br />
identified by<br />
manual inspection<br />
of the automated<br />
clash detection<br />
results.<br />
5.1.2 LVL.<br />
ROOF<br />
Hard<br />
Hydraulic pipe<br />
intersecting a<br />
section of<br />
structural<br />
concrete slab.<br />
No action as this<br />
is an illegal clash.<br />
The<br />
disciplines<br />
responsible<br />
for this clash<br />
are Hydraulic<br />
and<br />
Structural;<br />
however as it<br />
is an illegal<br />
clash- no<br />
further action<br />
will be<br />
required.<br />
N/A – is an<br />
illegal clash.<br />
Structural<br />
Building<br />
System<br />
Hydraulic<br />
(Drainage)<br />
Building<br />
System<br />
4 – Instances<br />
identified by<br />
manual inspection<br />
of the automated<br />
clash detection<br />
results.<br />
24
16212 – Digital Design and Construction<br />
Assessment Task; UTS Central Project<br />
Model Coordination Audit<br />
5.1.3 LVL.<br />
ROOF<br />
5.1.4 LVL.<br />
ROOF<br />
Hard<br />
Hard<br />
Vertical section<br />
of pressurized<br />
fire pipe<br />
intersecting a<br />
section of<br />
structural<br />
concrete slab.<br />
Horizontal<br />
section of<br />
pressurized fire<br />
pipe<br />
intersecting a<br />
section of<br />
structural<br />
concrete slab.<br />
No action as this<br />
is an illegal clash.<br />
No action as this<br />
is an illegal clash.<br />
The<br />
disciplines<br />
responsible<br />
for this clash<br />
are Fire and<br />
Structural;<br />
however as it<br />
is an illegal<br />
clash- no<br />
further action<br />
will be<br />
required.<br />
The<br />
disciplines<br />
responsible<br />
for this clash<br />
are Fire and<br />
Structural;<br />
however as it<br />
is an illegal<br />
clash- no<br />
further action<br />
will be<br />
required.<br />
N/A – is an<br />
illegal clash.<br />
N/A – is an<br />
illegal clash.<br />
Structural<br />
Building<br />
System<br />
Structural<br />
Building<br />
System<br />
Fire Building<br />
System<br />
Fire Building<br />
System<br />
7 - Instances<br />
identified by<br />
manual inspection<br />
of the automated<br />
clash detection<br />
results.<br />
2 - Instances<br />
identified by<br />
manual inspection<br />
of the automated<br />
clash detection<br />
results.<br />
25
16212 – Digital Design and Construction<br />
Assessment Task; UTS Central Project<br />
Model Coordination Audit<br />
5.1.5 LVL.<br />
ROOF<br />
5.1.6 LVL.<br />
ROOF<br />
Hard<br />
Hard<br />
Electrical<br />
cable tray<br />
intersecting a<br />
structural<br />
concrete wall<br />
and beam.<br />
Electrical<br />
cable tray<br />
intersecting a<br />
structural<br />
concrete wall.<br />
NB: This clash is<br />
in conjunction<br />
to the one<br />
discussed<br />
above.<br />
This clash can be<br />
resolved by<br />
shifting the<br />
cable tray to the<br />
right by 200mm<br />
and dropping it<br />
be 150mm so<br />
that it clears the<br />
currently clashed<br />
structural<br />
components<br />
and wrap under<br />
the tunnel.<br />
This clash can be<br />
resolved by<br />
lifting the cable<br />
tray by 35mm<br />
and to shifting it<br />
to the left by<br />
200mm. In doing<br />
this and<br />
connecting the<br />
cable tray will be<br />
in line with the<br />
constructed<br />
holes in the wall.<br />
NB: an upturn<br />
connection<br />
junction<br />
between the<br />
cable trays in<br />
the tunnel<br />
(shown in<br />
previous clash)<br />
will need to be<br />
installed as well.<br />
The<br />
disciplines<br />
responsible<br />
for the<br />
resolution of<br />
this clash are<br />
the Electrical<br />
and Structural<br />
Engineers,<br />
with the<br />
Electrical<br />
Engineer<br />
making the<br />
amendments<br />
as their units<br />
are of lesser<br />
importance<br />
to the<br />
building’s<br />
design.<br />
The<br />
disciplines<br />
responsible<br />
for the<br />
resolution of<br />
this clash are<br />
the Electrical<br />
and Structural<br />
Engineers,<br />
This clash is<br />
of low<br />
severity due<br />
to the low<br />
number of<br />
instances (1)<br />
and the ease<br />
of resolving<br />
the clash.<br />
This clash is<br />
of low<br />
severity due<br />
to the low<br />
number of<br />
instances (1)<br />
and the ease<br />
of resolving<br />
the clash.<br />
Structural<br />
Building<br />
System<br />
Structural<br />
Building<br />
System<br />
Electrical<br />
Building<br />
System<br />
Electrical<br />
Building<br />
System.<br />
1 – Instances<br />
identified by<br />
manual inspection<br />
of the automated<br />
clash detection<br />
results.<br />
1 – Instances<br />
identified by<br />
manual inspection<br />
of the automated<br />
clash detection<br />
results.<br />
26
16212 – Digital Design and Construction<br />
Assessment Task; UTS Central Project<br />
Model Coordination Audit<br />
5.1.7 LVL.<br />
ROOF<br />
Hard<br />
Two sets of<br />
structural steel<br />
framing is<br />
intersecting a<br />
composite<br />
Mechanical<br />
Unit<br />
encasement.<br />
An immediate<br />
coordination<br />
meeting<br />
between the<br />
structural<br />
engineer and<br />
the mechanical<br />
engineer to be<br />
arranged.<br />
The two<br />
disciplines<br />
involved in<br />
the resolution<br />
of this clash<br />
instance are<br />
structural and<br />
mechanical.<br />
This clash is<br />
of high<br />
severity due<br />
to the<br />
complexity<br />
with resolving<br />
the clash<br />
type and 2<br />
instances<br />
involved.<br />
Structural<br />
Building<br />
System<br />
Mechanical<br />
Building<br />
System<br />
2 – Instances<br />
identified by<br />
manual inspection<br />
of the automated<br />
clash detection<br />
results.<br />
5.1.8 LVL.<br />
ROOF<br />
5.1.9 LVL.<br />
ROOF<br />
Hard<br />
Hard<br />
Structural steel<br />
framing<br />
intersecting a<br />
large sized<br />
mechanical<br />
unit in two<br />
separate<br />
locations.<br />
Section of<br />
hydraulic<br />
drainage pipe<br />
intersecting<br />
Level 17<br />
ceiling.<br />
This clash can be<br />
resolved by<br />
shifting the unit<br />
to forward by<br />
400mm and then<br />
shifting it to the<br />
right by 200mm.<br />
Hydraulic<br />
Engineer to shift<br />
the two pipes<br />
on the<br />
immediate left of<br />
the green pipe<br />
by 50mm to left,<br />
and then shift<br />
the green pipe<br />
left by 100mm.<br />
The two<br />
disciplines<br />
involved in<br />
the resolution<br />
of this clash<br />
instance are<br />
structural and<br />
mechanical.<br />
The two<br />
disciplines<br />
involved in<br />
the resolution<br />
of this clash<br />
would be the<br />
Hydraulic<br />
Engineer and<br />
the Architect.<br />
However due<br />
to the<br />
precedence<br />
of discipline<br />
priorities, the<br />
Hydraulic<br />
Engineer<br />
would be<br />
responsible<br />
with making<br />
the changes.<br />
This clash is<br />
of moderate<br />
severity due<br />
to the two<br />
disciplines<br />
involved<br />
being of<br />
higher<br />
weighting.<br />
However<br />
due to the<br />
ease of<br />
resolving the<br />
clash, it is not<br />
considered<br />
of high<br />
severity.<br />
Clash<br />
severity of<br />
this instance<br />
is low due to<br />
the limited<br />
instances<br />
and relative<br />
ease of<br />
resolution.<br />
Structural<br />
Building<br />
System<br />
Architectural<br />
Building<br />
System<br />
Mechanical<br />
Building<br />
System<br />
Hydraulic<br />
(Drainage)<br />
Building<br />
System<br />
1 – Instance<br />
identified by<br />
manual inspection<br />
of the automated<br />
clash detection<br />
results.<br />
2 – Instances<br />
identified by<br />
manual inspection<br />
of the automated<br />
clash detection<br />
results.<br />
27
16212 – Digital Design and Construction<br />
Assessment Task; UTS Central Project<br />
Model Coordination Audit<br />
5.1.10 LVL.<br />
ROOF<br />
5.1.11 LVL.<br />
ROOF<br />
Soft<br />
Hard<br />
Hydraulic pipe<br />
intersecting a<br />
mechanical<br />
riser casing.<br />
Dry Fire cable<br />
tray<br />
intersecting a<br />
basic<br />
blockwork wall<br />
with a ceiling<br />
located<br />
immediately<br />
above.<br />
Hydraulic<br />
Engineer to<br />
communicate<br />
with the<br />
architect<br />
regarding the<br />
nature of the rise<br />
(NB: had no<br />
mechanical units<br />
in it) and resolve<br />
clash.<br />
Core holes to be<br />
cut out or built<br />
into the wall to<br />
accommodate<br />
the fire system<br />
components.<br />
Fire collars to be<br />
installed if<br />
necessary.<br />
The<br />
disciplines<br />
responsible<br />
for this clash<br />
are Hydraulic,<br />
Architectural;<br />
and<br />
Mechanical.<br />
The Fire<br />
Engineer, the<br />
Architect and<br />
the Structural<br />
Engineer are<br />
responsible<br />
for the<br />
resolution of<br />
this clash<br />
instance.<br />
This clash is<br />
of a<br />
miscellaneou<br />
s nature and<br />
depending<br />
on the visual<br />
inspection of<br />
the clash; it<br />
seems that it<br />
can be easily<br />
resolved by<br />
general<br />
communicati<br />
ons between<br />
the architect<br />
and the<br />
Hydraulic<br />
Engineer.<br />
This clash is<br />
of low<br />
severity due<br />
to the limited<br />
instances<br />
and relative<br />
ease of<br />
resolving the<br />
clash.<br />
Architectural<br />
Building<br />
System<br />
Architectural<br />
Building<br />
System<br />
Hydraulic<br />
(Drainage)<br />
Building<br />
System<br />
Fire Building<br />
System<br />
6 – Instances<br />
identified by<br />
manual inspection<br />
of the automated<br />
clash detection<br />
results.<br />
1– Instance<br />
identified by<br />
manual inspection<br />
of the automated<br />
clash detection<br />
results.<br />
28
16212 – Digital Design and Construction<br />
Assessment Task; UTS Central Project<br />
Model Coordination Audit<br />
5.1.12 LVL.<br />
ROOF<br />
Hard<br />
Pressurised fire<br />
pipe<br />
intersecting<br />
basic<br />
blockwork wall<br />
with a ceiling<br />
located<br />
immediately<br />
above.<br />
Core holes to be<br />
cut out or built<br />
into the wall to<br />
accommodate<br />
the fire system<br />
components.<br />
Fire collars to be<br />
installed if<br />
necessary.<br />
The Fire<br />
Engineer, the<br />
Architect and<br />
the Structural<br />
Engineer are<br />
responsible<br />
for the<br />
resolution of<br />
this clash<br />
instance.<br />
This clash is<br />
of low<br />
severity due<br />
to the limited<br />
instances<br />
and relative<br />
ease of<br />
resolving the<br />
clash.<br />
Architectural<br />
Building<br />
System<br />
Fire Building<br />
System<br />
2 – Instances<br />
identified by the<br />
manual inspection<br />
of the automated<br />
clash detection<br />
results.<br />
5.1.13 LVL.<br />
ROOF<br />
5.1.14 LVL.<br />
ROOF<br />
Hard<br />
Hard<br />
Cable tray<br />
intersecting the<br />
composite<br />
ceiling and<br />
nearby<br />
mechanical<br />
duct.<br />
Cable tray<br />
intersecting the<br />
composite<br />
ceiling and<br />
nearby fire<br />
services.<br />
Cable tray to be<br />
dropped by 150<br />
and shifted to<br />
the left by<br />
400mm.<br />
Arrange a<br />
design<br />
coordination<br />
meeting<br />
between the<br />
services<br />
consultants,<br />
Structural<br />
Engineer and<br />
the Architect to<br />
resolve this issue.<br />
Electrical<br />
Engineer and<br />
the project<br />
Architect are<br />
responsible<br />
for the<br />
resolution of<br />
this clash.<br />
Mechanical<br />
Engineer<br />
would also<br />
be engaged<br />
due to the<br />
proximity of<br />
the duct to<br />
the cable<br />
trays and QA<br />
purposes (eg:<br />
prevent unidentified<br />
knock on<br />
effects).<br />
The Electrical<br />
Engineer and<br />
the architect<br />
are the two<br />
direct<br />
disciplines<br />
responsible.<br />
Other<br />
services<br />
consultants<br />
including Fire<br />
and Structural<br />
may also be<br />
involved.<br />
This clash is<br />
of low<br />
severity due<br />
to the ease<br />
of its<br />
resolution<br />
and limited<br />
instances;<br />
however 3<br />
disciplines still<br />
need to be<br />
involved in its<br />
coordinated<br />
amendment.<br />
This clash is<br />
of high<br />
severity due<br />
to the<br />
complexity<br />
of the clash<br />
and the<br />
multiple<br />
consultants<br />
required<br />
resolving it.<br />
Arch.<br />
Building<br />
System<br />
Arch.<br />
Building<br />
System<br />
Electrical<br />
Building<br />
System<br />
Electrical<br />
Building<br />
System.<br />
1– Instance<br />
identified by<br />
manual inspection<br />
of the automated<br />
clash detection<br />
results.<br />
1– Instance<br />
identified by<br />
manual inspection<br />
of the automated<br />
clash detection<br />
results.<br />
29
16212 – Digital Design and Construction<br />
Assessment Task; UTS Central Project<br />
Model Coordination Audit<br />
5.1.15 LVL.<br />
ROOF<br />
5.1.16 LVL.<br />
ROOF<br />
Hard<br />
Hard<br />
Large<br />
mechanical<br />
unit<br />
intersecting<br />
aluminum<br />
louvers and<br />
plasterboard<br />
basic walls.<br />
Large<br />
mechanical<br />
unit<br />
intersecting<br />
basic walls in<br />
multiple areas.<br />
A design<br />
coordination<br />
meeting<br />
between the<br />
Mechanical<br />
Engineer and<br />
Architect to be<br />
arranged<br />
urgently. Other<br />
design<br />
consultants to<br />
also be invited to<br />
determine<br />
potential knock<br />
on effects and<br />
how to resolve<br />
them.<br />
NB: May just be<br />
an illegal clash.<br />
A design<br />
coordination<br />
meeting<br />
between the<br />
Mechanical<br />
Engineer and<br />
Architect to be<br />
arranged<br />
urgently. Other<br />
design<br />
consultants to<br />
also be invited to<br />
determine<br />
potential knock<br />
on effects and<br />
how to resolve<br />
them.<br />
NB: May just be<br />
an illegal clash.<br />
The<br />
Mechanical<br />
Engineer and<br />
the architect<br />
are the two<br />
main<br />
consultants<br />
responsible<br />
for the<br />
resolution of<br />
this clash<br />
instance.<br />
Other<br />
consultants<br />
are to<br />
provide<br />
advisory<br />
assistance,<br />
The<br />
Mechanical<br />
Engineer and<br />
the architect<br />
are the two<br />
main<br />
consultants<br />
responsible<br />
for the<br />
resolution of<br />
this clash<br />
instance.<br />
Other<br />
consultants<br />
are to<br />
provide<br />
advisory<br />
assistance,<br />
This clash is<br />
of high<br />
severity due<br />
to the<br />
complexity<br />
of the clash<br />
and the<br />
multiple<br />
consultants<br />
required<br />
resolving it.<br />
This clash is<br />
of high<br />
severity due<br />
to the<br />
complexity<br />
of the clash<br />
and the<br />
multiple<br />
consultants<br />
required<br />
resolving it.<br />
Arch.<br />
Building<br />
System<br />
Arch.<br />
Building<br />
System<br />
Mechanical<br />
Building<br />
System<br />
Mechanical<br />
Building<br />
System<br />
2 – Instances<br />
identified by the<br />
manual inspection<br />
of the automated<br />
clash detection<br />
results.<br />
4 – Instances<br />
identified by the<br />
manual inspection<br />
of the automated<br />
clash detection<br />
results.<br />
30
16212 – Digital Design and Construction<br />
Assessment Task; UTS Central Project<br />
Model Coordination Audit<br />
5.1.17 LVL.<br />
ROOF<br />
5.1.18 LVL.<br />
ROOF<br />
Hard<br />
Hard<br />
A vertical<br />
section of<br />
pressurised<br />
Hydraulic<br />
(water & Gas)<br />
pipe<br />
intersecting a<br />
composite<br />
ceiling.<br />
A horizontal<br />
section of<br />
pressurised<br />
Hydraulic<br />
(water & Gas)<br />
pipe<br />
intersecting a<br />
basic block<br />
wall in two<br />
sections.<br />
No action as this<br />
is an illegal clash.<br />
Hydraulic<br />
Engineer to<br />
confirm that the<br />
clash is an illegal<br />
clash and that<br />
the block wall<br />
core is being<br />
used as a riser.<br />
If not, the<br />
Hydraulic<br />
Engineer is to<br />
communicate<br />
with the<br />
Architect and<br />
Structural<br />
Engineer on<br />
possibility of<br />
turning the wall<br />
into a riser, or<br />
move that<br />
section of<br />
hydraulic pipes.<br />
The<br />
disciplines<br />
responsible<br />
for this clash<br />
are Hydraulic<br />
and<br />
Architectural;<br />
however as it<br />
is an illegal<br />
clash- no<br />
further action<br />
will be<br />
required.<br />
The<br />
disciplines<br />
responsible<br />
for this clash<br />
are Hydraulic,<br />
Structural and<br />
Architectural.<br />
N/A – is an<br />
illegal clash.<br />
Clash<br />
severity is<br />
moderate<br />
due to the<br />
very limited<br />
instances<br />
and<br />
simplicity of<br />
the clash<br />
instance.<br />
Arch.<br />
Building<br />
System<br />
Arc.<br />
Building<br />
System<br />
Hydraulic<br />
(Water &<br />
Gas)<br />
Building<br />
System<br />
Hydraulic<br />
(Water &<br />
Gas)<br />
Building<br />
System<br />
4 – Instances<br />
identified by the<br />
manual inspection<br />
of the automated<br />
clash detection<br />
results.<br />
2 – Instances<br />
identified by the<br />
manual inspection<br />
of the automated<br />
clash detection<br />
results.<br />
31
16212 – Digital Design and Construction<br />
Assessment Task; UTS Central Project<br />
Model Coordination Audit<br />
5.1.19 LVL.<br />
ROOF<br />
5.1.20 LVL.<br />
ROOF<br />
Hard<br />
Hard<br />
A vertical<br />
section of<br />
pressurised<br />
Hydraulic<br />
(water & Gas)<br />
pipe<br />
intersecting<br />
level 17<br />
concrete slab.<br />
A section of<br />
pressurised<br />
hydraulic pipe<br />
intersecting a<br />
structural<br />
concrete<br />
beam.<br />
No action as this<br />
is an illegal clash.<br />
Pressurised<br />
hydraulic pipe to<br />
be shifted to the<br />
left by 200mm<br />
then brought<br />
forward by<br />
200mm, and<br />
then lowered by<br />
200mm so as to<br />
avoid<br />
intersection with<br />
the network of<br />
fire pipes below.<br />
The<br />
disciplines<br />
responsible<br />
for this clash<br />
are Hydraulic<br />
and<br />
Structural;<br />
however as it<br />
is an illegal<br />
clash- no<br />
further action<br />
will be<br />
required.<br />
The<br />
disciplines<br />
responsible<br />
for this clash<br />
are Hydraulic<br />
and<br />
Structural.<br />
N/A – is an<br />
illegal clash.<br />
This clash<br />
instance is<br />
moderate<br />
due to the<br />
low number<br />
of instances,<br />
relative ease<br />
of resolving<br />
the clash<br />
and level of<br />
priority<br />
assumed by<br />
the two<br />
disciplines<br />
clashed.<br />
Structural<br />
Building<br />
System<br />
Structural<br />
Building<br />
System<br />
Hydraulic<br />
(Water &<br />
Gas)<br />
Building<br />
System<br />
Hydraulic<br />
(Water &<br />
Gas)<br />
Building<br />
System<br />
4 – Instances<br />
identified by the<br />
manual inspection<br />
of the automated<br />
clash detection<br />
results.<br />
2 – Instances<br />
identified by the<br />
manual inspection<br />
of the automated<br />
clash detection<br />
results.<br />
32
16212 – Digital Design and Construction<br />
Assessment Task; UTS Central Project<br />
Model Coordination Audit<br />
Automated Services Check by #12609842 for Level Roof<br />
Item<br />
No.<br />
Location<br />
Model Image<br />
Clash<br />
Type<br />
Description of<br />
Clash and/or<br />
Root Cause<br />
Suggested<br />
Action /<br />
Comments<br />
Disciplines<br />
responsible/<br />
Assigned to<br />
Severity of<br />
Clash<br />
Clashed<br />
System A<br />
Clashed<br />
System B<br />
Count<br />
6.0 Navisworks Clash Detection<br />
6.1 Roof Level<br />
6.1.1<br />
LVL.<br />
ROOF<br />
Hard<br />
Section of<br />
hydraulic pipe<br />
work<br />
intersecting a<br />
section of<br />
mechanical<br />
duct.<br />
Root Cause =<br />
hydraulic pipes<br />
located<br />
110mm into the<br />
side of the<br />
duct.<br />
Hydraulic pipe to<br />
be shifted to the<br />
left by 115mm so<br />
as not to<br />
intersect the<br />
duct, and be<br />
relocated into<br />
the nearby<br />
150mm wide<br />
riser.<br />
NB: The pipe is<br />
116mm wide.<br />
The<br />
disciplines<br />
responsible<br />
for the<br />
resolving this<br />
clash are the<br />
Hydraulic<br />
and<br />
Mechanical.<br />
This clash is<br />
of low<br />
severity due<br />
to ease of<br />
resolving the<br />
clash and<br />
limited<br />
instances.<br />
No potential<br />
knock on<br />
effects were<br />
identified<br />
when<br />
developing<br />
the<br />
proposed<br />
solution.<br />
Mechanical<br />
Building<br />
System<br />
Hydraulic<br />
(Drainage)<br />
Building<br />
System<br />
2 – Instances<br />
identified by<br />
the manual<br />
inspection of<br />
the<br />
automated<br />
clash<br />
detection<br />
results.<br />
6.1.2 LVL. 8<br />
Hard<br />
Section of<br />
hydraulic pipe<br />
intersecting a<br />
nearby mech<br />
unit in multiple<br />
location.<br />
Root cause =<br />
proximity of<br />
several services<br />
in a small<br />
space<br />
Design<br />
coordination<br />
meeting to be<br />
arranged.<br />
NB: the hydraulic<br />
pipes are in very<br />
close proximity<br />
with the fire<br />
pipes and are<br />
already clashing<br />
with nearby<br />
electrical trays.<br />
The Hydraulic<br />
Engineer,<br />
Mechanical<br />
Engineer are<br />
directly<br />
responsible<br />
for the<br />
resolution of<br />
the clash. The<br />
Electrical and<br />
Fire Engineers<br />
would be<br />
required to<br />
provide<br />
assistance in<br />
the<br />
identification<br />
This clash is<br />
of high<br />
severity due<br />
to<br />
complexity<br />
of the clash<br />
and many<br />
potential<br />
knock on<br />
effects such<br />
as clashes<br />
with nearby<br />
electrical<br />
trays and fire<br />
pipes.<br />
Mechanical<br />
Building<br />
System<br />
Hydraulic<br />
(Drainage)<br />
Building<br />
System<br />
8 – Instances<br />
identified by<br />
the manual<br />
inspection of<br />
the<br />
automated<br />
clash<br />
detection<br />
results.<br />
33
16212 – Digital Design and Construction<br />
Assessment Task; UTS Central Project<br />
Model Coordination Audit<br />
of knock-on<br />
effects.<br />
6.1.3<br />
LVL.<br />
ROOF<br />
Hard<br />
Sections of<br />
pressurized<br />
hydraulic pipes<br />
intersecting<br />
mechanical<br />
units.<br />
NB: there is a<br />
226mm open<br />
gap to the<br />
right of the two<br />
pipes (shown in<br />
the second<br />
image).<br />
Pipe are to be<br />
shifted to the<br />
right by 450mm<br />
and narrowed so<br />
that they fit<br />
easily into the<br />
nearby clear<br />
space.<br />
The Hydraulic<br />
Engineer and<br />
mechanical<br />
Engineer are<br />
responsible<br />
for<br />
developing a<br />
solution to this<br />
clash. Other<br />
services<br />
engineers<br />
would also<br />
be consulted<br />
to identify<br />
potential<br />
knock-on<br />
effects.<br />
These clash<br />
instances are<br />
of moderate<br />
severity due<br />
to the limited<br />
number of<br />
clashes, but<br />
high<br />
potential for<br />
knock on<br />
effects such<br />
as cable<br />
trays that<br />
perpendicul<br />
arly pass<br />
through the<br />
open space<br />
on levels<br />
below.<br />
Mechanical<br />
Building<br />
System<br />
Hydraulic<br />
(Water &<br />
Gas)<br />
Building<br />
System<br />
4 – Instances<br />
identified by<br />
the manual<br />
inspection of<br />
the<br />
automated<br />
clash<br />
detection<br />
results.<br />
6.1.4 LV.8<br />
Hard<br />
A local region<br />
of hydraulic<br />
pipe network<br />
intersecting a<br />
nearby section<br />
of mechanical<br />
duct units.<br />
Root cause =<br />
hydraulic pipes<br />
are too low.<br />
This section of<br />
duct should be<br />
lifted by 250mm<br />
to avoid further<br />
clashes with any<br />
other services.<br />
Hydraulic<br />
Engineer and<br />
Mechanical<br />
engineer are<br />
responsible<br />
for the<br />
resolution of<br />
this clash<br />
instance.<br />
This clash<br />
type is of<br />
moderate<br />
severity due<br />
to the many<br />
instances,<br />
yet ease of<br />
resolution<br />
and minimal<br />
knock-on<br />
effects<br />
presented by<br />
the<br />
proposed<br />
Mechanical<br />
Building<br />
System<br />
Hydraulic<br />
(Water &<br />
Gas)<br />
Building<br />
System<br />
8 – Instances<br />
identified by<br />
the manual<br />
inspection of<br />
the<br />
automated<br />
clash<br />
detection<br />
results.<br />
34
16212 – Digital Design and Construction<br />
Assessment Task; UTS Central Project<br />
Model Coordination Audit<br />
solution.<br />
6.1.5<br />
6.1.6<br />
LVL.<br />
ROOF<br />
LVL.<br />
17<br />
Hard<br />
Hard<br />
Network of<br />
cable trays<br />
clashing with<br />
mechanical<br />
duct units in<br />
multiple<br />
locations.<br />
Root cause =<br />
vexed root<br />
causes; is<br />
partially due to<br />
the height and<br />
overall<br />
location of the<br />
cable trays.<br />
Vertical cable<br />
tray<br />
intersecting<br />
mechanical<br />
duct.<br />
Root cause =<br />
cable tray if<br />
80mm too far<br />
to the left.<br />
A design<br />
coordination<br />
meeting should<br />
be arranged.<br />
NB: cable tray<br />
can’t be lifted or<br />
shifted without<br />
producing<br />
multiple knock<br />
on effects.<br />
NB: may need to<br />
individually<br />
resolve all the<br />
clashes by<br />
shifting, lifting,<br />
extending,<br />
bending and<br />
lowering the<br />
trays at different<br />
points.<br />
Shift the cable<br />
tray to right by<br />
80mm so that it is<br />
relocated into<br />
the 200mm open<br />
space on the<br />
right between<br />
the duct and<br />
vertical pipes.<br />
The electrical<br />
and<br />
mechanical<br />
consultants<br />
are directly<br />
responsible<br />
for the<br />
resolution of<br />
these clashes,<br />
however due<br />
to the<br />
complex<br />
nature of the<br />
clash, other<br />
services<br />
consultants<br />
would also<br />
be involved.<br />
The Electrical<br />
Engineer is<br />
the holds<br />
lead<br />
responsibility<br />
for resolving<br />
this clash,<br />
and the<br />
Mech and<br />
Hydraulic<br />
Engineers are<br />
to confirm<br />
that<br />
proposed<br />
solution is<br />
This clash<br />
type is of<br />
high severity<br />
due to the<br />
many<br />
instances<br />
and the high<br />
potential of<br />
knock effects<br />
upon lifting,<br />
lowering and<br />
shifting of the<br />
electrical<br />
trays.<br />
This clash is<br />
of low<br />
severity as<br />
there are<br />
minimal<br />
instances<br />
and the<br />
proposed<br />
solution is of<br />
relative ease<br />
to resolve<br />
with minimal<br />
knock-on<br />
effects<br />
identified.<br />
Mechanical<br />
Building<br />
System<br />
Mechanical<br />
Building<br />
System<br />
Electrical<br />
Building<br />
System<br />
Electrical<br />
Building<br />
System<br />
11 –<br />
Instances<br />
identified by<br />
the manual<br />
inspection of<br />
the<br />
automated<br />
clash<br />
detection<br />
results.<br />
2 – Instances<br />
identified by<br />
the manual<br />
inspection of<br />
the<br />
automated<br />
clash<br />
detection<br />
results.<br />
35
16212 – Digital Design and Construction<br />
Assessment Task; UTS Central Project<br />
Model Coordination Audit<br />
acceptable.<br />
6.1.7<br />
LVL.<br />
ROOF<br />
Hard<br />
Section of fire<br />
pipe colliding<br />
with a large<br />
mechanical<br />
duct unit.<br />
Root cause =<br />
height of the<br />
fire pipe<br />
network.<br />
Fire pipe network<br />
on the roof to be<br />
lifted by 500mm.<br />
The Fire<br />
Engineer is<br />
the main<br />
consultant<br />
responsible<br />
for resolving<br />
this issue, with<br />
the<br />
Mechanical<br />
and Structural<br />
Engineers<br />
also tasked<br />
with advisory<br />
roles.<br />
This clash is<br />
of a high<br />
severity<br />
nature due<br />
to the<br />
disciplines<br />
involved (NB:<br />
the fire pipe<br />
also<br />
intersects<br />
multiple<br />
structural<br />
steel<br />
members<br />
nearby).<br />
However its<br />
resolution is<br />
of relative<br />
ease to fix.<br />
Mechanical<br />
Building<br />
System<br />
Fire<br />
Building<br />
System<br />
2 – Instances<br />
identified by<br />
the manual<br />
inspection of<br />
the<br />
automated<br />
clash<br />
detection<br />
results.<br />
6.1.8<br />
LVL.<br />
ROOF<br />
Hard<br />
A section of fire<br />
cable tray (dry<br />
fire) is<br />
intersecting<br />
nearby large<br />
mechanical<br />
units in multiple<br />
locations.<br />
Root cause:<br />
Poor<br />
positioning of<br />
the dry fire<br />
system.<br />
This section of<br />
the Fire Building<br />
System on the<br />
floor should be<br />
shifted the left by<br />
700mm so as to<br />
avoid the<br />
multiple large<br />
mechanical units<br />
nearby.<br />
The Fire<br />
Engineer<br />
would be the<br />
leading<br />
consultant<br />
responsible<br />
with resolving<br />
this clash<br />
instance.<br />
This clash is<br />
of low<br />
severity as<br />
there are<br />
only 3<br />
instances of<br />
the clash<br />
and the<br />
proposed<br />
resolution<br />
strategy<br />
presents<br />
minimal<br />
knock-on<br />
effects.<br />
Mechanical<br />
Building<br />
System<br />
Fire<br />
Building<br />
System<br />
3 – Instances<br />
identified by<br />
the manual<br />
inspection of<br />
the<br />
automated<br />
clash<br />
detection<br />
results.<br />
36
16212 – Digital Design and Construction<br />
Assessment Task; UTS Central Project<br />
Model Coordination Audit<br />
6.1.9<br />
6.1.10<br />
Hard<br />
Hard<br />
Three hydraulic<br />
pipes<br />
intersecting a<br />
section of<br />
electrical<br />
cable tray.<br />
Root cause =<br />
poor location<br />
of the<br />
hydraulic pipes<br />
by the<br />
engineer.<br />
A section of<br />
hydraulic pipe<br />
is intersecting a<br />
nearby electric<br />
cable tray.<br />
Hydraulic pipes<br />
should be shifted<br />
forward by<br />
200mm so as to<br />
be relocated to<br />
the open void in<br />
front of the<br />
cable tray<br />
(shown in image<br />
2).<br />
The electrical<br />
cable tray<br />
should be lifted<br />
by 200mm, as<br />
the hydraulic<br />
pipe needs<br />
special height<br />
considerations to<br />
ensure that<br />
necessary runs<br />
are achieved.<br />
This clash<br />
would be the<br />
responsibility<br />
of the<br />
Hydraulic<br />
Engineer to<br />
resolve as<br />
changes to<br />
their system is<br />
the most<br />
appropriate<br />
solution.<br />
Other<br />
services<br />
engineers<br />
should be<br />
informed to<br />
confirm no<br />
unidentified<br />
knock-on<br />
effects.<br />
The Electrical<br />
Engineer<br />
would be the<br />
consultant<br />
responsible<br />
for resolving<br />
this issue.<br />
This clash is<br />
of low<br />
severity due<br />
to limited<br />
clash<br />
instances<br />
and the<br />
relative ease<br />
of resolving<br />
the clash<br />
with minimal<br />
knock-on<br />
effects.<br />
This clash is<br />
of low<br />
severity due<br />
to singular<br />
clash<br />
instance and<br />
the relative<br />
ease of<br />
resolving the<br />
clash with<br />
minimal<br />
knock-on<br />
effects.<br />
Hydraulic<br />
(Drainage)<br />
Building<br />
System<br />
Hydraulic<br />
(Drainage)<br />
Building<br />
System<br />
Electrical<br />
Building<br />
System<br />
Electrical<br />
Building<br />
System<br />
3 – Instances<br />
identified by<br />
the manual<br />
inspection of<br />
the<br />
automated<br />
clash<br />
detection<br />
results.<br />
1 – Instance<br />
identified by<br />
the manual<br />
inspection of<br />
the<br />
automated<br />
clash<br />
detection<br />
results.<br />
37
16212 – Digital Design and Construction<br />
Assessment Task; UTS Central Project<br />
Model Coordination Audit<br />
6.1.11 LVL. 8<br />
6.1.12 LVL.8<br />
Soft<br />
Hard<br />
A section of<br />
hydraulic pipe<br />
work is<br />
intersecting the<br />
outer rim of a<br />
fire sprinkler<br />
guard zone.<br />
A section of<br />
pressurised fire<br />
pipe is<br />
perpendicularl<br />
y intersecting a<br />
dry fire cable<br />
tray.<br />
This clash is to be<br />
resolved by<br />
raising the issue<br />
at the next<br />
design meeting.<br />
This clash can be<br />
resolved by<br />
lowering the fire<br />
pipe by 100mm<br />
so that it wraps<br />
under the cable<br />
tray but doesn’t<br />
intersect the<br />
HVAC duct<br />
below (yellow).<br />
All services<br />
engineers<br />
would be<br />
directly<br />
involved in<br />
the resolution<br />
of this clash<br />
as image 2<br />
shows that<br />
this is a clash<br />
hotspot. The<br />
Structural<br />
Engineer and<br />
Architect are<br />
unlikely to be<br />
impacted as<br />
there is much<br />
space above<br />
the clash<br />
zone to<br />
resolve the<br />
many<br />
clashes.<br />
The Hydraulic<br />
Engineer is<br />
the leading<br />
consultant<br />
responsible<br />
with resolving<br />
this clash. The<br />
Fire and<br />
Mechanical<br />
Consultants<br />
would be<br />
responsible<br />
with<br />
confirming<br />
that the<br />
proposed<br />
solution won’t<br />
produce<br />
further knockon<br />
effects<br />
unidentified<br />
in this model.<br />
This clash is<br />
of high<br />
severity due<br />
to the many<br />
knock on<br />
effects that<br />
will likely arise<br />
whilst<br />
resolving the<br />
direct issue.<br />
Eg:<br />
continued<br />
clash with<br />
the nearby<br />
cable tray<br />
and mech<br />
unit, but no<br />
clash<br />
between<br />
hydraulic<br />
and fire<br />
systems.<br />
This clash is<br />
classified as<br />
of low<br />
severity as<br />
there is only<br />
one instance<br />
of the clash<br />
and the<br />
clash can be<br />
easily<br />
resolved with<br />
no<br />
identifiable<br />
knock-on<br />
effects.<br />
Hydraulic<br />
(Drainage)<br />
Building<br />
System<br />
Hydraulic<br />
(Drainage)<br />
Building<br />
System<br />
Fire<br />
Building<br />
System<br />
Fire<br />
Building<br />
System<br />
1– Instance<br />
identified by<br />
the manual<br />
inspection of<br />
the<br />
automated<br />
clash<br />
detection<br />
results.<br />
1 – Instance<br />
identified by<br />
the manual<br />
inspection of<br />
the<br />
automated<br />
clash<br />
detection<br />
results.<br />
38
16212 – Digital Design and Construction<br />
Assessment Task; UTS Central Project<br />
Model Coordination Audit<br />
6.1.13 No Hydraulic - Electrical Building System clashes were identified.<br />
6.1.14 No Hydraulic - Electrical Building System clashes were identified.<br />
Hydraulic<br />
(Water &<br />
Gas) Building<br />
System<br />
Hydraulic<br />
(Water &<br />
Gas) Building<br />
System<br />
Hydraulic<br />
(Water &<br />
Gas) Building<br />
System<br />
Electrical<br />
Building<br />
System<br />
Electrical<br />
Building<br />
System<br />
Fire<br />
Building<br />
System<br />
0 – Instances<br />
identified by<br />
the<br />
automated<br />
clash<br />
detection<br />
assessment.<br />
0 – Instances<br />
identified by<br />
the<br />
automated<br />
clash<br />
1 – Instance<br />
identified by<br />
the<br />
automated<br />
clash<br />
6.1.15 LVL. 17<br />
6.1.16<br />
NB: only one clash between the Hydraulic (Water & Gas) and Fire Building Systems were identified and has been reported in<br />
the row above.<br />
Hydraulic<br />
(Water &<br />
Gas) Building<br />
System<br />
Fire<br />
Building<br />
System<br />
N/A<br />
39
16212 – Digital Design and Construction<br />
Assessment Task; UTS Central Project<br />
Model Coordination Audit<br />
6.1.17<br />
Hard<br />
A pressurised<br />
fire pipe is<br />
interesting an<br />
electrical<br />
cable tray.<br />
Root cause =<br />
location of the<br />
fire pipe system<br />
directly above<br />
the electrical<br />
system, hence<br />
intersecting it<br />
at multiple<br />
locations.<br />
As open space<br />
above the<br />
system is not of<br />
scarcity, the fire<br />
pipe can be<br />
lifted by 500mm<br />
and shifted<br />
backwards by<br />
800mm which<br />
would resolve all<br />
4 clash<br />
instances.<br />
The Fire<br />
Engineer<br />
would be the<br />
leading<br />
consultant on<br />
the resolution<br />
of this issue.<br />
The Electrical,<br />
Mechanical<br />
and<br />
Hydraulic<br />
Engineers<br />
would be<br />
tasked with<br />
QA<br />
responsibilities<br />
.<br />
This clash<br />
instance is of<br />
low severity<br />
as the<br />
proposed<br />
solution isn’t<br />
difficult to<br />
exercise and<br />
ensures no<br />
identifiable<br />
knock-on<br />
effects.<br />
Electrical<br />
Building<br />
System<br />
Fire<br />
Building<br />
System<br />
3 – Instances<br />
identified by<br />
the<br />
automated<br />
clash<br />
6.1.18 LVL. 8<br />
Hard<br />
A pressurised<br />
fire pipe is<br />
interesting an<br />
electrical<br />
cable tray.<br />
Root cause =<br />
location of the<br />
fire pipe system<br />
directly above<br />
the electrical<br />
system, hence<br />
intersecting it<br />
at multiple<br />
locations.<br />
Pressurised fire<br />
pipes along this<br />
row to be shifted<br />
to the right by<br />
500mm.<br />
The Fire<br />
Engineer<br />
would be<br />
mainly<br />
responsible<br />
for the<br />
resolution of<br />
this clash. The<br />
services<br />
engineers<br />
would be<br />
tasked with<br />
QA<br />
responsibilities<br />
and<br />
confirming no<br />
other knockon<br />
effects.<br />
This clash is<br />
of low<br />
severity as<br />
the<br />
proposed<br />
solution<br />
presents<br />
minimal<br />
knock on<br />
effects.<br />
Electrical<br />
Building<br />
System<br />
Fire<br />
Building<br />
System<br />
5 – Instances<br />
identified by<br />
the<br />
automated<br />
clash<br />
40
16212 – Digital Design and Construction<br />
Assessment Task; UTS Central Project<br />
Model Coordination Audit<br />
Other Significant Clashes<br />
Item<br />
No.<br />
Location<br />
Model Image<br />
Clash<br />
Type<br />
Description of<br />
Clash and/or<br />
Root Cause<br />
Suggested<br />
Action /<br />
Comments<br />
Disciplines<br />
responsible/<br />
Assigned to<br />
Severity of<br />
Clash<br />
Clashed Systems<br />
Count of<br />
clashes in<br />
local area<br />
7.0 Navisworks Clash Detection<br />
7.1 Roof Level<br />
LVL. 8 Hard Hydraulic pipes<br />
are intersecting<br />
a section of<br />
mechanical rigid<br />
duct and the<br />
nearby fire<br />
sprinkler is<br />
intersecting the<br />
same section of<br />
duct. The<br />
7.1.1<br />
Hydraulic pipes<br />
in this area are<br />
also intersecting<br />
the cable tray<br />
on the right.<br />
Arrange a<br />
design<br />
coordination<br />
meeting and<br />
develop<br />
solutions for<br />
each of the<br />
systems which<br />
utilises the vast<br />
open space<br />
above.<br />
Mechanical,<br />
Fire,<br />
Electrical;<br />
Hydraulic.<br />
High severity<br />
due to the<br />
complexity of<br />
the clash<br />
and<br />
likelihood of<br />
knock-on<br />
effects if not<br />
resolved in<br />
coordination<br />
with the<br />
other services<br />
consultants.<br />
Mechanical Building System<br />
Fire Building System<br />
Electrical Building System<br />
Hydraulic (Drainage)<br />
Building System<br />
3<br />
7.1.2<br />
LVL.<br />
ROOF<br />
Hard<br />
Root Cause =<br />
Poor<br />
coordination<br />
between the<br />
services<br />
consultants.<br />
HVAC units<br />
intersecting<br />
aluminum louver<br />
wall. Hydraulic<br />
pipes (red and<br />
blue) intersecting<br />
mechanical<br />
units.<br />
NB: Electrical<br />
tray network<br />
open ended.<br />
Arrange a<br />
design<br />
coordination<br />
meeting<br />
between the<br />
involved<br />
disciplines.<br />
Mechanical;<br />
Architectural;<br />
Hydraulic;<br />
Electrical.<br />
High severity<br />
due to the<br />
complexity of<br />
the clash<br />
and<br />
likelihood of<br />
knock-on<br />
effects if not<br />
resolved in<br />
coordination<br />
with the<br />
other services<br />
consultants.<br />
Mechanical Building<br />
System;<br />
Architectural Building<br />
System;<br />
Hydraulic Building System;<br />
Electrical Building System.<br />
6<br />
41
16212 – Digital Design and Construction<br />
Assessment Task; UTS Central Project<br />
Model Coordination Audit<br />
7.1.3<br />
LVL.<br />
ROOF<br />
Hard<br />
Structural steel<br />
member<br />
intersecting a<br />
section of<br />
mechanical<br />
duct (pink).<br />
Pressurised fire<br />
pipes<br />
intersecting steel<br />
member.<br />
Electrical cable<br />
tray also<br />
intersecting the<br />
same section of<br />
mechanical<br />
duct as the steel<br />
member.<br />
Arrange a<br />
design<br />
coordination<br />
meeting<br />
between the<br />
involved<br />
disciplines.<br />
Structural;<br />
Mechanical;<br />
Fire;<br />
Electrical.<br />
High severity<br />
due to the<br />
complexity of<br />
the clash<br />
and<br />
likelihood of<br />
knock-on<br />
effects if not<br />
resolved in<br />
coordination<br />
with the<br />
other services<br />
consultants.<br />
Structural Building System;<br />
Mechanical Building<br />
System;<br />
Fire Building System;<br />
Electrical Building System.<br />
5<br />
Fire pipe further<br />
down<br />
intersecting<br />
another<br />
mechanical unit.<br />
42
16212 – Digital Design and Construction<br />
Assessment Task; UTS Central Project<br />
Model Coordination Audit<br />
3.0 Summary of Findings<br />
The level of development (LOD) of this federated model is LOD 200. This is because most<br />
model elements were information rich and meant that the different trades would be able to<br />
start ordering materials and equipment at this stage of design development.<br />
However, there were many clashes of significance identified on the levels investigated<br />
within this report which affirms that current design coordination to date need to urgently<br />
resolved.<br />
Furthermore, this model is a good schematic design which needs vast developments and<br />
amendments before construction can commence based off these designs. It should be<br />
noted that lower floors are usually better documented as design consultants amend plans<br />
on a bottom up basis, meaning that upper floors such as the roof are more likely to have<br />
unaddressed clashes.<br />
43