Use Case of Ideate Explorer for Revit
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
I recently had a client who came to me, unable to open a project from Autodesk Construction Cloud (ACC). A quick clearing of their local ACC cache/files allowed the client to open the project, but it still took nearly 10 minutes to open. This wasn't entirely shocking due to the size of this project (700+ MB), but I thought "we can improve this". Based on how much was in the local ACC cache, I had a feeling this model hadn't had much maintenance. I recommended the basics - auditing and compacting - as well as reviewing linked content. There were quite a few items that Revit was unable to locate and load - likely long-abandoned items that were just adding to the opening time while Revit hunted for them. Not to mention their paths belonging to various project user's personal file folders.
As a cherry on top, I decided to run the model through Ideate Explorer to take a closer look. The thing that stood out to me the most was how quickly I was able to identify red-flag warnings as well as the quantity, something the native Revit warning tool doesn't do (see below). Nothing immediately stood out to me in the native warning list.The native Revit warning tool results
When I ran Ideate Explorer, I immediately saw 243 warnings for members with identical instances, which added bulk to the model and could cause issues with scheduling. The tool even lets me jump to a view that shows the elements in question. There are a million other things I can do with Ideate Explorer, but this was a quick, easy, and obvious win for cleaning up this model.
Ideate Explorer Warnings