Page History

...

Gap analysis document

• link

Reference Design

• Feedback from all other participants

...

• GENIVI technical summit - content planning, additional information
  
  • registration link is at https://www.eventleaf.com/TechSummit19ent
  • content will be finalized this week, 3 tracks are planned: Connected Services, Android Automotive, Cybersecurity
  • quick poll on who will attend
• https://grpc.io/: is this relevant for CCS ?
  • g stands for Google
  • Gunnar: we look at Google rpc in the GPRO project when we did the survey on communication protocols, look at the list of technologies we looked at and the GPRO white paper
  • grprc is built on http2 which never took off, people are rather working on http3, gprc is likely well suited on web technologies, it is one of many choices that are out there
  • from my perspective, it is relevant but not more relevant than anything else, when it comes to protocols that are not REST oriented protocols, MQTT has more relevance
• SAREF Automotive - https://www.w3.org/2019/09/trans-data-ws/SAREF.pdf
  
  • Benjamin reviewed the paper presented at the W3C workshop on data models for transportation, his findings on SAREF automotive are here
  • use cases identified in the paper are
    • Platooning
    • Automated Valet Parking (AVP)
    • Cooperative Perception Service (CPS)
    • Vulnerable Road Users (VRUs)
  • Philippe: these use cases fit well into the the future, i.e. much beyond a 5-year horizon
  • Philippe: IMHO currently in the CCS project,  short term is represented by the current High Mobility offering on the market, and the on-going work is rather looking at the mid-term,
  • Kevin: it would be good to ask OEMs what use cases are more tangible to implement
• Gap analysis deliverable - review feedback of draft sections on VSS, Sensoris, etc.
  • Philippe: I reshuffled the pages a little bit and the draft deliverable appears now in the main CCS page table of content, look at Gap analysis draft Vehicle Data Models - Overview & Gap Analysis deliverable
  • Philippe: Guru and Benjamin have provided their inputs, Guru added his inputs in the wiki, I added the link the CVIM doc prepared by Benjamin to the wiki page
  • Kevin: I reviewed the draft document on VSS prepared by Gunnar, the intro is not specific to VSS but fairly general
  • Gunnar: agreed, we need to ask again for the review work  the VSS doc
  • /TODO/ Daniel/Benjamin/Guru/etc please review the VSS doc
  • Gunnar: I will review the Sensoris section written by Guru
  • Kevin: I will review the CVIM doc prepared by Benjamin
  • Gunnar: Steve pointed us to two other data exchange standards from the Open Group
  • I found them to be mostly similar or related to what OCF might be doing.  I also found them to be fairly thin specs in particular O-DM but the messaging standard might have something useful
    • Open Data Format (O-DF) https://publications.opengroup.org/c14a
    • Open Messaging Interface (O-MI) https://publications.opengroup.org/c14b
  • We are wondering what OCF think about it:
    • Is it used by OCF or not ?
    • Is it out of scope and covering other unrelated things ?
    • or is it overlapping, but OCF have created other standards to cover this instead ? (It might of course boil down to a simple XML vs JSON preference...)
    • Unknown User (don.dulchinos) Do you have any feeling on how well these standards are adopted?
  • /TODO/ Don review these data exchange standards from the Open Group
  • Gunnar: we should consider adding some info on SAREF and the Open Group work in the gap analysis deliverable
• Design concerns wiki page - more feedback
  • link added to the CCS main wiki page
  • Gunnar: the topics / issues in the design concerns page should be transformed soon in a set of work items described in jira, Kevin has provided his comments already, other comments are welcome until next week call
  • I will also review the existing tickets in Jira that might be relevant to the topics described in the design concerns wiki page
  • Philippe: I will projectize this in Jira starting next week
• Sprint & backlog review (end of Sprint 4)

  • Jira
    server JIRA serverId 121ddff2-c571-320f-9e4d-d5b9371533bd key VCS-48

    target date for producing the gap analysis deliverable is 8 November, we will present it at the tech summit

  • Jira
    server JIRA serverId 121ddff2-c571-320f-9e4d-d5b9371533bd key VCS-59

    /TODO/ Gunnar ping Michael Ger to get a Cloudera architect into CCS project

  • Jira
    server JIRA serverId 121ddff2-c571-320f-9e4d-d5b9371533bd key VCS-35

    Daniel said he is "back" and should start working on it this week

  • Jira
    server JIRA serverId 121ddff2-c571-320f-9e4d-d5b9371533bd key VCS-60

    /TODO/ Gerald please do

  • Jira
    server JIRA serverId 121ddff2-c571-320f-9e4d-d5b9371533bd key VCS-6

    see above design concerns, projectization will be developed further starting next week

  • Jira
    server JIRA serverId 121ddff2-c571-320f-9e4d-d5b9371533bd key VCS-61

    done, see above

  • Jira
    server JIRA serverId 121ddff2-c571-320f-9e4d-d5b9371533bd key VCS-39

    no news from Sebastian, Gerald Spreitz can you help ?
• Enterprise data value: new topic to be added to the project scope ?
  • Steve: when I met with Ford last week, one of their concerns was how to make value out of the vehicle data
  • this is a gap in the CCS project charter according to Ford and GM perspective
  • Steve: it seems to me that these organisations do not fuly understand yet what means a shared platform for capturing and distributing vehicle data
  • Gunnar: one of the criticisms we had with the European OEMs concept of neutral server is that the OEMs will control all the vehicle data, we do not understand what the enterprise data value means for for the US OEMs yet,
  • Steve: theUS OEMs seem to be looking for which strategic partnerships they need to build for the vehicle data
  • Kevin: what kind of uses cases are foreseen , what kind of data rates are considered ?
  • Philippe: I would suggest to ask high mobility (Kevin) to deliver a company presentation at the tech summit because HM business in my opinion exemplifies what the enterprise data value is about

...

• Gap analysis
  • Gunnar: shares the draft sections on VSS available at this document and asks participants to review it
  • Guru: wonders whether building a huge wiki page containing all the sections of the gap analysis is the right approach
  • Gunnar: for the time being, in my opinion, the sections for each project should be structured according to the wiki page table of content
  • Guru: will finalize the draft sections on Sensoris accordingly in the document he initiated and will call for a review in one day or so

...

• Call with Sensoris
  • very good and friendly atmosphere in the call
  • Prokop seems to be quite open for a coordination discussion
  • He gave a rough overview od Sensoris including business cases and system architecture, business cases are OEM-related and do not intend to provide an open access to the vehicle
  • Sensoris objective is to describe what the car is sensing for the world surrounding it, e.g. number of lanes, road works, traffic signals, outside temperatue (as part of a data set called climate, temperature and weather)
  • Gunnar: VSS (was described by Prokop as...) focusing more on the in-vehicle data and SensorIS more on modeling the outside world that the car drives through.  We have not been through to compare the data models during the call but there seems to be is some overlap in some areas but not in other like map-related data and data with a location-based focus
  • Gunnar: License - Sensoris do not permit derivatives (Using CC-BY-ND).   It could be interpreted as they are only body that can launch Sensoris specs, but also means that flexible reuse is difficult.  They propose openess to anyone who wants to change the SensorIS spec.  
  • Unknown: "This is the way they work with Japanese projects"
    • look at the CCS minutes of July 22, link to Japanese projects:  http://en.sip-adus.go.jp/sip/
  • Gunnar: Sensoris welcome any proposal that would make their data model more complete, but this proposal would become part of the Sensoris data model because of their licensing approach
  • Prokop shows an architecture picture (that includes GENIVI and AGL as a kind of "technology choices" inside of vehicle.  Explanation was made about GENIVI Alliance actual scope and current projects.)
  • Sensoris main purpose is to make sure that OEMs are not delivering different data, they should deliver the same data
  • Prokop said it is out of scope of Sensoris to describe the system and software architecture, however they care about the "how" (e.g. protocols) to some extent
  • Gerald: motivation for having a common data model in Sensoris is for instance the wipers model (e.g. 3 bits on the CAN bus)
  • Gunnar: Gerald had a quite long discussion with Prokop about how OEMs provide the data, Sensoris does not care about the software architecture OEMs will use, more that the data that comes out is according to some shared standard (so that 3rd party developers can engage with more than one OEM).
  • Gunnar: it seems they would reuse whatever architecture is defined by GENIVI
  • Philippe: IMHO we should not fight for having an aligment of the data models, we could likely live with some duplicated representation for the data that overlap between Sensoris and VSS
  • Benjamin: agreed
  • discussion follows on GENVIVI scope vs Sensoris scope, VSS could be considered upstream w.r.t. Sensoris for the data defined in both projects
  • another meeting will be scheduled in 4-week time, we need to do our gap analysis between Sensoris and VSS first

    • Jira
      server JIRA serverId 121ddff2-c571-320f-9e4d-d5b9371533bd key VCS-35

        will be added to the new sprint
  • Scrum review

    • Jira
      server JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 121ddff2-c571-320f-9e4d-d5b9371533bd key VCS-42

      done

    • Jira
      server JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 121ddff2-c571-320f-9e4d-d5b9371533bd key VCS-47

      done

    • Jira
      server JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 121ddff2-c571-320f-9e4d-d5b9371533bd key VCS-31

      kept in the backlog, can be activated whenever Don provides us with an update on the OCF Automotive group work

    • Jira
      server JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 121ddff2-c571-320f-9e4d-d5b9371533bd key VCS-42

      done,

    • Jira
      server JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 121ddff2-c571-320f-9e4d-d5b9371533bd key VCS-52

      created, we might be interested in knowing more about the OCF cloud services framework in the future when we start looking at the available technologies for the framework

    • Jira
      server JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 121ddff2-c571-320f-9e4d-d5b9371533bd key VCS-40

      done

    • Jira
      server JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 121ddff2-c571-320f-9e4d-d5b9371533bd key VCS-50

      done, Gerald provided an updated version of the CCS block-diagram highlighting GENIVI components rather than Autosar framework

    • Jira
      server JIRA serverId 121ddff2-c571-320f-9e4d-d5b9371533bd key VCS-33

      done

    • Jira
      server JIRA serverId 121ddff2-c571-320f-9e4d-d5b9371533bd key VCS-35

      added to the sprint, new Jira ticket created

      Jira
      server JIRA serverId 121ddff2-c571-320f-9e4d-d5b9371533bd key VCS-53

        with blocking link added

    • Jira
      server JIRA serverId 121ddff2-c571-320f-9e4d-d5b9371533bd key VCS-38

      updated
      • Gerald: IMHO ISO ExVe is not too exciting, performing a gap analysis between ExVe is to be further discussed with Kevin,
      • ticket is reassigned to Kevin to determine whether it is worth GENIVI buys the access to the specs from ANSI/ISO,
      • Gunnar: then we should likely check the architecture proposed by ISO ExVe can be filled by some components we have identified in the GENIVI communication framework
  • Review of remaining items related to Analysis epic in the backlog

    • Jira
      server JIRA serverId 121ddff2-c571-320f-9e4d-d5b9371533bd key VCS-3

      actually done with the various surveys completed
    • tickets to be added to the next Sprint starting on 10 September:

      • Jira
        server JIRA serverId 121ddff2-c571-320f-9e4d-d5b9371533bd key VCS-4

      • Jira
        server JIRA serverId 121ddff2-c571-320f-9e4d-d5b9371533bd key VCS-5

      • Jira
        server JIRA serverId 121ddff2-c571-320f-9e4d-d5b9371533bd key VCS-6

      • Jira
        server JIRA serverId 121ddff2-c571-320f-9e4d-d5b9371533bd key VCS-7

      • Jira
        server JIRA serverId 121ddff2-c571-320f-9e4d-d5b9371533bd key VCS-24

        inputs for this work item will be given by the various gap analysis we have identified
  • Gap analysis deliverable

    • Jira
      server JIRA serverId 121ddff2-c571-320f-9e4d-d5b9371533bd key VCS-48

      updated with subtasks for Kevin, Gunnar, Gerald, Guru, Benjamin, Daniel for describing their contribution to the deliverable, please refer to the GAP analysis outline draft

Monday, August 26

Participants

...

• Sensoris
  
  • Gerald has contacted the project chairman
  • timeslot proposed on Thu 29/8 at 8:30am for a sync call (expected participants: Gerald (call moderator), Gunnar, Philippe, Benjamin),

    Jira
    server JIRA serverId 121ddff2-c571-320f-9e4d-d5b9371533bd key VCS-49

    updated and closed
  • Philippe will send an invite once the timeslot is confirmed by Sensoris chairman has confirmed the timeslot
• discussion on the draft content of the gap analysis deliverable prepared by Kevin: Gap analysis draft Vehicle Data Models - Overview & Gap Analysis deliverable
• discussion on whether to include CVIM in the gap analysis, even though the results of Automat have not been exploited by OEMs which participated to the Automat project
  • consensus seems to be there are some good stuff in CVIM that is worth appearing in the gap analysis
• Kevin, Gerald, Gunnar will start populating the deliverable in the wiki
• report from Don on OCF automotive
  • Don was not able to sync with OCF staff as expected
  • Don showed a slide deck about working mode with GENIVI
• next week agenda: backlog and sprint review
• misc. Benjamin's slide deck on his findings on CVIM are available there
• Adjourned: 17:05

...

• Connected Services project charter

  • Philippe asks participants to review the project charter and provide comments by next week

  • Philippe: asks participants for their inputs on what should be the project deliverables; he suggests a combination of paper work (likely EA (UML) models, text-based specifications) and code (prototype implementation, proof-of-concept), reminds that Gerald presented the list of outputs of the various sprints identified in the workplan he presented at the last AMM (look here)
  • Kevin: the text is good, the charter will be useful for sharing with the HM team
  • /TODO/ all review the project charter and send comments to Philippe by email by next week
• ISO Extended Vehicle update
  • Gerald provides a couple of links he got from Bosch After Market colleagues
  • link: https://www.figiefa.eu/new-economic-study-vehicles-manufacturers-external-backend-data-access-models-risk-major-cost-burden-to-consumers-and-independent-stakeholders-reaching-e65-billion-in-2030/
  • link: https://www.figiefa.eu/wp-content/uploads/Knobloch-Gr%C3%B6hn-OEM-3rd-Party-Telematics-General-Analysis-Report.pdf
    
    • this link presents the results of an evaluation made by a consulting company about how the data access around ExVe is implemented

  • link: https://www.caruso-dataplace.com/wp-content/uploads/2019/06/137%C2%A9THOMAS_BITTERA_CARUSO_HAL2_05062019-copy-2.jpg

  • link: https://www.neutralvehicle.com/ (yet another start-up company)

  • /TODO/ all review these materials, we will put this at the agenda of next week's call,

    Jira
    server JIRA serverId 121ddff2-c571-320f-9e4d-d5b9371533bd key VCS-38

    added to the backlog and current sprint
• W3C work status
  
  • Gunnar presents the content of the following wiki page Connected Services: W3C VISS/VSI specification status
    • discussion on proff-of-concept implementation of the VISS/VSI
  • Kevin: is there a general plan/timeline for VSS Gen2 ?
  • Benjamin: things will be delayed until the data models for transportation workshop has happened (scheduled on 12-13 September 2019)(look here)
    
    • current WG charter started on May 2018 and will end on June 2020, 

      Jira
      server JIRA serverId 121ddff2-c571-320f-9e4d-d5b9371533bd key VCS-27

        commented
• Sensoris
  • Gerald shows a slide deck (link TO BE ADDED) from Bosch describing the status of Sensoris work
  • Version 1.0.0 of the Sensoris specification will be released in the next days under CC-ND license
  • data provided by Sensoris are not only about the vehicles but about the environment
  • Version 1.1.0 will introduce the concept of "jobs"
    • jobs = login jobs running for a certain period of time for a certain fleet of vehicles
  • Gunnar: it would be good to identify how much overlap we have, shows the interest of different domain taxonomies
  • Gerald: it would be good also to set up a call with the sensoris project once we have reviewed the Sensoris specification that will be published soon
• AOB
  • telco schedule
    • DECISION  we will start scheduling the weekly call on Monday afternoons at 4pm CET next week (8 July)
    • (added offline) cloudera and autonomic.ai which are based on US Pacific coast have been invited to join

...