BAuD II WP3 Workshop/Demo 2017-08-17 Mathias Johanson Alkit Communications AB

Concept Montrig WICE unit VCC Engineer Concept Measurement assignment design Survey design Analytics design BAuD/WICE back-end Montrig Subjective / objective data analyses Analytics fw (triggering subjective user feedback) Monitored signals Answers uploaded Questions sent to app Bulk measurement data upload Was the alert relevant ? Yes No In-vehicle signals monitored and logged WICE unit Driver’s smartphone with subjective data capture app Test vehicle

Framework Architecture Users Presentation layer / User interface Back-end server architecture Measurement Task design tool Survey design tool Measurement Task Manager Monitoring & Triggering mechanism Subjective Data Task Manager Analytics Framework Telematic service layer Smartphone App Service Layer ? ? ? Data sources

Prototype system implementetation End user WICE Portal Test objects Web front end / GUI Measurement task Analysis definition WICE unit (WCU) WICE Analysis server MCD-Hub Signal Reader MDF reader Java processing R scripts Analysis result WICE back-end MDF-files MDF shot files BAuD WP3 server Web front end / GUI Was the alert relevant ? Yes No Poll design tool montrig DB Q A

Pilot Use Cases Two focused active safety use cases: Driver Alert (DAC) and Forward Collision Warning (FCW)

DAC Use Case Investigate distribution of ’tired’ vs. ’distracted’ When DAC triggers, ask driver ”Do you feel tired?” Response alternatives: YES / NO If NO, ask ”Were you doing something other than driving when the alert appeared?” Follow up whether driver takes a pause a suggested When the car comes to a halt, if DAC has triggered and the driver answered "Yes“ (is tired), ask driver ” Did you take a break?” If NO, ask ” Was this because you: (1) were close to the target destination, (2) didn't understand the suggestion, (3) didn't feel tired (4) could drive the car without problem?”

FCW Use Case FCW – acceptance for false warnings When FCW triggers, ask driver ”Did you feel that the collision warning was correct?” Response alternatives: YES / NO If NO, ask ”Was the collision warning disturbing?”

Trigger conditions DAC & FCW DAC trigger: CADSWarning & 192 UD signal BAUD_DAC = CADSWarning & 192 Trigger: CHANGE_UP(BAUD_DAC, 1) FCW trigger: CADSWarning & 7 UD signal BAUD_FCW = CADSWarning & 7 Trigger: CHANGE_UP(BAUD_FCW, 1)

Joint Subjective / Objective Data Analysis First version of prototype system will have export functions for subjective data, objective data and anthropometric data Built-in analytics functions (web based) to be explored later (SODASAD or other initiatives)

Plotting answers vs. User info Answers to ”Are you tired?” when DAC alert is detected

Plotting answers vs. in-vehicle signal Answers to ”Were you doing something else when DAC triggered?” Plotted against VehicleSpeed

Privacy and integrity issues When subjective data capture is scaled up to large customer groups, privacy issues must be considered PhD thesis work ongoing Approach is to use differential privacy

Revised Framework Architecture Users Presentation layer / User interface Back-end server architecture Measurement Task design tool Survey design tool Measurement Task Manager Subjective Data Task Manager Analytics Framework Privacy preservation layer Privacy preservation layer Telematic service layer Monitoring & Triggering mechanism Smartphone App Service Layer ? ? ? Data sources