Overview of Remote Notifications
Desigo CC has the capability to send out remote notification (RENO) messages—delivered, for example, using email, SMS or pagers—to one or more groups of contacts (recipients).
Remote notifications can be of two types:
- Alarm-triggered notifications: Messages preconfigured in the system to be sent out when certain alarms occur in the building control site. These alarm-triggered notifications are set up in Engineering mode. Also, they can be configured to be sent out by the system either with (manual sending) or without (automatic sending) operator intervention.
- New (operator issued) notifications: Messages composed and sent on the initiative of the operator. These operator-issued notifications are instead always sent with operator intervention (manual sending). They are not tied to any triggering event, and can be sent out at any time in Operating mode.
Operators can interact with remote notifications in the following ways:
- Start, Stop, or Resend a Remote Notification (Alarm-Triggered or Operator-Issued)
- Monitor the Progress and Outcome of Sent Notifications (Alarm-Triggered or Operator-Issued)
- Enable or Disable an Alarm-Triggered Remote Notification
Location of Remote Notifications
Alarm-triggered remote notification objects are located under Applications > Remote Notifications in the Application View of System Browser.
Recipients of a Remote Notification
Remote Notifications (whether alarm-triggered or operator-issued) can be addressed to one or more recipient groups (for example, supervisors, operators) selected from the Desigo CC Overview of Address Book. These recipients do not necessarily have to be Desigo CC users.
- For each individual contact, the address book stores a preferred device (email address, mobile phone number, or pager number) that can be used to contact that person, and optionally also a fallback device.
- Desigo CC will attempt to send the notification to all the members of each recipient group, using the preferred and (if available) fallback devices configured in the address book. (It will try the preferred device first and, if that fails, it will try the fallback device).
- For sending to succeed it is necessary for the corresponding system services (for email, sms, or pager communication) to be configured.
Replies from Recipients and Escalation Rules
Depending on how a remote notification is configured, it may or may not require a response from the recipients of the message.
How Recipients can Reply to a Remote Notification
When the recipients receive a remote notification message (via email, SMS, or pager) they can acknowledge the notification by replying to the message in the following ways.
- Email: reply to the email message without adding any additional text.
- SMS: reply to the SMS in one of the following ways:
- Paste and send back the received text message, including the numeric code at the end of the received text message.
- Send a text message that contains the numeric code included at the end of the received text message.
- Pager: notification acknowledge is not supported.
NOTE:
Replying to a remote notification message only acknowledges the notification. It is not the same thing as acknowledging the event, which is instead done by sending an Acknowledge command from Event List (see Send Alarm Handling Commands).
Remote Notification Event Log
When working with remote notifications, entries are recorded in the History Database tracking the progress of remote notifications (such as, remote notification devices status error, remote notification creation/deletion or start/stop, and so on).
