Technical Trade SchoolBOOT advanced-bootcamp
BOOT-CX
Ten concept and evidence figures

BOOT-CX Visual Aid Library

Figure-use rule

Each figure is an orientation and reasoning aid, not a project drawing. Learners must pair it with the current sequence, point list, wiring/piping documents, manufacturer instructions, and as-found evidence.

Figure 1 — Controlled lab baseline, source/live truth and recovery critical

Normal-rule anchor

Procedure accuracy is version and controller specific; a source file is not proven deployed truth until compared and tested.

Case overlay

The provided .CXB opens with missing libraries and the live controller differs from the handoff version.

Calculation/evidence callout: Reconcile required/actual versions and dependencies; calculate coverage, age, checksum matches, and recovery time.

Figure 2 — Cylon architecture, controller families and project structure critical

Normal-rule anchor

Product-family similarity does not prove capacity, I/O, firmware, or feature equivalence; exact data controls.

Case overlay

A template developed for one controller family exceeds available points and memory on another target.

Calculation/evidence callout: Calculate point/capacity utilization, expansion requirements, network counts, spare margin, and unsupported features.

Figure 3 — Mixed I/O, UniPut, BACnet objects, scaling and proof critical

Normal-rule anchor

I/O configuration, object value, strategy value, and physical process are related but independent evidence layers.

Case overlay

A universal input reads plausibly while configured for the wrong thermistor curve; an output object changes without actuator travel.

Calculation/evidence callout: Calculate linear scaling, sensor error, command/proof error, timeout, and state-table coverage.

Figure 4 — Blocks, data types, execution, timing and readable strategy

Normal-rule anchor

A strategy that appears to work in one steady state may fail on startup, type conversion, race/timing, or retained state.

Case overlay

A latch remains true after restart and a numeric block silently interprets an enumerated state.

Calculation/evidence callout: Calculate scan versus process timing, timer behavior, type/range limits, block utilization, and test coverage.

Figure 5 — Requirement decomposition, states, permissives, PID and restart critical

Normal-rule anchor

Every transition needs trigger, prerequisites, action, proof, timeout/fault response, recovery, and restart behavior.

Case overlay

A lead pump starts from schedule but restarts after a power interruption without proof or anti-cycle delay.

Calculation/evidence callout: Calculate reset slope, PID error/output limits, deadband, stage thresholds, minimum on/off time, and transition coverage.

Figure 6 — Terminal, VAV, VVT and fan-coil applications critical

Normal-rule anchor

Application templates require a verified equipment and sensor contract; VAV, pressure-dependent VVT, and measured-airflow hybrid VVT are not interchangeable.

Case overlay

A hybrid VVT box uses a crossflow pickup but the strategy applies VAV minimums without verifying central-unit mode or pressure reference.

Calculation/evidence callout: Calculate airflow from supplied DP relationship, zone demand, minimum/maximum limits, heating/cooling transitions, and changed-case coverage.

Figure 7 — AHU and plant applications with safeties and staging critical

Normal-rule anchor

Supervisory logic must not replace listed/hardwired safeties, and a commanded state is not equipment or process proof.

Case overlay

An AHU fan command is on while proof is false and static pressure rises because isolation dampers remain closed.

Calculation/evidence callout: Calculate reset, PID/staging thresholds, proof timeout, load/temperature relationships, runtime balance, and recovery sequence.

Figure 8 — BACnet/IP, MS/TP, FLX identity, routing and load critical

Normal-rule anchor

One online indication is insufficient; identity, topology, error counters, timing, service acceptance, and application freshness must agree.

Case overlay

Objects read locally but not from INTEGRA after a network-number conflict and polling increase.

Calculation/evidence callout: Calculate subnet/identity inventory, token/update time, poll/COV load, error rate, and capacity margin.

Figure 9 — Download, upload, compare, watch, debug and rollback critical

Normal-rule anchor

A successful download is not acceptance; correct target, deployed artifact, function, failure, restart, rollback, and restoration must be proven.

Case overlay

A mass download reaches 14 of 16 controllers and leaves two with mismatched versions and one test override.

Calculation/evidence callout: Calculate completion/exception rate, version/checksum coverage, deployment duration, rollback time, and temporary-state closure.

Figure 10 — INTEGRA, graphics, alarms, trends, schedules and operator truth; Point-to-point, functional commissioning, recovery and handoff critical

Normal-rule anchor

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.

Case overlay

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/evidence callout: 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.