# Autonality EV depot charging calculator

> Public browser calculator for checking whether a depot charging window, installed chargers and site power can deliver the daily energy required by an EV fleet. No login is required.

## Open

- English: https://www.autonality.ai/en/b2b/ev-depot-charging-calculator/
- Spanish: https://www.autonality.ai/b2b/calculadora-recarga-flotas-electricas/
- German: https://www.autonality.ai/de/b2b/ev-depot-charging-calculator/

## When to use it

Use this calculator for questions such as:

- Can a depot charge N electric vans overnight with the available site power?
- How much charging power is required for a representative fleet day?
- Are chargers or site power the likely bottleneck?
- Roughly how many active chargers are needed in the available window?
- How many representative vehicles could the current depot support?

It is an aggregate energy/power calculation, not a per-vehicle charging schedule.

## Agent interaction

The calculation runs in JavaScript in the browser.

1. Open a calculator URL.
2. Fill the form normally, or pass supported fields as URL query parameters.
3. Wait for the result to render.
4. Read the JSON snapshot from `[data-agent-result="depot-charging"]` or `window.__autonalityCalculators.depotCharging`.

The page also emits `autonality:calculator-report`. The event detail has `source: "depot"`.

## Inputs / URL parameters

- `vehicles`: number of EVs to charge
- `dailyKmPerVehicle`: representative daily distance per vehicle, km
- `consumptionKwh100`: representative consumption, kWh/100 km
- `chargingEfficiencyPct`: grid-to-battery efficiency, %
- `returnTime`: depot return time, `HH:MM`
- `departureTime`: next departure time, `HH:MM`
- `chargerPowerKw`: nominal power per charger, kW
- `chargerCount`: installed/available charger count
- `sitePowerKw`: power available for EV charging, kW
- `operationalMarginPct`: additional energy margin, %

Unknown parameters are ignored. Invalid values keep the page default.

## Default scenario

```json
{
  "vehicles": 10,
  "dailyKmPerVehicle": 120,
  "consumptionKwh100": 28,
  "chargingEfficiencyPct": 90,
  "returnTime": "18:00",
  "departureTime": "06:00",
  "chargerPowerKw": 11,
  "chargerCount": 5,
  "sitePowerKw": 55,
  "operationalMarginPct": 15
}
```

## Important result fields

- `plannedGridEnergyKwh`
- `chargingWindowHours`
- `averagePowerRequiredKw`
- `installedChargerPowerKw`
- `effectivePowerKw`
- `deliverableGridEnergyKwh`
- `energyBalanceKwh`
- `utilizationPct`
- `minimumActiveChargers`
- `vehiclesSupported`
- `status`: `sufficient`, `tight`, or `insufficient`
- `bottleneck`: `site`, `chargers`, or `balanced`

## Interpretation rules

- `sufficient` means the aggregate configured energy can be delivered with meaningful headroom.
- `tight` means the aggregate case fits but has limited operational headroom.
- `insufficient` means the configured energy/power requirement does not fit the charging window and available power.
- Do not infer a detailed charging schedule from this calculator.
- If vehicles have materially different return times, distances or charger compatibility, use a richer simulation.

## Scope boundary

The authenticated Autonality application contains richer route, vehicle, depot and stress-test logic. There is no public calculation HTTP API or MCP endpoint yet.
