Routines Page

Routines Page

KODE gives you a pre-configured library of FDD Routines that you can use to configure your systems more quickly and easily eliminating the need to create new routines from scratch.


To meet your use cases, the FDD Routines page allows you to view and design algorithms or logical flows that can be applied to devices of one or more buildings on the FDD page.


To go to the FDD Routines, from the FDD page, click the Routine option placed on your left side. On this page, you will see the list of all created routines and their Name, Description, Domain, Priority, and Grouping Policy.


Click the “+ Create Routine” button to create a new Routine.


In the "Routines Details" page fill in the required information, including Routine name, put a description, select Domains, Events Grouping, Priority, select Canonical Types and Entities of Base Devices and Reference Devices, and 

  • Set the Max Duration of the test in Minutes.



  • Go to the "Logic" tab, and from the left section drag and drop the fields to create the logical path of the testing.



  • Go to the "Debugger" tab to test your created sequences, end-user-facing parameter names, and help text.

How it works

After building out the logic, you will move on to the Debugger tab. On the left sidebar, you will see the parameters and inputs you defined, and on the main part of the screen, the container for the simulator output.


Verify Parameters (PARAMS)

This section shows the parameters defined in the sequence that are adjustable when configuring a project's routine or workflow. You can also adjust them here to help tune these parameters while testing.

Start the Simulator 

In the center of the screen, click the “Start Simulation” button.

How the Simulator Works

Once the button is clicked, the engine will go through the routine as it would on a device, following it step by step and adhering to the parameters defined on the left, listening for input values.


Notes
Delay times are also adhered to, so if you are testing a sequence that requires a device to be running for 30 minutes first before proceeding, you will also have to wait that length of time in the simulator.  It is recommended, during testing, to change the unit of time to “seconds'' on the timer logic blocks if time compression is needed, but remember to return them to the correct unit before deploying on a project.

Send Input Values

With the simulator running, update the INPUT values under the parameters, and when satisfied, click Send. These values will be provided in the sequence as data input for their respective read blocks.

Info
Remember when testing to think about your defined boundary values and how breaching those should affect the outcome of the test.  For example, if you are looking to trigger an event when a sensor value exceeds its setpoint, you should not only test that condition but also at least one condition where it would not trigger an event.

Verify the expected response from the simulator

If the response is not as expected, return to the logic builder to troubleshoot the cause.

Info
String builders and conditional blocks can be used to help provide additional output to the simulator when more complicated sequences are being developed.

Save the Routine

After you set up the routine click ‘Save’ and your routine will appear on the Routines list.


Clicking on the three dots at the end of each Routines row from the list view, you will be able to Edit, Export, Duplicate and Delete a routine.



    • Related Articles

    • FDD on Mobile App

      Introduction Fault Detection and Diagnostics (FDD) is a proactive approach for identifying and analyzing system failures or faults within a building's infrastructure at their earliest stages. Navigate through FDD Log into the Mobile App and you’ll ...

    • Managing Notification Policies

      Creating a policy In the context of FDD, a policy refers to the establishment of notification preferences. The policy determines the communication method, the message, the recipient group, and escalation patterns. To create a policy, follow these ...

    • FDD User Manual

      Understanding Fault Detection & Diagnostics What is a Fault? A fault is a period of time in which a specified condition is true on a specific device. For example, this is a fault: @8:00am AHU-1 Could not maintain discharge temperature within setpoint ...

    • FDD Batch Configuration

      The goal of FDD configuration is to establish monitoring and alarms on any of the integrated pieces of equipment to determine a system fault. Follow the below steps to configure FDDs of your choice. Go to KDOE OS and select a site. Navigate to the ...

    • Workflows Page

      KODE gives you a pre-configured library of workflows that you can use to configure your own systems more quickly and easily and eliminates the need to create new routines or workflows from scratch. To meet your use cases, the Workflows page allows ...