Understand export presets and profiles
Understand built-in profile intent, configure the current workspace and standardize repeatable company exports.
- Applies to
- Current Prism release · Navisworks Manage 2025–2027
- Availability
- Built-in engine profiles; company profiles require Pro; managed signed profiles require Ultra
- For
- BIM managers and recurring export operators
- Last reviewed
Built-in and managed profiles
| Profile intent | Managed use | Trade-off |
|---|---|---|
| Fast Export preset | Engine or managed workflow for a quick test of the ordinary Standard pipeline | Fastest settings, basic semantics, minimal properties and usually larger geometry. |
| Balanced Export | Engine baseline or managed routine company exports | Cleaned and instanced geometry with standard semantics, properties and checks. |
| High Quality Export | Managed archive, high-fidelity review or difficult geometry | Strong cleanup and rich data with slower processing. |
| Coordination IFC | Managed model checking and coordination exchange | Optimized geometry, coordination classes and strict validation. |
| Facility Management IFC | Managed asset, space and systems handover | Richer FM data with required storey completeness. |
| Selected Objects Only | Managed workflow for a controlled subset | Layers current selection over a base preset. |
| Discipline Export | Managed workflow for one or more trades | Filters by resolved discipline, not display-name guessing. |
| Source File Export | Managed federation split by appended model | Preserves source identity and shared alignment. |
What a resolved profile controls
- Scope intent and stable identifiers for selected objects, sets, disciplines or sources.
- Geometry quality, cleanup, instancing, normals and target-specific options.
- Semantic depth, materials, storeys, systems and property families.
- Validation level, check families, report behavior and performance budgets.
- Target-specific container, coordinates, structure, packaging and compatibility values.
The same model, resolved profile and explicit options produce the same export intent. The report records the internal profile key and final values so a reviewer can identify what actually ran.
Review before writing
Use Review, and a checks-only path where the selected target exposes one, to resolve the settings and filters without replacing the final model. Confirm the effective object count, property and validation depth, output structure and warnings before the final export.
Create a company standard
Define the receiving contract
Name the format, version, scope, coordinates, required properties, validation policy and receiving applications.
Choose a defined intent
Use the balanced defaults, a coordination/FM specification or an installed company profile rather than changing unrelated options.
Test representative models
Cover disciplines, large coordinates, sections, repeated objects and the largest practical federation.
Publish a controlled profile
Pro organizations can distribute company profiles; Ultra deployments can use managed signed profiles for stronger central control.
Record ownership and review
Give the profile an owner, supported application versions and a retest date. Keep old delivery rules versioned rather than silently changing them.
What Prism remembers
- The output folder, advanced-settings visibility and workspace preferences are remembered per Windows user.
- A missing or damaged local setting falls back to safe defaults rather than blocking the export.
- Company overrides layer over the resolved profile; Review shows the final values that will run.
- Do not treat a remembered output folder or scope as project approval. Verify both on every job.