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

BAS-407 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 process, intent, roles, and test authority

Why it matters: The person who writes or corrects code does not automatically have authority to accept it; roles and evidence remain distinct.

Vocabulary and working scope

Cx process; OPR; BOD; design review; submittal; sequence; points list; control drawing; prefunctional checklist; FPT; commissioning authority; contractor; witness; deficiency; 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

The programmer is asked to sign acceptance for an AHU sequence before the owner witness attends.

Calculation: Reconcile requirements, test steps, roles, witnesses, acceptance authority, and unresolved items.

Retrieval prompts

Module 2

Readiness, safety, prerequisites, and baseline

Why it matters: Testing an unready system creates misleading failures and risk; unmet prerequisites are evidence, not pressure to proceed.

Vocabulary and working scope

Approved test; JHA; qualified role; occupancy/process impact; communication; current documents; point completion; TAB status; sensor calibration; equipment readiness; weather/load; backup; rollback; abort; as-found.

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 functional test is scheduled while TAB is incomplete, freeze conditions exist, and the latest program backup is missing.

Calculation: Score prerequisite completion, identify critical blockers, and calculate available test window against stabilization and restoration time.

Retrieval prompts

Module 3

Point-to-point checkout, scaling, identity, and proof

Why it matters: Point checkout proves the entire signal or command chain; seeing a value change on one screen does not prove identity, scaling, or physical action.

Vocabulary and working scope

Point ID; physical label; wiring; object; units; range; polarity; state text; calibration; command; output; feedback; proof; fail position; quality; priority; graphics; trend.

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

Two room sensors are swapped in software and a damper output changes on screen but not at the actuator.

Calculation: Calculate scaling, error, tolerance, percent span, command/feedback difference, and point completion/defect counts.

Retrieval prompts

Module 4

Command priority, overrides, safeties, release, and restoration

Why it matters: A test is incomplete until every software and physical temporary state is explicitly reconciled and normal control is proven.

Vocabulary and working scope

Priority array; effective command; operator override; test force; HOA/local; safety; interlock; manual mode; expiration; relinquish; default; override register; 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

A valve remains open after a test because the command was released at one priority but another override remains active.

Calculation: Reconcile every active priority, local/manual state, temporary account, alarm inhibit, jumper, and expected normal value before closeout.

Retrieval prompts

Module 5

Loop performance, tuning, disturbance, and acceptance

Why it matters: Tune only after sensor, final element, direction, range, authority, and upstream process are verified; trend evidence must span disturbance through recovery.

Vocabulary and working scope

SP; PV; output; direct/reverse; bias; gain; integral; derivative; dead time; lag; saturation; overshoot; settling; steady-state error; disturbance; load; acceptance band.

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 static-pressure loop overshoots after a setpoint step while one damper is mechanically stuck and the fan minimum is too high.

Calculation: Calculate error, overshoot, settling time, oscillation period, percent saturation, and acceptance-band duration.

Retrieval prompts

Module 6

Modes, states, transitions, schedules, and restart tests

Why it matters: Steady operation in one mode does not prove transition logic; failures often live at startup, shutdown, overlap, timeout, and restart boundaries.

Vocabulary and working scope

Occupied; unoccupied; warm-up; cooldown; standby; manual; fault; smoke/freeze response; entry; exit; dwell; timeout; schedule exception; power cycle; network loss; recovery.

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

An AHU restarts into occupied cooling after a brief outage even though a freeze trip remains latched.

Calculation: Measure transition time, dwell, timeout, recovery, and schedule alignment against the test tolerance.

Retrieval prompts

Module 7

Safeties, failure modes, fallback, and negative testing

Why it matters: Critical negative tests must be planned with qualified roles and safe simulation methods; software testing cannot replace required device or life-safety acceptance.

Vocabulary and working scope

Loss of proof; sensor failure; communication loss; high/low limit; smoke interface; freeze; trip; degraded mode; fallback; lockout; retry; alarm; safe position; manual recovery.

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 simulated supply-air sensor failure drives a fallback setpoint but suppresses the alarm and leaves economizer enabled.

Calculation: Calculate time to safe state, alarm delay, retry count, fallback limits, and recovery time.

Retrieval prompts

Module 8

Integration, end-to-end timing, data quality, and external systems

Why it matters: An integration point is accepted only when identity, units, state meaning, authority, quality, timing, physical response, and owner are proven end to end.

Vocabulary and working scope

Controller; supervisor; gateway; OEM; network; command; priority; status; units; enumeration; quality; timestamp; latency; routing; alarm; trend; schedule; demarcation.

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 chiller enable reaches the gateway but returns a delayed run status in a different enumeration and the alarm timestamps disagree.

Calculation: Calculate latency, clock offset, update interval, stale threshold, mapping coverage, and loss/recovery duration.

Retrieval prompts

Module 9

Issues, severity, correction, retest, witness, and acceptance

Why it matters: A cleared symptom is not closure; the corrected mechanism, changed case, regression scope, restoration, and authorized acceptance must be documented.

Vocabulary and working scope

Observation; deficiency; severity; impact; evidence; owner; due date; correction; retest; regression; changed case; witness; exception; deferred acceptance; closure.

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 fan-proof defect is corrected by changing delay logic, but no test verifies real loss of proof or restart behavior.

Calculation: Reconcile open, corrected, retested, accepted, deferred, and rejected issues; no critical issue can be averaged away.

Retrieval prompts

Module 10

Turnover, changed-case defense, and systems manual

Why it matters: Turnover artifacts must be current, reproducible, appropriately protected, and usable by the people who inherit the system; a quiz score cannot compensate for a critical safety, identity, evidence, or restoration failure.

Vocabulary and working scope

As-built; sequence; points list; drawings; code; database; backup; restore note; test record; issue log; alarm matrix; trend list; schedule; credentials handoff; operator training; systems manual; changed case; evidence defense.

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 accepted program differs from the archived version, operator training uses an old graphic, and the changed case introduces one swapped point and one unrelated mechanical defect.

Calculation: Compare revisions/checksums, required versus delivered artifacts, restore-test status, training task success, changed-case evidence, and open ownership.

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.