top of page

Welcome to our Use Case Demo for Safety Analytics!

 

Minimize downtime and predict breakdowns before they happen: Explore how Predii generates accurate, vehicle-, mileage-, and location- specific error patterns from historical repair records.

 

​​Simply try out our sample dashboard application based on public NHTSA data and see how it works!

About this Demo: Example Application NHTSA Safety Data

​

The National Highway Traffic Safety Administration (NHTSA) maintains public data base for consumer reported safety issues.  NHTSA uses this information as a basis for investigation into defects and potential vehicle safety recalls. 

​

This Demo Dashboard is configured to answer safety and quality related questions and shows aggregated insights extracted from these customer complaints on a Year, Make, Model, Engine and even Parts level.

​

These insights include:

  • Top Customer reported concerns ("symptoms")

  • Top Technician reported failures

  • Top replaced parts & parts failure rates

  • Mileage distribution

  • Geo Information​

​​

Vehicle Make and Year Filter​

In total, the NHTSA data base contains more than 1.2 Million records on real life vehicle issues, safety & quality concerns, and component failure. This POC Dashboard is based on 9,656 (customer-reported) extracted symptoms and 11,299 (technician-reported) failures across 268 makes¹ and 6,138 models.

​

Simply filter for Makes, Models, and Vehicle Year for refinement. 

​¹total of extracted makes: 1056 incl. trucks, trailers, RV. For quality of the analysis we considered all makes with records >10

​

Top (Driver-reported) Customer Concerns

​'Customer verbatim’ data is extremely hard to translate into usable analytics. Customer complaints consist of textual data, real life human language, which is unstructured, messy, and contains very domain-specific automotive terminology. 

​

Predii’s Natural Language Processing engine has been purpose-built to extract predictive and prescriptive insights from unstructured textual, sensor, and procedural automotive data; our algorithm has been fine-tuned to understand automotive jargon for 10+ years.

​

This allows us to translate the entirety of individual records into classified, categorized symptoms as shown in the example.

​

Top (Technician-reported) Vehicles Failures​

In additional to verbatim data ('technician notes)', Technician-reported failures contain Diagnostic Trouble Cdes, Part numbers, ACES/PIE definitions, and more. The Predii technology is able to capture these data points, categorize them, and translate them into actionable insights.

​

Top Technician Reported Failures for this POC data set include: Check Engine Light, specifically defined noises heard from different parts of the vehicle ("knocking", "grinding", "clicking").

​

Top Contributing Makes & Models​

Allows viewers to break to aggregated views across all symptoms and failures and narrow down to specific Makes and Models. 

​​

Mileage Distribution​

Odometer readings show the mileage distribution for each concern/failure per make and model, allowing users to identify patterns and trends. Mileage distribution is crucial for advanced analytics including prediction of quality issues.

bottom of page