Skip to main content

Clash Report

Clash results, past the XML.

Who owns it, how long it has been open, and whether coordination is actually converging.

Report pages

Clash Overview Clash Detective Clash Aggregated Clash Tooltip Comments Tooltip

Supported sources

Navisworks

See the setup below for template access and required inputs.

Choose your clash source

Use Navisworks Clash Detective results exported as XML. Frame reports on those results; it does not perform clash detection. The local XML workflow and uploaded clash snapshots are different sources. Choose the matching option in the template dialog rather than mixing their setup instructions.

Set up a clash dashboard

  1. Export a known clash test from Navisworks with its results and element references.
  2. For a local-file report, choose the local clash template and set its XML file parameter in Power BI Desktop. Follow the local clash walkthrough.
  3. For Frame-managed results, upload the clash export against the appropriate model, wait for processing, and choose that source when generating the report.
  4. Compare the number of results and status totals with the Navisworks export. Check one test’s tolerance and one known clash.
  5. Use the detail pages to review ownership and status. Viewer context requires the corresponding model and usable element references.

Read the results correctly

Missing assignees or dates remain missing inputs, not evidence of zero delay. Historical analysis needs comparable snapshots; one XML export cannot establish a trend. A local XML report still needs file access at refresh time, while the model viewer uses its separate model connection. Review template access before using the report with your own project.

How Frame builds it

One export, or every export

Keep it local Clash XML exported from Navisworks Local template a file path, no upload One snapshot re-export to refresh Or upload each cycle Every export one per coordination run Frame stamped, then merged Aggregated cycle over cycle
Frame does not run clash detection — it reads what Clash Detective exports. Uploading each cycle is what turns a pile of tests into a trend.

Datasets in this report

FRAME_ClashResultsCurrent
One row per clash, with status, assignee, distance, coordinates, approval and resolution dates, and a status colour for driving the viewer.
FRAME_ClashTestsCurrent
One row per clash test, with tolerance, selection sets, and new, active, reviewed, approved, and resolved counts.
FRAME_ClashElementsCurrent
The elements involved in each clash, including the source file each one came from.
FRAME_ClashCommentsCurrent
Comment threads on individual clashes, with author, status, and date.

Read more

Build reports that drive action

Discover the benefits of Frame today.