AVEVA Folds OSIsoft’s PI System Into CONNECT as a Single Industrial Intelligence Platform

AVEVA has positioned CONNECT as the unifying layer for the technology it acquired from OSIsoft, folding the PI System’s historian and dashboarding capabilities into a broader industrial software portfolio that spans oil and gas, power and utilities, and EPC, among other industries. AVEVA describes CONNECT as an open cloud platform built to link operational information and give teams shared visibility across engineering and asset data. The company says CONNECT and its software combine to replace scattered, siloed systems with one central industrial backbone. SAP customers who adopted PI System as a standalone historian will find the underlying data architecture now sits inside a larger, cloud-oriented suite instead of a discrete product line.

Unifying Operational Data Across Industries

AVEVA’s ambition for CONNECT is to replace fragmented, siloed systems with one architecture spanning engineering, operations, and asset data. Its EPC materials say engineering, procurement, and construction companies turn to the platform to link project data, staff, and processes across every phase of a build, from initial simulation and design to construction and visualization. The offering also includes process libraries for chemical processing, process utilities, and flare networks, giving project teams a shared reference point instead of separate toolsets for each discipline.

The oil and gas materials describe a similar aim: AVEVA states its platform speeds up information discovery and reduces data silos so upstream, LNG, pipeline, and downstream teams can reach relevant information faster. Operational and engineering data that once lived in separate historians, simulators, and design tools now moves through CONNECT’s cloud architecture. Organizations that feed PI System data into SAP for maintenance planning or finance reporting will see this consolidation shift where that integration point sits. SAP teams pursuing clean core strategies increasingly expect OT and historian data to arrive through governed APIs instead of custom, point-to-point connections, and a single cloud backbone makes that governance model easier to enforce than a collection of separate legacy tools.

Real-Time Intelligence for Asset Performance and Compliance

AVEVA’s power and utilities materials describe an Industrial Intelligence platform that gives operators real-time visibility, deeper analytics, and unified engineering tools aimed at keeping operations reliable, improving asset performance, and speeding project delivery. The company also says continuous monitoring and analytics help utilities avoid outages, stay compliant, and meet net-zero targets.

On the oil and gas side, AVEVA names the PI System directly, describing a self-service dashboard that lets teams display data in context, run on-the-fly analysis, and view PI System information from any device. The same materials point to asset health tools built on real-time monitoring, predictive analytics, and advanced alerting designed to catch problems early. Plants that route PI System data into SAP asset performance management or maintenance modules will recognize this workflow, now delivered through a cloud-first interface instead of an on-premises client. SAP’s own asset performance management tools can overlap with third-party predictive analytics platforms in this space, and that overlap typically pushes teams toward a build-versus-buy evaluation when a historian vendor changes its delivery model. Time-series historian data routed into SAP for maintenance and finance reporting remains common in process industries, which is why the shift from an on-premises PI System to a cloud-based CONNECT layer matters to SAP administrators rather than being purely an OT concern.

What This Means for SAPinsiders

• PI System now lives inside a larger platform. SAP-aligned teams evaluating a renewal or expansion need to determine whether they are re-engaging with standalone PI System licensing or the full AVEVA CONNECT suite. That distinction affects both cost structure and the scope of integration work required.
• Cloud delivery replaces on-premises historian deployment. Organizations running PI System on-premises should plan a migration path as AVEVA emphasizes CONNECT’s cloud architecture over local installations. Delaying that planning risks a mismatch between OT data availability and SAP reporting cycles.
• Cross-industry data unification changes ownership questions. Governance teams managing OT-to-SAP integration should reassess who owns data definitions and access controls as AVEVA consolidates industry-specific tools under one platform. Clean core initiatives depend on that ownership being resolved before new API connections are built.