Skip to content

BlogWorkflows

BIM Clash Detection Against Existing Conditions

BIM Clash Detection Against Existing Conditions

BIM clash detection is the process of checking the discipline models of a building project against each other to find places where elements interfere, such as a duct passing through a beam. It is done before anything is built, so conflicts are resolved in design instead of on site. Autodesk describes the purpose as identifying cross-discipline interferences earlier in the design process. On a renovation the new design must also fit the building that is already standing, and that raises a second question: where do the existing conditions in the test come from. This guide covers the kinds of clash, how a clash test is run, and the two ways to bring existing conditions in, a scan-to-BIM model or the registered point cloud, with what each one catches and misses.

What is clash detection in BIM

Clash detection compares the geometry of two selections of model elements, for example the ductwork of the mechanical model against the beams of the structural model, and reports every place where they conflict. The check runs in coordination software such as Autodesk Navisworks, on a federated model: each discipline’s model linked into one file without being merged.

Autodesk’s Navisworks documentation defines three clash types, and a fourth idea, the time-based clash, comes from the same tool.

Clash type What it means Example
Hard clash Geometry of selection A intersects geometry of selection B by more than the set tolerance A duct runs through a steel beam
Clearance clash Geometry comes within a specified distance of other geometry, whether or not it touches A pipe leaves no room to remove a filter or open an access panel
Duplicate clash The geometry of selection A is the same as that of selection B The same fixture modeled in two files
Time-based (4D) clash A conflict checked over time, by linking clash tests to a construction sequence A crane path blocked by a structure that is built later

The first three rows follow the Navisworks definitions: a hard clash is “a clash in which the geometry of selection A intersects that of selection B by a distance of more than the set tolerance”, and the Clearance test type is described as checking “for geometry within a specific distance”. A clearance clash is often called a soft clash informally, but Autodesk uses ‘soft’ for clashes between moving objects, found by running Clash Detective at each step of an animation. Autodesk calls the time-based case time-based clashing with TimeLiner, and soft clashing for animated objects. The 4D example is ours; Autodesk’s overview says only that clash tests can be linked with Object Animation and TimeLiner.

How a clash test is run

A coordination cycle has the same parts on most projects.

  1. Assemble the federated model. Each discipline model is exported or linked into the coordination file in a common coordinate system. If the models do not share an origin, every result is wrong, so this is checked first.
  2. Define the clash tests. A test pairs two selections, for example mechanical ducts against structure, and a test type: hard, clearance or duplicates.
  3. Set rules and tolerance. Autodesk states that “tolerance controls the severity of the clashes reported and the ability to filter out negligible clashes”. Clash rules let the team ignore pairs that are expected to touch.
  4. Run and group. Results are grouped by level, by system or by the element behind many of them.
  5. Assign and resolve. Each group gets an owner in a coordination meeting. The owner moves the element, the team accepts the clash, or it goes back to the designer.
  6. Re-run. The tests run again on revised models until the open count is acceptable to the team.

Who runs the tests, who attends the meeting and how often it happens are set in the BIM execution plan. The Penn State BIM Project Execution Planning guide, part of the National BIM Standard, exists so that “all parties are clearly aware of opportunities and responsibilities” in the project’s BIM workflow.

Why existing conditions matter

On a renovation, addition or tenant fit-out, the new ducts, pipes and equipment must fit around what is already in the building: the beams, the old ductwork, the sprinkler main, the conduit run someone added in a past fit-out. If the existing systems are not in the federated model, the test cannot find clashes with them, however well it is configured. The new design passes and the clash is found in the ceiling during installation.

Existing conditions usually come from the original drawings, which show the building as designed or as reported at closeout, not as it stands. The guide to as-built drawings vs record drawings explains the gap, and existing conditions documentation for renovation covers choosing a record for the work at hand. A scan replaces assumption with measurement. The remaining question is what form that measurement takes inside the clash test.

Option 1: a scan-to-BIM model of the existing systems

In the first method the registered point cloud is modeled into Revit elements, and that existing-conditions model is linked into the federated model alongside the new design. Ducts, pipes, beams and equipment become objects with categories, sizes and systems, so every Navisworks test works as it does between any two models: selections by category, rules, grouping, clearance tests.

For MEP, the level of development matters. The BIMForum specification added LOD 350 because the working group “identified the need for an LOD that would define model elements sufficiently developed to enable detailed coordination between disciplines, e.g. clash avoidance/detection”. It describes LOD 350 as intended for “construction-level coordination”. LOD 300 is the common level for a scan-to-BIM model, and a clearance or hard test against a duct modeled at LOD 300 is only as good as that duct’s modeled size and position. BIMForum writes LOD for designed elements; for existing conditions the LOD is used by convention, with the accuracy stated separately as a USIBD Level of Accuracy. The guide to LOD in BIM gives every level, and the MEP scanning service page describes what we model from a scan.

A model is also an interpretation. Whoever models the cloud decides where a duct’s centerline sits, and the model carries that decision’s error on top of the survey’s. State the model’s accuracy separately from its level of development, using the USIBD Level of Accuracy specification.

Option 2: the registered point cloud as a reference

In the second method the registered cloud is attached to the coordination file as it is, with no modeling of the existing systems. A coordinator can place the new design in the cloud, look for conflicts and measure from the points.

Autodesk’s Clash Detective documentation says the tool lets you “conduct clash tests between traditional 3D geometry (triangles), and laser-scanned point clouds”. So a point cloud can be one side of a Navisworks test, and the other side is ordinary model geometry. The page does not describe how a cloud is selected, what test type to use or how tolerance applies to points, and it states that Clash Detective is available to Navisworks Manage users only. Confirm the settings in your version before relying on a test.

What the cloud lacks is structure. It is a set of points, not a set of ducts: nothing says which points are a sprinkler main, so a test cannot be set up as “new ductwork against existing pipes”. The results say that new geometry meets scanned points at a location, and a person must decide what the points are. Scan data also holds everything in view, including furniture and people, and nothing behind a surface. A line of sight that never reached the top of a duct leaves a gap, and a gap produces no clash. The guide to registered vs unregistered point clouds explains why the cloud must be registered into one coordinate system before any of this works.

Model vs point cloud for clash testing

Test against a scan-to-BIM model Test against the point cloud
What is in the test Modeled objects with categories and sizes Points with no object identity
Test setup Selection by category or system, as with any model Selection of the whole cloud; verify the method in the software
Result meaning Object A conflicts with object B New geometry meets scanned points at a location
Grouping and assigning By system, level, element By location, reviewed by a person
Upfront work Modeling the existing systems Registration and cleanup only
Accuracy Survey accuracy plus modeling decisions Survey accuracy of the points, limited by point spacing
Covers what the scanner did not see No No
Fits Heavy MEP coordination, repeated test cycles Spot checks, a single route, verifying a model

Neither method detects what the scanner could not see. Pipes above a hard ceiling and framing inside a wall are in neither the cloud nor the model unless access was opened for the scan.

Which to use

Use the model where many trades will test against the existing systems over several cycles and results must be grouped and assigned by system, such as an MEP replacement or a lab fit-out. The modeling is paid for once and reused by every test until conditions change.

Use the cloud where the question is narrow: whether one new route clears one corridor, whether a piece of equipment fits through a door and a stair, or whether the existing model matches what is standing. Some projects do both, modeling the systems the new design touches and keeping the cloud attached to check the model.

Whichever method, state the tolerance in the scope. Autodesk notes that tolerance filters out negligible clashes, so one set too loose can hide real conflicts. We give no single number here: the right one depends on the scanner, the registration and the LOD, and it belongs in the BIM execution plan. We deliver the registered point cloud, and models of existing MEP systems from it, which the coordination team then tests against. The workflow from scan to model is in the scan-to-BIM workflow guide, and importing a point cloud into Revit covers the first step on the modeling side.

FAQ

What is clash detection in BIM?

Checking discipline models against each other to find places where elements conflict, such as a duct through a beam, so that they are resolved in design instead of on site. It is run on a federated model in software like Navisworks.

What is the difference between a hard clash and a soft clash?

A hard clash is geometry that intersects beyond the set tolerance. A clearance clash is geometry that comes within a set distance without touching. Autodesk uses ‘soft clash’ for clashes between moving objects, checked with an animation.

Can Navisworks run clash detection against a point cloud?

Autodesk’s Clash Detective documentation says you can conduct clash tests between traditional 3D geometry and laser-scanned point clouds, and that the tool is available to Navisworks Manage users. The page does not detail the test setup, so check the settings in your version.

Do I need a scan-to-BIM model to run clash detection on a renovation?

No. A model gives objects that tests can select and group by system, which suits heavy coordination. A registered point cloud can serve as a reference for a narrow check, with a person judging the results.

What LOD is needed for clash detection?

BIMForum introduced LOD 350 for detailed coordination between disciplines, including clash detection. Existing-conditions models from a scan are often LOD 300, and the LOD should be set in the scope with a separate accuracy statement.

Who is responsible for resolving clashes?

It is assigned in the BIM execution plan. Each clash group is given an owner in the coordination meeting, usually the discipline whose element is moved.

Sources

Ready when your site is.