Mobile SCADA access in SCADA systems - Step-by-Step Execution

Process Flow - Mobile SCADA access

User opens mobile SCADA app

↓

App sends login request

↓

SCADA server authenticates user

↓

Access granted

↓

User views SCADA data

↓

User sends control commands

↓

SCADA server processes commands

↓

Updates sent back to mobile app

This flow shows how a mobile SCADA app connects to the SCADA server, authenticates the user, and allows viewing and controlling SCADA data.

Execution Sample

SCADA systems

1. User opens mobile SCADA app
2. App sends login request to server
3. Server checks credentials
4. If valid, server sends SCADA data
5. User views data and sends commands
6. Server processes commands and updates data

This sequence shows the basic steps for mobile SCADA access from login to command execution.

Process Table

Step	Action	Input/Condition	Result	Next Step
1	Open app	User launches app	App ready to login	Send login request
2	Send login request	User credentials	Request sent to server	Server authenticates
3	Authenticate user	Check credentials	Credentials valid?	If yes: grant access; if no: deny
4	Grant access	Credentials valid	Access granted, send SCADA data	Display data on app
5	Display data	SCADA data received	User sees real-time data	User sends control commands
6	Process commands	User commands received	Commands executed on SCADA	Send updates to app
7	Update app	SCADA updates	App shows updated status	Wait for next user action
8	Deny access	Credentials invalid	Access denied message	End session

💡 Execution stops when user logs out or access is denied due to invalid credentials.

Status Tracker

Variable	Start	After Step 2	After Step 4	After Step 6	Final
User credentials	None	Entered by user	Validated	Used for commands	Cleared on logout
SCADA data	None	None	Received from server	Updated after commands	Displayed on app
Access status	None	Pending	Granted or Denied	Active if granted	Inactive after logout

Key Moments - 3 Insights

Why does the app stop if credentials are invalid?

Because at step 3 in the execution table, if credentials are invalid, the server denies access and the session ends at step 8.

How does the app get updated SCADA data after commands?

At step 6, the server processes user commands and sends updated data back to the app, which is shown at step 7.

What happens if the user does not send any commands after login?

The app continues to display real-time SCADA data and waits for user input, as shown in steps 5 and 7.

Visual Quiz - 3 Questions

Look at the execution table, at which step does the server check user credentials?

A Step 4

B Step 2

C Step 3

D Step 5

💡 Hint

Check the 'Action' column for 'Authenticate user' in the execution table.

According to the variable tracker, what is the state of 'Access status' after step 4?

A Pending

B Granted or Denied

C None

D Active

💡 Hint

Look at the 'Access status' row under 'After Step 4' in the variable tracker.

If the user sends no commands, what does the app do according to the execution flow?

A Continues showing SCADA data and waits

B Displays error message

C Closes immediately

D Logs out automatically

💡 Hint

Refer to steps 5 and 7 in the execution table where the app displays data and waits for user commands.

Concept Snapshot

Mobile SCADA access flow:
1. User opens app and logs in.
2. Server authenticates credentials.
3. If valid, SCADA data is sent to app.
4. User views data and sends commands.
5. Server processes commands and updates app.
6. Access denied if credentials invalid.

Full Transcript

Mobile SCADA access starts when the user opens the mobile SCADA app. The app sends a login request with user credentials to the SCADA server. The server checks these credentials. If they are valid, the server grants access and sends SCADA data to the app. The user can then view real-time SCADA data and send control commands. The server processes these commands and sends updates back to the app. If credentials are invalid, the server denies access and the session ends. The app continues to display data and wait for user commands until logout or denial.