OOI Overview May 2015

1. OOI Overview May 2015

2. OOI Overarching Objectives • The design requirements of the OOI lead to three essential objectives: • Sustain, for decades, the delivery of multiple streams of ocean data, resolving ocean processes and properties across a range of temporal and spatial scales; • Facilitate the use of the designed capabilities of the OOI for specific at-sea experiments or extension of the temporal and spatial reach of ocean research; • Sustain the expansion capabilities of the observatory as technology evolves and in response to new science questions. 2

3. Scope of the OOI Four Global high latitude sites Station Papa Irminger Sea Argentine Basin Southern Ocean Two Coastal Arrays Endurance Array Pioneer Array Cabled Array Meso-scale, Plate Scale network CyberInfrastructure Acquisition, Storage, Processing, and Distribution of Data

4. OOI Organization Structure * CI transitions to full Rutgers leadership as OOI Net transitions to O&M

5. Significant Changes within OOI • January 2014, PMO took over direct management of CI-UCSD work effort due to concerns of inadequate progress towards delivery • February 2014, contracted with Raytheon to develop a rapid prototype, based on their Universal Framework (uFrame) service oriented architecture used by National Weather Service AWIPS II • June 2014, successful demonstration of uFrame prototype • July 2014, PMO decided to transition away from software being developed at CI-UCSD due to lack of adequate defect closure rate and concerns of future maintainability • July 2014, Rutgers begins transition to CI Implementing Organization • August 2014, Raytheon under contract for full development of uFrame with PMO acting as Implementing Organization with transition to Rutgers

6. Current priorities Manage the close out of Construction accounts across the project, assuring that sufficient funds remain to address the last emerging risks. Must align budget and staffing to only the most essential remaining work. Execute the transition to operations (second builds, first ‘turns’, shift to O&M $$) for all arrays

7. Coastal - Pioneer • Challenges • Technology • Fuel cell • AUV w/docking stations • Coastal surface piercing profiler • Environmental • Equipment loss from interaction with other ocean users

8. Coastal - Endurance • Challenges • Technology • Fuel cell • Coastal surface piercing profiler

9. Global - Papa • Surface piercing profiler removed at last maintenance replacement, Plan B to be developed • Open Ocean Glider problems, working with vendor to resolve • Profiler gliders to be installed at June 2015 maintenance cycle

10. Global - Irminger • Operating well with exception of Fleet Broadband on Surface Mooring which has not been operating since deployment • Open Ocean Glider problems, working with vendor to resolve • Profiler gliders not ready for deployment

11. Global – Southern Ocean, 55S • Operating well with exception of acoustic modem on Hybrid Profiler mooring • Open Ocean Glider problems, working with vendor to resolve • Profiler gliders not ready for deployment

12. Global – Argentine Basin • Operating well • Open Ocean Glider problems, working with vendor to resolve • Profiler gliders not ready for deployment

13. Cabled As of 5/1/2015 • Challenges • Technology • Deep profiler

14. Deployed Scope of OOI (over 800 instruments distributed over all moorings, benthic packages, seafloor nodes, gliders and AUVs) Global Arrays Coastal Arrays Cabled Arrays Cyberinfrastructure • Computing platforms, software applications, storage, and high speed network equipment • Cyber Points of Presence (CyberPoPs) • Acquisition Points • Distribution Points • Integrated Observatory Network – OOI Net • Hardware / Software • Redundant computing environment Connected by 880km of seafloor cable, with 10KW power, internet connectivity between 7 primary nodes, multiple secondary nodes, and all distributed instrumentation Extensive details about each component can be found on the OOI website (http://oceanobservatories.org)

15. CyberInfrastructure • Highlights • All data from deployed infrastructure is being stored, regardless of OOINet readiness level • OOINet has ingested data from deployed Pioneer moorings and gliders, Papa and Endurance gliders, as well as initial Build 1B Cabled instruments • Attempted to deliver pre-commissioned data via interim user interface, but resource drain was impacting ability to deliver production OOI Net • Rutgers staff has ramped up and will be ready to assume O&M role

16. Overall CI Architecture • Flexible network architecture • Decentralized network architecturewith 5 P2P connected sites (OMC-WHOI, OMC-OSU, OMC-SIO, RSN, CI-RU) • Independent administrative domains (e.g., IP space) • Supports both VPN and non-VPN configurations • Security • Short-term: traditional firewall system (iptables) • Long-term: Latest generation firewall appliances to consolidate security layers • External connections • Leverages institutional VPN infrastructure

17. CI - Build Descriptions • Build 1 • Proof of Concept • Ingests data, applies algorithms, provides data products • 23 sensors integrated • Build 2 • Data Management • Capability to record and manage deployed moorings and platforms • User Interface prototype • Plotting, charting, SW Management, landing page • Sensors/Algorithms • 35 New sensors/algorithms integrated • Build 3 • Data Management complete • Provenance tracking, life-cycle management • User Interface refinements • Manage user accounts, annotate data, update metadata, • Build 3 (cont) • User Interface (cont) • Prototype health status/monitoring, trouble ticket integration, operator turnover • Sensors/Algorithms • 12 New sensors/algorithms integrated • Build 4 • User Interface refinements • Command and Control prototype • Asset Management prototype • QA/QC analysis results, Alarms and Alerts, ERDDAP integration • Help/FAQ/Glossasry/Tool Tips • All Algorithms integrated • User Interface complete • Sensors/Algorithms • 31 New sensors/algorithms integrated • Build 5 • User Interface Complete • Sensors Complete • 31 New sensors/algorithms integrated • All builds include sensor drivers/parsers and algorithms • All builds post Build 1, include incremental UI functionality

18. OOI Net User Testing and Release • Alpha testing May 2015 • Based on OOI Net Build 4 • User consist of OOI Project Scientist and Operators, member of UNOLS OOSC, and NSF • Defined methodology for user feedback to software build team • Beta testing June 2015 • Based on OOI Net Build 5 • Alpha continue use of system • OOI work with NSF to define criteria for selection of Beta users with a linkage to upcoming proposals • Commissioned Release – September 2015

19. CI – Data Management • Pioneer mini-workshop held in February • Attendance OOI Team, invited external SMEs, UNOLS OOSC • Review of initial data and Rutgers proposed Quick Looks • Recommendations of proposed deep dives by Data Evaluators • Review of Data QA/QC algorithms • OOSC provided prioritized list of recommendations • Other Array level workshops to follow • OOI Team to run mini-workshops for initial data review • OOSC will run community workshops • Workshop dates are driven by data availability through OOINet

20. Technical Issues and Risks for OOI Surface-piercing profiler technology is not as mature as initially expected. Global surface-piercing profiler was descoped and is being replaced by gliders functioning as virtual moorings. Coastal surface-piercing profiler, long-term performance to be assessed. (WHOI – SIO – OSU - OL) Risk: hoped-for advances in vertical resolution of upper-ocean processes (supporting the ‘transformative’ aspect of the OOI) must await further progress by vendors (partially mitigated) Vertical moorings deployed within the cabled array have technical issues to resolve, specific to the deep and shallower profiler. Remaining shallow profiler continues successful testing. Deep profiler issues identified and resolution in progress. Testing in progress. (UW- OL) Risk: hoped-for advances in vertical resolution of upper-ocean processes (supporting the ‘transformative’ aspect of the OOI) must await further progress with technology reliability. (low technical risk, moderate schedule risk)

21. Technical Issues and Risks for OOI The AUV docking system is scheduled for Spring 2015 deployment within the Pioneer Array. In-water tests demonstrated some success. Docking system complexity and final design changes could lead to a schedule problem. (WHOI - OL) Risk: AUVs may need to be descoped, eliminating the resolution planned to be obtained by the AUVs (high risk). Fuel cell development continues for the surface moorings, but progress has been slower than expected. Unit failed to operate on recent deployment, and was immediately recovered. Failure analysis indicated root cause, but partial redesign requirement for remediation. (WHOI - OL) Risk: Mission duration may be impacted by lack of full power from wind and solar generators for charging AUV batteries – eliminating the resolution planned to be obtained by the AUVs (moderate to high risk).

22. Budget & Funding Status • MREFC fully funded • NSF has provided the full MREFC funding to Ocean Leadership and OL has distributed to each Implementing Organization • Control Account Closeouts • OL is actively closing out accounts to be prepared for the period of performance completion • Weekly meetings are held to coordinate with all of the finance staff • Closed accounts are flagged in the accounting system to prevent new charges from posting

23. Summary Program Financials • ARRA fully spent and closed • MREFC remaining to spend is $29.39M, of which $7.28M is already obligated • The current contingency balance is $2.9M. OOI is actively monitoring risks which, if realized will further reduce this figure

24. Unobligated balance by IO

25. Unobligated balance - PMO • Bulk of remaining PMO budget: • Potential resolution of claims currently working through ratification process with former CyberInfrastructure Implementing Organization • Raytheon work for CI Management Support and uFrame build

26. Unobligated balance - WHOI • Remaining Unobligated balance of $9.45m • Categories of remaining funding: • Main construction cruises are complete • Cost reviews have identified $1.5m available for immediate re-budgeting • Expect additional funding to become available as weekly financial close out meetings continue

27. Contingency-Risk Snapshot • Intend to close above Risk with the exception of 9000 CI-Execution Risks

28. Proposed Contingency Risk Closeout

29. Schedule

30. Schedule Milestones to Complete September July August May June Commissioning • Station Papa • Irminger • Southern Ocean • Argentine Basin • Endurance • - ISM/CSPP/Gliders • Pioneer • CSPP/Gliders • AUV / Dock • Fuel Cell • Cabled • Deep Profiler • CI Conditional Acceptance Conditional Acceptance Deploy Conditional Acceptance Deploy Decision Point 2 Deploy Decision Point 3 Shallow water test Longevity Test Refurbish Decision Point 1 Increment 1 Increment 2 Refurbish Conditional Acceptance Deploy Build 3 Build 4.1 Build 5 Build 6 V & V V & V V & V V & V Final Casandra Configuration

31. Overview Summary • Currently operating on no cost extension of period of performance through 6/30/2015 • Following presentations will review progress to project completion and technology risk associated with: • CI Design • CI Build Status • CI Testing • CI Completion • Marine Technologies Completion