Learn what IT/OT convergence is and how integrating these systems improves visibility and understanding of operational performance.
OT, short for operational technology, is defined by the ISA95 standard as the devices, assets, and systems used in the physical process (level 0), sensing and manipulation (level 1), supervisory control (level 2), and manufacturing operations management (level 3). OT includes equipment and devices used in the physical process—pipes, belts, machines, robots, sensors, controllers, etc., and the systems used to control equipment—HMI, SCADA, MES, etc.
OT is focused on manufacturing and industrial operations, whereas IT is focused on the physical and digital assets and processes used to create, process, store, and secure electronic data.
OT departments are primarily concerned with availability, uptime, and data quality and reliability of systems.
IT is typically more concerned with the security, standardization, and scalability of systems.
Process convergence is the unification of workflows across IT and OT. Both departments need to revise their procedures and policies to drive visibility, alignment, and ultimately understanding. The convergence of processes represents an organizational convergence, addressing the internal business structures. For example, a company may have established SOPs for cybersecurity, these processes and procedures should consider and protect OT networks.
Software and data convergence brings together IT and OT systems into an architecture that is seamless, secure, and scalable to meet the needs of the enterprise. This convergence allows OT data from the manufacturing shop floor to be leveraged in IT systems, such as the cloud or IoT platforms, for visibility and insights into performance.
Physical convergence refers to physical devices being retrofitted with newer hardware to accommodate the addition of IT to OT. Examples of this include investments in networking equipment for OT.
OT systems were originally designed to be isolated, intended to be 'air-gapped' from IT systems and external networks.
The diverse nature of OT systems complicates their integration with IT in a repeatable and scalable way.
IoT projects often lack a single owner, causing poor communication. OT lacks security knowledge and IT is unaware of OT projects, risking security.
Organizations may find it challenging to restructure traditionally separate IT and OT departments to effectively manage newly integrated technology.
Communicate goals: Understand the business objective, set measurable and realistic goals, and then communicate clearly across teams.
Provide training: Cross-training OT and IT teams on the responsibilities and priorities of each team can help improve understanding and collaboration.
Show overlap: Identify and communicate the areas of shared responsibility, especially in terms of systems and security.
Use the right tools: Determine and deploy the right toolset to enable discovery, configuration, management, and security.
Define roles and responsibilities: Clearly communicate the roles and responsibilities for each team, and the opportunities and areas for collaboration.
Kepware industrial connectivity accesses data from OT assets and devices—regardless of age or manufacturer—and makes the data available to IT and OT systems.
ThingWorx industrial IoT visualizes and analyzes IT and OT data from disparate sources. Combining pre-built manufacturing apps with the best-in-class industrial IoT platform, ThingWorx enables data-driven decisions.