What is the difference between AVEVA PI and OSIsoft PI?
AVEVA acquired OSIsoft in 2021. The product is now called AVEVA PI System, but the technology is the same.
AVEVA PI System
AVEVA PI System implementation services for pharmaceutical manufacturers. The engagement covers the architecture, the deployment, the tag governance, the analytics, the OT/IT integration, and the post-deployment support.
PI System architecture
The PI System architecture is designed for the production environment: PI Server, PI Vision, PI Asset Framework (AF), PI Interfaces, and PI Integrators.
PI System deployment
The PI System deployment covers the server installation, the interface configuration, the network and security design, the initial tag population, the user setup, and the go-live.
PI Asset Framework (AF)
The PI AF is the metadata layer that enables the analytics, the calculations, the rollups, and the event frames.
Tag governance
The tag governance covers the naming standard, the hierarchy, the metadata, the request workflow, the retirement workflow, and the quality monitoring.
How to use this page
Use this AVEVA PI System page as a planning checkpoint before vendor selection, architecture review, validation scoping or implementation sequencing. The strongest next step is to compare the guidance with your current SOPs, system inventory, batch records, data flows and QA review routines so the discussion starts from evidence instead of assumptions.
Evidence to prepare
For AVEVA PI System, prepare the records, owners, risks and decision criteria linked to pi system architecture, pi system deployment, pi asset framework (af), tag governance. Useful evidence includes current process maps, interface lists, audit trail expectations, exception workflows, data retention rules and the business reason for changing the current operating model.
Frequently asked questions
How long does PI System implementation take?
A typical PI System implementation takes 6-12 months.