Product Brief - TML - TATA - v1.3

TomTom Product Brief CONFIDENTIAL
V1.2 Final
TomTom Product Brief
TATA motors Program 2022/23
© 2021 TomTom Global Content B.V. Page 1 of 27

V1.2 Final
Table of contents
1 Application request .................................................................................................... 4

1.1 Customer platform .............................................................................................. 4
1.2 Geographical coverage and volume ....................................................................... 5
1.3 Timelines ........................................................................................................... 6
2 Solution proposal ....................................................................................................... 7
2.1 Solution description ............................................................................................. 7
2.2 Products & services included in the offer ................................................................ 8
3 Product overview ....................................................................................................... 9
3.1 Maps ................................................................................................................. 9
3.2 Connected services ........................................................................................... 13
3.3 Places .............................................................................................................. 14
3.4 Navigation ....................................................................................................... 15
4 Integration and customization ................................................................................... 18
4.1 Architectural overview ....................................................................................... 18
4.2 Integration and support services ......................................................................... 18
4.3 Deliverables ..................................................................................................... 18
4.4 Access control .................................................................................................. 19
4.5 Security ........................................................................................................... 20
4.6 Privacy and data processing ............................................................................... 20
4.7 Certification ..................................................................................................... 21
5 Quality ................................................................................................................... 22
5.1 Quality standards .............................................................................................. 22
5.2 Security and privacy standards ........................................................................... 24
5.3 Product quality ................................................................................................. 24
5.4 Product performance ......................................................................................... 25
6 Glossary and references ........................................................................................... 26

V1.2 Final
Version history
Version Status Date Author Changes
Version1.3 Closed 2021-10-26 Frederik Bohez
Table 1 Version history
© 2021 TomTom Global Content B.V.

This document provides information regarding the products and/or services of TomTom Global Content B.V.
and/or any of its affiliates (“TomTom”). The content is confidential and subject to change. Any disclosure to
a third party is subject to TomTom’s non-disclosure agreement. It is strictly forbidden to disclose or use the
document or its content without the prior approval of TomTom.

V1.2 Final
1 Application request
TomTom is pleased to present this product proposal to TML. This product proposal is based on
the request of TATA motors Program 2022/23 as described in RFQ_Map-Navigation
Requirements_CVP Phase3_13102021.pdf.
The Solution Provider is responsible for carrying out below work description
• Navigation solution development for the connected car features in infotainment and mobile application
• Quality assurance for the work packages
This document is descriptive in nature and does not supersede other documents such as
compliance responses or product reference lists.
1.1 Customer platform

No description of customer platform, like head unit, cloud setup, smartphone app or other
devices is available, recommendation is shared
Component Target platform TomTom recommendation
TML (no info received) Dual-core @1.5GHz (minimal)
4.000 DMIPS per core
CPU
Quad-core @1.9GHz (recommended)
4.500–5.000 DMIPS per core
TML (no info received) Reasonably modern GPU supporting
Graphics
OpenGLES 3.0 (or newer)
TML (no info received) LPDDR3 1GB (minimal)
RAM
LPDDR4 >1GB (recommended)
TML (no info received) 40GB (depends on NDS map coverage
Storage
and configuration)
Display TML (no info received) 10” or more for IVI display
Positioning TML (no info received) GNSS + dead reckoning
Connectivity TML (no info received) WiFi and cellular (3G or better)
Table 2 Customer platform

V1.2 Final
1.2 Geographical coverage and volume

Requested by TML, this program is India only and with estimated volume of 280K vehicles.
TomTom can provide the solution components for the requested geographic regions, as defined
below:
Continent Region
Africa Africa
Southern Africa
Americas Caribbean
North America
South America
Asia Central Asia
India (requested by TML for the TATA offering)
Israel
Japan (partner data from Zenrin)
Middle East
Southeast Asia (including Hong Kong and Macao)
South Korea
Taiwan
Europe Europe
Turkey
Russia
Oceania Australia and New Zealand
Oceania
Total
Table 3 Geographical coverage
For the above markets in this proposal, features can vary in availability from country to country.
Please review the appendices for a detailed overview of available coverage and map features
per market.

V1.2 Final
1.3 Timelines
TomTom assumes the following milestones for this product proposal:
Date Milestone
2021 Project award & project kick-off
2022 week 17 Feature Complete date (Phase1: companion app, only SDK support)
2022 week 40 Feature Complete data (Phase2: Infotainment (tbc by TML))
2022 week 26 SOP – Start of Production (Phase 1: companion app)
2023 week 08 SOP – Start of Production (Phase 2: infotainment (tbc by TML))
2022 week 26 SOS – Start of Servicing Term
2026 week 08 EOP – End of Production
2029 week 08 EOS – End of Servicing Term
Table 4 Timelines
Should the project award decision be postponed, the planning will be delayed accordingly.
Further planning details are provided in the appendices, as well as division in project
responsibilities.

V1.2 Final
2 Solution proposal
2.1 Solution description

Phase 1: TML Mobile app - TML Companion App
- TML team is developing the companion app for its users.
- By using TomTom technology which enables the end-user to:

o To search for locations and create routes upfront before getting in the car.
o To send location or route towards the infotainment system (phase 2) the syncing
is developed by TML. On requested NavSync API can be requested and offered
separately later-on.
o To use the navigation on its companion app to perform the last mile navigation to
the destination from last parked car location.
o The Commercial offer provides more information on the Go SDK offering: Search-
Routing-, Navigation-, Display API as well es the extended routing & Reachable
range API.
Phase 2: TML Infotainment - TomTom In-dash Navigation solution

- TML team will be using navigation application and user interface developed by TomTom
for the in-dash infotainment system
- The navigation system should include some online services: Search, Traffic and Routing.
For the electric vehicles also extended route can be created.
- The onboard map should be capable of receiving incremental updates using the installed
data sim.
- Alternative routes should be available, and recalculation or route is required in case of

severe traffic delays along the route or on request.
- The Tabular weather information should also be made available. (for In-dash system
TPEG is used)
- This product brief provides detail description of the provided commercial offer which
includes: Navkit2, Android Navkit UI, NDS map with Map updates as well as the provided
connected services.

V1.2 Final
2.2 Products & services included in the offer

This proposal includes the following products and services, described in more detail in the
referenced sections:
3.1 Maps
3.1.1 SD Map
3.1.2 NDS Map
3.1.3 Map Display API
3.2 Connected services
3.2.1 Traffic Incidents Feed
3.2.2 Traffic API
3.2.3 Tabular Weather Feed
3.3 Places
3.3.1 Search API
3.4 Navigation
3.4.1 NavKit2
3.4.2 NavKit2 UI for Android
3.4.3 Routing API
3.4.4 Long Distance EV Routing API

V1.2 Final
3 Product overview
This section provides a high-level overview of the products included in the solution proposal.
3.1 Maps
3.1.1 SD Map
TomTom SD (Standard Definition) Map provides a digital representation of the real world as
relevant for vehicle navigation use cases. TomTom SD Map is based on TomTom defined data
specification which is shared with the customer.
The proposed SD Map data content for TATA motors Program 2022/23 will include the following
attributes (where available):
Attribute Description Included
Road Topological road network enhanced with detailed attributes to ✓
Geometry enable destination addressing and turn-by-turn navigation
functionality, containing additional features supporting map
display. This includes:
Street Names Official and alternative street names. ✓
House Number House number availability at road
ranges crossings
Manoeuvres Information relating to prohibited,
restricted or priority routes
Blocked Passages Physical Obstructions
Structures Bridges & Tunnels (dimension,
over/underpass levels, etc.)
Speed limits Speed restriction values as attribute on
road element
Signpost Exit, route number and destination
Information information on limited access highways
Lane Information Lane-specific characteristics incl. type,
number of lanes per road element,
divider type and direction.
Traffic Message Codes (locations and paths) and
Channel (TMC) reference to core geometry.
Road classifications Classes identifying road importance in
terms of usage
Core POIs POIs categories: airport/airline access,
city centre, ferry terminal, frontier
crossing, mountain pass/peak Railway
station, rest area, toll booth, hospital
(ER), beaches, golf course, national park
Local particularities
Restricted access
area
POIs POIs categories include but are not limited to the following ✓
categories and sub-categories: Doctors Office, Hotel/Motel,
Restaurant, Retail Store, Sports Centre and Theatre. POIs feature

V1.2 Final
a number of key attributes and are connected to 3D landmarks,

where available. POI data additionally supports multiple entry-
points.
Speed profiles Speed Profiles (compact), Speed Profile Extended ✓
Buildings Building footprints for height “shoeboxes” ✓

2.5D
Voice maps Phonetic data for text-to-speech ✓
Address Relation of the XY coordinates to the location of a buildings or ✓
Points other structures to street name, house number etc. that make up
an address.
Table 5 SD Map attributes
The above SD Map attributes are available in India.
3.1.2 NDS Map

TomTom NDS (Navigation Data Standard) map is a runtime format compiled map suitable for
navigation and ADAS applications requiring map content from an embedded storage. NDS maps
are modular in content, configurable by region and updatable by content and region.
The offered NDS map in the NDS profile “Automotive Mapline 3.0” includes following building
blocks in NDS Version 2.4.6:
NDS Product NDS Building Block Description
Overview Map Basic Map Display Overview map for navigation background in large
scale
Navigation Basic Map Display Background map display consisting of road network,
Automotive land use
Routing Road network enhanced with detailed attributes to
support route calculation including lane info,
curvature, gradient, speed limits, speed profiles, and
sign content (no icons)
Full Text Search Search information built from e.g. administrative
areas, street names, address points, house number
ranges, and postal codes
Names Name information of administrative areas, street
names, address points, house number ranges, postal
codes, and POI
Traffic Information TMC table to relate traffic information to the road
element
POI POI information
Speech Voice maps for speech output
LM High 3D Objects 3D landmarks for advanced display
Every Product Shared data Meta Information for NDS product to be shared over
all NDS building blocks
Table 6 NDS map building blocks

V1.2 Final
Availability of attributes by country is provided in the Product Reference List. No Product

Reference List is required as only one country, ‘India’ is offered where all building blocks are
available. Please note that the data size of the NDS map will grow over time, as the maps
become more complete and take in more of the real world.
3.1.2.1 Content protection

TomTom’s compiled map data requires content protection and verification. TomTom and TML
need to agree on a secure authentication mechanism for protecting the map data, as well as to
verify the software on-board. This solution determines the authenticity of the map content and
identifies valid devices, e.g. based on production series ID.
3.1.2.2 NDS map updates

TomTom will make the following NDS map updates available:
Update type Update frequency Delivery method
Full updates Yearly CDN, FTP
Incremental update Quarterly CDN
Table 7 NDS update frequency
Map updates can be applied on a region-by-region basis, allowing for an optimization between
update channels as shown in the picture below. The navigation application can apply logic to
automatically retrieve updates for the driver-relevant regions (IQ Maps).
Figure 1 Map update channels
3.1.3 Map Display API

TomTom Map Display API is a suite of web services designed for developers to create web and
mobile applications around map display. Map Display API supports the following use cases in a
Smartphone Companion App or Web Portal:
• Display a map at the given location and show its detailed surroundings.
• Place the current vehicle location on a map, or other points of interest to the user, such
as favorite locations or calendar events.
The style of the API output can be configured with a Map Styler.

V1.2 Final
Figure 2 Map styler - 2D view
Vector
The Vector service delivers geographic map data packaged in a vector representation of
squared sections called vector tiles. Each tile includes pre-defined collections of map features
(points, lines, road shapes, water polygons, building footprints, etc.).
Vector maps are the most versatile online maps, providing the following benefits:
• Less bandwidth consumption than raster tiles
• Customizable to fit client application look & feel
• Rotates and tilts to provide an interactive user experience
Figure 3 Vector map
Raster
The Raster service renders map data that is divided into gridded sections called tiles. Tiles are
square images (png or jpg format) in various sizes which are available at 23 different zoom
levels, ranging from 0 to 22. The raster tiles are static images that display a detailed map all-in-
one.
Copyright
Service to provide copyright information on the information above.
More information on Map Display API is provided in the Developer Portal

https://developer.tomtom.com/ .

V1.2 Final
3.1.3.1 Maps SDK

TomTom can provide a Maps Mobile SDK (Android, iOS) and Maps Web SDK (JS) to support the
development of a smartphone companion app or web portal. The SDKs provide client libraries
containing client-side code that make it easier to develop apps with the common use cases such
as search for a location, routing to a destination, rendering a map and placing pins on the map
or other map manipulations etc. The SDKs depend on the needed APIs: Search API, Routing
API, Map Display API and Traffic API.
3.2 Connected services

3.2.1 Traffic Incidents Feed
TomTom Traffic Incidents Feed provides near real-time information on traffic incidents including:
• Congestion (jams) on roads with abnormal delays
• Turn-dependent congestion (turn-dependent jams) (turning lane is impacted differently
than main carriageway)1
• Jam ahead warnings
• Roadworks
• Roadblocks
The Traffic Incidents Feed is calculated globally every 30 seconds, however the update frequency
to the client may be slower than that.
3.2.1.1 Delivery method

The Traffic Incidents Feed is made available in the following delivery method(s):
Delivery method Format Description
Intermediate feed Protobuf or HTTP-based protocol that retrieves traffic
DATEX II information for an entire country
End-user feed TPEG2 TEC Traffic Event Compact according to TPEG2
specification by TISA
Table 8 Traffic Incidents delivery methods
1
Part of the ‘Lane Level’ package which is available as a separate subscription

V1.2 Final
3.2.2 Traffic API

TomTom Traffic API is a suite of web services enabling application developers to embed traffic
information in their application. Traffic API provides incident and flow data in both tile and
segment data. Traffic API tiles are used in combination with Map Display API tiles.
Service Method
Traffic Incidents Incident Details
Incident Viewport
Raster Incident Tiles
Vector Incident Tiles
Map Styles
Table 9 Traffic API
More information on Map Display API is provided in the Developer Portal

https://developer.tomtom.com/ .
3.3 Places
3.3.1 Search API
TomTom Search API is a service in the form of an online API which provides among others
address search, POI (Point of Interest) search and (Reverse) Geocoding. A free text search
function allows finding addresses, street, geographies and POIs. Search results can be updated
while typing to quickly find what the user is looking for. Many additional optional parameters
are available that allow for high degree of customization in the search request. For example,
searching around a point, along a route or within a bounding box, language selector, search by
Brand or Category ID (e.g. to create a ‘find parking button’), or filters for EV plug connector
type or traditional fuel type.
Common use cases supported by the Search API:

• Search for an address, a POI, or a combination of both.
• Search for an area, for example: "Chinatown".
• Search in the direction you are heading.
• Search for cross streets, for example: "Clay Street Drumm Street".
• Search for a POI near a POI or address, for example:
o "Coffee near XYZ company"
o "Restaurants on Main Street"
o "ATMs near AMC Theater"
o "Parking near 1234 Main Street"
Supported methods are:

Service Method
Search Fuzzy Search
Points of Interest Search
Category Search
Geometry Search

V1.2 Final
Nearby Search
Along Route Search
Geocoding Geocode
Structured Geocode
Reverse Geocoding Reverse Geocode
CrossStreet Lookup
Table 10 Search API methods
More information on Search API is provided in the Developer Portal

https://developer.tomtom.com/.
3.4 Navigation
3.4.1 NavKit2
TomTom NavKit2 is TomTom’s portable navigation software development kit (SDK). It provides
high-quality services to be used by navigation applications operating on different platforms,
ranging from automotive head units to mobile devices. It is designed to allow integrators and
application developers to add tailored application logic and user experiences on top, which are
accessed through APIs. SDKs are available to assist with integration.
NavKit2 is provided with map content and navigation logic (e.g. route calculation, search) by
cloud services. Today NavKit requires connectivity to operate. NavKit2 navigation functions are
resilient against connectivity loss, but endured operation without connectivity will result in a
degraded navigation experience.
Key features of NavKit2 include:

- Customizable map rendering, generating multiple map views
- Search
- Routing with customizable consumption model, for various route type, vehicle types and
optimization/avoidance criteria
- Guidance for turn by turn navigation
- Map matching based on pattern matching
- Support for onboard map, online map and live map data
- Onboard prediction engine for destination and route prediction
- Driving assistance support by providing relevant information to ADAS functions in the
vehicle
- Passive community input

V1.2 Final
The following table shows in more detail the behavior of the navigation engine in the different
connected states.
While connected Connectivity Lost in Pre-installed map

(Full online) transit (Fall back) (Fall back)
Basic TbT Online Search Map Display for Route Online Routing*
services Corridor
Online Routing (configurable buildings, Online Search*
LM, DTM)*
Online Guidance Follow the planned Onboard Guidance
route
Online Map Display No re-route, no search Onboard Map Display
(Phase 1: will be using
online maps through
API)
Phase 2: will be using
onboard NDS map in
the car)
Traffic Services Online Service No traffic** Proprietary*
IQ routes (speed
profiles available)
EV Services Real time No real time availability Real time availability
availability of and Charging station and Offline - charging
charging stations POIs cached stations (POIs)
POIs*
Online Range Onboard Range Onboard Range
Visualization Visualization Visualization
Online Range Range Along planned Onboard Range Along
Along Route route
Online Long Follow the planned Onboard Long Distance
Distance EV route EV Routing
Routing
China, Korea, China, Korea, Japan China (online services
Japan and India and India for KOR and JPN
subject of discussion)
Map Format Proprietary Proprietary NDS
Map Update Weekly Weekly Configurable frequency
Frequency (IQ Maps)*
Table 11 NavKit2 configuration
*Depending on configuration of pre-installable map it this case TML – TATA solution the
quarterly update was suggested.
** When no connectivity is available only cached traffic (with longer time validity) is available
A detailed description of NavKit2 including support for languages and localization is provided in
the Product Description. (Phase1: companion app languages will be defined by TML)

V1.2 Final
3.4.2 NavKit2 UI for Android

TomTom NavKit2 UI for Android is the navigation HMI based on NavKit. NavKit2 UI is optimized
for in-car usage and offers the application logic and the user interface to all the navigation
features. It draws on the vast UX experience of TomTom and is focused on usability and
minimal driver distraction, including for example TomTom’s IP protected route bar.
A detailed description of NavKit2 UI for Android including support for languages and localization
is provided in the Product Description (Phase 1: for the companion app languages are selected
by TML) .
3.4.2.1 Keyboard
This proposal assumes that the keyboard is provided by the platform, including functionality for
handwriting recognition.
3.4.3 Routing API

The TomTom Routing API enables online planning of a route from a given origin and
destination, providing various options to plan a route with different criteria. The service utilizes
TomTom Traffic and TomTom speed profile data in addition to the latest NDS map data to offer
the best available routes. As an additional benefit compared to the on-board route planning, the
Routing API takes the full traffic flow model into account and is not limited to a certain radius
around the user’s location. Incorporating such data into an on-board routing solution would
require significantly increased bandwidth.
Service Method
Routing Calculate Route
Calculate Reachable Range
Common Routing Parameters
Batch Routing Asynchronous Batch
Synchronous Batch
Matrix Routing Asynchronous Matrix
Synchronous Matrix
Table 12 Routing API methods

3.4.4 Long Distance EV Routing API

TomTom Long Distance EV Routing service calculates a route between a given origin and
destination. The route contains charging stops that have been added automatically based on the
vehicle's consumption and charging model. Each charging stop results in an additional leg in the
route response. Each additional leg contains information on charging in its leg summary,
including remaining charge at arrival and charging time.
Long Distance EV Routing API requires an electric consumption model to be set.


V1.2 Final
4 Integration and customization
4.1 Architectural overview

Companion App
TomTom Cloud
App Store Application
NavSync
NavSync Positioning Publish
Client
SDK
User Login Navigation SDK libraries
Interface (Go SDK)
Head Unit TML TomTom Cloud Services

System App Cellular Cloud Online Service
or WiFi SDK Repository
Service Traffic Incidents API Search API
Navigation Software IAM
Location TPEG Service Long distance EV Routing API
GNSS NavKit2 UI ComKit
Manager TPEG2-PKI Routing API NDS Web Portal
MapDisplay
TPEG2-WEA Extended routing
Positioning Services TML API Navigation Tiles API
Car Sensor Engine Connector
CVP
Manager Content Delivery
Sensors Ecosystem
NavKit 2
Sensor Onboard Service
Manager Map
USB Drive Dealer Admin
TML 3rd party TomTom
Figure 4
4.2 Integration and support services

Included in this proposal are the following integration and support services:
Incase customer creates own application based on TomTom software development kit or API
support might be provided on request.
4.3 Deliverables
4.3.1 Content deliverables
Map data in NDS format is delivered via dedicated, secure electronic delivery to the customer.
In case NDS maps are delivered directly to system clients, the map data is delivered as a
service.
4.3.2 Software deliverables

TomTom delivers its embedded software deliverables as binary software packages with the
necessary accompanying documentation, via dedicated electronic delivery, e.g. a secure FTP
server. TomTom assumes that TML will provide for a software update mechanism. Such a

V1.2 Final
mechanism should include a place where the software update can be found (e.g. a web portal or
application UI), a download/transfer mechanism to the vehicle/client and an upload/install
mechanism on the TATA motors Program 2022/23 system. The software update package format
shall be agreed with TomTom, in which the new TomTom software can be contained such that
the update mechanism can install this on the device. The update mechanism shall ensure that
this package is only usable for the intended device/users and cannot be copied to or used in
unauthorized devices.
4.3.2.1 Open Source policy

TomTom has its own Open Source Policy that is created to comply with laws and regulations.
TomTom’s Open Source policy is continuous reviewed to guarantee it complies with customers’
requirements.
To manage open source compliance, a tool called Protex (by BlackDuck) that automatically scans,
discovers and identifies software origins is used. In every release, a report is generated and the
license requirements of the open-source software in use are checked. In case of open-source
software licenses that are not permitted the code is removed. If required by the license an
attribution list is created or the source code is published. The Protex report is shared with
customer as part of the Release Notes.
4.3.3 Service deliverables
4.4 Access control

TomTom provides solutions to control access to the over-the-air services that are part of this
product offer, that match the needs of TML in terms of technical capabilities and the commercial
end-user licensing scenarios that shall be applied.
Access Control Service (authorization validation)

TomTom’s Access Control Service provides access to TomTom online services based on
entitlements managed by TML, by validating a JSON Web Token (JWT) or certificate issued by
TML for each client device. To support the validation process, integration with the authorization
service of TML is required.
This gives TML full flexibility to decide per individual device, which set of services it should be
authorized to receive and during which time period.
Access Control Service (group entitlement)

TomTom’s Access Control Service provides access to TomTom online services based on a pre-
defined entitlement for an entire group of client devices. Each group can be defined in
agreement with TomTom, for example as car lines, and will be authorized to receive the same
set of services until the same end date. The authorization of client devices belonging to a group,
is handled with an API key issued by TomTom. TML will need to support replacement of API
keys, for example via software updates.
With this solution, TML is not required to do any entitlement or access management to enable
the access control to TomTom’s services.
Access Management Service (individual entitlement provisioning)

V1.2 Final
TomTom’s Access Management Service provides per-device entitlement and access

management to TomTom online services, including access control.
Devices authenticate against the service with client certificates individually signed by TomTom.
For each authorized device, TML provisions entitlements for a defined set of services until an
individual end date.
Access Management Service (automatic entitlement provisioning)

TomTom’s Access Management Service provides per-device entitlement and access
management to TomTom online services, including access control.
Devices authenticate against the service with client certificates individually signed by TomTom.
Entitlements for each device are created automatically in the system based on pre-defined rules
for the set of services and duration of service period, so that TML does not need to do any
entitlement provisioning or management.
4.5 Security
Security is part of the TomTom software development lifecycle which means that in every step of
the development process on or more security measures are embedded. These include, but are
not limited to, threat modeling (TARA), Static application security test (SAST), software
composition analysis (SCA), Penetration testing, Security verification with public cloud security
modules, and continuous vulnerability management. In addition, TomTom has security policies in
place and there are regular trainings and awareness sessions.
On the technical aspect, TomTom makes use of proven cloud technologies (e.g. Microsoft Azure)
with their accompanying availability, scalability and security aspects. TomTom also ensures that
all connections are secured by using HTTPS to guarantee confidentially and integrity of the data.
The TomTom services can be protected by our Access Control Service to allow for individual or
group-based access.
For the on-device data, TomTom ensures that the NDS map data is encrypted so that corrupted
and/or malicious maps can’t be decrypted. For accessing this data, the navigation engine needs
to have an NDS key store (typically stored in a secure storage) and key store password (part of
the NavKit secure library). TomTom map updates are releases with a digital signature so that
corrupted/malicious updates cannot be installed in the vehicle.
4.6 Privacy and data processing

As an independent service provider, TomTom complies with privacy laws and regulations.
Therefore, providing us with probe and sensor data is subject to receiving the necessary end-user
consent as required by personal data protection law. TomTom deidentifies all location data it
receives and anonymize it further to use it for new product cases. Customers will control the
collection of probe and sensor data but will grant to TomTom the right to use the deidentified and
anonymous data for product improvements, quality assurance and new product development for
the benefit of all customers. TomTom processes probe and sensor data solely on behalf of its
customers and will not resell location probe and sensor data.

V1.2 Final
TomTom aligns to the requirements set out in the General Data Protection Regulation EU
2016/679 and will also align to the California Consumer Privacy Act.
4.7 Certification
Certain government regulations might impose specific requirements on map data or require
certification, in order to be allowed to sell the system. This can imply the use of a specific part
number, in case governmental map requirements are not compatible with neighbouring
countries. In addition, censoring requirements can cause delays in the preparation for start of
production. Acting upon this is responsibility of TML as e.g. to apply for system compliance
clearance required by country’s laws and regulations. TomTom will provide information for map
certification where available but has not incorporated any cost for changes that might be
required of the system in order to pass changed certification.

V1.2 Final
5 Quality
5.1 Quality standards

TomTom maintains a certified ISO 9001:2015 Quality Management System (QMS) that covers
all process areas (e.g. sales, engineering, purchasing, quality, operations, etc.). The quality
system consists of procedures, templates and training material combined and presented in a
uniform way. The quality system is compliant with the standard requirements of the automotive
industry (ISO 9001) and our (OEM) customers. The different process areas (see picture here
below) are assessed by the external assessor every 6 months and on a monthly basis by means
of internal audits.
Figure 5 TomTom Automotive Quality Management System Process House
TomTom is also committed to ethical business and environment being a member of the EICC
and driving activities at different sites in accordance with ISO 14001. TomTom follows a
milestone-based life cycle for its software development process.
5.1.1 Continuous improvement

TomTom is driving a continuous improvement program to provide better quality products to its
customers with Automotive SPICE as guidance.
TomTom has set up several continuous improvement initiatives in the software development
process to improve in the most relevant areas for its customers. Consequently, improvements
are executed on a regular basis.
Our improvement proposals can be the result of:

V1.2 Final
- internal and external audits

- management reviews of the quality system
- issues submitted by the quality system users
- improvement areas defined by management team and/or discipline management
These improvements are reviewed regularly by the management team to assure support,
execution and deployment within the organization.
5.1.2 Continuous Integration and Continuous Delivery

TomTom uses the Continuous Integration (CI) and Continuous Delivery (CD) software
development practices as part of the standard way of working of project teams, which includes
automated building, automated testing, every single change to the master repository is built
and tested before being committed. Adopting these practices in the software development
provides developers with fast feedback of their code change, ensures no breaking changes are
merged to master and creates build artifacts for each build. At TomTom, we’ve chosen Jenkins
as our main CI system and Artifactory as the main build artifact storage repository.

V1.2 Final
5.2 Security and privacy standards

TomTom manages information security with policies and standards aligned with ISO27001.
TomTom central security team defines security policies and standards. It supports security
operation and product development. Product units opt for secure development practices and
tools that suit their development best. Threat modelling, security static/dynamic analysis,
penetration test and other security activities are widely adopted in the software development
lifecycle. The security operation center continuously monitors the network for potentially
malicious activities. The incident response plan is in place to manage data breaches in the rare
case that they do occur.
On privacy, TomTom aligns to the requirements set out in the General Data Protection
Regulation EU 2016/679 and will also align to the California Consumer Privacy Act.
5.3 Product quality

Release rules:
• For intermediate release during development phase:

o Review all severity S, A and B issues and review actions set to address them
• For production release:
o No severity S and A issue
o Less than 10 severity B issues and review of actions set to address them
• During development:
o Monitor the different reported bugs to address them in a timely manner –Monitoring of the time taken to repair
issues in line with their severity and the release package requirements
o If there are specific requirements from the customer to be applied in this area, the identification of the specific
requirement will be integrated in the product quality plan and agreed between both parties before the development is
started.
Details might be agreed in SLA in due time, close to business awarding.

V1.2 Final
5.4 Product performance

For all projects, TomTom identifies the major product performance criteria that are to be
checked and monitored throughout the release that will be provided to the customer to ensure
the performance is in line with requirements.
These criteria will need to be agreed between both parties at an early stage of the product
development.
5.4.1 Data consumption

TomTom services require near-constant connectivity to deliver frequent updates on the
surrounding situation. The amount of data consumed depends on the following factors:
• Driving behavior
o Time of day, e.g. rush hour vs. night-time
o Seasonality effect (e.g. more traffic jams in winter vs. spring)
o Location, e.g. urban vs rural area
o Average duration or length of the trip
/ session time
• Configuration settings
o Inner & outer radius (see image)
o Maximum messages within a radius
o Stateless (one-off) requests
o Which services to use (Traffic, Parking, EV,
Weather, Fuel, etc.)
o In general, there is a trade-off between data
consumption and user experience.
Bandwidth consumption varies for many reasons (beyond TomTom’s control) and cannot be
guaranteed. However, for a specific driver profile and configuration settings TomTom has
performed simulations to estimate the bandwidth consumption.
The below represents bandwidth consumption calculations for a driver with a typical
“commuter” profile (daily trips during rush hours, afternoon trips during the weekend) in a
major European metropolitan area. Bandwidth consumption was approximately half for the
same profile and settings in a rural area.
End-user Feed Data usage (MB / hr)

Traffic Incidents Feed – TPEG2 TEC 0.28
Table 13 Bandwidth consumption calculation with typical 'commuter' profile

V1.2 Final
6 Glossary and references

ADAS Advanced Driver Assistance System
ACS Access Control Service
API Application Programming Interface
ASR Automatic Speech Recognition
CDN Content Distribution Network
CDP Content Download Portal
CPU Central Processing Unit
ECU Electronic Computation Unit
EMI Electromobility (charging infrastructure)
EV Electric Vehicle (also known as BEV or Battery Electric Vehicle)
GNSS Global Navigation Satellite System
GPS Global Positioning System
FPI Fuel Price Information
(H)AD (Highly) Automated Driving
HD High Definition
HP Horizon Provider
HMI Human Machine Interface
IME Input Method Engine
MQTT MQ Telemetry Transport
NDS Navigation Data Standard
OS Operating System
POI Point Of Interest
PCC Predictive Cruise Control
PKI Parking Information
PPC Predictive Powertrain Control
Protobuf Method for encoding structured data in an efficient yet extendable format
http://code.google.com/p/protobuf
RAM Random Access Memory
SD Standard Definition
TFP Traffic Flow and Prediction
TISA Traveller Information Services Association
TMC Traffic Message Channel
TPEG Transport Protocol Experts Group
TTS Text To Speech
UI User Interface
USB Universal Serial Bus
VIN Vehicle Identification Number
VLI Vigilance Location Information
VPA Virtual Private Assist
WEA Weather (information)

V1.2 Final
References
List of tables
Table 1 Version history .................................................................................................... 3
Table 2 Customer platform ............................................................................................... 4
Table 3 Geographical coverage ......................................................................................... 5
Table 4 Timelines ............................................................................................................ 6
Table 5 SD Map attributes .............................................................................................. 10
Table 6 NDS map building blocks .................................................................................... 10
Table 7 NDS update frequency ........................................................................................ 11
Table 8 Traffic Incidents delivery methods ........................................................................ 13
Table 9 Traffic API ......................................................................................................... 14
Table 12 Search API methods ......................................................................................... 15
Table 13 NavKit2 configuration ....................................................................................... 16
Table 14 Routing API methods ........................................................................................ 17
Table 15 Bandwidth consumption calculation with typical 'commuter' profile ......................... 25
List of figures
Figure 1 Map update channels......................................................................................... 11
Figure 2 Map styler - 2D view ......................................................................................... 12
Figure 3 Vector map ...................................................................................................... 12
Figure 4 ....................................................................................................................... 18
Figure 5 TomTom Automotive Quality Management System Process House ........................... 22

Product Brief - TML - TATA - v1.3

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Product Brief - TML - TATA - v1.3

Uploaded by

Copyright:

Available Formats

TomTom Product Brief CONFIDENTIAL

TomTom Product Brief

TATA motors Program 2022/23

© 2021 TomTom Global Content B.V. Page 1 of 27

1 Application request .................................................................................................... 4

© 2021 TomTom Global Content B.V. Page 2 of 27

Table 1 Version history

© 2021 TomTom Global Content B.V.

© 2021 TomTom Global Content B.V. Page 3 of 27

1.1 Customer platform

© 2021 TomTom Global Content B.V. Page 4 of 27

1.2 Geographical coverage and volume

© 2021 TomTom Global Content B.V. Page 5 of 27

© 2021 TomTom Global Content B.V. Page 6 of 27

2.1 Solution description

- By using TomTom technology which enables the end-user to:

Phase 2: TML Infotainment - TomTom In-dash Navigation solution

- Alternative routes should be available, and recalculation or route is required in case of

© 2021 TomTom Global Content B.V. Page 7 of 27

2.2 Products & services included in the offer

© 2021 TomTom Global Content B.V. Page 8 of 27

© 2021 TomTom Global Content B.V. Page 9 of 27

a number of key attributes and are connected to 3D landmarks,

Buildings Building footprints for height “shoeboxes” ✓

The above SD Map attributes are available in India.

3.1.2 NDS Map

© 2021 TomTom Global Content B.V. Page 10 of 27

Availability of attributes by country is provided in the Product Reference List. No Product

3.1.2.1 Content protection

3.1.2.2 NDS map updates

Figure 1 Map update channels

3.1.3 Map Display API

© 2021 TomTom Global Content B.V. Page 11 of 27

Figure 2 Map styler - 2D view

Figure 3 Vector map

More information on Map Display API is provided in the Developer Portal

© 2021 TomTom Global Content B.V. Page 12 of 27

3.1.3.1 Maps SDK

3.2 Connected services

3.2.1.1 Delivery method

© 2021 TomTom Global Content B.V. Page 13 of 27

3.2.2 Traffic API

More information on Map Display API is provided in the Developer Portal

Common use cases supported by the Search API:

Supported methods are:

© 2021 TomTom Global Content B.V. Page 14 of 27

More information on Search API is provided in the Developer Portal

Key features of NavKit2 include:

© 2021 TomTom Global Content B.V. Page 15 of 27

While connected Connectivity Lost in Pre-installed map

© 2021 TomTom Global Content B.V. Page 16 of 27

3.4.2 NavKit2 UI for Android

3.4.3 Routing API

More information on Search API is provided in the Developer Portal

3.4.4 Long Distance EV Routing API

Long Distance EV Routing API requires an electric consumption model to be set.

More information on Search API is provided in the Developer Portal

© 2021 TomTom Global Content B.V. Page 17 of 27

4 Integration and customization

4.1 Architectural overview

Head Unit TML TomTom Cloud Services

USB Drive Dealer Admin

TML 3rd party TomTom