Page History

...

• Call with Sensoris
  • very good and friendly atmosphere in the call
  • Porkop 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 rather describes the in-vehicle data, we have not been through the data models during the call, there 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 want derivatives, there are the only body that can launch Sensoris specs, they propose openess to anyone and 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)
  • 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
  • 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
  • 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

...