The OPC UA "Aggregating Server" pattern consists of exposing, through a single OPC UA server, data coming from multiple sources (Modbus PLCs, BACnet devices, SQL databases), so as to simplify integration on the SCADA/MES side.
True
An Aggregating Server is a single front-facing OPC UA server with backend connectors to heterogeneous sources: Modbus PLCs, BACnet devices, Siemens S7 controllers, SQL databases, REST APIs and so on. Each source is mapped into a hierarchical branch of the OPC UA Address Space, so a SCADA or MES client sees one unified semantic tree instead of several incompatible drivers. This pattern is the de-facto standard for modern data aggregation in Industrie 4.0 and is implemented by products such as Kepware KEPServerEX, Matrikon and the Unified Automation OPC UA Gateway.
OPC UA bank in preparation
The full OPC UA bank isn't available yet. Drop your email to get notified at launch and grab an early-bird discount.
Join the waitlist →See the 9 other OPC UA practice questions
Related questions
- What is the complete format of an OPC UA NodeId?2. NodeIds · NodeId-Format
- An OPC UA Subscription groups several MonitoredItems and publishes value changes periodically (PublishingInterval typically 100-1000 ms); the server keeps a buffer of unacknowledged notifications for reliability.3. Services · Subscriptions
- Which Security Modes does an OPC UA SecureChannel support per the standard?4. Security · SecureChannel-Modi
- OPC UA uses X.509 certificates to authenticate applications (both client and server): each application holds its own certificate, and trust is established mutually through the exchange that happens during the SecureChannel handshake.4. Security · Zertifikate
- OPC UA Pub/Sub supports several transports: UDP multicast (lowest latency, machine-to-machine), MQTT (cloud-friendly via broker) and AMQP (enterprise messaging), making it adaptable to a wide range of use cases.9. Pub/Sub · Transport-Optionen