Versions Compared

Old Version 123

changes.mady.by.user Philippe Robin

Saved on

compared with

New Version 124

changes.mady.by.user Philippe Robin

Saved on

Key

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

...

  • 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

...

  • Gerald shows this slide (to be uploadedGerald Spreitz please upload the slide), 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 ?

    • Jira
      serverJIRA
      serverId121ddff2-c571-320f-9e4d-d5b9371533bd
      keyCCS-82
      created, unassigned

  • 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

  • Gunnar: remember that data set must rather be called naming of signals
  • Glenn: this is work-in-progress,
  • wip,
  • Glenn expects to have an answer in a week or the rationale for not having an answer Gunnar: reminder data set = naming of signalsand not being able to share the data Geotab use with power utilities
  • Glenn: what is important is the rationale of the power utilities for using the signals by the power utilities>>>>>>>>>>>>>>>>>>>>>>>>>>
    • Jira
      serverJIRA
      serverId121ddff2-c571-320f-9e4d-d5b9371533bd
      keyCCS-77
      commented

data contracts & data categories

  • Gunnar: shows the data bundles wiki page, reminds about the privacy aspects
  • Gunnar: the need has to drive the work, we need to work out a complete access control group first before reworking data contracts and data categories
  • Gunnar: do other think we need to work in parallel ?
  • Gunnar: elaborates on the EV data the OEMs would like to control the accessibility of (e.g. battery durability relales to warranty cost, etc.), I am sure we will have the mechanisms to handle this
    • the data related to this might even not be transmitted because providing those data is not in the business contract
    • delivering that data can be done under a contract to specific third parties
  • Gunnar: we expect to have the mechanism to control the access technically and businesswise

    • Jira
      serverJIRA
      serverId121ddff2-c571-320f-9e4d-d5b9371533bd
      keyCCS-83
      created, unassigned

communication framework

  • look at Vehicle Data Exchange Prococols wiki page
  • Gunnar: presented the wiki page, are the protocols we discuss enough for what we want to do ? he explains his vision of the work to do as described in the wiki
  • Kevin: explains the differences between the latest "big picture" diagram and the initial one
  • Kevin: explains he removed the container processing because we use Gen2 now
  • Gunnar: here are in my the pieces of the puzzle
    1. understanding of the big picture
    2. protocols between compoments
    3. dig into components

Sprint & backlog review

  • the Jira tracker was renamed as CCS (instead of VCS) and updated, look at CCS backlog
  • /TODO/ Gunnar to check that the Jira notification scheme is active for the CCS project
  • /TODO/ All to check the backlog and current sprint content
  • current sprint is until the end of March
  • Philippe's expectation is that we will be able to start some PoC activities soon in order to show something at the upcoming Spring AMM (12-14 May)

AOB Privacy

Friday,  February 28 - Communication Framework

...