INTERACTIVE SUB-PLATFORM
Enterprise Integration
Explore AVEVA, Ignition and the Unified Namespace as working integration patterns. Select a platform, inspect each layer, trace data, and run operating scenarios.
3Integration patterns
5Traceable layers
InteractiveClickable architecture
ISA-95Context model
Choose a platform
AVEVA
HMI/SCADA, historian and enterprise operations.
Ignition
Gateway, tags, OPC UA, MQTT, historian and applications.
UNS
MQTT Sparkplug operational namespace and publish/subscribe distribution.
Start exploring
Select a platform above. Its functions, typical architecture and integration role will appear here.
Trace the enterprise path
After selecting a platform, click each node to explain that layer and what data moves through it.
Run integration scenarios
Select a scenario to walk through the system response.
Compare roles
| Layer | AVEVA | Ignition | UNS |
|---|---|---|---|
| Primary role | Supervisory operations | Application / gateway platform | Operational data distribution |
| Typical protocols | OPC UA, Modbus, vendor drivers | OPC UA, MQTT Sparkplug, SQL | MQTT Sparkplug |
| Historian | Strong native capability | Native/tag historian | Not a historian by itself |
| Enterprise context | Via apps and interfaces | Via gateway, apps and connectors | Topic hierarchy and payload context |