BOOT-NIA 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
Interfaces exist to support safe decisions and actions; screen inventories and visual preference are secondary to consequential tasks.
Case overlay
An operator must identify why a zone is hot, but the dashboard shows scores without source state, time, or drilldown.
Calculation/evidence callout: Calculate task frequency/consequence priority, required evidence coverage, decision time, and unresolved task risk.
Normal-rule anchor
A page that is easy to reach but loses building, equipment, role, or time context can produce a fast wrong action.
Case overlay
Two AHUs share similar names and a floor link opens the same relative page against the wrong station context.
Calculation/evidence callout: Calculate path depth/clicks, wrong-context rate, task time, orphan/dead-end links, and responsive coverage.
Normal-rule anchor
Every visual element needs a task purpose and complete data-state behavior; image ownership and accessibility are design requirements.
Case overlay
A gauge shows 72.000 degrees with no unit while a missing point renders as zero and a copied icon has unknown rights.
Calculation/evidence callout: Calculate precision from sensor/process need, chart scale, asset/license coverage, state coverage, and clutter/task ratio.
Normal-rule anchor
A binding that works in normal state is incomplete until identity, quality, time, failure, override, and changed context are visible.
Case overlay
A temperature tile binds correctly on AHU-1, converts units twice on AHU-2, and shows stale data as normal.
Calculation/evidence callout: Calculate binding/state coverage, value/unit error, stale threshold, exception count, and two-instance reuse pass rate.
Normal-rule anchor
A button click or successful write is not successful equipment operation, and the interface must not imply otherwise.
Case overlay
A fan command displays success for a viewer role while a higher priority prevents operation and no timeout appears.
Calculation/evidence callout: Calculate bounds, effective priority, command/proof error and timeout, denial coverage, audit completeness, and temporary-state closure.
Normal-rule anchor
Reuse is a governed contract, not copy/paste; every variant and failure state must remain truthful.
Case overlay
A VAV template works until a fan-powered box lacks discharge temperature and an older page expects a renamed slot.
Calculation/evidence callout: Calculate required/optional contract coverage, exception rate, regression scope/pass rate, and maintenance reduction.
Normal-rule anchor
Semantic automation inherits data-quality defects; generated navigation requires validation and governed exceptions.
Case overlay
A filter excludes untagged critical equipment and groups two pumps under the wrong plant relation.
Calculation/evidence callout: Calculate semantic coverage, orphan/duplicate/ambiguous rates, filter precision/recall on a sample, and remediation backlog.
Normal-rule anchor
Alarm, trend, and schedule widgets are useful only when identity, quality, time, lifecycle, authority, and source context are preserved.
Case overlay
A comfort complaint page hides an active schedule exception and trends use a different timezone than alarm timestamps.
Calculation/evidence callout: Calculate time offset, sample adequacy, alarm/task coverage, schedule precedence, and evidence retrieval time.
Normal-rule anchor
Accessibility is operational quality: an action or state unavailable without a mouse, color vision, perfect sight, or fast network is a functional defect.
Case overlay
The alarm table is unreadable at 200% zoom, keyboard focus disappears, and a mobile action button covers proof state.
Calculation/evidence callout: Calculate contrast from approved tools, task success/time/error by mode, breakpoint/state coverage, and latency percentiles.
Normal-rule anchor
A deployment is incomplete until the right artifact is on the right target, tasks pass across roles/states, rollback works, and operators receive a controlled handoff. Beauty is valuable only when it strengthens comprehension, action safety, context, evidence, accessibility, and maintainability.
Case overlay
The new dashboard passes locally but production-like caching serves an old include and one role loses alarm drilldown. Changed-capstone condition: Stakeholders prefer a cleaner page that removes status text and diagnostic detail needed during failures.
Calculation/evidence callout: Calculate task and regression pass rates, issue severity/closure, deployment/rollback time, version coverage, and residual risk. Calculate requirement/task coverage, component reuse, state/accessibility defects, maintenance impact, accepted residual risk, and owner/due-date completeness.