Warning

Under construction

Page started from the Docs, Simulations, and User Manual entries under the current Help option in the TethysDash UI by Mike G. and Thomas H. (User Manual revision Tue Jun 17 10:35:10 GMT-700 2014).

There are three roles in the TethysDash system: observer, operator, and admin.

Observer role

This is an implicit role when no role has been assigned to a registered user. An observer can view vehicle activity via listing of recent events and collaboration notes (in both TethysDash and FleetStatus) and graphically by visualizing vehicle locations on the FleetStatus map.

Operator role

In general, users with the operator role should know how to monitor vehicle operations and determine if the vehicle is performing well. This entails being available by TethysDash notification to respond to a message from the vehicle, being able to initiate simple commands and contacting other operators if uncertain of correct course of action.

Besides being observers, operators can also perform actions related with configuring and commanding the vehicles, as well as —for some specially designated "super-operators"— initiate corrective actions that can mitigate subsystem failures on the vehicles.

One of the specially designated super-operators should be on call at all times while a vehicle is deployed.

Operator Watchstanding Basics

  • First, verify notifications are enabled for all relevant vehicles and function as needed to alert operator in the event of emergency, notes, commands, log critical and similar alerts.

    This is can be configured on your account page to send various subsets of messages received from the vehicles.

    • Web enabled device. While on wath, the operator will need a device capable of web access. This can be a smart phone, tablet, laptop or PC.

    • Audible / vibration alerts. TethysDash has a Notifications feature that allows text messages and e-mail alerts to be sent to your preferred device.

  • Next, the operator should verify they understand the deployment plan for their watch. The deployment plan for the vehicles can be described in entries accessible from the "Docs" option in TethysDash.

  • Positive hand off of vehicle to next watchstander. Changing of the watch is only final when the oncoming watch stander has made a Note Entry on TethysDash that they have the watch. It is very important that there is always an operator monitoring the vehicle.

Operator Responsibilities

The basic responsibilities of the operator on watch can be summed up by asking the questions of "Is the vehicle OK?" and "Is the deployment going according to plan?" Positive answers to both of these questions results in a successful watch.

  • Is the vehicle OK? This is answered by using the most recent information in TethysDash or FleetStatus to verify the location of the vehicle is consistent with the currently running mission.

    The operator on watch should always know when the vehicle is due to check in next. This is dependent on the mission and should be described in the deployment plan. It is good practice to make a Note entry regarding next expected surfacing prior to turning over the watch to the next operator.

  • Is the deployment being successful? The Deployment Plan will have a schedule of when the vehicle should be doing what mission. As this changes over the course of the deployment, the deployment plan will be updated. The operator on watch should verify the currently running mission matches the schedule in the Deployment Plan.

    Each mission may have specific information that is being reported to the log page. This will be detailed in the Deployment plan. The operator should verify the expected data is being plotted on the log page and contact the on duty super-operator if it is not.

Admin role

Users with the admin level role have access to all operations provided by the system, including operator and observer actions, ability to assign roles to other users, and perform other administrative tasks.