Stateful alarms keep severity, source, duration, acknowledgement, and recovery visible through the event lifecycle.
GEM operations
Know what happened. Know what needs attention.
GEM brings alarms, system health, history, and diagnostics into one operating environment, giving property teams the context to respond, investigate, and verify recovery.
Alarm management
From signal to resolution.
A threshold crossing or equipment disconnect should become a clear workflow—not another unexplained message.
- 01DetectA condition crosses into alarm.
- 02NotifyThe right recipients receive it.
- 03RespondAcknowledge, shelve, or escalate.
- 04RecoverClear the event and preserve its history.
Use email, SMS, push, or call notifications, then escalate an unacknowledged event on a defined schedule.
Shelve known work, latch events that must not be missed, notify on recovery, and review each delivery result.
- Acknowledge and shelve
- Escalation schedules
- Recovery notices
- Delivery history
System health
See the root cause, not a wall of alerts.
GEM can check supported equipment and services by ping, TCP, or HTTP. Dependencies and health rollups represent the relationships among an uplink, switch, controller, and the systems downstream.
When an upstream path fails, dependent checks can be suppressed instead of creating an alert storm.
UpstreamInternet path
InfrastructureCore network
DownstreamControllers & systems
One upstream issue can explain—and suppress—many downstream failures.
Network checks, discovery, dependency rollups, and uptime monitoring are available with the Network Monitoring feature module.
History and context
Follow the chain of events.
Bring commands, access events, alarms, automation runs, site-mode changes, and monitor transitions into a timeline that can be narrowed to the part of the property under review.
Trends in context
Chart tracked values, compare periods and related attributes, overlay automation events, and export the selected data.
Reliability over time
Review device uptime, disconnect counts, average downtime, and exact online and offline transitions across a selected period.
Diagnostics
Find the quiet problems.
Before an upgrade, handoff, or service visit, GEM can run read-only checks across the live system and its configuration. Each result explains what was found and links to the place where it can be reviewed. Nothing is deleted or rewritten automatically.
- Disconnected or stale equipment
- Broken references and duplicate addresses
- Empty or recursive automations
- Sensitive values stored in plaintext
Make operations easier to understand.
Bring the property, connected systems, and escalation requirements. We’ll show how GEM turns available data into a practical operating workflow.