Automotive Linux Wiki

Note that this information may or may not be out of date. This expert group is no longer meeting and its work is complete.

Welcome to the Gap Analysis Expert Group. While the name does not sound too exciting this Expert Group fulfills an important role for AGL. The task of this Expert Group analyze the AGL system stack and compare it against various targets from different perspectives.

None - Group is defunct

The following are considered possible starting points for gaps analysis.

1. AGL Specification version 0.82 doc pdf
2. GENIVI 6.0
3. Tizen IVI 3.0
4. JLR Use Cases - see Use Cases and Requirements for IVI
5. Typical IVI system - this is an abstract concept rather than a definitive specification. In most cases individuals doing the comparison to a typical IVI system do not have a written spec.

There are a number of different gap analysis targets that have been considered.

1. Gap between Tizen IVI 3.0 and a “typical IVI system”
2. Gap between AGL spec 0.82 and a “typical IVI system”
3. Gap between AGL spec 0.82 and GENIVI 6
4. Gap between AGL spec 0.82 and Tizen IVI 3.0
5. Gap between Tizen IVI 3.0 and GENIVI 6
6. Gap between AGL spec 0.82 and JLR Use cases

The results of each of these analyses may feed into the 1.0 version of the AGL specification.

This gap analysis prepared by Symphony Teleca compares the Tizen IVI 3.0 (Release 03/2014) against the feature set of a common IVI platform that OEMs are currently building into their vehicles. It does not include any future features. This gap analysis uses the feature perspective and identifies features, sub-features and sub-sub-features. It also identifies, if possible, where the gap is located (e.g. middleware, operating system, etc.)

Tizen IVI Feature Gap Analysis
Tizen IVI Feature Gap Analysis

Not Started

Not Started

This analysis is being performed by a number of AGL members in Japan. Each company took one or more sections of the AGL spec and performed the necessary analysis. There have been several face to face meetings in Japan to discuss these results as well.

Toyota's analysis on HMI: toyota_gap_analysis_homescreen.xls

Pioneers Analysis on AGL App Framework: pioneer_gap_analysis_agl_app_framework.xlsx

Panasonic's Analysis on Web API: panasonic_webapi_gapanalysis.pdf panasonic_tizenwebapi_list.xlsx (note: there is no web APIs defined in the spec v0.82, so this study shows the “status” of Tizen Web API.)

Fujitsu Ten's Analysis on Linux Kernel & Drivers: fujitsuten_gap-analysis_kernel.pdf (note: “NG” in the document means “no good”, thus gaps have been identified)

Not started. This may be available from the GENIVI Alliance.

Not started.

(+ AGL specification 1.0)

This gap analysis prepared by IoT.bzh compares the Tizen IVI 3.0 (Release 03/2014), current Poky/OpenEmbedded Yocto layers, and GENIVI Yocto layers (“meta-ivi”).

It also analyzes their respective states with regards to AGL specification 1.0.

Tizen IVI, Yocto, GENIVI Gap Analysis (AGL spec 1.0)