Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

EV data use cases : presentation by Geotab & discussion

  • Sarah is senior customer project projects manager in EV fleet management at Geotab and works on smart charging
  • Geotab has a B2B & B2C smart charging management platform offering
  • Sarah delivers this presentation (add link)
  • The rationale for enabling smart charging through the monitoring of EV data is that the grid is not originally designed for EV charging and commercial EV fleet operators and power utilities expect to improve the charging operations according to different criteria (hence the different use cases presented)
  • the consumer use case scenarii (i.e. for passenger EVs) are not distant from the commercial fleet, however there is less maturity in consumer EVs than commercial EVs
  • DERMS means Distributed Energy Resource Management System, Demand-Side Management is a subset of DERMS
  • Gunnar: we need to define the vehicle data we need for EV management in the VSS database we use in GENIVI for the vehicle data modeling
  • Sarah: currently this is no standard wean use and it is a lot of work to do (i.e. to adapt to the commercial EVs our customer use), we are very much interested in standards
  • Gunnar: you use the OBD-II port, it is a subset of all electrical data available in the car, in VSS the vehicle data set is much larger, the branch for EV data is very minimal
  • Philippe: do you support OCPP (Open Charge Alliance) ?
  • Sarah: we support OCPP in our smart charging platform, OCCP is not using a lot of vehicle data, we look at the state of charge in the vehicle only
  • Philippe: explains GENIVI objective which is to enhance the VSS database w.r.t. EVs in order to be future proof (because ICE part will decrease in the future)
  • Gunnar: this is why we need domain expertise to identify which data need to be added in VSS for EVs
  • Sarah: it is not a considerable data set, OEMs have a different level of data than the one we use, fleet managers need less data, the so-called last mile delivery use case is interested in other set of
    data, power utilities need only the 15mn average power consumption
  • Glenn: it is worth noting that with commercial fleet management, the decision making / policy making are focused in the same hands
  • Glenn: in the consumer domain instead, the decision making is much more distributed, the policies are much more diverse, deploying DERMS is more difficult (or less mature for the time being)
  • Next step
    • Gunnar: we need to look at the current content of VSS and see how it matches with Geotab undertanding of the use cases and required data set
    • Kevin: the datasets for EV are very limited because the OEMs do not want to share the information about their battery management (and degradation for instance)
    • Glenn: we are in a process of mapping the vehicle data we use at Geotab artefacts to the VSS data but the project is not completed yet
    • Gunnar: we need to improve the VSS database if necessary, e.g. to allow third parties to have access to some specific dataset extensions
    • TODO Glenn review the current EV branch of the VSS database and check whether the data described there are relevant and sufficient for enabling EV charging management / DERMS

...