Program Validation & Data Management Using Autodesk Revit + drofus + an IFC Model Server

Transcription

1 Program Validation & Data Management Using Autodesk Revit + drofus + an IFC Model Server Rolf Jerving CEO

2 Class Summary In this class, I will focus on new workflows enabled by combining Autodesk Revit Architecture and/or Autodesk Revit MEP software with drofus integrated program management software, including its built-in Industry Foundation Classes (IFC) model server. 1. About building programming, BPie and work flows 2. How to build a requirements-/ data model 3. Data driven design in Autodesk Revit Architecture and Autodesk Revit MEP & data management 4. Continuous program validation through an embedded IFC model server 5. Export of data to IFC and COBie 6. Implementation examples. Co-presenter Greg Schleusner, HOK.

3 Learning Objectives At the end of this class, you will be able to: Explain how data-driven design can be more efficient than design-driven data management Explain how controlling and managing all parameters across models helps to reduce errors Explain how a cloud based planning, program validation and data management tool, such as drofus, improves productivity with Autodesk design suites Describe the advantages of synchronizing data through the Revit API combined with an integrated IFC model server Export project data from Autodesk Revit Architecture, Autodesk Revit MEP and drofus to IFC/COBie.

4 About this presentation I will shift between PowerPoint and live use of tools several times The handout documents more of the actual work flow Not possible to do the same things I show without being a registered customer of all tools used Q & A at the end of the presentation

5 Building programming, BPie and work flows

6 Definition Building programming is the process of collecting all requirements the building must fulfill (buildingsmart international work group for building programming 2007) It s a process It s about the requirements It s a building project

7 Programming vs. design Requirements and design evolve in an iterative process Initially the program drives the design BPie (Owner) requirements can be managed in parallel with the design BPie A standardized requirements model for data exchange between program and design.

8 Various tools for programming tasks Not many world wide Trelligence Affinity Codebook Earnest drofus Onuma..? Quite different tools with different scope and capabilities I will show how drofus can support projects when Autodesk Revit is the design tool.

9 Requirements models and data driven design

10 The concept of templates Template 001: Office, 1 person Data field Value Descrition of the function/activity in the room Number of people in the room, normally 1 Office work for one person... Permanent work place Required door opening Temperature day summer, min Yes Minimum xxxx XX F El power, normal supply

11 Setup of new projects Different projects needs different requirements- / data models Different owners/clients have different standards Different national standards between countries Different data needs for e.g. opera houses and hospitals Large projects vs. small projects = easy setup & customization of tools is an important issue Beneficial if you can copy project standards and GUI between projects Let s: a) Customize a new project, and b) Create a requirements model for use in design!

12 Data driven design specify it before you design it Model 1 Planning tool Model 2 Model 3 Model x

13 Data driven design and data management Data driven design requires more efforts earlier in the project In parallel with early design, the requirements/data model must be established. Stakeholder involvement is an important (and time consuming) part of this process Our experience is that this gives good ROI later in the project Project data is well structured from the beginning stored in one source The process creates a common understanding among all parties of the project goals and scope Design can be executed more efficient Program drives the design and the design drives the program : =This requires a tool that supports configurable data flow between all design models and the program/external database.

14 Data management accross several models Database tool (In the cloud)

15 Let s go to work in Autodesk Revit Architecture!

16 Program validation Critical important process for both the design team, the constructor and the client. Is important from start to end of the project in order to meet project goals Involves validation of programmed area vs designed area, rooms, detailed room requirements (Room Data Sheets), FF&E, performance based requirements, Can be time consuming and source of errors in large projects. Program validation across multiple models can be difficult Public owners starts to require validation based on open data standards Let s see how an embedded IFC model server can do it!

17 Data Export / data exchange Several exchanges for different purposes, e.g. BPie, HVACie, COBie.. The future (already today) is about data export on open data formats, required primarily from public owners This requires processes and tools that support: Collection of large amounts of data from many sources Import and export on open data formats Let s see how project data can be exported to IFC/COBie

18 Implementation Examples Large Hospital Project, Norway New Østfold Hospital, Norway. 900,000 sqft HOK Firm Wide BIM Manager Greg Schleusner

19 Autodesk, AutoCAD* [*if/when mentioned in the pertinent material, followed by an alphabetical list of all other trademarks mentioned in the material] are registered trademarks or trademarks of Autodesk, Inc., and/or its subsidiaries and/or affiliates in the USA and/or other countries. All other brand names, product names, or trademarks belong to their respective holders. Autodesk reserves the right to alter product and services offerings, and specifications and pricing at any time without notice, and is not responsible for typographical or graphical errors that may appear in this document., Inc. All rights reserved.