Technical Trade SchoolBAS-200 installer-series
BAS-206
Concept reading and source route

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

Source of truth, revisions, status, and responsibility

Why it matters: A neat redline on a superseded drawing is still the wrong record.

Vocabulary and working scope

Issued/approved/as-built; drawing/spec/submittal/RFI/change; document number/revision/date; superseded; field copy; owner; distribution; hold 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

The field folder contains three drawing revisions and an email sketch with no approval status.

Calculation: Reconcile document inventory, current/superseded status, recipients, and unresolved authority.

Retrieval prompts

Module 2

Naming grammar, labels, and accessible identity

Why it matters: Labels connect physical and digital assets; names must be stable, human-usable, and governed.

Vocabulary and working scope

Site/area/equipment/device/panel/cable/terminal/network/point; grammar; abbreviation; uniqueness; durable material; placement; readability; both-end identity; QR/barcode optional; non-color cues.

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

Two VAVs share a label and a cable tag matches neither drawing nor controller object.

Calculation: Calculate duplicate/missing/mismatched label rates and reconcile every required identity.

Retrieval prompts

Module 3

Jacket-color standards and color-independent verification

Why it matters: Color is an overlay, not proof; every color-coded item requires independent text and source verification.

Vocabulary and working scope

Owner legend; cable function; color vision/accessibility; printed marking; text tag; drawing; terminals; approved exception; legacy fade; mixed standards; legend revision.

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 expansion uses a new owner legend while existing faded cables follow a prior standard.

Calculation: Reconcile legend versions, cable tags, product markings, endpoints, and approved exceptions.

Retrieval prompts

Module 4

Workmanship criteria, inspection, and objective defect writing

Why it matters: A professional finding says what/where/requirement/evidence/impact, not who to blame or merely that work looks bad.

Vocabulary and working scope

Source-qualified acceptance; observable condition; location/identity; requirement; consequence; severity; owner; correction; verification; photo/measurement; preference versus defect.

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 reviewer dislikes routing appearance, but only some conditions conflict with actual requirements.

Calculation: Calculate inspected/pass/fail/deferred counts and classify objective versus preference findings.

Retrieval prompts

Module 5

Redlines, dimensions, photos, privacy, and as-found facts

Why it matters: A redline does not self-approve design, and a close-up without context or safe identity is weak or unsafe evidence.

Vocabulary and working scope

Controlled drawing; actual route/location/elevation; cable/device/panel/terminal/address changes; dimensions; cloud/date/initial; RFI link; overview/context/detail photos; label/scale; before/after; hidden work; privacy; non-color 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

A sensor moved and a trunk changed floors with no dimensions; the hidden-work photo captures a password label but no equipment ID.

Calculation: Use scale/dimensions and reconcile every change/photo to issue, owner, approval, privacy check, and final drawing.

Retrieval prompts

Module 6

Daily reports, coordination, RFIs, and substitutions

Why it matters: Daily reports distinguish observed fact, planned work, pending decision, and approved change.

Vocabulary and working scope

Date/weather/access; staffing/work areas; completed/in-progress; inspections/tests; deliveries; constraints; coordination; safety observations; delays; RFI/change/substitution; owner; next plan.

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 route conflict stops work, but the report says only “waiting on others” and loses the technical question.

Calculation: Reconcile planned/completed/blocked quantities and calculate delay/decision status without unsupported blame.

Retrieval prompts

Module 7

Punch, nonconformance, severity, correction, and retest

Why it matters: Correction is not closure; independent verification and authorized disposition are required.

Vocabulary and working scope

Issue ID; asset/location; requirement; evidence; consequence; critical/major/minor project categories; owner; due; containment; correction; retest; closure authority; recurrence.

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 label was replaced but the drawing/database mismatch and recurrence across 20 boxes were not checked.

Calculation: Calculate aging, recurrence, closure/reopen, and retest coverage.

Retrieval prompts

Module 8

Turnover artifact architecture and version reconciliation

Why it matters: A folder of files is not turnover until identity, version, completeness, navigation, and unresolved risk are controlled.

Vocabulary and working scope

As-built drawings; submittals; sequences; points; panel/terminal/cable/address schedules; tests; calibration; backups; manuals; training; warranties; issue log; index; revision/checksum 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

The package contains two station backups, mismatched point lists, and no index showing which is final.

Calculation: Calculate artifact completeness, version conflicts, unresolved items, and acceptance status.

Retrieval prompts

Module 9

Installation-series quality dashboard and trend learning

Why it matters: Quality metrics support prevention only when definitions, denominator, sample, context, and ownership are clear.

Vocabulary and working scope

First-pass yield; defect category; rework hours; issue aging; repeated cause; inspection sample; vendor/crew neutrality; leading/lagging indicator; corrective action; lessons learned.

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

Most punch items are labels, but one crew worked from a stale legend and the metric lacks installed quantity.

Calculation: Calculate rates with denominators, Pareto shares, aging, and before/after corrective-action evidence.

Retrieval prompts

Module 10

Final record defense, secure archive, and OJL handoff

Why it matters: Professional records must be useful, honest, secure, and within authority; completeness claims require evidence.

Vocabulary and working scope

As-left truth; open risk/owner/due; acceptance signatures; secure storage; retention; access; export; sensitive-data handling; OJL observation criteria; lessons; release hold.

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 customer wants turnover today while two critical retests and one drawing conflict remain open.

Calculation: Reconcile all artifacts/issues/tests/approvals and calculate release readiness without averaging critical gaps.

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.