BAS-505 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.
ABB Cylon ecosystem and engineering architecture
Why it matters: ABB Cylon is a family of related but distinct products; exact model, firmware, tool, module, license, and project architecture control the workflow.
Vocabulary and working scope
CXproHD; site; network; controller; strategy; CB family; FB family; CBXi/FBXi; CBV/FBV; CBT; FLX; INTEGRA; BuildingPro; INTEGRA-ProPack; Niagara supervision.
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 site has CBV terminals, an FBXi plant controller, FLX I/O, and an INTEGRA supervisor, but the learner cannot identify which project contains the source strategy.
Calculation: Count devices, networks, strategies, I/O, supervisory dependencies, licenses, and unresolved sources of truth.
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?
Controller-family and hardware selection
Why it matters: A controller that fits physically may still fail the application because of I/O mode, resource, firmware, bus, program, licensing, or lifecycle limits.
Vocabulary and working scope
CBM; CBT; CBV; CBR; CBXi; FBXi; FBVi; UniPut; FLX; I/O count/type; power; communications; memory/resource; firmware; replacement; lifecycle.
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 proposed replacement has the right enclosure footprint but insufficient UniPut modes and a different supported firmware path.
Calculation: Reconcile I/O by type, UniPut modes, expansion capacity, program/resource load, network limits, spare capacity, and lifecycle risk.
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?
CXproHD site, network, controller, strategy, and version model
Why it matters: Saved project, open strategy, live controller, exported archive, and supervisor database can disagree; source-of-truth must be established, not assumed.
Vocabulary and working scope
Project/site; network; device; strategy; address; database; upload/download; firmware; tool version; license; source/live state; archive; compare; revision.
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 strategy opens under v1.07.06, but the controller firmware and archived .CXB reflect a prior commissioning revision.
Calculation: Compare versions, checksums where available, timestamps, device/strategy counts, missing dependencies, and change 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?
Strategy blocks, data types, execution, and readable logic
Why it matters: Block connections do not explain intent; types, units, initialization, execution order, timing, priority, failure, comments, and test vectors must be explicit.
Vocabulary and working scope
Boolean; numeric; enum; variable; constant; function block; link; execution order; timer; latch; selector; PID; state; retained value; naming; comments; revision; reusable macro.
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 fan strategy restarts latched on and a timer output reaches a dependent block one execution cycle later than expected.
Calculation: Build truth/state tables, trace several cycles, calculate timing and analog math, and compare predicted with observed strategy values.
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?
I/O, UniPut, scaling, BACnet priority, and safe failure
Why it matters: UniPut flexibility requires exact mode and electrical verification; a plausible strategy value can still be the wrong signal, priority, or physical state.
Vocabulary and working scope
AI/AO/BI/BO/UI/UO; UniPut mode; voltage/current/resistance; pulse; units; calibration; object; priority; relinquish; quality; fallback; fail state; command; proof.
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
An output is configured for the wrong electrical mode while BACnet priority 8 masks the strategy command.
Calculation: Calculate scaling endpoints/midpoint, current/voltage plausibility, effective priority, deviation, proof timeout, and fallback result.
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?
Terminal and fan-coil strategy centerpiece
Why it matters: Terminal logic must match the actual physical coil, valve, fan, airflow, sensor, changeover, and safety arrangement; a stock example is only a starting hypothesis.
Vocabulary and working scope
CBV/FBV; fan coil; VAV/VVT awareness; occupancy; zone temperature; airflow; fan speeds; valve/damper; reheat; condensate/window/contact; frost; deadband; changeover; alarms.
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 four-pipe fan coil has three fan speeds, a window contact, condensate alarm, and valves that must not overlap under changeover faults.
Calculation: Calculate deadbands, airflow/temperature scaling, fan thresholds, valve timing, occupancy delays, and changed-case acceptance.
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?
AHU, plant, VAV, staging, and coordinated applications
Why it matters: Coordination logic cannot hide mechanical design constraints or listed safeties; every request and effective command requires source, limits, proof, fallback, and ownership.
Vocabulary and working scope
AHU; RTU; VAV; hybrid VVT; pumps; boilers; chillers; lead/lag; staging; minimum flow; reset; trim/respond; safeties; proofs; failure substitution.
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 pumps alternate weekly, but one fails proof during low-load operation and minimum-flow protection must survive lead substitution.
Calculation: Calculate staging thresholds, run-hour rotation, minimum on/off time, flow/reset values, request persistence, and proof-response limits.
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?
BACnet/IP, MS/TP, FLX, routing, and addressing
Why it matters: Discovery is incomplete evidence; exact identity, path, electrical topology, object semantics, timing/load, command authority, and process result must agree.
Vocabulary and working scope
Device instance; network number; IP/subnet/gateway; MS/TP MAC/baud; topology; FLX bus; router; discovery; duplicate; object list; polling/COV; PICS; writable behavior.
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 controller is visible through two routes, an MS/TP MAC is duplicated, and FLX I/O appears but updates intermittently.
Calculation: Reconcile all identities, segment/device load, token/poll timing, latency, error counts, object coverage, and physical response.
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?
INTEGRA, BuildingPro, graphics, alarms, trends, and tuning
Why it matters: Supervisory objects and ProPack components accelerate engineering but require exact version support, state testing, performance baseline, and physical/process validation.
Vocabulary and working scope
INTEGRA; BuildingPro; ProPack; Niagara station; driver; points; graphics; alarms; histories; schedules; users; tuning; command/proof; stale/null; audit.
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 ProPack component reports normal while its source point is stale, and a tuning change improves discovery but overloads an older field network.
Calculation: Measure point/binding coverage, history sampling, alarm delivery, schedule precedence, poll/write load, latency, and resource margin.
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?
Download, debug, firmware, .CXB backup, recovery, and turnover
Why it matters: A project archive is not a proven recovery asset until restored on a compatible isolated target and critical I/O, strategies, networks, supervisory services, users, and operator tasks pass.
Vocabulary and working scope
Baseline; strategy upload/download; compare; online values; fault injection; firmware; archive; .CXB; clean restore; point-to-point; functional test; issue/retest; as-built; training.
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 firmware change succeeds but one strategy differs from source and two temporary priorities remain after testing.
Calculation: Reconcile planned/applied/retested items, compare versions/artifacts, calculate RPO/RTO and pass rate, and account for every temporary state and open risk.
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
- ABB CXproHD official catalog
Current official programming and commissioning product role for Cylon BACnet controller families. - CXproHD v1.07.06 bulletin
Designated lab-version change and compatibility evidence; never assume universal behavior from the course version. - Cylon INTEGRA-ProPack manual
Engineering-library source for Niagara integration, services, components, and supported workflows. - Niagara Workbench Guide-LITE
Workbench views, component model, navigation, points, histories, alarms, schedules, and station workflow. - Working with BACnet
Engineering-library reference for objects, properties, services, networks, and evidence-driven troubleshooting. - ANSI/ASHRAE Standard 135-2024 scope route
Current published BACnet standard scope and edition route; adopted project edition and addenda govern. - ASHRAE Guideline 13-2024
BAS architecture, hardware, communications, programming, testing, documentation, cybersecurity, and legacy-system framework. - NIST SP 800-82 Rev. 3
Current OT security guidance for accounts, segmentation, remote access, monitoring, change, and recovery.