Create, schedule, and manage Functional Testing projects to automate equipment testing across your building in Cloud BMS.
FTT projects automate testing across entire buildings, multiple floors, and extended time periods. A project assigns devices to a workflow, sets a testing schedule, and groups tasks by floor or device count for systematic execution.
Navigate to FTT from the left sidebar, then select the three-dot menu at the top right and choose Projects.
Choose the building where you want to run tests. This step completes automatically if you navigate to FTT from within a building.
2
Select a workflow and parameters
Choose the testing workflow for your project. The left panel lists all available workflows from the library. Select a workflow to view and adjust its parameters on the right.
Step 1: Select a workflow from the library and adjust its parameters
Each workflow includes adjustable parameters that control success criteria and time limits. Adjust these values to match your building’s specific requirements.
Select the devices to test during the project. Use the search bar and filters to narrow devices by Canonical Type and Area. For building-wide commissioning, select all compatible devices. You can also select specific floors or individual devices.
Step 2: Select devices to include in the project with search and area filtering
4
Set the schedule
Configure when and how tests run. The schedule defines the testing cadence, grouping strategy, and recurrence pattern.
Step 3: Configure the testing schedule with grouping, frequency, and task preview
Schedule project
Option
Description
Now
Finalize the schedule immediately
Decide Later
Save the workflow and parameters as a draft and set the schedule later
Group by
Option
Description
By Floor
Test one floor per commissioning day, working from bottom to top
By Count of Devices
Test a fixed number of devices per day (such as 5, 10, or 50)
By None
Include all selected devices in a single group with one testing period
Choose a grouping strategy
Use By Floor when operators review results by area and you want a clear floor-by-floor cadence.
Use By Count of Devices when floors are uneven or you want a fixed daily workload (for example, 10 devices per day).
Use By None for a small selection, a single floor already filtered in device pick, or a one-time commissioning batch.
Date and timeSet the project start date and the time each test begins. Common configurations schedule tests during late afternoon when equipment runs at steady state.The Date is the earliest possible start date. Test on Day (for weekly cadence) is the weekday when runs are allowed. Cloud BMS schedules the first run on the first selected Test-on-Day that falls on or after the Date.For example, if Date is Friday, February 7 and Test on Day is Monday, the project does not run on February 7. It starts on the next Monday after February 7.Test frequencyUse Test Every and Test on Day to define how often tests run. The schedule preview updates as you configure these fields.RecurrenceEnable the Recurring toggle and optionally turn on Advanced Settings to configure repeat behavior.Simple recurrence starts the next cycle after the current cycle finishes. Advanced scheduling starts the next cycle a set time after project start or project end. The platform blocks overlapping advanced schedules.
Advanced recurrence settings with repeat timing, delay, and estimated next occurrences
Option
Description
Repeat After
Choose whether the next cycle starts after the project is completed or after the project has started
Delay
Set a delay period (in weeks) between project cycles
Ends
Choose Never for continuous testing or After to limit the number of recurrences
Schedule previewThe preview table shows all scheduled tasks with their dates, device counts, and estimated next occurrences. Tasks are automatically named based on floor or group.
Reorder tasks: drag the handle on the left side of each row
Edit or delete a task: select the three-dot menu on a task row to edit its details or remove it from the schedule
Add Task: after you remove a device from an existing task, Add Task becomes available. Use it to create a new task for devices that are not in any group, then assign those devices on the Devices tab
Three-dot menu on a task row with Edit and Delete options
The Edit Task dialog lets you modify task-level settings on two tabs:
Details: change the task name, start date, start time, notify users, and adjust workflow parameters for this specific task
Edit Task Details tab with task configuration and parameter overrides
Devices: add or remove individual devices from this task
Edit Task Devices tab showing device selection for a specific task
5
Add details and notify users
Complete the project configuration with a name, description, notification settings, and simultaneous test limits.
Step 4: Configure project details, notifications, and maximum simultaneous tests
Hide Project configuration fields
Field
Description
Project Name
Descriptive name for the project scope, such as “Spring FCU Heating” or “Annual VAV Damper Testing”
Description
Summary of the project. Select the auto-generate icon to create a description from your schedule configuration.
Reason
Category for creating the project, such as “Routine Maintenance”
Specific Reason
Additional detail about why the project was created
Notify Users
Select specific users to notify before tests, after tests, or both
Notify Roles
Select a role (such as Operator/Engineer) to notify all users in that role
Max Simultaneous Tests
Number of devices tested at the same time within a single task (range: 1 to 5)
Confirm whether notifications send before tests, after tests, or both when you select users and roles.
Select + Work Order to configure automatic work order creation when testing completes. Work orders push results to an external system through the QR Connect API.
Work Order configuration with trigger, criteria, and payload settings
Field
Description
Name
Identifier for the work order rule
Create On Completion Of
Trigger point: Project, Task, or Test
Avg Score
Score range that triggers work order creation (for example, 0% to 99% to capture all non-perfect results)
Field / Operator / Action
Filter conditions (for example, Status In Completed)
The Configure Payload section maps FTT data to your external work order system. Set the data source, entity, and action, then fill in the required fields using template variables.
Payload configuration mapping FTT data to external work order fields
Available template variables include Task Name, Task Score, Workflow, Building, Task Reason, Task - Number of Devices, Task Started At, Task Ended At, Task Readable Duration, Task Duration, Test Status, Device, and Area.Select Save to create the project. A preview of the project and all scheduled dates appears.
Projects often run over weeks or months. As tasks complete, statuses turn green and average scores update for each task. Select a project from the list to open its details.
The Details tab shows all scheduled tasks with their execution history and scoring. The right panel displays project metadata including workflow, device count, completion percentage, status, description, recurrence settings, and assigned users.
Project details view showing scheduled tasks, scores, and project metadata
Expand a task row to view the individual devices assigned to that task. Select one or more tasks to access bulk actions at the bottom of the page.
Expanded task showing individual device assignments with action buttons
The Devices tab provides a cross-project view of all device test results. A stacked bar chart shows completed, failed, and archived test counts per floor. A donut chart summarizes overall pass rates. The device table lists individual scores and allows sorting and searching.
Devices tab with test result charts and individual device scores
Recurring projects enable continuous commissioning. Set up annual testing cycles aligned with heating and cooling seasons, or run year-round continuous testing.
