Skip to content

Meeting 31 Jan 2019 Operators feedback report

Jump to bottom
Sebastian Fehlandt edited this page Jan 31, 2019 · 1 revision

Participants

Discussed topics:

  • Audible signals
    • Operators have identified some cases where alarms are triggered but there is no sound. This is contrasted with other systems that report alarms as well
    • Inria Team will review and try to fix
  • Overview: Difficulties identifying new alarms:
    • Operators claim they should be able to identify new alarms on the main panel from a distance with ease, which the current interface is not allowing to do.
    • A screen of 46 inches and a distance of 1.5 meters should be considered
    • Inria Team will review some options
  • General:
    • Day/night contrast and brightness is a minor comment, there is no need to change it. If brightness is too much of a problem Emilio thinks it can be fixed adjusting luminosity in the room
    • Emilio has trouble distinguishing yellow from green alarms. Specially, when alarms are invalid (since the icons have no filling in such cases)
      • Inria team will adjust and come up with a proposal to review with him.
      • This is very important because, Emilio was using the ack icon to identify alarms, but that could lead to errors as alarms could be cleared and non-acknowledged, or acknowledged and set.
  • Ack / Shelve:
    • Operators claimed that "if an alarm happens while doing acknowledge and/or shelving, focus should change to the new alarm event"
      • We agreed not to do this, since it could be confusing, and could mean loose of work or errors where users end up acknowledging/shelving a different alarm.
    • We all agreed to add timestamp and values to ack /shelve panel
    • We agreed there it is ok that there is no connection between ack and shelve, that is, they are independent and users should acknowledge even if they shelve an alarm.
    • Disabling or suppressing alarms:
      • Since there is no requirement for this we agreed not to add this new "disabled" state
      • Since the problem is only for the UPS Failure alarms of the antennas, we agreed to make the antennas plugin send those alarms as cleared always (possibly in maintenance mode)
  • Weather view:
    • It is important to distinguish affected antennas and not all the associated antennas
    • It is important to distinguish when windspeed is over 15 mts than when it is over 20 m/s
    • Humidity should not trigger alarms, maybe we should review this...
  • Antennas view:
    • The narrow bars in the matrix is confusing and do not facilitate awareness or identification of the alarms
    • The operators did not see any case where devices where in maintenance so they have no comments about it. But a priori, it is not very important to distinguish such cases.
    • Inria Team will review some options
  • REQ-HAND-005:
    • We agreed that this info should be in the wiki, which is accessed with a button for each alarm (and thus, not from the main panel). Emilio comments this is the best way since it is decoupled from the IAS, and thus, they can edit it freely.

Follow us on twitter

Clone this wiki locally