BAS-105 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.
Project lifecycle, roles, sources and document control
Why it matters: The newest-looking file is not necessarily approved for construction; title block, status, revision, distribution, contract hierarchy, and project authority govern.
Vocabulary and working scope
Owner/operator; engineer; controls contractor; electrical/mechanical trades; AHJ; OPR/BOD awareness; spec; drawings; submittal; sequence; RFI; bulletin; ASI/change; redline/as-built; revision/status.
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 field set lacks the latest bulletin while a shop drawing contains an unapproved change.
Calculation: Reconcile revisions/dates/status, calculate document coverage and superseded-file risk, and list unresolved authority.
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?
Drawing conventions, sheets, views, symbols, notes and scale
Why it matters: Symbols and scale are aids; written dimensions, details, notes, revisions, and field verification control within project rules.
Vocabulary and working scope
Cover/index; disciplines; sheet/detail references; plans/elevations/sections/details; legends; abbreviations; north/grid/elevation; dimensions; graphic scale; not-to-scale; general/keyed notes.
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 sensor appears centered graphically, but a keyed note and dimension locate it elsewhere.
Calculation: Use supplied architectural/engineering scales, convert units, calculate route/area/quantity, and perform reasonableness checks.
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?
Mechanical plans, schedules, details and system flow
Why it matters: Mechanical drawings explain physical systems but may not fully define control sequence, point semantics, or installation responsibility.
Vocabulary and working scope
AHU/RTU/VAV/VRF/plant plans; equipment tags; duct/piping; arrows; valves/dampers; sections/details; equipment schedules; capacities; connection points; zones; control intent limits.
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 VAV schedule lists reheat but the plan tag and detail disagree on coil type.
Calculation: Reconcile equipment counts/tags/capacities, calculate simple flow/size/quantity from supplied data, and quantify unresolved discrepancies.
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?
Control schematics, sequences, points and state traces
Why it matters: A point on a list does not prove its purpose, state semantics, priority, timing, or failure behavior; sequence and equipment evidence must align.
Vocabulary and working scope
Control diagram; sequence of operation; modes; enable/permissive/interlock/safety; setpoints; reset; alarms; point list; AI/AO/BI/BO; enumerated; command/proof; timing; fallback; 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
The sequence requires fan proof before heating, but the point list includes only fan command.
Calculation: Build truth/state tables, calculate timing/setpoint/reset examples, and measure requirement-to-point/test 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?
Electrical/control diagrams, terminal plans and responsibility boundaries
Why it matters: A diagram shows functional intent; exact ratings, listings, installation, adopted code, and field condition require separate verification.
Vocabulary and working scope
Single-line awareness; ladder/control schematic; panel/wiring diagram; power source; protection; transformer; relay/starter/VFD control; terminal; wire/cable tag; grounding/reference; trade scope; interconnection.
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 controls drawing shows a dry contact, but the equipment diagram supplies voltage at the terminal.
Calculation: Calculate control load/VA, conductor/terminal counts, voltage-drop example, and interface/responsibility 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?
Network risers, topology, addresses and data paths
Why it matters: Lines on a riser are not proof of physical route, address assignment, required flow, device capability, or as-built state.
Vocabulary and working scope
Ethernet/IP; BACnet/IP; RS-485/MS/TP; router/BBMD awareness; controller/device; network/device/MAC/IP identity; VLAN/subnet handoff; topology; termination/reference/shield; ports; owner IT boundary.
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 controllers share a device instance and the riser omits an intermediate router.
Calculation: Calculate address/subnet examples, device/segment counts, spare/capacity from supplied limits, and identity 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?
Submittals, product data, schedules and approved-equivalent review
Why it matters: Similar description, appearance, or capability does not establish an approved equivalent; all critical interfaces and authority must reconcile.
Vocabulary and working scope
Model/part; options; voltage; range; signal; rating; listing; environment; dimensions; accessories; firmware; sequence compatibility; exceptions; deviations; approved status; substitution/RFI.
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 replacement sensor matches range and output but lacks required enclosure rating and averaging length.
Calculation: Create a requirement/product coverage matrix and calculate confirmed/failed/unknown fields and material/count impacts.
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?
Point, cable, panel, device and test schedule reconciliation
Why it matters: Schedule totals are useful only when duplicates, spares, alternates, deleted points, and cross-references are controlled.
Vocabulary and working scope
Point schedule; cable schedule; panel layout; device schedule; controller capacity; terminal plan; label; test sheet; alarm/trend/schedule matrix; spare; quantities; cross-reference.
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 point list has 42 points, the controller schedule has 40, and two graphic points have no field source.
Calculation: Calculate counts by type, controller capacity/spare, cable/terminal quantities, coverage, duplicates, and exceptions.
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?
Field verification, photos, RFIs and decision records
Why it matters: A field conversation or photo without identity, context, revision, and decision record is not controlled authorization.
Vocabulary and working scope
Planned versus as-found; datum; location; access; obstruction; existing condition; photo context/detail; measurement; markup; issue statement; requirement; proposed options; impact; question; response; distribution.
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
Ductwork blocks the specified sensor location and the installer wants to move it without engineering review.
Calculation: Calculate dimensional conflict, route/quantity impact, response age, issue severity, and decision/record completeness.
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?
Redlines, as-builts, turnover and change reconciliation; Integrated document trace, conflict diagnosis and defense
Why it matters: A redline records what was installed; it does not itself approve a deviation or replace formal change control. Professional document literacy includes knowing when the evidence is insufficient and stopping before a silent assumption becomes installed work.
Vocabulary and working scope
Redline convention; revision cloud/delta awareness; actual route/location/terminal/address/model; deletion/addition; RFI/change reference; legibility; dates/initials; as-built incorporation; version; turnover index; open items. Changed set; hidden revision; normal model; cross-document contradiction; field evidence; source hierarchy; RFI; calculation; responsible owner; temporary decision; final record; 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
Ceilings close tomorrow while cable routes, terminal changes, and one device relocation remain unmarked. Changed case: A drawing, sequence, submittal, and field installation each describe a different fan-proof method.
Calculation: Calculate planned/installed/tested/documented counts, redline completeness, open-item age, and turnover coverage. Score source authority/coverage, reconcile quantities and timing, rank contradictions, and calculate closure/readiness before release.
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
BAS specification, architecture, installation, communications, testing, documentation, cybersecurity, and legacy context. - Honeywell Engineering Manual of Automatic Control for Commercial Buildings
Foundational heat, HVAC process, control, devices, electricity, DDC, applications, and documentation; current standards and exact project/product information govern. - ASHRAE standards and guideline title/scope route
Use to locate current applicable standards; confirm edition, adoption, project, owner, and AHJ requirements. - NFPA 70 National Electrical Code official route
Use only the locally adopted edition, amendments, project requirements, listings, and AHJ decisions; course text is not code permission.