JoeGuardian Automation

33. SCADA vs HMI vs PLC (33 of 41)

---

In industrial automation, three terms appear everywhere:

PLC
HMI
SCADA

They are connected, but they are not the same thing.

A PLC controls the machine.
An HMI allows the operator to interact with the machine.
SCADA supervises, monitors, trends, alarms, and collects data across a larger system.

A simple way to remember:

PLC controls. HMI operates. SCADA supervises.

Understanding the difference helps automation technicians troubleshoot communication problems, machine faults, alarm issues, data problems, and control system architecture.

---

1. What Is a PLC?

A PLC, or Programmable Logic Controller, is the industrial controller that directly controls the machine or process.

The PLC reads inputs, executes logic, and controls outputs.

Basic PLC flow:

Inputs → PLC Logic → Outputs

The PLC connects to:

Sensors
Push buttons
Limit switches
Photoeyes
Analog transmitters
VFDs
Remote I/O
Relays
Solenoids
Motor starters
Valves
Safety status signals

The PLC is where the real control decisions happen.

Example:

Photoeye detects box
     ↓
PLC input turns ON
     ↓
PLC logic evaluates sequence
     ↓
PLC output starts conveyor or reject device

---

2. What Is an HMI?

An HMI, or Human Machine Interface, is the operator interface.

It allows humans to see machine status and send commands to the PLC.

An HMI may show:

Machine running
Machine stopped
Faults
Alarms
Current mode
Production count
Setpoints
Manual controls
Recipe selection
Sensor status
Motor status

An HMI may allow the operator to:

Start machine
Stop machine
Reset faults
Select Auto or Manual mode
Jog devices
Change setpoints
Acknowledge alarms
View diagnostics

Important:

The HMI should not directly control the machine without PLC logic validating the command.

The HMI sends requests.

The PLC decides if those requests are allowed.

Example:

Operator presses Start on HMI
     ↓
HMI writes Start_Request tag
     ↓
PLC checks permissives, interlocks, faults, mode, and safety status
     ↓
PLC starts machine only if allowed

---

3. What Is SCADA?

SCADA means Supervisory Control and Data Acquisition.

SCADA is usually a larger system used to monitor and supervise multiple machines, lines, utilities, or process areas.

SCADA may include:

Server
Client workstations
Historian
Alarm server
Database
Reports
Trends
Dashboards
Remote operator stations
Engineering tools

SCADA is commonly used for:

Plant-wide monitoring
Alarm history
Trends
Reports
Batch records
Utilities monitoring
Production dashboards
Energy monitoring
Water systems
Process overview
Remote supervision

SCADA usually communicates with PLCs and other controllers to collect data and sometimes send supervisory commands.

---

4. Simple Difference

System	Main Role	Typical Location	Main User
PLC	Controls machine/process	Control panel	Technician / PLC logic
HMI	Operator interface for one machine or line	Machine panel / operator station	Operator
SCADA	Supervises larger system and collects data	Control room / server / plant network	Operators, supervisors, engineers

Simple memory:

PLC = control
HMI = operation
SCADA = supervision and data

---

5. Industrial Architecture Example

A simple architecture may look like this:

Field Devices
     ↓
PLC / Remote I/O
     ↓
HMI
     ↓
SCADA
     ↓
Historian / Reports / Dashboards

More detailed:

Sensors / Motors / VFDs / Valves
        ↓
PLC I/O and Logic
        ↓
PanelView or Machine HMI
        ↓
SCADA Server
        ↓
Historian / Alarm Database / Reports

Each layer has a role.

The field devices interact with the real process.
The PLC controls the process.
The HMI gives local operator control.
SCADA gives higher-level visibility.

---

6. PLC Responsibilities

The PLC should handle:

Real-time control
Inputs and outputs
Sequences
Permissives
Interlocks
Fault handling
Motor control
Valve control
Analog scaling
State machines
Safety status monitoring
Machine commands
Feedback validation

The PLC should remain the authority for machine control.

Example:

Even if the HMI sends Start_Request,
the PLC decides if Start_Command is allowed.

This is important for safe and predictable operation.

---

7. HMI Responsibilities

The HMI should handle:

Operator screens
Start/stop requests
Mode selection requests
Fault display
Alarm banners
Manual controls
Setpoint entry
Recipe selection
Production count display
Machine status
Diagnostic screens

A good HMI should explain what is happening.

Bad HMI message:

Fault 47

Better HMI message:

Conveyor Motor Feedback Fault
Motor was commanded ON but running feedback did not return within 3 seconds.
Check overload, VFD status, contactor, feedback wiring, or motor starter.

The HMI is not just a screen.

It is a troubleshooting tool.

---

8. SCADA Responsibilities

SCADA should handle:

Plant-wide visualization
Multiple PLC connections
Alarm summary
Alarm history
Trends
Reports
Historical data
Production dashboards
Operator workstations
Data logging
Remote supervision
Utility monitoring
Process overview

SCADA is especially useful when one system needs to monitor many machines or process areas.

Example:

One SCADA system monitors:
- Boiler system
- Water system
- Pasteurizer
- Fillers
- Packaging lines
- Tank farm
- Air compressors

---

9. HMI vs SCADA

HMI and SCADA can look similar because both use screens.

But their scope is different.

HMI

Usually local to a machine or line.

Example:

PanelView on a filler
HMI on a wrapper
Touchscreen on a palletizer

SCADA

Usually supervises many systems.

Example:

Control room application monitoring all production lines
Ignition dashboard showing plant utilities
FactoryTalk View SE client monitoring multiple PLCs

Simple difference:

HMI = local machine interface
SCADA = plant-wide or system-wide supervision

---

10. HMI vs PLC

A common mistake is thinking the HMI controls the machine directly.

Better concept:

HMI sends requests.
PLC validates and controls outputs.

Example:

HMI_Start_Button = request
PLC_Start_Permissive_OK = validation
Motor_Run_Command = actual PLC command

The HMI button should not directly energize an output.

Bad structure:

HMI button → physical output

Better structure:

HMI button → request bit → PLC logic → command bit → physical output

This keeps the machine safe and predictable.

---

11. SCADA vs PLC

SCADA should not replace PLC control logic.

SCADA may send supervisory commands, but the PLC should still protect the machine.

Example:

SCADA requests pump start
     ↓
PLC checks permissives
     ↓
PLC starts pump only if safe

SCADA may be slower, network-dependent, and not designed for direct high-speed machine control.

The PLC should handle fast and critical control.

SCADA should handle monitoring, trends, alarms, supervisory commands, and data.

---

12. Communication Between PLC, HMI, and SCADA

Communication may happen using:

EtherNet/IP
Modbus TCP
Profinet
OPC UA
OPC DA
Serial protocols
Vendor-specific drivers

Common examples:

PanelView Plus ↔ Allen-Bradley PLC
FactoryTalk View ↔ PLC through FactoryTalk Linx
Ignition SCADA ↔ PLC through OPC UA or device driver
SCADA Historian ↔ PLC tags

The HMI or SCADA reads and writes PLC tags.

Example tags:

Machine_Running
Machine_Faulted
Start_Request
Reset_Request
Tank_Level_Pct
Pressure_PSI
Motor_Run_Status
Alarm_Active

---

13. Data Flow Example

Example: Tank level monitoring.

Level transmitter measures tank level
     ↓
PLC analog input reads 4–20 mA
     ↓
PLC scales raw value to Tank_Level_Pct
     ↓
HMI displays Tank Level = 65%
     ↓
SCADA logs tank level trend
     ↓
Historian stores data for reports

The same value may exist in multiple layers, but the source of truth usually starts in the PLC or instrument.

---

14. Alarm Flow Example

Example: Motor overload fault.

Overload contact opens
     ↓
PLC input changes
     ↓
PLC latches Motor_Overload_Fault
     ↓
HMI displays active fault
     ↓
SCADA logs alarm history
     ↓
Operator or technician corrects issue
     ↓
Reset request sent
     ↓
PLC clears fault only if safe

The HMI and SCADA display the fault.

The PLC controls the fault logic.

---

15. Common Troubleshooting Problems

Problem 1 — HMI button does not work

Possible causes:

HMI not communicating
HMI tag wrong
PLC request bit not changing
PLC in wrong mode
Permissive missing
Interlock active
Fault active
PLC logic blocking command

Troubleshooting path:

Press HMI button
Check PLC request tag
Check mode
Check permissives
Check interlocks
Check command bit
Check output

---

Problem 2 — HMI shows wrong value

Possible causes:

Wrong HMI tag
PLC scaling wrong
Analog input issue
Communication delay
Wrong engineering units
Old screen object linked to wrong tag

Troubleshooting path:

Compare HMI value to PLC tag
Check raw analog value
Check scaling
Check HMI tag reference
Check instrument signal

---

Problem 3 — SCADA trend is missing data

Possible causes:

SCADA communication issue
Historian service stopped
Wrong tag path
PLC offline
Network issue
Data logging disabled
Tag renamed

Troubleshooting path:

Check PLC online status
Check SCADA communication
Check tag path
Check historian status
Check network connection
Check alarm/event logs

---

Problem 4 — SCADA alarm appears but HMI does not

Possible causes:

Different alarm configuration
Different tags used
HMI alarm not configured
SCADA alarm based on historian or calculated tag
Communication differences

The technician must verify which system generated the alarm.

---

16. Local Control vs Supervisory Control

A good architecture separates local and supervisory control.

Local control

Handled by PLC and HMI.

Examples:

Start conveyor
Jog motor
Open valve
Reset local fault
Manual control
Machine sequence

Supervisory control

Handled by SCADA.

Examples:

Start batch
Monitor line status
Collect data
View trends
Generate reports
Coordinate multiple systems

SCADA may request actions, but the PLC should validate and execute them.

---

17. Security Considerations

PLC, HMI, and SCADA systems are part of the OT environment.

Good practices include:

Limit who can change setpoints
Use user roles on HMI
Control remote access
Avoid direct IT-to-PLC access
Segment networks
Use backups
Document IP addresses
Restrict engineering software access
Log operator actions when needed

A bad architecture can allow unnecessary access to critical control systems.

A good architecture uses controlled communication paths.

---

18. Backup Considerations

A technician should understand that PLC, HMI, and SCADA backups are different.

PLC backup

Contains:

PLC program
Tags
Logic
I/O configuration
Controller settings

HMI backup

Contains:

Screens
Buttons
Alarm displays
Tag references
User security
Runtime application

SCADA backup

May contain:

Projects
Gateway configuration
Alarm pipelines
Historical database configuration
Client screens
Device connections
Scripts
Reports
Tags

When troubleshooting or replacing hardware, you need the correct backup for the correct layer.

---

19. Technician Checklist

When working with PLC, HMI, and SCADA systems, ask:

Is the PLC online and in RUN mode?
Is the HMI communicating with the PLC?
Is SCADA communicating with the PLC?
Are tags mapped correctly?
Is the HMI showing the correct machine status?
Is SCADA logging trends and alarms?
Are alarms generated in PLC, HMI, or SCADA?
Are commands validated by PLC logic?
Are user permissions correct?
Are backups available?
Is the network healthy?

---

20. Common Mistakes

Mistake 1 — Thinking HMI logic replaces PLC logic

The PLC should validate all machine commands.

Mistake 2 — Assuming SCADA directly controls everything

SCADA supervises. PLCs control.

Mistake 3 — Not knowing where an alarm is generated

An alarm may come from PLC logic, HMI configuration, or SCADA alarm rules.

Mistake 4 — Editing the wrong layer

Changing an HMI screen does not change PLC logic.

Changing PLC logic does not automatically fix SCADA trends.

Mistake 5 — No backups

Without backups, replacing hardware becomes much harder.

---

Final Thoughts

PLC, HMI, and SCADA are different layers of an industrial automation system.

Each layer has a purpose.

PLC = controls the machine
HMI = allows local operation and diagnostics
SCADA = supervises, trends, logs, and reports

A strong automation technician understands how these layers communicate and where to troubleshoot.

When something does not work, ask:

Is the issue in the PLC logic?
Is the issue in the HMI screen or tag?
Is the issue in SCADA communication or configuration?
Is the issue in the field device?

That mindset prevents guessing.

PLC controls. HMI explains. SCADA supervises. Together, they form the visibility and control structure of industrial automation.