Safety Pilot Model Deployment Status Update - DRIVE C2X

Safety PilotModel DeploymentStatus UpdateDrive C2X @ TSS, GothenburgJune 13 2013Kate Hartman, Acting Team Lead – ResearchITS JPO

TODAY’S PRESENTATIONOverview• Background• Model DeploymentAccomplishments• Lessons Learned duringModel Deployment2

BACKGROUND3

SAFETY PILOT OBJECTIVES• Obtain user acceptance data• Derive safety system effectiveness values for supporting 2013and 2014 NHTSA agency decisions• Understand how the system operates in a real world, highlyconcentrated environment• Understand the potential role that aftermarket devices mightplay in accelerating benefits• Archive data for future government and industry use4

NHTSA AGENCY DECISIONS ON CONNECTEDVEHICLE TECHNOLOGY• Decision Schedules– CY2013: Light Vehicles– CY2014: Heavy Vehicles• Potential Outcomes of Decisions– Mandatory deployment oftechnology (FMVSS)– Voluntary installation of wirelessdevices (NCAP)– Additional research anddevelopment5

• 73 miles of instrumented roadway with27 roadside units in Ann Arbor, MI• Over 2,800 vehicles equipped with avariety of device types• Various V2V and V2I applications• Testing of prototype securitymechanisms and device certificationprocessesWHAT IS SAFETY PILOT?A major road test and real world implementation involving:• 1 year of data collection to support 2013NHTSA decision6

MODEL DEPLOYMENT: LIGHT VEHICLES• 64 - Fully Integrated Light Vehicles− Safety system installed by the manufacturer, integrated directly with thevehicle’s CAN-bus− Driven by 128 recruited volunteers, divided into two 6 month phases• Safety applications for ILVs vary by manufacturer - includes EEBL, FCW,IMA, LTA, BSW/LCW, and DNPW7

MODEL DEPLOYMENT: LIGHT VEHICLES• 300 – Light Vehicles with AftermarketSafety Devices (ASDs)− 200 ASD only, 100 ASD with DAS− Safety Applications: EEBL, FCW, CSW• 2,200 - LVs with Vehicle AwarenessDevices (VADs)− Provides basic functionality only, transmitsspeed and location− Does not generate warnings8

MODEL DEPLOYMENT: COMMERCIAL VEHICLES• 3 Integrated Freightliner CascadiaTrucks – driven by participatingfleets– Rightaway Delivery, LLC– 4H• 16 - Retrofit Safety Device (RSD)on existing fleet vehicles− Sysco (8) Battelle RSD− Conway (8) Cambridge RSD• 150 - CVs with Vehicle AwarenessDevices• Safety Applications: EEBL, FCW,IMA, BSW/LCW, CSW9

MODEL DEPLOYMENT: TRANSIT VEHICLES• Three UM (3) buses equipped withretrofit devices (TRP)• 61 drivers• 100 transit buses with VADs• Safety Applications for Transit• FCW, EEBL, CSW• Pedestrian in Signalized CrosswalkWarning• Vehicle Turning Right in Front of BusWarning10

MODEL DEPLOYMENTACCOMPLISHMENTS11

INTEROPERABILITY ACHIEVED• 3 Stages of Testing Completed– Including bench and field testing• 8 Vehicle manufacturers (CAMP)• Multiple vendors included– Savari– Cohda— Denso— Arada• Multiple vehicle platforms– Light, heavy, and transit vehiclesInteroperability has been achieved across all devices and vehicles participating inthe Safety Pilot Model Deployment!12

• 2,430 VADs• 281 ASDsVEHICLES & DEVICES DEPLOYED• 64 Integrated Light Vehicles• 19 Integrated / Retrofit HeavyVehicles• 3 Retrofit Transit Vehicles• 24 RSEsOver 98% of the vehicle fleet has been deployed and is operating in the ModelDeployment!13

Cumulative Interactions (30m)INTERACTIONS GENERATED70.00060.00050.00040.000Interaction TargetsObserved Interactions37.486Phase II30.00020.00010.000-Phase I28.70423.70016.0309.4103.7969901 2 3 4 5 6 7 8 9 10 11 12MonthsWithin 10% of the projected number of interactions by Month 6. Will meetinteraction targets by completion of Model Deployment.14

DATA COLLECTED Data collected to date• Integrated Light Vehicles – monthly DAS downloadsthrough May• VADs - 1,918 log downloads• Light Vehicle ASDs - 195 log downloads• Heavy Vehicles – monthly downloads through May Data transferred to Independent Evaluatorfor analysis Data will be transferred to Real-Time DataCapture Program for research and archivingCollected data from multiple sources for the first 6 months of Model Deployment.Preliminary analysis on effectiveness of safety systems has started.15

MODEL DEPLOYMENTLESSONS LEARNED16

PROGRAM MANAGEMENT APPROACHUtilize a modular program structure that separatesthe implementation of critical components from noncriticalcomponents.Examples from Safety Pilot• Supported on-time deployment of integrated light vehicles in August2012 to provide data for 2013 NHTSA decision• Vehicles and devices not critical to 2013 NHTSA decision (ASDs, Trucks,Transit) were deployed after Model Deployment launch• Critical components of the program did not have their schedulesimpacted by the schedules of non-critical components17

APPROACH TO COORDINATIONDevelop and execute a comprehensive coordination management plan;over-communicate to project partners.Examples from Safety Pilot• Over 10 contractors and partners had to worktogether to make Safety Pilot successful• Monthly working meetings were held at UMTRIwith all project partners (sometimes in garages)• Weekly conference calls were held for specifictopics (security, outreach, data, project mgmt)18

APPROACH TO DEVICE MANAGEMENTComprehensive property and configurationmanagement systems are critical to support detailedanalysis of safety applications.Examples from Safety Pilot• Encountered challenges utilizing the property and configurationmanagement systems to support the safety application analysis.• For example, GPS and DSRC antenna placement and softwareconfiguration parameters had a significant impact on safety applicationperformance.• Additional software tools had to be developed to allow the data fromthese systems to be usable in the analysis of the safety applicationperformance.19

APPROACH TO DRIVER RECRUITMENTCommunity engagement is an important part of asuccessful subject recruitment strategy.Examples from Safety Pilot• Recruited parents of students in the Ann Arborpublic school system• Allowed participants to donate participantcompensation to their child’s school• This worked well for the integrated light vehicles• Recruitment for trucks and buses was a challengedue to a number of factors20

DEVICE TESTING APPROACHAllow for additional time for end-to-end system testing, including multiplerounds of testing and a comprehensive dry-run prior to launch.Examples from Safety Pilot• Multiple rounds of Vehicle AwarenessDevice Certification testing• 3 rounds of device interoperability testing• Additional time was needed for dry runtesting prior to launch• Devices were brought to a stable state butonly after deployment launch21

APPROACH TO DATA COLLECTIONIdentify data needs early and verify the data processes prior to the startof data collection.Examples from Safety Pilot• Challenge to combine data from variousdevices into a consistent format for dataevaluation• Data requirements did not describe theintended use of data, led to somemisunderstanding of data needs• Required frequent communicationbetween data generator and data recipientto detect issues in a timely mannerVirginiaTech/CAMPSouthwestResearchModelDeploymentDatabaseU of MBattelle22

QUESTIONS AND INFORMATIONKate HartmanITS JPOkate.hartman@dot.gov202-366-274223