Skip to end of metadata
Go to start of metadata

Definitions

This section defines the most essential terms that will be used within this architecture specification. See Table 1.

Table 1. Definitions for selected essential terms

Term Definition
Agent An interacting system software entity, mostly realized as a capability container process, representing a principal (user or organization) and acting on their behalf in order to autonomously manage a set of resources. Resource agents are agents that front resources, such as instruments and virtual machines.
Capability Container COI subsystem developed software environment providing the core CI software infrastructure platform ("container") to host system and user provided services. Each CC provides secure and reliable access to all CI services, resources and interfaces via Exchange messaging. CCs may exist in different technologies (Java, Python, C/C++ for embedded environments) but all implementations follow the same Exchange messaging and Federated Facility governance conventions.
Cyberinfrastructure Point of Presence (CyberPoP) Physical deployment site of the Integrated Observatory with compute, storage, and network equipment, monitored by the operations team. Hosts a purpose-specific configuration of one or multiple CI capability containers in one physical hosting environment with access to local resources. Includes hardware and may have additional software deployed.
Data Product An information product that is derived from observational data through any kind of computation or processing. This includes aggregation, analysis, modeling, or visualization processes. (Note: The use of 'data product' across the OOI project often deviates from this definition.)
Data Set (or Dataset) Any information product handled by the CI Data Management services network. A dataset contains the actual information product as well as descriptive metadata on potentially multiple levels. Examples of data sets include observational data, derived data, data products, aggregate data, or analysis and visualization data products.
Data Stream A sequence of messages with a common set of characteristics out of a defined topic tree structure of characteristics. (In the DOORS Reference Module: A sequence of data packets used to continuously transmit or receive information, typically in real time and without any direct action on the part of the data consumer.)
Deployment The placement of a resource into a given location, context, or configuration (typically, the final location where it is intended to operate-this is part of the OOI activity commission. Deployment may be hierarchical, with entities deployed on other entities. Deployment may also be repeated, with entities deployed over and over for operation, as a CTD rosette off a ship — this corresponds to the OOI activity activate.
Exchange The Integrated Observatory communication network that is accessible via each CI capability container. Realized using AMQP message broker and hardware messaging infrastructure. A common message format applies. The Exchange provides secure, reliable message-based information exchange, policy enforcement and reliability. Enables flexible routing, interception for extensibility.
Exchange Broker The software or hardware messaging appliances that provide the connection points necessary for messaging and that host the messaging resources, such as exchanges and queues.
Exchange Point Logical message router, part of an Exchange Space, routing messages of a specific content class, described by a specific content structure, the topic tree. Example: An science data exchange point within the ION science data exchange space, where content is structured at first by variable and on the second level by origin. Subscriptions can be made to receive all messages satisfying a filter expression on part of the tree.
Exchange Space Logical namespace of Exchange participants, and part of the Exchange, operated within one domain of authority. May be distributed across multiple Exchange Brokers.
Execution Engine Executes Processes, defined for the specific type of the engine, as data stream processes. Examples include Capability Container, Matlab and SQLstream execution engines.
Facility An independent domain of authority owning and operating resources. Synonymous to Org. Users can become members in facilities and use resources shared with the facility. A facility may affiliate with other facilities to share and use resources. Marine facility, virtual observatory, classroom, laboratory and user facility are specialized instances of facilities.
Feature Type
Structure of data within the OOI Common Data Model. Examples include: station, grid, swath
Instrument
A physical device with an electric, communications and data interface, hosting or fronting one or multiple sensors. An example of an instrument is a CTD that hosts sensors for temperature, pressure and conductivity.
Integrated Observatory Network The computer systems, networks, and software that together present the OOI's assets as a single system. Developed by the CI Implementing Organization
Model (environmental) An algorithm for hindcasting, nowcasting or forecasting the state of the environment over a specific spatial and temporal extent. 
Observation Plan A user provided statement of intent for performing observatory observations and processing, involving a number of ION resources over a period of time. Resources include instruments, data products, compute resources etc.
Following an observation request, as part of a service agreement proposal and the subsequent service agreement, the observation plan meets the request and the agreement by defining a sequence of activities leading to the intended result.
Observatory
A collection of sites with associated resources for performing environmental observations.
Org
See Facility.
Persona
A stereotypical user of the system, such as "university professor" that may fill many roles in the system concurrently or over time.
Platform
A physical package with a manufacturer, model, and serial number, providing physical mounting locations for one to many instruments.
(Capability Container) Process
Software hosted and managed by a Capability Container. Processes control local/external resources, compute results and interact via messages.
(Stream) Process
A user or operator defined algorithm or scientific workflow bound to a data stream (via a subscription) to execute in the Integrated Observatory Network as a data stream process in near real-time when new messages arrive as part of the subscription.
Process Definition/Statement Definition and packaging of an algorithm in source or executable form that can be applied to a data stream when instantiated into the actual executing process by an Execution Engine
Resource Any entity associated with the Integrated Observatory that provides capability and has a life cycle. Subclasses of resources includes information resources, taskable resources and executable resources.
(Executable) Resource
An Integrated Observatory resource that can be instantiated into a Taskable Resources (i.e., executed), from a form represented as an Information Resource. Examples: User process description, Virtual Machine Image.
(Information) Resource
An Integrated Observatory resource that exists as an artifact represented in electronic form, without behavior. Examples: science data, annotations, derived data products, workflows, user identities
(Taskable) Resource
A resource managed by the Integrated Observatory resource that has behavior. Examples: physical device, instrument, Virtual Machine, EPU, data stream process.
Resource Registry COI subsystem developed infrastructure, based on DM subsystem developed Common Object Model and Persistent Archive infrastructure, to maintain and find information describing the various types of resources in the system. For Information Resources, may reference or contain the actual information artifact itself, such as science data.
Role Aggregation of responsibilities and authorities that a user may fulfill when interacting with the system. Examples include Observatory Operator, Instrument Operator.
Service Capability available within the OOI Integrated Observatory Network. Accessible by name via the network by following a specified service access protocol (interaction pattern and message format). Service are provided by software processes, deployed within a CI capability container, taking request messages from a service worker queue.
Service Agreement Proposal Request to use a resource together with a proposal of conditions, constraints and parameter ranges. For instance, the request to use a specific sensor in a certain time interval once an hour for 1 minute and its associated bandwidth and impact on the environment.
Site
Root or child element of an Observatory with a defined set of characteristics. Sites have different types, such as Observatory (the root), Subsite, PlatformSite, InstrumentSite.
Subscription A statement of intent from a consumer to an Exchange Point of receiving a data stream as a sequence of messages with a provided set of common characteristics. Subscriptions apply until they are removed and may range over historic and future messages satisfying the characteristics. Most commonly, messages related to a subscription are delivered into a message queue.
Subsystem Product development team implementing and integrating services and resource data models associated with one subsystem. The scope of work for a subsystem is prescribed in the Construction Plan and elaborated in the System Architecture.
Workflow A process description in a higher-level language, orchestrating a sequence of actors and conditions, coordinating a number of resources towards producing a workflow output, such as a derived data product. Workflows are data stream processes of higher sophistication.

See Also

Acronyms and Abbreviations

  • ANF: Array Network Facility (seismic observatory MREFC project)
  • API: Application Programming Interface
  • AS: Analysis and Synthesis (subsystem)
  • ASPEN: Automated Scheduling and Planning ENvironment (tool by JPL)
  • AUV: Autonomous Underwater Vehicle
  • CEI: Common Execution Infrastructure (subsystem)
  • CentOS: Community Enterprise Operating System
  • CG: [Coastal Global] (observatory)
  • CGSN: Coastal and Global Scale Nodes (OOI implementing organization)
  • CI: Cyberinfrastructure (OOI implementing organization)
  • CIAD: CI Architecture Document
  • COI: Common Operating Infrastructure (subsystem)
  • COL: Consortium for Ocean Leadership
  • CyberPoP: Cyberinfrastructure point of presence (see above)
  • DAP: Data Access Protocol
  • DCL: Data Concentrator and Logger (CSGN system component)
  • DM: Data Management (subsystem)
  • DMAC: Data Management and Communicatons (IOOS organization)
  • DNS: Domain Name Server
  • DoDAF: Department of Defense Architecture Framework
  • DOORS: Dynamic Object Oriented Requirements System
  • EOI: External Observatory Integration (subsystem)
  • EPE: Education and Public Engagement (OOI implementing organization)
  • EPU: Elastic Processing Unit
  • EVMS: Earned Value Management System
  • FDR: [OOI Final Design Review]
  • GEOSS: Global Earth Observing System of Systems
  • GOOS: Global Ocean Observing System
  • ICD: Interface Control Document
  • IEEE: Institute of Electrical and Electronics Engineers
  • IMS: Integrated Master Schedule (of the OOI program)
  • IO: Implementing Organization (of OOI)
  • IOC: Initial Operating Capability (spiral milestone and review)
  • ION: Integrated Observatory Network (system the OOI CI IO is building)
  • IOOS: Integrated and Sustained Ocean Observing System (by NOAA)
  • IPAA: Instrument and Platform Agent Architecture
  • IPT: Integrated Product Team
  • IRS: Interface Requirement Specification
  • LCA: Life Cycle Architecture Review (spiral milestone and review)
  • LCO: Life Cycle Objectives Review (spiral milestone and review)
  • LDAP: Lightweight Directory Access Protocol
  • LOC: Lines of code
  • MARS: Monterey Accelerated Research System
  • MBARI: Monterey Bay Aquarium Research Institute
  • MEDEA: Measurements of Earth Data for Environmental Analysis
  • MI: Marine Integration (subsystem)
  • MOOS (MBARI): Monterey Ocean Observing System (originally MBARI Ocean Observing System)
  • MOOS (MIT): Mission Oriented Operating Suite - an AUV control system, also referred to as MOOS-DB
  • MTS: Marine Technology Society (of IEEE)
  • NEPTUNE Canada: NorthEast Pacific Time-Series Undersea Networked Experiments
  • NetCDF: Network Common Data Form
  • NOAA: National Oceanic and Atmospheric Administration
  • NORUS: North American-Norway Educational Program
  • NRC: National Research Council
  • OMS: Observatory Management System (system component of RSN)
  • OOI: Ocean Observatories Initiative
  • OPeNDAP: Open-source Project for a Network Data Access Protocol
  • OSSE: Observing System Simulation Experiment
  • PDR: Preliminary Design Review
  • PP: Planning and Prosecution (subsystem)
  • PUCK: Pluggable Underwater Connector with Knowledge MBARI)
  • RSN: Regional Scale Node (OOI implementing organization)
  • SA: Sensing and Acquisition (subsystem)
  • SIAM: Software Infrastructure and Application for MOOS (MBARI's MOOS), an infrastructure or middleware system
  • SSDS: Shore Side Data System, software developed by MBARI (a candidate design reference for the DM subsystem)
  • TDP: Technical Data Package
  • THREDDS: Thematic Realtime Environmental Distributed Data Services
  • TRL: Technology Readiness Level

Labels

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