Construction BIM Execution Plan

Construction BIM Execution Plan HA0385 – FSNI HEAD OFFICE BUILDING

Revision Date Issued By Revision Comments 1 30/01/19 CM Tender Issue 2 29/04/2019 CM Revised 3 07/08/2019 CM Updated per Assemble (SD) Review 30/07/19

Construction BIM Execution Plan Revision 3 2 HA0385 FSNI Head Office Building 07/08/19 Hawkins

Change Register Revision 1 – Issued for Tender Submission

Revision 2 – Revised as noted

Revision 3 – Assemble review update


Contents Change Register ......................................................................................................................................................................... 2

Contents .......................................................................................................................................................................................... 3

Project BIM Methodology Overview ................................................................................................................................. 6

Project Information .................................................................................................................................................................... 7

Key Project Contacts ................................................................................................................................................................ 8

Project Goals .............................................................................................................................................................................. 10

BIM Use Competency Requirements ........................................................................................................................... 11

Client Specific Requirements ............................................................................................................................................ 12

Project Deliverables ............................................................................................................................................................... 13

Information Management and Exchange .................................................................................................................. 15

Information Exchange ...................................................................................................................................................... 15

Schedule of Information Exchange .......................................................................................................................... 16

BIM Project Information .................................................................................................................................................. 16

Model Description Document ...................................................................................................................................... 16

IFC Model Exchange for Revit Users ........................................................................................................................ 17

File Naming Conventions ............................................................................................................................................... 20

Model Naming Convention ........................................................................................................................................... 20

Drawing Naming Convention ...................................................................................................................................... 21

Sheet Numbering Convention ..................................................................................................................................... 22

Model Management .............................................................................................................................................................. 23

Space and Room Naming Conventions ................................................................................................................ 23

Modelling Software ........................................................................................................................................................... 23

Federation and Review Software ............................................................................................................................... 23

Measurement and Coordinate Systems: ............................................................................................................... 24

Reference Documents and Modelling Standards ............................................................................................ 25

Coordination and Collaboration ...................................................................................................................................... 26

Meeting Schedule .............................................................................................................................................................. 26

3D Coordination and Review Protocols and Process ..................................................................................... 27

Clash Detection and Visual Review .......................................................................................................................... 28

Issue Resolution .................................................................................................................................................................. 28


Facilities Management ............................................................................................................................... 29

Quality Control .......................................................................................................................................................................... 30

Quality Control Checks .................................................................................................................................................... 30

Model Acceptance Criteria ................................................................................................................................................. 31

Level of Development (LOD) ............................................................................................................................................. 32

LOD 100 ................................................................................................................................................................................... 32

LOD 200 ................................................................................................................................................................................... 32

LOD 300 ................................................................................................................................................................................... 32

LOD 350 ................................................................................................................................................................................... 32

LOD 400 ................................................................................................................................................................................... 32

Field Verification (As-Built/Record Modelling) ......................................................................................................... 33

No Field Verification (NFV) ............................................................................................................................................ 33

Quality Assurance As-Built (QAB) .............................................................................................................................. 33

Visual As-Built (VAB) .......................................................................................................................................................... 33

Measured As-Built (MAB) ............................................................................................................................................... 33

Specific Elements to be Field-Verified ..................................................................................................................... 34

Model Element Responsibilities Table ......................................................................................................................... 35

Appendices ................................................................................................................................................................................. 43


Executive Summary

To Hawkins, BIM is not one specific new tool or technology that drastically changes the way we do things. Instead it should be seen as a gradual evolution of existing processes, in our continual endeavor to ‘work smarter, not harder’. By changing the way we work, adopting more collaborative and coordinated work practices, and supporting more integrated project delivery, we can actively generate improved project outcomes for all involved.

The project BIM Execution Plan helps to define these methods of work to successfully achieve the project goals, including successful completion of the design, construction, and handover phases, and providing both built and digital assets to our client which provide value long into the future.

This BIM Execution Plan defines the specific goals and information required throughout the delivery of the project. It is important that the standards and methods in these documents are agreed and maintained by all team members to support the strategy for producing the individual component models which make up part of the federated BIM model.

Our aim is to engage and support our project teams to actively value and contribute to an open, collaborative working environment through the development and promotion of BIM capabilities and knowledge.

All team members working on this project are required to understand the contents of the BIM Execution Plan and ensure that their working methods are aligned with these requirements. It is expected that all parties working on the project will adhere to these standards in the preparation and delivery of their design information.


Project BIM Methodology Overview Further to recent industry experience, and known levels of sub-contractor ‘BIM’ capability, we attach our proposed BIM management workflows in the appendices (refer SK01, SK02, SK03, MM-WF-01, MM-WF-02, MM-WF-03). We propose where sub-contractors are BIM-capable or have design elements to their trades that they complete their own modelling and thus installation layout drawings. Where sub-contractors do not have this capability, we propose to engage an external resource to complete modelling (and installation layout drawings) on their behalf. Individual component drawings (switchboards, pumps) and schematics, will still be produced by the sub-contractor or their suppliers, with details of these elements provided to the external modelling resource for integration with the construction phase models. Where an external modelling provider is utilized for multiple trades, it is expected that this provider will coordinate among these trades, with only a final coordination step required with any other subcontractors performing their own modelling. To facilitate efficient ongoing coordination of the various sub-trade disciplines, live models will be hosted on an online platform (Autodesk BIM360) to enable linked reference models to be live, thus avoiding coordination against outdated information. Clash detection and visual review will be utilized by the external modelling provider to identify any geometric clashes or other coordination issues, which are then to be resolved by the respective trade modeller. If these cannot be resolved independently by the modeller, issues are then escalated to the attention of Hawkins, using a cloud-based issue tracking platform (KUBUS BIMcollab). If required, issues can be further escalated to the design team, or specific trade subcontractors to advise the required course of action to resolve. Once issues are resolved in each area, installation layout drawings can then be extracted from the models and issued to the design team/client for formal review and sign-off, along with review by the installation sub-contractors. When construction commences, any significant deviations from the layout drawings will be recorded by the trade subcontractor and updated within the models for later inclusion on ‘as-built’ record drawings. It is the responsibility of individual sub-contractors to ensure as-built deviations are accurately recorded and advised back to Hawkins as part of their quality control practices. Trades/disciplines that do not generally undertake further design development or shop drawings (internal walls/linings for example) will not be amended by Hawkins or our sub-contractors. It is our expectation that should these be modified in any way by design change or other instruction, that the original author of these model elements (generally the architectural design consultant) will modify the model and re-issue accordingly. Should any significant deviation from the design documents arise on site, marked up drawings will be provided to the relevant design consultant to enable their model to be updated to reflect the ‘as-built’ condition.


Project Information

Project Name FSNI Head Office Building Project Owner AIAL - Auckland International Airport Limited Main Tenant: FSNI - Foodstuffs North Island Limited Project Address Project address to be confirmed, Auckland Brief Project Description 8,500m2 Head Office Building Contract Type/Procurement Method TBC Contractor Engagement – Indicative Date 28 29 March 2019 Construction Completion/Handover Date 03 December 2020 (TBC) Has a Project BIM Brief been completed? Yes, Assemble BIM Brief dated 30/01/19


Key Project Contacts

Role Company Name Phone Email Client Team Client AIAL Peter Donovan [email protected] Project Manager Xigo Shane Phillips 021 935 292 [email protected] Xigo Thomas Rutter 021 024 00443 [email protected] Cost Consultant Rider Levett Bucknall Chris Haines +64 9 3091074 [email protected] BIM Manager Assemble Ltd Steve Davis 021 444 270 [email protected] Project Manager FSNI RDT Pacific Sarah Houlden 027 539 2008 [email protected] Construction Project Director Hawkins Craig Treloar 027 221 2832 [email protected] Project Manager Hawkins Sam Gordon [email protected] VDC/BIM Manager Hawkins Christian McCartney 0274 298 480 [email protected] Services Engineer Hawkins Graeme Cox [email protected] Design Team Basebuild Architecture - Lead Consultant

Monk Mackenzie Architects Raukura Turei 027 663 4013 [email protected]

Basebuild Architecture – BIM Modeller

Assemble Dwane Stairmand 09 927 4472 [email protected]

Interior Fitout Monk Mackenzie Architects Sean Flanagan 021 072 8494 [email protected] Interior Fitout – BIM Modeller Assemble Dwane Stairmand 09 927 4472 [email protected] Structural BGT Structures Andrew Gaul 022 1234513 [email protected] Structural – BIM Modeller BGT Structures Snehal Muley 09 9707880 Ext. 213 [email protected] Mechanical E-Cubed David Fullbrook +64 9 303 0007 [email protected]


Role Company Name Phone Email Mechanical – BIM Modeller E-Cubed Reuben Wood +64 9 303 0007 [email protected] Electrical Electrical Consulting Nick Topp +64 9 309 0640 [email protected] Electrical – BIM Modeller Electrical Consulting Brendan Reid +64 9 3090640 [email protected] Hydraulics E-Cubed Connor Fullbrook +64 9 303 0007 [email protected] Hydraulics – BIM Modeller E-Cubed Reuben Wood +64 9 303 0007 [email protected] Fire Protection Protech Design Stuart Hope +64 9 298 4877 [email protected] Fire Protection – BIM Modeller Protech Design Matthew Burton +64 9 298 4877 [email protected] Fire Engineering Holmes Fire Kathryn Devine +64 9 308 7030 [email protected] Civil Harrison Grierson Chris Mellican +64 9 9175000 [email protected] Sub-Contractor BIM Coordinators

Economech Leon Lakay +64 9 579 1444 (Ext. 848)

[email protected]

Construction Workshop Greg Diamond +64 3 261 9465 +61 42 607 9436

[email protected]

Construction Workshop Jos Holtrop +64 21 1801 605 [email protected]


Project Goals

This table lists the client’s goals and expectations for the project and how BIM could be enabled to assist in achieving them.

Refer to Appendix D of the New Zealand BIM Handbook for BIM Use Definitions.

Priority Goal Description – Value Added Objectives BIM Uses Low To represent both permanent and temporary facilities on site during multiple phases of

the construction process. It may also be linked with the construction programme to convey space and sequencing requirements.

Site Utilisation Planning

High To eliminate any major system conflicts prior to installation during construction, reduce waste and rework, hence increasing productivity on site

3D Coordination

Medium To show the construction sequence and space requirements on a building site for the construction project team for a better understanding of project milestones and construction plans.

Programming/4D Modelling

High To depict an accurate representation of the physical conditions, environment and assets of a facility. If the model is kept up to date as the construction happens, Contractor can use these models and documents for Council As-Record application. As-record elements to be verified by appropriate party. Further clarification of the information required for this BIM Use can be found in the Construction MEA.

Record Modelling

Low To connect the information in the BIM (model and CDE) with Client’s Asset Management software. Asset Management criteria to be further defined by AIAL and FSNI

Operation/Asset Management


BIM Use Competency Requirements

This table identifies the clients required uses of BIM throughout the course of the project, from conception to operation. Additionally, it identifies the parties responsible for each intended use, and level of value gained from this use.

Items shown in italics will only be undertaken if Hawkins project management determine doing so will add significant value to the project, over and above typical 2D planning processes.

BIM Use Value to Project

Responsible Parties Value to Responsible Parties

Competencies Required

Site Utilisation Planning Low Hawkins High Ability to create a 3D BIM model reflective of the proposed site facilities arrangement. Understanding of intended methodology, and project logistics.

Design Authoring High Design Team, Subcontractors High Ability to create and develop a comprehensive Building Information Model, Design and Construction experience.

Programming/4D Modelling Low Hawkins, Subcontractors High Ability to understand connection between programme activities and relevant 3D model elements.

Design Review High Design Team, Hawkins High Ability to navigate and interrogate a multi-discipline federated construction model.

3D Coordination High Design Team, Hawkins, Subcontractors High Ability to navigate and interrogate a multi-discipline federated construction model. Ability to identify appropriate solutions to coordination issues and action accordingly.

Record Modelling High Design Team, Hawkins, Subcontractors High Ability to identify and verify changes made to site installations that are not in accordance with For Construction installation layouts and amend the relevant Building Information Model accordingly.

Asset Management Low Design Team, Hawkins, Subcontractors, AIAL Asset Information Team

Low Ability to understand connection between 3D model elements and associated data, and their use through the operation of a built asset.


Client Specific Requirements

AIAL have specific requirements for all Airport precinct projects. Refer to AIAL Asset information delivery manual. In particular – allow for the following:

Periodic hand-over of models for review and check by BIM Managers & AIAL BIM team. The Contractor is expected to carry out this task for Record Modelling Delivery of native and IFC files by all parties at agreed milestones including a model description document to track all changes. All documentation (as far as practical) is to be authored from the BIM software (not separated). All models are to be spatially located to AIAL requirements. All models and documents are to adhere to AIAL document naming conventions. Inclusion of project specific data within all models submitted. Use of Aconex as Common data environment.


Project Deliverables This section details the required deliverables from each of the parties to this BIM Execution Plan.

The below table provides more detailed deliverables as required to fulfil each of the client specific requirements above.

BIM Use What From To Due Date/Stage Format Comments

3d Coordination/Clash Detection Model Consultants Hawkins Contract award *.rvt Consultants to provide fully

coordinated models as defined in MEA table.

3d Coordination/Clash Detection Model Subcontractors/External

Modelling Resource Hawkins

Pre-construction & Construction

*.rvt/.ifc/ .nwc

Models as per Model Element Responsibilities Table

3d Coordination/Clash Detection Model External Modelling

Resource Hawkins


*.nwc Federated model including clash

detection tests/results

3d Coordination/ Clash Detection Model Hawkins Consultants/

Subcontractors/ Client


*.nwd Hawkins to provide federated model

for coordination/review purposes

Construction System Design, Mock-up, and Phase Planning

Model Subcontractors/External Modelling Resource

Hawkins Pre-construction & Construction

*.nwd As required to assist construction activities

Design Authoring Drawings Subcontractors/External

Modelling Resource Hawkins/

Subcontractors Construction *.rvt/.pdf

Installation layout drawings reflecting coordinated models – to include overall layout plans (1:100), 1:50

detailed layouts, elevations, sections, details, and 3D views, as required to clearly communicate the subtrade

works.


BIM Use What From To Due Date/Stage Format Comments

Record Modelling Drawing Markups

Subcontractors Hawkins/External

Modelling Resource

Construction *.pdf

Marked up drawings showing any site-instigated deviations from the construction issue drawing layouts

for inclusion in “as-built” record models.

Asset Management Data Subcontractors Hawkins/External

Modelling Resource

Construction *.xls/.pdf Asset information/data as required by AIAL to be populated against model

elements

Record Modelling Models Hawkins Client Regular drops / Handover

*.rvt / *.ifc (other native as

required)

Record Modelling Drawings Hawkins Client Regular drops / Handover

*.pdf / *.dwg DWG’s – only plans, elevations, and

sections as individual sheets

Record Modelling Asset Data Hawkins Client Regular drops / Handover

*.xlsx


Information Management and Exchange Information Exchange The following table identifies the responsible parties, design authoring software and version to be used with the associated BIM Uses, along with the collaboration file format that the team will use to exchange models. Unless agreed otherwise, all parties are to issue both native format model files, along with .IFC exports at each exchange.

BIM Use Responsible Party Receiver Software Version Collaboration File Format

Comments

Design Authoring Design Consultants Hawkins Autodesk Revit 2019.2 .rvt, .ifc, .pdf

Autodesk AutoCAD 2015 .dwg, .pdf Graphisoft ArchiCAD 21 / 2017 .ifc, .pdf

Design Authoring Subcontractors, External

Modelling Resource Hawkins Autodesk Revit 2019.2 .rvt, .ifc, .pdf

Models to be hosted on BIM360

3D Coordination Subcontractors, External

Modelling Resource Hawkins Autodesk Navisworks 2018 .nwc, .ifc

Design Discipline to export models to .nwc and .ifc BIM Manager to append to .nwf/ .nwd format and load into the Aconex BIM viewer

All models are to be uploaded to the Aconex document register at the required frequency, superseding previous versions.

Native Revit project models will be hosted on BIM360 to enable efficient coordination between separate discipline models.


Schedule of Information Exchange

Information Exchange Purpose Discipline Frequency Day/Date Comments

Design Authoring – Model Handover Design to Construction

All Design Disciplines (Design Consultants)

Once Issue of Detailed Design/IFC Design Models

Design Authoring – Construction Phase

All specialist building services subtrades

Daily Daily – multiple times Daily synchronisation of models

to BIM360 Docs

3D Coordination All specialist building services subtrades

Weekly Friday, 4pm Synchronisation of models to BIM360 Docs, weekly publish

BIM Project Information The following information should be included within each model of the project. These parameters are based on AIAL AIDM Section 08. BIM Requirements

Organization Name [company name] Organization Description [company discipline] Building Name OF Model Author [discipline BIM Coordinator name] Project Issue Date Weekly publish date Project Status [Coordination – Construction – Handover & Operations] Client Name AIAL - FSNI Project Address TBC Project Name FSNI Head Office Building Project Number [AIAL CAPEX Number] 91947

Model Description Document Each modelling team should include the BIM Model Description Document (MDD) issued by AIAL that includes crucial information for each model it publishes. The document should describe the contents of the model, any major revisions/changes and explain its purpose and limitations. This MDD can be incorporated in the native model or as a stand-alone file but should be exported as a PDF at every end of the design phase.


IFC Model Exchange for Revit Users Revit Users should link Other’s native Revit models.

Export Process: For Revit Users, create a dedicated IFC Export 3D view which contains building elements to be coordinated across disciplines. Other’s models and duplicated items to be hidden (such as through Worksets, Visibility Graphics or filters).

Under Export, duplicate IFC2x3 Coordination View to modify the setting and follow the images below.


File Naming Conventions The file naming convention for the project is in line with AIAL Asset Information Delivery Manual, Design Documentation Standards, and Document Management Procedures.

Model Naming Convention AIAL Capex No Project Description File Type Discipline Area

FSNI Warehouse and Offices 91947

Foodstuffs North Island FSNI Model MDL

Acoustic AC Office OF

Drawing DWG Architectural AR Land Development LD

Report RPT Construction CT

Warehouse Building

WH

Image IMG Civil CV

Schedule SCH Electrical EL

Façade FA

Federated Model FED

Fire Engineering FE

Fire Protection FP

Geotechnical GO

Mechanical ME

Security SC

Seismic SE

BIM BM


Drawing Naming Convention

AIAL Capex No Project Description File Type Discipline Area Sheet Number FSNI Warehouse and Offices 91947

Foodstuffs North Island FSNI Model MDL

Acoustic AC Office OF # # ##

Drawing DWG Architectural AR Land Development LD 4-digit sheet number

Report RPT Construction CT

Warehouse Building

WH See below for sheet

numbering breakdown

Image IMG Civil CV

Schedule SCH Electrical EL

Façade FA

Federated Model FED

Fire Engineering FE

Fire Protection FP

Geotechnical GO

Mechanical ME

Security SC

Seismic SE

Utilities UT

BIM BM


Sheet Numbering Convention

Each sheet number is made up of four digits which represent the following information

# - Sheet Series # - Building Level ## - Building Zone/Sequential Sheet Number 0 – General and Details 0 – Ground Floor (OF Level 0) Zones or Sequential Numbers 1 – Schematics 1 – Level 1 (OF Level 1) 10 – Zone 1a 01 2 – Layouts (Layout subject (ie equipment/containment etc) varies by discipline) 2 – Level 2 (OF Level 2) 11 – Zone 1b 02 3 - Layouts 3 – Roof (OF Roof) 20 – Zone 2a 03 4 - Layouts 21 – Zone 2b 04 5 - Layouts 30 – Zone 3a 05 6 – Plantrooms and Risers 9 – Multiple Levels (Applies to Schematics, Risers, General Details) 31 – Zone 3b 06 7 - Spare 40 – Zone 4a …. 8 - Schedules 41 – Zone 4b 9 - Spare


Model Management

Space and Room Naming Conventions Space naming convention as defined by Architectural (Monk Mackenzie Architects) model in accordance with AIAL standards.

Modelling Software All design team models were received in Autodesk Revit 2018 format, and subsequently upgrade by Hawkins to Revit 2019. Latest Revit build to be used is 2019.2.1, build 19.2.10.7, 20190225_1515(x64).

Other modelling formats (for example Tekla/ProSteel for structural steel, FireAcad/AutoSprink for sprinkler systems etc, are to be reviewed and agreed with Hawkins to ensure a suitable workflow can be established for best achieving interoperability.

Federation and Review Software Models will be federated using both Revit and Navisworks Manage (2018). The use of Revit in the initial step of model federation ensures models are correctly aligned using shared (‘real-world’) coordinates (allowing for any discrepancy in Project Internal coordinates), before being exported to Navisworks cache (*.nwc) files. Navisworks cache files are to be exported from the federated Revit model to Project Internal coordinates, and shifted to Shared Coordinates using ‘Units and Transform’ within the Navisworks federated model (*.nwf).


Measurement and Coordinate Systems: The following coordinates are to be used for the project:

Project Base Point (Revit)

Project Origin Auckland, 1946 Mt Eden Circuit at 800000mN 400000mE Horizontal Datum NZTM 2000 Project Location Easting Northing RL 400469699.898166 787888749.295991 7500 Model Rotation from True North 340.999° Legal Description

All Design consultants must acquire coordinates from the Office Architecture model (91947-AIAL-MDL-AR-OF). Refer to Acquisition of Coordinate Procedure for Revit models on Aconex.

CAD Origin (0,0,0)

Project Location X Y Translation to TBC TBC Relation to project gridlines TBC TBC Model Rotation from True North TBC Elevation - Z TBC

Note: IFC/DWG models will be imported origin to origin as required, and adjusted within Revit to match existing models. Z – height to be modelled at correct real-world datum value.


Reference Documents and Modelling Standards These are the minimum modelling standards for the project, and must be adhered to;

Generic Title Applicable Reference Document/Notes Version NZ BIM Handbook BIM Acceleration Committee. (2016) New Zealand BIM Handbook. Wellington.

Also refer associated appendices. November 2016

LOD Standards The BIMForum. (2017) 2017 Level of Development Specification. Electronic copy available from BIM Manager

2017

NZCIC Design Guidelines NZCIC Design Documentation Guidelines. Refer to all disciplines and co-ordination checklist. 2016 AIAL Asset Information Delivery Manual

AIAL Draft 2018

AIAL Management Procurement – Documentation Management

AIAL Draft 2018

Assemble BIM Execution Plan - AIAL-FSNI Landings (Office & Warehouse)

Revision G, 28 August 2018


Coordination and Collaboration The design review, model coordination and clash detection procedures are described in the BIM Guidelines.

Meeting Schedule The table below schedules the required meetings over the course of the project to more efficiently collaborate and coordinate.

Meeting type Facilitator Project Stage Required Attendees

Required Technology

Frequency Location

BIM Requirements kick-off Assemble Pre-construction All Large screen,

HDMI Once

Assemble Office

Design Review and Coordination Hawkins Pre-Construction Relevant design

team, subcontractors

Large screen, HDMI

Weekly TBC

Design Coordination Hawkins Construction/Shop Drawings Relevant design

team, subcontractors

Large screen, HDMI

Weekly Site

Desktop reviews with model authors Sub-contractors,

external modelling resource

Pre-Construction, Construction

Sub-contractors, external modelling resource, Hawkins

BIM Manager

Large screen, HDMI

Ongoing as required

Office

BIM Handover Assemble Project Handover All, AIAL Asset

Information team Large screen,

HDMI Once TBC


3D Coordination and Review Protocols and Process A key goal/benefit achieved through the use of BIM tools on this project is the spatial coordination of building elements through 3D coordination, design review, and clash detection. To ensure a structured approach to clash detection, and that clashes are managed in an efficient manner, the below clash detection matrix will be used to test for spatial coordination issues within the federated Navisworks model, utilizing Navisworks Manage, and the “Clash Detective” tool within.

Clashes are to be tested to realistic construction tolerances (ie -50mm, for seismic clearance in accordance with NZS 4219), or as required to ensure compliance with the relevant seismic/design standards when elements are installed in location on site. The tolerance for each test is as shown in the matrix below.

[01] STRUCTU

RE

[02] CEILINGS

[03] SEISMIC (IM

MOVABLE)

[04] ARCH SUPPORT

[05] LIGHTS

[06] AIR TER

MINALS

[07] MEC

H EQUIP

[08] ELEC

T EQ

UIP

[09] DUCTW

ORK

[10] HYD

PIPE (SYP

H)

[11] HYD

PIPE (DR)

[12] MEC

H PIPE

[13] CABLE TRAY

[14] HYD

PIPE (PRESSU

RE)

[15] LA

B PIPE

[16] FIRE PIPE SO

LID

[17] FIRE PIPE FLEX

[18] SEISMIC (MOVABLE)

[19] FLOORS AND W

ALLS

[01] STRUCTURE N N N ‐10 ‐100 ‐10 ‐10 ‐10 ‐10 ‐10 ‐10 ‐10 ‐10 ‐10 ‐10 ‐10 50 N N

[02] CEILINGS N N N N 50 50 50 ‐50 ‐50 ‐50 ‐50 ‐50 ‐50 ‐50 ‐50 50 N N

[03] SEISMIC (IMMOVABLE) N N ‐100 ‐50 ‐50 ‐50 ‐50 ‐50 ‐50 ‐50 ‐50 ‐50 ‐50 ‐50 50 N N

[04] ARCH SUPPORT N ‐100 ‐50 ‐50 ‐50 ‐50 ‐50 ‐50 ‐50 ‐50 ‐50 ‐50 ‐50 50 N N

[05] LIGHTS 25 25 ‐100 ‐100 ‐100 ‐100 ‐100 ‐100 ‐100 ‐100 ‐100 ‐100 50 ‐100 N

[06] AIR TERMINALS 25 ‐50 ‐50 25 ‐50 ‐50 ‐50 ‐50 ‐50 ‐50 ‐50 50 ‐25 ‐25

[07] MECH EQUIP 25 ‐50 25 ‐50 ‐50 ‐50 ‐50 ‐50 ‐50 ‐50 50 ‐25 ‐25

[08] ELECT EQUIP 25 ‐50 ‐50 ‐50 ‐50 ‐50 ‐50 ‐50 ‐50 50 ‐25 ‐25

[09] DUCTWORK 25 ‐50 ‐50 ‐50 ‐50 ‐50 ‐50 ‐50 50 ‐25 ‐25

[10] HYD PIPE (SYPH) 25 ‐50 ‐50 ‐50 ‐50 ‐50 ‐50 50 ‐25 ‐25

[11] HYD PIPE (DR) 25 ‐50 ‐50 ‐50 ‐50 ‐50 50 ‐25 ‐25

[12] MECH PIPE 25 ‐50 ‐50 ‐50 ‐50 50 ‐25 ‐25

[13] CABLE TRAY 25 ‐50 ‐50 ‐50 50 ‐25 ‐25

[14] HYD PIPE (PRESSURE) 25 ‐50 ‐50 50 ‐25 ‐25

[15] LAB PIPE 25 ‐50 50 ‐25 ‐25

[16] FIRE PIPE SOLID 25 50 ‐25 ‐25

[17] FIRE PIPE FLEX N ‐25 ‐25

[18] SEISMIC (MOVABLE) N N

[19] FLOORS AND WALLS N


Clash Detection and Visual Review While clash detection will be utilized, the majority of design coordination and model review should be undertaken visually. Clash detection should only be used to provide the ‘red flags’ that should be further inspected, as simply moving geometry to avoid a clash in one location can have significant knock-on effects down-stream.

Issue Resolution While the clash detection processes detailed above will identify any geometric intersection “clashes”, it will not identify issues that are not clashes, or provide input on the appropriate actions to resolve the issues or clashes.

Hawkins expectation is that individual modellers will undertake correction and resolution of simple geometric clashes where the solution can be readily envisaged, taking care that the correction action does not cause further issues or clashes away from the original issue location. Where an issue or clash cannot be easily resolved, the modeller is to escalate the issue/clash to an “Issue” within the BIMcollab platform provided by Hawkins, assigning the issue to the team member based placed to resolve the issue. If the issue is expected to have time or cost implications, Hawkins team will escalate it further as an RFI to the design team/client via the Aconex Project CDE.

Please refer also to MM-WF-03 - Model Issue Resolution Workflow_R01 included at the appendices for further detail.


Facilities Management While integrated asset data within the BIM models is not a specific client requirement, this information must still be collected and collated as part of the development of Operations and Maintenance Manuals. As building services elements are modelled for the purpose of shop drawings, asset information can easily be added at this stage for later export to Excel (.xlsx) and import into AIAL GIS/FM systems.

Asset data can be generated in many ways, allocated into one of four sub-categories, depending on how data is created or derived from the model. These sub-categories are as follows;

Sub-Category Description Examples Project-generic Data which is generally consistent for all model elements across

a project Site Code, Site Name, Structure Code

Model-generated Data which is automatically generated through placement of an element within a model.

Level, GUID, Service Name, System

Element-specific Data which is specific to the element, and typically informed by product technical submissions

Vendor, Manufacturer, Life Expectancy, Serial Number*

Site-generated Data which is only generated once an asset is installed, or the project is completed

Warranty Start, Serial Number*

Note: Serial number can be generated by technical submission where specific elements are already allocated to a location, ie AHU’s, or generated from site installation where elements are ordered in bulk and are not allocated to specific locations, ie smoke detectors.

Data to be collected for specific asset types is as defined in Appendix E of the AIAL Asset Information Delivery Manual. Where possible data should be appended to default Revit parameters (other software TBC) such as “Mark”, “Manufacturer”, “Model”, or “Level”, however this may be adapted as required with agreement from Hawkins. Towards completion of the project, data will be mapped and extracted from Revit in Comma Separated Values (*.csv) format and handed to the AIAL Asset Information Team alongside record BIM models.

Where Hawkins do not control/maintain a model containing assets which AIAL requires data for (for example fire doors within the Architectural model), we will request that the model owner provides the above parameters for each element type as a blank data field, with data to be input (via Excel data transfer processes, to be developed) by the Hawkins project team, with input from relevant subcontractors.


Quality Control Quality Control Checks The following checks should be completed regularly to assure quality within models, both of 2D/3D geometry, as well as any other information contained within the model. This process will also assist in eliminating errors and working towards achieving the desired project outcomes.

In addition to the Quality Control checks undertaken by the BIM Coordinators and BIM Manager (listed in the BIM Execution Plan), model authors should also perform a quality check before sharing data to confirm that the agreed standards have been followed. These include (but are not limited to):

File naming meets agreed protocol Data saved to agreed project co-ordinate system Model saved to a 3D view with all elements visible. All reference data (2D & 3D) removed (methodology to be confirmed with Hawkins) Checked and reviewed for error warnings Purged, audited and compressed (methodology to be confirmed with Hawkins) Level of Development meets Model Element Responsibilities Table requirements Note: These processes don’t replace picking up the phone and talking to each other.

Check Definition Responsible parties Project stage Frequency

Visual check See that there are no unintended model components and the design intent has been followed

BIM Coordinators Coordination Ongoing

Interference check Detect problems in the disciplines model where two components are clashing including soft and hard

BIM Coordinators Coordination Fortnightly

Model integrity checks Ensure integrity of the model aligns with BIM Uses and client’s BIM specific modelling and documentation requirements & standards, as set out in Model Standards

Hawkins BIM Coordinator/Manager

Coordination, Construction, Completion

Monthly

Design review Review that the ongoing development of the model is aligned with the client objectives.

Hawkins BIM Coordinator/Manager

Coordination Fortnightly

Authoring software warnings Ensure all warnings are resolved prior to issue of models. BIM Coordinators Ongoing


Model Acceptance Criteria Further to the above Quality Control checks, the following criteria will need to be met for Hawkins to accept models from other parties for further federation/coordination. Models not meeting these criteria will be returned to the author for correction prior to being combined into the federated model for further coordination.

- Models correctly located to either shared (Revit), or project internal coordinate system. Please note requirement for models to be correctly located in relation to the true CAD cartesian origin (0,0,0) to ensure alignment when exported to interoperable formats (ie .ifc)

- Model elements to correct Level of Development as defined in the model element authoring table

- All elements in correct worksets

- All elements in correct phases

- Model elements coordinated with one another (within same model)

- Model elements coordinated with one another (across different disciplines)

- Models must contain all views, details, and sheets as included in the contractually issued documentation set

- Model elements must have adequate spatial allowance for other elements not necessarily modelled, for example seismic restraints

- Models do not exceed industry best-practice file sizes, and are split/linked as required to remain easily manageable


Level of Development (LOD) Level of Development (LOD) is “a means of defining the extent to which a model element has been developed, from conception in the mind of the designer through to its construction and operation” (NZ BIM Handbook, 2016), and helps to “give clarity to each member of a design/construction team as to what they are required to author in their models at each stage and to what extent others can rely on them”.

Hawkins and the NZ BIM Handbook refer to the BIMForum LOD Specification in order to define the scope of each LOD, from LOD 100 through to LOD 400. A brief outline of our interpretation of each LOD is below. Refer to the 2018 BIMForum LOD specification for further detail.

LOD 100 – Conceptual, diagrammatic, or schematic information. Not geometric model objects.

LOD 200 – Generic model objects as placeholders. May be indicative of the proposed object, or volume for space reservation only.

LOD 300 – Model element is graphically represented within the model as a specific system, object, or assembly. Generally reflects “design intent”.

LOD 350 - As per LOD 350, but also includes interfaces with other systems and further model geometry as necessary to coordinate with other elements. May include hangers, supports, seismic bracing or other, as required to coordinate. Generally reflects “construction intent”.

LOD 400 – Model element represents complete and final fabrication detail including fittings and fixings, holes, or other assembly information.


Field Verification (As-Built/Record Modelling) Provision of a Field-Verified record model requires elements to be verified on site as being in accordance with the virtually modelled element. Elements can be verified on site, either through completion of standard quality assurance/control procedures (QAB), Visual As-Built (VAB) verification, and Measured As-Built (MAB) verification, with the latter of these (MAB) requiring digital surveying, or laser scanning of the final installation. The level of accuracy of these methods of verification differ (QAB lowest, MAB highest), however the final purpose of the verified model geometry will determine what level is suitable.

No Field Verification (NFV) Generally not used.

Quality Assurance As-Built (QAB) As part of Hawkins (and our subcontractors) quality assurance and control procedures, constructed systems and elements are confirmed as being constructed in accordance with the relevant construction documents. Verification status is not specifically noted within model element properties.

Visual As-Built (VAB) Specified elements are visually checked for correct position, orientation, and alignment, with any recognisable deviations from the modelled element noted and updated in the model to reflect the site-installed condition. Visual as-built may include some basic measurement (tape measure, spirit level) for position, alignment, level, and plumb. Visual as-built includes spot checks on installed elements to ensure they are installed in accordance with “For Construction” documentation.

Measured As-Built (MAB) Specified elements will be digitally surveyed using traditional survey techniques, or 3D laser scanning, and compared against modelled elements. Deviations between modelled elements and the site-installed condition will be updated in the model to reflect any deviations to +/-10mm unless a higher Level of Accuracy (LOA) is specified. Timing of a measured as-built is also to be specified, for example pre-pour, post-pour etc. Verification status is specifically noted within model element properties.


Specific Elements to be Field-Verified While the Model Element Responsibilities Table includes general subcategories of model element, it may not always be necessary to field verify all elements of that category. In this case, specific elements to be field verified are to be scheduled in the table below. This table also includes a description of the reason for field verifying this element, and the required LOA.

The requirement for visual or measured as-built is to be noted in the Model Element Responsibilities Table in conjunction with the general LOD levels. It is important to note that model elements do not need to be progressed to ‘LOD 500’ to achieve a VAB or MAB status. For example, an element modelled to LOD 300 may be field verified by visual inspection, and noted in the Model Element Responsibilities Table as LOD 300 VAB.

It is to be assumed that all elements where not specifically field-verified have been installed in accordance with the relevant design documentation with quality-assurance based verification (QAB).

Element Description/Reason Timing LOD VAB/MAB LOA

TBC


Model Element Responsibilities Table

This table assigns responsibilities to Model Elements via an Author (MEA) and defines Level of Development (LOD) for those model elements across project stages. Elements and their respective LOD’s at Detailed Design are as per the Assemble Construction MEA Table (91947-FSNI-PRC-BM-OF-Model Element Authoring Construction.pdf), Revision A, dated 20 December 2018. Legend for model element responsibilities table:

MEA discipline

Design Consultants

Hawkins

Level of Development (LOD) Refer to New Zealand BIM Handbook for definitions

100 Conceptual

200 Approximate geometry

300 ‘Design intent’ with precise geometry to correct size, shape, and position

350 ‘Installation intent’ as required for specific coordination, ie hangers and bracing

400 Fabrication and assembly including all fixings and fittings

Suffix: VAB/MAB See explanation of Field Verification on page 33

Sub-Contractors TBC

Structural Steel

Concrete Works

Mechanical

Fire Protection

Hydraulic

Electrical

Communications/Data

Security

Curtainwall Facade

Civil Services

Arrow indicates model element remains as per detailed design consultant models, and carried through to handover, with update by original model author to match design changes or significant ‘as-built’ deviations from design


Project Phase Concept design

Preliminary design

Developed design

Detailed design

Construction design

Handover/ Record

Notes

Model Element MEA LOD MEA LOD MEA LOD MEA LOD MEA LOD MEA LOD

Refer Design BEP for Design Phases

SPATIAL

Site boundaries, setbacks 500 QAB

Grids 500 QAB

Levels 500 QAB

Rooms/Spaces 300 NFV

SITE

Topography 300 QAB

External Levels 300 QAB

Stormwater 300 300 300 VAB

Services (in ground) 300 300 300 VAB

Roadways QAB

Parking VAB

Paths/Paving 300 VAB

Walls/Fencing 300 VAB

Soft landscaping (2D) N/A VAB

SUBSTRUCTURE



Preliminary design

Developed design

Detailed design

Construction design

Handover/ Record

Notes



Foundations 300 QAB

Retaining walls 300 QAB

Subsoil Drainage 300 300 300 VAB

Slab on Grade 300 QAB

STRUCTURE

Beams – Structural Steel 300 400 400 VAB

Columns – Structural Steel 300 400 400 VAB

Shaft openings 300 VAB

Stairs 300 400 400 VAB

Ramps 300 VAB

Structural Walls 300 VAB

Beams - Concrete 300 VAB

Columns - Concrete 300 VAB

Slabs (including slab edges) 300 VAB

Bracing 300 400 400 VAB

Penetrations 300 VAB



Preliminary design

Developed design

Detailed design

Construction design

Handover/ Record

Notes



Precast Wall Panels 300 300 VAB

ENCLOSURE/EXTERNAL

Roofing 300 VAB

Cladding 300 VAB

Decking 300 VAB

Curtain walls/windows 300 VAB

Windows 300 VAB

Doors 300 VAB

Canopies 300 VAB

INTERIOR

Partitions 300 QAB

Interior doors 300 QAB

Interior Windows 300 QAB

Ceilings 300 QAB

Seismic supports/restraints 300 300 VAB

Flooring 300 QAB



Preliminary design

Developed design

Detailed design

Construction design

Handover/ Record

Notes



Balustrading 300 QAB

F, F & E

Casework, joinery 300 NFV

Fixtures 300 VAB

Fittings 300 VAB

Equipment (non-service) 300 VAB

Furniture (Loose) 300 NFV

Furniture (Fixed) 300 VAB

Finishes 300 QAB

Signage 300 NFC

MECHANICAL

Plant external 300 350 350 VAB

Plant internal 300 350 350 VAB

Air terminals 300 350 350 VAB

Services in risers 300 350 350 VAB

Louvers 300 350 350 VAB



Preliminary design

Developed design

Detailed design

Construction design

Handover/ Record

Notes



Ductwork 300 350 350 VAB

Flexible ductwork 200 350 350 VAB

Registers 300 350 350 VAB

Pipework_50mm+ 300 350 350 VAB

Pipework_<50mm 200 350 350 VAB

Controls (2D) N/A

Electrical for Mechanical (E4M)

350 350 Including cable distribution, controls, MCC’s etc, VAB

Seismic support/restraints X 350 350 VAB

HYDRAULIC

Plant & equipment 300 350 350 VAB

Sanitary fixtures 300 350 350 VAB

Pipework _50mm+ 300 350 350 VAB

Pipework_25 - 50mm X 350 350 VAB


Seismic support/restraints 350 350 VAB



Preliminary design

Developed design

Detailed design

Construction design

Handover/ Record

Notes



FIRE PROTECTION

Sprinklers 300 350 350 VAB

Pipework (main) 300 350 350 VAB

Pipework (branch) 300 350 350 VAB

Detection 200 350 350 VAB

EWIS / alarm systems 200 350 350 VAB

Fire panels 200 350 350 VAB

Hydrants 300 350 350 VAB

Extinguishers 300 350 350 VAB


Valve sets 200 350 350 VAB

Seismic supports/restraints X 350 350 VAB

ELECTRICAL

Electrical fixtures 200 300 300 VAB

Power outlets (2D) N/A 300 300 VAB

Switch & distribution boards 200 300 300 VAB



Preliminary design

Developed design

Detailed design

Construction design

Handover/ Record

Notes



Cable trays 300 350 350 VAB

Conduits (>50mm) X 300 300 VAB

Lighting fixtures 2D 300 300 VAB

Light switches / controls 2D 300 300 VAB

Communications 2D 300 300 VAB

Security 2D 300 300 VAB


Seismic supports/restraints X 300 300 VAB

CONVEYING

Lifts, escalators (N/A) N/A


Appendices

1. SK01_BIM Management Workflow (D)_20190807

2. SK02_BIM Management Workflow - Subcontractor, External Modelling Resource Workflow_20180829

3. SK03_BIM Management Workflow - Indicative Model Progression Timeline_20190807

4. MM-WF-01 Model Structure and Federation Workflow_R01_20180222

5. MM-WF-02 Model Development Progression Workflow_R01_20180222

6. MM-WF-03 Model Issue Resolution Workflow_R01_20180222

7. Clash Detection Matrix

8. Subcontractor BIM Requirements

Construction BIM Execution Plan

Documents

Transcript of Construction BIM Execution Plan