Skip to main content
The Events page displays FDD events for your building. You can filter, search, acknowledge, create work orders, and investigate events from a single interface. Switch to Incidents when you want related events grouped together.
Select a building from the sites list, then navigate to FDD > Events > List in the left sidebar.

Events list

The Events list page combines priority filtering and a sortable table. The page header provides controls for streaming, date range, and filters.
Events page with sidebar showing Events List Active Historical and Faults navigation, Pause Streaming button, Last 7 Days date picker, Filters button, priority summary cards for Total 297, Life-Safety 0, Critical 2, Warning 66, and Alert 229, and a Table View listing events with Name, Device, Device Type, Point Name, Point Value, Start Time, End Time, Duration, and Ack'ed columns

The Events list shows priority summary cards, streaming controls, and a sortable table with event details

Select Pause Streaming to stop live updates while you review the current list. Use the Last 7 Days date picker to set the time range for the list.

Filters

Select Filters at the top right to open the filter bar.
Events page header showing filter dropdowns for Areas, Routines, Priorities, Device Types, Ack Status, Domains, Work Order, Event State, and Users, with Save and Clear All buttons, and priority summary cards for Total, Life Safety, Critical, Warning, Alert, and Info

The filter bar provides dropdown slicers for narrowing events by area, routine, priority, and more

The following dropdown slicers are available: Select Save to save the current filter selection as your personal default. Expand the Save dropdown and select Save for Building to apply the filters for all users viewing this building. Select Clear All to remove all active filters.

Priority summary cards

Below the filters, a row of priority cards displays the event count by severity level: Total, Life Safety, Critical, Warning, Alert, and Info. These cards are interactive — select a priority card to filter the table to that severity level. The count on each card updates dynamically as you apply or remove filters. Use the search bar above the table to find events by event name, device name, or building name.

Events table

The table view lists each event as a row with sortable columns. Click the up or down arrows on any column header to sort the table. Customize which columns appear and their order using the column configuration icon in the upper-right corner of the table. Pagination controls at the bottom let you configure the number of lines per page. Click any row to open the event report.

Bulk acknowledge

Select the checkboxes on the left side of the table to choose one or more events. Use Shift + click to select a range. A footer appears with Acknowledge and Create Work Order actions. Select Acknowledge to confirm. Based on your permissions, you may only be able to acknowledge events assigned to you. The count on the Acknowledge button shows how many of the selected events you can acknowledge.

Create work orders per event

Create one work order per selected event from the Events list. Select events with row checkboxes or the header select-all control. In the list footer, select Create Work Order (badged with the selection count). The button uses the same work order creation permission as a single-event work order. This flow does not combine several events into one work order.
1

Select events

Select the events that need field response. The footer shows Acknowledge and Create Work Order with the live selection count.
2

Review the batch

The review dialog lists one row per selected event with Event Name, Device Name, Event ID, and Status. Sort columns and page through the list as needed. Use the delete icon on a row to remove that event from the batch without returning to the table.These statuses describe the work order inside the bulk creation workflow. They are not the operational status of the work order in the destination CMMS.
3

Choose Send Work Orders or Review Each

Select Send Work Orders to send every ready work order in one action. Select Review Each to open the standard work order form for the first event and walk the set one by one.
4

Edit in Review Each (optional)

The form uses the same fields as single-event creation (name, data source, entity, action, title, description, category, subcategory, location, device link, and priority). The header shows the event name, status chip, Event N of M, previous and next controls, and a dropdown to jump to any event in the batch. Use Back or Back to Selected Events to return to the review dialog.
5

Review outcomes and retry failures

After submission, the dialog reports Sent or Not Sent per row:
  • All succeeded — every selected work order was sent to the external system
  • Partial failure — some sent and some not sent; continue editing incomplete rows until they are Ready, then send again
  • Total failure — none were created; complete required fields and try again
In the Review Each path, outcomes can also appear inline in the submission dialog. Successfully created work orders appear under Generated Work Orders with single-event work orders.
Select Cancel Creation only when you intend to leave the flow. The Discard Work Order Creation? confirmation warns that unsaved progress and the current selection are lost. Choose Keep Working to stay in the flow.
There is no bulk apply of category, priority, or location across the batch. Editing in Review Each is one event at a time. Failed submissions are not retried automatically.

Export

Select the download icon from the table toolbar to open the Export Options dialog. Configure the maximum number of rows (default 1,000), select the export type (CSV or PDF), and choose which columns to include.
Export Options dialog showing Maximum number of rows set to 1000, Export type with CSV selected and PDF option, and a column selection list with checkboxes for Building, Priority, Name, Start Time, Duration, Event ID, Area, Device, Device Type, and End Time

The Export Options dialog lets you select the format, row limit, and columns to include

Any active filters also apply to the exported data.

Full screen mode

Select the full screen button in the upper-right corner to maximize the table view for a wider display.

Acknowledge events

Only users assigned to the event’s notification policy can acknowledge it. FDD adds policy recipients as event assignees when it sends notifications.
Each event has one acknowledgment, not one per assignee. If someone else already acknowledged it, you do not need to acknowledge again. You also need building access for that site.
You can acknowledge from the event report header, from the Events list footer after selecting rows, or through the acknowledgment link in email notifications. If the Acknowledge button is unavailable, confirm that your account or role is listed in the policy assigned to the event. See Notification policies for policy configuration.

Event report

Select an event from the table to open its report page. The event report provides automated trend charts, device context, and collaboration tools for investigating a single event.
Event report for Temperature Greater than Setpoint while Occupied on FCU_203, showing a Points Trend panel listing device points with live values, Combined Lines and Bars display mode tabs, a trend chart plotting Zone Temp Setpoint and Zone Temp over time, an Occupancy Command bar chart showing UnOccupied and Occupied periods, and a Reference Devices tab

The event report shows the event name, device, trend charts with point selection, and display mode controls

Event header

The header displays the event name, device name, event ID, and assigned users as avatar icons. If you are a policy assignee, select Acknowledge to confirm you have reviewed the event. FDD generates automated trend charts for the device associated with the event. Use the time range controls and date picker at the top right to adjust the visible window. Switch between display modes:

Point selection panel

The Points Trend panel on the left lists all available points for the device with their live values. Search for specific points or check their checkbox to toggle visibility on the trend chart. Select Show Selected to display only checked points. Select Clear Selection to reset. Use the Reference Devices tab to view and overlay points from related devices.

Event details sidebar

The sidebar on the right side of the event report contains multiple sections accessible through icon tabs. Each tab provides a different layer of context for investigating the event.

Details

Displays core event information including the fault condition description, current state, priority level, triggering point name and value, timestamps, duration, and the affected device, area, and building.
Event report for Temperature Greater than Setpoint while Occupied showing the Details panel with Description explaining setpoint and dead-band logic, Event State set to Closed, Priority set to Alert, Point Name showing Zone Temp, Point Value showing 23.60, Start Time and End Time timestamps, Duration of about 1 hour, and Device, Area, and Building fields

The Details tab shows the fault description, event state, priority, point data, timestamps, and device location

Possible solutions

Lists recommended actions to resolve the fault. Each solution is an expandable card that you can select to view detailed troubleshooting steps.
Event report showing the Possible Solutions panel with four expandable solution cards: 1 - Verify Sensor Accuracy and Labeling, 2 - Inspect HVAC System Components, 3 - Review Historical Data and Operational Trends, 4 - Adjust HVAC System Settings

The Possible Solutions tab lists actionable troubleshooting steps for the detected fault

Parameters

Shows the tuning parameter values configured for the routine that generated the event. Each parameter card displays the parameter name, its current value, and a description of its function.
Event report showing the Parameters panel with cards for Start Delay (30), Heating Setpoint Dead-band (1.5), Return to Normal Delay (5), Cooling Setpoint Dead-band (1.5), Alarm On Delay (15), and Single Setpoint Dead-band (3), each with a description of the parameter's function

The Parameters tab displays all configured tuning parameters with their current values and descriptions

Historical

Lists past occurrences of the same event on the same device. Each entry shows the date and time range. Select any historical entry to navigate to that event’s report. Use this section to identify recurring patterns and assess whether the fault is intermittent or persistent.
Event report showing the Historical panel with a list of previous event occurrences on dates including May 12, May 11, May 8, and March 20, 2026, each showing the time range of the event

The Historical tab lists previous occurrences of the same event with date and time ranges

Work orders

Displays linked work orders for the event. Select + to create a new work order directly from the event report. To create one work order for each of several events from the list, see Create work orders per event.

Referenced devices

Lists related devices grouped by ontology relationship type (for example, hasInputSubstance, isMeasuredBy). Select a device to expand its point list and view live values. Check a point’s checkbox to overlay it on the trend chart for comparison. Use the search bar and relationship filters to narrow the list.
Event report showing the Referenced Devices panel with 4 related devices, relationship filters for hasInputSubstance and isMeasuredBy, and an expanded BTU_L4_HW device showing point values for Flow Rate, Heat Total Energy, Power, Return Water Temp, Supply Water Temp, Total Volume, Device Status, and Connector Status

The Referenced Devices tab shows related devices with live point values that you can overlay on the trend chart

Comments

A shared space for team collaboration. Type a message in the text field and select the send button to post a comment. All team members with access to the event can view and reply to comments.
Event report showing the Comments panel with a Type Here text input field and a send button

The Comments tab provides a text input for adding notes and collaborating with team members

Activity logs

An audit trail of all actions and updates associated with the event. Each entry shows the action taken and a timestamp. Activity logs track event lifecycle changes such as creation, closure, acknowledgments, and status updates.
Event report showing the Activity Logs panel with two entries: Event closed on May 12 at 5:49 PM and This event/incident is created on May 12 at 4:59 PM

The Activity Logs tab records all event lifecycle changes with timestamps

Incidents view

Switch to the Incidents view using the Incidents toggle above the table. Incidents group related events by finding commonalities through ontology relationships, reducing the number of individual issues you need to investigate.
Events page with Incidents toggle selected showing a table with columns for Incident ID, Name, Building, Events, Areas, Priority, Devices, Start Time, End Time, Duration, Assignees, and Ack ID, with two incident rows displayed

The Incidents view groups related events with columns for Incident ID, Name, Building, Events count, Areas, Priority, Devices, Start Time, End Time, Duration, Assignees, and Ack ID

FDD creates incidents using Reference Based Grouping. For example, if a VAV cannot meet its room temperature setpoint, the system checks whether the associated AHU or sibling VAVs also have active events. Related events are grouped under a single incident.

Incidents table

The incidents table lists each incident as a row. Search incidents by Incident ID, Building, or Routines. Click the expand icon on the right side of any row to reveal an inline incident summary without leaving the table. Click any row to open the full incident report.

Incident report

The incident report displays the incident ID in the header along with assignee avatars and an Acknowledge button for policy assignees. Summary cards at the top show Number of Events, Average Event Duration, and Affected Areas.
Incident report for incident 260509-87843 showing Number of Events 32, Average Event Duration About 5 hours, Affected Areas 6, a Status donut chart showing 100% Closed, an Areas bar chart with count and average duration per floor, Domains donut chart with Heating Issue and Cooling Issue, Device Types donut chart, and a Details sidebar with Incident State Closed, Priority Alert, Start Time, End Time, Duration about 9 hours, and Building

The incident report shows summary metrics, status and area charts, domains and device type breakdowns, and a Details sidebar

Overview visualizations display below the summary cards: Overall Impact displays a timeline view of each routine involved in the incident. Color intensity represents the number of affected devices over time. Use the scrubber bar below to zoom into a specific time window. Table View lists all events contributing to the incident in a sortable table with columns for Name, Device, Device Type, Point Name, Point Value, Start Time, End Time, Duration, and Ack’ed. Select any event row to open the event report. Select a device name to navigate to the device details page.
Overall Impact timeline showing Damper Fully Open for Long Periods and Flow Less Than Setpoint routines across a time axis, followed by a Table View with columns for Name, Device, Device Type, Point Name, Point Value, Start Time, End Time, Duration, and Ack'ed listing events across EVAV and SVAV devices

The Overall Impact timeline and Table View list all events contributing to the incident

Select Select Points to choose points across multiple devices for trend comparison. A trend chart appears below the table, plotting the selected points over time.

Incident details sidebar

The sidebar on the right side of the incident report contains three tabs accessible through icon buttons. Details — displays core incident information: Comments — a shared space for team collaboration. Type a message and select the send button to post a comment.
Incident sidebar showing the Comments tab with a Type Here text input field and a send button, alongside icon tabs for Details, Comments, and Activity Logs

The Comments tab provides a text input for notes and team collaboration on the incident

Activity Logs — an audit trail of all actions associated with the incident. Each entry shows the action taken and a timestamp.
Incident sidebar showing the Activity Logs tab with two entries: All events are closed so incident is closed too on May 9 at 5:17 PM, and Merged Flow Less Than Setpoint Flow Less Than Setpoint to create this incident on May 9 at 8:45 AM

The Activity Logs tab records incident lifecycle changes such as creation and closure

Advanced use cases

Subsystem alarm ingestion and writeback

Subsystem alarm ingestion and acknowledgment writeback are limited-release capabilities. They are not available on all environments. Contact your KODE representative if your organization needs this workflow.
Cloud BMS can ingest native alarms from connected subsystems through data sources. This brings BMS and other subsystem alarms into the same Events workflow as routine-generated faults. Operators can view, acknowledge, comment on, and create work orders without switching to the source console. Niagara is the first supported connector. Additional subsystems will use the same normalized alarm structure in future releases.

Capabilities

Current limitations

V1 imports all alarms enabled in the source system. Selective filtering by priority, domain, or alarm name is not available yet. Notification policies do not route email, SMS, or push alerts for subsystem alarms in V1. KODE does not show inline confirmation when acknowledgment writeback succeeds or fails. FDD routines and subsystem alarms run in parallel. Routine-based FDD is not replaced by alarm ingestion.

Acknowledgment writeback

Ack writeback sends an acknowledgment from KODE back to the source subsystem when you acknowledge an alarm on the Events list or event report. This keeps both systems in sync and helps prevent unacknowledged alarms from accumulating in the BMS queue. Acknowledgments made in the source system also appear in KODE. See Acknowledge events for list and report workflows.

Next steps

Faults

Track recurring equipment issues and manage long-term maintenance priorities.

FDD dashboards

View building health at a glance with active and historical event dashboards.

Configuration

Set up monitoring rules and parameters for your building equipment.

Data sources

Configure connectors used by limited-release subsystem alarm ingestion.
Last modified on August 18, 2026