Skip to end of metadata
Go to start of metadata
The OOI program went through a replanning in November 2013 to reflect current progress and future scope. During this replanning, the number of OOI CI releases was reduced to 3. This page reflects post-replanning content.

Transition to Operations Strategy

Releases are the increments of the CI system in the operational environment. The CI will be rolled out in three releases.

Configuration Items are the primary deliverables of the OOI Cyberinfrastructure Implementing Organization to the system integrator (COL) representing NSF. Configuration items undergo acceptance testing before commissioning.

The Commissioning Plan [CI-COMM] provides details about configuration items and deployment locations. See also the CI Network Design.

Releases and Target User Audiences

The architecture of the OOI Integrated Observatory is structured in a way that supports an incremental transition to operations. In particular, the design supports four incremental releases of the CI that increasingly deliver capabilities and thereby support user relevant applications and processes; beginning from data distribution and storage in release 1 to advanced concepts of interactive ocean science, including instrument and observatory interactivity exploiting knowledge gained through observations and analyses. The goal is to deliver capabilities to the user communities at the earliest time possible and to facilitate incremental change as requested by the users, in addition to the planned increase in capability. Each release has a specific theme and is targeted at providing value to a specific group of stakeholders, building on and potentially revising capabilities previously delivered.

The four releases have the following themes and primary target user audiences:

Release Title Capabilities (added) Audience (added) Deployment Limit in Scope
R1 Data Distribution Network
  • automated end-to-end data distribution and preservation
  • provisional support to integrate OOI instrument resources
  • Data Consumers (such as data analysis and numerical modelers): receive data and subscriptions in real-time
  • Data Providers: register new data sources
  • Single-site (San Diego)
  • Single domain of authority (ION)
  • Single software message broker
  • Data Provider role limited to few selected early adopter users
  • System has to be restarted when service changes are made
  • Basic access policy
  • Simple Web UI plus VPN system messaging access
R2 Managed Instrument Network
  • definition of OOI observatories and sites
  • end-to-end control of instruments and marine infrastructure
  • automated OOI data product generation
  • real-time visualization generation
  • OOI Observatory Operators: define observatory and assets
  • OOI Marine Operators and Instrument Providers: define and manage instruments, define data products
  • Multi-Site deployment. High-available system deployment in Portland, managed out of San Diego, with network equipment in Seattle, Chicago, Woods Hole
  • Data processing in the Amazon EC2 cloud for OOI users
  • Software federated messaging, highly available
  • Multi-domain of authority with restrictions (ION full capability, marine facilities limited capability)
  • Only OOI personnel can contribute and modify resources
  • Multi-site deployment
R3 On-Demand Measurement Processing
  • end-to-end control of how data are processed
  • supporting more advanced workflows of instrument providers and data product consumers
  • on demand measurements supporting event-driven opportunistic observations
  • definition of observation plans and marine resource coordination
  • autonomous marine asset control
  • PI Instrument Providers and Operators: add instruments and related resources (agents, policy) on the fly
  • User Data Analysts: define data products and analyses
  • User Resource Providers: add storage and computation resources to the system
  • Multi-Site deployment. High-available system deployment in Portland, managed out of San Diego, with network equipment in Seattle, Chicago, Woods Hole
  • Data processing in Amazon EC2, TeraGrid, OSG and other clouds for any OOI user with their own credentials and accounts.
  • Software and hardware federated messaging
  • Fully federated multi-domain of authority
  • Open the system to contributions and control from users
  • Advanced, multi-resource policy

Breakdown By Subsystem

The six subsystem IPTs will construct deliverables that will be integrated by the integration team and are subject to QA by the test and validation team. Deliverables may be of different character and include:

Table 2. Deliverables for Each Subsystem

Category Explanation
Services Functional capabilities exposed as named services via the COI subsystem, deployed on CI Capability Containers. Such services are available to service consumers within the CI (i.e., other subsystem services and processes) and externally (i.e., functions presented to users via web UIs or application interfaces). Services include core infrastructure services and application level capabilities. Services never expose the technologies they are constructed in; these technologies may be replaced over time while maintaining the same service interface.
Components and Frameworks Software ready to be extended and configured for deployment by other subsystems. An example is the instrument agent framework, which is the software that can be specialized into specific types of instrument agents.
Data Models and Configuration Data models and resource specific configuration specializing general underlying services. For instance resource, message type and object definitions, and data models for specific information repository instance or policy applicable to types of resources.
User and Application Interfaces Presentation forms such as graphical web user interfaces and Web Service externalization interfaces for services and resources of the integrated observatory network. Includes the actual user and application interfaces as well as any form of service and resource integration software necessary to make the interfaces work.

The following sections provide detail for the subsystem specific work packages that are part of each release.

Release 1: Data Distribution Network

Provides end-to-End automated Data preservation and distribution. See also Release 1 Scoping and Figure 3 for an illustration of service components.

Figure 3. Release 1 service components (illustrative)

Table 3 below lists the work packages of this release.

Table 3. Release 1: End-to-end Automated Data Preservation and Distribution

Subsystem Work Packages (High-Level Services)
Common Operating Infrastructure
  • Federated Facility (Virtual Organization) Services
  • Enterprise Service Bus & Capability Container
  • Identity & Policy Management Services
  • Resource Catalog & Repository Services
Common Execution Infrastructure
  • Elastic Computing Services
  • Execution Engine Catalog & Repository Services
  • Resource Management Services
Data Management
  • OOI Common Data and Metadata Model
  • Dynamic Data Distribution Services
  • Data Catalog & Repository Services
  • Persistent Archive Services
Sensing and Acquisition
  • Instrument Direct Access
  • Instrument Management Services
  • Instrument and Data Process Repository
  • Data Acquisition Services

Release 2: Managed Instrument Network

Provides End-to-End control of how Data are collected. See Figure 4 for an illustration of service components.

Figure 4. Release 2 service components (illustrative)

Table 4 below lists the work packages of this release.

Table 4. Release 2: End-to-end Control of How Data are Collected

Subsystem Work Packages (High-Level Services) Construction Plans
Common Operating Infrastructure
  • Federated Facility Services (Virtual Organization) (Part 1)
  • Identity & Policy Management Services
  • Capability Container & Distributed Service Infrastructure (Part 2)
  • Resource Lifecycle Services
R2 COI Construction Plan
Common Execution Infrastructure
  • Elastic Computing Services - Elastic computing planner service
  • Execution Engine Catalog & Repository Services
  • Resource Management Services
  • Process Management Services
  • Process Catalog & Repository Services
  • Integration w/ National Computing Infrastructure
R2 CEI Construction Plan
Data Management
  • Dynamic Data Distribution Services
  • OOI Common Data and Metadata Model (Part 2)
  • Persistent Archive Services (Part 2)
  • Search and Navigation Services
  • External Data Access Services
R2 DM Construction Plan
Sensing and Acquisition
  • Instrument Direct Access
  • Instrument Management Services
  • Instrument and Data Process Repository
  • Data Acquisition Services
  • Marine Observatory Facility Services
  • Instrument Activation Services
  • Data Processing Services
  • Data Product Catalog and Repository Services
R2 SA Construction Plan
Analysis and Synthesis
  • Data Analysis & Visualization Services (Part 1)
R2 AS Construction Plan
External Observatory Integration
  • Neptune Canada Integration Package 1
  • IOOS Integration Package 2
R2 EOI Construction Plan
User Experience
  • Product Analysis, UX Design Goals & Constraints Specification
  • User Workflow, Interaction & Visual Design
  • Design & Specification Evaluation
  • UI Component Specification
  • UI Component Development
R2 UX Construction Plan

Release 3: On Demand Measurement Processing

Release 3 was replanned November 2014. Detailed information will be posted soon.

Labels

release-scope release-scope Delete
read-av read-av Delete
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.