Where will robotaxis charge?

I start with the next trip, not the charger catalog. A robotaxi charging plan has to account for where the car waits and when it must leave. A plug at the wrong location does not answer either question.

I plan around two kinds of stops: depots for charging and service, and smaller lots near riders. Choose the stop by the work the car needs before its next assignment.

Waiting is an operating decision

Time between rides gives an operator a chance to charge a vehicle. That same period also has to accommodate movement into the site, service work and departure. I would assess the whole stop before promising that a particular charging window is usable.

A car waiting near riders serves a different purpose from a car held far from its next assignment. I want the location decision to include that difference. The question is not simply whether a parking space is empty.

Check the pickup time, service needs and battery together. A car with enough charge may still need cleaning. A clean car may need energy before it can take the next ride.

Depots and distributed lots have different roles

A depot offers a place to organize charging and service together. Distributed lots offer additional locations where a vehicle can wait closer to demand. I would not assume that either arrangement is the right answer for every operating area.

The depot decision should start with the work that must happen there. Cleaning, inspection and charging each require a place in the operating plan. A site should not be called ready merely because it can hold cars.

For a distributed lot, I would ask what services are actually available. A parking reservation is not a charging reservation. Nor does a charger establish that the site can complete a cabin check before departure.

At an airport-adjacent lot, check the entrance and available service against the expected vehicle movements. A nearby parcel only helps if the car can enter, finish its work and leave on time.

Power capacity comes before equipment counts

I check the site's power before counting chargers. Several installed ports may share a limited supply. Ask the utility and design team what service is available and how many vehicles it can serve together.

My software-defined power routing application addresses allocation within EV hubs. It proposes directing converter capacity through ports within the site's power envelope. The allocation also has to satisfy connector compatibility, isolation and thermal limits alongside the vehicles' service commitments.

Match the schedule to the site's limits and the cars' departure times. Both determine which charging commitments the owner can accept.

Charge around the mission

My AV dwell and charging scheduler links a vehicle's mission window to station availability through signed dwell-and-charge credentials. The proposed schedule coordinates arrival, charging and departure so one car does not overrun another car's slot.

Set the departure time with the reservation. The charging slot must fit the next mission.

The robotic EV charging connector application addresses another part of the stop. It proposes checking vehicle identity, port alignment and safe-state before coupling. Physical connection and scheduling are different problems, and both have to fit the vehicle's planned visit.

Before committing a site, inspect the installed charger, connection method and reservation process. Assign someone to handle a failed connection. The fleet needs a departure decision even when charging cannot start.

A charged car is not necessarily ready

Charging is one service event. Cleaning and readiness checks address different reasons a vehicle should remain out of service. I would not use battery state as a substitute for a decision about the whole vehicle.

My autonomous fleet service readiness certification proposal uses a signed certificate drawn from charging, cleaning, inspection, sensor calibration, cabin checks and lost-item handling. That evidence supports authorizing, blocking, rerouting, downgrading or rescheduling the next mission.

I want service evidence connected to dispatch decisions. The underlying checks need to fit the work being authorized. A vehicle that has finished charging still needs a readiness decision about the next mission, including the other service work relevant to that assignment.

For an owner, I would turn this into a straightforward question. Who decides that the car can return to service? The answer should identify responsibility rather than point only to a charging receipt.

Why parking operators belong in the discussion

Wins Parking designs, builds and manages parking. EV and robotaxi charging installation is its second operating pillar. Those activities make the relationship between land, vehicle access and charging directly relevant to the business.

Wins operates a yard at the entrance to Eagle County Airport in Gypsum, Colorado. For an airport-adjacent property, I would examine the entrance, the available power and the intended vehicle activity together. The physical location gives those operating questions a specific place to start.

I would ask the owner and fleet operator to agree on the work expected at the property. Who handles access? Who handles charging and service? Who makes the departure decision? Those responsibilities matter before the fleet begins relying on the location.

Start with a site and a responsibility

My first questions would be practical. Where will the vehicle wait, what power is confirmed, and what must happen before it leaves? I would then identify who owns each decision.

My charging and readiness applications are patent-pending.

I would begin with the land, the installed equipment and the vehicle's next mission. Then I would identify the changes the site needs and who is responsible for them. That gives owners a basis for evaluating the stop as an operation, from arrival through service to departure.