The plant is healthy. Is the SCADA system running it?
Levels, pumps and breakers are watched every minute of every day. The servers, licences, backups, alarms and remote access that make up the SCADA system itself are often looked at once a year, or when something breaks.
This site sets out what managing a SCADA system actually involves, so it stays secure, supportable and ready for its next upgrade.
| Pri | Source | Message |
|---|---|---|
| 2 | Servers | Operating system out of vendor support in 212 days |
| 2 | Servers | Last restore test 14 months ago |
| 3 | WTP2 RTU | 3 vendor remote-access accounts not reviewed |
What managing a SCADA system covers
Ten areas, each small on its own. Neglect any of them for a few years and it becomes the reason an upgrade overruns, an outage lasts a day instead of an hour, or an auditor finds a remote-access account nobody remembers creating.
- Asset register and architecture
- Every server, workstation, PLC, RTU, network device, licence and software version, with firmware levels and support dates, plus an architecture drawing that matches reality. Everything else on this list depends on it.
- Change control
- Every configuration, database and logic change is recorded, reviewed, tested away from production where possible, and reversible. You can always answer who changed what, when and why.
- Backups and recovery
- Full images and configuration exports for servers, controllers and network devices, stored off the system and restored on a schedule. A backup that has never been restored is a hope, not a plan.
- Patching and obsolescence
- Vendor-qualified patches applied on a planned cycle, and end-of-support dates for the platform, operating systems and hardware tracked years ahead, so a migration is budgeted rather than forced.
- Alarm management
- An alarm philosophy, rationalised alarms with a defined priority and response, and regular review of floods, chattering and standing alarms, following ISA-18.2 / IEC 62682. Operators should trust every alarm they see.
- Cybersecurity
- Zones and conduits, hardened hosts, managed accounts and privileges, monitoring and a rehearsed incident response, measured against IEC 62443 and, for Australian critical infrastructure, the SOCI Act.
- Remote access
- Every vendor and engineer route into the system is known, approved, time-limited, logged and reviewed. Forgotten remote access is one of the commonest ways into an operational network.
- Vendor and support arrangements
- Who fixes what, how fast and under which contract, with licence renewals, spares holdings and an escalation path that works at 2 a.m. on a public holiday.
- Historian and data
- Tag naming, retention, data quality and the interfaces that feed operational reports, compliance returns and enterprise systems, built without opening new paths into the control network.
- People and knowledge
- Current documentation, trained operators and engineers, and no single person who is the only one who knows how the system really works.
A SCADA system's life, and where management fits
Most of a system's cost and risk sits in the long middle of its life, not in the project that delivered it. Management is what keeps that middle stretch healthy and makes the last step a choice rather than an emergency.
Requirements and concept
What the system must monitor and control, for whom, and to what security level.
Design and build
Platform, architecture, telemetry, displays and alarms, with security designed in.
Test and commission
Factory and site acceptance, cutover planning and operator training.
Operate and maintain
Fifteen to twenty-five years of the ten areas above. This is where management lives.
Review and improve
Performance reviews, alarm rationalisation, security assessments and tuning.
Migrate or renew
Planned replacement with parallel running and a tested rollback.
Common questions
What is a SCADA system?
SCADA (supervisory control and data acquisition) is the software, servers, networks and field devices that let operators monitor and control equipment spread across many sites, such as reservoirs, pump stations, substations, pipelines and solar farms, from a central control room. operationaltechnology.au explains SCADA, PLCs, RTUs and the wider world of operational technology in more depth.
What does a SCADA manager do?
A SCADA manager looks after the SCADA system as an asset in its own right: keeping it documented, backed up, patched, secure and supported, controlling changes to it, keeping alarms useful, managing who can reach it remotely, and planning its renewal before the platform or hardware runs out of support. In smaller organisations this is part of an engineer's or operations manager's role rather than a job title.
How is managing SCADA different from managing IT?
Availability and safety come first, so servers cannot simply be rebooted or patched on a monthly cycle. Patches usually need vendor qualification, systems stay in service for 15 to 25 years, and a configuration change can move real equipment. Change control, testing and recovery planning matter more than in most IT environments.
Which standards apply to managing a SCADA system?
IEC 62443 for industrial cybersecurity (iec62443.au explains every part and the security levels), ISA-18.2 / IEC 62682 for alarm management and ISA-101 for operator displays. In Australia, owners of critical infrastructure assets also have obligations under the Security of Critical Infrastructure (SOCI) Act, and energy businesses commonly use the AESCSF.
When should a SCADA system be replaced?
Start planning when the platform, operating system or server hardware has an end-of-support date within about five years, when spares or skills are getting hard to find, or when the system cannot meet current security requirements. A planned migration with parallel running is far cheaper and safer than a forced one after a failure.
Need a hand with yours?
SCADA Manager is written by Adam Woodland, an independent OT/ICS cybersecurity and SCADA consultant with more than 25 years across water, energy and transport in Australia and the UK, and an ISA/IEC 62443 Expert.
That covers SCADA health checks and performance reviews, Geo SCADA (ClearSCADA) expertise, platform migrations, alarm rationalisation, remote-access reviews and IEC 62443 security assessments.