PSAP Notification & Alerting: Mass Emergency Communication Platform

Overview#

A tornado warning is confirmed at 7:42 p.m. on a Tuesday. The affected area covers three counties, 280,000 residents, and six languages. The communications centre has approximately four minutes to reach as many people as possible before the system becomes overwhelmed. The Notification & Alerting module is built for exactly that four-minute window.

The module delivers a mass emergency communication platform for PSAPs and emergency communications centres, enabling rapid dissemination of emergency alerts across multiple channels with geographic targeting, multi-language support, and Common Alerting Protocol compliance. It serves police dispatch centres, fire and rescue operations, EMS coordination hubs, and multi-agency coordination centres that need to reach large populations fast, with accuracy, and across every available channel simultaneously.

Key Features#

IPAWS Integration & WEA Broadcast#

• Common Alerting Protocol (CAP) 1.2 Compliance: Industry-standard alert messaging with alert metadata including sender, severity, urgency, certainty, and event category
• SAME (Specific Area Message Encoding) event codes for national compatibility
• Geographic targeting via polygon, circle, and county FIPS codes
• Multi-language support with effective date/time, expiry, and cancellation handling

Multi-Channel Mass Notification#

• SMS Text Messages: Standard 160-character SMS with universal carrier compatibility
• Long SMS auto-segmentation for messages up to 1,600 characters
• Unicode support for international languages
• Email, push notification, social media, and TTY/relay service channels delivering redundant message paths

Geographic Targeting & Segmentation#

• Polygon Drawing: Custom boundary definition drawn directly on an interactive map
• GIS shapefile import for county boundaries and evacuation zones
• Multi-polygon support for non-contiguous affected areas
• Radius-based targeting for circular alert zones

Subscriber Management & Opt-In Compliance#

• Subscriber Capacity: 10M+ subscribers per agency with real-time replication across data centres
• Point-in-time recovery for data corruption events
• TCPA-compliant opt-in and opt-out management

Real-Time Delivery Tracking & Analytics#

• Live Delivery Dashboard: Real-time progress visualisation with recipients-reached counter, delivery rate graph, and per-channel breakdown
• Automated alerts when delivery rates fall below expected thresholds
• Historical campaign analytics for after-action review

Geofence-Based Public Warning Targeting#

Geographic targeting through drawn polygons and county codes is now complemented by persistent geofence entities that PSAPs define once and reference in alert composition. Public warning geofences are maintained in the geofencing domain with full audit trail, and any active incident linked to a geofence carries that geofence's boundaries into the alert composition interface.

• Persistent Alert Geofences: Geofences are saved as named, reusable entities in the platform, so a recurring flooding zone or wildfire risk corridor can be used in multiple alert campaigns without re-drawing the boundary each time.
• Incident-Linked Geofence Context: When a public warning is issued against an active incident, the linked incident's geofence context is carried into the alert, so the alert polygon automatically reflects the incident's declared impact boundary rather than requiring a second boundary definition.
• Impact Density Provenance: Each geofence carries the data source and provenance of its boundary definition, so alerts composed against that geofence carry an auditable record of why the affected area was defined as it was.
• Public Warning Audit Trail: Every public warning issued against a geofence is recorded in a typed audit trail with actor, organisation, geofence identifier, CAP message identifier, and timestamp, providing regulators and IPAWS administrators with a complete record of geofence-based alert issuance.
• Common Operating Picture Context: Issued public warnings with geofence context are surfaced in the PSAP Common Operating Picture, so dispatchers can see live alert boundaries alongside field units and active incidents rather than consulting a separate alert management system.

Benefits#

• Broad Reach: 50,000+ recipients per minute enables county-wide alerts in under four minutes
• Multi-Channel Redundancy: Multiple simultaneous delivery channels ensure message receipt even when individual channels are congested
• Geographic Accuracy: Polygon-based targeting reduces alert fatigue in areas outside the affected zone
• Scalability: 10M+ subscriber capacity supports population growth and regional consolidation without infrastructure changes
• Compliance: TCPA-compliant delivery prevents regulatory exposure

Use Cases#

• Emergency dispatch centres issuing tornado warnings, flood alerts, or evacuation orders across large geographic areas
• Multi-agency coordination centres coordinating mass casualty event notifications to hospitals, utilities, and public
• Police dispatch operations issuing Amber Alerts or active threat notifications to specific neighbourhoods
• Fire and rescue operations notifying residents of evacuation zones during wildland fire events
• Island and remote emergency services reaching dispersed populations through SMS and satellite-connected channels

Integration#

The module connects with IPAWS for national WEA and EAS broadcast, wireless carrier networks for cell broadcast and SMS delivery, email service providers, push notification platforms, social media APIs, and TTY/relay services for accessibility-compliant alerting. CAP 1.2 format ensures compatibility with all national and state alerting infrastructure.

Open Standards#

• OASIS Common Alerting Protocol 1.2 (CAP 1.2): All emergency alerts are composed, validated, and serialised as CAP 1.2 XML (namespace urn:oasis:names:tc:emergency:cap:1.2), enforcing mandatory fields, severity/urgency/certainty enumerations, polygon area definitions, and cancellation references before submission to IPAWS OPEN.
• EAS / SAME (47 CFR § 11.31): Specific Area Message Encoding headers are generated and validated in strict conformance with the FCC rule, including originator codes, three-letter event codes, six-digit SAME location codes (up to 31 per message), and duration quantisation rules.
• CTIA Wireless Emergency Alerts 3.0 (WEA 3.0): Outbound WEA channel payloads are constructed to the CTIA WEA 3.0 profile, enforcing the 360-character body limit, permitted character set, and WEAHandling event-code vocabulary before delivery via IPAWS OPEN.
• W3C XML Digital Signature (XMLDSig): Each CAP document is signed with an RSA-SHA256 enveloped signature using Exclusive C14N canonicalisation before submission to FEMA IPAWS OPEN, following the W3C XMLDSig specification (http://www.w3.org/2000/09/xmldsig#).
• NENA i3 / NG911 Audit Standard: Every CAP egress event is written as a CAP_EGRESS_ISSUED audit record conforming to the NENA i3 audit-trail model, providing a tamper-evident log for after-action review.
• FIPS 6-4 County Codes: Geographic targeting uses six-digit Federal Information Processing Standard county codes as SAME geocodes within CAP area blocks, ensuring compatibility with national alerting infrastructure and EAS location routing.
• Unicode (ISO/IEC 10646) / UTF-8: Alert text is encoded in UTF-8 throughout, with multi-language <info> blocks per the CAP specification, enabling delivery in any of the supported languages to diverse populations.
• GeoJSON (RFC 7946) / WGS 84: Persistent geofence boundaries are stored and exchanged as GeoJSON Polygons on WGS 84, enabling interoperability with mapping systems and GIS tools that consume geofence definitions.

Last Reviewed: 2026-07-28 Last Updated: 2026-07-28