Technical Trade SchoolBAS-500 platform-specialization
BAS-503
Concept reading and source route

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

Distech ecosystem and system architecture

Why it matters: Brand familiarity does not replace architecture: identify where logic executes, where values originate, which interface commands, and which service stores evidence.

Vocabulary and working scope

ECLYPSE; APEX; ECY; ECB; EC-Net; ENVYSION; EC-gfxProgram; Allure; room devices; edge/cloud boundary; supervisor; BACnet/IP; MS/TP; Modbus; MQTT 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

A project uses an ECLYPSE controller, ECB terminals, Allure sensors, embedded ENVYSION, and EC-Net supervision, but ownership of schedules and alarms is unclear.

Calculation: Count controllers, networks, supervisory services, protocol paths, execution locations, dependencies, and unresolved authorities.

Retrieval prompts

Module 2

Tool, firmware, license, hardware, and application selection

Why it matters: Similar-looking controllers are not interchangeable; supported tool/firmware pairing, resource limits, electrical ratings, licenses, and current product instructions govern.

Vocabulary and working scope

EC-gfxProgram version; controller family; firmware; license; host; I/O count/type; memory/resource; protocol support; room-device support; compatibility; replacement path.

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 replacement controller has enough terminals but lacks the required protocol option and does not support the existing room-device path.

Calculation: Reconcile physical and network I/O, program/resource load, protocol/device limits, spare capacity, license count, and support horizon.

Retrieval prompts

Module 3

EC-gfxProgram canvas, blocks, data types, and execution

Why it matters: A correct block diagram still fails when data type, initialization, execution order, persistence, or hidden interface assumptions are wrong.

Vocabulary and working scope

Project; device; program; block; link; Boolean; numeric; enum; time; persistent value; constants; execution order; task/cycle; encapsulation; naming; comments; 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

A fan latch returns after restart and a one-cycle pulse is consumed before an alarm block sees it.

Calculation: Build truth/state tables, trace values over several cycles, calculate timer behavior and execution margin, and compare expected to observed watch values.

Retrieval prompts

Module 4

Physical I/O, network values, scaling, priority, and failure

Why it matters: Universal terminals require explicit configuration; program value, object value, electrical output, proof, and process response remain separate claims.

Vocabulary and working scope

AI/AO/BI/BO/UI/UO; universal input; voltage/current/resistance; pulse; enum; BACnet value; units; facets; scaling; calibration; priority; fallback; quality; fail state.

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 0-10 V pressure sensor is configured to the wrong range while a higher BACnet priority holds the fan enable off.

Calculation: Calculate slope/intercept, endpoints/midpoint, loop and voltage plausibility, priority result, deviation, and proof timeout.

Retrieval prompts

Module 5

HVAC application patterns and sequence translation

Why it matters: A platform library accelerates work but never overrides the actual equipment, approved sequence, airflow/plant constraints, life-safety interfaces, or manufacturer limits.

Vocabulary and working scope

VAV; VVT; hybrid VVT with airflow reference; AHU; RTU; fan coil; heat pump; plant; occupancy; safeties; proofs; PID; reset; staging; alarms.

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 single-source rooftop system serves hybrid VVT zones with aftermarket crossflow airflow pickups and requires pressure-aware zone control without pretending it is a central VAV plant.

Calculation: Calculate airflow/setpoint scaling, loop error, reset slopes, stage thresholds, timing, diversity/request counts, and acceptance bands.

Retrieval prompts

Module 6

BACnet/IP, MS/TP, Modbus, and ECLYPSE network commissioning

Why it matters: A device discovered on a screen is not commissioned until unique identity, route, object meaning, timing/load, security, physical effect, and as-built record agree.

Vocabulary and working scope

IP addressing; VLAN/gateway; BACnet network/device identity; BBMD/FDR awareness; MS/TP MAC/baud/topology; routing; Modbus map; discovery; duplicate; time; DNS/NTP.

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 devices share an instance, an MS/TP segment has intermittent token loss, and an imported Modbus value uses the wrong word order.

Calculation: Reconcile subnet and BACnet identities, token/poll timing, register decoding, network load, latency, and before/after error counts.

Retrieval prompts

Module 7

Allure and room-device integration

Why it matters: Room display state must not imply controller acceptance or equipment proof; local choices require range, authority, timeout, feedback, and fallback.

Vocabulary and working scope

Allure; temperature; humidity; CO2/VOC; occupancy; setpoint; fan/mode; display; bus/path; calibration; limits; local authority; fallback; replacement; user experience.

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 occupant changes setpoint and fan mode, but the controller rejects one value and a failed humidity sensor remains displayed as normal.

Calculation: Calculate calibration offset, setpoint bounds, occupancy timeout, update/freshness, failed-sensor fallback, and command-to-acknowledgement time.

Retrieval prompts

Module 8

ENVYSION, EC-Net, alarms, trends, schedules, and operator truth

Why it matters: Operator presentation is correct only when context, units, status, freshness, permission, command, proof, failure, and audit behavior are tested together.

Vocabulary and working scope

Embedded visualization; EC-Net; equipment page; binding; value/status/time; command/proof; alarm; trend; schedule; user/role; remote path; inaccessible/null state.

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 shows a green fan after command despite no proof, and a schedule edit succeeds locally but is overwritten upstream.

Calculation: Measure top-task steps/time/errors, state coverage, history interval adequacy, alarm latency, schedule precedence, and permission outcomes.

Retrieval prompts

Module 9

Templates, download, debug, backup, and version control

Why it matters: Download success is not release evidence; source, generated project, controller-resident state, parameters, graphics, and backup must reconcile after normal/fault/restart tests.

Vocabulary and working scope

Reusable blocks; encapsulation; template; parameter; project; controller upload/download; compare; online values; debug; fault injection; backup; checksum; release; rollback.

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 copied fan-coil template uses an old point range and the controller upload does not match the project believed to be current.

Calculation: Count changed items and exceptions, compare checksums/versions, calculate download/test duration, regression pass rate, and rollback readiness.

Retrieval prompts

Module 10

Commissioning, cybersecurity, remote access, recovery, and turnover

Why it matters: Remote access uses a named account, least privilege, approved target/actions, time limit, logging, impact control, and verified logout/restoration; it never creates silent production authority.

Vocabulary and working scope

Readiness; point-to-point; functional test; users; roles; passwords; certificates; services; Neeve remote session; logging; backup; restore; issue/retest; as-built; training.

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 remote lab session remains connected after a download and one local override is still active when the student begins handoff.

Calculation: Reconcile test pass/fail/retest, user/permission exceptions, session duration, temporary states, RPO/RTO, and artifact completeness.

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.