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
These are the scheduled dates for Release 3 Construction.
|Release 3 Start Date||8/27/2012|
|Release 3 End Date||1/22/2014|
|Phase||Start Date||End Date|
|Inception Iteration 1||8/27/2012||12/18/2012|
|LCO Review Period||12/19/2012||1/10/2013|
|Elaboration Iteration 1||1/11/2013||3/07/2013|
|Elaboration Iteration 2||3/08/2013||5/02/2013|
|Construction Iteration 1||5/17/2013||7/11/2013|
|Construction Iteration 2||7/12/2013||9/05/2013|
|Construction Iteration 3||9/06/2013||10/31/2013|
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 3.
See also: Marine Integration Construction Plan
The following diagram illustrates the service components being delivered in Release 3 on top of the existing Release 1 & 2 functionality.
Release 3 service components (illustrative)
Release 3 functionality provides end-to-end control of how data is processed.
|For a more detailed listing of Release 3 features, see the R3 Features and Capabilities List.|
- Perform interactive quality assurance on instruments and interactive quality control on data products
- Register user-contributed data calibration workflows
- Track data calibration and validation processes applied to instrument data
- Define new, user-created data acquisition processes
- Define new, user-created algorithms and workflows to produce new data products
- Define and validate interactive observatory mission workflows
- Interactively plan, test, monitor, and manage observation missions
- Allocate and schedule observatory resource usage
- Register user-contributed instruments
- Define and create virtual workspaces and workspace policies
- Set up and manage social networks for scientists and educators
- Collaborate with other virtual classrooms and labs
- Share resources
- Access, transform, and integrate data from multiple sources including external sources
- Interactively apply analysis tools of the user’s choice
- Create and register new resources by combining data from multiple resources.
- Integrate and work with data from external sources
- Annotate data with comments, tags, ratings, and other user-contributed information
- Uniquely identify a data subset and create annotations for any data subset
- Describe physical samples and physical analytical results
- Classify resources by type, (seismic, water column, etc.), using system and user-defined taxonomies
- Cross-reference external data catalogs, maintain metadata, pointers and functions (such as check for updates)
- Create and register new, user-created workflows as OOI resources
- Create and register new, user-created models or analyses as OOI resources
- Use event detection in workflows and models
- Use user and community-developed processes for transformation, analysis, and visualization
- Use integrated third-party analysis and visualization capabilities
- Search for and use existing scientific workflows
- Monitor and control data processes anywhere in OOI network
- Test power, communications, and time interfaces
- Test environmental compliance
- Track status of non-physical resources such as memory, executables, etc.
- Track faults through a dedicated fault-monitoring interface
- Interact with all suitable ION services by way of mobile devices