Why Aveva PDMS Outperforms Intergraph PDS in Plant Design

In my 20 years of piping engineering, I have managed mega-projects using both Aveva PDMS and Intergraph PDS. I remember a specific offshore platform project where our PDS database corrupted mid-way through routing a high-pressure steam line. That incident cost us three weeks of rework. When we transitioned to Aveva PDMS, the difference was night and day. The object-oriented database structure of PDMS handled concurrent multi-user routing without a single database lock or crash.

Analyzing Aveva PDMS vs Intergraph PDS Databases

To understand the performance gap, let us calculate the database transaction overhead during concurrent piping routing. Suppose we have a team of fifty piping designers working simultaneously on a complex refinery module. In Intergraph PDS, each designer’s action requires a write operation to the relational database and a file-lock on the MicroStation DGN file. The total network traffic can be calculated using the transaction frequency formula: Total Traffic equals the number of concurrent users multiplied by the average transaction size multiplied by the frequency of database commits.

If fifty users generate transactions of one hundred and fifty kilobytes at a frequency of zero point five transactions per second, the network must support three thousand seven hundred and fifty kilobytes per second of continuous, low-latency data transfer. Because PDS uses file-locking, any network latency exceeding fifty milliseconds causes database timeouts and file corruption. In contrast, Aveva PDMS uses a data-streaming protocol that only transmits incremental object changes, reducing the average transaction size to less than ten kilobytes. This reduces the total network traffic to two hundred and fifty kilobytes per second, allowing seamless collaboration even across low-bandwidth global networks.

Furthermore, the integration of piping specifications under ASME B31.3 is handled natively within the PDMS database. When a designer selects a piping class, the software cross-references the material limits in real-time. In PDS, this requires querying external relational tables, which introduces a lag that compounds as the model size grows.

How to Migrate Plant Design Databases Safely

Migrating from a legacy system like Intergraph PDS to Aveva PDMS requires a rigorous validation process. In my experience, skipping database integrity checks before migration leads to broken piping specs and misaligned coordinates in the target model.

Field Case Study: Real-World Application

For any complex brownfield or greenfield project exceeding ten thousand piping lines, I strongly advise using Aveva PDMS over Intergraph PDS to ensure database stability and minimize field rework.

Aveva PDMS vs Intergraph PDS FAQ Guide