Open Telematic Platform

One adapter. Different apps.

Apps run on the OTP Adapter inside the vehicle. Each application has its own purpose and configuration. It uses the vehicle and device data intended for that purpose and connects it to its cloud service.

Product visualisation of the OTP Adapter on a workbench, with vehicles in the background
OTP Adapter · Product visualisation
App examples

What vehicle data can enable.

These examples illustrate the OTP app concept. The functions implemented for a project depend on the apps used, their configuration and the available vehicle data.

Trip log

Record trips, positions and available distance data and prepare them for a digital trip log.

Accident

Analyse available motion and vehicle data to provide the associated application with indications of a possible accident.

Theft

Use vehicle positions and movements as the basis for a theft-monitoring application.

Maintenance

Prepare available operating and diagnostic data for maintenance needs, vehicle condition overviews and service processes.

Refuelling

Combine available fuel-level and consumption data with trip data to help track refuelling and fuel use.

Your application

A custom app uses the data your product needs. We discuss the vehicle connection, processing on the adapter and the destination cloud.

Configurations

Configuration makes the difference.

Apps share the technical foundation of the OTP Adapter. The data they collect, how they combine it and where they send the results depend on each app’s configuration. The OTP Backend manages how these elements work together.

How the platform works
OTP Adapter: enclosure views and size comparison with a smartphone

What should your vehicle be able to do?

Let’s discuss your application, the vehicle data it needs and the cloud where that data should arrive.