Best Known Methods

These are the practices that consistently produce clean, constructible routes. None of them are required to run Auto BIM Route — but following them gives the routing algorithm the best chance of getting it right the first time, and keeps processing fast and stable.

Electrical Zone Settings: dimension adjustments

The Electrical Zone Settings control how much room ABR has to work in — the width of the routing zone (the horizontal space above the ceiling) and its height (the vertical space below the ceiling). How wide or tight you set those zones is the single biggest lever on the quality of the result.

Widening zones (more space)

• Pro — grants the routing algorithm maximum flexibility to stagger conduits, avoid obstacles and resolve clashes.
• Con — increases the risk of unconstructible routes, excessive bends and complicated obstacle maneuvers.

Narrowing zones (less space)

• Pro — forces smoother, highly constructible, realistic routing paths.
• Con — limits routing flexibility; overly tight constraints can cause processing failures.

The sweet spot is usually the tightest zone that still routes cleanly — start narrow for realistic paths, and only widen if the algorithm can’t find a solution.

Final coordination workflow

Treat ABR as the engine for the first pass, then finish by hand:

1. Algorithmic routing — use ABR to generate the initial, baseline conduit paths.
2. Manual refinement — manually adjust conduit elevations and stub locations for precision where it matters.

Interference management: model categories & Revit links

Before you run, trim what ABR has to look at:

• Uncheck unnecessary model categories and Revit links prior to execution — do this from the Start window category selection or the Graphics / Clash settings.
• Every active category is another set of obstacles ABR tests against. Reducing them sharply cuts clash-detection processing time and makes the whole run noticeably faster.

3D conduit processing: batch workflows

Don’t process the whole floor at once:

• Route in small, targeted groups rather than everything in one pass.
• Keep each batch tight — ideally two active panels (a single From / To pair) or one localized conduit trunk.
• Smaller batches drastically reduce computation time and help prevent crashes on large models.

Elevation changes: kicks vs. stubs

When you change a run’s elevation, the size of the change decides what ABR draws:

• Small elevation changes create a kick — a smooth diagonal transition.
• Large elevation changes create a stub — a vertical up/down.

As a rule of thumb, roughly 1 ft 6 in and below gives a kick, and 1 ft 7 in and above gives a stub. Minimizing the zone width encourages the smoother kick instead of a stub — handy when you want the run to stay tucked up tight.