MobiWize Web site project

1. Supervisor: Boaz Mizrachi Students: Rami Younes Israel Adler MobiWize Web site project

2. Agenda • Motivation • Project description • System block diagram • Basic Usage Model • Entrance Screen • Driving Sessions Screen • Google Earth Screen • Personal Summary and Recommendations • Feedback Screen • Framework • Progress

3. Motivation • Background: MobiWize develops a system which helps drivers reduce their fuel costs by changing driving habits. The system collects driving session data from the car using system sensors and car sensors through the OBDII interface. All the data is transferred to a database.Besides real-time advices displayed by the in-car system, we would like to display to the driver or fleet manager extend data regarding the driving sessions. This will be done by a web interface.

4. Project description Building a web (Server/Client) application which takes the driving session data, arranges it and shows in-depth and statistical data.The data will be displayed using Google Earth API.

5. System block diagram

6. Basic Usage Model 1) The user logs into the website using his username, plate number and password. 2) In the first screen a home page screen is displayed (Driving Sessions Screen). 3) In the second screen a dynamic graphical map is displayed. (Google Earth Screen). 4) The third screen displays Personal Summary and Recommendations. 5) The last screen is a Feedback Screen which allows the user to send a feedback.

7. Entrance Screen • Components: • Driver’s name • Vehicle plate number • Password • Actions: • Accept: user name + password + vehicle number • Verify credits against SQL table • Approve / deny / permissions

8. Driving Sessions Screen • Components: • Sessions list + scroll bar with the following columns: • Data + time, duration , Origin + destination, Distance, Accumulated fuel Average fuel, Total grade, Optimizer check box • Buttons: • Sort, Detail, Optimizer, Exit • Actions: • Select sessions • Open (details) in Google Earth – show KML files per session • Optimizer: • If check box checked: • Per the selected session • Per origin and destination • Calculate best route and speed profile • Calculate expected fuel consumption (momentary / total) • Generate KML and open Google Earth • Call-out: where to release throttle pedal, total summary at the end

9. Google Earth Screen • Components: • Selected sessions • Per session: • Speed (height) • Fuel consumption (color) • Engine Load (width) • Recommendations (call-outs) • Summaries (call-outs) • Arrange components as XML sub-directories: • Session / recommendations / summary • Hover: • At each session point, show current load/consumption on the Vehicle BSFC diagram • Buttons + Actions • Standard Google-Earth

10. Summary and Recommendations • Components: • Show personal summaries (per entire sessions / per time period) • Fuel efficiency: • Per accelerations, Per cruise, Per decelerations • Maintenance: • Compare several criteria / parameters between same vehicles to get recommendations for maintenance • Tire pressure • Engine temperature • Compare to: • same make/model, same driver (different periods) • Show graphs / tables / numbers / colors • Personal Recommendation: • Generate auto recommendations for driver according to above mentioned summary • Actions: • Sort, search, compare

11. Feedback Screen • Components: • Send email to us. • Text explanation on how to communicate with us.

12. Framework • Web server containing PHP – HTTP, CSS, PHP • PostgreSQL database • JavaScript • Google Earth API • Integration into existing website

13. Progress • Background study • Entrance Screen • Driving Sessions Screen • Google Earth Screen – in work currently • Driving session data import • Personal Summary and Recommendations • Feedback Screen Further work: • Optimization of current route • Finding optimal route