All changes are tracked for transparency and troubleshooting.

Important Before You Begin

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’s 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 for FDD Config Changes

Every update to configs is recorded in the back end at the building level.

The log shows:

• What was changed

• Who changed it

• When it was changed

Automatic Actions on FDD 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/events, it is closed.

How FDD Responds to Common Actions

Update Point or Device

When a point or device is updated (e.g., an ontology field is changed):

• The system checks if it’s being used in any FDD configs.

• If the device/point becomes incompatible:

• The related configs are grayed out.

• Any active alarms/events linked to it will remain active until the device/point is removed from the config.

• If the point still exists in KODE OS but is untemplated:

• The config can still trigger alarms when its conditions are met, even if the point/device appears grayed out in the config.

• To remove an incompatible point/device:

• Delete and recreate the config, or

• Restore the device/point to its previous ontology fields → open the config → deselect the device/point → save changes.

Best Practice: 

Always deselect the device/point from the FDD config before making changes, or confirm it is not part of any active config.

Deleting a Point or Device

When a point/device is deleted:

• The system checks if it is used in any FDD configs.

• Related configs gray out after device/point deletion.

• If an alarm was already generated for the deleted point/device, it remains active in the FDD list.

• If only some points of a config are deleted:

• The config grays out and will not trigger events if the missing point is required for alarms.

• Already-triggered alarms remain active for the deleted devices/point(s).

• To clear active events from deleted points/devices:

• Delete and re-enable the FDD config.

Best Practice:

​

Always deselect the device/point from the FDD config before deleting them.

Updates on Building, Device, or Point Names

If a FDD config is enabled, and the building, device, or point name changes:

• The updated name will not appear for:

• Already-triggered events

• New events from existing configs

• Only FDD configs enabled after the change will display updated names.

Config-Specific Actions (FDD Configs)

Disable Configs

Configs are disabled and all linked events/incidents are closed.

Enable Configs

Configs are activated; events will trigger after alarm conditions are met.

Update Configs

Changes are saved and recorded in the system.

How FDD Configs Responds Routine Updates

Updating Routine Canonicals or Entities

• If a FDD routine’s configs are enabled and you add/remove canonicals or entities, or change selected points in logic blocks from the routine, the FDD config changes from Enabled to Unconfigured.

Deleting 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.