The site had no coverage, so we built it a network.
A private 5G deployment is a network engineering job, not a product install. The site had coverage the public carrier was never going to build, devices that had to move without dropping, and data that could not leave the premises — so it needed its own network, engineered to the place rather than the street.
DomainWireless, private cellular network
PlatformsFaststream Radio, Connected Edge
ScopeSite survey to operating network
Binding constraintCoverage, control and data residency on-site
DisclosureRepresentative programme; customer not named
CONTEXT
Where this started.
The site — large, partly indoor, partly open, with moving vehicles and machinery — had no usable public coverage and requirements a carrier could not meet: guaranteed capacity, deterministic latency and data that stays on the premises.
A private 5G network answers that by scoping a full cellular network to the site: its own radios placed for the coverage needed, its own on-premises core so traffic stays local, and its own managed devices.
The programme is therefore a coverage-and-integration problem — survey, radio placement, core, devices and the tie-in to the site's existing systems — rather than a box to plug in.
CHALLENGES
4 problems, named.
Stated before any of them had an answer.
01
The public network was never coming
Coverage had to be engineered to the site — indoors, outdoors, around metal and moving obstacles — not inherited from a carrier's rollout.
02
Devices move and must not drop
Vehicles, handhelds and machinery roam across the site, so handover and mobility had to be seamless, which Wi-Fi does not guarantee.
03
The data has to stay on-site
Residency and continuity required an on-premises core and local breakout, so the network keeps running when the outside link fails.
04
It has to join what already runs
A new network is useless if it does not integrate with the SCADA, cameras, safety and IT systems the site already depends on.
ARCHITECTURE
How it was built.
The coverage and the on-premises core are marked because they are why a site runs its own 5G at all: coverage it engineers, and control and data it keeps.
CONTRIBUTION
What Faststream did.
The scope of the work, rather than a capability list.
Site survey and RF planning — mapping coverage against the real obstacles, indoors and out, with the site's moving equipment in mind.
Radio placement — indoor small cells, outdoor units and hazardous-area variants positioned for the site, not the street.
On-premises core — a compact 5G core on-site so control and user planes stay local and survive an outside outage.
Slicing and local breakout — guaranteed service for control, safety and video, with edge compute kept on the premises.
Device onboarding — SIMs, routers, handhelds and sensors provisioned and managed on the private network.
Systems integration and operations — tie-in to the existing SCADA, MES, camera and safety systems, plus monitoring and updates.
WHAT WAS HARD
The parts that consumed the schedule.
Rarely the subsystem that sounds difficult.
01
Coverage where metal moves
Modelling coverage is easy on paper; holding it as vehicles and machinery move through the site, blocking and reflecting, is the real survey work.
02
Seamless mobility
Keeping a moving device attached across cells without a drop is exactly where Wi-Fi struggles and where the private-5G design earns its place.
03
Keeping data on-site
An on-premises core and local breakout are what make residency and continuity real, and they add operational surface the site has to be able to run.
04
Joining legacy systems
The value only appears when the network feeds the systems the site already uses, and those integrations are where the schedule quietly goes.
OUTCOME
What resulted.
Coverage the site engineered
Wireless across the whole site, indoors and out, designed for its geometry rather than inherited from a carrier.
Devices that stay attached
Seamless mobility for vehicles, handhelds and machinery, with guaranteed service for the traffic that matters.
Data kept on the premises
An on-premises core and local breakout, so user data and edge compute stay on-site and survive an outside outage.
Integrated and operable
Tied into the systems the site already runs, with monitoring and updates the site can operate.
Confidentiality
Customer projects are presented at property, capability, outcome and integration level. Customer names, internal architecture, confidential deliverables and commercial terms are not disclosed. Where a detail would identify a customer it is omitted rather than approximated. More is available under a non-disclosure agreement, within the limits the customer has agreed.
Wi-Fi struggles with wide-area coverage, seamless mobility and guaranteed latency for dense moving devices; the public network was never going to be built out to this site and would not keep the data local. Private 5G engineers coverage to the site, keeps devices attached as they move, and keeps control and data on the premises.
02
Does the data really stay on-site?
Yes, when the network is built with an on-premises core and local breakout. User traffic and edge compute stay on the site, which matters for latency, for continuity when the outside link fails, and for data-residency requirements.
03
What decides where the radios go?
The site survey. Coverage is modelled against the real obstacles — buildings, metal, moving vehicles — and the radios are placed to hold coverage as the site operates, indoors and outdoors, which is different from covering an empty map.