GridPolicy is the platform's automation and orchestration engine for facilities, campuses, and operational environments. It transforms events from across the ecosystem into repeatable workflows, policy-driven actions, escalations, acknowledgements, and evidence-backed outcomes.
What It Is
GridPolicy is where organizations define what should happen when things occur. It is the rule engine that sits between events and action. It allows organizations to model operational logic across access control, visitor activity, room panels, kiosks, patrols, telemetry, incidents, maintenance triggers, and broader business workflows.
Rather than leaving procedures in PDFs or tribal knowledge, GridPolicy turns them into enforceable and auditable operational policies. It supports simple if/then workflows as well as more sophisticated multi-stage playbooks with conditions, roles, escalations, acknowledgements, and downstream actions across connected systems.
Why It Matters
Facilities are full of conditions that require consistent handling. A forced door, an unacknowledged alert, a missed patrol checkpoint, a leak alarm, a failed access credential, a temperature excursion, a visitor exception, or a room panel emergency acknowledgement are not just isolated events. They are inputs into operational policy.
GridPolicy ensures those events produce consistent outcomes. It reduces operational drift, speeds response, improves auditability, and allows facilities to automate the obvious while still routing human decision-making where needed.
Key Capabilities
Unified Event Intake
Access control events, visitor events, GridStation events, GridComms patrol and panic events, telemetry/alarms, incident records, and work order signals.
Rule Authoring
Event-based triggers, time-based conditions, schedule-aware logic, site/building/zone scoping, severity handling, role-aware routing, and threshold logic.
Workflow Automation
Create incidents, tickets, or tasks. Notify users, groups, or stations. Route to GridCommand. Trigger acknowledgements and log evidence.
Playbooks
Guided operational response steps, checklist execution, owner assignment, escalation on missed steps, and time-to-complete controls.
Governance
Audit trail of rule execution, policy versioning, permissions and approval flows, and test/simulate mode before deployment.
How It Ties Into the Ecosystem
GridPolicy relies on GridIntegrate for normalized event sources. It routes work through GridCommand, enforces actions through GridStation, and interacts with GridComms for field response. It ties into GridPass for visitor and access workflows, and into GridTwin for real-time condition visualization.
Example Workflows
- If a door is forced after hours, open an incident, notify security, push an alert to the nearest station, and escalate if unacknowledged.
- If a patrol checkpoint is missed, notify the supervisor, create an exception record, and require acknowledgement.
- If a leak sensor alarm appears in a critical room, notify operations, display instructions on local panels, and create a work order.
- If a visitor fails a screening rule, notify reception and security and prevent further check-in progress until reviewed.
Intended Users
Launch Scope & Roadmap
First
- Rule engine foundation
- Event-based triggers
- Basic playbooks
- Notification actions
Next
- Visual rule builder
- Complex multi-stage playbooks
- Schedule-aware logic
- Simulation mode
Later
- AI-suggested policies
- Cross-site policy templates
- Predictive escalation
- Compliance auto-reporting