XoomPark's AV-Ready Staging Evidence Pilot is a 30-day test in one market: score 10-25 private sites for autonomous-fleet ground-service use, then build sample reservation, session, and SLA evidence records.
The AV-Ready Staging Evidence Pilot is XoomPark's first commercial offer: a focused, 30-day engagement in a single metro where XoomPark identifies and scores 10-25 private sites for autonomous-fleet ground-service use, then produces sample reservation, session, and SLA evidence records against those sites. It is a structured way to test, in one market, whether off-depot private capacity can be qualified, reserved, and proven without committing to a long build. The output is a scored site list plus a working evidence trail a fleet-ops team can inspect.
| Attribute | Detail |
|---|---|
| Duration | 30 days, one market |
| Sites scored | 10-25 candidate private sites |
| Use cases | Staging, overnight storage, charging-adjacent queueing, recovery holding, PUDO access |
| Deliverables | Scored site list, access-rule profiles, sample reservation/session/SLA evidence records |
| Who it's for | Fleet-ops, eMobility, and ground-service teams testing off-depot capacity |
| What it is not | Not a long-term contract, not a charger build, not a maintenance program |
What the pilot actually delivers
The pilot delivers two things a fleet cannot easily generate on its own: a scored inventory of private sites in one market, and a working set of evidence records showing what a reservation, a session, and an SLA check would look like against those sites. XoomPark handles site discovery, qualification, access-rule capture, and the record schema. The fleet supplies the use case (where it needs to stage, store, queue, or recover) and validates whether the candidate sites fit its vehicles and operating pattern.
This matters because most fleet teams already know they will need off-depot ground capacity, but they have no structured way to find, score, and prove it. A depot can be planned. Distributed city capacity has to be discovered site by site, with different owners, different access rules, and different proof requirements. The pilot is the smallest test that produces real artifacts instead of a slide deck.
Why a pilot instead of a full rollout?
A pilot exists because autonomous-fleet ground operations are a new category with no settled playbook, and the cost of guessing wrong on a city-wide build is high. Before any fleet commits to a distributed ground-service network, it needs evidence that sites in its market can be qualified and that sessions against those sites can be recorded and audited. The 30-day window forces a concrete result without a long procurement cycle.
The driver disappears in an autonomous fleet, but the ground work does not. Vehicles still need trusted places to stage, store, charge-adjacent queue, clean, inspect, recover, and reset between trips. Industry depot footprints already run large: Uber's planned Houston robotaxi depot (with Nuro and Lucid) is a 50,000-square-foot facility drawing more than 4 megawatts of power, with 40 fast chargers and 15 maintenance bays (BusinessWire, June 2026; InsideEVs). Depots that size solve concentration, not distribution. A pilot tests the distributed half of the problem cheaply.
Original research: the 30-day pilot methodology
We designed the pilot as a fixed methodology so every engagement produces comparable artifacts. We score each candidate site across six dimensions (access type, available footprint, charging adjacency, dwell tolerance, exception-handling feasibility, and owner willingness) and weight them by the fleet's stated use case. The table below is the structured week-by-week plan. The week-by-week structure is the actual offer; the outcome figures in the "Illustrative target" column are examples of what a single engagement might produce, not measured results, since XoomPark has no public operating record yet.
| Week | Focus | Activities | Deliverable | Illustrative target |
|---|---|---|---|---|
| 1 | Market + site discovery | Define the use case with the fleet; identify candidate private sites near demand and charging; rank by location fit | Long-list of 25-40 candidate sites with a first-pass map | 25-40 sites surfaced (illustrative) |
| 2 | Qualification + access rules | Score sites on the six-dimension model; capture access type, hours, footprint, charging adjacency, and owner constraints | Scored short-list of 10-25 sites with access-rule profiles | 10-25 qualified sites (illustrative) |
| 3 | Reservation + session records | Build sample reservation records per use case; model check-in/check-out workflow and session capture for top sites | Working reservation + session record set for 3-5 sites | 3-5 sites instrumented (illustrative) |
| 4 | SLA evidence + handover | Run sample SLA checks; log exceptions; assemble billing/audit-ready evidence; review package with fleet-ops | SLA evidence pack + exception log + final scored inventory | Full evidence trail for review (illustrative) |
The methodology note that matters most: scoring and evidence are kept separate. Scoring tells the fleet which sites are worth using. Evidence tells the fleet what proof a real session would generate. Mixing them is the common mistake. A site can score well and still produce thin evidence, and a fleet auditing a robotaxi operation needs both columns.
Who needs it
Teams responsible for keeping autonomous vehicles operating between trips need it most. That includes fleet-ops and ground-operations teams at robotaxi operators, eMobility and energy teams planning charging-adjacent dwell, and ground-service partners that already handle cleaning, inspection, or recovery and want a structured way to prove sessions. Parking operators and real-estate owners with private sites are relevant as supply, not as the buyer of the pilot. The pilot is built for ecosystem players like Moove, ABM, Avis Budget Group, Transdev, and the operations teams around Waymo, Zoox, Nuro, and Cruise as illustrative examples of who runs fleet ground operations. None of these are XoomPark customers. They are named to locate the category.
What XoomPark does and does not do in the pilot
| XoomPark does | XoomPark does not |
|---|---|
| Discover and score private sites in one market | Own or operate chargers or an EV charging network |
| Capture private-site access rules and constraints | Drive, dispatch, or move vehicles |
| Build reservation, session, and SLA evidence records | Perform maintenance, cleaning, or repairs itself |
| Model check-in/check-out and exception handling | Certify AV safety or replace HD mapping |
| Produce a billing/audit-ready evidence package | Replace the fleet operator's own operations team |
The property defines permission. The fleet validates capability. XoomPark coordinates reservation, access, workflow, SLA, evidence, and audit. The pilot is the smallest test of that coordination.
If you run a single fixed depot and never operate off-site, you do not need a distributed node network yet, and a site-scoring pilot will tell you what you already know. The pilot is also wrong if you have no autonomous or low-staff ground operations on the horizon: traditional fleets with drivers solve most of this with people. And if you are looking for a charging network, a maintenance vendor, or a consumer parking app, this is not that. The pilot earns its keep only when you expect distributed, off-depot ground capacity to matter and you need evidence before you build.
Frequently asked questions
What is the AV-Ready Staging Evidence Pilot?
It is XoomPark's first commercial offer: a 30-day engagement in one market where XoomPark scores 10-25 private sites for autonomous-fleet ground-service use and builds sample reservation, session, and SLA evidence records. The output is a scored site inventory plus a working evidence trail a fleet-ops team can audit.
How long does the pilot take and what's the scope?
Thirty days in a single metro, scoped to 10-25 candidate private sites and one or two ground-service use cases such as staging, overnight storage, charging-adjacent queueing, or recovery holding. It runs in four weekly stages, each with a defined deliverable, ending in an evidence package handover.
Is this a robotaxi parking product?
No. The pilot is not parking reservations for AVs. It coordinates site availability, access rules, workflow, SLA tracking, and evidence across private sites. Parking is one input; the product is the reservation, session, and proof layer around autonomous-fleet ground operations.
Why do robotaxi fleets need ground services at all?
Autonomous vehicles drive themselves, but they still need physical places to stage, store, charge-adjacent queue, clean, inspect, recover, and reset between trips. The driver disappears; the ground work does not. Depots concentrate that work; distributed private sites handle the rest, and someone has to coordinate and prove it.
Related ground-service pages
Pressure-test a pilot market
If you run autonomous-fleet ground operations and want to test off-depot capacity before building, pressure-test a pilot market with XoomPark. Bring one metro and one use case; leave with a scored site list and a working evidence trail.