Technical Trade SchoolBAS-300 service-series
BAS-308
Concept reading and source route

BAS-308 Reading Guide

How to use this reading guide

This is the concept-review layer for a 100% online course. Read each module before its lesson, complete the retrieval prompts without looking, then use the linked authoritative sources to verify project-specific editions, requirements, and manufacturer procedures.

Online evidence is not OJL: browser simulations, document cases, and isolated remote equipment build reasoning and documentation skill; supervised field performance is recorded separately.

Module 1

Commissioning purpose, process, and roles

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

Vocabulary and working scope

Owner value; quality process; startup versus commissioning; owner; Cx provider; designer; contractor; controls; TAB; operator; AHJ; witness; acceptor; responsibility matrix.

Source-to-result trace

  1. Locate the controlling requirement and establish authority.
  2. Identify the physical and digital boundaries.
  3. Preserve as-found state and timestamps.
  4. Trace the initiating condition through logic, interfaces, equipment, and process response.
  5. Compare expected and actual evidence.
  6. Calculate with units and stated tolerance.
  7. Record action, result, restoration, uncertainty, and owner.

Worked thinking prompt

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

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

Retrieval prompts

Module 2

Requirement traceability from OPR to evidence

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

Vocabulary and working scope

OPR; BOD; contract; submittal; sequence; points; drawings; TAB; training; systems manual; requirement ID; conflict; RFI; acceptance owner.

Source-to-result trace

  1. Locate the controlling requirement and establish authority.
  2. Identify the physical and digital boundaries.
  3. Preserve as-found state and timestamps.
  4. Trace the initiating condition through logic, interfaces, equipment, and process response.
  5. Compare expected and actual evidence.
  6. Calculate with units and stated tolerance.
  7. Record action, result, restoration, uncertainty, and owner.

Worked thinking prompt

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

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

Retrieval prompts

Module 3

Readiness, startup, prefunctional checks, and TAB state

Why it matters: A functional test cannot compensate for incomplete prerequisites or unknown initial conditions.

Vocabulary and working scope

Installation complete; point-to-point; calibration; safeties; startup; TAB; network/trend; schedules; load/weather; permits; witnesses; tools; open issues; blocker severity.

Source-to-result trace

  1. Locate the controlling requirement and establish authority.
  2. Identify the physical and digital boundaries.
  3. Preserve as-found state and timestamps.
  4. Trace the initiating condition through logic, interfaces, equipment, and process response.
  5. Compare expected and actual evidence.
  6. Calculate with units and stated tolerance.
  7. Record action, result, restoration, uncertainty, and owner.

Worked thinking prompt

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

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

Retrieval prompts

Module 4

Functional performance test anatomy

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

Vocabulary and working scope

Unique ID; requirement; purpose; scope; risk; initial condition; manipulation; expected result; tolerance; response/hold time; evidence; pass/fail/blocked/deferred; restore; issue/retest.

Source-to-result trace

  1. Locate the controlling requirement and establish authority.
  2. Identify the physical and digital boundaries.
  3. Preserve as-found state and timestamps.
  4. Trace the initiating condition through logic, interfaces, equipment, and process response.
  5. Compare expected and actual evidence.
  6. Calculate with units and stated tolerance.
  7. Record action, result, restoration, uncertainty, and owner.

Worked thinking prompt

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

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

Retrieval prompts

Module 5

Modes, transitions, resets, and staging tests

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

Vocabulary and working scope

Occupied/unoccupied; warm-up/cooldown; enable; economizer; heat/cool; reset; trim/respond; lead/lag; entry/exit; hysteresis; timers; load boundaries.

Source-to-result trace

  1. Locate the controlling requirement and establish authority.
  2. Identify the physical and digital boundaries.
  3. Preserve as-found state and timestamps.
  4. Trace the initiating condition through logic, interfaces, equipment, and process response.
  5. Compare expected and actual evidence.
  6. Calculate with units and stated tolerance.
  7. Record action, result, restoration, uncertainty, and owner.

Worked thinking prompt

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

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

Retrieval prompts

Module 6

Failure, alarm, power-recovery, and fallback tests

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

Vocabulary and working scope

Sensor failure; loss of proof; high/low limit; communication loss; power recovery; fallback; lockout; alarm routing; operator response; safe simulation; prohibited action.

Source-to-result trace

  1. Locate the controlling requirement and establish authority.
  2. Identify the physical and digital boundaries.
  3. Preserve as-found state and timestamps.
  4. Trace the initiating condition through logic, interfaces, equipment, and process response.
  5. Compare expected and actual evidence.
  6. Calculate with units and stated tolerance.
  7. Record action, result, restoration, uncertainty, and owner.

Worked thinking prompt

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

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

Retrieval prompts

Module 7

Smoke and life-safety interface testing boundary

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

Vocabulary and working scope

Fire-alarm input; smoke-control mode; priority; dedicated controls; fan/damper proof; firefighter control; normal HVAC inhibition; acceptance test; AHJ/witness; restoration; prohibited independent test.

Source-to-result trace

  1. Locate the controlling requirement and establish authority.
  2. Identify the physical and digital boundaries.
  3. Preserve as-found state and timestamps.
  4. Trace the initiating condition through logic, interfaces, equipment, and process response.
  5. Compare expected and actual evidence.
  6. Calculate with units and stated tolerance.
  7. Record action, result, restoration, uncertainty, and owner.

Worked thinking prompt

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

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

Retrieval prompts

Module 8

Evidence, instruments, and time integrity

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

Vocabulary and working scope

Clock synchronization; trend interval; event logs; screenshots; raw export; witness notes; instrument identity/status; uncertainty; naming; configuration; change log; retention.

Source-to-result trace

  1. Locate the controlling requirement and establish authority.
  2. Identify the physical and digital boundaries.
  3. Preserve as-found state and timestamps.
  4. Trace the initiating condition through logic, interfaces, equipment, and process response.
  5. Compare expected and actual evidence.
  6. Calculate with units and stated tolerance.
  7. Record action, result, restoration, uncertainty, and owner.

Worked thinking prompt

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

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

Retrieval prompts

Module 9

Issues, retest, and acceptance boundaries

Why it matters: An issue is not closed by editing the expected result to match actual behavior.

Vocabulary and working scope

Observation versus deficiency; requirement citation; expected/actual; impact; owner; due; workaround; disposition; retest; pass/fail/blocked/deferred/accepted with exception; no coaching.

Source-to-result trace

  1. Locate the controlling requirement and establish authority.
  2. Identify the physical and digital boundaries.
  3. Preserve as-found state and timestamps.
  4. Trace the initiating condition through logic, interfaces, equipment, and process response.
  5. Compare expected and actual evidence.
  6. Calculate with units and stated tolerance.
  7. Record action, result, restoration, uncertainty, and owner.

Worked thinking prompt

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

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

Retrieval prompts

Module 10

Seasonal/deferred tests, turnover, and capstone

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

Vocabulary and working scope

Unavailable weather/load; trigger; date; owner; risk; temporary acceptance; training; sequences; points; trends/alarms; backups; licenses; cybersecurity/access; systems manual; ongoing plan.

Source-to-result trace

  1. Locate the controlling requirement and establish authority.
  2. Identify the physical and digital boundaries.
  3. Preserve as-found state and timestamps.
  4. Trace the initiating condition through logic, interfaces, equipment, and process response.
  5. Compare expected and actual evidence.
  6. Calculate with units and stated tolerance.
  7. Record action, result, restoration, uncertainty, and owner.

Worked thinking prompt

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

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

Retrieval prompts

Required and deeper reading

Adoption note: Standards, codes, project requirements, owner criteria, manufacturer instructions, and employer safety programs control. Confirm the adopted edition and authority before applying a numeric requirement.