Validate an export and read the reports
Configure Prism checks, IDS validation, halt-on-blocking policy, HTML/JSON/CSV reports and BCF issue output, then decide whether a result is deliverable.
- Applies to
- Current Prism release · Navisworks Manage 2025–2027
- Availability
- Summary on all plans; full reports, IDS and BCF require Pro or higher
- For
- BIM coordinators, reviewers and quality managers
- Last reviewed
What Prism validates
Prism validates the resolved request before work begins, checks the generated target before publication and produces a final summary. Target-specific checks cover the structure and invariants the chosen format can prove; a successful write alone is not treated as a valid delivery.
- Configuration and non-empty effective scope.
- Stable identity and duplicate-identifier conditions where the target uses them.
- Geometry validity, finite coordinates, supported primitives and target structure.
- Required properties, units and semantic completeness according to the selected profile.
- Container integrity, references and companion-file joins for multi-file targets.
Errors, warnings and blocking policy
| Result | Meaning | Action |
|---|---|---|
| Error | A required condition failed or the output cannot be trusted as requested. | Correct the cause and rerun. Do not deliver the failed target. |
| Warning | Prism completed but found a limitation, fallback or quality concern. | Assess it against the project requirement and record the decision. |
| Information | Context about scope, configuration, provenance or checks. | Keep it with the report for traceability. |
Each built-in check has a fixed blocking or warning severity. Enable the checks the delivery requires, and turn on Halt on blocking failure when the project contract requires all blocking checks to pass. Allowing publication with warnings does not make those warnings automatically acceptable.
IDS conformance checking
Use the approved IDS file
Confirm its version, project applicability and owner before loading it.
Choose the failure policy
Decide whether a failed specification blocks publication or is reported for review.
Run a checks-only pass
Test the requirement against a representative scope before the final full export.
Review by specification
Separate missing applicability, missing property and invalid value failures instead of treating one count as the answer.
Keep the inputs together
Archive the IDS version, model result and report as one review record.
Reports and BCF
| Artifact | Use |
|---|---|
| Validation summary | Final export status and counts; available on every plan. |
| HTML report | Human review, sign-off and sharing inside the project team. |
| JSON report | Automation, evidence pipelines and structured analysis. |
| CSV report or attributes | Tabular review and exact companion joins where the target supports them. |
| BCF issues | Route supported findings into a BIM coordination issue workflow. |
| Resolved profile log | Record the resolved profile, scope and effective configuration that produced the output. |
Make a delivery decision
Confirm the requested scope and format
A clean report for the wrong subset or target is not approval.
Resolve every error
Correct source data, scope, configuration, component or destination failures and rerun.
Assess warnings
Assign an owner and written acceptance or remediation for each material warning.
Verify in the receiver
Open the final output in the intended application and repeat the project acceptance checks.
Archive evidence
Keep target, companions, report, profile and requirement versions under the same delivery record.