PLC Simulator
SCADA Training

SCADA Training — The PLC Layer That Drives Every System

Every SCADA system reads from a PLC. Master the controller logic, tag databases, HMI binding, alarm rungs, and Modbus communications that SCADA engineers must know — free, in your browser, no install.

Start freeRun your first PLC program — no signup

Join 13400+ learners practicing PLC programming

SCADA training — PLC ladder logic and HMI tag binding in the browser

Foundations

What is SCADA — and how it differs from HMI and PLC

SCADA stands for Supervisory Control and Data Acquisition. It is the software layer that sits above the controllers on a plant or utility network: it acquires live data from PLCs and RTUs across the site, presents it to operators on graphical screens, logs it to a historian for trends and reports, raises and manages alarms, and sends operator commands and setpoints back down to the controllers.

People often blur three terms. A PLC (Programmable Logic Controller) is the hardware that runs control logic in real time — it decides. An HMI (Human-Machine Interface) is typically a single screen at one machine for a local operator. SCADA is the site-wide supervisory system that may aggregate dozens of HMIs and PLCs, add historian and alarm-management infrastructure, and span control rooms. Put simply: the PLC controls, the HMI displays one machine, and SCADA supervises the whole site. And no — SCADA is not the same as a PLC; SCADA reads from PLCs and cannot run without them.

SCADA runs the systems behind manufacturing lines, power transmission and distribution, water and wastewater treatment, oil and gas pipelines, and building management. Because those are critical-infrastructure sectors, modern SCADA work increasingly includes OT cybersecurity (IEC 62443 segmentation, hardening, patch management) alongside the control engineering — a discipline that sits next to, not inside, the PLC layer this platform teaches.

From field signal to operator decision

See how a SCADA system moves, presents and diagnoses industrial data

These six views connect the physical process to the PLC, network, HMI, historian and troubleshooting workflow. They are the mental models you need before vendor-specific screen building becomes useful.

SCADA system architecture for two remote water pumping stations showing field instruments, PLC and RTU panels, industrial network, firewall, historian and operator HMI
01Follow the control path from dispersed field instruments through local PLCs and RTUs to the SCADA server, historian and operator workstations.
SCADA tag lifecycle showing a tank level transmitter, analog input, scaled PLC tag, communication gateway and HMI trend
02A useful SCADA tag starts as a physical measurement, becomes a raw input, is scaled in the PLC and only then reaches the HMI with engineering units and context.
High performance SCADA HMI showing one high-level alarm, first-out indication, alarm summary and operator response workflow
03Alarm handling is a workflow: detect, notify, investigate, acknowledge after validation, correct the cause and confirm the process has recovered.
SCADA historian trend analysis comparing tank level, valve command, pump current and pump trip alarm in time order
04Historian evidence turns an alarm into a diagnosis by aligning process values, commands, equipment current and event timestamps.
Modbus TCP training diagram showing a PLC server, SCADA client, managed switch, request and response packets, coils and register data types
05Modbus TCP carries addressed data between a client and server; coils, discrete inputs, input registers and holding registers have different access semantics.
SCADA stale tag troubleshooting workflow tracing HMI quality through server, network, PLC, I O module and field temperature transmitter
06A stale display is not automatically a bad sensor. Diagnose the chain in order: tag quality, server path, network, PLC state, I/O update and field signal.

Standards-backed definition

What this course means by SCADA

NIST distinguishes SCADA systems from other industrial control systems by their use for geographically dispersed assets with centralised data acquisition and supervisory control. PLCs execute the local control application; SCADA collects and presents the wider operating picture. That distinction is why this course starts with trustworthy PLC tags, alarms and communications instead of treating SCADA as screen design alone.

The Modbus Organization defines Modbus as an application-layer client/server protocol. In practice, a SCADA driver requests addressed coils, discrete inputs, input registers or holding registers from a PLC or gateway. Learning what each data type represents—and how to verify its source—prevents attractive screens built on ambiguous or stale data.

This platform teaches the controller-facing foundation hands-on: logic, tag design, HMI binding, alarm behaviour, trends and protocol concepts. It does not claim to replace production work on redundant SCADA servers, historian administration, site cybersecurity controls or a vendor's engineering environment.

The architecture

The SCADA stack you train on, illustrated

Each diagram is a layer SCADA training has to cover — from the field I/O and controller up to the operator screen and the network that connects them. Everything below the screen is what this platform teaches hands-on.

A SCADA and HMI screen reading live PLC tags — pushbuttons, pilot lamps, numeric displays, trends and alarms bound to controller memory, the supervisory layer SCADA training coversA SCADA supervisory layer above a PLC, an operator HMI panel beside the PLC, and the PLC wired down to field devices such as sensors and a motor.SCADAsupervisory layerHMI panelPLCcontrollerSMfield devices (sensors, motor)
The supervisory screen — widgets bound to live PLC tags.
An industrial SCADA network topology — multiple PLCs and RTUs reporting to a SCADA server over Ethernet, the site-wide architecture a SCADA engineer designsAn industrial Ethernet/IP or PROFINET network: a PLC, operator HMI, a variable frequency drive and remote I/O all connected through a network switch.SWITCHEthernet/IP · PROFINETPLCHMIVFDI/Ostar topology via managed switch
Site-wide topology — PLCs and RTUs reporting to the SCADA server.
The PLC architecture underneath a SCADA system — CPU, power supply, digital and analog I/O modules and the Ethernet port the SCADA server pollsA modular PLC rack on a backplane: power supply, CPU processor, input module, output module and a communications module side by side.PLC RACKbackplane busPSUPowerCPUProcessorDIInputDOOutputNETComms
The controller SCADA reads from — CPU, I/O modules, comms port.
A Modbus TCP transaction between a SCADA master and a PLC slave, reading coils and holding registers — the most common protocol connecting PLCs to SCADAA Modbus master polling three slave devices over a shared serial or TCP link, reading and writing their holding registers and coils.MASTERpolls slavesModbus RTU / TCPID 01regs/coilsID 02regs/coilsID 03regs/coilsrequest / response polling
Modbus TCP — coils and registers the SCADA driver polls from the PLC.
Analog I/O scaling for SCADA — a raw 4-20 mA sensor value converted to engineering units for trends and displays on the SCADA screenA 4 to 20 milliamp analog signal from a sensor, read by the analog input card and scaled linearly into engineering units such as degrees Celsius.sensor4-20mAAI cardADC62.5deg C (scaled)10004mA20mAlinear scaling
Analog scaling — raw counts to engineering units for SCADA trends.
The PLC scan cycle that produces the tag values a SCADA system samples — read inputs, execute logic, update outputs, repeatThe repeating PLC scan cycle: read inputs, execute the ladder logic, update outputs, then housekeeping, looping continuously.1Read Inputs2Execute Logic3Update Outputs4HousekeepingSCANCYCLE
The scan cycle — the real-time loop SCADA samples tag values from.
A ladder logic alarm rung whose latched output becomes a SCADA alarm tag, showing how PLC logic feeds the SCADA alarm systemA basic ladder logic rung between two power rails: an examine-if-closed contact (XIC) in series driving an output coil (OTE).L1L2] [StartXIC I:0/0LampOTE O:0/0
Every SCADA alarm starts as a PLC rung — the logic you write here.
A browser-based SCADA and PLC practice environment with no Ignition or WinCC license and no install required on any operating systemA web browser window running a PLC ladder logic simulator with an input/output strip, requiring no installation or download.plcsimulator.app/playno installINPUTSOUTPUTS
All in a browser tab — no Ignition or WinCC licence, no install.

Skills matrix

What SCADA roles actually need

"SCADA training" covers a spectrum from HMI operator to full SCADA architect. The table below maps each role to the PLC skills and SCADA software skills required — and marks what this platform covers.

RolePLC skills neededSCADA software skills neededCovered here
SCADA OperatorRead P&IDs; understand what PLC outputs correspond to which field devicesNavigate HMI screens; acknowledge alarms; escalate correctlyP&ID reading concepts, HMI widget behavior
Controls TechnicianRead and modify PLC ladder logic; trace I/O faults; use force bitsConfigure alarm setpoints; add trend pens; verify tag valuesFull ladder logic, I/O addressing, troubleshooting methodology
Controls EngineerDesign tag database; write sequencer logic; configure PID loops; program ModbusConfigure OPC-UA server; build historian; design alarm philosophyTag design, PID, Modbus TCP register maps, alarm logic patterns
SCADA EngineerSame as Controls Engineer plus communication protocol troubleshootingIgnition/WinCC screen design; redundancy configuration; security hardeningPLC side fully; SCADA-software side: conceptual only

What you learn

How our scenarios teach the PLC side of SCADA

A 170-scenario catalogue and 55 guided learning modules cover the PLC layer every SCADA system depends on. The most SCADA-relevant topics:

Tag databases and I/O mapping

Every SCADA tag maps to a PLC memory address. Learning to design a clean tag database — input bits, output bits, internal flags, integer registers, timer accumulators — is the most transferable SCADA skill. Covered across the fundamentals lessons and every scenario.

PLC Fundamentals lesson →

HMI screen building with live tag binding

The HMI Builder lets you place pushbuttons and pilot lamps on a canvas, bind each to a PLC tag, and run them against the live simulation. This is the same widget-binding model used in FactoryTalk View and WinCC — different product names, same underlying concept.

HMI Simulator →

Alarm logic in the PLC layer

The ISA-18.2 alarm management standard requires safety-critical alarms to be in the PLC, not only in the SCADA software. The alarms lesson and fault-injection scenarios cover latching alarm rungs, acknowledge/reset logic, and priority-based alarm shelving patterns.

Alarms lesson →

Modbus TCP register maps

Modbus is the most common protocol connecting PLCs to SCADA systems in legacy and new installations. The Modbus TCP lesson covers coil registers (0x), discrete inputs (1x), holding registers (4x), and the read/write function codes that a SCADA driver uses. You will understand exactly what the SCADA system is reading when you configure a Modbus device driver.

Modbus TCP lesson →

PID loop control and SCADA setpoints

SCADA operators change PID setpoints from the control room screen. Understanding the P, I, and D contributions, the output clamp, and the bumpless transfer between manual and auto mode is essential for anyone who configures PID loops or supports operators using them. Covered in the PID lesson and the PID temperature scenario.

PID temperature scenario →

Communications: OPC-UA and protocol concepts

OPC-UA is the modern successor to OPC-DA for SCADA connectivity. The communications lessons cover the client-server model, address space browsing, and how a SCADA historian subscribes to OPC-UA nodes. Conceptual — no live OPC server — but sufficient to understand what you are configuring in Ignition or WinCC.

Lesson library →

Honest scope

What this platform does NOT teach

Most training platforms oversell their scope. Here is an honest list of what you will still need elsewhere after completing this curriculum:

  • ✗Ignition screen building — Inductive Automation's Perspective and Vision modules require hands-on time in Ignition Designer. Their free online training resources cover this well.
  • ✗WinCC Unified / WinCC flexible — Siemens HMI configuration inside TIA Portal requires a TIA Portal license. The TIA Portal evaluation license is free for 21 days.
  • ✗Wonderware / AVEVA System Platform — a proprietary system with no free tier. Training through AVEVA partners only.
  • ✗SCADA cybersecurity (IEC 62443) — network segmentation, firewall rules, patch management, and industrial DMZ design. This is a separate discipline; the ISA/IEC 62443 qualification path covers it.
  • ✗Physical wiring and I/O commissioning — no browser simulator replaces wiring a real PLC input card to a field device. Hands-on lab time at a college, training center, or on the job is required.

SCADA platforms

WinCC, Ignition, and Wonderware SCADA training

These are the most searched SCADA platform names. Here is an honest summary of what we cover for each.

Partial — PLC side

WinCC SCADA training

WinCC runs inside TIA Portal and reads Siemens PLC tags directly. This platform teaches Siemens TIA Portal-style ladder logic (FB/FC structure, DB organization, network programming), which is the PLC knowledge a WinCC integrator needs. WinCC screen design and driver configuration require TIA Portal — use the Siemens evaluation license.

Siemens PLC training →

Partial — PLC side

Ignition SCADA training

Ignition (Inductive Automation) is platform-agnostic — it connects to any PLC via OPC-UA, Modbus, or a vendor driver. The PLC programming skills and Modbus register concepts here transfer directly to configuring Ignition device connections. Ignition-specific training (Perspective, Reporting, Historian) is best through Inductive Automation's free online courses.

PLC training curriculum →

Foundation only

Wonderware / AVEVA training

Wonderware System Platform (now AVEVA) is common in oil and gas, chemicals, and utilities. The PLC programming and tag architecture knowledge from this platform applies. Wonderware-specific Object-Oriented configuration requires AVEVA's proprietary training program — no free tier exists.

Stay on this page →

Keep learning

Related training on this platform

Start the PLC foundation every SCADA role requires.

Free account. Browser-based. Guided paths and a 170-scenario catalog — no install or credit card to start.

Start freeRun your first PLC program — no signup
Questions

SCADA training — frequently asked questions

SCADA training teaches you to design, configure, and operate Supervisory Control and Data Acquisition systems — the software layer that reads PLC tags, displays operator screens, logs trend data, and raises alarms. Good SCADA training covers both the PLC controller layer (ladder logic, tag databases, I/O mapping) and the supervisory software layer (screen building, driver configuration, historian setup).

Competency and practice field guide

SCADA training: practice plan

Direct answer

The learner can trace a field value into a trustworthy display, diagnose data quality and test operator response to abnormal conditions.

Written for operators, technicians and controls engineers learning tags, alarms, trends, communications and supervisory control.

System map / 02

NODE 01observable

Scope

Operator tasks, controlled process, tag contract and abnormal response.

NODE 02observable

Signal path

PLC values through communications, quality, server state and HMI objects.

NODE 03observable

Baseline practice

Commands, status, alarms and trends with correct timestamps.

NODE 04observable

Edge cases

Stale data, communication loss, role limits and restart.

NODE 05observable

Fault practice

A mapping, quality, alarm or process-feedback fault.

NODE 06observable

Transfer to the job

Tested displays and procedures reviewed in the production stack.

Continue the signal path / 08

HMI and SCADA learning path

Link PLC state to a usable operator experience

Build the control state first, bind clear tags, then practice alarms, trends and operator decisions against a running process.