Edge computing in SCADA in SCADA systems - Step-by-Step Execution

Process Flow - Edge computing in SCADA

Data generated by sensors

↓

Edge device collects data

↓

Edge device processes data locally

↓

Immediate action

↓

Local control

↓

Feedback loop

Data flows from sensors to edge devices where it is processed locally for quick actions, then summarized data is sent to the central SCADA system for monitoring.

Execution Sample

SCADA systems

Sensor -> Edge Device -> Local Processing -> Action or Send to SCADA

Shows the path of data from sensor through edge device processing to local action or central SCADA.

Process Table

Step	Action	Data State	Result
1	Sensor generates raw data	Raw sensor data	Data ready for edge device
2	Edge device receives data	Raw sensor data	Data stored locally
3	Edge device processes data	Raw sensor data	Processed data (e.g., anomaly detected)
4	Edge device triggers immediate action	Processed data	Local control activated
5	Edge device sends summary to SCADA	Processed data summary	Central SCADA updated
6	SCADA system analyzes summary	Summary data	Operator alerted if needed
7	Feedback sent to edge device	Control commands	Edge device adjusts operations
8	End of cycle	N/A	Waiting for next sensor data

💡 Cycle ends waiting for new sensor data to start again

Status Tracker

Variable	Start	After Step 2	After Step 3	After Step 5	Final
Raw sensor data	None	Received	Processed	Summarized	Waiting
Processed data	None	None	Available	Sent to SCADA	Used for control
Local control state	Inactive	Inactive	Inactive	Activated	Active
SCADA summary	None	None	None	Received	Analyzed

Key Moments - 3 Insights

Why does the edge device process data before sending it to SCADA?

Processing at the edge reduces data sent over the network and allows faster local responses, as shown in steps 3 and 4 of the execution table.

What happens if the edge device detects an anomaly?

It triggers immediate local control actions (step 4) before sending a summary to SCADA (step 5), ensuring quick response.

Why does SCADA only receive summarized data, not raw data?

To reduce network load and focus on important information, SCADA receives processed summaries (step 5), not all raw data.

Visual Quiz - 3 Questions

Look at the execution table, at which step does the edge device activate local control?

A Step 2

B Step 5

C Step 4

D Step 6

💡 Hint

Check the 'Result' column for local control activation in the execution table.

According to the variable tracker, what is the state of 'Processed data' after step 3?

A None

B Available

C Sent to SCADA

D Waiting

💡 Hint

Look at the 'Processed data' row under 'After Step 3' in the variable tracker.

If the edge device did not process data locally, how would the execution table change?

A Step 3 would be skipped, and raw data sent directly to SCADA

B Step 4 would trigger more local actions

C SCADA would not receive any data

D Sensor would generate no data

💡 Hint

Consider the role of step 3 in processing before sending data to SCADA.

Concept Snapshot

Edge computing in SCADA:
- Sensors generate data
- Edge devices process data locally
- Immediate local actions reduce delays
- Summarized data sent to central SCADA
- SCADA monitors and sends feedback
- Improves speed and reduces network load

Full Transcript

Edge computing in SCADA means data from sensors is first handled by nearby edge devices. These devices process data locally to detect issues quickly and act immediately if needed. Then, they send only summarized information to the central SCADA system for monitoring. This approach speeds up responses and reduces the amount of data sent over the network. The SCADA system can then analyze summaries and send commands back to edge devices to adjust operations. This cycle repeats continuously as new sensor data arrives.