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||7/16/13||9/9/13|
|Inception Iteration 2||9/9/13||11/4/13|
|Elaboration Iteration 1||11/19/13||1/24/14|
|Elaboration Iteration 2||1/27/14||3/21/14|
|Construction Iteration 1||4/7/14||5/30/14|
|Construction Iteration 2||6/2/14||7/25/14|
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 4.
See also: Marine Integration Construction Plan
The following diagram illustrates the service components being delivered in Release 4 on top of the existing Release 1,2 & 3 functionality.
Release 4 service components (illustrative)
Release 4 functionality provides control of models driven by the data collection process and provides control of data, processes and models to drive the collection process.
- Manage missions controlling autonomous assets
- Coordinate fixed and mobile mission assets
- Simulate missions
- Integrate multiple models
- Execute model ensembles and tune model parameters
- Nest models at different spatial scales
- Operate Virtual Organizations (Facilities)
- Use automated brokering and negotiation for resources
- Use online mediation support for contract negotiations
- Perform collaborative observational tasks (set up collaborative missions)
- Extend virtual labs and classrooms with the ability to control instruments, define observational missions
- Provide an interactive observing environment for collaboration with shared tools, resources, and data
- Public can access instruments based on availability and policy
- Define mission plans based on mission goals; ION determines the resources needed and brokers them
- Request instrument use
- View current allocation of instruments
- Collaboration tools for data product generation and instrument sharing and use
- Autonomous resource control
- Closed-loop processes: Observe, analyze, exploit (change plan), observe – some change auto, some manual