From a single facility to multi-tenant monitoring operations: alarm intake, triage, escalation, and response.
What It Is
GridAlarm is an alarm monitoring and management platform for single-site owners (tied to GridBuilding), multi-building operators (GridCampus / BlueCity / GridFolio), alarm monitoring companies (multi-customer / multi-tenant central station workflows), organizations providing their own internal monitoring and response, and organizations offering monitoring/dispatch services as a service.
GridAlarm supports alarm intake (intrusion, life safety, leak/flow, environmental, access events, duress/panic, equipment alarms), an alarm console with queues, prioritization, acknowledgements, and escalation timers. It creates incidents either via GridCommand integration or GridAlarm's own incidents system. Policies and automation run through GridPolicy; connectors via GridIntegrate (alarm panels, sensors, VMS, access control, BMS). Responder context comes from GridTwin (2D/3D diagrams) and optional GridCommunity/BlueCity exposure controls. Strong audit trails and operator action logging are built in.
GridAlarm also includes a panic lockout mechanism: any authorized user can trigger a panic lockout on their account or local station; it requires a second authorized user to clear (two-person rule); all actions are logged.
Why It Matters
Alarm monitoring is critical for facility safety and operational response. Without a unified alarm platform, operators juggle disconnected panels, call lists, and incident systems. GridAlarm brings intake, triage, escalation, and response into one console—with deep ties to dispatch, digital twin context, and automation. It aligns with central-station operational needs and allows future compliance alignment.
Key Capabilities
Alarm Intake & Normalization
GridIntegrate connectors ingest alarms from panels, sensors, VMS, access control, BMS, and normalize them into a unified event stream.
Alarm Console
Queues, priorities, SLAs, acknowledgements, escalation timers, and operator status with console mode and global pause.
Response Workflows
Internal response vs service provider response with contact lists, escalation ladders, and response plans.
Incidents
Native GridAlarm incidents or GridCommand-integrated incidents with handoff and deep links.
Digital Twin Context
GridTwin 2D/3D diagrams and controlled responder views via GridCommunity/BlueCity.
Automation & Escalation
GridPolicy rules for auto-escalation, routing, and incident creation.
Auditability & Evidence
Strong audit trails, operator action logging, and evidence packets (tie to GridVault/GridComply later).
Multi-Tenant Monitoring
Customers, sites, operators, permissions for central-station style workflows.
How It Ties Into the Ecosystem
GridAlarm integrates with GridIntegrate for alarm sources, GridPolicy for automation, GridCommand for incident handoff, GridTwin for spatial context, GridCommunity/BlueCity for responder views, and GridComply for evidence.
Example Workflows
- An operator receives an intrusion alarm, views site context in GridTwin, acknowledges, creates an incident, and dispatches via GridCommand.
- A monitoring company manages alarms for 50 customers with per-customer sites, contacts, and escalation rules.
- A duress alarm triggers a response plan, notifies the call list, and creates an incident with full audit trail.
- Panic lockout is triggered; a second authorized user clears it with full logging.
Intended Users
Launch Scope & Roadmap
First
- Alarm console
- Intake normalization
- Incidents (native + GridCommand)
- Response plans
- Panic lockout
Next
- Multi-tenant mode
- GridTwin integration
- Evidence packets
- Advanced rules
Later
- UL alignment features
- AI-assisted triage
- Predictive nuisance filtering