IP Integration Module

Overview

The AtHoc IP Integration Module is used to “IP-enable” legacy mass notification systems, such as Giant Voice, campus cable TV, local radio, and serve as a conduit between them. The IP Integration Module connects these traditional, non-IP systems with the AtHoc IWSAlerts mass notification platform to provide a comprehensive and unified emergency mass notification system.  AtHoc IWSAlerts provides a Unified Notification™ management system, allowing operators to alert personnel from a single web-based console, including integration with and activation of numerous traditional, non-IP-based systems.

Benefits

• Single unified activation – AtHoc IWSAlerts can activate the external systems along with other devices  as part of the same scenario, assisting in the streamlining of operations and reduction in alert activation time in emergency situations
• Simplified alert activation – Simplified activation and message consistency across communication systems and delivery devices
• Consistent messaging – Operators can choose to have the external systems use the same message as other alerting devices or have a separate message as determined by the scenario or permitted operator
• Remote web-enabled activation – Web-enablement and remote activation of the external systems, allowing them to be activated from any network connected computer, providing activation redundancy
• Map based selection – Support geographical based targeting using AtHoc’s internal map-based GIS targeting
• Scheduled automatic alerting – AtHoc IWSAlerts supports scheduled automatic activation; for example, weekly test alerts
• Permission based activation – AtHoc IWSAlerts permission management system can limit system activation to only authorized operators

Architecture and Deployment

The AtHoc IP Integration Module is a PC-based appliance that connects to the local network, and uses the Common Alerting Protocol (CAP) or XML over HTTP/S to communicate with the AtHoc IWSAlerts server.  Normally the module is installed in the vicinity of the legacy alert delivery system, and connects to it using non-IP interfaces, such as a serial port (e.g. RS-232), dry contacts and audio-out connectors.

The IIM supports legacy, non-IP systems by physical connections supporting the following interfaces:

• Serial interface (RS-232, RS-485)
• Dry contacts
• Audio-out
• Dual-tone multi-frequency (DTMF)

The IIM typically connects to the external system’s central control unit (CCU) and activates it using one or more of the above standard interfaces. Two IIM boxes can be used concurrently, each interfacing to a separate CCU, for redundancy purposes.

Fig. 1: Architecture Diagram for triggering alerts to Giant Voice and PA systems