Design Review Competing Needs: Limited Resources

1
Design ReviewCompeting Needs Limited
Resources

• Eric Albert, Plant Operations-UPE
• Tom Girard, Plant Extension-AEC
• David Karle, Plant Extension-AEC

2
Purpose

• To give a brief overview of the design process
  and how we address sometimes conflicting
  stakeholder needs

3
Design Review Goals

• To meet the construction project needs with the
  funds available.
• To facilitate F O in achieving this goal.

4
Stakeholder Needs

• Occupant/User
• Maintenance and Operations
• Administration (including FO)

5
Stakeholder-Occupant/User

• Projects that meet their program requirements
  managed wants and desires
• Stay within available funding
• Flexibility for future
• Schedule requirements
• Minimal disruption from maintenance -
  reliability, maintenance access
• Conduct business during construction - interim
  space, noise constraints
• Reasonable operating costs

6
Stakeholder-Maintenance Operations

• Building systems that can be operated and
  maintained with funds available
• Long term quality
• Low life cycle cost
• Retire items beyond life (FCA)

7
Stakeholder-Administration (including FO)

• Aesthetic image
• In keeping with long term plans
• Fiscal responsibility
• Code accountability - life safety
• Stewardship - sustainability
• Efficient design process that prevents undue
  delay
• Security

8
Conflict and Compromise

• Dichotomies
• and
• Trichotomies

9
Conflicts

• Low first cost -v- Low life cycle cost
• Mechanical/Electrical Space -v- Program Space
• Project scope and budget -v- Infrastructure
  renewal needs
• Aesthetics -v- Utilitarian Function
• Aesthetics -v- Cost (first and LCC) -v- Energy

10
Conflicts ...

• Cost (first and LCC) -v- Future Flexibility
• Code and Safety -v- Program
• Resolving Dichotomies -v- Design Schedule and
  Cost (A/E fees)
• Sustainability -v- Cost -v- Quality
• Quality -v- Cost -v- Schedule

11
Laws of Construction

• Fast, cheap or good - pick two
• In conflicts between the laws of physics and the
  laws of economics, physics always wins.

12
Keys to Project Success

• Acknowledge, address and resolve conflicts as
  early as possible in the design process
• Strive for the synergy of Win-Win solutions

13
An Ideal Design Process

• Programming
• Schematic Design
• Design Development
• Construction Documents

14
Programming

• Needs of all stakeholders are identified,
  including infrastructure

15
Schematic Design

• Governing codes and standards for design are
  established, potential variances identified
• Preliminary floor plan options are explored to
  meet program needs
• Design criteria, preliminary calculations,
  studies (LCC), and estimates are developed
• Dichotomies must be identified plan and schedule
  developed for resolving

16
The Age-Old Conflict
17
Design Development

• Dichotomies and fundamental design decisions are
  resolved and documented in Design Intent
• Design documents are prepared based on decisions
  made-decisions focused on resolving dichotomies
• Floor plan and system design concepts are set
• Code and standard variances are addressed

18
Construction Documents

• Final design progresses and dichotomy decisions
  are affirmed based on Design Intent, refined
  calculations and cost estimates.
• Final spatial coordination and construction
  details are completed.
• Ideally, review is limited to errors and
  omissions, not last minute redefinition of needs.

19
Summary

• Identify conflicts and schedule for resolution as
  early in design process as possible.
• Develop case studies and standards to streamline
  design and value engineering decision-making
• Focus analysis on Life Cycle Cost wherever
  possible
• Strive for Win-Win resolution of conflicts
• Resolving challenges such as ...

20
Challenges

• Getting appropriate manpower and resources
  allocated early in design process
• Defining roles and responsibilities of project
  team
• Updating Design Guidelines to support project
  design management

21

• Question and Answer