Skip to main content
Changes to FDD configurations, devices, points, and routines trigger specific system behaviors. All changes are tracked for transparency and troubleshooting.
Always check if the specific point or device is part of any active FDD config before making changes or deletions. If it is, deselect it from the config first, or confirm that it is not in use. Failing to do this can cause FDD configs to gray out, trigger unwanted alarms, or leave active events that must be manually cleared.

​
Activity log

Every update to configs is recorded at the building level. The log shows what was changed, who changed it, and when it was changed.

​
Automatic actions on config changes

When a config is deleted or disabled:
  • Any related active events or active incidents are automatically closed
  • If an incident has no other active linked FDD configs or events, it is closed

​
Device and point changes

Devices and points are managed through the Config Details page, where you select or deselect devices for each routine and configure parameters in the right panel.
Config Details page for Temperature Greater than Setpoint while Occupied showing folder tabs for All, Folder 1, and Folder 2, a device table with checkboxes listing devices like VAV_207, FCU_403, and VAV_302 with their areas and point counts, and a Routine Params panel on the right showing Arbitrary Heating Setpoint 66, Alarm On Delay 1, Arbitrary Cooling Setpoint 75, Start Delay 30, Heating Setpoint Deadband 1.50, and Cooling Setpoint Deadband 1.50

The Config Details page shows selected devices and routine parameters that are affected by device or point changes

​
Update a point or device

When a point or device is updated (for example, an ontology field is changed), the system checks if it is being used in any FDD configs. If the device or point becomes incompatible:
  • The related configs are grayed out
  • Any active alarms or events linked to it remain active until the device or point is removed from the config
If the point still exists in Cloud BMS but is untemplated, the config can still trigger alarms when its conditions are met, even if the point or device appears grayed out in the config. To remove an incompatible point or device:
  • Delete and recreate the config, or
  • Restore the device or point to its previous ontology fields, open the config, deselect the device or point, and save changes
Always deselect the device or point from the FDD config before making changes, or confirm it is not part of any active config.

​
Delete a point or device

When a point or device is deleted, the system checks if it is used in any FDD configs. Related configs gray out after device or point deletion. If an alarm was already generated for the deleted point or device, it remains active in the FDD list. If only some points of a config are deleted:
  • The config grays out and does not trigger events if the missing point is required for alarms
  • Already-triggered alarms remain active for the deleted devices or points
To clear active events from deleted points or devices, delete and re-enable the FDD config.
Always deselect the device or point from the FDD config before deleting them.

​
Update names

If an FDD config is enabled and the building, device, or point name changes, the updated name does not appear for:
  • Already-triggered events
  • New events from existing configs
Only FDD configs enabled after the change display updated names.

​
Parameter updates

If parameters for an enabled FDD config are changed while it has already-triggered active events:
  • The currently active event remains active under the old parameters
  • FDD does not retroactively update or close events when parameters are changed
  • Once the active event ends, the updated parameters are applied for future event creation
Before adjusting parameters, review active events linked to the config so you can track which are still running under the old conditions.

​
Config actions

The Configs list shows the current status of each routine. Batch actions at the bottom of the page let you delete, disable, enable, or configure multiple routines at once.
Batch Configuration page showing a table with routines like Temperature Greater than Setpoint while Occupied with Event Status Enabled and Fault Status Not Configured, expanded to show Folder 1 with 78 devices and Folder 2 with 1 device, and additional routines in Not Configured status, with Delete, Disable, Enable, and Configure action buttons at the bottom

The Configs list shows routine statuses and Multi-Config folders, with batch action buttons at the bottom

​
Routine updates

​
Update canonicals or entities

If an FDD routine’s configs are enabled and you add or remove canonicals or entities, or change selected points in logic blocks from the routine, the FDD config changes from Enabled to Unconfigured.
Add Devices dialog with Name As set to Base, a Canonicals section showing selectable tags for fcu, vav, ahu, fan, radiantDevice, and uh, and an Entities section showing selectable tags for OM, ZTS, ZTSS, CLGUM, COUNTER, CSM, DAF, DFC, DFCS, DFEN, DFFREQ and more, with Cancel and Save buttons

Canonicals and Entities are defined in the routine's Add Devices dialog -- changes here affect all linked configs

Changing selected points in logic blocks also triggers the config to become Unconfigured.
Select Field dialog in the Logic tab showing a Base dropdown expanded with Required Fields listing occupied_mode and run_status as selectable options, with Cancel and Save buttons

The Select Field dialog in the Logic tab shows the required fields that, if changed, reset linked configs to Unconfigured

​
Delete a routine

A deleted local FDD routine is removed across the portfolio. All FDD configs linked to it are deleted. Any active events linked to it are deleted.
Deleting a routine is irreversible and affects every building in the portfolio that uses it. Verify linked configurations before proceeding.

​
Next steps

Configuration

Set up and manage fault detection rules and monitoring parameters.

Routines

Create and test custom fault detection rules using the logic builder.

Events

Monitor and investigate real-time fault events across your building equipment.
Last modified on August 18, 2026