Releases are the increments of the CI system in the operational environment. The CI will be rolled out in four releases.
- Release Construction Plan Overview
- Release 1 Construction Plan - historic reference only
- Release 2 Construction Plan
- Release 3 Construction Plan
- Release 4 Construction Plan
- Marine Integration Construction Plan
Figure 1 shows the four incremental releases of CI as a master schedule.
Figure 1. 2660-00003 CI Master Schedule (as rebaselined in the fall of 2011)
|Phase||Start Date||End Date|
|Release 2 Inception with LCO||5/2/11||9/2/11|
|Release 2 Elaboration with LCA||9/5/11||3/13/12|
|Release 2 Construction with IOC||3/14/12||9/10/12|
|Release 2 Transition with PRR||9/11/12||11/6/12|
|Release 3 Inception with LCO||7/4/12||11/6/12|
|Release 3 Elaboration with LCA||11/7/12||3/25/13|
|Release 3 Construction with IOC||3/26/13||9/20/13|
|Release 3 Transition with PRR||9/23/13||11/18/13|
|Release 4 Inception with LCO||7/16/13||11/18/13|
|Release 4 Elaboration with LCA||11/19/13||4/4/14|
|Release 4 Construction with IOC||4/7/14||8/7/14|
|Release 4 Transition with PRR||8/8/14||10/3/14|
The four releases have the following themes and primary target user audiences:
- Release 1 provides a Data Distribution Network, a fully capable automated end-to-end data distribution and preservation infrastructure. It targets observational data consumers, such as data analysis and numerical modelers. In addition, it will support the needs of the OOI Marine observatories as instrument providers for instrument integration.
- Release 2 provides a Managed Instrument Network, adding end-to-end control of how data are collected and supporting more advanced processes of instrument providers with managed instrument control. The primary target user community are OOI Marine Observatory instrument providers and operators.
- Release 3 delivers OnDemand Measurement Processing. It adds end-to-end control of how data are processed, supporting more advanced workflows of instrument providers and data product consumers, as well as on demand measurements supporting event-driven opportunistic observations.
- Release 4 delivers the Interactive Ocean Observatory, which adds control of integrated ocean models driven by the data collection process, supporting data product developers and the numerical modeling community. It also adds control of data, processes, and models to drive the collection process, supporting observatory interactivity and transformative ocean observatory science for all users.
In its final deliverable with Release 4, the CI will provide real-time modeling and data assimilation, adaptive sensing and platform control, rapid response and event capture, closed loop, integrated sensing, modeling, and distributed network control.
The work breakdown and design of the OOI CI supports the incremental construction in five releases by six subsystem integrated product teams (IPT). Each subsystem IPT is responsible for the delivery of the respective subsystem services for each release. Once integrated, the subsystems will operate services networks within the Integrated Observatory system of systems.
The six subsystem IPTs are:
- Sensing and Acquisition (S&A) Subsystem Integrated Product Team
- Data Management (DM) Subsystem Integrated Product Team
- Analysis and Synthesis (A&S) Subsystem Integrated Product Team (will be formed in Release 2)
- Planning and Prosecution (P&P) Subsystem Integrated Product Team (will be formed in Release 3)
- Common Execution Infrastructure (CEI) Subsystem Integrated Product Team
- Common Operating Infrastructure (COI) Subsystem Integrated Product Team
The integration of tools and applications is based on the framework that the CI infrastructure provides, in particular the service-oriented integration architecture based on governed message exchange. The deployment of system entities across the observatory network is also based on the framework that the CI infrastructure provides. The following sections provide further details about the subsystems and the releases to the degree relevant for the CI architecture and design specification.
Figure 2 shows the planned construction and integration of subsystems into the four CI releases.
Figure 2. 2660-00004 Subsystem Development Schedule
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:
Deliverables for Each Subsystem
|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.
Further detailed documentation of the release content can be found in the Architecture Specification page: CIAD AV Transition to Operations