By product

Navisworks

95 actions in Navisworks Manage and Simulate 2023–2027. Coordination is mostly triage, triage is mostly clicking — this gives that time back.

What it can reach

Walkthrough: a coordination round

Start with the shape of the problem, not the list:

“Run every clash test and tell me which ones got worse since the last run.”

Then group and triage in the chat — status, comments, and a viewpoint and image per result, so the report shows the problem:

“Group the structural-vs-MEP clashes by level, then export an HTML report with images for Level 3.”

Clash results, grouped and triaged from the panel. The grouping is a real Clash Detective grouping, not a copy.

Walkthrough: keeping the federation honest

Half of every coordination meeting is about which version someone is looking at.

“What’s in this federation, and when was each model last refreshed?”

From there: append the new architectural NWC, remove what is superseded, refresh the rest, and report what changed.

The federation, listed with what each model contributes.

Walkthrough: search sets that follow the naming standard

Search sets are the thing everybody agrees to and nobody maintains. Describing one is faster than building it:

“Make a search set for every pipe over 200 mm diameter and put it in the MEP folder.”

Folder included — the set lands where your standard says, not at the bottom of the list.

Walkthrough: the 4D schedule

Fourteen TimeLiner actions: tasks, geometry links, task types, appearances, date roll-up, CSV export. The day-saver is rule-based bulk attach:

“Attach these 400 objects to the schedule by rule — dry run first.”

Ask for the dry run explicitly and you get the mapping to check before anything is committed.

Full tool list

Every action with a one-line description is in the toolbox entry, and the product page answers the common questions.

Guides

Navisworks clash detection with AI: from clash test to report