When data from users arrives in the back-end, it goes through several stages of processing: data cleaning, data filtering, and ultimately storing.
Depending on your use case and preferences, you can choose how much of that process you want to use, and what part you want to handle on your own back-end system.
There are several architecture options available that allow developers to use our services in different and unique ways:
Using the full workflow, from collection through processing to storage:
This is best for clients that are looking for a full telematics solution - everything you need is included.
Using our collection interface and sophisticated processing tools, but storing the data in your own back end:
This is best for clients that are looking for high-quality telematics data, but want to run extensive analytics and statistics across the entire data set - we provide quality data, you access and analyze it however you want.
Using our hugely scalable [Collection platform] (https://docs.telematicssdk.com/docs/architecture#option-3-collection)
(and as well as the convenient in-device pre-processing using our SDK) can provide many benefits, even if you do all the processing and storing yourself. The method requires advanced telematics knowledge to properly process the unfiltered raw data.
If you are going to use full work-flow, no additional actions are required from you. That is the default scheme and all data collected by the Telematics SDK will be processed, stored, and available via APIs.
The rest of the options (Collection and processing, Collection only)
For the rest of the options, you have to set up [Data Export]
To find out more about the platform and available data, please refer to Data workflow and categories of data
You can combine the options or use all of them together.
Principal schematic of data flows The scheme description
|Full workflow||Collection and Processing||Collection only|
|User Services API|
|Additional API services|
|List of Trips|
|Basic trip statistics|
Updated about 1 month ago