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.
- Release Construction Plan Overview
- Construction Plans for all releases
- Further detailed documentation of the release content can be found in the Architecture Specification page: Transition to Operation
|Phase||Start Date||End Date|
|Inception Iteration 1||5/2/11||6/24/11|
|Inception Iteration 2||6/27/11||8/19/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|
|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|
The following link describes the contents and an overview of the subsystem construction plans.
The following are links to each subsystem construction plan for Release 2.
See also: Marine Integration Construction Plan
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)
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.
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:
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
This includes activities such as configuring and deploying instruments, monitoring platform and instrument state and usage, and performing platform- or instrument-specific commands
This includes most instrument lifecycle activities such as commissioning and decommissioning, testing for marine network qualification, and managing instrument participation in the OOI network.
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.).
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.
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:
This includes activities related to determining location, repair state, etc. throughout the life of the resource
This introduces personalized profiles for individual users, and supports association between a single user id and multiple external identities
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:
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
This introduces concepts of versions of data resources, and expands concepts of provenance
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
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:
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
The following table summarizes the Construction Plans.
|Page||Subsystem Name||Subsystem Description||Release 2 Focus||Subsystem Tasks GD|
|MI Construction Plan||Marine 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 Plan||Analysis & 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:
|R2 AS Tasks|
|R2 CEI Construction Plan||Common 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:
|R2 CEI Tasks|
|R2 COI Construction Plan||Common 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:
|R2 COI Tasks|
|R2 DM Construction Plan||Data 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:
|R2 DM Tasks|
|R2 EOI Construction Plan||External 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 Plan||Sensing & 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 Plan||User 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:
|R2 UX Tasks|