BAS-409 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.
Configuration items, repositories, artifact inventory, and baselines
Why it matters: Version control must include more than editable code; generated, binary, platform, certificate, database, and field-installed artifacts need traceable configuration management.
Vocabulary and working scope
Configuration item; source; generated artifact; binary; export; station; controller program; graphic; point database; gateway map; certificate; license; schema; document; repository; baseline; checksum; owner.
Source-to-result trace
- Locate the controlling requirement and establish authority.
- Identify the physical and digital boundaries.
- Preserve as-found state and timestamps.
- Trace the initiating condition through logic, interfaces, equipment, and process response.
- Compare expected and actual evidence.
- Calculate with units and stated tolerance.
- Record action, result, restoration, uncertainty, and owner.
Worked thinking prompt
A repository contains logic source but the deployed controller binary, station database, gateway map, and certificate are missing.
Calculation: Reconcile source, generated, deployed, backed-up, hashed, owned, and unknown configuration items.
Retrieval prompts
- What would normal look like in this mode?
- Which two independent observations would strengthen the conclusion?
- What result would disprove the leading hypothesis?
- Which action requires authorization or a qualified person?
- What must be restored and documented?
Naming, versions, commits, records, and traceability
Why it matters: A timestamped filename is not sufficient traceability when it does not connect reason, author, source, review, test, and deployed result.
Vocabulary and working scope
Version; revision; commit; tag; release; build; date; author; issue; work order; message; scope; atomic change; provenance; checksum; signed approval; immutable record.
Source-to-result trace
- Locate the controlling requirement and establish authority.
- Identify the physical and digital boundaries.
- Preserve as-found state and timestamps.
- Trace the initiating condition through logic, interfaces, equipment, and process response.
- Compare expected and actual evidence.
- Calculate with units and stated tolerance.
- Record action, result, restoration, uncertainty, and owner.
Worked thinking prompt
Five files named FINAL are stored on a laptop and the running station cannot be matched to any of them.
Calculation: Verify version uniqueness, checksum matches, issue-to-commit-to-release coverage, and chronological consistency.
Retrieval prompts
- What would normal look like in this mode?
- Which two independent observations would strengthen the conclusion?
- What result would disprove the leading hypothesis?
- Which action requires authorization or a qualified person?
- What must be restored and documented?
Diff, peer review, approval, and risk classification
Why it matters: A small line diff can have large physical consequence, while a large generated diff may contain little semantic change; review follows behavior and risk.
Vocabulary and working scope
Text diff; structured diff; binary compare; export; semantic change; generated noise; reviewer; approver; separation of duties; risk class; consequence; blast radius; reversibility; evidence.
Source-to-result trace
- Locate the controlling requirement and establish authority.
- Identify the physical and digital boundaries.
- Preserve as-found state and timestamps.
- Trace the initiating condition through logic, interfaces, equipment, and process response.
- Compare expected and actual evidence.
- Calculate with units and stated tolerance.
- Record action, result, restoration, uncertainty, and owner.
Worked thinking prompt
A one-line default changes every VAV minimum airflow after regeneration of 300 controller files.
Calculation: Count affected assets/points/modes, estimate blast radius and rollback effort, and reconcile reviewer findings and approvals.
Retrieval prompts
- What would normal look like in this mode?
- Which two independent observations would strengthen the conclusion?
- What result would disprove the leading hypothesis?
- Which action requires authorization or a qualified person?
- What must be restored and documented?
Branches, releases, tags, builds, packages, and integrity
Why it matters: A release is a reproducible package with identity and evidence, not whichever file is currently open in an engineering tool.
Vocabulary and working scope
Branch; mainline; feature; merge; conflict; tag; release candidate; build; compiler/tool version; dependency; package; manifest; checksum; signature; reproducible build; promotion.
Source-to-result trace
- Locate the controlling requirement and establish authority.
- Identify the physical and digital boundaries.
- Preserve as-found state and timestamps.
- Trace the initiating condition through logic, interfaces, equipment, and process response.
- Compare expected and actual evidence.
- Calculate with units and stated tolerance.
- Record action, result, restoration, uncertainty, and owner.
Worked thinking prompt
Two programmers export controller binaries with different tool versions and produce nonmatching files from the same source.
Calculation: Compare dependency/tool versions, build checksums, manifest coverage, conflict resolution, and promotion status.
Retrieval prompts
- What would normal look like in this mode?
- Which two independent observations would strengthen the conclusion?
- What result would disprove the leading hypothesis?
- Which action requires authorization or a qualified person?
- What must be restored and documented?
Change plan, backup, window, prechecks, abort, and rollback
Why it matters: Rollback is engineered before deployment; a backup with unknown contents or restore time is not an adequate recovery plan.
Vocabulary and working scope
Change request; reason; scope; affected users; outage; communication; backup; restore test; precheck; dependency; test; maintenance window; abort threshold; rollback trigger; owner; witness.
Source-to-result trace
- Locate the controlling requirement and establish authority.
- Identify the physical and digital boundaries.
- Preserve as-found state and timestamps.
- Trace the initiating condition through logic, interfaces, equipment, and process response.
- Compare expected and actual evidence.
- Calculate with units and stated tolerance.
- Record action, result, restoration, uncertainty, and owner.
Worked thinking prompt
A critical supervisor update is scheduled for a two-hour window, but the last restore test took three hours.
Calculation: Calculate window, stabilization, verification, and rollback timing; reconcile RPO/RTO and dependency readiness.
Retrieval prompts
- What would normal look like in this mode?
- Which two independent observations would strengthen the conclusion?
- What result would disprove the leading hypothesis?
- Which action requires authorization or a qualified person?
- What must be restored and documented?
Controlled deployment, one-change evidence, and verification
Why it matters: A successful download is not successful change; deployed identity, behavior, collateral functions, monitoring, and restoration must be proven.
Vocabulary and working scope
Release; target identity; pre-state; implementation log; one controlled change; timestamp; witness; expected result; postcheck; regression; monitor; effective version; temporary state; restoration.
Source-to-result trace
- Locate the controlling requirement and establish authority.
- Identify the physical and digital boundaries.
- Preserve as-found state and timestamps.
- Trace the initiating condition through logic, interfaces, equipment, and process response.
- Compare expected and actual evidence.
- Calculate with units and stated tolerance.
- Record action, result, restoration, uncertainty, and owner.
Worked thinking prompt
The release loads without error but one controller remains on the old version and an operator override masks a failed output.
Calculation: Reconcile planned and actual targets/versions, tests, response times, overrides, alarms, accounts, and temporary conditions.
Retrieval prompts
- What would normal look like in this mode?
- Which two independent observations would strengthen the conclusion?
- What result would disprove the leading hypothesis?
- Which action requires authorization or a qualified person?
- What must be restored and documented?
Emergency changes and retrospective control
Why it matters: Urgency can compress workflow but does not erase identity, authority, backup, scope, monitoring, restoration, or retrospective accountability.
Vocabulary and working scope
Incident; emergency authority; containment; temporary change; minimum record; risk acceptance; communication; backup; rollback; monitoring; retrospective review; permanent correction; expiration.
Source-to-result trace
- Locate the controlling requirement and establish authority.
- Identify the physical and digital boundaries.
- Preserve as-found state and timestamps.
- Trace the initiating condition through logic, interfaces, equipment, and process response.
- Compare expected and actual evidence.
- Calculate with units and stated tolerance.
- Record action, result, restoration, uncertainty, and owner.
Worked thinking prompt
During a freeze event, an operator asks for an immediate temporary setpoint and alarm-delay change.
Calculation: Track elapsed decision/action/recovery times and reconcile temporary changes, expirations, approvals, and retrospective actions.
Retrieval prompts
- What would normal look like in this mode?
- Which two independent observations would strengthen the conclusion?
- What result would disprove the leading hypothesis?
- Which action requires authorization or a qualified person?
- What must be restored and documented?
Drift detection, unauthorized change, and configuration audit
Why it matters: Drift is not automatically malicious or harmless; preserve evidence and determine source, authority, consequence, and recovery before overwriting it.
Vocabulary and working scope
Desired state; actual state; drift; compare; checksum; runtime override; local change; unauthorized edit; audit log; exception; reconciliation; evidence; containment; incident route.
Source-to-result trace
- Locate the controlling requirement and establish authority.
- Identify the physical and digital boundaries.
- Preserve as-found state and timestamps.
- Trace the initiating condition through logic, interfaces, equipment, and process response.
- Compare expected and actual evidence.
- Calculate with units and stated tolerance.
- Record action, result, restoration, uncertainty, and owner.
Worked thinking prompt
A nightly compare finds changed VAV setpoints, a new administrator, and one controller checksum mismatch.
Calculation: Calculate drift rate, affected assets, age, authorization coverage, and baseline reconciliation status.
Retrieval prompts
- What would normal look like in this mode?
- Which two independent observations would strengthen the conclusion?
- What result would disprove the leading hypothesis?
- Which action requires authorization or a qualified person?
- What must be restored and documented?
Dependencies, vendors, libraries, schemas, certificates, and lifecycle
Why it matters: Hidden dependencies become outages during restore or upgrade; every required component needs version, source, support, license, integrity, owner, and replacement path.
Vocabulary and working scope
Dependency; library; module; driver; vendor tool; firmware; schema; API; certificate; license; support status; vulnerability; compatibility; expiration; end of life; migration; owner.
Source-to-result trace
- Locate the controlling requirement and establish authority.
- Identify the physical and digital boundaries.
- Preserve as-found state and timestamps.
- Trace the initiating condition through logic, interfaces, equipment, and process response.
- Compare expected and actual evidence.
- Calculate with units and stated tolerance.
- Record action, result, restoration, uncertainty, and owner.
Worked thinking prompt
A station depends on an unsupported driver, an expiring certificate, and a vendor library stored only on one laptop.
Calculation: Calculate days to expiration/EOL, dependency coverage, compatibility results, and recovery-source availability.
Retrieval prompts
- What would normal look like in this mode?
- Which two independent observations would strengthen the conclusion?
- What result would disprove the leading hypothesis?
- Which action requires authorization or a qualified person?
- What must be restored and documented?
Recovery, closeout, lessons, and series capstone defense
Why it matters: Recovery is complete only when approved functions and as-left configuration are proven, stakeholders are informed, evidence is preserved, and open risks have owners.
Vocabulary and working scope
Rollback; restore; last known good; fallback operation; incident/change linkage; postchange review; closeout; as-left; lessons learned; corrective action; owner; due date; evidence defense; archival.
Source-to-result trace
- Locate the controlling requirement and establish authority.
- Identify the physical and digital boundaries.
- Preserve as-found state and timestamps.
- Trace the initiating condition through logic, interfaces, equipment, and process response.
- Compare expected and actual evidence.
- Calculate with units and stated tolerance.
- Record action, result, restoration, uncertainty, and owner.
Worked thinking prompt
A rollback restores comfort but leaves an old certificate, stale gateway map, and undocumented temporary admin account.
Calculation: Reconcile all configuration items, versions, functions, tests, temporary states, issues, owners, and archive records; critical gaps cannot be averaged away.
Retrieval prompts
- What would normal look like in this mode?
- Which two independent observations would strengthen the conclusion?
- What result would disprove the leading hypothesis?
- Which action requires authorization or a qualified person?
- What must be restored and documented?
Required and deeper reading
- ASHRAE Guideline 13-2024
Modern BAS specification, architecture, I/O, communication, configuration, testing, documentation, cybersecurity, and legacy-system context. - NIST SP 800-82 Rev. 3
Current OT security guidance for BAS access, segmentation, remote work, monitoring, and recovery boundaries. - NIST SP 1339 OT Backup Quick Start Guide
Current OT backup, restore testing, recovery exercise, and change-management guidance. - IEC 61131-3:2025
Current programming-language concepts for structured text, ladder, function blocks, and sequential function charts; platform implementation still controls. - Honeywell Engineering Manual of Automatic Control for Commercial Buildings, 1997
Foundational control-loop, DDC, controller-programming, application, and BMS architecture source; legacy examples require current project and standards verification.