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

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

Secure remote session and workspace

Why it matters: Remote convenience never removes authorization, target control, audit, or restoration requirements.

Vocabulary and working scope

Named account; MFA; least privilege; approved target/port/action; reservation; audit; privacy; baseline; abort; logout; access 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 learner sees two similarly named JACEs and is unsure which one is the assigned training target.

Calculation: Reconcile reservation time, login/logout, target count, actions, and access-closure log.

Retrieval prompts

Module 2

Hierarchy, equipment, and point identity

Why it matters: A familiar point name is not sufficient identity; equipment, source controller, object/instance, units, and location must agree.

Vocabulary and working scope

Site; building; system; equipment; device; controller; object; point; instance; channel; source; naming; duplicate identity.

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 AHUs both contain a point named SAT and one graphic is bound to the wrong object.

Calculation: Reconcile point-list, controller-object, database, graphic, and equipment identities with zero unresolved duplicates.

Retrieval prompts

Module 3

Command, output, action, proof, and process

Why it matters: A front-end command or animated graphic does not prove physical action or process result.

Vocabulary and working scope

Requested value; effective priority; controller output; relay/interface; physical action; feedback; status; proof; process response.

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 fan command is on and the graphic fan icon is green, but duct static remains zero.

Calculation: Compare expected versus actual response at each chain link and record the last proven link.

Retrieval prompts

Module 4

Reliability, freshness, timestamps, and quality

Why it matters: A plausible value without current timestamp, quality, and source evidence may be more dangerous than an obvious fault.

Vocabulary and working scope

Reliability/status; stale/held/default/substituted values; timestamp; update rate; COV; clock source; timezone; daylight saving; historian delay.

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 outdoor-air temperature remains 55°F through a large weather change and shows no visible alarm.

Calculation: Calculate data age, clock offset, sampling interval, and event alignment before comparing points.

Retrieval prompts

Module 5

Schedules, calendars, modes, and exceptions

Why it matters: The displayed weekly schedule may not be the effective command when calendars, exceptions, optimum logic, or local overrides apply.

Vocabulary and working scope

Occupied/unoccupied; holiday; special event; warm-up; optimum start; local override; effective schedule; time zone; precedence; expiry.

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 building is unoccupied on a Tuesday despite a normal occupied weekly schedule.

Calculation: Calculate effective start/stop and exception duration using supplied timezone, calendar, and precedence data.

Retrieval prompts

Module 6

Trend design and interpretation

Why it matters: Trend more intentionally, not merely more: each point and interval must support a hypothesis or required context.

Vocabulary and working scope

Question; point set; units; mode; interval/COV; duration; timestamp; retention; export; normalization; missing data; aliasing; annotation.

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 VAV complaint lasts three minutes, but the trend interval is fifteen minutes and mixed time bases are used.

Calculation: Select sample interval from event duration and calculate rate, lag, duty cycle, and simultaneous-state windows.

Retrieval prompts

Module 7

Alarm lifecycle, routing, and triage

Why it matters: Acknowledging an alarm changes workflow state; it does not remove the underlying condition.

Vocabulary and working scope

Source; condition; limit; deadband; delay; enable; inhibit; event; notification; acknowledgment; return-to-normal; routing; escalation; 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 low-temperature alarm repeatedly returns after acknowledgment and is routed to the wrong team.

Calculation: Calculate alarm persistence, chatter frequency, deadband crossing, delay, and response time from event records.

Retrieval prompts

Module 8

Overrides, priorities, and relinquish behavior

Why it matters: Clearing an override without knowing the next effective priority and physical impact can create a new fault.

Vocabulary and working scope

Effective priority; source; value; duration; owner; reason; expiration; release; fallback; default; manual/HOA; override register.

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 damper remains at 100% after the visible operator override is released.

Calculation: Reconcile every active priority, source, timestamp, expiration, and effective result before and after release.

Retrieval prompts

Module 9

Offline cascades and stale graphics

Why it matters: Alarm count is not fault count; one upstream loss can create many derived or stale point symptoms.

Vocabulary and working scope

Device/network offline; parent-child alarm flood; last-known value; stale binding; partial recovery; router/switch/controller boundary; IT/OT handoff.

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

Fifty point alarms appear at the same second after one field controller loses communication.

Calculation: Group events by timestamp and dependency; compare unique root events to downstream alarm count.

Retrieval prompts

Module 10

Remote diagnosis, restoration, and handoff

Why it matters: A remote diagnosis is complete only when technical states and cyber access are both restored or explicitly transferred.

Vocabulary and working scope

Session plan; read-only first; approved commands; captures; change log; rollback; trainer reset; audit export; logout; account closure; customer record.

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 training fault is corrected, but a forced point and active remote account remain after logout.

Calculation: Reconcile session actions, captures, changes, overrides, alarms, restored baseline, and access closure; all critical states must close.

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.