BOOT-CX 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.
Controlled lab baseline, source/live truth and recovery
Why it matters: Procedure accuracy is version and controller specific; a source file is not proven deployed truth until compared and tested.
Vocabulary and working scope
CXproHD version; controller family/model; firmware; license; libraries/ProPack; connection; project/source copy; deployed copy; checksum/version; backup; reset; authority; stop.
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
The provided .CXB opens with missing libraries and the live controller differs from the handoff version.
Calculation: Reconcile required/actual versions and dependencies; calculate coverage, age, checksum matches, and recovery time.
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?
Cylon architecture, controller families and project structure
Why it matters: Product-family similarity does not prove capacity, I/O, firmware, or feature equivalence; exact data controls.
Vocabulary and working scope
Site; network; controller; strategy; FLX/CB/FB awareness; I/O expansion; BACnet identities; capacity; licensing; INTEGRA relationship; application fit.
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 template developed for one controller family exceeds available points and memory on another target.
Calculation: Calculate point/capacity utilization, expansion requirements, network counts, spare margin, and unsupported features.
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?
Mixed I/O, UniPut, BACnet objects, scaling and proof
Why it matters: I/O configuration, object value, strategy value, and physical process are related but independent evidence layers.
Vocabulary and working scope
AI/AO/BI/BO/UniPut; signal type/range; units; calibration; normal/fail state; BACnet object; priority; command; feedback; physical proof; safeties.
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 universal input reads plausibly while configured for the wrong thermistor curve; an output object changes without actuator travel.
Calculation: Calculate linear scaling, sensor error, command/proof error, timeout, and state-table 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?
Blocks, data types, execution, timing and readable strategy
Why it matters: A strategy that appears to work in one steady state may fail on startup, type conversion, race/timing, or retained state.
Vocabulary and working scope
Block contracts; Boolean/analog/enumerated values; execution order; scan/update timing; retained state; initialization; naming; comments; modules/macros; dead code; diagnostics.
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 latch remains true after restart and a numeric block silently interprets an enumerated state.
Calculation: Calculate scan versus process timing, timer behavior, type/range limits, block utilization, and test 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?
Requirement decomposition, states, permissives, PID and restart
Why it matters: Every transition needs trigger, prerequisites, action, proof, timeout/fault response, recovery, and restart behavior.
Vocabulary and working scope
Sequence clauses; mode/state tables; enable/permissive/interlock/safety; setpoint/reset; PID; deadband; hysteresis; staging; anti-cycle; fallback; restart; manual/auto.
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 lead pump starts from schedule but restarts after a power interruption without proof or anti-cycle delay.
Calculation: Calculate reset slope, PID error/output limits, deadband, stage thresholds, minimum on/off time, and transition 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?
Terminal, VAV, VVT and fan-coil applications
Why it matters: Application templates require a verified equipment and sensor contract; VAV, pressure-dependent VVT, and measured-airflow hybrid VVT are not interchangeable.
Vocabulary and working scope
Zone demand; occupancy; airflow/pressure; damper; reheat; fan; condensation/freeze; ventilation; single-source VVT; measured-airflow hybrid; limits; local/network fallback.
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 hybrid VVT box uses a crossflow pickup but the strategy applies VAV minimums without verifying central-unit mode or pressure reference.
Calculation: Calculate airflow from supplied DP relationship, zone demand, minimum/maximum limits, heating/cooling transitions, and changed-case 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?
AHU and plant applications with safeties and staging
Why it matters: Supervisory logic must not replace listed/hardwired safeties, and a commanded state is not equipment or process proof.
Vocabulary and working scope
AHU modes; fans/proof; dampers/valves; economizer; SAT/static reset; coils; freeze/smoke boundaries; pumps; lead/lag; boilers/chillers; staging; failure/restart.
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 AHU fan command is on while proof is false and static pressure rises because isolation dampers remain closed.
Calculation: Calculate reset, PID/staging thresholds, proof timeout, load/temperature relationships, runtime balance, and recovery sequence.
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 identity, routing and load
Why it matters: One online indication is insufficient; identity, topology, error counters, timing, service acceptance, and application freshness must agree.
Vocabulary and working scope
IP/device/network/MAC identity; topology; baud; Max_Master; routing; BBMD awareness; object exposure; polling/COV; FLX expansion; duplicate identity; diagnostics.
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
Objects read locally but not from INTEGRA after a network-number conflict and polling increase.
Calculation: Calculate subnet/identity inventory, token/update time, poll/COV load, error rate, and capacity 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, upload, compare, watch, debug and rollback
Why it matters: A successful download is not acceptance; correct target, deployed artifact, function, failure, restart, rollback, and restoration must be proven.
Vocabulary and working scope
Target verification; source/deployed compare; backup; compile/validation; download scope; impact; watch values; forced/test states; audit; fault injection; abort; rollback; restart; clean state.
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 mass download reaches 14 of 16 controllers and leaves two with mismatched versions and one test override.
Calculation: Calculate completion/exception rate, version/checksum coverage, deployment duration, rollback time, and temporary-state closure.
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, graphics, alarms, trends, schedules and operator truth; Point-to-point, functional commissioning, recovery and handoff
Why it matters: A polished supervisor page is unsafe if identity, status, stale/override/fault state, authority, accepted command, physical proof, or denial is hidden. Commissioning closes only when field/object/logic/process evidence, exception handling, restart, recovery, records, and temporary-state reconciliation pass.
Vocabulary and working scope
Supervisor integration; point import; names/units/status; graphics; commands; alarms; trends; schedules; users/roles; time; history; operator workflow; latency; audit. Readiness; point tests; normal/boundary/failure/restart; issue/retest; regression; backup; .CXB; version manifest; recovery; as-built; operator handoff; defense.
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 graphic command appears accepted for an unauthorized role while the controller rejects it and the trend timestamp is stale. Changed-capstone condition: Steady-state tests pass, but failed-sensor fallback and backup restore were never exercised.
Calculation: Calculate command/proof timing, sample/storage needs, stale thresholds, alarm delay, role-test coverage, and task success. Calculate test and requirement coverage, defects/retest, restore time, version reconciliation, temporary-state closure, and residual 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 Cylon CXproHD official catalog route
Current platform route; exact designated lab baseline and controller-family documentation govern procedures. - ASHRAE Standard 135 official scope and current-edition route
Confirm the current standard, addenda, interpretations, adopted/project requirements, and product implementation before making a compliance claim. - ASHRAE Guideline 13-2024
BAS specification, installation, integration, testing, documentation, cybersecurity, and lifecycle context. - NIST SP 800-82 Rev. 3
OT governance, architecture, access, monitoring, incident response, backup, recovery, and compensating-control guidance.