BOOT-BAC 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.
BACnet purpose, source hierarchy, PICS, BIBBs and product evidence
Why it matters: BACnet defines interoperable data and services, but project requirements and implemented capabilities determine what two devices can actually do together.
Vocabulary and working scope
Building use case; Standard 135; addenda/interpretations; project specification; PICS; BIBBs; BTL listing; optional services; product/firmware limits; evidence claims.
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 controller is BACnet listed, yet the required schedule write and event enrollment workflow fails between vendors.
Calculation: Build a requirement-to-capability coverage matrix and calculate confirmed, unsupported, ambiguous, and untested coverage percentages.
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?
Objects, properties, units, status, reliability and point truth
Why it matters: A plausible Present_Value is not point truth when identity, units, reliability, override, timestamp, or physical corroboration is wrong.
Vocabulary and working scope
Object/device identity; Present_Value; units; Status_Flags; Reliability; Out_Of_Service; timestamps; priority; physical condition; controller logic; graphic/trend consumers.
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 discharge-air value looks normal on a graphic while Reliability is fault, units are wrong, and the sensor is disconnected.
Calculation: Convert units, calculate scaling/error and age, and compare independent evidence to acceptance tolerance.
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?
Services, priority arrays, command, proof and safe relinquish
Why it matters: A successful write response proves protocol acceptance, not effective priority, physical action, safe process response, or restoration.
Vocabulary and working scope
ReadProperty; WriteProperty; ReadPropertyMultiple; priority array; Relinquish_Default; command value; accepted write; equipment proof; timeout; release; temporary-state inventory.
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
An AO accepts a write but does not move because a higher priority remains active; the operator later sees an unexplained override.
Calculation: Calculate effective priority, command/proof error and timeout, then reconcile every introduced priority or Out_Of_Service state to zero.
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?
BACnet/IP identity, routing, BBMD/FDR and duplicate conditions
Why it matters: Identity exists at several layers; a device may be reachable by IP while BACnet discovery or routed services fail.
Vocabulary and working scope
IP/subnet/gateway; UDP port; BACnet network number; device instance; router; BBMD; BDT; foreign device; broadcast domain; NAT constraints; duplicate IP/network/device; path 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
Local Who-Is works, remote discovery fails, and two routers advertise the same BACnet network.
Calculation: Calculate subnet membership, broadcast boundaries, FDR lifetime margin, hop/path inventory, and duplicate coverage.
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?
BACnet/SC hubs, nodes, certificates, trust and migration
Why it matters: BACnet/SC protects transport relationships; certificate lifecycle, identity, authorization, product support, operations, and recovery still require governance.
Vocabulary and working scope
SC node/hub; WebSocket/TLS awareness; certificate identity; trust store; expiry; DNS/time; primary/failover; owner PKI; migration coexistence; revocation; recovery.
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 node stops reconnecting after certificate renewal while time is wrong and an old trust anchor remains on one hub.
Calculation: Calculate certificate-life and renewal windows, time error, node/hub capacity from supplied limits, and recovery coverage.
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?
MS/TP RS-485 physical layer and segment commissioning
Why it matters: RS-485 electrical integrity and MS/TP link configuration are separate but interacting evidence layers; neither is proven by seeing one device online.
Vocabulary and working scope
Daisy-chain topology; polarity; reference/common; shield/drain; termination; bias product behavior; cable/impedance; stubs; loading; MAC; baud; Max_Master; environment; grounding/noise.
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 trunk works with two devices and fails after a controller is added through a long star branch with reversed polarity.
Calculation: Calculate segment loading and stub/length ratios from supplied limits, expected end-to-end termination resistance, token-cycle effects, and error rate.
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?
Token timing, traffic load, APDU behavior and performance
Why it matters: Latency must be traced through the whole service path; changing baud or timeouts blindly can hide rather than fix the cause.
Vocabulary and working scope
Token rotation; Max_Info_Frames; retries; timeouts; APDU segmentation; request/response; COV versus polling; controller resource limits; trend/alarm load; latency 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
Zone values update every 90 seconds after a front-end polling change, but CRC errors remain low.
Calculation: Calculate token-cycle and update-time estimates, requests per minute, retry percentage, latency distribution, and before/after load.
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?
Discovery tools, captures, filters and sanitized evidence
Why it matters: A large capture is not automatically useful evidence; placement, time quality, question, filter, scope, and sanitization determine value.
Vocabulary and working scope
Tool authority; capture point; interface; display filters; Who-Is/I-Am; Read/Write; errors/rejects/aborts; invoke IDs; NPDU/APDU; timestamps; clock; privacy; export sanitization.
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 capture shows repeated retries, but it was taken on the wrong VLAN and the timestamps do not match controller logs.
Calculation: Calculate capture duration/size, request-response latency, retry/error rate, and clock offset before correlating sources.
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?
COV, schedules, events, notifications, trends and lifecycle state
Why it matters: Configuration existence does not prove delivery, acknowledgement, persistence, restart behavior, time quality, or operator usefulness.
Vocabulary and working scope
COV subscription; increment; lifetime; confirmed/unconfirmed notification; event state; limits/deadband/delay; notification class; schedule/calendar; trend interval/COV; buffer; timestamps; restart.
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
An alarm appears locally but not at the workstation after restart; trend samples are duplicated around a time correction.
Calculation: Calculate COV/reporting volume, alarm delay, schedule precedence, sample storage/retention, missing/duplicate rates, and time skew.
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?
Multi-vendor gateways, optional features and changed-case interoperability; Commissioning, issue/retest, restoration and professional defense
Why it matters: Interoperability is a tested use-case claim, not a brand-wide claim; gateways introduce translation, lifecycle, performance, and ownership boundaries. A system is not commissioned when only discovery and point reads pass; functional outcomes, failures, restart, recovery, documentation, and restoration are required.
Vocabulary and working scope
Native BACnet; gateway; protocol map; object mapping; units/state translation; writable behavior; priorities; timing; quality; alarms/trends; restart; licensing; ownership. Commissioning plan; normal/boundary/negative/failure/restart tests; witness; acceptance source; issue severity; correction; retest/regression; temporary states; as-built; handoff; oral defense.
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 Modbus gateway maps an enumerated state as analog, reverses byte order on energy, and drops quality on communications loss. Changed-capstone condition: All devices appear online, yet one priority remains, two notifications are unverified, and the final router configuration was not backed up.
Calculation: Calculate map coverage, scaling/byte-order results, update latency, error handling coverage, and untested combinations. Reconcile planned/executed/passed/failed/retested tests and calculate critical coverage, issue closure, temporary-state closure, and residual risk.
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 Standard 135 official scope and current-edition route
Confirm the current standard, addenda, interpretations, adopted/project requirements, and product implementation before making a compliance claim. - ASHRAE Guideline 13-2024
BAS specification, installation, integration, testing, documentation, cybersecurity, and lifecycle context. - BACnet International BACnet/SC resource
Secure-connect architecture, certificate/trust concepts, migration, and interoperability routes. - NIST SP 800-82 Rev. 3
OT governance, architecture, access, monitoring, incident response, backup, recovery, and compensating-control guidance.