Join us to participate in the upcoming 2019 City:One Challenge. 

Crowdsourced Driver Monitoring for Mapping High Collision Risk Location

An app which monitors drivers for harsh braking, aggregates & clusters harsh braking locations across drivers as a risk display analytic

Photo of John Lindsay
4 2

Written by

Hard braking is considered one of the most highly predictive variables for predicting future crashes. However, normally harsh braking is tied to individual drivers. 

This patented composite app has two parts. The front end app is a smartphone app which monitors drivers for harsh braking. When harsh braking occurs, the location is logged. Over time clusters of harsh braking may be observed on the map display, enabling individual drivers to change behavior at those locations. The back end is an anonymous, aggregate view of harsh braking events across the drivers who choose to contribute to the city. A searchable map display of those aggregate events is available to the city traffic engineer. Again, clusters of harsh braking may be observed for their attention, with higher frequency clusters drawing attention of the traffic engineer for possible corrective action. 

Describe who will use your solution (1,000 characters)

Individual drivers would be the users of the front end mobile app. Traffic engineers and Departments of Transportation would be the primary users of the back-end aggregate data

Describe your solution's stage of development

  • Prototype - you have built a prototype and tested it with potential users

Tell us about your team or organization (500 characters)

John Lindsay - Inventor, founder, lead developer

Size of your team or organization

  • 2-10

Funding Request

  • $100,000

Rough Budget (500 characters)

$50k - promotion of the mobile app to drivers within the municipality $50k - additional development, storage, and compute in response to pilot usage

Describe how you would pilot your idea (1000 characters)

The first phase of the pilot would be localized marketing of the app to drivers within the municipality. Once a threshold usage is reached, the dashboard screens would be provide to one or person within the municipality.

Describe how you would measure the success of your pilot (1000 characters)

Key metrics are expect to be: Number of front-end app installations Frequency of front-end app use Number of harsh braking events measured Frequency of back-end usage by traffic engineers Number of hotspots targeted for further study or correction

Sustainability Plan (500 characters)

Yes. After a pilot period of feedback, usage, and features revisions/additions, the expect fee structure is monthly or annual fee to the municipality, with the hard money return on investment for a municipality would be a reduced frequency and man-hours of first responder deployments. Soft money return on investment for a municipality would be factors such as increased safety reputation.


Join the conversation:

Photo of MaCie' Moore

Hey John Lindsay this is MaCie' one of the online facilitators here! Thank you for participating in the challenge! I love this idea! I am not new to car accidents or near accident situations. Will the information be updated depending on the time of day, for example during peak traffic hours ? Also will you overlay this with other variables that could be causing hard braking like construction, school zones, etc?

Photo of John Lindsay

Hello MaCie,

The back-end data is updated in near real-time. To illustrate, one of the search filters shown in the search screen in the above images is a "Last Hour" filter. As there isn't a central repository for those other variables, the back-end does not currently overlay them. But if a pilot or other information dictates, the system could incorporate additional data to be included for display/processing.

View all comments