A manufacturing plant depends on the internet for more than email: cloud ERP and production software, shipping labels, machine vendors' remote support, cameras and links to other sites all ride on it. The priorities are getting fiber to an industrial address, which often means construction and should be quoted early, keeping plant-floor equipment on its own network apart from office IT and the internet, and having a backup on a different path so shipping keeps moving when the primary drops.
Plants are not offices with machines attached. The address is often at the edge of a carrier's network, the building is full of metal, some of the equipment runs software older than the people operating it, and an outage is measured in trucks that do not leave. This guide is about buying connectivity with those facts in mind.
Start with what actually stops
Before choosing a circuit, map what depends on it. Machine control usually does not; the business systems around it often do.
| System | Needs the internet? | What happens in an outage |
|---|---|---|
| PLCs and machine control | Usually not | Lines keep running on local control |
| HMIs and local SCADA | Usually not, if hosted on site | Operators keep their screens |
| Cloud MES or production tracking | Yes | Work orders, counts and quality data stop recording, or queue locally if the software supports it |
| Cloud ERP | Yes | Order entry, inventory and purchasing stop |
| Shipping and labels | Usually yes | Carrier labels and documents cannot be printed, so trucks wait |
| Phones | Yes, on cloud phone systems | Calls fail over to mobiles, if that was set up |
| Cameras and door access | Depends on whether they are cloud-managed | Recording may stop; doors may fall back to local rules |
| Vendor remote support | Yes | A broken machine waits for a technician on site |
The result of this exercise is usually clear. If shipping and production tracking stop without the internet, the plant needs a backup line. If they do not, a single good circuit may be enough.
Getting fiber to an industrial address
Industrial parks and older manufacturing districts are often outside the dense parts of carrier networks. Expect three possible situations:
- Lit: a carrier already has fiber in the building, and service is typically installed in 2–4 weeks.
- Near-net: fiber runs nearby, and a lateral must be built into the site, typically 60–90 days, with a construction cost recovered as a one-time charge, a longer term or a higher monthly rate.
- Off-net or no fiber nearby: the options are a longer build, fixed wireless where there is a line of sight, or shared fiber or coax where it reaches the office end of the building.
Get construction quotes in writing early, from more than one carrier, because the differences between them can be large. Our guide to special construction costs explains how those charges are built and negotiated. For the circuit itself, plants that run shipping and production systems in the cloud usually want dedicated internet access with an SLA as the primary.
Keep plant-floor systems apart from office IT
Plant-floor equipment, often called operational technology or OT, is built to run for many years. Many controllers and HMIs cannot be patched easily, and some run old operating systems that can no longer be updated at all. Those devices should never be reachable from the internet, and they should not share a flat network with office laptops and email.
- Separate networks for office IT and the plant floor, with a firewall between them that allows only the specific traffic production software needs.
- A buffer zone between the two for systems that both sides use, such as a historian or a file transfer point, so neither side talks directly to the other.
- No direct internet access for controllers. If a cloud service needs plant data, it should come through a gateway designed for that.
- An inventory of every device on the plant floor, what it runs and who supports it. You cannot protect equipment you do not know is there.
The layered approach is described in industrial security standards such as the IEC 62443 series, and US cybersecurity agencies have repeatedly warned against connecting industrial control systems directly to the internet. Our cybersecurity page covers firewalls and protection for the office and network edge.
Remote access for machine vendors
Machine builders and integrators often need remote access to diagnose problems, and it saves days compared with waiting for a technician. It is also one of the most common weak points in plant networks, because it is often set up quickly and then forgotten. Safer practice:
- No permanently open ports or remote desktop connections from the internet to the plant floor.
- A controlled remote access gateway, with a separate account for each vendor and multi-factor authentication.
- Sessions turned on by your staff when needed, limited in time and to the machine concerned.
- A log of who connected, when and to what.
Wi-Fi on the plant floor
Metal racking, machinery, high ceilings and electrical noise make plant floors hard for Wi-Fi. Handheld scanners, tablets on carts and wireless sensors need coverage designed from a survey, often with industrial-grade access points mounted for the space. Our guide to internet for warehouses and logistics covers coverage among racks in more detail, and our managed network and Wi-Fi service handles surveys, segmentation and monitoring.
Cameras and the upload they need
Cameras are where plant upload needs most often surprise people. A camera system that records on site uses almost no internet bandwidth, except when someone views footage remotely. A system that streams every camera continuously to the cloud can need a large, constant upload. Know which you have, or which you are about to buy, before sizing the circuit.
Backup, power and diversity
- A second circuit from a different network, ideally entering the site on a different path. Two circuits sharing one conduit can fail together; see route diversity and redundancy.
- Fixed wireless or cellular as the backup where only one cable route reaches the site.
- Power: a UPS for the network equipment and the carrier's equipment, and a plan for what stays on during a power cut.
- Failover that switches automatically. SD-WAN can also steer traffic between lines and connect several sites.
More than one site
Many manufacturers run a plant, a warehouse and an office in different places, sometimes in different states. How they connect depends on what passes between them:
- Everything lives in the cloud. Each site needs good internet and a backup, and the sites rarely talk to each other directly. SD-WAN can manage the lines at every site from one place and fail over automatically.
- A shared system lives at one site. If the ERP server, file storage or a production database sits at the main plant, the other sites need a dependable path to it: a private Ethernet connection between the sites, or encrypted tunnels over the internet managed by SD-WAN.
- Large files move between sites, such as CAD models, machine programs or inspection images. Size the links for those transfers, not just for day-to-day traffic.
Keep the plant-floor separation consistent across every site. A well-segmented main plant connected to a flat network at a smaller site is only as safe as the smaller site.
A worked example
Hypothetical: the plant, devices and bitrates are invented to show the sizing method. Camera bitrates vary widely with resolution and settings, so check your own.
A single-site plant runs two shifts, with about 60 people using computers, tablets or scanners. It uses cloud ERP, a cloud production tracking system and a cloud shipping platform that prints carrier labels for about 60 shipments a day. It is installing 32 cameras.
- Cameras streamed to the cloud: at an assumed 4 Mbps per camera, 32 cameras need about 128 Mbps of upload, around the clock.
- Cameras recorded on site: near zero constant upload, with short bursts when a manager views footage remotely.
- Everything else: ERP, production tracking, shipping, phones and email for 60 users, comfortably under 100 Mbps at peak.
The plant chooses a local recorder with cloud backup of selected clips, which removes the constant 128 Mbps. It orders 500 Mbps dedicated internet access from a near-net carrier, accepting a construction quote and a 90-day timeline, and adds a fixed wireless backup, which can be installed far sooner and carries shipping and phones in the meantime. Office IT and the plant floor go on separate networks, and vendor remote access moves to a gateway with per-vendor accounts.
Questions to ask your provider
- Is any carrier already lit at this address? If not, what does construction cost and how long will it take, in writing?
- What can serve the site while construction is underway?
- Can the backup come from a different network, on a different physical path or a different technology?
- What upload speed will we have, and is it guaranteed?
- What is the repair commitment, and does it cover nights and weekends when our second shift is running?
- How would you separate office IT from the plant floor, and handle vendor remote access?
- If we add sites later, how would they connect to this one?
Get the site qualified
We qualify industrial addresses across several Tier 1 carriers and bring back construction quotes and timelines in writing, with the runner-ups so you can see the market. Carriers pay FiberX, so there is no markup, our lowest-price promise applies, and if your current setup already wins we will say so. Quotes are free with no obligation, Phil Morales is your one point of contact, and you usually hear back the same day. Send us the site address, call 478-758-8091 or text (347) 870-0965.
