Construction Management 2005 New Challenges and Opportunities with High Tech Projects

1
Construction Management 2005New Challenges and
Opportunities with High Tech Projects

• International SuperconferenceLondon, UK May
  2005The London Radisson SAS Portman Hotel

2
Agenda

• How they did it before 3D
• Why Mechanical Design Process Plant is 3D, but
  Architectural (i.e. buildings) Construction isnt
• Business benefits of extra dimension(s)
• Reality not Theory Case Studies
• 3D in Process Plant
• Workflow and Process
• Potential Issues from using 3D

3
How did they typically do it?

• Whats an ortho(graphic)?
• aka floor plan layout

4
How did they typically do it?

• Whats a PID?
• Process Instrumentation Drawing (Diagram)

5
How did they typically do it?

• Whats an iso(metric)?
• spool drawing.

6
So Why 3D?
7
Mechanical Process Plant v AEC

• Mechanical one stakeholder, one design format,
  one design team, shared goal, united business
  drive. 3D
• Process Plant one design team, one stakeholder,
  highly engineered. 3D
• AEC multiple stakeholders, disparate design
  team using multitude of design formats,
  individual goals, self preservation business
  drive. 2D, but 3D is coming

8
Money from the Third Dimension- Aspirations

• The Egan report identified improvement targets
• 10 reductions in capital cost and construction
  time annually
• 20 reduction in defects and accidents
• 10 increase in productivity and profitability
• 10 increase in predictability of project
  performance as targets.

9
Money from the Third Dimension- Aspirations

• A code of procedure for the construction
  industry produced by CPIC (UK) gives estimated
  10 saving of the contract sum by producing
  interference free production documentation

10
Money from the Third Dimension - Quantitative

• The NIST report (USA) of August 2004 gave a
  figure of 15.8 Billion wasted by US construction
  industry through poor collaboration on projects
• KLM project compared 2D to 3D in a quantitative
  study. Investment of 80K (software and
  training) gave return of 10 savings on the
  project 600,000 71 ROI

11
3D, 4D, nD

• 3D brings understanding, collaboration,
  communication, builds reusable data and speeds
  decisions for every stakeholder
• Adding 4D Time offers buildability checking,
  workflow planning, enhanced communication, forces
  human change (Planner talking to Designer)
• Adding costs, risk, etc (5D?) brings in more
  stakeholders, lessens conflicts

12
Single Building Model

• Lifecycle use
• Data added at every stage is usable during
  lifetime
• Reduces understanding hurdles between lifecycle
  phases
• Bid Design - Plan Build Manage
• Same model throughout

13
3D CAD Project Benefits

• Design
• Multi-discipline design environment
• Consistency of design data
• Automatic deliverable production
• Construction
• Clash detected design
• Visualisation
• Construction status
• Operations and maintenance
• Effective data handover
• Online visualisation
• Maintain design integrity

14
Consistency of Design Data

• Data exchange with other systems
• IPID data transfer to 3D CAD model
• Pipe stress analysis
• Material management system
• Sub contractor interfaces
• Specification and parametric driven design
• Enforces standards methodology
• Utilises specs and catalogues

15
Automatic deliverable production

• Plot plans
• Fabrication drawings
• Layout drawings
• MTOs
• Reports

16
3D in Action

• BAA T5
• Complex project, variety of formats
• Use of NW as collaborative medium
• Lifecycle use (Maximo asset management)
• Checking design, not detection

17
3D in Action

• Lucas
• No Change orders
• Saved gt 2M on the project by using virtual model
• 4D use

18
4D in Action
19
Construction Materials Status
20
4D in Action
21
(No Transcript)
22
(No Transcript)
23

Design

• Multi-discipline design environment
• Design modelling of all engineering disciplines
• Concurrent engineering
• Rapid production of project deliverables
• Visualisation
• On-going clash detection

24
(No Transcript)
25
(No Transcript)
26
(No Transcript)
27
Construction

• Clash detected design
• Minimise field re-work
• Visualisation
• Component location surrounding items
• Construction status

28
Construction Status
Fabrication
Primavera
Procurement
PDS Data
Construction
Query from Integrated Construction Database and
highlight/isolate in the model
Integrated Construction Information
OR
Pick object in the model and get information
from the Construction Database
29
Workflow Process
30
Use of 3D

• Delivers quantifiable business benefits
• Improves design quality
• Reduces waste
• Compresses schedule
• Enables collaboration
• Provides accountability
• Can force human process change and lessen
  confrontation

31
Operations and Maintenance

• Effective data handover
• Interface to operations system SAP/PDS
  database/INTools/EDMS
• Online visualisation
• Maintain design integrity
• Ongoing modifications

32

• Technology is only an enabler for human process
  change.

33
It seemed like a good idea at the time

• ...and it still is, but
• Real world applications, consequences and
  questions.

34
Transfer of Electronic Design Information

• Traditionally, contract documents include hard
  copy versions of final drawings and
  specifications. These are
• Un-editable,
• non-alterable, and
• difficult to transfer to another project or
  party.
• Protects the designer from mis-use or
  misapplication of the design on another project.
• Typically contractual provisos against such use.

35
Is the model to be considered...

• ...a part of the contract documents?
• details? Specifications? FRS? sequence of
  operation?
• ...the source of the contract documents?
• Iso-gens, ortho-gens, smart PIDs, Bill of
  Materials
• the product of design?
• Code or Regulatory Submissions, display model,
  marketing package
• a part of the design process
• charettes design workbooks, sketches, design
  studies

36
In the Electronic Documentation era, what level
of electronic is appropriate?

• In Construction - a freeze frame condition
• build this as shown at some time X
• Change Orders represent incremental movement of
  design intent\construction obligation over time
• build THIS as shown at Time X
• Limited need for real time interaction

37
In the Electronic Documentation era, what level
of electronic is appropriate?

• For Operations and Maintenance - more
  interactive
• What do we do if? How do we do it?
• normal operation on-line\off-line
• emergency operations (failure modes)
• service work around
• seasonal differences
• usage differences

38
In the Electronic Documentation era, what level
of electronic is appropriate?

• For Facility and Asset Management
• full interoperability is required for...
• Inventory
• Move Control
• Building Histories (as-builts)
• Energy ManagementOptimization
• Interconnection with other operations

39
The model in the context of the project

• As a part of the contract
• The model becomes a deliverable with a due date
  and a completion date.
• Models construction must meet the Standard of
  Care normally practiced within the profession
  perfection is not expected.
• As a source point for other drawings, the models
  quality ripples through other documents.
• When used in asset management, the impact of an
  error reaches further and lives beyond a single
  project.

40
The model in the context of the project

• When not a part of the contract
• the model is a tool, like sketch paper.
• no obligation to allow review or inspection by
  others
• no obligation to meet the Standard of Care in
  its production, but
• failure to do so could lead to E O claims
• As the project progresses, the model loses value
  as the gap between design and built
  increases.
• So what good is it?

41
One ScenarioThe Model as a part of the contract

• Does that include
• software to view it?
• to use it?
• (cost and training impacts, legacy issues)
• By whom? When? How?
• What do you build from?
• How?
• Who owns the errors?
• contractor shall verify vs. suitable for
  intended purpose

• a deliverable
• turned over to the owner
• must be useable
• must be accurate but perfection is not a
  reasonable expectation!
• used to create orthographic and isometric
  drawings.

42
When not a part of the contract

• like design development sketches
• Should a client pay extra?
• If he does, what are his rights to the
  intermediate work product?
• then, the model cant defend the designer
• What about insurance coverage?
• Practice safe designing!

• NOT deliverable!
• It is a tool.
• No obligation
• to allow review or inspection by others
• to meet the Standard of Care
• but, failure to do so could lead to E O claims

43
Things like Information missing from the model

• The field install shows a structural member that
  was required by the design shown on the
  structural drawings, but missing from the model,
  hence

44
Things like Incomplete database development

• The model shows ductwork, but database has no
  values, thus, the Interference (clash) check
  software will not see the ductwork and a clash
  results. Incomplete database leads to rework in
  the field.

45
Things like Incomplete design documentation

• The model shows vessel install, but not all of
  the piping and other items that will be present.
  The virtual arrangement is much less cluttered
  than the actual. Incomplete detailing leads to
  unforeseen difficulties which impacts on-going
  operation.

46
Other challenges in todays projects

• Speed of Delivery, User Flexibility
• Technology
• incorporating new changing on the fly
• Performance Expectations Specifications
• Environmental Quality
• Green Design
• IEQ
• Operational Efficiency
• Environmental footprint

47
Speed and Functionality Drivers

• Modular Construction
• Time-to-market and technology drivers push
  modular construction solutions.
• Factory designed, fabricated and tested are
  these construction services or products?
• New ownership ideas
• Buy?
• Lease?
• Rent?
• Outsource?

48
Speed and Technology

• Projects
• with single source responsibility
• design, furnish, install (old school)
• transfer, operate, finance
• for non-infrastructure (newer)
• Super skids for
• proprietary and critical
  technology
• support operations utilities with
• ongoing service needs
• Adapts to technology changes

49
Environmental Drivers

• Operational Efficiency
• Energy
• HVAC
• Day lighting
• Controls
• Reliability
• Maintenance
• Efficiency and ambience' are NOT mutually
  exclusive.

50
Environmental Drivers

• Environmental footprint
• Site selection, development and orientation
• New concerns
• Storm Water
• Gray Water

51
Environmental Drivers

• Performance-based contracts
• Design-build on
• complex projects,
• high tech projects
• fast-track projects
• Concerns?
• Scope definition (without design)
• Quality definition, valuation, acceptance
• Sustainable Design
• When is green design just good design?
• Sustainability is measured over time.
• How do
  you balance
• design, construction operation
• against performance?
• Your mileage may vary

52
IEQ Indoor Environmental Quality

• Human Factors
• Comfort Quality Reliability Safety

53
Design and Scope Management

• Prescriptive Specifications
• Traditional design-bid-build execution
• Performance Specifications
• For design-build and on technology systems
  which change rapidly
• Unforeseen Conditions
• brownfield recovery for urban inner ring
  districts
• Environmental remediation
• Potential for Hazardous Materials

54
Project Execution Change Management

• Requests For Information in design-build
  execution, RFIs (theoretically) no longer exist.
  Clarifications of intent must be handled
  promptly to control scope creep or deviations.

55
Project Execution Change Management

• Shop Drawings as delivery shifts to
  performance basis, shop drawing control
  becomes more dependent upon PMO, CM and other
  outside review and approval.
• Clear definition of scope, goals and objectives
  at the start is more critical as there are fewer
  check points downstream.

56
AGC Protocol

• "Guidelines for the Use of Electronic
  Communication in Construction Contract
  Administration
• Purpose of the Guidelines is to permit parties to
  rely on electronic data, not just on paper
• Guidelines suggest that parties agree on concepts
  such as
• software for transmission of documents
• handling upgrades of software used
• electronic document version control
• Privacy
• indemnification
• There are practical difficulties in attempting to
  have all parties agree to use identical software.

57
Thanks for Coming

• Thanks to our speakers
• Robert Court
• Charles L. Brown
• Richard H. Lowe
• Robert A. Prentice
• E. Mitchell Swann
• Peter Thompson