Theme: Shared capability without blurred accountability
Quick definition
IT/OT convergence coordinates technology, information, skills and working practices between digital business services and systems affecting physical operations. Its purpose is useful flows and shared decisions, not making IT and OT identical or placing everything on one network.
Convergence in context
ISA-95 provides language for activities and information exchange between manufacturing control and enterprise functions. NIST describes OT’s distinct performance, reliability and safety requirements. Convergence must hold both perspectives: exchange across boundaries and consequence-led operation.
For example: a concrete information flow
A maintenance system needs pump runtime and alarms to plan work. OT supplies verified signals; IT manages work orders and analysis. The flow needs a shared equipment identity, timestamps, quality status and explicit accountability when data is absent.
Technology and organisation
Shared Ethernet or IP expertise can simplify support, but convergence also covers roles, incident response, change windows and supplier access. An API or platform solves transport. It does not decide who may alter control logic or stop a process.
Opportunities
Well-designed convergence can reduce duplicate entry, improve situational awareness and connect operating results with maintenance, energy and business decisions. Shared identity, logging and access principles can strengthen troubleshooting and governance.
Limitations and risks
More connectivity creates dependencies and possible attack paths. Data does not become seamless or correct automatically. Centralisation can increase the reach of a failure. Segmentation, least privilege, local autonomous operation and tested recovery are still selected according to consequence.
HubMind’s view
Converge information contracts and cooperation before infrastructure. Once ownership, meaning and failure paths are explicit, technology can be shared where value exceeds dependency. Start with one valuable flow and test loss, delay and incorrect values before scaling.
A practical next step
Choose one decision requiring IT and OT data. Map sources, interfaces, permissions and process consequences. Assign incident and change responsibilities. Then verify the flow in normal operation and during a realistic communications outage.
Related concepts
Sources and further reading
Scope and freshness
IT/OT cooperation viewed through NIST SP 800-82 Rev. 3 and ISA-95’s public activity and interface model. No product architecture is prescribed. Reviewed 31 August 2026.