Diagnose deployed platform and instrument faults.
|Actors||Observatory Operator, Integrated Observatory Operator|
|Uses||UC.R2.14 Monitor an Instrument
UC.R2.10 Manage Marine Platform
UC.R2.04 Browse to Get Data Product
|Is Used By|
|Is Extended By|
|In Acceptance Scenarios||AS.R2.01A Operate Marine Observatory, AS.R2.02B Data Support via Cruise, AS.R2.02C Instrument Life Cycle Support|
|Primary Service||Marine Observatory Facility Services|
|UC Status||Mapped + Ready|
This information summarizes the Use Case functionality.
Use tools and procedures to diagnose and fix deployed instrument malfunctions.
- Only information which is forwarded to terrestrial network can be monitored. (Higher priority messages should be forwarded first.)
Instrument has been integrated into remote platform, has been running normally for some time
- Data process in Integrated Observatory generates event based on instrument engineering parameter's value.
- This may be a value like 'Battery Voltage' outside acceptable limits, or a status value like 'Calibration Status' no longer reading "OK".
- Specific values to test will be specified by marine observatories before and during operations.
- <3> Marine Observatory Operator asynchronously receives event message(s) indicating instrument fault(s)
- Operator retrieves faulty instrument's transmitted data products (science and engineering), inspects and analyzes retrieved data and messages
- So far this is just looking at the data already retrieved.
- Operator views current instrument status, gets list of latest messages
- Goes back and looks at/searches through past messages looking for clues and patterns.
- Possibly message have not been transferred to shore yet, but we have to assume this is not the case.
- <2> Operator configures agent/driver to emit debug messages
- Agents/drivers should emit messages at operator-specified level/verbosity, e.g. error/warn/info/debug (the coding terms). Normally agents/drivers would operate in low-verbosity (non-debug) mode.
- Operator needs to subscribe to these messages or configure the system to log them.
- <3> Observatory Operator configures alert and notification system to alert when a certain message is received.
- Operator logs onto remote platform to examine settings and conditions
- Capabilities here depend on the platform in question and the communication link.
- <3> Observatory Operator configures remote platform and/or communication system to connect and communicate messages more often.
- This setting will be 'undone' when troubleshooting is through.
- <2> Operator inspects and analyzes debug messages
- Operator accesses instrument in "direct mode", tests communication and response from instrument
- See UC.R2.07 Direct Instrument Access use case.
All reasonable paths to identify and address the instrument failure have been addressed.
These comments provide additional context (usually quite technical) for editors of the use case.