Electronics of Usage Based Insurance Device Considerations Mike - PowerPoint PPT Presentation

Electronics of Usage Based Insurance “Device Considerations” Mike Carroll – VP Sales-Telematics Danlaw Inc

Agenda • Danlaw DNA – Corporate Overview p • Automotive Telematics 101 – The Basics • What data is available from the car • OBDII Device Considerations • Data Transmission • Best Practices • Automotive Telematics 201 – The Road less Travelled

Insurance Telematics Growing

Vehicle Telematics How it works: How it works: Wireless/Cell lar Wireless/Cell lar Wireless/Cellular Wireless/Cellular GPS GPS Data Center Data Center End End- -User User- -Apps Apps OBDII DataLogger or OEM OBDII DataLogger or OEM

m2m Value Chain END USERS CLIENT CLIENT SERVICES GATEWAY CARRIER DEPLOY DEVICE LOGGER H/W in in value chai value chai ing blocks ing blocks M2m M2m Build Build

Typical OBD DataLogger Accelerometer Accelerometer Internal GPS Antenna Internal GPS Antenna Internal Cellular Antenna Internal Cellular Antenna OBDII OBDII – – J1962 Connector J1962 Connector Weight: 53.8 grams/1.9 ounces Weight: 53.8 grams/1.9 ounces Weight: 53.8 grams/1.9 ounces Weight: 53.8 grams/1.9 ounces

Additional Device Features Friend or Foe? Friend or Foe?

Simple Self-Installation Step 1 Step 2 Find the OBDII Port usually located in the driver’s Find the OBDII Port usually located in the driver s Insert the DataLogger Insert the DataLogger side foot well under the steering column into the OBDII Port

OBD: 1996-Present What, Where, When, Why, How and How Many

How can a “standard” not be standard? Vehicle Protocol Support Protocol Name Speed p Used by y most Asian and European ISO 9141 10.4 Kbits/second manufacturers J1850 PWM 41.6 Kbits/second Ford, Mazda (Pulse Width Modulation) J1850 VPW (Class II) J1850 VPW (Cl II) 10.4 & 41.6 Kbits/second primarily older model GMs (Variable Pulse Width) ISO 14230 KWP2000 100 Kbits/second Older Chrysler ISO 15765 250 & 500 Kbits/second All major OEMs by 2008 CAN (Controller Area Network) Ford, GM, DCX, European & Varies by application 11bit & 29bit identifier addressing Asian OEMs GMLAN (GM), FNOS (Ford)

Common Logger Parameters Feature Example ◙ ◙ Installs via OBDII Installs via OBDII ◙ Unit ID ◙ VIN ◙ ODO* ◙ Vehicle Speed ◙ Trip Start/End ◙ Connect Event ◙ Disconnect Event ◙ GPS - LAT/LON/ALT ◙ RPM ◙ E T I Member -Par tner Throttle Position ◙ Battery Voltage ◙ Coolant Temp ◙ MIL Status Othe r OBDII and Non OBDII data c an be c olle c te d on a c ustom basis * ODO is pr ovide d as long as the ODO output is pr ovide d by the OE M

Data Transport & Firmware Updates • Cellular o GSM vs. CDMA o TCP vs. UDP o SMS o SMS • Bluetooth • Wifi Wifi • USB • FOTA vs. Fixture

Transport Certifications • FCC Certification: PTCRB • Carrier Certifications: • AT&T • Rogers • Sprint • T-Mobile • Verizon

Physical & Electrical Testing y g • Bump test occasional EN 60068 ‐ 2 ‐ 29:1993 p 9 993 • Random vibration 5Hz to 200Hz 8 Hours • Power Temperature Cycling 35 Cycles ‐ 40 to +85 • Thermal Shock EN 60068 ‐ 2 ‐ 14: 1999xii Th l Sh k EN 6 68 ii • Free fall ‐ EN 60068 ‐ 2 ‐ 32:1993xxii • EMC ‐ ESD SAE J551/15 EMC ESD SAE J551/15 • Sleep State Current Consumption • Functional Validation – As per customer requirements • Independent Customer Testing

Data Transmission Wh l Why less is more and other Heresies i d th H i • Give me ALL the data • Data Compression • Event Thresholds • Event Thresholds • Summary Reporting

Detour Ahead Where is my data? Wh i d ? • Compatible Vehicle? • Device Shipped? • Installed? Installed? • Provisioned on Cell carrier? • Pointed at correct server? • Correct firmware? • Functioning device? F ti i d i ? • Activated in Gateway? • Cell coverage? • Mapped to DB? pp • Output from Scoring Alg? • Pushed to Data Warehouse? • Insurance or Consumer Facing App working?

Vehicle M2M Challenges g Wireless: Certifications: PTCRB & FCC & Wireless Carrier Certifications Data Plans, Roaming Rules, FOTA g BlueTooth, WiFi, Zigbee, DSRC for device ‐ to ‐ device communications Vehicle Compatibility: 250 million cars, suvs & pickups on the road with over 35,000 unique Year/Make/Models 250 illi & i k th d ith 35 000 i Y /M k /M d l Hybrid Vehicles, Future Vehicles & Future Protocols (FlexRay, etc.) Truck and Heavy Duty Vehicle Protocol (1708 & 1939) D t I t Data Integrity: it GPS Data Quality, OBD Data Capture Functional/Proprietary Message Data support (ODO, VIN, etc.) Integration & Website Issues: Integration of Device Data with backend Applications IT Infrastructure, Backend & website to display the data Automotive OEM vs. Aftermarket Lifecycles 9.5 vs. 2.5 years

Just when you thought it was safe to get back in the car

Best Practices from 15 projects • Reducing Risk: Trusted Partners • Reducing Risk: Trusted Partners • Setting Expectations • Phased Rollouts

Critical Task Items • LBS services • Critical Data Elements • IT Systems Integration • Trip Report Summary • Single Sign ‐ On Strategy • Trip Definition • Trip Definition Integration Integration • Wireless Data Billing • Data Frequency • Data Format Actuary Actuary Order Order Fulfillment Fulfillment Fulfillment Fulfillment Marketing Marketing • Branding • Unit Provisioning • Enclosure Logo/Color g • SIM, VIN, Unit ID , , • Packaging • Username/Password • Website Colors/Logos/look & feel • Shipping (FEDEX, UPS…) • Opt ‐ Out Strategy & RMA

Vehicle Telematics Vertical Markets ROADSIDE LEASING/ AUTOMOTIVE TRUCK/HEAVY TRAFFIC OEM –TIER1 INSURANCE ASSIST LOANS FLEET EQUIPMENT CONTROL ENGINEERING PAYD Towing Buy ‐ Pay Here Mileage Mileage ITS Data Recording Teen Safety Diagnostics High Risk Maintenance Maintenance Road Tolling Trouble Shooting High Risk g Door Unlock Immobilizer Diagnostics g Diagnostics g Congestion Mgt g g Service Systems y Crash Detect LBS Track & Trace Dispatch Dispatch VII Track & Trace Theft Recovery Diagnostics Track & Trace Track & Trace V2V ECU FOTA E ‐ Call/E ‐ 911 Break ‐ in Detect Break in Detect Crash Detect Crash Detect Fuel Use/Econ Fuel Use/Econ Fuel Use/Econ Fuel Use/Econ Pay Go Pay ‐ Go Recovery Road Tax Service Hours Emissions Road Tax Emissions

The Road less Traveled • One port ≠ One application O t ≠ O li ti • Who else wants to take a byte out of your data? y y

Questions? • Mike Carroll • Mike Carroll • mikec@danlawinc.com • 248 ‐ 705 ‐ 5732 • Thanks for your time • Thanks for your time….. From your friends at Danlaw