ACORD Standard VehicleTelematicsNotify messaging allows telematics data providers to deliver data to data consumers (typically insurance carriers). These messages provide a standard XML method to package and deliver vehicle telematics events, data streams, and data summaries.
The ACORD P&C VehicleTelematicsNotify transaction specification, available to both ACORD members and non-members, provides information needed to implement and deploy telematics data delivery in a secure, standard way, enabling data quality and consistency and allowing single implementations to connect with multiple business partners.
VehicleTelematicsNotify messages are essentially data "push" messages whereby an unsolicited message is sent from one party to another with no expectation of an immediate business response beyond an optional acknowledgement of receipt. A typical implementation has a telematics service provider sending messages at the conclusion of a 24-hour period, or on conclusion of a vehicle trip.
Value Proposition Adopting the message format provides the following benefits:
- Telematics Service Providers can route a single standard VehicleTelematicsNotify message format to multiple insurance carriers without the need for carrier-specific coding.
- Carriers can accept VehicleTelematicsNotify messages from multiple data providers in a common, standard format without the need for provider-specific coding.
- All VehicleTelematicsNotify communications may be electronically tracked and maintained by data provider and consumer telematics systems.
- Communication is quicker, time is saved, workflow improved and errors reduced avoiding loss of data.
- Using VehicleTelematicsNotify messages eliminates the need to rekey data or process and import spreadsheets, reducing manually introduced errors, increasing data consistency and workflow auditability.
Business Context
Multiple scenarios illustrate the workflow communications that currently occur between an insurance carrier and business partners:
VehicleTelematicsNotify can be used to send:
- Individual telematics device status events, e.g., connects and heartbeats.
- Individual vehicle event notifications, e.g., severe braking or cornering, acceleration, and other extreme vehicle maneuvers.
- Complete, uninterpreted device data, including position, accelerometer, speed, etc.
- Extracted device data streams reflecting individual vehicle events.
- Telematics scores.
In scope
The relevant parts of the telematics data provider (TSP) / data consumer (insurance carrier) process ecosystem are shown on the accompanying diagram. A vehicle may carry a number of telematics devices, each of which has its own protocol and format for communicating through the telecommunications infrastructure to a Telematics Service Provider. This data provider typically processes and packages the data for consumption by their insurance carrier business partners. The ACORD P&C XML VehicleTelematicsNotify transaction is used to deliver this data to various business partners in a consistent format, maintaining data quality and consistency.
Outcome
The VehicleTelematicsNotify message standard was published in 2013, and updated in 2014. The message specification is available to: