BOOT-NIA Reading Guide
How to use this reading guide
This is the concept-review layer for a 100% online course. Read each module before its lesson, complete the retrieval prompts without looking, then use the linked authoritative sources to verify project-specific editions, requirements, and manufacturer procedures.
Online evidence is not OJL: browser simulations, document cases, and isolated remote equipment build reasoning and documentation skill; supervised field performance is recorded separately.
Operator roles, tasks, consequences and evidence needs
Why it matters: Interfaces exist to support safe decisions and actions; screen inventories and visual preference are secondary to consequential tasks.
Vocabulary and working scope
Operator/technician/manager roles; goals; decisions; frequency; consequence; normal/abnormal; authority; source drilldown; completion evidence; recovery.
Source-to-result trace
- Locate the controlling requirement and establish authority.
- Identify the physical and digital boundaries.
- Preserve as-found state and timestamps.
- Trace the initiating condition through logic, interfaces, equipment, and process response.
- Compare expected and actual evidence.
- Calculate with units and stated tolerance.
- Record action, result, restoration, uncertainty, and owner.
Worked thinking prompt
An operator must identify why a zone is hot, but the dashboard shows scores without source state, time, or drilldown.
Calculation: Calculate task frequency/consequence priority, required evidence coverage, decision time, and unresolved task risk.
Retrieval prompts
- What would normal look like in this mode?
- Which two independent observations would strengthen the conclusion?
- What result would disprove the leading hypothesis?
- Which action requires authorization or a qualified person?
- What must be restored and documented?
Information architecture, page context and navigation
Why it matters: A page that is easy to reach but loses building, equipment, role, or time context can produce a fast wrong action.
Vocabulary and working scope
Portfolio/site/building/floor/equipment hierarchy; context; breadcrumbs; nav files; links; back path; role landing; search/filter; responsive regions; deep links; source context.
Source-to-result trace
- Locate the controlling requirement and establish authority.
- Identify the physical and digital boundaries.
- Preserve as-found state and timestamps.
- Trace the initiating condition through logic, interfaces, equipment, and process response.
- Compare expected and actual evidence.
- Calculate with units and stated tolerance.
- Record action, result, restoration, uncertainty, and owner.
Worked thinking prompt
Two AHUs share similar names and a floor link opens the same relative page against the wrong station context.
Calculation: Calculate path depth/clicks, wrong-context rate, task time, orphan/dead-end links, and responsive coverage.
Retrieval prompts
- What would normal look like in this mode?
- Which two independent observations would strengthen the conclusion?
- What result would disprove the leading hypothesis?
- Which action requires authorization or a qualified person?
- What must be restored and documented?
Widgets, assets, values, units, precision and failure presentation
Why it matters: Every visual element needs a task purpose and complete data-state behavior; image ownership and accessibility are design requirements.
Vocabulary and working scope
Widget purpose; value/state; unit; precision; symbol; color/noncolor cue; licensed/original asset; chart/table; loading/null/down/stale; annotation; source.
Source-to-result trace
- Locate the controlling requirement and establish authority.
- Identify the physical and digital boundaries.
- Preserve as-found state and timestamps.
- Trace the initiating condition through logic, interfaces, equipment, and process response.
- Compare expected and actual evidence.
- Calculate with units and stated tolerance.
- Record action, result, restoration, uncertainty, and owner.
Worked thinking prompt
A gauge shows 72.000 degrees with no unit while a missing point renders as zero and a copied icon has unknown rights.
Calculation: Calculate precision from sensor/process need, chart scale, asset/license coverage, state coverage, and clutter/task ratio.
Retrieval prompts
- What would normal look like in this mode?
- Which two independent observations would strengthen the conclusion?
- What result would disprove the leading hypothesis?
- Which action requires authorization or a qualified person?
- What must be restored and documented?
ORDs, bindings, context and complete state matrices
Why it matters: A binding that works in normal state is incomplete until identity, quality, time, failure, override, and changed context are visible.
Vocabulary and working scope
ORD; slot/property; relative binding; target context; conversion; units; status; timestamp; null; down; stale; fault; disabled; override; alarm; loading; fallback; drilldown.
Source-to-result trace
- Locate the controlling requirement and establish authority.
- Identify the physical and digital boundaries.
- Preserve as-found state and timestamps.
- Trace the initiating condition through logic, interfaces, equipment, and process response.
- Compare expected and actual evidence.
- Calculate with units and stated tolerance.
- Record action, result, restoration, uncertainty, and owner.
Worked thinking prompt
A temperature tile binds correctly on AHU-1, converts units twice on AHU-2, and shows stale data as normal.
Calculation: Calculate binding/state coverage, value/unit error, stale threshold, exception count, and two-instance reuse pass rate.
Retrieval prompts
- What would normal look like in this mode?
- Which two independent observations would strengthen the conclusion?
- What result would disprove the leading hypothesis?
- Which action requires authorization or a qualified person?
- What must be restored and documented?
Safe actions, roles, priorities, confirmation, proof and recovery
Why it matters: A button click or successful write is not successful equipment operation, and the interface must not imply otherwise.
Vocabulary and working scope
Writable action; role/permission; value limits; priority; confirmation; reason; accepted/denied; command/proof; timeout; release; audit; undo/recovery; safety boundary.
Source-to-result trace
- Locate the controlling requirement and establish authority.
- Identify the physical and digital boundaries.
- Preserve as-found state and timestamps.
- Trace the initiating condition through logic, interfaces, equipment, and process response.
- Compare expected and actual evidence.
- Calculate with units and stated tolerance.
- Record action, result, restoration, uncertainty, and owner.
Worked thinking prompt
A fan command displays success for a viewer role while a higher priority prevents operation and no timeout appears.
Calculation: Calculate bounds, effective priority, command/proof error and timeout, denial coverage, audit completeness, and temporary-state closure.
Retrieval prompts
- What would normal look like in this mode?
- Which two independent observations would strengthen the conclusion?
- What result would disprove the leading hypothesis?
- Which action requires authorization or a qualified person?
- What must be restored and documented?
Reusable PxInclude/templates, variants and regression
Why it matters: Reuse is a governed contract, not copy/paste; every variant and failure state must remain truthful.
Vocabulary and working scope
PxInclude/template; relative context; component contract; required/optional points; variants; missing data; naming/tags; version; consumer pages; change impact; regression.
Source-to-result trace
- Locate the controlling requirement and establish authority.
- Identify the physical and digital boundaries.
- Preserve as-found state and timestamps.
- Trace the initiating condition through logic, interfaces, equipment, and process response.
- Compare expected and actual evidence.
- Calculate with units and stated tolerance.
- Record action, result, restoration, uncertainty, and owner.
Worked thinking prompt
A VAV template works until a fan-powered box lacks discharge temperature and an older page expects a renamed slot.
Calculation: Calculate required/optional contract coverage, exception rate, regression scope/pass rate, and maintenance reduction.
Retrieval prompts
- What would normal look like in this mode?
- Which two independent observations would strengthen the conclusion?
- What result would disprove the leading hypothesis?
- Which action requires authorization or a qualified person?
- What must be restored and documented?
Semantic navigation, hierarchies, filters and source drilldown
Why it matters: Semantic automation inherits data-quality defects; generated navigation requires validation and governed exceptions.
Vocabulary and working scope
Tags/relations; equipment/point context; hierarchy; nav generation; filters; floor/portfolio views; semantic query; ambiguous/missing tags; source link; governance.
Source-to-result trace
- Locate the controlling requirement and establish authority.
- Identify the physical and digital boundaries.
- Preserve as-found state and timestamps.
- Trace the initiating condition through logic, interfaces, equipment, and process response.
- Compare expected and actual evidence.
- Calculate with units and stated tolerance.
- Record action, result, restoration, uncertainty, and owner.
Worked thinking prompt
A filter excludes untagged critical equipment and groups two pumps under the wrong plant relation.
Calculation: Calculate semantic coverage, orphan/duplicate/ambiguous rates, filter precision/recall on a sample, and remediation backlog.
Retrieval prompts
- What would normal look like in this mode?
- Which two independent observations would strengthen the conclusion?
- What result would disprove the leading hypothesis?
- Which action requires authorization or a qualified person?
- What must be restored and documented?
Alarms, trends, schedules, calendars and audit in task context
Why it matters: Alarm, trend, and schedule widgets are useful only when identity, quality, time, lifecycle, authority, and source context are preserved.
Vocabulary and working scope
Alarm state/priority/source/ack; trend value/quality/time; schedule/calendar/current/next event; audit; drilldown; comparison; operator notes; timezone/DST; export.
Source-to-result trace
- Locate the controlling requirement and establish authority.
- Identify the physical and digital boundaries.
- Preserve as-found state and timestamps.
- Trace the initiating condition through logic, interfaces, equipment, and process response.
- Compare expected and actual evidence.
- Calculate with units and stated tolerance.
- Record action, result, restoration, uncertainty, and owner.
Worked thinking prompt
A comfort complaint page hides an active schedule exception and trends use a different timezone than alarm timestamps.
Calculation: Calculate time offset, sample adequacy, alarm/task coverage, schedule precedence, and evidence retrieval time.
Retrieval prompts
- What would normal look like in this mode?
- Which two independent observations would strengthen the conclusion?
- What result would disprove the leading hypothesis?
- Which action requires authorization or a qualified person?
- What must be restored and documented?
Accessibility, keyboard, responsive, latency and role testing
Why it matters: Accessibility is operational quality: an action or state unavailable without a mouse, color vision, perfect sight, or fast network is a functional defect.
Vocabulary and working scope
Keyboard order/focus; visible focus; labels; headings; landmarks; contrast; noncolor meaning; zoom/text scale; screen reader names; responsive layouts; touch targets; loading/latency; role views.
Source-to-result trace
- Locate the controlling requirement and establish authority.
- Identify the physical and digital boundaries.
- Preserve as-found state and timestamps.
- Trace the initiating condition through logic, interfaces, equipment, and process response.
- Compare expected and actual evidence.
- Calculate with units and stated tolerance.
- Record action, result, restoration, uncertainty, and owner.
Worked thinking prompt
The alarm table is unreadable at 200% zoom, keyboard focus disappears, and a mobile action button covers proof state.
Calculation: Calculate contrast from approved tools, task success/time/error by mode, breakpoint/state coverage, and latency percentiles.
Retrieval prompts
- What would normal look like in this mode?
- Which two independent observations would strengthen the conclusion?
- What result would disprove the leading hypothesis?
- Which action requires authorization or a qualified person?
- What must be restored and documented?
Integrated operator workflow, deployment, rollback and handoff; UX capstone defense and maintainable design governance
Why it matters: 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.
Vocabulary and working scope
Five tasks; normal/failure/changed cases; versions; backup; target; deployment window; smoke/regression; permissions; rollback; cache/session; issue/retest; training; as-left. Design rationale; task evidence; style tokens; component contracts; asset rights; accessibility; state/action matrix; test results; change process; ownership; backlog; limitations.
Source-to-result trace
- Locate the controlling requirement and establish authority.
- Identify the physical and digital boundaries.
- Preserve as-found state and timestamps.
- Trace the initiating condition through logic, interfaces, equipment, and process response.
- Compare expected and actual evidence.
- Calculate with units and stated tolerance.
- Record action, result, restoration, uncertainty, and owner.
Worked thinking prompt
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: 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.
Retrieval prompts
- What would normal look like in this mode?
- Which two independent observations would strengthen the conclusion?
- What result would disprove the leading hypothesis?
- Which action requires authorization or a qualified person?
- What must be restored and documented?
Required and deeper reading
- Tridium University and Niagara certification route
Current training/course route; exact OEM distribution, build, modules, license, and support policy govern the lab and real sites. - ASHRAE Standard 135 official scope and current-edition route
Confirm the current standard, addenda, interpretations, adopted/project requirements, and product implementation before making a compliance claim. - ASHRAE Guideline 13-2024
BAS specification, installation, integration, testing, documentation, cybersecurity, and lifecycle context. - NIST SP 800-82 Rev. 3
OT governance, architecture, access, monitoring, incident response, backup, recovery, and compensating-control guidance.