compared with
Current by Michael Meisinger
on Apr 15, 2014 12:29.

Key
This line was removed.
This word was removed. This word was added.
This line was added.

Changes (16)

View Page History


Observatory Management is the capability to operate and govern an observatory and its resources. Observatories are defined under the authority of either a Marine Facility, e.g. the CG or RSN organizations, or as virtual observatory under the authority of an independent organization (or user). In Release 2, the primary use observatory is within a Marine Facility, applying Marine IOs' resource policies. Marine operators can define their own resource policies, and to assign resource attributes that trigger the appropriate policies given the roles of the principals.
Observatory Management is the capability to operate and govern a marine facility (e.g. RSN, CGSN, EA organizations) and its resources. The facility applies Marine IOs' resource policies. Marine operators can define their own resource policies, and assign resource attributes that trigger the appropriate policies given the roles of the acting users.

In addition to the marine facilities, ION provides an integrated view, the ION Integrated Observatory, a virtual observatory. In Release 3, additional "Virtual Observatories" can be defined by authorized users with selected assets.
In addition to the marine facilities, the OOINet architecture supports the concepts of defining "Virtual Observatories" with their own sets of users and policies, but sharing the underlying resources from marine facilities. The implementation of these concepts has been descoped.

For the purposes of the concepts on this page, we use the terms "observatory" and "marine facility" interchangeably, unless explicitly stated.

*See also:*



h2. Observatory Topology Structure

The principal objectives of observatory management are planning of observatory resources and deployments, command and control of observatory resources, and monitoring the state of health of observatory resources. The diagram below shows how resources in an observatory are organized from an architectural perspective.
The main objectives of observatory management are
* planning of observatory resources and deployments, 
* command and control of observatory resources, 
* and monitoring the state of health of observatory resources. 

The diagram below shows how resources in an observatory are organized.

!https://docs.google.com/drawings/pub?id=1fC7cuvuA7olPGVAHlbwEyRh3lg2cHNSwHIdiBJ8Z2h8&w=924&h=646|border=1!

_Figure 1. Observatory Resources and Associations (OV-1)_


h3. Observatory Sites

Sites structure the planned topology of an observatory and identify planned observatory resources. [Observatory|syseng:Resource Spec for Observatory] and [Subsite|syseng:Resource Spec for Subsite] are organizational resources to group lower level sites and to characterize them together.
One of the primary functions of a marine facility (observatory) is to manage its sites. Sites are hierarchically structured named locations of the observatory. Sites fall into these categories:

Platform and instrument sites identify observatory resources for physical deployments. They constrain the device model of deployed devices and provide a reference for a continuous flow of information from a defined site, independent of the different devices deployed at the site over time.
* *Geographical sites*: Named location determined by a geographical area for a region of interest within the marine facility. Examples include "Coastal Pioneer Upstream Inshore". In OOINet these are represented by the resource types [Observatory|syseng:Resource Spec for Observatory] and [Subsite|syseng:Resource Spec for Subsite]. Note: In OOINet Releases 2 and 3, only Observatory is used for geographical sites and Subsite is never used.
* *Device sites*: Named location, potentially determined by a geographical location (stationary assets) or area (mobile assets), where physical assets of a defined characteristic can be deployed. OOINet resource types include [PlatformSite|syseng:Resource Spec for PlatformSite] and [InstrumentSite|syseng:Resource Spec for InstrumentSite]. Note: In OOINet Releases 2 and 3, PlatformSite can have PlatformSite child sites to represent more sophisticated assemblies such as moorings.

Note: these resources were formerly called "logical platform" and "logical instrument".
Device sites identify observatory resources for physical deployments. They constrain the device model of deployed devices and provide a reference for a continuous flow of information from a defined site, independent of the different devices deployed at the site over time.

h4. Platform Site