OPC UA Level 2 to Web API Level 4
Move selected industrial data through Level 3 and the Level 3.5 DMZ using only outbound connections from Level 2.
A layered OT-to-IT data path.
The Level 2 DataMule initiates the OPC UA connection and sends the approved data outward to a Level 3 DataMule. The flow then continues to the Level 3.5 DMZ DataMule and finally to the Web API in Level 4 IT.
Only outgoing connections from Level 2.
Outbound to Level 2
The Level 2 DataMule initiates the OPC UA session to the selected server. No inbound session is opened toward the Level 2 DataMule.
Outbound to the DMZ
The Level 2 DataMule initiates delivery to the Level 3 DataMule. No higher-level component initiates a connection into Level 2.
DMZ-to-IT delivery
The DMZ DataMule validates and relays the approved payload to the Level 4 Web API.
Purpose-built for segmented architectures.
No inbound Level 2 rule
Firewall policy can remain directional: connections originate inside Level 2 and move outward toward their defined peers.
DMZ isolation
The second DataMule separates OT collection from IT-facing API delivery and absorbs temporary endpoint outages.
Controlled payload
Only selected OPC UA fields, normalized into an approved API payload, cross the zone boundaries.
Validate the boundary with one data flow.
Define the OPC UA source, DMZ route and Web API contract.