Connectivity Cost

IIoT and SCADA Cost Estimation: What Drives Cost per Connected Asset

How to price an IIoT and SCADA project by cost per connected asset, from sensor hardware and tag-mapping labor to SCADA upgrades, MQTT egress, and the overhead lines estimators forget.

Price IIoT and SCADA work by cost per connected asset, then roll up. A typical brownfield asset lands between 1,200 and 4,500 dollars all-in, and the spread is almost entirely labor and integration, not hardware. A gateway runs 300 to 900 dollars and sensors 50 to 400 dollars each, but engineering time to map tags, wire I/O, and validate streams often doubles the bill of materials. Estimators who quote only hardware routinely underbid by 40 to 60 percent. Use the Sensor Installation Cost and IIoT ROI calculators to separate capital from the labor that actually decides the margin.

Tag mapping labor is the line item that sinks quotes. Budget 10 to 25 minutes per tag for discovery, mapping, and validation on legacy PLCs, less on modern OPC UA equipment. An asset exposing 45 tags at 18 minutes each is 13.5 hours; at a loaded rate of 110 dollars per hour that is roughly 1,485 dollars of labor before any hardware. Across 60 assets that is close to 89,000 dollars of pure mapping effort. The Tag Mapping Workload calculator converts tag counts and per-tag minutes into hours and cost so you can defend the number line by line instead of guessing a lump sum.

SCADA upgrades carry cost that lives outside the per-asset math. License tiers scale by tag count in bands, so crossing from 5,000 to 5,001 tags can jump a license 8,000 to 20,000 dollars at the next tier. Add server hardware or virtualization, redundancy for critical HMIs, and 15 to 25 percent annual maintenance on the license base. A mid-size SCADA modernization commonly runs 150,000 to 600,000 dollars. The SCADA Upgrade Cost calculator breaks this into license, engineering, hardware, and commissioning so you are not surprised by the maintenance tail that recurs every year after go-live.

Recurring data cost is the line that turns a clean capital quote into a bad total cost of ownership. MQTT egress and cloud ingestion bill per message or per GB. At 5.2 GB per day per gateway and 20 gateways, that is 104 GB daily, roughly 3.1 TB monthly; at even 0.05 dollars per GB of managed ingestion plus platform per-message fees, monthly bills reach thousands. Publish-on-change instead of fixed-interval can cut volume 60 to 90 percent on steady processes. Run the MQTT Data Cost calculator with both publishing strategies before you quote a monthly platform fee to the customer.

Historian storage is cheap per gigabyte but expensive in retention scope. Raw storage might be 0.02 to 0.10 dollars per GB per month, but the real drivers are retention years, replication, and backup copies. A 5,000-tag system generating 3.46 GB per day uncompressed and held 7 years is over 8.8 TB before compression; with three copies for HA and backup you triple that footprint. Compression buys back 5 to 20 times, so the honest number is a range, not a point. The Data Historian Storage Cost calculator lets you price low, expected, and high compression so the quote survives an audit.

Overhead lines are where defensible quotes get their credibility. Add commissioning and validation at 15 to 30 percent of hardware plus labor, network hardening and OT firewall work, spare gateways at 5 to 10 percent of fleet, and a contingency of 10 to 15 percent for brownfield surprises like undocumented PLCs. Project management typically adds another 8 to 12 percent. A quote that shows only hardware and mapping and omits these reads as naive to a buyer who has done this before. Itemize them; a line the customer can question is more defensible than a padded unit rate.

Estimates go wrong in predictable places. The biggest is assuming every in-scope asset is greenfield when 30 to 50 percent need protocol converters or serial-to-Ethernet gateways at 150 to 600 dollars extra each. The second is sizing bandwidth and storage on target tags rather than the 80 to 90 percent that actually get mapped, which overbuilds by 10 to 20 percent. The third is forgetting the annual maintenance and data egress tail, which over 5 years can exceed the original capital. Anchor the capital number with the IIoT ROI calculator so the payback story survives these recurring costs.

Build the quote bottom-up and cross-check top-down. Sum per-asset hardware, per-tag mapping labor, SCADA license band, recurring data and storage, and overhead, then divide by asset count to get a blended cost per connected asset. If that blended number falls outside 1,200 to 4,500 dollars for a brownfield plant, find out why before you send it. A quote landing at 800 dollars per asset almost always dropped mapping labor or the SCADA license; one at 7,000 dollars usually double-counted engineering. The sanity band is your fastest defense against a mispriced bid.

Published 2026-07-01.