Notification Groups
Notification groups are the building blocks of
the notification system. These are configurable and
expandable to satisfy the many different business rules and needs of our
customers. In this article we will review the configuration of a Notification Group, settings, notification types, report content and frequency. Most buildings will have a single notification group that includes all devices however you can create as many notification groups as needed, to split your access group responsibilities by floor, critical areas, or tenant spaces.
Device Detail Admin access level is required to edit a notification group.
Updating Notification Groups
Updating contact information and creating a new recipient is done within the Notification Recipients section.
Once you have confirmed that a notification recipient has a profile and their contact information is accurate, we can finish setting up the Notification Group.
Navigate from sidebar-> Groups-> Notification Groups-> select a notification group or Create new.
The summary page of a Notification Group shows us the current configuration. We have broke this page down into 3 sections.
- Current notification recipients and the type of notification they will receive on the right. In this example, the recipients are assigned to different calling hours. We will discuss this below.
- The notifications tab tells us the content the recipients in Section A will receive.
- The Day of the Week tabs show us that reports are currently setup on those days and times. Selecting each day will expose the content included on those daily reports.
- The device included in this notification group. Most customers will have a single notification group for all devices however you can create multiple notification groups to meet your needs.
Edit Notification Group
Once you enter the editing of the notification group you will see 7 steps across the top.
Make sure you select Save and continue after each step.
Step 1-Define
Active- You can deactivate a notification group which will place it in the inactive tab on the notification group overview page. This will turn off all notifications for the group and make it easy to reactivate if needed at a later time.
Call Retries- When a voice call is initiated, the system will ask a user to confirm the alarm. In the image below, if no recipients are reached, the system will attempt 2 retries of the phone tree.
After Hours- The notification group allows you to create an after hours calling tree. If enabled, you will set your normal business hours and any days that should have the after hours calling tree applied ALL DAY.
In the example below, our normal hours calling tree will be enabled Monday-Friday 8am-5pm. The after hours calling tree will be enabled Monday-Friday from 5pm-8am AND all day on Saturday and Sunday.
Step 2-Recipients
- Recipients are broken into sections based on the calling tree they are associated with. If you wish to move a recipient to a different calling tree, you can use the buttons on the right side for Normal and After hours.
- If a recipient has a notification recipient profile but are not part of the notification group, they will appear at the bottom under Not contacted.
- Use the X on the far right side of a recipient if you wish to remove them from a notification group. They will then be placed under Not contacted.
- If a recipient was added to a notification group but their recipient profile was later made inactive, they will appear with a red X under the Active column.
In the example below,
- Bill W. is Active and will receive the daily Report (See Step 6). Bill will receive email and text notifications for the content selected on Step 4. Bill will also receive Voice notifications, at all hours, in the event of a water alarm.
- Bob S. is Active and will receive text notifications for the content selected on Step 4. Bob will receive Voice notifications for a water alarm, during the normal hours selected on from Step 1.
- Kelsi B. is Not active. If her recipient profile was made active again, she would receive email notifications for the content selected on Step 4. Kelsi will also receive voice notifications for a water alarm, on the days/times selected from Step 1 Afterhours.
Step 3- Calls
Recipients are put in their respective calling tree based on our selection in Step 2. Use the up and down arrows to change the calling order.
Step 4- Devices
Here we select the devices we want to be part of this notification group. Devices are organized by the tabs for each device type. If you have a single notification group for all device, you will select each device tab, and select all devices.
Failure to associate a device with a notification group will prevent the proper notification from being received.
Trident requires that every device be part of at least one notification group. If a device is not part of a notification group, a red banner will be displayed on the Dashboard.
Step 5- Notifications
Step 5 allows us to select the content our recipients will be notified for.
In this example,
- Our voice recipients from Step 2 (Bill, Bob, and Kelsi), will receive a phone call in the event of Water detected.
- Bill and Kelsi are configured to receive email notifications from Step 2 and will receive an email for a leak cleared, manual or auto reset, and if an Smart Base Station (SBS) reports lost communication.
- Bill and Bob are configured to receive text notification from Step 2 and will receive text notifications for a leak cleared, manual or auto reset, and if an Smart Base Station (SBS) reports lost communication.
Step 6- Reports
Step 6 allows us to set the days and times a daily report will be sent. Use the tabs for days of the week, select the send time and content to be included on the report.
Below we see that the Monday report will be sent out at 7am. The report will include any devices in lost communication, any device in alarm, and any devices that have critical battery or power disconnected.
Reports are pulled at the time they are sent (7am). If a device is included on a report, we recommended logging into Trident and verifying the device status as the health of a device can change later in the day.
Step 7- Webhooks
The Trident Alarm Webhook API is a lightweight API that provides one-way data sharing to user defined URLs triggered by Trident System Alarm events. From a Trident perspective, webhooks are considered as a type of notification to a recipient, similar to e-mails, texts and phone calls. It produces a machine to machine (M2M) notification via the webhook.
See Also
Notification Set Up Video
Related Articles
Trident Voice Notifications
Depending on your notification group configuration, Trident can call you in the event of a water alarm or SBS lost communication. Voice notifications will only go out at the intitial detection of a water alarm and all future notifications (for the ...Notification Recipients
Notification Recipients are configured to receive several types of communications for reports, alarms, and reports based on site needs. A recipient needs to have a profile create prior to adding them to a notification group. To view or make changes ...How do I make changes to my notification recipients?
Notification recipients are easily managed by an end user with the Function Admin access level. From the sidebar->Groups->Notification recipients. If you do not have Function Admin rights, you will not be able to make changes to notification ...How do I remove a device from Trident?
If a device is missing or needs to be removed from the Trident Platform you can change the device Status. Changing a device to a removed state will remove it from reports, notifications, and groups. It is important to understand the 3 different ...Valve Reports
A valve report can be produced to view all active valves, names, valve groups and trigger endpoints. This report should be verified for accuracy and can be exported for future use. Go to Reports-Valves from the sidebar. This report gives you a ...