Prism uses data captured by telematics devices, combined with other contextual data, to produce insightful analysis of vehicle activity. For telematics providers this allows Prism to be used by their clients to provide value-added services leveraging their existing installed devices.
Data transfer methods
Prism can accept data through one of the following methods:
If your telematics system provides a REST API with endpoints that allow the data listed in our Data Input Specification to be accessed, our team can work with you to develop a Prism integration add-on that will extract data from your system on a daily basis via standard REST API calls.
Prism has a sophisticated framework for managing REST API data extraction processes that includes navigating API rate limits and multi-client processes.
If your telematics system does not provide an API, you can send flat data files in an agreed format that aligns with our Data Input Specification to an Amazon Web Service S3 bucket that we will provision for you.
This allows you to control how and when files are sent (we suggest daily) to Prism. When they arrive, Prism processing will be triggered via S3 Events.
To use this option you must be able to supply files in a consistent format on an ongoing basis using automated processes. Manual file extracts and uploads, while possible, are prone to human error and not advised.
If your devices or systems provide a real-time binary or encoded data stream that can be directed externally, our team can provide an HTTP or Websocket endpoint that allows the data to captured by Prism.
This method, while offering real-time data access, does not allow historic data to be accessed by Prism, which is often a requirement of clients.