KODE OS's FDD Configuration enables you to set up and manage fault detection rules across your building portfolio. Configure monitoring parameters, notification policies, and device assignments to detect energy, comfort, and maintenance inefficiencies in real-time.

Overview 

FDD Configuration is where you activate and customize monitoring rules (routines) for your building equipment. Each routine contains logic to detect specific operational issues—from temperature deviations to equipment failures. The configuration process determines which devices to monitor, what thresholds trigger alerts, and how notifications are delivered.

Key capabilities 

• Configure Events (real-time alarms). 

• Apply routines from the KODE Library or custom rules.

• Set device-specific parameters and thresholds.

• Manage notification policies and priority levels.

• Use Multi-Config folders for granular control.

• Batch configure multiple routines simultaneously.

Events

Events are real-time, high-priority notifications requiring immediate action (e.g., equipment failure, leak detection). 

Open the FDD Configs page 

To begin configuring FDD routines, navigate to the configuration interface.

1. In KODE OS, select FDD from the main navigation.

2. Open the secondary sidebar menu on the left.

3. Select Configs. The FDD Configs page appears, displaying all available routines.

The Configs list

The Configs list displays comprehensive information about each available routine.

• Name: The routine name (click to open configuration details).

• Event Status: Shows if Events are enabled (Enabled, Disabled, Mixed, Not Configured).

• Fault Status: Shows if Faults are enabled (Enabled, Disabled, Mixed, Not Configured).

• Number of Folders: Configuration folders within the routine (for Multi-Config).

• Number of Devices: Total devices monitored.

• Policy: Notification policy for real-time events.

• Priority: Alert priority level (Critical, High, Medium, Low).

• Source: Local (custom) or Library routine.

• Recommended Type: Suggested configuration (Event, Fault, or Both).

• Description: Explanation of what the routine monitors.

Status definitions:

• Not Configured: No configuration exists.

• Disabled: Configuration exists, but monitoring is paused.

• Enabled: Actively monitoring devices.

• Mixed: Contains folders with different statuses.

Quick configuration using automation

The fastest way to deploy FDD is by using automated configuration, which applies recommended settings based on the routine type.

Configure multiple routines

1. In the Configs list, select the checkboxes next to the routines you want to configure.

2. Click the Configure button at the bottom. The Configure Routines dialog appears.

3. Select a Notification Policy (Events Only) from the dropdown.

4. Click Configure. The system automatically:

• Finds all compatible devices.

• Creates initial configuration.

• Enables Events based on the Recommended Type.

• Applies default parameters.

Enable or disable routines

After configuration, you can manage routine status using batch actions.

1. Select configured routines using checkboxes.

2. Click Enable to start monitoring or Disable to pause.

3. Confirm the action when prompted.

Note: Disabled routines retain their configuration but stop generating new events.

Detailed configuration setup

For precise control over monitoring behavior, you can configure routines individually.

1) Open the routine configuration

1. Click the routine name in the Configs list. The Config Details page opens.

2. The page displays:

• Top Menu: Folder navigation (All, Folder 1, etc.)

• Main panel: Device selection and configuration options

• Right panel: Parameters and settings

2) Select devices to monitor

The routine automatically displays compatible devices based on required data points.

1. In the All tab or a specific folder, view available devices.

2. Select devices by:

• Clicking individual checkboxes.

• Select All in the column header.

• Searching by device name.

3. For devices with multiple point options (e.g., dual temperature sensors), select the appropriate combination from the dropdown.

3) Configure parameters

Each routine includes adjustable parameters that control detection sensitivity.

1. Go to the Parameters section in the Configuration panel.

2. Adjust values based on your building's operation:

• Start Delay: Minutes after the equipment starts before monitoring begins.

• Alarm On Delay: Duration condition must persist before triggering.

• Return to Normal Delay: Time required at the normal state before clearing.

• Tolerances: Acceptable deviation from setpoints.

3. Consider your equipment and building needs:

• Tighter tolerances for critical spaces.

• Longer delays for equipment with normal startup fluctuations.

• Wider deadbands for older equipment.

4) Set notification preferences

Configure how and when the routine generates notifications.

1. In the Notification Settings section, configure the following:

• Grouping Policy:

• Reference-based: Aggregates related events into incidents (recommended for most cases).

• None: Each event generates individual notifications (use for critical alarms).

• Priority Level:

• Life-Safety: Immediate action is required to prevent serious harm or life-threatening danger.

• Critical: Urgent issue affecting comfort, energy, or mechanical systems, risking major impact to the entire building.

• Warning: Prompt attention needed for potential risk to comfort, energy, or mechanical systems, typically affecting a floor or portion of the building.

• Alert: System irregularity detected, often impacting an individual zone or indicating early signs of long-term inefficiency.

• Info: Non-urgent notification for informational purposes or system updates.

2. Notification Policy: Select from your configured policies.

3. Customize Base Settings:

• Event Name: Clear, descriptive title.

• On Create Description: What triggered the event?

• On End Description: What resolved the event?

• Possible Solutions: Suggested corrective actions.

5) Enable Events 

Determine whether the routine monitors for real-time events.

1. Select the toggle for Enable Event Streaming if the routine is a critical failure. 

2. Click Save to apply the changes.

Using Multi-Config folders

Multi-Config allows different settings for device subgroups within the same routine.

When to use folders

Create folders when devices need different settings:

• Threshold values (e.g., server rooms vs. offices)

• Notification policies (e.g., critical vs. standard equipment)

• Priority levels (e.g., executive floors vs. common areas)

• Operating parameters (e.g., 24/7 vs. scheduled equipment)

Create a configuration folder

1. In the Config Details page, click + Folder in the left panel.

2. Enter a descriptive Folder Name (e.g., "Server_Room_VAVs").

3. Click Create.

4. Select and configure devices specific to this folder.

Manage multiple folders

Each folder maintains independent settings.

1. Switch between folders using the left panel navigation.

2. Configure each folder with the appropriate:

• Device selections

• Parameter values

• Notification settings

• Event enabling

3. Save each folder individually before switching.

Note: The routine's overall status displays 'Mixed' when folders have different enabled states.

Best practices

Deployment strategy

1. Start with critical equipment: Configure high-priority routines first.

2. Use recommended types: Follow Library suggestions for Events.

3. Test with small groups: Pilot on one floor or system before full deployment.

4. Review after one week: Check for false positives or missed issues.

5. Document customizations: Note why parameters differ from defaults.

Parameter tuning guidelines

For new equipment:

• Use default parameters initially

• Tighten tolerances after the break-in period

• Reduce delays for faster response

For older equipment:

• Increase tolerances to account for degradation

• Add longer delays to filter normal fluctuations

• Consider lower priority levels

For critical spaces:

• Minimize or eliminate delays

• Use tighter tolerances

• Set high/critical priority

• Enable "None" grouping for individual alerts

Organization tips:

• Naming conventions: Use consistent, descriptive names.

• Folder structure: Group by location, criticality, or equipment age.

• Policy alignment: Match notification policies to team responsibilities.

• Regular reviews: Schedule monthly configuration audits.

Common workflows

Initial FDD deployment

1. Review available Library routines.

2. Select 5-10 high-value routines to start.

3. Use batch configuration with default settings.

4. Enable and monitor for one week.

5. Tune parameters based on results.

6. Expand to additional routines.

Adding custom routines

1. Create a routine in Logic Builder (separate tool).

2. Find a new routine in the Configs list (Source: Local).

3. Configure devices and parameters.

4. Test on a small device set.

5. Expand after validation.

Troubleshooting

No compatible devices found

• Cause: Devices lack the required data points.

• Solution: Verify point templating is complete.

The configuration won't save

• Cause: Missing required fields or invalid parameters.

• Solution: Check for error messages and red field indicators.

Too many notifications

• Cause: Parameters are too sensitive.

• Solution: Increase tolerances and delays.

Events not generating

• Cause: Parameters are too relaxed or the routine is disabled.

• Solution: Review thresholds and routine status.

Mixed status unexpected

• Cause: Multi-Config folders have different states.

• Solution: Review each folder's configuration.

Frequently asked questions

Q: How many devices can one routine monitor?

A: No hard limit, but consider manageability.

Q: Do I need to configure every available routine?

A: No. Start with high-value routines relevant to your equipment and expand gradually.

Q: Can I export or import configurations?

A: Routine logic can be imported and exported. Device configurations must be set per building.

Q: What happens during building commissioning changes?

A: You may need to reconfigure if device names or points change significantly.

Q: How do parameters affect Events?

A: Events trigger immediate notifications.

Q: Can I schedule when routines are active?

A: Not directly, but you can disable/enable routines manually or use occupancy-based routines.

Q: Should I use the same notification policy for all routines?

A: Not necessarily. Critical routines might need different recipients or escalation paths than standard monitoring.

Q: What's the best Grouping Policy to use?

A: Use Reference Based for most equipment to see related issues together. Use None only for critical alarms that need individual attention.