Patterns / Integration Architecture
OT–IT Integration
A zoned architecture that lets operational and enterprise systems share data without sharing risk.
OT Zone
Conduit / Edge Broker
Operational Backbone
Canonical Contracts
Enterprise Layer
Conceptual flow
Problem
Plant, grid, and field systems hold the operational truth, but exposing them directly to enterprise networks is unacceptable.
Context
Utilities, energy, and manufacturing with SCADA, historians, AMI, and enterprise applications.
Solution
Apply zone and conduit segmentation, a unidirectional or brokered edge, an operational data backbone, and canonical contracts before the enterprise layer consumes anything.
Benefits
- Safety and security preserved
- Operational data reused enterprise-wide
- Clear accountability at the boundary
Risks
- Latency at the boundary
- Duplicate semantics between OT and IT
- Change windows constrained by operations
Trade-offs
- Controlled boundary over direct access
When to use
- Regulated critical infrastructure
- Asset-intensive operations
When not to use
- Pure IT estates
Related patterns
Discuss this pattern
How have you applied it — and where did it break? Bring your experience to the community.
Open the discussion