BOOT-N4 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.
Fleet intake, exact build, modules, licenses and recoverability
Why it matters: Niagara procedures and artifacts are distribution/build/module dependent; source, deployed, backup, and supported state must be distinguished.
Vocabulary and working scope
OEM distribution; N4 build; modules/versions; licenses; host/JVM/OS; drivers; dependencies; station state; backups; manifests; scope; authority; stop criteria.
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 stations report the same version label but have different module sets and one backup cannot start in the recovery lab.
Calculation: Calculate version/dependency coverage, backup age, restore success/time, resource margin, and unsupported-condition count.
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?
Platform/station identity, time, users, roles, certificates and Fox trust
Why it matters: Connectivity does not justify accepting unknown certificates, disabling validation, sharing credentials, or broadening roles.
Vocabulary and working scope
Host/platform/station identity; DNS/IP/time; users/roles; service accounts; certificates; trust stores; Fox/secure services; expiry; least privilege; audit; revocation; 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
A station reconnects only when trust checks are disabled; its clock is wrong and the replacement certificate identity changed.
Calculation: Calculate clock skew, certificate/renewal window, role/permission coverage, failed-login rate, and trust-path 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?
Alarm pipeline, routing, actionability and flood control
Why it matters: Alarm reduction requires rationalization and cause correction; suppression is temporary controlled state, not proof of resolution.
Vocabulary and working scope
Alarm source; class; extension; state; inhibit/suppress/shelve; ack; routing; recipient; escalation; timestamps; root/cascade; flood; audit; restoration.
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
One failed sensor produces 300 downstream alarms while an important fan-proof alarm never reaches the operator.
Calculation: Calculate alarm rate, top contributors, standing/stale counts, actionability, routing coverage, flood reduction, and suppression 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?
Histories, sampling, COV, timestamps, retention and evidence questions
Why it matters: More samples are not automatically better evidence; process dynamics, question, storage, quality, and clock alignment govern.
Vocabulary and working scope
History extension; interval/COV; deadband; capacity; rollup; time zones/DST; quality; gaps/duplicates; exports; retention; question; event correlation.
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 five-minute trend misses short cycling, while a faster trend doubles storage and repeats samples after time correction.
Calculation: Calculate sample interval, storage/retention, gap/duplicate percentage, clock offset, cycle frequency, and detection limits.
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?
BQL and NEQL question design, scope and validation
Why it matters: A syntactically valid query can be operationally wrong through scope, semantics, missing data, type conversion, or hidden exclusions.
Vocabulary and working scope
Query question; scope/root; BQL; NEQL; object/type/tag/property filters; columns; null/type; pagination; false positives/negatives; target manifest; safe bulk preparation.
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 query identifies 180 points for change but omits disabled stations and includes test equipment.
Calculation: Calculate expected/returned/verified counts, precision/recall on a sample, null/type rates, and target-manifest reconciliation.
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?
BFormat, tags, relations and governed semantic reuse
Why it matters: Names and tags are data contracts; cosmetic consistency is insufficient when relations, types, context, or consumers break.
Vocabulary and working scope
BFormat context; slots/properties; tags; relations; Haystack awareness; dictionaries; equipment/point context; naming; null/type; duplicates; governance; migration; consumers.
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 reusable VAV page works on one station and binds to the wrong discharge temperature on another because context relations differ.
Calculation: Calculate semantic coverage, orphan/duplicate rates, template binding success, exception rate, and migration 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?
PX, templates, navigation and operator task truth
Why it matters: A graphic is not correct because it renders; target context, data state, authority, action result, physical proof, and recovery must be visible.
Vocabulary and working scope
PX/PxInclude; ORD/binding; relative context; reusable template; nav; hierarchy; states; actions; permissions; command/proof; responsive/accessibility; latency; source 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 floor page opens the wrong equipment after navigation and shows an override as normal for one role.
Calculation: Calculate task success/time, binding/state coverage, command/proof latency, accessibility defects, and reuse exception 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?
Provisioning, batch work, driver tuning and job reconciliation
Why it matters: Bulk work multiplies both benefit and error; a completed job status does not prove every target, function, restart, or restore.
Vocabulary and working scope
Provisioning job; target manifest; preflight; backup; batch; pilot; stop threshold; module/install/service actions; driver poll/write/COV; job output; exceptions; retry; rollback.
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 batch upgrade succeeds on 18 of 20 stations, one is offline, and one restarts with a driver disabled.
Calculation: Calculate target/pilot/success/exception rates, duration, bandwidth/load, resource margin, retry/rollback, and final version 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?
Station output, exceptions, drivers, networks and performance
Why it matters: The last exception line, high CPU, or offline point is a symptom until context, timing, scope, and alternatives are tested.
Vocabulary and working scope
Station output; exception chain; thread/CPU/heap/resource awareness; driver status; queue; polling; retries; network latency/loss; blocked services; timestamps; baseline; correlation.
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
Graphics freeze every hour while CPU is moderate; station output shows queue growth after a scheduled export.
Calculation: Calculate baseline versus incident latency/load, error and retry rates, queue growth, resource headroom, and test discrimination.
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?
Fleet hardening, change control, optimization and regression; Failed-station restore, critical-function proof and fleet defense
Why it matters: 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.
Vocabulary and working scope
Supported hardening; services/ports; roles; certificates; password/service-account policy; backups; change request; artifact/version control; performance target; regression; monitoring; expiry. Clean recovery environment; platform/station dependencies; licenses/certificates; backup; restore; identity; network; drivers; alarms/histories/PX; critical sequence; as-left; handoff.
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
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: 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.
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.