What SCADA does
SCADA stands for supervisory control and data acquisition. In plain terms, it lets a small team watch and run equipment spread across many sites from one place. Each site has a controller, usually a PLC or remote terminal unit (RTU), that runs the local equipment. SCADA collects data from all of them, stores the history, shows it on screens and sends alarms to whoever is on call.
Municipal water and wastewater systems, irrigation districts, oil and gas operators, agricultural operations and owners of multiple buildings all use some form of SCADA or remote monitoring.
Choosing how sites communicate
In rural Alberta and BC, communications are often the hardest part of the design. Common options:
| Link | Strengths | Watch for |
|---|---|---|
| Cellular | Easy to deploy where coverage is good; good bandwidth | Coverage gaps, carrier network changes, data plans |
| Licensed or unlicensed radio | Owner-controlled, no monthly carrier fee | Needs line of sight or repeaters; path study required |
| Satellite | Works almost anywhere | Latency, cost per data and weather effects |
| Fibre or wired | Fast and reliable | Only practical where it already exists or is close |
Many systems use a primary and a backup link for critical sites. Ask for a coverage or radio path survey before choosing, rather than assuming a phone shows enough bars.
Protocols you may hear about include Modbus, DNP3 and MQTT. DNP3 and similar protocols support time-stamped data and report-by-exception, which helps when bandwidth is limited and you need to know exactly when something happened.
Designing for remote and cold
A remote site may be hours away and visited weekly or less, so the hardware has to look after itself.
- Power: battery backup sized to keep communications and key alarms alive through an outage; solar where there is no grid.
- Heat: enclosure heaters and insulation so electronics, batteries and displays stay within their rated range.
- Self-monitoring: alarms for power failure, low battery, high or low enclosure temperature, intrusion and communication loss.
- Local control: the site should keep running safely if communications fail, not wait for instructions.
- Surge and lightning protection on power, antenna and field wiring.
Alarms that people trust
A SCADA system lives or dies on its alarms. Too many nuisance alarms and on-call staff start ignoring them; too few and something important is missed.
- Give each alarm a clear priority and a response.
- Use delays and deadbands to stop chattering alarms.
- Route alarms to the right person, with escalation if nobody acknowledges.
- Review alarm history regularly and fix the worst offenders.
Schedule a test alarm each month to prove that phones, texts or calls actually reach the on-call person. Carrier and contact list changes break call-outs quietly.
History, reports and compliance
The historian is the quiet workhorse of a SCADA system. It stores every value and alarm with a time stamp, which turns into:
- Daily and monthly reports for flows, levels, run hours and energy use
- Evidence for regulators where reporting is required, for example on some water and wastewater systems
- Maintenance insight, such as pumps whose run time is creeping up as they wear
- Answers after an incident: what happened, in what order, and when
Make sure the historian is backed up and that time stamps come from the remote sites where possible, not just from when the server received the data. When a link drops and catches up later, that difference matters. If you have reporting obligations, confirm with your regulator what records you must keep and for how long, then set retention to match.
Security for remote access
Remote access is the point of SCADA and also its biggest risk. Avoid exposing controllers directly to the internet, use encrypted connections, give each person their own login, and keep track of who has access. Our guide on cybersecurity for building and plant controls covers the basics.
Starting pumps or opening valves remotely must never bypass local safety interlocks. People working at a site need lockout procedures that remote operators cannot override.
Getting started
Start small if you need to: monitoring a few critical alarms by cellular is far better than a weekly drive-by. A well-designed system can grow into full SCADA later. Our SCADA and remote monitoring team designs, builds and services remote systems, including the PLC systems and UPS systems at each site.
Common questions
What is the difference between a PLC and an RTU?
Both are controllers at a site. RTUs are designed around remote communication, low power and data logging; PLCs are designed around local control. Modern products overlap heavily.
Can we add monitoring to an old lift station without replacing everything?
Often yes. A small controller or cellular gateway can read existing alarms and signals and report them, leaving local controls in place until a larger upgrade.
What happens if the cellular network goes down?
A well-designed site keeps running under local control, logs data, and reports communication loss as an alarm. A backup link can be added for critical sites.
Who owns the data?
You should. Make sure contracts give you access to the historian data and the configuration, regardless of who hosts the server.
Codes and permit rules change and every building is different. For work on your system, talk to a licensed electrician and your local permit authority.