In order to use the existing standards most efficiently, we started the project with an exploration of the existing interoperability standardization efforts.

After further researching this problem in the scientific literature, we found no widely adopted industry-wide data models. Some approaches claim to improve interoperability.However, most advances in the scientific literature related to this problem are isolated cases, and are very limited in their scope, only working for some data formats already known to the authors. This makes it difficult to reuse their solution and raises the necessity of coming up with a more universal solution that may be used by Konetik and/or other companies that provide services based on telematics data.

Telematics data companies use arbitrary formats, but tend to have information that is similar, and could be adapted to work on the same services. If we can transform a telematic dataset to be in any format, then we can make it compatible with any telematics system, regardless of its format. The necessary condition is it must contain the necessary information.

TelematicZap solution allows users to share and control the access of services to their telematics data, irrelevant of the data format. In the next sections, we’ll explain the motivation behind it, and how we managed to achieve it.

You can experiment with our prototype by setting up the following GitHub repository locally: github.com/iotlabsltd/telematiczap, or simply take a look at our 2 min demo video instead.

The live version also provides the following features:

– An authentication system for accessing the dashboard and submitting data

– An open specification of the API and data models (telematiczap.uc.r.appspot.com/api/)

– An endpoint for registering OAuth 2.0 client applications (telematiczap.uc.r.appspot.com/o/applications/)