BMS points list template: columns, point types and naming rules

Published 20 October 2026 · 6 min read

A BMS points list template is a table with one row per point, each physical input or output wired to a controller and each value exchanged over a bus, and a fixed set of columns: tag, location, equipment, description, point type, unit, alarm and priority, logging and interval, and the panel the point belongs to. The point types are usually five: analogue input (AI), analogue output (AO), digital input (DI), digital output (DO) and communication or bus point (BUS). Written once, with a single naming rule, the list drives the price, the programming, the supervisory views, the point-to-point tests and the as-built file.

What the points list is for

The specification describes behaviours; the points list says what is measured and commanded to achieve them. Bidders count inputs and outputs per panel to size controllers and price cabling; the supervisory licence is sized on the number of points; the programmer builds the database from it; the test team checks it row by row. A points list "to be established by the contractor" produces bids that cannot be compared, and a change order at the first site survey. The BMS specification template shows where the list sits among the tender documents: as an appendix that forms part of the contract, completed by the contractor during detailed design and updated until the as-built version.

Columns of a usable points list

At detailed design, add the controller address, the BACnet object or Modbus register and the terminal or wiring reference; the as-built list carries them. Totals by type and by panel, calculated by formulas, let anyone check the spare capacity required by the specification.

Point types

• AI, analogue input: a measured value. Water, air and room temperatures, pressures, CO₂, humidity, illuminance.
• AO, analogue output: a modulated command. Valves, dampers, fan speeds, setpoints sent to equipment.
• DI, digital input: a two-state signal. Run status, faults, filter alarms, frost and fire safety contacts, window contacts, presence.
• DO, digital output: an on/off command. Start and stop of heat pumps, pumps, air handling units, exterior lighting.
• BUS, communication point: a value read or written over a network rather than wired: zone controller setpoints, DALI lighting scenes, meter power and energy indexes over M-Bus or Modbus, data from a heat pump's own controller.

Meter readings over a bus are BUS points with a unit such as kWh. Counting inputs wired to a controller, where used, should be declared as such so that the test sheet checks the pulse weight.

Example: an air handling unit (fictitious data)

A heat-recovery air handling unit serving offices, in a fictitious project, has 22 points: 1 DO, 7 DI, 7 AI and 7 AO. An extract:

Two rows show why the list is a coordination tool: the fire safety contact is supplied by another work package, and the frost thermostat triggers a sequence that the functional tests will replay. Both carry priority 1 alarms, which the acceptance rules treat as safety functions.

One naming rule, written once

Choose one pattern and state it in the specification, for example [EQUIPMENT]-[FUNCTION]: AHU1-TSA for the supply air temperature of air handling unit 1, Z04-TROOM for the room temperature of zone 04. Then fix the details:

1. A closed list of abbreviations, published in an appendix: CMD command, STS status, FLT fault, TSA supply air temperature, TRA return air temperature, TOA outdoor air temperature, SP setpoint, SPD speed, VLV valve, DMP damper.
2. Upper case, hyphens as separators, no spaces, no accents, one tag per point and no reuse.
3. The same tag in the points list, the controller, the supervisory system, the panel drawings and the cable labels.
4. A full label for the operator in the supervisory system ("AHU 1 north wing offices supply air temperature"), with an SI unit and, for analogue points, a validity range beyond which the value is flagged as invalid.

Consistent tags also help security: the equipment inventory and network drawing required in the BMS cybersecurity requirements checklist are far easier to check when every device and point is named the same way.

From points list to test matrix

Each row becomes one point-to-point test, chosen by type: an AI is read and compared with a reference measurement, with scaling, unit, alarm thresholds and logging checked; an AO is commanded at 0, 50 and 100% and the actuator position checked; a DI is simulated at the equipment, with feedback, delay, label, priority and acknowledgement checked; a DO is commanded, with status and manual override checked; a BUS point is read and compared with the local display, and its behaviour on loss of communication observed. Each test is dated and marked Pass, Fail or Not applicable, and 100% of the points are tested before the functional tests start. The sequence that follows is set out in the BMS commissioning and acceptance checklist.

FAQ

How many points does a building need?

There is no ratio: the count follows the plant, the zones and the functions required. The fictitious administrative building of the example above, with two heat pumps, three air handling units and twelve zones, has 300 points.

Who writes the points list, the designer or the contractor?

Both, in turn. The designer issues it with the tender so that bids are comparable; the contractor completes it at detailed design with addresses and wiring, then updates it until the as-built version.

Should bus points be in the list?

Yes. They consume supervisory licence capacity, they need labels, alarms and logging like wired points, and they must be tested, including on loss of communication.