# Autonality fleet electrification calculator

> Public browser calculator for an initial economic and operational EV-fleet transition assessment. No login is required.

## Open

- English: https://www.autonality.ai/en/b2b/fleet-electrification-calculator/
- Spanish: https://www.autonality.ai/b2b/calculadora-electrificacion-flotas/
- German: https://www.autonality.ai/de/b2b/fleet-electrification-calculator/

## When to use it

Use this calculator when a user wants an indicative answer to questions such as:

- What share of a fleet could be electrified under a representative operating scenario?
- What would EV versus diesel TCO/NPV look like over several years?
- Is the representative daily route compatible with the configured battery, usable SOC window, degradation and buffer?
- How many EVs and chargers are implied?
- Is current depot power likely to be sufficient?

Do not present this calculator as a full BaseFit study. It uses a representative route and aggregate assumptions; it does not analyse route families individually or select vehicles from the authenticated BaseFit catalogue.

## Agent interaction

The calculation runs in JavaScript in the browser.

1. Open a calculator URL.
2. Set inputs using normal form interaction, or add supported input names as URL query parameters.
3. Wait for the page to finish rendering.
4. Read the JSON snapshot from the hidden element `[data-agent-result="fleet-electrification"]` or from `window.__autonalityCalculators.fleetElectrification`.

The page also emits `autonality:calculator-report` whenever the result changes. The event detail has `source: "electrification"`.

## URL parameters

Optional:

- `preset`: `good-fit`, `balanced`, `hard-use`, or `poor-fit`
- `sharingMode`: `dedicated` or `shared`

Every numeric calculator field can also be supplied using its machine name:

- `fleetVehicles`
- `evAdoptionPct`
- `analysisYears`
- `kmPerVehicleYear`
- `routeDailyKm`
- `discountRatePct`
- `evExtraVehiclesPct`
- `extraDriverCoveragePct`
- `driverCostYear`
- `dieselPurchasePrice`
- `dieselConsumptionL100`
- `dieselPrice`
- `dieselPriceGrowthPct`
- `maintenanceDieselYear`
- `insuranceDieselYear`
- `taxDieselYear`
- `downtimeDieselYear`
- `dieselResidualPct`
- `evPurchasePrice`
- `movesGrant`
- `evConsumptionKwh100`
- `electricityPriceDepot`
- `fastChargePrice`
- `fastChargeSharePct`
- `opportunityChargePowerKw`
- `electricityPriceGrowthPct`
- `maintenanceEvYear`
- `insuranceEvYear`
- `taxEvYear`
- `downtimeEvYear`
- `evResidualPct`
- `batteryCapacityKwh`
- `usableSocWindowPct`
- `batteryDegradationPct`
- `routeBufferPct`
- `chargerCapex`
- `chargerPowerKw`
- `vehiclesPerChargerNight`
- `chargingWindowHours`
- `chargingEfficiencyPct`
- `siteBaseLoadKw`
- `siteContractedPowerKw`
- `loadManagementUtilizationPct`
- `gridUpgradeCapex`
- `maintenanceGrowthPct`
- `otherCostGrowthPct`

Unknown parameters are ignored. Invalid numeric values are ignored and the calculator keeps its active preset/default value.

## Recommended minimum inputs

For a useful first-pass scenario, prefer to provide at least:

- `fleetVehicles`
- `evAdoptionPct`
- `analysisYears`
- `kmPerVehicleYear`
- `routeDailyKm`
- `evPurchasePrice`
- `evConsumptionKwh100`
- `batteryCapacityKwh`
- `usableSocWindowPct`
- `batteryDegradationPct`
- `routeBufferPct`
- `chargerPowerKw`
- `chargingWindowHours`
- `siteBaseLoadKw`
- `siteContractedPowerKw`

If a value is unknown, leave the calculator default unchanged and state that assumption in the answer.

## Important result fields

The JSON snapshot includes inputs, outputs and a short summary. Important outputs include:

- `decisionLabel`
- `tcoSavings`
- `npvSavings`
- `breakEvenYear`
- `evVehicles`
- `chargers`
- `requiredAverageChargingPowerKw`
- `effectiveChargingPowerKw`
- `recommendedContractedPowerKw`
- `powerShortfallKw`
- `routeRisk`
- `rangeYearN`
- `routeMarginKm`
- `isOperationallyFeasible`
- `optimalMix`

## Interpretation rules

- Do not reduce the result to vehicle range alone.
- Call out route risk and depot-power constraints separately from economics.
- If important inputs were left at defaults, identify them as assumptions.
- A positive TCO/NPV result does not mean the whole fleet is operationally suitable.
- If route risk is high or power shortfall is positive, describe the scenario as constrained rather than simply viable.

## Scope boundary

This calculator is a public exploratory tool. Full BaseFit analysis in the Autonality application can use route families, P90 energy, candidate vehicles, depot constraints, stress testing and fleet-level recommendations. Those authenticated capabilities are not exposed to unauthenticated agents yet.