Revit to PCF
PipeEX PCF Export for Revit piping
PipeEX PCF Export is the public product page for the Windows Revit add-in from PipeEX that exports PCF from piping models for downstream isometric and stress workflows.
The site also includes trial access, buyer guides, a technical FAQ, tutorials, licensing information, and contact paths so each public page can stand on its own.
What PipeEX PCF Export is used for
Teams use PipeEX PCF Export when they need a repeatable handoff from Revit piping into PCF-aware tools such as AutoCAD Plant 3D, CAESAR II, and AutoPIPE.
The proof point is a pilot PCF validated in your own downstream toolchain, not just a screenshot of the add-in inside Revit.
A useful evaluation starts with one representative routed system, the Revit year used by the team, the target downstream application, and a short checklist for line identity, components, coordinates, and required mapped attributes.
Revit to PCF workflow
PipeEX PCF Export reads Revit piping geometry, connector relationships, family identity, and mapped parameters, then writes a PCF file intended for downstream isometric or stress workflows.
The workflow is source-model first: fix disconnected elements, inconsistent line numbers, and missing shared parameters in Revit or in the PipeEX PCF Export mapping instead of hand-editing a PCF that will be overwritten on the next export.
That repeatability is the reason the site points buyers from the product overview to the guides, FAQ, trial request, and licensing pages before procurement.
Pilot proof points
A first pilot should show that the same Revit line can be exported, imported, reviewed, corrected at the source if needed, and exported again without rebuilding the route manually.
Use Plant 3D, CAESAR II, AutoPIPE, or the receiving tool your team already owns to verify continuity, component sequence, branch behavior, size/spec/material fields, and any contract attributes that appear in deliverables.
When the pilot passes, the next decision is commercial: trial access, quote-based pricing, and the right static or floating license model for the team.