OPC UA Server
In Server mode inSCADA lets external OPC UA clients connect to read and write data. It creates a namespace of its own and presents the data it has collected as OPC UA nodes.
Where it is used
Section titled “Where it is used”- Presenting data to a higher-level SCADA, or to MES/ERP systems, over OPC UA
- OPC UA communication between separate inSCADA installations
- Feeding third-party analytics and reporting tools
- Acting as an OPC UA gateway to cloud platforms (Azure IoT Hub, AWS IoT and the like)
Configuration
Section titled “Configuration”Connection
Section titled “Connection”| Parameter | Example | Description |
|---|---|---|
| Protocol | OPC UA Server | The protocol |
| Port | 4840 | The listening port (for incoming connections) |
| Security Mode | SignAndEncrypt | The security mode |
| Security Policy | Basic256Sha256 | The security policy |
| Encoding Type | Binary | The encoding |
The security and authentication settings have the same shape as on the client.
Namespace
Section titled “Namespace”inSCADA creates a namespace for the OPC UA server by itself: urn:inscada:milo:connection-namespace. The variables you define are presented as nodes under it.
Device, frame and variable
Section titled “Device, frame and variable”These are defined exactly as in client mode. The values of the variables you define are presented as nodes to the connected OPC UA clients.
A typical deployment
Section titled “A typical deployment”Here inSCADA collects data from field devices over several different protocols and presents it upwards as an OPC UA server. Because OPC UA is platform-independent, this integrates cleanly across different operating systems and environments.