OOI Network Program Management

Rosie Heatley Lunde

Project Management Documents

•The Project Execution Plan (PEP) for the Ocean Observatories Initiativedescribes how JOI will manage the OOI project in accordance with MREFCguidelines.

•The PEP provides an overview of NSF expectations that specifically bear onproject management practices:

-- Work Breakdown Structure-- OOI Project Baseline-- Earned Value Management System-- Risk Management Plan

•The initial issue of the PEP contains information at a level that is appropriatefor a conceptual design.

•Each IO will develop a PEP for its activities which will be incorporated byreference into the OOI Network PEP.

•The Project Development Plan (PDP) for the Ocean Observatories Initiativedescribes the way forward to the OOI Preliminary Design Review in April 2007.

OOI Work Breakdown Structure for CDR

Work Breakdown Structure with Budget Numbers

1.0 Ocean Observatories

Initiative (OOI) Work

Breakdown Structure

$309.5 FY06M

1.1 OOI Network IO (JOI) 1.2 Cyberinfrastructure

(CI)

1.3 Coastal Scale

Observatory (CSO)

1.4 Regional Cabled

Observatory (RCO)

1.5 Global Scale

Observatory (GSO)

1.6 Maintenance and

Operations

$75.3 $25.3 $51.6 $120.4 $36.9

1.1.1 OOI Network

Project Management

1.2.1 CI IO Project

Management

1.3.1 CSO IO Project

Management

1.4.1 RCO IO Project

Management

1.5.1 GSO IO Project

Management

$7.0 $4.0 $2.0 $4.0 $2.0

1.1.2 OOI Network

Systems Engineering

1.2.2 CI Systems

Engineering

1.3.2 CSO Systems

Engineering

1.4.2 RCO Systems

Engineering

1.5.2 GSO Systems

Engineering

$8.0 $5.0 $4.0 $4.0 $4.0

1.1.3 Education and

Public Outreach

1.2.3 Software

Development

1.3.3 CSO Software

Development

1.4.3 RCO Software

Development

1.5.3 GSO Software

Development

$5.0 $8.0 $2.0 $4.0 $2.0

Project Contingency 1.2.4 CI Hardware

Development

1.3.4 CSO Hardware

Development

1.4.4 RCO Hardware

Development

1.5.4 GSO Hardware

Development

$55.3 $2.0 $1.2 $6.0 $1.8

1.3.5 CSO Shore

Facilities

1.4.5 RCO Shore

Facilities

$0.6 $9.5

1.2.5 CI Implementation 1.3.6 CSO

Implementation

1.4.6 RCO

Implementation

1.5.5 GSO

Implementation

$6.3 $41.8 $92.9 $27.1

OOI Network CDR Baseline

•The OOI Project CDR Baseline consists of:-- CDR Technical Baseline-- CDR Cost Baseline-- CDR Schedule Baseline

•The OOI Project Baseline will be controlled through the OOI ConfigurationManagement and Change Control Plan.

•NSF has the sole authority to revise any of the baselines.

•The OOI Network CDR Technical Baseline is the Conceptual Network Design(CND) which was described in the previous four presentations.

OOI Network CDR Cost Baseline(Millions of 2006 Dollars)

$309.5$36.9$120.4$51.6$25.3$75.3TOTAL

$55.3----$55.3Contingency

$5.0----$5.0Education

$168.1$27.1$92.9$41.8$6.3-Implementation

$10.1-$9.5$0.6--Shore Facilities

$11.0$1.8$6.0$1.2$2.0-Hardware

$16.0$2.0$4.0$2.0$8.0-Software

$25.0$4.0$4.0$4.0$5.0$8.0Systems Eng

$19.0$2.0$4.0$2.0$4.0$7.0Project Support

TOTALGSO IORCO IOCSO IOCI IOProgramOffice

•Detailed cost tables are available for each Implementation cell.

•Contingency has been estimated for each cell in the budget table by applyinga top down analysis.

Basis of OOI Network CDR Cost Baseline

•The CND contains detailed cost breakouts for each Implementation site. Most ofthese costs are well understood and based on price lists, quotations, previouspurchases, and RFPs.

•The RCO Implementation cost is derived from actual costs associated with theNEPTUNE Canada supply contract with Alcatel.

•Historically, JPL estimates project management and systems engineering,combined, at 15% of the total project cost.

•Education dollars have been allocated and will be capped.

•The ORION Engineering Committee estimated Software and HardwareDevelopment based on their knowledge of past developments.

•Some high risk development activities on profiling moorings, AUV dockingstations, and bio-fouling resistant sensors are planned to be funded separately byNSF.

OOI Contingency Assessment – Top Down

$55.3$309.5$36.9$120.4$51.6$25.3$75.3TOTAL

$55.3----$55.3Contingency

Scope$0.00%$5.0----$5.0Education

Experience$34.320%, 30% (CI)$168.1$27.1$92.9$41.8$6.3-Implementation

Experience$1.515%$10.1-$9.5$0.6--Shore Facilities

Development$3.330%$11.0$1.8$6.0$1.2$2.0-Hardware

Open Source$4.020%, 30% (CI)$16.0$2.0$4.0$2.0$8.0-Software

Interfaces$7.530%$25.0$4.0$4.0$4.0$5.0$8.0Systems Eng

People Costs$4.825%$19.0$2.0$4.0$2.0$4.0$7.0Project Support

RationaleContingencyContingencyTOTALGSOIO

RCO IOCSOIO

CI IOProgramOffice

•Higher contingency assigned to CI because these costs were based on estimates rather thanquotations.

•New development activities were assigned a higher contingency.

•System Engineering was assigned a higher contingency due to the number of interfacingparties.

•When established, IOs will establish a bottom up view of cost, risk, and contingency.

OOI Network CDR Schedule Baseline

•The OOI Network is an ever-changing, ever-growing, and never-endingnetwork of observatories.

•How do we define “done”? How is a critical path determined forsomething that is continuously evolving?

•Purdue’s center of excellence in System of Systems engineering told usthat, in their opinion, no one has really figured out how to apply standardproject management schedule practices to this type of project.

•Hence, the OOI Network will be transformative within the MREFC projectmanagement guidelines!

•"It's a matter of definition." – Mark Coles, June 2006

OOI Primary, Secondary Node Nomenclature

Primary Node

Secondary Node

Sensors

OOI Network Interface for Schedule

OOI Network Schedule Definitions

•Primary Nodes are located in key areas of scientific interest (asdefined through the RFA process). Secondary nodes and sensors willevolve and change over time.

•Some secondary nodes and core sensors will be installed on the initialnetwork, but the absence of a core sensor would not indicate that thenode is not capable of providing scientific data.

•Therefore, the OOI Network is "complete" when theCyberinfrastructure is fully capable (Release 3) and all of the primarynodes are operating.

•However, a primary node is "complete" when the CI is functional(Release 1) and the node is capable of transmitting scientific data andreceiving instrument control commands via the CI.

Conceptual OOI Network Schedule

OOI Network:

CI:

CSO:

RCO:

GSO:

OOI Network Critical Path

•Primary nodes can complete anytime after Release 1 of the CI;therefore, Release 1 of the CI software is the critical path for theOOI’s first primary node.

•Additional primary nodes can complete in any order and at anytime, subject to budget, weather, development constraints.

•The RCO, because it uses most of the available OOI Networkbudget in the mid-years, will likely be the controlling factor intiming of the GSO and CSO node completion.

•The critical path for the OOI Network will be either Release 3 ofthe CI software or the latest scheduled primary node.

OOI Network Program Management

•The primary node definition will also help in discussion ofmaintenance, reliability, and other factors for the OOI network.

•Primary nodes can complete in any order and at any time. Thisflexibility is a feature that lowers the overall schedule risk for theOOI Network.

•Ultimately, the IOs will develop detailed schedules and milestoneswhich will allow the determination of the OOI Network critical pathand the critical path for each primary node.

“The Way Forward”

•The Project Development Plan details the activities for the preliminarydesign phase of the OOI Network.

•A major activity will be JOI's solicitation, awarding, and management ofthe Subawards for the Implementing Organizations.

•JOI will respond to the CDR action items and prepare for thePDR/Construction Review in April.

•JOI will prepare the Construction Proposal for the OOI Network.

•NSF will hold a workshop on current activities in Cyberinfrastructuretechnology.

•JOI will trial-run an Earned Value Management System and other projectmanagement software tools.

“The Way Forward – Continued”

•The Programmatic Environmental Assessment will continue with thedevelopment of the assessment document by SRI International undercontract from JOI.

•System engineering will refine the Science User Requirements toincorporate into the IO Subawards.

•System engineering will develop a Concept of Operations for the OOINetwork, including reliability, operations, and maintenance.

•JOI will work with Navy contacts to prepare detailed plans for thepotential use of the USNS Zeus for cable route survey work in early2007.

•JOI will work to accommodate a process for Navy review of the OOIand future OOI proposals.

CDR Continues!

•LUNCH!

•Review Team – Executive Session from 1:00 to 1:30

•OOI Network Team – Pep Rally from 1:00 to 1:30

•Break-out Rooms – 1:30 to 5:30

•Review Team – Executive Session from 5:30 to 6:00

•Social – 6:00 – Atrium of Building A, Second Floor

•Dinner – 7:00 – Phil’s Eatery