Florida ITS Performance Measures Update

1. Florida ITS Performance Measures Update presented toPerformance Measures Session FDOT ITS Working Group Meeting, Tampa, FL presented byKenny Voorhies, Cambridge Systematics March 20, 2008

2. Agenda • Incident Duration • Highlights from last ITS working group meeting • Progress report • Action items • Travel Time Reliability • Highlights from last ITS working group meeting • Progress report • Action items • Next steps

3. Incident DurationConcerns from Last Working Group Meeting • Actions of partner agencies will not be included in timeline • Time emergency vehicles arrive on the scene • Incident investigation time by FHP • FHP CAD system could be helpful for operations purposes • Initially, reporting of incident duration will likely differ among Districts • Roll out of SunGuide software • Operators in different districts interpret the incident duration timestamps differently

4. Incident Duration Action Items • Review incident duration definitions with each District and fine-tune to resolve misinterpretations • Conduct pilot test for incident duration • District 6 • Plan for consistent training of operators across Districts • Conduct QA/QC of incident duration results across Districts to identify anomalies

5. Incident DurationProgress Report • Met with D6 SunGuide Transportation Management Center - March 10/11 • Recommendations • Document current SunGuide reports • Provide validation of SunGuide reports • Conduct Statewide Workshop • Provide standard operating guidelines • Conduct operations staff training on definitions

6. Travel Time ReliabilityConcerns from Last Working Group Meeting • Connection between speed data and reliability unclear • Method of calculating reliability not clear • Concern that since districts don’t have data for roadways before the implementation of ITS, it won’t be possible to quantify the full benefits of ITS

7. Travel Time Reliability Action Items • Conduct a reliability workshop with FDOT Districts to review FDOT definitions of reliability using actual data • Pilot test for travel time reliability in one district

8. Travel Time ReliabilityProgress Report • Met with D5 on February 12 • Recommendations • Create template for developing detector configuration file • Create guidelines for detector quality and maintenance (statewide level) • Define reporting templates • Conduct training

9. Next Steps • Conduct Incident Duration Teleconference with Districts within next 4 weeks • Review timeline and definitions • Clarify expectations for this reporting cycle • Discuss concerns • Conduct Reliability Teleconference within the next 2 months • Review data and reporting • Clarify expectations for this and next reporting cycles • Discuss concerns

10. Next Steps (continued) • Central Office • Develop and implement Incident Duration Performance Measures Policy • Develop detector data quality guidelines • Develop training materials and plan • Begin compiling data for 07/08 report to FTC

11. Questions and Contact • Anita Vandervalk or Kenny Voorhies • avandervalk@camsys.com • kvoorhies@camsys.com • Cambridge Systematics2457 Care Drive, Suite 101Tallahassee, Florida 32308