OPC (OLE for Process Control) in SCADA systems - Step-by-Step Execution

Process Flow - OPC (OLE for Process Control)

Client Requests Data

↓

OPC Server Receives Request

↓

Server Reads Data from PLC or Device

↓

Server Sends Data to Client

↓

Client Receives and Uses Data

↓

Repeat or Close Connection

This flow shows how an OPC client asks for data, the OPC server gets it from devices, and sends it back to the client.

Execution Sample

SCADA systems

1. Client connects to OPC Server
2. Client requests 'Temperature' tag
3. Server reads 'Temperature' from PLC
4. Server sends value 72.5 to Client
5. Client displays value

This example traces a client requesting a temperature value from an OPC server connected to a PLC.

Process Table

Step	Action	Component	Data/Value	Result
1	Connect to OPC Server	Client	N/A	Connection Established
2	Request 'Temperature' tag	Client	Tag='Temperature'	Request Sent
3	Receive request	OPC Server	Tag='Temperature'	Request Received
4	Read 'Temperature' from PLC	OPC Server	PLC Tag='Temperature'	Value=72.5
5	Send value to Client	OPC Server	Value=72.5	Value Sent
6	Receive value	Client	Value=72.5	Value Received
7	Display value	Client	Value=72.5	Value Displayed
8	End or Repeat	Client/Server	N/A	Process Ends or Loops

💡 Process ends after value is displayed or repeats for new requests

Status Tracker

Variable	Start	After Step 2	After Step 4	After Step 6	Final
Connection Status	Disconnected	Connected	Connected	Connected	Connected
Requested Tag	None	Temperature	Temperature	Temperature	Temperature
Value from PLC	None	None	72.5	72.5	72.5
Value at Client	None	None	None	72.5	72.5

Key Moments - 3 Insights

Why does the client need to connect before requesting data?

The client must establish a connection first (see Step 1 in execution_table) so the server can receive and respond to requests.

How does the server get the actual data value?

The server reads the value directly from the PLC device (Step 4), not from the client or cache.

What happens if the client requests a tag that does not exist?

The server cannot find the tag and will return an error or no data, stopping the normal flow after Step 3.

Visual Quiz - 3 Questions

Look at the execution table, what is the value of 'Value from PLC' after Step 4?

A Temperature

B 72.5

C None

D Disconnected

💡 Hint

Check the 'Value from PLC' column in variable_tracker after Step 4

At which step does the client receive the requested data value?

A Step 6

B Step 3

C Step 2

D Step 5

💡 Hint

Look at the 'Receive value' action in the execution_table

If the client never connects, what happens to the connection status variable?

A It becomes 'Error'

B It changes to 'Connected'

C It stays 'Disconnected'

D It becomes 'None'

💡 Hint

See variable_tracker 'Connection Status' start and after Step 2

Concept Snapshot

OPC (OLE for Process Control) allows clients to request real-time data from industrial devices via an OPC server.
Clients connect to the server, request tags (data points), and receive current values.
The server reads data directly from devices like PLCs and sends it back.
This enables easy, standardized communication between control systems and software.
Always connect before requesting data, and handle errors if tags are missing.

Full Transcript

OPC (OLE for Process Control) is a way for software clients to get data from industrial devices through an OPC server. The client first connects to the server, then asks for a specific data tag like 'Temperature'. The server receives this request, reads the current value from the connected device such as a PLC, and sends the value back to the client. The client then receives and displays this value. This process can repeat as needed. If the client does not connect first, the server cannot receive requests. If the requested tag does not exist, the server returns an error. This flow ensures standardized, real-time data exchange in industrial automation.