Revit models, AutoCAD drawings, and point-cloud scans are outgrowing the servers, VPNs, and backup windows most architecture and engineering firms built years ago, and the fix is usually storage, bandwidth, and workflow changes, not new design software.
A 400MB Revit file doesn’t stay 400MB once it’s open. Revit users commonly report memory use climbing toward 8GB once a project is open across multiple views for active editing, well past the size of the file itself. Multiply that by six people syncing to the same central model over a branch-office VPN and the slowdown stops being a mystery. Nobody misconfigured anything. The math just caught up with the network.
Most firms don’t call an IT company because a model crashed once. Rarely that simple. They call because backups quietly stopped finishing overnight, or because the branch office says loading last week’s drawing set now takes ten minutes instead of one. Both point to the same root cause. Infrastructure sized for the file sizes of ten years ago, running the workloads of 2026. That gap is exactly what VJNetworks’ managed IT services for design and engineering firms are built to close, and it rarely starts with buying new software.
What’s Actually Inside a Modern BIM File
Big files. Bigger every year. Revit central models on a real commercial project commonly run 200MB to 1GB or more. Sometimes bigger. Autodesk’s own guidance acknowledges the problem directly: Revit files can become very large, up to 2GB or more, and the company publishes specific steps to shrink an oversized file back down, according to Autodesk’s guidance on keeping Revit file size manageable. AutoCAD drawings stay smaller on their own. Kilobytes up to maybe 20 or 30MB for a normal sheet. Push past 80 to 90MB, though, and most firms consider that large enough to slow performance on a typical construction set.
None of that is a flaw. Not in Revit. Not in AutoCAD. Both do exactly what they were built to do. The problem sits underneath them. The network was specified for a much smaller file, years before anyone on staff was running 3D coordination across four disciplines in the same model.
Why Synchronize with Central Feels Slower Every Quarter
Here’s how the collaboration actually works, briefly. The central model lives on a server. Each team member works from a local copy. Simple so far. “Synchronize with Central” is bidirectional. It uploads whatever that person just changed, then pulls in everyone else’s updates since the last sync. Locking happens at the workset or element level, not across the whole file. But when several people sync at once, everyone waits.
Distance makes it worse. In a specific, measurable way. Autodesk’s own network documentation for Revit Server recommends a minimum sustained bandwidth of roughly 3Mbps and benchmarks its performance testing at 65 milliseconds of WAN latency, a figure meant to represent a realistic multi-office deployment. A standard branch-office VPN connection frequently falls short of both numbers at once, especially during the exact hours everyone is trying to sync simultaneously before lunch.
| What You Notice | What’s Actually Happening |
|---|---|
| Synchronize with Central takes 5+ minutes at 4pm | Multiple people syncing the same central model at once, over bandwidth sized for email and browsing, not large file transfer |
| Overnight backups aren’t finished by morning | Storage volume grew faster than the backup window; compression barely helps CAD/BIM data the way it helps office documents |
| The branch office says everything feels “laggy” | WAN latency to the central file exceeds what worksharing was ever designed to tolerate well |
| A model occasionally comes back corrupted after two people sync at the same moment | A sync collision that clean infrastructure and disciplined worksharing practices are supposed to prevent |
| Opening a drawing set from the shared drive takes longer every month | Project storage is simply bigger than it was a year ago, and nothing about local storage or the network changed to keep pace |
Backups Weren’t Built for This Much Data
Project storage at architecture and engineering firms has grown fast. Not gently, either. It jumped from an industry average of 3.34TB in 2018 to 25.64TB in 2023, based on figures from Egnyte’s AEC Insights Report. Seven and a half times the storage, in five years, on infrastructure that mostly didn’t get resized to match.
Compression is part of why backup windows blow out first. CAD and BIM files are binary and dense. Compressing them doesn’t shrink them the way it shrinks a folder of Word documents and spreadsheets. Deduplication is the trick most backup systems use to avoid storing the same data twice, and it works far less efficiently here, because every version has meaningfully different binary content. A backup job that used to finish by 3am can end up still running when the office opens. Nobody touched the backup software. Nothing changed on purpose. The data just outgrew the window.
Signs Your Network Is the Actual Bottleneck
A few patterns show up over and over on firms running Revit, AutoCAD, Bluebeam, and Procore side by side:
- Central model files pushing past 1GB, and syncs that used to take 30 seconds now taking several minutes
- A second or third office added in the last two years, with no corresponding change to the network
- Backup completion times creeping later each month, not because anyone changed the backup software
- Remote or hybrid staff opening drawing sets over a VPN connection that predates the firm’s current project load
- Someone on staff has quietly started keeping a personal copy of “the good version” of a model, because they don’t fully trust the sync
- IT has been asked more than once this year whether it’s “just time for new computers”
That last one comes up constantly, and it’s usually the wrong question. Faster workstations help. A little. They don’t fix a 65-millisecond latency problem. Or a storage system that’s outgrown its backup window.
What Actually Fixes This, Roughly in Order of Cost
There’s no single silver-bullet product here. Pretending otherwise would be dishonest. Revit, AutoCAD, Bluebeam, and Procore are four genuinely different tools doing four different jobs, model authoring, drafting, PDF markup and review, and construction project management. None of them solve a network problem alone. The fix is almost always a mix, scaled to firm size and budget, which is exactly the kind of scoping VJNetworks walks through as part of its network infrastructure planning work with design and engineering clients.
Local, fast storage for active projects still matters more than most firms expect in a cloud-first year. Tiered storage puts active projects on fast local NVMe or SSD storage. Completed, archived projects move off to cheaper cloud storage instead. That split handles the two access patterns BIM work actually creates. Big sequential transfers when someone opens a multi-gigabyte model. Constant small random-access requests during live coordination. Cloud storage alone struggles with both.
For firms with more than one office, WAN optimization matters almost as much as raw bandwidth. Without it, a CAD file opening across a standard WAN connection can reportedly take up to an hour on a bad day, according to reporting in Manufacturers’ Monthly’s coverage of accelerating CAD performance over the WAN. An hour. For one file. SD-WAN technology, which bonds connections and routes traffic along the best available path in real time, is documented to meaningfully improve CAD and CAM application performance for firms running multiple locations against the same shared files.
Cloud-based collaboration is real. It works, when it’s set up correctly. Autodesk Construction Cloud is the current product. BIM 360 is the same company’s older platform, still functional for existing customers, but it’s no longer where Autodesk puts new investment. Both let teams co-author a central model hosted in the cloud instead of on a single office’s server. Every location connects to the same hosted file. Nobody’s syncing across a WAN to somebody’s basement server closet anymore. It’s a real shift in where the bottleneck sits. Not a magic fix. It comes with its own bandwidth requirements, worth checking against your actual connection before committing.
GPU-accelerated virtual workstations are the least-known option. For the right firm, the most useful one. A cloud-hosted virtual machine with a dedicated GPU lets someone run Revit or AutoCAD remotely with near-local performance, because the heavy rendering work happens next to the data instead of being dragged across a slow connection. Pricing runs roughly $70 to $180 per user per month without a GPU allocation, more with one. Out of reach for a two-person shop. Squarely in range for a firm juggling five simultaneous active projects.
Where to Actually Start
Not every firm needs all four fixes. Not even close. Rarely all four. A ten-person shop running two active projects out of one office has a very different network reality than a 60-person firm with three locations and a construction-administration team living in Procore all day — exactly the kind of construction and engineering IT environment where these storage, bandwidth, and backup gaps show up first. The honest starting point is almost always the same, though: measure what’s actually happening before spending money on any of it.
That means checking real sync times against what they were a year ago, checking whether backups are actually finishing inside their window, and checking WAN latency to every office instead of guessing. Backup and continuity planning belongs in that same conversation, since a backup job that silently stops finishing is also a data-loss risk, not just an inconvenience.
Things People Ask Before Calling Us
Do we need to buy new design software, or is this actually a network problem?
How big does a Revit project actually have to get before it becomes an IT issue?
Would moving everything to the cloud fix our CAD and BIM slowdowns by itself?
We can’t do a full infrastructure overhaul this year. What’s the cheapest fix that actually helps?
Does Autodesk Construction Cloud solve the network problem on its own?
Every firm we’ve talked to about this problem is running a different mix of Revit, AutoCAD, Bluebeam, and Procore, on a different number of active projects, out of a different number of offices. No two setups match. There isn’t a single fix that applies evenly. There’s a starting point: an honest look at where the actual bottleneck sits, storage, bandwidth, or backup capacity, before spending on any of them. VJNetworks has worked with small and mid-size firms across the Tri-State area for over 20 years, and when something breaks mid-sync, someone from my team responds within 15 minutes. Not the next business day.
A free IT assessment checks real sync times, backup completion, and bandwidth against what your project load actually needs. No obligation, no sales pitch.