BAS-502 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.
Secure baseline, fleet architecture, and prechange evidence
Why it matters: Speed begins with a trustworthy baseline; unknown dependencies, unsupported combinations, or unproved recovery are stop conditions.
Vocabulary and working scope
Supervisor; JACE fleet; dependencies; OEM/build; modules; licenses; services; time; DNS; certificates; users; routes; health; active jobs; backup; stop conditions.
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 supervisor sees three stations but one has different modules, another has wrong time, and no one can identify the last known-good backup.
Calculation: Reconcile versions, capacity/headroom, clock offset, backup age, certificate expiry, issue counts, and proposed change blast radius.
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?
Secure Niagara Network, TLS, certificates, users, and roles
Why it matters: A working insecure connection is a critical defect; trust, identity, authorization, availability, and emergency access must all be engineered and tested.
Vocabulary and working scope
Foxs; TLS; PKI; subject/SAN; trust; expiry; renewal; station identity; RBAC; categories; permissions; service accounts; audit; emergency access.
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 certificate replacement breaks one peer, an old service account remains active, and a shared admin credential appears in a handoff note.
Calculation: Calculate renewal lead, role coverage, privilege exceptions, session/revocation time, certificate chain dates, and permitted service paths.
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, rationalization, and flood diagnosis
Why it matters: An alarm exists only when the right condition reaches the right responsible person with context, timing, action, audit, and verified return-to-normal behavior.
Vocabulary and working scope
Alarm source; extension; class; console; recipient; schedule; acknowledgement; return to normal; suppression; shelving; flood; cascade; root event; audit.
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 single communication loss creates 800 alarms, while the actual root event is buried and after-hours routing is inactive.
Calculation: Calculate event rate, peak flood, persistence/deadband, delivery latency, nuisance percentage, and residual coverage after proposed rationalization.
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, BQL, reporting, and evidence quality
Why it matters: A query result is evidence only after scope, type, time, quality, units, expected count, representative validation, and known gaps are documented.
Vocabulary and working scope
History extension; interval; COV; capacity; rollup; archive; export; BQL; joins/relations awareness; timestamp; status; gaps; retention; report.
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 fleet energy report mixes units, hides stale values, and loses short cycling because intervals differ by station.
Calculation: Calculate sampling adequacy, storage and retention, gap percentage, time offset, rollup error, and report 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?
NEQL, BQL, BFormat, and safe query-driven work
Why it matters: Query before clicking, but never treat the result set as authorized targets until representative validation, exclusions, owners, pilot, and rollback are complete.
Vocabulary and working scope
NEQL; BQL; predicates; projections; paths; tags; relations; BFormat; context; null; type; export; result validation; dry run; target manifest.
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 BQL query returns 460 points for a batch extension change, including 14 wrong types and six customer-specific exceptions.
Calculation: Compare expected/actual counts, sample confidence, false-positive/negative rate, target coverage, exception count, and reconciliation after pilot.
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?
Tags, relations, Haystack, and semantic fleet models
Why it matters: Tags are governed data, not labels; vocabulary, relationships, scope, source, validation, version, and change ownership determine meaning.
Vocabulary and working scope
Tag dictionary; namespace; site; equipment; point; ref; relation; hierarchy; Haystack; semantic query; validation; orphan; collision; provenance.
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 campuses use the same tag spelling differently and a query silently omits VAVs with an older template.
Calculation: Calculate required/actual tag coverage, orphan and collision counts, query precision/recall, 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?
Templates, PX reuse, navigation, and operator-state truth
Why it matters: Reuse is safe only when its interface contract and state matrix are explicit and regression-tested on representative variants.
Vocabulary and working scope
Template; prototype; relative ORD; PxInclude; nav; hierarchy; widget; binding; command/proof; writable action; alarm/history link; accessibility; 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 fleet VAV template works on ten boxes but writes to the wrong priority on two older controllers and hides stale airflow.
Calculation: Measure binding/interface coverage, variant pass rate, task steps/errors, state coverage, and changed-case regression results.
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 operations, tuning, and write semantics
Why it matters: A batch operation combines target selection, authorization, timing, resource impact, write semantics, process consequence, exceptions, and restoration; success count alone is insufficient.
Vocabulary and working scope
Provisioning job; target set; platform/station action; driver tuning; poll scheduler; COV; max write; startup write; stale behavior; queue; pilot; stop rule.
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 tuning-policy change reduces traffic but causes startup output blips on legacy controllers after a power event.
Calculation: Calculate target count, job duration, poll/write load, queue growth, exception rate, response latency, and before/after resource margin.
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, performance, and root-cause diagnosis
Why it matters: Read the complete exception chain and correlate time, component, service, resource, physical symptom, and changed case before concluding cause.
Vocabulary and working scope
Station output; stack trace; exception chain; jobs; thread/queue; CPU; heap; storage; GC awareness; driver health; network errors; down/stale; symptom 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 station becomes slow after a graphics release; output shows repeated binding exceptions, a full history queue, and intermittent driver timeouts.
Calculation: Calculate event rate, resource trend, queue growth, error concentration, response latency, and whether timing supports the proposed causal chain.
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 change, recovery, optimization, and professional defense
Why it matters: The professional result is a reproducible evidence package: what changed, why, where, under whose authority, what was tested, what failed, how recovery was proved, and what remains open.
Vocabulary and working scope
Change request; diff; review; manifest; checksum; release window; backup; abort; rollback; clean restore; functional proof; monitoring; handoff; unresolved risk.
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 fleet optimization passes initial checks, then one station fails after reboot and another retains a temporary command.
Calculation: Reconcile planned/applied/failed/rolled-back targets, checksum and version state, RPO/RTO, functional pass rate, temporary-state count, and open risk ownership.
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 Niagara Framework current product route
Current product and release context; exact OEM distribution, supported build, module, license, and SMA status still control the lab. - Tridium University certification catalog
Current Level 1, Level 2, and Level 3 competency context; TTS prepares and extends skills but does not claim to issue Tridium certification. - WEBs-N4 Overview
Engineering-library platform architecture and workflow source; verify every procedure against the designated supported lab build. - Niagara Workbench Guide-LITE
Workbench views, component model, navigation, points, histories, alarms, schedules, and station workflow. - Niagara Graphics Guide and Curriculum
PX/Hx/graphics, bindings, reusable presentation, state truth, and operator-task design. - ANSI/ASHRAE Standard 135-2024 scope route
Current published BACnet standard scope and edition route; adopted project edition and addenda govern. - ASHRAE Guideline 13-2024
BAS architecture, hardware, communications, programming, testing, documentation, cybersecurity, and legacy-system framework. - NIST SP 800-82 Rev. 3
Current OT security guidance for accounts, segmentation, remote access, monitoring, change, and recovery.