Skip to end of metadata
Go to start of metadata

Overview of "Manage Marine Platform" Use Case

Manage a marine observatory platforms and its resources.

Tip: Key Points
UC Priority= 4 or 5: Critical, is in R2
Only boldface steps are required
<#> before a step —> lower priority
(optional) —> run-time option

Related Jira Issues:   Open   •   All


Refer to the Product Description and Product Description Release 2 pages for metadata definitions.

Actors Marine Observatory Operator (Observatory Operator)
References UC.R2.08 Manage Instrument Lifecycle
UC.R2.11 Define Marine Observatory Resources and Policy
Uses UC.R2.14 Monitor an Instrument
UC.R2.06 Command Instrument
UC.R2.07 Direct Instrument Access
Is Used By  
Is Extended By  
In Acceptance Scenarios AS.R2.01A Operate Marine Observatory, AS.R2.02A Cruise Support, AS.R2.02B Data Support via Cruise, AS.R2.02C Instrument Life Cycle Support
Technical Notes  
Lead Team SA
Primary Service Marine Observatory Facility Services
Version 2.1.1
UC Priority 4
UC Status Mapped + Ready
UX Exposure MNC


Manage remote and directly connected marine platforms as collections of instruments, physical devices and associated platform resources. Management includes control, monitoring, and event notification.


  • Platform is capable of being managed by the Integrated Observatory (i.e., is commandable).
  • For intermittently connected platforms, monitoring and commanding the platform can occur without the platform connected directly via satellite.

Initial State

Platform operational and connects (at least intermittently) to the shore.

Scenario for "Manage Marine Platform" Use Case

  1. Marine Observatory Operator inspects platform resource status and levels
    1. These are defined as those resources that specifically address platform capabilities. (They are provided and measured by engineering systems and instruments on the platform.)
    2. Resources include power, onboard data storage, CPU load, memory usage, and communication bandwidth.
    3. There may be additional relevant status items to display.
  2. Marine Observatory Operator inspects status messages for platform
    1. Marine Observatory Operator has ready access to time-tagged platform error/warning/info/debug messages.
    2. Again, these are the messages from the platform resources.
  3. <3> Marine Observatory Operator inspects overview of status indicators for platform connected instruments
    1. Status overview indicates basic status categories for principal functions (power, command, data, ...)
  4. <3> Marine Observatory Operator inspects overview of all platform instrument/driver/agent statuses.
    1. Display list of all instruments installed on platform
    2. For each, display summary items like ID#, name, port, agent/driver state, sampling status, counts of info/warning/alarm notifications, time since last communication
    3. Marine Observatory Operator has ready access to time-tagged instrument info/warning/alarm/debug messages
  5. Marine Observatory Operator commands platform assets, including (in some cases) power supplied to instrument ports.
    1. These are the assets providing platform capabilities, like communications, power, computing, and location and time sensing.
    2. Platform may have control over power for individual instruments or sub-platforms, via the power ports the platform can control.
  6. Marine Observatory Operator can monitor and command specific instruments on the platform
    1. Done by visiting the instrument page and issuing the appropriate command(s).
    2. Contingent on whether remote connection to platform is available.
    3. See UC.R2.14 Monitor an Instrument and UC.R2.06 Command Instrument
  7. Marine Observatory Operator receives asynchronous notification of a platform fault
    1. Important messages (such as faults) are propagated from agent/driver to user, even over intermittent network links (e.g. satellite link)
  8. <3> Marine Observatory Operator views summary of telemetry received from platform
    1. Includes age since last communication and/or data sample; increasing stream age indicates possible fault in instrument, platform, communication link, or other subsystem
    2. Marine Observatory Operator can ideally view history of instrument error sampling rates
  9. For intermittently connected platforms, Marine Observatory Operator can request immediate establishment of satellite connection to the platform
    1. Obtaining a connection is not guaranteed (the platform may be freely mobile under water, for example).
    2. This connection then enables direct platform and instrument access (see UC.R2.07 Direct Instrument Access)
    3. The establishment of the connection could lead to update of status and events from the platform as a side effect, depending on communications designs.
  10. Marine Observatory Operator can modify the platform configuration that describes the installed systems.
    1. This capability supports operational replacement, addition, or deprecation of deployed instruments.
    2. Parts of this may not be supported through a user interface.
  11. Marine Observatory Operator can modify the platform's operational configuration.
    1. This capability supports modifications to the operations of the platform-supporting instruments.
    2. Includes telemetry schedule for platform-supporting instruments.

Final State

Platform configuration and systems updated or scheduled for update with next communication interval.


These comments provide additional context (usually quite technical) for editors of the use case.

(click on # to go to R2 use case)
01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20
21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40
41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
61     27B


r2-usecase r2-usecase Delete
usecase usecase Delete
productdescription productdescription Delete
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.
  1. Jun 28, 2011

    Tom O'Reilly says:

    As an example observatory status summary page, see Node status summary.pdf from ...

    As an example observatory status summary page, see Node status summary.pdf from the MBARI MOOS observatory