Events are high-priority notifications that need to be responded to in real time to avoid significant occupant discomfort, energy usage, or mechanical issues.

Page Overview

The Event Details page offers robust tools to review, investigate, and triage Events.

ID # & Name

The Event ID and Name can be found in the top left. The ID is auto-generated and corresponds to the date that the event was generated. The name identifies the routine that was violated and specifies the issue detected.

Details

Here you will find key information about the event, such as the associated building, device, floor, priority, start and end times, current status, and any relevant parameters or metadata.

Acknowledgment

Users assigned to an event will see a large acknowledge button at the top right. This allows users to confirm that they have reviewed or addressed the event. Once acknowledged, the event status is updated to reflect that someone has taken ownership. If SLAs are enabled, the time to acknowledge will be checked against the SLA.

When acknowledging user will be presented with a text box to leave comments. Any comment left during acknowledgment will be added to the comment history of the event.

Automated Trends

Event Details automatically trends any points associated with the routine. These trend lines appear at the top of the page, and a red highlighted region displays the duration of the event.

Manual Point Trender

Use the point picker at the top right to trend additional data points for deeper analysis. The point trends will be inserted below the automated trends and above the possible solutions. They will default to display the time period associated with the event's start and end dates.

Possible Solutions

This section offers diagnostic steps and possible solutions to the event. This database is currently a static set of solutions associated with each routine. These are customizable and adjustable on a per-building basis.

External Push

The external push button enables users to create work orders in 3rd party work order systems if integrated. To generate a work order, click Push External Source and then populate the payload to be sent to the 3rd party system. The dynamic fields can be used to rapidly populate data from your specific event instance.

Historical

Displays previous instances of this event on the same device, helping to identify patterns and determine whether recurring issues need closer investigation. Select a historical work order from this list to review the specific trends and scenarios that led to its generation. 

Activity Log

Captures and timestamps all user actions and system updates linked to the event, providing a complete audit trail from creation to resolution.

Assignee

This field details the specific users who have been assigned to the event. These users are assigned automatically according to the notification policy.

Comments

Offers a central space for real-time collaboration, where team members can post observations, updates, and any pertinent communication related to the event.

Logic Blocks

Visually outlines the system’s diagnostic logic, illustrating how sensor inputs, thresholds, and rules interact to trigger the event.