BAS-501 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
Platform administration, station engineering, driver integration, and operator use are different contexts; the visible tree never proves the physical process by itself.
Case overlay
A learner can open a station tree but cannot explain whether a failed connection belongs to the platform daemon, station, Fox link, or field driver.
Calculation/evidence callout: Create a dependency matrix and count every required component, service, license, interface, evidence source, and unresolved owner.
Normal-rule anchor
A version number alone is not compatibility evidence; OEM distribution, exact build, modules, dependencies, license, host platform, and support policy travel together.
Case overlay
Workbench opens an older station, but two modules are missing and a license feature is unavailable after copying it to a new laptop.
Calculation/evidence callout: Reconcile required versus installed versions, dependencies, feature counts, capacity, expiration dates, storage margin, and rollback prerequisites.
Normal-rule anchor
Commissioning changes the computer beneath the station; it requires an impact plan, known-good backup, exact target, protected credentials, abort criteria, and functional postchecks.
Case overlay
A JACE is reachable on a bench address but has wrong time, stale certificates, an unknown station copy, and no tested backup.
Calculation/evidence callout: Calculate addressing, storage/headroom, elapsed outage, backup age, time offset, and recovery objective; compare each to the supplied criterion.
Normal-rule anchor
A component is not its view; present value, effective command, electrical output, equipment action, and process result are separate claims qualified by identity, type, path, status, source, and freshness.
Case overlay
Two points share a display name, a graphic binds to the wrong proxy path, priority 8 remains active, and fan proof is off.
Calculation/evidence callout: Resolve path and dependencies, convert raw values, reconcile priorities/fallback, and calculate deviation, freshness, proof timeout, and rename/move blast radius.
Normal-rule anchor
Trends, alarms, and schedules are operational programs with source, time, quality, ownership, retention, test, and restoration requirements.
Case overlay
A zone complaint is hidden by a coarse interval, alarm routing is outside the active window, and a holiday exception outranks the weekly schedule.
Calculation/evidence callout: Calculate sample coverage, storage, time alignment, persistence/deadband, schedule overlap, and override expiry with units and acceptance bounds.
Normal-rule anchor
Discovery proves a response, not correctness, ownership, writable authority, units, or physical effect; read before write and preserve all temporary state.
Case overlay
A device appears twice through two routes, point units disagree with the submittal, and a write succeeds without equipment response.
Calculation/evidence callout: Reconcile network/device uniqueness, poll and COV load, token timing, value scaling, and command-to-proof response.
Normal-rule anchor
Connectivity restored by disabling trust, sharing an account, or granting broad permissions is a failed repair.
Case overlay
A supervisor cannot connect after a certificate renewal, and an operator role can reach a platform action it should not use.
Calculation/evidence callout: Calculate certificate lead time, account/role coverage, permission exceptions, session duration, and route/service exposure against policy.
Normal-rule anchor
Reusable engineering makes variation explicit and carries requirements, units, failure behavior, test cases, version, and rollback with the template.
Case overlay
A copied VAV template contains absolute links, a retained override, and a timer that behaves differently after restart.
Calculation/evidence callout: Build truth/state tables, calculate scaling and timing, check template coverage, and compare expected and actual values over multiple scans.
Normal-rule anchor
A graphic is an operating interface, not decoration; it fails when it implies proof from command, hides bad data, loses context, or exposes an unsafe action.
Case overlay
A fan animates from command, a missing temperature displays zero, and a copied page operates the wrong VAV.
Calculation/evidence callout: Measure top-task steps/time/errors, binding coverage, missing-state handling, and action-to-proof timeout against acceptance criteria.
Normal-rule anchor
A backup is only a recovery hypothesis until restored and functionally tested with required modules, licenses, certificates, users, networks, services, graphics, alarms, histories, and schedules.
Case overlay
A power event leaves one station down, time wrong, histories stopped, and a replacement controller available but unproved.
Calculation/evidence callout: Compute RPO, RTO, backup age, restore duration, unresolved count, function pass rate, and evidence completeness with reasonableness checks.