Roboflow + AVEVA InTouch and System Platform
Show detections, counts and pass or fail results in AVEVA InTouch and System Platform as live tags, served from Roboflow's OPC UA Server on your edge device.
How to connect AVEVA InTouch and System Platform to Roboflow
6 stepsSet up an edge device
Register a device in Deployment Manager on a network the AVEVA node can reach, with port 4840 open between them. The device runs your Workflows on site.
Add the OPC UA Server service
On the device's Configuration tab, add the OPC UA Server service and create a folder and tags for your results, such as a Boolean reject flag and an Int32 defect count. Turn on Require authentication if clients should log in.
Write results from the Workflow
Add one OPC UA Writer Sink per tag. Enter the device's endpoint URL, the namespace http://opcua.roboflow.run, the folder.tag path as the Object Name with Variable Name left empty, and a value type that matches the tag.
Connect OI Gateway
In AVEVA's OI Gateway, add an OPC UA client connection to the device's endpoint, enter the user name and password if you set them, and browse to the tags.
Use the tags in InTouch or System Platform
In InTouch, point an Access Name and Topic at the OI Gateway connection and use the tags in windows and alarms. In System Platform, reference them from your objects.
Monitor the connection
The device page in Deployment Manager shows how many OPC UA clients are connected and the latest tag values, so you can confirm AVEVA is subscribed.
What teams build with AVEVA InTouch and System Platform
Show inspection results on operator screens
Put live pass or fail status, defect counts and the last class seen on the InTouch windows operators already use.
Alarm on a defect
Set an alarm on the reject flag so operators are alerted the moment a defect is found.
Log counts to your historian
Historize defect and output counts alongside other process data to compare shifts and lines.
Questions
Yes. AVEVA InTouch and AVEVA System Platform were sold under the Wonderware name, and the same setup applies.
No. Roboflow's OPC UA Server service runs on the edge device, and OI Gateway connects to it directly.
Turn on Require authentication in the OPC UA Server service so clients need a user name and password. The service's HTTP API on port 8092 is not authenticated, so keep it off networks that should not write tags.
No. The OPC UA Server service and the OPC UA Writer Sink run on your own edge device, on the plant network.
The OPC UA Server service and the OPC UA Writer Sink are part of the Enterprise plan. Talk to our team to add them to your workspace.
Why are companies choosing Roboflow?
The end-to-end platform for vision AI: create datasets, train models and deploy to production.
Flexible deployment modes
Move from a scalable cloud API to edge hardware like NVIDIA Jetson without managing complex dependencies.
Integrated workflow builder
Combine multiple AI models, custom business logic and third-party integrations into one production-ready pipeline in a low-code editor.
Model monitoring and alerts
Dashboards track confidence, inference time and request volume for your deployed models, and email alerts tell your team when confidence suddenly drops.
