Expand alarm annotation and consider a double-ack Merged

Initial use-case: classifying alarms for future analysis and reporting. e.g. MAOP alarms, false alarms, Safety or DOT related.

Eventual use-case: Machine Learning algos take advantage of human classification

Also consider this as how we would double-ack an alarm.

New Workflow:

• Alarm comes in and is flashing on the alarm pager

• Operator clicks the ack button to the immediate left of the alarm

• A pop-up appears, with

  • the alarm entry reproduced

    • Bonus points for the current alarm story being represented, perhaps as a collection of rows that match the GUID of the alarm being ack'd

    • Extra bonus points for showing any related commands the operator has issued the point in question, or (for maximum bonus points) any point related to the one in question

  • a drop down that presents pre-configured catgorisations

  • a free text field for the user to enter short notes

  • a cancel button, which dismisses the popup without doing anything

  • an ack button, which ack's the alarm, and stores the user's selected catgory and entered text

• These annotations are stored along with the event

  • no requirements for this to be in the main event table

  • likely need 1-to-many for alarms and annotations

  • will need to be able to send annotations to CONNECT along with the events

• extensibility points enabling customisations. Including: extra read-only information in the pop-up, perform additional actions when the user ack's the alarm

  • text strings that the customer has previously configured system-wide.