A 14-month greenfield AVEVA PI System deployment for PetroVietnam Fertilizer and Chemicals Corporation, covering 4 workshops, OT/IT integration, and the foundation for advanced analytics use cases.
PVCFC operates one of the largest fertilizer production complexes in Vietnam, with 4 workshops producing different product grades. The modernization program consolidated operational data, enabled cross-workshop performance benchmarking, and laid the foundation for advanced analytics and predictive maintenance use cases.
Phase 0: Architecture and procurement (6 weeks) for multi-workshop architecture, OT/IT network and security design, hardware sizing, and vendor coordination. Phase 1: Foundation deployment (3 months) including PI Server, PI Interfaces, network, security, and initial tag population. Phase 2: Tag governance and rollout (4 months) including naming standard, hierarchy, and workshop-by-workshop expansion. Phase 3: Analytics foundation (3 months) including PI AF templates, KPIs, and analytics access. Phase 4: Support and handoff (2 months) with 6-month support window.
Cross-workshop visibility enabled for site management. Foundation established for the analytics pilots including the predictive maintenance pilot that identified a high-impact failure mode. Tag naming and hierarchy standardized across 4 workshops. Site engineering team owns the system without external support after the engagement.
Tag governance before tag population. OT/IT boundary is a security and ownership decision. Engineering team training is part of the deliverable.
Use this PVCFC: AVEVA PI System Across 4 Workshops 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.
For PVCFC: AVEVA PI System Across 4 Workshops, prepare the records, owners, risks and decision criteria linked to project background, approach, outcomes, lessons learned. 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.
Selected after a vendor selection process comparing AVEVA PI, OSIsoft (pre-AVEVA), and an open-source alternative (InfluxDB). The selection considered the multi-workshop scope, the existing DCS environment, and the long-term support model.
14 months total: 6 weeks architecture, 3 months foundation, 4 months tag governance, 3 months analytics, 2 months support and handoff with 6-month support window.
Cross-workshop production visibility, performance benchmarking, predictive maintenance pilot, anomaly detection, and yield optimization. The site engineering team has extended the system to energy monitoring and environmental compliance reporting.