Titan HST allows you to send mass notifications to the phones of users via a smartphone app.
Native Integration Available
This integration requires a Class 4 License and a Ops Link Server. Please contact your account manager for more details.
Integration: Supported Features
- Mass Notifications via Action Plans
- Get Config
- Sync
Integration Requirements
Version Requirements
Verified on Titan HST version 7.54.4
License Requirements
Requires a Titan HST account
Permission Requirements
Requires an API key (Please contact your representative at Titan to acquire this)
Network Requirements
| From | To | Port | Use |
| OpsLink Server | titanhst.com | 443 TCP | Titan HST API - Synchronisation and mass notification |
Native Integration: Sync Configuration
Using the Sureview Advanced Device Setup go to the Sync Tab and add "Titan" as a new Sync System including the following fields
| Title | The user facing name of the Titan system you are connecting to |
| Area | The Area/Site that the Mass Notifications will be used. |
| Type | Titan |
| OpsLink | The name of your connected OpsLink Server |
| Host | N/A - Leave Blank (The integration automatically connects to titanhst.com) |
| Port | 0 (The integration automatically connects on port 443) |
| ExtraValue | api_key=xxxxx; The unique API key obtained from Titan HST (contact Titan HST support ro request your API key) Example api_key=f8yHKDWMspmjUL6LzHVMYBHPmYEIFC7VgBr3M0Kj0zXEKiFo6MMCJ8Y2dZiqALzN; |
Native Integration: Area Sync
Once you have saved your Sync Configuration (described above) you can then add the individual Area Syncs to synchronise Notification Templates (Titan Broadcast Presets) and Notification Users (Titan People, Roles and Lists), against individual Areas in SureView.
Important: It's recommended that you first create a dedicated "Titan" area to synchronise into, this helps keeps the items organised
- Go to the Sureview "Syncs" tab (when adding or editing your Sync System)
- Click Add Area Sync
-
Complete the Area Sync Fields
| Title | The friendly name for the individual Area Sync |
| Area | Which Sureview Area should the sync use. It's highly recommended to sync into a dedicated "Titan" area |
| Identifier |
Leaving the identifier blank will cause sync to bring in all Titan Broadcast Presets. Note: All Titan People, Roles and Lists will be synced in as "Users" in sureview. These are not true logins and have no impact on your user license. If you only want to synchronise specific Notification Templates (Broadcast Filter) then enter a identifier. You can use * wildcards to sync in all broadcast filters with a name that matches e.g. TemplateFilter=*Evacuate*; would match the Titan Broadcast Filters Fire Evacuate
|
| Interval | How often should the system sync into SureView? default: 24 hours |
| Enabled | Enable or Disable the automatic Sync default on |
| Allow Update Area | Allows the sync to automatically move items to a different area Default off recommended to keep off |
| Allow update Device Settings | Allows the sync to automatically update the item settings Default off recommended to keep off |
Triggering Notifications
Once the Titan has been synced into Sureview an action plan with a "Mass Notification" step will need to be created.
Operators will use the Mass Notification action step to send Mass Notifications when needed.,
Please see the following support pages for more details
and
Note: Titan only allows notifications to be sent to registered Titan "users" (people, roles and lists) or via Titan Broadcast Presets (Notification Templates). Selecting anything else in the Mass Notification Action Plan Recipient will cause the notification to be rejected.
Notification Templates
Notification Templates (Titan Broadcasts Presets) should ONLY be created and edited from within Titan HST itself and then synced into Sureview .
Titan HST Notification Templates must not be edited with the Sureview Notification Templates setup page as this will invalidate the link between the sureview notification template and the Titan Broadcast Presets
Comments
0 commentsPlease sign in to leave a comment.