Implementation
Custom solutions and implementation
This page describes implementation and workflow support that may follow after a team validates PipeEX PCF Export in its workflow.
The primary evaluation path remains the product and trial pages; custom work is secondary and scoped.
When services apply
Custom solutions are appropriate after the team understands PipeEX PCF Export and has a real PCF workflow to validate. They are not the first step for a buyer who has not tested the add-in.
Typical service work is bounded: mapping workshops, family or template alignment, rollout planning, export QA checklists, and small automation tasks around a confirmed Revit-to-PCF process.
The goal is to help the customer standardize a repeatable handoff, not to replace project engineering, model authoring, or downstream software administration.
What stays out of scope
Open-ended BIM outsourcing, full plant modeling, contract engineering sign-off, and guaranteed behavior inside third-party tools are outside the normal custom-solutions scope.
If a downstream tool rejects a PCF, the fix may be in Revit model data, family mapping, target-tool rules, or project standards. A scoped engagement should define which layer is being investigated before work begins.