L5 IST: The 5 Failure Modes We Still See in 2025
L5 Integrated Systems Testing is the last cheap opportunity to find out what the design missed. After 200+ commissioning engagements, you'd expect the surprises to run out. They don't.
Here are the five L5 failure modes that still show up on new sites — every one caught, all of them worth calling out for anyone briefing a Cx contractor.
1 — Interlock logic that reads clean in isolation, fails in integration
Each system's control narrative reviews cleanly. Then L5 runs a utility drop with battery discharge and generator pickup, and an interlock that assumed a specific breaker sequence trips out of order. It never showed up at L4 because L4 tested each system in isolation.
The fix is always a control-narrative amendment and a re-run — cheap at L5, expensive after go-live.
2 — CRAH failover that leaves stranded flow
Chilled-water loops rebalance on failover in a way the design intent didn't fully simulate. One CRAH takes over the load, another sits at half flow because a modulating valve was tuned in isolation. Under peak load the stranded flow means one cabinet row runs warmer than spec.
Only visible under a full L5 with the cooling on the intended lag/lead pattern.
3 — Fire suppression cause-and-effect that dumps too aggressively
The C&E matrix on paper is fine. Walked out live, a single VESDA alert triggers a partial pre-discharge sequence that shouldn't fire until second-stage confirmation. Wiring correct, logic wrong.
A dry L5 walkthrough finds it before the site is occupied. A skipped L5 finds it during a real event.
4 — BMS points that never actually got mapped
The BMS integrator hands over the graphics and the site accepts. During L5, a simulated sensor failure surfaces three points that were terminated but never mapped to the graphics — invisible until something goes wrong.
Fixable in a day if caught at L5. Fixable in a week if caught after the ops team has moved in.
5 — Documentation that describes a site nobody built
As-builts don't match. The one-line reflects the design; the site reflects the field change that never made it back onto paper. L5 forces the drawing walk-through that turns the red-lines into a defensible record.
Skip it and the next capital project starts with an archaeology dig.
Where Integrator Services fits
Every Integrator Services commissioning engagement runs a full L5 IST — witnessed, documented, and closed before we sign L6. In live environments we script L5 around the workload with explicit isolation and rollback triggers. Send us the SLDs and the current programme; we come back the same week with a plan and an SLA.
Request a scope