Can one pilot prove every project line will export correctly?
No. Use the first pilot to validate the workflow and mapping assumptions, then test additional line types that contain unusual components, branches, or project-specific attributes.
Guide
How to export PCF from Revit
This guide explains the practical workflow from a Revit piping model to a PCF file that can be validated in Plant 3D, CAESAR II, AutoPIPE, or a similar downstream tool.
The page focuses on model hygiene, export setup, and post-export checks rather than marketing claims.
Requirements before export
Before exporting PCF, confirm the Revit model is authored in a supported Revit release, PipeEX PCF Export is installed for that year, and the target downstream tool can import PCF for the use case you are testing.
Choose one representative piping system for the first pilot. It should include straight pipe, elbows, tees, valves, branches, and at least one item that depends on project-specific attributes such as material, insulation, rating, or line number.
Agree on acceptance criteria before pressing export: the PCF should preserve connectivity, line identity, coordinates, component identity, and the mapped fields your Plant 3D isometric or stress-analysis workflow actually consumes.
Prepare the Revit piping model
Check continuity first. Disconnected pipe ends, placeholder fittings, and mixed systems can produce split PCF output or missing components downstream.
Normalize naming before export. Line numbers, system names, service tags, and equipment references should follow one convention instead of being corrected manually after the PCF is generated.
Review families and shared parameters. If a valve, flange, reducer, or special item needs a downstream code, rating, or material field, that data should exist in the Revit content or in a mapped shared parameter before export.
How PipeEX PCF Export maps Revit piping data to PCF
PipeEX PCF Export treats the Revit-to-PCF handoff as a repeatable mapping problem: Revit piping elements provide geometry, connectors, component identity, and shared parameters; the export turns those into PCF records that downstream tools can read.
The important setup work is deciding which Revit parameters are authoritative for line IDs, specs, materials, pressure class, insulation, and tags. A stable mapping avoids one-off cleanup and makes re-export after model changes practical.
Do not assume every client attribute is automatic. If a downstream deliverable requires a field, include it in the pilot checklist and verify it in the imported PCF result.
Step-by-step export process
Open the Revit model, isolate the representative piping system, and confirm the active view or selection contains the intended line scope.
Run PipeEX PCF Export with the agreed mapping profile, then save the generated PCF with a clear model issue, date, and line identifier so the file can be traced back to the Revit state that produced it.
Archive the PCF together with the model milestone and validation notes. Re-export after major model merges, family swaps, or line-number changes instead of hand-editing an older file.
Validate the PCF in Plant 3D
Import the PCF into Plant 3D or the ISO engine used by the team and verify that the line appears as one connected route with the expected branches and components.
Compare the generated isometric, bill of material, and line metadata against the Revit model. Pay special attention to line numbers, valve tags, sizes, component classes, and any field that procurement or construction uses.
If Plant 3D resolves a fitting incorrectly, record whether the cause is missing Revit data, a family mapping issue, or an import-side catalog/spec rule. That distinction prevents the team from fixing the wrong layer.
Validate the PCF in CAESAR II or AutoPIPE
For stress workflows, import the same PCF into CAESAR II, AutoPIPE, or the solver used by the project and check the route geometry, branch points, supports if mapped, and component sequence.
Stress tools often require additional engineering assumptions after import. Treat PCF as the geometry and component handoff, then document which loads, boundary conditions, or analysis-specific fields are still completed in the solver.
A successful pilot should show that Revit-to-PCF removes re-digitizing effort while still leaving engineering review and solver setup under the stress engineer control.
Common export errors and fixes
Missing line segments usually point to broken Revit connectivity, excluded selection scope, or a component family that does not expose the expected connectors.
Wrong tags or blank attributes usually point to inconsistent shared parameters, unmapped fields, or values stored on a different element than the export profile expects.
Unexpected component names or SKEY-like representation usually point to a family-to-PCF mapping issue. Fix the mapping or family data, then re-export and compare the new PCF against the previous pilot output.
FAQ for the first pilot
Should the team edit the PCF manually after export?
Manual edits may be useful for diagnosis, but production fixes should normally happen in the Revit model, family data, or PipeEX PCF Export mapping so the result is repeatable after re-export.
What evidence should be kept after validation?
Keep the model issue, exported PCF, downstream import result, screenshots or reports, and a short checklist covering connectivity, line identity, components, coordinates, and required attributes.