Introductions and OOI Overview

1. Introductions andOOI Overview

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. 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

4. Summary of this presentation Reality of the OOI today status, gaps Scope overview of the OOI built to sustain data delivery to stakeholders Data management overview Structure to be implemented and operated What, Who, How, Where Work-to-go between today and O&M (Tuesday AM)

5. The Reality of the OOI – marine deployments • Status today (1) • Deployments of marine hardware are progressing according to the project schedule - however, • risks remain for certain technologies and requirements • fuel cells • AUV docks • bio-acoustics • resolution of the upper few meters of the water column

6. The Reality of the OOI – marine deployments • Status today (2) • Deployments of marine hardware are progressing according to the project schedule - however, • risks remain in closing all the integration gaps required to achieve commissioning (more on this later) • supply-chain delays being addressed aggressively

7. The Reality of the OOI – impact of software delays (1) • The extended delays in Release 2 completion led to these management actions at Ocean Leadership: • descoped portions of original CI design; • inserted Software PM and CI SE under OL authority; • transferred coding of instrument and platform drivers, algorithms, data set agents to other work groups; • transferred completion of User Interface to another work group;

8. The Reality of the OOI – impact of software delays (2) • Significant cross-OOI consequences resulted from the delays in Release 2 completion: • compressed schedule to get drivers and product algorithms aligned with deployments; • development of a Concept of Operations has been delayed; • final commissioning schedule for marine deployments delayed- requires end-to-end data delivery (products to the user), including integration and testing of drivers, agents, product algorithms and user screens into the final release; • Extended delays in commissioning of deployed hardware have construction budget implications.

9. The Reality of the OOI – getting well (1) • Positives • Core code development for R3 making progress – target for completion has slipped from late June to late July; • Improved progress on coding of drivers, agents, algorithms – integration and testing has schedule risk; • Improved user interface underway – integration of screens by late summer; • New database is much more responsive (faster)

10. The Reality of the OOI – getting well (2) • Gaps • User-focused Use Cases now in draft form – will iterate until May 15; • ConOps, with FTEs and budget, requires another 2(?) weeks • Clear description of R3 functionality (incremental in May and June, full by July, following forensic assessment); • Load testing of software – incremental through May and June; • External feedback on user interface – (composition of review board established)

11. The Reality of the OOI – getting well (3) • Gaps - continued • Require an updated timeline for completion of all commissioning steps for marine deployments that accurately reflects delivered functionality for users; • Including: • Populate metadata • Deliver Technical Data Package • Author Operating procedures & work instructions • Perform Validation Testing • Conduct Training

12. Release Plan, 2014 February March April May June July August Driver & Algorithm Development Dates subject to revision when performance metrics become available MIP Steps 1 - 4 31 30 Regional Scale Node (29 drivers) 25 Station Papa (13 drivers) 25 Coastal Gliders (6 drivers) 18 14 Pioneer (9 drivers) Integration, Deployment, and Release MIP Step 5 14 2 Release 2.3 31 8 Release 2.2 (3 Drvrs) 31 25 Release 2.2.1 (9 Drvrs) Deployment Cruise Dates 10 16 Station PAPA Endurance WFP 11 13 Pioneer WFP RSN 1 Coastal Gliders OOINET Release 3 Scope to Complete • Release 3.0 (Beta 2) • STC (beta) • UX Screens • Marine Int. • Release 3.0 (Final) • Defect Corrections • PRR Build • Release 3.0 (Beta1) • STC (alpha) • UX Screens • Marine Int. • Release 3.0 (Beta 3) • STC (beta) • UX Screens • Marine Int. PRR July 16 27 25 31 17 21 PRR

13. Project Scope Overview

14. Organization Breakdown Structure Ocean Leadership Program Management, Integration engineering, Leadership and oversight Direct CI management Cyberinfrastructure IO (Subawardee) University of California, San Diego Coastal/Global IO (Subawardee) Woods Hole Oceanographic Institution Endurance Array IO (Subawardee) Oregon State University Regional IO (Subawardee) University of Washington Education IO (Subawardee) Rutgers University

15. Scope Defined as Discrete Requirements • Science Themes • high level science theme for the OOI program • Science Questions • Top level science drivers, derived from the L1 Science Themes • Science Requirements • specific requirements detailing the types of measurements, their locations, their accuracies, necessary to answer the science questions • System Requirements • detailed for the infrastructure by system • L3-CG-RQ-573 Pioneer surface moorings shall measure the Partial Pressure of Carbon Dioxide (pCO2) of surface water • Subsystem Requirements • detailed for sub-systems and instruments • L4-CG-IP-RQ-203 pCO2 instruments shall be capable of sampling intervals of no less than one time per hour. ~5500 total requirements across all levels

16. OOI Science Requires Resolution of High Frequency Forcing (minutes-hours) In Distant and/or Extreme Environments for Sustained Periods (years-decades) 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 The locations and type of infrastructure drive engineering design, deployment, and maintenance profiles

17. Project Scope – Coastal/Pioneer Array • DCN 1600-00004 – Pioneer Array • Three EM surface moorings (B, E, H) • Three Multi-Function Nodes at the base of EM surface moorings (two supporting AUV docks) • Five coastal wire-following profilers • (C, F, G, I, J) • Two coastal surface-piercing profilers • (A, D) • Two AUV docking stations (B, H) • Two AUVs • Six gliders • 24 instrument classes • 157 total instruments

18. Project Scope – Coastal/Endurance Array • Washington Line – 90 instruments • Two EM surface moorings with wind, photovoltaic and fuel cell power generation, high speed and low speed satellite communications, and meteorological sensors (80, 600 m) • One EM surface mooring with battery power and Iridium satellite communications (25 m) • Two bottom-mounted, surface-piercing profilers (25m and 80m) with acoustic communications to the surface buoy • One wire-following profiler mooring at 600 m • Three benthic multifunction nodes (MFN) at 25m, 80m and 600m with sensors, comms to the surface • Six gliders across the Endurance Array • DCN 1600-00002 – Endurance Array • Oregon Line –131 instruments • Two surface moorings with wind and photovoltaic power generation, sat comms, and met sensors (80, 600 m) • One 25m surface mooring with battery power, sat comms • Two bottom-mounted surface-piercing profiler moorings • One hybrid profiler mooring with deep profiler and shallow profiler cabled to RSN (600 m) • One uncabled benthic multifunction node (MFN) at 25m with sensors, commsto the surface • Two cabled benthic experiment packages (BEP) with fiber optic communications and power via cabled nodes

19. Project Scope – Global Arrays DCN 1600-00001 Argentine Basin DCN 1600-00003 Irminger Sea DCN 1600-00005 Southern Ocean DCN 1600-00006 Station Papa *Station Papa does not contain Surface Mooring • One acoustically-linked Global Surface Mooring*, with high-power buoy and high-bandwidth (active antenna) satellite telemetry • One Global Hybrid Profiler mooring with up to two wire-following profiler operating and one surface-piercing profiler • Two subsurface Mesoscale Flanking Moorings with fixed sensors and acoustic communications to gliders • Three gliders with extended endurance and acoustic communications to the Mesoscale Flanking Moorings • 19 Instrument Classes • 80 Instruments - Southern Ocean, Argentine Basin • 76 Instruments – Irminger Sea • 57 Instruments - Station Papa

20. Project Scope – Regional Scale Nodes • DCN 4501-00001 and DCN 4500-00001 • Shore Station • Axial Seamount/Hydrate Ridge • Paired Deep and Shallow Profiler Moorings • Extension cables to multiple sites and Endurance Array • LP J-Boxes • MP J-Boxes • Seafloor Instruments • 34 Instrument Classes • 100 Total Instruments

21. Project Scope – Education & Public Engagement • EPE is constructing an integrated suite of software tools and a web portal that enable scientists and educators to enhance undergraduate education (primary) and engage the general public (secondary) using real-time OOI data. Specifically the EPE will provide: • aweb portal enabling virtual collaboration and sharing of materials, • enhanced software for the creation of concept maps that translate science concepts into education material, • integration of a suite of educational data visualization tools, • and step by step guidance on the best practices for developing educational labs & lessons with a real-time data.

22. Data Management

23. OOIN High Level Network Design Adjustments under consideration – to be finalized by fall 2014

24. DATA FLOW • OOI PURPOSE- • Deliver data and products to users and permanent storage • BASIC APPROACH- • Acquire and store measurements from sensors • Make high quality data and products available to all; open access • Provide them quickly (many in near-real time) 23

25. USERS ENTER HERE 24

26. OOINET Data Ingestion From Iridium downlink or recovery • Cyber Pop Post Recovery • OOINET pydap Postgress ERDDAPServer Postgress Glider Platform Separate Data Files Glider • Temp • Press. • Lat./Lon • Etc. Files : Disk Storage Hard Disk Storage Meta-Data data data data OMC OOINET CORE Algorithms UI Server MIO File Server Dataset AgentDriver DatasetAgent Instrument data is now stored in separate files on a hard disk, and Metadata is stored in the Postgress Database Local Storage rsync Local Storage CI File Server

27. OOINET Data Service to Users • Cyber Pop • User Space ERDDAP Website (Browser) • OOINET pydap Postgress ERDDAPServer Files : Disk Storage Algorithms user data user req. Meta-Data Meta-Data user req. User Request OOINET Website (Browser) OOINET CORE UI Server ION Services Drivers Agents Local Storage CI File Server

28. Data Product Levels • Level 0 (L0) • Unprocessed data: Data that are in instrument/sensor units and at instrument/sensor resolution. They are sensor by sensor (unpacked and/or de-interleaved) and are available in OOI supported formats (e.g., NetCDF). • the driver for each instrument will parse the strings from each instrument into uncalibratedsensor values. For example, a voltage reading from a sensor. • Level 1 (L1) • Basic Data: data that have been calibrated, are in well-defined scientific units, and may have some QC applied. • For example, a temperature in degrees C • Level 2 (L2) • Derived Data Products: Data that have been manipulated and/or combined and include new values not present in original data. • For example, salinity derived from conductivity measurements.

29. OOINet

30. Coastal Pioneer Upstream Inshore WFP FLORT-K (fluorometer on wire-following profiler)

31. Summary • Delays in CI progress have impacted several components of Data Management, recovery still underway • led to a revision of final capabilities • moved driver, data agent, algorithm work • moved user interface work • Marine Deployments revealing gaps in functionality and process • O&M procedures under development; • Some Interface Control Documents have required rework; • Database performance, now improving

32. Summary Construction is still in progress, follow on presentations detail how we shift from building infrastructure to delivering data, retaining the focus on the primary objective of the OOI: Sustain, for decades, the delivery of multiple streams of ocean data, resolving ocean processes and properties across a range of temporal and spatial scales;