BAS-505 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.
Normal-rule anchor
ABB Cylon is a family of related but distinct products; exact model, firmware, tool, module, license, and project architecture control the workflow.
Case overlay
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/evidence callout: Count devices, networks, strategies, I/O, supervisory dependencies, licenses, and unresolved sources of truth.
Normal-rule anchor
A controller that fits physically may still fail the application because of I/O mode, resource, firmware, bus, program, licensing, or lifecycle limits.
Case overlay
A proposed replacement has the right enclosure footprint but insufficient UniPut modes and a different supported firmware path.
Calculation/evidence callout: Reconcile I/O by type, UniPut modes, expansion capacity, program/resource load, network limits, spare capacity, and lifecycle risk.
Normal-rule anchor
Saved project, open strategy, live controller, exported archive, and supervisor database can disagree; source-of-truth must be established, not assumed.
Case overlay
A strategy opens under v1.07.06, but the controller firmware and archived .CXB reflect a prior commissioning revision.
Calculation/evidence callout: Compare versions, checksums where available, timestamps, device/strategy counts, missing dependencies, and change coverage.
Normal-rule anchor
Block connections do not explain intent; types, units, initialization, execution order, timing, priority, failure, comments, and test vectors must be explicit.
Case overlay
A fan strategy restarts latched on and a timer output reaches a dependent block one execution cycle later than expected.
Calculation/evidence callout: Build truth/state tables, trace several cycles, calculate timing and analog math, and compare predicted with observed strategy values.
Normal-rule anchor
UniPut flexibility requires exact mode and electrical verification; a plausible strategy value can still be the wrong signal, priority, or physical state.
Case overlay
An output is configured for the wrong electrical mode while BACnet priority 8 masks the strategy command.
Calculation/evidence callout: Calculate scaling endpoints/midpoint, current/voltage plausibility, effective priority, deviation, proof timeout, and fallback result.
Normal-rule anchor
Terminal logic must match the actual physical coil, valve, fan, airflow, sensor, changeover, and safety arrangement; a stock example is only a starting hypothesis.
Case overlay
A four-pipe fan coil has three fan speeds, a window contact, condensate alarm, and valves that must not overlap under changeover faults.
Calculation/evidence callout: Calculate deadbands, airflow/temperature scaling, fan thresholds, valve timing, occupancy delays, and changed-case acceptance.
Normal-rule anchor
Coordination logic cannot hide mechanical design constraints or listed safeties; every request and effective command requires source, limits, proof, fallback, and ownership.
Case overlay
Two pumps alternate weekly, but one fails proof during low-load operation and minimum-flow protection must survive lead substitution.
Calculation/evidence callout: Calculate staging thresholds, run-hour rotation, minimum on/off time, flow/reset values, request persistence, and proof-response limits.
Normal-rule anchor
Discovery is incomplete evidence; exact identity, path, electrical topology, object semantics, timing/load, command authority, and process result must agree.
Case overlay
A controller is visible through two routes, an MS/TP MAC is duplicated, and FLX I/O appears but updates intermittently.
Calculation/evidence callout: Reconcile all identities, segment/device load, token/poll timing, latency, error counts, object coverage, and physical response.
Normal-rule anchor
Supervisory objects and ProPack components accelerate engineering but require exact version support, state testing, performance baseline, and physical/process validation.
Case overlay
A ProPack component reports normal while its source point is stale, and a tuning change improves discovery but overloads an older field network.
Calculation/evidence callout: Measure point/binding coverage, history sampling, alarm delivery, schedule precedence, poll/write load, latency, and resource margin.
Normal-rule anchor
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.
Case overlay
A firmware change succeeds but one strategy differs from source and two temporary priorities remain after testing.
Calculation/evidence callout: Reconcile planned/applied/retested items, compare versions/artifacts, calculate RPO/RTO and pass rate, and account for every temporary state and open risk.