Monday is groundbreak on a Texas AI campus. The fence is up. The pad is dirt. There is no fiber, no house power, and no carrier coverage worth betting a superintendent's day on. Eighteen months later the first hall is enclosed, commissioning crews are walking cooling skids, and security is treating the place like a live facility. The permanent campus network is still a drawing.
Those are two different jobs. Construction needs coverage before anything exists to attach a radio to. Commissioning and early operations need a campus-grade wireless layer after the building is up — but before the owner's fiber, private wireless, and security stack are actually in production. Most programs plan wireless for the finished campus and leave both windows to personal phones, hotspot kits, and a camera vendor who discovers there is nothing to backhaul the footage.
We already covered why a construction jobsite cannot wait on the carrier, and which package to turn on at groundbreak. This post is the data-center version of that problem: what the Mobile Connectivity Unit does before steel goes up, what it does after the halls are live, and why those two windows are the same deployment — not two separate capital projects.
Why It Breaks Down
The failure is not "the site needs 5G." The failure is treating wireless as a day-two install that starts after power and fiber land. On an AI campus, day two is often a year away — and the day the first hall is weathertight is not the day the campus network is ready.
- Nothing to plug into on day one. Groundbreak starts before conduit, house power, and permanent backhaul. Crews, machines, drones, and the gate still need a network that carries its own power and its own uplink.
- The campus is a bad radio environment. Steel, reinforced concrete, outdoor substations, and long outdoor runs between halls defeat trailer Wi-Fi and overloaded public LTE. Coverage that works at the office trailer dies at the far pad.
- Security changes the day the building is a building. During dirt work, the risk is copper, diesel, and equipment walking off. After enclosure, it is perimeter video, access control, and a site that cannot afford blind spots — with uplink that has to be predictable, not best-effort.
- Commissioning is a different traffic mix. Cooling, electrical, water, and environmental sensors generate a steady stream that construction tablets never did. The network that coordinated rebar crews is not automatically the network that carries commissioning telemetry.
- Hall 1 and Hall 2 overlap. The first hall can be in fit-out while the next pad is still a construction site. A static install sized for one phase is dark for the other.
- Permanent wireless arrives on a capital calendar. Owner private 5G, DAS, and campus fiber are real programs. They are also procurement-and-install programs. They do not show up the morning the GC needs BIM, PTT, and cameras.
Every week the build waits on comms shows up in the schedule. Every hour commissioning loses a sensor path or a camera feed shows up as a delayed hall. The cost of a temporary, operated network is small next to either number — if it is scoped as a bridge, not as a substitute for the campus design.
What Actually Works
The useful model is not "install private 5G and keep it forever." It is one private 5G platform that rolls on when the site has nothing, reconfigures when the job changes shape, and rolls off when the owner's network is actually ready. Same van. Two windows. Different VLANs, talkgroups, and camera rules.
Before construction — and through the build
This is the window we already run on industrial jobsites. The Unit arrives with its own power, Starlink and cellular failover, and a CBRS Band 48 sector on the mast. The private network is live within an hour of being positioned. Foremen get tablets that reach the GC's document system. Crews get on-prem push-to-talk that does not die when the nearest tower congests. Concrete, environmental, and equipment sensors get an IoT VLAN instead of a clipboard. Drones get a dedicated command path instead of a consumer SIM.
Perimeter cameras and edge AI run on the van — footage stays on the on-prem NVR, not in a vendor cloud the owner never approved. As the footprint moves from the first pad to the next hall, the Unit repositions and the network is back in about an hour. No trench. No stranded AP on a fence that gets moved next month.
After construction — commissioning and early operations
When the first hall is enclosed, the job does not become "wait for the campus core." Commissioning crews need a campus-wide layer for walkdowns, punch-list photos, vendor laptops, and the telemetry coming off cooling plants, switchgear, and environmental monitors. Security needs continuous video and access events with uplink they can count on. Field techs and any inspection robots or vehicles need mobility between buildings and outdoor yards — the thing trailer Wi-Fi never did well.
The same platform covers that window. Traffic gets re-segmented: construction VLANs wind down, commissioning and security VLANs take priority, identity-based access stays on devices you provisioned. Edge inference can watch perimeter, gates, and exclusion zones without sending operational video off-site. If the owner's fiber is in one building and dark everywhere else, the Unit is the outdoor and inter-hall layer until the permanent plant is commissioned — not a second architecture you have to design from scratch.
The overlap is the real job
On a multi-hall campus, construction and operations share a fence line for months. Hall 1 can be in commissioning while Hall 2 is still dirt, copper, and night-shift theft risk. That is not two vendors and two networks. It is one operated platform with isolated segments: GC and trades on the build side, owner and commissioning on the live side, security watching both. When Hall 2 needs the van closer to the new pad, it moves. When the owner's campus wireless finally takes Hall 1, that segment comes down cleanly.
Two windows, one deployment
Pre / during build: coverage, PTT, IoT, drones, and jobsite security from a self-powered private 5G cell — no fiber required. Post-build / commissioning: campus mobility, commissioning telemetry, and on-prem video analytics until the permanent network is in production. Overlap: Hall 1 and Hall 2 on isolated VLANs from the same Unit, then demob or slide to the next pad.
The Unit on Your Site
The Clover IQ Mobile Connectivity Unit is a Sprinter with three racks, a telescoping mast, satellite backhaul, and a self-contained power system. It is an operated deployment, not a pallet of radios left in a conex. Pre-construction, it is the jobsite network. Post-construction, it is the commissioning and early-operations layer. It is not the owner's 15-year campus wireless design — and it should not be scoped as one.
Week one — survey, then live
A paid site survey maps the current pad, the phase plan, and where commissioning will start. The Unit deploys from that plan. Private 5G is live within an hour of positioning. Full handoff — coverage documented, cameras on the NVR, IoT onboarded, PTT tested — is an eight-hour job, not a six-month carrier request.
Through the build
Weekly on-site maintenance and 24/7 remote monitoring are part of the monthly engagement. When the work moves, the van moves. A 30-minute response commitment applies during active deployments. You are not opening a ticket with a camera vendor who blames the hotspot vendor.
Through commissioning
When the first hall goes weathertight, we do not rip the network out and start a new project. Talkgroups, VLANs, and camera rules get rebuilt for commissioning and security. If the owner wants the three-station control room for the cutover window, that is a Full Command scope change on the same van — not a new install.
When the campus network is actually ready
Mast down, devices recovered, footage handed off per the data agreement, deployment report in two business days. No orphaned APs in a hallway that is now a live data hall. If the next pad is already breaking ground, the Unit slides instead of demobbing. If you want it as backup through the permanent cutover, that is a defined overlap — not an accidental lease you forgot to cancel.
Three packages, same platform — Network, +Devices, or Full Command. Large multi-hall programs usually start at Full Command because security and commissioning video are not optional on a data center fence. Smaller or shorter pads can start lighter and add a tier without swapping vendors. Minimum subscription is three months. Setup is waived at six months and longer, which is how most campus programs actually run.
What It's Worth
The return is schedule and risk, not a prettier RF map. Bring a hall online a week earlier and you have moved revenue on a facility that costs more per acre than almost anything else being built in Texas right now. Lose a week to comms, a theft, or a commissioning hold, and you have paid for the Unit several times over. The figures below are illustrative — validate them against your contract value, hall count, and commissioning calendar.
- Construction coordination: Supervisors on personal phones and failed uploads burn time every shift. We have walked that math on general construction jobsites. A data center GC with a large supervisory staff does not escape it.
- Theft and materials: Unmonitored pads lose equipment, copper, and diesel. One recovered incident on a 12-month build often clears the engagement. After enclosure, the same cameras become the owner's temporary perimeter — not a second capital CCTV project.
- Commissioning hold time: A cooling or electrical walkdown that cannot get sensor data or vendor connectivity off the hall floor is a delayed energization. The Unit is cheaper than a slipped go-live, even if you never count construction theft.
- Capex you do not strand: Buying a campus wireless plant to cover an 18-month build, then discovering it is in the wrong place for operations, is how temporary sites get permanent-network economics. Monthly coverage that demobs — or slides to Hall 3 — keeps that risk off the books.
You still need a permanent campus design. Fiber, indoor wireless, and the owner's security architecture do not go away. The Unit is what you run until that design is commissioned, and what you keep on the next pad while Hall 1 is already earning. That is a different purchase than "make private 5G the forever layer."
Questions from the Field
Does the Unit become our permanent data center network?
No. It is a mobile, operated platform sized for construction, commissioning, and the overlap between halls. When the owner's fiber and campus wireless are in production, we demob or move to the next pad. If you need a long-term private 5G program inside the finished facility, that is a different scope — we will say so on the discovery call instead of stretching a van into a building system.
When should the van arrive, and when does it leave?
Arrive with groundbreak — or with the first week of site establishment if that is earlier than dirt work. Leaving when the last hall is enclosed is usually too early. The useful end date is "permanent campus network commissioned" or "next pad needs the coverage," whichever comes first. A network that only covers construction leaves commissioning on the same personal phones you just spent a year replacing.
Can construction crews and commissioning teams share one network?
They can share one platform. They should not share one VLAN. Construction, commissioning, IoT, and security are isolated. Devices are provisioned; a trade contractor does not get a path into the owner's commissioning segment because they are on the same jobsite. That segmentation is part of the survey, not a setting someone finds after a scare.
What happens when our fiber and permanent private wireless come online?
We run a defined cutover: confirm the owner path, move critical devices, keep the Unit as failover for a short overlap if you want it, then decommission. Footage and device inventory go back to you. Nothing stays plugged into a live hall because someone forgot a temporary AP. If Hall 2 is still a jobsite, the van relocates instead of going home.
We are building several halls over a few years. Do we re-buy this every time?
No. The monthly model is meant to follow the campus. One engagement can cover Hall 1 construction, Hall 1 commissioning, and Hall 2 dirt as a continuous subscription with repositioning included. You are not buying a new architecture per hall. You are keeping the same operated cell on the part of the campus that does not have a finished network yet.
Straight Talk
Clover IQ does not operate data centers, and we do not pretend a Sprinter is a campus core. We build and run a mobile private wireless and edge-AI platform for sites that need coverage before — and sometimes after — permanent infrastructure exists. That is a construction problem we already solve on industrial jobsites. AI campuses make it sharper because the building becomes a high-security facility while the next pad is still a construction site.
If your campus already has fiber, indoor wireless, and a security plant that works, use that. If you are still writing the permanent private 5G RFP, do not wait for that paper to cover groundbreak. The Unit is the bridge: live in week one, useful through commissioning, gone when the owner network is real — or still on site for the hall that has not poured yet.
Start with a 30-minute discovery call. Bring the hall schedule, when fiber is actually promised, and whether commissioning security is in scope. We will tell you if the engagement fits, which tier to start on, and what a paid site survey would lock down before the first crew shows up without signal.
