BOOT-N4 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
Niagara procedures and artifacts are distribution/build/module dependent; source, deployed, backup, and supported state must be distinguished.
Case overlay
Two stations report the same version label but have different module sets and one backup cannot start in the recovery lab.
Calculation/evidence callout: Calculate version/dependency coverage, backup age, restore success/time, resource margin, and unsupported-condition count.
Normal-rule anchor
Connectivity does not justify accepting unknown certificates, disabling validation, sharing credentials, or broadening roles.
Case overlay
A station reconnects only when trust checks are disabled; its clock is wrong and the replacement certificate identity changed.
Calculation/evidence callout: Calculate clock skew, certificate/renewal window, role/permission coverage, failed-login rate, and trust-path completeness.
Normal-rule anchor
Alarm reduction requires rationalization and cause correction; suppression is temporary controlled state, not proof of resolution.
Case overlay
One failed sensor produces 300 downstream alarms while an important fan-proof alarm never reaches the operator.
Calculation/evidence callout: Calculate alarm rate, top contributors, standing/stale counts, actionability, routing coverage, flood reduction, and suppression closure.
Normal-rule anchor
More samples are not automatically better evidence; process dynamics, question, storage, quality, and clock alignment govern.
Case overlay
A five-minute trend misses short cycling, while a faster trend doubles storage and repeats samples after time correction.
Calculation/evidence callout: Calculate sample interval, storage/retention, gap/duplicate percentage, clock offset, cycle frequency, and detection limits.
Normal-rule anchor
A syntactically valid query can be operationally wrong through scope, semantics, missing data, type conversion, or hidden exclusions.
Case overlay
A query identifies 180 points for change but omits disabled stations and includes test equipment.
Calculation/evidence callout: Calculate expected/returned/verified counts, precision/recall on a sample, null/type rates, and target-manifest reconciliation.
Normal-rule anchor
Names and tags are data contracts; cosmetic consistency is insufficient when relations, types, context, or consumers break.
Case overlay
A reusable VAV page works on one station and binds to the wrong discharge temperature on another because context relations differ.
Calculation/evidence callout: Calculate semantic coverage, orphan/duplicate rates, template binding success, exception rate, and migration completeness.
Normal-rule anchor
A graphic is not correct because it renders; target context, data state, authority, action result, physical proof, and recovery must be visible.
Case overlay
A floor page opens the wrong equipment after navigation and shows an override as normal for one role.
Calculation/evidence callout: Calculate task success/time, binding/state coverage, command/proof latency, accessibility defects, and reuse exception rate.
Normal-rule anchor
Bulk work multiplies both benefit and error; a completed job status does not prove every target, function, restart, or restore.
Case overlay
A batch upgrade succeeds on 18 of 20 stations, one is offline, and one restarts with a driver disabled.
Calculation/evidence callout: Calculate target/pilot/success/exception rates, duration, bandwidth/load, resource margin, retry/rollback, and final version coverage.
Normal-rule anchor
The last exception line, high CPU, or offline point is a symptom until context, timing, scope, and alternatives are tested.
Case overlay
Graphics freeze every hour while CPU is moderate; station output shows queue growth after a scheduled export.
Calculation/evidence callout: Calculate baseline versus incident latency/load, error and retry rates, queue growth, resource headroom, and test discrimination.
Normal-rule anchor
Security and optimization changes require operational acceptance, supportability, rollback, and changed-case regression, not just configuration compliance. A station that starts is not recovered until dependencies, identity, secure relationships, drivers, critical logic/data/operator paths, and documentation are validated.
Case overlay
Disabling a legacy service improves posture but breaks an undocumented integration and delays alarms. Changed-capstone condition: A restored station runs but certificates, histories, alarm routing, and one driver differ from the baseline.
Calculation/evidence callout: Calculate before/after objective, required-flow/function coverage, regression pass rate, residual exposure, rollback time, and monitoring period. Calculate RTO achievement, recovered/dependency/version coverage, critical-test pass rate, residual differences, and restoration completeness.