Architecture and engineering firms need symmetrical bandwidth, because large models, drawing sets, point clouds and renders move up to the cloud as often as they come down, and low, steady latency, because cloud collaboration and file sync between offices punish a jittery connection. For most firms, symmetrical fiber sized to the largest files you move on deadline, a backup line, and a sensible file storage strategy matter more than any single speed figure.
A 20-person design firm can move more data in a week than a 200-person office in another industry. Building information models grow large, laser scans and drone surveys produce enormous datasets, and teams in different offices and at home work on the same project at the same time. This guide covers how that changes the connection, the network inside the office and the links between offices.
What runs on a design firm's connection
- CAD and BIM authoring on powerful workstations, with project files stored on a file server, in the cloud or both.
- Cloud collaboration and worksharing, where team members sync changes to a shared model.
- Point clouds from laser scanning, and photos and models from drone surveys.
- Rendering, on local machines or a cloud rendering service.
- Drawing exchange with clients, consultants and contractors through shared platforms.
- Remote workstations for staff working from home on models too heavy for a laptop.
- Video meetings and design reviews with screen sharing.
- Plotters and large-format printers, and the phones.
Upload and latency both matter
Every sync pushes your changes up and pulls others' changes down. Publishing a drawing set, sending a model to a consultant or uploading a scan for processing all go out of the building. A connection with a large download and a small upload, which describes many cable plans, slows the whole firm whenever someone sends a big file. Our guide to symmetrical vs asymmetrical internet explains why.
Latency matters as much as bandwidth for some workflows. Opening large files from a file server in another office, or working on a remote workstation, depends on how quickly each small exchange completes. A line with high latency, jitter or packet loss feels slow even when the speed test looks fine. Our guide to latency, jitter and packet loss covers how to measure them.
Three ways firms store project files
| Approach | How it works | Network implication |
|---|---|---|
| Office file server | Projects live on a server in the main office; other sites and home staff reach it over the network | Fast inside the office; remote access depends heavily on upload and latency at the main office |
| Cloud storage and collaboration | Projects live with a cloud provider; everyone syncs to it | Every office and home user needs good upload; the main office is no longer a bottleneck |
| Hybrid with local caching | Files live in the cloud, with a cache appliance or service in each office holding active projects locally | Local speed for active work, with the sync running in the background, so upload still decides how quickly changes reach other offices |
None is right for every firm. The choice depends on how many offices you have, how much work is done from home, and how your design software handles collaboration. The network should be planned alongside that decision, not after it.
More than one office
Firms with several offices need the offices to behave like one. The options range from secure tunnels over each office's internet line, to managed SD-WAN that uses several lines at each site and steers traffic over the best one, to private Ethernet links between offices for firms that move huge files between sites daily. Our guide to multi-site internet covers the design.
If your projects live with a major cloud provider, a private connection to that provider can give more consistent performance than the public internet for heavy sync and remote workstations. Our cloud connectivity page explains how those links work.
Remote workstations and home working
Heavy models do not run well on laptops, and copying a large project home is slow and risky. Many firms keep the computing power in the office or the cloud and let staff connect remotely to a powerful workstation. That works well when:
- The office or cloud end has plenty of upload and low latency.
- Home users have a stable connection with a decent upload, wired to the router where possible.
- Remote access uses an encrypted, multi-factor connection, with no remote desktop ports open to the internet.
Test the experience from a typical home before committing. A model that feels responsive in the office can be painful over a poor connection.
Site offices and fieldwork
Construction administration and site visits bring their own needs: a temporary office on a site, scans uploaded from the field, and photos and markups sent back the same day. Our guide to internet for construction sites covers temporary connections, fixed wireless and cellular options.
Rendering, plotting and the conference room
Rendering is the other heavy load. Rendering on local workstations or an in-house render machine uses the internal network, not the internet, but cloud rendering services mean uploading the full scene, textures and all, and downloading the frames. For animations and large stills on deadline, that upload can be the slowest step. Time a real job before relying on cloud rendering for a client presentation.
Inside the office, wire every workstation. Models and drawing sets opened over Wi-Fi from a file server or a local cache are slow and unpredictable, and a wired gigabit connection to each desk costs little compared with the time it saves. Plotters and large-format printers receive big print files and belong on the wired network too. The conference room is where clients see the work, so wire the room system, keep a tested way to present a model from a visitor's laptop without joining the staff network, and check video quality at the busiest time of day.
Opening or moving an office
Qualify the address across several carriers before signing a lease. A building where a carrier is already lit can typically be connected in 2–4 weeks; one that needs construction can take 60–90 days, which is long enough to delay a move. Ask specifically about upload speeds and whether a second carrier can provide a backup on a different path.
Security and confidentiality
- Client drawings are confidential. Treat models and drawing sets as sensitive business information, with access limited to project teams.
- Some contracts carry security requirements. Public-sector and defense-related work can include contractual rules about how project information is stored and accessed. Check your contracts; this is general information, not legal advice.
- Separate networks for staff workstations, plotters and printers, visitors, and devices such as cameras and conference room systems.
- Backups kept off site and tested by restoring a real project. Ransomware has hit design firms precisely because their project files are irreplaceable.
A worked example
Hypothetical: the firm, file sizes and figures are invented to show the arithmetic. Check your own projects.
An architecture firm has 25 staff in two offices, keeps projects in cloud storage with local caching in each office, and has a cable plan with a 35 Mbps upload in the main office. On a renovation project, the surveyor delivers an 80 GB point cloud that has to go to the cloud for the team in the second office.
- The scan: 80 GB is about 640,000 megabits. At 35 Mbps, that is about 5 hours of fully saturated upload, in theory, and everyone else's sync waits behind it. At 500 Mbps it is about 21 minutes.
- Daily sync: 20 people saving model changes and publishing drawings send a steady stream of smaller uploads all day.
- Calls: design reviews with screen sharing add a few megabits each in both directions.
The scan explains why the second office complained that models were out of date. The firm moves the main office to symmetrical fiber at 500 Mbps, keeps cable as a backup on a different network, and adds the same at the second office. Bandwidth was the visible problem; the upload was the cause.
Choosing the circuit
A small firm on cloud storage is often well served by good symmetrical shared fiber with a backup line. A larger firm, or one that hosts project files and remote workstations in its own office, usually belongs on dedicated internet access with an SLA, a static IP block and consistent latency. Either way, size the upload for the largest files you move on a deadline day, not for an average Tuesday.
Questions to ask your provider
- Is the service symmetrical, and what is the upload speed in writing?
- What latency can we expect to our cloud provider and between our offices?
- Can the backup line come from a different network, with automatic failover?
- Are static IPs included for remote access?
- What are the options for linking our offices, and how do they fail over?
- How long will installation take at each address?
Get your offices priced
We qualify each address across several Tier 1 carriers, bring back the best offer, and price inter-office links in the same comparison. Carriers pay FiberX, so there is no markup, our lowest-price promise applies, and if your current setup already wins we will say so. In a building where a carrier is already lit, installation typically takes 2–4 weeks, and 60–90 days if construction is needed. Quotes are free with no obligation, you usually hear back the same day, and Phil Morales is your one point of contact. Send us your addresses, call 478-758-8091 or text (347) 870-0965.
