Safe Ride Digital

 

 

DMS373: Midterm Update

Michaela, Morgan, Sade

March 4, 2015

Recap and Status

This term is dedicated to...

1. Finalizing our rider-dispatcher solution
2. Producing a digital solution for drivers

 

We're also back on track: Public Safety Directors are on-board!

• Recently received the "go ahead" for live testing and offered to help publicize the online application on their end
• We can also proceed with a tablet in the van (It needs to be securely placed and not in use when the van is in motion)

Further Motivation

• One rider on average per night is dropped (considered a "no show")
• Students have reported waiting > 1 hour for a pick up
• Short-distance requests may be denied by dispatchers
• Drivers normally conduct 20 to 25 trips per night, so we see room for efficiency

Dispatcher UI

A few enhancements:

• Real-time confirmation column
  • Entries can now go into "Incoming Requests" and "Completed Requests"
• Drag and drop capability

 

Potential solution to help prioritize requests:

• Three variables determine priority: number of passengers, frequency of pick up location, frequency of drop off location

We're officially live!

saferide.sa.rochester.edu

 

Only for testing now...

Soon to be publicized to the student body!

Video Updates

7 interviews, 2 scheduled for after break

3 Riders

3 Drivers

1 Dispatcher

The video emphasizes:

• Safe Ride is important
• Safe Ride is inefficient from all sides involved and plagued by miscommunication
• Safe Ride is popular Safe Ride is popular, & there’s a demand for it to improve

Video Updates

What's left:

• Dispatch, van footage

• Narrative footage

• Integrate explanatory audio/voice-over

• Integrate stills and footage of team at work

Preliminary Driver Interviews

Number of drivers interviewed: 5 (out of 9)

 

Drivers would like to see...

• Listing of the pick up and drop off location
• Number of riders and the time
• Rider notification feature
• Touch screen is preferred over voice API
• A way to manually add a request or no shows

Iteration 1: Driver Interface

Driver Feedback Round 1

Number of drivers interviewed: 4 (out of 9)

 

Positive feedback:

• Easy to understand use
• Covers everything the driver does throughout the night
• Has time stamps

Areas of improvement:

• Need to allow confirmed rides to move to top of queue
• Feature to alert students that driver is there
• Need to show number of riders with each request

Moving Forward

Our updated goals include:

• Iterate on driver interface solution; share with Dana Perrin (Public Safety) for approval
• Complete two rounds of live testing by end of March in order to open it up to the student community
• Continue interviewing with drivers to enhance their interaction with the Rails-based version
• Finalize video and record shots of students using Safe Ride Digital

Schedule for rest of term

March 16 - 20: Week 1 of live testing and interviews

March 22: Round 2 of Driver Interviews

March 22 - 28: Week 2 of live testing and interviews

March 30: Open online app to student body

March 31: Finalize promotional video

April 6 - 11: First testing of tablet with drivers

April 12 - 18: Iterate on version per feedback from interviews, improve any bugs

April 20 - 25: Prepare for atrium presentation