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

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

Operational policy, ownership, and source hierarchy

Why it matters: An alarm, trend, or schedule without an owner and defined operational purpose becomes noise, cost, or hidden risk.

Vocabulary and working scope

Alarm philosophy; trend standard; scheduling policy; owner; responder; escalation; operating hours; service level; project sequence; operator authority; retention; audit; change control.

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 building has thousands of alarms, no documented response owners, and three conflicting occupancy schedules.

Calculation: Inventory and reconcile configured artifacts against required, owned, tested, obsolete, and exception categories.

Retrieval prompts

Module 2

Alarm philosophy, actionability, classes, and priorities

Why it matters: An alarm is actionable information requiring a defined response; abnormal data that requires no action may belong in a trend, diagnostic, or report instead.

Vocabulary and working scope

Event; alarm; advisory; fault; notification; priority; severity; consequence; urgency; response time; operator action; instruction; source; condition; return-to-normal.

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

Every VAV reports a high-damper alarm during morning warm-up, but operators have no action to take.

Calculation: Calculate alarm rate by class, actionable percentage, standing alarms, and priority distribution against owner targets.

Retrieval prompts

Module 3

Limits, deadbands, delays, persistence, and return-to-normal

Why it matters: Delay and deadband are justified by process dynamics, sensor quality, consequence, and response, not selected merely to reduce alarm count.

Vocabulary and working scope

Threshold; high/low limit; deviation; deadband; hysteresis; on-delay; off-delay; persistence; debounce; enable condition; mode suppression; return-to-normal; latch; reset; 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 discharge-air deviation alarm chatters every minute after fan startup and remains active after the system enters unoccupied mode.

Calculation: Calculate deviation, persistence, delay, hysteresis, process time, and expected return-to-normal window.

Retrieval prompts

Module 4

Routing, escalation, acknowledgement, shelving, suppression, and audit

Why it matters: Acknowledgement does not correct the condition; shelving and suppression are temporary governed states with reason, owner, expiry, and audit.

Vocabulary and working scope

Recipient; role; route; schedule; escalation; acknowledgement; response; shelve; suppress; inhibit; maintenance mode; expiration; reason; approval; audit; orphan alarm.

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 contractor shelves a recurring chiller alarm for a week using a shared account and no expiration note.

Calculation: Reconcile sent, received, acknowledged, acted, returned, shelved, expired, and orphaned events with timestamps.

Retrieval prompts

Module 5

Alarm rationalization, floods, common cause, and KPIs

Why it matters: Alarm reduction preserves required detection and response; hiding symptoms without correcting logic, equipment, ownership, or process is not rationalization.

Vocabulary and working scope

Rationalization; duplicate; consequential alarm; common cause; cascade; flood; chattering; stale; standing; bad actor; root alarm; KPI; benchmark; review cadence.

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 network dropout generates 600 downstream point alarms in four minutes and obscures the single gateway failure.

Calculation: Calculate alarms per hour, flood peaks, chattering frequency, standing duration, top contributors, and reduction without loss of required coverage.

Retrieval prompts

Module 6

Trend questions, point selection, and evidence packages

Why it matters: Trending every point at one interval is not a strategy; select values and states that trace source, decision, command, proof, process, and context.

Vocabulary and working scope

Question; hypothesis; controlled variable; explanatory variable; SP; PV; command; proof; mode; load; weather; occupancy; quality; event marker; baseline; comparison group.

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 question is why zone temperature rises each afternoon, but the existing trend contains only zone temperature.

Calculation: Map each hypothesis to required points and calculate coverage, data age, and expected event duration.

Retrieval prompts

Module 7

Sampling, COV, time synchronization, retention, and rollups

Why it matters: Sampling must be fast enough for the process and all compared clocks must share a known time basis; rollups cannot recreate detail that was never captured.

Vocabulary and working scope

Fixed interval; COV; deadband; sample; event; aliasing; Nyquist awareness; timestamp; clock; offset; time zone; daylight saving; retention; aggregation; min/max/average; gap; interpolation.

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 ten-second fan-proof dropout occurs daily, but proof is stored on a fifteen-minute interval and controllers differ by six minutes.

Calculation: Compare event duration, sample rate, COV behavior, storage estimate, clock offset, completeness, and rollup error.

Retrieval prompts

Module 8

Trend analysis, visualization, and diagnostic interpretation

Why it matters: Correlation and sequence coincidence generate hypotheses; root cause requires a mechanism and a test that distinguishes alternatives.

Vocabulary and working scope

Overlay; synchronization; normalization; scatter; slope; lag; correlation; causation; baseline; changed case; outlier; saturation; hunting; drift; occupancy; weather normalization.

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

Valve command tracks temperature error, but discharge temperature does not change until twenty minutes later and outdoor temperature is falling.

Calculation: Calculate error, lag, rate of change, percent time saturated, cycle period, before/after difference, and uncertainty.

Retrieval prompts

Module 9

Schedules, calendars, holidays, optimum start, and override expiry

Why it matters: Every temporary schedule or occupancy override has a reason, owner, start, expiry, affected systems, audit, and verified release.

Vocabulary and working scope

Weekly schedule; exception; holiday; calendar; occupancy; warm-up; cooldown; optimum start/stop; after-hours request; temporary override; expiration; priority; time zone; daylight saving.

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 recurring holiday exception leaves the building occupied for a weekend after daylight-saving time changes.

Calculation: Calculate occupied hours, exception overlap, optimum-start lead, after-hours duration/cost proxy, and expiration/release status.

Retrieval prompts

Module 10

Integrated operations layer, testing, handoff, and restoration

Why it matters: Configuration is accepted only when operators can interpret and act, audit is preserved, critical faults remain visible, and temporary states return to normal.

Vocabulary and working scope

Cross-link; alarm-to-trend; schedule context; response instruction; operator role; simulation; fault injection; routing test; time test; retention test; backup; release; rollback; training; review cadence.

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 staged fault alarms correctly but routes to the wrong role, the trend starts after the event, and the maintenance suppression remains active.

Calculation: Reconcile planned/actual tests, response times, routing, trend coverage, schedule state, suppression expiry, and restoration.

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.