clay packard, pe its gc software project manager florida department of transportation waze – fdot...
TRANSCRIPT
Clay Packard, PE
ITS GC Software Project Manager
Florida Department of Transportation
WAZE – FDOT Integration
Waze – FDOT Integration 2
Objectives
Obtain incident data on Florida’s State arterial roadways– Deployments on most limited-access highways
Provide data to a third party to reach more motorists
11/12/2015
Waze – FDOT Integration 3
Agreement
Data sharing agreement effective 3/28/2014
Requires attribution by both parties
11/12/2015
FDOT to Waze Data Sharing
District Public Information Office
• Provides Planned Road / Lane Closures
FDOT Regional Transportation Management Centers (TMC)
• TMC receives planned closures
• TMC Operators produce incident data
• Intelligent transportation systems (ITS) detectors produce traffic conditions data
FL511 System’s Third Party Data Feed
• Collects data from TMCs statewide
• Packages data as single data feed
Waze
• Receives FDOT Data
• Provides Crowd-Sourced Data
11/12/2015 Waze – FDOT Integration 4
FDOT Third-Party Data Feed
Provides statewide real-time data – Sent by TMCs to FL511
Feed updated every one minute Date types Include:
– Floodgates– Traffic events– Camera images– Dynamic message sign messages– Traffic speed– Travel times
11/12/2015 Waze – FDOT Integration 5
Waze – FDOT Integration 6
SunGuide® Software
FDOT’s statewide advanced traffic management system (ATMS) software– Integrates ITS devices and TMC operations– Incident Management
Waze data integrated into SunGuide software Two phases:
– Quick integration (phase 1)– Long-term integration (phase 2)
11/12/2015
Waze – FDOT Integration 7
Waze Data Feed
Waze data contain incidents and traffic jams– Crashes, disabled vehicle, debris on roadway, etc.– We do NOT receive speeds from Waze
FDOT retrieves data and stores in a database Distributed to Transportation Management
Centers (TMC) Some data filtered out:
• Police locations• Weather conditions • Other / chit-chat• Miscellaneous
11/12/2015
Waze – FDOT Integration 8
Decisions – Data Distribution
11/12/2015
Other filtering decisions– Decentralized with
seven Districts and a Turnpike Enterprise.
– Districts do not need statewide data
– Districts monitor the state roadway system
Phase 1 Integration – Map Icon
11/12/2015 Waze – FDOT Integration 9
10
SunGuide Integration
Phase 2 Goals: Operate efficiently for TMC operators Behave consistently with other incident detection
and data sources Automate transfer of information from Waze to
SunGuide alerts/events
11/12/2015 Waze – FDOT Integration
SunGuide Integration - Diagram
11/12/2015 Waze – FDOT Integration 11
12
Receiving Alerts – Mockup
Alerts received within the SunGuide software
Consistent among all Incident Detection sources
Operator clicks alert to begin the information transfer to SunGuide and response process
11/12/2015 Waze – FDOT Integration
Alert Handling – GUI Screen
11/12/2015 Waze – FDOT Integration 13
Event Management – GUI Screen
11/12/2015 Waze – FDOT Integration 14
Event Management – GUI Screen
11/12/2015 Waze – FDOT Integration 15
16
Performance Measures
Events detected by Waze first Events detected by TMC or other sources first Events not detected by Waze False alarms, and confidence level correlation Event clearance/closure notification
11/12/2015 Waze – FDOT Integration
17
Dissemination Policies
Instrumented state roads: – Confirm Waze event prior to posting to Florida’s 511
(FL511) system Non-instrumented state roads covered by FL511
system:– Post Waze event as unconfirmed
Non-instrumented state roads not covered by FL511 system: – Post “floodgate” message for road closures
11/12/2015 Waze – FDOT Integration
Fred Heery, PETSM&O Program [email protected]
Mark Wilson, PEState Traffic Operations [email protected]
Derek Vollmer, PEITS Software and Architecture [email protected]
Clay Packard, PE
ITS GC Software Project Manager
QUESTIONS?