practical collaboration issues practice on major projects jackso… · · 2009-12-01• a...
TRANSCRIPT
Practical Collaboration Issues & Practice on Major Projects
Integrating IFC into the Process
AgendaAgenda
• IntroductionIntroduction
• Project Players – Maturity & Requirements
i i l bi d j• Big BIM – Little bim – Integrated Project Delivery
• Introducing a Common Data Environment
• The Federated Process & Using IFCsg
• Simplicity Please
IntroductionIntroduction
• Experience on major project programmespe e ce o ajo p oject p og a es• Now being implemented so born of experience• A practical view using IFC as an integrated part ofA practical view using IFC as an integrated part of the solution
• Based on some good practice learned on projects g p p jsuch as London CrossRail
• Overcoming the issues of an immature industry and technologies
• Scalable for the Future
CAD MaturityCAD Maturity
Courtesy of Mark Bew & M Richards Building Smart UK
Issues on Major Project ProgrammesIssues on Major Project Programmes
• Bentley have been commissioned on a number of ymajor project programmes to deliver LifeCycleData Management Solutions
• We have had to deal with this maturity model• 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 environmentyet work in this environment
• Building Smart IFCs can provide our baseline protocols for this deliveryp y
W f d i h D i dWe were faced with a Desired Project Data Strategyj gy
• 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 andonce 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
HOW CANWE DELIVER THISCan we do ‘Business as Usual’?
HOW CAN WE DELIVER THIS STRATEGY?
What’s Needed?What s Needed?CREATESHARE
PUBLISH RECORD
• The industry has struggled with information management on infrastructureThe industry has struggled with information management 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 trustedA 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
Coordination & CollaborationCoordination & CollaborationCommercial Operational
Business Systems
Financial EDMS
2D CAD
Project Collaboration
Lifecycle Coordination
3D CAD
CollaborationCoordination
BIM
GIS FM
Coordination & CollaborationCoordination & CollaborationCommercial Operational
Business Systems
Financial EDMS
2D CADDocument Control
Review and Acceptance
Project Collaboration
Lifecycle
Coordination
3D CADProject Control
CollaborationCoordination
BIM
Hosted
Tender Control
GISHosted service
FM
BIG BIM or little bimBIG BIM or little bim
BIG BIMLittle bim
• Software to model a building in 3D • Uses standard components that can be
BIG BIM
Building Information Modelling is…..........…not Just About Buildings!…however it is about…Si l S f T thUses standard components that can be
parametrically changed• Components are interdependent and
connect intelligentlyC bli h d i d ti
• Single Source of Truth• Interoperability• Coordination• Consistency• Connected Working• Can publish drawings and sections
automatically• Drawings change as the model changes
so no more having to change a section, l l ti i di id ll d
• Connected Working• Informed Design Decisions• Reusing Design Data• Locating Data Quickly & Effectively• Visualisation in Contextplan, elevation individually and
synchronise• Components have properties and can
be scheduled
Visualisation in Context• Streamlining Design Decisions• Increasing Productivity• Reducing Risk• Improving Profit
• Data can be extracted for quantitiesp g
IntroducingA COMMON DATA ENVIRONMENT
IntroducingA COMMON DATA ENVIRONMENT
APPROACH
Common Data Environment BasicsCommon Data Environment Basics• Based on UK BS 1192:2007
A D t St d d th th D i St d d• A Data Standard rather than a Drawing Standard• Collaborative Model Approach• Model Building & Content Standards
D T f S d d (IFC )• Data Transfer Standards (IFCs etc)• Spatially Correct
– Common Grid and Common Origin for all Data with defined Map Transformations
D i P bli ti f M d l• Drawings are Publications from Model• Federated Data Modelling • A ‘Nested Container Based’ data hierarchy
Fil id ifi b d i hi h• File identifiers based on container hierarchy• Data Classified in Layers• Tools Protocols and Processes for collaboration
The collaboration environmentThe collaboration environment
COLLABORATESharing content and
monitoring performance
MANAGE
Location of contentand access
CREATEMove content into data environment for reuse, distribution,
DELIVERGet the right content to the right audience in the right form
and storageform
PRESERVELong‐term archive and storage of essential
content
The ComplexitiesThe Complexities
Hybrid DataHybrid Data
Our SolutionOur Solution• Permit multiple source data• Set delivery standards
– Modelling Basics– Model Contents at Stages
• Use IFCs amongst other solutions to import to a Shared EnvironmentUse 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
Bentley IFC White PaperBentley IFC White Paper
Bentley Architecture was ycertified by the IAI as compliant with the Extended Coordination View of IFC2x3 Step 1 inView of IFC2x3 Step 1 in June 2006 and Step 2 compliant in March 2007
Google… “Bentley IFC White Paper”
Generate Integrated Views SpacevalidationGenerate Integrated Views validation
E i t
Bentley Building Mechanical Systems Bentley Architecture
Equipmentregistry
GSA Concept Design View COBIE
“IFC” data exchange• Focused on downstream analysis and data• Focused on downstream analysis and data repurposing where appropriate; many‐to‐many application data exchange and BIM coordination
Concrete walls
Geometry plus data in native modelling format
Data export configured to suit Concrete walls
Wall 1 4.6m3
Wall 2 5.8m3
Total 10.4 m3
‐ file name‐ unique ID‐ classification‐ overall height‐ overall width‐ thickness
p gintended use
Source BIM
‐ etc
Summary lists
For input to specialist analysis software
IFC export
For manual analysis of data
Detailed list
Sub set of data and geometry from source BIM
Set Data Content Development
I f ti l l Obj t tt ib t d t
Set Data Content Development Standards
Information level Construction object type Object attribute data
Key
Primary areas of focus
Secondary area of focus
te uild
ing
exte
nts
uild
ing
oom
s
uild
ing
elem
ents
nish
es
unct
ion
eom
etry
/loca
tion
uild
ing
phys
ical
dat
a
oces
s da
ta
oduc
t dat
a
pera
tiona
l dat
a
Sit
Bu
Bu
Ro
Bu
Fin
Fu Ge
Bu
Pro
Pro
Op
1. Pre-design
2. Concept
3. Schematic design
4. Detailed design
5. Construction documents
6. Tender
7 Construction7. Construction
8. Defects liability
DATA LIFECYCLEDATA LIFECYCLE
Data Lifecycle ProcessData Lifecycle ProcessCommon Data Environment
Data Lifecycle ProcessData Lifecycle ProcessCommon Data Environment
Work in progressWIP
Non‐verified data d bused by one team
only
Data Lifecycle ProcessData Lifecycle ProcessData Environment
Work in progressWIP
Non‐verified data d b
Share
Verified data that can be sharedused by one team
onlycan be shared between teams
Document
Published Coordinated and validated data
Data Lifecycle ProcessData Lifecycle ProcessCommon Data Environment
Work in progressWIP
Non‐verified data d b
Share
Verified data that can be sharedused by one team
onlycan be shared between teams
Document
Published Coordinated and validated data
Archive
Data maintained for knowledge and
legacy
DataLifecycle ProcessDataLifecycle Process
PRODUCTION DELIVERABLE OUTPUT
Project/Programme ControlledLocal ControlData Created in U S t
COORDINATEDPRIVATE CREATE PUBLISHED STORED
j / gData in Project/Programme Lingua Franca
Users Systems and Formats
Work in progressWIP
Non‐verified data used by one team
Document
Published Coordinated and
Share
Verified data that can be shared
Archive
Data maintained for knowledge and
used by one team only validated data
can be shared between teams legacy
How do we move out of silos?
Work in progressWIP Share
COORDINATEDPRIVATE CREATE
Native Format
Non‐verified data used by one team
only
Non Silo’d Verified data that can be shared between
teamsTranslated Format
Team 1
IFC Transport
Team n
THE FEDERATED PROCESSTHE FEDERATED PROCESS
A Simplified View
CDE Lifecycle ProcessCDE Lifecycle ProcessWork in progress
WIP DocumentShare Archive
Non‐verified data used by one team
only
Published Coordinated and validated data
Verified data that can be shared between teams
Data maintained for knowledge and
legacy
Creation ‐WIPCreation WIPWork in progress
WIP DocumentShare Archive
Non‐verified data used by one team
only
Published Coordinated and validated data
Verified data that can be shared between teams
Data maintained for knowledge and
legacy
Team 1
SHARING with other TeamsSHARING with other TeamsWork in progress
WIP Share
Non‐verified data used by one team
only
Verified data that can be shared between teams
SHARETeam 1
Transform to SHARETransform to SHARE
Referencing SHARED DataReferencing SHARED DataWork in progress
WIP Share
Non‐verified data used by one team
only
Verified data that can be shared between teams
SHARETeam 1
Team 2
Reference
Team 2 Adding DataTeam 2 Adding DataWork in progress
WIP Share
Non‐verified data used by one team
only
Verified data that can be shared between teams
SHARETeam 1
Team 2
Team 2 SHARINGTeam 2 SHARINGWork in progress
WIP Share
Non‐verified data used by one team
only
Verified data that can be shared between teams
SHARETeam 1
Team 2
Transform to SHARE
Publishing & DocumentingPublishing & DocumentingWork 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
SHARETeam 1
PUBLISHfor
Deliverable
Team 2
Publishing & DocumentingPublishing & DocumentingWork 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
SHARETeam 1
PUBLISHFor
Production
PUBLISH
Team 2
Team 3 to n ‐ ContributingTeam 3 to n ContributingWork 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
SHARETeam 1 PUBLISH
Team 2
Team 3
Team n
Change Request or RejectionChange Request or RejectionWork in progress
WIP Share
Non‐verified data used by one team
only
Verified data that can be shared between teams
SHARETeam 1
Team 2
Team 3
Team n
Change RequestRequest
Change Request or RejectionChange Request or RejectionWork in progress
WIP Share
Non‐verified data used by one team
only
Verified data that can be shared between teams
SHARETeam 1
Team 2
ChangeState toSH
ARE
Team 3
Team n
Change Request
eo Request
Change Request or RejectionChange Request or RejectionWork in progress
WIP Share
Non‐verified data used by one team
only
Verified data that can be shared between teams
SHARETeam 1
Team 2
ChangeState toSH
ARE
Team 3
Team n
Change Request
eo Request
Federated SummaryFederated 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• 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 informationp j• Makes project data available in a controlled environment• Avoids Collaboration by TWITTER
ConclusionConclusion
• 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
sharedshared.• Sharing information reduces the time and cost in producing
coordinated information.• Any number of documents can be generated from different• 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 g ginformation.
• Design information can be reused for construction planning, estimating, cost planning, facilities management and other down stream activitiesstream activities.
Simplicity PleaseSimplicity Please
• The real issue is peopleThe real issue is people
• WE must make these standards more approachable to the industryapproachable to the industry
• When it becomes simple the industry will f llfollow
• The technology should be transparent.
SummarySummary