When AEC firms talk about hardware for BIM workflows, Revit usually dominates the conversation. That makes sense. It’s the tool most team members touch every day, and its performance characteristics are well-documented and frequently discussed. However, for the people running coordination, the most demanding hardware workload on a project often isn’t Revit at all.
Navisworks Manage, the primary tool for multi-discipline clash detection and model coordination, processes data differently than any other major AEC application. Understanding how it handles models helps explain why the hardware demands are higher than most teams expect, and why underpowered coordination machines create problems that show up at exactly the wrong moments in a project.
How Navisworks Handles Model Data
Revit loads model data selectively. It caches geometry, reads from file as needed, and manages what’s actively in memory based on what you’re working with. This approach works well for the authoring workflow, where you’re typically focused on a portion of the model at any given time.
Navisworks takes a different approach. When you open an NWD or NWF file that aggregates models from multiple disciplines, Navisworks loads the full federated dataset into system RAM to process it. All of the geometry, all of the clash test data, all of the linked model information. This is what allows it to perform clash detection and coordination analysis across disciplines, but it means the RAM requirement scales directly with the size of the combined model, not just the piece you’re actively reviewing.
On a small commercial project, this isn’t a significant concern. The combined model might be several hundred megabytes, well within what a 32 GB machine can handle. On a hospital, a data center, an airport terminal, or a large mixed-use development, the federated Navisworks model can easily reach 10 to 20 GB of raw data. That’s where the hardware demands become a genuine constraint.
What Happens When RAM Isn't Enough
The failure mode for Navisworks under RAM pressure is well known to anyone who’s tried to run coordination on an underpowered machine. Load times become measured in minutes. Navigation through the model is sluggish, with the application pulling data in from the page file because physical RAM is exhausted. Clash test runs that should complete in minutes take much longer. And at some point, the application may simply crash, taking the coordination session with it.
This tends to happen at the worst possible times. Coordination sessions are scheduled, deadline-driven, and involve multiple team members. A machine that can’t load the full model without degrading to unusable performance creates a bottleneck that affects the entire coordination workflow, not just one person’s experience.
The irony is that the machine experiencing the problem is often spec’d well for the Revit workflow. It runs Revit fine. The BIM modelers using it day to day have no complaints. But Navisworks has a different RAM demand profile, and a machine that handles the authoring workload without issues can still be the wrong tool for the coordination role.
What the Right Configuration Looks Like
For VDC coordinators and BIM managers running Navisworks coordination on projects of moderate scale, 64 GB of RAM is the practical minimum. It provides enough headroom to load a meaningful federated model while leaving the operating system and other applications room to run without performance degradation.
For teams running coordination on large infrastructure, healthcare, or complex mixed-use projects where the federated model regularly exceeds 10 GB, 128 GB becomes a justifiable configuration. The cost difference between 64 GB and 128 GB of DDR5 memory is modest relative to the value of a coordination machine that can handle the full project dataset without constraint.
Fast NVMe storage also matters for Navisworks, both for the initial load time of large NWD files and for the scratch space the application uses when processing large clash test runs. A PCIe Gen 4 or Gen 5 NVMe drive with ample free space keeps the application from being further constrained by slow I/O.
Run Navisworks without interruption.
If your coordination team is experiencing performance problems in Navisworks, or if you’re building a hardware configuration for a new project involving large, federated models, we can help you size the hardware correctly.
Reach out to the BIMBOX team for a configuration consultation.