SCADA Programming:
What It Is and Why
Cloud Eliminates It (2026)

Back to Blog

The phrase "SCADA programming" means different things to different people. To a controls engineer, it means writing tag databases, building HMI screens, and configuring communication drivers. To an operations manager, it means months of delays and a bill that balloons from the original estimate. To a small operator who just wants to know if their pumps are running, it can mean a system that was never built because the cost was too high to justify.

This guide explains what SCADA programming actually involves, why it costs what it does, and why the emergence of cloud SCADA platforms has made much of it obsolete for the majority of industrial operators.

What Is SCADA Programming?

SCADA programming is the process of configuring and customizing a SCADA software platform to work with a specific industrial operation. Unlike consumer software - where you install an app and it works - traditional SCADA software is a blank canvas. Every deployment requires significant engineering work to make it function. That engineering work is what people mean by "SCADA programming."

The major components of a traditional SCADA programming project include:

1. Communication Driver Configuration

Before a SCADA system can display any data, it needs to communicate with the PLCs and RTUs in the field. This means selecting and configuring the right communication drivers for each protocol in use - Modbus RTU, Modbus TCP, OPC-UA, DNP3, EtherNet/IP - and defining the exact register addresses, poll rates, and connection parameters for each device. A single site with ten RTUs using two different protocols can take a day or more just to configure the communications layer correctly.

2. Tag Database Build-Out

Every sensor value in the system is represented as a "tag" in the SCADA database. Each tag needs to be defined with its name, data type, engineering units (PSI, °F, gal/min), scaling factors, alarm limits, and historian logging rate. For a well pad with 40 sensors per well and 20 wells, that is 800 tags - each configured individually. At a typical engineering rate of $150–$250/hr, the tag database alone can represent $10,000–$30,000 in labor.

3. HMI Screen Development

The Human Machine Interface - the dashboard operators use - has to be built from scratch in traditional SCADA software. This means drawing process flow diagrams (called "mimics"), placing live data elements on the screen, connecting them to the correct tags, and configuring the visual appearance. A professional HMI for a complex facility can take weeks of dedicated engineering time and result in hundreds of custom screens.

4. Alarm Configuration

Alarm management is more than setting high and low limits. Each alarm needs to be prioritized (critical, high, medium, low), suppressed during known maintenance windows, routed to the right operators, and documented in the alarm management system. Industrial alarm management standards (ISA-18.2) define detailed requirements that take significant time to implement correctly.

5. Historian and Reporting Setup

The historian database needs to be configured to store each tag at the right sampling rate (some tags every second, others every minute). Reports and trend views then need to be built on top of the historian data - daily production summaries, shift reports, maintenance logs. In traditional SCADA platforms, each report is a custom-built template.

6. Server Infrastructure

All of this runs on servers that need to be specified, purchased, installed, and maintained. Redundant servers for high-availability deployments, backup power, network switches, firewall configurations, antivirus management, Windows patch schedules. A traditional SCADA server room is an IT project in its own right.

Why Traditional SCADA Programming Costs So Much

The cost of SCADA programming is not arbitrary. It reflects the genuine complexity of what is being built. Three factors drive most of the cost:

Scarce Skilled Labor

Certified SCADA integrators - engineers who know both industrial protocols and SCADA software deeply - are not common. The people who can configure a traditional on-premise SCADA system correctly, handle protocol edge cases, and commission a system in a live production environment command rates of $150–$300/hr. A typical project involves two to five engineers working for four to twelve weeks.

Custom Engineering for Every Site

Every industrial operation is different. Different PLCs, different sensors, different process flows, different alarm philosophies, different reporting requirements. Traditional SCADA software provides a generic platform, but every deployment is effectively a custom software project. Unlike a website template you can fill in, a SCADA deployment starts from near-zero at each new site.

On-Site Work and Travel

Much of SCADA commissioning has to happen on site: physically connecting to PLCs to verify tag values, walking the process to validate that HMI screens reflect reality, testing alarm responses with operators present. For remote sites - oil fields, substations, water treatment facilities - this means significant travel time and cost on top of engineering hours.

How Cloud SCADA Eliminates Traditional Programming

Cloud SCADA platforms approach the problem from a completely different direction. Instead of building a general-purpose blank canvas that requires custom programming, they are pre-built systems designed around the most common industrial use cases - particularly oil and gas, water, and manufacturing monitoring.

Auto-Discovery Instead of Manual Configuration

When a Merobix gateway connects to a PLC or RTU running Modbus or OPC-UA, the platform automatically scans for available registers and proposes a tag list. The operator confirms the mapping and sets engineering units. Configuration that took days in traditional SCADA takes minutes in a cloud platform.

Pre-Built Dashboard Templates

Instead of drawing HMI screens from scratch, cloud SCADA platforms provide pre-built dashboard templates for common asset types: rod pumps, tank batteries, separators, compressors, electric submersible pumps. An operator selects the template, maps it to their device tags, and has a functional display within the hour.

Guided Alarm Configuration

Alarm limits are configured through a web-based form - enter high-high, high, low, and low-low limits for each tag, assign notification recipients, and save. No scripting, no alarm database programming, no custom notification routing logic.

No Server Infrastructure

The cloud platform's infrastructure is maintained by the vendor. There are no servers to buy, no operating systems to patch, no backup power to maintain, no IT staff required. The operator's only hardware is the gateway device at each field site - a ruggedized unit about the size of a paperback book that a field technician can install in under an hour.

Traditional SCADA vs Cloud SCADA: Side-by-Side

Factor	Traditional SCADA	Cloud SCADA (Merobix)
Initial setup cost	$50,000 – $200,000+	Hardware + subscription
Time to first data	4 – 12 weeks	Same day (< 4 hours)
HMI screens	Custom-built by integrators	Pre-built templates
Tag database	Manual entry, every tag	Auto-discovery + confirm
Alarm setup	Scripted/custom	Web-based form
Server infrastructure	Required (on-site IT)	None (cloud-hosted)
Adding a new site	Weeks + additional engineering cost	Install a gateway, done same day
Mobile access	Requires VPN or extra licensing	Included - any browser, any device
Software updates	Manual, scheduled downtime	Automatic, zero downtime

When Does Traditional SCADA Programming Still Make Sense?

Cloud SCADA is not the right fit for every application. Traditional SCADA programming still makes sense when:

• Complex control requirements: If your operation requires tight closed-loop control with millisecond response times - chemical reactors, high-speed manufacturing lines, turbine control - traditional on-premise SCADA with hardened servers may be necessary.
• Air-gapped networks: Some critical infrastructure or defense-related facilities cannot connect to the internet under any circumstances. On-premise SCADA is the only option for these sites.
• Highly custom integrations: Legacy proprietary protocols, custom hardware interfaces, or unique process requirements that do not fit standard templates may still require custom SCADA engineering.
• Large-scale enterprise deployments: Operations with hundreds of sites, thousands of tags, and complex corporate data integration requirements may benefit from the deep configurability of dedicated enterprise on-premise SCADA platforms - though cloud options exist here too.

For the majority of oil and gas operators, water utilities, and mid-size manufacturers, these conditions do not apply. The operation needs reliable data, good alarms, and mobile access - not custom HMI screens built by a $200/hr integrator.

How to Use Cloud SCADA Software: Getting Started

For operations teams evaluating cloud SCADA for the first time, the setup process looks nothing like traditional SCADA programming:

1. Order a Merobix gateway - a pre-configured hardware device ships to your site within a few days
2. Connect the gateway to your RTUs or PLCs - using existing Modbus or Ethernet wiring in most cases
3. Power on the gateway - it connects to the Merobix cloud platform automatically over cellular or your site network
4. Confirm your tag list - the platform auto-discovers available registers; you label them and set engineering units in a web form
5. Set alarm limits - configure high/low thresholds and notification contacts in the platform's alarm configuration tool
6. Invite your team - add other operators, managers, and engineers as users with appropriate access levels

Total time for a single-site deployment: two to four hours, including hardware installation. No SCADA integrator required. No custom programming. No server room.

Frequently Asked Questions