IIoT integration with SCADA in SCADA systems - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define the protocol used for IIoT data transfer in SCADA.

SCADA systems

protocol = "[1]"

Drag options to blanks, or click blank then click option'

AHTTP

BMQTT

CFTP

DSMTP

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing HTTP which is heavier for IIoT devices.

MQTT is a lightweight messaging protocol commonly used for IIoT data transfer in SCADA systems.

2fill in blank

medium

Complete the code to set the SCADA system to subscribe to the IIoT sensor topic.

SCADA systems

scada_client.subscribe("[1]")

Drag options to blanks, or click blank then click option'

Asensor/data

Bdevice/control

Csystem/logs

Dalerts/warnings

Attempts:

3 left

💡 Hint

Common Mistakes

Subscribing to control or log topics instead of sensor data.

The SCADA system subscribes to the 'sensor/data' topic to receive IIoT sensor readings.

3fill in blank

hard

Fix the error in the code to correctly parse JSON payload from IIoT device.

SCADA systems

import json
payload = '{"temperature": 22.5}'
data = json.[1](payload)

Drag options to blanks, or click blank then click option'

Adumps

Bload

Cdump

Dloads

Attempts:

3 left

💡 Hint

Common Mistakes

Using json.load which expects a file object.

json.loads() parses a JSON string into a Python dictionary.

4fill in blank

hard

Fill both blanks to filter IIoT sensor data with temperature above 25 and create a dictionary.

SCADA systems

filtered_data = {device_id: data[1] for device_id, data in sensors.items() if data['temperature'] [2] 25}

Drag options to blanks, or click blank then click option'

A.copy()

B==

C>

D!=

Attempts:

3 left

💡 Hint

Common Mistakes

Using '==' or '!=' instead of '>' for temperature comparison.

We use .copy() to copy the data dictionary and filter where temperature is greater than 25.

5fill in blank

hard

Fill all three blanks to create a dictionary of device names in uppercase with their status if status is 'active'.

SCADA systems

active_devices = [1]: [2] for [3], info in devices.items() if info['status'] == 'active'}

Drag options to blanks, or click blank then click option'

Adevice.upper()

Binfo['status']

Cdevice

Dinfo

Attempts:

3 left

💡 Hint

Common Mistakes

Using info instead of info['status'] as value.

The keys are device names in uppercase, values are their status, and the loop variable is device.

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