BAS-206 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.
Normal-rule anchor
A neat redline on a superseded drawing is still the wrong record.
Case overlay
The field folder contains three drawing revisions and an email sketch with no approval status.
Calculation/evidence callout: Reconcile document inventory, current/superseded status, recipients, and unresolved authority.
Normal-rule anchor
Labels connect physical and digital assets; names must be stable, human-usable, and governed.
Case overlay
Two VAVs share a label and a cable tag matches neither drawing nor controller object.
Calculation/evidence callout: Calculate duplicate/missing/mismatched label rates and reconcile every required identity.
Normal-rule anchor
Color is an overlay, not proof; every color-coded item requires independent text and source verification.
Case overlay
An expansion uses a new owner legend while existing faded cables follow a prior standard.
Calculation/evidence callout: Reconcile legend versions, cable tags, product markings, endpoints, and approved exceptions.
Normal-rule anchor
A professional finding says what/where/requirement/evidence/impact, not who to blame or merely that work looks bad.
Case overlay
A reviewer dislikes routing appearance, but only some conditions conflict with actual requirements.
Calculation/evidence callout: Calculate inspected/pass/fail/deferred counts and classify objective versus preference findings.
Normal-rule anchor
A redline does not self-approve design, and a close-up without context or safe identity is weak or unsafe evidence.
Case overlay
A sensor moved and a trunk changed floors with no dimensions; the hidden-work photo captures a password label but no equipment ID.
Calculation/evidence callout: Use scale/dimensions and reconcile every change/photo to issue, owner, approval, privacy check, and final drawing.
Normal-rule anchor
Daily reports distinguish observed fact, planned work, pending decision, and approved change.
Case overlay
A route conflict stops work, but the report says only “waiting on others†and loses the technical question.
Calculation/evidence callout: Reconcile planned/completed/blocked quantities and calculate delay/decision status without unsupported blame.
Normal-rule anchor
Correction is not closure; independent verification and authorized disposition are required.
Case overlay
A label was replaced but the drawing/database mismatch and recurrence across 20 boxes were not checked.
Calculation/evidence callout: Calculate aging, recurrence, closure/reopen, and retest coverage.
Normal-rule anchor
A folder of files is not turnover until identity, version, completeness, navigation, and unresolved risk are controlled.
Case overlay
The package contains two station backups, mismatched point lists, and no index showing which is final.
Calculation/evidence callout: Calculate artifact completeness, version conflicts, unresolved items, and acceptance status.
Normal-rule anchor
Quality metrics support prevention only when definitions, denominator, sample, context, and ownership are clear.
Case overlay
Most punch items are labels, but one crew worked from a stale legend and the metric lacks installed quantity.
Calculation/evidence callout: Calculate rates with denominators, Pareto shares, aging, and before/after corrective-action evidence.
Normal-rule anchor
Professional records must be useful, honest, secure, and within authority; completeness claims require evidence.
Case overlay
The customer wants turnover today while two critical retests and one drawing conflict remain open.
Calculation/evidence callout: Reconcile all artifacts/issues/tests/approvals and calculate release readiness without averaging critical gaps.