Skip to end of metadata
Go to start of metadata
This page describes integrating the various types of OOI marine platforms with the Integrated Observatory Network, based on the MI Instrument and Platform Agent Architecture and management by the Sensing and Acquisition subsystem services.

Platform Integration

Deployment and Integration Scenarios

Figure 1 below shows an illustration of the interfaces of the OOI Integrated Observatory Network to the Regional Scale Nodes (RSN) observatories and the Coastal/Global Scale Nodes (CGSN) observatories.

Figure 1. Platform Integration (OV-1)

CI Computational Element Variant (DESCOPED)

Figure 2 shows a variant of Figure 1 with a CI Computational Element on intermittently connected CG platforms. This variant has been descroped

Figure 2. Platform Integration (Computational Element Scenario) (OV-1)

Data Acquisition Architecture (DESCOPED)

Figure 3 shows the flows of data acquisition from a remote platform. It shows both near real-time (via intermittent satellite link) and manual data recovery data flows.

Note that data decimation is optional for instruments that produce higher data rates than feasible to recover in near real-time via the satellite link. In this case it is a platform function to recover selected subsets of data on demand. This can initially be realized as a manual data/file retrieval function.

Figure 3. Data Acquisition from Remote Platform

The following information sets are distinguished:

  • Raw port logs, written by the CG Data logger. Bidirectional traffic log annotated with time stamps
  • Raw data stream emitted by the instrument agent
  • Parsed data stream emitted by the instrument agent
  • Decimated data stream emitted by a platform hosted decimation transform process
  • Events, produced by platform hosted transform process (Release 3 and above)

The actual number of distinguishable instance information sets is determined by the number of instruments on a platform, and by the number of sensors (= independent streams) per instrument, including science data sensors and engineering data sensors.

The figure above shows Release 3 elements. Event detection processes can take instrument agent data in real-time or on a schedule and analyze it to find science or infrastructure events that can trigger immediate adaptive actions. A SmartExecutive is a component managing a device (platform or instrument) that works within a boundary plan. The plan as well as environmental input are solved into a specific set of commands for this device. This allows the SmartExecutive to react to environmental and infrastructure events, even in the case where no shore-side connectivity exists.

Platform Types and Agents

See also



read-mi read-mi Delete
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.