What You Actually Need to Know About the Pdms Reference Manual
The Pdms Reference Manual is the documentation suite that ships with AVEVA PDMS (now part of the E3D Design line). It covers everything from database structure to DLS scripting, rule creation, and report writer configuration. Most people only look at it when something breaks. That is usually too late. I spent about three years working primarily in PDMS for subsea and topside piping design. The reference materials are split across several books: the Getting Started guide, the Modeling and Detailing manuals, the Rules and Reports guide, and then the standalone reference sections that cover the DLS language and the data dictionary. The PDFs are heavy. They are not friendly to search. You will spend more time navigating than reading. Here is the practical approach I ended up using. I kept the Rules and Reports manual open on one screen while working in the client. I bookmarked the DLS syntax tables and kept a separate cheat sheet for the command structure. The reference is technically complete, but it assumes you already understand how PDMS organizes its hierarchy. If you do not, the definitions read like alphabet soup.
One thing most people miss: the reference manual does not explain when to use ENQUIRY versus EXPOSE. Those are two different operations with very different performance costs. ENQUIRY reads data without modifying anything and is faster for bulk checks. EXPOSE brings objects into the local DADs space so you can modify them, but it adds significant overhead in large models. I learned this the hard way on a 40,000-branch junction model where a DLS script running ENQUIRY loops took twelve minutes. Switching it to the equivalent EXPOSE approach ran for forty-seven minutes before the session crashed. Another edge case that burned me once: the reference says the REPORT WRITER can output to Excel format directly. It can, but the formatting is broken for any multi-section report. I found that exporting to DELTA then running a small conversion macro produced clean spreadsheets in under a minute, while trying to force the direct Excel path produced garbled columns and lost header rows. The workaround was to output to .DEL and use a simple VBA conversion step. That cut our reporting time from roughly two hours per deliverable down to about twenty minutes. There are also limitations you need to accept upfront. The manual does not cover every version-specific bug. What is documented for PDMS 12.1 is not always accurate for 14.1 or later, especially around DLS object references and the way composite rules are evaluated. The documentation also treats the software as if every installation follows best practices. In reality, many sites have custom rule libraries, modified templates, and non-standard naming conventions that the manual does not account for. When something does not work as described, the issue is often site configuration, not user error.
If you are starting fresh, I would recommend pairing the Pdms Reference Manual with a focused DLS exercise file. The manual explains the theory. Practice files show you where the rules actually break. Try writing a simple report that lists all pipes above a certain diameter in a selected zone. The theory section tells you the commands. The execution will reveal which ones require you to adjust context first, which ones return empty results because of hidden hierarchy nesting, and which ones silently skip junctions that do not match your filter criteria. The manual is reference-grade material, not a tutorial. It will not walk you through building a model from scratch or explain why your rule evaluation order matters. What it does well is provide exact syntax and command parameters when you need them. Treat it as a lookup tool rather than a reading assignment. Keep it bookmarked. Search by keyword, not by chapter. And save yourself some frustration by noting which sections are outdated for your specific PDMS release version before you start depending on them.
Get the Full Details
