dbt models for OCPP logs here
kwwhat is an open-source dbt project that models reliability and utilization metrics from EV charger logs based on the OCPP 1.6 and 2.0.1 protocols. Starting from raw OCPP logs, the project builds a transparent path toward meaningful metrics like uptime, session success, and visit-level outcomes.
This project is powered by public OCPP log data and is designed for CSMS providers, utilities, researchers, and data practitioners aiming to build their own charger analytics stack.
kwwhat includes:
git clone https://github.com/YOUR_USERNAME/kwwhat.git
cd kwwhat
Then update your profiles.yml
to point to your raw data location (e.g., DuckDB, BigQuery, Snowflake, Redshift, etc.).
Metric | Description |
---|---|
_uptime_pct |
% of time a charger had a regular heartbeat and port was not in a Faulted state |
visit_success_rate |
% of visits that result in meaningful energy transfer. Visit is a rollup of sessions generated by the same driver on the co-located chargers close in time |
first_attempt_success_rate |
Visits where the first charging attempt succeeded |
troubled_success_rate |
Visits that initially failed but succeeded sfter some troubleshooting |
TBD
Designed based on industry frameworks and academic research to align metrics with real-world expectations:
The Public EV Charging Infrastructure Playbook by U.S. Joint Office offers guidance for performance evaluation in EV infrastructure EV Charging KPI Playbook
The Sage‑published journal article Novel Methodology to Measure the Reliability of Public DC Fast Charging Stations proposes a data-driven framework for charger reliability, which informed the visits logic in kwwhat. Novel Methodology to Measure the Reliability of Public DC Fast Charging Stations
Uptime calculations modeled in part after NEVI guidelines
This project was created independently and outside of any prior employment. It does not include any proprietary information, logic, or data.
The kwwhat project is licensed under the MIT License. External datasets and tools used in this repo follow their respective licenses as noted above.
Open to contributions from the EV data community. If you’re building in this space and want to improve reliability tracking, user experience analytics, or charger diagnostics — join in!
Questions? Ideas? Drop an issue.