15.7 Commercial Prints, Equipment Schedules, and BAS Documentation

15.7 Commercial Prints, Equipment Schedules, and BAS Documentation

The Building Automation sheet of the Competency and Task List names these competencies:

• Reading and interpreting commercial building prints — lighting, electrical, mechanical, plumbing, and HVACR
• Reading and interpreting commercial building schedules located on prints
• Creating flow charts to illustrate the operational sequence of VAV, AHU, cooling towers, rooftop units, etc.
• Creating and maintaining documentation related to a BAS install — to include hardware components and address schema
• Creating network diagrams

The prior-knowledge block on the same sheet adds converting schematic diagrams to ladder diagrams, NEC usage, ampacity calculations, and voltage-drop calculations — all of which are read off, or checked against, the drawings.

Residential service work runs on a unit wiring diagram and a nameplate. Commercial and light-commercial work runs on a drawing set, and a technician who cannot navigate one cannot commission a building.

---

1. How a Commercial Drawing Set Is Organized

Sheets carry a discipline prefix followed by a number. The prefixes are near-universal:

Read M and E together. A rooftop unit appears on the M sheets with its airflow and capacity, and on the E sheets with its circuit, disconnect, and overcurrent protection. The MCA and MOCP on the unit's data plate (Section 1.7) must agree with what the E sheets provide. Discovering at start-up that a 60 A unit is on a 40 A circuit is a drawing-coordination failure that was visible on paper months earlier.

Every sheet also carries:

• A title block — project, sheet name and number, date, and the design professional's seal
• A scale and often a graphic scale bar. Never scale a drawing for a dimension that is written elsewhere; prints get reproduced at the wrong size.
• A north arrow on plan views
• Revision deltas and clouds — a numbered triangle beside a clouded area marks what changed and when. Working from a superseded sheet is the single most common cause of installed-and-wrong.
• A legend defining the symbols, and an abbreviations list

Plan, section, elevation, detail, and riser. A plan is a horizontal cut looking down; a section is a vertical cut, keyed to the plan by a section marker; a detail is an enlarged view of one condition; a riser diagram is a not-to-scale schematic showing how a system stacks through the floors. Control and network layouts are usually shown as riser or one-line diagrams because physical routing is left to the installer.

---

2. Reading Equipment Schedules

A schedule is a table on the drawings that carries the design data for each piece of equipment. It is where design intent lives, and it is what a commissioning technician measures against.

Air handling unit / rooftop unit schedule typically carries:

VAV terminal unit schedule: tag, served room, inlet size, maximum cfm, minimum cfm, reheat coil capacity (MBH or kW), water flow gpm, and electrical data. The maximum and minimum cfm columns are the numbers programmed into the box controller — and a box whose programmed minimum does not match the schedule is a very common commissioning defect that shows up later as a ventilation or comfort complaint.

Pump schedule: tag, gpm, head in feet, motor HP, efficiency, impeller diameter. Grille/register/diffuser (GRD) schedule: type, size, neck size, cfm, throw, and NC rating. Motor and panel schedules on the E sheets give circuit numbers, breaker sizes, and available capacity.

The habit worth building: before touching a unit, read its schedule row. Knowing that RTU-3 is scheduled for 4,000 cfm at 1.2 in. w.c. ESP turns a measured 2,900 cfm at 1.9 in. w.c. from a number into a diagnosis.

---

3. The Sequence of Operation

The sequence of operation is printed on the mechanical or controls sheets and is the contractual definition of what the control system must do. A complete sequence covers, for each mode:

• Occupied operation — what runs, what the setpoints are, how the loops behave
• Unoccupied operation — setback, night setup, and whether the fan cycles
• Optimal start / warm-up / cool-down
• Economizer enable and disable conditions, and the changeover method (Section 12.3)
• Safeties and interlocks — freezestat, high static, smoke detector, low limit
• Failure and alarm conditions and what the system does about them
• Reset schedules — supply-air temperature reset, static pressure reset, hot-water reset

When the graphic and the sequence disagree, the sequence governs. Graphics are a convenience; the sequence is the specification.

Converting a sequence to a flow chart is a named competency, and it is how ambiguity gets found before it gets installed. Drawing the AHU start sequence forces the questions the prose glossed over: what if status never proves, how long does the controller wait, what do the dampers do while the fan is proving.

---

4. The Points List (I/O Summary)

The points list enumerates every input and output the control system must provide, unit by unit. It drives the controller count, the wire count, the price, and the commissioning checklist.

Note the four point types from Section 15.4 in use: analog inputs and outputs are numeric, statuses and commands are Boolean, and the occupancy state is an enumerated virtual point.

Counting points is how a controller is selected. A field controller with 8 universal inputs and 4 analog outputs cannot serve a unit that needs 11 inputs, and finding that out during rough-in is expensive. Count the list, add spare capacity — 15–20% is normal practice — and select the controller.

---

5. Network Diagrams and the Address Schema

A network diagram shows what talks to what: the IP backbone, each supervisory controller, each field bus segment off it, and every device on each segment with its address. It is not a physical routing drawing; it is a logical map. When a segment goes quiet at 2 a.m., this diagram is what tells the technician which twenty devices are affected and where the segment begins and ends.

The address schema is the companion table, and the task list names maintaining it explicitly:

A disciplined schema encodes meaning: trunk number in the hundreds digit, MAC in the last two. Then a device instance tells a technician which trunk and which device it is without opening a laptop — and, critically, prevents the duplicate MAC and duplicate device-instance faults from Section 15.3, whose symptoms mimic a wiring problem.

---

6. The Documentation Set That Makes a System Serviceable

A BAS installation is finished when these exist, are accurate, and can be found:

1. As-built drawings — the set marked to reflect what was actually installed, not what was designed
2. Points list, as-built — including points added, deleted, or re-terminated during construction
3. Address schema and network diagram
4. Archived controller programs, one file per controller, named to match the controller label
5. Sequence of operation, as-commissioned, including any approved deviations from the design sequence
6. Submittals and shop drawings for every device — cut sheets, wiring diagrams, torque tables
7. O&M manuals and the commissioning report with recorded before/after readings
8. Login credentials and licensing information, transferred to the owner

The failure this prevents. Five years on, a controller fails. With the archive, it is a replace-and-download afternoon. Without it — no program file, no points list, no address schema, and a graphic that no longer matches the building — it is a re-engineering project. The documentation is not paperwork; it is the difference between a repairable system and a replaceable one.