Automate approved Prism exports
Configure licensed Ultra command-line exports using approved model snapshots, versioned request files and machine-specific authorisation.
- Applies to
- Current Prism release · Navisworks Manage 2025–2027
- Availability
- Ultra; licensed per pipeline
- For
- BIM automation engineers and platform administrators
- Last reviewed
What headless export is
The Ultra headless command submits an existing Paramora ModelSnapshot to the same licensed target runners and capability checks as the interactive connector. It is not a generic NWD reader, does not automate the Navisworks user interface and does not bypass target availability or validation.
Prerequisites
- An Ultra agreement that explicitly covers the automation pipeline and target capabilities.
- A supported machine with the complete signed Prism engine and required target components.
- A version-matched .pmsnap produced through an approved connector or capture workflow.
- A validated export-request JSON file using the documented protocol version and stable IDs.
- A machine-scoped online entitlement or separately issued offline license appropriate to the deployment.
Command syntax
Paramora.Engine.exe --export <request.json> --snapshot <model.pmsnap>
Paramora.Engine.exe --export <request.json> --snapshot <model.pmsnap> --license <license.json>Progress and the final job result are emitted as JSON lines on standard output; sanitized diagnostics use standard error. Treat the final job status and report as authoritative rather than only the process exit or presence of a target file.
Production pipeline design
Pin compatible inputs
Version the snapshot producer, protocol, request schema, preset/profile and signed component channel together.
Validate before publish
Write to a staging destination, require the terminal validation policy and promote only a complete verified artifact set.
Capture evidence
Retain the request digest, input identity, target hashes, resolved profile, report, component/product version and timestamps.
Bound resources and cancellation
Set job time, memory and storage expectations and handle cooperative cancellation before force-cleanup.
Protect authorization
Use machine-scoped credentials or offline licenses from their intended secret store; never commit them beside request files.
Evidence for automation support
- Product and component version, update channel and target format.
- Sanitized request JSON or a minimal reproduction with private paths and credentials removed.
- Final JSON result, report and relevant standard-error diagnostics.
- Input snapshot schema/version and a hash; do not attach a customer model unless support explicitly requests a secure transfer.
- Expected versus actual result, first failing timestamp with time zone and whether the same request succeeds interactively.