Preliminary requirements

Required conditions

• You are on duty, with your call sign entered.
• The alert is shown in the Alerts panel on the Console tab.

Required persons

1 × Operator. Estimated time: 5 to 20 minutes for each alert.

Support equipment

• A computer or phone with a web browser, on the same network as the server

Supplies

None

Spares

None

Safety conditions

Procedure

1. 1

   Read the alert. Note its severity (Alarm, Caution or Event), the channel or condition, and when it was raised.

2. 2

   Select Acknowledge on the alert.

   Check that the alert now shows Acked with your call sign.

   Note

   Acknowledging records that you have seen the alert. It does not clear it. The alert closes by itself once its condition clears.

3. 3

   Find the cause.

   1. 3.1

      For a limit alert, select the channel name in the alert. Look at the last 7 days of the channel on the chart.

      • Grey bands show eclipse. A temperature that drops in each eclipse and recovers in sunlight is normal.

      • Red ticks along the top show geomagnetic storms. Check whether the reading lines up with one.

      • Coloured bands show the caution and alarm zones.

   2. 3.2

      If the alert says that no new frames have arrived, or that the satellite may have gone silent, refer to Telemetry reception – Fault isolation: no frames, or satellite may have gone silent (DMC-DLD-A-10-20-00-00A-400A-A).

   3. 3.3

      If the alert says that the server cannot reach SatNOGS, or that the API key is missing or rejected, refer to SatNOGS link – Fault isolation: data is not being collected (DMC-DLD-A-10-10-00-00A-400A-A).

4. 4

   Record what you found. Type a short note in the log note box on the Console tab and select Log note.

5. 5

   If the alert is expected and you need it out of the main list for a while, shelve it:

   1. 5.1

      Select Shelve on the alert.

   2. 5.2

      Choose how long: 1 hour, 6 hours, 1 day or 1 week.

   3. 5.3

      Type a reason the next operator can act on, for example: "Battery temperature low in each eclipse since season change; within mission behaviour. Review limits Friday."

   4. 5.4

      Select the second Shelve button, next to the reason. Check that the alert now appears under Shelved.

6. 6

   If a limit is wrong rather than the value, change the limit. Refer to Channel limits – Set or change limits (DMC-DLD-A-20-20-00-00A-130A-A).

Requirements after job completion

• The alert is acknowledged, the cause is noted in the log, and the alert is either closed, open with a known cause, or shelved with a reason.