How should a manufacturer connect multiple sites?

With one identity system, one set of shared platforms, and links between sites sized for what genuinely crosses them. The mistake to avoid is replicating the head office arrangement at every location, which multiplies cost, maintenance and inconsistency without improving anything.

The principle that makes multi-site work is that a person should be able to arrive at any location and work normally: same sign-in, same access, same systems, same phone extension. That is achievable when identity and the core platforms are hosted, because then a site needs good connectivity and sound local network equipment rather than its own miniature version of everything. It also removes the situation where each location has developed its own way of doing things because nobody could support them centrally.

Connectivity between sites is the part that needs real design rather than a default. Work out what actually crosses the link: an ERP session is light, a full backup crossing every night is not, and video and voice need prioritising. Then size accordingly and provide a second path, because an isolated site is an idle site. Energy Logistix runs 24/7 across five sites at 99.99% uptime using SD-WAN, which uses multiple links intelligently rather than relying on one.

Two practical points. Standardise the equipment across sites, since one model of switch and one access point is far easier to support and stock spares for than five variations acquired at different times. And decide explicitly what happens at a site when its link fails, because in manufacturing an isolated location with a running line needs a plan rather than a phone call to head office. If you want your sites designed to work the same way, call 1800 456 567.