One network across the whole campus, not forty Wi-Fi islands.
A campus is dozens of buildings, open ground between them, and thousands of devices that move. Wi-Fi covers it in islands with gaps and handover drops; the public network does not reach indoors or keep the data private. A private 5G network covers the whole estate as one, and keeps it on-site.
DomainWireless, private cellular network
PlatformsFaststream Radio, Connected Edge
ScopeSite survey to operating network
Binding constraintSeamless coverage across buildings and grounds, data kept on the estate
DisclosureRepresentative programme; customer not named
CONTEXT
Where this started.
The campus — many buildings, open ground between them, a dense and mobile population of devices — ran on Wi-Fi that covered it in islands: gaps outdoors, dropped handovers between access points, and no guarantee for the traffic that mattered.
A private 5G network covers the whole estate as one network: radios placed for indoor and outdoor coverage, an on-premises core so data and policy stay on the campus, and managed devices that stay attached as people and machines move.
The programme is a coverage-and-integration problem — survey the estate, place radios for seamless indoor and outdoor coverage, stand up the core, and tie into the campus IT, security and building systems — not a Wi-Fi refresh.
CHALLENGES
4 problems, named.
Stated before any of them had an answer.
01
Coverage in islands, not a campus
Wi-Fi covered buildings separately and left the ground between them thin; coverage had to be engineered across the whole estate, indoors and out.
02
Devices move and must not drop
People, AGVs, carts and AR/VR headsets roam across buildings and grounds, so handover had to be seamless — exactly where dense Wi-Fi struggles.
03
The data has to stay on the estate
Residency and policy required an on-premises core and local breakout, so campus traffic and identity stay on-site.
04
It has to join campus IT and security
A new network only helps if it integrates with the identity, security, building-management and application systems the campus already runs.
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.
Estate RF survey — mapping coverage across buildings and the open ground between them, indoors and out, with the campus's device density and movement in mind.
Radio placement — indoor small cells and outdoor units positioned for seamless coverage across the whole campus, not building by building.
On-premises core — a compact 5G core on-site so identity, policy and user traffic stay on the estate and survive an outside outage.
Slicing and QoS — guaranteed service for the traffic that matters — AGVs, AR/VR, voice and security — separated from best-effort.
Device onboarding — SIMs and eSIMs, routers, handhelds, AGVs and headsets provisioned and managed on the private network.
Systems integration and operations — tie-in to campus identity, security, building-management and application systems, with monitoring and updates.
WHAT WAS HARD
The parts that consumed the schedule.
Rarely the subsystem that sounds difficult.
01
Seamless across the whole estate
Covering one building is easy; holding a device attached as it moves between buildings and across open ground, without a drop, is the campus design problem.
02
Density without contention
Thousands of devices in one place is where Wi-Fi contends; the private-5G design has to keep guaranteed traffic ahead of best-effort.
03
Keeping identity and data on-site
An on-premises core and local breakout make residency and policy real, and add operational surface the campus IT team has to run.
04
Joining what already runs
The value appears when the network feeds the identity, security and building systems the campus already uses, and those integrations take the schedule.
OUTCOME
What resulted.
One campus, one network
Seamless wireless across every building and the ground between them, engineered to the estate rather than stitched from access points.
Devices that stay attached
People, AGVs and headsets move across the campus without dropping, with guaranteed service for what matters.
Data kept on the estate
An on-premises core and local breakout keep identity, policy and traffic on-site and running through an outside outage.
Integrated and operable
Tied into campus IT, security and building systems, with monitoring and updates the estate can run.
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 covers a campus in islands with gaps outdoors and dropped handovers between access points, and it contends under high device density. Private 5G covers the whole estate as one network, keeps devices attached as they move, and keeps identity and data on-site.
02
Does campus data stay on the estate?
Yes, with an on-premises core and local breakout. Identity, policy and user traffic stay on the campus, which matters for security, for continuity when the outside link fails, and for data residency.
03
Can it carry AGVs and AR/VR?
Yes — on a dedicated slice with guaranteed latency and bandwidth. AGVs, AR/VR and voice get service held ahead of best-effort traffic, which dense Wi-Fi cannot guarantee.