Report & coordinates
Reads a clash report — Navisworks XML or HTML, a CSV or Excel sheet, or a BCF — and maps every clash point into this model. Nothing is created until you place markers.
Clash report
Format
Detected from the file's content, not its extension — a renamed export still reads. Override only if the detection is wrong.
Navisworks Clash Detective XML · 3 clash tests · 131 results · declared units mm · 86 results carry a size attribute.
Also loaded: 199 interference result(s) from the Interference Check — rows arrive in this document's internal feet, so the coordinate step below is skipped for them (Identity mapping). They carry no status and sit on the (none) chip.
Coordinate source
Shared reads this model's own project location and derives the mapping from it, then proves the mapping by round-tripping a probe point. Project Internal treats the report's numbers as Revit internal coordinates. Manual applies your own offset and rotation.
Source
Report units
Project base point: E/W 420.500 m N/S 318.250 m Elev 0.000 m True north 14.0000°
Mapping: Shared basis established — T, u, v probed through GetProjectPosition · round trip 0.00 mm ✓
Mapping: Shared basis established — T, u, v probed through GetProjectPosition · round trip 0.00 mm ✓
Duplicate clash points
Navisworks reports one result per intersecting pair, so a single duct through a layered wall arrives as several clashes at nearly the same point. Points closer together than this collapse to one marker. Set 0 to keep every clash.
Collapse withinmm
Clashes
TO PLACE
119
after collapse + filter
MAPPED
131
of 131 results
COLLAPSED
12
within 150 mm
CLASH TESTS
3
in the report
WITH A SIZE
86
size attribute read
Filter
Clash test
Status
New 0
Active 0
Reviewed 0
Approved 0
Resolved 0
(none) 0
119 clashes · 3 tests
A clash point is not an element — it has no ElementId until a marker exists for it — so these rows are the report's. Click a row to zoom the active view to that point; Export writes the filtered set to .xlsx with both report and internal coordinates.
Place markers
Places one family instance at every clash point that survived the filter, on the nearest level, with a sequential Mark. Only OneLevelBased families can be positioned this way — anything else is refused before a transaction opens.
Marker family
Family
Type
'CustomClashPoint' is OneLevelBased — 55 marker(s) will be placed on the nearest level to each clash point · Mark continues from CLH-0411.
Place only clashes that have no marker yet
64 of the 119 already carry a marker — 55 will be placed.
Marker size
A clash report carries no geometry size. Leave this off for a fixed-geometry coordination marker; turn it on to write a size into every instance, taken from the report where it carries one and from these figures everywhere else.
Write size parameters
Width mm
Height mm
Diameter mm
'Diameter' is a TYPE parameter on this family, so a size cannot be written per marker — one write would resize every instance of the type. Those writes will be declined. Make it an instance parameter in the family editor, or leave size writing off.
55 placed · grouped by clash test
By now every row is a real element, so this is the suite's shared review grid: click a row to select and zoom that marker in Revit.
Status
Every clash in the report, matched to the marker placed for it. Mark a clash completed when it has been resolved in the model — the state is stored on the marker itself, so it survives a save, travels with the model, and is still there the next time this report is imported.
NEW
55
no marker yet
PLACED
58
marker, still open
COMPLETED
6
resolved in the model
IGNORED
0
set aside
NOT IN REPORT
2
marker, clash gone
Filter
Show
Reconciled against 66 markers in the model. Two markers name a clash the re-run no longer reports — the crossing is gone, or the test was rebuilt.
113 outstanding · 3 ticked
3 ticked — Mark completed stamps them done on the marker itself.
Settings
Saved to cit_config.json beside this tool. The size-parameter lists are tried in order and the first name that exists, is writable and takes a length wins.
Marker identity
Mark prefix
State parameter
The state is written as a short [CIT|…] token inside that parameter, alongside anything already written there — your own text is preserved. Changing the parameter after markers exist orphans the ones already stamped.
Markers are stamped prefix + a sequential number, continuing from the highest number already in the model. Keep this different from the MEP Opening Tool's WOT- prefix: both write the same Mark parameter, and a shared prefix makes the two sequences renumber each other.
Size parameter names
Width
Height
Diameter
Comma separated. A name of Radius receives half the diameter. These are shared with the MEP Opening Tool, so a change here changes both.
Size from the report
Navisworks reports no sizes of its own, but a model appended with its parameters carries them as object attributes. Any of these keys, found on either side of a clash, is read as that clash's size.
Export
Open the file after export