BAS-501 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.
Niagara ecosystem, roles, and mental map
Why it matters: Platform administration, station engineering, driver integration, and operator use are different contexts; the visible tree never proves the physical process by itself.
Vocabulary and working scope
Workbench; platform; station; JACE; supervisor; daemon; Fox; Niagara Network; driver network; module; license; SMA; OEM distribution; device-to-enterprise path.
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 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: Create a dependency matrix and count every required component, service, license, interface, evidence source, and unresolved owner.
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?
Supported build, installation, home, daemon, license, and modules
Why it matters: A version number alone is not compatibility evidence; OEM distribution, exact build, modules, dependencies, license, host platform, and support policy travel together.
Vocabulary and working scope
Niagara home; Workbench build; Java/runtime; daemon; distribution file; module JAR; dependency; license; certificate; compatibility; upgrade path; 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
Workbench opens an older station, but two modules are missing and a license feature is unavailable after copying it to a new laptop.
Calculation: Reconcile required versus installed versions, dependencies, feature counts, capacity, expiration dates, storage margin, and rollback prerequisites.
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 connection, commissioning, network, time, and backup
Why it matters: Commissioning changes the computer beneath the station; it requires an impact plan, known-good backup, exact target, protected credentials, abort criteria, and functional postchecks.
Vocabulary and working scope
Platform credentials; host identity; TCP/IP; DNS; NTP; route; commissioning wizard; distribution; station install; passphrase; backup; reboot; service state.
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 JACE is reachable on a bench address but has wrong time, stale certificates, an unknown station copy, and no tested backup.
Calculation: Calculate addressing, storage/headroom, elapsed outage, backup age, time offset, and recovery objective; compare each to the supplied criterion.
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 components, points, facets, status, priority, and physical truth
Why it matters: 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.
Vocabulary and working scope
Config; Drivers; Services; component/type/slot/property/action/topic; ORD; views; links; control point; numeric/binary/enum; facets; status; reliability; priority array; fallback; proxy extension; command; proof.
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 points share a display name, a graphic binds to the wrong proxy path, priority 8 remains active, and fan proof is off.
Calculation: Resolve path and dependencies, convert raw values, reconcile priorities/fallback, and calculate deviation, freshness, proof timeout, and rename/move 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?
Histories, alarms, schedules, and operational evidence
Why it matters: Trends, alarms, and schedules are operational programs with source, time, quality, ownership, retention, test, and restoration requirements.
Vocabulary and working scope
History extension; interval; COV; capacity; rollup; alarm source; class; recipient; acknowledge; schedule; calendar; special event; temporary override; 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 zone complaint is hidden by a coarse interval, alarm routing is outside the active window, and a holiday exception outranks the weekly schedule.
Calculation: Calculate sample coverage, storage, time alignment, persistence/deadband, schedule overlap, and override expiry with units and acceptance bounds.
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?
BACnet discovery, devices, points, and MS/TP/IP integration
Why it matters: Discovery proves a response, not correctness, ownership, writable authority, units, or physical effect; read before write and preserve all temporary state.
Vocabulary and working scope
BACnet/IP; MS/TP; network number; device instance; MAC; baud; BBMD/FDR awareness; discovery; learn; proxy; object/property; PICS; priority; polling/COV.
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 device appears twice through two routes, point units disagree with the submittal, and a write succeeds without equipment response.
Calculation: Reconcile network/device uniqueness, poll and COV load, token timing, value scaling, and command-to-proof response.
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?
Niagara Network, Fox, users, roles, and certificates
Why it matters: Connectivity restored by disabling trust, sharing an account, or granting broad permissions is a failed repair.
Vocabulary and working scope
Niagara Network; Fox/Foxs; station identity; peer link; virtuals; users; roles; permissions; categories; TLS; trust store; certificate expiry; audit; remote session.
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 cannot connect after a certificate renewal, and an operator role can reach a platform action it should not use.
Calculation: Calculate certificate lead time, account/role coverage, permission exceptions, session duration, and route/service exposure against policy.
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?
Wiresheets, logic, templates, and reusable engineering
Why it matters: Reusable engineering makes variation explicit and carries requirements, units, failure behavior, test cases, version, and rollback with the template.
Vocabulary and working scope
Wiresheet; links; kitControl; Boolean; numeric; timers; latches; PID; state; program service; palette; template; relative binding; naming; revision; test vector.
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 copied VAV template contains absolute links, a retained override, and a timer that behaves differently after restart.
Calculation: Build truth/state tables, calculate scaling and timing, check template coverage, and compare expected and actual values over multiple scans.
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/Hx graphics, bindings, navigation, and operator task truth
Why it matters: 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.
Vocabulary and working scope
PX; Hx; browser; widget; binding; relative ORD; nav file; hierarchy; writable control; command/proof; alarm/trend/schedule link; stale/null state; accessibility.
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 animates from command, a missing temperature displays zero, and a copied page operates the wrong VAV.
Calculation: Measure top-task steps/time/errors, binding coverage, missing-state handling, and action-to-proof timeout against acceptance criteria.
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?
Backup, restore, station copy, troubleshooting, and certification practical
Why it matters: 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.
Vocabulary and working scope
Station backup; system backup; export; dependencies; checksum; clean restore; station output; jobs; logs; faults; down/stale; compare; rollback; 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
A power event leaves one station down, time wrong, histories stopped, and a replacement controller available but unproved.
Calculation: Compute RPO, RTO, backup age, restore duration, unresolved count, function pass rate, and evidence completeness with reasonableness checks.
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 4 Install and Startup Guide
Platform, daemon, installation, commissioning, station, backup, and startup concepts. - Niagara Workbench Guide-LITE
Workbench views, component model, navigation, points, histories, alarms, schedules, and station workflow. - Working with BACnet
Engineering-library reference for objects, properties, services, networks, and evidence-driven troubleshooting. - NIST SP 800-82 Rev. 3
Current OT security guidance for accounts, segmentation, remote access, monitoring, change, and recovery.