Catalyst - AEC Resource - Perth BIM Plan by DanielBiagi

July 18 2013

BIIM PRO OJECT EEXECUTTION PLLAN FO OR CO ONSTRUCTION PHASSE

FOR

TERMINA AL 1 DO OMESTIIC PIER R AND INTERN NATION NAL DEPA ARTUREES EXPA ANSION N ‐ PER RTH AIR RPORT L LOCATIO N

PEERTH, W WA, AU USTRALLIA

DEVELOPED BY ATALYST AEEC CA

VERSION 2.0 0

DATTE:24 JULY 2 2013 TER RMINAL 1 DOMES STIC PIER AND INTERNATIONAL N DEPARTURES EXP PANSION - PERTH AIRPORT BUIILDING INFORMATTION MODELLING G PROJECT EXEC CUTION PLAN - VERSION 2.0

July 18 2013

BIM PROJECT EXECUTION PLAN VERSION 2.0 FOR

TERMINAL 1 DOMESTIC PIER AND INTERNATIONAL DEPARTURES EXPANSION PERTH AIRPORT DEVELOPED BY

CATALYST AEC TABLE OF CONTENTS SECTION A: BIM PROJECT EXECUTION PLAN OVERVIEW ...................................................................... 4 SECTION B: GENERAL PROJECT INFORMATION ..................................................................................... 4 SECTION C: KEY PROJECT CONTACTS .................................................................................................... 5 SECTION D: PROJECT GOALS / BIM USES ................................................................................................ 6 SECTION E: ORGANIZATIONAL ROLES / STAFFING ............................................................................... 12 SECTION F: BIM PROCESS WORKFLOW ................................................................................................. 14 SECTION G: COLLABORATION PROCEDURES ....................................................................................... 15 SECTION H: QUALITY CONTROL ............................................................................................................. 16 SECTION I: TECHNOLOGICAL INFRASTRUCTURE NEEDS .................................................................... 17 SECTION J: BIM SPECIFIC PROJECT STANDARDS - CONSTRUCTION ................................................. 18 SECTION K: MULTI-DISCIPLINE COORDINATION PROCESS .............................................................. 31 SECTION I: CLASH DETECTION WORKFLOW....................................................................................... 34 ATTACHMENT A: ABOUT BIM................................................................................................................. 43 ATTACHMENT B: REVIT GENERAL MODELING BEST PRACTICES ..................................................... 44 ATTACHMENT C: SHOP DRAWINGS AND CONSTRUCTION SCOPE OF WORKS (LOD 400) ............. 49 ATTACHMENT D: FILES MAINTENANCE CHECKLIST .......................................................................... 51 ATTACHMENT E: NAVISWORKS EXPORT SETTINGS .......................................................................... 52 ATTACHMENT F: NAVISWORKS FEDERATED MODELS DESIGN........................................................ 53 ATTACHMENT G: QA/QC PROCEDURE & SPREADSHEET BY CATALYST AEC.................................. 54 ATTACHMENT H: DEFINITIONS ............................................................................................................. 55 Disclaimer The materials in this document are provided for the sole use of the recipient and “as is” without any express or implied warranty of any kind including warranties of no infringement of intellectual property or fitness for a particular purpose. Catalyst AEC offers no assurance of uninterrupted or error free service. Catalyst AEC does not warrant the accuracy or completeness of the information, text, graphics, links or other items contained in this document. In no event Catalyst AEC will be liable for any damages whatsoever (including, without limitation, damages for loss of profits, business interruption, loss of information) arising out of the use or inability to use the information contained in this document, even if Catalyst AEC has been advised of such. Catalyst AEC reserves the right to change the information found in this document at any time without notice

TERMINAL 1 DOMESTIC PIER AND INTERNATIONAL DEPARTURES EXPANSION - PERTH AIRPORT BUILDING INFORMATION MODELLING PROJECT EXECUTION PLAN - VERSION 2.0

July 18 2013

TERMINAL 1 DOMESTIC PIER AND INTERNATIONAL DEPARTURES EXPANSION - PERTH AIRPORT BUILDING INFORMATION MODELLING PROJECT EXECUTION PLAN - VERSION 2.0

July 18 2013

SECTION A: BIM PROJECT EXECUTION PLAN OVERVIEW The intent of this document is to provide a framework that will allow the successful implementation of Building Information Modelling (BIM) on the Perth Airport Terminal 1 Domestic Pier and International Departures Expansion Project. This document defines:  best practices  collaboration with PAPL/ APP  methods  outlines requirements for coordination between all disciplines  protocols  relevant business processes  roles and responsibilities  supporting software to obtain the necessary additional information / data for handover. Building Information Modelling is an approach that is characterised by the creation and use of coordinated, internally consistent computable information about a building project. Reliable building information is the essential feature of Building Information Model (BIM) and its digital design processes. It both incorporates and moves beyond the needs of designers and focuses attention over the total life of the building, incorporating not only the Design and Documentation phase of the building, but through planning, fabrication, construction, installation and commissioning and passes through to the facilities manager for management of occupied building.

SECTION B: GENERAL PROJECT INFORMATION 1.

PROJECT OWNER:

PERTH AIRPORT PTY. LTD.

PROJECT NAME:

PERTH AIRPORT TERMINAL 1 DOMESTIC PIER AND INTERNATIONAL DEPARTURES EXPANSION

PROJECT LOCATION AND ADDRESS:

HORRIE MILLER DRIVE, PERTH, WA, AUSTRALIA

CONTRACT TYPE / DELIVERY METHOD:

LUMP SUM / CONSTRUCTION

PROJECT NUMBERS:

501B

PROJECT SCHEDULE / PHASES /

REFER TO SEPARABLE PORTION BREAKDOWN – 16 SEPARABLE PORTIONS APPLICABLE

MILESTONES:

PROJECT DESCRIPTION

REFER TO BUILT ENVIRONS PROJECT EXECUTION PLAN FOR FULL OUTLINE

TERMINAL 1 DOMESTIC PIER AND INTERNATIONAL DEPARTURES EXPANSION - PERTH AIRPORT BUILDING INFORMATION MODELLING PROJECT EXECUTION PLAN - VERSION 2.0

July 18 2013

SECTION C: KEY PROJECT CONTACTS

ROLE

Owner

ORGANIZATION

PAPL

Delegate of the APP Owner’s Representative Design Compliance & BIM Manager Design Team

CONTACT

LOCATION

PHONE

Guy Thompson

PO Box 6, Cloverdale WA Australia 6985

Via Aconex

+61 89 4788450

Steve Crook

Ground Floor, 16 Altona Street, West Perth 6005 Australia WA

Via Aconex

0408 809 860

Via Aconex Built Environs Rocky Slater

Site Office

0420 976 268

BIM Facilitator Catalyst AEC

Soledad Ferreyra

Site Office

BIM Leader in Argentina

Catalyst AEC

Mariano Gerez

Mariano Benitez, 1889, Cordoba, Argentina

Project Architect

Woods Bagot

Patrick Prseradski

Site office

Civil and Structural Engineer

Arup

Caroline Thomas

Site office

M/E/P and FP Engineer

Aurecon

Shandip Level 1 Septimus Roe Square Abeywickrema 256 Adelaide Terrace. Perth

Via Aconex

Via Aconex Via Aconex

Chris Anderson Site Office Neal Coles

Hydraulic Triple T Subcontractor Commercial

John Mcrae

105 Adams Road. Mariginup.

Gary Davies

+1 949 2098779 +61 8 93225541

+61 8 9327 8432

Via Aconex Via Aconex

+ 61 8 9223 1511 +61 8 9412 5500 +61 8 9405 4200

Via Aconex 36 Beringarra Ave Malaga

+61 8 9202 4666

Via Aconex Fire Protection National Fire Ashley Knapp 12 Davison Street Maddington John Passmore Construction Subcontractor Solutions 169 Longjiang Road, Via Aconex Team

Structural Steel MHI Subcontractor

+61 4 59786102

Via Aconex

Electrical Greenco Subcontractor

Mechanical MPM Group Andrew Subcontractor Arrowsmith

Via Aconex

Taicang Port Develop, , Taicang City, Yusheng Wang Jiangsu Province, Sushoutaicang China (Mainland China) 215433

+61 8 9459 3366

+86 512 82780668

Baggage handling

BCS

Jian Hua Yang

PO Box 5011, Hallam Vic Australia 3803

Via Aconex

Aerobridge

BCS Jian Hua Yang (Thyssenkrup)

PO Box 5011, Hallam Vic Australia 3803

Via Aconex

+61 3 97031364 +61 3 97031364

TERMINAL 1 DOMESTIC PIER AND INTERNATIONAL DEPARTURES EXPANSION - PERTH AIRPORT BUILDING INFORMATION MODELLING PROJECT EXECUTION PLAN - VERSION 2.0

July 18 2013

SECTION D: PROJECT GOALS / BIM USES In general, the BIM Execution Plan is to create a technically accurate and highly detailed BIM/3D computer model of the:  architectural components  building systems  electrical‐ including data/ communications/ PA system and CCTV  fire protection, fire alarm  hydraulic  lighting  mechanical  other systems as required by PAPL  security  signage/ way finding/ advertising (Optional‐TBD)  structural – superstructure and structural steel Intended Use: The intended use of BIM for this project will accomplish the following objectives: 1. Building services coordination and development of coordinated services shop drawings development. 2. Construction Phasing and Sequencing (Optional) 3. Coordination between disciplines and trades (clash detection) during construction phases. 4. Illustrations and presentation to Perth Airport Authorities. 5. Monitor work‐in‐place including updating of 3D Model for portraying key progress elements. 6. As a data rich legacy document for Facility Management and Maintenance. This model will be used by Perth Airport Authorities to submit permits for posterior operations, maintenance and remodelling necessary work. Current Status: At the moment of preparation of this plan, design stage has been finished. Design models have been prepared and utilised by the design team (Architects and Consultants). The computer model(s) developed from this point forward will be utilised for multiple purposes including (but not limited to): shop drawings documentation, building systems spatial coordination, & clash detection; 4D scheduling and planning & As‐Built's, facilities management (if agreed). All models will be prepared independently by various parties. Different software platforms will be utilised to create each model (as appropriate to discipline). All models will be combined into an aggregate project model using Autodesk Navisworks software to create a BIM/Virtual Design & Construction (VDC) Model and implement VDC practices.

MAJOR BIM GOALS / OBJECTIVES:

PRIORITY (HIGH/ MED/ LOW)

GOAL DESCRIPTION

POTENTIAL BIM USES

HIGH

Increase Field Productivity

Design Reviews, 3D Coordination

HIGH

Accurate 3D model for FM team

Record Model, 3D Coordination

HIGH

Eliminate Field Conflicts

3D Coordination

HIGH

Quickly Asses Cost associated with design changes

Design Reviews, 3D Coordination

MED

Track Progress During Construction

4D Modeling

LOW

Facilitate visualisation through 3D Images

3D Review and Coordination

TERMINAL 1 DOMESTIC PIER AND INTERNATIONAL DEPARTURES EXPANSION - PERTH AIRPORT BUILDING INFORMATION MODELLING PROJECT EXECUTION PLAN - VERSION 2.0

July 18 2013

BIM USES: PLAN

DESIGN

CONSTRUCT

OPERATE

PROGRAMMING

DESIGN AUTHORING

SITE UTILISATION PLANNING

BUILDING MAINTENANCE SCHEDULING

SITE ANALYSIS

DESIGN REVIEWS

CONSTRUCTION SYSTEM DESIGN

BUILDING SYSTEM ANALYSIS

3D COORDINATION

ASSET MANAGEMENT

STRUCTURAL ANALYSIS

DIGITAL FABRICATION

SPACE MANAGEMENT / TRACKING

LIGHTING ANALYSIS

3D CONTROL AND PLANNING

DISASTER PLANNING

ENERGY ANALYSIS

RECORD MODELING

MECHANICAL ANALYSIS

OTHER ENG. ANALYSIS

SUSTAINABLITY (LEED) EVALUATION

CODE VALIDATION

PHASE PLANNING (4D MODELING)

COST ESTIMATION

EXISTING CONDITIONS MODELING

POTENTIAL USES

BIM USES DEFINITIONS:

3D Coordination

Description: A process in which Clash Detection software is used during the coordination process to determine field conflicts by comparing 3D models of building systems. The goal of clash detection is to eliminate the major system conflicts prior to installation. Potential Value:  Coordinate building project through the model  Increase productivity across the project  Potential for less cost growth (i.e. less change orders)  Potential to decrease construction time – due to reduced clashes  Production of more accurate as built drawings  Reduce and eliminate field conflicts  Reduced raised RFI's ‐ significantly compared to other methods  Subcontractors can visualize construction Resources Required:  Design Authoring Software  Model Review application Team Competencies Required:  Ability to deal with people and project challenges  Ability to manipulate, navigate, and review a 3D model  Knowledge of BIM model applications for facility updates  Knowledge of building systems. TERMINAL 1 DOMESTIC PIER AND INTERNATIONAL DEPARTURES EXPANSION - PERTH AIRPORT BUILDING INFORMATION MODELLING PROJECT EXECUTION PLAN - VERSION 2.0

July 18 2013

Record Modelling Description: Record Modelling is the process used to depict an accurate representation of the physical conditions, environment, and assets of a facility. The record model should, at a minimum, contain information relating to the main architectural, structural, and MEP elements. It is the culmination of all the BIM Modelling throughout the project, including linking Operation, Maintenance, and Asset data to the As‐Built model (created from the Design, Construction, 4D Coordination Models, and Subcontractor Fabrication Models) to deliver a record model to the owner or facility manager. Additional information including equipment and space planning systems may be necessary if the owner intends to utilise the information in the future. Potential Value:  Ability for embedding future data based upon renovation or equipment replacement  Aid in future modelling and 3D design coordination for renovation  Aid in future permit processes – to understand exactly what is installed where (e.g. continuous change vs. code.)  Better accommodate owner's needs and wants  Easily assess PAPL requirement data such as room areas or environmental performance to as‐ designed, as‐built or as‐performing data.  Improve documentation of environment for future uses, e.g., renovation or historical documentation  Minimize building turnover information  Minimize required storage space for information  Minimize facility turnover dispute (e.g. link to contract with historical data highlights expectations and comparisons drawn to final product.)  Provide owner with accurate model of building, equipment, and spaces within a building to create possible synergies with other BIM Uses Resources Required:  3D Model Manipulation Tools  Access to Essential Information in Electronic Format Team Competencies Required:  Ability to manipulate, navigate, and review 3D model – in viewer software  Ability to use BIM modelling application for building updates  Ability to effectively communicate between the design and construction teams Asset Management (PAPL potential use) Description: A process in which an organised management system is bi‐directionally linked to a record model to efficiently aid in the maintenance and operation of a facility and its assets. These assets, consisting of the physical building, systems, surrounding environment, and equipment, must be maintained, upgraded, and operated at an efficiency which will satisfy both the owner and users in the most cost effective manner. It assists in financial decision‐making, short‐term and long‐term planning, and generating scheduled work orders. Asset Management utilizes the data contained in a record model to populate an asset management system which is then used to determine cost implications of changing or upgrading building assets, segregate costs of assets for financial tax purposes, and maintain a current comprehensive database that can produce the value of a company's assets. The bi‐directional link also allows users to visualise the asset in the model before servicing it potentially reducing service time.

TERMINAL 1 DOMESTIC PIER AND INTERNATIONAL DEPARTURES EXPANSION - PERTH AIRPORT BUILDING INFORMATION MODELLING PROJECT EXECUTION PLAN - VERSION 2.0

July 18 2013

Potential Value:  Assist finance/commercial department in efficiently analysing different types of assets through an increased level of visualisation  Allow for future updates of record model ‐ to show: o current building asset information after upgrades o Replacements o maintenance by tracking changes o Importing new information into model.  Automatically generate scheduled work orders for maintenance staff.  Increase the opportunity for measurement and verification of systems during building occupation  Maintain up‐to‐date facility and equipment data ‐ including but not limited to: o maintenance schedules o warranties o cost data o upgrades o replacements o damages/deterioration o maintenance records o manufacturer's data o equipment functionality  Perform and analyse facility and equipment condition assessments  Ability to produce accurate quantity take‐offs of current company assets which aids in financial reporting, bidding, and estimating the future cost implications of upgrades or replacements of a particular asset.  Provide one comprehensive source for tracking the use, performance, and maintenance of a building's assets for the owner, maintenance team, and financial department  Store operations, maintenance owner user manuals, and equipment specifications for faster access. Resources Required:  Asset Management system  Ability to Bi‐directional link facilities record model and Asset Management System. Team Competencies Required:  Ability to manipulate, navigate, and review a 3D Model (preferred but not required)  Ability to manipulate an asset management system  Knowledge of tax requirements and related financial software  Knowledge of construction and the operation of a building (replacements, upgrades, etc.)  Pre‐design knowledge of which assets are worth tracking, whether the building is dynamic vs. static, and the end needs of the building to satisfy the owner Spatial Management and Tracking (PAPL potential future use) Description: A process in which BIM is utilised to effectively distribute, manage, and track appropriate spaces and related resources within a facility. A facility building information model allows the facility management team to analyse the existing use of the space and effectively apply transition planning management towards any applicable changes. Such applications are particularly useful during a facilities renovation where building segments are to remain occupied. Space Management and Tracking ensures the appropriate allocation of spatial resources throughout the life of the facility as a record model. Potential Value:  More easily identify and allocate space for appropriate building use  Increase the efficiency of transition planning and management  Proficiently track the use of current space and resources  Assist in planning future space needs for the facility TERMINAL 1 DOMESTIC PIER AND INTERNATIONAL DEPARTURES EXPANSION - PERTH AIRPORT BUILDING INFORMATION MODELLING PROJECT EXECUTION PLAN - VERSION 2.0

July 18 2013

Resources Required:  3D Model Manipulation Team Competencies Required:  Ability to manipulate, navigate, and review record model  Ability to assess current space and assets and mange appropriately for future needs  Knowledge of facility management applications  Ability to effectively integrate the record model with the Facility Management's Application and appropriate software associated with PAPL's needs. Disaster Planning Description: A process in which emergency responders would have access to critical building information in the form of a model and information system. BIM has the potential to provide critical building information to emergency responders that could improve the efficiency of the response and minimise safety risks both within and immediately adjacent to the facility. Static building information, such as floor plans and equipment schematics, would reside in a BIM model. The BIM would help to clearly display where the emergency is located within the building, possible routes to the area, and any other harmful locations within the building. Potential Value:  Provide police, fire, public safety officials, and first responders access to critical building information in real‐time  Improve the effectiveness of emergency response  Minimise risks to responders Resources Required:  Design review software to view Record Model and components (in easily accessible area) Team Competencies Required:  Ability to manipulate, navigate, and review BIM model for facility updates  Ability to make appropriate decisions during an emergency Phase Planning (4D Modelling) – (not captured in revised Stage 2 scope) Description: A process in which a 4D model (3D models with the added dimension of time) is utilised to effectively plan the phased occupancy in a renovation, retrofit, addition, or to show the construction sequence and space requirements on a building site. 4D modelling is a powerful visualisation and communication tool that can give a project team, including the owner, a better understanding of project milestones and construction plans. Potential Value:  Better understanding of the phasing schedule by PAPL stakeholders and all project participants  Conveying the spatial complexities of the project, planning information, and support conducting additional analyses  Decreased waste  Dynamic phasing plans of occupancy offering multiple options and solutions to space conflicts  Identification of schedule, sequencing or phasing issues  Integrate planning of human, equipment and material resources with the BIM model to better schedule and cost estimate the project  Marketing purposes and publicity  Monitor procurement status of project materials  More readily constructible, operable and maintainable project TERMINAL 1 DOMESTIC PIER AND INTERNATIONAL DEPARTURES EXPANSION - PERTH AIRPORT BUILDING INFORMATION MODELLING PROJECT EXECUTION PLAN - VERSION 2.0

July 18 2013

 

Show the critical path of the project in real time. Space and workspace conflicts identified and resolved ahead of the construction process

Resources Required:  Design Authoring Software  Scheduling Software  4D Modelling Software Team Competencies Required:  Knowledge of construction scheduling and general construction process. (A 4D model is connected to a schedule, and is therefore only as good as the schedule to which it is linked).  Ability to manipulate, navigate, and review a 3D model.  Knowledge of 4D software: import geometry, manage links to schedules, produce and control animations, etc.

TERMINAL 1 DOMESTIC PIER AND INTERNATIONAL DEPARTURES EXPANSION - PERTH AIRPORT BUILDING INFORMATION MODELLING PROJECT EXECUTION PLAN - VERSION 2.0

July 18 2013

SECTION E: ORGANIZATIONAL ROLES / STAFFING

1. BIM ROLES AND RESPONSIBILITIES:

BUILT ENVIRONS/ CATALYST a. DESIGN COMPLIANCE AND BIM MANAGER:             

Communicates directly with the PAPL design team (through approved Aconex protocols) Communicates directly with the subcontractor/ construction team for conflict resolution Coordinates construction sequencing and scheduling activities. coordinates data extraction sets ‐ required by the trades and ensures that these requests are met to agreed timeframes Coordinates update of as‐constructed conditions in the Final Model deliverable Coordinates with the PAPL design team to ensure all design changes have been captured/documented in the BIM in a timely manner (be it either Contractor and PAPL initiated) Determines the BIM focus areas for coordination assessment Ensures that the Construction Team has necessary hardware and BIM Software properly installed and accessible for project use Project main point of contact for BIM related issues between the PAPL design consultancy team, the construction team, all subcontractors, suppliers and others (as required) Reports on BIM progress‐ project wide Review clash detection assessments‐ provide outline for potential solution directly with subcontractor/ construction team prior to raising to PAPL design consultancy team. Reviews and releases RFI’s for conflict resolution/ clash detection Run/ manage the coordination/clash detection meetings

b. BIM FACILITATOR: 

Compile information from smaller models from other project members and disseminating it in a useful form to all project stakeholders (i.e. create aggregate project model in NavisWorks).  Ensure that Modelling requirements and Level of Detail & Development guidelines are being adhered to by all project model contributors.  Facilitates use of composite trade models in construction coordination/clash detection meetings  Interrogate the models to determine clash/ hierarchy and potential solution  Maintain file transfer site  Manage collaborative sessions within the models  Manage the flow of Information between all team members‐ via Aconex  Oversee access rights‐ file transfer site  Prepare all visual material for BIM coordination meetings  Prepare RFIs  Preserve Record Versions of the Models ‐ incrementally  Provides detection reports by the identification and resolution of all hard and soft collisions for Design Compliance and BIM Manager assessment  Run all clash detection batches Note: BIM Facilitator/Modelling Manager is not responsible for checking models (created by others) for accuracy; this is the responsibility of the model’s “Owner”.

TERMINAL 1 DOMESTIC PIER AND INTERNATIONAL DEPARTURES EXPANSION - PERTH AIRPORT BUILDING INFORMATION MODELLING PROJECT EXECUTION PLAN - VERSION 2.0

July 18 2013

2. BIM USE STAFFING: The following table outlines the minimum commitment required by parties (as nominated) to attend meetings to see and solve BIM clashes in a collaborative site based environment. The times allocated/ indicated relate to the programmed meetings (as detailed further in this execution plan), some additional time to review clashes found and RFI closures. The time allocated for modelling has been estimated from the information sourced from interviews held. NUMBER OF TOTAL STAFF FOR ESTIMATED WORKER HOURS BIM USE

BIM USE

ORGANISATION

LOCATION(S)

3D coordination

Built Environs

Min 60/month

Site Office

3D coordination

Catalyst AEC

160/month

Site Office

3D coordination

Greenco

60/month

Project’s Office

3D coordination

Triple T

60/month

Project’s Office

3D coordination

MPM Group

Min 90/month

Project’s Office

3D coordination

National Fire Solutions

60/month

Project’s Office

Record Modelling

MPM Group

1200 (total)

MPM’s Offices Project’s Office

Record Modelling

Catalyst AEC

4000 (total)

Catalyst’s Offices / Site Office

Phase Planning (4D Modelling)

Catalyst AEC

600 (total)

Catalyst’s Offices / Site Office

The terminology of record modelling is modelling to the level of the LOD 400 model (as required).

TERMINAL 1 DOMESTIC PIER AND INTERNATIONAL DEPARTURES EXPANSION - PERTH AIRPORT BUILDING INFORMATION MODELLING PROJECT EXECUTION PLAN - VERSION 2.0

July 18 2013

SECTION F: BIM PROCESS WORKFLOW

TERMINAL 1 DOMESTIC PIER AND INTERNATIONAL DEPARTURES EXPANSION - PERTH AIRPORT BUILDING INFORMATION MODELLING PROJECT EXECUTION PLAN - VERSION 2.0

St andar di zat i on f orConst r uct i on Owner :WoodsBagot

July 18 2013

SECTION G: COLLABORATION PROCEDURES

1. COLLABORATION STRATEGY The BIM coordination process will be collaborative and managed through regular weekly coordination meetings‐ held on site. All documents/ models will be managed through strict document management, transfer, and record storage protocols. Aconex will be utilised to transmit all BIM related communications – including but not limited to:  meeting records/ minutes  RFI’s  clash detection reports  coordination zone sketches  model revisions‐ federated 2. MEETING PROCEDURES: MEETING TYPE BIM REQUIREMENTS KICK‐OFF

BIM EXECUTION PLAN DEMONSTRATION

DESIGN COORDINATION

PROJECT STAGE

FREQUENCY

PARTICIPANTS

LOCATION

Construction

Once off

ALL

BEPL Site Office

Construction

Once off – PAPL/ APP/ PAPL design consultants. Once off – subcontractors (including select PAPL design consultants)

ALL

BEPL Site Office

Construction

BEPL Site Office

Weekly

KEY FOCUS AREAS BUILDING SERVICES SUBCONTRACTORS/ SELECT PAPL DESIGN CONSULTANTS (AS REQUIRED) BUILDING SERVICES SUBCONTRACTORS/ SELECT PAPL DESIGN CONSULTANTS (AS REQUIRED)

BEPL Site Office

CONSTRUCTION ‐ OVER‐THE‐SHOULDER PROGRESS REVIEWS

Construction

Fortnightly

ANY OTHER BIM MEETINGS THAT OCCURS WITH MULTIPLE PARTIES

Construction

As needs basis

All‐ as required dependent on focus area

BEPL Site Office

3. INTERACTIVE WORKSPACE

All BIM coordination meetings will take place in Built Environs site office – meeting room facilities. Both rooms available have teleconference facilities and AV equipment set up. BIM setup will include:  site based BIM file server  specialist PC’s/ laptops with appropriate hardware  Software licenses for coordination purposes.  Internet access is also a requirement.

TERMINAL 1 DOMESTIC PIER AND INTERNATIONAL DEPARTURES EXPANSION - PERTH AIRPORT BUILDING INFORMATION MODELLING PROJECT EXECUTION PLAN - VERSION 2.0

July 18 2013

The site compound has the advantage of being immediately adjacent to the construction area‐ enabling meeting participants to physically review areas either prior to or after BIM coordination meetings (as construction progresses) SECTION H: QUALITY CONTROL

1. OVERALL STRATEGY FOR QUALITY CONTROL: QUALITY CONTROL WILL BE PERFORMED AS FOLLOWS: A. INITIAL DESIGN MODEL AUDITS WILL BE PERFORMED TO UNDERSTAND MODELS INTEGRITY, STANDARDS, AND LEVEL OF COMPLETENESS. B. PERIODICAL QA/QC SHOULD BE PERFORMED TO ACHIEVE STANDARDS AND BEST PRACTICES MODELLING PER THIS BIM MANUAL. THE SPREADSHEET PROVIDED IN ATTACHMENT F WILL BE USED. C. AUTOMATED AVAILABLE SOFTWARE TOOLS WILL BE USED FOR MODEL INTEGRITY CHECKS AT REGULAR INTERVALS.

2. QUALITY CONTROL CHECKS: THE FOLLOWING CHECKS SHOULD BE PERFORMED TO ASSURE QUALITY ASSURANCE WITHIN THE FEDERATED MODELS: CHECKS

DEFINITION

RESPONSIBLE PARTY

SOFTWARE PROGRAM(S)

FREQUENCY

Detect problems in the model where two building INTERFERENCE CHECK Catalyst AEC components are clashing including soft and hard

Navisworks

As per BIM Coordination Meetings Schedule

STANDARDS CHECK

Ensure that the BIM and AEC CADD Standard have Catalyst AEC been followed

REVIT Navisworks

Prior to each coordination process

VISUAL CHECK

Ensure there are no unintended model Model or Activity owner – REVIT components and design intent has been followed per BIM workflow Navisworks

Daily

MODEL INTEGRITY CHECKS

QC validation process used to ensure that the Project Facility Data set has no undefined, Model or Activity owner incorrectly defined or duplicated elements and the per BIM workflow reporting process on non‐compliant elements and corrective action plans

Prior to each coordination process

REVIT Navisworks

Refer to Appendix G for further outline

TERMINAL 1 DOMESTIC PIER AND INTERNATIONAL DEPARTURES EXPANSION - PERTH AIRPORT BUILDING INFORMATION MODELLING PROJECT EXECUTION PLAN - VERSION 2.0

July 18 2013

SECTION I: TECHNOLOGICAL INFRASTRUCTURE NEEDS

1. SOFTWARE‐ TO BE INTEGRATED DISCIPLINE ARCHITECTURE STRUCTURE

STEEL CONCRETE

SOFTWARE

VERSION

REVIT ARCHITECTURE

2012

TEKLA – EXPORT TO REVIT

2012

REVIT STRUCTURE

2012

MECHANICAL

REVIT MEP

2012

ELECTRICAL

REVIT MEP

2012

HYDRAULIC

REVIT MEP

2012

FIRE PROTECTION AEROBRIDGE BAGGAGE HANDLING ALL

REVIT MEP

2012

AUTOCAD 3D

2012

AUTOCAD 3D

2012

NAVISWORKS MANAGE REVIEW/ACONEX

2012

TERMINAL 1 DOMESTIC PIER AND INTERNATIONAL DEPARTURES EXPANSION - PERTH AIRPORT BUILDING INFORMATION MODELLING PROJECT EXECUTION PLAN - VERSION 2.0

July 18 2013

SECTION J: BIM SPECIFIC PROJECT STANDARDS ‐ CONSTRUCTION

1. PROJECT MODEL BREAKDOWN

Due to anticipated file size and construction programme, the project model will broke into 2 distinct models designated as smaller independent projects as follows:

1. DOMESTIC PIER TERMINAL EXTENSION

TERMINAL 1 DOMESTIC PIER AND INTERNATIONAL DEPARTURES EXPANSION - PERTH AIRPORT BUILDING INFORMATION MODELLING PROJECT EXECUTION PLAN - VERSION 2.0

July 18 2013

2. MODEL ZONING BREAK‐DOWN Due to coordination & documentation purposes, both the Domestic Pier & Terminal Extension Models will be break up into zones designated as Focus Zones 2.1. DOMESTIC PIER ZONING The DOMESTIC PIER Model will be divided by the following Focus zones designation:

DOMESTIC PIER ZONING ZONING

DESCRIPTION

 From 6000mm left of grid W30 to 2000mm right of grid W21  From 4000mm up of grid 1 & 4000mm down of grid 9

ZONE 4

ZONES

ZONE 5

 

From 2000mm left of grid W21 to 2000mm right of grid W11 From 4000mm up of grid 1 & 4000mm down of grid 9

 

From 2000mm left of grid W11 to 9000mm right of grid W1 From 4000mm up of grid 1 & 4000mm down of grid 9

ZONE 6

NODES & FIX LINKS

NODE 1 (143 & 144)

 

NODE 2 (145 & 146)

 

NODE 3 (147)

 

NODE 4 (148 & 149) NODE 5 (150)

From grid W19 to grid W10 From 4000mm down of grid 9 From grid W30 to grid W22 From 4000mm down of grid 9 From 4000 left of W30 From 4000mm down of grid 9 to grid 5

 

From 15000 left of grid W30 to grid W22 From 4000mm up of grid 1

 

From grid W15 to grid W7 From 4000mm up of grid 1

TERMINAL 1 DOMESTIC PIER AND INTERNATIONAL DEPARTURES EXPANSION - PERTH AIRPORT BUILDING INFORMATION MODELLING PROJECT EXECUTION PLAN - VERSION 2.0

July 18 2013

2.2. TERMINAL EXTENSION ZONING The TERMINAL EXTENSION Model will be divided by the following Focus zones designation: (Distances for the Node 6 have been taken from the vertical grid W1 & the Horizontal grid 1 from the Pier)

TERMINAL EXTENSION ZONING ZONING ZONES

DESCRIPTION ZONE 1

 

Parallel to Grid L5 From 2000 down of grid L5 to 73000 up of grid L5

ZONE 2

 

Parallel to Grid L5 From 2000 up of grid L5 to 120000 down of grid L5

ZONE 3

 

Parallel to grid L15 From grid L15 to 95000 down of grid L15

NODE 6 (Node 151)

  

Parallel to grid 1 From 20000 left of grid W1 to 30000 right of grid W1 From 30000 up of grid 1 to 70000 up of grid 1

NODES

TERMINAL 1 DOMESTIC PIER AND INTERNATIONAL DEPARTURES EXPANSION - PERTH AIRPORT BUILDING INFORMATION MODELLING PROJECT EXECUTION PLAN - VERSION 2.0

July 18 2013

3. MODELS NAMING CONVENTION All file names should use UPPER_CASE_LETTERS format and the following naming convention: FILE NAMES FOR MODELS SHOULD BE FORMATTED AS: PROJECT NUMBER

‐

BLDG NUMBER

‐

DOCUMENT FILE TYPE

‐

ORGANIZATION

‐

DISCIPLINE

‐

PROJECT BREAKDOWN

Domestic Pier Model

501B‐300‐RVT‐WBAUS‐ARC‐DP‐CP

ARCHITECTURAL

Terminal Extension Model

501B‐300‐RVT‐WBAUS‐ARC‐TE‐CP

Terminal Existing Model

501B‐300‐RVT‐WBAUS‐ARC‐TEXIST‐CP

Domestic Pier Model

501B‐300‐RVT‐MPM‐MEC‐DP‐CP

Terminal Extension Model

501B‐300‐RVT‐MPM‐MEC‐TE‐CP

Domestic Pier Model

501B‐300‐RVT‐BE‐HYD‐DP‐CP

Terminal Extension Model

501B‐300‐RVT‐BE‐HYD‐TE‐CP

Domestic Pier Model

501B‐300‐RVT‐BE‐ELE‐DP‐CP

Terminal Extension Model

501B‐300‐RVT‐BE‐ELE‐TE‐CP

Domestic Pier Model

501B‐300‐RVT‐BE‐FRP‐DP‐CP

Terminal Extension Model

501B‐300‐RVT‐BE‐FRP‐TE‐CP 501B‐300‐RVT‐RE‐STR‐STL‐DP‐CP & 501B‐300‐RVT‐BE‐STR‐STL‐DP‐CP 501B‐300‐RVT‐RE‐STR‐STL‐TE & 501B‐300‐RVT‐BE‐STR‐STL‐TE‐CP 501B‐300‐RVT‐BE‐STR‐CON‐DP‐CP

MECHANICAL HYDRAULIC ELECTRICAL FIRE PROTECTION

Domestic Pier Model

STRUCTURAL STEEL

STRUCTURAL CONCRETE

Terminal Extension Model Domestic Pier Model Terminal Extension Model ‐

BAGGAGE HANDLING

‐

AEROBRIDGE

‐

PHASE

501B‐300‐RVT‐BE‐STR‐CON‐TE‐CP 501B‐300‐DWG‐BCS‐BH‐TE‐CP 501B‐300‐RVT‐BE‐BH‐TE‐CP

Project and Building Numbers

PROJECT NUMBER 501B

PROJECT NAME T1 Domestic Pier and International Departures Expansion Project

BUILDING NUMBER 300

BUILDING NAME Terminal 1

Document File Type: Software Extension & Format

SOFTWARE EXTENSION

PROGRAM/FORMAT

RVT

REVIT 2012

TEKLA

TEKLA STRUCTURES

NWC

NAVISWORKS CACHE

NWD

NAVISWORKS DOCUMENT

NWF

NAVISWORKS WORKING FILE SET

DWG

AUTOCAD

TERMINAL 1 DOMESTIC PIER AND INTERNATIONAL DEPARTURES EXPANSION - PERTH AIRPORT BUILDING INFORMATION MODELLING PROJECT EXECUTION PLAN - VERSION 2.0

July 18 2013

Discipline & Organisation Codes DISCIPLINE CODE

DISCIPLINE NAME

ROLE

ORGANIZATION

ORGANIZATION CODE

‐

GENERAL CONTRACTOR

BUILT ENVIRONS

‐

BIM FACILITATOR

CATALYST AE

CAT

ARCHITECTURAL

ARC

ARCHITECTS

WOODS BAGOT

WBAUS

MECHANICAL

MEC

MECHANICAL SUBCONTRACTOR

MPM GROUP

MPM

HYDRAULIC

HYD

HYDRAULIC SUBCONTRACTOR

TRIPLE T

ELECTRICAL

ELE

ELECTRICAL SUBCONTRACTOR

GREENCO

FIRE PROTECTION

FRP

FIRE PROTECTION SUBCONTRACTOR NATIONAL FIRE SOLUTIONS

STRUCTURAL STEEL

STR‐STL

STEEL SUBCONTRACTOR

RAPID ALLIANCE

STRUCTURAL CONCRETE

STR‐CON

STRUCTURAL ENGINEER

ARUP

OveARUP

BAGGAGE HANDLING

BAGGAGE HANDLING SUBCONTRACTOR

BCS

Project Breakdown Models PREFIX

PROJECT BREAKDOWN MODEL

DOMESTIC PIER

TERMINAL EXTENSION

Project Phases PREFIX

PROJECT PHASE

DESIGN PHASE

CONSTRUCTION PHASE

AS‐BUILTS CONSTRUCTED PHASE

4. PROJECT LOCATION & ORIENTATION The Project location and orientation is the same as that established during the design phase of the project. All models must be in the correct location in 3D space (x, y and s coordinates) by adopting the origin defined in the Architecture design models by acquiring coordinates of one of these Architectural Design models:  7‐70‐0710_T1Departures_Pier_A12_Export  7‐70 0710_T1Departures_Terminal_A12_Export The correct insertion point is critical an ensures that each model will align properly in the Federated Model 4.1. SITE ADDRESS The address for the project is:

TERMINAL 1 DOMESTIC PIER AND INTERNATIONAL DEPARTURES EXPANSION - PERTH AIRPORT BUILDING INFORMATION MODELLING PROJECT EXECUTION PLAN - VERSION 2.0

July 18 2013

4.2. PROJECT ORIGIN The origin of all CAD/Revit models/drawings should been at an agreed common as follows. Project Base Point has been located at the centroid of the Existing Terminal grid at the following coordinates:  N/S: 264420134.5  E/W: 64976211.6  Angle to True North: 14.011 4.3. PROJECT NORTH The angle from Project North to True North is 14 00’ 39”

5. GRIDS SET OUT All models will need to copy/monitor the grids set by the architectural model DOMESTIC PIER The Departure Pier model Grid Setting Out Point with the True North setting is the following:  278706.628 east from grid W1  130319.118 south from grid 9

TERMINAL EXTENSION The Terminal Extension model Radial Grid Setting Out Point with the Project North setting in relation to the Pier Grid set out is the following:

TERMINAL 1 DOMESTIC PIER AND INTERNATIONAL DEPARTURES EXPANSION - PERTH AIRPORT BUILDING INFORMATION MODELLING PROJECT EXECUTION PLAN - VERSION 2.0

July 18 2013

6. LEVELS MODEL BREACKDOWN

LEVEL NAME

LEVEL ABBREVIATION

RL (MM)

FLOOR TO FLOOR (MM)

PIER LEVEL 0

L00

20000

4604 (to Pier L1)

PIER LEVEL 1

L01

24604

10000 (to Pier L2)

PIER LEVEL 2

L02

34604

Top of Roof/Building

TERMINAL LEVEL 0

L00

20000

2575 (to Terminal L0Mezz)

TERMINAL LEVEL 0 MEZZ

L00MEZZ

22575

2929 (to Terminal L1)

TERMINAL LEVEL 1

L01

25504

5160 (to Terminal L2)

TERMINAL LEVEL 2

L02

30664

5900 (to Terminal L3)

TERMINAL LEVEL 3

L03

36564

Top of Roof/Building

DOMESTIC PIER

TERMINAL EXTENSION

Refer to SECTION I: NAVISWORKS CLASH DETECTION SETTINGS & WORKFLOW

7. MEASUREMENT AND COORDINATE SYSTEMS 1.1. Units: Metric Units. One unit (in the model) equals one millimeter

1.2. Scale: BIM/3D Models shall be created at a scale 1:1 and the. One unit (in the model) equals one millimeter 1.3. Tolerances: Models and Model Elements must be within 3.125mm of theoretical dimensions. Tolerances for specific items and systems will be determined as necessary. Model tolerances are not to be construed as construction tolerances 1.4.

Dimensions and the Standard Unit of Measurement to be Used

DIMENSION

UNIT OF MEASUREMENT

ABBREVIATION

LENGTH

MILIMETERS

AREA

SQUARE METRES

TERMINAL 1 DOMESTIC PIER AND INTERNATIONAL DEPARTURES EXPANSION - PERTH AIRPORT BUILDING INFORMATION MODELLING PROJECT EXECUTION PLAN - VERSION 2.0

July 18 2013 VOLUME

CUBIC METRES

ANGLE

DEGREES

WEIGHT

KILOGRAMS

SLOPE

PERCENT

TERMINAL 1 DOMESTIC PIER AND INTERNATIONAL DEPARTURES EXPANSION - PERTH AIRPORT BUILDING INFORMATION MODELLING PROJECT EXECUTION PLAN - VERSION 2.0

July 18 2013

8. VISUALIZATION REQUIREMENTS

8.1. 2D VIEWS – IN MODEL Navisworks Export Views

All Stakeholders are to provide a plan view of each level with the View Range settings specified in Section I: 2.1. Understanding Levels Coordination volumes These are to be categorized as “Navisworks Export” and be used by the BIM Manager to assist in creating the Federated Model(s)

8.2. 3D VIEWS – IN MODEL Navisworks Export Views Stakeholder’s models are to provide 3D views categorized as “Navisworks Export” for each 2D “Navisworks Export” created per Level and per Focus Zone These views are to be configured to show only the elements that are to be exported to the federated Navisworks model All unnecessary settings that diminish the performance such as sun studies and shadows are to be turned off in this view. Refer to Section M: LOD400 – Construction Model / Required Content by System to determine what should be

exported from each stakeholder’s model Refer to Section I: 1. Discipline Color Coding & 2. Navisworks nwc Export 3D Views to determine what

Navisworks views should be exported from each stakeholder model and then be federated into Navisworks

9. MODEL LEVEL OF DETAIL (LOD) BIM based models are developed throughout the lifecycle of the project, from design, construction and through to the operational lifecycle of a building project. As the information progresses through the lifecycle of the project the requirements on completeness of the data increases. To provide measurable goals and milestones this development of information is defined as level of detail (LOD). Formerly projects progressed through a percentage based system related to the overall requirements of the delivery for construction. Level of detail (LOD) is envisaged to redefine this progress in a way that can be measured for both documentation and information. There are five levels and each level helps defining consistent expectations throughout the building lifecycle from planning through design and construction and ultimately the building life cycle. The following LOD descriptions identify the content requirements and associated authorised uses in the construction Phase 1.1. LOD 400 ‐ Construction Model

This level of development is referred to as the construction stage. Model elements are virtual representations of the proposed element and are modelled as actual assemblies accurate in terms of quantity, size shape, location and orientation with complete fabrication, assembly and detailing information. Models will be geometrically accurate and coordinated and will incorporate all information to allow procurement, fabrication and construction. There will be no discrepancies between information indicated on printed documents and the properties within the model components. Models will be available for the usages as defined in the BEP TERMINAL 1 DOMESTIC PIER AND INTERNATIONAL DEPARTURES EXPANSION - PERTH AIRPORT BUILDING INFORMATION MODELLING PROJECT EXECUTION PLAN - VERSION 2.0

July 18 2013

Models must be 100% complete for the current building, level and phase. This includes, but is not limited to:  All equipment to scale  All model elements are to have identity codes  All valves and clean‐outs outside of the building to have GPS coordinates identified in the model component  Any item which may impact coordination with other disciplines  Equipment to have manufacturer and model attached (if known)  Identify all service and access areas  Model all “no‐fly zones” for: o access o maintenance clearance o elevator shaft o building code and regulation compliance o constructability with solid transparent objects  Penetration through building systems such as cast‐in‐place concrete and CMU walls shall be identified in the Subcontractor’s model by means of a modelled sleeve (w/ defined tolerance)  Piping that is larger than 25mm diameter  Show all sleeved or cored hole penetrations  Show size and thickness of housekeeping pads 1.2. Required Content by System

The level of detail defined in each section below is the minimum level of detail required in the LOD400 model. Greater detail than the minimum should be incorporated in the model whenever possible. 1.2.1.

                

Architectural All exterior walls All interior ceilings, soffits, stairs, and railings will be modelled. All interior walls, including non‐rated walls separating rooms, will be modelled. Studs and individual layers of drywall will not be modelled Architectural fixtures and fittings ‐ will be modelled to account for general size, location, geometry & orientation Colour Door and window hardware will not be modelled Doors, window leaves, and frames will be modelled. Exterior doors, Exterior windows Facades suites Final finish, texture, and material will be approved in the Field Interior doors and windows will be modelled to the extent that the walls that they are associated with are included in the model Massing Roof components, including gutters, downpipes and capping Signage will be modelled to account for general size, location, geometry & orientation Stairs and landings Walls, ceilings, and soffits will be modelled as the overall thickness including elevation changes and termination points. Overall thickness to be determined by their actual total composite assemblies

TERMINAL 1 DOMESTIC PIER AND INTERNATIONAL DEPARTURES EXPANSION - PERTH AIRPORT BUILDING INFORMATION MODELLING PROJECT EXECUTION PLAN - VERSION 2.0

July 18 2013

1.2.2. Structural 1.2.2.1. Steel Structure (by RAPID ALLIANCE)  All primary and secondary structural steel members will be modelled, including: o standard steel member sizes o gusset plates o braces o kickers and equipment supports.  Angles  Beams  Bolts, clip angles, etc. will not be modelled  Bracing  Columns  Gusset plates  Knife plates  Metal decks will be modelled as the overall thickness of the slab; ribs in metal decks, where hidden, will not be modelled.  Miscellaneous metals such as elevator hoist beams, rails and intermediate rail support steel for the elevator will be modelled  Other elements necessary for the successful coordination of other building trades  Reinforcing steel and imbeds will not be modelled 1.2.2.2. Concrete Structure – will not be modelled in addition to current models  All cast‐in‐place concrete, including all penetrations and openings identified in the construction documents.  Chamfers at corners will not be modelled.  Edges of all slabs and penetrations of structural systems will be accurately located in the model

1.2.3. HVAC         

Concrete Equipment pads, inertia pads and Access Doors Drip Pans, supports, and hydraulic POC (if required) External insulation on piping and ductwork must be modelled to scale‐ internal insulated duct is to be noted Identify duct balance dampers and model service access requirements as solid objects Key access requirements within ceilings, voids, risers and all plant withdrawal space required for maintenance Model all ductwork to be shown as actual duct size, in the correct location in 3D space Model all fire and smoke dampers and indicate service access requirement (i.e. access panel) if not readily accessible Model all grilles, registers, louvers and diffusers Model all Mechanical Equipment:  AHUs  All Valves & control valves  Built‐Up AHUs  Controls  Equipment access zones will be modelled as solids  Fans  heat exchangers  High & low point drains  Pumps  Tanks  Valves TERMINAL 1 DOMESTIC PIER AND INTERNATIONAL DEPARTURES EXPANSION - PERTH AIRPORT BUILDING INFORMATION MODELLING PROJECT EXECUTION PLAN - VERSION 2.0

July 18 2013

  

Model coil pull areas Model duct hangers, supports and seismic bracing Model the zone of influence for all hangers and deck inserts

1.2.4. Electrical       

            

Equipment pads, inertia pads, and Access Doors Trenches for underground conduits? Model all audio speakers and equipment Model all cable trays and/or J‐hook locations Model all conduits 25mm and larger Model all Controls Equipment:  cable tray  Controls Model all Electrical Equipment:  Access Doors  ATS’s  AV Equipment  CCTV  data racks  Exit Signs  Generators  Recessed Electrical devices  starters  switch/paralleling gear  Transformers  VFDs Model all Fire Alarm devices Model all grouped conduit raceways (2) or more Model all junction boxes 100mmx100mm and larger Model all light fixtures (including neon) and switching devices & motion detectors Model all panels Model all security devices (cameras, card readers, motion sensors, auto door locks, etc.) Model door security junction boxes and automatic door openers Model hangers, supports and seismic bracing Model phone/data ports Model racks carrying more than 2 conduits 1” and smaller Model the zone of influence for all hangers and deck inserts Necessary “No‐Fly” zone Thermostats and boxes

1.2.5. Hydraulic      

Access doors and Accessibility requirements for code and maintenance purposes Concrete Equipment pads, inertia pads and Access Doors Drip Pan hydraulics External insulation on piping must be modelled to scale. Model all drip legs, drain pipes, blow down valves, and cleanouts Model all Hydraulic Equipment:  Chilled Water  Domestic Water  in wall carriers  In wall hydraulic equipment  Pumps  Steam  Storm/Roof Leaders TERMINAL 1 DOMESTIC PIER AND INTERNATIONAL DEPARTURES EXPANSION - PERTH AIRPORT BUILDING INFORMATION MODELLING PROJECT EXECUTION PLAN - VERSION 2.0

July 18 2013

    

 Tanks  water heaters Model all piping including insulated piping with insulation Model all underground piping. Model all valves, gauges, and control valves and service access Model pipe hangers, supports and seismic bracing Model the zone of influence for all hangers and deck inserts

1.2.6. Fire Protection     

   

Access doors and Accessibility requirements for code and maintenance purposes. Access Doors Fire Sprinkler main lines, branch lines, sprinklers and risers will be modelled Model “No‐fly zones” above control panels shall be modelled as solids Model all Fire Protection Equipment:  Drain valves  Dry System  Fire Department Valves  Fire Pump  Hangers & Seismic Bracing  Main Fire Protection Systems  Pre‐action System  Valve Assemblies Model all fittings, drains and test connections. Model all sprinkler head locations and sprinkler head types Model any tanks not included in the architectural or structural Models Model the zone of influence for all hangers and deck inserts

1.2.7. Vertical Transportation  

Not in the BIM scope of work Clear shaft space requirements are included in the architectural scope

1.2.8. Civil/Site 

Not in the BIM scope of work

TERMINAL 1 DOMESTIC PIER AND INTERNATIONAL DEPARTURES EXPANSION - PERTH AIRPORT BUILDING INFORMATION MODELLING PROJECT EXECUTION PLAN - VERSION 2.0

July 18 2013

SECTION K: MULTI‐DISCIPLINE COORDINATION PROCESS The collaborative process for this project has been developed to ensure BIM is achieved to the highest level; this to ensure that all parties has access to up‐to‐date information 1. SPATIAL COORDINATION – CONSTRUCTION PHASE 3D Computer coordination as it relates to Mechanical, Electrical, Hydraulic, Fire Protection, Fire Alarm and Special Systems, etc. during the construction modeling phase:

The subcontractor (or Catalyst on the behalf of the Electrical, Fire and Hydraulics subcontractor) will deliver a 3D computer model that is complete. Any elements not included/ modelled would not be available to clash detect against and therefore will become the Subcontractor’s responsibility to coordinate in the field  The Model shall be developed in a software package compatible with NavisWorks Manage 2012  The Subcontractor(s) shall provide Catalyst AEC (BIM Facilitator) with a 3D computer model in a format compatible with Revit 2012 and in NavisWorks Document Format (.NWD) *The Steel structural TEKLA model will directly export the TEKLA file to a Revit file using the “Export to Revit” application inside TEKLA software so as to be used by all subcontractors during the coordination process  Exchange of 2D CAD files shall be in the AutoCAD 2011 file format  The Subcontractor(s) shall provide a list of minimum typical clearances for all model components 2. COORDINATION PROCEDURE  Design Consultants shall provide initial coordinated 3D models  PAPL design consultants shall provide initial coordinated 3D models.  The Mechanical & Steel Structure Subcontractor will deliver a 3D model in Revit 2012 that is complete and complies with this BEP  The Electrical, Hydraulic & Fire Protection Subcontractors shall provide Catalyst AEC with the following information to Catalyst in pursuit of 3D design models upgrade to the Construction Models LOD400:  Sketches on Construction documents with changes  Specifications of all Elements including but not limited to:  Equipment cut‐sheets  Fixtures & devices cut‐sheets  Materials  Insulation type and thickness when applicable  Fitting specs when applicable (types, nominal diameters),  Access doors & accessibility requirements  Hangers, supports with their zone of influence  All Construction Models shall be complete for the coordination process during the construction phase and shall comply with this BEP  Each trade is required to download and use these files to coordinate their systems modelled in a weekly basis  The 3D coordination program will be divided in Key Focus Zones for both the Departure Pier and Terminal Extension projects and will follow a sequence priority provided by Built Environs  Subcontractors shall be prepared to accommodate Coordination Meetings sessions to resolve model conflicts within the Project Schedule and sign off on a 3D Model to be considered the basis for construction on an Focus Zones and floor by floor basis consistent with the Project Schedule  Catalyst AEC will provide clash detection reports for each Focus Zone to accommodate the above Refer to Clash Reports

TERMINAL 1 DOMESTIC PIER AND INTERNATIONAL DEPARTURES EXPANSION - PERTH AIRPORT BUILDING INFORMATION MODELLING PROJECT EXECUTION PLAN - VERSION 2.0

July 18 2013



Each Trade is required to review the clash detection reports generated by the Catalyst AEC (BIM Facilitator) as issued via Aconex before the Coordination Meeting session. All parties are to arrive at the meeting prepared to address the unresolved clashes in a constructive manner  Following 100% coordination and agreement on the Construction Model LOD400, the subcontractor agrees and will sign off to be responsible for locating their respective components within an agreed tolerance based on the Construction Model  Any variation beyond the agreed tolerance must be coordinated/ agreed with Built Environs first.  Items not included in the coordination model will be installed after all coordinated elements are in place.  Components that are installed in conflict with model layout and create obstacles or additional work for other disciplines shall require the following: o removal and reinstallation per model 3. 3D MODELS DELIVERABLE REQUIREMENTS  The Coordination model shall include, at a minimum: The modelling elements per modelling requirements specified by this document and the LOD  All objects must be modelled as 3D solids, not wires frames or lines  All 2D reference as well as non‐essential information should be deleted, only 3D information should remain in the file. This includes, but is not limited to the following: o Text o Leaders o Symbols o Architectural References o Unnecessary views Refer to Attachment B: Revit General Best Practices  After getting rid of unnecessary information, Model are to be purged before uploading to Aconex  All Stakeholder Models need to comply with the Files Maintenance Checklist available in Attachment D  All Stakeholder Models are to have a pre‐determined Starting view with the minimum following information: o Project Name o Service or discipline o Model Breakdown: Pier or Terminal o Model Name o Version Number: Version number need to match the Aconex Version created when uploading so as to keep track and make sure all stakeholders are using the proper version 4. COLLABORATION PROCESS WORKFLOW

4.1. Basic Workflow for the Coordination Process WEEKLY BASIS  By COB Friday (weekly) o Each Stakeholder will upload a Progress 3D Model in their native format (Revit, Autocad 3D, Tekla) to Aconex following the proper Documents Register Procedure. o Each Stakeholder Model need to comply with Section K: Item 3, 3D Models Deliverable Requirements o Each Stakeholder will upload a Navisworks NWC for the Focus Zone/s in review Refer to Section I: Naviswoks .NWC Export 3D Views & Attachement E: Navisworks Export Settings TERMINAL 1 DOMESTIC PIER AND INTERNATIONAL DEPARTURES EXPANSION - PERTH AIRPORT BUILDING INFORMATION MODELLING PROJECT EXECUTION PLAN - VERSION 2.0

July 18 2013



By COB Monday (weekly) o Catalyst AEC’s BIM Facilitator shall audit the models for minimum adherence to the BIM requirements of the project to ‐ Attachment A: General Revit Modelling Best Practices & Attachment F: Files Maintenance Checklist o Catalyst AEC’s BIM Facilitator shall notify if there is any Stakeholder model that needs to addressed comments and be re‐uploaded to comply with the BEP standards o All Stakeholders 3D Revit Models are available to download and be used as reference by other Stakeholders



By COB Monday (Weekly) o AEC’s BIM Facilitator will Federate all Stakeholder’s .NWC models of the Focus Zone to be coordinated o AEC’s BIM Facilitator will run clash detection batches for the focus zone in concerned o Built Environs will initially assigned Clashes to the Stakeholder party that need to proceed with the change to address the clash Tuesday (Weekly) o Built Environs to review clashes before BIM Coordination Meeting and start assigning Wednesday BIM Coordination Meeting (Weekly) o A Services Coordination meeting will occur to cover all issues discovered through the Clash detection process o All BIM representatives to attend o This is repeated for each Focus Zone, throughout the project as needed.

4.2. Document Issuing Protocols All drawings/models, documents, meeting minutes etc. are to be uploaded to Aconex for all project participants TERMINAL 1 DOMESTIC PIER AND INTERNATIONAL DEPARTURES EXPANSION - PERTH AIRPORT BUILDING INFORMATION MODELLING PROJECT EXECUTION PLAN - VERSION 2.0

July 18 2013

SECTION I: NAVISWORKS CLASH DETECTION SETTINGS & WORKFLOW 1.

DISCIPLINE

DISCIPLINE COLOR CODING For identification & Coordination purposes Stakeholders shall export trades with default colors shown in chart below: COLOR

ARCHITECTURAL

LIGHT GREY

STRUCTURAL STEEL & CONCRETE

DARK GREY

MECHANICAL

BLUE

HYDRAULIC

CYAN

FIRE

RED

ELECTRICAL(DATA/ COMMS & LIGHTING)

GREEN

BAGGAGE HANDLING SYSTEM

YELLOW

NAVISWORKS FEDERATED MODELS Due to the size & complexity of the project a series of federated models will be created in Navisworks. These models will be used for visualization and construction coordination. Refer to Attachement F: Navisworks Federated Models Design NAVISWORKS NWC EXPORT 3D VIEWS Stakeholders shall provide a navisworks NWC file for: o Each Model Breakdown: Domestic Pier & Terminal Extension o Each level: Refer to item 2.1. below o Each Focus Zone: Refer to Section J: Model Zoning Breakdown for Domestic Pier & Terminal Extension for Focus Zones delimitation Refer to Section J: Visualization Requirements for Navisworks 2D & 3D Export views procedure 2.1. Understanding Levels Coordination volumes PIER & TERMINAL Levels o Underground Level [UG] has been added to coordinate underground services. View range of “Navisworks Export” view setting should be as follows:  Associated to Pier Level 0 & Terminal Level 0  Top view range set to the Associated Level 0  Bottom view range set to ‐5000 of the associated Level 0 o Nodes will have 1 volume with ALL Levels to coordinate View range of “Navisworks Export” view setting should be as follows:  Associated to Level 0  Bottom view range set to ‐5000 of associated Level 0  Top view range set to the Level 2

TERMINAL 1 DOMESTIC PIER AND INTERNATIONAL DEPARTURES EXPANSION - PERTH AIRPORT BUILDING INFORMATION MODELLING PROJECT EXECUTION PLAN - VERSION 2.0

July 18 2013

PIER LEVELS

View range of “Navisworks Export” view setting for the Pier should be as follows: o Pier Level 00  Associated to Level 0  Bottom view range set to ‐725 of the associated Level 0  Top view range set to the level above o Pier Level 01  Bottom view range set to the associated level  Top view range set to +4000 of the associated Level 01 o Pier Level 02  Associated to Level 2  Bottom view range set to ‐6000 of the associated Level 2  Top view range set to +5000 of the associated Level 2 TERMINAL LEVELS

View range of “Navisworks Export” view setting should be as follows: o Terminal Level 00  Associated to Level 0  Bottom view range set to the associated Level 0  Top view range and cut plane set to the level 1 o Terminal Level 01  Associated to Level 1  Bottom view range set to the associated level  Top view range and cut plane set to the Level above o Terminal Level 02  Associated to Level 2  Bottom view range set to the associated Level 2  Top view range and cut plane set to +5000 of the Level above 3

TERMINAL 1 DOMESTIC PIER AND INTERNATIONAL DEPARTURES EXPANSION - PERTH AIRPORT BUILDING INFORMATION MODELLING PROJECT EXECUTION PLAN - VERSION 2.0

July 18 2013

2.2. Navisworks Export 3D views & .NWC File Naming Protocol [PROJECT]‐[PROJECT #]‐[FORMAT]‐[ORG CODE]‐[DISCIPLINE]‐[MODEL BREAKDOWN]‐[LEVEL ABB]‐ZONE‐[ZONE#] Charts Below shows “Navisworks Export” View & File names for each Stakeholder Model

ARCHITECTURAL MODEL BREAKDOWN

LEVELS

UNDERGROUND

Level 0

Level 1 DOMESTIC PIER

Level 2

ALL

UNDERGROUND

Level 0 TERMINAL EXPANSION Level 1

ZONES & NODES

NAVISWORKS NWC

ZONE 4

501B‐300‐NWC‐WBAUS‐ARC‐DP‐UG‐ZONE‐4

ZONE 5

501B‐300‐NWC‐WBAUS‐ARC‐DP‐UG‐ZONE‐5

ZONE 6

501B‐300‐NWC‐WBAUS‐ARC‐DP‐UG‐ZONE‐6

ZONE 4

501B‐300‐NWC‐WBAUS‐ARC‐DP‐L00‐ZONE‐4

ZONE 5

501B‐300‐NWC‐WBAUS‐ARC‐DP‐L00‐ZONE‐5

ZONE 6

501B‐300‐NWC‐WBAUS‐ARC‐DP‐L00‐ZONE‐6

ZONE 4

501B‐300‐NWC‐WBAUS‐ARC‐DP‐L01‐ZONE‐4

ZONE 5

501B‐300‐NWC‐WBAUS‐ARC‐DP‐L01‐ZONE‐5

ZONE 6

501B‐300‐NWC‐WBAUS‐ARC‐DP‐L01‐ZONE‐6

ZONE 4

501B‐300‐NWC‐WBAUS‐ARC‐DP‐L02‐ZONE‐4

ZONE 5

501B‐300‐NWC‐WBAUS‐ARC‐DP‐L02‐ZONE‐5

ZONE 6

501B‐300‐NWC‐WBAUS‐ARC‐DP‐L02‐ZONE‐6

NODE 1

501B‐300‐NWC‐WBAUS‐ARC‐DP‐ALL‐NODE‐1

NODE 2

501B‐300‐NWC‐WBAUS‐ARC‐DP‐ALL‐NODE‐2

NODE 3

501B‐300‐NWC‐WBAUS‐ARC‐DP‐ALL‐NODE‐3

NODE 4

501B‐300‐NWC‐WBAUS‐ARC‐DP‐ALL‐NODE‐4

NODE 5

501B‐300‐NWC‐WBAUS‐ARC‐DP‐ALL‐NODE‐5

ZONE 1

501B‐300‐NWC‐WBAUS‐ARC‐TE‐UG‐ZONE‐1

ZONE 2

501B‐300‐NWC‐WBAUS‐ARC‐TE‐UG‐ZONE‐2

ZONE 3

501B‐300‐NWC‐WBAUS‐ARC‐TE‐UG‐ZONE‐3

ZONE 1

501B‐300‐NWC‐WBAUS‐ARC‐TE‐L00‐ZONE‐1

ZONE 2

501B‐300‐NWC‐WBAUS‐ARC‐TE‐L00‐ZONE‐2

ZONE 3

501B‐300‐NWC‐WBAUS‐ARC‐TE‐L00‐ZONE‐3

ZONE 1

501B‐300‐NWC‐WBAUS‐ARC‐TE‐L01‐ZONE‐1

ZONE 2

501B‐300‐NWC‐WBAUS‐ARC‐TE‐L01‐ZONE‐2

ZONE 3

501B‐300‐NWC‐WBAUS‐ARC‐TE‐L01‐ZONE‐3

ZONE 1

501B‐300‐NWC‐WBAUS‐ARC‐TE‐L01‐ZONE‐1

Level 2

ZONE 2

501B‐300‐NWC‐WBAUS‐ARC‐TE‐L01‐ZONE‐2

ZONE 3

501B‐300‐NWC‐WBAUS‐ARC‐TE‐L01‐ZONE‐3

ALL

NODE 6

501B‐300‐NWC‐WBAUS‐ARC‐TE‐ALL‐NODE‐6

TERMINAL 1 DOMESTIC PIER AND INTERNATIONAL DEPARTURES EXPANSION - PERTH AIRPORT BUILDING INFORMATION MODELLING PROJECT EXECUTION PLAN - VERSION 2.0

July 18 2013

STRUCTURAL CONCRETE MODEL BREAKDOWN

LEVELS

UNDERGROUND

Level 0

Level 1 DOMESTIC PIER

Level 2

ALL

UNDERGROUND

Level 0 TERMINAL EXPANSION Level 1

Level 2 ALL

ZONES & NODES

NAVISWORKS NWC

ZONE 4

501B‐300‐NWC‐BE‐STR‐CON‐DP‐UG‐ZONE‐4

ZONE 5

501B‐300‐NWC‐BE‐STR‐CON‐DP‐UG‐ZONE‐5

ZONE 6

501B‐300‐NWC‐BE‐STR‐CON‐DP‐UG‐ZONE‐6

ZONE 4

501B‐300‐NWC‐BE‐STR‐CON‐DP‐L00‐ZONE‐4

ZONE 5

501B‐300‐NWC‐BE‐STR‐CON‐DP‐L00‐ZONE‐5

ZONE 6

501B‐300‐NWC‐BE‐STR‐CON‐DP‐L00‐ZONE‐6

ZONE 4

501B‐300‐NWC‐BE‐STR‐CON‐DP‐L01‐ZONE‐4

ZONE 5

501B‐300‐NWC‐BE‐STR‐CON‐DP‐L01‐ZONE‐5

ZONE 6

501B‐300‐NWC‐BE‐STR‐CON‐DP‐L01‐ZONE‐6

ZONE 4

501B‐300‐NWC‐BE‐STR‐CON‐DP‐L02‐ZONE‐4

ZONE 5

501B‐300‐NWC‐BE‐STR‐CON‐DP‐L02‐ZONE‐5

ZONE 6

501B‐300‐NWC‐BE‐STR‐CON‐DP‐L02‐ZONE‐6

NODE 1

501B‐300‐NWC‐BE‐STR‐CON‐DP‐ALL‐NODE‐1

NODE 2

501B‐300‐NWC‐BE‐STR‐CON‐DP‐ALL‐NODE‐2

NODE 3

501B‐300‐NWC‐BE‐STR‐CON‐DP‐ALL‐NODE‐3

NODE 4

501B‐300‐NWC‐BE‐STR‐CON‐DP‐ALL‐NODE‐4

NODE 5

501B‐300‐NWC‐BE‐STR‐CON‐DP‐ALL‐NODE‐5

ZONE 1

501B‐300‐NWC‐BE‐STR‐CON‐TE‐UG‐ZONE‐1

ZONE 2

501B‐300‐NWC‐BE‐STR‐CON‐TE‐UG‐ZONE‐2

ZONE 3

501B‐300‐NWC‐BE‐STR‐CON‐TE‐UG‐ZONE‐3

ZONE 1

501B‐300‐NWC‐BE‐STR‐CON‐TE‐L00‐ZONE‐1

ZONE 2

501B‐300‐NWC‐BE‐STR‐CON‐TE‐L00‐ZONE‐2

ZONE 3

501B‐300‐NWC‐BE‐STR‐CON‐TE‐L00‐ZONE‐3

ZONE 1

501B‐300‐NWC‐BE‐STR‐CON‐TE‐L01‐ZONE‐1

ZONE 2

501B‐300‐NWC‐BE‐STR‐CON‐TE‐L01‐ZONE‐2

ZONE 3

501B‐300‐NWC‐BE‐STR‐CON‐TE‐L01‐ZONE‐3

ZONE 1

501B‐300‐NWC‐BE‐STR‐CON‐TE‐L01‐ZONE‐1

ZONE 2

501B‐300‐NWC‐BE‐STR‐CON‐TE‐L01‐ZONE‐2

ZONE 3

501B‐300‐NWC‐BE‐STR‐CON‐TE‐L01‐ZONE‐3

NODE 6

501B‐300‐NWC‐BE‐STR‐CON‐TE‐ALL‐NODE‐6

TERMINAL 1 DOMESTIC PIER AND INTERNATIONAL DEPARTURES EXPANSION - PERTH AIRPORT BUILDING INFORMATION MODELLING PROJECT EXECUTION PLAN - VERSION 2.0

July 18 2013

STRUCTURAL STEEL MODEL BREAKDOWN

LEVELS

UNDERGROUND

Level 0

Level 1 DOMESTIC PIER

Level 2

ALL

UNDERGROUND

Level 0 TERMINAL EXPANSION Level 1

Level 2 ALL

ZONES & NODES

NAVISWORKS NWC

ZONE 4

501B‐300‐NWC‐RA‐STR‐STL‐DP‐UG‐ZONE‐4

ZONE 5

501B‐300‐NWC‐RA‐STR‐STL‐DP‐UG‐ZONE‐5

ZONE 6

501B‐300‐NWC‐RA‐STR‐STL‐DP‐UG‐ZONE‐6

ZONE 4

501B‐300‐NWC‐RA‐STR‐STL‐DP‐L00‐ZONE‐4

ZONE 5

501B‐300‐NWC‐RA‐STR‐STL‐DP‐L00‐ZONE‐5

ZONE 6

501B‐300‐NWC‐RA‐STR‐STL‐DP‐L00‐ZONE‐6

ZONE 4

501B‐300‐NWC‐RA‐STR‐STL‐DP‐L01‐ZONE‐4

ZONE 5

501B‐300‐NWC‐RA‐STR‐STL‐DP‐L01‐ZONE‐5

ZONE 6

501B‐300‐NWC‐RA‐STR‐STL‐DP‐L01‐ZONE‐6

ZONE 4

501B‐300‐NWC‐RA‐STR‐STL‐DP‐L02‐ZONE‐4

ZONE 5

501B‐300‐NWC‐RA‐STR‐STL‐DP‐L02‐ZONE‐5

ZONE 6

501B‐300‐NWC‐RA‐STR‐STL‐DP‐L02‐ZONE‐6

NODE 1

501B‐300‐NWC‐RA‐STR‐STL‐DP‐ALL‐NODE‐1

NODE 2

501B‐300‐NWC‐RA‐STR‐STL‐DP‐ALL‐NODE‐2

NODE 3

501B‐300‐NWC‐RA‐STR‐STL‐DP‐ALL‐NODE‐3

NODE 4

501B‐300‐NWC‐RA‐STR‐STL‐DP‐ALL‐NODE‐4

NODE 5

501B‐300‐NWC‐RA‐STR‐STL‐DP‐ALL‐NODE‐5

ZONE 1

501B‐300‐NWC‐RA‐STR‐STL‐TE‐UG‐ZONE‐1

ZONE 2

501B‐300‐NWC‐RA‐STR‐STL‐TE‐UG‐ZONE‐2

ZONE 3

501B‐300‐NWC‐RA‐STR‐STL‐TE‐UG‐ZONE‐3

ZONE 1

501B‐300‐NWC‐RA‐STR‐STL‐TE‐L00‐ZONE‐1

ZONE 2

501B‐300‐NWC‐RA‐STR‐STL‐TE‐L00‐ZONE‐2

ZONE 3

501B‐300‐NWC‐RA‐STR‐STL‐TE‐L00‐ZONE‐3

ZONE 1

501B‐300‐NWC‐RA‐STR‐STL‐TE‐L01‐ZONE‐1

ZONE 2

501B‐300‐NWC‐RA‐STR‐STL‐TE‐L01‐ZONE‐2

ZONE 3

501B‐300‐NWC‐RA‐STR‐STL‐TE‐L01‐ZONE‐3

ZONE 1

501B‐300‐NWC‐RA‐STR‐STL‐TE‐L01‐ZONE‐1

ZONE 2

501B‐300‐NWC‐RA‐STR‐STL‐TE‐L01‐ZONE‐2

ZONE 3

501B‐300‐NWC‐RA‐STR‐STL‐TE‐L01‐ZONE‐3

NODE 6

501B‐300‐NWC‐RA‐STR‐STL‐TE‐ALL‐NODE‐6

TERMINAL 1 DOMESTIC PIER AND INTERNATIONAL DEPARTURES EXPANSION - PERTH AIRPORT BUILDING INFORMATION MODELLING PROJECT EXECUTION PLAN - VERSION 2.0

July 18 2013

MECHANICAL MODEL BREAKDOWN

ZONES & NODES

LEVELS

UNDERGROUND

Level 0

Level 1 DOMESTIC PIER

Level 2

ALL

UNDERGROUND

Level 0 TERMINAL EXPANSION Level 1

Level 2 ALL

NAVISWORKS NWC

ZONE 4

501B‐300‐NWC‐MPM‐MEC‐DP‐UG‐ZONE‐4

ZONE 5

501B‐300‐NWC‐MPM‐MEC‐DP‐UG‐ZONE‐5

ZONE 6

501B‐300‐NWC‐MPM‐MEC‐DP‐UG‐ZONE‐6

ZONE 4

501B‐300‐NWC‐MPM‐MEC‐DP‐L00‐ZONE‐4

ZONE 5

501B‐300‐NWC‐MPM‐MEC‐DP‐L00‐ZONE‐5

ZONE 6

501B‐300‐NWC‐MPM‐MEC‐DP‐L00‐ZONE‐6

ZONE 4

501B‐300‐NWC‐MPM‐MEC‐DP‐L01‐ZONE‐4

ZONE 5

501B‐300‐NWC‐MPM‐MEC‐DP‐L01‐ZONE‐5

ZONE 6

501B‐300‐NWC‐MPM‐MEC‐DP‐L01‐ZONE‐6

ZONE 4

501B‐300‐NWC‐MPM‐MEC‐DP‐L02‐ZONE‐4

ZONE 5

501B‐300‐NWC‐MPM‐MEC‐DP‐L02‐ZONE‐5

ZONE 6

501B‐300‐NWC‐MPM‐MEC‐DP‐L02‐ZONE‐6

NODE 1

501B‐300‐NWC‐MPM‐MEC‐DP‐ALL‐NODE‐1

NODE 2

501B‐300‐NWC‐MPM‐MEC‐DP‐ALL‐NODE‐2

NODE 3

501B‐300‐NWC‐MPM‐MEC‐DP‐ALL‐NODE‐3

NODE 4

501B‐300‐NWC‐MPM‐MEC‐DP‐ALL‐NODE‐4

NODE 5

501B‐300‐NWC‐MPM‐MEC‐DP‐ALL‐NODE‐5

ZONE 1

501B‐300‐NWC‐MPM‐MEC‐TE‐UG‐ZONE‐1

ZONE 2

501B‐300‐NWC‐MPM‐MEC‐TE‐UG‐ZONE‐2

ZONE 3

501B‐300‐NWC‐MPM‐MEC‐TE‐UG‐ZONE‐3

ZONE 1

501B‐300‐NWC‐MPM‐MEC‐TE‐L00‐ZONE‐1

ZONE 2

501B‐300‐NWC‐MPM‐MEC‐TE‐L00‐ZONE‐2

ZONE 3

501B‐300‐NWC‐MPM‐MEC‐TE‐L00‐ZONE‐3

ZONE 1

501B‐300‐NWC‐MPM‐MEC‐TE‐L01‐ZONE‐1

ZONE 2

501B‐300‐NWC‐MPM‐MEC‐TE‐L01‐ZONE‐2

ZONE 3

501B‐300‐NWC‐MPM‐MEC‐TE‐L01‐ZONE‐3

ZONE 1

501B‐300‐NWC‐MPM‐MEC‐TE‐L01‐ZONE‐1

ZONE 2

501B‐300‐NWC‐MPM‐MEC‐TE‐L01‐ZONE‐2

ZONE 3

501B‐300‐NWC‐MPM‐MEC‐TE‐L01‐ZONE‐3

NODE 6

501B‐300‐NWC‐MPM‐MEC‐TE‐ALL‐NODE‐6

BAGGAGE HANDLING MODEL BREAKDOWN

TERMINAL EXPANSION

LEVELS

Level 0

ZONE

NAVISWORKS NWC

ZONE 1

501B‐300‐NWC‐BCS‐BH‐TE‐L00‐ZONE‐1

ZONE 2

501B‐300‐NWC‐BCS‐BH‐TE‐L00‐ZONE‐2

ZONE 3

501B‐300‐NWC‐BCS‐BH‐TE‐L00‐ZONE‐3

TERMINAL 1 DOMESTIC PIER AND INTERNATIONAL DEPARTURES EXPANSION - PERTH AIRPORT BUILDING INFORMATION MODELLING PROJECT EXECUTION PLAN - VERSION 2.0

July 18 2013

Chart below shows Navisworks Export file names for Electrical as Sample to follow by Hydraulics & Fire Protection as well Only required change is to update the discipline abbreviation FRP for fire & HYD for hydraulics:

ELECTRICAL, FIRE PROTECTION & HYDRAULICS MODEL BREAKDOWN

LEVELS

UNDERGROUND

Level 0

Level 1 DOMESTIC PIER

Level 2

ALL

UNDERGROUND

Level 0 TERMINAL EXPANSION Level 1

Level 2 ALL

ZONES & NODES

NAVISWORKS NWC

ZONE 4

501B‐300‐NWC‐BE‐ELE‐DP‐UG‐ZONE‐4

ZONE 5

501B‐300‐NWC‐BE‐ELE‐DP‐UG‐ZONE‐5

ZONE 6

501B‐300‐NWC‐BE‐ELE‐DP‐UG‐ZONE‐6

ZONE 4

501B‐300‐NWC‐BE‐ELE‐DP‐L00‐ZONE‐4

ZONE 5

501B‐300‐NWC‐BE‐ELE‐DP‐L00‐ZONE‐5

ZONE 6

501B‐300‐NWC‐BE‐ELE‐DP‐L00‐ZONE‐6

ZONE 4

501B‐300‐NWC‐BE‐ELE‐DP‐L01‐ZONE‐4

ZONE 5

501B‐300‐NWC‐BE‐ELE‐DP‐L01‐ZONE‐5

ZONE 6

501B‐300‐NWC‐BE‐ELE‐DP‐L01‐ZONE‐6

ZONE 4

501B‐300‐NWC‐BE‐ELE‐DP‐L02‐ZONE‐4

ZONE 5

501B‐300‐NWC‐BE‐ELE‐DP‐L02‐ZONE‐5

ZONE 6

501B‐300‐NWC‐BE‐ELE‐DP‐L02‐ZONE‐6

NODE 1

501B‐300‐NWC‐BE‐ELE‐DP‐ALL‐NODE‐1

NODE 2

501B‐300‐NWC‐BE‐ELE‐DP‐ALL‐NODE‐2

NODE 3

501B‐300‐NWC‐BE‐ELE‐DP‐ALL‐NODE‐3

NODE 4

501B‐300‐NWC‐BE‐ELE‐DP‐ALL‐NODE‐4

NODE 5

501B‐300‐NWC‐BE‐ELE‐DP‐ALL‐NODE‐5

ZONE 1

501B‐300‐NWC‐BE‐ELE‐TE‐UG‐ZONE‐1

ZONE 2

501B‐300‐NWC‐BE‐ELE‐TE‐UG‐ZONE‐2

ZONE 3

501B‐300‐NWC‐BE‐ELE‐TE‐UG‐ZONE‐3

ZONE 1

501B‐300‐NWC‐BE‐ELE‐TE‐L00‐ZONE‐1

ZONE 2

501B‐300‐NWC‐BE‐ELE‐TE‐L00‐ZONE‐2

ZONE 3

501B‐300‐NWC‐BE‐ELE‐TE‐L00‐ZONE‐3

ZONE 1

501B‐300‐NWC‐BE‐ELE‐TE‐L01‐ZONE‐1

ZONE 2

501B‐300‐NWC‐BE‐ELE‐TE‐L01‐ZONE‐2

ZONE 3

501B‐300‐NWC‐BE‐ELE‐TE‐L01‐ZONE‐3

ZONE 1

501B‐300‐NWC‐BE‐ELE‐TE‐L01‐ZONE‐1

ZONE 2

501B‐300‐NWC‐BE‐ELE‐TE‐L01‐ZONE‐2

ZONE 3

501B‐300‐NWC‐BE‐ELE‐TE‐L01‐ZONE‐3

NODE 6

501B‐300‐NWC‐BE‐ELE‐TE‐ALL‐NODE‐6

CLASH REPORTS In addition to clash detection reporting conducted using the federated models, it is expected that individual disciplines implement internal coordination and clash detection procedures as part of their normal modelling process. 3.1. HTML Clash Detection Reports

TERMINAL 1 DOMESTIC PIER AND INTERNATIONAL DEPARTURES EXPANSION - PERTH AIRPORT BUILDING INFORMATION MODELLING PROJECT EXECUTION PLAN - VERSION 2.0

July 18 2013

A Series of clash detection reports are generated in HTML format as part of the routine generation of the Federated Navisworks model. Clashes listed in the HTML report will be filtered by clash batch & status with colour coding These clash detection reports include:  Summary reports: o summarised breakdown of number and severity of clashes o location of high concentrations



Detailed reports:

Clash Description Clash detection batch name Clash Distance Clash Name Clash Point Date Created Number of clashes by status Revit Category Revit Element IDs of items involved Revit Family Name Revit Type Name Tolerance Total number of clashes 3.2. Model Viewpoints Viewpoints are saved within the federated model to aid visualisation and resolution of the clash. All clash viewpoints will be filed under a clash detection folder and then within folders named the same as the respective clash detection batch. Each viewpoint will be titled with the Clash Name as found in the accompanying HTML reports o o o o o o o o o o o o o

o o o

1. o o o

Setting Up Batch Routines

Batch reports are clash detection reports run to compare two or more nominated aspects of the design at each focus areas Batches will run for each Focus Zone at each level, e.g. Zone 1, Level 00 Batches will be grouped as follows: 1. ARCH/STRU vs SERVICES SERVICES vs SERVICES. 2. 3.

Clash Status Definitions with Color Coding

In the detailed clash detection reports, each clash is classified by its current status and is to be tracked using one of the predefined statutes found in the following table as part of Navisworks Manage Clash Detective tool: STATUS

DEFINITION

CONSIDERED A CLASH

OLD

Out‐dated clash that hasn’t been rechecked in current round of test



NEW

New clash discovered during latest round of tests



ACTIVE

An ongoing current clash that has not been resolved but has not been reviewed or approved



REVIEWED

A clash that has been reviewed by the project team/BIM Facilitator and action has been undertaken or correspondence has been entered into to solve it

APPROVED

A clash that has been reviewed by the project team but not resolved within the model. Instead noted as a false positive/insignificant clash

RESOLVED

A clash that has been reviewed and resolved within the model and will no longer be reported in subsequent rounds of tests

TERMINAL 1 DOMESTIC PIER AND INTERNATIONAL DEPARTURES EXPANSION - PERTH AIRPORT BUILDING INFORMATION MODELLING PROJECT EXECUTION PLAN - VERSION 2.0

July 18 2013

RESOLVING CLASHES

Upon receiving the HTML reports and Federated Navisworks model, the trade design/contractor’s team will review them before the Coordination meeting. Major clashes and coordination issues will be raised during this meeting in an open forum to allow for their resolution. The federated models will be displayed onscreen to help visualise the clash, and any outcomes will be marked up on the relevant drawing sheets/ 3D clash image and transmitted via Aconex as a meeting record. After the Coordination meeting concludes, each trade subcontractor (or Catalyst on their behalf) will amend their respective models in accordance with the meeting record. Any minor clashes are to be resolved outside of the design coordination meeting between the respective consultants involved If a clash is identified in a report and is reviewed and deemed to be insignificant or a false positive, Catalyst AE’s BIM Facilitator should be notified so as to mark up the relevant HTML report with the revised Clash Status. This notification will occur either in the Coordination Meeting or by communication between parties via Aconex. Each trade should make sure that the reviewed items are not significant. Upon receiving any notification regarding the HTML Clash reports, Catalyst’s BIM Facilitator will change the status appropriately in the next federated model that is produced

2. 3.

4. 5. 6.

Each trade is required to:    



Run the clash detection analysis for their respective trade system(s) against the Architectural/Structural construction models to ensure that there are no conflicts between the architectural/structural elements and their system(s) prior to submittal Post to Aconex up‐dated drawings/models at least once per week, prior to the clash detection analysis run by the BIM Facilitator. Collaborate with each other trade through Aconex, telephone, and in person to resolve basic clashes outside of the Coordination meetings. It is expected that the Coordination meetings are held to address difficult areas that are not able to be coordinated between the multiple trades themselves. At these meetings, the resolution will be collectively agreed upon, and a trade will be identified as having to “move”. This trade will adjust the respective model and repost it for the following weeks meeting. All trades are responsible to update and post the changes agreed upon at the meeting within 1 week of the coordination meeting

TERMINAL 1 DOMESTIC PIER AND INTERNATIONAL DEPARTURES EXPANSION - PERTH AIRPORT BUILDING INFORMATION MODELLING PROJECT EXECUTION PLAN - VERSION 2.0

July 18 2013

ATTACHMENT A: ABOUT BIM

Building Information Modelling (Source: Mastering REVIT Architecture 2008)

On today’s projects, complexity is very high, but the production of drawings is now the by‐product of building a virtual 3D model composed of constructive elements. These elements are loaded with data that describe not only geometry, but also cost, manufacturer, count, and just about any other metadata you can imagine. With an integrated parametric 3D model, it’s possible to detect spatial clashes between the multitudes of systems in the building. You can know with confidence whether duct work will interfere with the structural steel long before construction starts. The goal of reducing errors and smoothing out the construction process is driving firms to be more efficient, effective, and productive. In this reality plans, sections, and elevations are all derivative representations—producing them isn’t a set of isolated, discontinuous tasks. A data rich model means that more analysis and iterative searching for optimal solutions can occur early in the design process. As detail is added, the model becomes an increasingly accurate representation of what will actually be built. The model itself can be used to generate part lists, shop drawings, and instructions for industrially produced elements. The ultimate benefits of BIM are still emerging in a market primed to radically change the way buildings are designed and built. A shift in process and expectation is happening in the Architecture, Engineering, Construction (AEC) world, with private and public sector owners beginning to demand BIM models as part of the delivery package. The shift from traditional 2D abstractions to on‐demand simulations of building performance, usage, and cost is no longer a futuristic fantasy but a reality. In the age of information‐rich digital models, all disciplines involved with a project can share a single database. Architecture, structure, mechanical, infrastructure, and construction can be coordinated in ways never before possible. Models can now be sent directly to fabrication machines, bypassing the need for traditional shop drawings. Energy analysis can be done at the outset of design, and construction costs are becoming increasingly predictable. These are just a few of the exciting opportunities that a BIM approach offers. Designers and contractors can begin to look at the entire building process, from preliminary design through construction documentation into construction, and rethink how buildings come together. The whole notion of paper‐based delivery may become obsolete as more players adopt up‐to‐date, accurate, digital models. As we’ve mentioned, with a Revit Building Information Model, a parametric 3D model is used to generate traditional building abstractions such as plans, sections, elevations, details, and schedules. The drawings produced aren’t discrete collections of manually coordinated lines, but interactive representations of a model. The immediate 3D design visualisation of the building and its spaces improves understanding of the building and gives you the ability to show a variety of design options to all members of a project, at any moment. Integrated design and documentation keeps the data centralised and coordinated. This in turn leads to live and up‐to‐date schedules and quantity take‐offs. That information can then be used to make decisions earlier in the design process, reducing risk and cost overruns. Not only that, but with the coordinated BIM model, you can start running energy analysis, solar studies, daylighting simulations, and egress analysis much earlier in the process, allowing you to iterate through design decisions earlier, not later. Coordination with BIM is now required for many buildings to come into existence. Consider Daniel Libeskind’s recently completed Denver Art Museum and its extreme geometric configuration. Integrating the mechanical and structural systems into a 3D model was essential to the building’s successful completion. Exact spatial organisation of structural members could be modeled, which in turn led to fewer field errors and fewer requests for information. In addition, parts could be sent directly to fabrication from the model, eliminating the need for 2D drawings entirely. In the BIM era, 3D experience is the norm, not the exception. TERMINAL 1 DOMESTIC PIER AND INTERNATIONAL DEPARTURES EXPANSION - PERTH AIRPORT BUILDING INFORMATION MODELLING PROJECT EXECUTION PLAN - VERSION 2.0

July 18 2013

ATTACHMENT B: REVIT GENERAL MODELING BEST PRACTICES The objective of this Section is to provide general modelling best practices for Revit used on the Terminal 1 Departure Pier and Terminal Extension Project

1. GENERAL STANDARDS In general, the following characteristics of a Revit‐based application model can affect performance:  Complex geometry  Multiple parametric relationships  Multiple constraints/ linked files The following sections will examine many aspects of modelling and recommend certain practices in particular situations, but examining a model and its constituent families with these factors in mind will aid in optimising model performance

2. ARRAYS Arrays can be used to copy and associate objects together. After the array is deployed, performance may be improved by ungrouping the array and removing the parametric associations of the copied objects. You can also attain the same result by clearing the Group and Associate option before creating the array.

3. CONSTRAINTS Minimal constraints will help prevent:  "Can't keep joined" errors when moving objects.  Workset sharing issues where a user may unknowingly take ownership of an object 4. DWG FILES  Minimise the number of linked DWG files.  DWG files should only be used for coordination purposes in the Construction Models  Avoid importing unnecessary data like hatching or AutoCAD®‐specific line work such as construction lines.  Delete unnecessary parts and layers of the DWG file within AutoCAD and import only the cleaned, smaller DWG.  Avoid exploding the geometry imported from DWG files. The exploding operation within a Revit‐ based application can change a DWG from a single managed element to hundreds or thousands of additional elements depending on the number of entities in the imported DWG. Only link essential DWG files into necessary views.  Switch off visibility of 2D AutoCAD DWGs in perpendicular views. A 2D AutoCAD file linked into a plan view will show as collinear lines in elevation, causing performance degradation.  Linked or imported DWG files shall be placed on a unique workset  Remove all DWG files prior to issuing to external parties 5. MODELLING ECONOMICALLY  Limit joined geometry to necessities  Remove unneeded area schemes  Avoid maintaining unnecessary groups.  Delete unused groups from the project browser.  Purge unused objects. Because purged objects cannot be recovered, you may wish to make a backup of the project before purging.  Regularly review and fix warnings (Modify Ribbon > Warnings)

TERMINAL 1 DOMESTIC PIER AND INTERNATIONAL DEPARTURES EXPANSION - PERTH AIRPORT BUILDING INFORMATION MODELLING PROJECT EXECUTION PLAN - VERSION 2.0

July 18 2013

6. MODELING TOOLS Appropriate modelling tools for component creation shall always be used when modelling within Revit. For example:  Walls shall be modelled using wall tools, floors shall be modelled using floor tools etc  The use of non‐standard modelling process where a tool is available is not acceptable. Some building components or elements may not have a specific tool available. When this situation occurs the building component may be modelled & placed in the correct Revit category 7. PROJECT TEMPLATES  Avoid populating project templates with an excessive number of families that may or may not be useful for every project.  Favour a minimal rather than a comprehensive template. 8. RAILINGS  Avoid use of railings for extensive fences or separation systems, or at the very least limit the visibility of these elements.  There is no warning offered by Revit‐based applications, but performance is impacted because of the number of lines required to generate each railing element.  If a lengthy railing element is desired, consider modelling a simplified railing representation, relying on railing details to fully describe the design. 9. RASTER IMAGES  Remove unneeded raster images and renderings. Raster images represent a performance and file size cost that should be minimised.  Monochrome raster images are smaller than colour images.  Save black and white raster images as 1 bit per pixel format instead of JPG or TIF. MS Paint refers to this format

10. STAIRS  

Like railings, stairs are complex elements, but may not be easily simplified. Confine stair visibility to essential views.

11. UPGRADING LINKED PROJECTS TO A NEW VERSION OF REVIT   

Temporarily rename all central files. Renamed central files will fail to locate any Revit models linked to the renamed central and Revit will avoid temporarily upgrading the links. After you have upgraded each central file, use the Save As command to return each to its original name. Upgrade each central file's linked files. The upgraded central files will once again find the upgraded linked file.

12. VIEWS       

Before closing a file, keep only a simple drafting view open to accelerate saving and subsequent opening of the file. Minimise view depth where possible in elevation, plan, and section views. Consider back clipping views to reduce the quantity of geometry maintained in a view. o Right click in views to select View Properties Far Clip Offset o set the distance from the view camera to the desired view depth. Use section boxes to limit visible geometry when working in a 3D view. Minimise view quantity to help reduce model size. To optimise static models to be linked into active models (for instance, in the case of an existing contextual building model adjoined to a model of new construction) delete as many views as possible from the static model to be linked. Use the Wireframe or Shading display modes when working in a linked file environment. Wireframe and Shading modes can be 3 times faster than the Hidden Line or Shading with Edges modes. TERMINAL 1 DOMESTIC PIER AND INTERNATIONAL DEPARTURES EXPANSION - PERTH AIRPORT BUILDING INFORMATION MODELLING PROJECT EXECUTION PLAN - VERSION 2.0

July 18 2013

   

 



Avoid hiding large quantities of individual elements in views. Using the Paste Aligned command to paste into closed views will open and close the target views. When repeating such an operation several times, performance will be improved by opening all the target views before beginning the sequence of paste operations. Zoom in to speed up drawing and snapping. If you have a very dense view, and snap lines appear to be shooting off in all directions o click Manage tab > o Settings panel > o Snaps, and in the Snaps dialog, o Clear the Snap to Remote Objects option. Close unnecessary windows. When you are working in a 3D view, most of the file is placed into RAM. It is also recommended that these views should be closed when saving to central, since the Revit‐based applications will regenerate this complex view as part of the save process. Revit‐based applications will update all currently open views affected by changes in the model. Often, users will not realise that half a dozen or more views are currently open. In the following illustration, the Switch Windows drop‐down shows there are a number of other views open. o Clicking the Close Hidden button will close the concealed views, allowing the Revit‐based application to update only the current view with changes until other views are reopened. Assign the proper level of visual detail to a given view. In a 1/8" plan view, assigning a display detail level of Fine may be unnecessary. Plan views with the detail level set to Fine or Medium

13. VOLUMES ‐ ROOMS AND SPACES 

     

Only select the Room Bounding option for linked files if they are absolutely needed to bound volumes (rooms and spaces). The Revit‐based application will need to process these additional boundaries, which can affect model performance. This option is a type parameter for the linked file itself. Promptly resolve warnings about volume boundaries overlapping. If you have two levels with the same elevation, Revit‐based applications will perform better if all volumes are placed on one of the two levels, rather than dividing the same volumes between the two levels. Avoid coincident room or space separation lines overlapping each other and overlapping walls. To locate room or space separation lines in a model, create a wireframe view template with walls and room or space separation lines visible. Set the colour for room or space separation lines to red with a heavy line weight so they are easy to identify. Place room or space separation lines on one workset for better control. (see Worksets section). Turning area and volume computation off can improve performance, but will disable much of the volume analytical functionality in Revit MEP. When volume computation is off, Revit based applications will represent rooms as simple extrusions, without considering ceilings, roofs, floors, or other upper or lower boundaries. Because volume computations may affect the performance of your Revit project, it is disabled by default, except in Revit MEP, where the setting is enabled by default. Turn volume computations on, when you need to

14. WORKSETS The Revit platform originally implemented worksets as a mechanism to enable multiple users to collaborate on a single model by taking temporary ownership of user‐defined element groups. Making an entire workset editable (by checking it out) prevented other users from editing any part of that workset until control was relinquished upon a Save to Central operation. Worksets remain extremely valuable for data segregation and managing workflow, because they enable selectively opening and closing portions of a project across all project views. This level of control can represent an advantage over view dependent features such as view filters or visibility/ graphics settings in certain workflows. While the capability to check out a workset remains valuable under certain circumstances outlined below, in general the best practice is to use element borrowing rather than checking out entire worksets.

TERMINAL 1 DOMESTIC PIER AND INTERNATIONAL DEPARTURES EXPANSION - PERTH AIRPORT BUILDING INFORMATION MODELLING PROJECT EXECUTION PLAN - VERSION 2.0

July 18 2013

The Revit platform team recommends that worksets should be employed most often to segregate conceptual areas of a project, such as:  Separate buildings  Grid and levels  Building core  Building shell  Furniture and equipment spanning multiple categories  Spatially identifiable areas of a single building (such as wings)  Linked RVT and DWG files  Room or space separation lines (see Volumes ‐ Rooms and Spaces section)  Checking out a workset may occasionally be of use if certain model elements, such as the building grid or linked files, need to be protected from accidental change.  In that event, BIM managers or team leaders will sometimes check out a workset containing project elements that should not be casually edited or relocated.  Worksets can help manage element visibility to reduce visual clutter during editing, as well as the Revit platform's use of memory.  Closing currently unneeded worksets can release allocated RAM for the Revit platform's use in memory‐intensive tasks such as printing and exporting.  Although closed worksets will not appear in views, any elements within them will still be updated during model regeneration if they are impacted by changes made in open worksets, thus maintaining data coordination across the model. NOTE: Upgrading models to the current version of the Revit‐based application will force every workset to open, and will therefore not benefit from selective workset closure before file upgrade.  Use selective workset opening when accessing a work shared project file.  Close worksets not required for a given editing session.  When creating a workset, leave the Visible by default in all views option selected. Clearing this option can render the workset completely invisible and problematic in multi‐discipline workflows where feature visibility can be of paramount importance. 15. WORKSHARING  When making significant changes in a project (moving a level or major geometry changes), it is recommended that you perform the operation when no other users are working on the file and all other users have relinquished all elements. Once the changes are saved to central, have all users make new local files.  Save to Central operations can be accelerated by a preceding Reload Latest command.  When a project has been edited by other users for a day or more, it may be faster to create a new local from the central model rather than relying on the Reload Latest command to update the individual local model a day or more behind the remainder of the team.  Try to keep project team workstation specifications equivalent. A dramatically weaker machine specification used by a single team member can reduce overall project performance.  Revit‐based applications save only one local model at a time to the central file. As deadlines approach and the frequency of saving to central increases, use the Work sharing Monitor feature to coordinate Save to Central commands across the team. Alternatively, team members could stagger their regular saves to central by either communicating an intention to save to central to the team or by assigning a standard saving time to each team member; for example, at ten or fifteen minutes after the hour.  When attempts to save to central collide, Revit‐based applications notify you that another user is currently saving to central. Cancelling the Save to Central operation will prevent queuing the save request, allowing the user to continue to edit the local file before another Save to Central command.  Because the Revit platform attempts to update all open views before saving, both local saves and saving to central will increase in performance if a simple view, such as a drafting view, is the only view open when the save operation begins.  To reduce disk usage and memory usage, regularly compact central and local files.

TERMINAL 1 DOMESTIC PIER AND INTERNATIONAL DEPARTURES EXPANSION - PERTH AIRPORT BUILDING INFORMATION MODELLING PROJECT EXECUTION PLAN - VERSION 2.0

July 18 2013

 

TIP When you need to upgrade a work shared file from one version of Revit to another, rename all of the central files first. If you have linked files, Revit cannot find the links and thus will not try to temporarily upgrade the links. After you have upgraded, you can then use the Save As command to revert to the original name. Then, when you upgrade the linked files, Revit will once again find the upgraded linked file.

TERMINAL 1 DOMESTIC PIER AND INTERNATIONAL DEPARTURES EXPANSION - PERTH AIRPORT BUILDING INFORMATION MODELLING PROJECT EXECUTION PLAN - VERSION 2.0

July 18 2013

ATTACHMENT C: SHOP DRAWINGS AND CONSTRUCTION SCOPE OF WORKS (LOD 400) This section defines the design consultants’, subcontractors ‘and fabricators’ responsibilities for the development and delivery of BIM requirements during Construction (LOD 400) Phase. All responsibilities within this document are subject to design change. 1. DESIGN CONSULTANTS’ RESPONSIBILITIES This section defines the responsibilities of the design consultants in the development and delivery of BIM requirements. All responsibilities within this document are subject to design change and design scope still to be confirmed

1.1. Architecture  

Incorporate any revisions to the model and model components due to design changes Revise and review the model for any requests for information (RFIs) or technical queries (TQs) from the Construction Model’s Owners & Coordination Meetings

1.2. Structural Steel Engineering     

Ensure all issues discovered through the LOD400 Modeling Upgrade process are address through the model to the BIM coordination workshop details Include the BIM Manager in for any RFIs or TQs for the review and coordination cycles. Incorporate any changes to the designed systems from the Coordination Meetings Revise and review the model for any requests for information (RFIs) or technical queries (TQs) from the Steel Contractor Owner & Coordination Meetings Incorporate any revisions to the model and model components due to procurement issues. Work with the BIM Facilitator to facilitate any requirements for fabrication and construction tracking.

1.3. Electrical Engineering  

1.4. Fire Protection Engineering   

1.5. Hydraulic Engineering   

1.6. Mechanical (HVAC) Engineering    

Revise and review the model for any requests for information (RFIs) or technical queries (TQs) from the Steel Contractor Owner & Coordination Meetings Incorporate any revisions to the model and model components due to procurement issues. Incorporate any revisions to the model and model components due to procurement issues. Incorporate any changes to the designed systems from the workshop model. Incorporate additional details to the model from the workshop layouts and fabrication in preparation for the As‐Built Model. TERMINAL 1 DOMESTIC PIER AND INTERNATIONAL DEPARTURES EXPANSION - PERTH AIRPORT BUILDING INFORMATION MODELLING PROJECT EXECUTION PLAN - VERSION 2.0

July 18 2013

SUBCONTRACTORS’ / FABRICATORS’ RESPONSIBILITIES At the award of the subcontract, Design (LOD 200) Revit models will be passed to the subcontractor. These models will form the basis of the shop detailing model(s) and additionally will be progressed through to Construction Modeling Phase (LOD 400). The subcontractor (or Catalyst on the subcontractor’s behalf) will produce workshop and fabrication requirements using approved BIM compliant workshop detail authoring tools. The detailed requirements for all deliverables will be provided in the BEP and will include but not be limited to the following:  Submit RFIs and TQs to Built Environs for approval. Built Environs to then progress approved RFIs and TQs to the engineer for resolution.  Work with the BIM Manager to facilitate any requirements for fabrication and construction tracking.  Ensure all issues discovered through the internal checking process are processed through the model to the workshop details.  Throughout the shop detailing period both the shop detailing model and the Revit LOD 400 model will be submitted to the BIM Manager weekly for review and coordination.  Within 4 weeks of the approval of shop details the finalised shop detailing model and the completed Revit LOD 400 model will be submitted to Built Environs as record models along with and referenced equipment documents and data sheets.  At this point, the Revit LOD 400 model will become an As‐Built progress model. The completeness of the Revit LOD 400 must be approved by the Project BIM Manager for acceptance by the Managing Contractor.  Throughout the construction and installation period the Revit LOD 400/500 model will be submitted once (1) each month to the BIM Manager and this submitted model will incorporate all final installation information for the components installed in the previous month of work. This model will also reflect any modification to location or layout made as a part of the construction and installation to the tolerances as noted.  Any additional referenced documents for these installed components may also be submitted at this time and uploaded according to the requirements of PAPL as might be agreed at award e.g. O&M manuals, certificates, warrantees etc.

TERMINAL 1 DOMESTIC PIER AND INTERNATIONAL DEPARTURES EXPANSION - PERTH AIRPORT BUILDING INFORMATION MODELLING PROJECT EXECUTION PLAN - VERSION 2.0

July 18 2013

ATTACHMENT D: FILES MAINTENANCE CHECKLIST 1.

WEEKLY FILE MAINTENANCE

Stakeholder’s model should perform the following steps:       

AUDIT THE CENTRAL FILE;

EVERY TWO WEEKS FILE MAINTENANCE:

PERFORM A COORDINATION REVIEW, IF USING REVIT TO MAINTAIN COORDINATION WITH OTHER STAKEHOLDERS PERFORM AN INTERFERENCE CHECK, IF USING REVIT TO DETECT COLLISIONS; REVIEW AND RESOLVE WARNINGS; DELETE UNUSED OR REDUNDANT VIEWS; PURGE UNUSED ELEMENTS; AND COMPACT THE CENTRAL AND LOCAL FILES.

In addition to weekly maintenance tasks, perform the following step: 

CREATE A BACKUP OF THE CENTRAL FILE. 3. DAILY  AUDIT LOCAL FILES UPON OPENING THEM; AND  COMPACT LOCAL FILES WHEN CLOSING THEM FOR THE DAY. BACKUPS AND ARCHIVES  AT EACH ISSUE DATE, OR AS REQUIRED, USE THE DETACH FROM CENTRAL OPTION TO CREATE AN INDEPENDENT, ARCHIVE‐READY CENTRAL FILE.  BACKUPS CAN BE GENERATED VIA THE SAME PROCESS, BUT THIS IS GENERALLY UNNECESSARY, AS EACH USER’S LOCAL FILE CAN BE CONSIDERED TO BE A BACKUP FILE. IF A CENTRAL FILE BECOMES CORRUPT, IT IS OFTEN MOST EFFICIENT TO CONVERT THE MOST‐RECENTLY‐SAVED LOCAL FILE FOR THAT PROJECT INTO A NEW CENTRAL FILE, RATHER THAN ATTEMPTING TO RECOVER A BACKUP FILE THAT MAY BE OBSOLETE. DETERMINE THE PROJECT’S BIM ROLES/RESPONSIBILITIES AND BIM USE STAFFING

TERMINAL 1 DOMESTIC PIER AND INTERNATIONAL DEPARTURES EXPANSION - PERTH AIRPORT BUILDING INFORMATION MODELLING PROJECT EXECUTION PLAN - VERSION 2.0

July 18 2013

ATTACHMENT E: NAVISWORKS EXPORT SETTINGS Below is the correct settings display when exporting from Revit to Navisworks

TERMINAL 1 DOMESTIC PIER AND INTERNATIONAL DEPARTURES EXPANSION - PERTH AIRPORT BUILDING INFORMATION MODELLING PROJECT EXECUTION PLAN - VERSION 2.0

July 18 2013

ATTACHMENT F: NAVISWORKS FEDERATED MODELS DESIGN

TERMINAL 1 DOMESTIC PIER AND INTERNATIONAL DEPARTURES EXPANSION - PERTH AIRPORT BUILDING INFORMATION MODELLING PROJECT EXECUTION PLAN - VERSION 2.0

ZONE 4 ‐ LEVEL 02 FEDERATED MODEL

ZONE 5 ‐ LEVEL 02 FEDERATED MODEL

ZONE 1 ‐ LEVEL 02 FEDERATED MODEL

ZONE 2 ‐ LEVEL 02 FEDERATED MODEL

ZONE 3 ‐ LEVEL 02 FEDERATED MODEL

ZONE 4 ‐ LEVEL 01 FEDERATED MODEL

ZONE 5 ‐ LEVEL 01 FEDERATED MODEL

ZONE 1 ‐ LEVEL 01 FEDERATED MODEL

ZONE 2 ‐ LEVEL 01 FEDERATED MODEL

ZONE 3 ‐ LEVEL 01 FEDERATED MODEL

ZONE 4 ‐ LEVEL 00 FEDERATED MODEL

ZONE 5 ‐ LEVEL 00 FEDERATED MODEL

ZONE 1 ‐ LEVEL 00 FEDERATED MODEL

ZONE 2 ‐ LEVEL 00 FEDERATED MODEL

ZONE 3 ‐ LEVEL 00 FEDERATED MODEL

ZONE 4 UNDERGROUND FEDERATED MODEL

ZONE 5 UNDERGROUND FEDERATED MODEL

ZONE 1 UNDERGROUND FEDERATED MODEL

ZONE 2 UNDERGROUND FEDERATED MODEL

ZONE 3 UNDERGROUND FEDERATED MODEL

NODE 4 FEDERATED MODEL

NODE 3 FEDERATED MODEL

NODE 5 FEDERATED MODEL

DOMESTIC PIER MODEL

NODE 2 FEDERATED MODEL

NODE 6 FEDERATED MODEL

NODE 1 FEDERATED MODEL

DOMESTIC PIER FEDERATED MODEL

TERMINAL EXPANSION FEDERATED MODEL

TERMINAL 1 DOMESTIC PIER AND INTERNATIONAL DEPARTURES EXPANSION

FEDERATED MODEL

July 18 2013

ATTACHMENT G: QA/QC PROCEDURE & SPREADSHEET BY CATALYST AEC Catalyst AEC understands that model quality is the highest priority to accomplish BEP Goals and uses. In behalf of model quality, a Cross QA process is will be applied as follows: 1. Use of color code dimensions and tags according to the element status at each trade virtual model (QA views will be used by floor/zones as required) • CAT ‐ Modeler Dimension_Cyan– Cyan • CAT ‐ QA Approved_BLACK– Black • CAT‐ RFI_RED– Red • CAT ‐ Discrepancy with Design_Magenta– Magenta 1. Red RFIs elements will be record in an internal RFI log and submitted as “Internal RFIs” for each focus zone addressing each missing or conflict information from the shop drawings documentation provided. This will happened first internally and will be raised out in the weekly coordination meetings when solution can’t be accomplish internally 2. Internal RFIs visual color code: Red color: Missing Element's Location specify with dimensions, spot elevation ‐ Elements that do not represent have missing location specification will displayed grayed out. ‐ Elements in question and their dimensions will display red Blue color: Missing element's ID, service system. ‐ Elements that do not represent missing ID or services systems will displayed grayed out ‐ Elements in question and ID's tags will display blue Purple color: Elements with conflict between plan and detail or clashing with other element ‐ Elements that do not represent any conflict will displayed grayed out ‐ Elements in question, their plan view will displayed blue and their IDs tag will displayed purple Refer to attached “Global RFI” sample for reference Refer to attached “Internal RFI” sample for reference

TERMINAL 1 DOMESTIC PIER AND INTERNATIONAL DEPARTURES EXPANSION - PERTH AIRPORT BUILDING INFORMATION MODELLING PROJECT EXECUTION PLAN - VERSION 2.0

July 18 2013

ATTACHMENT H: DEFINITIONS 3D: 3D refers to the physical geometry of the building as defined in the model, within the context of BIM this is made up of a collection of building components such as such as walls, slabs, columns, doors, windows, etc. It provides a way to visualise what the end product will look like.

4D: 4D refers to the effect of time against the model, specifically relating to the incorporation of the construction program timeline to the model components. This allows construction sequencing simulations, scheduling and on‐site production control of the project

Authoring Tool: Refers to various BIM software and/or applications used to create, edit and alter objects/elements which makes up the BIM model. Autodesk Revit Architecture: BIM authoring software developed by Autodesk that is predominantly used by architectural firms to create, edit and review architectural design from concept design to construction. Autodesk Revit Structure: BIM authoring software developed by Autodesk that is predominantly used by structural engineering firms to create, edit and review structural design and analysis from concept design to construction.

Autodesk Revit MEP: BIM authoring software developed by Autodesk that is predominantly used by mechanical, electrical and hydraulic (MEP) engineers supporting building system designs and analysis from concept design to construction.

BIM: Building Information Modelling (BIM) is the generation and management of information about a building during its entire life cycle. BIM is facilitated by a suite of technologies and processes that integrate to form the „model‟ (essentially a database) at the heart of which is an object (or component) based 3D representation of each building element. The model is the single point of truth for the project.

DWG: DWG (DraWinG) is a binary file format used for storing two and three dimensional design data and metadata. It is the native format for several CAD packages including AutoCAD. Model Author / Model Owner: Model Author or Model Owner refers to each individual who contributes to the authoring of model content. The role of a model author includes; Creation and placement of model components; Entering applicable information regarding model components; Coordination of created components; Communication of model creation and coordination issues to the Model Manager

NWC: Navisworks Cache (NWC) is the file format developed by Autodesk and is opened in the software Autodesk Navisworks

NWD: Navisworks Document (NWD) is the file format developed by Autodesk and is opened in the software called Autodesk Navisworks Manage and Autodesk Navisworks Freedom.

RVT: Standard file format used by all versions of Autodesk Revit.

TERMINAL 1 DOMESTIC PIER AND INTERNATIONAL DEPARTURES EXPANSION - PERTH AIRPORT BUILDING INFORMATION MODELLING PROJECT EXECUTION PLAN - VERSION 2.0