Last week’s forum activity centered on enhancing CAD systems’ efficiency and reliability. Members engaged in robust discussions on data governance training, debating its role in fortifying data integrity. There was a lively exchange on optimizing Navisworks clash detection, with participants sharing practical experiences. Additionally, troubleshooting broken references in PDM and the perennial question of grid naming conventions sparked thoughtful dialogue.
This Week’s Hot Topics
Training that strengthens CAD data governance
The community shared insights into effective training programs that bolster data governance, ensuring smoother project management. Read more here
Dialing in Navisworks clash tolerance
Members are tweaking clash detection settings in Navisworks to improve project outcomes, sharing tips on setting appropriate tolerances. Read more here
Preventing broken references in PDM
Avoiding broken references in PDM systems is crucial for efficiency; the community discussed strategies to maintain link integrity. Read more here
Do you skip I and O on grids
A lighthearted yet practical debate on whether to skip the letters I and O in grid naming to prevent confusion. Read more here
Looking forward to another week of insightful discussions. Keep sharing your knowledge and questions.
But @alee43, our best signal boost came from running discipline-specific clash tests with saved Search Sets and excluding fasteners/embeds, then setting MEP clearance equal to insulation thickness so the hits are meaningful. We save those settings in an NWF template so no one “turns the radio back up” later. Small caveat: IFC imports sometimes explode elements into parts, so spot-check your sets or you’ll miss pipe supports.
I started using Navisworks Compare to limit clash tests to only changed scopes, and last week’s drop cut our run time by half. We tag those deltas into a ‘Changed=Yes’ search set and only re-run the linked tests — just make sure everyone exports fresh NWCs or you’ll chase ghost moves. @alee43 this plays nice with your discipline sets; caveat: mirrored Revit elements can flip GUIDs, so sanity-check the first pass.