TAMING BIG DATA FOR SMARTER FUTURE

Transcription

1 2015 APA National Planning Conference Function Code: S585 TAMING BIG DATA FOR SMARTER FUTURE Ed Hutchinson

2 OVERVIEW 1. Enterprise Information Management (EIM) 2. Data Clearing House 3. Florida Transportation Data Symposium

3 ENTERPRISE INFORMATION MANAGEMENT Enterprise view of maintaining and managing all areas related to management of the Department s data. Information Technology Strategic Initiatives Enterprise Information Technology Governance Enterprise Information Management Uniform Information Technology Standards

4 ENTERPRISE INFORMATION TECHNOLOGY GOVERNANCE The purpose of the Data Governance Document is to document FDOT s approach to governing how data will be stored, shared and protected within the organization.

5 DATA CLEARINGHOUSE Data Sources Data Users 26 MPOs 14 Seaports Private Sector FDOT Modal Offices 7 FDOT Districts

6 DATA CLEARINGHOUSE Data Sources Data Users 27 MPOs 14 Seaports Private Sector 7 FDOT Districts

7 DATA CLEARINGHOUSE Data Sources The addition of added Value Bottleneck Study Data Users 27 MPOs 14 Seaports Private Sector 7 FDOT Districts

8 DATA CLEARINGHOUSE

9 FLORIDA TRANSPORTATION DATA SYMPOSIUM!!!!! Save the Date August 18-20th 2015 Omni Orlando Resort at Champions Gate Contact Promotion Website:

10 CONTACT Ed Hutchinson FDOT

11 2015 APA National Planning Conference Function Code: S585 TAMING BIG DATA FOR SMARTER FUTURE Ed Hutchinson

12 OVERVIEW!Enterprise Information Management (EIM)!Data Clearing House!Florida Transportation Data Symposium

13 ENTERPRISE INFORMATION MANAGEMENT!Enterprise view of maintaining and managing all areas related to management of the Department s data.!information Technology Strategic Initiatives "Enterprise Information Technology Governance "Enterprise Information Management "Uniform Information Technology Standards

14 ENTERPRISE INFORMATION TECHNOLOGY GOVERNANCE The purpose of the Data Governance Document is to document FDOT s approach to governing how data will be stored, shared and protected within the organization.

15 DATA CLEARINGHOUSE Data Sources Data Users 26 MPOs 14 Seaports Private Sector FDOT Modal Offices 7 FDOT Districts

16 DATA CLEARINGHOUSE Data Sources Data Users 27 MPOs 14 Seaports Private Sector 7 FDOT Districts

17 DATA CLEARINGHOUSE Data Sources The addition of added Value Data Users 27 MPOs Bottleneck Study 14 Seaports Private Sector 7 FDOT Districts

18 FLORIDA TRANSPORTATION DATA SYMPOSIUM! Save the Date August 18-20th 2015! Omni Orlando Resort at Champions Gate Contact Promotion Website:

19 CONTACT Ed Hutchinson FDOT

20 USING DATA TO IMPROVE SAFETY Krishnan Viswanathan, CDM Smith

21 AGENDA Purpose Technology Study Design User Interface Data Processing Results Summary and Next Steps

22 PURPOSE Study Level 0 Automation Evaluate impacts of Advanced Driver Assistance System (ADAS) Measure changes in driver behavior in face of driver feedback technology Measure performance improvements as a result of feedback

23 TECHNOLOGY - GEOTAB Provides vehicle diagnostics information Real time data on vehicle exceptions and performance Data transmitted via cellular signals Dashboard to visualize data

24 TECHNOLOGY - MOBILEYE Daylight Pedestrian Collision Warning, including Bicycle Detection Forward Collision Warning, both in Highway and Urban areas, including Motorcycle Detection Lane Departure Warning Headway Monitoring and Warning

25 STUDY DESIGN Instrument 100 vehicles in Florida DOT District 7 Vehicles from Florida DOT and local transit agencies 100 vehicles have GeoTab devices 50 vehicles have Mobileye devices Study duration is 1 year Installs completed in August Data collection underway

26 USER INTERFACE

27 USER INTERFACE

28 USER INTERFACE

29 DATA PROCESSING Daily stream of data! Mobileye exceptions! Geotab exceptions Data arrives with lat/long information, time of day, and vehicle id for each type of Mobileye or Geotab exception Data converted into R data.table for processing and analysis ArcGIS used to spatially locate data

30 RESULTS ODOMETER READINGS Sep 2014 Oct 2014 Nov 2014 Dec 2014 Jan 2015 Feb 2015 Mar 2015 Min Max 18,001 21,382 22,440 19,634 23,968 13,820 12,838 Median 3,896 4,049 3,189 3,216 3,388 3,203 2,765 Mean 4,461 4,812 4,301 4,301 4,414 4,274 3,863

31 RESULTS MONTHLY MILEAGE BY VEHICLE Sep 2014 Oct 2014 Nov 2014 Dec 2014 Jan 2015 Feb 2015 Mar

32 RESULTS DISTANCE, SPEED, TRIP DURATION

33 RESULTS MOBILEYE EXCEPTIONS Type of Warning Mobileye Events (September 2014) Mobileye Events (October 2014) Mobileye Events (November 2014) Mobileye Events (December 2014) Mobileye Events (January 2015) Mobileye Events Mobileye Events (February 2015) (March 2015) # % # % # % # % # % # % # % ME Forward Collision Warning 1, % 1, % % % % % % ME Headway Warning (Tailgating) 69, % 65, % 8, % 7, % 11, % 10, % 8, % ME Left Lane Departure 14, % 10, % 1, % 2, % 2, % 2, % 1, % ME Pedestrian Collision Warning % % % % % % % ME Right Lane Departure 29, % 21, % 7, % 7, % 9, % 8, % 7,728 42/0% ME Urban Forward Collision Warning 2, % % % % % % % Total 117, % 100, % 18, % 17, % 24, % 21, % 18, %

34 RESULTS MOBILEYE EVENTS BY VEHICLE TYPE 90.0% 80.0% 70.0% 60.0% 50.0% 40.0% 30.0% 20.0% 10.0% 0.0% Car Large Bus Pickup Small Bus Truck Van ME Forward Collision Warning ME Headway Warning (Tailgating) ME Left Lane Departure ME Right Lane Departure ME Pedestrian Collision Warning ME Urban Forward Collision Warning

35 RESULTS GEOTAB EXCEPTIONS Sep-14 Oct-14 Nov-14 Dec-14 Jan-15 Feb-15 Mar-15 Speeding 19,380 23,176 17,707 16,966 16,846 14,448 16,517 Hard Acceleration 1,423 1, ,199 1,042 1,166 1,120 Harsh Cornering Harsh Braking Total 21,479 25,512 19,440 19,164 18,873 16,412 18,737

36 RESULTS COMPARISONS OF VEHICLES WITH AND WITHOUT MOBILEYE Anchor Towing FDOT D7 Car Oct 2014 Nov 2014 Dec 2014 Jan 2015 Feb 2015 Mar Oct 2014 Nov 2014 Dec 2014 Jan 2015 Feb 2015 Mar 2015 Anchor Towing, Administrative, Pickup - Standard Anchor Towing, Administrative, Pickup - Standard, Mobileye FDOT District 7, Administrative, Car FDOT District 7, Administrative, Car, Mobileye HART Large Bus HART Small Bus Oct 2014 Nov 2014 Dec 2014 Jan 2015 Feb 2015 Mar Oct 2014 Nov 2014 Dec 2014 Jan 2015 Feb 2015 Mar 2015 HART, Administrative, Bus - Large, HART Maintenance, HART Safety HART, Administrative, Bus - Small, HART Maintenance, HART Safety HART, Administrative, Bus - Large, HART Maintenance, HART Safety, Mobileye HART, Administrative, Bus - Small, HART Maintenance, HART Safety, Mobileye

37 RESULTS TOTAL MOBILEYE EXCEPTIONS DENSITIES

38 RESULTS FORWARD COLLISION EXCEPTIONS DENSITIES

39 SUMMARY AND NEXT STEPS Noticeable change in driver behavior by number of incidents! Reduced number of incidents However, don t notice in statistically significant changes in the vehicles with and without Mobileye Critical to know context of operations Develop performance measures to quantify change due to these devices

40 CONTACT Krishnan Viswanathan CDM Smith

41 SIS BOTTLENECK STUDY Chris Edmonston, AICP and Praveen Pasumarthy, P.E., PTOE

42 INTRODUCTION! Background! Study Purpose! Scope of Study! Study Findings! Next Steps

43 BACKGROUND! Strategic Intermodal System (SIS) was created in 2003! Designate facilities and services of statewide significance! Serve the mobility needs of citizens, businesses, and visitors! Help Florida to " become a worldwide economic leader, " enhance economic prosperity and competitiveness, " enrich quality of life, and " reflect responsible environmental stewardship.

44 BACKGROUND

45 STUDY PURPOSE! Identify bottlenecks on Strategic Intermodal System (SIS)! Use the data available with FDOT! Identify bottlenecks at statewide and district level! Present the results in easy to understand format

46 SCOPE OF THE STUDY! Activity 1: Data review " Data available with FDOT " Vehicle probe data! Activity 2: Methodology to identify bottlenecks " Research efforts in the field of congestion and bottlenecks " Contemporary practices by DOTs, MPOs, etc. " Develop the methodology! Activity 3: Identify bottlenecks " Analyze the data " Prepare maps/graphics

47 DATA SOURCES! Existing FDOT Data Sources " Roadway Characteristics Inventory (RCI) " Traffic Monitoring Program # Telemetered Traffic Monitoring Sites (TTMSs) # Portable Traffic Monitoring Sites (PTMSs)! Vehicle Probe Data " INRIX s Vehicle Probe Data Phase I " FHWA s NPMRDS from HERE Phase II

48 VEHICLE PROBE DATA! Data sources " Traffic sensors # Induction loop sensors # Radar sensors # Toll tag readers " Probe Vehicles! Data is normalized to account for major events, weather conditions, etc.! Data provided in CSV format! Speed data obtained at 5-min intervals! 64 million records (auto); 17 million records (freight)

49 FHWA S NPMRDS ON NHS

50 FHWA S NPMRDS ON SIS

51 COVERAGE OF FHWA S NPMRDS

52 COVERAGE OF FHWA S NPMRDS Passenger Data Freight Data

53 COVERAGE OF FHWA S NPMRDS Hourly Daily Monthly Observations (in millions) 3 2 Observations (in millions) 8 6 Observations (in millions) AM 4 AM 8 AM 12 PM 4 PM 8 PM 0 Mon Tue Wed Thu Fri Sat Sun 0 Jul Aug Sept Oct Nov Dec

54 COVERAGE OF FHWA S NPMRDS Hourly Daily Monthly Passenger Observations (in millions) Observations (in millions) Observations (in millions) AM 4 AM 8 AM 12 PM 4 PM 8 PM 0 Mon Tue Wed Thu Fri Sat Sun 0 Jul Aug Sept Oct Nov Dec Freight Observations (in millions) Observations (in millions) Observations (in millions) AM 4 AM 8 AM 12 PM 4 PM 8 PM 0 Mon Tue Wed Thu Fri Sat Sun 0 Jul Aug Sept Oct Nov Dec

55 METHODOLOGY TO IDENTIFY BOTTLENECKS! Summary of research efforts in the field of congestion and bottlenecks! Contemporary practices " National performance reports " State DOT practices " MPO/Local government practices! Recommended methodology to identify bottlenecks on SIS network

56 CONGESTION! FHWA defines congestion as an excess of vehicles on a roadway at a particular time resulting in speeds that are slower - sometimes much slower - than normal or free flow speeds Poor Signal Timing, 5% Bad Weather, 15% Special Events, 5% Bo#lenecks, 40%! Recurring and non-recurring congestion Work Zones, 10% Traffic Incidents, 25%

57 BOTTLENECK! Bottleneck can be defined as a localized section of highway that experiences reduced speeds and inherent delays due to a recurring operational influence or a nonrecurring impacting event! Recurring and non-recurring bottlenecks! Bottleneck occurs on a subordinate segment of a facility! Bottleneck certainly constitutes congestion, but congestion is often more than a bottleneck

58 BOTTLENECK

59 CONTEMPORARY PRACTICES! National Performance Reports " Urban Congestion Report by FHWA " Urban Mobility Report by Texas Transportation Institute " National Traffic Scorecard by INRIX! State DOT Practices " Florida DOT " California DOT " Washington State DOT! MPO/Local Government " Metroplan Orlando " North Florida TPO " Georgia Regional Transportation Authority

60 RECOMMENDED METHODOLOGY STEP 1: Determine the purpose STEP 2: Develop a plan based on the uses and users STEP 3: Collect and process required data STEP 4: Calculate performance measures and identify bottleneck & congestion STEP 5: Communicate in a meaningful way

61 RECOMMENDED METHODOLOGY STEP 1: Determine the purpose STEP 2: Develop a plan based on the uses and users STEP 3: Collect and process required data! Primary purpose would be for planning purposes! Bottlenecks should be identified using maps! Resulting product should be easy to understand and interesting to read STEP 4: Calculate performance measures and identify bottleneck & congestion STEP 5: Communicate in a meaningful way

62 RECOMMENDED METHODOLOGY STEP 1: Determine the purpose STEP 2: Develop a plan based on the uses and users STEP 3: Collect and process required data STEP 4: Calculate performance measures and identify bottleneck & congestion! Bottlenecks identified for auto and truck mode! Bottlenecks identified based on weekday travel patterns! Travel time reliability measures are used! Yearly trends will be reported! Statewide and district-level measures will be reported STEP 5: Communicate in a meaningful way

63 RECOMMENDED METHODOLOGY STEP 1: Determine the purpose STEP 2: Develop a plan based on the uses and users! Vehicle probe data from FHWA will be used! FDOT data will be used for mapping purposes STEP 3: Collect and process required data STEP 4: Calculate performance measures and identify bottleneck & congestion STEP 5: Communicate in a meaningful way

64 RECOMMENDED METHODOLOGY STEP 1: Determine the purpose STEP 2: Develop a plan based on the uses and users! Process FHWA NPMRDS data! Identify performance measures! Define and identify bottlenecks STEP 3: Collect and process required data STEP 4: Calculate performance measures and identify bottleneck & congestion STEP 5: Communicate in a meaningful way

65 RECOMMENDED METHODOLOGY STEP 1: Determine the purpose STEP 2: Develop a plan based on the uses and users STEP 3: Collect and process required data! Display results in easy-to-understand tables and graphics! Present the yearly trends! Present results statewide and by district STEP 4: Calculate performance measures and identify bottleneck & congestion STEP 5: Communicate in a meaningful way

66 QUANTIFY CONGESTION/BOTTLENECK! NCHRP Report 398: Quantifying Congestion (1997)! Presented methods to measure congestion! Difficult to conceive of a single value to describe congestion! Four components in a congested roadway system " Duration amount of time congestion affects the travel system " Extent number of people or vehicles or geographic area affected by congestion " Intensity severity of the congestion " Reliability variation in the other three elements

67 QUANTIFY CONGESTION/BOTTLENECK Phase I Methodology Phase II Methodology Duration: Extent: Duration: Extent: Frequency of Congestion None Frequency of Congestion Vehicle Miles Traveled Intensity: Reliability: Intensity: Reliability: None Planning Time Index Vehicle Hours of Delay Planning Time Index

68 STATISTICAL VALIDATION! Statistical validation of measures is essential! Margin of error " Expresses amount of random sampling error in results " High Margin of error = Low confidence in results " Segments with margin of error greater than 10% are eliminated

69 STATEWIDE SIS BOTTLENECKS

70 NEXT STEPS! Phase II of the study is underway to identify the causes of top bottlenecks and suggest corrective actions! Incorporate the bottlenecks in FDOT s Strategic Investment Tool! Update the list of top bottlenecks every two years! Update methodology using advancements in and coverage of vehicle probe data