The Promise and the Pain of Traditional SCADA
Supervisory Control and Data Acquisition has been the backbone of industrial infrastructure management for more than four decades. Water utilities, energy distributors, gas networks, and municipal operators all rely on SCADA to see what is happening across their assets in real time, respond to alarms, and automate control actions. The value proposition is undeniable. The delivery mechanism, however, has always come with a brutal bill.
A conventional SCADA rollout looks something like this. Engineering teams spend months surveying the field to map cable routes. Civil contractors follow to dig trenches across roads, over rail crossings, under riverbeds, and along canal banks. Manholes are installed. Steel cabinets bolted to concrete pads. Uninterruptible power supplies sized and wired. RS-485 or Modbus RTU runs pulled over hundreds of metres. A communications concentrator — or several — is installed at strategic points. After months of civil works, commissioning begins: each Remote Terminal Unit (RTU) is programmed, each analogue loop calibrated, and each alarm threshold tuned. The SCADA server is configured, the HMI screens built, and operators trained on a system that, by the time it goes live, has consumed a budget that could have funded a small infrastructure project in its own right.
Industry analysts consistently report that in large SCADA projects the majority of the total cost sits not in the software licence or even the RTU hardware, but in the civil and electrical infrastructure surrounding it — cabling, conduit, power supply, cabinets, and the associated groundwork. For a medium-sized water utility with 200 pressure monitoring points spread across a network, a traditional SCADA deployment can take two to three years and consume millions in capital expenditure before a single real-time reading appears on a screen.
And then the network grows. A new pressure zone is created. A pumping station is built on the far side of a river. A regulator is installed under a busy road junction. Each extension triggers a fresh round of permits, trench digging, cable pulling, and cabinet installation. SCADA becomes a constraint on the speed at which an organisation can instrument its own infrastructure.
What “Over-the-Top” Means in This Context
The term over-the-top originates in telecommunications, where it describes services — video streaming, messaging, voice calls — delivered over the public internet rather than through the proprietary networks that carriers originally built for those purposes. Netflix does not need to lay fibre. WhatsApp does not need to own a telephone exchange. They ride the infrastructure that already exists.
The same logic, applied to industrial monitoring, produces a category of solutions that deliver SCADA-equivalent value — real-time data acquisition, alarm management, automated control, reporting, and integration — by riding communications networks that are already built, already maintained, and already paid for by someone else. No trench digging. Simply give ignore to cable permitting. No cabinet on a concrete pad. Without dedicated power supply. The monitoring capability arrives on top of existing public or private wireless networks.
ThingsLog is, in the most precise sense of the term, an over-the-top SCADA platform.
The ThingsLog Architecture: Three Layers, Zero Civil Works
Layer 1 — The Field Device
At the edge, ThingsLog deploys its own range of low-power data loggers — hardware designed and manufactured in-house, CE certified, and rated IP68 for continuous immersion. Every device in this family shares a critical characteristic: it requires no external power connection and no communication cable to function. The logger connects to an existing meter, sensor, or actuator. A battery — in low-power NB-IoT or LoRa mode lasting more than ten years — is inserted. The device boots, selects the best available network from its supported radio stack (LoRa, NB-IoT, LTE-M, 4G, 2G), and begins transmitting readings on a configurable schedule. From unboxing to live data: minutes, not months.
- LPMDL-1104 — compact 4G/2G logger with two pulse inputs and four analogue channels, relay outputs, GNSS positioning. Battery, solar, or external power.
- LPMDL-1106 — multi-channel ultra-low-power logger supporting NB-IoT, Cat-M1, and 2G fallback for flow, pressure, level, temperature, and environmental measurements.
- LPMDL-1105 — LoRa/LoRaWAN logger for pulse counting and analogue measurement with over a decade of battery life at 15-minute reading intervals.
- TLCTL-1104 — 4G MQTT Modbus controller for active control: pumping stations, street lighting, remote actuators.
- NRW Logger — combined pressure and flow data logger for non-revenue water detection, available across all radio technologies.
Layer 2 — The Network
ThingsLog field devices transmit over networks operated by mobile carriers (NB-IoT, Cat-M1, 4G) or LoRaWAN gateway operators. These networks are already built, already maintained, and already paid for. A single ThingsLog device mounted on a meter in a manhole under a road transmits through the concrete and soil via NB-IoT — a technology specifically designed for deep indoor and underground penetration — to the carrier’s base station and into ThingsLog’s cloud platform. The operator has not paid for a metre of cable, dug a single trench, or obtained a single crossing permit.
Layer 3 — The Cloud Platform
ThingsLog’s cloud platform operates as a fully managed SaaS service hosted in EU data centres — or, for organisations with data sovereignty requirements, as an on-premises or PaaS deployment. The platform provides real-time data ingestion, anomaly detection and trend analysis, a configurable rules engine that triggers SMS/email/push alerts and issues relay commands to actuators, automated reporting, and open API integration via REST, MQTT, Modbus RTU/TCP, M-BUS, wireless M-BUS, and S0 pulse output — enabling data push into existing SCADA, GIS, ERP, billing, or hydraulic modelling systems.
The Obstacles Traditional SCADA Creates — and ThingsLog Eliminates
Cables Across Rails, Rivers, and Roads
Every crossing of a railway, a navigable waterway, or a public road is a regulatory and logistical event. Rail crossings require weeks or months of permitting, narrow installation windows, and specialist directional-drilling contractors. River crossings demand environmental permits and hydrological surveys. Road crossings require traffic management plans and municipal permits. A single difficult crossing can delay a SCADA extension by six months and add five to six figures to the project cost.
ThingsLog transmits wirelessly. There is nothing to cross. A pressure sensor on one bank of a river and a flow meter on the other bank each transmit independently to the carrier’s nearest cell tower. No permission is required from the railway operator. No environmental survey is triggered. No trench is dug under the road. Both monitoring points go live on the same day, for the cost of two data loggers and two SIM cards.
Complex Power Supply
Providing mains power to a remote or underground monitoring point requires its own electrical infrastructure: a low-voltage distribution network connection, a cabinet with distribution board and circuit protection, and typically an uninterruptible power supply. ThingsLog loggers in NB-IoT or LoRa mode operate for more than ten years on a single set of standard battery cells at 15-minute reading intervals. There is no power supply problem to solve, no mains connection to negotiate, no generator to refuel. The device is installed, the battery is inserted, the monitoring point is live.
Extra Manholes and Cabinets
Every traditional SCADA field installation requires a weatherproof, tamper-resistant enclosure: a roadside cabinet, pole-mounted box, or in-ground manhole. These structures cost money to fabricate and install, require ventilation or climate control, present a theft and vandalism risk, and require periodic inspection. A ThingsLog data logger is a self-contained device the size of a paperback book. It mounts directly on a meter, inside an existing meter box, or on a pipe — no dedicated cabinet, no climate control, no external footprint. In many deployments it sits inside the existing meter pit, invisible from the street.
Long Lead Times
Civil design, permitting, procurement, civil construction, electrical installation, and commissioning combine to produce lead times of twelve to thirty-six months for significant SCADA extensions. During this period the utility operates blind — unable to detect losses, respond to pressure anomalies, or verify consumption in unmonitored zones. ThingsLog collapses this to weeks. A project to instrument fifty pressure monitoring points can be designed, procured, shipped, and installed in four to eight weeks. Operations teams see their network in real time before the traditional alternative would have finished the permitting phase.
ThingsLog vs. Traditional SCADA: A Structured Comparison
| Dimension | Traditional SCADA | ThingsLog OTT SCADA |
|---|---|---|
| Deployment lead time | 12–36 months | 2–8 weeks |
| Civil infrastructure | Trenches, cable ducts, manholes, cabinets | None |
| Power supply | Mains connection or generator | 10+ year battery (NB-IoT/LoRa); solar optional |
| Communications | Proprietary cable or licensed radio | NB-IoT, LTE-M, 4G, LoRaWAN — carrier-operated |
| Network crossings | Permits for every rail/road/river crossing | Wireless — no crossings required |
| Field enclosures | Weatherproof cabinets on every RTU | Device mounts within existing meter box |
| Protocol support | Modbus RTU/TCP, DNP3, IEC 60870 | REST, MQTT, Modbus, M-BUS, wM-BUS, S0, API |
| Integration | Requires gateway and protocol conversion | Native API push to SCADA, GIS, ERP, billing |
| Scalability | Each new point requires civil design and works | New device ships, clips on, transmits within the day |
| Maintenance | Cable faults, cabinet inspections, UPS testing | Battery replacement after 10+ years; OTA firmware updates |
| CapEx model | High upfront CapEx dominated by civil works | Low hardware cost; SaaS subscription eliminates server CapEx |
| Data sovereignty | On-premises server, customer managed | EU-hosted SaaS or on-premises/PaaS deployment |
Real-World References
Sofia Water, Bulgaria’s largest water utility, uses ThingsLog for smart metering and network monitoring across one of Central Europe’s largest urban distribution networks. The density of Sofia’s streets — crossed by tram lines, metro infrastructure, and heavily trafficked arterials — makes traditional SCADA cable runs a permitting nightmare. ThingsLog’s wireless loggers operate in existing meter pits, transmitting through NB-IoT and feeding data directly into the utility’s operational systems.
Bulyard Shipbuilding Industry, the largest shipbuilding enterprise in Bulgaria by volume, deployed ThingsLog for remote water metering across its facility. A shipyard’s combination of heavy industrial infrastructure, active production areas, and dock crossings makes cable-based monitoring impractical. ThingsLog’s battery-powered loggers solved the problem without any of these complications.
Kaufland and dm, pan-European retail chains operating hundreds of stores, use ThingsLog for energy and water monitoring across their facility portfolios. ThingsLog devices install in hours, integrate via API with ERP and facility management platforms, and report in real time to central operations teams — with no tolerance for multi-month civil lead times.
Hotel Budapest and agri-cooperatives across Central and Eastern Europe round out a reference portfolio spanning city-centre hospitality to open agricultural land — where fields separated by streams, irrigation channels, and farm tracks present cable-routing challenges the wireless model sidesteps entirely.
The Economics: What Over-the-Top Actually Saves
The financial case is not primarily about the device cost. A ThingsLog logger is competitively priced relative to a traditional RTU, but the RTU is rarely the dominant cost. The savings materialise in the infrastructure the wireless model eliminates.
For twenty new pressure loggers across a medium-sized city under traditional SCADA: route survey and cable design (six to eight weeks), permitting for crossings (four to twelve months), civil construction and electrical installation (several more weeks), server configuration and HMI development — total timeline to live data: twelve to twenty-four months.
Under ThingsLog: site survey to confirm coverage (one to two days), device delivery (one to three weeks), installation by one technician with no civil equipment (one day for twenty devices), platform configuration (hours) — total timeline to live data: two to six weeks.
The CapEx profile shifts from a large, upfront civil works commitment — required before a single reading is taken — to hardware procurement that scales per monitoring point as it is commissioned. For public utilities and municipal operators operating under capital budget constraints, this incremental model can be the difference between a monitoring programme that proceeds and one that stalls indefinitely in a project queue.
Conclusion: SCADA Value, Delivered Now
The purpose of SCADA has always been to give operators visibility and control over their infrastructure in real time. That purpose has not changed. What has changed is the set of technologies available to deliver it.
ThingsLog represents the maturation of a model in which the value of operational telemetry — real-time data, automated alarms, remote control, system integration — is decoupled from the civil infrastructure that traditional SCADA required to produce it. By combining battery-powered, multi-network field hardware with a cloud analytics and automation platform, ThingsLog delivers the full SCADA functional stack over wireless networks that operators do not need to build or maintain.
The cables that used to have to cross the railway line do not get crossed. The road does not get dug up. The river does not get drilled under. The cabinet does not go on the concrete pad. The mains connection does not get negotiated. The manhole does not get installed. And the monitoring point goes live this week, not next year.
That is what over-the-top SCADA means in practice. And for the operators who have been watching their infrastructure age while waiting for a traditional SCADA project to clear its permitting backlog, it is not an incremental improvement. It is a different category of solution entirely.
ThingsLog provides industrial IoT monitoring hardware and cloud software for water utilities, energy managers, facility operators, and infrastructure owners across Central and Eastern Europe and beyond. To discuss a specific deployment scenario, contact the ThingsLog team at sales@thingslog.com.
