Review your Plant 3D P&ID configuration
Get a clearer view of your P&ID class setup before a project handover or standards review. Open local project files, explore the configuration and export your findings with P&ID Class Audit.
- No account required
- Files processed locally
- SQLite project files, ZIP or JSON snapshot
What you can do with P&ID Class Audit
See the class structure
Explore your P&ID configuration in one place instead of gathering class details individually during a review.
Prepare a standards review
Use the configuration overview to identify differences worth checking. Inheritance is provisional; a difference is a review item, not automatically an error.
Share the findings
Export an audit report for colleagues without changing the original project files. Reports contain project metadata, so choose carefully who receives them.
How it works
Choose a project or snapshot
Select Project.xml, PnIdPart.xml and ProcessPower.dcf together, or a folder or ZIP containing them. If your project uses different names, keep the filenames referenced by its configuration.
Explore the configuration
Review the class structure and configuration details. The built-in sample lets you try the workflow before opening your own files.
Export and review
Download a report and check the findings with the project administrator before making any changes in Plant 3D.
Your output: Downloadable audit reports. Your original files stay unchanged.
Before you start
Which project files are supported?
The tool reads local SQLite P&ID projects, project folders or ZIPs, and schema 1 or 2 JSON audit snapshots from the desktop tool. A single P&ID database can also be opened. Project.xml alone is not enough; drawings are not required.
Can I audit SQL Server projects or drawing objects?
SQL Server, cloud projects and DWG contents are not supported. This is a configuration review: it does not inspect placed objects or validate style definitions.
What if the database is in use?
Use a consistent backup or export a JSON snapshot with the desktop tool. Live journal sidecars and WAL databases are not suitable inputs. Do not delete journal files to make a database open.
What are the file limits?
The current limits are 100 MB per database or ZIP, 200 MB of relevant files after extraction, and 20 MB per JSON snapshot. Folder and ZIP imports allow up to 3,000 entries. Available browser memory also matters; a desktop JSON snapshot can help on smaller devices.
Are project files uploaded or changed?
Selected files are read in browser memory and are not uploaded by the tool or saved to WordPress. Original files stay unchanged. The website still loads application files normally, and exported reports contain project metadata.