Functional Performance Testing: From Sequence of Operation to Evidence

Start with the approved operating story

The sequence of operation describes how a system is intended to behave. The functional test turns that description into evidence. Every important mode, transition, interlock, alarm, safety, reset, staging decision, and recovery should be traceable to a test step or to a documented reason it was excluded.

This translation often reveals ambiguity before field testing. If two reasonable readers expect different responses, the sequence needs clarification. Discovering that conflict during test development is far less expensive than arguing about it while a full project team waits in the mechanical room.

Separate readiness from functional testing

Functional testing is most productive after installation, startup, point-to-point checkout, controls checkout, TAB, and required manufacturer activities are complete. A readiness checklist should confirm that sensors are credible, devices can stroke, safeties are active, setpoints are documented, and required trends are configured.

When those prerequisites are incomplete, the test becomes a mixture of startup, programming, repair, and acceptance. The record becomes difficult to interpret because the tested system is changing while the test is being performed.

Build each step around cause and response

A good test step identifies the initial state, the action that creates the condition, the expected response, the measurement or observation, the allowed time or tolerance, and the pass or fail decision. The method should avoid damaging equipment or defeating a safety without an approved procedure.

• Normal operation at representative load
• Startup, shutdown, and occupied-to-unoccupied transitions
• Capacity modulation, staging, lead-lag rotation, and reset logic
• Alarm initiation, annunciation, routing, acknowledgment, and recovery
• Loss of a sensor, device, power source, communication path, or supporting system
• Interactions between HVAC, electrical, plumbing, life-safety, and controls systems

Document the result so someone else can follow it

The final report should show what happened, not only a pass/fail box. Record dates, participants, equipment identifiers, test conditions, relevant setpoints, trend intervals, instruments, observations, measured values, deficiencies, corrective actions, and retest results.

Deferred or seasonal tests should remain visible. A system that could not be demonstrated at the required load has not produced the same evidence as a completed test, even when the deferral is reasonable and approved.