Commercial and Fleet Vehicle activity

Overview to COVESA Board for Expert Group consideration

June 2024

Copyright ©2022 COVESA

| 1

13 September 2022 |

CV Overview

Initial Goal:

Establishing a VSS marketplace,. fleet focused but applicable to other verticals

Interests and alignment:

BoF recap, stakeholders attracted and related interests

Proposed Expert Group:

Scope, liaisons, participants, input and promotion request

1

2

3

Commercial Fleets Run on Data

As data drives their businesses, they have come to rely on and will increasingly require reliable, secure, high quality information platforms

Productivity

• Customer service times
• Identify unexpected stops
• Accurate arrival and departure times
• Optimized routes
• Reduce time waste and inefficiencies

Optimization

• Manage vehicle maintenance
• Proactively detect electrical and other issues
• Advanced diagnostic data

Safety

• Collision notifications
• Driver risk management
• In-vehicle coaching
• Track speeding
• Seat belt use
• Driving in reverse

Sustainability

• Increase fuel efficiency. Decrease Idle
• Track CO2 emissions
• Fleet electrification
• EV performance monitoring and reporting

Compliance

• Electronic driver logs
• Tax reporting
• Vehicle inspection reports DVIR

Expandability

• E.g.
• Winter operations
• Cold chain
• Video
• …

Telematics Timeline

​

​

​

OBDII

OEM Cloud Ingestion

In-Vehicle API

1990s Present Future

When will OBDII “go away”? No clear answer and potentially a long tail in some vehicle classes, being replaced with alternate interfaces & gateways

​

Current In-Vehicle APIs are mostly proprietary per manufacturer (custom engineering required) - awaiting widespread adoption of VISS

4 | © 2023 Geotab Inc. All Rights Reserved

The Issue: OEM data currently not suited for all use cases and different across OEMs

To make best possible use of the OEM data, it has to match the data (in quantity and quality) generated by aftermarket devices (including bi-directional communication!)

Safety

Productivity

Fleet Optimization

Compliance

Sustainability

Available Data Points per OEM

Available Rules & Reports per OEM

Data Parity w/ GO

OEM A

OEM B

OEM C

OEM D

OEM A

OEM B

OEM C

OEM D

*Note: percentages not current, analysis as of 2022

5 | © 2023 Geotab Inc. All Rights Reserved

Today: Not leveraging the value of data, but creating complexity with integration efforts

​

​

Different types, makes, model, years - and data

OEM

Telematics Service Provider

Fleet Owner

ExVeh

LeaseCos

Insurance

Traffic Infrastructure

Smart cities

Charging Providers

...

Multiple OEM and TSP clouds

Multiple data users

x

x

TSPs

6 | © 2023 Geotab Inc. All Rights Reserved

Complexity reduction by using standards for non-differentiating and non-competitive tasks

TSP

Different vehicle makes and models in one fleet

For a seamless and value-adding product offering in an ecosystem, interfaces between parties should be frictionless and interoperable based on agreed standards and best practises

Multi-make fleet connectivity solutions

Integration complexity

Fleet Customer

OEM

Fleet connectivity ecosystem

• new revenue stream for OEMs
• Develop and integrate embedded TCU (OEM competency)
• ensure car IT security

• Use vehicle data and analytics to manage fleet across multiple brands - in one system
• make use of embedded TCU

• minimize integration effort
• make use of embedded TCU
• Data parity with aftermarket device
• Bi-directional communication for new use cases

✓

╳

✓

7 | © 2023 Geotab Inc. All Rights Reserved

Most needed Data Points, ~80 to start with

Fleet Operational Data

2

Source: Fleet Management Data Set, including Use Cases, frequency and Importance

8 | © 2023 Geotab Inc. All Rights Reserved

Why Sampling Methodology is relevant

• Typically OEMs provides fixed interval (time or distance), event or both
• More data not necessarily better (e.g. GPS @1 sec) - relevant data is needed
• Curve logic provides intelligent lossy compression, open sourced under MPL
• Produces a better representation and is more efficient (lower cost)

Sampling Methodology

1

9 | © 2023 Geotab Inc. All Rights Reserved

OEM engagement

• HD Truck OEM following guidelines less VSS in NA
• Japanese OEM intent to pilot in EU
• Various stages of discussion with a number of OEM
• A few monitoring activity, several have made notable incremental improvements to current data offerings, endorsements provided.
• Business case created for OEM perspective
• Attracting HD OEM

Update

1

10 | © 2023 Geotab Inc. All Rights Reserved

Liaisons Established

• ACEA Fleet Management Standard (FMS) - mapped to VSS, undergoing evolution and On-board API
• American Trucking Association’s (ATA) Technology and Maintenance Council (TMC) - Data Science team and RP1226
• Verband Deutscher Verkehrsunternehmen (VDV)
• Information Technology for Public Transportation (ITxPT)

Update

1

11 | © 2023 Geotab Inc. All Rights Reserved

Industry Verticals Attracted

• Ford EV researchers in Köln has been working on improved range prediction as part of an EU grant
• Insurtech

Update

1

12 | © 2023 Geotab Inc. All Rights Reserved

Expert Group Charter Scope

• Still pushing original guidelines seeking to establish VSS in marketplace, additional industry verticals
• Fleet Management Standard (FMS) and ATA TMC RP1226 On-board API
• Additional necessary signaling

Proposal

1

13 | © 2023 Geotab Inc. All Rights Reserved

Additional Signaling

​

Task Force started, Hierarchical Informational Model (HIM) / VSS overlays

• DTC and fault codes
• Control Unit firmwares’ version and software validation numbers
• Trailer
• Tractor to trailer interface (wired, WLAN, other)
• Upfitting (refrigeration, salt spreader, plow, sirens)
• HD truck/bus not adequately represented already in VSS

Proposal

1

14 | © 2023 Geotab Inc. All Rights Reserved

 VSS abstraction 

(databroker)

RP1226 Gateway

FMS 

(OEM centric)

J1939 <> UDS <> SOVD

Telematics device SW

3rd Party Telematics SW

rFMS forwarder

OEM Gateway

3rd Party cloud

OEM cloud

VDV

OBDII/ 9pin

COVESA FMDG

FMS

VDV

(Gov centric)

VMRS (Fleet centric)

RP1226 Gateway

(SDV)

Fleet Management Data Guidelines

Open Telematics Framework (SDV based) SOA arch

...

*SDV fleet vehicle must:

• Be self discoverable both in cloud/vehicle
• Have redundancy capabilities in-built for Fleet-Ops
• Unified Data model needed
• Current support for OBD – J1939  – future needs to include UDS - SOVD

HMI app

Traditional Edge Telematics Device

RP1226

Requesting input, participation and promotion

• Draft Charter
• Specifically want input on naming, scoping, business case
• Introductions to colleagues, partners and help with wider promotion

Input and Promotion

1

Contact: Thomas Spreckley and Ted Guild

16 | © 2023 Geotab Inc. All Rights Reserved