Technical Trade SchoolBAS-400 developer-series
BAS-403
Concept reading and source route

BAS-403 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.

Module 1

Information-model purpose, users, and identity

Why it matters: A name is a label; identity and meaning require stable keys, context, units, relationships, quality, and governance.

Vocabulary and working scope

Asset; entity; point; object; signal; observation; command; metadata; semantic model; identity; alias; source of truth; consumer; lifecycle; ownership.

Source-to-result trace

  1. Locate the controlling requirement and establish authority.
  2. Identify the physical and digital boundaries.
  3. Preserve as-found state and timestamps.
  4. Trace the initiating condition through logic, interfaces, equipment, and process response.
  5. Compare expected and actual evidence.
  6. Calculate with units and stated tolerance.
  7. Record action, result, restoration, uncertainty, and owner.

Worked thinking prompt

Three front-end paths use different names for the same discharge-air sensor, while two identical labels refer to different physical sensors.

Calculation: Reconcile source records to unique physical and digital identities; duplicates, aliases, orphans, and unresolved collisions must be counted.

Retrieval prompts

Module 2

Naming conventions, dictionaries, and revision control

Why it matters: A convention must define grammar and governance, not merely provide examples; abbreviations and exceptions belong in a controlled dictionary.

Vocabulary and working scope

Site; building; floor; area; system; equipment; point; type; qualifier; delimiter; length; reserved character; abbreviation; uniqueness; human-readable label; machine key; revision.

Source-to-result trace

  1. Locate the controlling requirement and establish authority.
  2. Identify the physical and digital boundaries.
  3. Preserve as-found state and timestamps.
  4. Trace the initiating condition through logic, interfaces, equipment, and process response.
  5. Compare expected and actual evidence.
  6. Calculate with units and stated tolerance.
  7. Record action, result, restoration, uncertainty, and owner.

Worked thinking prompt

A controller limits object names to sixteen characters while the enterprise standard requires readable multi-building uniqueness.

Calculation: Calculate maximum lengths, collision counts, abbreviation coverage, and migration impact across supplied target constraints.

Retrieval prompts

Module 3

Point metadata, units, ranges, facets, and quality

Why it matters: A numeric value without units, range, timestamp, quality, and source can be plausible and still be unsafe or meaningless.

Vocabulary and working scope

Display name; description; units; precision; min/max; normal range; sensor range; commandability; writable; enum; state text; reliability; quality; timestamp; source; sample method.

Source-to-result trace

  1. Locate the controlling requirement and establish authority.
  2. Identify the physical and digital boundaries.
  3. Preserve as-found state and timestamps.
  4. Trace the initiating condition through logic, interfaces, equipment, and process response.
  5. Compare expected and actual evidence.
  6. Calculate with units and stated tolerance.
  7. Record action, result, restoration, uncertainty, and owner.

Worked thinking prompt

A temperature point displays 72.0 with no unit, a 0-10 V raw range, and a stale quality flag hidden by the graphic.

Calculation: Verify engineering-unit conversion, range, precision, age, and plausibility; count missing or conflicting required facets.

Retrieval prompts

Module 4

Equipment, location, and relationship hierarchy

Why it matters: Containment, service, flow, and control are different relationships; forcing them into one folder tree destroys meaning.

Vocabulary and working scope

Site; building; floor; space; zone; system; equipment; subsystem; point; contains; serves; feeds; hasPart; controlledBy; measuredBy; locatedIn; upstream/downstream.

Source-to-result trace

  1. Locate the controlling requirement and establish authority.
  2. Identify the physical and digital boundaries.
  3. Preserve as-found state and timestamps.
  4. Trace the initiating condition through logic, interfaces, equipment, and process response.
  5. Compare expected and actual evidence.
  6. Calculate with units and stated tolerance.
  7. Record action, result, restoration, uncertainty, and owner.

Worked thinking prompt

A VAV controller is physically in a ceiling, belongs to an air system, serves a zone, and is commanded by a central schedule.

Calculation: Test graph completeness with counts and queries for orphan points, equipment without spaces, zones without serving equipment, and broken upstream/downstream paths.

Retrieval prompts

Module 5

Project Haystack tags and references

Why it matters: Tags describe meaning in combinations; adding many tags without a controlled convention can create contradictory or nonportable models.

Vocabulary and working scope

Marker tag; value tag; reference tag; entity; dict; id; ref; site; equip; point; sensor; cmd; setpoint; air; water; zone; ahu; vav; relationship; query/filter.

Source-to-result trace

  1. Locate the controlling requirement and establish authority.
  2. Identify the physical and digital boundaries.
  3. Preserve as-found state and timestamps.
  4. Trace the initiating condition through logic, interfaces, equipment, and process response.
  5. Compare expected and actual evidence.
  6. Calculate with units and stated tolerance.
  7. Record action, result, restoration, uncertainty, and owner.

Worked thinking prompt

Legacy VAV points contain names but no equipment references, and airflow values mix sensor, setpoint, and command meanings.

Calculation: Calculate tagging coverage, valid-reference rate, query precision/recall on the supplied answer set, and exception count.

Retrieval prompts

Module 6

Brick entities, classes, relationships, and validation

Why it matters: Ontology modeling separates what an entity is from how it relates; a valid label does not compensate for a wrong class or missing relationship.

Vocabulary and working scope

Ontology; class; instance; equipment; point; location; system; feeds; hasPoint; isPointOf; hasPart; isPartOf; SHACL/constraint awareness; inference; query.

Source-to-result trace

  1. Locate the controlling requirement and establish authority.
  2. Identify the physical and digital boundaries.
  3. Preserve as-found state and timestamps.
  4. Trace the initiating condition through logic, interfaces, equipment, and process response.
  5. Compare expected and actual evidence.
  6. Calculate with units and stated tolerance.
  7. Record action, result, restoration, uncertainty, and owner.

Worked thinking prompt

An AHU discharge sensor is modeled as a generic temperature point with no equipment or location relationship.

Calculation: Count validation violations, classify missing versus conflicting relationships, and test required competency queries against expected results.

Retrieval prompts

Module 7

BACnet object identity and semantic crosswalk

Why it matters: BACnet object name is not a globally unique enterprise identity; network/device/object context and mapping provenance must be preserved.

Vocabulary and working scope

Device instance; network; MAC; object type; object instance; object name; description; present value; units; status flags; reliability; priority array; profile; vendor identifier; semantic alias.

Source-to-result trace

  1. Locate the controlling requirement and establish authority.
  2. Identify the physical and digital boundaries.
  3. Preserve as-found state and timestamps.
  4. Trace the initiating condition through logic, interfaces, equipment, and process response.
  5. Compare expected and actual evidence.
  6. Calculate with units and stated tolerance.
  7. Record action, result, restoration, uncertainty, and owner.

Worked thinking prompt

Two vendor devices expose identical object names and one gateway changes engineering units during mapping.

Calculation: Construct unique keys, verify object counts, reconcile units/enumerations, and identify duplicate, missing, or unstable identifiers.

Retrieval prompts

Module 8

Templates, normalization, import, and mapping

Why it matters: Bulk automation multiplies both good rules and bad assumptions; import requires validation before and after every controlled batch.

Vocabulary and working scope

Source schema; target schema; transform; lookup; normalization; default; exception; bulk import; dry run; idempotence; dependency; collision; rollback; report.

Source-to-result trace

  1. Locate the controlling requirement and establish authority.
  2. Identify the physical and digital boundaries.
  3. Preserve as-found state and timestamps.
  4. Trace the initiating condition through logic, interfaces, equipment, and process response.
  5. Compare expected and actual evidence.
  6. Calculate with units and stated tolerance.
  7. Record action, result, restoration, uncertainty, and owner.

Worked thinking prompt

A CSV import would rename 4,000 points, assign units by suffix, and overwrite existing descriptions.

Calculation: Calculate match, exception, collision, overwrite, and rollback counts; verify idempotence on a second dry run.

Retrieval prompts

Module 9

Data quality, time, scaling, status, and lineage

Why it matters: Data quality is use-specific; a value acceptable for an operator overview may be inadequate for control, fault detection, billing, or compliance.

Vocabulary and working scope

Accuracy; resolution; precision; completeness; validity; timeliness; consistency; availability; timestamp; clock offset; stale; COV; interpolation; scaling; unit transform; provenance; lineage.

Source-to-result trace

  1. Locate the controlling requirement and establish authority.
  2. Identify the physical and digital boundaries.
  3. Preserve as-found state and timestamps.
  4. Trace the initiating condition through logic, interfaces, equipment, and process response.
  5. Compare expected and actual evidence.
  6. Calculate with units and stated tolerance.
  7. Record action, result, restoration, uncertainty, and owner.

Worked thinking prompt

A historian resamples five-minute COV data into one-minute values and an analytics rule treats interpolated values as direct measurements.

Calculation: Calculate age, completeness, clock offset, unit/scaling error, interpolation share, and quality-rule pass rate.

Retrieval prompts

Module 10

Governance, validation queries, migration, and handoff

Why it matters: Semantic work is configuration management: every change can affect graphics, trends, alarms, analytics, integrations, and human search.

Vocabulary and working scope

Data owner; steward; change request; controlled vocabulary; approval; validation rule; regression query; exception; migration; deprecation; alias; audit; revision; consumer notification.

Source-to-result trace

  1. Locate the controlling requirement and establish authority.
  2. Identify the physical and digital boundaries.
  3. Preserve as-found state and timestamps.
  4. Trace the initiating condition through logic, interfaces, equipment, and process response.
  5. Compare expected and actual evidence.
  6. Calculate with units and stated tolerance.
  7. Record action, result, restoration, uncertainty, and owner.

Worked thinking prompt

A naming cleanup improves consistency but breaks saved reports and external API consumers that rely on legacy paths.

Calculation: Reconcile affected consumers, validation results, migrated/deferred/failed entities, aliases, and open exceptions before release.

Retrieval prompts

Required and deeper reading

Adoption note: Standards, codes, project requirements, owner criteria, manufacturer instructions, and employer safety programs control. Confirm the adopted edition and authority before applying a numeric requirement.