Versions Compared

Key

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

Monday,  March 2 - Vehicle Data

Agenda:

  • a use case presented by Gerald
  • Data set for EV management
  • data contracts & data categories
  • communication framework
  • Bosch Vehicle Abstraction Layer - relevance for CCS
  • Sprint & backlog review
  • AOB
    • EU privacy guidelines

Participants

  • Ulf, Glenn, Gerald, Guru, Kevin Valdek, Gunnar, Philippe

Minutes

a use case presented by Gerald

  • Gerald shows this slide (to be uploaded), is the CCS use case APP presented here still what we are discussing in the project ?

  • Gunnar: what do you mean by: is CCS still supporting this use case ?

  • Gunnar: at signals level, we can think of signal groups you can get access to
  • Ulf: W3C Gen2 could be a potential candidate for a large part of this use case, Gen2 supports both on-board agents and cloud-based agents
  • Gerald: can you clarify what you mean by the grouping of signals ?

  • Gunnar: tthis is work-in-progress, my view is that there will be many groups because having a fine granularity is key

  • Gerald: can the granularity be down to one signal only ?

  • Gunnar: I wrote an example related to vehicle identification for the VSS layer presentation that gives an idea of what I think is an appropriate grouping

  • Gunnar: we could look a little bit deeper in the design of this APP use case you presented using Gen2

  • /TODO/ create jira ticket ?

  • Gerald: thinks about the monetization of this use case, if you do not provide vehicle data you have to pay for the app

  • Gerald: we should not forget about the commercial aspects in our work

Data set for EV management

  • wip,
  • Glenn expects to have an answer in a week or the rationale for not having an answer
  • Gunnar: reminder data set = naming of signals
  • Glenn: important is the rationale for using the signals by the power utilities
  • >>>>>>>>>>>>>>>>>>>>>>>>>>


Friday,  February 28 - Communication Framework

...