| Training dates | 07 Nov 2016 - 09 Nov 2016 |
|---|---|
| Delivered by | Jamie (Deactivated) <jamie.brown@mpec.co.uk> |
| Description |
|
Active alerts
Managing your active alerts is the most important workflow to add into your schedule and/or processes. You can make use of e-mail alert notifications to receive instantaneous notifications when alert conditions are triggered, and/or you can use the Alerts screen in Centrix to see all the currently active (triggered) alerts and interrogate them.
Standard alert features
Centrix supports a number of preset alerts for various known rail faults/conditions. However, each alert shares the following standard profile;
| Alert name | A unique name for the alert, this will appear in the e-mail subject of any notifications. |
|---|---|
List of e-mail addresses that should receive e-mail notifications. Tip: Use labels to group e-mail addresses into logical groups, rather than using the e-mail field. Tip: Even when using labels for alerts, it is useful to use this when 'trialling' a new alert that you don't want e-mailing to other team members. | |
| Subscribed? | E-mail notifications will only be sent if this is ticked . |
| Suppression period | Use this to stop Centrix sending notifications for repeated alerts. Repeated alerts within the configured period will not trigger e-mail notifications, but will still appear in the alert history in Centrix. |
| Priority | Use this as desired to allow you to make a decision on prioritising active alerts. Tip: Use High/Critical for alerts on critical assets. Tip: You can setup multiple alerts for track circuits/points with High/Low thresholds. |
| Labels | Labels are used to group alerts into their associated teams. They can also be used for informational purposes. Labels can have e-mail addresses attached to them which will define who should receive e-mail notifications for the alert they are attached to. |