SC Infrastructure Upgrade Initiative FY2002

1
FY 2002 Facilities Management Workshop
Science Laboratories Infrastructure Program
Updates
Barry Sullivan SLI Program Manager Office of
Science U.S. Department of Energy
October 24, 2002
2
SLI Program Funding
3
Science Laboratories Infrastructure Funding
(in thousands of dollars)
4
Continuing Resolution (CR)

• Current Resolution runs through November 22
• Can not start any new projects
• No new FY 2003 design starts
• No new construction (FY 2002 design starts)
  starts can be initiated i.e. if FY 2003 is the
  first year of construction funding, no funding
  under CR
• Lame Duck session after election, outcome
  uncertain CR may go into January 03 or later
• Contracts may be bid under CR, no final awards
  are allowed

5
External Independent Reviews (EIRs)Independen
t Project Reviews (IPRs) Lessons Learned
6
Lessons Learned

• The Review Teams must follow Order 413.3
• Pick a point in the process (i.e. preliminary
  design complete) and ensure all presentations,
  documentation, etc. reflect this point
  consistently
• The HQ SLI project rep will coordinate
  communication between OECM, the review team
  leader, and the site
• Frequent communications between the contact
  points are essential to ensure all parties have
  what they need to meet the schedule
• Ensure all project schedules include sufficient
  time for CDs, EIRs, IPRs, etc.
• Provide all documentation requested prior to the
  review at the agreed upon date communicate
  schedule problems in a timely manner
• All stakeholders should be cognizant of the cost,
  scope and schedule being presented to the team

7
Lessons Learned(continued)

• Be professional at all times
• Team is doing a job requested by DOE the Team
  does not set agenda
• Information requested during review should be
  provided expeditiously or a date given when it
  will be provided
• Be receptive to suggestions or state that you
  will evaluate them
• Problems you have with the Team should be
  communicated to the SLI representative who will
  attempt to resolve the issue
• Ensure all projects have resource loaded
  schedules and a designated critical path
• Make individuals available during scheduled
  presentations and at informal sessions
• Provide short resumes highlighting applicable
  experience of primary project team members

8
Lessons Learned(continued)

• Ensure PEPs and AEPs meet the Order requirements
  and the associated memos these documents are
  used extensively by the Review Team
• Review the EIRs or IPRs from other labs and
  communicate with them to build on their
  experience

9
FY 2005 Projects
10
FY 2005 Project Review Schedule
11
Project Description Pointers

• Specific benefits are better than generalities.
  Good Examples
• Utility system is the only source of power to
  1500 users/researchers at the site.
• The system is averaging three failures per year
  and 30 hours of accelerator downtime and the
  failure rate is increasing (maintenance history
  is essential for making this case).
• Poor Examples
• The utility system is old and the failure rate is
  increasing.
• Building x is old and the systems are beyond
  their useful life and need to be replaced.

12
Project Description Pointers (cont)

• New OMB examiner is a former researcher at LANL
• As long as researchers have common eating area
  and conference area, they dont need to be
  co-located i.e. increased productivity
  associated with co-locating scientists was over
  rated
• I was in a trailer and it wasnt that bad.
• Bottom Line
• Stress inadequacy of facilities, not necessarily
  type
• Increased productivity associated with
  co-locating scientists should not be the main
  selling point of a project

13
Project Description Pointers (cont)

• Projects must be in your Strategic Facilities
  Plan
• HQ landlord Program must concur with your
  priorities
• Projects should be in 5-20M range
• SLI construction program covers 11 SC sites and
  has 31M in construction funding available i.e.
  there is only enough funding for 1-3 new starts
  per year