Message 1 of 1
Version Control Headaches in ACC Docs
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
Hi all,
I’m trying to tighten our clash detection and issue-tracking workflow inside ACC. We have multiple trades uploading on different schedules at Eracore, and it gets messy deciding when to “lock in” coordination models before running new clash tests.
For those managing large coordination jobs, do you run weekly clash cycles in ACC or still prefer to do so in Navisworks first? We’ve been experimenting with both, but it’s hard to keep everyone aligned on which issues are still active.
Would appreciate hearing how other teams structure their review process to stay on top of model updates and avoid duplicate issue tracking.