AMRIT notification center user guide
Go to "Note for Argo operators" section
The Horizon Europe AMRIT project has enabled the development of a multidirectional notification centre, centralising and relaying metadata, data and technical alerts to network operators. It works on the principle of “publish/subscribe” protocols for users. Available alerts/notifications are made searchable through a catalogue (with filters). A dashboard is used to consult alerts history and manage subscriptions.
The system comprises:
- A subscription Management (customizing alert subscriptions)
- Alert Actions (users can perform actions on alerts, e.g., ack)
- Alert History (access to past alerts)
- Real-time Notifications (emails)
- Alert Processing (processing and de-duplicating alerts)
- Alert Sources (diverse sources providing alerts)
The notification centre has been designed to manage several alert types:
- Operations Alerts from platforms (e.g., beaching warnings, EEZ warnings, battery levels, floats technical alerts, etc.)
- Data Management notifications (e.g., quality control feedback, metadata verification, etc.)
- Support Requests (e.g., data processing requests, ship and recovery operations, etc.)
- Information (e.g., new platform deployments, cruise plans and data flow modifications, etc.)
The goal of this beta testing phase is to allow partners to consult existing operational alerts, act on alerts and manage emails notifications using the AMRIT Dashboard.
We would need feedback on all parts of the system, including: alert format, the alerts dashboard user experience, managing subscriptions, etc.
Please report your feedback on the notification center here : https://github.com/amrit-eu/notifications-center/issues
Or you can send email to Romain.
Note that only a set of pre-defined alerts (and alerts severity) from Argo floats are published on this system for the moment. Please contact us should you envisage other alerts could be provided by your institute. This could concern other platforms, data quality, etc.
Start the experience by going with your browser to AMRIT Boards.
On the Dashboard click the "Login" button at the top-right of the screen and login with your OceanOPS account.
From this menu you can also create an OceanOPS account or change your password.
Then go on the Alerts Board on the left panel, which opens two tabs (INBOX for the notification dashboard and SUBSCRIPTIONS).
All alerts history can be viewed and filtered from the INBOX table menu:
: Several filters are available. For the Resource (e.g., Argo WMO number) and Event filter, you can write a partial identifier and all resources and events containing your input will be retrieved:
: You can expand an alert to have more information on it.
You can also click on an alert row to access to a page describing the alert's details:
To be able to act on alerts you must be connected with your OceanOPS account and special rights given. Please ask Thomas Latter tlatter@wmo.int to activate the "alert_editor" role on your oceanops account and be able to act on alerts.
You have to select one or multiple alerts to be able to act on them:
You can :
-
Acknowledge an alert : it means « I saw this alert ». If the same alert (same resource/WMO and same event) is received again, it will be considered as a duplicate, even if the alert is acknowledged, hence no email will be sent. -
Unacknowledge an alert. -
Add a note : leave one or several short comments about the alert, its status, or your actions (e.g. float with low battery added to the recovery webpage). -
Close : It is not considered an alert anymore (has been treated or not relevant anymore). If the same alert (resource/WMO – event) is received again, it will be considered as a new alert. hence a new email will be sent. Note that after the alert's timeout, the alert will be automatically closed. -
Delete : The alert is deleted from database and will no longer be accessible. Only some admin users can delete alerts.
Note
We consider Close is the appropriated action in most cases
On the SUBSCRIPTIONS tab, users can manage their subscriptions and choose whether they want to receive an email when a new alert is received.
Users will not receive an email if the alert is considered to be a duplicate by the alert management system (based on the resource–event pair). This prevents users from receiving multiple emails for the same alert if transmitted to the system multiples times.
To create a subscription, you must be logged in.
Click the “Add subscription” button and choose an alert category. You can then add several filters, such as the minimum severity of the alert. Don’t forget to activate « Receive Emails ».
For the moment, only Argo platform alerts are available. So, to be sure to received it, you need to create a subscription with the right topic.
The Argo floats’s alerts and associated category and severity currently sent to the system can be found in this file
Please contact Romain for more infomation. The catalogue is reproduced here :
| Category | Name | Description | Severity | Value | Origin | Frequency | Timeout |
|---|---|---|---|---|---|---|---|
| Technical issue | FLAG_MissingCycle_LOGICAL | A cycle is missing | minor | Ifremer / coriolis | Alerts are sent every hour for floats that have transmitted since the last extraction. | 2 weeks | |
| Technical issue | FLAG_MissingVerticalProfile_LOGICAL | Data transmission is behind schedule | major | Last station date | Ifremer / coriolis | Alerts are sent every hour for floats that have transmitted since the last extraction. | 2 weeks |
| Battery issue | FLAG_VoltageDrop_LOGICAL | Float experienced a voltage drop | critical | VOLTAGE_BatteryPumpStartProfile_volts (battery's voltage) | Ifremer / coriolis | Alerts are sent every hour for floats that have transmitted since the last extraction. | 2 weeks |
| Technical issue | FLAG_SUPRAHydraulicAlert_LOGICAL | Check hydraulic behaviour | warning | Ifremer / coriolis | Alerts are sent every hour for floats that have transmitted since the last extraction. | 2 weeks | |
| Technical issue | FLAG_FloatDriftAtSurface_LOGICAL | Float at the surface | critical | Ifremer / coriolis | Alerts are sent every hour for floats that have transmitted since the last extraction. | 2 weeks | |
| Technical issue | FLAG_FloatInEOL_LOGICAL | Float in end of life | critical | TECH_SURFACE_CLOCK_EOLStart_YYYYMMDDHHMMSS or CLOCK_EOLStart_YYYYMMDDHHMMSS | Ifremer / coriolis | Alerts are sent every hour for floats that have transmitted since the last extraction. | 2 weeks |
| Technical issue | FLAG_GpsValidFix_LOGICAL | GPS failure | trace | TECH_FLAG_GPSValidFix_LOGICAL | Ifremer / coriolis | Alerts are sent every hour for floats that have transmitted since the last extraction. | 2 weeks |
| Technical issue | FLAG_EmergencyAscent_LOGICAL | Emergency ascent | major | NUMBER_EmergencyAscents_COUNT | Ifremer / coriolis | Alerts are sent every hour for floats that have transmitted since the last extraction. | 2 weeks |
| Technical issue | FLAG_FalseGrounding_LOGICAL | Float detected a grounding which is suspicious given the bathymetry | informational | PRES_Traj-AtAscendingProfileDeepestLevel_dbar (grounding pressure) | Ifremer / coriolis | Alerts are sent every hour for floats that have transmitted since the last extraction. | 2 weeks |
| Technical issue | TECH_FLAG_EndOfLifeAlarm_LOGICAL | End of life alarm triggered | critical | 1 | Ifremer / coriolis | Alerts are sent every hour for floats that have transmitted since the last extraction. | 2 weeks |
| Technical issue | TECH_FLAG_FileFailureAlarm_LOGICAL | Alarm raised when a file cannot be transmitted | minor | Ifremer / coriolis | Alerts are sent every hour for floats that have transmitted since the last extraction. | 2 weeks | |
| Technical issue | TECH_FLAG_GPSFailureAlarm_LOGICAL | Alarm raised when the GPS fails | trace | 1 | Ifremer / coriolis | Alerts are sent every hour for floats that have transmitted since the last extraction. | 2 weeks |
| Technical issue | TECH_FLAG_PowerOnAlarm_LOGICAL | Power on alarm detected | informational | Ifremer / coriolis | Alerts are sent every hour for floats that have transmitted since the last extraction. | 2 weeks | |
| Technical issue | TECH_FLAG_PressureSwitchFailureAlarm_LOGICAL | Alarm raised when the pressure switch fails | major | Ifremer / coriolis | Alerts are sent every hour for floats that have transmitted since the last extraction. | 2 weeks | |
| Technical issue | TECH_CLOCK_EndOfLifeAlarm_YYYYMMDDHHMMSS | End of life alarm timestamp | critical | TECH_SURFACE_CLOCK_EOLStart_YYYYMMDDHHMMSS or CLOCK_EOLStart_YYYYMMDDHHMMSS | Ifremer / coriolis | Alerts are sent every hour for floats that have transmitted since the last extraction. | 2 weeks |
| Technical issue | TECH_FLAG_UvpBrokenAlarm_LOGICAL | Alarm raised when Uvp sensor is broken | major | 1 | Ifremer / coriolis | Alerts are sent every hour for floats that have transmitted since the last extraction. | 2 weeks |
| Technical issue | TECH_FLAG_RamsesBrokenAlarm_LOGICAL | Alarm raised when Ramses sensor is broken | major | 1 | Ifremer / coriolis | Alerts are sent every hour for floats that have transmitted since the last extraction. | 2 weeks |
| Technical issue | TECH_FLAG_MpeBrokenAlarm_LOGICAL | Alarm raised when Mpe sensor is broken | major | 1 | Ifremer / coriolis | Alerts are sent every hour for floats that have transmitted since the last extraction. | 2 weeks |
| Technical issue | TECH_FLAG_EcoBrokenAlarm_LOGICAL | Alarm raised when Eco sensor is broken | major | 1 | Ifremer / coriolis | Alerts are sent every hour for floats that have transmitted since the last extraction. | 2 weeks |
| Technical issue | TECH_FLAG_SfetBrokenAlarm_LOGICAL | Alarm raised when Sfet sensor is broken | major | 1 | Ifremer / coriolis | Alerts are sent every hour for floats that have transmitted since the last extraction. | 2 weeks |
| Technical issue | TECH_FLAG_SunaBrokenAlarm_LOGICAL | Alarm raised when Suna sensor is broken | major | 1 | Ifremer / coriolis | Alerts are sent every hour for floats that have transmitted since the last extraction. | 2 weeks |
| Technical issue | TECH_FLAG_OcrBrokenAlarm_LOGICAL | Alarm raised when Ocr sensor is broken | major | 1 | Ifremer / coriolis | Alerts are sent every hour for floats that have transmitted since the last extraction. | 2 weeks |
| Technical issue | TECH_FLAG_OptodeBrokenAlarm_LOGICAL | Alarm raised when Optode sensor is broken | major | 1 | Ifremer / coriolis | Alerts are sent every hour for floats that have transmitted since the last extraction. | 2 weeks |
| Technical issue | TECH_FLAG_Ramses2BrokenAlarm_LOGICAL | Alarm raised when Ramses2 sensor is broken | major | 1 | Ifremer / coriolis | Alerts are sent every hour for floats that have transmitted since the last extraction. | 2 weeks |
| Technical issue | TECH_FLAG_CroverBrokenAlarm_LOGICAL | Alarm raised when Crover sensor is broken | major | 1 | Ifremer / coriolis | Alerts are sent every hour for floats that have transmitted since the last extraction. | 2 weeks |
| Technical issue | TECH_FLAG_Alarm1Type_NUMBER | Type of alarm (11: External pressure sensor => No pressure information, 12: Barometer sensor, 13: Failure on initialization of SBE41 reset offset, 14: Failure on initialization of SBE41 cut-off, 15: Error system, 18: Rescue, 19: GNSS, 20: RTC, 22: DO Aanderaa4330 sensor, 23: Invalid setting of mission, 24: Invalid setting of sensor, 25: Invalid setting of CTD sensor, 26: Empty ballast sensor, 27: Flash memory, 28: SDCard memory, 31: Ice – Satellite mask, 32: Clock drift, 33: CTD SBE41 sensor, 34: CTD RBR sensor, 35: CTD RBR reset offset) | major | Type of alarm number | Ifremer / coriolis | Alerts are sent every hour for floats that have transmitted since the last extraction. | 2 weeks |
| Technical issue | TECH_FLAG_Alarm2Type_NUMBER | Type of alarm (0: Low battery voltage, 1: Low external pressure, 2: High external pressure, 3: Low internal pressure, 4: High internal pressure, 5: Low internal temperature, 6: High internal temperature, 7: Low internal humidity, 8: High internal humidity, 9: Gap on external pressure, 10: High speed of descent, 16: Grounding – Volume max reached, 21: Insulation voltage, 29: Hanging – Volume max reached, 30: ISA detection – Number max of detection reached) | major | Type of alarm number | Ifremer / coriolis | Alerts are sent every hour for floats that have transmitted since the last extraction. | 2 weeks |
| Deployment or Retrieval | Note_For_Recovery | This alert is sent when an user add a note on a float on the https://floatrecovery.euro-argo.eu/ website | informational | Content of the user note | https://floatrecovery.euro-argo.eu/ | Triggered when an user write a note | 1 day |
| EEZ | Float_Approaching_EEZ_[Country]_ARV | Any type of float approaching the EEZ of certain countries. The severity of this alert depends on the distance to the EEZ. Countries concerned: Ecuador, Greece, Turkey, Tunisia, Chile, Russian Federation, China, Brazil, India, Argentina, Egypt, Peru. | critical if within the EEZ, major if distance to EEZ < 50 NM, minor if distance between 50 and 100 NM, normal (= closure of any pre-existing alert) if distance > 100 NM. | Distance in NM to EEZ | Oceanops | distance to EEZ is computed every day for floats that have transmitted during the past 3 days | 3 years |
| EEZ | Float_Inside_EEZ_[Country]_NARV | Floats measuring "non-IOC" variables that are inside any EEZ | critical | Last observation date | Oceanops | distance to EEZ is computed every day for floats that have transmitted during the past 3 days | 3 years |
| Icing | FLOAT_APPROACH_ICE | Any type of float approaching the ice cover. The severity of this alert depends on the distance to ice cover. | |||||
| The Arctic and Antarctic daily shapefile - "Overlay" product from U.S. National Ice Center Products (https://usicecenter.gov/Products/ArcticData) is used to compute the distance between the float and the nearest polygon. | Distance in NM to nearest ice. | Oceanops | distance to ice is computed every day for floats that have transmitted during the past 3 days | 3 months |
The fleetmonitoring web interface displays some technical alerts on Argo floats, computed at Coriolis data centre. Our aim with this notification centre is to inform Argo operators in near-real time about most critical alerts triggered on their floats, so appropriate actions or technical investigations could happen, if applicable. It also offers the possibility to be informed by email, acknowledge alerts or a leave a note on a float.
Romain’s recommendation for testing would be for you to subscribe only to alerts from “Technical issue”, Country = “Your country”, and minimum Severity = major or critical. You can also subscribe to all alerts from a specific WMO if you wish.
It is expected you would receive less than 5-10 alerts a month.
THANK YOU FOR YOUR HELP in designing this notification centre that will be used to manage Argo floats alerts, QC feedback, FileChecker rejections, EEZ warnings and more.
Important
AMRIT is funded by the European Union’s Horizon Europe INFRA 2023-DEV-01 Programme under Grant Agreement No. 101132013. The information and views of this website lie entirely with the authors. The European Commission is not responsible for any use that may be made of the information it contains.