Everbridge CEM
The Everbridge CEM integrated system provides critical event management.
Definitions
Critical Event Management (CEM) — Management of critical events such as severe weather, workplace violence, active shooters, terrorism, IT and power outages, environmental discharges, critical equipment failures, medical emergencies, social media attacks, etc.
Incident — An object in the Everbridge system which can be used to send information to certain contacts. Incidents can hold variables and accept inputs for them.
Scenario — This is the parent for multiple incidents within the Everbridge system. This can be used to launch multiple incidents. For example, sending notifications in different languages for different contacts.
Setup
See the Data Servers page for information on configuring driver communication.
Prerequisites
Software | Version |
---|---|
.NET Framework | 4.7.2 |
IPFusion — Everbridge CEM | 1.0 |
When completing your setup, be sure to have the Everbridge documentation available for reference.
Ports
These ports must be open in your network firewall for the integration to work.
Purpose | Default Value | Configurable |
---|---|---|
Dataserver | 9630 | Yes |
Debug Tools | 9631 | No |
Third Party Configuration
When creating incident templates, the integrated system uses Azure Cloud Hosting to receive the events. To configure this, navigate to the Incident Template. In Publishing Options and check Web Posting/Azure.
https://evbgremote.azurewebsites.net/api/incident?orgid=OrganizationID
The OrganizationID
is replaced with the ID of the Everbridge organization. The
username and password will need to be provided for the web endpoint.Communication Configuration
In the integrated system configuration panel, you will find the Communication Settings. The following information is required:
Username | The Username of the Everbridge account owner. |
Password | The Password of the Everbridge account owner. |
Organization ID | The Organization ID of the Everbridge account owner. |
Assets
System
The system asset is a representation of the connection state to the Azure Web Posting Queue.
Supported States
Normal | The asset is online and in its default state. |
Masked | The asset has been masked over its true state. |
Fault | An issue has been detected in a connected asset. |
Acknowledged | An asset alarm has been acknowledged. |
No Communication | Communication has been lost with the driver or asset. This status can
also occur if the communication configuration for the system or asset is
invalid. Note: This status is required in all status
tables.
|
See the Configure a Status Table page for more information on configuring status tables.
Supported Commands
Mask | Mask the asset's true state. |
Acknowledge | Acknowledge an asset alarm. |
Reset | Resets the asset to its true hardware state. |
Cancel | Deselects all selected assets. |
See the Command Tables page for more information on configuring command tables.
Workflow Integration
System Commands
System commands are commands executed through Workflows at the system level. For more information about Workflows, see the Workflows section.
Launch Scenario
Provides the ability to launch a scenario.
Scenario Name | The Name of the Scenario to launch. |
Parameters | A comma separated list of key-value pair strings in the
form key::value that are appended as
additional configuration parameters for the templates of the
scenario being launched. Note: Some scenarios may have
required parameters. You can view further information
about parameters here. |
Launch Scenario With Incident Name
Provides the ability to launch a scenario, and pass an incident name to call it under.
Scenario Name | The Name of the Scenario to launch. |
Incident Name | The Name displayed on the Everbridge dashboard of the launched scenario. |
Parameters | A comma separated list of key-value pair strings in the
form key::value that are appended as
additional configuration parameters for the templates of the
scenario being launched. Note: Some scenarios may have
required parameters. You can view further information
about parameters here. |
Launch Incident
Provides the ability to launch an incident.
Template Name | The Name of the Template used to launch the incident. |
Parameters | A comma separated list of key-value pair strings in the
form key::value that are appended as
additional configuration parameters for the templates of the
scenario being launched. Note: Some scenarios may have
required parameters. You can view further information
about parameters here. |
Launch Incident with Name
Provides the ability to launch an incident, and pass a given name.
Template Name | The Name of the Template used to launch the incident. |
Display Name | The Name displayed on the Everbridge dashboard of the launched incident. |
Parameters | A comma separated list of key-value pair strings in the
form key::value that are appended as
additional configuration parameters for the templates of the
scenario being launched. Note: Some scenarios may have
required parameters. You can view further information
about parameters here. |
System Events
System events are events used to trigger Workflow actions at the system level. For more information about Workflows, see the Workflows section.
Incident Opened
Provides the ability to receive a notification of an activated incident.
Title | The title of the notification or triggered incident. |
Message | The body of the notification or triggered incident. |
Troubleshooting
Logs from the driver and Runtime can be viewed in the Debug Tools client. These messages contain information which can provide further context for issues during initialization, or while actively running. This can help diagnose problems.