The BAS/controls commissioning process from design review through functional performance testing, the independent commissioning agent's role, functional test scripting, common findings, retro-commissioning vs. new-construction commissioning, and continuous commissioning enabled by analytics.
Installing a BAS and verifying it are two different functions, and conflating them is one of the most consequential mistakes on a controls project: a system can pass a superficial acceptance test while still failing to execute its sequence of operation correctly across the full range of conditions it will actually encounter. This module works through design review, point-to-point verification, and functional performance testing in the order they actually happen, why an independent commissioning agent's findings carry more weight than a contractor self-certifying its own work, and the specific, repeatable structure a functional test script needs to be defensible.
By the end of this module you should be able to distinguish new-construction commissioning from retro-commissioning, explain why the most common commissioning findings (sequence deviations, sensor miscalibration, setpoint conflicts, missing interlocks) recur across nearly every project, and see how continuous commissioning extends this discipline into an ongoing practice — the same FDD infrastructure Module 16 builds its optimization strategy on.