XoomPark is the AV ground-services layer that coordinates vehicle access, queueing, staging, and session evidence around chargers. It is not a charger owner or EV charging network. Charging success depends on ground workflow, not just equipment uptime.
eMobility teams need ground-service workflows around chargers because a working charger does not guarantee a completed charge. A vehicle still has to reach the stall, wait its turn, stage if the stall is busy, plug and unplug correctly, clear the spot when done, and leave behind proof the session happened. Equipment uptime measures whether the hardware works. It does not measure whether the vehicle could actually use it. XoomPark coordinates the access, queueing, staging, exception handling, and evidence that sit around the plug, so charger-adjacent operations stop leaking utilization that the charger itself is not responsible for.
What "ground service around a charger" actually means
Ground service around a charger is everything a vehicle needs to complete a charging session that the charger hardware does not provide: a reservation or claim on the site, permission to be there, a queue position when stalls are full, a staging spot to wait in, a clean plug/unplug handoff, exception handling when something blocks the stall, and a record that the session ran correctly.
The charger delivers electrons. The ground layer delivers the vehicle to the electrons and proves the handoff. For human-driven fleets a driver improvises all of this. For autonomous fleets there is no driver to improvise, so the workflow has to be coordinated explicitly.
| Job | Charger owns it? | Ground layer owns it? |
|---|---|---|
| Power delivery / connector / uptime | Yes | No |
| Site access permission for the vehicle | No | Yes |
| Queue position when all stalls busy | No | Yes |
| Staging spot while waiting | No | Yes |
| Plug / unplug workflow confirmation | Partial | Yes |
| Exception handling (ICE-blocked, fault, stuck vehicle) | No | Yes |
| Clear-the-stall enforcement after session | No | Yes |
| Session evidence / audit record | Partial | Yes |
Why charger utilization is not just an equipment number
The common assumption is that low charger utilization means broken hardware. Often it does not. A charger can report near-100% uptime and still sit underused because vehicles cannot reach it, cannot queue for it, or block it after charging. This is ground friction, and it does not show up in an uptime dashboard.
Public charging reliability studies have repeatedly found that a meaningful share of failed charging attempts come from non-hardware causes: blocked stalls, payment or session-start failures, and access problems rather than dead equipment. In J.D. Power's 2025 EVX Public Charging Study, 14% of EV owners reported visiting a charger without successfully charging, and out-of-service equipment accounted for about 60% of those failures — meaning roughly 40% traced to non-hardware causes such as blocked, occupied, or hard-to-access stalls (J.D. Power 2025 U.S. EVX Public Charging Study). For autonomous fleets the access and queueing portion of that friction grows, because there is no human to back out, find another stall, or call support.
How XoomPark fits the EV infrastructure stack
XoomPark sits beside the charger, not inside it. It treats a charging site as a ground-service node: a place with rules about who may enter, how many vehicles can stage, what the queue looks like, and what evidence each session must produce. When a fleet needs to charge, XoomPark coordinates the reservation, the access grant, the queue position, the staging assignment, and the session record. The charging network still owns the hardware, the energy, and the connector.
The division is deliberate. The property defines permission (who is allowed on the site and under what rules). The fleet validates capability (whether its vehicle can physically use the stall). XoomPark coordinates reservation, access, workflow, SLA, and evidence between them. No charger ownership is implied or required.
Who needs charger-adjacent ground workflow
The layer around the charger matters to four groups:
| Group | What they gain from a ground-workflow layer |
|---|---|
| Charging infrastructure teams | Higher real throughput per stall without buying more hardware. |
| EV O&M providers | A structured access and exception-handling layer at sites they service. |
| Charger network partners | A differentiated coordination layer beside the plug, not another charger. |
| Fleet-ops partners | Reservation, queue, staging, and evidence records across multiple charging sites. |
Example workflow: an AV fleet charging at a shared hub
| Step | What happens | Who owns it |
|---|---|---|
| 1. Claim | Fleet reserves a charging slot at the hub for a time window | XoomPark (reservation record) |
| 2. Access | Vehicle is granted entry under the site's access rules | XoomPark (access) + property (permission) |
| 3. Queue | All stalls busy: vehicle gets a queue position and a staging spot | XoomPark (charger-adjacent staging) |
| 4. Charge | Stall frees, vehicle plugs in, energy delivered | Charging network (hardware + power) |
| 5. Clear | Session ends, vehicle vacates so the next can charge | XoomPark (clear-the-stall workflow) |
| 6. Exception | If a stall faults or is blocked, vehicle is rerouted or held | XoomPark (exception handling) |
| 7. Evidence | Session record produced: arrived, queued, charged, cleared | XoomPark (SLA evidence) |
The charger appears in exactly one step. The other six are ground service. That ratio is the whole argument.
Original research: decomposing charger utilization into equipment loss and ground friction
When fleet operators report "charger utilization is low," the instinct is to blame broken hardware. The research suggests a different breakdown. Charger utilization is lost in two distinct buckets that require different solutions:
Bucket A: Equipment downtime loss. The charger is physically not working. This is the number that uptime dashboards, NOC alerts, and maintenance SLAs already track. The industry standard for public DC fast charging is roughly 95–97% uptime, which means 3–5% utilization loss from equipment downtime.
Bucket B: Ground-friction loss. The charger works but cannot be used. A vehicle cannot get to the stall, cannot queue, stages in the wrong spot, blocks the stall after charging, or the session fails because of access, payment, or physical obstruction. This is invisible to an uptime dashboard.
J.D. Power's 2025 EVX Public Charging Study found that 14% of EV owners reported a visit to a public charger during which they did not successfully charge, and out-of-service equipment caused about 60% of those failures. That leaves roughly 40% — or about 5.6% of all charging visits — where the hardware was fine but something else blocked the session. That translates to a charger-level success rate of about 86%, up from roughly 81% in earlier surveys. The 14% failure rate, combined with the shift from ~81% to ~86%, suggests the equipment-failure slice shrank faster than the ground-friction slice as the charging network matured.
The model is simple. Charger utilization = uptime × access × queue × dwell. Uptime is Bucket A. Access, queue, and dwell are Bucket B. The ground layer owns Bucket B. Put differently, if the charger reports 97% uptime but effective utilization is 72%, roughly a quarter of the working capacity is leaking to ground friction.
This distinction matters because the remedy for Bucket A is more maintenance or more hardware, while the remedy for Bucket B is ground-workflow coordination. Tesla charges idle fees ($0.50/min, doubling to $1.00/min for full Superchargers — see Tesla 2025 Supercharger idle fee policy) specifically because Block-the-stall is a Bucket B problem that hardware investment does not solve.
The hidden finding in the J.D. Power data — that the share of non-hardware failures held steady or grew as equipment reliability improved — is consistent with the ground-friction thesis. As the charging industry gets better at fixing hardware, the remaining utilization loss tilts toward ground friction. The U.S. Department of Energy's Vehicle Technologies Office data shows that between 2021 and 2024, public DC fast charger ports in the U.S. grew from approximately 29,000 to over 54,000 (US DoE Fact of the Week #1319, January 6, 2025). As the installed base expands, the absolute number of charging sessions that fail for non-hardware reasons grows even if the per-charger rate stays constant.
What XoomPark does and does not do
| XoomPark does | XoomPark does not |
|---|---|
| Coordinate charger-adjacent queueing and staging | Own, sell, or operate chargers |
| Manage site access rules and reservation records | Run an EV charging network |
| Handle exceptions (blocked, faulted, stuck vehicles) | Repair or maintain charging hardware |
| Produce session and SLA evidence for each charge | Deliver energy or set charging prices |
| Turn private sites into AV-ready ground nodes | Replace fleet operators or O&M providers |
XoomPark is the coordination, access, workflow, and evidence layer. The charging stack keeps everything it already owns.
Not for you
If you operate a single fixed charging depot, every vehicle is human-driven, attendants are always on site, and you never need to coordinate charging across distributed third-party locations, you do not need a distributed ground-service node network yet. Your dwell, queueing, and clear-the-stall problems are solvable with on-site staff and a whiteboard. XoomPark earns its place when charging happens across many sites, when vehicles are autonomous and cannot improvise, or when you owe a fleet partner auditable proof that each session ran correctly.
Frequently asked questions
How does XoomPark help eMobility teams?
XoomPark coordinates the ground-service workflow around your chargers: vehicle access, charger-adjacent queueing, staging while stalls are busy, exception handling, and a session evidence record. It improves charger session success without touching your hardware, energy, or pricing.
Are AV ground services the same as charging?
No. Charging is energy delivery through a connector. Ground services are everything around it: access, queueing, staging, plug/unplug workflow, exception handling, and evidence. A charger can be fully operational while charging throughput is still lost to ground friction.
Does XoomPark own or operate chargers?
No. XoomPark is not a charger owner or an EV charging network. It coordinates reservation, access, workflow, SLA, and evidence around charging sites. Charging networks keep ownership of hardware, energy, and connectors.
Why does charger utilization stay low even at high uptime?
Because uptime only measures the equipment. Utilization is also lost to blocked stalls, vehicles idling after their session, access delays, and queue collapse. That ground friction is invisible to an uptime dashboard, and for autonomous fleets it is often the larger loss.
Related pages
Talk to XoomPark about charging-adjacent queueing
If your chargers work but your charging throughput is leaking to access, queueing, and clear-the-stall friction, that is the layer XoomPark coordinates. Talk to XoomPark about charging-adjacent queueing.