SCADA Cost FAQs for Small Water and Wastewater Systems
Price comes up early in every SCADA conversation, and it is the hardest thing to get a straight answer on. Here is what the numbers actually look like, what is recurring, and what grant money will and will not cover.
How much does SCADA cost for a small water system?
–Most vendors quote only, but two publish their prices, and those two set a useful floor.
Trihedral posts a US price list for VTScada. Under its pricing effective July 1, 2025, a single-server bundle licensed for 1,000 I/O tags is $14,795. That covers one runtime, one development node, two remote users, alarm notification, and the first year of support. Priced by component instead, a 1,000-tag runtime with full historian starts at $3,395, before development, alarm notification, or thin clients. Annual support after the first year is 15 percent of the total software purchase price, with 24/7 emergency support at an additional 5 percent.
Inductive Automation licenses Ignition by the server rather than by tag count, so one license covers unlimited tags and clients. Its published annual support starts at 16 percent of the software’s retail price and runs to 24 percent at the highest tier.
Rockwell sells FactoryTalk View either as a subscription or as a perpetual license with maintenance, both priced by quote.
Those figures are software alone. Field hardware, communications, installation, and integration labor are quoted per project, which is why no vendor answers this with one number. What belongs in the full five-year figure is a longer conversation.
What does SCADA cost every year after you buy it?
+The one recurring cost vendors publish is the annual support contract, priced as a percentage of what you paid for the software.
annual support What happens
if it lapses
(Trihedral) 15% of total software
purchase price, plus 5%
for 24/7 emergency support Support can be continued
only while it has not lapsed
(Inductive Automation) 16% of retail price at the
lowest tier, up to 24%
at the highest Not published
(Rockwell) Included in the annual
cost when bought as
a subscription Not published
On VTScada’s published 1,000-tag single-server bundle, the first year of support is included in the purchase price. Year two is when the percentage starts.
Support is not the only thing that recurs. Connectivity, remote access, IT help, and the staff hours to keep a system patched all come back every year. None of those are published by any vendor, which is why they have to be priced for your specific system rather than looked up.
Can grant funding pay for a SCADA system?
+Yes. Both federal revolving fund programs name SCADA specifically, and both allow it as a project on its own rather than only as part of a larger construction job.
EPA’s guidance for the Drinking Water State Revolving Fund says the loan fund may finance installing or updating SCADA systems, along with upgrading outdated computers and software and creating secure network backups. It then says plainly that these are eligible components of larger drinking water system improvement projects, or may be stand-alone projects. EPA’s Clean Water State Revolving Fund guidance uses the same language for publicly owned treatment works.
A few things that decide whether your project qualifies:
It has to connect to compliance or public health. DWSRF projects must either help the system comply with national primary drinking water regulations or significantly further the health protection goals of the Safe Drinking Water Act.
Your state sets the priorities. EPA notes that CWSRF eligibility may vary according to each state’s priorities, so the state’s Intended Use Plan is the document that governs. Some states reward automation directly. Connecticut’s drinking water application instructions assign priority points to facility automation and name SCADA as the example.
Terms run long. DWSRF loans extend up to 30 years, and up to 40 years for disadvantaged communities.
Assessments are funded separately. DWSRF set-aside funds can pay for cybersecurity assessments and emergency response planning, and EPA states that infrastructure improvements identified by those assessments may then be funded through the loan fund.
Rural systems have a second route. USDA Rural Development’s Water and Waste Disposal program serves areas of 10,000 people or fewer and funds construction, equipment, and engineering fees. Grants can be combined with loans where that is needed to keep user costs reasonable. SCADA is not named in USDA’s materials the way it is in EPA’s, so confirm the scope with your state Rural Development office before you build it into an application.
None of this covers the recurring side of a subscription, which works differently and is worth understanding before you write a scope of work.
Will grant funding cover a subscription, or only equipment?
+Equipment and installation are the safe part. Recurring subscription fees are not, and that distinction is written into the federal rules.
Federal regulations governing the Drinking Water State Revolving Fund list operation and maintenance costs as ineligible. That is the sentence that matters.
Hardware, installation, integration, and engineering fit the capital definition the program is built around. A monthly or annual fee to keep a service running does not, and no EPA guidance we could find addresses whether a software subscription qualifies.
That leaves it to the state. SRF programs are administered state by state, and the answer you get in one state may not match the next. Ask your state program in writing, before the scope of work is final, whether it will fund the equipment and installation portion and whether a prepaid multi-year term can sit inside the capital request.
Two things worth knowing while you ask:
One federal program is written more broadly. The Midsize and Large Drinking Water System Infrastructure Resilience and Sustainability program, for systems serving 10,000 or more people, covers planning, design, construction, implementation, operation, or maintenance of projects that increase resilience, and cybersecurity is named. That wording reaches further than SRF does. The program is currently closed to applications, so treat it as something to watch rather than something to plan around.
Accounting treatment is a separate question from eligibility. Under GASB 96, a subscription running longer than twelve months is recorded as a subscription asset and a subscription liability rather than a simple expense, which puts it on the books as an intangible capital asset. That helps a finance director explain the purchase. It does not make a grant program willing to pay for it, and the two should not be confused in an application.
The practical structure most utilities land on is to put hardware, installation, integration, and any prepaid term into the capital request, then carry renewals in the operating budget. Confirm it with your state program rather than assuming, because the rule that governs your project is theirs, not EPA’s.
What does the implementation timeline cost you?
+Deployment time is a cost, not just a schedule. Every week before a system turns on is labor you are paying for and monitoring you do not have yet.
The spend sits in what has to be built first. An on-premise install means procuring a server, licensing an operating system, configuring backup and remote access, and often engineering a radio path between the plant and the remote sites. Radios, repeaters, towers, and network equipment each carry a purchase, an install, and configuration labor. That work is billed whether the system is monitoring anything yet or not.
A cellular setup removes most of that sequence:
Plug and play, connected to the PLC you already have.
No new network drop, no static IP, no port forwarding.
The HMI, dashboard, and report builder are drag and drop.
Text or email alarms, acknowledged from your phone.
With no server to procure and no radio path to engineer, what remains is hardware installation and screen configuration, which is why the timeline is measured in days rather than months.
Two costs ride on that timeline. Integration labor is usually billed hourly, so a longer build is a bigger invoice. And a system that is not live is not catching the overflow or the pump failure it was bought to catch, which is the cost nobody puts on a proposal.
What does it cost if you have to replace your PLCs?
+Replacing working controllers is usually the largest avoidable expense in a SCADA project, and the one most likely to be buried in a proposal.
Your PLCs are the longest-lived equipment in the system. Control hardware like PLCs and telemetry typically runs around fifteen years in service, against roughly five for a server. Scrapping controllers with a decade of life left means paying for hardware you did not need to buy and rebuilding control logic that already worked.
A system that connects to your existing controllers avoids that line item entirely. The hub reads the PLC where it sits, and your control logic stays put. Pumps still run, tanks still fill, treatment keeps following the program you set.
Two things determine whether your equipment qualifies:
Protocol support. Can the platform read your controller directly, or does it need third-party driver software in between? That middle layer is its own license and its own annual renewal.
Physical reach. Can the hub connect to the controller where it is installed, or does the panel need work first?
Ask a vendor both questions about your equipment by name, before a quote is final. A compatibility problem found during installation becomes a change order.
What does replacing your HMI add to the project?
+A new screen is rarely just a screen. It carries configuration labor and operator retraining, and both are real costs that rarely appear as line items.
The HMI is what an operator works from. Some plants run a panel mounted on site and wired to the PLC. Others work from a workstation, and many run both. A modern platform adds its own screens, reachable from a browser or a phone, which raises the question of what happens to the ones you have.
Three outcomes, with different price tags:
Local screens keep running, the platform’s screens are an addition. No replacement cost, no retraining.
You rebuild screens and remove the old ones. That is configuration hours plus time spent getting operators comfortable on an unfamiliar layout.
Local screens for the people in the plant, remote screens for everyone else.
Get the answer in writing before you buy.
A hard requirement for screens on site is a legitimate constraint, and it is cheaper to name during evaluation than to solve during installation.
One distinction worth keeping straight: replacing an HMI is not replacing a PLC. Your operator screens and your control logic are separate purchases, and a system can change how you see the process without touching how it runs.
Does phasing one site at a time cost more?
+Usually not, and for a small system spreading the spend across budget years is often the only way the project happens at all.
Phasing lets you put the worst site on first, watch it run, and commit the rest once it has proven out. You are asking a council to approve a smaller number, and you are not betting a full capital budget on a platform nobody has used yet. For a utility working against a grant cycle, it also lets the project match the money as it arrives.
Whether phasing is affordable depends on how the second site gets added. On a central server with a radio network, each new site may need engineering against existing infrastructure, and a repeater or tower if it sits too far out. Those costs land on the site that triggers them, so site four can cost several times what site two did. On a cellular setup, each site communicates on its own, so the cost of adding one stays close to the cost of the last one.
Three questions before you phase:
Does adding a site later cost more than including it at the start?
Do all sites report to one dashboard, or does the second one create a second system to maintain?
How does your license or subscription change as sites are added?
Sites 40 miles apart on one screen is the outcome. Confirm the per-site math holds before you buy the first one.
Ready to simplify your SCADA operations?
Connect with SimpliScada to discuss secure cloud SCADA for your water or wastewater system.