IIoT, SCADA & Edge Connectivity calculator

SCADA Upgrade Cost Calculator

Estimate what a SCADA upgrade will cost on a single site or line. Enter the cost per HMI server or runtime seat, the total tag count being loaded onto the new platform, the share of tags actually migrated (some legacy tags are dropped during cleanup), and a fixed adder for engineering, FAT, SAT, and cutover support. The calculator returns the variable platform cost and the loaded total.

What this calculator does

  • Estimate the loaded cost of a SCADA upgrade across HMI servers, polled tags, and screens from the unit cost per HMI server (or seat), the tag count loaded onto the upgrade, the share of tags actually migrated, and a fixed engineering and cutover adder.
  • Use it when you are scoping a SCADA modernization (for example moving from a legacy SCADA to Ignition, AVEVA, or FactoryTalk View) and need a defensible per-site cost before the integrator quote.
  • It returns the loaded SCADA upgrade cost for one site or line, broken into variable platform cost and a fixed engineering and cutover adder.

Formula used

  • Variable SCADA platform cost = HMI server count × cost per seat × share of tags migrated
  • Total SCADA upgrade cost = variable platform cost + fixed engineering and cutover cost

Inputs explained

  • Number of HMI servers or runtime seats: Use the count of HMI servers, redundant pairs, or runtime seats in the new SCADA architecture.
  • Cost per HMI server or runtime seat: Use the per-seat or per-server price from the SCADA vendor quote, including base license and any required runtime modules.
  • Share of legacy tags migrated: Use the share of legacy SCADA tags actually rebuilt on the new platform after rationalization (typical 60 to 90 percent, with the remainder dropped, merged, or deferred).
  • Fixed engineering, FAT, SAT, and cutover cost: Include integrator engineering hours, factory acceptance test, site acceptance test, validation, training, weekend cutover labor, and rollback contingency.

How to use the result

  • Use it before issuing an RFP for a SCADA modernization, when comparing two SCADA platforms head-to-head, or when finance needs a per-site number to roll into a multi-site rollout plan.
  • It is a planning estimate. It does not include downstream historian, MES, or analytics layer cost; pair with the data historian storage cost and tag mapping workload calculators for a full migration view.

Common questions

  • Why scale the platform cost by share of tags migrated? Most SCADA upgrades drop or merge 10 to 40 percent of legacy tags during rationalization. Scaling the variable line by the share actually migrated avoids over-buying licenses and runtime.
  • What goes into the fixed engineering and cutover adder? Integrator engineering hours, FAT and SAT, GAMP or 21 CFR Part 11 validation if regulated, training, weekend cutover labor, and rollback or hot-standby contingency.
  • How does this differ from the SCADA migration workload calculator? This one returns dollars; the migration workload calculator returns hours. Use them together: workload sizes the labor, this one rolls labor and platform into a per-site dollar figure.
  • Should I include redundant servers? Yes. If the new architecture has hot-standby HMI servers, count both nodes in the seat count, since both need licenses.

Last reviewed 2026-05-12.