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

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

Program purpose, risk, and success measures

Why it matters: Fault count and checklist completion are activity metrics; success requires verified condition, closure, recurrence, and outcome evidence.

Vocabulary and working scope

Safety; reliability; comfort; IAQ; energy; asset life; evidence quality; preventive/predictive/condition/corrective maintenance; owner risk; KPIs.

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 team closes many analytics tickets while comfort complaints and repeat faults rise.

Calculation: Calculate verified closure, recurrence, critical overdue, and false-positive rates with severity retained.

Retrieval prompts

Module 2

Asset and maintenance requirement register

Why it matters: “Check annually” is not production-ready until the asset, source, method, acceptance condition, role, evidence, and exception path are defined.

Vocabulary and working scope

Asset hierarchy; identity; location; criticality; manufacturer; project; code/standard; warranty; task; interval/trigger; role; method; acceptance; evidence; 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

A generic PM list assigns the same interval to critical AHUs and noncritical storage-room units.

Calculation: Calculate risk rank and interval status only within source/warranty limits; compare due, completed, deferred, and overdue tasks.

Retrieval prompts

Module 3

Integrated BAS and HVAC preventive maintenance

Why it matters: A trend pattern can prioritize field work but does not certify physical cause, and a successful backup file is not proven recovery until integrity and an approved restore process are verified.

Vocabulary and working scope

Sensor drift; actuator/linkage; dampers/valves; panel power; controller storage/battery; network and time sync; alarms/trends; overrides; backups/restore; licenses/accounts; filter, coil, fan, belt, bearing, motor, VFD, heat-transfer, cycling, hunting, runtime, and qualified field-referral awareness.

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

Fan power rises and airflow falls while the supervisor backup is unverified; sensor drift, filter loading, and recovery risk all require separate evidence and ownership.

Calculation: Calculate data and backup age, override duration, starts, duty cycle, ΔT/load indicators, runtime/peer deviation, and maintenance coverage by asset criticality.

Retrieval prompts

Module 4

Data-quality gate

Why it matters: Analytics applied to unfit data produces confident-looking noise; fitness is specific to the question and time scale.

Vocabulary and working scope

Point identity; units; range; source; calibration; location; timestamp; sampling; gaps; stale/default; overrides; mode; occupancy; weather; load; change history; 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

An economizer rule uses a stale mixed-air sensor and unsynchronized outdoor-air data.

Calculation: Calculate completeness, data age, clock offset, sampling adequacy, and valid-mode coverage before analysis.

Retrieval prompts

Module 5

Transparent FDD rule anatomy

Why it matters: A useful rule says when it applies, what data it trusts, how long the condition persists, what excludes it, and how it is field-verified.

Vocabulary and working scope

Target fault; applicability; inputs; quality gates; expected relation; threshold; deadband; persistence; reset; exclusions; confidence; output; owner; verification; version.

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 simultaneous-heating/cooling rule fires during legitimate dehumidification reheat.

Calculation: Calculate residual/threshold, persistence, deadband, confidence inputs, and reset timing from the declared rule.

Retrieval prompts

Module 6

Baselines, normalization, and pattern methods

Why it matters: A baseline is only valid for the population, modes, weather/load range, and system configuration from which it was built.

Vocabulary and working scope

Schedule; threshold; relationship; residual; peer; baseline; weather; load; occupancy; mode; season; simple statistics; interpretability; drift; change point.

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

Post-retrofit energy is compared to a mild prior month without weather or occupancy normalization.

Calculation: Calculate supplied baseline, residual, percent deviation, degree-day/load normalization, and confidence limits using the stated method.

Retrieval prompts

Module 7

False positives and missed faults

Why it matters: A false positive is evidence about data, rule, context, or system change; suppressing it without diagnosis can create a missed fault.

Vocabulary and working scope

Sensor bias; units; mode; unstable state; maintenance activity; sequence revision; bad threshold; persistence; normalization; data gap; interacting faults; label truth set.

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 rule floods after a scheduled control-sequence update changed the expected SAT target.

Calculation: Calculate precision, recall awareness, false-positive rate, missed-fault count, and revised threshold/persistence on labeled cases.

Retrieval prompts

Module 8

Triage, work orders, and responsible routing

Why it matters: A low-confidence critical-safety indication receives controlled escalation; a high-confidence low-impact finding may wait.

Vocabulary and working scope

Safety/critical first; comfort; IAQ; production; energy; asset risk; confidence; recurrence; effort; bundling; SLA; evidence packet; role; escalation.

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 portfolio has one possible freeze-protection failure and twenty minor efficiency findings.

Calculation: Use stated risk, impact, confidence, recurrence, and effort weights while allowing critical-risk override of the score.

Retrieval prompts

Module 9

Verification, value, and closure

Why it matters: A cleared analytic flag is not verified repair; closure needs field/as-left evidence and a suitable recurrence window.

Vocabulary and working scope

As-found field evidence; correction; as-left; recurrence window; baseline; avoided runtime; energy estimate; comfort/maintenance impact; uncertainty; measured versus estimated; 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 valve fault disappears after a rule reset, but no field inspection or affected-mode retest occurred.

Calculation: Calculate verified runtime/energy change from stated baseline and assumptions and report uncertainty and non-energy outcomes.

Retrieval prompts

Module 10

Portfolio governance and continuous improvement

Why it matters: Every live analytic rule and suppression needs an owner, version, reason, effective date, review/expiry, and rollback.

Vocabulary and working scope

Rule version; approval; rollback; access; retention; privacy; suppression expiry; exception owner; KPI; coverage; precision; closure; recurrence; seasonal review; owner feedback.

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 critical rule has been suppressed indefinitely because it generated too many tickets.

Calculation: Reconcile active rules, versions, suppressions, expired exceptions, verified findings, recurrence, and owner actions.

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.