Practical Collaboration Issues & Practice on Major Projects. Integrating IFC into the Process

Transcription

1 Practical Collaboration Issues & Practice on Major Projects Integrating IFC into the Process

2 Agenda Introduction Project Players Maturity & Requirements Big BIM Little bim Integrated Project Delivery Introducing a Common Data Environment The Federated Process & Using IFCs Simplicity Please

3 Introduction Experience e on major project poga programmes Now being implemented so born of experience A practical view using IFC as an integrated part of the solution Based on some good practice learned on projects such as London CrossRail Overcoming the issues of an immature industry and technologies Scalable for the Future

4 CAD Maturity Courtesy of Mark Bew & M Richards Building Smart UK

5 Issues on Major Project Programmes Bentley have been commissioned on a number of major project programmes to deliver LifeCycle Data Management Solutions We have had to deal with this maturity model and find ways to deliver data safely for coordination, collaboration throughout the project lifecycle The concept of a Single Building Model does not yet work in this environment Building Smart IFCs can provide our baseline protocols for this delivery

6 We were faced with iha Desired Project Data Strategy To create an integrated design, facilitating multidisciplinary coordination & collaboration throughout the life of the project, becoming the base for an asset management system To collect data at its point of creation and enter that data once only and then allow it to be used and improved, and passed along to others through the life cycle of the facility. To make data entry and data maintenance part of the business process and not a separate step

7 Can we do Business as Usual? HOW CAN WE DELIVER THIS STRATEGY?

8 What s Needed? SHARE CREATE PUBLISH RECORD Theindustryhasstruggled has struggled with informationmanagementmanagement on infrastructure projects for a long time Some are well managed using model data instead of electronic paper A framework is needed that enables the industry to share data in a trusted environment A common glue to exchange information Technology can enable this but it needs a managed framework for users to operate in

9 Coordination & Collaboration Commercial Operational Financial Business Systems EDMS 2D CAD 3D CAD Lifecycle Coordination Project Collaboration BIM GIS FM

10 Coordination & Collaboration Commercial Operational Financial Business Systems EDMS 2D CAD Document Control Review and Acceptance 3D CAD Lifecycle Coordination Project Collaboration Project Control BIM Tender Control GIS FM Hosted service

11 BIG BIM or little bim

12 Little bim Software to model a building in 3D Uses standard components that can be parametrically changed Components are interdependent and connect intelligently Can publish drawings and sections automatically Drawings change as the model changes so no more having to change a section, plan, elevation individually id and synchronise Components have properties and can be scheduled Data can be extracted for quantities BIG BIM Building Information Modelling is... not Just About Buildings! however it is about Single Source of Truth Interoperability Coordination Consistency Connected Working Informed Design Decisions Reusing Design Data Locating Data Quickly & Effectively Visualisation in Context Streamlining Design Decisions Increasing Productivity Reducing Risk Improving Profit

13 Introducing A COMMON DATA ENVIRONMENT APPROACH

14 Common Data Environment Basics Based on UK BS 1192:2007 A Dt Data Standard d rather than a Drawing Standard d Collaborative Model Approach Model Building & Content Standards Data Transfer Standards d (IFCs etc) Spatially Correct Common Grid and Common Origin for all Data with defined Map Transformations Drawings are Publications from Model Federated Data Modelling A Nested Container Based data hierarchy File identifiers ifi based on container hierarchyh Data Classified in Layers Tools Protocols and Processes for collaboration

15 The collaboration environment COLLABORATE Sharing content and monitoring performance CREATE Move content into data environment for reuse, distribution, and storage MANAGE Location of content and access DELIVER Get the right content to the right audience in the right form PRESERVE Long term archive and storage of essential content

16 The Complexities

17 Hybrid Data

18 Our Solution Permit multiple source data Set delivery standards Modelling Basics Model Contents at Stages Use IFCs amongst other solutions to import to a Shared Environment Work inside Bentley ProjectWise Managed Environment Capture IFC file as a deliverable Test Limits Use Bentley IFC import capability to transform into data Add to non IFC Data Deliver a Hybrid Single Source of Truth in Bentley Solution Build into the Project Standards & Protocols Federate the Resulting Data

19 Bentley IFC White Paper Bentley Architecture was certified by the IAI as compliant with the Extended Coordination View of IFC2x3 Step 1 in June 2006 and Step 2 compliant in March 2007 Google Bentley IFC White Paper

20 Generate Integrated Views Space validation Bentley Building Mechanical Systems Bentley Architecture Equipment registry COBIE GSA Concept Design View IFC data exchange Focused on downstream analysis and data repurposing where appropriate; many to many application data exchange and BIM coordination

21 Geometry plus data in native modelling format Data export configured to suit intended use Source BIM Concrete walls Wall 1 4.6m 3 Wall 2 5.8m 3 Total 10.4 m 3 file name unique ID classification overall height overall width thickness etc For manual analysis of data For input to specialist analysis software Sub set of data and geometry from source BIM Summary lists Detailed list IFC export

22 Set Data Content Development Standards Information level l Construction object type Object attribute t data Key Primary areas of focus Secondary area of focus Sit te Bu uilding extents Bu uilding Ro ooms Bu uilding elements Fin nishes Fu unction Ge eometry/location Bu uilding physical data Pro ocess data Pro oduct data Op perational data 1. Pre-design 2. Concept 3. Schematic design 4. Detailed design 5. Construction documents 6. Tender 7. Construction 8. Defects liability

23 DATA LIFECYCLE

24 Data Lifecycle Process Common Data Environment

25 Data Lifecycle Process Common Data Environment Work in progress WIP Non verified data used by one team only

26 Data Lifecycle Process Data Environment Work in progress WIP Non verified data used by one team only Share Verified data that can be shared between teams Document Published Coordinated and validated data

27 Data Lifecycle Process Common Data Environment Work in progress WIP Non verified data used by one team only Share Verified data that can be shared between teams Archive Data maintained for knowledge and legacy Document Published Coordinated and validated data

28 DataLifecycle Process PRODUCTION DELIVERABLE OUTPUT Local Control Data Created in Users Systems and Formats Project/Programme Controlled Data in Project/Programme Lingua Franca PRIVATE CREATE COORDINATED PUBLISHED STORED Work in progress WIP Non verified data used by one team only Share Verified data that can be shared between teams Document Published Coordinated and validated data Archive Data maintained for knowledge and legacy

29 How do we move out of silos? PRIVATE CREATE Work in progress WIP Non verified data used by one team only Native Format Translated Format COORDINATED Share Non Silo d Verified data that can be shared between teams Team 1 IFC Transport Team n

30 THE FEDERATED PROCESS A Simplified View

31 CDE Lifecycle Process Work in progress WIP Non verified data used by one team only Share Verified data that can be shared between teams Document Published Coordinated and validated data Archive Data maintained for knowledge and legacy

32 Creation WIP Work in progress WIP Non verified data used by one team only Share Verified data that can be shared between teams Document Published Coordinated and validated data Archive Data maintained for knowledge and legacy Team 1

33 SHARING with other Teams Work in progress WIP Non verified data used by one team only Share Verified data that can be shared between teams Team 1 SHARE Transform to SHARE

34 Referencing SHARED Data Work in progress WIP Non verified data used by one team only Share Verified data that can be shared between teams Team 1 SHARE Team 2 Reference

35 Team 2 Adding Data Work in progress WIP Non verified data used by one team only Share Verified data that can be shared between teams Team 1 SHARE Team 2

36 Team 2 SHARING Work in progress WIP Non verified data used by one team only Share Verified data that can be shared between teams Team 1 SHARE Team 2 Transform to SHARE

37 Publishing & Documenting Work in progress WIP Share Document Non verified data used by one team only Verified data that can be shared between teams Published Coordinated and validated data Team 1 SHARE PUBLISH for Deliverable Team 2

38 Publishing & Documenting Work in progress WIP Share Document Non verified data used by one team only Verified data that can be shared between teams Published Coordinated and validated data Team 1 SHARE PUBLISH PUBLISH For Production Team 2

39 Team 3 to n Contributing Work in progress WIP Share Document Non verified data used by one team only Verified data that can be shared between teams Published Coordinated and validated data Team 1 SHARE PUBLISH Team 2 Team 3 Team n

40 Change Request or Rejection Work in progress WIP Non verified data used by one team only Share Verified data that can be shared between teams Team 1 SHARE Team 2 Team 3 Team n Change Request

41 Change Request or Rejection Work in progress WIP Non verified data used by one team only Share Verified data that can be shared between teams Team 1 SHARE Team 2 Team 3 Change State to SHARE Team n Change Request

42 Change Request or Rejection Work in progress WIP Non verified data used by one team only Share Verified data that can be shared between teams Team 1 SHARE Team 2 Team 3 Change State to SHARE Team n Change Request

43 Federated Summary Using Standard Bentley Tools & their IFC compliance Presents a Single Source of Truth for the Project Not a milestone post box Permits Cross Project Data Sharing Avoids massive single models Takes advantage of the power of IFCs Can develop as IFCs develop Lets each party concentrate on their task but share the benefit of other project information Makes project data available in a controlled environment Avoids Collaboration by TWITTER

44 Conclusion Using IFC has provided a path out of Silos Integrates IFC data with the multiple sources of data on programmes Ownership of information remains with the originator although it is shared. Sharing information reduces the time and cost in producing coordinated information. Any number of documents can be generated from different combinations of model files. Spatial co ordination becomes a by product of using the collaboration environment and will deliver right first time design information. Design information can be reused for construction planning, estimating, cost planning, facilities management and other down stream activities.

45 Simplicity Please The real issue is people WE must make these standards more approachable to the industry When it becomes simple the industry will follow The technology should be transparent.

46 Summary