Technical Trade SchoolBAS-300 service-series
BAS-308
Ten concept and evidence figures

BAS-308 Visual Aid Library

Figure-use rule

Each figure is an orientation and reasoning aid, not a project drawing. Learners must pair it with the current sequence, point list, wiring/piping documents, manufacturer instructions, and as-found evidence.

Figure 1 — Commissioning purpose, process, and roles critical

Normal-rule anchor

Commissioning is a managed quality process, not a synonym for point checkout or one functional test.

Case overlay

A controls contractor is asked to sign final owner acceptance for a sequence outside the assigned role.

Calculation/evidence callout: Reconcile responsibility-matrix assignments and identify unowned, duplicated, or unauthorized decisions.

Figure 2 — Requirement traceability from OPR to evidence critical

Normal-rule anchor

A test expected result must come from the approved requirement chain, not tester preference.

Case overlay

The OPR requires humidity control, but the sequence and point list contain no humidity function.

Calculation/evidence callout: Build a requirement trace matrix and reconcile required, designed, submitted, implemented, tested, and accepted status.

Figure 3 — Readiness, startup, prefunctional checks, and TAB state critical

Normal-rule anchor

A functional test cannot compensate for incomplete prerequisites or unknown initial conditions.

Case overlay

The AHU is scheduled for FPT while TAB is incomplete and two critical sensors are unverified.

Calculation/evidence callout: Calculate readiness completion by required item, but any critical blocker forces blocked status regardless of percent.

Figure 4 — Functional performance test anatomy critical

Normal-rule anchor

Commanding a point and seeing it change is not a complete FPT; process response, timing, evidence, and restoration are required.

Case overlay

A script says “verify economizer works” without conditions, expected values, tolerance, or evidence.

Calculation/evidence callout: Calculate expected response/tolerance/time from supplied requirement and define pass/fail boundaries before execution.

Figure 5 — Modes, transitions, resets, and staging tests

Normal-rule anchor

A sequence may pass steady-state checks while failing entry, exit, priority, timer, or recovery behavior.

Case overlay

The AHU cools correctly after manual enable but fails scheduled warm-up exit.

Calculation/evidence callout: Calculate transition conditions, timer windows, reset targets, staging thresholds, and expected state sequence.

Figure 6 — Failure, alarm, power-recovery, and fallback tests critical

Normal-rule anchor

Failure testing requires greater control than normal-mode testing because the test intentionally removes trusted conditions.

Case overlay

A sensor-failure test is proposed by disconnecting a production input without impact or restore planning.

Calculation/evidence callout: Calculate persistence, delay, fallback duration, recovery sequence, and alarm-routing response from synchronized evidence.

Figure 7 — Smoke and life-safety interface testing boundary critical

Normal-rule anchor

Life-safety acceptance tests follow dedicated approved procedures and authorities; ordinary HVAC FPT authority does not transfer automatically.

Case overlay

A commissioning script asks the BAS technician to simulate a fire-alarm input without the fire-alarm contractor or AHJ plan.

Calculation/evidence callout: Use the approved state/priority matrix and timestamped proof list; no generic calculation substitutes for acceptance criteria.

Figure 8 — Evidence, instruments, and time integrity critical

Normal-rule anchor

Evidence must allow another reviewer to reproduce what was tested, under which conditions, and with what measurement limits.

Case overlay

Three systems log the same transition at different times and the screenshot omits point identity.

Calculation/evidence callout: Calculate clock offsets, response times, tolerance, uncertainty, and data-age limits before scoring the result.

Figure 9 — Issues, retest, and acceptance boundaries critical

Normal-rule anchor

An issue is not closed by editing the expected result to match actual behavior.

Case overlay

A failed static-reset test is relabeled acceptable because the project is behind schedule.

Calculation/evidence callout: Reconcile issue status counts and verify that every closed issue has correction, retest evidence, and authorized disposition.

Figure 10 — Seasonal/deferred tests, turnover, and capstone critical

Normal-rule anchor

Deferred does not mean forgotten; each test needs a trigger, responsible owner, due condition, risk treatment, and closure evidence.

Case overlay

Heating-season testing is deferred in July and no owner or trigger is assigned.

Calculation/evidence callout: Reconcile required, completed, failed, blocked, deferred, retested, accepted, and open tests, plus training/turnover deliverables.