EVCare™ is in advanced pilot discussions with leading North American transit agencies. The scenario below is illustrative and modeled — it shows how a deployment is designed to unfold and the targets EVCare™ is built to hit. It is not a record of a completed customer deployment.
Modeled targets — not yet field-verified
What a Pilot Looks Like
EVCare™ connects to an agency's existing telematics and BMS data streams — no hardware installation, no operational disruption. A typical pilot is structured in three phases.
Illustrative Scenarios
The examples below are illustrative of EVCare™'s intended capabilities — they are modeled scenarios, not records of real events.
CareStar™ is designed to detect a module temperature rise well above the fleet average and trigger an AMS™ prescription to return the bus to depot — surfacing early thermal-runaway indicators before the bus completes its route cycle.
FitStar™ is designed to flag a bus below the SoC threshold for a given block during morning dispatch planning, so it can be reassigned to a shorter route before pullout — preventing a mid-route service disruption.
LPM™ is designed to identify accelerating degradation patterns consistent with BMS component failure, so maintenance can be scheduled before a cascade failure that would otherwise sideline the bus for several service-days.
Start Your Pilot
Start a pilot and we'll model projected outcomes against your specific fleet before you commit. When the results are in, your fleet could anchor our first named case study.
EVCare™ is at MVP stage today, and we’re transparent about it: the current platform delivers the core battery-health intelligence, while additional modules and capabilities will be introduced and integrated across 2027 and 2028 as we scale.