Planning Fleet Charging Around Solar Carports and Duty Cycles

Translate duties into charging requirements

Fleet charging starts with return times, next departures and the energy needed for the next duty. Identical vehicles may have different routes, loads and parking windows, so dividing equipment evenly by vehicle count is insufficient. Dispatch, facilities and electrical teams should identify typical and exceptional duties, distinguishing flexible departures from priority vehicles. Aggregated operational records can support planning without exposing individual drivers' travel. Daytime solar production does not mean vehicles serving daytime routes are present to use it. Timing is a separate design question that must be resolved.

Check vehicle and site constraints together

Charging speed depends on vehicle acceptance, equipment and available site supply. Charger ratings alone cannot establish readiness times. Include uncertainty in returns, queues, occupied bays and other building loads. AFDC public and fleet charging material helps structure equipment, location and operating questions, while local connection rules, connector requirements and qualifications need separate confirmation. Distinguish energy required for the next duty from a preference for a fully charged battery. This clarifies the service floor and avoids treating simultaneous full charging of every vehicle as an untested default.

• Record returns, departures and duty energy needs.
• Separate essential and flexible vehicle schedules.
• Check alternatives for faults and low generation.

Check solar alignment against real shifts

A hypothetical delivery fleet leaves early and returns after sunset, so its main charging window misses daytime solar. High canopy production does not automatically become energy used directly by those vehicles. Assess the respective roles of the grid, storage and scheduling, explaining how duties remain supported if an option is omitted. A fleet making short daytime trips may have more opportunities to charge during generation, but stops must be long and predictable enough. Use each fleet's duty records rather than transferring a solar-use percentage from a showcase example.

Handover an operating and exception process

The final plan should assign connection tasks, readiness checks, fault notifications and dispatch decisions. Rehearse representative workdays and peak duties jointly, recording unmet constraints rather than relying on a single powered-up demonstration. If a remote platform is used, confirm permissions, data export and support scope. Review changes in duties: a new route or shift can alter demand before the fleet adds vehicles. Keep evidence for the canopy, solar and charging systems separately. Energy-saving objectives do not establish a guarantee of vehicle availability or business continuity.