Cost · Point count
Point Count Guide for Building Automation Projects
A practical method for counting I/O and integration points, structuring a point schedule and keeping the count consistent from design to handover.
Quick answer
A building automation point count should list every signal the system reads, writes or exchanges, classified by type and location. Count physical I/O, bus devices and integration objects with explicit rules, add documented spare capacity, and keep one schedule from design through commissioning and handover.
Classify points before counting them
Start with six classes: analogue input, analogue output, digital input, digital output, bus or field-device points, and integration or virtual points. Each class has a different cost, termination and testing method. A temperature sensor is an analogue input; a valve actuator may need an analogue output and a feedback input; a DALI luminaire group is a bus object; a meter register read over Modbus is an integration point. Mixing these classes in one total hides the cost structure and makes controller selection guesswork. Classify first, then count within each class. The classification also tells the panel designer what terminals, power and separation are required. The schedule should show the counting rule in a header note so that later reviewers apply it consistently.
Counting rules that survive a tender
Count one point per signal, not one per device. A fan-coil unit with a valve output, fan speeds and a filter switch is several points, not one. Count spare I/O separately and state the percentage or quantity explicitly. Count metering registers that are actually used, not every register the meter exposes. Count integration points that carry data into sequences or reports, and mark monitoring-only points. Decide how virtual points are treated and keep that rule for every bidder. These rules should appear in the tender documents so that proposals can be compared without rework. Ambiguity here is not a technical detail; it is a commercial risk that surfaces at the first change order.
Build the schedule from assets and sequences
A point schedule should have columns for point name, description, location, equipment, signal type, range and units, controller and panel, terminal or address, alarm class, historian setting and the sequence or graphic that consumes it. Build it from the equipment schedule and the sequence of operation, not from a generic template. Allocate points to controllers with a stated loading limit, and keep spare capacity per panel and per bus segment. The schedule then becomes the basis for panel design, software configuration, testing and the as-built record. A schedule that cannot be traced to a sequence is either incomplete or carrying points nobody needs.
Review at every design gate
Point counts drift when the design develops and nobody reconciles the changes. Review the schedule at concept, detailed design, tender, factory acceptance and site acceptance. At each gate, compare the current count with the previous issue, explain additions and deletions, and check that spare capacity has not been consumed by scope growth. At handover, verify the as-built count against the tested points and record any points that were installed but not commissioned. A count that is only updated at the end is a source of disputes, not a design tool. The review record also shows the owner how the scope changed and why. Freeze the rule, not the numbers, because the numbers will legitimately change.
Point classes and counting rules
7 rows| Point class | Examples | Counting rule |
|---|---|---|
| Analogue input | Temperature, humidity, pressure, CO2 | One point per measured signal and range |
| Analogue output | Valve, damper, fan speed command | One point per modulated output; feedback is separate |
| Digital input | Door contact, fault, status, pulse | One point per status or pulse signal |
| Digital output | Relay, contactor, enable command | One point per switched output |
| Bus device | DALI group, KNX device, Modbus register | Count the objects used by sequences, graphics or reports |
| Integration point | Gateway tag, API object, virtual point | Count once at the interface and map to the internal object |
| Spare point | Reserved I/O or bus capacity | State quantity and location explicitly; never hide it in a percentage |
Project images
3 images
Frequently asked
01How many spare points should a schedule include?
Enough for the documented future loads and a stated allowance for unknown changes. The quantity should be visible per panel and per bus, not buried in a percentage.
02Do integration points count as I/O?
They are not physical I/O, but they are engineering points. Count them separately and state whether they are included in the commercial point total.
03Who prepares the point schedule?
The automation designer usually prepares it, with input from the MEP consultant and the controls contractor. The owner should approve the final issue.
04When should the count be frozen?
At tender, with a change-control process afterwards. The schedule should still be updated at each design gate and reconciled at handover.
05How do we check a contractor's count?
Ask for the schedule, not the total. Sample rooms or plant areas, compare against the equipment list and sequences, and review the spare capacity assumptions.
Next step
Bring us the building.
Tell us the building type, systems in scope and the outcome you need. We will map the shortest path to a working system.