Question 1

Do I need OCPP and OCPI, or is one enough?

Accepted Answer

You need both if your vehicles charge anywhere other than your own depot. OCPP connects chargers you control to your platform; OCPI connects your platform to charge point operators you do not control, and delivers the Charge Detail Records you bill against. A pure depot-charging fleet can start with OCPP alone, but most last-mile and taxi fleets hit public charging within the first year.

Question 2

Can I use my existing AIS-140 device instead of a new telematics unit?

Accepted Answer

Yes, for location, speed and trip data — that is what the AIS-140 unit is certified to provide, and it is already fitted on new Indian commercial vehicles. It will not report battery state of charge or cell temperature, so pair it with the OEM telematics API rather than replacing it. A second GPS tracker duplicates a device you already pay a subscription for.

Question 3

How long does EV fleet system integration take end to end?

Accepted Answer

For a 40 to 150 vehicle fleet on a platform with existing connectors, about 90 days across four overlapping stages. The variable is rarely the software — it is how many distinct charger models and OEM APIs you run. Each extra charger firmware version adds roughly a week of testing, which is why the connector inventory belongs in week one.

Question 4

Who owns the charging and telematics data — us or the vendor?

Accepted Answer

Whatever your contract says — which is why the export clause matters more than the marketing claim. Insist on a documented API export of full historical session, telematics and transaction data, with no volume cap and a stated turnaround on termination. Separately, driver location and home-charging addresses are personal data under India's DPDP framework, so your fleet carries data-fiduciary obligations regardless of which vendor stores the rows.

Question 5

What happens if we integrate payments before chargers and telematics?

Accepted Answer

You build a billing layer against identifiers that are still changing. Reconciliation depends on stable session IDs from the charger layer and stable vehicle IDs from telematics; if either is renumbered mid-project, every mapping is rewritten and historical invoices stop tying back. Teams that take this shortcut typically lose a quarter to variance investigation at month-end close.

Resources: page 5

EV Fleet System Integration: Connecting Chargers, Telematics and Payments

Vendor-Agnostic EV Operating System: Why Open Fleet Ecosystems Win

EV Fleet Exception Handling: A Supervisor’s Playbook For Outages, No-Shows And SOC Errors

EV Fleet Transition Risk: 4 Strategic Risks And How To Mitigate Them

EV Fleet Tariff Configuration: A Step-By-Step Guide To Dynamic Pricing In YoMobility

EV Fleet Dynamic Tariffs: Turning Pricing Into a Margin Lever

EV Depot Operations Guide: Charger Mix, Layout And Software Integration

EV Depot Design Strategy: Building Future-Ready Charging Hubs For Fleets

EV Fleet Sustainability Reporting: A Step-By-Step Guide

See YoMobility on your fleet