Create Projects & Check Compatibility

1. These workflows are expected as standard deliverables if applicable to the building.

1. V2 - VAV - Induced Heating

2. V2 - VAV - Damper Min / Max

3. V2 - FCU - Heating

4. V2 - FCU - Cooling

5. V2 - AHU - Heating Operation

6. V2 - AHU - Mixed Damper Operation

2. The first step is to create the projects and save them as drafts. This will allow you to check the compatibility of the workflows.

Calibrate & QA Workflow Deployment

1. Workflow calibration consists of small-scale testing on 5 devices per workflow or a floor per workflow. The goal is to ensure the following

1. Points are writable

2. Equipment is responding to commands

3. The parameters are adequately adjusted

4. 80% of tests pass or produce valid results

Set Testing Schedule

1. Once you have some valid results to show the client, sit with them to discuss a testing schedule for the building. We recommend the following best practices

1. Create Projects that span the cooling and heating seasons

1. Start of Spring - End of Summer

1. VAV Damper Operation

2. FCU Cooling

2. Start of Fall - End of Winter

1. VAV - Induced Heating

2. FCU Heating

2. Run these tests weekly, in the late afternoon, on low-occupancy days. This is the ideal testing window because

1. Weekly creates a reasonable workload and cadence for operators to review results.

2. Running in the late afternoon ensures equipment is at a steady state compared to running during startup.

3. Late afternoon and low occupancy days minimize impact on tenants.

4. Running during hours when equipment is already scheduled is more energy efficient than starting equipment in the middle of the night for testing.

3. Another popular option is to test a certain number of devices every day / multiple times a week.  Testing 10 devices a day typically takes less than 30 minutes. This can be scheduled for late afternoon, like 4 or 5 pm, and quickly test all equipment in the building.

Additional Workflows

1. The following workflows can be deployed as needed but are not expected as part of standard delivery.

1. V2 - VAV - Stuck Damper Testing

1. Deployed if Min/Max flow is not compatible or the site team is looking for a more simple version of a test.

2. V2 - VAV - Airflow Setpoint Tracking 

1. Deployed if Min/Max flow not compatible. This will work if the airflow setpoint is writable, but the damper is not.

Product Support

The KODE Labs Product Team maintains and supports the FTT workflow library. We make the following commitments to our partners.

1. We will add new variations within 7 days of receiving clear requirements. A variation is a small adjustment to point requirements, i.e., controlling a fan cmd % instead of a on/off fan command. A new variation is not a request for a custom workflow.

2. Product Support is available for consulting on workflow needs for projects but should never be the first person to review and should not be responsible for delivery unless there is an extreme case.

3. Link Creator Guide