Versions Compared

Old Version 100

changes.mady.by.user Philippe Robin

Saved on

compared with

New Version 101

changes.mady.by.user Philippe Robin

Saved on

Key

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

Monday, January 27

Agenda:

  • CES debriefing
  • vehicle data models: relevance of the specs for EV Charging to our work on data modeling (e.g. OCPP)
  • platform candidates for the CCS PoC: are the following platforms relevant : Amazon Auto, MS Azur, Veniam ?
  • project organization: add another weekly call to discuss architecture
  • Sprint & backlog review
  • AOB
    • data categories

Participants

  • Kevin, Guru, Glenn, Benjamin, Keith, Gunnar, Philippe, Steve

Minutes

EV charging

  • Kevin: IMHO EV charging when the vehicle is connected to the charging station is totally in the scope of use cases and specifications defined by a consortium like the Open Charging Alliance. However there is a need to know the status of the EV battery charge when the vehicle is not connected
  • Glenn: AKAIK the utilities request the status of EV battery charge for load balancing, I could bring an expert in the call to explain the EV/Power Utility communication use case for commercial vehicles as means possible inclusion by GENIVI in defining 'scope' for EV/Electrical Utility communication requirements - leading to the development of open specifications for broaded use of same.
  • /TODO/ Geotab to provide an expert in this area to describe current use cases at Monday GENIVI call. (5:30 CET)
  • Benjamin: in W3C VSS, there is a branch on battery capacity but it is empty up to now
  • Gunnar: agreed, there is a need to complement VSS on this
  • Gunnar: I agree that when the EV is connected to the charging station, this is not a use case for GENIVI, however when the vehicle is OTA, this is in scope of our CCS project
  • Kevin: last week we at High Mobility open sourced all of our SDK with a unified set of APIs (based on data we got from BMW/Mercedes/... on the production projects), it might be good to look at data examples available at
  • Gunnar: IMHO we should rename this topic to EV management (i.e. something different than EV charging) since we do not overlap with the work on EV charging
  • Guru: we need also to clarify how this topic fits with the EV battery management system
  • EV charging docs (reminder) - useful links

Communication infrastructure - Platform candidates for the CCS PoC

  • Philippe: reminds us it would be good to look at Amazon Auto and MS Azure and Veniam (https://veniam.com/products/) as possible target platforms for the CCS project demonstrator

  • Kevin: does not know Veniam, will check

  • Gunnar: we need to undestand what role Amazon would like to play: do Amazon want to compete with companies like Geotab and others or do they simply want to sell infrastructure

  • Gunnar: IMHO it is time to make a generalization of the infrastructure we have in mind

  • Gunnar: I would like to know whether the car OEMs are already communicating their data through vehicle neutral servers ?

  • Kevin: we should organize a call to brainstorm on the communication with others

  • Gunnar: AFAIK W3C process is a little bit slow, we should organize to make faster progress, we need to put building blocks in place

  • decision  schedule a call for brainstorming on communication infrastructure with Kevin/Gunnar on Thu 30 Jan 11:30am CET (ad-hoc call), Philippe will send a calendar invite DONE

  • (added offline): Geotab proposed to provide an overview of commercial vehicle to cloud services use case as an example that GENIVI may choose to include in TBD scope for vehicle/'cloud services' (e.g. Amazon, Microsoft Azure), and development of applicable open specifications to satisfy such use cases. Geotab will join the ad-hoc call to present this.

Data categories

  • Gunnar: in order to keep things concrete, it would be good to give an example of data categories for VSS signals

  • Glenn asks for clarification

  • Glenn will send a note to Geotab/Ulf and asks him to sync with Gunnar on this

  • Gunnar: the scope of the work proposed is not the same as what Geotab is doing for the W3C VSS PoC but we could reuse the same set of data

  • /TODO/ Gunnar follow with Ulf/Geotab on providing examples of data categories for VSS

  • Keith: aks a question on VISS (not captured, apologies)

  • Gunnar: will provide a clarification

Project organization

  • doodle-like table to gather participants' availability for a second call updated online,  table is here
  • Wednesdays at 4pm CET or 5pm CET are the possible common slots
  • /TODO/ Glenn to check whether these timeslots fit with the availabilities for Geotab
  • /TO/ Guru to check whether these timeslots fit with his availabilities
  • we will make the decision for the timeslot and the periodicity of calls at next Monday call

Sprint & backlog review

  • Philippe: will update the backlog and the current sprint content according to latest discussions
  • Jira
    serverJIRA
    serverId121ddff2-c571-320f-9e4d-d5b9371533bd
    keyVCS-68
    • Glenn reports on the event he attended in Washington DC last week, this event organized by SAE was about the real-world data collection, 1600 people attended it, including many OEMs; Glenn mentioned GENIVI CSS work in the talk he delivered at the event
    • Philippe: reminds us to identify other events in different geographies

AOB

  • Due to traveling constraints, Philippe proposed to re-schedule next Monday call at 5:30pm CET
  • All: agreed. A calendar invite will be sent.

Monday, January 20

Agenda:

  • CES debriefing
  • vehicle data models: relevance of the specs for EV Charging to our work on data modeling (e.g. OCPP)
  • platform candidates for the CCS PoC: are the following platforms relevant : Amazon Auto, MS Azur, Veniam ?
  • project organization: add another weekly call to discuss architecture
  • Sprint & backlog review (skipped)
  • AOB

...