IIoT integration with SCADA in SCADA systems - Step-by-Step Execution

Process Flow - IIoT integration with SCADA

IIoT Devices Collect Data

↓

Data Sent via Protocols (MQTT/OPC-UA)

↓

SCADA System Receives Data

↓

SCADA Processes and Visualizes Data

↓

Operator Monitors and Controls

↓

Commands Sent Back to IIoT Devices

Data flows from IIoT devices to SCADA via protocols, SCADA processes and visualizes it, then operators can control devices.

Execution Sample

SCADA systems

1. IIoT device sends sensor data via MQTT
2. SCADA subscribes and receives data
3. SCADA updates dashboard
4. Operator sends control command
5. Command sent back to IIoT device

This sequence shows how IIoT devices communicate with SCADA and how control commands flow back.

Process Table

Step	Action	Data/Command	System State	Output/Result
1	IIoT device sends data	Temperature=75°F	Data in MQTT broker	Data published to topic
2	SCADA subscribes to topic	Temperature=75°F	SCADA receives data	Data available for processing
3	SCADA updates dashboard	Temperature=75°F	Dashboard shows 75°F	Operator sees updated value
4	Operator sends command	Set Fan Speed=High	Command queued in SCADA	Command ready to send
5	SCADA sends command to IIoT device	Set Fan Speed=High	IIoT device receives command	Fan speed set to High
6	IIoT device confirms action	Fan Speed=High	SCADA receives confirmation	Operator notified of success
7	Monitoring continues	Temperature=75°F	Continuous data flow	Real-time updates ongoing

💡 Continuous loop; stops when system is turned off or communication lost

Status Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4	After Step 5	After Step 6	Final
Temperature	N/A	75°F	75°F	75°F	75°F	75°F	75°F	75°F
Fan Speed Command	None	None	None	None	High	High	High	High
SCADA Dashboard	Empty	Empty	Shows 75°F	Shows 75°F	Shows 75°F	Shows 75°F	Shows 75°F + Confirmation	Shows 75°F + Confirmation

Key Moments - 3 Insights

Why does SCADA need to subscribe to a topic before receiving data?

SCADA subscribes to the MQTT topic to listen for messages. Without subscribing, it won't receive the IIoT device data. See execution_table step 2 where SCADA subscribes and then receives data.

How does the operator's command reach the IIoT device?

The operator sends a command to SCADA, which queues and then sends it to the IIoT device. This is shown in steps 4 and 5 where the command moves from operator to SCADA to device.

What happens if the IIoT device does not confirm the command?

SCADA will not receive confirmation, so the operator won't see success notification. This can cause alerts or retries. Step 6 shows confirmation; without it, the system knows the command failed.

Visual Quiz - 3 Questions

Look at the execution table, at which step does SCADA update the dashboard with new data?

A Step 2

B Step 3

C Step 4

D Step 5

💡 Hint

Check the 'Action' and 'Output/Result' columns for dashboard updates.

According to the variable tracker, what is the fan speed command after step 4?

A None

B Low

C High

D Medium

💡 Hint

Look at the 'Fan Speed Command' row under 'After Step 4' column.

If the IIoT device never confirms the command, which step's output will not occur?

A Step 6 output

B Step 3 output

C Step 5 output

D Step 2 output

💡 Hint

Check the 'Output/Result' column for step 6 about confirmation.

Concept Snapshot

IIoT devices send data via protocols like MQTT or OPC-UA to SCADA.
SCADA subscribes to receive and process this data.
SCADA visualizes data on dashboards for operators.
Operators send control commands back through SCADA to IIoT devices.
Confirmation from devices ensures command success.
This loop enables real-time monitoring and control.

Full Transcript

This visual execution shows how IIoT devices integrate with SCADA systems. First, IIoT devices collect sensor data and send it using protocols such as MQTT. SCADA subscribes to these data topics to receive the information. Once SCADA gets the data, it updates its dashboard so operators can see real-time values. Operators can then send control commands through SCADA, which forwards them to the IIoT devices. The devices confirm the commands, and SCADA notifies the operator. This cycle continues for ongoing monitoring and control.

Practice

1. What is the main purpose of integrating IIoT devices with a SCADA system?

easy

A. To disconnect sensors from the network

B. To replace SCADA with IIoT devices entirely

C. To enable real-time monitoring and control of industrial processes

D. To increase manual data entry tasks

Solution

1. Step 1: Understand IIoT and SCADA roles

   IIoT devices collect data from machines, and SCADA systems monitor and control processes.

2. Step 2: Identify integration benefits

   Connecting IIoT to SCADA allows real-time data flow for better monitoring and control.

3. Final Answer:

   To enable real-time monitoring and control of industrial processes -> Option C

4. Quick Check:

   IIoT + SCADA = real-time monitoring [OK]

Hint: IIoT integration improves monitoring and control [OK]

Common Mistakes:

• Thinking IIoT replaces SCADA completely
• Assuming integration increases manual work
• Believing sensors get disconnected

2. Which protocol is commonly used to send IIoT device data to a SCADA system?

easy

A. SMTP

B. HTTP

C. FTP

D. MQTT

Solution

1. Step 1: Review common IIoT communication protocols

   MQTT is lightweight and designed for IoT device messaging.

2. Step 2: Match protocol to SCADA data transfer

   MQTT is widely used to send IIoT data to SCADA due to efficiency and reliability.

3. Final Answer:

   MQTT -> Option D

4. Quick Check:

   MQTT is common for IIoT to SCADA data [OK]

Hint: MQTT is the lightweight messaging protocol for IIoT [OK]

Common Mistakes:

• Confusing MQTT with HTTP or FTP
• Choosing protocols not designed for real-time data
• Selecting email protocol SMTP

3. Given this MQTT message payload from an IIoT sensor:
{"temperature": 75, "pressure": 30}
Which SCADA tag mapping is correct to read the temperature value?

medium

A. Tag: sensor.temperature, Value: 75

B. Tag: sensor.pressure, Value: 75

C. Tag: sensor.temperature, Value: 30

D. Tag: sensor.humidity, Value: 75

Solution

1. Step 1: Identify the temperature value in the payload

   The JSON shows "temperature": 75, so temperature is 75.

2. Step 2: Match the tag to the correct value

   The tag sensor.temperature should map to 75, not 30 or other values.

3. Final Answer:

   Tag: sensor.temperature, Value: 75 -> Option A

4. Quick Check:

   Temperature tag matches 75 value [OK]

Hint: Match JSON key to SCADA tag name exactly [OK]

Common Mistakes:

• Swapping temperature and pressure values
• Using wrong tag names like humidity
• Assigning wrong values to tags

4. You configured an OPC UA client to connect IIoT devices to SCADA, but no data appears. What is the most likely cause?

medium

A. Incorrect OPC UA server endpoint URL

B. MQTT broker is down

C. SCADA tags are mapped correctly

D. IIoT devices are powered off but still sending data

Solution

1. Step 1: Check OPC UA client connection settings

   If the server endpoint URL is wrong, the client cannot connect and receive data.

2. Step 2: Rule out unrelated issues

   MQTT broker status is irrelevant for OPC UA; correct tag mapping doesn't cause no data; powered off devices can't send data.

3. Final Answer:

   Incorrect OPC UA server endpoint URL -> Option A

4. Quick Check:

   Wrong endpoint URL blocks OPC UA data [OK]

Hint: Verify OPC UA endpoint URL first when no data [OK]

Common Mistakes:

• Confusing MQTT issues with OPC UA problems
• Assuming tags mapping causes no data
• Ignoring device power status

5. You want to integrate multiple IIoT sensors sending data via MQTT into SCADA. Which approach best ensures data consistency and scalability?

hard

A. Use a single SCADA tag for all sensors and ignore MQTT QoS settings

B. Map each sensor's MQTT topic to a unique SCADA tag and use a message broker with QoS 1 or 2

C. Send data directly from sensors to SCADA without a broker

D. Manually enter sensor data into SCADA daily

Solution

1. Step 1: Understand MQTT QoS and topic mapping

   MQTT QoS 1 or 2 ensures reliable message delivery; unique topics per sensor avoid data mix-up.

2. Step 2: Evaluate scalability and consistency

   Mapping each sensor to unique tags and using a broker with QoS supports scalable, consistent data flow.

3. Final Answer:

   Map each sensor's MQTT topic to a unique SCADA tag and use a message broker with QoS 1 or 2 -> Option B

4. Quick Check:

   Unique tags + QoS broker = consistent scalable integration [OK]

Hint: Use unique tags and MQTT QoS for reliable data [OK]

Common Mistakes:

• Using one tag for all sensors causing data overwrite
• Ignoring MQTT QoS leading to lost messages
• Bypassing message broker causing scalability issues
• Manual data entry causing errors and delays