Technical Trade SchoolBAS-400 developer-series
BAS-402
Concept reading and source route

BAS-402 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

Sequence authority and requirement decomposition

Why it matters: A sequence is an executable contract; missing conditions and conflicts are documented and resolved before code creates an accidental design decision.

Vocabulary and working scope

OPR; design intent; sequence of operation; equipment submittal; safety matrix; point list; control diagram; shall statement; assumption; conflict; request for information; acceptance criterion.

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 sequence requires economizer cooling, the equipment submittal limits damper travel, and the points list omits mixed-air temperature.

Calculation: Count and reconcile requirement statements against implemented, tested, deferred, blocked, and unresolved items.

Retrieval prompts

Module 2

Modes, state machines, and transition tables

Why it matters: Every mode needs explicit priority, entry, action, exit, indication, timeout, and restart behavior; otherwise two valid conditions can produce an undefined state.

Vocabulary and working scope

Occupied; unoccupied; standby; warm-up; cooldown; setup/setback; smoke; freeze; shutdown; manual; fault; entry; action; exit; priority; timeout; hysteresis; restart.

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

Warm-up and smoke shutdown become true together during a controller restart.

Calculation: Enumerate mode combinations, verify one effective state, and calculate timeouts and minimum dwell periods.

Retrieval prompts

Module 3

Safeties, permits, proofs, shutdown, and restart

Why it matters: Software may respond to a listed or field safety but must not be represented as replacing required hardware, approved interface, or qualified testing.

Vocabulary and working scope

Hardwired safety; software interlock; permit; proof; command; trip; lockout; reset; retry; post-run; fail position; fan status; airflow proof; freezestat; smoke interface; high/low limit.

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 supply fan command is on, proof fails after delay, the VFD reports run, and a smoke contact changes state.

Calculation: Calculate proof delay, retry window, post-run, and maximum time to safe state; reconcile command, drive, proof, and process evidence.

Retrieval prompts

Module 4

Setpoints, deadbands, timers, reset, and limits

Why it matters: The program must expose both requested and effective setpoint and identify every limit, reset, override, and fallback that can change it.

Vocabulary and working scope

Active setpoint; user setpoint; default; limit; deadband; hysteresis; rate limit; ramp; minimum on/off; delay; linear reset; trim/respond; demand; fallback; quality.

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 duct-static setpoint rises despite low damper requests because stale zone requests continue to trim the loop.

Calculation: Calculate reset slope, response step, request persistence, rate limit, and bounded effective setpoint.

Retrieval prompts

Module 5

Terminal-unit sequence patterns

Why it matters: Terminal logic must match the physical terminal and central-system strategy; adding airflow reference to hybrid VVT improves evidence but does not turn one central heating/cooling source into independent zone heating and cooling.

Vocabulary and working scope

Pressure-independent VAV; pressure-dependent VAV; fan-powered box; series/parallel fan; reheat; cooling minimum; ventilation minimum; airflow sensor; damper; discharge temperature; VVT; hybrid measured-airflow VVT; VRF interface.

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 rooftop unit serves four zones using programmable VAV-class controllers, crossflow pickup tubes, and a hybrid Carrier/Trane-inspired VVT strategy.

Calculation: Calculate airflow setpoints, percent design flow, heating/cooling demand, damper bounds, and central-mode vote or request thresholds.

Retrieval prompts

Module 6

AHU fan, SAT, static pressure, and trim-and-respond

Why it matters: Reset responds to persistent valid demand and sheds stale or failed requests; it never substitutes for proper sensor location, airflow setup, or fan safety.

Vocabulary and working scope

Supply/return/relief fan; start/stop; proof; VFD; duct static; SAT; reset; critical zone; request; trim; respond; high static; low temperature; fan tracking; sensor location.

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

One VAV remains at 100% damper because of a failed airflow pickup and drives the AHU static setpoint to maximum.

Calculation: Calculate static reset steps, request persistence, SAT reset, fan tracking offset, and response/settling acceptance.

Retrieval prompts

Module 7

Economizer, ventilation, freeze protection, and humidity

Why it matters: Economizer and ventilation logic must distinguish minimum ventilation from free cooling and must define sensor validity, lockouts, integrated cooling, damper proof, and safe low-temperature response.

Vocabulary and working scope

Outdoor-air enable; dry-bulb; enthalpy; high limit; mixed air; minimum outdoor air; DCV; damper limits; mechanical cooling integration; freeze protection; low-limit control; dehumidification; humidity lockout.

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

Outdoor air is cool but humid, mixed-air temperature is unreliable, and the return fan is below its minimum speed.

Calculation: Calculate mixed-air temperature estimate, outdoor-air fraction where measurements permit, high-limit decision, ventilation setpoint, and low-limit response timing.

Retrieval prompts

Module 8

Plant staging, lead-lag, minimum flow, and reset

Why it matters: Plant efficiency logic cannot violate manufacturer minimum flow, anti-recycle, safeties, or project staging authority.

Vocabulary and working scope

Enable; demand; proof; lead/lag; rotation; staging; debounce; minimum run/off; standby; failure; lockout; differential pressure; bypass; minimum flow; supply-temperature reset; load aggregation.

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 lead pump fails proof during low load while the standby pump is unavailable and the chiller requires minimum evaporator flow.

Calculation: Calculate load fraction, stage thresholds, run-hour rotation, minimum flow margin, differential-pressure reset, and retry timing.

Retrieval prompts

Module 9

Guideline 36 mapping, requests, alarms, and fallback

Why it matters: Guideline 36 is a source of uniform sequence intent, not permission to ignore adopted project requirements, equipment limits, or documented deviations.

Vocabulary and working scope

ASHRAE Guideline 36-2024; generic sequence; project adaptation; zone group; request; suppression; reset; fault response; alarm; sensor failure; fallback; override; operator display; acceptance.

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 project specifies a custom VAV sequence but also references Guideline 36 for trim-and-respond and fault behavior.

Calculation: Build a clause-to-code/test matrix and calculate request thresholds, persistence, suppression, and bounded reset behavior.

Retrieval prompts

Module 10

Program package, peer review, simulation, and controlled release

Why it matters: A program is not complete when it compiles; it is complete when approved intent is traceable, critical cases pass, deployment is controlled, and restoration is proven.

Vocabulary and working scope

Code review; requirement coverage; test harness; normal/boundary/fault/restart cases; download plan; backup; compare; version; witness; rollback; operator notification; issue log; as-left.

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 offline simulation passes, but the field controller has a different firmware revision and one unavailable function block.

Calculation: Reconcile requirements and tests, compare versions/checksums, calculate response tolerances, and prove rollback within the approved window.

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.