ocean observatories initiative ooi project scope …ooi annual review year 2 may 16 – 20, 2011...
TRANSCRIPT
OOI Annual Review Year 2May 16 – 20, 2011
Ocean Observatories Initiative
OOI Project Scope and Status
Building/deploying science infrastructure for
understanding a changing water planet
OOI Annual Review Year 2May 16 – 20, 2011
OOI science requirements were defined by the community
Overarching Science themesForcing and exchanges at the boundaries
• Ocean-atmosphere exchange• Fluid-rock interactions
Dynamics of the boundary regimes• Coastal ocean dynamics and ecosystems• The subseafloor biosphere• Plate-scale, ocean geodynamics
Dynamics and variability of the ocean volume• Climate variability• Ocean circulation• Turbulent mixing and biophysical interactions• Ecosystems
Across the boundaries and in the interior• Carbon cycling, ocean acidification, ecosystem health
OOI Annual Review Year 2May 16 – 20, 2011
OOI requirements are controlled in DOORS
X
OOI Annual Review Year 2May 16 – 20, 20112
OOI Science Requires Resolution of High Frequency Forcing (minutes-hours) In Distant and/or Extreme Environments for Sustained Periods (years-decades)
Four high latitude sitesStation PapaIrminger Sea
Argentine BasinSouthern Ocean
Two Coastal networks Endurance Array
Pioneer Array
Cabled Meso-scale, Plate Scale Interactions
The locations and style of infrastructure drive engineering design, deployment, and
maintenance profiles
OOI Annual Review Year 2May 16 – 20, 2011
OOI Construction Work Breakdown Structure (WBS)
X
OOI Annual Review Year 2May 16 – 20, 2011
WBS 1.2 Cyberinfrastructure
X
OOI Annual Review Year 2May 16 – 20, 2011
Cyberinfrastructure Design Items
X
OOI Annual Review Year 2May 16 – 20, 2011
OOI engineering strategy based on multiple modes of communication
3
OOI Annual Review Year 2May 16 – 20, 2011
OOI Integrated Observatory• Observatory Requirements:
Provide one integrated observatory interface to all users
inside and outside the OOI. Enable the users to inves>gate observa>ons, manage the
observatory and its assets and collaborate with each other in
teams.
• Engineering Drivers: A geographically distributed system of systems with
observatories at mul>ple scales and opera>onal authority. OOI-‐wide need for data distribu>on, storage, processing and command
and control.
Compute Clouds
Marine
Interface
Cyber Points of Presence
Cyber
Operations
MarineOperations
Marine
Interface
Marine
Interface
OOI Observatory Network
Integrated Observatory
Network
ExploitObserve
ModelObserve
Model
Exploit
MarineOperations
MarineOperations
OOI Annual Review Year 2May 16 – 20, 2011
• Observatory Requirements:Enable communi>es of users to work with the instruments and
observatory assets they need from across all OOI sites in a uniform
observatory environment. Support mul>ple “virtual” observatories in
parallel.
• Engineering Drivers: Mul>ple heterogeneous
communi>es of users accessing shared observatory assets across
the OOI. Enable access to observatory assets based on user authoriza>on level and observatory
policy.
Virtual Observatories
Obs
erva
tory
In
terf
ace
OOI Annual Review Year 2May 16 – 20, 2011
Event Detection and Response
• Observatory Requirements:Support closed loop scien>fic ac>vi>es. Enable interac>ve and event-‐driven control of the observatory assets based on interac>ve and real-‐>me observa>ons and analyses.
• Engineering Drivers: Workflows accessing real-‐>me measurements, external data sources, real-‐>me processing, QA and event-‐detec>on, complex numerical models leading to control of mobile and sta>onary observatory assets.
Assimilate measurement products from multiple observing systems to establish the initial conditions for a network of ocean modeling systems
Use modeling results to guide the tasking of observing programs performed by the network of sensor platforms
Ocean ObservingSystems
Ocean ModelingSystems
ScheduleCollect
Process
Observe
Product
Assimilate AnalyzeEvaluate
Model
Understanding
PlanTest
Control
Exploit
Task
OOI Annual Review Year 2May 16 – 20, 2011
OOI Deployment Topology
• Observatory Requirements:Provide observatory assets to support measurements of scien>fic processes. Provide computa>onal and network assets to enable real-‐>me, secure access and processing for the observatory users
• Engineering Drivers: Proximity to observatory assets, geographic redundancy. High-‐bandwidth, low latency access to na>onal and interna>onal network peering points. Access to commercial and academic compute clouds
Seattle, WA
Portland, OR
San Diego, CA
Chicago, IL
McLean, VA
Woods Hole, MA
Distribution Point
Acquisition Point/
Engineering Center
Marine Observatory
Dedicated 10GE
VPN over Internet
OOI Annual Review Year 2May 16 – 20, 2011
National & International Observatory Integration
NEPTUNE Canada
NFS OOI Network
NOAA N-Wave Network
Global LambdaIntegrated Facility
Engineering Driver:The topology used by the
OOI program is easily integrated into national and international cyber-
networks. This will facilitate collaboration for
developing the international ocean observing network
OOI Annual Review Year 2May 16 – 20, 2011
OOI Network Deployment
Portland, ORAccess Point
Management Network
Pacific City, ORShore Station
Axial SeamountNode 3
Mid-PlateNode 5
Hydrate RidgeNode 1
EnduranceArray
Pioneer Array
Argentine Basin Array
Station PapaArray
Southern OceanArray
Satellite Communications
Marine OperationsManagement Point
Satellite Access Point
Woods Hole, MAAccess Point
Irminger SeaArray
10 GbEInternet
T1
Satellite
User
Marine
Cyber
Regional Scale Nodes Coastal Scale Nodes Global Scale Nodes
Research & Educations Facilities
End UserApplications
San Diego, CADistribution Point
Chicago, ILDistribution Point
Seattle, WADistribution Point
Observatory Network
Public Internet
Observatory Operations
Management Point
Portland, ORAcquisition Point
Woods Hole, MAAcquisition Point
Academic HPC & Cloud Facilities
Execution Point
Commercial HPC & Cloud Facilities
Execution Point
National Data RepositoriesExecution Point Engineering Driver:
The physical network links the marine
operators, external users, and educators to the ocean assets deployed throughout the world’s oceans.
OOI Annual Review Year 2May 16 – 20, 2011
OOI Cyberinfrastructure Year 2 Milestones
• Release 1: Data Distribution Network
– Life Cycle Architecture Review: August 2010– Initial Operating Capability Review: May 2011
• Life Cycle Architecture Review for Instrument Agents and External Observatory Integration: Dec 2010
• Completed purchase and installation of San Diego Engineering Center (CyberPoP Buildout): Jan 2011
10
OOI Annual Review Year 2May 16 – 20, 2011
NRCCritical Infrastructure for Ocean Sciences
• Recommendations– Establish broadly accessible virtual
(distributed) data centers that have seamless integration of federal, state, and locally held databases.
– Examine and adopt proven data management practices from allied disciplines
– Facilitate broad community access to infrastructure assets, including mobile and fixed platforms and costly analytical equipment
11
OOI Annual Review Year 2May 16 – 20, 2011
NRCCritical Infrastructure for Ocean Sciences
• The risk of a singe-point due to a sole means of communication is clear and argues for some redundancy in data pathways, as wel as a set of standards common to nay provider. In innovative redundancy solution is “store and forward” capability, which could be located on commercial ships and aircraft, offshore platforms, or even miniature satellites.
12
OOI Annual Review Year 2May 16 – 20, 2011
NRCCritical Infrastructure for Ocean Sciences
• Two-way communications, especially for platforms, has ben truly transformative in the last two decades and will remain essential to ocean research infrastructure assets in the future.
• Barriers to be overcome include data accessibility and impediments to collaboration, which are critical to continued success. For community-wide facilities that provide laboratory analyses, independent verification and calibration is needed to provide sustained confidence in the data being produced.
13
OOI Annual Review Year 2May 16 – 20, 2011
NRCCritical Infrastructure for Ocean Sciences
• A major need for success in the realm of data management is to establish seamless integration of federal, state, and locally held databases, so that relevant data can be easily retrieved by a range of users.
• Data Management - This important crosscutting infrastructure category is subject to rapid changes, driven almost entirely from outside the field of ocean sciences.
14