Alarms and Notifications

Current alarm/event model

The current SEMS event interface exposes:

• active events
• historical timeline
• severity categories
• acknowledged vs unreviewed state
• active vs cleared state

Acknowledgement

The current API and UI support event acknowledgement for accounts with the appropriate permission. Public documentation may therefore instruct an admin/operator to acknowledge reviewed alarms in the event interface.

Notification rules

The current product supports persisted notification rules and webhook delivery.

Publicly verified boundaries:

• rules are disabled by default
• notification management is permission-controlled
• delivery history is available through dedicated API routes
• debounce/repeat/recovery behavior is part of the rule model

Practical operator guidance

• clear the root cause first;
• acknowledge only after the event has been reviewed;
• use historical event context when a fault repeats;
• treat notification rules as an extension of the event system, not as a substitute for commissioning validation.