Roboflow + AVEVA PI System
Store detections, counts and pass or fail results as PI points, collected from your edge device over OPC UA with the AVEVA Adapter or PI Connector for OPC UA.
How to connect AVEVA PI System to Roboflow
6 stepsSet up an edge device
Register a device in Deployment Manager on a network the adapter or connector host 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 a tag for each value you want in PI, such as an Int32 defect count or a Boolean reject flag. Turn on Require authentication if the adapter or connector 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 the adapter or connector
Configure the data source of the AVEVA Adapter for OPC UA, or a PI Connector for OPC UA data source, with the device's endpoint URL and the user name and password if you set them.
Select the tags to collect
With the adapter, discover the device's data items and set the data selection. With the connector, browse the address space; it creates PI points and AF elements automatically.
Check the data
Trend the new PI points in your usual PI tools. The device page in Deployment Manager shows how many OPC UA clients are connected and the latest tag values.
What teams build with AVEVA PI System
Trend defect rates by shift
Store defect and output counts as PI points and compare them by shift, line or product.
Investigate a quality event
Look back at what the vision system reported at the moment a problem started, next to the rest of your PI data.
Correlate vision results with process conditions
Compare defect rates with temperature, line speed or other points already in PI.
Questions
Yes. The AVEVA PI System is the PI System formerly sold by OSIsoft, and the same setup applies.
The AVEVA Adapter for OPC UA sends data to OMF endpoints such as PI Web API and AVEVA's cloud data services, and runs on Windows or Linux. PI Connector for OPC UA writes to PI Data Archive and Asset Framework and builds AF elements automatically. Use whichever your PI team already runs.
No. Roboflow's OPC UA Server service runs on the edge device, and the adapter or connector connects to it directly.
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.
