Technical Trade SchoolBAS-100 foundation-series
BAS-105
Ten concept and evidence figures

BAS-105 Visual Aid Library

Figure-use rule

Each figure is an orientation and reasoning aid, not a project drawing. Learners must pair it with the current sequence, point list, wiring/piping documents, manufacturer instructions, and as-found evidence.

Figure 1 — Project lifecycle, roles, sources and document control critical

Normal-rule anchor

The newest-looking file is not necessarily approved for construction; title block, status, revision, distribution, contract hierarchy, and project authority govern.

Case overlay

A field set lacks the latest bulletin while a shop drawing contains an unapproved change.

Calculation/evidence callout: Reconcile revisions/dates/status, calculate document coverage and superseded-file risk, and list unresolved authority.

Figure 2 — Drawing conventions, sheets, views, symbols, notes and scale

Normal-rule anchor

Symbols and scale are aids; written dimensions, details, notes, revisions, and field verification control within project rules.

Case overlay

A sensor appears centered graphically, but a keyed note and dimension locate it elsewhere.

Calculation/evidence callout: Use supplied architectural/engineering scales, convert units, calculate route/area/quantity, and perform reasonableness checks.

Figure 3 — Mechanical plans, schedules, details and system flow critical

Normal-rule anchor

Mechanical drawings explain physical systems but may not fully define control sequence, point semantics, or installation responsibility.

Case overlay

A VAV schedule lists reheat but the plan tag and detail disagree on coil type.

Calculation/evidence callout: Reconcile equipment counts/tags/capacities, calculate simple flow/size/quantity from supplied data, and quantify unresolved discrepancies.

Figure 4 — Control schematics, sequences, points and state traces critical

Normal-rule anchor

A point on a list does not prove its purpose, state semantics, priority, timing, or failure behavior; sequence and equipment evidence must align.

Case overlay

The sequence requires fan proof before heating, but the point list includes only fan command.

Calculation/evidence callout: Build truth/state tables, calculate timing/setpoint/reset examples, and measure requirement-to-point/test coverage.

Figure 5 — Electrical/control diagrams, terminal plans and responsibility boundaries critical

Normal-rule anchor

A diagram shows functional intent; exact ratings, listings, installation, adopted code, and field condition require separate verification.

Case overlay

The controls drawing shows a dry contact, but the equipment diagram supplies voltage at the terminal.

Calculation/evidence callout: Calculate control load/VA, conductor/terminal counts, voltage-drop example, and interface/responsibility coverage.

Figure 6 — Network risers, topology, addresses and data paths critical

Normal-rule anchor

Lines on a riser are not proof of physical route, address assignment, required flow, device capability, or as-built state.

Case overlay

Two controllers share a device instance and the riser omits an intermediate router.

Calculation/evidence callout: Calculate address/subnet examples, device/segment counts, spare/capacity from supplied limits, and identity coverage.

Figure 7 — Submittals, product data, schedules and approved-equivalent review critical

Normal-rule anchor

Similar description, appearance, or capability does not establish an approved equivalent; all critical interfaces and authority must reconcile.

Case overlay

A replacement sensor matches range and output but lacks required enclosure rating and averaging length.

Calculation/evidence callout: Create a requirement/product coverage matrix and calculate confirmed/failed/unknown fields and material/count impacts.

Figure 8 — Point, cable, panel, device and test schedule reconciliation critical

Normal-rule anchor

Schedule totals are useful only when duplicates, spares, alternates, deleted points, and cross-references are controlled.

Case overlay

The point list has 42 points, the controller schedule has 40, and two graphic points have no field source.

Calculation/evidence callout: Calculate counts by type, controller capacity/spare, cable/terminal quantities, coverage, duplicates, and exceptions.

Figure 9 — Field verification, photos, RFIs and decision records critical

Normal-rule anchor

A field conversation or photo without identity, context, revision, and decision record is not controlled authorization.

Case overlay

Ductwork blocks the specified sensor location and the installer wants to move it without engineering review.

Calculation/evidence callout: Calculate dimensional conflict, route/quantity impact, response age, issue severity, and decision/record completeness.

Figure 10 — Redlines, as-builts, turnover and change reconciliation; Integrated document trace, conflict diagnosis and defense critical

Normal-rule anchor

A redline records what was installed; it does not itself approve a deviation or replace formal change control. Professional document literacy includes knowing when the evidence is insufficient and stopping before a silent assumption becomes installed work.

Case overlay

Ceilings close tomorrow while cable routes, terminal changes, and one device relocation remain unmarked. Changed case: A drawing, sequence, submittal, and field installation each describe a different fan-proof method.

Calculation/evidence callout: Calculate planned/installed/tested/documented counts, redline completeness, open-item age, and turnover coverage. Score source authority/coverage, reconcile quantities and timing, rank contradictions, and calculate closure/readiness before release.