Skip to end of metadata
Go to start of metadata

Release 2 Plans

Each of the four CI releases has a specific set of themes that determine the features that are developed in that release, and which cumulatively result in the final system as envisioned by the OOI project. Each release has a primary theme, which brings particular capabilities to maturity and drives the bulk of activity. Additionally, a release has a set of secondary themes that either complete earlier capabilities or provide foundational work for later releases. User and stakeholder engagement activities and planning are structured around these themes.

See Also:

Release Plan

Phase Start Date End Date
Inception Iteration 1 5/2/11 6/24/11
Inception Iteration 2 6/27/11 8/19/11
LCO Review 8/22/11 9/2/11
Elaboration Iteration 1 9/5/11 10/28/11
Elaboration Iteration 2 10/31/11 1/3/12
Elaboration Iteration 3 1/4/12 2/28/12
LCA Review 2/29/12 3/13/12
Construction Iteration 1 3/14/12 5/8/12
Construction Iteration 2 5/9/12 7/3/12
Construction Iteration 3 7/3/12 8/28/12
IOC Review 8/29/12 9/10/12
Transition 1 9/11/12 10/2/12
Transition 2 10/2/12 10/23/12
PR Review 10/24/12 11/6/12

Subsystem Construction Plans

The following link describes the contents and an overview of the subsystem construction plans.

Release Construction Plan Overview

The following are links to each subsystem construction plan for Release 2.

R2 AS Construction Plan
R2 CEI Construction Plan
R2 COI Construction Plan
R2 DM Construction Plan
R2 EOI Construction Plan
R2 SA Construction Plan
R2 UX Construction Plan

See also: Marine Integration Construction Plan

Release 2 Functionality

The following diagram illustrates the service components being delivered in Release 2 on top of the existing Release 1 functionality.

Release 2 service components (illustrative)

Themes and Features

CI Release 2 is designated the Managed Instrument Network release, reflecting our primary theme of developing integrated support for OOI Marine Observatory instrument providers and operators. Secondary themes are support for operational management of the CI infrastructure and network, integration of computational tools for data manipulation, analysis, and visualization, and early prototyping of release 3 capabilities.

Managed Instrument Network (Primary Theme)

The goal of the primary theme is to provide end-to-end control of data collection and advanced control of managed instruments for OOI Marine Observatory instrument providers and operators. The features planned under this theme are:

Operate Observatory

This includes activities such as managing policies for marine resources (observatories, platforms, instruments, etc.), managing resources and their use, and tracking and auditing access to resources and services

Operate Platforms and Instruments

This includes activities such as configuring and deploying instruments, monitoring platform and instrument state and usage, and performing platform- or instrument-specific commands

Manage Instrument Lifecycle

This includes most instrument lifecycle activities such as commissioning and decommissioning, testing for marine network qualification, and managing instrument participation in the OOI network.

Test and Troubleshoot Instruments

This includes activities such as applying test procedures to test and troubleshoot an instrument, testing its data for OOI format compliance, and accessing supporting materials for resources in the OOI network (manuals, pictures, logs etc.).

Acquire Data and Generate Data Products

This includes activities related to data acquisition and data product generation processes, including accessing and processing an instrument’s raw data, and controlling acquisition, dissemination, and persistence of data from platforms, instruments, or observatories.

CI Infrastructure and Network Management (Secondary Theme)

The goal of this theme is to support those parts of operations and management of the CI portion of the OOI network that are not covered by existing network management tools. The features planned under this theme are:

Monitor resource status

This includes activities related to determining location, repair state, etc. throughout the life of the resource

Enhanced user accounts

This introduces personalized profiles for individual users, and supports association between a single user id and multiple external identities

Define and manage data persistence

Enhanced Data Interaction and Visualization (Secondary Theme)

This theme is aimed at providing more powerful support to science end-users, particularly in the areas of locating and working with data of interest. The features planned under this theme are:

Improved search tools

This expands the tools provided for search-by-query of OOI data resources, introducing more sophisticated metadata search capabilities, filtering and organizing search results, saved query and prospective query capabilities

Data history and provenance

This introduces concepts of versions of data resources, and expands concepts of provenance

Visualization tool integration

This allows externally created tools for generating data visualizations to be registered and used through the OOI ION interface, focusing specifically on developer-created visualization workflows and tools, and MatLab-based visualizations

Early Prototyping (Secondary Theme)

The Early Prototyping theme allows for experimentation with features or technologies to be introduced in a later release. So far only one feature is planned:

Mobile Delivery Prototyping

Experiment with the opportunities presented by use of the OOI on handheld devices such as smartphones or tablet computers, and develop understanding of user desires and development requirements

Release 2 Construction Plans Summary

The following table summarizes the Construction Plans.

PageSubsystem NameSubsystem DescriptionRelease 2 FocusSubsystem Tasks GD
MI Construction PlanMarine Integration

This Marine Integration subsystem is responsible for the design and implementation of the Instrument Platform Agent Architecture (IPAA). The IPAA is part of the CI Marine Network Integration which will implement, integrate and activate each of the Marine Nodes into the Integrated Observatory Network. The IPAA is responsible for the specification, development and prototyping of the OOI standard instrument agent and instrument/device driver strategy.

The focus of MI is to deliver the design and implementation of the Instrument Platform Agent Architecture (IPAA). The IPAA is part of the CI Marine Network Integration which will implement, integrate and activate each of the Marine Nodes into the Integrated Observatory Network. The IPAA is responsible for the specification, development and prototyping of the OOI standard instrument agent and instrument/device driver strategy.

R2 MI Tasks
R2 AS Construction PlanAnalysis & Synthesis

The Analysis & Synthesis subsystem supports a wide variety of data and data product analysis, manipulation, generation and presentation, especially through visualization. It also provides the virtual collaboration platform that will be applied to realize virtual observatories, classrooms and laboratories.

The focus of A&S-R2 is delivery of the following services:

  • Data Analysis and Visualization Services—provides a generalized analysis and synthesis framework for transforming, analyzing, and visualizing data through the application of user and community developed processes.
R2 AS Tasks
R2 CEI Construction PlanCommon Execution Infrastructure

The Common Execution Infrastructure subsystem is responsible for the services to manage the distributed, immediate mode execution of processes.

The focus of CEI-R2 is to extend and utilize the CEI-R1 functionality by delivering the following services:

  • Elastic Computing Services-extends the elastic processing unit infrastructure
  • Execution Engine Catalog & Repository Services-provides the models and capabilities to describe execution engines for processes
  • Resource Management Services-establishes standard models for the operational management (monitor & control) of stateful and taskable resources.
  • Process Management Services—provides the scheduling, and management services for policy-driven process execution at specified execution sites. The service supports the coupling of the dynamic data distribution service with the process and its triggering. Provenance and citation annotation are registered associating the input and output products with the execution process and its operating context.
  • Process Catalog and Repository Services—maintains process definitions and references to registered process engine configurations and execution sites.
  • Integration with National Computing Infrastructure—provide the capability to deploy OOI processing, in particular data stream processing on to the national/commercial computing infrastructure, focused on the Amazon Web Services (EC2)
R2 CEI Tasks
R2 COI Construction PlanCommon Operating Infrastructure

The Common Operating Infrastructure subsystem is a task and product account responsible for providing the services and distributed infrastructure to build a secure, scalable, fault-tolerant federated system of independently operated observatory components.

The focus of COI-R2 is to extend and utilize the COI-R1 functionality by delivering the following services:

  • Federated Facility Services—provides management and governance services for a collection of resources on behalf of a group or individual. It represents the domain of authority for the set of resources managed by the facility. The governance services provide for the following set of collaboration agreements: membership, partnership, federation, and delegation. Delegation, for example, is used to give a marine observatory the rights to operate/manage a research team’s instrument on their behalf.
  • Capability Container & Distributed Service Infrastructure — provides the distributed service infrastructure for the secure, scalable, and fault-tolerant operation and federation of the Facilities (operational domains of authority) that comprise the deployed system of systems: Presentation Framework - the web services and browser presentation containers as well as the web user interface “portlet” building blocks; Governance Framework - identity and policy management to govern the use of resources by participants through policy enforcement and decision services; Service Framework - provisioning, federating, delegating, and binding service interactions between resources; Resource Framework - provisioning, managing, and tracking the use of resources; Distributed State Management - managing active and persisted distributed state; Federated Message Exchange - messaging, bulk data transfer, guaranteed data transfer, and provisioning streaming media channels.
  • Resource Lifecycle Services—resource management services to transition a resource from cradle to grave.
R2 COI Tasks
R2 DM Construction PlanData Management

The Data Management Subsystem is responsible for providing life cycle management, federation, preservation and presentation of OOI data holdings and associated metadata via data streams, repositories and catalogs.

The focus of DM-R2 is to extend and utilize the DM-R1 functionality by delivering the following services:

  • OOI Common Data and Metadata Model—provides the common data and metadata model for the Integrated Observatory into which all integrated data products must translate, if required, for shared syntactic and semantic access. The scope of syntactic representation of observed data shall be extendable and comprehensive. The scope of the observatory metadata model and semantic representation shall be extendable yet constrained in implementation to at least meet all data requirements imposed by the set "Core" OOI sensors and their associated Quality Assurance/Quality Control processing.
  • Persistent Archive Services—provides cataloging, preservation, validation, and curation services to organize, persist, and maintain data holdings with their associated metadata for an individual, group, and/or community.
  • Search and Navigation Services—provides query and browsing services by context, based on the content metadata and semantics of the data holdings.
  • External Data Access Services—provides an extensible suite of access interfaces and data formats for interoperability with external communities and applications
R2 DM Tasks
R2 EOI Construction PlanExternal Observatories Integration

This subsystem ensures the Integrated Observatory Network (ION) interoperates with Integrated Ocean Observing System (IOOS), Neptune Canada and the World Meteorological Organization (WMO). It is responsible for exploiting the CI integration strategy for external interoperations with independent observatory systems.

The focus of EOI-R2 is to deliver the functionality to interoperate with a core set of applications and services used widely within the IOOS community. This effort is developed in close association with the NOAA IOOS office and its Data Integration Framework project. This effort is also the top level application concern for ION-R2 that provides the external application integration context for the design and testing of the four active ION subsystem development efforts in ION-R2; Sensing and Acquisition, Data Management, Common Operating Infrastructure, and Common Execution Infrastructure.

R2 EOI Tasks
R2 SA Construction PlanSensing & Acquisition

The Sensing and Acquisition subsystem is a task and product account responsible for providing the life cycle and operational management of sensor network environments as well as observing activities (i.e., scheduling, collecting, processing) associated with sensor data acquisition.

The focus of S&A-R2 is to deliver the functionality to access, control, modify, monitor, and document the complete operational life cycle of all instruments and external data sources within the OOI domain of responsibility. This effort is developed in close association with the “Instrument and Platform Agent Architecture” Control Account. This effort is also the top level application concern for this release and provides the application context for the design and testing of the four active infrastructure subsystem development efforts in ION-R2; Data Management, Common Operating Infrastructure, and Common Execution Infrastructure.

R2 SA Tasks
R2 UX Construction PlanUser Experience

User Interfaces, designs, templates presenting the capabilities of the Integrated Observatory to its users. Every release has a different target user audience and adds incrementally to the capabilities of preceding releases.

The focus of UX-R2 is on the following areas:

  • Product Analysis, UX Design Goals & Constraints Specification – This involves the development of a detailed specification of the user-facing features that must be enabled to meet release objectives, along with specific goals for design outcomes and definition of the targeted design space (characteristics of targeted users, the tasks to be supported, where the users are assumed to work, what tools they use).
  • User Workflow, Interaction & Visual Design – This develops a map of the workflows, conceptual interactions and visual components required to deliver the user-facing features. It also includes the development of high level descriptions of all workflows, interaction architecture and visual flows.
  • Design & Specification Evaluation – Validates the detailed designs and documentation of all workflows, interactions and views with respect to usability and design goals.
  • UI Component Specification – Produces detailed specifications of non-development interface elements (e.g., graphical elements) and coding requirements.
  • UI Component Development - Builds and integrates prototypes as needed to illustrate and test proposed interface solutions to critical user-facing features.
R2 UX Tasks
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.