FDD Configuration enables you to set up and manage fault detection rules across your building portfolio. It helps detect energy, comfort, and maintenance inefficiencies in real-time.

• Not Configured: No configuration exists for the routine.

• Disabled: Configuration exists, but monitoring is paused, meaning no new events are generated.

• Enabled: The routine is actively monitoring devices and generating events.

• Mixed: The routine contains folders with different statuses (e.g., some enabled, some disabled).

Follow these steps to configure multiple FDD routines in a batch:

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

2. Click the Configure button. The Select Policy pop-up window appears.

3. Select a Policy from the dropdown list.

4. Click Configure.

5. The system automatically performs the following actions:

• Finds all compatible devices for the selected routines.

• Creates the initial configuration for each routine.
  

• Enables Events based on the Recommended Type.
  

• Applies default parameters to the routines.
  

• Select the routine name in the Configs list. The Config Details page opens, displaying the following panels:

• Device list: List the compatible devices for that routine..

• Right panel: Displays parameters and settings for the routine.

1. Go to the Parameters section in the Configuration panel (right panel).

2. Adjust the values for each parameter based on your building's operational needs:

• Alarm On Delay: The duration a condition must persist before triggering an alarm.

• Start Delay: The number of minutes after equipment starts before monitoring begins.

• Return to Normal Delay: The time required for a normal state to persist before clearing an alarm.

• Tolerances: The acceptable deviation from setpoints before an event is triggered.

Other parameters are available, depending on the FDD routine’s rule logic. 

3. Consider your equipment and building needs:
   

• Apply tighter tolerances for critical spaces to ensure immediate detection of issues.

• Use longer delays for equipment with normal startup fluctuations to avoid false positives.

In the Possible Solutions section, you can add, edit, or delete the possible solutions.

1. To add a solution, click the + Add Solution button. 

2. To edit a solution, click the three dots button for the solution and select Edit. A pop-up window appears where you can edit the Name and the Body Text where the possible solutions are described. 

3. To delete a solution, click the three dots button for the solution and select Delete. 

Multi-Config folders

This guide shows users how to leverage Multi-Config folders to apply varied settings for device subgroups, enhancing granular control over FDD routines. It is intended for administrators and advanced users who need to apply different settings to subgroups of devices within the same routine.

When to use folders

Multi-Config folders are beneficial when you need to apply different settings to subgroups of devices within the same routine. Consider creating folders in the following scenarios:

• Threshold values: Apply different threshold values for devices in different environments, such as server rooms versus offices.

• Notification policies: Assign distinct notification policies based on the criticality of equipment, for example, critical versus standard equipment.

• Priority levels: Set varying priority levels for different areas of a building, such as executive floors versus common areas.

• Operating parameters: Configure different operating parameters for equipment that operates on different schedules, such as 24/7 versus scheduled equipment.

Create a configuration folder

To create a new configuration folder, 

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

2. Next to the All tab, click  +. An editable field appears. 

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

4. Select and configure devices specific to the new folder.

5. Specify the settings in the panels (Routine Params, Status Setup, Notification Settings, etc.). 

6. Click Save Folder.

Manage multiple folders

Each folder within a Multi-Config routine maintains independent settings for its assigned devices. Follow these steps to manage multiple folders:

1. Switch between folders using the tabs at the top of the Config Details page.

2. Configure each folder with the appropriate settings for its devices:

• Device selections

• Parameter values

• Notification settings

• Base Settings

• Possible Solutions

3. Click Save Folder for each folder individually before switching to another folder.

The routine's overall status displays as Mixed when folders within it have different enabled or disabled states.

Best practices for FDD deployment and tuning

This article provides best practices for deploying FDD, tuning parameters, and organizing configurations for optimal performance and manageability. It is intended for administrators, building managers, and other users looking for guidance on effective FDD implementation and ongoing optimization.

Deployment strategy

Follow these best practices for a successful and phased FDD deployment:

• Start with critical equipment: Prioritize configuring high-priority routines for essential equipment to ensure critical issues are detected first. 

• Test with small groups: Pilot FDD routines on one floor or system before a full-scale deployment across your entire building portfolio.

• Review after one week: Monitor the deployed routines for about one week to identify any false positives or missed issues, allowing for early adjustments.

Parameter tuning guidelines

Adjust FDD routine parameters based on the age and criticality of your equipment to optimize detection sensitivity.

For new equipment:

• Use default parameters initially.

• Tighten tolerances after the break-in period to ensure more precise fault detection.

• Reduce delays for faster response times once the equipment stabilizes.

For older equipment:

• Increase tolerances to account for normal degradation and wear over time.

• Add longer delays to filter out normal fluctuations that might otherwise trigger false alarms.

• Consider lower priority levels for non-critical routines on older equipment.

For critical spaces: 

• Minimize or eliminate delays to ensure immediate notification of issues.

• Use tighter tolerances for precise monitoring.

• Set high or critical priority levels to ensure urgent alerts.

• Enable None grouping for individual alerts to prevent aggregation of critical notifications.

Organization tips:

Implement these organizational tips to improve the management and effectiveness of your FDD configurations:

• Naming conventions: Establish and follow consistent, descriptive naming conventions for all your FDD routines and folders.

• Folder structure: Organize routines into folders based on logical groupings, such as location (e.g., floor, building), criticality, or equipment age.

• Policy alignment: Align notification policies with specific team responsibilities to ensure that the right personnel receive relevant alerts.

• Regular reviews: Schedule monthly configuration audits to verify settings, identify outdated routines, and ensure ongoing optimization.

Common Workflows for FDD Configuration

This article describes typical scenarios and step-by-step workflows for initial FDD deployment and adding custom routines. It is intended for all users of FDD Configuration, especially those looking for practical examples of common tasks.

Initial FDD deployment workflow

Follow this typical workflow for an initial FDD deployment to ensure efficient setup and monitoring of your building equipment:

1. Review the available Library routines to understand the predefined fault detection options. 

2. Select 5-10 high-value routines to start. These are typically routines that address common or critical inefficiencies.

3. Use batch configuration with default settings for these routines to quickly deploy them across compatible devices.

4. Enable the routines and monitor them for approximately one week to observe their behavior and initial event generation.

5. Tune the parameters of the routines based on the results and observations from the monitoring period to reduce false positives and improve accuracy.

6. Gradually expand to additional routines as you gain confidence in the system's performance and accuracy.

Add custom routines workflow

Follow this workflow to integrate and configure custom-built FDD routines:

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

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

3. Configure the devices and parameters for your custom routine according to its specific logic and your monitoring needs.

4. Test the custom routine on a small set of devices to validate its functionality and ensure it performs as expected.

5. Expand the deployment of the custom routine to a wider range of devices only after successful validation.

Troubleshooting FDD configuration issues

This guide provides solutions to common problems encountered during FDD configuration and operation. It is intended for users who are encountering issues or unexpected behavior with FDD Configuration.

No compatible devices found

Cause: Devices lack the required data points for the routine's logic.

Solution: Verify that point templating is complete for the devices you are attempting to monitor. Ensure all necessary data points are available and correctly configured.

Configuration won't save

Cause: There are missing required fields or invalid parameters within the routine's configuration.

Solution: Check for specific error messages and look for red field indicators on the configuration page. These indicators highlight fields that require attention before saving.

Too many notifications

Cause: The routine's parameters are set to be too sensitive, leading to an excessive number of notifications.

Solution: Increase the tolerances and delays in the routine's parameters. This will make the detection less sensitive and reduce the frequency of alerts.

Events not generating

Cause: The routine's parameters are too relaxed, or the routine is currently disabled.

Solution: Review the thresholds and routine status. Ensure the routine is enabled and that parameters are set appropriately to trigger events under desired conditions.

Mixed status unexpected

Cause: This status occurs when Multi-Config folders within a routine have different states (e.g., some are enabled while others are disabled).

Solution: Review each folder's configuration within the routine to ensure all folders are set to the intended status. Adjust as necessary to achieve a consistent state or to manage the mixed status intentionally.

Frequently Asked Questions

This article provides concise answers to frequently asked questions regarding FDD routine monitoring, configuration, and policies. It is intended for all users seeking quick answers to common questions about FDD Configuration.

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. You need to enable configs on all newly-installed devices.

Q: How do parameters affect Events?

A: Events trigger immediate notifications. Parameters control the tolerances and time delays of Event monitoring. Adjusting these will change the sensitivity of your monitoring operations. 

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: No. Notification policies define the following: 

• Communication Method (Email, Push, SMS, Phone Call).

• Message Content (what information does the email / sms body contain). 

• Who is notified.

• Who should be notified if the event is not acknowledged within the expected time frame (escalations).

Policies are uniquely defined by these criteria. Create policies according to the desired workflows of your team.

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

A: Use Reference Based when you want to roll an event into related issues on equipment or equipment relationships. 

Note: You won't receive individual notifications when using reference based and will receive a single notification for all events grouped together. 

Use None only for critical alarms that need individual attention.

FDD routine parameters: Technical reference 

This article provides a comprehensive technical reference for all adjustable parameters within FDD routines, including their definitions, accepted values, and impact on fault detection. It is intended for advanced users, system integrators, and anyone needing detailed technical specifications for FDD routine parameters.

Parameter definitions

The following table provides definitions for the adjustable parameters within FDD routines.

Impact on detection sensitivity

Adjusting these parameters directly affects the sensitivity and behavior of fault detection within FDD routines:

Default values and recommended ranges

Default values for FDD parameters are automatically applied during initial configuration. Recommended ranges can vary based on equipment type, building function, and criticality. For optimal performance, consider the following general guidelines:

• Start Delay: Default values are typically sufficient. Adjust upward only if equipment frequently experiences extended, normal startup cycles that trigger false alarms.

• Alarm On Delay: Start with a moderate delay (e.g., 5-10 minutes). Reduce for critical systems needing immediate attention; increase for less critical systems or those with known minor fluctuations.

• Return to Normal Delay: Set to ensure stability after a fault. A common range is 5-15 minutes, depending on how quickly the system should confirm recovery.

• Tolerances:

• Critical Equipment/Spaces: Use tighter tolerances (e.g., 1-2% deviation).

• Non-Critical Equipment/Spaces: Default tolerances or slightly wider ranges (e.g., 3-5% deviation) are often appropriate.

These ranges should be fine-tuned based on observed operational data and feedback from initial deployments.