Owners- How to contract for BIM deliverables and actually get what you want. Birgitta Foster & Cindy Baldwin

Transcription

1 Owners- How to contract for BIM and actually get what you want Birgitta Foster & Cindy Baldwin

2 Introduction Virtual Design Construction Operations Check us out at.. VDCOtech.com Owner BIM representative

3 Aligning organizational goals with BIM Deliverables OVERVIEW Keeping your Eye on the data Owners How to contract for BIM and actually get what you want Dictating platformspecific BIM Practical and achievable BIM To Do or Not to do Record Model

4 BIM Deliverables and Organizational goals Expectations Unsatisfactory experience : o Requiring BIM without defining why or how their BIM o Results unsure why they are doing BIM. Best chance at success o Business BIM Uses - Business reasons to use BIM o Not a one time savings but the ANNUALIZED savings o Contracting for the BIM you can use

5 ESTABLISH DEFINE DEVELOP CONTRACT Business BIM Uses User Requirements Deliverable Requirements Contracts Requirements 2D CD CAD Excel Geometry Data Emergency Mgt CMMS Space Mgt 3D EHS Requirements File Formats PDF Word Documents Submittals Record Commissioning report Geometry - MP Spec/LOD Spec/M3 Data - Facility Data Spec/COBie/LOD Attributes Data Schedules Naming Conventions Design Team Programming CD Package Sheet Views Equip Schedules BIM Uses Schedule File Format Software Contractor Submittals Commissioning BIM Guidelines Digital Deliverable Guide Geometry - MP Spec Facility Data Spec File Formats BIMPxP Design Team Deliverables Contractor Schedule Software Documents BIM Uses

6 Business BIM Uses BIM Deliverables and Organizational goals Start here Assessment based on 1- Current need 2- short term need 3- long term need Begin your BIM roadmap

7 BIM Deliverables and Organizational goals A pain point o is a problem, real or perceived. o creates opportunities for themselves by creating solutions. o Solutions create value for everyone. Business Value Uncover most common organizational Pain Points

8 8 Keeping your Eye on the data What data can do we need? get?

9 9 Keeping your Eye on the data KISS principal : Data we need

10 Keeping your Eye on the data Go beyond COBie with data

11 Keeping your Eye on the data EHS check : Equipment Utilities = Room Utilities Reformat the data for Owner data schedules FMS System Data set for upload Missing

12 Dictating platformspecific BIM Pros and Cons

13 September 2016 Owner ( Year released) Broward County Aviation Department - BCAD ( 2013) Design Software Construction Software 3D viewer IFC requirements Record - Design As-built - GC Neutral- Native & IFC compliant Acceptable : ArchiCAD; Bentley Ach V8i, Bentley Building, Revit Neutral- Native & IFC compliant Acceptable : ArchiCAD; Bentley Ach V8i, Bentley Building, Revit Broward Health - FLA ( 2013) Revit Revit N/A N/A DELIVERABLES YES - compliant 2x3 for Record & As built YES - IFC compliance for file transfer & Solibri checker YES_ Design -Native/IFC YES_ A/S/MEPF Models must reflect as-built geometry & Data. Native- Navisworks/IFC/RVT YES- Native and IFC YES_ A/S/MEPF Models;2D PDF; BIM-Native- Navisworks/RVT/IFC Dictating platformspecific BIM Denver Airport ( 2013) Revit Revit Navisworks/Revit N/A N/A YES_ Navisworks/Revit Record AS-built Department of Defense Military Health System - DOD-MHS ( 2011) Federal Aviation Administration- FAA (2012) Neutral- Native- IFC certified Neutral- IFC Compliant - Arch/Struct: Revit Architecture, Bentley Architecture(Triforma), Tekla MEPF Revit MEP, AutoCAD MEP, Bentley BIM Neutral- Native- IFC certified Neutral- IFC Compliant - Revit MEP, AutoCAD MEP, Bentley BIM, CAD-Duct, CAD-Pipe,AutoSprink, PipeDesigner 3D Navisworks /Navigator/ Adobe/Google earth Navisworks /Navigator/ Adobe/Google earth YES - certified 2x3 or better for Coord view for all deliverable YES - certified 2x3 or better for Coord view for all deliverable N/A N/A YES_Design & Contractor - As-built conditions and updated parameters YES -Record models Florida International Unv (2014) Revit Revit/Navisworks Navisworks Yes- at close out for record keeping and interoperability NO_ See as-built YES_ Design update Arch & Struct through construction/ Contractor MEPF Reviewed Fifteen (15) Standards University California San Francisco Medical Ctr (2015) Massport ( 2015) Revit Revit N/A Univ Southern California (USC) Design Bid Build (2012) Revit Revit Navisworks Revit Neutral- Not specified- Native Navisworks YES- IFC file may be required on some projects for model quality review at handover NO - Only when used for coordination YES -May be required- all subs have capability to save into most recent version YES_The Record Model is the Design Intent Model updated to show the as-built locations of the elements within this model and does not reflect all As Built components geometry. will contain accurate attribute data on major equipment and systems for FM. Typically updated by the Designer from information provided by the Constructor (digital mark-ups, photography, laser scans). It may be used by Commissioning YES_The As-Built Model (.nwd) is submitted to MPA by the Contractor. The As-Built Model is typically an Autodesk Navisworks file that includes shop models and drawing information from trades and fabricators with detail of the as-built conditions. This model may also include laser scan data. It is used as a detailed reference document of all as-built conditions, but is not the basis of FM. N/A YES- By Contractor Called Record for LOD 500 YES_ As Constructed YES_ As Constructed - Native USC GMP Contracts (2012) Revit Revit Navisworks/ Revit N/A YES YES_ Revit or Native USC PRevitXP (2015) Revit Revit N/A N/A YES- with shared parameters & COBie data YES_ Revit/Native(trade models) University South Florida- USF (2015) Revit Revit Navisworks N/A See as-builts YES_Construction updates by Contractor then sent to Design team for final As built -Revit/Navisworks Veterans Administration - VA - (2010) Neutral- IFC Compliant - Arch/Struct: Revit, Bentley BIM, ArchiCAD, Tekla, Vectorworks; MEPF: ArchiCAD MEP, Revit, AutoCAD MEP, Bentley BIM, Neutral- IFC Compliant - ArchiCAD MEP, Revit, AutoCAD MEP, Bentley BIM, CAD-Duct, CAD-Pipe, AutoSprink, PipeDesigner 3D N/A YES_- IFC file format of the consolidated building systems models - Coordination view YES- Native file format(s) of Design Model - YES_ Contractor Native file formats of the final Design Intent model remains current with all consolidated as-built Model(s) for building systems used approved bulletins for overall scope. It is NOT in the multi-discipline coordination process. The expected that product specific information will be Model(s) shall be fully coordinated and align with the added to this model. Design Model for architecture and structure; General Services Admin -GSA Series 8 FM (2012) United States Army Corp of Engineers- USACE ( 2012) Birgitta Foster/VDCO Tech 2016 Neutral- IFC Compliant - should create IFCs in compliance with the coordination view, spatial program validation view and COBie Neutral- IFC Compliant - should create IFCs in compliance with the coordination view, spatial program validation view and COBie N/A YES- Design Intent BIMs: Record BIMs deliverable -- not required for Construction or Coordination BIMs YES_ Native and IFC - represent the final asconstructed building and components configuration, including Architectural Supplemental Instructions, Change Notices, and field changes YES_Native and IFC, Editable copy of the Record BIM that is constantly updated to represent the current completed state of the building and systems configuration. Neutral-Revit or AECOsim Neutral-Revit or AECOsim N/A IFC coord view - archive n/a YES -Record models

14 Dictating platformspecific BIM Pros o Healthier competition no software requirements to limit the set of bidders o The team members work with their own software platforms o Do not use unfamiliar software o Or pay a third party to produce the BIMs. Cons Owners may have oless control of the final software selection orisk receiving a less desirable platform. osupport multiple software platforms odifficultly hiring experienced staff in the multiple platforms oa platform not compatible downstream applications.

15 To Do or Not to do Record Model Record vs As-Built Record should be reserved for models being provided by the designers of record. As-built is associated with contractor provided as-installed building models.

16 To Do or Not to do Record Model Wide range Record BIM ostrategies o Arch/Struct CD BIMs with Contractor MEPF models o Design intent models to incorporate as-constructed conditions o Design record models use As-built model elements with product data OWNER Example : Design Intent model remains current with all approved bulletins for overall scope. It is NOT expected that product specific information will be added to this model. oterminology mix and matching = confusing o As-built Record o Record As-built o Design As-built o Contractor Record o Contractor Record As-built

17 To Do or Not to do Record Model Contractors As-Built Deliverables omost consistent owner BIM requirement. onative common deliverable file formats. osome cases IFC and Navisworks files. ohybrid mix of BIM/3D CAD/2D CAD ofederated Models- A trend to merge into a single deliverable o limits the number of BIMs the owner ultimately stores, manages and updates

18 To Do or Not to do Record Model Design Teams Deliverable Record BIMs PROS - Provides record models of changes recorded by the Design Team - More accurate starting point for renovations - Better investment than 2D record drawing from Contactor redlines - Reuse of Contractor models to capture undocumented changes CONS - Perceived risk will come with a price tag - Hard to identify level of effort for each project - No industry-wide best practice/guidelines/standards available

19 Practical and achievable BIM Ensure practical and achievable oproven obest Practice examples oresource Model ovalidation Tools

20 Practical and achievable BIM Proven to be achievable All required tested o As acceptable for intended use by End User o Produced with existing project software o Workflows are possible and practical

21 Practical and achievable BIM Best Practice - Example Building Systems YARD SALE! Set systems with specific color When placing - wrong color = wrong system Use the software to stop before it happens

22 Practical and achievable BIM Transfer using INSERT FROM FILE Provide a Resource Model Contains Owner Specific o Data Schedules o Sheet Views o Libraries o Shared Parameters NOT A Model TEMPLATE Transfer as PROJECT INFO

23 Practical and achievable BIM Automate checking your staff doesn't have time to do thoroughly AV Equipment at required height? Building Systems Pipe material correct? System components assigned no Yard Sale! Fire dampers in all Fire walls? More control of your Data Validation Tools Data Clash detection Acceptable Manufactures? Motor voltages?

24 Practical and achievable BIM Leverage BIM deliverable software Record BIMs o Reverse Clash detection o Value-Add approach

25 Design Intent Vs As Constructed = off by more than 12 Reverse Clash Detection

26 Contractor Routing Design Intent Routing Value Add to update?? Contractor Routing Design Intent Routing CHILLED WATER LINES CHILLED WATER RISERS

27 Contractor Location VAV & Duct Design Intent Location Value Add to update?? Contractor Routing Ductwork Design Intent Routing

28 Contractor Piping Design Intent Piping Pumps Value Add to update?? Contractor Routing Ductwork Design Intent Routing

29 Record modeling o MEANS contains the same content and level of development as the Design Intent BIMs for Construction Documents. o Does NOT Mean. to contain all the construction details in the trade models.

30 Owner example Rules of thumb Design Intent Model updated when Contractor Models are either : A) Location of element* deviates o 6 or more in any space o 12 or more in any concealed spaces, mechanical spaces for MEP & other building systems. o 12 or more by any slab openings, steel members greater than 10 in depth and other major structural elements. B) Equipment* or system component* has been o Replaced by an owner-approved alternate or o Added during the construction phase of the project. *Vague= $$.. must define to what Equipment/system/component

31 ESTABLISH DEFINE DEVELOP CONTRACT Business BIM Uses User Requirements Deliverable Requirements Contracts Requirements 2D CD Geometry Data Emergency Mgt CMMS Space Mgt 3D Record EHS Requirements Geometry - MP Spec/LOD Spec/M3 Data - Facility Data Spec/COBie/LOD Attributes Data Schedules Naming Conventions BIM Guidelines Digital Deliverable Guide Geometry - MP Spec Facility Data Spec Documents Best Practices BIMPxP CAD Excel File Formats PDF Word Documents Submittals Commissioning report Design Team Programming CD Package Sheet Views Equip Schedules BIM Uses Schedule File Format Software Contractor Submittals Commissioning Contractor Design Team Deliverables Schedule Software BIM Uses

32 Owners How to contract for BIM and actually get what you want THANK YOU! Birgitta Foster Cindy Baldwin