Hi all,
We have a shopfloor where most machine data is exposed via OPC UA Structured DataTypes / ExtensionObjects instead of simple atomic tags. This is based on a standard machine information model, so values and metadata like unit, limits, ID, timestamp, status, etc. come together as one structured object.
The overall scale is large around 100k shopfloor tags/signals follow this pattern.
I understand Ignition can connect and read these, but practically they seem to come in as Document/JSON rather than fully expanded member tags.
I wanted to ask what is the best and most scalable way to handle this in Ignition.
-
Should we keep the structured object as the source and only extract required members into derived tags?
-
Should we flatten things upstream before Ignition?
-
Is there a recommended UDT-based abstraction approach in Ignition for this?
-
What are the real performance concerns at this scale for subscriptions, tag count, memory, historian, alarming, and UI bindings?
-
Any known limitations with custom structured datatypes / ExtensionObjects / datatype definitions in current Ignition versions?
Mainly looking for best practice from people who have implemented this in production, especially at large scale.