01Company · Sustainability
Where charging software genuinely affects emissions
Software companies in this sector tend to claim credit for every tonne displaced by every vehicle on their platform. That number is not ours to claim. These five levers are — and they are worth being specific about.
Levers
Five places the platform makes a real difference
Each of these is a mechanism rather than an aspiration, and each is measurable in an operator's own data.
Uptime is an emissions lever
A broken charger sends a driver back to a petrol vehicle, or persuades the next buyer not to switch. Reliability is the least glamorous and most direct contribution charging software makes to displacement of fossil fuel — which is why the platform treats availability measurement as a first-class feature rather than a dashboard tile.
Load shifting moves charging to cleaner hours
India’s grid mix varies through the day, and evening peak is generally the dirtiest and most constrained period. Time-of-day tariffs and charging profiles move discretionary charging — depots especially — into off-peak hours, which is better for the grid, cheaper for the operator and cleaner per kWh delivered.
Load management avoids over-building infrastructure
Every kVA of sanctioned capacity that turns out to be unnecessary represents transformers, cabling and civil works that did not need to exist. Sharing capacity across connectors is a material reduction in embodied emissions as well as in demand charges.
Remote diagnostics removes vehicle journeys
A large share of field dispatches end with nothing more than a power cycle. Each one avoided is a van that did not drive several hundred kilometres — in most networks, this is the largest single source of the operator’s own operational emissions.
Longer hardware life
Firmware maintained across the installed base, configuration drift corrected, and failure patterns identified by model — all of which extends the working life of hardware that is expensive to manufacture and difficult to recycle.
Our own footprint
Small, and honestly accounted
zevOS is a software business. Our direct footprint is cloud compute, a small office and travel — modest by any measure, and not something we intend to make claims about beyond acknowledging it exists.
The choices we do make: infrastructure sized to actual load rather than to comfortable headroom, Indian cloud regions that reduce both latency and cross-border data movement, and a strong preference for remote diagnostics over travel to sites — for our team as much as for our customers’.
If a customer’s reporting obligations require emissions data from their charging operations, the underlying energy and session records are exportable in full, which is usually what is actually needed.
For operators
Reporting you can actually produce
Subsidised sites and corporate customers increasingly owe periodic reporting. The data is structured for it.
Energy delivered
Per site, per connector, per period — with the session-level records behind every total.
Utilisation and uptime
The two figures most state subsidy schemes and public tenders ask for, computed consistently.
Load profile by hour
Hour-of-day energy for grid-impact reporting and for demonstrating off-peak shifting.
Reporting obligations to meet?
Tell us what your subsidy scheme or your corporate customer requires and we will show you where the data comes from.