Count inputs and outputs across every key subsystem. Apply spares and expansion for safer estimates. Download tables for quick coordination with vendors and teams.
| Equipment | Qty | AI/Unit | AO/Unit | DI/Unit | DO/Unit | Base Total |
|---|
A reliable I/O estimate starts by separating physical points from software points. Use AI for sensors such as temperature, pressure, flow, humidity, CO2, and differential pressure. Use AO for modulating outputs like VFD speed commands and valve or damper actuators. Use DI for status, proof, alarms, and interlocks, and DO for start/stop, enable, reset, and damper open/close commands. Keep a notes column in your project schedule to capture special points.
Normalize naming so every row matches the equipment schedule: AHU-01, CHWP-02, CT-01, and VAV-101. Quantity drives multiplication, so confirm counts from drawings. If vendor packages include built-in controllers, treat those points as integrated and exclude them from panel counts unless hardwired to the BAS. For typical estimating, an AHU often carries 30–40 total points, while a simple VAV may carry 4–6.
Apply spares and expansion to reduce late change orders. A common approach is 10–20% spares plus 5–15% expansion for future tenants or phased work. This calculator combines both into one factor and then rounds up to your chosen increment. Rounding to 5 or 10 points helps align with module capacities and avoids under-ordering.
Once adjusted totals are known, translate points into modules. Typical capacities are AI 8 or 16, AO 4 or 8, and DI/DO 16 each. Module counts are ceiling-based, because partial modules still require full hardware. Panel quantity is then estimated by dividing total modules by a maximum modules-per-panel value that reflects enclosure size, power, and wiring density.
Use the equipment breakdown table to support controls narratives, I/O schedules, and shop drawing reviews. Export CSV for estimating sheets and scope comparisons across bidders. Export PDF for submittals and coordination meetings. Track revisions by date, and re-run counts when equipment quantities or sequences change to keep the budget defensible. These outputs improve clarity for contractors, consultants, and owners.
1) What is included in an I/O point?
An I/O point is a field connection that lands on a controller input or output. It includes sensors, switches, relays, actuators, and command signals that require wiring and termination.
2) How should I count integrated equipment controllers?
If a packaged unit has its own controller and only provides network data, count it as integration, not hardwired I/O. Count hardwired points only when signals are physically landed at your panel.
3) Should I add spares and expansion separately?
You can, but keep the logic consistent. This calculator adds both percentages to create one factor, which helps you reserve capacity for maintenance replacements and predictable future scope growth.
4) Why do module sizes change between vendors?
Different platforms offer different channel densities, isolation, and mixed-signal options. Always confirm the exact card or module capacities from the selected supplier before final procurement and detailed design.
5) How does rounding affect my final hardware count?
Rounding prevents underestimating capacity when totals sit near a module boundary. Rounding up to 5 or 10 points typically aligns better with card sizes and reduces risk of field add-ons.
6) Can I use this output for tender documents?
Yes, as an estimating baseline. Include assumptions, allowances, and module sizing rules in your tender clarifications. Final quantities should be validated against the approved controls narrative and drawings.
Important Note: All the Calculators listed in this site are for educational purpose only and we do not guarentee the accuracy of results. Please do consult with other sources as well.