Skip to main content
The FDD Settings page provides four configuration tabs that control how events are prioritized, acknowledged, displayed, and triaged across your portfolio.
Navigate to FDD in the left sidebar, then select Settings at the bottom of the secondary sidebar.

Priorities

The Priorities tab defines the severity levels assigned to events, incidents, and faults. Each priority level has a name, description, color-coded badge, SLA configuration, and visibility toggle.
FDD Settings page showing the Priorities tab with five levels: Life-Safety with description Immediate action required to prevent serious harm or life-threatening danger and a 90 min SLA, Critical with description Urgent issue affecting comfort energy or mechanical systems risking major impact to the entire building with No SLA, Warning with description Prompt attention needed for potential risk to comfort energy or mechanical systems typically affecting a floor or portion of the building with No SLA, Alert with description System irregularity detected often impacting an individual zone or indicating early signs of long-term inefficiency with No SLA, and Info with description Non-urgent notification for informational purposes or system updates with No SLA, each with a colored badge, Edit button, and visibility toggle, and a Reset to default button at the top right

The Priorities tab lists all priority levels with their descriptions, SLA settings, and visibility controls

The default configuration includes five levels: Each priority level supports the following options:
  • SLA — set a time-based service level agreement for response (for example, 90 minutes for Life-Safety)
  • Edit — modify the name, description, color, or SLA for the priority level
  • Visibility — toggle the priority level on or off. Hidden priorities do not appear in filters or event views.
Select Reset to default to restore the original Cloud BMS priority configuration.

Acknowledgment

The Acknowledgment tab controls how users acknowledge events. Only users assigned to the event’s notification policy can acknowledge it. These settings control comment requirements. They do not change who is allowed to acknowledge.
FDD Settings page showing the Acknowledgment tab with a single option: Acknowledgment with Comments toggle enabled, with the description Acknowledge events and leave a comment to maintain clarity and accountability, and a Save button at the bottom right

The Acknowledgment tab lets you require comments when acknowledging events

Toggle
When enabled, users must leave a comment when acknowledging an event. This maintains clarity and accountability by requiring documentation of the acknowledgment action.
Select Save to apply changes.

Table Management

The Table Management tab controls column visibility and ordering across Events, Incidents, and Faults tables throughout your portfolio. Each table type maintains independent column settings.
FDD Settings Table Management tab showing three column groups side by side: Event Columns with 17 total columns and 17 active showing Name, Device, Device Type, Point Name, Point Value, Start Time, End Time, Duration, Priority, and Work Order Url with blue toggles, Incident Columns with 13 total columns and 12 active showing Incident ID, Name, Building, Events, Areas, Priority, Devices, Start Time, End Time, and Duration, and Fault Columns with 14 total columns and 14 active showing Device, Routine, Status, Est Cost, Occurrences, Duration, Time in Fault Per Day, Watchers, Labels, and Last Comment, all last changed Nov 25 9:44 AM, with a Reset to default button

Table Management shows column toggles for Event, Incident, and Fault tables side by side

Each column group displays a count indicator (for example, “Total columns: 17, Active columns: 17”) and the date of the last change.

Configure columns

  • Toggle visibility — use the switch next to each column name to show (blue) or hide (gray) the column
  • Reorder columns — click and hold the drag handle next to any column name, drag to the desired position, and release

Apply changes

When you select Apply changes, a confirmation dialog appears.
Apply table management changes confirmation dialog stating You're about to apply these table management changes to all buildings, The edits aren't saved yet, When applied updates will roll out across the system, with Keep editing and Apply changes buttons

The confirmation dialog warns that changes will roll out across the system

Resetting to default applies instantly and affects all users portfolio-wide. Coordinate with your team before resetting.
Individual users can customize their own column preferences per building. User preferences override the organization’s portfolio or building-level settings.

Column reference

Triage Rules

The Triage Rules tab defines automated rules that manage fault statuses and labels based on time-based conditions. Each rule has a description, an optional label, a configurable time parameter, and an enabled toggle.
FDD Settings Triage Rules tab showing a table with columns for Triage Rule, Description, Label, Parameter, and Enabled, listing six rules: Reopened with label Reopened and 1 days parameter, Overdue with label Overdue and 1 days parameter, Work Order Created with label Work Order and no parameter, Work Order Closed with label Work Order and no parameter, Revert In Progress to Open with no label and 2 days parameter, Revert Suppressed to Open with no label and 2 days parameter, and Revert Resolved to Open with no label and 2 days parameter, all with blue enabled toggles, and a Reset to default button

Triage Rules automate fault status changes and label assignments based on configurable time windows

Use the toggle in the Enabled column to activate or deactivate individual rules. Select Reset to default to restore the original triage rule configuration.

Next steps

Events

Monitor and investigate real-time fault events across your building equipment.

Notification policies

Control how FDD delivers alerts through email, SMS, push, and phone calls.

Handling FDD updates

Understand how configuration changes affect active events and incidents.
Last modified on August 18, 2026