GAP analysis outline draft

Introduction

• Introduction to the Cloud & Connected Services GENIVI project
• Charter summary
• Scope
• Deliverables

Analysed specifications

• Listing the open source projects that are analysed in this document:
  • Vehicle Signal Specification (VSS)
  • SensorIS
  • Extended Vehicle (ExVe) ISO standard
  • (Connected Vehicle Information Model (CVIM) from AutoMat) - need to decide how to present this based on the project state
  • P.Car - Android Auto vehicle interface (should there be a Jira task to survey this project separately first?)
  • Any other IOT projects?
• Listing of projects that were examined but not included in the GAP analysis - together with the reasons: (we need to decide how to handle these two projects, this is just a suggestion)
  • Connected Vehicle Information Model (CVIM) from AutoMat?
  • Connected Car Consortium

Analysis criteria

• What parts of the projects were analysed and to what extent?
  • Motivation & problem space
    • Scope
    • Licenses
    • Applicable to different domains
  • Data model & data characteristics
    • Encoding
    • Technologies
  • Contents
    
    • Specification
    • Tooling
    • Source code structure
  • Stakeholders
    • Current status
    • Roadmap
  • Metadata & policies (Unknown User (benjamin_klotz) , Benjamin has a special interest for metadata & policies of all existing projects)

GAP analysis

following above list of analysis criteria

Motivation & problem space

Vehicle Signal Specification (Gunnar Andersson )

TBA.

SensorIS (Unknown User (gururaja.n) )

TBA.

Extended Vehicle (ExVe) ISO standard Unknown User (kevinval)

TBA.

CVIM (Unknown User (benjamin_klotz) )

TBA.

Table comparison (if applicable)

TBA.

Data model & data characteristics

Vehicle Signal Specification (Gunnar Andersson )

Content outline:

• Need for shared data (model) description
• Tree hierarchy equivalence
• VSS specification structure and content
• Terms/nomenclature/definitions ("what is a data model, specification, ..." - reusing Daniel's infographic)
• Beyond: Deeper analysis of data characteristics - data ontologies
• (Open) Licensing
  • Common data model - can companies agree?
  • ...plus proprietary and function-specific extensions (still with common format and tooling)
• Car-network focus vs. generic usage
• VSS principle can be applied in network - ECU-internal, intra-ECU, and cloud connected services
• W3C protocol definition and usage of VSS
• Potential for VSS use in CCS.

SensorIS (Unknown User (gururaja.n) )

TBA.

Extended Vehicle (ExVe) ISO standard  Unknown User (kevinval)

TBA.

CVIM (Unknown User (benjamin_klotz) )

TBA.

Table comparison (if applicable)

TBA.

Contents

Vehicle Signal Specification (Gunnar Andersson )

TBA.

SensorIS (Unknown User (gururaja.n) )

TBA.

Extended Vehicle (ExVe) ISO standard Unknown User (kevinval)

TBA.

CVIM (Unknown User (benjamin_klotz) )

TBA.

Table comparison (if applicable)

TBA.

Stakeholders

Vehicle Signal Specification (Gunnar Andersson )

TBA.

SensorIS (Unknown User (gururaja.n) )

TBA.

Extended Vehicle (ExVe) ISO standard Unknown User (kevinval)

TBA.

Table comparison (if applicable)

TBA.

Metadata & policies

Vehicle Signal Specification (Gunnar Andersson )

TBA.

SensorIS (Unknown User (gururaja.n) )

TBA.

Extended Vehicle (ExVe) ISO standard Unknown User (kevinval)

TBA.

CVIM (Unknown User (benjamin_klotz) )

TBA.

Table comparison (if applicable) (Unknown User (benjamin_klotz) To Be Confirmed)

TBA.

Conclusions

TBA.

References

TBA.

Project Team

TBA.