Cloud-based SCADA (IIoT) in SCADA systems - Step-by-Step Execution

Process Flow - Cloud-based SCADA (IIoT)

Sensors collect data

↓

Data sent to Edge Gateway

↓

Edge Gateway preprocesses data

↓

Data transmitted securely to Cloud

↓

Cloud SCADA system stores and analyzes data

↓

Operators access dashboard remotely

↓

Control commands sent back to devices

↓

Devices adjust operations accordingly

Data flows from sensors through gateways to the cloud, where it is stored and analyzed, then operators remotely monitor and control devices.

Execution Sample

SCADA systems

1. Sensor reads temperature
2. Gateway receives data
3. Gateway sends data to cloud
4. Cloud stores and analyzes
5. Operator views dashboard
6. Operator sends control command

This sequence shows how sensor data moves from collection to cloud storage and operator control in a cloud-based SCADA system.

Process Table

Step	Action	Data State	System Component	Result
1	Sensor reads temperature	Temperature=75°F	Sensor	Data ready
2	Gateway receives data	Temperature=75°F	Edge Gateway	Data buffered
3	Gateway sends data to cloud	Temperature=75°F	Network	Data transmitted securely
4	Cloud stores and analyzes	Temperature=75°F	Cloud SCADA	Data stored and alert checked
5	Operator views dashboard	Temperature=75°F	Operator Interface	Current status displayed
6	Operator sends control command	Command=Increase cooling	Operator Interface	Command sent to cloud
7	Cloud forwards command	Command=Increase cooling	Cloud SCADA	Command dispatched to gateway
8	Gateway sends command to device	Command=Increase cooling	Edge Gateway	Device receives command
9	Device adjusts operation	Cooling increased	Device	Operation updated
10	System monitors new state	Temperature=72°F	Sensor	Data updated
11	Loop continues	Updated data	System	Continuous monitoring
12	Exit	N/A	System	Process runs continuously

💡 Cloud-based SCADA runs continuously for real-time monitoring and control

Status Tracker

Variable	Start	After Step 1	After Step 4	After Step 9	Final
Temperature	N/A	75°F	75°F	72°F	72°F
Command	None	None	None	Increase cooling	Increase cooling
Data State	No data	Data ready	Stored	Updated	Updated

Key Moments - 3 Insights

Why does the temperature value stay the same between steps 1 and 4?

Because the sensor reads the temperature once at step 1 and the same data is transmitted and stored without change until the device adjusts operation at step 9.

How does the operator's command reach the device?

The command flows from the operator interface to the cloud SCADA, then to the edge gateway, and finally to the device, as shown in steps 6 to 8.

Why does the system continue running after step 11?

Because cloud-based SCADA systems operate continuously for real-time monitoring and control, looping through data collection and command cycles.

Visual Quiz - 3 Questions

Look at the execution table, what is the temperature value after step 9?

A 70°F

B 72°F

C 75°F

D None

💡 Hint

Check the 'Temperature' variable in variable_tracker after step 9

At which step does the operator send a control command?

A Step 6

B Step 4

C Step 8

D Step 10

💡 Hint

Look at the 'Action' column in execution_table for operator actions

If the gateway fails to send data to the cloud at step 3, what happens next?

A Data is lost and system stops

B Operator receives alert immediately

C Gateway retries sending data

D Device adjusts operation without command

💡 Hint

Consider typical edge gateway behavior in cloud-based SCADA systems for reliable data transmission

Concept Snapshot

Cloud-based SCADA (IIoT) collects sensor data via gateways,
sends it securely to the cloud for storage and analysis,
operators monitor and control devices remotely,
and the system runs continuously for real-time updates.

Full Transcript

In a cloud-based SCADA system for Industrial IoT, sensors first collect data such as temperature. This data is sent to an edge gateway that preprocesses and buffers it. The gateway securely transmits the data to the cloud SCADA system, where it is stored and analyzed. Operators access a remote dashboard to view current system status and send control commands. These commands flow back through the cloud and gateway to the devices, which adjust their operations accordingly. The system continuously monitors updated data, enabling real-time control and monitoring. This flow ensures efficient, remote management of industrial processes.

Practice

1. What is the main advantage of using cloud-based SCADA systems in industrial settings?

easy

A. Requires physical presence at the factory to operate

B. Does not support real-time data updates

C. Only works with wired connections

D. Remote monitoring and control of machines via the internet

Solution

1. Step 1: Understand cloud-based SCADA purpose

   Cloud-based SCADA allows monitoring and controlling machines remotely using internet connectivity.

2. Step 2: Compare options

   Remote monitoring and control of machines via the internet correctly states remote control via internet. Options A, C, and D contradict the cloud-based approach.

3. Final Answer:

   Remote monitoring and control of machines via the internet -> Option D

4. Quick Check:

   Cloud SCADA = Remote control [OK]

Hint: Cloud SCADA means control machines from anywhere [OK]

Common Mistakes:

• Thinking cloud SCADA needs physical presence
• Assuming only wired connections work
• Believing cloud SCADA can't update data in real-time

2. Which protocol is commonly used to send sensor data from SCADA devices to the cloud?

easy

A. MQTT

B. FTP

C. HTTP

D. SMTP

Solution

1. Step 1: Identify common IIoT protocols

   MQTT is a lightweight messaging protocol designed for IoT and SCADA data transmission.

2. Step 2: Eliminate other protocols

   HTTP is general web protocol, FTP is for file transfer, SMTP is for email. MQTT fits SCADA sensor data best.

3. Final Answer:

   MQTT -> Option A

4. Quick Check:

   SCADA sensor data uses MQTT [OK]

Hint: MQTT is made for IoT messaging [OK]

Common Mistakes:

• Confusing FTP or SMTP as sensor data protocols
• Choosing HTTP which is less efficient for SCADA
• Not knowing MQTT is lightweight and fast

3. Given this MQTT topic subscription in a cloud SCADA system:
factory1/machineA/temperature
What data will the system receive?

medium

A. Temperature readings from machine A in factory 1

B. Humidity readings from machine A in factory 1

C. Temperature readings from all machines in factory 1

D. Control commands for machine A

Solution

1. Step 1: Analyze MQTT topic structure

   The topic 'factory1/machineA/temperature' specifies data from machine A's temperature sensor in factory 1.

2. Step 2: Match topic to data type

   Temperature readings from machine A in factory 1 matches temperature readings from machine A. Other options mention humidity, all machines, or commands, which don't match the topic.

3. Final Answer:

   Temperature readings from machine A in factory 1 -> Option A

4. Quick Check:

   Topic matches temperature data [OK]

Hint: Topic parts show source and data type [OK]

Common Mistakes:

• Confusing temperature with humidity
• Assuming topic covers all machines
• Thinking topic is for control commands

4. A cloud SCADA system fails to receive sensor data. The MQTT broker URL is set as mqtt://broker.example.com. What is the likely issue?

medium

A. The URL should use tcp:// instead of mqtt://

B. The URL should be http://broker.example.com

C. The broker URL must include a port number

D. The MQTT protocol is not supported for SCADA

Solution

1. Step 1: Check MQTT broker URL format

   MQTT URLs usually require a port number (e.g., 1883) to connect properly.

2. Step 2: Evaluate options

   The broker URL must include a port number correctly identifies missing port number. The URL should use tcp:// instead of mqtt:// is incorrect because mqtt:// is a valid scheme. The MQTT protocol is not supported for SCADA is false; MQTT is supported. The URL should be http://broker.example.com uses HTTP which is wrong for MQTT.

3. Final Answer:

   The broker URL must include a port number -> Option C

4. Quick Check:

   MQTT URL needs port [OK]

Hint: MQTT URLs need port number to connect [OK]

Common Mistakes:

• Changing mqtt:// to tcp:// incorrectly
• Using HTTP instead of MQTT protocol
• Assuming MQTT is unsupported in SCADA

5. You want to design a cloud SCADA system that scales automatically when more machines are added. Which cloud feature should you use?

hard

A. Manual server provisioning

B. Auto-scaling groups with MQTT brokers

C. Static IP addresses for each machine

D. Local data storage on each machine only

Solution

1. Step 1: Understand scalability needs

   Auto-scaling groups allow cloud resources to grow or shrink automatically based on demand.

2. Step 2: Match cloud feature to SCADA scaling

   Using auto-scaling with MQTT brokers supports dynamic machine additions. Manual provisioning and static IPs do not scale well. Local storage only limits cloud benefits.

3. Final Answer:

   Auto-scaling groups with MQTT brokers -> Option B

4. Quick Check:

   Auto-scaling = scalable SCADA [OK]

Hint: Auto-scaling adjusts resources automatically [OK]

Common Mistakes:

• Choosing manual provisioning which is slow
• Using static IPs that limit flexibility
• Relying only on local storage without cloud