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

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

Service mission and work order

Why it matters: The work order defines the assigned problem and authority; it does not prove the cause or permit every technically possible action.

Vocabulary and working scope

Customer objective; complaint; affected area; urgency; service-level expectations; work-order scope; exclusions; contacts; success condition.

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 customer reports that the west wing is hot and asks the technician to force cooling immediately.

Calculation: Reconcile requested, authorized, completed, deferred, and open work counts; the categories must balance.

Retrieval prompts

Module 2

Authorization, access, privacy, and OT security

Why it matters: Technical ability is not authorization; access must be named, least-privilege, time-bounded, logged, and closed.

Vocabulary and working scope

Site access; identity; least privilege; remote target; approved ports/actions; credentials; occupant and customer information; logging; reservation; 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 shared administrator credential is offered for a quick remote check of a production supervisor.

Calculation: Compare session start/end, reservation window, authorized target count, and access-closure evidence.

Retrieval prompts

Module 3

Complaint interview and operating context

Why it matters: Ask for time, place, operating mode, impact, and recent changes before asking the customer to agree with a technical theory.

Vocabulary and working scope

Who; what; where; when; frequency; duration; impact; occupancy; weather; process; recent work; operator actions; exceptions; desired outcome.

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

Three occupants say the room is always cold, but the complaint occurs only during Monday morning warm-up.

Calculation: Build a timestamped event line and compare complaint windows to schedule, occupancy, weather, and system-mode windows.

Retrieval prompts

Module 4

Source control and evidence preservation

Why it matters: A screenshot without point identity, timestamp, units, mode, source, and revision is an illustration, not sufficient diagnostic evidence.

Vocabulary and working scope

Current drawings; sequences; point lists; submittals; service history; trend exports; photos; revisions; backups; audit logs; customer-data redaction.

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 graphic looks wrong after a recent controls upgrade, but the technician has an old point list and no change record.

Calculation: Reconcile document revision dates and trend time bases; calculate clock offset before comparing events.

Retrieval prompts

Module 5

Arrival, hazards, and as-found state

Why it matters: The as-found condition must be recorded before a test, reset, override, restart, cover removal, or setpoint change can alter it.

Vocabulary and working scope

Job hazard analysis; energy/media state; equipment condition; alarms; overrides; HOA/local positions; open panels; occupant/process impact; emergency route.

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 technician arrives to find a panel door open, a VFD in HAND, and an unrecorded alarm inhibit.

Calculation: Count and reconcile every temporary/manual/open state before and after work; zero unaccounted states is required.

Retrieval prompts

Module 6

Work plan and customer updates

Why it matters: A professional update states what is known, unknown, being tested, affected, and expected next without guaranteeing an unproven outcome.

Vocabulary and working scope

Hypotheses; evidence plan; impacts; test sequence; communication checkpoints; downtime; expected versus possible result; stop and restore criteria.

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 initial one-hour visit becomes a multi-trade investigation after the BAS evidence points toward a mechanical restriction.

Calculation: Compare planned and actual elapsed time, interruption duration, and next-update commitment with stated assumptions.

Retrieval prompts

Module 7

Uncertainty, escalation, and refusing unsafe work

Why it matters: Escalation is a professional technical action when the next test belongs to another qualified role or exceeds assigned authority.

Vocabulary and working scope

Evidence strength; confidence; stop-work; qualified roles; electrical; refrigerant; combustion; TAB; life safety; IT; design; owner decisions.

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 manager asks the BAS technician to bypass a freezestat so the air handler can run for a demonstration.

Calculation: Use a risk matrix with severity, likelihood, detectability, and reversibility; any life-safety boundary overrides convenience scoring.

Retrieval prompts

Module 8

Execution, change control, and restoration

Why it matters: Closing the software window is not restoration; the physical, controller, network, alarm, schedule, and access states must be proven.

Vocabulary and working scope

One-change control; backups; before/after; temporary settings; override register; witness; abort; rollback; retest; affected modes; normal release.

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 test override fixes the complaint, but the technician cannot identify the original priority source.

Calculation: Reconcile all commands, forces, jumpers, test modes, open enclosures, temporary accounts, and alarms to an explicit as-left state.

Retrieval prompts

Module 9

Service record and customer handoff

Why it matters: The record distinguishes evidence from inference and states both the confirmed cause and what remains unknown.

Vocabulary and working scope

Factual narrative; measurements; sources; cause; correction; unresolved items; affected systems; retest; as-left state; owner; due date; customer explanation.

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 immediate comfort issue is corrected, but a recurring network dropout remains unproven and requires follow-up.

Calculation: Check that planned actions equal completed plus deferred plus cancelled, and that every open item has one owner and due date.

Retrieval prompts

Module 10

Integrity, closeout, and series handoff

Why it matters: A service visit is not complete because the customer is temporarily comfortable; it closes only with truthful evidence, restoration, ownership, and communication.

Vocabulary and working scope

Truthful time/material; parts and settings; signature authority; no hidden defects; no unsupported savings/safety claim; lessons learned; next-course evidence packet.

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 technician is pressured to report a sensor replacement as complete before the failed reference check is repeated.

Calculation: Reconcile labor, material, test, retest, and open-item records; critical evidence cannot be averaged away by a high overall score.

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.