Statewide Transportation Management Center Software Library System (SunGuide SM ) TIM & SunGuide SM Coordination Meeting October 21, 2004 Orlando, Florida Liang Y, Hsia, P.E. State Traffic Engineering & Operations Office Florida Department of Transportation

2 Goals and Objectives FDOT Goals –Improve transportation safety. –Reduce congestion and delays. –Acquire (own) the most technically comprehensive ITS software. –Establish a software standard at TMCs throughout the State of Florida. –Reduce multiple TMC software development, maintenance, and update costs. SunGuide software goals: –Flexible and expandable to match individual TMC needs. –Respond to traffic incidents in a rapid, accurate, and effective manner.

3 Release-Oriented Development Approach

4 T M C Software ATMS07 - Regional Traffic Control

5 Advanced Transportation Management Systems (ATMS) ATMS04 - Freeway Control FDOT District 3 – Tallahassee (Planned)

6 Road Rangers EM4 - Roadway Service Patrols

7 Emergency Management EM1 - Emergency Response Emergency Management Agencies

8 Emergency Management EM1 - Emergency Response EOC Emergency Status Monitoring

9 511 ATIS1 – Broadcast Traveler Information 511 Traveler information telephone service

10 Operation & Maintenance MC01-Maintenance and Construction Vehicle Tracking

11 ITS Data Warehouse AD2 ITS Data Warehouse

12 SunGuide SM Software Deployment SunGuide SM Software Deployment Center-To-Center Communications TxDOT Extensible Markup Language (XML) Simple Object Access Protocol (SOAP)

13 Center-to-Center (C2C) Communications

14 SunGuide SM Software Project NTCIP 1203 Dynamic Message Signs

15 SunGuide SM Software Project NTCIP 1204 Environmental System Sensors (RWIS on FDOT Tallahassee Microwave Tower)

16 SunGuide SM Software Project NTCIP 1205 Closed-Circuit Television Control

17 SunGuide SM Software Project NTCIP 1207 Ramp Meter Control

18 SunGuide SM Software Project NTCIP 1208 Video Switches

19 SunGuide SM Software Project NTCIP 1209 Transportation System Sensor

20 SunGuide SM Software Project NTCIP Translator FDOT uses NTCIP translator devices for non-NTCIP DMS and CCTV to save device driver software development costs

21 Status of Release 1 Activities Project Management: –PM / Meetings / Reviews –Process documents –Interface Control Documents (ICDs) Core software framework: –Database –User administration –Executive handler –Status logger –User interface –Map –Data Bus DMS: –General Subsystem –NTCIP Florida MIB driver –Mark IV version 2.5 driver CCTV Control: –General Subsystem –NTCIP 1205 driver Video Switching –General Subsystem –IP Video switching driver Video Wall –General Subsystem –Barco/Argus video wall driver Traffic Detection, driver for: –General Subsystem –Bitrans B238-I4 driver –RTMS (EIS and Wavetronix) driver Incident Management: –GUI –Subsystem

22 Status of Release 2 Activities Ramp Metering: –Design activities initiated –Initial GUI design completed –High level design completed Emergency Evacuation: –Requirements refined and provided to FDOT –Design initiated Data Archive –Requirements refined –Design initiated Web Server –Requirements refined –Design initiated HAR –Requirements refined –Design initiated Center-to-Center –Requirements refined –Design initiated RWIS –Requirements refined –Design initiated Inventory and Maintenance –Requirements to be refined Optional Service: –iFlorida Data Collection Process (DCP)

23 License Discussion / Software Baseline

24 License Updates SwRI / FDOT Sublicense –License executed before the contract started. –TxDOT informed SwRI on January 22, 2004 that TransGuide software was on “hold”. –License amended on April 12, 2004 (to support District 2 and name change) For a FDOT / TxDOT partnership to occur two things are needed: –MOU: FDOT provided TxDOT with comments and legal opinion on March 2, 2004 –TxDOT Software License (solves TransGuide license issue) TxDOT provided FDOT with a license on June 30, 2004 (included previous FDOT requests for content). FDOT signed license on August 10, Waiting for signatures by TxDOT – TxDOT acknowledged the receiving of the FDOT signed license on August 23, 2004.

25 License Updates - continued FDOT / WSDOT Term of Use (TOU): –WSDOT provided FDOT with standard TOU on February 11, –FDOT provided recommendation on to WSDOT on March 13, –FDOT provided comments to the WSDOT’s Office of General Counsel’s August 21, –WSDOT began working on FDOT’s comments on August 26, FDOT / MDX Joint Program Agreement (JPA) –FDOT provided MDX with preliminary JPA on December 3, –MDX provided FDOT with draft final JPA on June 23, –FDOT worked on Locally Funded Agreement and MDX JPA.

26 License Updates - continued SwRI / FDOT / Lee County Sublicense –Lee County provided FDOT with official letter for participation on July 27, 2004 –FDOT and SwRI started documentation preparation on July 30, 2004 –SwRI provided FDOT with draft language on September 10, 2004 FDOT issued iFlorida Data Collection Process (DCP) notice to proceed on September 8, GDT License: System Planning Office and Office of Information Systems are finalizing the license agreement on September 14, 2004.

27 Software Baseline Information: Significant Reuse Of Existing Software Legend: E- Existing M – Modified N - New

28 Software Baseline Information: Ownership

29 Budget / Work Plan

30 Release-Oriented Development Approach Release 1 Release 2a Release 2b not in scope

31 Budget for SunGuide SM Effort: Release 1 Source: SwRI BAFO Budget Amount: $3,208,052

32 Budget for SunGuide SM Effort: Release 2a Source: SwRI BAFO Budget Amount: $2,074,276

33 Budget for SunGuide SM Effort: Release 2b Source: SwRI BAFO Budget Amount: $245,311

34 Budget for SunGuide SM Effort: Deployment and Support Source: SwRI BAFO

35 SunGuide SM Budget in Ten-Year ITS Cost Feasible Plan (Programmed Dollars in Millions) Funding Source FY FY FY FY06-07 FY STMCSLS* District (Ramp Metering) 3. MDX

36 SunGuide SM Budget in Ten-Year ITS Cost Feasible Plan (Programmed Dollars in Millions) Funding Source FY FY FY FY STMCSLS* District 6 (Ramp Metering) 3. MDX *Note: Total $8.09 Million

37 SunGuide SM Software and TIM SunGuide SM Software and TIM TIM Applications

38 Scan Traffic Conditions Map Colors Indicate Traffic Conditions –Mouse over Roadway for Details –Select Closest Camera –Drag Camera to Display on Monitor –PTZ Camera to Examine Traffic Conditions Check DMS Messages –Congestion Warning

39 Traffic Conditions

40 Incident Management Auto-Detected –Alarm Raised by TSS –Confirmed by Operator –Review, Complete, Modify & Execute Plan Manual (911 / 511) –Enter Incident Management Data –Review, Complete, Modify & Execute Plan

41 SunGuide Software and TIM SunGuide SM Software and TIM AMBER Alert Handling

42 Amber Alert Handling Pre-planning –DMS Standard Groups –Standard Message Templates (license plate, make, model, color, etc.) –Notification Information Deployment –Compose Message –Set Time Limit –Display Message –Check DMS Status

43 Amber Alert DMS Group Selection

44 DMS Control

45 SunGuide Software and TIM SunGuide SM Software and TIM Special Events

46 Special Event Pre-plan Messages for DMS –Ingress to ALLTEL Stadium –Egress from ALLTEL Stadium –Alternate Plans Deploy Messages with Duration Event Management –Check Traffic Conditions –Check Message Deployment –Adjust Traffic Diversion Messages

47 SunGuide SM Software and TIM SunGuide SM Software and TIM Emergency Evacuation

48 Emergency Evacuation Web based information tool: –Evacuation Guidance –Evacuation Travel Information –Evacuation Traffic Management –Evacuation Planning Support –Resource Sharing –Shelter Location & Available Spacing (Future Feature) Combine with the SunGuide software to provide evacuation services

49 SunGuide SM Software Deployment SunGuide SM Software Deployment Transportation Management Centers Applications and Deployments

50 District 4 Broward County RTMC

51 District 4 Broward County RTMC

52 District 4 Schedule September 2004 District 4 moves equipment to new TMC October 12, 2004 SunGuide SM Software Team performs Milestone Demonstration December 2004 SunGuide SM Software Team provides TMC operators with software training January 2005SunGuide SM Software Team sets up the District 4 software

53 District 4 Schedule December 2004 I95/I595 Video Monitoring Project Starts. January 2005 District 4 TMC Grand Opening. January 2005 Complete I 95/I 595 Video Monitoring and Detector System

54 District 4 Milestone Demonstration

55 District 4 Milestone Demonstration

56 District 6 RTMC

57 District 6 Schedule June 25, 2004New TMC Grand Opening July 2005I-95 Package B project completion April 2005Ramp metering subsystem to be installed and tested June 2005SunGuide SM Software Release 2 deployment includes Ramp metering system

58 Miami-Dade Expressway (MDX) Authority

59 MDX Schedule April 7, 2003MDX sent letter to ITS Office about participating in SunGuide SM Project April 25, 2003FDOT Responded, Welcoming MDX’s participation December 3, 2003FDOT provided MDX with a draft Joint Program Agreement June 2005 SunGuide SM Software Release 2 deployment at MDX October 2005 MDX TMC Operational

60 District 7 RTMC November 2005Building Construction Finish SunGuide April 2006SunGuide SM Software Deployment

61 District 2 RTMC FY 2004I-95 N ITS Improvement FY 2006SunGuide Deployment (Tentative) FY 2004I-95 N ITS Improvement FY 2006SunGuide SM Deployment (Tentative)

62 District 5 RTMC FY 2004Orlando RTMC retrofit and upgrade FY iFlorida C2C between Districts 2 and 5

63 Turnpike RTMC

64 Turnpike Schedule March 2004SunNav 1.1 Test April 2004SunNav 1.2 Development September 2005 Observation of D 4, D 6, MDX C2C Deployment

65 District 1 December 2006 SunGuide Deployment at Ft. Myers RTMC FY 2011 (2005) Sarasota RTMC December 2006 SunGuide SM Deployment at Ft. Myers RTMC FY 2011 (2005) Sarasota RTMC

66 District 3 FY 2007 Pensacola RTMC FY 2008 Tallahassee RTMC

67 Broward County Lee County Bridge Incident Management July 27, 2004 Lee County Public Works will apply SunGuide Software

68 C2C Schedule February 16, 2004SunGuide SM and C2C Project Team completed Interface Control Document (ICD) February 20, 2004SunGuide SM and C2C Project Coordination Teleconference March 9, 2004SunGuide SM & C2C Project Coordination Meeting June, 2005C2C deployment among Districts 4, 6, and MDX

69 Schedule Summary SunGuide SM Software Development Team: –Notice to Proceed: October 7, 2003 –Release 1:September 2004, or 5.75 months after May 6, 2004, Notice To Proceed for Engineering Change Order No. 2 –Release 2:June 2005 –Three Milestone Demonstrations Demo 1:October 12, 2004 at District 4 Demo 2:March 2005 at District 6 Demo 3:To be determined at District 7

70 TIM Requirements Statewide Summary Report for performance measurement Change management New requirements District TIM & SunGuide SM coordination

71 Project Web Site

72 Questions?