BAS-504 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
Honeywell is an ecosystem, not one workflow; exact model, region, firmware, tool, license, bus, and project design control the engineering path.
Case overlay
A project combines WEBs supervision, Spyder terminals, Stryker VAVs, and an Optimizer plant controller, but the learner assumes one download process applies to all.
Calculation/evidence callout: Count devices, buses, execution locations, interfaces, licenses, dependencies, and ownership boundaries.
Normal-rule anchor
The smallest controller with enough terminals is not necessarily suitable; sequence complexity, program model, buses, licensing, support, and recovery matter.
Case overlay
A VAV controller fits the point count, but the sequence requires an unsupported hybrid airflow/zone feature and a network interface not present on that model.
Calculation/evidence callout: Reconcile I/O, devices, buses, program/resource load, spare capacity, licensing, support, and replacement constraints.
Normal-rule anchor
HOA and service interfaces are independent authority sources that must be visible, controlled, tested, and restored; the program cannot silently override field reality.
Case overlay
An output remains in a local HOA state after software testing and a retained parameter changes the restart sequence.
Calculation/evidence callout: Build truth/state tables, calculate timing/scaling, reconcile command sources, and compare expected versus observed values through restart.
Normal-rule anchor
Do not force a programmable workflow onto a wizard-based application or vice versa; document which behavior is fixed, configurable, exposed, hidden, or unsupported.
Case overlay
A wall module displays setpoint correctly, but the terminal application maps occupancy and airflow units differently than the supervisor.
Calculation/evidence callout: Calculate sensor calibration, setpoint limits, airflow scaling, timing, parameter bounds, and archive/live configuration differences.
Normal-rule anchor
A displayed value without source, units, status, freshness, command authority, and independent proof is incomplete evidence.
Case overlay
A valve is commanded closed at one priority, held open locally, and its discharge-temperature trend still looks plausible because the sensor is stale.
Calculation/evidence callout: Calculate scaling, deviation, priority resolution, loop/output plausibility, proof time, and failed-sensor fallback.
Normal-rule anchor
Library, wizard, and example applications require project-specific review; equipment physics, sequences, TAB/design data, safeties, and owner criteria govern.
Case overlay
A hybrid VVT zone uses an aftermarket crossflow pickup for airflow reference under a single-source rooftop system, while a nearby pressure-independent VAV uses a central AHU.
Calculation/evidence callout: Calculate airflow and setpoint scaling, PID error, reset slopes, ventilation/minimums, stage timing, and request logic.
Normal-rule anchor
A bus name does not guarantee compatible power, topology, devices, addressing, or tools; exact current instructions control.
Case overlay
A mixed trunk has a duplicate instance, a wrong baud device, and a Sylk wall module drawing power but not exchanging valid data.
Calculation/evidence callout: Reconcile addresses and identities, segment/device limits, update/poll timing, scaling, error counts, and response latency.
Normal-rule anchor
Supervisory success is not device or process proof; every imported point and action requires identity, units, status, source, priority, physical effect, and failure-state testing.
Case overlay
An imported schedule overrides a local calendar, and a fan graphic animates on command despite a failed current switch.
Calculation/evidence callout: Measure binding/point coverage, history sampling, alarm delivery, schedule precedence, command-to-proof, and task performance.
Normal-rule anchor
Security and lifecycle changes are operational changes: least privilege, availability, emergency access, supported versions, dependencies, backups, rollback, and functional proof travel together.
Case overlay
A legacy Spyder site moves under a newer WEBs supervisor while shared accounts and expired certificates remain undocumented.
Calculation/evidence callout: Calculate account/role exceptions, certificate lead, version/support gaps, backup age, migration coverage, RPO/RTO, and postchange pass rate.
Normal-rule anchor
A successful download is only one event; release requires requirement coverage, normal/fault/restart tests, no unreleased command or HOA state, known backup, and reproducible as-left evidence.
Case overlay
The controller passes occupied cooling, fails proof-loss shutdown, and the project file differs from the uploaded live application.
Calculation/evidence callout: Reconcile requirements/tests/issues/retests, compare versions/checksums, calculate response and recovery times, and account for every temporary state.