FDOT District 1 Southwest Interagency Facility for Transportation (SWIFT) SunGuide Center. Strategic Operations Plan Prepared by: Telvent Farradyne

Transcription

1 FDOT District 1 Southwest Interagency Facility for Transportation (SWIFT) SunGuide Center Strategic Operations Plan Prepared by: Telvent Farradyne Telvent Farradyne (Page i) Revised: 6/2/08

2 Table of Contents 1 Strategic Operations Plan - Document Overview Usage Guidelines for Supplementary Manuals Manual Updates Introduction to the FDOT District 1 SWIFT SunGuide Center SWIFT SunGuide Center Roles and Responsibilities SWIFT SunGuide Center ITS Deployment SWIFT SunGuide Center Coverage Area FDOT Districts - Statewide FDOT District 1 Map FDOT District FDOT District FDOT District 4 - Adjacent to District FDOT District 5 - Adjacent to District FDOT District 6 - Adjacent to District FDOT District 7 - Adjacent to District FDOT Florida s Turnpike District Local, Regional, and Statewide Agencies FDOT District 1 SWIFT SunGuide Center Team Members Telvent Farradyne Southwest Research Institute MVP Marketing & Public Affairs Transportation Management Centers District 2 Jacksonville RTMC District 3 Tallahassee RTMC and Pensacola RTMC District 4 Palm Beach ITMS District 4 Broward TMC District 5 Orlando RTMC District 6 Miami / Dade County TMC District 6 Miami/Dade Expressway Authority (MDX) District 7 Tampa Bay SunGuide RTMC Florida s Turnpike TMC Advanced Traveler Information Systems (ATIS) Providers Southwest Regional 511 Service Tampa Bay 511 Service Southeast Regional 511 Service Statewide 511 Service Florida Highway Patrol (FHP) Troop F FHP Communications & Dispatch Troop F Troops K & L Troop C Other FHP Troops Office of Motor Carrier Compliance Local Police County Sheriff s Offices Local Police City Other Law Enforcement Agencies Local Fire Departments & Fire Rescue...37 Telvent Farradyne (Page ii) Revised: 6/2/08

3 7.9.1 Local Fire Department Coverage Areas on I-75 North Local Fire Department Coverage Areas on I-75 South Local Fire Department Coverage Areas on I Local Fire Departments Contact Information Florida Department of Transportation FDOT D1 Traffic Operations FDOT D7 Traffic Operations FDOT D4 Traffic Operations FDOT Public Information Office (PIO) FDOT Maintenance Road Ranger Service Patrol Vendors Road Ranger Service Patrol Vendor FDOT District Road Ranger Service Patrol Vendor FDOT District Road Ranger Service Patrol Vendor FDOT District 4 & District Road Ranger Service Patrol Vendor General Contact Information Federal Highway Administration Traffic Engineering Collier County Traffic Operations Department Lee County Traffic Signals Charlotte County Traffic Signals Sarasota County Traffic Signals Manatee County Traffic Signals District 4 Traffic Engineering Departments District 7 Traffic Engineering Departments Emergency Operations Centers Emergency Operations Centers in FDOT District Palm Beach County Emergency Operations Center Broward County Emergency Operations Center Public Safety Answering Points (PSAPS) Transit Collier Area Transit (CAT), Trolley, & Greyhound Bus Lee County Transit (LeeTran) Charlotte Area Transit & Dial-A-Ride Sarasota County Area Transit (SCAT) Manatee County Area Transit (MCAT) Media Metro Networks WGCU (Radio and Television) The News-Press Television Stations Radio Stations The Department of Environmental Protection (DEP) Animal Rescue and Removal Large Animal Removal and Disposal Large Animal Rescue By County Southwest Florida International Airport (RSW) Charlotte County Airport (PGD) Sarasota/Bradenton International Airport (SRQ) Field Device Descriptions and Locations General Operational Concepts Incident Detection, Verification, and Response...69 Telvent Farradyne (Page iii) Revised: 6/2/08

4 9.2 Incident Level Definitions Incident Level Determination Factors Spill Mitigation Guidelines Move It Law Move Over Act Open Roads Policy Event Timelines First Responder Checklist Dynamic Message Sign Strategies Definition of At and Past an Exit Definition of At, Before, and Beyond an Exit Definition of Commercial Vehicle Fifty Miles an Hour Rule SunGuide TM Software Description Event Management / Performance Measures (EM/PM) EM/PM - Main Screen EM/PM - Event Detail Window EM/PM - Report Feature SunGuide Software Incident Management Module IM Module - Dynamic Message Sign Control IM Module - Closed Circuit Television (CCTV) Control IM Module - Video Wall Control SunGuide Software Data Management Data Entry Steps Input Monitor and Update Clear Block CCTV Images Road Rangers SunGuide Reports Audit Preferences Video Detection Alerts Currently Blocked CCTV Images Road Ranger Service Patrol Procedures Road Ranger Service Patrol Coverage Area Maps and Operational Aids AVL and Road Ranger Service Patrol Rules Per FDOT Shift Start and Shift End Road Ranger Administration Form SunGuide Software Patrol Status Changes Authorized Leave from Road Ranger Beats Coverage Changes when One or More Zones are Not Patrolling Road Ranger Communications Two-Way Radio Setup Two-Way Radio Usage Vacating the Road Ranger Communications Console Transmission Quality, Volume, and Tone Road Ranger Telephone Calls NATO Phonetic Alphabet SWIFT SunGuide Center Approved Ten Signals and Dispatch Codes Telvent Farradyne (Page iv) Revised: 6/2/08

5 All 10-Codes Commonly Used 10-Codes by Operations Staff Radio Console Equipment Incident Detection and Road Ranger Dispatch Driving in the Emergency Lanes to Reach Incidents Dispatching Multiple Units Road Ranger Arrival SunGuide Software Event Details Data Entry Road Ranger Service Patrol Incident Types Accidents Abandoned Vehicles Disabled Vehicles Animals Road Ranger and Motorist Interaction Transporting Motorists Maintenance of Traffic Road Ranger Assist Updates Road Ranger Assist Clearance Road Ranger Service Patrol Problems Road Ranger Service Patrol Issue Resolution Local Agencies & Motorists Citizen and Agency Complaints Road Ranger Service Patrol Involved in an Accident Road Ranger Service Patrol Vehicle Not Operational or Missing Equipment Road Ranger Procedure when One or More Zones Not on Duty Road Ranger Service Patrol Procedural Errors Incorrect MOT Setup Road Ranger Service Patrol Safety Road Ranger Service Patrol Hourly Procedure Safety AVL Operation and Monitoring Road Ranger Common Data Entry Errors Incident Management 7 Step Concept Incident Management Roadway Monitoring and Incident Detection Video Wall Detection CCTV Detection Camera Presets Camera Pan/Tilt/Zoom (PTZ) Restricting Camera Images Vendor Camera Control Software Microwave Vehicle Detector System MVDS False Alarms Road Ranger Detection FHP Dispatch Star FHP Calls FHP Radio Transmissions FHP Website Local Police & Fire Department Scanner Telephone Alert SWIFT SunGuide Center Account Websites Regional Traffic Management Centers Road Construction Monitoring Telvent Farradyne (Page v) Revised: 6/2/08

6 14.15 WINK Radio Traffic Broadcasts Incident Management Event Confirmation CCTV Confirmation Road Ranger Confirmation Florida Highway Patrol Confirmation Event Confirmation Flowchart Incident Management Event Evaluation Incident Level Definitions (With Examples) Wrecker Services and Classifications Incident Management DMS Response Plan DMS Response Plan Guidelines DMS Message Priority DMS Response Plan Flowchart DMS Message Credibility DMS Message Activation Procedure General DMS Message Activation Procedure Long Term Road Work DMS Message Activation Procedure Travel Times DMS Message Activation Procedure - Test Messages Camera Verification of DMS Message Content Incident Management Event Notification Event Notification Text Alerts Event Notification Categories Event Notification SWIFT SunGuide Center Website Event Notification Newsworthy Events Event Notification Crashes in Work Zones Event Notification Flowchart Event Notification SWIFT SunGuide Center Agency Contact List Incident Management Event Monitoring Event Monitoring Flowchart Incident Management Event Closure Event Closure Flowchart Event Closure Flowchart Description Unresolved Events Lane Closing Incidents not Meeting the Goal of the Open Roads Policy Procedures Specific Incident Types Amber Alert Procedure LEO (Law Enforcement Offenders) Alert Plan LEO Alert Plan DMS Message Template Roadwork Procedures Scheduled Roadwork Emergency Roadwork Power Plant Procedure Accident Investigation Sites Special Events Procedures Prioritizing Multiple Events Procedures Other Operational Situations Traffic Signal Malfunctions Live Animals Causing a Safety Hazard Procedure for Graffiti Sightings Regional Event Management FDOT District 1 SWIFT SunGuide Center as the Assisting Agency Telvent Farradyne (Page vi) Revised: 6/2/08

7 DMS Message Activation Procedure District 4 Broward TMC Incidents DMS Message Activation Procedure Florida s Turnpike Incidents DMS Message Activation Procedure District 6 TMC Incidents DMS Message Activation Procedure District 7 TMC Incidents DMS Message Activation Procedure District 5 TMC Incidents FDOT District 1 SWIFT SunGuide Center as the Requesting Agency DMS Usage for Regional Events Other Resources Star FHP (*FHP) Motorist Assistance Calls Information Required & Questions to Ask the Caller Calls from I-75 - Not for Motorist Assistance Calls from Arterial Roadways in FDOT District 1 - Not for Motorist Assistance Calls in Other TMC Jurisdictions Star FHP Call Taking Summary Procedures - Equipment Failures Telvent SOS Helpdesk Building Maintenance Power Failure Electrical Generator Failure Road Ranger Radios Local Network Failure Video Wall Failures Failure to Access the Video Wall from the Operator Stations Video Wall Configuration during Video Wall or Software Failures DMS Damaged from an Accident, Vandalism, or High Winds DMS Message Malfunction RTMC Website Failure Total System CCTV Failure Fiber Optic Cable Damage or Failure Incident Notification Failure SunGuide Software Failure - Backup Operations Event Notification Procedures Backup Event Notification Contacts by Impact Group Backup Event Notification Formats Event Notification Format - Incidents Event Notification Format Amber (Child Abduction) Alert Event Notification Format Storm Watch and Storm Warning Event Notification Format Shutdown for SWIFT SunGuide Center Power Failure Event Notification Format Power Restored at the SWIFT SunGuide Center Event Notification Format SWIFT SunGuide Center Relocated to Alternate Facility Event Notification Format Operations Resumed at the SWIFT SunGuide Center Event Notification Format Administration Event Notification Format SWIFT SunGuide Center Bulletin (Newsworthy Events) Road Ranger Data Entry - Backup SWIFT SunGuide Disaster Recovery Plan Disaster Event Overview Initial Failure Crisis Assessment Crisis Designations Coordinating with Other FDOT Districts Communications with the Media Telvent Farradyne (Page vii) Revised: 6/2/08

8 28.4 Roles and Responsibilities Employee Vacation Status Disaster Recovery Plan Flowcharts Page 1 Flow Chart Description Page 2 Flow Chart Description Page 3 Flow Chart Description Page 4 Flow Chart Description End of Disaster State TMC Staff Assessment Review Training Initial Operator Training Periodic Testing Quarterly Plan Review with Senior Management Hurricane and Severe Weather Plan Hurricane Categories Hurricane and Severe Weather Objectives Plan Development Road Ranger Redundant Communications Relocation of Operations Staff Develop Emergency Contracts Repair of ITS Field Devices Utilize Vehicle Counts and Speed Data Spare Parts Inventory Generators for Field Equipment Portable Traffic Control Devices Backup Communications for External Contacts Preparation SWIFT SunGuide Facility Operations Staffing Road Ranger Program Emergency Operations Centers FDOT Maintenance ITS Field Device Preparation Severe Weather Supplies Severe Weather Radio SWIFT SunGuide Center Generator SWIFT SunGuide Center Facility Recovery Emergency Communication Teams Damage Assessment Teams ITS Field Device and Internal Systems Recovery Hurricane and Severe Weather Flowchart Hurricane and Severe Weather Schedule Phase A - Before Hurricane SWIFT SunGuide Center Field Device Maintenance Contractor Phase B - Hurricane Alert SWIFT SunGuide Center Field Device Maintenance Contractor Phase C - Hurricane Watch SWIFT SunGuide Center Telvent Farradyne (Page viii) Revised: 6/2/08

9 Field Device Maintenance Contractor Phase D - Hurricane Warning SWIFT SunGuide Center Field Device Maintenance Contractor Phase E - After Hurricane SWIFT SunGuide Center Field Device Maintenance Contractor SWIFT SunGuide Disaster Recovery Plan Specific Disaster Procedures Building Threats and Evacuations Fire Drill Fire Power Failure Bomb Threats Severe Weather Other Hazardous Conditions Remote Operation of the SWIFT SunGuide Center Homeland Security Policy Weapons of Mass Destruction Threat and Incident Response Continuity of Operations Plan Other Emergency Procedures Regional Civilian Evacuation and Contra-Flow Plans Diversion Routes (Future) Full Road Closures on I Brush Fires on I Full Road Closures on Roadways Other than I Diversion Route Scenarios Bridge Security Plans (Future) Frequently Asked Questions From the Public Frequently Asked Questions Concerning the SOP Document List of Acronyms Emergency Contact Information FDOT District 1 Staff RTMC Operations FDOT District 1 Staff - Field and Internal Equipment Maintenance Road Ranger Staff Incident Responders and Partner Agencies District Incident Responders and Partner Agencies Other Districts Telvent Farradyne (Page ix) Revised: 6/2/08

10 1 Strategic Operations Plan - Document Overview The Strategic Operations Plan (SOP) document is a detailed manual that addresses the plans, procedures, and guidelines for activities conducted by the Florida Department of Transportation (FDOT) District 1 Southwest Interagency Facility for Transportation (SWIFT) SunGuide Center (SWIFT SunGuide Center). It includes the vision, mission, values, strategic objectives, and key performance measures of the SWIFT SunGuide Center. It also provides the staff with the reference materials and the knowledge necessary to operate the Regional Transportation Management Center (RTMC) in support of FDOT s overall mission. This SOP was developed utilizing the Systems Engineering Management Plan (SEMP) traceability matrix. Portions of this document were developed jointly with FDOT and the Florida Highway Patrol (FHP) to provide a review process to resolve operational issues, facility issues, and agency responsibilities. All procedures contained in this document have been reviewed and approved by FDOT. Any changes, additions or deletions of procedures noted in the document will have received FDOT approval before inclusion in this manual. The SOP will be reviewed and revised by the RTMC Operations Manager every six months after the commencement of operations at the SWIFT SunGuide Center. 1.1 Usage Guidelines for Supplementary Manuals In addition to the SWIFT SunGuide Center SOP, there are several other documents that are necessary for the successful operation of the traffic management center. These documents are all located at the individual operator workstations in the control room, on the SWIFT SunGuide Center operations server, in the office of the RTMC Operations Supervisor, and in the office of the RTMC Operations Manager. All the documents are listed and described in the list below. o Standard Operating Guidelines Provides specific administrative and operational policies and guidelines for the operators and supervisors working at the FDOT District 1 SWIFT SunGuide Center. o Strategic Operations Plan Addresses the plans, procedures, and guidelines for activities conducted by the SWIFT SunGuide Center. This document will include the vision, mission, values, strategic objectives, and key performance measures of the SWIFT SunGuide Center. o Dynamic Message Sign SOP Contains the policies and procedures governing the activation of the SWIFT SunGuide Center Dynamic Message Signs (DMS). The DMS message matrix will also be included in this document. o SWIFT SunGuide Center Training Manual Provides the purpose, plan, and chronology for the 2-4 week training program offered to all new SWIFT SunGuide Center operators and employees. o TIM Team Manuals These two manuals contain the contact information and interagency procedures for incident responding agencies in Collier-Lee and Charlotte-Sarasota- Manatee Counties. Telvent Farradyne Page 1 Revised: 6/2/08

11 o Local TMC Manuals The operations manuals for each TMC whose coverage area borders FDOT District 1 o SEFRTOC Standard Operating Guidelines - This manual describes the procedures for communications and incident coordination between the five southeast Florida traffic management centers. o SunGuide Software Manuals The manual(s) that describe the SunGuide software and give instructions on its use and functionality. o 511 Operations Manuals The manuals for operating the local and statewide 511 systems o Road Ranger Scope of Services and Performance Expectations Documents The documents governing the operation of the FDOT District 1 Road Ranger program o Radio Console Users Manual o Manual containing the design, functionality, and instructions on the use of the radio console equipment FHP Communications Center Manuals The manuals for operating the FHP communications center o Local 911 Center Manuals The manuals for operating the local 911 call centers o Traffic Management Operations Manuals The manuals containing the policies and procedures for operating traffic signal systems o Southwest Florida Contra-flow Plan This plan dictates where to station emergency personnel and how to reconfigure the roadway system so the population of southwest Florida can be safely and efficiently be relocated to a safer location during times of emergency. o Telvent USA Employee Handbook Provides the employee with important information about Telvent. It will acquaint employees with the policies, practices, programs, and services which guide your employment at Telvent Farradyne. o Telvent SOS Helpdesk User Manual This manual describes the Telvent Outsourcing tool called the "SOS Helpdesk" that is used to log all IT support requests and track their progress to completion. Telvent Farradyne Page 2 Revised: 6/2/08

12 1.2 Manual Updates This document is considered a living document, so it will be updated as policies and procedures change over time. Changes made to this document will be tracked in the Updates to This Manual table below. The previous two bi-annual section updates will be tracked individually and older updates will be condensed into a summary style entry to maintain a reasonable document page count. These older individual table entries may be accessed in previous versions of this document. SEC- TION # Entire Document DATE SECTION UPDATED 8/20/07 to 12/31/07 Updates to This Manual SECTION NAME CHANGE IMPLEMENTED Strategic Operations Plan (SOP) Manual Creation Created this manual and received FDOT approval Entire Document 8/25/04 to 12/29/06 Sample Entries Updates to this Manual Removed the record of all changes made to this document in this section, Updates to This Manual from 8/25/04 to 12/29/06. This was necessary for ease of reading and document space concerns. 6 to 16 1/26/07 ITMS Procedures Separated this section (section 6) into multiple and more specific sections. This was a first attempt, so additional /26/07 Notification Procedures by Incident Impact Level changes will be necessary in the near future. Changed the wording of this section to more accurately reflect current procedures. Telvent Farradyne Page 3 Revised: 6/2/08

13 2 Introduction to the FDOT District 1 SWIFT SunGuide Center The SWIFT SunGuide Center is the hub of real-time operations on I-75 and the supporting arterial network throughout FDOT District 1. This center s system relays information to the public through many components, allows the public to make efficient and timesaving transportation decisions, and serves as the base of regional traffic management, law enforcement, and incident management. FDOT has plans to widen Interstate 75 (I-75) throughout District 1 over the next few years. During the construction period, it is expected that congestion and delays will increase from lane closures and other construction-related activities. In addition, these construction projects are expected to cause an increase in incidents along the freeway. FDOT District 1 has constructed the SWIFT SunGuide Center and the ITS field devices to manage traffic flow on I-75. This is especially important when lane closing incidents, construction, recurring delays, and other events impact traffic flow. The SWIFT SunGuide Center provides the public with real-time information on current traffic conditions along I-75. The SWIFT SunGuide Center is connected with the highway service patrol program (Road Rangers), the Advanced Traveler Information System (ATIS) 511 program, the various Traffic Signal Control Systems throughout the district (which has several cameras strategically positioned to view some arterial roadways), the FDOT District 1 Public Information Office (PIO), the Florida Highway Patrol (FHP), the Collier-Lee County Traffic Incident Management (TIM) Team, and the Charlotte-Sarasota-Manatee TIM Team. The SWIFT SunGuide Center operates and manages field devices, including, but not limited to, closed circuit television (CCTV) cameras, dynamic message signs (DMS), vehicle detection systems (VDS), roadway weather information systems (RWIS), and the safety barrier cable system (SBCS). These devices are all controlled through the centralized SunGuide TM computer system. Telvent Farradyne Page 4 Revised: 6/2/08

14 3 SWIFT SunGuide Center Roles and Responsibilities The FDOT District 1 SWIFT SunGuide Center provides full traffic management services and is the real-time communications hub for FDOT and FHP incident response throughout Collier and Lee Counties along I-75. The SWIFT SunGuide Center coverage area will increase as the FMS is extended north through Charlotte, Sarasota, and Manatee Counties. This includes Intelligent Transportation Systems control, operations, and traffic monitoring. Specifically, the RTMC operations personnel have the following roles and responsibilities. o Are the primary 24/7/365 incident management system on I-75 in Collier and Lee Counties o Enhance travel safety and transportation efficiency by managing incidents, controlling traffic, and providing accurate information to the public o Coordinate and manage the relocation of impediments to traffic flow o Monitor the roadways and respond to incidents as they occur to reduce incident response time and clearance times o Be the hub of communications for incident response for FDOT, FHP, and other responding agencies o Assist FHP by sharing CCTV camera images for faster emergency response o Coordinate emergency responses to significant roadway incidents by dispatching the FDOT Road Rangers and making other agency notifications o Coordinate and request the deployment of FDOT maintenance equipment to help expedite the clearance of major incidents o Coordinate and request the deployment of traffic signal technicians for the repair of signal systems o Coordinate temporary modifications to the traffic signal timing patterns during road closing incidents to ease traffic congestion o Request temporary modifications to the traffic signal timing patterns through the local traffic engineering offices during road closing incidents to ease traffic congestion o Operate and maintain the SunGuide software system o Provide timely and accurate incident detection, verification, and response for incident management, while continuing to strive to meet the 90 minute goal of Florida s Open Roads Policy o Provide ITS service to the public o Be the communications source of incident information to the public by communicating with the FDOT public information officers and by utilizing the RTMC website, operating the 511 system, and activating dynamic message signs o Aggressively use resources to gather, analyze, detect, and report incidents by using the deployed ITS devices throughout the I-75 corridor o Increase the motorist s understanding of the SWIFT SunGuide Center through consistent and high quality public relations and media outreach for FDOT o Maintain a staff of customer service professionals and operators that are trained to handle roadway incidents from the SWIFT SunGuide Center Telvent Farradyne Page 5 Revised: 6/2/08

15 4 SWIFT SunGuide Center ITS Deployment The SWIFT SunGuide Center FMS provides southwest Florida with robust Intelligent Transportation Systems (ITS), makes interstate widening safer, and assists with emergency evacuations. ITS is the application of computers, electronics, communications, and other technologies to manage transportation systems more safely and efficiently. The SWIFT SunGuide Center operates and manages all the FMS devices along I-75 in Southwest Florida for FDOT District 1, provides the coordination and cooperation with the agencies needed to achieve the objective of a seamless transportation network across multiple jurisdictions, and serves as the dissemination point for transportation information to the public. The Phase 1 FMS deployment of the SWIFT SunGuide Center covers approximately 98 miles of I-75 in Collier and Lee Counties. The SWIFT SunGuide Center monitors and operates 26 Dynamic Message Signs (DMS), 89 Closed Circuit Television (CCTV) Cameras, 111 vehicle detectors, and 2 Roadway Weather Information Systems (RWIS). The SWIFT SunGuide Center also monitors the safety barrier cable system (SBCS) that is deployed on the Alligator Alley section of I-75 in Collier County. In the future, additional field devices will be deployed on I-75 as the FMS is expanded into Charlotte, Sarasota, and Manatee Counties in 2009, 2012, 2013, respectively. These future projects will add DMS, CCTV Cameras, vehicle detectors, RWIS, License Plate Readers, and Highway Advisory Radio (HAR). A satellite TMC is also planned for Sarasota and Manatee Counties that will control the field devices on I-75 and the segment of I-275 from I-75 to the Sunshine Skyway Bridge. Telvent Farradyne Page 6 Revised: 6/2/08

16 5 SWIFT SunGuide Center Coverage Area The primary coverage area for the SWIFT SunGuide Center is the mainline and access points of I-75 in Collier, Lee, Charlotte, Sarasota, and Manatee Counties. A substantial number of ITS devices with incident detection/verification capabilities are currently deployed along the I-75 corridor in Collier and Lee Counties. The secondary coverage area includes the local agencies which manage the computerized signal systems bordering the I-75 corridor. The tertiary coverage area includes the arterial roadways throughout all the counties incorporated into FDOT District 1. Specifically, the SWIFT SunGuide Center coverage area encompasses the I-75 corridor starting at the Broward/Collier County Line on the eastern boundary of District 1, goes westward across the Everglades, then turns northward through the remainder of Collier, Lee, Charlotte, Sarasota, and Manatee Counties. The coverage area ends at the interchange of I-75 and I-275 in Manatee County where District 7 coverage begins. The east-west section of I-75 is referred to as Alligator Alley, which is a rural freeway with few interchanges. Due to the importance of these interchanges, particularly in this rural region, the project corridor limit was extended east into the FDOT District 4 area of Broward County to include the I-75 interchange with Government Road/Snake Road. The north-south section of I-75 is a mixture of urban, inter-urban, and rural freeway sections. The total length of I-75 in District 1 is about 218 miles, and currently consists of about 955 lanemiles in both directions. The Interstate intersects with a number of state and county highways. FDOT has identified a growing need for improved traffic and incident management in the I-75 corridor. This need has been substantiated by county transportation agencies, local and state law enforcement, Emergency Operation Center (EOC) operators, and the traveling public. Initial capacity improvements are planned for I-75 in Collier and Lee Counties to include the addition of two general-purpose lanes for a total of six lanes. Long range plans consider additional capacity and other improvements projected through Telvent Farradyne Page 7 Revised: 6/2/08

17 6 FDOT Districts - Statewide FDOT is divided into 7 geographic districts and the Florida s Turnpike Enterprise district that resides in District 1, 6, 4, 5, and 7. These districts are responsible for operating and maintaining the transportation system at the local level. Each of the districts is managed by the District Secretary. Each district has major division for Administration, Planning, Production, and Operations. Each district also has a Public Information Office and a General Counsel Office that report directly to the District Secretary. Telvent Farradyne Page 8 Revised: 6/2/08

18 6.1 FDOT District 1 Map A map indicating the twelve counties in District 1 is given below. Telvent Farradyne Page 9 Revised: 6/2/08

19 6.2 FDOT District 2 District 2 is not adjacent to FDOT District 1. A map indicating the location of District 2 is given below. 6.3 FDOT District 3 District 3 is not adjacent to FDOT District 1. A map indicating the location of District 3 is given below. Telvent Farradyne Page 10 Revised: 6/2/08

20 6.4 FDOT District 4 - Adjacent to District 1 District 4 is adjacent to the eastern border of District 1. A map indicating the location of District 4 is given below. 6.5 FDOT District 5 - Adjacent to District 1 District 5 is adjacent to the north-eastern border of District 1. A map indicating the location of District 5 is given below. Telvent Farradyne Page 11 Revised: 6/2/08

21 6.6 FDOT District 6 - Adjacent to District 1 District 6 is adjacent to the southern and south-eastern borders of District 1. A map indicating the location of District 6 is given below. 6.7 FDOT District 7 - Adjacent to District 1 District 7 is adjacent to the northern border of District 1. A map indicating the location of District 7 is given below. Telvent Farradyne Page 12 Revised: 6/2/08

22 6.8 FDOT Florida s Turnpike District The Florida s Turnpike District is not county or area specific. It is a select number of roadways that are located within several other FDOT District areas. A map indicating the coverage area of the Florida s Turnpike District is given below. Telvent Farradyne Page 13 Revised: 6/2/08

23 7 Local, Regional, and Statewide Agencies Descriptions of the local, regional, and statewide agencies that interact with the SWIFT SunGuide Center are given below. Additional contact names and numbers for agencies that are not provided in the Primary Contact Information for Partner Agencies section of this document are also included, when appropriate. For agency/contact information not located in this document, please refer to the two Traffic Incident Management (TIM) Notification & Agency Resource Guides for Collier-Lee and Charlotte-Sarasota-Manatee Counties. 7.1 FDOT District 1 SWIFT SunGuide Center Team Members The RTMC team is composed of Telvent Farradyne, Southwest Research Institute (SwRI) and M. Victoria Pennington Marketing and Public Affairs (MVP Marketing). All three agencies are uniquely qualified to operate the SWIFT SunGuide Center because we have the technical, operational, and public relations experience required for an operation of this magnitude Telvent Farradyne Telvent has the lead position on the team. In this capacity, Telvent is responsible for the operation of the SWIFT SunGuide Center and all the associated responsibilities that go with this obligation. These include; recruiting operators, development and provision of operating training, development of the Strategic Operations Plan and the Standard Operating Guidelines, updating the contact information of all SWIFT SunGuide Center partners ever six months during the semi-annual document reviews, and overall management of the contract Southwest Research Institute SwRI has been serving as the SunGuide SM software developer for four years, and is under contract to provide ongoing maintenance and support of SunGuide SM deployments. SwRI also has extensive experience in TMC support and maintenance for the Texas Department of Transportation s TransGuide SM facility and the Orlando Orange County Expressway Authority (OOCEA) Data Server. SwRI is currently under contract to provide 24/7 support for SunGuide SM, TransGuide SM, and OOCEA. SwRI provides the IT services required by FDOT on this project. Specifically, SwRI: o Facilitates, coordinates, and troubleshoots activities for software database and network management and maintenance o Maintains all SWIFT SunGuide Center system hardware, software, and network components o Coordinate ITS field equipment preventive and responsive maintenance, to support 24/7/365 operations o Supports the development of the SOP and the SOG. This is important because the plans and guidelines contained in these two documents are interrelated with the operation of the SunGuide SM software. o Contributes to the development and delivery of the operator training MVP Marketing & Public Affairs M. Victoria Pennington Marketing and Public Affairs (MVP) is a marketing and public relations firm experienced in marketing, product development, advertising, sales promotion, market research and organizational development. The firm has enjoyed significant success recently with its work on the Telvent Farradyne Page 14 Revised: 6/2/08

24 Jacksonville 511 web site. The firm has successfully represented several public sector clients in a variety of community forums and public hearings. MVP has the resources to develop an extensive promotional campaign encompassing advertising, media relations, collateral, a contest and special events. M. Victoria Pennington Marketing & Public Affairs (MVP) handles the important role of pubic relations and outreach for the SWIFT SunGuide Center. MVP Marketing has the lead responsibility for the design development and launch of the District 1 SWIFT SunGuide Center web site. The firm also has the lead responsibility for the public relations interface with the FDOT Public Information Office. Telvent Farradyne Page 15 Revised: 6/2/08

25 7.2 Transportation Management Centers There are currently five transportation management centers in southeast Florida. The Palm Beach ITMS and the Broward TMC manage the roadways in FDOT District 4. The District 6 TMC and the Miami-Dade Expressway Authority (MDX) manage the roadways in FDOT District 6. The Florida s Turnpike TMC in Pompano manages the southern span of the Florida s Turnpike and associated toll roads. The Florida s Turnpike TMC in Turkey Lake manages the northern span of the Florida s Turnpike and completes the TMC coverage for the entire FDOT Florida s Turnpike Enterprise District. The Florida s Turnpike resides in FDOT Districts 1, 6, 4, 5, and 7. These five agencies (6 including the Florida s Turnpike TMC in Turkey Lake) are all participants in the SEFRTOC (South-East Florida Regional TMC Operations Committee) sub-committee to the ITS Coalition that meets on a monthly basis to discuss TMC operational issues and interagency incident coordination. Other traffic management centers throughout the state of Florida include the District 7 Tampa RTMC, the District 5 Orlando RTMC, and the District 2 Jacksonville RTMC. These agencies manage the roadways in their respective FDOT Districts. It has been proposed that all Florida traffic management centers will be part of a statewide communications group that, much like SEFRTOC, will meet to discuss TMC operations issues, interagency incident coordination, and procedure synchronization. The proposed name of this group is Florida s Uniform Statewide Integrated Operations Network (FUSION). Telvent Farradyne Page 16 Revised: 6/2/08

26 7.2.1 District 2 Jacksonville RTMC The FDOT District 2 Jacksonville RTMC is an older facility that approximately measures 2,000 square feet. The TMC is manned with operations staff and a project manager. The daytime facility is operated out of the FDOT office from 6 A.M. to 6 P.M. Monday through Friday. During non-operational hours, one operations staff member is stationed in the FHP dispatch facility. The FDOT District 2 Jacksonville RTMC is only contacted for long-lasting regional incidents on I-75 south in District 1. The District 2 RTMC is provided incident status updates every 60 minutes or as traffic conditions change, and will be notified as soon as possible after all travel lanes are open. FDOT District 2 Jacksonville RTMC 2198 Edison Avenue Jacksonville, FL TMC Contact Information Phone: Derrick Odom 24/7 #: , x122 TMC Supervisor II, SmartRoute Systems Fax: Work: ryan.crist@dot.state.fl.us Cell: Website: derrick.odom@dot.state.fl.us Ryan Crist TMC Supervisor II, SmartRoute Systems Office: Mobile: ryan.crist@dot.state.fl.us Peter Vega District 2 ITS Engineer Office: Mobile: peter.vega@dot.state.fl.us Gina Busscher Public Information Officer Office: gina.busscher@dot.state.fl.us Telvent Farradyne Page 17 Revised: 6/2/08

27 7.2.2 District 3 Tallahassee RTMC and Pensacola RTMC Currently, FDOT District 3 is planning to build RTMCs in Tallahassee and Pensacola by FDOT District 3 RTMC Tallahassee Advanced Traffic Management System Street Address TBD Tallahassee, FL TMC Contact Information Phone: TBD Gabriel Manendez, PE, COT Nextel ID: TBD Public Works Director Main: TBD Work: Fax: TBD TBD Website: TBD Telvent Farradyne Page 18 Revised: 6/2/08

28 7.2.3 District 4 Palm Beach ITMS FDOT District 4 Palm Beach Interim Traffic Management System The Palm Beach ITMS is located just north of the north-east corner of the Palm Beach International Airport in West Palm Beach. The primary coverage area of this TMC encompasses I-95 in Palm Beach, Martin, St. Lucie, and Indian River Counties in District 4. The Palm Beach ITMS is contacted for all Level 3 incidents on I-75 west in Collier County, SR-80 west, and SR-70 west. The Palm Beach ITMS is provided incident status updates every 20 minutes or as traffic conditions change, and will be notified as soon as possible after all travel lanes are open. FDOT District 4 Palm Beach ITMS 2200 Centrepark West Drive Suite #200 West Palm Beach, FL TMC Contact Information Main: Helena White Backdoor: ITMS Operations Manager Fax: Work: Ops Cell: Cell: Ops Cell ID: 158*24*12819 Home: Website: Helena.white@telvent.abengoa.com pb-itms@telvent.abengoa.com Kevin Toth ITMS Project Manager Office: Mobile: Nextel: 159*507527*1 kevin.toth@telvent.abengoa.com Telvent Farradyne Page 19 Revised: 6/2/08

29 7.2.4 District 4 Broward TMC FDOT District 4 Smart SunGuide Traffic Management Center The Broward TMC is located on Commercial Boulevard in Fort Lauderdale between the Florida s Turnpike and I-95. The primary coverage area of this TMC encompasses I-75, I- 95, and I-595 in Broward County. The Broward TMC is contacted for all Level 3 incidents on I-75 west in Collier County and all Level 1 and Level 2 incidents on the Alligator Alley section of I-75 west. The Broward TMC is provided incident status updates every 20 minutes or as traffic conditions change, and will be notified as soon as possible after all travel lanes are open. FDOT District 4 Smart SunGuide TMC 2300 West Commercial Boulevard Fort Lauderdale, FL TMC Contact Information Main: Dee McTague Cell: TMC Operations Manager Nextel ID: 158*940*71 Work: Nextel ID: 158*940*92 Cell: Fax: dee.mctague@smartsunguide.com Website: Sarah Stanley PIO: ITS Marketing Office: Mobile: sarah.stanley@smartsunguide.com Telvent Farradyne Page 20 Revised: 6/2/08

30 7.2.5 District 5 Orlando RTMC The FDOT District 5 Orlando RTMC is co-located with FHP and is the regional hub for the Central Florida Regional Transportation Operations Consortium ITS systems. The RTMC monitors I-4 and I-95 with CCTV, vehicle detector stations, and DMS to alert motorists of changing traffic conditions. The FDOT District 5 Orlando RTMC is contacted for all Level 3 incidents on I-75 south in District 1. The District 5 RTMC is provided incident status updates every 20 minutes or as traffic conditions change, and will be notified as soon as possible after all travel lanes are open. FDOT District 5 Orlando RTMC 133 South Semoran Boulevard Orlando, FL TMC Contact Information Phone: Eddie Grant Nextel ID: 158*42*1640 RTMC Manager Fax: Work: @cfl.rr.com Cell: Website: eddie.grant@dot.state.fl.us Jennifer Heller ITS Operations Manager Work: Jennifer.heller@dot.state.fl.us Steve Honan Public Information Officer Phone: Phone #2: Cell#2: steve.homan@dot.state.fl.us Telvent Farradyne Page 21 Revised: 6/2/08

31 7.2.6 District 6 Miami / Dade County TMC FDOT District 6 SunGuide Control Center The FDOT District 6 TMC is a two-story structure measuring 32,000 square feet that is co-located with FHP Troop E Dispatching, SRS (511), Fish and Wildlife Commission (FWC) Dispatching, South Florida Commuter Services, and the State Technology Office. The primary coverage area of this TMC encompasses I-75, I-95, I-195, I-395, SR 826, SR 874, US-1, and US-27 in Dade County and US-41 and US-1 in Monroe County. The District 6 TMC is contacted for all Level 3 incidents on I-75 west in Collier County and all Level 1 and Level 2 incidents on the Alligator Alley section of I-75 west. The District 6 TMC is provided incident status updates every 20 minutes or as traffic conditions change, and will be notified as soon as possible after all travel lanes are open. FDOT District 6 SunGuide TMC 1000 NW 11 th Ave Miami, FL TMC Contact Information Phone: Rory Santana Nextel ID: 880*30849 ITS Manager Main: Work: Fax: Cell: Cell 2: Website: rory.santana@dot.state.fl.us Javier Rodriguez ITS Operations Engineer Phone: Cell: Cell #2: Eddie Montas TMC Operations Supervisor Phone: Cell: Javier.rodriguez2@dot.state.fl.us Cell#2: eddie.montas@dot.state.fl.us Telvent Farradyne Page 22 Revised: 6/2/08

32 7.2.7 District 6 Miami/Dade Expressway Authority (MDX) The Miami-Dade Expressway Authority operations and Road Ranger dispatch are performed at the District 6 SunGuide TMC. MDX oversees, operates, and maintains five expressways: SR 836 (Dolphin Expressway), SR 112 (Airport Expressway), SR 874 (Don Shula Expressway), SR 878 (Snapper Creek Expressway), and SR 924 (Gratigny Parkway). The Miami-Dade Expressway Authority TMC is not usually contacted for incidents, because of their co-location with the FDOT District 6 TMC. However, MDX will be provided incident status updates every 20 minutes or as traffic conditions change, and will be notified as soon as possible after all travel lanes are open, when communications are necessary. Miami-Dade Expressway Authority 1000 NW 11 th Ave Miami, FL TMC Contact Information (See contact information for the FDOT District 6 TMC) Steve Andriuk Incident Management Cell: Mike Smith Manager of Maintenance and Operations Phone: , x2116 Cell: Nextel ID: 159*52112*16 msmith@mdx-way.com Paul Watt Maintenance Superintendent Cell: pwatt@vmsom.com Telvent Farradyne Page 23 Revised: 6/2/08

33 7.2.8 District 7 Tampa Bay SunGuide RTMC The District 7 Tampa Bay SunGuide Center is located at the District 7 headquarters on McKinley Drive in north Tampa. The center provides freeway management on sections of I-275, I-75, and I-4. The two story building is a hardened facility with 19,000 square feet of floor space that will allow operations to continue throughout severe weather events. FHP dispatch, the District Emergency Operations Center, Florida Fish & Wildlife, SERT, FDOT MCCO, and FDLE are co-located in the RTMC along with FDOT. The District 7 Tampa Bay SunGuide RTMC is contacted for all Level 3 incidents on I-75 south in District 1 and all Level 1 and Level 2 incidents on I-75 south in Manatee, Sarasota, and Charlotte Counties. The District 7 RTMC is provided incident status updates every 20 minutes or as traffic conditions change, and will be notified as soon as possible after all travel lanes are open. FDOT District 7 Tampa Bay SunGuide RTMC North McKinley Drive Tampa, FL TMC Contact Information Phone: Dave Howell Main: RTMC Operations Manager Fax: Work: dhowell@hntb.com Cell: dhowell@hntb.com Terry Hensley Traffic Incident Manager Office: Mobile: terry.hensley@dot.state.fl.us Telvent Farradyne Page 24 Revised: 6/2/08

34 7.2.9 Florida s Turnpike TMC Florida s Turnpike Traffic Operations Center The Florida s Turnpike TMC operates two Traffic Operations Centers: o Broward County at the Pompano Beach Service Plaza o Orlando at the Turkey Lake Service Plaza These centers divvy the operations responsibilities for the entire span of the Florida s Turnpike Enterprise toll roads. The Florida s Turnpike operations centers are the only TMCs in southeast Florida that control Highway Advisory Radio (HAR) systems. The Florida s Turnpike TMC in Pompano is contacted for all Level 3 incidents on I-75 west in Collier County, SR-80 west, and SR-70 west. The Florida s Turnpike TMC in Pompano is provided incident status updates every 20 minutes or as traffic conditions change, and will be notified as soon as possible after all travel lanes are open. Florida s Turnpike Traffic Operations Center Pompano TMC Milepost 65 Pompano Beach, FL Florida s Turnpike Traffic Operations Center Turkey Lake TMC Milepost 263, Building 5315 Ocoee, FL TMC Contact Information Pompano TMC Mari Soper-Bojan Phone: x1370 Assistant TMC Manager, Pompano Main: Work: Cell: Cell: Ops #1: 162*19*63853 Nextel ID: 158*19*167 Ops #2: 159*77156*18 mari.soper-bojan@dot.state.fl.us Voice mail: (954) x turnpike.traffic@dot.state.fl.us Website: Turkey Lake TMC Kelly Kinney Phone: x3363 Assistant TMC Manager, Turkey Lake Main: Work: Cell: Cell: Nextel ID: 158*21* Kelly.kinney@dot.state.fl.us Telvent Farradyne Page 25 Revised: 6/2/08

35 7.3 Advanced Traveler Information Systems (ATIS) Providers The three-digit telephone number, 511, is used nationally by the public to acquire traveler information, such as anticipated travel delays, traffic accidents, roadway blockages, and lane closures. In Florida, there are ATIS providers for regional areas and a statewide 511 service for long-duration incidents that could affect travel through multiple local regions. The 511/ATIS providers rely heavily on the local traffic management centers to provide them information. The 511 service is provided free of charge Southwest Regional 511 Service The 511/ATIS service in southwest Florida is provided by the staff at the FDOT District 1 SWIFT SunGuide Center as of August The 511 service is operational 24 hours a day and 7 days a week. The coverage area for the southwest region includes all major roadways in Collier, Lee, and Charlotte Counties. The southwest regional 511 service is responsible for updating the statewide 511 service, when appropriate. The website for the southwest regional 511 service is Tampa Bay 511 Service Tampa Bay area travelers can use the 511 service to obtain real-time traffic conditions and other information. In addition, they can access traffic information on the website. The service is provided by FDOT District 7 as part of the Tampa Bay SunGuide RTMC Program. Information is currently provided for Hernando, Hillsborough, Manatee, Pasco, Pinellas, Polk and Sarasota counties Southeast Regional 511 Service The 511/ATIS service in southeast Florida is provided by an agency named SmartRoute Systems (SRS). The 511 service is operational 24 hours a day and 7 days a week. The coverage area for the southeast region includes all roadways in FDOT District 4 and District 6. The southeast regional 511 service is responsible for updating the statewide 511 service, when appropriate. The FDOT District 1 SWIFT SunGuide Center will notify the southeast regional 511 service provider of all crashes and lane-blocking incidents in District 1, severe weather events, or other events that could impact traffic in their coverage area. Similarly, the southeast regional 511 service provider will notify the FDOT District 1 SWIFT SunGuide Center of any incidents in the District 1 coverage area, major incidents near District 1 that could impact diversion routes, weather events, and statewide Amber alerts. The FDOT District 1 SWIFT SunGuide Center and the southeast regional 511 service provider will exchange incident information every 20 minutes, as conditions change, or as updated information is received. Southeast Regional 511 Contact Information Nextel ID: 158*880*11 Phone: Cell: Alex Mirones Director of Operations Phone: Cell: Nextel ID: 159*131698*1 Telvent Farradyne Page 26 Revised: 6/2/08

36 Mike Millard 511 Project Manager Phone: Cell: Penny Kamish Regional Director of Operations Cell: Statewide 511 Service The ITN for the Statewide 511 project was awarded to Logic Tree and the IBI Group with SwRI as a sub-contractor. The regional 511 services are responsible for updating the statewide 511 service, when appropriate. This project will include the data fusion system that will gather incident information from the SunGuide software and various 3 rd party sources and fuse it into the IVR. The FDOT District 1 SWIFT SunGuide Center staff will be responsible for all the necessary data collection. The FDOT District 1 SWIFT SunGuide Center will notify the statewide 511 service provider of all crashes and lane-blocking incidents in District 1, severe weather events, and Amber alerts. The FDOT District 1 SWIFT SunGuide Center and the statewide 511 service provider will exchange incident information every 20 minutes, as conditions change, or as updated information is received. Statewide 511 Contact Information Nextel ID: TBD Phone: TBD Cell: TBD TBD Director of Operations Phone: TBD Cell: TBD Nextel ID: TBD TBD TBD Project Manager Phone: TBD Cell: TBD Nextel ID: TBD TBD Telvent Farradyne Page 27 Revised: 6/2/08

37 7.4 Florida Highway Patrol (FHP) Troop F The function and duties of the Florida Highway Patrol include: o Patrolling state highways and regulating, controlling, and directing the movement of traffic. o Maintaining public order, apprehending fugitives, and effecting arrests for violations of the law that takes place in the presence of law enforcement officers. o Investigating and enforcing laws pertaining to the offense of auto theft. o Enforcing laws regulating dimensional regulations, taxing, operation, and other restrictions relating to licensing of vehicles or their operators. o Investigating traffic crashes. o Confiscating contraband and stolen property. o Assisting other constituted law enforcement agencies in the quelling of mobs and riots, the guarding of prisoners, and the policing of disaster areas. o Members of the Patrol occupying command or special duty positions will devote a minimum of 10% of their duty hours to patrol related duties. The FHP Troop F Fort Myers District Headquarters is co-located in the SWIFT SunGuide Center. The FHP Troop F Headquarters is located at the Bradenton District Station in Manatee County. Troop F is commanded by a Major who is charged with the operations of the ten counties which comprise the troop. The coverage area for Troop F is exactly the same as the coverage area for FDOT District 1, except that Troop F does not cover Polk and Okeechobee Counties. Troop F is responsible for Manatee, Hardee, Highlands, Sarasota, Desoto, Charlotte, Glades, Lee, Hendry, and Collier Counties. These 10 counties are broken down into four districts which are the Bradenton District, the Arcadia District, the Venice District, and the Fort Myers District. The Bradenton District is located at Troop F Headquarters and includes: o Manatee County. The Arcadia District is located in Arcadia and includes: o DeSoto County o Hardee County o Highlands County o Glades County o Hendry County The Venice District is located in Venice and includes: o Sarasota County o Charlotte County The Fort Myers District is located in the same building as the FDOT District 1 SWIFT SunGuide Center and includes: o Lee County o Collier County Telvent Farradyne Page 28 Revised: 6/2/08

38 The FHP Points of Contact in the RTMC are, in order: Captain James (Jim) Wells Office: , x300 Lieutenant Billy Rippy Office: Main: , x302 Fax: FHP Communications & Dispatch Troop F The Communication Centers of the Florida Highway Patrol are staffed by approximately 260 men and women performing many of the functions necessary to allow the Florida Highway Patrol and its fellow law enforcement agencies to meet their mandated functions. Their duties include telephone contact with the public and other law enforcement agencies for both emergency and non-emergency situations, dispatching emergency and non-emergency calls for service, performing computer inquiries for wanted persons, vehicles, registration, driver license, etc., and many other important tasks. The FHP Communications and FHP Dispatch Points of Contact in the SWIFT SunGuide Center are, in order: Captain Terry Davis FMRCC Commander Office: Main: Fax: terry.davis@flhsmv.gov Troop F Fort Myers Contact Numbers Dispatch: Information: Duty Officer Sup.: Shift Commander: Office District: Office Sub-District: Regional: *FHP (*347) Emergency: 911 Emergency: Fax: Clerks: Clerks (Naples): Records: PIO Lt. Dodson: , x117 Troop Commander: Major Rebecca Tharpe , x106 Telvent Farradyne Page 29 Revised: 6/2/08

39 District Commander: Capt. Eddie Johnson Fort Myers District: Captain James (Jim) Wells Office: , x300 Fort Myers District: Lieutenant Billy Rippy Office: Main: , x302 Fax: Naples Sub-District: Lt. Paul France Troop F Venice District Contact Numbers Troop F Naples District Contact Numbers Dispatch: Dispatch: Information: Information: Fax: Duty Officer Sup.: PIO Lt. Dodson: , x117 Troop F Bradenton District Contact Numbers Dispatch: Information: Fax: Duty Officer Sup.: PIO Lt. Dodson: , x117 Troop F Arcadia District Contact Numbers Dispatch: Information: PIO Lt. Dodson: , x Troops K & L The FHP Lake Worth Regional Communications Center (LWRCC) is the communications hub for Troops K and L, which rests on the eastern border of the FDOT District 1 and FHP Troop F coverage area. The Troop K area encompasses the Florida s Turnpike. Troop L covers the counties in FDOT District 4 and Okeechobee County. The Center is located at the West Palm Beach Service Plaza on the Florida s Turnpike at mile marker 94. General #: Fax: Dispatch Troop L/K Dispatch Lantana Suncom: Duty Officer Sup: Telvent Farradyne Page 30 Revised: 6/2/08

40 Shift Commander: Facility Commander: Captain I. A. Egeli Phone: Cell: Cell: FHP Motorola Radio Contact: Lenny Horner Troop C The Troop C area rests on the northern border of FDOT District 1 and FHP Troop F. It encompasses the counties in FDOT District 7 in addition to Polk and Sumter Counties. General #: Fax: Dispatch Troop L/K Duty Officer Sup: Opt 6 Shift Commander: Opt 7 Facility Commander: Captain Urana Harris Phone: Harris.Urana@hsnd.state.fl.us Other FHP Troops Main telephone numbers for other FHP troops in Florida. Troop A Panama City: (Florida Only) Troop B Lake City Troop D Orlando Troop E Miami Troop G Jacksonville Troop H Tallahassee Telvent Farradyne Page 31 Revised: 6/2/08

41 7.5 Office of Motor Carrier Compliance The Motor Carrier Compliance Office (MCCO) is a designated traffic law enforcement agency who has the same authority as other peace officers of the state including making arrests for violations of law, carrying firearms, service court process, and confiscating contraband. The agency operates a statewide system of weigh station facilities. Officers and inspectors appointed by the division have the authority to issue citations for violations and collect civil penalties while enforcing state law and federal regulations. In order to assist the department in fulfilling its mission, MCCO has the following goals and objectives. o Protect the state s highway and bridge infrastructure from overweight, oversized, and unsafe vehicles. Protect the lives and property through a comprehensive safety program, which includes Commercial Motor Vehicle (CMV) safety inspections, compliance reviews, traffic enforcement, post crash investigations, as well as outreach programs. o Enforce all state and general laws governing the operations of CMVs on Florida s roadways including registration, fuel tax, and driver s licenses. o Enforce laws involving the transportation of contraband using Florida s transportation system including illegal drugs and stolen property. o Perform general law enforcement duties required during mutual aide events and to assist other state and local agencies when requested. o Support and participate in Florida s efforts to provide domestic security generally, and to protect the state s transportation infrastructure from terrorism or other illegal acts. o Aide motorists who require law enforcement assistance and generally enforce laws that provide a safe driving environment for Florida s citizens and visitors. An example of the agency s involvement in public highway safety is it NO ZONE program. This is a public education campaign to make motorists aware of the dangers of driving in a trucker s blind spot, and is part of the national Don t Hang Out in the NO-ZONE campaign. MCCO is co-located in the FDOT District 1 SWIFT SunGuide Center to more effectively carry out its mission in partnership with traffic management colleagues within FDOT, as well as the FHP Regional Communications Center. The MCCO Points of Contact in the SWIFT SunGuide Center are, in order: Captain Troy L. Thompson Office: Mobile: troy.thompson@dot.state.fl.us Lieutenant R. G. Chick Richards Office: Fax: robert.richards@dot.state.fl.us Telvent Farradyne Page 32 Revised: 6/2/08

42 Telvent Farradyne Page 33 Revised: 6/2/08

43 7.6 Local Police County Sheriff s Offices Dispatch Main Other Info Lee County Sheriff s Office Lee County Sheriff s Office Bonita Springs Lee County Sheriff s Office Town of Fort Myers Beach Lee County Sheriff s Office Captiva (Island Coastal) Lee County Sheriff s Office North District Lee County Sheriff s Office Lehigh District Lee County Sheriff s Office West District Lee County Sheriff s Office South District Collier County Sheriff s Office Charlotte County Sheriff s Office All of Lee county is dispatched from the number Sarasota County Sheriff s Office Emergency: Manatee County Sheriff s Office Emergency: Pinellas County Sheriff s Office Emergency: Desoto County Sheriff s Office Palm Beach County Sheriff s Office 3228 Gun Club Road West Palm Beach, FL Broward County Sheriff s Office BSO Duty Officer Broward County Sheriff s Office Communications Broward County Sheriff s Office Bomb and Arson Broward County Sheriff s Office Special Operations Broward County Sheriff s Office Helicopters Fax: Supervisor: Telvent Farradyne Page 34 Revised: 6/2/08

44 7.7 Local Police City Dispatch Main Other Info Bradenton Beach PD Emergency: Bradenton PD Cape Coral PD Fort Myers PD Holmes Beach PD Emergency: Longboat Key PD Emergency: Miccosukee Police Alligator Alley Substation Northport (7327) Emergency: Punta Gorda PD Sanibel PD Sarasota PD Emergency: St. Petersburg Beach PD Emergency: St. Petersburg PD Emergency: Venice PD Belle Glade PD (Palm Beach County) Telvent Farradyne Page 35 Revised: 6/2/08

45 7.8 Other Law Enforcement Agencies Dispatch Main Other Info Office of Agricultural Law Enforcement Bureau of Alcoholic Beverages & Tobacco Fax: Federal Bureau of Investigation Florida Marine Patrol Lee County Port Authority U.S. Coast Guard National Response Center U.S. Coast Guard Marine Safety Office, Tampa U.S. Coast Guard Cortez U.S. Coast Guard Bradenton U.S. Coast Guard Fort Myers Beach U.S. Coast Guard St. Petersburg Department of Homeland Security (DHS) Florida Department of Law Enforcement (FDLE) Emergency: Superbowl Planning, etc Amber Alerts, etc. Telvent Farradyne Page 36 Revised: 6/2/08

46 7.9 Local Fire Departments & Fire Rescue Local Fire Department Coverage Areas on I-75 North Agency Limits Northbound I-75 Milepost Primary Contact Number Ochopee Broward County Line to SR Fire Control & Rescue Golden Gate SR 29 to Golden Gate Fire Control & Rescue Parkway Overpass North Naples Golden Gate Parkway Fire Control & Rescue Overpass to Lee County Line Bonita Springs Collier County Line to Mile Fire Control & Rescue Estero Fire Rescue Mile to Mile San Carlos Park Fire Control & Rescue South Trail Fire Control & Rescue Fort Myers Fire Tice Fire Control & Rescue Bayshore Fire Control & Rescue Charoltte County North Port Fire District Sarasota County Fire Department Venice Fire Department Nokomis Fire Department Sarasota County Fire Department (Rescue) Sarasota County Fire Department East Manatee North River Mile to Mile Mile to SR 884 Colonial Boulevard SR 884 Colonial Boulevard to SR 82 MLK Jr. Boulevard SR 82 MLK Jr. Boulevard to Caloosahatchee River Caloosahatchee River to Charlotte County Line Lee County Line to Sarasota County Line Charlotte County Line to SR 777 River Road SR 777 River Road to Laurel Road Laurel Road to MP 199 Crossover MP 199 Crossover to SR 72 Clark Road Laurel Road to SR 72 Clark Road SR 72 Clark Road to University Parkway University Parkway to Manatee River Manatee River to Hillsborough County Line X Telvent Farradyne Page 37 Revised: 6/2/08

47 7.9.2 Local Fire Department Coverage Areas on I-75 South Agency Limits Southbound I-75 Milepost Primary Contact Number North River Hillsborough County Line to Manatee River East Manatee Manatee River to University Parkway X2246 Sarasota County University Parkway to Fire Department MP 199 Crossover Sarasota County MP 199 Crossover to Fire Department (Rescue) Jacaranda Boulevard Venice Fire Department MP 199 Crossover to Jacaranda Boulevard Sarasota County Jacaranda Boulevard to Fire Department Ponce de Leon North Port Fire District Ponce de Leon to Charlotte County Line Charlotte County Sarasota County Line to Lee County Line Bayshore Charlotte County Line to Fire Control & Rescue Caloosahatchee River Tice Caloosahatchee River to Fire Control & Rescue SR 82 MLK Jr. Boulevard Fort Myers Fire SR 82 MLK Jr. Boulevard to SR 884 Colonial Boulevard South Trail SR 884 Colonial Boulevard to Fire Control & Rescue Mile 129 San Carlos Park Mile 129 to Mile Fire Control & Rescue Estero Fire Rescue Mile to Mile Bonita Springs Fire Control & Rescue North Naples Fire Control & Rescue Golden Gate Fire Control & Rescue Ochopee Fire Control & Rescue Mile to Collier County Line Lee County Line to Golden Gate Parkway Overpass Golden Gate Parkway Overpass to SR 29 SR 29 to Broward County Line Telvent Farradyne Page 38 Revised: 6/2/08

48 7.9.3 Local Fire Department Coverage Areas on I-275 Agency Limits North/West I-275 Milepost Primary Contact Number North River I-75 to Sunshine Skyway Bridge Agency Limits South/East I-275 Milepost Primary Contact Number North River Sunshine Skyway Bridge to I Local Fire Departments Contact Information Agency Dispatch Main Other Info Alva Bayshore Boca Grande Bonita Springs Bradenton X1112 Bradenton / Sarasota Airport Cape Coral Captiva Cedar Hammock X2246 Charlotte 911 CSO Charlotte County Fire and EMS Charlotte CSO Direct to EMS Desoto County East Manatee (formerly Braden River) X2246 Englewood Estero State Division of Forestry Collier, Lee, Hendry Counties Charlotte, Sarasota, Manatee Counties X Fort Myers Fort Myers Beach X6163 Fort Myers Shores Golden Gate Hillsborough Fire Iona-McGregor Lehigh Acres Longboat Key Telvent Farradyne Page 39 Revised: 6/2/08

49 Agency Dispatch Main Other Info Manatee ECC Manatee County X2246 Matlacha-Pine Island Myakka City X2246 Nokomis North Fort Myers North Naples North Port North River X2246 Ochopee Port Authority Airport ARFF Punta Gorda San Carlos Park Sanibel Sarasota Airport CFR Fax: Sarasota County Southern Manatee X2246 South Trail SW Florida Urban Search & Rescue Tampa X6805 Tice Upper Captiva Useppa Island Venice West Manatee Whitfield Palm Beach County Fire Rescue Chief Steve Jerauld Pager: Telvent Farradyne Page 40 Revised: 6/2/08

50 7.10 Florida Department of Transportation The FDOT mission is to provide a safe transportation system that ensures the mobility of people and goods, enhances economic prosperity, and preserves the quality of our environment and community. There are many functional areas within the department to accomplish the above mission, including the FDOT Traffic Engineering and Operations Office. The SWIFT SunGuide Center is part of this department, whose goal is to provide support and expertise in the application of traffic engineering principals and practices to improve safety and mobility FDOT D1 Traffic Operations FDOT District 1 Traffic Operations Main Office 801 North Broadway Street Bartow, FL FDOT District 1 Traffic Operations Southwest Area Office 2295 Victoria Avenue, Suite 292 Fort Myers, FL FDOT District 1 Traffic Operations Contacts include: FDOT RTMC Manager: Carlos Bonilla Office: Mobile: carlosf.bonilla@dot.state.fl.us ITS Project Manager: Katherine Duvall Office: Fax: katherine.duvall@dot.state.fl.us ITS Program Manager: Chris Birosak Office: Cell: Fax: chris.birosak@dot.state.fl.us ITS Senior Project Manager: Mark Roberts Office: Fax: mark.roberts@dot.state.fl.us Traffic Incident Management Project Manager: Don Olsen Office: Fax: don.olsen@dot.state.fl.us FDOT D7 Traffic Operations FDOT District 7 Traffic Operations Main Office North Malcolm McKinley Drive Tampa, FL Telvent Farradyne Page 41 Revised: 6/2/08

51 Main #: ITS Program Manager: Bill Wilshire Office: ITS Freeway Operations Manager: TBD Office: Mobile: Nextel ID: Traffic Incident Manager: Terry Hensley Office: ITS Project Manager: Robert Lopes, E.I.T. Office: FDOT D4 Traffic Operations FDOT District 4 Traffic Operations 2300 West Commercial Boulevard Fort Lauderdale, FL Fax #: ITS Program Manager: Dong Chen Office: Mobile: dong.chen@dot.state.fl.us ITMS Project Manager: Steve Corbin Office: Mobile: Nextel ID: 158*940*86 steven.corbin@dot.state.fl.us Road Ranger & TIM Team Project Manager: Gaetano Guy Francese Office: Mobile: gaetano.francese@dot.state.fl.us FDOT Public Information Office (PIO) The FDOT Public Information Office provides information to legislators, public officials, department employees, the public, and the media about the department's operations and programs FDOT District 1 PIO Notify the FDOT District 1 PIO of all Level 3 incidents, newsworthy events, and any Level 2 or other incidents with significant traffic impact. FDOT District 1 Public Information Officer For Sarasota and Manatee Counties Telvent Farradyne Page 42 Revised: 6/2/08

52 Cindy Clemmons-Adente or Lauren Hatchell Phone: Toll Free: Off-Hours: Fax: FDOT District 1 Public Information Officer For Collier, Lee, and Charlotte Counties Debbie Tower or JoAnn May Main: Work: (Debbie Tower) Work: (JoAnn May) Toll Free: (Bartow Office) Off-Hours: (Debbie Tower cell) Fax: joann.may@dot.state.fl.us debbie.tower@dot.state.fl.us FDOT District 4 PIO Notify the Palm Beach ITMS or the Broward TMC for all newsworthy events that occur or may impact traffic in FDOT District 4. FDOT District 4 Public Information Officer Barbara Kelleher Phone: Toll Free: Cell: Fax: Barbara.kelleher@dot.state.fl.us FDOT Construction Public Information Officer Christie Klammer Phone: Mobile: cklammer@pbfdot.com I-95 Construction Public Information Officer Palm Beach The Corradino Group Meredith Rapp 321 South Dixie Highway West Palm Beach, FL Office: , x1130 Cell: Fax: mrapp@i95wpb.com FDOT District 7 PIO Notify the FDOT District 7 Tampa Bay RTMC for all newsworthy events that occur or may impact traffic in FDOT District 7. District 7 Public Information Office Telvent Farradyne Page 43 Revised: 6/2/08

53 11201 North McKinley Drive Tampa Bay, FL Main #: Fax #: Toll Free#: Kristen Carson Cell #: Marianne Scorza Cell #: Terry Hensley Cell #: Telvent Farradyne Page 44 Revised: 6/2/08

54 FDOT Maintenance FDOT Maintenance is responsible for maintaining the State Highway System and mobile equipment fleet in the districts. Local maintenance offices are responsible for minor bridge and roadway repairs, mowing, pavement upkeep, roadway signs, rest area maintenance, inspection and operation of movable bridges, and issuance of permits for lane closures, driveways and special uses. FDOT District 1 Maintenance or the appropriate Asset Management Company shall be notified of all damage to infrastructure (barriers, bridges, guardrail, etc.), safety hazards created from live animals, all Level 3 incidents, Level 2 incidents involving substantial fuel spills (>10 gallons), overturned tractor trailers, damage to state property, or when traffic control/diversion equipment is needed FDOT District 1 Maintenance Local FDOT Facilities FDOT District 1 has established seven local operations centers and maintenance yards that provide maintenance and emergency response on the state highway system, except for I-75 and I-275 (see the FDOT District 1 Maintenance Asset Management Firms section below for specific information). While FDOT has contracted the maintenance and emergency response for I-75 and I-275 to the asset management providers, resources are available from the operations centers and maintenance yards under extenuating circumstances. Normal working hours: o Monday Friday from 0700 to 1730 hours Working hours for Collier County: o Monday Thursday from 0630 to 1700 hours After hours calls are taken by an answering service that contacts the appropriate on-call person. Response FDOT Facility Area By County Address 24 Hour Contact Number Collier County Collier 4800 Davis Boulevard Road Department Naples Okeechobee Operations Okeechobee 500 NW 9 th Street Center Okeechobee Sebring Operations Highlands 4722 Kenilworth Boulevard Center Sebring Bartow Operations Polk 2740 SR 60 West Center Bartow LaBelle Operations Glades & 880 West Cowboy Lane Center Henry LaBelle Fort Myers Lee & 2981 NE Pine Island Road Operations Center Charlotte Cape Coral Arcadia Operations DeSoto & SR 70 West & Parker Street Center Sarasota Operations Center Hardee Manatee & Sarasota Arcadia st Street Sarasota Telvent Farradyne Page 45 Revised: 6/2/08

55 FDOT District 1 Maintenance Asset Management Firms The asset manager contractors serve an important role in the operations and maintenance of the interstates in FDOT District 1. This is providing the roadway maintenance, including high mast lighting locates and maintenance, mowing, and rest area upkeep. The ITS Maintenance Contractor provides maintenance for the field devices within the I-75 corridor. The RTMC Building Services Support Contractor provides the maintenance for the SWIFT SunGuide Center building. Maintenance includes repairing and replacing damaged equipment as well as performing preventive maintenance. The maintenance of the building does not include maintaining the ITS LAN and all associated equipment used to control the ITS field devices on I-75. FDOT has several asset management firms under contract to maintain I-75 and I-275. These firms, along with their coverage areas, are given below. County Coverage Area Mile Marker Company Emergency Contact Backup Contact Supervisor Phone All I-75 Bridges ICA, Inc Counties and Structures Collier I ICA, Inc Lee & I DBI Charlotte Sarasota I DBI SR 681 Manatee I-75 I-275 (south of the Skyway Bridge) N & S Skyway Rest Areas DBI David Reichel Area Manager Additional Contact Information: County Asset Management Company Collier ICA, Inc. Mike Myers Javier Rolon David Buser Ernie Molina Lee & Charlotte Sarasota & Manatee Jorgensen Construction Services Jorgensen Construction Services Contact Name Job Title Contact Number Richard Fimbel Mark Perez Paul Sprague Colleen Dalton Richard Fimbel Dave Reichel Paul Sprague Colleen Dalton Superintendent Area Operations Engineer Resident Engineer Regional Manager Project Manager Lead Maintenance Technician Traffic Services Supervisor Corporate Safety Director Project Manager Lead Maintenance Technician Traffic Services Supervisor Corporate Safety Director Telvent Farradyne Page 46 Revised: 6/2/08

56 FDOT D4 Maintenance Palm Beach, Martin, St. Lucie, Indian River Counties The FDOT District 4 Maintenance coverage area includes all limited access highways and state roadways, except for areas with long-term active construction. FDOT District 4 Maintenance will not be contacted directly. All issues involving damage to infrastructure, safety hazards, incidents, fuel spills, overturned vehicles, damage to state property, and traffic control device requests in the District 4 coverage area that requires the attention of FDOT Maintenance shall be directed to the Palm Beach ITMS. The Palm Beach ITMS is responsible for contacting the appropriate FDOT personnel. FDOT District 4 Maintenance Facility Palm Beach County 7900 Forest Hill Boulevard West Palm Beach, FL Working Hours are Monday to Friday from 0700 to 1730 hours. Front Desk: FDOT Maintenance contact order: Mike Atkins Extension 1126 Larry Bauer Extension 1205 Don Archibald Extension 1130 Paul Blanchard Extension 1125 Ricardo Estripeaut Extension 1104 FDOT District 4 Maintenance Facility Martin, St. Lucie, and Indian River Counties 3601 Oleander Avenue Fort Pierce, FL Working Hours are Monday to Friday from 0700 to 1730 hours. Front Desk: After Hours: FDOT D4 Maintenance Broward County The FDOT District 4 Maintenance coverage area includes all limited access highways and state roadways, except for areas with long-term active construction. FDOT District 4 Maintenance in Broward County will not be contacted directly. All issues involving damage to infrastructure, safety hazards, incidents, fuel spills, overturned vehicles, damage to state property, and traffic control device requests in the District 4 coverage area in Broward County that requires the attention of FDOT Maintenance shall be directed to the Broward TMC. The Broward TMC is responsible for contacting the appropriate FDOT personnel FDOT D7 Maintenance The FDOT District 7 Maintenance coverage area includes all limited access highways and state roadways, except for areas with long-term active construction. FDOT District 7 Maintenance will not be contacted directly. All issues involving damage to infrastructure, safety hazards, incidents, fuel spills, overturned vehicles, damage to state property, and traffic control device requests in the District 7 coverage area that requires the attention of FDOT Maintenance shall be directed to the FDOT District 7 Tampa Bay RTMC. Telvent Farradyne Page 47 Revised: 6/2/08

57 The FDOT District 7 Tampa Bay RTMC is responsible for contacting the appropriate FDOT personnel. Telvent Farradyne Page 48 Revised: 6/2/08

58 7.11 Road Ranger Service Patrol Vendors The primary purpose of the statewide Florida Road Ranger Service Patrol is to respond to nonrecurring incidents such as motor vehicle collisions, material spills, and vehicular breakdowns. The response and assistance provided at these incidents helps to reduce the disruption to the traffic stream and improves safety to motorists and other incident scene responders. All services are provided to the public free of charge by the FDOT. FDOT District 1 operates a Road Ranger Service Patrol Program on I-4, I-75 and I-275 in Polk, Collier, Lee, Charlotte, Sarasota, and Manatee Counties. The Road Ranger Service Patrol vehicles are privately owned and specially equipped utility trucks that work under contract to FDOT. Separate contracts may be made through District Construction Projects to provide Road Ranger Service Patrols within construction project limits. The Road Ranger Service Patrol program operates 16 hours per day and 7 days per week. FDOT handles the program administration and oversight. The FDOT District 1 SWIFT SunGuide RTMC serves as the communications hub. The Road Ranger Service Patrol operators work independently while on patrol or performing motorist assists, but work under the direction of on-scene FHP personnel and incident commanders at major incident scenes. The program s key functions are as follows. o Patrol the assigned section of the interstate to locate motorists in need of assistance. o Incident management by notifying the RTMC when the operator detects an incident, or verifying status changes of the incident as they occur, assisting in relocating vehicles from the roadway in accordance with the Move-It Law (including pushing or towing), assisting injured persons until more qualified help arrives, assisting other responders as needed (including acting as a bridge for communications with the RTMC or other centers), clean-up of minor spills from the roadway (including vehicle fluids if nonhazardous and non-cargo), providing temporary MOT devices for traffic control around an incident scene, moving to upstream positions to protect the end of the queue that builds after an incident, and such other duties needed that the operator can safely and completely perform. o Respond to call box actuations o Provide roadside assistance to disabled vehicles, such as providing enough gasoline to get them to a gas station, assisting in tire changes and minor repairs, and other needs of a minor nature. o Remove debris from the roadway, including shoulders, whether associated with an incident, simply reported to FHP, or detected while on patrol. o General observation of the freeway to detect asset damage or suspicious activity. o Serve as goodwill ambassadors to the traveling public as FDOT s point persons in the field Road Ranger Service Patrol Vendor FDOT District 1 Service Patrol at Central Office Traffic Operations website: Anchor Towing & Marine Transport of Broward, Inc. Lourdes Daniel Owner and General Manager 2467 Pembroke Road Hollywood, FL Main: Fax: Telvent Farradyne Page 49 Revised: 6/2/08

59 Road Ranger Service Patrol Vendor FDOT District 7 Service Patrol at Central Office Traffic Operations website: Anchor Towing & Marine Transport of Broward, Inc. Lourdes Daniel Owner and General Manager 2467 Pembroke Road Hollywood, FL Main: Fax: call4tow@bellsouth.net Road Ranger Service Patrol Vendor FDOT District 4 & District 6 Sunshine Towing Contact Numbers Maggie Ramos Alexis Ramos Owner and General Manager Owner and General Manager Cell: Cell: Nextel ID: 158*880*17913 Nextel ID: 158*880*965 Backup: sunshinebroward@cs.com Sunshine Towing Palm Beach County Office: Fax: xxx-xxx-xxxx Gilbert Hernandez Ariadis DeLaCruz Supervisor Shift Lead Cell: Cell: Personal: Sunshine Towing Broward County Office: Fax: Jose Leal Ray Bechero AM Supervisor Weekend Supervisor Cell: Cell: Nextel ID: 158*880*44 Nextel ID: 159*202645*28 Sunshine Towing Dade County Office: Fax: Road Ranger Service Patrol Vendor General Contact Information Contact information for the Service Patrol vendors can be found at the FDOT Central Office Traffic Operations website, Telvent Farradyne Page 50 Revised: 6/2/08

60 7.12 Federal Highway Administration The Federal Highway Administration (FHWA) is a vital partner in ITS. While they provide substantial financial resources for planning, design, construction, and management and operations, they also help in stewarding standards, providing training, and other human-based resources to the corridor Traffic Engineering The overall goal of traffic engineering is to protect motorists and pedestrians, reduce motorist travel time, and aid in the efficiency of roadways. The local/city/county traffic signal engineering departments play a key part in achieving this overall goal in the traffic engineering industry. Most adjacent traffic signals are pre-programmed to work in coordination. When incidents cause a significant traffic impact, the SWIFT SunGuide Center will inform the appropriate traffic signal engineering departments so they can remotely modify the traffic signal timings near the problem area to better accommodate the flow of traffic. ITS related functions that the traffic engineering agencies perform include: o Incident management o Traffic signal control o Signal preemption for emergency vehicles o Monitoring on freeways, inasmuch as it might affect arterial network operations o Monitoring on arterial highways o Development and implementation of freeway control strategies o Road weather detection o Traffic prediction capability o Traffic data archive, data management, and data warehousing o Traffic, incident and construction information dissemination o Dissemination of information via DMS, HAR, cable television, and internet websites o Real time communication to the Emergency Operations Centers o Real time communications to interactive traveler information networks via kiosks, media, ATIS/511, and websites o Real time regional data sharing o Middleware that enables integration among all participating agencies o ITS maintenance management and information o Transportation system performance measuring and assessment District 1 Traffic Operations Engineer L. K. Nandam 801 North Broadway, P.O. Box 1249 Bartow, FL Phone: Fax: Collier County Traffic Operations Department The Collier County Traffic Operations Department staff monitors, maintains, and controls the traffic signals, roadway lighting and signs in unincorporated Collier County. The Collier County Traffic Operations Department will be contacted at the start and end of all Level 3 Incidents in Collier County or that may impact traffic in Collier County. Collier County Traffic Engineering will only receive 20 minute update notifications when their services are Telvent Farradyne Page 51 Revised: 6/2/08

61 requested for an incident. Collier County Traffic Engineering will also be contacted for traffic signal outages, damage, and signal timing problems. Contact Information Main: Main: Lee County Traffic Signals The Lee County Traffic Engineering staff monitors, maintains, and controls the countywide signal system. Lee County Traffic Engineering will be contacted at the start and end of all Level 3 Incidents in Lee County or that may impact traffic in Lee County. Lee County Traffic Engineering will only receive 20 minute update notifications when their services are requested for an incident. Lee County Traffic Engineering will also be contacted for traffic signal outages, damage, and signal timing problems. Contact Information Normal Hours: After Hours: Greg Coggins coggingc@leegov.com Work: Fax: Lee Salley Work: Charlotte County Traffic Signals The Charlotte County Traffic Engineering staff monitors, maintains, and controls the countywide signal system. Charlotte County Traffic Engineering will be contacted at the start and end of all Level 3 Incidents in Charlotte County or that may impact traffic in Charlotte County. Charlotte County Traffic Engineering will only receive 20 minute update notifications when their services are requested for an incident. Charlotte County Traffic Engineering will also be contacted for traffic signal outages, damage, and signal timing problems. Contact Information Main: Fax: After Hours Charlotte County Sheriff s Office Main: Sarasota County Traffic Signals The Sarasota County Traffic Engineering staff monitors, maintains, and controls the countywide signal system. Telvent Farradyne Page 52 Revised: 6/2/08

62 Sarasota County Traffic Engineering will be contacted at the start and end of all Level 3 Incidents in Sarasota County or that may impact traffic in Sarasota County. Sarasota County Traffic Engineering will only receive 20 minute update notifications when their services are requested for an incident. Sarasota County Traffic Engineering will also be contacted for traffic signal outages, damage, and signal timing problems. Contact Information Main: Manatee County Traffic Signals The Manatee County Traffic Engineering staff monitors, maintains, and controls the countywide signal system. Manatee County Traffic Engineering will be contacted at the start and end of all Level 3 Incidents in Manatee County or that may impact traffic in Manatee County. Manatee County Traffic Engineering will only receive 20 minute update notifications when their services are requested for an incident. Manatee County Traffic Engineering will also be contacted for traffic signal outages, damage, and signal timing problems. Contact Information Main: Traffic Communications Center th Terrace East Bradenton, FL Art Chestley Signal Timing Supervisor Work: , x7816 County Traffic Operations Manager Alan Bentley Operations Manager Work: District 4 Traffic Engineering Departments Traffic signal control agencies in FDOT District 4 should not be contacted directly by SWIFT SunGuide Center staff. All traffic signal issues and requests in the appropriate coverage area should be directed to either the Palm Beach ITMS or the Broward TMC Palm Beach County Traffic Engineering The Palm Beach County Traffic Engineering Staff monitors and controls the countywide signal system. A new Palm Beach TMC facility that will house the traffic engineering and FDOT operations departments has been constructed and will be functional by the end of This system is currently being upgraded to include CCTV cameras, DMS, fiber optic communications, as well as control center upgrades (e.g., hardware, software, video wall, monitors). In addition, a fiber optic communication link is being implemented between the Palm Beach County EOC and the Palm Beach County Traffic Control Center that will allow video sharing between the two agencies. Palm Beach County Traffic Engineering Telvent Farradyne Page 53 Revised: 6/2/08

63 Normal Hours Contact: Computer Room: (561) Computer Room Fax: (561) Operator: (561) After Hours Contact #1 After Hours Contact #2 Jason Hoel Jack Hoffman Cell #1: (561) Office: (561) Cell #2: (561) Cell: (561) Home: (561) Boca Raton Traffic Engineering The Boca Raton Traffic Engineering Department is responsible for the signal system in the city of Boca Raton. Contact #1 Contact #2 Tony Chu T. Douglas Hess Office: Office: After Hours: Cell: Broward County Traffic Engineering Division The Broward County Traffic Engineering Division (BCTED) monitors and controls the countywide signal system. Broward County Traffic Engineering 2301 W. Commercial Blvd. Fort Lauderdale, FL Contact: Emmanuel Posadas Office: Fax: District 7 Traffic Engineering Departments Traffic signal control agencies in FDOT District 7 should not be contacted directly by SWIFT SunGuide Center staff. All traffic signal issues and requests in the appropriate coverage area should be directed to the FDOT District 7 Tampa Bay RTMC. District 7 Traffic Operations Engineer Gary Thompson North McKinley Drive Tamp, FL Phone: Fax: Emergency Operations Centers Local emergency operations centers exist to ensure that their jurisdictions are prepared to respond to emergencies, recover from them, and lessen their impacts. In Florida, the emergency operations centers are responsible for the county in which they reside. Each county s emergency operations center (EOC) reports to the State Emergency Operations Center in Tallahassee. Telvent Farradyne Page 54 Revised: 6/2/08

64 The SWIFT SunGuide Center will call the various emergency operations centers to coordinate DMS messaging for tropical storm alerts, hurricane alerts, storm shelter activations, and diversion route planning Emergency Operations Centers in FDOT District 1 Collier County EOC 3301 East Tamiami Trail Building F, Suite #103 Naples, FL Main: Website: Lee County EOC 2665 Ortiz Avenue Fort Myers, FL Main: Website: Charlotte County EOC Airport Road Punta Gorda, FL Main: Website: Sarasota County EOC 1660 Ringling Boulevard Sarasota, FL Main: Website: Manatee County EOC 112 Manatee Avenue West Bradenton, FL Main: Fax: Website: Palm Beach County Emergency Operations Center Palm Beach County EOC 20 South Military Trail West Palm Beach, FL Main: Ops #1: Ops #2: Nextel ID: 159*26*11189 Fax: , Also ext.: 6467, 6468, 6469, 6472 Pager: @messaging.nextel.net Websites: Bob Rehr Telvent Farradyne Page 55 Revised: 6/2/08

65 Office: Cell: Pager: Fax: Dave Messinger Office: Fax: Everette Vaughan Jr. Office: Fax: FDOT Contact at EOC during hurricanes: ESF3 Emergency Storm Function 3 Eric Padron Cell: EOC #1: EOC #2: EOC #3: Broward County Emergency Operations Center Broward County EOC 201 NW 84th Avenue Plantation, FL Work: Telvent Farradyne Page 56 Revised: 6/2/08

66 7.15 Public Safety Answering Points (PSAPS) A Public Safety Answering Point is a facility equipped and staffed to receive emergency and non-emergency calls requesting police, fire, emergency medical, and other public safety services via telephone and other communication devices. A primary PSAP is a facility at which emergency calls are first answered and triaged. The primary PSAP may also be the point from which calls are dispatched. The secondary PSAP is the point to which a primary PSAP transfers calls for service for dispatch or further processing. Unless specifically requested by a local PSAP, the SWIFT SunGuide operations staff will not contact any PSAP agency directly. All direct contact will be executed by FHP dispatch. Telvent Farradyne Page 57 Revised: 6/2/08

67 7.16 Transit Collier Area Transit (CAT), Trolley, & Greyhound Bus Collier Area Transit offers the public CAT bus service within Collier County. CAT buses operate seven days a week from 6 a.m. to 7:30 p.m. (depending on the route). Bus schedules are available on the buses, at Collier County government offices, Collier County libraries, Naples Area Chamber of Commerce locations and various area businesses. Other Collier County Services: The Naples Trolley is a private trolley tour service operating in Naples. (800) Greyhound Bus Line offers regular service into Naples Davis Boulevard Naples, FL Main: Lee County Transit (LeeTran) LeeTran is operated under the authority of Lee County Government and the Lee County Board of Commissioners. LeeTran operates 17 fixed bus routes which last year provided nearly 2.8 million rides to residents and visitors. In addition, LeeTran provides a "Park and Ride" trolley service to and from area beaches. Public transit services are available Monday through Saturday, from 5:00 a.m. to 9:45 p.m., with limited Sunday service on some routes. LeeTran 6035 Landing View Rd. Ft. Myers, FL Phone: (LEE-TRAN) Fax: Charlotte Area Transit & Dial-A-Ride The Dial-a-Ride Service Area includes all of Charlotte County located west of the Myakka River (excluding the bridgeless barrier islands, but including the Charlotte County portion of Boca Grande Island). It serves all of mid-county, located between the Myakka and the Peace Rivers. It also includes the Punta Gorda area, extending as far south as Tropical Gulf Acres, east to the Charlotte County Airport, and north to Peace River Shores on US-17. Service on Burnt Store Road extends to South Punta Gorda Heights (Scham Road). Dial-a-Ride bus service hours: Airport Road Punta Gorda, FL Phone: Monday thru Friday from 0700 to 1800 hours Saturdays from 0900 to 1800 hours Telvent Farradyne Page 58 Revised: 6/2/08

68 Sarasota County Area Transit (SCAT) Sarasota County Area Transit offers the public SCAT bus service within Sarasota County. Sarasota County Transit Administration 5303 Pinkney Avenue Sarasota, FL Contacts: Anthony C. Beckford SCAT Office Transit General Manager Main: Office: Office: Brenda J. Miller Complaints Department Transit Manager Janet Wagnitz Office: Office: Manatee County Area Transit (MCAT) Manatee County Area Transit (MCAT) offers eleven routes serving Bradenton, Ellenton, Palmetto and the Gulf Beach communities of Manatee County. Buses run hourly from 0600 to 1900 hours, Monday through Saturday. No service is offered on Sundays or the following holidays: New Year s Day, Memorial Day, Independence Day, Labor Day, Thanksgiving Day, Christmas Eve (after 1500 hours) and Christmas Day. MCAT fixed routes connect with the FREE Manatee Trolley on Anna Maria Island. Daily service runs from 0600 to 2230 hours every 20 minutes from the Anna Maria City Pier on the north to Coquina Beach on the south. Trolleys offer both air conditioned and open-air seating. Manatee County Area Transit Community Services Department, Transit Division th Avenue East Bradenton, Florida Office: , x227 Telvent Farradyne Page 59 Revised: 6/2/08

69 7.17 Media Media agencies provide additional ways for the SWIFT SunGuide Center to provide traffic information to the public. This includes radio announcements, television broadcasts, newspaper articles, etc. as typical sources Metro Networks Metro Networks provides traffic information to almost all of the media outlets throughout FDOT District 1. Metro Networks should be contacted when any incident affects traffic in FDOT District 1. The preferred method of communication is by telephone. Metro Traffic s regular operating hours are from 0545 to 2400 hours, Monday through Friday, although it is possible that someone may be available in the office at all other times. Contact Information: Metro Networks Main: Fax: Emergency: WGCU (Radio and Television) WGCU provides public radio and TV broadcasting throughout Collier, Lee, Charlotte, Sarasota, DeSoto, Glades, and Hendry Counties. The WGCU is TV 30 and radio frequency 90.1 FM. The affiliated radio station, WKMO, has a frequency of 91.7 FM. The WGCU Newsroom regular operating hours are from 0500 to 1900, Monday through Friday. Contact Information: WGCU Newsroom Main: Fax: Emergency: The News-Press The News-Press is one of southwest Florida s local newspapers. Contact Information: 2442 Dr. MLK Jr. Blvd. Fort Myers, FL (239) Main (800) Subscribe (239) Classified Television Stations Television stations that give regular traffic reports in Southwest Florida are WINK TV, NBC-2, ABC-7, and FOX-4. One of these stations will be approved by FDOT to be placed on the video wall and monitored for traffic reports and traffic related news events by the staff. Telvent Farradyne Page 60 Revised: 6/2/08

70 Radio Stations Radio stations that give regular traffic reports in Southwest Florida are: WINK 1240 AM Fort Myers Website: Traffic Information: Webstream: N/A WNOG 1270 AM Naples Website: Traffic Information: Webstream: N/A WCCF 1580 AM Punta Gorda Website: Traffic Information: N/A Webstream: N/A WCNZ 1660 AM Marco Island Website: Traffic Information: N/A Webstream: N/A (Additional information will be provided by Debbie Tower because she has this information readily available). One of these stations will be approved by FDOT to be placed on the video wall and monitored for traffic reports and traffic related news events by the staff. Telvent Farradyne Page 61 Revised: 6/2/08

71 7.18 The Department of Environmental Protection (DEP) The Department of Environmental Protection is the lead agency in state government for environmental management and stewardship and is responsible for protecting our air, water, and land. DEP responds to incidents that may cause impact to the environment such as large fuel spills, chemical spills, and radioactive material spills. When such an event occurs, the SWIFT SunGuide Center must contact this agency by using the information given below. FDEP 24 Hour Emergency Response Main: Animal Rescue and Removal The following agencies should be contacted, in addition to FHP, whenever a live or dead animal causes a disturbance or safety hazard on state roadways in FDOT District 1. All disturbances and safety hazards in other districts should be directed to the appropriate TMC or RTMC Large Animal Removal and Disposal Live Removal Alligator Removal, Fish and Wildlife Conservation Commission Hours of Operation: 24/7/365 Main: Disposal SWS Environmental First Response Hours of Operation: 24/7/365 Main: Large Animal Rescue By County Collier Domestic Animal Services Normal Hours: After Hours: Lee County Sheriff Main: Charlotte County Animal Control Normal Hours: After Hours: Sarasota County Animal Services Normal Hours: After Hours: Manatee County Sheriff Main: , x1159 Telvent Farradyne Page 62 Revised: 6/2/08

72 7.20 Southwest Florida International Airport (RSW) Southwest Florida International Airport was certified for operation in May 1983 and consistently has outpaced all projections for its growth. The airport now serves more than 7 million passengers annually. It ranks among the 50 busiest airports in the nation and well above the national average for both historic and projected growth. Coordination with SWFIA includes notification to both inbound and outbound travelers of problems at the airport, parking capacity, incidents on I-75, and incidents on nearby arterial roadways. In case of an airport emergency, the SWIFT SunGuide Center will be notified by the Department of Airports. Confirmation of the emergency will be made by a call back to the number listed below. Southwest Florida International Airport Terminal Access Road, Suite 8671 Fort Myers, FL Main: Charlotte County Airport (PGD) Charlotte County Airport is located on Southwest Florida's Gulf Coast in Punta Gorda, Florida. Charlotte County Airport Authority A-1 Airport Road Punta Gorda, FL Main: Sarasota/Bradenton International Airport (SRQ) Sarasota Bradenton International serves over one million passengers a year as a gateway to the southwest Gulf coast of Florida. Major domestic and commuter airlines provide daily scheduled service, as do seasonal international and domestic charter carriers. Sarasota Bradenton International Airport 6000 Airport Circle Sarasota, FL Main: Public Information / Media Relations Michael Walley Office: , ext #4217 Telvent Farradyne Page 63 Revised: 6/2/08

73 8 Field Device Descriptions and Locations Device Device Number Roadway Direction Reference Point Plan # Latitude Longitude CCTV 1 I-75 North North of Indiantown Rd. N26 o ##.### W80 o 0#.### CCTV 2 I-75 North South of Indiantown Rd. N26 o ##.### W80 o 0#.### CCTV 3 I-75 South N26 o ##.### W80 o 0#.### CCTV 4 I-75 North N26 o ##.### W80 o 0#.### CCTV 5 I-75 North N26 o ##.### W80 o 0#.### CCTV 6 I-75 North N26 o ##.### W80 o 0#.### CCTV 7 I-75 South N26 o ##.### W80 o 0#.### CCTV 8 I-75 North N26 o ##.### W80 o 0#.### CCTV 9 I-75 South N26 o ##.### W80 o 0#.### CCTV 10 I-75 North N26 o ##.### W80 o 0#.### CCTV 11 I-75 North N26 o ##.### W80 o 0#.### CCTV 12 I-75 North CCTV 13 I-75 North CCTV 14 I-75 North CCTV 15 I-75 North CCTV 16 I-75 North CCTV 17 I-75 North CCTV 18 I-75 North CCTV 19 I-75 North CCTV 20 I-75 North CCTV 21 I-75 North CCTV 22 I-75 North CCTV 23 I-75 North CCTV 24 I-75 North CCTV 25 I-75 North CCTV 26 I-75 North CCTV 27 I-75 North CCTV 28 I-75 North CCTV 29 I-75 North CCTV 30 I-75 South CCTV 31 I-75 North CCTV 32 I-75 South CCTV 33 I-75 North CCTV 34 I-75 South CCTV 35 I-75 South CCTV 36 I-75 North CCTV 37 I-75 North CCTV 38 I-75 South CCTV 39 I-75 North CCTV 40 I-75 North CCTV 41 I-75 South CCTV 42 I-75 North CCTV 43 I-75 South CCTV 44 I-75 North CCTV 45 I-75 South CCTV 46 I-75 North CCTV 47 I-75 South CCTV 48 I-75 North CCTV 49 I-75 South CCTV 50 I-75 South CCTV 51 I-75 North Telvent Farradyne Page 64 Revised: 6/2/08

74 Device Device Number Roadway Direction Reference Point Plan # Latitude Longitude CCTV 52 I-75 North CCTV 53 I-75 South CCTV 54 I-75 North CCTV 55 I-75 South CCTV 56 I-75 North CCTV 57 I-75 North CCTV 58 I-75 North CCTV 59 I-75 North CCTV 60 I-75 South CCTV 61 I-75 North CCTV 62 I-75 South CCTV 63 I-75 South CCTV 64 I-75 North CCTV 65 I-75 North CCTV 66 I-75 South CCTV 67 I-75 South CCTV 68 I-75 North CCTV 69 I-75 North CCTV 70 I-75 North CCTV 71 I-75 South CCTV 72 I-75 North CCTV 73 I-75 North CCTV 74 I-75 North CCTV 75 I-75 North CCTV 76 I-75 North CCTV 77 I-75 South CCTV 78 I-75 South CCTV 79 I-75 North DMS 1 I-75 North DMS 2 I-75 South DMS 3 I-75 North DMS 4 I-75 South DMS 5 I-75 North DMS 6 I-75 South DMS 7 I-75 North DMS 8 I-75 South DMS 9 I-75 North DMS 10 I-75 South DMS 11 I-75 North DMS 12 I-75 South DMS 13 I-75 North DMS 14 I-75 South DMS 15 I-75 North DMS 16 I-75 South DMS 17 I-75 North DMS 18 I-75 North DMS 19 I-75 South DMS 20 I-75 North DMS 21 I-75 South DMS 22 I-75 South DMS 23 I-75 North DMS 24 I-75 North DMS 25 I-75 South Telvent Farradyne Page 65 Revised: 6/2/08

75 Device Device Number Roadway Direction Reference Point Plan # Latitude Longitude DMS 26 I-75 South MVDS 1 I-75 North N26 o W80 o MVDS 2 I-75 North MVDS 3 I-75 South MVDS 4 I-75 North MVDS 5 I-75 North MVDS 6 I-75 North MVDS 7 I-75 South MVDS 8 I-75 North MVDS 9 I-75 South MVDS 10 I-75 North MVDS 11 I-75 North MVDS 12 I-75 North MVDS 13 I-75 North MVDS 14 I-75 North MVDS 15 I-75 North MVDS 16 I-75 North MVDS 17 I-75 North MVDS 18 I-75 South MVDS 19 I-75 South MVDS 20 I-75 North MVDS 21 I-75 North MVDS 22 I-75 North MVDS 23 I-75 North MVDS 24 I-75 North MVDS 25 I-75 North MVDS 26 I-75 North MVDS 27 I-75 North MVDS 28 I-75 North MVDS 29 I-75 North MVDS 30 I-75 North MVDS 31 I-75 North MVDS 32 I-75 South MVDS 33 I-75 South MVDS 34 I-75 North MVDS 35 I-75 South MVDS 36 I-75 North MVDS 37 I-75 South MVDS 38 I-75 North MVDS 39 I-75 North MVDS 40 I-75 South MVDS 41 I-75 South MVDS 42 I-75 North MVDS 43 I-75 North MVDS 44 I-75 North MVDS 45 I-75 South MVDS 46 I-75 North MVDS 47 I-75 North MVDS 48 I-75 South MVDS 49 I-75 North MVDS 50 I-75 South MVDS 51 I-75 North MVDS 52 I-75 North Telvent Farradyne Page 66 Revised: 6/2/08

76 Device Device Number Roadway Direction Reference Point Plan # Latitude Longitude MVDS 53 I-75 South MVDS 54 I-75 South MVDS 55 I-75 North MVDS 56 I-75 North MVDS 57 I-75 South MVDS 58 I-75 North MVDS 59 I-75 South MVDS 60 I-75 North MVDS 61 I-75 North MVDS 62 I-75 South MVDS 63 I-75 North MVDS 64 I-75 South MVDS 65 I-75 North MVDS 66 I-75 South MVDS 67 I-75 North MVDS 68 I-75 South MVDS 69 I-75 North MVDS 70 I-75 South MVDS 71 I-75 North MVDS 72 I-75 South MVDS 73 I-75 North MVDS 74 I-75 North MVDS 75 I-75 South MVDS 76 I-75 North MVDS 77 I-75 South MVDS 78 I-75 South MVDS 79 I-75 North MVDS 80 I-75 North MVDS 81 I-75 North MVDS 82 I-75 North MVDS 83 I-75 South MVDS 84 I-75 North MVDS 85 I-75 South MVDS 86 I-75 North MVDS 87 I-75 South MVDS 88 I-75 North MVDS 89 I-75 North MVDS 90 I-75 South MVDS 91 I-75 South MVDS 92 I-75 North MVDS 93 I-75 South MVDS 94 I-75 North MVDS 95 I-75 North MVDS 96 I-75 South MVDS 97 I-75 North MVDS 98 I-75 North MVDS 99 I-75 North MVDS 100 I-75 South MVDS 101 I-75 South MVDS 102 I-75 North MVDS 103 I-75 North MVDS 104 I-75 South MVDS 105 I-75 North MVDS 106 I-75 South Telvent Farradyne Page 67 Revised: 6/2/08

77 Device Device Number Roadway Direction Reference Point Plan # Latitude Longitude MVDS 107 I-75 South MVDS 108 I-75 North MVDS 109 I-75 South MVDS 110 I-75 North MVDS 111 I-75 South Device Key: CCTV Closed Circuit TV Camera DMS Dynamic Message Sign MVDS Microwave Vehicle Detection System Telvent Farradyne Page 68 Revised: 6/2/08

78 9 General Operational Concepts 9.1 Incident Detection, Verification, and Response Incidents will be detected by numerous means: o CCTV o FHP Dispatch o Road Rangers o VDS speed detectors o Incident response agencies o Safety barrier cable system o *FHP calls o Media sources o Several other sources not mentioned above Incidents, once detected, must be confirmed prior to initiating activating DMS messages and performing other motorist information activities. Incidents can be confirmed through the following methods. o CCTV o FHP Dispatch when the responding officer is confirmed to be on scene o Road Ranger o Other Traffic Management Centers that verify confirmation in their coverage area o I-75 Construction PIO (when notified by a reliable source on scene) o FDOT District 1 PIO o FDOT Maintenance at the incident scene o FDOT Road Watcher at the incident scene o Local Emergency Operations Centers o SWIFT SunGuide Center and FDOT staff members at the incident scene The SWIFT SunGuide Center will begin the incident response process once an incident is confirmed. Because of the many specifics of the incident response process, please refer to the Incident Management Event Evaluation, Incident Management DMS Response Plan, Incident Management Event Notification, Incident Management Event Monitoring, and Incident Management Event Closure sections of this document for further details. 9.2 Incident Level Definitions The SWIFT SunGuide Center operators must estimate the incident levels of all incidents when they occur. All incidents are classified into three traffic impact categories: Level 1, Level 2, and Level 3. The definition of the three incident categories is given below. Level 1: Incidents of any duration that do not close travel lanes (shoulder incidents, delays, event delays, Amber alerts, etc.) or the "Start Time" to "Clear Time" duration of a lane closing (not road closing) incident is estimated to be less than 30 minutes. Level 2: The "Start Time" to "Clear Time" duration of a lane closing incident is estimated to be 30 minutes or greater but less than 2 hours. This does not include a full closure of the roadway. Level 3: Telvent Farradyne Page 69 Revised: 6/2/08

79 The "Start Time" to "Clear Time" duration of a lane closing incident is estimated to be 2 hours or greater or all travel lanes are blocked on any roadway or ramp. Significant area-wide congestion is expected (but not necessary). 9.3 Incident Level Determination Factors Circumstances influence the determination of the estimated incident level. Some of these circumstances are given below. o An incident must be immediately categorized as a Level 3 incident whenever the incident involves: A total roadway closure An overturned tractor trailer or commercial vehicle (with more than two axles) that blocks at least one travel lane A fuel spill greater than 40 gallons Emergency road work projected to last longer than 2 hours Overnight road work that lasts past 0600 hrs Daytime road work that lasts past 1600 hrs A struck pedestrian that blocks at least one travel lane A fatality or possible fatality that blocks at least one travel lane Any crime scene that blocks at least one travel lane 9.4 Spill Mitigation Guidelines FDOT has adopted this policy to help reduce incident clearance times. This policy contains guidelines for early responders to motor vehicle crashes to reduce the confusion and subsequent delays in reopening roadways when spilled vehicle fluids are involved. These guidelines were developed by the multi agency, Florida Statewide Traffic Incident Management Program (TIMP) to clarify the goals, objectives and processes for clearing the highway of spilled motor vehicle fluids resulting from crashes and other vehicle incidents. The guidelines were reviewed and endorsed by FDOT, Florida Department of Environmental Protection (DEP), and FHP. 9.5 Move It Law This law states that motorists shall move vehicles from travel lanes as soon as possible and do not have to wait for police agencies to arrive before the vehicles can be moved. The Road Rangers have pamphlets that contain the law. These pamphlets also provide a form to transfer information, such as insurance policies and driver s licenses of the parties involved. 9.6 Move Over Act Drivers are now required to "move over" or "slow down" when approaching an authorized emergency vehicle that is stopped on a highway in Florida. This law was designed to protect law enforcement and other emergency workers on Florida highways. The Move Over Act was signed by Governor Jeb Bush on May 1, Drivers approaching a law enforcement or other authorized emergency vehicle with emergency lights activated while parked on an interstate highway or a roadway with two or more lanes are required to vacate Telvent Farradyne Page 70 Revised: 6/2/08

80 the lane closest to the emergency vehicle, as soon as it is safe to do so. Drivers are also required to slow down to a speed that is 20 miles per hour less than the posted speed limit when the posted speed limit is 25 miles per hour or greater. Drivers must slow to 5 miles per hour when the posted speed limit is 20 miles per hour or less. Telvent Farradyne Page 71 Revised: 6/2/08

81 9.7 Open Roads Policy The Open Roads Policy is an agreement between FHP and FDOT to expedite the removal of vehicles, cargo, and debris from the roadways on the State Highway System to restore a safe and orderly flow of traffic following incidents on Florida s roadways. The specific goal is to clear the travel lanes of roadways within 90 minutes of the arrival of the first responding FHP officer. Telvent Farradyne Page 72 Revised: 6/2/08

82 9.8 Event Timelines Event timelines document the flow of activities throughout the life of the event. They are used by agencies to review responder activities and identify areas for improvement. Many agencies, such as fire rescue, hold internal staff meetings to review their agency s performance after responding to an event. Because there are many different agencies responding to major events, however, it is beneficial to have event review meetings with all responding agencies. These meetings are typically referred to as Post Incident Analysis. FDOT facilitates the multi-agency post incident analysis of major events at the bi-monthly Traffic Incident Management (TIM) Team meetings. With the implementation of SunGuide software, FDOT has the capability to create chronology reports that provide the data needed to create timelines. Therefore, this is just another example of why the SWIFT SunGuide Center staff must log all important activities into the SunGuide event reports in a timely and accurate manner. The Event Timeline Graph shown below, shows the typical activities documented in event timelines. The order of the activities may vary. For example, the Road Rangers may detect the event before FHP receives a 911 call or an SWIFT SunGuide Center operator may detect an event with a CCTV before being otherwise notified. Therefore, this timeline is general in nature and is not intended to reflect every possible order of activities. Telvent Farradyne Page 73 Revised: 6/2/08

83 9.9 First Responder Checklist The directives and on-scene incident strategy of the first response agencies should be known by the operators so the SWIFT SunGuide Center can use the resources necessary to properly respond to events in FDOT District 1. The First Responder Checklist is given below. First Responder Checklist: 1. Overview of scene details. Exact location, including direction and lanes blocked. 2. Injuries? Persons trapped? (Give number and severity) 3. Fire or HazMat potential? 4. Can vehicles be moved out of traffic NOW? 5. Give directions to approach and park. 6. Special investigation needed? 7. Tow truck and clean-up needs. 8. Location for staging back-up units. 9. Upstream diversion needed? 10. What level of motorist information is needed? 11. Is there an off site location to relocate the damaged vehicles? 9.10 Dynamic Message Sign Strategies The FDOT District 1 Dynamic Message Signs (DMS) are all located on I-75 throughout the coverage area. Messages on these DMS advise motorists of adverse conditions ahead and may sometimes suggest a course of action. The adverse conditions mentioned above include incident, construction, recurring congestion, Amber Alert, and special event advisories. When appropriate, the DMS will also display alternate route diversion information. A secondary use of DMS is for real-time and advance notice construction advisories. Use of the DMS for this purpose is coordinated through FDOT Maintenance or the FDOT District 1 asset management company. The key consideration when using a DMS is to recognize the limited amount of information that can be delivered. DMS messages must be well crafted to provide just the essential information. The default messages for DMS will be travel time messages. Public service, advertising, or other non-traffic related messages will not normally be displayed. Amber Alert messages will be posted in accordance with guidelines established by FDLE and FDOT. Message libraries have been developed and entered into the SunGuide system. In cases where free-form messages need to be posted, approval must be obtained from the RTMC Shift Supervisors, RTMC Operations Supervisor, or the RTMC Operations Manager. Telvent Farradyne Page 74 Revised: 6/2/08

84 9.11 Definition of At and Past an Exit To consistently relay location information to motorists, the definitions of AT an exit and PAST an exit need to be clearly defined. If a motorist can use the exit ramp to exit the highway and use the entrance ramp to reenter the highway without ever physically passing the incident scene, the incident is considered to be AT the exit. All other areas are considered to be PAST the previous exit. The image below shows a visual representation of the above definition. Telvent Farradyne Page 75 Revised: 6/2/08

85 9.12 Definition of At, Before, and Beyond an Exit A visual example of the definitions of AT, BEFORE, and BEYOND an exit is given below Definition of Commercial Vehicle According to of the Federal Motor Carrier Safety Regulations, a Commercial Motor Vehicle is... Any self-propelled or towed motor vehicle used on a highway in interstate commerce to transport passengers or property when the vehicle: Has a gross vehicle weight rating or gross combination weight rating, or gross vehicle weight or gross combination weight, of 4,536 kg (10,001 pounds) or more, whichever is greater. 1. Is designed or used to transport more than 8 passengers (including the driver) for compensation. 2. Is designed or used to transport more than 15 passengers, including the driver, and is not used to transport passengers for compensation. 3. Is used in transporting material found by the Secretary of Transportation to be hazardous under 49 U.S.C and transported in a quantity requiring placarding under regulations prescribed by the Secretary under 49 CFR, subtitle B, chapter I, subchapter C. Telvent Farradyne Page 76 Revised: 6/2/08

86 9.14 Fifty Miles an Hour Rule This accepted rule was developed by several members of the Telvent Farradyne project staff and can be found in the NHI IM course CD. Please note that this rule considers the minimum amount of DMS activation. Additional DMS may always be activated when conditions warrant. Section 12-2 states: If determined to be of long duration, notify motorists 50 miles back for every anticipated hour of duration. This will reduce the amount of traffic approaching the area. Establish well marked alternate routes. Section states: Background: One of the important areas of traffic management for an incident is to deal with motorists far enough away from the site to permit diversion, voluntary or otherwise. The 50/1 Rule means that for every hour of anticipated disruption of traffic at the scene, motorists should be advised 50 miles in advance of the area. Example: A two-hour anticipated disruption would require notice to motorists within a 100 mile radius. This notification will allow motorists the option of choosing alternate routes. This can be a very effective means of managing traffic and reducing the amount approaching the scene. Use of the media or include the media on the team, and DMS to alert traffic well in advance of the scene will enhance site management. Section states: EXERCISE CHALLENGE: Information about the incident needs to be disseminated in a radius of 50 miles for every expected hour of duration. Each group will be asked to establish what actions they would recommend for proper handling of the clearance process for this scenario. o Each group will present their findings to the class. o Develop a traffic management plan that requires a more global scope including diversion routes and motorist information using the 50 MPH rule. Telvent Farradyne Page 77 Revised: 6/2/08

87 10 SunGuide TM Software Description The SunGuide TM software was developed by SwRI for the FDOT Central Office to provide a common software platform for all TMC Operations in the state of Florida. The SunGuide TM software has the capability to control field devices (CCTV, DMS, etc.), post travel times on DMS, collect event data, create performance measure reports, and manage/dispatch Road Rangers. The SunGuide TM software is still in the development stages and will eventually include the capability of controlling ramp meters, and streamlining center-to-center communications. The SunGuide TM software comprises of two parts: o Event Management / Performance Measures (EM/PM) o SunGuide Software Incident Management (IM) Module EM/PM functions as a data entry tool and serves as the systems event creation and tracking program. The SunGuide software IM Module allows for the monitoring and interaction with the field equipment Event Management / Performance Measures (EM/PM) The following sections provide an overview of the Event Management / Performance Measures module in the SunGuide software. For more detail instructions on how to use this and other modules in SunGuide software, refer to the latest SunGuide Software Users Manual. Updates to the SunGuide User Manual can be obtained from The FDOT District 1 SunGuide Southwest RTMC uses the EM/PM module of the SunGuide software to collect, store and disseminate information about incidents along the roadways actively managed by the RTMC. Through various input screens, information about incidents is entered by the TMC Operator. The main objectives of SunGuide event management are: o Traffic Event and Incident Management o Information Dissemination to the Public o Road Ranger Dispatch o Reporting and Tracking Roadway Impact o Sending Incident Notifications to Incident Responding Agencies EM/PM - Main Screen The main screen is the first screen to appear once the user is logged into SunGuide. This screen contains a series of options at the top of the screen: Event List, Block CCTV, Road Rangers, Reports, Audit, and Logout. Below these options is an area to search for a specific event or range of events. In addition to these options, there is a section for VDS Alerts, Safety Barrier Cable System Alerts, and Currently Blocked CCTVs. o Event List Window The Event List Window contains a list view of current events grouped by status. Each event listing displays the Event ID, Event Location, Primary Vehicle, Event Type, Blockage, Road Ranger, Organization, Operator, Date Added, and Date Last Updated. By single clicking on an event in the Event List window opens the event for viewing and editing. The event status definitions are described below: Active An active event has been confirmed via Road Ranger, CCTV, or FDOT personnel on-scene. The RTMC Operator must have confirmation from one of these units before making the event active. Once active, the event is listed as Active With Travel Lane Blockage or Telvent Farradyne Page 78 Revised: 6/2/08

88 Active With No Travel Lane Blockage, depending on the situation. Unconfirmed An unconfirmed event has not been verified by a Road Ranger, CCTV, or FDOT Personnel on-scene. Once the unconfirmed event is verified, it moves to an Active Status with or without travel lane blockage depending on the situation. Unresolved An unresolved event is one that the RTMC has managed and assisted, but the vehicle remains on the shoulder. Once the vehicle is removed from the shoulder, it will be moved to Closed status. Closed A closed event is one that the RTMC has managed and assisted. The vehicle is not obstructing any lanes, including shoulders. Once the vehicle is moved into the Closed status, the event can no longer be accessed from the Event List window. False Alarm Verified events that have been saved to the system and cancelled prior to arrival of any responders. For example: the RTMC operator detects a disabled vehicle on the shoulder with a CCTV and then dispatches a Road Ranger. While the Road Ranger is in route, the RTMC operator sees the disabled vehicle drive away. Void Events that have been entered in error (e.g., duplicate events). Audit Reopens the event for editing. Please note that this function requires the proper permissions and can only be performed with FDOT approval. o Block CCTV Images On some occasions, it is necessary to block a camera s image feed from the public viewing. This feature becomes a vital feature of SunGuide when the incident involves injuries and the images are sensitive to the general public. o Road Rangers The Road Rangers option is used to create, update, and maintain the Road Rangers beat schedule and details. This section prompts for the Truck #, Status, Date, Driver, Beat, and Radio of the Road Ranger. See the Road Ranger Dispatch section of this document for additional details. o Reports The Report feature allows the RTMC operator to quickly print out a chronology of activities for each event. This can be used to facilitate the transfer of information during shift change. The Report feature is also used to provide quality control on data and report performance measures. o Audit This section requires special permissions that shall be determined by the RTMC Operations Manager and is used to modify event details. Some examples of event details that can be changed are Road Ranger Status, Time Reported to the TMC, Notifying Agency/Contact, and Event Location. o Automated VDS and Cable Barrier Detection Alerts Located on the right hand side of the Event List is a series of alerts and messages used to remind the RTMC operator of specific event details. The System Alerts section of the Event List enables the RTMC operator to respond faster to incidents. It lists the type of detection, CCTV or Cable Barrier Detection Device, used to detect the event and the elapsed time since initial detection. o Currently Blocked CCTV Cameras This area provides the RTMC operator a snapshot view of all currently blocked CCTV cameras. When a CCTV image is blocked, the CCTV ID and length of time it has been blocked will be listed in this section. Telvent Farradyne Page 79 Revised: 6/2/08

89 EM/PM - Event Detail Window The event detail window contains all the information specifics related to an event. This screen will display the Operator, Event ID, Create Date, Create Time, FHP Incident No., Organization, Notifying Agency, Notifying Contact, Status, Status Changed Date/Time, Type of Event, Attributes, Vehicle Description, Location, Vehicles Dispatched/Assisting/Activities, Conditions, Lane Blockage, Responding Agencies, Primary/Secondary Associated Events, and Comments. In addition to the preceding information, you can also access the External Communications window and Clone Event. See below for more information on specific features and functions contained in the Event Detail window. o Administrative Details This section can only be controlled by a user designated as an Administrator and contains event ownership and status details. The RTMC operators name, date/time event was created, current status, and the last date/time event was updated can be viewed in the Administrative Details. In addition, the event ownership can be taken in this section. o Reporting & Dispatch The Reporting and Dispatch section contains the event notification and dispatching information. The notifying organization, agency, and contact information is maintained in this section. In addition, the dispatching and updating of Road Ranger activities are managed here. See the Road Ranger Dispatch section of this document for more details. o Responders Notified This section is located to the right of the screen, and is for documentation of responders notified by the RTMC, responders who notified the RTMC, and the arrival and departure of each event responder. o Impact on Roadways The Impact on Roadways section contains the event location, congestion information, lane blockage, External Communications, anticipated clearance time, and alternate routes. Event Location It is essential for the location description to be entered in as accurately and precisely as possible. To determine the event location, make use of the available maps, and develop your knowledge of roadway locations in the geographical coverage area to the point where you can recognize cross streets at a glance while using the CCTV or receiving information from others sources. Note: Event Location must be entered from top to bottom as each successive list is populated based on the selection from the previous list. Lane Blockage The Lane Blockage section can be modified to correctly represent the lane structure of the event location. The lane configuration can be modified to add or delete Travel Lanes (up to eight), Right and Left On/Off Lanes, Right and Left Entrance/Exit Ramps (up to three lanes) and Right and Left Shoulder. It is important to utilize this modification to correctly represent the lane obstruction. When a lane blocking event is detected and not verified, click on the lane until a? is displayed. When the lane blockage is confirmed, change the? to. Telvent Farradyne Page 80 Revised: 6/2/08

90 External Communications The External Communications section is used for sending Incident notifications. messages are automatically generated by the system based on information entered in the Event Detail window. o Event Details The Event Details section contains FHP Incident Number, the event type, several other event attributes, Clone Event function, vehicle information, primary and secondary events, injuries, and weather conditions. In addition, one can also access the External Communications window, Clone event as Abandoned Vehicle, Generate Event Chronology Report, and Block CCTV Images. Vehicle Information The Vehicle Information will contain the color, make, model, tag ID, and state issued. When a duplicate tag is entered in SunGuide, the system will generate a tag alert notifying the RTMC operator of the vehicle s service history. Clone Event When the event changes significantly, such as accident to abandoned vehicle or disabled vehicle to abandoned vehicle, it is important to clone the event, link the cloned event to the original incident, and continue managing the cloned event until completed or another cloned event needs to be created. This ensures that the incident retains the original event type. The Clone Event function will take the contents of the already generated (original) event and copy these details to the newly generated event. Once the Road Ranger leaves the scene, the event status shall be changed from active to unresolved. As the Road Ranger patrols and passes the event, it shall be noted if the owner is still with the vehicle and waiting for a tow. If the owner leaves, then a second event (abandoned vehicle) shall be created using the Clone Event feature and the original event closed. Please note: the Road Ranger must be departed from the event before the event can be cloned. Also, if the clone event function is applied to disabled vehicles, then all the event information (including vehicle information) is copied to the new event. If the clone event function is applied to another type of event, then only the location of the event is copied. o Comments and Event History The comments section allows the operator to document pertinent information about the event. There are some situations where documentation into comments is necessary, such as hour monitoring of roadwork and checking on the status of abandoned vehicles. The Event History is an area that is automatically populated by the system as the RTMC operator is entering information EM/PM - Report Feature The SunGuide system has a Report feature which offers the RTMC operator the ability to search and analyze event details and trends. Within the Report window, there are a series of filters that can be used to narrow the search parameters. The following reports are available. o Event List o Event Details o Event Summary o Chronology o Event Response Telvent Farradyne Page 81 Revised: 6/2/08

91 o Agency Response o Level o Lane Blockage o DMS o Camera Blockage o Road Ranger o Road Ranger Administration o Road Ranger Administration Summary o Road Ranger Administration Details o Road Ranger Cost Savings o Quality Assurance (QA) o Void Road Ranger o FHP Request o Notification List Contacts o Chronology short o VDS Usage o Motorist Calls 10.2 SunGuide Software Incident Management Module As previously stated, the SunGuide software Incident Management (IM) Module enables the user to monitor and interact with the field equipment. Specifically, this module allows DMS, CCTV, and video wall control functions. These controls provide the RTMC operators with the necessary tools to effectively monitor the progression of multiple incidents simultaneously. The SunGuide IM Module also contains an algorithm that uses occupancy, volume, and speed data to make a determination of a probable incident, based on user-defined thresholds IM Module - Dynamic Message Sign Control The SunGuide software IM Module allows RTMC operations staff to activate pre-programmed DMS messages in the field for abnormal traffic conditions and other RTMC events. The SunGuide software IM Module offers two ways to activate these messages. o Individual DMS message activation o DMS response plan The individual DMS message activation method is accomplished by the user selecting a preprogrammed DMS message from the message library and activating that message on one or more DMS. The DMS response plan is an automatically generated SunGuide system DMS message activation function. The module evaluates user-defined criteria such as location, lane blockage, and search distance from the incident to the DMS locations. From these criteria, the module develops a suggested messaging plan. This function is intended to reduce the time to post messages to DMS and improve overall operations IM Module - Closed Circuit Television (CCTV) Control The SunGuide software IM Module allows for the operation of the CCTV system. By using the SunGuide Camera Control and Video Switching, the RTMC operations staff can move a camera, check the operational status of the camera, store presets, and lock the camera preventing others from using the camera. Telvent Farradyne Page 82 Revised: 6/2/08

92 IM Module - Video Wall Control The SunGuide software IM Module allows for the control of the RTMC video wall. The RTMC operations staff can configure the placement of the cameras on the video wall by simply clicking on the desired CCTV and dragging it into an available source. There are multiple layouts which are predefined placements of the cameras which can be used to auto-populate the video wall. Telvent Farradyne Page 83 Revised: 6/2/08

93 11 SunGuide Software Data Management Incident information is entered by the SWIFT SunGuide Center operators through various input screens in SunGuide Data Entry Steps There are three steps to entering this data into SunGuide: 1. Input Input all traffic related events accurately and concisely 2. Monitor and Update Monitor active events regularly and frequently. Update events as conditions warrant a. Notification, arrival, and departure of responder(s) b. Lane blockage pattern c. Closure and termination of event 3. Clear Verify that incident information was entered properly and close the event Input To enter event information into SunGuide, the following information needs to be obtained: o Event Type o Notifying Agency and Contact o Event Location o Lane Blockage o Event Conditions o Specific Attributes o Vehicle Information Once an event has been detected and the preceding information has been obtained, begin entering the data into SunGuide. The system primarily utilizes drop-down lists, sub forms, and check boxes which enable easy event data entry. Enter a new event using the following process: o Located on the top of the main screen, click the Add Event button. You will be directed to a new window, which will prompt you for the following: Event Type (i.e., Accident, Disabled Vehicle, Debris) Notifying Agency (i.e., FHP, Road Ranger, CCTV) Notifying Contact (i.e., 911, T01, 935) Status (Unconfirmed, Active) o After the preceding information is entered, click the Create this Event button. The user will be directed to the Event Detail window, which will contain the specifics of the event. Enter the details in the following order: Event Location (County, Road, Direction, Relationship to Exit, Exit, Proximity to Exit) Lane Blockage (i.e., Left Shoulder, Left Lane, Center, Right Lane, Right Shoulder) Attributes (HAZMAT, Fire, Rollover) Vehicle Involved (Color, Make, Model, Tag ID, State) Primary/Secondary Events (if applicable) Injuries (if applicable) Weather Conditions (Pavement, Precipitation, Wind, Visibility, Illumination) Comments (Additional Event Details) Telvent Farradyne Page 84 Revised: 6/2/08

94 After the preceding information is entered, click the Save Changes button. The Event Detail window will refresh. o Next, enter the dispatch information. Click the Dispatch link located under the Reporting and Dispatch section. The section will expand and prompt for the following: Process (Arrive, Dispatch, Depart, Cancel, Activity, Status) Vehicle (Road Ranger Truck Number) Status (The Status drop-down list is only used when Arriving a vehicle. The system defaults to Assist- Motorist. Either change this value or skip to the next step. Activity (i.e., Debris, Flat Tire, Fuel, Jump) After you have entered the preceding information, click the Submit button. To minimize the section, simply click Dispatch link. o Update the Responder Table by clicking in the applicable agency row and status column. Make sure the times are accurate. o If applicable, send an Incident Alert Notification located in the External Communications section. Click the External Communications link located under the Impact on Roadways section. The section will expand and prompt for the following: Subject (Active Level 2, Active Level 3, Cleared, Amber Alert) Event Group (Level 3, Level 2, District 6, Testing, Construction, Amber Alert) Review the Title, Location, Body, and Footer and ensure the contents are correct. If satisfied with the contents, request approval from the RTMC Operations Supervisor. If approved, click the Send button. o Throughout the duration of the event, input additional event details in the Comments section. o Click the Save Changes button each time a new event is added Monitor and Update It is imperative that events are continuously monitored and updated as conditions change. When a notifying and/or responding agency informs the SWIFT SunGuide Center of changes, the SWIFT SunGuide Center operator is required to immediately update the information in SunGuide. This ensures the accuracy of the event data and ultimately the integrity of the system. o To modify an event in SunGuide, simply click on the event located in the Event List window. o Make the necessary changes. o Click the Save Changes button each time you make a change to an event Clear Once an event has been confirmed cleared, review the Event Detail screen to ensure all required and relevant information has been entered. Before closing an event, make certain all applicable agencies have been notified and documented correctly. By ensuring the Event Detail is complete, the user is enabling the data to be consistent and to accurately be reflected in the SWIFT SunGuide Center Performance Measures. o To change the status of an event or to close an event in SunGuide, simply click on the event located in the Event List window. Telvent Farradyne Page 85 Revised: 6/2/08

95 o Change the Status located under Administrative Details to reflect the current position of the event (Unconfirmed, Active, Closed, Unresolved, False Alarm, Void, Audit). o Review the event details. Make any necessary changes. o Click the Save Changes button Block CCTV Images On some occasions, it is necessary to block a cameras image feed from public viewing. This feature becomes a vital feature of SunGuide when the incident involves injuries and the images are sensitive to the general public. The RTMC Shift Supervisor is required to block any necessary CCTV cameras. SWIFT SunGuide Center operators share this responsibility, but it is possible that SWIFT SunGuide Center operators may not have the system privileges to do this task. To block a camera, o Click the Block CCTV Images button located on the top menu bar of the Event List window. You will be directed to a new page which lists all of the SWIFT SunGuide Center cameras. o Locate the camera that is to be blocked. o Click the Block button located to the right of the camera detail. To unblock a camera, o Click the Block CCTV Images button located on the top menu bar of the Event List window. The user will be directed to a new page which lists all of the SWIFT SunGuide Center cameras. o Locate the camera that is to be to unblocked. o Click the Unblock button located to the right of the camera detail Road Rangers Located on the top menu bar, there is a Road Ranger option which allows the SWIFT SunGuide Center operator to set up the Road Ranger schedule. The Road Rangers use two shifts, so the schedule needs to be modified during shift changes and when changes are made throughout the day. To create a new Road Ranger schedule, o Click the Road Rangers button located on the top menu bar of the Event List window. The user will be directed to a new page which displays the schedule details. o Select the Vehicle. o Select the Status, such as Patrolling. o Select the Driver field to correspond with the Vehicle number. o Select the Beat. o Select the Radio. o Click the Save button. o Repeat until all trucks have been entered. To modify an existing Road Ranger schedule, o Click the Road Rangers button located on the top menu bar of the Event List window. The user will be directed to a new page which displays the schedule details. o Select the Vehicle that is to be modified. o Next, select the Status, such as Meal or Break. o Make sure the Driver field corresponds with the Vehicle number. o Make sure the correct Beat is listed. o Make sure the correct Radio is listed. Telvent Farradyne Page 86 Revised: 6/2/08

96 o Click the Save button SunGuide Reports Located on the top menu bar of the Event List window, there is a Report feature which offers the SWIFT SunGuide Center operator the ability to search and analyze event details and trends. Within the Report window, there are a series of filters that can be used to narrow the search parameters. There are five categories of reports which make up 21 report types. The following list gives the different report types o Event List o Event Details o Event Summary o Chronology o Event Response o Agency Response o Level o Lane Blockage o DMS o Camera Blockage o Road Ranger o Road Ranger Admin o RR Admin Summary o RR Admin Details o RR Cost Savings o QA o Void Road Ranger o FHP Request o VisioPaD Usage o Notifier Contacts o Motorist Call o Chronology - Short o Performance Measures Reports Manager There are many occasions where printing a hard copy report is required. To access a report, follow these steps: o Click the Reports button located on the top menu bar of the Event List window. The user will be directed to a new page which lists all of the report types. o Narrow the search parameters by setting filters, by the range of events, location, and event properties. o After the filters are set, click the desired report type listed to the right of the filters. o The user will be directed to a new window, which you can either view and/or print the report Audit This section is used to modify event details and requires special permissions that shall be determined by the RTMC Operations Manager. Some examples of event details that can be changed are Road Ranger Status, Time Reported to the TMC, Notifying Agency/Contact, and Event Location Preferences Telvent Farradyne Page 87 Revised: 6/2/08

97 This portion of SunGuide allows the SWIFT SunGuide Center operator to create page refresh preferences. The SWIFT SunGuide Center operator can indicate the exact time the Event List is refreshed. In addition, the SWIFT SunGuide Center operator can receive a warning on events that has lapsed the indicated time allowance Video Detection Alerts Located on the right hand side of the Event List in SunGuide is a section used for automated video detection alerts. These alerts notify the SWIFT SunGuide Center operator of an active traffic event. By single-clicking on an alert in the Automated Detection Alert section, the event can be opened for creation and management. When you click the first event listed on top, a pop-up window will appear. This window will contain the Type, Camera, and Location. There are six options which the SWIFT SunGuide Center operator can choose: 1. Create New Event a. When this option is selected, a pop-up window will appear. b. This page just confirms that you want to create a new event. Click the Finish button. c. Once the Finish button is selected, you are directed to the Event Detail window. d. Build the event as any other event, except please note the following. i. Type of Event: This field defaults to Disabled Vehicle. The user will need to check this field to make sure it is correct, and otherwise change it to the correct event type. ii. Location: Check the location to make sure it has the correct Direction, Relationship, and Exit. iii. If the vehicle left before building the event: Select Other as Event Type. Include a Comment stating Vehicle Left. Close the event (Do not Void the event). e. Follow standard incident management procedures for active traffic events. 2. Create Secondary Event a. When this option is selected, a pop-up window will appear. b. The user is prompted to select the Primary Event from the drop down list. Once the event is located in the list, click the Finish button. i. Please notice the check box located below the selection of events: Filter event list above by distance from camera. This option will narrow down the selection of events based on a range between the event detected and the camera. c. Once the Finish button is selected, the user is directed to the Event Detail window. d. Build the event as any other event, but as with the Create New Event option, please make sure to check the Type of Event and Location. i. If the vehicle left before you building the event: Select Other as Event Type. Include a Comment stating Vehicle Left. Close the event (Do not Void the event). e. Follow standard incident management procedures for ATE. 3. Set Responder Arrival a. When this option is selected, a pop-up window will appear. b. This page will prompt you to assign a responder arrival to an event. c. Locate and select the event from the drop-down list. Telvent Farradyne Page 88 Revised: 6/2/08

98 i. Please notice the check box located below the selection of events: Filter event list above by distance from camera. This option will narrow down the selection of events based on a range between the event detected and the camera. d. Next, locate and select on the applicable responder. e. If the Responder selected was either a Road Ranger, the user is then required to select the Truck Number from the drop-down list. f. Click the Finish button. Once the Finish button is selected, the user is directed to the Event Detail window. g. Please notice the selected responder is updated in the Responder Notification table. 4. Dismiss as Already Detected a. When this option is selected, a pop-up window will appear. b. This window will prompt you to select the already established event. c. Locate and select the event from the drop-down list. i. Please notice the check box located below the selection of events: Filter event list above by distance from camera. This option will narrow down the selection of events based on a range between the event detected and the camera. d. Click the Finish button. Once the Finish button is selected, the window closes and the user is returned to the Event List Window. 5. Dismiss as False Alarm a. When this option is selected, a pop-up window will appear. b. This window will prompt the user to select the reason why the detected event is a false alarm. Currently, there are ten reasons why the event detected is a false alarm: i. Out of our Jurisdiction ii. Off-highway Other iii. Off-highway Vehicle iv. Poor Video v. Roadway Reflection vi. Rain on Lens vii. Shadow viii. Sign ix. Too much sky x. Congestion c. Click the Finish button. Once the Finish button is selected, the window closes and the user is returned to the Event List Window. Once a Video Detector System event has been handled with one of the six options, the event will be removed from the SunGuide system alerts section Currently Blocked CCTV Images Located on the right hand side of the Event List in SunGuide, is a section used for currently blocked CCTV images. This section lists cameras which have been blocked from website viewing. Telvent Farradyne Page 89 Revised: 6/2/08

99 12 Road Ranger Service Patrol Procedures SWIFT SunGuide Center operators will monitor, coordinate, and dispatch the Road Ranger Service Patrol vehicles in FDOT District 1. The SWIFT SunGuide Center is also responsible for entering all Road Ranger activities into the SunGuide system. This section describes the responsibilities and specific actions the SWIFT SunGuide Center staff needs to perform to effectively dispatch and utilize the Road Ranger Service Patrol program Road Ranger Service Patrol Coverage Area FDOT Districts 1 and 4 jointly fund the Road Ranger Service Patrol program in Collier and Broward Counties respectively on the Alligator Alley section of I-75. FDOT District 1 funds the Road Ranger Service Patrol program in Lee, Charlotte, Sarasota, and Manatee Counties. The RTMC dispatches the Road Ranger trucks on a 16 hour schedule 7 days per week. Schedule is subject to change with available funding and/or construction projects. See Attachment A for a current schedule. Additional details are given below. o Coverage in Collier County (54 miles). This beat covers (37.5 miles) of Alligator Alley from the West tollbooth up to the Broward County Line. o Coverage in Lee County (35 miles) o Coverage in Charlotte County (29 miles) o Coverage in Sarasota County (27 miles) o Coverage in Manatee County (43 miles). This beat also covers I-275 including the Sunshine Skyway Bridge in Hillsborough and Pinellas Counties up to the North Rest Area Maps and Operational Aids Create a map with the beat locations and insert here. Samples: Telvent Farradyne Page 90 Revised: 6/2/08

100 Telvent Farradyne Page 91 Revised: 6/2/08

101 o o o o o o 12.3 AVL and Road Ranger Service Patrol Rules Per FDOT Each driver can only be assigned to one truck at a time First status of the day must be START SHIFT Can't set the status back to START SHIFT until END SHIFT is selected When the status is END SHIFT, only the START SHIFT status should be available for selection Active Road Rangers must have driver and beat assigned SIRV vehicles can be dispatched without requiring a beat Beats can be assigned more than once Must be compatible with tablets Dispatched trucks should be shown on event list in regular format, arrived trucks in bold Cannot arrive a truck which is still on-scene at another event o Trucks should not be included in the dispatch dropdown of the GUI if their current status doesn't have the "Available for Dispatch" property set to true This includes "Out of Service" o A Road Ranger truck which is the notifying contact when an event is created should automatically be dispatched and arrived at the event, and Road Ranger agency notified and on-scene timestamps should be automatically set as well o A truck must be on-scene before an activity can be performed Activities cannot be entered if the truck is cancelled, dispatched, or departed o A truck can be cancelled before it arrives but once it arrives it cannot be cancelled, it must be departed o Cannot depart a truck until at least one activity is selected o Can only change truck status to other assisting status types if the truck is on-scene Cannot change to Patrolling, Meal, break, etc. o Cannot close events with dispatched or on-scene Road Rangers Notify the operator of the specific reason why the event cannot be closed o Upon arrival of the truck, set the truck status to Assist-Motorist (when Assist-Motorist is the default assisting status) o Upon departure of a truck automatically change status to Patrolling o Only display the departure in the responder table when all vehicles for the agency have departed If one Road Ranger leaves the scene but another one is still there, wait until the second one leaves to populate the Road Ranger agency departed timestamp in the responder table 12.4 Shift Start and Shift End The RTMC receives a schedule, by fax, from the Road Ranger Service Patrol contractor before the start of every scheduled Road Ranger shift. This list includes the number of Road Ranger vehicles that will be represented on the roadway, the name of the individual drivers, the numbers of each driver s truck, the cell phone number used by the drivers, and the zones each driver will be working that day. The RTMC operators are responsible for verifying this information when it is received. This task is vital for the RTMC staff so they can efficiently dispatch the Road Rangers throughout the day. Road Ranger Service Patrol operators should not leave their shifts until they receive authorization from the RTMC. When a Road Ranger Service Patrol operator receives a request for service or assistance from either the RTMC or a law enforcement officer near the end of their shift, the Road Ranger Service Patrol operator is obligated to request permission to work overtime based on funding availability. Telvent Farradyne Page 92 Revised: 6/2/08

102 The Road Ranger Service Patrol operators are responsible for contacting the RTMC upon the commencement of their shifts. If a Road Ranger Service Patrol operator does not call the RTMC to start his shift the RTMC operators must contact the Road Ranger Service Patrol operator to inquire about their status. If there is no answer from the Road Ranger Service Patrol operator, the Road Ranger Service Patrol Supervisor must be contacted. A detailed e- mail, including the time that the Road Ranger Service Patrol actually arrived on their beat, should also be sent to the RTMC Operations Supervisor and the RTMC Operations Manager. Management will track the frequency of these problems and notify the FDOT Road Ranger Service Patrol Project Manager, when appropriate. This procedure will ensure effective roadway coverage, communications, and dispatch potential as well as aid in the safety and protection of the Road Ranger Service Patrol operators. Please note: Each Road Ranger Service Patrol shift starts when the Vehicle/Operator access the covered roadway (i.e. I-75), not when they leave their maintenance garage. The Road Ranger shifts are scheduled to occur: o From 0530 to 1400 hours o From 1330 to 2200 hours o From 2130 to 0600 hours The Road Ranger shift changes, therefore, are scheduled to occur: o From 0530 to 0600 hours o From 1330 to 1400 hours o From 2130 to 2200 hours Telvent Farradyne Page 93 Revised: 6/2/08

103 Road Ranger Administration Form The Road Ranger Administration form in the SunGuide software will be used to enter the Road Ranger schedule information at each shift change. The schedule is built by utilizing the given drop-down lists to assign and record each vehicle, status, driver, beat, and radio at the start and end of each shift. Road Ranger status changes, such as breaks and repairs, may also be documented through this function. For an example, please refer to the screenshot below. The incoming RTMC Shift Supervisor is responsible for verifying that the Road Ranger schedule is entered correctly, based on the information provided by the Road Ranger contractor and actual events. If there are any changes to the schedule, the SWIFT SunGuide Center operators must: o Enter the appropriate information into the Road Ranger Administration form in SunGuide o Note the changes on the list that is faxed from the Road Ranger contractor o Contact the Road Ranger Supervisor on duty to ensure that they are aware of the changes o Record all telephone calls in the Incoming/Outgoing Contact Microsoft Access database 12.5 SunGuide Software Patrol Status Changes After the Road Ranger schedule has been entered and reviewed, all Road Ranger activities are managed from the Road Ranger Dispatch form. An example of the Road Ranger Dispatch form is given below. Telvent Farradyne Page 94 Revised: 6/2/08

104 The notified, arrived, and departed information that is entered by the SWIFT SunGuide Center operators into the Road Ranger Dispatch form is automatically recorded in the Responder Table (upper right). All Road Ranger activities will be entered into the SunGuide system and will follow the order listed below. o Dispatch To record the time the Road Ranger is dispatched to an event o Arrive To record the time the Road Ranger arrives at an event. At arrival, the Road Ranger status may be set to Assist Motorist, Assist FHP, or Assist Other Road Ranger. o Activity To record activities performed at an event. It is important to enter all activities performed by the Road Ranger o Depart To record the time the Road Ranger departs from an event. At departure, the Road Ranger status may be set to Patrolling, Meal, Break, Out of Service, Mechanical, Fuel, Inspection, or Base. o Cancel To cancel a Road Ranger that has been dispatched to an event, but has not yet arrived on scene. Please note: A Road Ranger cannot be canceled once they have arrived on scene. Telvent Farradyne Page 95 Revised: 6/2/08

105 Multiple Road Rangers may be dispatched to the same event and multiple activities, such as flat tire, jump, gas, etc, may be recorded for each Road Ranger at an event. Events cannot be closed until all Road Rangers have been assigned an activity and have departed from the event. There will be times when no Road Rangers are available to respond to an event. This may be attributed to shift changes, meals/breaks, re-fueling, inspections, etc. If this occurs and no Road Ranger is available to respond, then the SWIFT SunGuide Center operations staff will make a note in the Comment Section of the SunGuide software stating the reason why the Road Ranger was unavailable Authorized Leave from Road Ranger Beats Road Ranger Service Patrols must get authorization to leave their beat from the RTMC. The Road Ranger Service Patrol may leave their designated beats if one of the following occurs: o Mechanical failure of the Road Ranger Vehicle. In this instance a backup vehicle shall be put into service within thirty (30) minutes. o Replenish supplies or refuel at the nearest facility not to exceed two (2) miles from the beat. The vehicle leaving the beat for obtaining the fuel or supplies may do so no more than once per shift and must return to service within thirty (30) minutes. o In response to an order from a law enforcement officer or fire department official o For a Road Ranger rest period of no longer than fifteen (15) minutes. Such rest periods shall be outside the periods of hours and hours and shall be no more frequent than one such period per eight (8) hour work period worked by the specific Road Ranger. o A lunch period of no longer than thirty (30) minutes is allowed during a shift of eight hours or more. o The Road Ranger may leave the beat to bypass a significant queue to reach an incident or lane blockage. The diverted path must be quicker than traveling along the shoulder or if there is no shoulder to use. o To change drivers The Road Ranger Service Patrol must notify and get clearance from the RTMC when a request is made to leave its beat. If the RTMC is not notified when Road Ranger Service Patrol operators leave their beat, the RTMC operations staff must click the Road Ranger Procedural Error check box in the event details window of the SunGuide software and provide a detailed comment regarding the error, notify the Road Ranger Supervisor and RTMC Shift Supervisor, and send a brief with a description of the problem to the RTMC Operations Supervisor and RTMC Operations Manger Coverage Changes when One or More Zones are Not Patrolling It is the responsibility of the Road Ranger Service Patrol Vendor/contractor to ensure that the entire coverage area of the project is being patrolled. If a Road Ranger Service Patrol has to leave their beat for more than 30 minutes and is therefore leaving their beat un-patrolled, the RTMC operations staff must contact the Road Ranger Service Patrol Supervisor. The Road Ranger Supervisor will make arrangements to get a replacement Road Ranger Service Patrol operator and/or truck back into the un-patrolled area within the 30 minute tolerance. Telvent Farradyne Page 96 Revised: 6/2/08

106 12.7 Road Ranger Communications This section documents the actions required by the SWIFT SunGuide Center operations staff and the procedures governing radio communications between the SWIFT SunGuide Center operations staff and the Road Ranger contractors, as well as other partnering agencies related to incident management. The SWIFT SunGuide Center utilizes a 470MHz two-way radio communication system that provides continuous communications between the SWIFT SunGuide Center operations staff and the Road Ranger drivers. The FDOT RTMC Contract Manager and the FDOT Road Ranger Project Manager are responsible for the 470MHz two-way radio communication system. The RTMC Operations Manager will ensure that all communications are in compliance with the established procedures. All Road Ranger radio operations shall be conducted in accordance with Federal Communications Commission (FCC) rules and regulations. FDOT District 1 is authorized to transmit communications related to public safety and incident management, the protection of life and property, and other communications essential to FDOT District 1 activities. False calls, false or fraudulent distress signals, superfluous unidentified communications, and obscene, indecent, and profane language are prohibited Two-Way Radio Setup The SWIFT SunGuide Center utilizes three Highland Wireless Road Ranger radios for Road Ranger communications. Two radios are located in the Road Ranger operator console (rightfront) and one is in the operations operator console (center-front). This radio system is our primary communications source. The cell phones will only be used as a backup system if radio communications fails. The radios operate on 2 channels; I-95 WPB-1 (North tower from Delray to Southern) & I-95 WPB-2 (South tower from Lantana to Hobe Sound). The channel display is located at the top of the radio in the lighted box. Channels should be utilized so the trucks in south county use WPB 1 and trucks in North County use WPB 2. Trucks in the area of Lantana Rd to Southern Blvd can be heard on either channel. There are 3 columns with grey buttons across the top of the radio. The third button down in the first and second columns, labeled Channel Up and Channel Down, are to be used to move between channels. There is also a third channel labeled I-95 DELTA. This channel can be used to communicate with the Broward TMC. The radio will not ring as the telephone does. The radio transmissions come through similar to the Nextel push-to-talk communications. Road Ranger radio transmissions can be heard without lifting the handset. To respond, press and hold the red transmit button located at the bottom right of the radio. To adjust the speaker volume, turn the control located at the top right of the radio Two-Way Radio Usage All Road Ranger units shall be dispatched by SWIFT SunGuide Center operations staff only. The SWIFT SunGuide Center operations staff must be aware they are constantly being monitored by RTMC Shift Supervisors, the RTMC Operations Supervisor, the RTMC Operations Manager, the FDOT RTMC Contract Manager, the FDOT Road Ranger Project Manager, the Telvent Farradyne Page 97 Revised: 6/2/08

107 Road Ranger contractors, and public safety personnel. The SWIFT SunGuide Center staff s voices represent the SWIFT SunGuide Center and FDOT and must set the tone for each shift. The SWIFT SunGuide Center staff will promptly answer all calls on the radio system in a professional and businesslike manner, using the SWIFT SunGuide Center approved communications specified in this document. Communications must always be in the English language. The SWIFT SunGuide Center staff must evaluate the priority of the radio traffic before handling any other activity. Calls may be placed on stand by only when the SWIFT SunGuide Center operations staff is handling a higher priority activity such as posting DMS messages, making telephone calls requesting emergency response, etc. If the Road Ranger is in a life threatening situation, the call should be treated as the highest priority and handled immediately. The SWIFT SunGuide Center operations staff will monitor the radio channel before broadcasting, to ensure the channel is clear before transmitting. SWIFT SunGuide Center staff should also wait approximately 15 to 30 seconds between each attempt to contact a Road Ranger, unless circumstances dictate otherwise. The call sign for the SWIFT SunGuide Center will be RTMC and the call sign for the Road Ranger trucks will be Truck (Truck Number). As shown in the previous statement, the call signs for the Road Rangers are their individual truck numbers. It is possible to monitor Road Ranger transmissions from other traffic management centers. The call sign for the Palm Beach ITMS is Palm Beach. The call sign for the Broward TMC is Broward. At the start of a transmission or series of transmissions, the SWIFT SunGuide Center operations staff and Road Rangers are expected to properly identify themselves by their call sign. This call sign shall be broadcasted clearly and distinctly, as this identifies the transmitting station. After this identification, the agency should give the call sign of the unit in which they wish to communicate. For example, when the SWIFT SunGuide Center wishes to contact Road Ranger truck #1, the communication should be as follows: RTMC to Truck 1. Failure to comply may result in disciplinary action. Only pertinent information shall be broadcasted, and all dispatches shall be read using the proper format and stated as briefly as possible, using the appropriate ten-code and dispatch signals. Comments added as expressions of courtesy, such as please, thank you, or you re welcome, etc. shall not be used. Personal communications are prohibited. Questions concerning the need for transmitting sensitive messages shall be referred to the RTMC Shift Supervisor or designee. Radio communications for numbers/letters shall be grouped and read in series of three, counted from left to right. For example, the vehicle identification number (VIN) B1RH would be read as Bravo One Romeo Hotel five four two one seven eight. An exception to this series of three rule is the transmission of telephone numbers Vacating the Road Ranger Communications Console When two or more employees are working and it becomes necessary for one of them to leave their console unattended, another employee will be advised to monitor the other console. The employee leaving the position must brief the remaining SWIFT SunGuide Center staff and the RTMC Shift Supervisor of on-going activities and the status of all trucks. Telvent Farradyne Page 98 Revised: 6/2/08

108 Transmission Quality, Volume, and Tone The SWIFT SunGuide Center operations staff shall minimize and avoid all background noise as much as possible to guarantee clear and concise communications. The desired voice quality should display a positive impression, alertness, enthusiasm, confidence, calmness, businesslike approach, and a readiness to serve. The voice should not sound unprofessional at any time, particularly when under stress. Proper enunciation and pronunciation, i.e., words spoken clearly and distinctly, greatly improve the ability of the receiver to copy the contents of a message and eliminate needless repetition. The desired voice volume should not be too loud or too low. An excessively loud voice does not increase the volume; instead it may distort the signal and create a higher pitch. The SWIFT SunGuide Center operations staff must guard against the natural tendency to lower the volume of their voice as they speak. Normal conversational volume is normally sufficient. The SWIFT SunGuide Center operations staff should use moderate pitch level changes in their voice as they speak. A monotone voice is unacceptable. The SWIFT SunGuide Center operations staff should develop a pitch that is not too high or low. A high pitched voice may be improved by talking slower and at lesser volume. A low pitched voice may be improved by talking louder and using distinct enunciation. The SWIFT SunGuide Center operations staff must remember that the pace at which messages are delivered is important to understanding their content. Generally, a speaking rate of 40 words per minute is preferred for copying purposes Road Ranger Telephone Calls Communication between the SWIFT SunGuide Center operations staff and the Road Rangers will be made primarily through the 470 MHz radio communication system. The only case where a Road Ranger should use the telephone is when their radios are not working or when there is an emergency. The SWIFT SunGuide Center operations staff will follow the guidelines given below when receiving a phone call from a Road Ranger. o Ask the Road Ranger if they have an emergency or if there is a problem with their radio o If there is no emergency or problem with the radio, advise them that you can no longer take information over the telephone and request that they contact you on the SWIFT SunGuide Center radio communication system. o If there is a problem with the radio, check the Road Rangers portable and mobile radios while they are on the telephone. During this step, have the Road Ranger change to another frequency to determine whether the problem is a channel or radio specific problem. o If the telephone calls persist or if there is a permanent problem with the Road Ranger s radio, contact the Road Ranger Supervisor and send an to the RTMC Operations Supervisor, RTMC Operations Manager, FDOT RTMC Contract Manager, and the FDOT Road Ranger Project Manager. Telvent Farradyne Page 99 Revised: 6/2/08

109 NATO Phonetic Alphabet The NATO Phonetic Alphabet assigns code words to the letters of the English alphabet so that critical combinations of letters can be pronounced and understood by those who transmit and receive voice messages by radio or telephone regardless of their native language. This is especially true when safety is essential. A Alpha T Tango B Beta U Uniform C Charlie V Victor D Delta W Whiskey E Echo X X-ray F Foxtrot Y Yankee G Golf Z Zulu H Hotel I India J Juliet K Kilo L Lima M Mike N November O Oscar P Papa Q Quebec R Romeo S Sierra Telvent Farradyne Page 100 Revised: 6/2/08

110 SWIFT SunGuide Center Approved Ten Signals and Dispatch Codes FDOT utilizes the ten codes and dispatch signals which have been approved by the Joint Task Force for use in State Law Enforcement communications centers. 10-codes must be used to communicate effectively over the radio. The 10-Code series, properly known as 10 signals, are code words used to represent common phrases in voice communication, particularly in radio transmissions. Currently, there are Codes in use. The SWIFT SunGuide Center operations staff shall use the 10-Codes listed below when dispatching and communicating with Road Rangers. Telvent Farradyne Page 101 Revised: 6/2/08

111 All 10-Codes Commonly Used 10-Codes by Operations Staff 10-4 Acknowledgement 10-6 Busy 10-8 Available 10-9 Repeat Break Go to Base Location Telvent Farradyne Page 102 Revised: 6/2/08

112 10-23 Standby Contact With Message Received Emergency Did you receive? Enroute Negative Meet at Service Needed Cancel Disabled Vehicle On Scene Cleared Radio Console Equipment Radio console equipment includes a handset and headset. The SWIFT SunGuide Center operations staff shall use the headsets as much as possible to minimize control room noise. The handsets may be used when the headsets/earpieces are not functioning properly or when the SWIFT SunGuide Center operations staff is monitoring more than one channel simultaneously. The SWIFT SunGuide Center operations staff shall depress the transmit switch and pause for the tone identifier to transmit before speaking to eliminate fragmented or incomplete transmissions. For additional console operations refer to the radio console users manual Incident Detection and Road Ranger Dispatch Road Rangers should be dispatched by the SWIFT SunGuide Center whenever accidents or disabled vehicles are found on the roadway, travel lanes are blocked, traffic control may be required, unusual delays are noticed on CCTV, or when requested by FHP. In turn, the Road Ranger drivers will notify the RTMC of all incidents and problems encountered on the roadway. Specifically, the SWIFT SunGuide Center will: o Coordinate incident activities. Alert area Road Rangers of incident occurrence and status. Coordinate Road Ranger placement to provide most effective use of resources, including traffic control, queue protection and patrol of the queue area. o CCTV Monitoring The SWIFT SunGuide Center operators will use the CCTV cameras to visualize the incident scene and await the Road Ranger s arrival. This helps reduce response time if the Road Ranger is in an unsafe situation and allows the SWIFT SunGuide Center and FHP to determine if additional assistance needs to be dispatched to the scene of the call. o DMS Messages The SWIFT SunGuide Center operators will make appropriate notifications and post messages on the appropriate DMS, if an incident causes a lane blockage or unsafe traffic conditions are observed. o DMS Message Verification SWIFT SunGuide Center operators may dispatch Road Rangers to DMS in the field to verify that accurate information is displayed. o The SWIFT SunGuide Center will assist the Road Rangers in providing extended beat coverage when another Road Ranger is temporarily out of service, on lunch, or at base for equipment repair. Telvent Farradyne Page 103 Revised: 6/2/08

113 Driving in the Emergency Lanes to Reach Incidents The Road Ranger will call the SWIFT SunGuide Center for permission to drive in an emergency lane (shoulder) to reach an incident. The SWIFT SunGuide Center operator will notify the RTMC Shift Supervisor or designee of the request, who in turn will notify FHP dispatch. The RTMC Shift Supervisor or designee will use sound judgment to determine if the use of the shoulder is necessary. Road Rangers should only request to drive in the emergency lane when traffic is moving 10 miles per hour or less. The Road Ranger should use caution when driving along the shoulder and not exceed speeds of 15 miles per hour Dispatching Multiple Units When dispatching a Road Ranger unit to an incident outside their assigned zone or outside their communication channel, the SWIFT SunGuide Center will ask the Road Ranger to switch their radio to the appropriate common channel being used to work the incident. The Road Ranger working the incident must let the SWIFT SunGuide Center operator know when they are clear from the incident and that they will be switching back to their designated channel and returning to their assigned beat. When back on their designated channel the Road Rangers must say their call sign and clear for action or Road Ranger Arrival Upon arrival, Road Rangers will: o Contact the SWIFT SunGuide Center to provide basic information of each stop: location, vehicle description, tag number, lanes affected, fuel spill information, etc. This information is needed for both Road Ranger safety and SWIFT SunGuide Center awareness of roadway conditions. o Provide the SWIFT SunGuide Center with incident status updates every 20 minutes or whenever conditions change. The SWIFT SunGuide Center operator will actively seek the information if it is not provided. o Notify the SWIFT SunGuide Center of problems with the field devices which include: damage to any of the field equipment, incorrect DMS message display, no DMS message active during an active incident, etc. As a reminder, the SWIFT SunGuide Center operations staff must ask Road Rangers at lane closing incidents if the vehicles involved can be moved from the travel lanes upon their arrival. This should be notated in the Action Taken section of the Incident Report. If the Road Ranger moves the vehicles off the roadway, the operators must give FHP the new location of the incident scene so they can respond effectively SunGuide Software Event Details Data Entry The Event Details function in the SunGuide software allows for logging event details collected by the SWIFT SunGuide Center operations staff from the Road Rangers. This includes everything from the event location to information on the vehicle serviced. This also includes an area for comments to document information not collected by the pull-down menus and check boxes in the SunGuide software. If the event cannot be monitored with the CCTV cameras, the Road Ranger becomes the main confirmation source for incident information. The information that is collected from the Road Ranger is: Telvent Farradyne Page 104 Revised: 6/2/08

114 o Type of Incident o Location of Incident o Roadway o Direction o Proximity to Exit o Exit Number or Name o Notified By o Contact Name o Dispatched To o Road Ranger Activities performed o Beat Number o Anticipated Clearance Time o Lane Closures o Injuries o HazMat o Fire o Additional Services Required (FHP, Rotational Tow, Fire, Ambulance, etc.) The above areas of confirmed information collected from the Road Rangers on scene support the SWIFT SunGuide Center s event management activities, such as DMS message activation and making notifications to FHP and other agencies as required by the situation. While on scene at active events, the Road Ranger is required to inform the SWIFT SunGuide Center of any changes in the incident. These changes can range from lane block pattern, severity of the incident, additional services required, and duration changes based on information from onscene incident responders Road Ranger Service Patrol Incident Types Accidents The Road Ranger should notify the SWIFT SunGuide Center and request Law enforcement, fire, and ambulance assistance when necessary at accident scenes. The SWIFT SunGuide Center is responsible for contacting the requested agencies. The Road Ranger should remain at the scene until the appropriate assistance arrives. The Road Ranger should follow all reasonable directions from law enforcement personnel. The Road Ranger should protect accident scenes by setting Maintenance of Traffic (MOT) equipment Abandoned Vehicles The Road Ranger should notify the RTMC of all abandoned vehicles. The Road Ranger should report the vehicle s location, make, color, body type, license plate number, and lane blockage information. The RTMC operations staff shall provide this information to FHP dispatch to start the 6 hour clock. (Unless exception is stated in hazard zone, construction zone or poses danger to the motoring public that warrants expediting the relocation of the abandoned vehicle.) The RTMC operations staff will provide the Road Ranger with the SunGuide event confirmation number and must monitor the status of the abandoned vehicle via the Road Rangers and CCTV until the vehicle has been removed or departs from the scene. If the abandoned vehicle is impeding traffic or is considered to be a potential safety hazard, the Road Ranger should move the abandoned vehicle to the shoulder or call for support. Telvent Farradyne Page 105 Revised: 6/2/08

115 By law, abandoned vehicles will be removed from the roadway by FHP after 6 hours. Road Rangers are now authorized to issue FHP abandoned motor vehicle tags to vehicles they encounter on the roadway. This allows FHP to start the clock for the removal of abandoned vehicles when either Road Rangers or FHP arrive at the scene, which should help reduce the clearance time of these hazards from the roadway Disabled Vehicles The Road Ranger should offer services to stranded motorists even when the motorist s vehicle is already moved from the travel lane. Disabled vehicles should be removed from the travel lanes, with the least delay practicable, by moving them to the shoulder area or drop location. Should a motorist refuse to allow a disabled vehicle to be cleared from travel lanes, the Road Ranger Service Patrol operator should contact the RTMC for assistance. The Road Ranger Service Patrol should provide a Move-It brochure to the non-cooperative motorist. The RTMC operations staff will contact FHP and the Road Ranger Service Patrol should setup appropriate MOT to protect the incident scene until FHP personnel arrive. The Road Ranger shall not attempt to move these disabled vehicles until directed to do so by FHP. All disabled vehicles that are relocated should be parked with the wheels turned away from the roadway and the parking brake should be set, if possible Animals After clearing the travel lane, the Road Ranger should call and report the location, type, and condition of injured or dead animals to the SWIFT SunGuide Center. The SWIFT SunGuide Center operations staff will then call the local animal control agency. Refer to the Animal Rescue and Removal section of this document for additional details Road Ranger and Motorist Interaction Transporting Motorists If vehicle assistance or towing services cannot be obtained for a motorist, rather than leaving the motorist stranded, the Road Ranger should contact the SWIFT SunGuide Center and request authorization to transport the motorist to the nearest facility with available communications within the physical limits of their contractual obligation. The SWIFT SunGuide Center operations staff will confirm the license plate number of the motorist s vehicle and notify FHP dispatch of the arrangement between the motorist and Road Ranger Maintenance of Traffic The Road Rangers are required to set up temporary Maintenance of Traffic (MOT) for all assist activities on the highway. MOT equipment includes highway flares, cones, flagging, flashing amber/white lights, DMS board, etc. to assist with traffic control. The following guidelines have been established: o Always be conscientious of personal safety o Leave at least 1 car length (30-50 feet) in between the Road Ranger Service Patrol vehicle and the incident vehicle in front o Turn tires toward the nearest curb o DMS board must show the appropriate message, arrow or four points for shoulders Telvent Farradyne Page 106 Revised: 6/2/08

116 o 15 cones MUST be used if you are blocking ANY lanes o Use proper tapering of lanes (minimum of 5 cones per lane) o Cones must be spread out all the way to the front of the incident scene o No less than 8 cones MUST be used while working on the shoulder (disabled vehicle, accident, paperwork, etc.) o Road Ranger Service Patrol should notify RTMC before leaving the Road Ranger Service Patrol vehicle o There should be one Road Ranger Service Patrol per incident whenever possible o Light bar must be on when parked on shoulder o The Road Rangers should not spend more than 5 minutes doing data entry on the shoulder after an incident has been cleared o Seat belt MUST be worn at all times while in the Road Ranger Service Patrol vehicle, including times in the shoulder lane o The Road Rangers must wear their safety vest at all times both in and out of their Road Ranger Service Patrol vehicle o Safety vest must be clean and visible o Safety vest must fit properly o Safety vest should be worn properly (closed in front) Road Ranger Assist Updates Following the 15-minute rule for safety, the RTMC operations staff will contact all Road Ranger Service Patrol operators at active assists every 15 minutes to ensure that the Road Rangers are safe and to receive updated incident information. The Road Ranger Service Patrol operator will re-assess the traffic incident management vehicle positioning and scene safety and provide situational brief to the RTMC operations staff Road Ranger Assist Clearance At the end of an incident or motorist assist, the Road Ranger is required to inform the SWIFT SunGuide Center of their departure and the final status of the incident. The SWIFT SunGuide Center operations staff will then begin the operational and data entry tasks associated with incident clearance. In addition, the SWIFT SunGuide Center operations staff will provide the Road Ranger drivers with the unique Incident Number from the SunGuide software. This procedure was implemented to encourage proper communications and motorist assist reporting between the two agencies Road Ranger Service Patrol Problems The RTMC operations staff must notify the Road Ranger Service Patrol Supervisor and the RTMC Shift Supervisor of all Road Ranger problems or issues while they are happening. An e- mail with a brief description of the problem should also be sent to the RTMC Operations Supervisor, RTMC Operations Manager, and the FDOT Road Ranger Project Manager. Examples of out of the ordinary problems are when Road Ranger Service Patrol operators log off during their shifts for personal issues, leaving incident scenes before cleared from the roadway, leaving their beats early for shift change, leaving their beats without notifying the RTMC, excessive or unauthorized breaks, excessively long duration breaks, traveling more than two miles away from I-75 or I-275, argumentative behavior, contact cannot be established, relaying incident information after services are rendered, giving incorrect incident locations, Telvent Farradyne Page 107 Revised: 6/2/08

117 improper MOT setup, faulty equipment, missing equipment, etc. Please refer to the Road Ranger Scope of Services and Performance Expectations documents for additional details Road Ranger Service Patrol Issue Resolution Local Agencies & Motorists If a Road Ranger Service Patrol operator violates professional conduct or has a personal conflict with the RTMC staff, the RTMC operator should inform the RTMC Shift Supervisor of the issue. The RTMC Shift Supervisor will immediately contact the Road Ranger Service Patrol Supervisor and send an notification that describes the issue to the FDOT Road Ranger Project Manager, RTMC Operations Supervisor, RTMC Operations Manager, and FDOT RTMC Contract Manager. The RTMC operations staff shall contact the FDOT Road Ranger Project Manager by and cell phone if they observe Road Rangers having any issues in the field, such as: o A dispute with an FHP officer or other responding agency o A conflict with a motorist o Accepting gratuity of any kind o Failure to participate in the performance of their duties Citizen and Agency Complaints If a citizen, FHP, or other agency calls the SWIFT SunGuide Center and complains about Road Ranger services, the SWIFT SunGuide Center operations staff will document the name of the caller, name of the agency represented, contact information of the caller, and nature of the complaint. The SWIFT SunGuide Center operations staff should then inform the caller that a FDOT representative will be contacting them within a few days. The SWIFT SunGuide Center operations staff shall then send an with all available information to the RTMC Operations Manager and the RTMC Operations Supervisor, who will notify the FDOT RTMC Manager and the FDOT Road Ranger Project Manager Road Ranger Service Patrol Involved in an Accident In the event that a Road Ranger Service Patrol operator or vehicle is involved in an accident or any other significant incident, the following procedure must be followed. o Inquire if there are injuries and if an ambulance is needed on scene o If an ambulance is needed, the SWIFT SunGuide Center operations staff must immediately call 911 or notify FHP dispatch to request an ambulance. o Enter the incident with the event type of Accident into SunGuide software. o Under the Vehicles Information section, select Road Ranger for the make of the vehicle. o Notify the FDOT Road Ranger Project Manager, Road Ranger Supervisor, FDOT RTMC Manager, RTMC Operations Supervisor, and RTMC Operations Manager by telephone. o The FDOT Road Ranger Project Manager is responsible for sending an to the Statewide Road Ranger Project Manager, District Safety and Health Manager, and FDOT District 1 PIO. This will be created with information provided by the SWIFT SunGuide Center operations staff and report and will contain the following information: A description of what happened in the crash. The at-fault driver. If charges were filed and what were the charges? Has the Road Ranger been involved in a previous crash and were they at fault? Was alcohol or illegal substance involved? If the crash involved moving vehicles, was the Road Ranger wearing a seat belt? Telvent Farradyne Page 108 Revised: 6/2/08

118 o After the initial manual contacts are made and other essential operations activities are performed, the SWIFT SunGuide Center operations staff should use the Administrative Pages group in the SunGuide software to notify and update the above managers when accident details change. o Continue with all other normal reporting procedures until incident completion. o Put as many incident details in the SunGuide incident report (comments section) as possible. o When the incident report is completed, send an electronic copy to the RTMC Operations Supervisor and RTMC Operations Manager by . If any serious injuries are present, cones or any other form of MOT which was on the roadway for the incident are not to be moved or modified at the scene. In this case, flares can be used by the Road Rangers and the Road Ranger Supervisor when they arrive on scene Road Ranger Service Patrol Vehicle Not Operational or Missing Equipment The RTMC operations staff must contact the Road Ranger Service Patrol Supervisor whenever a Road Ranger calls the RTMC to request a second Road Ranger for the following reasons. o Unable to assist a motorist because the truck is not operational o Unable to assist a motorist because the truck does not have the proper equipment The Road Ranger Service Patrol Supervisor needs to know this information because Road Ranger Service Patrol vehicles should not leave their base with faulty equipment or without equipment required by the contract. Also, when the second Road Ranger arrives, the first Road Ranger should go back on duty and not remain on-scene if they are not needed. The Road Ranger Supervisor will make arrangements to re-equip the problem Road Ranger vehicle Road Ranger Procedure when One or More Zones Not on Duty Whenever there is a shortage of Road Rangers on duty, the SWIFT SunGuide Center operations staff must notify the Road Ranger Supervisor as soon as possible and send an e- mail to the RTMC Operations Supervisor and RTMC Operations Manager. This shortage can happen at any time and includes Road Ranger shift starts (not enough trucks log in for their daily shift), Road Rangers involved in an accident and will no longer patrol, a truck requiring extensive repairs that is taken back to the garage, etc. The SWIFT SunGuide Center operations staff should also call the Road Ranger Supervisor to assess the downtime until another Road Ranger can replace the absent patrol. When a Road Ranger will not be on patrol for 30 minutes or more, FHP should be notified of the Road Ranger shortage and the estimated downtime. If FHP requests Road Ranger assistance on a beat that is vacant before the 30 minute mark, the SWIFT SunGuide Center operations staff should explain that that specific Road Ranger is not on patrol and that the SWIFT SunGuide Center will send an adjacent Road Ranger to the call. If the adjacent Road Rangers are busy, the SWIFT SunGuide Center operations staff must give FHP an estimated response time. If a Road Ranger will be off the roadway for more than one hour during normal business hours, the RTMC Shift Supervisor must contact the FDOT Road Ranger Project Manager. As a rule of thumb, the On-Call Supervisor should always call the FDOT D1 Road Ranger Project Manager during normal hours. After-hours, the RTMC Shift Supervisor should only contact the FDOT D1 Road Ranger Project Manager whenever more than half the Road Ranger fleet will not be on Telvent Farradyne Page 109 Revised: 6/2/08

119 patrol until the next shift change or there is a matter that requires immediate attention. All other after-hours issues will be forwarded by the RTMC Operations Manager to the FDOT D1 Road Ranger Project Manager by the next business day Road Ranger Service Patrol Procedural Errors The SWIFT SunGuide Center operations staff shall monitor the Road Rangers and report any evidence that the Road Rangers are not performing the roles and responsibilities as described in this document and the SWIFT SunGuide Center SOG. When a Road Ranger is not adhering to their roles and responsibilities, then the SWIFT SunGuide Center operator shall inform the driver of the issue. Then the SWIFT SunGuide Center operator shall click the Road Ranger Procedural Error check box in the event details window of the SunGuide software and provide a detailed comment regarding the error, including the frequency in which the error/issue has occurred. Then the SWIFT SunGuide Center operator shall notify the RTMC Shift Supervisor who will notify the Road Ranger supervisor of the issue Incorrect MOT Setup When Road Rangers setup MOT incorrectly, the SWIFT SunGuide Center operations staff must immediately take a snapshot of the incident scene in SunGuide, notify the Road Ranger Supervisor, and notify the RTMC Shift Supervisor on duty. An with the snapshot and a short description of the procedure violation should also be sent to the RTMC Operations Manager and RTMC Operations Supervisor Road Ranger Service Patrol Safety This section provides guidelines to assist in ensuring Road Ranger Service Patrol operator Safety. While the RTMC is not specifically responsible for the safety of Road Rangers, the RTMC staff can be aware of potential issues to improve overall safety of the Road Ranger Service Patrol. The Road Ranger Service Patrol should approach every situation with caution and be conscientious of personal safety. The RTMC operations staff shall monitor the radio using the following guidelines: o If no contact has been made between the Road Ranger and RTMC within 15 minutes from the initial contact of reporting an assist, the RTMC staff will attempt to contact the Road Ranger originating the assist. o The Road Rangers welfare shall be checked every 15 minutes after initial contact until the assist is cleared. o In the event that two attempts to contact the Road Ranger have failed, the RTMC operations staff shall immediately dispatch the nearest available Road Ranger Service Patrol unit to the last location given by the Road Ranger performing the assist, notify the Road Ranger Supervisor on duty, and notify FHP dispatch. o If no Road Ranger unit is available, the RTMC operations staff shall utilize the closest available resource (FHP, Fire Rescue, etc.) by notifying them in person, by telephone, or by any other means of immediate communication. The RTMC Operations Supervisor, RTMC Operations Manager, Road Ranger Supervisor, FDOT RTMC Contract Manager, and FDOT Road Ranger Project Manager should be notified again. This should also be noted in the SunGuide software. o Messages of significant importance shall be broadcasted to all in-service units. o Emergency situations such as calls for backup, shootings, violent crimes in progress, large scale civil disturbances, disasters, etc., require expedient response by the RTMC. Telvent Farradyne Page 110 Revised: 6/2/08

120 Communication personnel receiving a report of this nature or any other life threatening situation shall broadcast an alert tone on all frequencies and pause for five seconds before broadcasting the information. The alert tone before a broadcast will signal the unit that important information is forthcoming. o The RTMC operations staff shall not dispatch Road Rangers to any incidents that are violent in nature or have known suspicious activity. Local law enforcement should be contacted to handle these situations instead Road Ranger Service Patrol Hourly Procedure Safety The RTMC operations staff must manually contact each individual Road Ranger Service Patrol every time one full hour has passed without a service call or prior contact with the RTMC. This procedure is necessary to ensure the Road Rangers are still on patrol in a safe condition. It also confirms that the Road Rangers are not sick, injured or sleeping on patrol. If a Road Ranger is injured, immediately call emergency services or notify FHP dispatch. All calls made as a result of this procedure must be logged in the Incoming/Outgoing Contact MS Access database and recorded in the SunGuide software. Comments will be logged in the comments field AVL Operation and Monitoring The Road Ranger Service Patrol vehicles are equipped with an Automatic Vehicle Location (AVL) system that displays the geo-location of the Road Ranger vehicles on an electronic map. This AVL system is monitored by the RTMC as part of the Road Ranger Service Patrol coordination and dispatching initiative. The RTMC operations staff will monitor the AVL system continuously during operating hours, and use the system for coordination of Road Ranger Service Patrol activities. The RTMC Operations Supervisor or RTMC Operations Manager must be manually contacted for all major problems with the system. An will suffice for minor system issues. RTMC management is responsible for notifying the FDOT Road Ranger Project Manager of any apparent problems with Service Patrol vehicles and/or the AVL monitoring system Road Ranger Common Data Entry Errors The following list describes several recurring mistakes operators make when entering data into the Road Ranger log form in Microsoft Access. These mistakes are all preventable. Please read the pitfalls below to avoid these common mistakes. o The Caller field on the Road Ranger log is being populated with Road Ranger when the log was created as a dispatch. The Road Ranger cannot dispatch him/herself to a call. The Road Ranger can initiate a call but there should be no Dispatch time, only Arrival and Departure times. The Caller field is only to be populated with Road Ranger when the Road Ranger notifies the RTMC. All other logs are to be labeled accordingly. o All Road Rangers are required to log in at the beginning and end of their shift. There is a log created at the beginning of each Road Rangers shift, which is the same log that is to be used to log the Road Ranger out. Separate logs have been created for the Road Rangers Start Shift and End Shift. This is incorrect. All operators should be familiar with the Road Ranger logs and these logs will be completed correctly. The Road Ranger Daily Zone Record can be used as a reference for the time to aid in locating the log for the start shift. o Road Ranger calls sometimes start out as the problem type Disabled Vehicle and then change when more specific information is given. In these situations, the problem type Telvent Farradyne Page 111 Revised: 6/2/08

121 should be changed from Disabled Vehicle to the more specific problem type ( Out of Fuel, Mechanical Problem, etc.). When the operators leave the problem type Disabled Vehicle and add the actual problem type, the monthly statistics get skewed with an abundance of the Disabled Vehicle calls. o Road Rangers can not get fuel and end their shift on the same log. The start shift/end shift log should only contain the Road Ranger Start Shift problem type and Road Ranger End Shift solution type. A separate log should be created for breaks and fuel calls. o One problem can yield more than one solution. Do not enter the same problem twice on a single log. o When Road Rangers give motorists oil or brake fluid, the problem type should be Mechanical Problem, not Other. o Especially for accident calls, the operators should ask the Road Rangers if they used speedy-dry. The Road Rangers frequently forget to mention this activity to the RTMC because it is part of an Accident, so it is preferred that we ask them this specific question to confirm the activity. Telvent Farradyne Page 112 Revised: 6/2/08

122 13 Incident Management 7 Step Concept The most common operational condition under which the SWIFT SunGuide Center has a positive impact will be during traffic incidents, which was the primary justification for the ITS deployment and the creation of the SWIFT SunGuide Center. Efficient incident management, including rapid detection, verification, quick clearance, and measures to mitigate recovery can save thousands of hours of needless delay and reduce the probability of secondary crashes. The following section describes the many ways to detect and verify incidents, as well as the actions necessary once the incidents are confirmed. Event management is a multi-step process that is both described and graphically depicted below. o Step #1: Roadway Monitoring & Incident Detection This step includes the use of CCTV, websites, 511, FHP, Road Rangers, traffic management centers, and other sources to detect events. Once the event is detected, the location of the event is determined which dictates the event confirmation process, as well as subsequent steps. o Step #2a: Event Confirmation (FDOT District 1 Coverage Area) Event confirmation is the process of verifying the occurrence, location, lane blockage, and other important information of the incident. o Step #2b: Regional Event Management The confirmation of events in the coverage area of other traffic management centers. These types of events are the responsibility of the coverage areas TMC, but the assistance of the FDOT District 1 SWIFT SunGuide Center may be requested or necessary. o Step #3: Event Evaluation Once the event is confirmed, the SWIFT SunGuide Center operations staff must evaluate the event and its potential impact to traffic and the incident responding agencies. The event evaluation process will help guide the SWIFT SunGuide Center operations staff to proceed with the activities required to effectively manage events. o Step #4: DMS Response Plan For events with blocked travel lanes or impact to traffic flow, the SWIFT SunGuide Center operations staff must post DMS messages to inform motorists of traffic conditions as soon as possible. o Step #5: Notifications Once the events have been confirmed, evaluated, and the DMS messages are activated, the SWIFT SunGuide Center operations staff must inform the appropriate agencies to ensure that accurate information is disseminated. Quickly disseminating this information is important because each of these partner agencies plays a significant role in the dispatch of resources, traffic management, and the clearance of the incident. o Step #6: Event Monitoring Providing Timely information to the motorists and other agencies require the SWIFT SunGuide Center operations staff to closely monitor events for changes in conditions. Changes include closure of travel lanes, opening of travel lanes, agency arrival times, agency departure times, additional resource needs, etc. Once changes have been identified, the SWIFT SunGuide Center operations staff must re-evaluate the event and proceed from Step #3. o Step #7: Event Closure As the event comes to an end, the SWIFT SunGuide Center operations staff must follow the procedures to ensure that the event is closed Telvent Farradyne Page 113 Revised: 6/2/08

123 correctly. This includes the very important task of monitoring unresolved events. Through the life of an event, the SWIFT SunGuide Center operations staff must continuously enter data into the SunGuide software. The data entry must be timely to ensure that accurate timelines of the event can be created. These event timelines serve as a valuable tool in evaluating and improving the SWIFT SunGuide Center procedures and operations. Please refer to the Event Timelines sub-section in the General Operational Concepts section of this document for more specific details. Telvent Farradyne Page 114 Revised: 6/2/08

124 Telvent Farradyne Page 115 Revised: 6/2/08

125 14 Incident Management Roadway Monitoring and Incident Detection 14.1 Video Wall Detection The video wall contains fifteen 57 inch screen rear projection monitors, called cubes. Combined, they make a seamless screen. The video wall layout is setup so that all SWIFT SunGuide Center CCTV cameras can be scanned in approximately 12 seconds so the SWIFT SunGuide Center operations staff can quickly detect traffic abnormalities. The SWIFT SunGuide Center CCTV cameras are displayed in geographical order from south to north. When scanning the cameras, the SWIFT SunGuide Center operations staff should look for visual clues to detect traffic events. o Very light or zero traffic flow at locations and times when heavier flow is expected o All or most vehicles changing lanes at a particular location o Vehicles slowing or stopping at locations and times when light traffic flow is expected o Scan cameras with typical traffic queues, bottlenecks, construction, and high-volume ramps for secondary events The SWIFT SunGuide Center operations staff must continuously do the following: o Visually scan the video wall for disruptions in traffic flow. o When traffic flow is disturbed, monitor the camera that shows the cause of the incident. o When traffic flow is disturbed, monitor the cameras downstream of the incident to closely monitor delays. This will also help the SWIFT SunGuide Center operations staff to quickly detect secondary incidents in the queue. o Display active incidents on the allocated area of the video wall. The video wall should display: o All SWIFT SunGuide Center CCTV camera images in order from south to north o Two active incident cameras. These areas on the wall are allocated for the SWIFT SunGuide Center staff to change camera images to show live traffic events for incident monitoring. o The SunGuide regional map display with current speed data o The xxxxx.com SWIFT SunGuide Center website (set to the active Traffic Events screen) o The FHP Traffic Crash Report website o The Weather Channel Pinpoint Doppler website with the map zoomed in to view southwest Florida o The Channel 13 Live Traffic Reports website (for FHP) o The Smart Viewer website for current Broward RTMC and Palm Beach ITMS incidents, o The statewide 511 website, o The southwest Florida 511 website, The video wall must always be filled with as many functioning traffic related images as possible and should be configured to look presentable at all times. The SunGuide software IM Module allows for the control of the SWIFT SunGuide Center video wall. The SWIFT SunGuide Center operations staff can configure the placement of the cameras on the video wall by simply clicking on the desired CCTV and dragging it into an available source. There are multiple layouts which are predefined placements of the cameras which can be used to auto-populate the video wall. Telvent Farradyne Page 116 Revised: 6/2/08

126 The standard video wall layout is shown in the picture below. This configuration should only be changed with the approval of FDOT or the RTMC Operations Manager. Insert Video Wall Layout - Picture 14.2 CCTV Detection Observation of an incident on the camera image is one basic detection method. The SWIFT SunGuide Center operations staff should scan through the presets of all the SWIFT SunGuide Center CCTV cameras when not performing other duties. The SWIFT SunGuide Center operations staff will utilize the camera control module included in the SunGuide software, or the xxxxxxxxxx VICON vendor supplied control unit to control (pan, tilt, zoom, etc.) each SWIFT SunGuide Center CCTV camera. The SWIFT SunGuide Center operations staff will point or direct the SWIFT SunGuide Center CCTV cameras to view the location or general direction of travel most likely to observe an incident. Through experience, operators will know where most incidents occur and point the cameras in appropriate directions throughout the day. Also, it is important to position the SWIFT SunGuide Center CCTV cameras (and all other agency s cameras) so they do not point directly into the sun. The sun can cause serious damage to the lenses of the cameras. The auto-iris function of cameras looking directly at the sun will also darken the images dramatically and obscure normally viewable details. The SWIFT SunGuide Center operations staff must also change the RTMC cameras to a valid preset position after using the pan/tilt/zoom function after scanning for possible events Camera Presets Add camera preset development information here. In general, 1=north, 3=south, 2=east, 4=west, x=ramps, etc., y=arterial roadways Camera Pan/Tilt/Zoom (PTZ) CCTV cameras may be panned and tilted at any time. The CCTV cameras must not be zoomed in during routine traffic monitoring, however. License plates and individuals should not be identifiable Restricting Camera Images When personal injuries or hazardous materials (HazMat) spills are suspected in a traffic accident, the SWIFT SunGuide Center operators may be required to zoom in to collect information that is required by FHP, Emergency Medical Services (EMS), FDOT, or for other informational purposes. When this occurs, it is critical that the operator restrict the CCTV camera image from any external video feeds. This task can be accomplished by using the appropriate function in the SunGuide software. Once zooming in is no longer necessary, the SWIFT SunGuide Center operator must return the camera back to a less specific view to continue monitoring traffic conditions and un-restrict the CCTV camera image from the blocked to the external video feeds. Please refer to the Block CCTV Images sub-section of the SunGuide Software Data Management section of this document for more specific details on restricting and un-restricting camera images on external video feeds. Video images should also be blocked from the website and all other external video feeds anytime the camera is not pointed directly on the highway corridor. Telvent Farradyne Page 117 Revised: 6/2/08

127 Once the CCTV camera image is restricted from public view, the RTMC Shift Supervisor must view the CCTV camera image on the SWIFT SunGuide Center website and all other external sources possible to insure that the access has actually been restricted. A restricted image on the SWIFT SunGuide Center website will display the Temporarily Unavailable message. When this option is deactivated the RTMC Shift Supervisor must check the SWIFT SunGuide Center website and other external sources again to insure that the image is displaying properly. Problems with this feature should be immediately ed to the RTMC Operations Supervisor and the RTMC Operations Manager Vendor Camera Control Software The xxxxxxxx VICON software is used as a backup method for viewing SWIFT SunGuide Center CCTV camera images on the workstation. With this application, the CCTV cameras are listed Add a description of this software (with pictures) here Microwave Vehicle Detector System The Microwave Vehicle Detector System (MVDS), also referred to as VDS, are electronic sensors which relay a variety of traffic data over a communication system to a central processing location within the SWIFT SunGuide Center. The VDS focuses on all lanes on I-75 and provides the SWIFT SunGuide Center operations staff with data such as average speed on segments of the highway, current speed, historical speed, volume, and automatic detection of congestion. The VDS also allow for the generation of travel times for the DMS messages displays and can detect motionless objects on the highway such as disabled vehicles, accidents, etc. The SunGuide software segments the highway into individual links. A link is an area of roadway monitored by each individual VDS unit. Each link detects traffic speeds that fall beyond the normal time of day threshold and produce an alert at the SWIFT SunGuide Center workstations. The system stores and updates historical data so it will not alert the RTMC operations staff of recurring congestion. The system may alert the RTMC operations staff of slower than normal traffic due to weather conditions depending on the severity of speed impact, location, and time of day, however. The SWIFT SunGuide Center operations staff will utilize the SunGuide software to monitor the volume and speed information from the 126 vehicle detectors in the Video Detection System (VDS). Slow traffic or high volume during non-peak times or normal speed traffic and light volume during peak travel times may indicate potential incidents MVDS False Alarms The VDS will generate an alarm that is displayed in the SunGuide software when abnormalities are detected. If an automatically generated alarm proves to be a false alarm, the SWIFT SunGuide Center operations staff must declare it as such in the system Road Ranger Detection The Road Rangers are a reliable incident detection source for the SWIFT SunGuide Center. They often provide detection and confirmation information simultaneously. For more information about the Road Ranger program, please refer to the Road Ranger Service Patrol Procedures section of this document. Telvent Farradyne Page 118 Revised: 6/2/08

128 14.5 FHP Dispatch FHP dispatch is collocated with the SWIFT SunGuide Center operations staff in the control room. This arrangement allows for very fast incident detection (and confirmation) times. FHP dispatch frequently receives 911 telephone calls from the public. Some of these emergency calls are motorists notifying dispatch of incidents they have encountered on the roadway. When this happens, FHP dispatch will gather the information, notify the SWIFT SunGuide Center operations staff of the incident details, and request for the potential incident to be located on a camera and the video wall. The SWIFT SunGuide Center operations staff must immediately search for these potential incidents, report findings to FHP dispatch, and put the CCTV camera image in the allotted space on the video wall. This procedure will ensure that both agencies have the correct incident information, including location, lane blockage, vehicles involved, etc Star FHP Calls Motorist assistance Star FHP (*FHP) calls in FDOT District 1 are received at the FDOT District 1 SWIFT SunGuide Center and are answered by the SWIFT SunGuide Center operations staff. It is possible for motorists requiring assistance from the Road Rangers to contact the SWIFT SunGuide Center operations staff and notify them of the event before otherwise detected. Therefore, this is a possible source for incident detection. Please refer to the Star FHP (*FHP) Motorist Assistance Calls section of this document for further details FHP Radio Transmissions The FHP radios are located in the FHP dispatch area of the SWIFT SunGuide Center control room. These radios may only be used by FHP dispatch personnel, but the volume of the transmissions allow for the SWIFT SunGuide Center operations staff to hear what is being said. These radios enable the SWIFT SunGuide Center operations staff to monitor transmissions between FHP dispatch and FHP troopers in the field in real time and should be monitored at all times. When incident information is overheard by the SWIFT SunGuide Center operations staff, the operators must immediately begin searching the SWIFT SunGuide Center CCTV cameras to visualize the incident. Once found, the SWIFT SunGuide Center operations staff must report all findings to FHP dispatch and put the CCTV camera image in the allotted space on the video wall FHP Website The FHP website is displayed on the SWIFT SunGuide Center video wall and on each workstation. The website is updated every 5-10 minutes and provides basic incident information. Because the SWIFT SunGuide Center operations staff is co-located with FHP dispatch, the chances of detecting in this fashion is very slim. Incident may still be detected this way, however, so monitoring the website is still a viable option. If inaccurate information is noticed on the FHP website, the SWIFT SunGuide Center operations staff should notify FHP dispatch as soon as possible so they can take corrective action. FHP website: Local Police & Fire Department Scanner Telvent Farradyne Page 119 Revised: 6/2/08

129 A local police and fire department scanner will be added to the SWIFT SunGuide Center when 511 duties commence. The scanner will be located in the 511 expansion area located next to the control room. The scanner will be monitored at all times and will be set at a volume that is clearly audible to all 511 employees. The scanner receives Collier, Lee, and Sarasota County police, fire, and public services. Some of the non-essential channels are locked out, but not all. Some channels are labeled, but most have 5 to 6 digit codes that could be police, fire, or other town/city services. Obviously, these local agencies respond to I-75 for incidents. The 511 operators will be responsible for reporting an incident that is heard on the scanner to the RTMC operators for use in verifying incidents. Depending on the set up, a response channel will carry information from the scene. This might be the channel to HOLD when units arrive to gather details about a scene. This incoming information can be useful and should be confirmed with CCTV cameras, Road Rangers, FHP, or the local fire department before commencing incident response procedures. Key words or phrases to listen for include: o Code 4 means accident o Traumahawk medical helicopter that responds to incident scenes If the scanner gets out of the trunk mode, it will make a loud grinding noise. Follow the procedures below to fix this problem. o Hit MANUAL o Hit TRUNK o Hit SCAN o Check the upper display to make sure SEARCH is showing. If not, select the SEARCH button. o Ensure that TRUNK is displayed on the screen. This is the only way to properly receive these two systems Telephone Alert Should the SWIFT SunGuide Center operations staff be alerted to an incident by a traveling staff member or any other non-*fhp civilian caller, the SWIFT SunGuide Center operations staff shall question the caller to get the correct location and direction of travel of the incident. Ask the caller the following typical questions to elicit sufficient information for responders, such as: o What is the suspected problem? o Where are you? o Do you see any highway signs or markers that will determine your location? o What direction were/are you driving? o Are you on the shoulder or in the travel lane? o Can the car be moved to the shoulder (if in the lane)? o Do you require emergency service, such as an ambulance? o Using good judgment or at the request of a motorist, tell the caller the action you will take to assist them, such as dispatching a Road Ranger vehicle, calling FHP dispatch for assistance, locating them on SWIFT SunGuide Center CCTV camera, etc. When an incident is detected by a motorist or other non incident confirmation source, the SWIFT SunGuide Center operations staff should take the following actions: o Create a new event in the SunGuide software. The initial information entered into the SunGuide software includes event type, notification source, and incident location. The Telvent Farradyne Page 120 Revised: 6/2/08

130 status of the event should be set as Unconfirmed in the SunGuide software at the creation of the new event. o If the lane blockage information is unknown, enter the lane closure information into the SunGuide software with a? over the lanes to show that the lanes blocked are unconfirmed. o Dispatch the closest Road Ranger. o Update the Road Ranger Dispatch table in the SunGuide software. This will inform the other SWIFT SunGuide Center operators and supervisors of the status of the Road Ranger and will make the dispatch of other Road Rangers more efficient. o Notify FHP dispatch personnel of the possible incident with initial incident details. o If CCTV camera coverage is available at the event location, scan the camera to monitor the event and begin the steps necessary to make the confirmed event Active in the SunGuide software. o If the event can be seen by the CCTV cameras, update the event in SunGuide with the CCTV number. o If the event cannot be seen by the CCTV cameras, wait for the Road Ranger, FHP trooper, or other reliable incident responding agency to arrive on scene to confirm the event. Change the event status to Active in the SunGuide software. o Notify FHP dispatch personnel when the incident is confirmed and specific details are known. o If more than one lane is blocked, dispatch additional Road Ranger trucks to the incident to provide additional short-term MOT. Optimally, there should be one Road Ranger per lane blocked. o Proceed to the Incident Management Event Confirmation section of this document for additional details pertaining to the event confirmation process SWIFT SunGuide Center Account All operators must continuously monitor the pb-itms@telvent.abengoa.com throughout their shift. This is not a verification source; it is solely an information detection source. Once received, all information received must be verified by the appropriate agency. The pb-itms@telvent.abengoa.com address receives incident and event information alerts from Meredith Rapp for I-95 construction, Christie Klammer for arterial roadway construction, FDLE for Amber Alerts, Barbara Kelleher for newsworthy events in District 4, Channel 25 for weather warnings, Palm Beach ITMS for incident alerts, Broward TMC for incident alerts, District 6 TMC for incident alerts, and the Florida s Turnpike for incident alerts. All FDOT District 1 SWIFT SunGuide Center incident alerts are also sent to this address. To access this account, 1. Log into your Telvent account using Lotus Notes. 2. Select File Database Open 3. Type in Calgary/Telvent/Abengoa in the server list. 4. Press Enter. 5. Wait a few seconds, and a list of databases on the Calgary server will appear. 6. Scroll way down to the mail folder and double click it to open. 7. Scroll down to the database, highlight it, and click on Open Telvent Farradyne Page 121 Revised: 6/2/08

131 Insert new picture above messages are also forwarded from the shared folder to each individual SWIFT SunGuide Center operator mailbox. This gives the SWIFT SunGuide Center operations staff an additional opportunity to be notified. This should reduce the operator response time for amber alert, construction, weather, and newsworthy incidents. Of course, operators are expected to continue to check the shared folder and their individual accounts, as normal. Please note: messages from the Broward TMC and Florida s Turnpike TMC will not be forwarded to the individual operator s mailboxes, but will still be collected in the wpbtmo@pbworld.com shared folder with the above contacts Websites The SWIFT SunGuide Center operations staff will monitor several websites throughout their shifts. These websites are a valuable resource for incident detection. The SWIFT SunGuide Center operations staff will monitor the primary websites every 30 minutes or more frequently as time permits. Once an event is observed on a website, the SWIFT SunGuide Center operations staff will contact the source to verify the event, gather specific incident details, and determine whether assistance is required. The websites that are continuously monitored to detect incidents are: o Statewide o Local or o Southeast Florida o FHP o Broward TMC o Palm Beach ITMS o Florida s Turnpike TMC Telvent Farradyne Page 122 Revised: 6/2/08

132 o District 7 TMC xxx o District 5 TMC xxx Regional Traffic Management Centers Traffic management centers in Florida are the detection source of incidents outside the FDOT District 1 SWIFT SunGuide Center coverage area. The traffic management center responsible for the incident will contact the FDOT District 1 SWIFT SunGuide Center to request DMS message activation, when necessary. For additional information, please refer to the Regional Event Management section of this document Road Construction Monitoring The FDOT District 1 SWIFT SunGuide Center receives weekly construction notices from the FDOT District 1 PIO, FDOT District 4 Construction PIO, FDOT District 7 Construction PIO, and the Florida s Turnpike PIO. These notices are sent directly to the pbitms@telvent.abengoa.com office address which is also forwarded to each individual SWIFT SunGuide Center employee s address. Special construction project announcements are also sent from the above sources, when the information is too recent to be included in the weekly notices. The active monitoring of road construction and maintenance activities is the responsibility of all SWIFT SunGuide Center employees. The SWIFT SunGuide Center operations staff must know the condition of the highway network at all times. The receipt of the weekly and special notices will be coordinated through the RTMC Operations Manager. Construction Engineering Inspectors (CEI), who are responsible for the onsite and project coordination of construction projects, are expected to call the SWIFT SunGuide Center operations staff at the start and end of the lane closure activities. The SWIFT SunGuide Center operations staff should contact the CEI responsible for the construction project whenever they have questions or concerns about the roadwork start times or lane closure configurations. The contact information for the CEI is given in the Emergency Contacts section of this document. A FHP trooper is stationed at every long term construction site when travel lanes are closed, so construction information may also be provided by FHP dispatch when asked. The SWIFT SunGuide Center operations staff should review the construction notices that are provided to the SWIFT SunGuide Center at the beginning of every shift so they may anticipate these planned events and lane closures. The SWIFT SunGuide Center CCTV cameras that may potentially view the construction activities should be turned in the direction of the scheduled construction work and frequently monitored to allow for fast detection and response. All construction work that disrupts the flow of traffic, blocks travel lanes, or blocks emergency lanes will be entered as events into the SunGuide software WINK Radio Traffic Broadcasts The SWIFT SunGuide Center operations staff must monitor the WINK-96.9 FM traffic reports on the web from 0500 to 1900 hours on weekdays. This streaming broadcast will be used to supplement unconfirmed incident information from the local police and fire department scanner, FHP dispatch, local agency websites, and other detection sources. Traffic reports are supplied by the Fort Myers Broadcasting Company, and air on the "5s" during rush hours and at the top and bottom of the hour at all other times. The general website is The live streaming podcast address is: Telvent Farradyne Page 123 Revised: 6/2/08

133 15 Incident Management Event Confirmation 15.1 CCTV Confirmation Once an incident is detected, it will be verified by using the SWIFT SunGuide Center CCTV cameras when possible. The cameras should be moved to view the general area where the incident was reported until the incident is found. The basic method is to take command of the camera, use the presets to quickly move the camera to the likely incident location. If the crash is not found on a preset view, the area should be scanned manually by using the PTZ function of the camera. Once the incident is located, center the camera on the incident location and then zoom into the incident scene to determine the lanes affected and the potential impact. This increases the ability to quickly zoom without having to re-center the image. As stated in the SWIFT SunGuide Center SOG, never zoom in closely enough on the incident scene to clearly view a person or vehicle! Remember that all images that are seen by the SWIFT SunGuide Center operations staff may also be seen by the public and the media through the SWIFT SunGuide Center website. The CCTV camera images are not recorded, but on occasion, the SWIFT SunGuide Center operations staff may be directed to save snap shot picture of a Level 3 incident as defined in the Incident Level Definitions (With Examples) section of this document for use at the FDOT District 1 TIM Team meetings. The picture must be saved by using the SunGuide software. Saving images by using the vendor software causes the web address to appear at the bottom of the picture and is no longer acceptable for distribution outside the SWIFT SunGuide Center. If SunGuide is not available but the SWIFT SunGuide Center website is, the SWIFT SunGuide Center operations staff may take a print screen of the camera image off the SWIFT SunGuide Center website. After the incident clears, these saved camera images must be ed to the RTMC Shift Supervisors, RTMC Operations Supervisor, and RTMC Operations Manager. The RTMC Shift Supervisor must inform FHP dispatch that the incident can be seen on camera and the camera image should be placed in the appropriate location on the video wall. This will allow FHP dispatch to view the image, assess the situation, and make informed dispatch decisions. When an incident is detected and confirmed by a CCTV camera image on a workstation or on the video wall, the SWIFT SunGuide Center operations staff should take the following actions: o Create a new event in the SunGuide software. The initial information entered into the SunGuide software includes event type, CCTV number, and incident location. The status of CCTV workstation/video Wall detected events are Active and should be set as Active in the SunGuide software at the creation of the new event. o Dispatch the closest Road Ranger and update the Road Ranger Dispatch Table in the SunGuide software. This will inform the other SWIFT SunGuide Center operators and supervisors on duty of the status of the Road Ranger and will assist with the more efficient dispatch of the Road Ranger program. o If more than one lane is blocked, dispatch additional Road Ranger trucks to the incident to provide additional short-term MOT. Optimally, there should be one Road Ranger per lane blocked. o Proceed to the Incident Management Event Evaluation section of this document for additional details pertaining to the event evaluation process. Telvent Farradyne Page 124 Revised: 6/2/08

134 15.2 Road Ranger Confirmation This method generally means that the incident was not initially found with the SWIFT SunGuide Center CCTV cameras and that the Road Ranger driver was the first responder on the scene of the incident. In this type of situation, the Road Ranger driver is both the incident detection and verification source. The Road Ranger program is one of the incident response agencies that the SWIFT SunGuide Center can utilize to verify incidents. Road Rangers work closely, and are dispatched, by the SWIFT SunGuide Center operations staff and almost always stay at the incident scene until cleared. This is a huge help to operations, because the Road Ranger can communicate with other incident response agencies and can provide continuous incident updates. The SWIFT SunGuide Center Operator should attempt to locate the incident on the SWIFT SunGuide Center CCTV cameras to provide an additional source of verification. In areas outside of camera coverage, it is important to know when the Road Ranger clears the scene and the status of the congestion at that time. It will determine the actions taken by the staff and will ensure that timely and accurate incident information is given to the public. The SWIFT SunGuide Center operations staff should maintain contact with the Road Ranger driver until the congestion resulting from the incident clears. When an incident is detected and confirmed by a Road Ranger, the SWIFT SunGuide Center operations staff should take the following actions: o Create a new event in the SunGuide software. The initial information obtained from the Road Ranger is entered into the SunGuide software includes Event Type, Road Ranger Truck Number, and location. The status of the event should be set as Active in the SunGuide software upon creation. Other information may also be gathered in the initial communication and noted on a pad to be entered into the SunGuide software as time permits. If the Road Ranger requests additional support, the SWIFT SunGuide Center operations staff will dispatch the closest Road Ranger, if available. o Update the Road Ranger Dispatch table in the SunGuide software. This will inform the other SWIFT SunGuide Center operators and supervisors of the status of the Road Ranger and will make the dispatch of other Road Rangers more efficient. o If CCTV camera coverage is available at the event location, scan the camera to monitor the event and provide a secondary confirmation to the information provided by the Road Ranger. o If the event can be seen by the CCTV cameras, update the event in SunGuide with the CCTV number. o If more than one lane is blocked, dispatch additional Road Ranger to provide additional short term MOT. Optimally, there should be one Road Ranger per lane blockage. o Proceed to the Incident Management Event Evaluation section of this document for additional details pertaining to the event evaluation process Florida Highway Patrol Confirmation FHP dispatch is located in the control room of the SWIFT SunGuide Center and will regularly communicate with the SWIFT SunGuide Center operations staff. FHP dispatch will assist the SWIFT SunGuide Center operations staff to detect incidents, verify incidents, and share other pertinent incident details. The SWIFT SunGuide Center operations staff may also request incident information, request missing incident details for incident reporting, and inquire about the verification of FHP website CAD data. Telvent Farradyne Page 125 Revised: 6/2/08

135 The SWIFT SunGuide Center Operator should attempt to locate the incident on the SWIFT SunGuide Center CCTV cameras to provide an additional source of verification. In areas outside of camera coverage, it is important to know when FHP clears the incident scene and the status of the congestion at the time. It will determine the actions taken by the staff and will ensure that timely and accurate incident information is given to the public. The SWIFT SunGuide Center operations staff should maintain contact with FHP dispatch until all travel lanes are reopened. The RTMC Shift Supervisor must inform FHP dispatch that the incident can be seen on camera and the camera image should be placed in the appropriate location on the video wall. This will allow FHP dispatch to view the image, assess the situation, and make informed dispatch decisions. When an incident is confirmed by FHP dispatch, the SWIFT SunGuide Center operations staff should take the following actions: o Collect the following information: type of incident, location of incident, roadway name, direction, proximity to exit or cross street, lane closure information, vehicle information (make, model, tag number), injuries, HazMat information, fire involved?, and FHP incident number. o Create a new event in the SunGuide software. The initial information obtained from FHP dispatch is entered into the SunGuide software includes Event Type, source (FHP), and location. The status of the event should be set as Active in the SunGuide software upon creation. Other information may also be gathered in the initial communication and noted on a pad to be entered into the SunGuide software as time permits. o If for some reason the lane blockage information is unknown, enter the lane closure information into the SunGuide software with a? over the lanes to show that the lanes blocked are unconfirmed. o Dispatch the closest Road Ranger. o Update the Road Ranger Dispatch table in the SunGuide software. This will inform the other SWIFT SunGuide Center operators and supervisors of the status of the Road Ranger and will make the dispatch of other Road Rangers more efficient. o If CCTV camera coverage is available at the event location, scan the camera to monitor the event and provide a secondary confirmation to the information provided by the Road Ranger or FHP. o If the event can be seen by the CCTV cameras, update the event in SunGuide with the CCTV number. o If more than one lane is blocked, dispatch additional Road Ranger to provide additional short term MOT. Optimally, there should be one Road Ranger per lane blockage. o Proceed to the Incident Management Event Evaluation section of this document for additional details pertaining to the event evaluation process. Telvent Farradyne Page 126 Revised: 6/2/08

136 15.4 Event Confirmation Flowchart Telvent Farradyne Page 127 Revised: 1/31/08

137 16 Incident Management Event Evaluation Active events need to be evaluated when first detected and confirmed, because the severity of the events determine the various levels of SWIFT SunGuide Center operations staff response. The first step in evaluating an event is to collect all of the available information and log it into the SunGuide software. In practice, it is not always possible to thoroughly and accurately evaluate event severity when the event is first detected. Because of this, the SWIFT SunGuide Center operations staff will continuously monitor the active traffic events for more data until the event ends. The SWIFT SunGuide Center operations staff will immediately update the data in the SunGuide software and re-evaluate the event as new information becomes available. For example, the SWIFT SunGuide Center operator witnesses a seemingly minor two car crash blocking the left lane. There is no visible damage to the vehicles. The event is classified as a Level 1 incident and the appropriate actions for Level 1 incidents are taken. FHP dispatch then receives a telephone call from one of the involved parties who relay that the accident occurred because the driver of one of the cars veered and struck their car because of a medical emergency. This is confirmed by the FHP trooper (through FHP dispatch) and the Road Ranger when they arrive on scene. The event should now be upgraded to a Level 2 incident because it will most likely block travel lanes for longer than expected. The SWIFT SunGuide Center then takes the appropriate actions for the Level 2 incident response Incident Level Definitions (With Examples) The incident level classifications are given in the Incident Level Definitions section of this document, but are also included here for reference. Level 1: Incidents of any duration that do not close travel lanes (shoulder incidents, delays, event delays, Amber alerts, etc.) or the "Start Time" to "Clear Time" duration of a lane closing (not road closing) incident is estimated to be less than 30 minutes. Examples of typical Level 1 incidents are given below. o Minor debris in the travel lanes that can be moved to the shoulder by one Road Ranger or FHP trooper. o Disabled vehicles in the travel lanes that can be moved to the shoulder or quickly serviced by the Road Rangers. o Minor vehicular accidents, such as fender benders in the travel lanes that can be moved on their own or by the Road Rangers. Level 2: The "Start Time" to "Clear Time" duration of a lane closing incident is estimated to be 30 minutes or greater but less than 2 hours. This does not include a full closure of the roadway. Examples of typical Level 2 incidents are given below. o An event detected by a Road Ranger on scene with a lane blockage that doesn t have a clearance time. o Road Ranger on scene requests additional Road Rangers o An event involving minor injuries that require fire rescue or ambulatory services. o Spilled loads that require additional responding agencies, such as: FDOT Maintenance, Asset Management Contractor, additional towing equipment, etc. o Disabled tractor trailer or overturned non-commercial vehicles that require additional towing equipment. (The wrecker requirements for different sized vehicles are located in the Wrecker Services and Classifications section of this document.) Telvent Farradyne Page 128 Revised: 1/31/08

138 Level 3: The "Start Time" to "Clear Time" duration of a lane closing incident is estimated to be 2 hours or greater or all travel lanes are blocked on any roadway or ramp. Significant area-wide congestion is expected (but not necessary). Examples of typical Level 3 incidents are given below. o Any event involving a total road closure for any amount of time o An event involving a fatality or having serious injuries o Events involving passengers that need to be extracted from their vehicles o An event involving an overturned tractor trailer or commercial vehicle o Accidents involving a large amount of debris that require additional resources o Events involving HazMat spill and response o Emergency roadwork projected to last greater than 2 hours o Overnight roadwork that lasts past 0600 hours o Daytime roadwork that lasts past 1600 hours o Infrastructure damage that impacts travel lanes or creates an unsafe environment 16.2 Wrecker Services and Classifications FHP dispatch and FHP on scene personnel are responsible for contacting towing companies to dispatch appropriate tow trucks and wrecker services to incident scenes. A list of the different types of tow trucks and wreckers is given below for informational purposes only. Currently, there are two different procedures for FHP to dispatch wrecker services to the scenes of an incident. These services include Triple-A (AAA) and rotation tows. o When a motorist requires AAA, they may notify the Road Ranger or FHP troop on scene and request that service. This action is acceptable for quick clearance because AAA companies are always local and the arrival times are usually within an acceptable time frame. The Road Ranger on scene will notify the SWIFT SunGuide Center operations staff of the request. The operations staff will then notify FHP dispatch and place the appropriate CCTV image of the scene on the video wall. FHP dispatch will then decide what type of equipment is necessary from the CCTV image on the video wall or at the recommendation of the FHP trooper on scene. Once a determination is made, FHP dispatch will make the appropriate contacts and dispatch wrecker services to the scene. The FHP trooper on scene will notify FHP dispatch of the request and will make a recommendation for the wrecker services needed. Once a determination is made, FHP dispatch will make the appropriate contacts and dispatch wrecker services to the scene. o If a motorist does not have AAA, FHP dispatch is responsible for sending a rotation tow to the scene. The rotation tow policy that was created by and is currently followed by FHP so that all qualified and reputable wrecker companies in the incident coverage area are contacted equally and fairly, towing services arrive on scene in a timely manner, to safeguard the vehicle owner s property, to protect the persons who remove the vehicles towed by the authority of FHP, and to provide a record of towed and stolen vehicles. The Road Ranger on scene will notify the SWIFT SunGuide Center operations staff that the motorist does not have AAA service but wrecker services are requested. The operations staff will then notify FHP dispatch and place the appropriate CCTV image of the scene on the video wall. FHP dispatch will then decide what type of equipment is necessary from the CCTV image on the video wall or at the recommendation of the FHP trooper on scene. Once a Telvent Farradyne Page 129 Revised: 1/31/08

139 determination is made, FHP dispatch will make the appropriate contacts and dispatch wrecker services to the scene. The FHP trooper on scene will notify FHP dispatch of the request and will make a recommendation for the wrecker services needed. Once a determination is made, FHP dispatch will make the appropriate contacts and dispatch wrecker services to the scene. Telvent Farradyne Page 130 Revised: 1/31/08

140 Wrecker classifications are as follows. Telvent Farradyne Page 131 Revised: 1/31/08

141 Telvent Farradyne Page 132 Revised: 1/31/08

142 17 Incident Management DMS Response Plan The SunGuide software Incident Management Module (IM) is a tool for the SWIFT SunGuide Center operations staff to generate DMS response plans. This section provides the procedures for using this tool. The default messages to be displayed on the DMS are travel times. The RTMC operations staff also uses DMS to post messages that inform the public of traffic conditions, such as travel lanes blocked. It is critical to post timely messages to gain and maintain the motoring public s confidence in the SWIFT SunGuide Center and the system. There is a module within the SunGuide software, called Incident Management or IM, which is used to create DMS response plans. The module evaluates user-defined criteria, such as location, lane blockage, and search distances for DMS devices, to develop a suggested messaging plan. This function is intended to reduce the time to post messages to the DMS and improve overall operations. The DMS messages used for the SWIFT SunGuide Center DMS response plans are preprogrammed into the software. DMS messages not currently programmed into the system must be added to the program before they can be activated into the system. If any DMS messages are necessary for an incident and are not located in the system, the RTMC Operations Manger must be contacted immediately. For further information about the content of the DMS messages, please refer to the SWIFT SunGuide Center DMS SOP document DMS Response Plan Guidelines When generating DMS Response Plans, the RTMC operations staff shall adhere to the following guidelines. o DMS shall be used for all events with blocked travel lanes. o Always review the DMS Response Plan before sending out to the DMS. If possible, have a shift supervisor or designee review the DMS messaging content and DMS sign selection before activating the DMS messages. o When multiple events occur simultaneously, each DMS shall message for the event closest to that DMS. o Active lane closing events receive a higher priority for messaging than Amber Alerts. o Amber Alert events have a higher priority for messaging than pre-warning events. o Pre-warning events have a higher priority than public service announcements DMS Message Priority When generating and activating DMS response plans, the SWIFT SunGuide Center operations staff must adhere to the following guidelines. o DMS will be used for all events with blocked travel lanes. o DMS will be used for all abnormal delays o DMS will be used for rush hour delays Telvent Farradyne Page 133 Revised: 1/31/08

143 o Always review the DMS response plan before activating the DMS messages. It is possible for the system to suggest inaccurate messages or DMS device locations. o If possible, have the RTMC Shift Supervisor review the DMS messaging and DMS device location selection before activating the DMS messages. o When multiple events occur simultaneously, each DMS will message for the event that is closest to that DMS, unless directed otherwise by management. o Active events receive a higher priority for messaging than travel time, Amber Alert or planned special event messages. o Amber Alert messages receive a higher priority than planned special event messages. o Planned special event messages receive a higher priority than public service messages. o Public service messages receive a higher priority than travel time messages, which are the default message type depending on the time of day DMS Response Plan Flowchart The DMS Response Plan Flowchart depicts the steps that are necessary to utilize the IM module within the SunGuide software. Telvent Farradyne Page 134 Revised: 1/31/08

144 Telvent Farradyne Page 135 Revised: 1/31/08

145 17.4 DMS Message Credibility The message design and display of the DMS messages must provide timely, reliable, accurate and relevant information and the DMS must be operated properly to be effective. Credibility is an extremely important consideration in properly operating a DMS system. Regardless of how well a message is designed, motorists will eventually come to distrust the signing system if the messages are not changed at the correct times and updated to reflect current traffic conditions. Each time the information displayed is disproved, the credibility of the system decreases. Eventually the messages are ignored and the DMS system is in jeopardy. There are several reasons why message credibility suffers: o Information is not correct. This can happen when the DMS message is not consistent with current conditions, etc. o Information is irrelevant to essentially all motorists using the facility. o Information is repetitive. This can happen when the DMS message is the same each morning when motorists pass the sign. This will normally happen when DMS messages are programmed to automatically activate at the same time each day. Displaying the same information daily may result in many motorists ignoring the DMS messages over time and they may not read more important messages that will impact their trip. Please not that this does not apply to daily rush hour traffic delays because these types of messages reflect current conditions and is valuable real time information. o Information is trivial. Trivial messages include DRIVE SAFELY, BUCKLE UP, time and temperature, and other public service messages. Displaying these types of messages consistently can result in many motorists (particularly commuters) ignoring the messages because they have no direct impact on their trips and consequently will begin ignoring all DMS messages in general. When an important trip-affecting message is displayed in the future, motorists may not read the message. To ensure that DMS credibility remains high, message accuracy must be a top priority for the SWIFT SunGuide Center operations staff. The SWIFT SunGuide Center operations staff must constantly monitor incidents and modify messages as the situation changes. The SWIFT SunGuide Center operators are responsible for activating and deactivating DMS messages. The RTMC Shift Supervisors are responsible for ensuring that all DMS messages are accurate, displayed on the appropriate DMS device, and removed when no longer needed DMS Message Activation Procedure General Only real-time information about incidents, traffic, roadwork, environmental, or pavement conditions that could have an effect on driver safety and traffic efficiency shall be displayed on the DMS. The following exceptions may occasionally be displayed o Advance notification of roadwork requiring lane closures within one week of the roadwork o Advance notification of special events that will adversely affect travel either because of added traffic generated or the requirement to close streets or highways All DMS in the FDOT District 1 SWIFT SunGuide Center coverage area that motorists may possibly encounter before arriving at an incident must be activated for full road closures and Level 3 incidents. The SWIFT SunGuide Center operations staff must also activate all arterial DMS, if installed, within at least 25 miles of Level 1 and Level 2 incidents. Inclusion of DMS located before at least 1 connector to another state roadway is also required for all incident types. The SWIFT SunGuide Center operations staff may only activate DMS messages listed in the SWIFT SunGuide Center DMS Standard Operating Procedures document. When an incident Telvent Farradyne Page 136 Revised: 1/31/08

146 requires a DMS message not found in the SWIFT SunGuide Center DMS SOP, the RTMC Shift Supervisor must contact the RTMC Operations Manager or designee for DMS message approval. If contact cannot be made with the RTMC Operations Manager within 5 minutes, the RTMC Operations Supervisor must be called for DMS approval. Local law enforcement agencies may request for the operations staff to post DMS messages on the devices that are not pre-approved in the DMS SOP document. These requests may be for public service announcements, for assistance to apprehend violent criminals, detour suggestions when no actual detour is in place, non-traffic related messages, etc. When requests of this nature are received, the operations staff must ask the requesting agency for the following information. o Who is requesting the DMS message content? o The contact number for the requesting party o The suggested duration of the DMS message o The suggested content of the DMS message The operations staff should then tell the requestor that they will work on their request and that a FDOT representative will be in contact with them shortly. The operations staff must then immediately contact the RTMC Operations Manager, who will then contact the FDOT RTMC Manager and one of the following individuals to make a decision concerning the request. Kevin J. Thibault, P.E. Assistant Secretary for Engineering & Operations Florida Department of Transportation 605 Suwannee Street, MS 57 Tallahassee, FL Work: (850) Ananth Prasad Florida Department of Transportation 605 Suwannee Street, MS 57 Tallahassee, FL Work: (850) FDOT has final authority over the use of the DMS signs and message content DMS Message Activation Procedure Long Term Road Work The SWIFT SunGuide Center operations staff should treat long-term construction lane and road closures similar to the normal daily road work closures. o DMS messages should be activated and maintained throughout the duration of the longterm construction. o The DMS messages activated for long-term construction should be treated as default messages when other incidents occur, which means that they will have the lowest possible DMS message activation priority. If possible, split DMS messaging is preferred (consult the SWIFT SunGuide Center DMS SOP). Otherwise, the long-term construction messages can be replaced with messages for more pressing incidents. o An active SunGuide incident report should be created and maintained throughout the long-term construction. o The SWIFT SunGuide Center website should inform motorists of the construction. The SWIFT SunGuide Center operations staff must activate OPEN DMS messages and create a new SunGuide incident report that is linked to the original event for completed long-term Telvent Farradyne Page 137 Revised: 1/31/08

147 construction closures. The OPEN DMS messages should be displayed until midnight after the next business day. This is an adequate amount of time because it will inform commuters that there was a change to the affected roadway during at least two separate rush hour periods. Contact the RTMC Operations Manager or the RTMC Operations Supervisor if there are any questions with this procedure or if the proper DMS message content is not found in the SWIFT SunGuide Center DMS SOP DMS Message Activation Procedure Travel Times Travel time messages will be the default messages displayed on the DMS devices during peak travel times. Travel times are calculated by utilizing the current average speeds from the radar readings between the DMS device and the target locations (TBD). FDOT requires statewide consistency in appearance and information displayed on the DMS, so all districts follow the same format to display the information. o The first line will indicate the destination o The second line will indicate the mileage to the destination o The third line will provide the average estimated travel time to the destination, or the average estimated travel time for the posted speed limit when the average speeds are higher than the posted speed limit FDOT expects each district to define the minimum and maximum travel times that will be displayed on the DMS (TBD) DMS Message Activation Procedure - Test Messages It is sometimes necessary to display messages on a DMS to perform the daily field equipment tests, assure correct operation, to burn-in new signs, or for special studies. Acceptable test messages include an approved TEST message or a non-message test pattern such as illuminated columns or rows. Approved TEST style DMS messages may be found in the SWIFT SunGuide Center DMS SOP. Other test messages shall be reviewed and approved by the RTMC Operations Manager before the messages are displayed Camera Verification of DMS Message Content Some SWIFT SunGuide Center DMS CCTV cameras can be directed to see active DMS messages. The SWIFT SunGuide Center operations staff should attempt to verify the displayed DMS message content in the field shortly after activating DMS messages for an incident. The SWIFT SunGuide Center operations staff should also use these cameras to verify DMS field equipment failures and DMS messages that cannot be deactivated before dispatching Road Rangers to the scene to verify the problem. The following table lists all current verification possibilities. SWIFT SunGuide Center CCTV Camera SWIFT SunGuide Center DMS Verified Remarks 22 4 Difficult to read during the daytime 37 6 Difficult to read during the daytime Telvent Farradyne Page 138 Revised: 1/31/08

148 The Possible, but unknown b/c camera is not functional Telvent Farradyne Page 139 Revised: 1/31/08

149 18 Incident Management Event Notification This section establishes the procedures for notifying partner agencies to ensure that traffic information is disseminated to interested parties, traffic events have the most efficient incident response, and all necessary resources are sent to the incident scene as quickly as possible. In addition to the Emergency Contact Numbers section of this document, all telephone numbers for these SWIFT SunGuide Center partner agencies can be found in the SWIFT SunGuide Center SOG. Descriptions of these agencies are given in the Local, Regional, and Statewide Agencies section of this document Event Notification Text Alerts The External Communications section of the SunGuide Software facilitates the dissemination of information through and text alerts by providing messages using a template which will be predefined by the RTMC Operations Manager and approved by FDOT. Messages in External Communications are automatically generated by the system, based on data entered and saved on the Event Data Entry form. Select the External Communications link to open the editor section as described in detail in the SunGuide Software Manual document. Some general information may also be referenced in the Input sub-section of the SunGuide Software Data Management section of this document. Adding, changing, or saving lane blockage information will automatically open the section for editing. The SWIFT SunGuide Center operations staff is expected to send SunGuide incident and special event pages to the SWIFT SunGuide Center partner agencies by incident level, time of day, and paging type. o Incident Levels Level 1, Level 2, or Level 3 o Time of Day Normal Business Hours are Monday through Friday from hours and After Hours are daily from 2101 to 0559 and all times on Saturday and Sunday. o Paging Type The two types of pages are the Initial and Cleared and Update pages. Initial and Cleared pages include the first notification page, the all travel lanes open page, and the all delays cleared page for incidents. Update pages include 20 minute update pages, delay start and update information pages, and incident status or detail update pages Event Notification Categories As stated above, the correct group must be selected by the operators for each page sent. All the paging categories are listed below. Level 1 Incident: o Normal Business Hours (M-F ) Initial and Cleared pages o Normal Business Hours (M-F ) Update pages o After Hours & Weekends (All other times) Initial and Cleared pages o After Hours & Weekends (All other times) Update pages Level 2 Incident: o Normal Business Hours (M-F ) Initial and Cleared pages o Normal Business Hours (M-F ) Update pages o After Hours & Weekends (All other times) Initial and Cleared pages Telvent Farradyne Page 140 Revised: 1/31/08

150 o After Hours & Weekends (All other times) Update pages Level 3 Incident: o Normal Business Hours (M-F ) Initial and Cleared pages o Normal Business Hours (M-F ) Update pages o After Hours & Weekends (All other times) Initial and Cleared pages o After Hours & Weekends (All other times) Update pages Miscellaneous Event Notification Categories: o Special Event (All times) Includes weather alerts, events with large crowd and congestion potential, newsworthy events, etc. o Child Abduction Alert (All times) Includes all active Amber alerts o Administration (All times) Includes pages for systems related issues, video wall failures, global DMS and camera failures, problems contacting SwRI for website issues, and other INTERNAL informational type notifications. o Construction (All times) Includes scheduled construction activities that may significantly impact traffic. Normally, incident alert messages are not sent for scheduled construction o Testing (All times) Used by the RTMC IT Technician and RTMC IT Manager to test the SunGuide communications system. The SWIFT SunGuide Center operations staff will only use this group at the request of the RTMC IT Technician, RTMC IT Manager, FDOT, or SWIFT SunGuide Center management. o SWIFT SunGuide Center Bulletin (All times) Used for newsworthy events which take place that may affect traffic. Examples include: construction accidents involving injuries, crime scenes that may impact traffic or traffic flow, incident response or tow truck personnel that get struck by vehicles, incidents that require an investigation for a fatality or possible fatality, incidents causing delays that are greater than or equal to 10 miles, etc. o Global (All times) Includes RTMC promotional pages, etc. The following rules are necessary for clarification and must be strictly adhered to: 1) All the miscellaneous paging messages must be supervisor approved except for the Child Abduction Alerts. For procedures on how to handle paging notifications for Child Abduction Alerts, please consult the Amber Alert Procedure sub-section of the Procedures Specific Incident Types section of this document. 2) An Initial and Cleared page is the correct paging category for i. Incident start (Subject Line will state Active ) ii. All lanes are open with or without delays (Subject Line will state Cleared ) iii. Traffic resumes to normal time of day volume (Subject Line will state Cleared ) iv. Incident upgrades from Level 1 to Level 2 v. Incident upgrades from Level 2 to Level 3 vi. A road closure or ramp closure reduces travel lane impact to one or more lanes blocked from all lanes blocked. (Subject Line will state Active ) vii. The first time a page is sent with fuel spill information 3) An incident must be immediately categorized as a Level 3 incident whenever the incident involves a total roadway closure, an overturned tractor trailer or commercial vehicle that blocks at least one travel lane, a fuel spill greater than 40 gallons, emergency road work projected to last greater than 2 hours, overnight road work that lasts past 0600, and daytime road work that lasts past ) An incident is considered to be newsworthy once delays are greater than or equal to 10 miles in length. Telvent Farradyne Page 141 Revised: 1/31/08

151 18.2 Event Notification SWIFT SunGuide Center Website The main purpose of the SWIFT SunGuide Center website is to provide a web interface for FDOT and the traveling public with current traveler information. The website provides incident reports, a speed detection map, and an active DMS message display. The website is maintained by the RTMC Operations Manager. The operation and programming of the SWIFT SunGuide Center website is transparent to the SWIFT SunGuide Center operations staff. Website maintenance shall be coordinated with the RTMC Operations Manager or designee. The website address is: Event Notification Newsworthy Events The RTMC Operations Manager or the RTMC on-call supervisor must be notified whenever there is a newsworthy event taking place in the SWIFT SunGuide Center coverage area that concerns traffic on I-75 or any arterial which impacts the interstate operations. Examples of newsworthy events include: o A construction worker fatality or injury o A police chase that closes I-75 or any arterial roadways which impact the interstate operations o they arrest the suspects of a shooting at Walgreen s o Any tow truck driver or pedestrian that is struck by a vehicle o A FHP crime scene o An incident that requires an investigation for a fatality or possible fatality (travel lane blocked or shoulders blocked) o Any incident that causes delays that are greater than or equal to 10 miles 18.4 Event Notification Crashes in Work Zones Crashes in construction areas and work zones on I-75 will be reported directly to the appropriate construction contractor, asset management firm contact, the ITS Maintenance Contractor and, when serious injuries are involved, the FDOT District 1 PIO. Crashes in construction areas and work zones on other state roadways in District 1 will be reported directly to the FDOT District 1 Maintenance contact. Crashes in construction areas and work zones outside of District 1 should be reported to the appropriate TMC. Each TMC is responsible for contacting the appropriate agencies in their area Event Notification Flowchart Please refer to the following page for the event notification flowchart. Telvent Farradyne Page 142 Revised: 1/31/08

152 Telvent Farradyne Page 143 Revised: 1/31/08

153 18.6 Event Notification SWIFT SunGuide Center Agency Contact List Telephone numbers, contact priorities, and contact procedures for the SunGuide paging groups are given in the SWIFT SunGuide Center Agency Contact List. These documents are shown below. Sample ITMS documents will add the SWIFT SunGuide Center version of this document when created. Telvent Farradyne Page 144 Revised: 6/2/08

154 Telvent Farradyne Page 145 Revised: 6/2/08

155 Telvent Farradyne Page 146 Revised: 6/2/08

156 Telvent Farradyne Page 147 Revised: 6/2/08

157 Telvent Farradyne Page 148 Revised: 6/2/08

158 19 Incident Management Event Monitoring After the detection, evaluation, implementation of DMS response plans, and all notifications are made for an event, the event shall be monitored continuously until all evidence of the event have been removed from the scene. The SWIFT SunGuide Center operations staff should use the CCTV cameras as a primary resource to monitor events. The staff will maintain the CCTV camera used to monitor the event scene at a wide angle view on the area until all responding agencies have departed. The SWIFT SunGuide Center operations staff will maintain awareness of the image and its appropriate content throughout the event. If the image should not be viewed by the public, then block the CCTV camera image by using the SunGuide software. Unblock the CCTV camera image as soon as the scene is acceptable for viewing again. The SWIFT SunGuide Center operations staff will use the CCTV cameras upstream of the events to monitor delays and secondary crashes. For example: the staff should monitor the CCTV cameras north of the event for southbound incidents. The cameras north of the event are considered to be upstream of the CCTV camera that is monitoring the incident scene. The SWIFT SunGuide Center operations staff will also use the CCTV cameras downstream of the events to monitor onlooker/rubbernecking delays in the opposite direction. Significant delays will warrant event creation and DMS message activation. The event in SunGuide must be linked to the original event for reference. The SWIFT SunGuide Center operations staff should also use the CCTV cameras to monitor the DMS messages that are activated for incidents to ensure that the correct messages are on the DMS. Different types of event changes warrant different responses as indicated in the Event Monitoring Flowchart below. These event changes include: o Detected secondary event o Additional emergency responders arrived and departed o Road Ranger needs additional assistance from another Road Ranger. For example: MOT for additional blocked travel lanes, assistance with clearing debris or vehicles from the travel lanes, etc. o Travel lane blockage increased or decreased o Extended traffic queues require changes to DMS plan o An unusual or unique occurrence takes place. Examples may include shootings or other police related activities, motorists that wander or do not cautiously cross the roadway, etc. o Detected HazMat, injuries, damage to the roadway, or any other event requiring additional resources o Event ends The SWIFT SunGuide Center operations staff will adhere to the following guidelines when responding to event changes. o Immediately update event details in the SunGuide software o A new event will be created by being cloned and linked to the original event when the incident scene has been cleared and the delays shift to a different ending point than the original incident exit/location o Events where the scene has not been cleared can only be reopened within 30 minutes after the initial closure of the event. If this timeframe is exceeded, a new event must be created and documented accordingly. Telvent Farradyne Page 149 Revised: 1/31/08

159 o Update the DMS Message Plan and incident notification alerts o Notify all applicable responding and partner agencies including: Road Rangers, FHP, other traffic management centers, local police, local fire departments, traffic engineering departments, etc. when appropriate. o All telephone calls must be logged into the Incoming/Outgoing Contact Microsoft Access Database and in the SunGuide software. If there are any questions regarding the handling of events, the SWIFT SunGuide Center operations staff should request assistance from the RTMC Shift Supervisor, RTMC Operations Supervisor, or the RTMC Operations Manager Event Monitoring Flowchart Please refer to the following page for the event monitoring flowchart. Telvent Farradyne Page 150 Revised: 1/31/08

160 Telvent Farradyne Page 151 Revised: 1/31/08

161 20 Incident Management Event Closure The event closure process begins when all emergency response vehicles depart the event scene. Once the vehicles depart from the scene, the motorist or their vehicle may still remain at the scene on the shoulder Event Closure Flowchart Please refer to the following page for the event monitoring flowchart. Telvent Farradyne Page 152 Revised: 1/31/08

162 Telvent Farradyne Page 153 Revised: 1/31/08

163 20.2 Event Closure Flowchart Description The SWIFT SunGuide Center operations staff must follow the steps in the Event Closure Flowchart when a Road Ranger departs the incident scene. These steps are described in detail below. o The flowchart starts with a check to make sure the DMS Response Plan is blanked and all relevant agencies have been updated that the travel lanes have been opened. o If the motorist departs from the incident scene, the SWIFT SunGuide Center operations staff will request all relevant information from the Road Ranger and update this information in the SunGuide software. Then the SWIFT SunGuide Center operations staff should provide the confirmation number (the SunGuide software event number) to the Road Ranger, depart the Road Ranger in the SunGuide software, and close the event. o If the motorist and the vehicle remain on scene, the SWIFT SunGuide Center operations staff will request all relevant information from the Road Ranger and update this information in the SunGuide software. Then the SWIFT SunGuide Center operations staff will provide the confirmation number (the SunGuide software event number) to the Road Ranger, depart the Road Ranger in the SunGuide software, and change the event status to Unresolved. At this point, the event is placed in an unresolved status until all evidence of the event is removed from the shoulder or the vehicle becomes abandoned. o If the motorist has left the incident scene and the vehicle remains, the SWIFT SunGuide Center operations staff will clone the event to create a new abandoned vehicle event. Once the event has been cloned, the old event is closed. The cloned event will be an abandoned event type and will be placed in an unresolved state. (Note: the Road Ranger and other emergency response vehicles must be departed from the event before the event can be cloned.) o It is the responsibility of the RTMC Shift Supervisor to notify FHP dispatch when an abandoned vehicle is found on the shoulder and also when an abandoned vehicle has been on the shoulder for more than 72 hours. FHP dispatch will then submit a request for an FHP trooper to tag the vehicle with an abandoned motor vehicle sticker which notifies the motorist that they have 24 hours to move their car or it will be towed. o Vehicles that have been tagged with an abandoned motor vehicle sticker that are not removed from the roadway within 24 hours must be reported to the RTMC Operations Manager. o Each time the status of an unresolved event is verified, the RTMC operations staff must document the current status of the event by entering a comment in the Comments field. One example is as follows, Road Ranger truck #452 verified that this abandoned vehicle still occupies the right shoulder. Although motorists and their vehicles remaining on the scene may be in a safe location, they are still a traffic hazard. Therefore, it is important to monitor these shoulder events and assist FHP with the removal of abandoned vehicles on the shoulder Unresolved Events Unresolved events can be defined as events in which the SWIFT SunGuide Center has previously responded and managed. Essentially, unresolved events are vehicles that are located on a roadway shoulder and do not impede traffic flow. Telvent Farradyne Page 154 Revised: 6/2/08

164 It is expected that all TMC Operators continually check the status of unresolved events. Ideally, all unresolved events in the SunGuide system should be reviewed and updated every 1-2 hours and at the start and end of every shift. The guidelines for managing unresolved events are given below. o It is important that each shift check on vehicles that have been left in the unresolved status. When reviewing the unresolved events, begin with the event types other than Abandoned. These events need to be updated to reflect whether the vehicle has been abandoned or not. After the non-abandoned event types are updated, continue checking the Unresolved list. Start with the oldest first (bottom of list) and work towards the newer ones (top of list). These events should be checked every 1-2 hours during each shift and before and after each break and lunch has been taken. o If the event is not viewable via CCTV, contact a Road Ranger to verify the status the next time they patrol past the site. The contacted Road Ranger asked to report the status of the vehicle is treated as a dispatch in the SunGuide system. Therefore, the information is input through the Dispatch section in the event screen. Once the Road Ranger is on scene, Arrive the Road Ranger through the Dispatch section of the event. Select No Service as the Activity for the Road Ranger. Enter a Comment indicating Unresolved Event Verification. Depart the Road Ranger through the Dispatch section of the event. If the vehicle is still there and not occupied: Provide the Event ID to the Road Ranger. This number is then written on the vehicles rear window, along with the Road Ranger truck number, and date/time of marking. Depart the Road Ranger through the Dispatch section of the event. Click the Clone Event button in the SunGuide to change the event type status to an abandoned vehicle. If the vehicle is gone: Remove the lane blockage from the Event Detail screen. Depart the Road Ranger through the Dispatch section of the event. Change the event status from Unresolved to Closed. Provide the Event ID to the Road Ranger Lane Closing Incidents not Meeting the Goal of the Open Roads Policy The RTMC Shift Supervisors must provide the RTMC Operations Manager with a copy of SunGuide incident reports whenever the Open Roads Policy is not met within the expected time frame. These incident reports will be forwarded by the RTMC Operations Manger to the Local TIM Meeting coordinators, who will facilitate debriefing sessions to aid in the more timely removal of future incidents. Telvent Farradyne Page 155 Revised: 6/2/08

165 21 Procedures Specific Incident Types 21.1 Amber Alert Procedure Amber Alerts are used by law enforcement to quickly disseminate information to the public about child abductions. The process for Amber Alert activations is as follows. o Local law enforcement contacts FDLE o If local law enforcement contacts the RTMC and requests DMS activation for the Amber Alert, the RTMC operations staff must tell the local law enforcement agency that DMS messages will be activated once written confirmation is received from FDLE (through the District 5 RTMC in Orlando). o FDLE evaluates the request and issues an alert to other law enforcement agencies. o If FDLE agrees that DMS messages should be activated, FDLE contacts the FDOT District 5 Regional TMC in Orlando o The District 5 TMC issues the information to the other traffic management centers in Florida. Official Amber Alert telephone notifications will be received directly from the FDOT District 5 TMC in Orlando by fax and telephone. The SWIFT SunGuide Center operations staff will also receive and pager notifications from the Florida Department of Law Enforcement (FDLE) and from FHP dispatch. Once the Amber Alert is confirmed to be active and DMS are requested, the SWIFT SunGuide Center operations staff should perform the following actions. o Receive the fax and telephone call from the District 5 TMC. The fax is especially important because it is documented proof of the Amber Alert activation and the details are on the document which avoids confusion and errors. o Verify that the following information is given on the fax: activation request agency, child s name, area of activation (statewide or in the District 1 coverage area), date and time of activation, vehicle make, vehicle model, and vehicle tag number. o Enter the event into the SunGuide software. o It is imperative to enter the vehicle information into the Vehicles section of the SunGuide software. o The tag alert feature in the SunGuide will notify the SWIFT SunGuide Center operations staff if a duplicate tag has been entered. If this happens, give FHP dispatch all the details of the previous events. o Refer to the SWIFT SunGuide Center DMS SOP for appropriate DMS message format and content. Most Amber Alert DMS messages have two phases/frames. o Contact the on-call supervisor to approve the DMS message content. o Receive approval from the RTMC Operations Manager or the on-call supervisor to activate the DMS messages in the field. o Activate the Amber Alert message on all DMS in the FDOT District 1 coverage area. Please note that Amber Alert messages are used as a default and should be temporarily replaced by DMS messages with active incident information. Refer to the DMS Message Priority section of this document for additional information. o Send an Amber Alert page to the Child Abduction Alert paging group in the SunGuide software. Message content will be automatically generated by the SunGuide software, but the information must be double checked by the RTMC operations staff and the RTMC Shift Supervisor on duty before being sent. Telvent Farradyne Page 156 Revised: 6/2/08

166 o Confirm with the FDOT District 5 TMC and FHP dispatch that the Amber Alert is still active at the top of every hour. Log this information as comments in the SunGuide software and the Ingoing/Outgoing Contacts Microsoft Access database. o Send an Amber Alert page to the Child Abduction Alert paging group in the SunGuide software at the top of every hour until the Amber Alert is cancelled. When the Amber alert is cancelled, the SWIFT SunGuide Center operations staff will o Receive a faxed cancellation message from the FDOT District 5 TMC o Receive a verbal cancellation notification from the FDOT District 5 TMC. If not, the SWIFT SunGuide Center operations staff must contact the FDOT District 5 TMC for confirmation of cancellation. o Update the event in the SunGuide software. o Blank the Amber Alert messages from the DMS o Notify the RTMC Operations Manager or the on-call supervisor o Close the event in the SunGuide software LEO (Law Enforcement Offenders) Alert Plan The Florida Department of Law Enforcement (FDLE), in conjunction with the Florida Department of Transportation (FDOT) and the Florida Highway Patrol (FHP), has established the FLORIDA LEO ALERT PLAN. The purpose of the Florida LEO ALERT plan is to broadcast critical information of an offender(s) who have killed or seriously injured a law enforcement officer, and that if not apprehended immediately would pose a significant risk to the public. The information would be broadcast in a timely manner, to the general public via FDOT s highway Dynamic Message Signs and other highway advisory methods. In the event the offender(s) is seen or if anyone has knowledge on the identity of the offender(s), that information can be provided immediately to the investigating law enforcement agency. The Florida LEO ALERT plan can assist in dramatically increasing the chances of capturing the offender(s) rapidly before they leave the State of Florida. CRITERIA: To activate the alert, the following four (4) criteria must be met: 1. The offender(s) killed or critically injured a law enforcement officer. 2. The law enforcement agency s investigation must conclude that the offender(s) pose a serious public risk. 3. There must be a detailed description of the offender(s) vehicle to broadcast to the public (photos when available). 4. The activation must be recommended by the local law enforcement agency of jurisdiction. Note: To activate FDOT s Dynamic Message Signs, enough vehicle descriptive information along with a complete or partial tag number to benefit a broadcast on the signs must be available. PROCESS FOR ACTIVATION: The activation process must be followed in this order: Telvent Farradyne Page 157 Revised: 6/2/08

167 1. The local law enforcement agency will call the Florida Department of Law Enforcement / Florida Fusion Center (FFC) desk located in Tallahassee, Florida. The FFC desk is staffed 24/7 and is the point of contact for LEO ALERTS. a. An on-call Special Agent Supervisor will work in conjunction with the local law enforcement to ascertain whether the case meets the criteria and to offer additional help if needed. b. An on-call FDLE FFC analyst will work in conjunction with the FDLE FFC duty officer if the request comes in after hours. 2. The FDLE will work in conjunction with the local law enforcement agency of jurisdiction to determine if the information is to be displayed on FDOT s Dynamic Message Signs on a regional or statewide manner. 3. The FDLE will work in conjunction with the local law enforcement agency of jurisdiction to prepare information (i.e. suspect(s), and/or vehicle, contact information, etc.) for public distribution using approved format(s). 4. FDOT will provide the approved template to be used including vehicle description, tag number, and any other identifier. 5. If FDLE determines that the FDOT Dynamic Message Signs are to be used, then the FDLE will contact FHP Communications Center Shift Commander located in Orlando, Florida at (407) in order to alert duty officers and other call takers of the LEO ALERT. The FDLE will then fax all available information concerning the LEO ALERT to the FHP Communications Center located in Orlando at (407) The FHP Shift Commander in Orlando is then responsible for relaying all information via telephone and fax to the other Shift Commanders at the appropriate FHP Communications Center(s) in the region(s) where the activation is occurring. 6. The FDLE will then contact FDOT s Orlando Regional Transportation Management Center (RTMC) by calling (407) to develop the content of the message to be utilized. FDLE will then fax the actual DMS message to the Orlando RTMC at (407) , using the attached format. 7. The Orlando RTMC staff will relay the request to the appropriate RTMC staff in the State to activate the Florida LEO ALERT Plan. The FDOT will then display the message until the offender(s) are captured or for a maximum of six (6) hours. FDOT will display the alert message on all requested DMS s unless a traffic emergency occurs that requires an individual or group of DMS s to display a motorist safety message. FDOT will record a brief LEO Alert message on the 511 System. The 511 System is used only when the DMSs are displayed. 8. FDLE will follow the same activation steps listed above if an additional activation is required containing revised vehicle information and/or broadcast area. 9. Once FDLE is informed that the offender(s) have been captured, the FDLE will immediately contact the FHP Shift Commander at (407) and FDOT at (407) to cancel the alert. The FHP Shift Commander in Orlando is then responsible for relaying the cancellation information to the Shift Commander(s) at the FHP Communications Centers that were originally notified. The Orlando RTMC will then notify all other RTMC staff statewide that the LEO Alert has been cancelled; messages can be blanked from the DMSs and 511. THE REVIEW PROCESS: Each activation will be brought before a special committee of state agency partners and law enforcement representatives, to ensure that the program s goals are being met and that each activation meets the criteria and is conducted in a timely manner. Telvent Farradyne Page 158 Revised: 6/2/08

168 OTHER RESOURCES: Local media outlets Local Crimes Stoppers For more information about the Florida LEO ALERT Plan: Please contact the FDLE Florida Fusion Center Desk at or LEO Alert Plan DMS Message Template The suggested DMS message template for LEO Alerts is given below. For more specific DMS message creation and naming information, please refer to the appropriate section of the SWIFT SunGuide Center DMS Standard Operating Procedures Manual. Telvent Farradyne Page 159 Revised: 6/2/08

169 21.3 Roadwork Procedures Roadwork events are classified into two categories, Emergency Roadwork and Scheduled Road Work. Scheduled Roadwork is defined as: 1. A scheduled roadwork pattern that only block travel lanes from 1900 to 0600 hours and 0900 to 1500 hours. 2. A scheduled roadwork pattern that does not block any travel lanes. Emergency Roadwork is defined as: 1. An unscheduled roadwork pattern that is necessary to fix unexpected damage to the roadway or infrastructure. 2. A scheduled roadwork pattern that remains on the roadway past 0600 hrs for overnight construction or past 1500 hrs for daytime construction. Please note that FHP is required to have a trooper on the scene of all construction jobs with lanes closed. Because of this arrangement, FHP dispatch may be a good source for real-time roadwork information. The following procedures must be followed for all roadwork events because of their long durations and the possibility that the lane blockage pattern may change without notification from contractors. o The SWIFT SunGuide Center operations staff must monitor the roadwork scene with the CCTV cameras throughout the duration of the event. o If the roadwork cannot be seen on CCTV camera, the SWIFT SunGuide Center operations staff should verify the lanes affected by asking the Road Ranger in that beat to contact the SWIFT SunGuide Center every time they pass the incident, asking FHP dispatch, or monitoring the FHP radio. o Make a note in the SunGuide software comments section indicating every time the SWIFT SunGuide Center operations staff receives updated information. o If changes occur, update the DMS messages to reflect the new lane blockages and make a note in the SunGuide software comment section that describe how the information was confirmed Scheduled Roadwork The SWIFT SunGuide Center operations staff receives a weekly report of scheduled roadwork activities from the FDOT District 1 Construction PIO, FDOT District 4 Construction PIO, and the Florida s Turnpike Construction PIO. On occasion, update notifications will also be sent to inform the staff of additional activities or changes to the scheduled roadwork. The SWIFT SunGuide Center operations staff will also receive manual notifications from the Construction Engineering Inspectors (CEI) and FHP dispatch at the start and end of all lane closing roadwork patterns. The SWIFT SunGuide Center operations staff must keep themselves informed of all roadwork activities and should pre-position the CCTV cameras to the potential site of the scheduled roadwork approximately one hour before the projected start time. CCTV cameras must be positioned to view the roadwork for the duration of the job so the DMS will be deactivated in as timely a manner as possible. Telvent Farradyne Page 160 Revised: 6/2/08

170 A SunGuide event and DMS messages will be activated for all roadwork activities. These DMS messages have the highest priority (the same as accidents and other lane blocking events). Please refer to the DMS Message Priority section of this document for additional details Emergency Roadwork The SWIFT SunGuide Center operations staff will receive manual notifications from the Construction Engineering Inspectors (CEI) and FHP dispatch at the start and end of all lane closing roadwork patterns. The SWIFT SunGuide Center operations staff must keep themselves informed of these roadwork activities and should visually verify the emergency roadwork on the CCTV cameras as soon as possible. These CCTV cameras must be positioned to view the emergency roadwork for the duration of the job so the DMS will be deactivated in as timely a manner as possible. A SunGuide event and DMS messages will be activated for all roadwork activities. These DMS messages have the highest priority (the same as accidents and other lane blocking events). Please refer to the DMS Message Priority section of this document for additional details. The SWIFT SunGuide Center operations staff has the following responsibilities when an emergency roadwork situation occurs because a scheduled roadwork pattern remains on the roadway past 0600 hours from the overnight shift or past 1500 hours for the morning shift. o Follow the same incident management plan as for an incident with a type of Accident. This includes manual notifications, incident alert notifications, SunGuide event reporting, and DMS message activation. o The incident type Emergency Roadwork must be selected for the SunGuide event. o Location information, arrival times, lanes closed, incident level, etc. should be tracked as normal. o Contact FDOT Maintenance, FHP dispatch, and the CEI of the project to determine the estimated clearance time. o Send an incident notification with the SunGuide software to the Level 2 or Level 3 contact group, depending on the estimated clearance time. o Notify the appropriate manual contacts by telephone. o Dispatch a Road Ranger to gather information about the incident, if necessary Power Plant Procedure The SWIFT SunGuide Center operations staff must activate DMS messages and create a SunGuide software event to aid with evacuation routes for power plant emergencies in FDOT District 1. In District 1 there are power plants located in Polk, Highlands, Manatee, Lee, Hardee, Hendry, and DeSoto counties. The specific DMS messaging procedures may be found in the SWIFT SunGuide Center DMS SOP or must be authorized by the RTMC Operations Supervisor or RTMC Operations Manager. Lee County The FPL Fort Myers plant is located on SR 80 and the Caloosahatchee River just east of I-75. Fort Myers Power Plant FP&L State Road 80 (SR-80) Fort Myers, FL The Lee County Solid Waste Energy Recovery Facility power plant site is located in an unincorporated area of Lee County, Florida, approximately 5 miles east of the City of Fort Myers, approximately 2.5 miles east of the intersection of I-75 and SR-82. Telvent Farradyne Page 161 Revised: 6/2/08

171 Lee County Solid Waste Entergy Recovery Facility Tom Erickson Buckingham Road, Suite 400 Plant Manager Ft. Myers, FL Work #: (941) Fax #: Manatee County The FP&L Manatee Unit 3 power plant site is located on 72.8 acres within the 9,500-acre Manatee Plant site in Manatee County, Florida. The power plant is approximately 4.5 miles east of the unincorporated town of Parrish, and approximately 2.5 miles south of the Manatee County- Hillsborough County line on SR 62 east of US 301. Polk County Polk Power Station occupies 4,300 acres on State Road 37 in Polk County, Florida. It is located approximately 40 miles southeast of Tampa and about 60 miles southwest of Orlando. Power Outages Polk County Hillsborough County Other Counties DeSoto County The DeSoto County power plant is located in Arcadia, FL. It is located approximately 40 miles southeast of Sarasota, consists of two 160-megawatt combustion turbine generating units, and is primarily fueled by natural gas. Telvent Farradyne Page 162 Revised: 6/2/08

172 21.5 Accident Investigation Sites Accident Investigation Sites (AIS) are currently being constructed as part of the I-75 widening project. These AIS are improved areas that are located on the state right-of-way near the freeway mainline. They are specifically designated and signed. to provide a safe location for motorists with partially disabled or wrecked vehicles, law enforcement, fire-rescue, Road Ranger motorist assists and other public service vehicles to use for temporary relocation off the freeway mainline. A total of twelve AIS will be installed under the I-75 widening project in FDOT District 1. These AIS are will be located on I-75 northbound and southbound between the Golden Gate Parkway in Collier County and SR-80 in Lee County. Please refer to the table below for specific locations. Interchange Direction CCTV Camera Preset # Project Site ID 1 Exit 107 Pine Ridge South X X I75S Exit 107 Pine Ridge North X X I75N Exit 111 Immokalee South X X I75S Exit 111 Immokalee North X X I75N Exit 116 Bonita Beach South X X I75S Exit 116 Bonita Beach North X X I75N Exit 123 Corkscrew South X X I75S Exit 123 Corkscrew North X X I75N Exit 131 Daniels South X X I75S Exit 131 Daniels North X X I75N Exit 136 Colonial South X X I75S Exit 136 Colonial North X X I75N-136 FDOT requires documentation of the number of times each Accident Investigation Site is used by the public or emergency personnel. The SWIFT SunGuide Center will include the AIS usage frequency in the weekly, monthly, quarterly, and yearly operations reports. FDOT will then provide this information to the FHWA. For more information about report preparation and submission, please refer to the Report Preparation and Management section of the SWIFT SunGuide Center Standard Operations Guidelines document. (Future) An AIS Incident event type will be added to the event reports in the SunGuide software. The addition of this event type will allow the SWIFT SunGuide Center to easily search for these incidents so the AIS usage information can be quickly obtained for reporting purposes. Events on the Mainline that are Moved to the AIS: To obtain accurate information for AIS usage, the SWIFT SunGuide Center operations staff must perform the following actions. o The detection and confirmation process will be performed as described in the Incident Management Roadway Monitoring and Incident Detection and Incident Management Event Confirmation sections of this document. o When the event is moved to the AIS, the current event should be cloned by clicking the Clone Event button and then closed. The cloned event type status should be changed Telvent Farradyne Page 163 Revised: 6/2/08

173 to AIS Incident. Event details tracked and inputted into the cloned event. The cloned event should be closed when cleared from the AIS. o The Road Ranger drivers will record AIS usage on their daily activity logs. These activity logs will be sent to SWIFT SunGuide Center management every week to supplement the information recorded by the SWIFT SunGuide Center operations staff. Events Detected and Resolved at the AIS: To obtain accurate information for AIS usage, the SWIFT SunGuide Center operations staff must perform the following actions. o Monitor the AIS with the CCTV cameras at the top of every hour to search for activities that have not been previously detected. The appropriate CCTV cameras and presets for viewing the AIS are given in the table above. o The SWIFT SunGuide Center operations staff will monitor the FHP radio to identify AIS usage by FHP troopers that does not involve Road Ranger assistance or SWIFT SunGuide Center event reporting. This type of FHP activity will be recorded as an event in the SunGuide software, even if there is no Road Ranger assistance or impact to travel. o When an event is located at the AIS, an event should be created with the event type of AIS Incident. o The AIS Incident event will be input into the SunGuide software and the event details will be tracked and closed, per the procedures given in this document. o The Road Ranger drivers will record AIS usage on their daily activity logs. These activity logs will be sent to SWIFT SunGuide Center management every week to supplement the information recorded by the SWIFT SunGuide Center operations staff. Telvent Farradyne Page 164 Revised: 6/2/08

174 21.6 Special Events Special events are scheduled events that may generate unusually high traffic volumes and may result in unexpected delays to motorists. Some special events may only require RTMC assistance for providing directions to a specific location. The RTMC Operations Manager is responsible for developing traffic management plans for all special events. For special events that have a regional impact, the RTMC Operations Manager will coordinate the traffic management plans with the local transportation agencies and the SEFRTOC partners. If a DMS messaging plan is necessary for a special event, the RTMC Operations Manager will provide the FDOT approved plan to the RTMC Operations Supervisor for implementation. Special event traffic management plans will normally include: o Nature of the event (for example: a sporting event, concert, funeral procession, yearly festival, etc.) o Expected duration of the event o Travel lane blockage, if applicable o DMS activation plan o DMS message content o Pre-event messaging requirements o The date and time that the DMS messages should be activated o Any other protocols that have been established Some examples of special events include, but are not limited to: o Minor league baseball events o Super Bowl planning in Miami or Tampa o Music concerts o Golf tournament parking o FHP or local police funeral processions o Yearly festivals (Sunfest, etc.) o Yearly events (Toys for Tots Motorcycle Run that closes I-95 in Broward County, etc.) o Public service events (Work Zone Safety Awareness Week, etc.) Example (Palm Beach ITMS) The Allianz Championship Senior PGA Golf Tournament Telvent Farradyne Page 165 Revised: 6/2/08

175 22 Procedures Prioritizing Multiple Events The SWIFT SunGuide Center operations staff must have the skill set to multi-task in their dayto-day operational tasks. For example, they are expected to enter data into the SunGuide software while dispatching a Road Ranger, and collecting information from the Road Rangers and CCTV cameras. There will be times when multiple events occur simultaneously and the SWIFT SunGuide Center operations staff will have to prioritize events and operational activities to ensure the best service is provided to the public and incident responders. The SWIFT SunGuide Center operations staff (operators and supervisors) for each shift will work together as a unit to expedite the management of events. The RTMC Shift Supervisor will act as the leader for the shift and ensure the workload is delegated in the most efficient manner. This requires the SWIFT SunGuide Center Operators to assist each other in managing events. For example: One SWIFT SunGuide Center Operator is making manual telephone notifications for an incident and the other operator on duty is creating an event in the SunGuide software when another incident occurs. The first operator may need to communicate with the Road Ranger while the second operator submits a DMS Response Plan for the first event. At the same time, the RTMC Shift Supervisor may simultaneously be requested to review a DMS Response Plan on one event and notify FDOT Maintenance for a totally separate event. The SWIFT SunGuide Center operations staff should use the following guidelines to prioritize activities and events. Activities There are a number of activities the Control Room Staff must perform when managing an event. When the SWIFT SunGuide Center operations staff has to manage multiple events simultaneously, the following guidelines shall be used to prioritize their activities. 1. Notify FHP dispatch for emergency services with the most serious injuries first. 2. Locate and confirm incidents on CCTV camera 3. Dispatch Road Rangers to the scene to confirm if the event can t be confirmed by CCTV 4. Activate DMS messages (quick and accurate activation of DMS messages is crucial) 5. Dispatch Road Rangers after DMS activation if the event can be confirmed on CCTV 6. Continue to input event information into SunGuide incident reports in real time 7. Dispatch additional Road Rangers 8. Notify additional resources (manual notifications) Events There will be times when the SWIFT SunGuide Center operations staff will have to simultaneously perform the same activity for two or more different events. For example, a SWIFT SunGuide Center Operator may need to develop a DMS Response Plan for two separate events occurring at the same time. The following guidelines shall be used to prioritize activities that need to be performed simultaneously at the same priority level identified above. 1. Event severity the more severe the event, the higher the priority (for example, Level 3 incidents should be handled before Level 1 incidents) 2. Vehicle speeds At high vehicle speeds, the incident scene is less safe than at lower vehicle speeds because vehicles traveling at high speeds can cause more damage to the responders. Motorists need more advanced warning at higher speeds. 3. Traffic volumes The higher the traffic volumes, the higher the priority for notifying additional resources. High traffic volumes will result in a longer delay to motorists. Therefore, it is important to get all resources dispatched as quickly as possible for events in high traffic volume conditions. Telvent Farradyne Page 166 Revised: 6/2/08

176 23 Procedures Other Operational Situations 23.1 Traffic Signal Malfunctions The SWIFT SunGuide Center operations staff may receive notification of traffic signal malfunctions during their shifts. Some traffic signal malfunctions include flashing, out completely, bulbs out, timing problems, etc. Traffic signal malfunctions should be relayed to the proper agency when they occur. All contact information is listed in the Emergency Contacts section of this document and on the RTMC Agency Contact List. Traffic signal malfunctions in the coverage area of another TMC should be reported to the appropriate TMC. The other traffic management centers are responsible for contacting the appropriate traffic engineering agency in their coverage area Live Animals Causing a Safety Hazard Whenever a live animal causes a disturbance or safety hazard on state roadways, the Animal Care and Control Division and FHP dispatch should be contacted. Please refer to the Emergency Contact Information section of this document for appropriate contact information Procedure for Graffiti Sightings The local police departments and FHP are cracking down on graffiti artists and are interested in stopping these types of activities. Taggers have frequently targeted sound barriers and hanging highway signs. The SWIFT SunGuide Center and the Road Ranger program have agreed to assist the police with this endeavor. The new procedures are as follows. o If the SWIFT SunGuide Center operations staff sees graffiti artists on camera, they should report this activity to FHP and the appropriate local police department. o If a Road Ranger sees graffiti artists while on patrol, the Road Ranger must call the SWIFT SunGuide Center to report the activity. The SWIFT SunGuide Center operations staff must then contact FHP and the appropriate local police department to report this activity. The Road Ranger should not stop near the crime scene, but should turn around at the next exit and report what is seen while driving on the other side of the highway. The Road Ranger must not be confrontational. The police have requested that the SWIFT SunGuide Center operations staff stay on the telephone with the local police dispatchers while the graffiti activity is taking place because the SWIFT SunGuide Center operations staff can continuously report what is seen on camera and it will increase the chances of arresting the people involved. The SWIFT SunGuide Center operations staff is expected to place the CCTV camera image in the appropriate spot on the video wall so FHP dispatch will be able to monitor the crime scene. The SWIFT SunGuide Center operations staff should provide the cell phone number of the involved Road Ranger to the police, upon request. Telvent Farradyne Page 167 Revised: 6/2/08

177 24 Regional Event Management Regional event management provides a seamless transportation system to southeast and southwest Florida motorists. This seamless transportation system is achieved through centerto-center TMC communications that enable a coordination of responses to planned and unplanned events, sharing of information, and sharing of resources such as DMS messing and Road Rangers. Center-to-center communication protocols are established through the Southeast Florida Regional TMC Operations Committee (SEFRTOC), which is made up of representatives from: o FDOT District 6 SunGuide TMC o FDOT District 4 SMART SunGuide TMC o Florida s Turnpike Enterprise TMC o Miami-Dade Expressway (MDX) Authority TMC (Future) o Palm Beach County Interim Traffic Management System TMC (ITMS) o FDOT District 1 SWIFT SunGuide Center During an event that has been deemed to have regional importance, there will be a requesting agency that is directly responsible for the event, and assisting agency or agencies that are called upon to provide support for the event. The procedures below are based on the SEFRTOC Standard Operating Guidelines. The RTMC Operations Manager is responsible for coordinating changes to these procedures with SEFRTOC, as well as updating these procedures based on changes to the SEFRTOC Standard Operating Guidelines. The following sections describe the procedures that address all event management functions: o Event Confirmation o Event Evaluation o DMS Response Plan o Notifications o Event Monitoring o Event Closure 24.1 FDOT District 1 SWIFT SunGuide Center as the Assisting Agency The FDOT District 1 SWIFT SunGuide Center acts as the Assisting Agency when an event occurs in the coverage area of another regional traffic management center. Generally, the requesting regional TMC will notify the FDOT District 1 SWIFT SunGuide Center of the event. However, the SWIFT SunGuide Center operations staff is expected to be proactive and will periodically monitor the regional TMC websites for events that may have regional impact, such as lane blocking events on I-75 south near the Broward/Collier County line and on I-75 north near the Manatee/Hillsborough County line. o Event Confirmation Since the event occurs in the jurisdiction of the requesting agency, they are responsible for confirming the event and gathering all the event details. Once the FDOT District 1 RTMC is notified, the RTMC operations staff must create a new event. This event is considered to be Active. If the event can be observed on a RTMC CCTV camera, the CCTV number must be logged into the SunGuide software incident report. The requesting agency should be notified of this additional resource and given access to view the CCTV image through the Center to Center (C2C) module. o Requesting Agency Requests DMS Support When the requesting agency asks for DMS support, the SWIFT SunGuide Center operations staff must notify the RTMC Shift Telvent Farradyne Page 168 Revised: 6/2/08

178 Supervisor of the request. The RTMC Shift Supervisor will evaluate the request and check for conflicts with any current DMS message activations in the FDOT District 1 SWIFT SunGuide Center coverage area. If there are no conflicts, the RTMC Shift Supervisor will monitor the implementation of the requested DMS response plan. If there is a conflict, the RTMC Shift Supervisor will call the requesting agency and notify them of the conflict. Once the District 1 SWIFT SunGuide Center incident no longer requires DMS messaging, the RTMC Shift Supervisor will notify the requesting agency to determine if DMS messaging is still required for their incident. Please refer to the Incident Management DMS Response Plan section of this document and the SWIFT SunGuide Center DMS SOP document for more information. Please note that all telephone communications must be logged in the Incoming/Outgoing Contact Microsoft Access database and the telephone log in the SunGuide software. o Requesting Agency Requests Road Ranger Support When the requesting agency asks for Road Ranger support, the SWIFT SunGuide Center operations staff must notify the RTMC Shift Supervisor of the request. The RTMC Shift Supervisor will evaluate the request and check for conflicts with the use of existing Road Ranger resources. If there are no conflicts, the RTMC Shift Supervisor will notify the Road Ranger Supervisor while the SWIFT SunGuide Center operations staff dispatches the appropriate Road Ranger or Road Rangers. The RTMC Shift Supervisor will monitor the implementation of the requested Road Rangers to ensure that the responding Road Rangers switch to the requesting agency s radio channel. If there is a conflict, the RTMC Shift Supervisor will call the requesting agency and notify them of the conflict. Once the Road Rangers are released from the incident, the RTMC Shift Supervisor will notify the requesting agency to inquire if assistance is still required. Please refer to the Road Ranger Service Patrol Procedures section of this document for more information. Please note that all telephone communications must be logged in the Incoming/Outgoing Contact Microsoft Access database and the telephone log in the SunGuide software. o Event Monitoring/Event Closure The SWIFT SunGuide Center depends on the requesting agency s operators to provide updates for their events. However, the RTMC Shift Supervisor and the SWIFT SunGuide Center operations staff should not depend solely on the requesting agency to provide updates. The SWIFT SunGuide Center staff must prompt the requesting agency for updates every 30 minutes if the requesting agency has not provided an update by that time. Once the lanes have been cleared, the requested DMS message activations must be cleared and the requested Road Rangers should resume their normal operations. Please note that all telephone communications must be logged in the Incoming/Outgoing Contact Microsoft Access database and the telephone log in the SunGuide software DMS Message Activation Procedure District 4 Broward TMC Incidents The RTMC operations staff is expected to activate DMS messages for incidents in Broward County at the request of the Broward TMC or if Alligator Alley is shut down in one or both directions. On I-95, Broward county extends from the Palm Beach County line between exits to exit 16 (Ives Dairy Road). On I-75, the Broward TMC coverage area extends from the Collier County line to the Miramar Parkway, which is the northern border of the FDOT District 6 RTMC. On I-595, the Broward TMC coverage area extends from the I-75 junction to US-1. The Broward TMC will contact the SWIFT SunGuide Center to request DMS activation whenever their Smart SunGuide response plan chooses to activate the DMS devices located Telvent Farradyne Page 169 Revised: 6/2/08

179 the closest to the FDOT District 1 coverage area. The SWIFT SunGuide Center operations staff must confirm the incident details with the Broward TMC when the request occurs to ensure proper DMS message content and incident report population. All DMS within at least 25 miles of the incident should be utilized. For incidents more than 25 miles away from the Collier County line, all DMS are expected to be activated at least back to the 1 st DMS location in D1. As always, all I-75 southbound DMS should be activated for Level 3 incidents unless otherwise directed by RTMC management. For further information about the content of the DMS messages, please refer to the SWIFT SunGuide Center DMS SOP document DMS Message Activation Procedure Florida s Turnpike Incidents The SWIFT SunGuide Center operations staff will activate DMS messages for all Level 3 incidents and other incidents with significant traffic impact upon request from the Florida s Turnpike TMC. The SWIFT SunGuide Center operations staff must confirm the incident details with the Florida s Turnpike TMC when the request occurs to ensure proper DMS message content and incident report population. All DMS within at least 25 miles of the incident should be utilized. For incidents more than 25 miles away from the Collier County line, all DMS are expect to be activated at least back to the 1 st DMS location in D1. For further information about the content of the DMS messages, please refer to the SWIFT SunGuide Center DMS SOP document DMS Message Activation Procedure District 6 TMC Incidents The SWIFT SunGuide Center operations staff will activate DMS messages for all Level 3 incidents and other incidents with significant traffic impact upon request from the District 6 TMC. The SWIFT SunGuide Center operations staff must confirm the incident details with the District 6 TMC when the request occurs to ensure proper DMS message content and incident report population. All DMS within at least 25 miles of the incident should be utilized. For incidents more than 25 miles away from the Collier County line, all DMS are expected to be activated at least back to the 1 st DMS location in D1. The SWIFT SunGuide Center receives the District 6 TMC incident notification pages on the operations cellular telephones phones as well as the wpb-tmo@pbworld.com SWIFT SunGuide Center office . If the District 6 TMC does not contact the SWIFT SunGuide Center operations staff for relevant incidents, then the SWIFT SunGuide Center operations staff should contact them to inquire if assistance is necessary. For further information about the content of the DMS messages, please refer to the SWIFT SunGuide Center DMS SOP document DMS Message Activation Procedure District 7 TMC Incidents The RTMC operations staff will activate DMS messages for all Level 3 incidents and other incidents with significant traffic impact upon request from the District 7 TMC. The RTMC operations staff must confirm the incident details with the District 7 TMC when the request occurs to ensure proper DMS message content and incident report population. Telvent Farradyne Page 170 Revised: 6/2/08

180 All DMS within at least 25 miles of the incident should be utilized. For incidents more than 25 miles away from the border of the FDOT District 7 TMC, all DMS are expected to be activated at least back to the 1 st DMS location in D1. As always, all I-75 northbound DMS should be activated for Level 3 incidents unless otherwise directed by SWIFT SunGuide Center management. For further information about the content of the DMS messages, please refer to the SWIFT SunGuide Center DMS SOP document DMS Message Activation Procedure District 5 TMC Incidents The SWIFT SunGuide Center operations staff will activate DMS messages for all Level 3 incidents and other incidents with significant traffic impact upon request from the District 5 TMC. The SWIFT SunGuide Center operations staff must confirm the incident details with the FDOT District 5 TMC when the request occurs to ensure proper DMS message content and incident report population. Incidents in FDOT District 5 will normally be very far away from the DMS units in FDOT District 1. All DMS are expected to be activated at least back to the 1 st DMS location in D1. For further information about the content of the DMS messages, please refer to the SWIFT SunGuide Center DMS SOP document FDOT District 1 SWIFT SunGuide Center as the Requesting Agency The FDOT District 1 SWIFT SunGuide Center is responsible for all aspects of event management in the FDOT District 1 coverage area. The SWIFT SunGuide Center becomes the requesting agency when FDOT District 1 events have a potential regional impact. An event has potential regional impact when traffic queues create abnormal delays for motorists traveling towards roadways managed by the SWIFT SunGuide Center. The SWIFT SunGuide Center operations staff will notify the RTMC Shift Supervisor of these conditions. All notifications to other District Transportation Management Centers will be made as soon as possible and not to exceed 10 minutes. When the RTMC operations staff notifies another District TMC, the RTMC Shift Supervisor shall inform them of the CCTV number used to monitor the event, if available, and open the camera for viewing. The RTMC Shift Supervisor will be responsible for updating the other District TMC of lane blockage pattern changes, residual delays, and whenever all travel lanes are opened. All telephone communications must be logged in the Incoming/Outgoing Contact Microsoft Access database and in the SunGuide software. Contact with other District Transportation Management Centers will also be initiated upon notification of an Amber Alert activation that is received from the District 5 TMC. Please refer to the Amber Alert Procedure section of this document for further information. The RTMC Shift Supervisor must use the following guidelines for notifying the regional traffic management centers: o Notify All Regional Transportation Management Centers When the event is expected to have all lanes blocked for extended period of time, as per the 50 Miles an Hour Rule section of this document or when the event may impact traffic flow from the coverage area of other regional traffic management centers. The RTMC Shift Supervisor will provide all event information to the regional TMC and will request DMS message support. The RTMC Shift Supervisor will follow the guidelines in the SWIFT SunGuide Center DMS SOP document when requesting a specific DMS message. Telvent Farradyne Page 171 Revised: 6/2/08

181 o Notify the District 4 Broward TMC Notify for events that have lanes blocked on I-75 north on Alligator Alley or any full road closure on I-75 north (at the discretion of the RTMC Shift Supervisor). The RTMC Shift Supervisor will provide all event information and request DMS message support. The RTMC Shift Supervisor will follow the guidelines in the SWIFT SunGuide Center DMS SOP document when requesting a specific DMS message. Also, for events near the Broward/Collier County line, the RTMC Shift Supervisor may request assistance from the Broward County Road Rangers for short-term Maintenance of Traffic (MOT). When requesting Road Ranger assistance, the RTMC Shift Supervisor will inform the Broward TMC of the radio channel dedicated for that event. The RTMC Shift Supervisor will also inform the Road Ranger Supervisor of the request. o Notify the Florida s Turnpike TMC Notify for events that have lanes blocked on I-75 north on Alligator Alley, any full road closure on I-75 north (at the discretion of the RTMC Shift Supervisor), any full road closure on SR-80 west, any full road closure on SR-70 west, any full road closure on SR-29, or any full road closure on US-41 west. The RTMC Shift Supervisor will provide all event information and request DMS message support. The RTMC Shift Supervisor will follow the guidelines in the RTMC DMS SOP document when requesting a specific DMS message. o Notify the Palm Beach ITMS TMC Notify for any full road closure on SR-80 west or any full road closure on SR-70 west. The RTMC Shift Supervisor will provide all event information and request DMS message support. The RTMC Shift Supervisor will follow the guidelines in the SWIFT SunGuide Center DMS SOP document when requesting a specific DMS message. o Notify the District 6 TMC Notify for any full road closure on I-75 north on Alligator Alley, any full road closure on I-75 north (at the discretion of the RTMC Shift Supervisor), any full road closure on US-41 west, any full road closure on US-27 north, or any full road closure on SR-29 north. The RTMC Shift Supervisor will provide all event information and request DMS message support. The RTMC Shift Supervisor will follow the guidelines in the SWIFT SunGuide Center DMS SOP document when requesting a specific DMS message. o Notify the District 7 TMC Notify for events that have lanes blocked on I-75 south in Manatee or Sarasota County, any full road closure on I-75 south, any full or partial road closure on I-275 south of the Sunshine Skyway bridge, any full road closure on US-41 south, any full road closure on SR-70 east, any road closure on SR-80 east, or any full road closure of arterial roadways in Manatee or Sarasota Counties. The RTMC Shift Supervisor will provide all event information and request DMS message support. The RTMC Shift Supervisor will follow the guidelines in the RTMC DMS SOP document when requesting a specific DMS message. o Notify the District 5 TMC Notify for any full road closure on I-75 south, any full road closure on US-17 south, or any full road closure on US-27 south. The RTMC Shift Supervisor will provide all event information and request DMS message support. The RTMC Shift Supervisor will follow the guidelines in the SWIFT SunGuide Center DMS SOP document when requesting a specific DMS message. o District 1 RTMC Requests for Road Ranger Support The RTMC Shift Supervisor will request assistance from Road Rangers in other TMC jurisdictions through the appropriate regional TMC (most likely the Broward TMC or the FDOT District 7 TMC). Part of this coordination will be for neighboring patrols to monitor traffic conditions near bordering areas and report real-time incident and congestion information to the appropriate TMC. Telvent Farradyne Page 172 Revised: 6/2/08

182 Also, during regional events, it is assumed that a good portion of the FDOT District 1 RTMC Road Rangers will be involved with the event. This could potentially require patrol routes and hours to be changed until the event has cleared. The RTMC Shift Supervisor will work with the Road Ranger Supervisor to establish new patrol routes and hours, when necessary. DBI, the asset management firm for I-75 from Broward County line to Hillsborough County line may also be contacted to supply emergency MOT, if necessary DMS Usage for Regional Events The RTMC Shift Supervisor will coordinate DMS messaging with other facilities and agencies. This includes message content, device availability, device usage, and other pertinent DMS information. Local event DMS messaging will have priority over regional requests. The RTMC Shift Supervisor will coordinate with other centers to reconcile any message conflicts or prioritization issues. If DMS messaging or device usage requests cannot be resolved, the RTMC Shift Supervisor will escalate the issue to the RTMC Operations Manager or designee. For information about the specific DMS message activation procedures, please refer to the Incident Management DMS Response Plan section of this document Other Resources There are several other resources in addition to the ones previously discussed that are available for use during regional events. o The Florida s Turnpike Highway Advisory Radio System This system is controlled by the Florida s Turnpike Traffic Management Center 24 hours a day and 7 days a week. The Florida s Turnpike operations staff is able to record and transmit messages with realtime traffic information that can be heard on 1640 AM. There are 20 HAR signs with flashing beacons that notify motorists to tune to 1640 AM for traveler information. o Portable DMS Portable DMS are able to be deployed quickly to strategic locations to support local and regional events. Normal DMS messaging structures apply to portable DMS as well. These requests must be directed to the RTMC Operations Manager or designee. o Severe Incident Response Vehicle (SIRV) The FDOT District 4 has a SIRV vehicle based out of the Broward TMC and is available 24 hours a day and 7 days a week to assist with major incidents. The vehicle serves as an incident command post with the SIRV staff serving as the liaison between incident response team members, traffic management center staff, and FDOT personnel. The vehicle also carries traffic management equipment, MOT equipment a self contained radio system, internet capabilities, hazardous material equipment, lighting, and an on-board digital video camera system. Insert the Regional Event Management Flowchart here Telvent Farradyne Page 173 Revised: 6/2/08

183 25 Star FHP (*FHP) Motorist Assistance Calls Motorist assistance Star FHP (*FHP) calls for I-75 in FDOT District 1 are received by the local FHP troop and then transferred to the RTMC operations staff. These motorist assist calls are primarily for Road Ranger assistance, but may sometimes be for other concerns or errant touch tone entries by the public. All *FHP calls will be entered as events in the EM/PM portion of the SunGuide software by using the Motorist Assist tab on the Events page. When taking *FHP calls, the motorist contact information will be required in order to create the event. Normal RTMC and EM/PM event entry procedures will be followed to complete the remainder of these types of events. All *FHP calls are transferred by FHP dispatch to the (xxx) xxx-xxxx RTMC telephone line. In the future, *FHP calls for motorist assistance may come directly to the RTMC operations staff instead of being transferred from FHP dispatch Information Required & Questions to Ask the Caller What? 1. Determine the nature of the call. If not readily volunteered, prove for information. Ask, What is your specific problem or request? Remember to control the complainant; do not let the complainant control you. 2. Do not ask the caller, Is this an emergency? a. The public should not establish priorities. The receiving SWIFT SunGuide Center operator should be the one to determine whether it is an emergency or not. b. The complainant may not be objective. c. The public may not recognize a potential emergency. If the complainant advises, No, the SWIFT SunGuide Center operations staff may delay action which could have negative results. Example: A woman calls and is asked, Is this an emergency? She states No and is placed on hold. Her husband was short of breath and she did not recognize this as an emergency. He was actually having a heart attack. d. The best action is for the SWIFT SunGuide Center operations staff to determine the nature of the complaint and decide if it is an emergency or not Where? 1. Location of the incident 2. Be specific Mileposts, direction, cross street, parking lot section, alley, business, gas station, etc. When? 1. What was the time of occurrence? 2. Is it in progress? 3. Did it just occur? 4. Was it a week ago? Call Back Number 1. What telephone number is the person calling from? 2. If the phone number is unavailable, what number can we use to currently contact them? Who? 1. Obtain the name of the caller 2. If the caller insists on remaining anonymous Telvent Farradyne Page 174 Revised: 6/2/08

184 a. Do not persist in obtaining the name. b. Obtain as much of the other pertinent information as possible Remember to obtain the Who? last. If you ask this first, there is a good chance the caller may hang up, etc. because they do not want to get involved. Location 1. Numerical addresses are not necessary to dispatch Road Rangers or FHP to an incident. Intersections, mile markers, and exit numbers can be used. 2. The SWIFT SunGuide Center operations staff should use all the information available to determine the correct location of the incident. Some methods, which may be used are: a. Asking the person to repeat the location when the SWIFT SunGuide Center operator is unsure what was heard. b. The SWIFT SunGuide Center operator should remember that the location the person is calling from is not necessarily where the Road Rangers or police are needed. Document the Call 1. Document in the Incoming/Outgoing Contact Microsoft Access database 2. Document in the event opened in the SunGuide software 3. Never leave anything to memory. Write or log everything! Even under the best of circumstances, important details of an event may be overlooked or forgotten Calls from I-75 - Not for Motorist Assistance If a caller does not require Road Ranger service or any other service that the SWIFT SunGuide Center can provide, the caller should be transferred back to FHP dispatch in the SWIFT SunGuide Center control room. To transfer *FHP telephone calls to FHP dispatch: o With the caller on the line, tab over to the transfer option on the telephone by using the arrows located on the base of the telephone. o Transfer? will appear in the telephone display window. o Press the check located between the 2 arrows on the base of the telephone. o Once you hear a dial tone, enter the extension for FHP dispatch. o When the line starts to ring, Transfer? will appear again in the display screen. o When FHP dispatch personnel answer the telephone, explain to them that a *FHP caller that does not require motorist assistance will be on the line when your conversation is complete. o Press the check once again located between the 2 arrows and the call should transfer to FHP dispatch Calls from Arterial Roadways in FDOT District 1 - Not for Motorist Assistance Non-emergency calls received for roadways other than I-75 in FDOT District 1, should be given the telephone number for the local police agency. If the correct local police agency cannot be determined by the SWIFT SunGuide Center operations staff, the operators should transfer the telephone call to FHP dispatch by using the procedure above Calls in Other TMC Jurisdictions Any *FHP call received for assistance in the coverage area of another regional TMC, should be directed to the appropriate TMC. An Interagency Event should be created in the Events page Telvent Farradyne Page 175 Revised: 6/2/08

185 in the EM/PM portion of the SunGuide software. Please remember that these types of events require the contact information and location of the caller to complete the event! 25.5 Star FHP Call Taking Summary o Always get a name and callback number on all calls. o Explain the options to the caller This is a free service and is a first come first served program. The exception is that medical emergencies, accidents, and travel lane blockages take priority over other events. Motorists can have a tow truck sent to them for a fee. Should they agree, the call should be transferred to FHP dispatch and they will provide the motorist a rotation tow truck. The normal response time for rotation tow truck to arrive is 30 minutes. o If the caller s location is unknown and it cannot be determined, transfer the call back to FHP dispatch so they may assist. o After receiving the caller s contact information, make sure that you advise them to Stay in their vehicle with their seatbelts on for their safety, if the vehicle is in a safe location. Put their flashers on If the vehicle is blocking the roadway, check to see if it can be moved off the roadway. Have the caller move the vehicle, if possible. If this is not possible, the caller should be advised to stay in a safe location off to the side of the road (preferably on the other side of a guardrail). o If the Road Ranger arrives on scene and the vehicle needs a tow truck, notify FHP dispatch and provide them all the relevant information. o On serious calls, try to get as much information as possible in case the call gets dropped or lost. Try to stay on the line with the caller until FHP receives the transferred call. o If there is anything that you don t understand, contact FHP dispatch for assistance. o In the rare instance that there is no answer from FHP dispatch, call the FHP Duty Officer Supervisor. If there is again no answer, call the FHP Shift Commander. o If AAA or other roadside services call for their customer, remind them that their customer has paid for the service they are offering. They should have their truck continue out to the customer. Telvent Farradyne Page 176 Revised: 6/2/08

186 26 Procedures - Equipment Failures The following sections contain the specific actions required by operators to fix problems with SWIFT SunGuide Center software and hardware Telvent SOS Helpdesk Telvent Outsourcing is the company that is responsible for providing IT services to all Abengoa business groups worldwide, including Telvent Farradyne. This company should be contacted whenever the SWIFT SunGuide Center experiences any IT problems with Telvent Farradyne owned software or hardware. Telvent Outsourcing provides service on issues such as desktop support, network connectivity, Lotus Notes, corporate applications, etc. Telvent Outsourcing uses a tool called the "SOS Helpdesk" to log all IT support requests and track their progress to completion. Users can register their IT support requests in the SOS Helpdesk, which will then be forwarded to the appropriate IT service center. When an issue is resolved, the user will receive an confirmation. You can even enter a complaint if you are not satisfied with the resolution to a SOS. If you require IT support, a request should be submitted in the SOS Helpdesk at Please refer to the SOS User Manual for additional details. As much detail about the problem should be included in the SOS description. Having specific details about the problem will help to resolve issues as quickly as possible. If the problem being experienced is urgent or there is a specific deadline for the work, it should be included in the text of the description. If you are unable to submit a request in the SOS Helpdesk, there is a 24x7 helpline that can be contacted. The number is (403) This helpline will submit a SOS request on your behalf. Usernames and passwords for the SOS Helpdesk are sent to all new employees as an from "Gestion de Usuarios" (Management of Users) with a subject of "Nuevo Acceso a Servicios al Empleado / New Access to Services to Employee". If for some reason this is not sent, you may "Helpdesk NA" to request one. Telvent Outsourcing also operates a 7x24 emergency helpline for support of critical outages. The purpose of this service is to solve critical problems with the Telvent network and the main Telvent business servers. To access the helpline from North America, dial 011 for international calling and then dial Follow-the-Sun Service Model Telvent Outsourcing operates four IT service centers to support all Abengoa companies worldwide. o Seville, Europe o Montevideo, South America o Calgary, North America o Beijing, Asia-Pacific The service model is currently organized by geography, but plans are already in place to change the model to operate independently of geography in order to provide a true 24x7 service. These changes have already begun and the new model is expected to be fully operational by January 1, Telvent Farradyne Page 177 Revised: 6/2/08

187 26.2 Building Maintenance FDOT is responsible for the maintenance of the building. This includes cleaning staff and repairs. The SWIFT SunGuide Center staff will call the RTMC Operations Manager or the RTMC Operations Supervisor whenever there is damage to the building (water leaks, damage to the walls, etc.). Management will then contact the FDOT RTMC Manager to report the problem. A brief description of the problem should also be included on the Shift Change Report until the problem is fixed. Information about the Shift Change Report may be found in the Shift Change / Overlap Procedure section of the Standard Operations Guidelines document. It is likely that a building manager will be assigned by FDOT to handle these types of building issues in the near future. If or when this occurs, the appropriate contact information will be added to this document Power Failure The system has an electrical generator for long-term power failures and an Uninterruptible Power Supply (UPS) system for short-term power failures. When a power failure occurs, the electrical generator should activate and provide power to all RTMC equipment for several days without any downtime. Operators must contact the RTMC Operations Manager and the RTMC Operations Supervisor when the electrical generator begins to provide power to the SWIFT SunGuide Center during a power failure. An incident alert page should also be sent to the Administration / Telvent (All times) paging group in SunGuide. See the Administration / Telvent Internal Paging Messages section of this document for further details about this paging group. Power restoration may be obvious once the RTMC recovers from a brown out, but it may be more subtle when backup power was immediately and continuously available. The RTMC operations staff must make every attempt possible to determine when power is restored so notifications can be made to the appropriate personnel. The RTMC operations staff may receive notifications from FHP dispatch, MCCO, the building manager, or the generator technicians, but should also aggressively confirm that power has been restored with these agencies when necessary Electrical Generator Failure Whenever an event with adequate pre-warning threatens the power source to the building (hurricanes, etc.), FDOT will request the in-house presence of generator service personnel throughout the event. This technician will ensure that power is maintained in the building so the systems and operations may continue without interruption. The SWIFT SunGuide Center building is equipped with multiple emergency power backup sources, including Uninterruptible Power Supplies (UPS) and a building generator. The UPS systems provide temporary power for one hour when the regular power supply from the utility company is not available. The generator uses on-site diesel fuel and has the capacity to provide continuous power to the SWIFT SunGuide Center building for at least 72 hours. The generator provides power for the mission-critical facilities, including the control room, equipment rooms, and their support utilities (i.e. air conditioning) during emergency operations. The electrical generator and fuel storage for the building is located in the north-east area of the facility near the garbage dumpsters and the east parking lot. Telvent Farradyne Page 178 Revised: 6/2/08

188 If the generator fails to activate, the RTMC Operations Manager or the RTMC Operations Supervisor must be notified so steps can be taken to fix the problem. While waiting for the generator to be fixed, the UPS should maintain short-term power in the RTMC. All non-essential equipment shall be powered down immediately, if plugged into the critical circuit. Examples of non-essential equipment include, but are not limited to: all computers except the video wall computer, all lights in the building except for the operations control room, and the copy machine. RTMC tenants should take extra care to make sure that non-essential equipment is not plugged into the critical circuit (red electrical outlets) and should double check when a power failure has occurred. Use the individual on/off switches located on the equipment to reduce the risk of damage when power is restored. The UPS should be able to operate essential equipment for approximately minutes. The generator has a service log that lists all previously performed maintenance activities. This service log provides useful information and is required to be present when inspected by the state. Contact the FDOT RTMC Manager, the RTMC Operations Manager or the RTMC Operations Supervisor immediately after deactivating the non-essential equipment. Management will either contact the proper FDOT contact who will call Florida Power and Light (FPL) or will call FPL directly to open a trouble ticket. This ensures that FPL knows that we do not have power and will address the issue. If power is not restored in 30 minutes, an incident alert page must be sent to all Level 1, 2, & 3 incident recipients to notify that the SWIFT SunGuide Center is in operation but in a limited capacity. Please refer to the Event Notification Format - Shutdown for SWIFT SunGuide Center Power Failure section in this document for the pre-approved message. After this page is sent, it is then necessary to shut down the SunGuide server. Refer to the SunGuide Software Manual for the correct shut down procedure. If a power failure renders all equipment at the SWIFT SunGuide Center inoperable, it is essential to continue the operation of the center. Notifications to local agencies and the Road Ranger program should continue, if possible. Operators, at the direction of the RTMC Operations Manager, may be required to contact authorized personnel to activate and deactivate the DMS units in the field. Authorized field personnel include: the RTMC IT Manager and the RTMC IT Technician, respectively. If a power failure that renders all equipment at the SWIFT SunGuide Center inoperable and the situation is projected to last more than one day, it may be necessary to relocate the RTMC operations staff to an alternate location. Procedures involving RTMC and staff relocation are given throughout the SWIFT SunGuide Disaster Recovery Plan, Hurricane and Severe Weather Plan, Hurricane and Severe Weather Schedule, and SWIFT SunGuide Disaster Recovery Plan Specific Disaster Procedures sections of this document. If the power failure affects the field devices, the operators, at the direction of the FDOT RTMC Manager and the RTMC Operations Manager, should contact the ITS Maintenance Contractor in order to mobilize the backup generators. The ITS Maintenance Contractor will deploy generators for a maximum of 50% of DMS, 25% of CCTV cameras, and 25% of vehicle detectors. These percentages will be used to develop a matrix of devices to be powered, to be developed in conjunction with the operations staff and maintenance staff, if there is a power failure which affects some or all of the system. When power is restored, the equipment shall be re-started using the normal, individual start-up procedures. Telvent Farradyne Page 179 Revised: 6/2/08

189 26.5 Road Ranger Radios The backup method of communication between the SWIFT SunGuide Center and the Road Rangers is through Nextel two-way Direct Connect radio communication. In the event of a SWIFT SunGuide Center mechanical direct connect failure, the Road Ranger drivers may use their cellular telephones to contact the SWIFT SunGuide Center main number directly Local Network Failure If the local network fails, the RTMC IT Manager must be contacted to resolve the problem. The RTMC IT Manager and the RTMC IT Technician will take the necessary steps to rebuild the server and restore data from tape backups. If the RTMC IT Manager and the RTMC IT Technician cannot be contacted in 10 minutes, call the RTMC Operations Manager and the oncall supervisor for direction Video Wall Failures If one or more of the SWIFT SunGuide Center cubes on the video wall turn black, the SWIFT SunGuide Center operations staff should press the Standby button on the back of the problem video wall units. The Standby button is specifically located on the lower left-hand corner of the video monitor in the button panel. If the video wall is not restored or turns black shortly after pressing the Standby button, contact the RTMC IT Technician and the RTMC IT Manager, respectively, to address the problem. This type of situation is most likely a lamp problem. Only contact the RTMC Operations Manager or the on-call supervisor if contact can not be made with the RTMC IT Technician or the RTMC IT Manager Failure to Access the Video Wall from the Operator Stations The following procedure should be followed whenever an operator cannot operate the video wall from their individual workstation and profile. The Creston Media video wall controller can be accessed by all RTMC operations staff and is located in the first row of workstations in front of the video wall between the center two workstations. To access the video wall from the center workstation: 1. Log in under your account. 2. Click the Start button 3. Click Programs 4. Click Barco Octopus 5. Click Octopus Client. This will start the program, which will be hidden at the very top of the screen. 6. Click Options 7. Click Configure connections 8. Click Add Server and type into the field, then click OK. 9. Click Startup, Reconnect, and Fallback 10. Click Connect, then OK 11. After this, you simply have to start the Octopus Client to access the video wall. Please notify the on-call supervisor or the RTMC Operations Manager if this procedure fails to solve the problem Video Wall Configuration during Video Wall or Software Failures Telvent Farradyne Page 180 Revised: 6/2/08

190 If the SunGuide software crashes or any program on the video wall ceases to function, the video wall must be modified as soon as the situation and the operational policy allows. Several functions on the video wall are not operable when SunGuide software crashes. Some of these functions include the SunGuide cameras, the SunGuide operations map, the SunGuide software window, and the SunGuide speed detection map. When the SunGuide software crashes, the video wall should display: o The FHP Traffic Crash Report website o A local Doppler radar weather map o A local or national TV news station o The SWIFT SunGuide Center website (set to the active Incident Report screen) o As many of the vendor supplied software camera images that are needed to fill the remaining empty space on the video wall In situations where individual CCTV cameras fail and show a blank or black image on the video wall, working camera images should replace the blank spaces at all times. This should be done for functionality and esthetic purposes. All other websites and images that fail to function should be removed from the video wall and replaced with cameras or more reliable images DMS Damaged from an Accident, Vandalism, or High Winds The RTMC operations staff must contact the RTMC IT Technician, RTMC IT Manager, RTMC Operations Manager, and RTMC on-call supervisor whenever a DMS is damaged from an accident, vandalism, or weather. The above individuals will be responsible for contacting the RTMC FDOT Manager and the ITS Maintenance Contractor. A page should also be sent to the SunGuide Administrative Pages group. If the DMS is blocking travel lanes on I-75 or any arterial roadway, it is considered Debris. Follow the normal event reporting procedures for this incident (DMS message activation, SunGuide incident report, manual contacts, etc.) DMS Message Malfunction The SWIFT SunGuide Center operations staff may occasionally encounter problems with DMS message control. Previously activated DMS messages may get stuck running in the field and cannot be deactivated from the SWIFT SunGuide Center. Some reasons that may allow this to occur include a software malfunction, a fiber malfunction, a communications failure, etc. This type of failure may be identified by, o A DMS message is confirmed to be active through the software, but no longer responds to any commands sent by the SWIFT SunGuide Center operations staff. o The DMS message is observed on camera even though the software reports that no message is currently active The SWIFT SunGuide Center operations staff must act quickly to help deactivate all errant messages in the field. Information provided by the SWIFT SunGuide Center to the public should be 100% accurate at all times, so the public will develop trust in our system. The specific procedure for deactivating incorrect DMS messages is given below, in order. o Check the SunGuide server to determine if the software crashed. If SunGuide is not operating properly, follow the System Start and System Shut Down instructions given in the SunGuide Users Manual. o Resend the blank command to the DMS with the errant messages. Telvent Farradyne Page 181 Revised: 6/2/08

191 o If the DMS cannot be observed on CCTV camera, a Road Ranger should be asked to verify the condition of the DMS on their normal patrol. If Road Rangers are busy with incidents and other normal responsibilities and can t arrive in a timely manner, the ITS Maintenance Contractor should be notified to verify the status of all DMS in question. o If the errant DMS message is still active, the RTMC IT Technician should be notified. If the RTMC IT Technician is not reached in minutes, contact the RTMC IT Manager. o If the RTMC IT Technician and the RTMC IT Manager cannot be reached, call the following people, in order, until someone is reached: RTMC backup IT Technician, FDOT RTMC Manager, RTMC Operations Manager, and RTMC Operations Supervisor. Leave a detailed message if an answering service is reached and continue to make telephone calls until you speak with someone directly. It is important to speak directly with one of the above contacts. Contact information may be found in the Emergency Contact Numbers section of this document. o Enter the relevant information into the Field Equipment and Internal Systems Tracking Microsoft Access database. Enter the contact attempts and results in the comments section of the open call log. The acceptable time frame for incorrect DMS message field deactivation is: Notify RTMC Message Type IT Technician 1. Lanes Closed As Soon As Possible 2. Delay As Soon As Possible 3. Road Work - (without As Soon As lane closure info) Possible 4. Child Abduction Alert As Soon As Possible 5. Test As Soon As Possible Business Hours Response After Hours Response As Soon As As Soon As Possible Possible 4 Hours 4 Hours 4 Hours 4 Hours 4 Hours 4 Hours Same Day Same Day RTMC Website Failure Whenever the SWIFT SunGuide Center website is not functioning properly, it is considered an emergency. In this situation, operators must adhere to the RTMC Website Malfunction Notification Procedure below. This procedure must be used and will not differ because of the time of day or week. If you have any reservations, you may contact the SWIFT SunGuide Center on-call supervisor. All relevant information and notifications must be recorded in the SWIFT SunGuide Center Incoming/Outgoing Calls and Field Equipment and Internal Systems Tracking databases. There are no exceptions. RTMC Website Malfunction - Notification Procedure: 1. Send an describing the problem to the RTMC Operations Manager, RTMC Operations Supervisor, RTMC IT Technician, RTMC IT Manager, RTMC Shift Supervisors, and the SWIFT SunGuide Center operations staff (if the website problem occurs 2 hours before shift change). 2. The RTMC IT Technician should be contacted by telephone. Calling home telephone and cell phone numbers is acceptable and expected. Telvent Farradyne Page 182 Revised: 6/2/08

192 3. There will be a maximum timeframe of 1 hour for the RTMC IT Technician to respond and commence working on the issue. 4. The SWIFT SunGuide Center operations staff must wait for 1 full hour before attempting to contact the RTMC IT Technician after the initial notification. 5. If the RTMC IT Technician does not call the SWIFT SunGuide Center within the 1 hour after being contacted, SWIFT SunGuide Center operations staff is expected to call the RTMC IT Technician for an update. 6. As soon as the issue has been resolved, the RTMC IT Technician will call the SWIFT SunGuide Center to let the staff know that the website is functional again. The RTMC IT Technician may also ask for the browser to be refreshed. 7. Send a confirmation to the RTMC Operations Manager, RTMC Operations Supervisor, RTMC IT Technician, RTMC IT Manager, RTMC Shift Supervisors, and the RTMC operations staff (if the website problem occurs 2 hours before shift change). This is only expected to contain the times for the start and end of the website problem. If there are any problems executing the above notification procedure, call the RTMC Operations Manager, RTMC Operations Supervisor, and RTMC on-call supervisor, respectively, until contact is made Total System CCTV Failure If all CCTV camera images fail to display or become inoperable, it is essential to continue the operation of the center. Notifications to local agencies and the Road Ranger program should continue. The SWIFT SunGuide Center operations staff is expected to dispatch Road Ranger trucks and talk to FHP dispatch to verify incidents, incident delays, and the extent of all delays so the SWIFT SunGuide Center can continue to accurately report traffic information to the public and partner agencies. When all CCTV cameras are not functioning, the most likely problems are a fiber cut or a SunGuide software failure. The SWIFT SunGuide Center operations staff must attempt to contact the appropriate personnel to fix the problem. Contact the RTMC IT Technician, RTMC IT Manager, and the RTMC on-call Supervisor. If no contact is made with the above individuals, call the RTMC Operations Manager and RTMC Operations Supervisor. Also note that the RTMC IT Technician should be available for any questions concerning the field equipment Fiber Optic Cable Damage or Failure When the fiber optic cables linking the ITS equipment in the field is cut or a splice vault/pull box is damaged, the situation must be reported to the ITS Maintenance Contractor by the RTMC operations staff. The ITS Maintenance Contract is currently held by Transcore. The SWIFT SunGuide Center operations staff must also contact the RTMC IT Technician, RTMC IT Manager, and the RTMC on-call Supervisor. If no contact is made with the above individuals, call the RTMC Operations Manager and RTMC Operations Supervisor. Also note that the RTMC IT Technician should be available for any questions concerning the field equipment. All incoming and outgoing calls must be recorded in the in the SWIFT SunGuide Center Incoming/Outgoing Calls and Field Equipment and Internal Systems Tracking databases. The RTMC operations staff may receive a telephone notification from the party responsible for the fiber optic cable or splice vault/pull box damage because the RTMC telephone number is clearly labeled on all fiber markers. Should this happen, the RTMC operations staff must contact the ITS Maintenance Contractor, RTMC IT Technician, RTMC IT Manager, and the RTMC on-call Supervisor. Again, all incoming and outgoing calls must be recorded in the in the Telvent Farradyne Page 183 Revised: 6/2/08

193 SWIFT SunGuide Center Incoming/Outgoing Calls and Field Equipment and Internal Systems Tracking databases Incident Notification Failure There are times when SunGuide incident alerts are sent by the SWIFT SunGuide Center operations staff but these incident alerts do not reach the intended recipients. These transmission errors may not be directly reported back to the SWIFT SunGuide Center operations staff. Some ways to determine that the incident alerts are not being transmitted include: o Not receiving the incident alerts on the operations cellular telephone o Not receiving the incident alerts on the xxxxx@swiftsunguidecenter.com general office e- mail account If the incident alerts are not being transmitted, o Try to determine the cause of the problem o Contact the RTMC IT Technician. If no answer, contact the RTMC IT Manager o Contact the RTMC on-call supervisor o Compose a short to the RTMC Operations Manager and RTMC Operations Supervisor that describes the problem and the actions taken o Enter all information into the Field Equipment and Internal Systems Tracking database o Log all calls into the Incoming/Outgoing Calls database. RTMC operators must ensure that Level 3 initial incident and incident cleared incident notifications were successfully transmitted 5 minutes after the incident notifications were sent. To do this, the SWIFT SunGuide Center staff should confirm that the incident alerts were sent to the SWIFT SunGuide Center operations cellular telephone and SWIFT SunGuide Center general office account. An additional verification process may be added to the SunGuide software in the future. The SWIFT SunGuide Center operations staff must resend the incident notifications to the individual recipients that were not contacted properly. Telvent Farradyne Page 184 Revised: 6/2/08

194 27 SunGuide Software Failure - Backup Operations 27.1 Event Notification Procedures Backup When the SunGuide software fails, incident pages must still be sent to the regular notification list. The SWIFT SunGuide Center operations staff will utilize telephones, cell phones, and the general office account to notify these incident notification contacts. All contacts that are normally notified of traffic conditions by the SunGuide communications software must be contacted individually with the medium they requested, if possible. All contacts that receive manual telephone calls should continue to receive telephone calls. All contacts that receive s should be ed and all contacts that receive faxes should be faxed. The SWIFT SunGuide Center general office , xxxx@swiftsunguidecenter.com, will have pre-defined groups for all incident types so the SWIFT SunGuide Center operations staff will not have to manually type each individual pager and address. Operators must never copy and paste when sending manual incident notifications. All incident notifications must by typed from scratch. This procedure is necessary to prevent multiple notifications from being sent with the same typo mistakes. Repeat violations of this procedure will be considered as insubordinate and the offending employee will have their employment terminated Event Notification Contacts by Impact Group The incident impact groups are categorized by level and time of day. The contacts that are in each group are as follows. Level 1 Incidents: Start/Clear Normal Business Hours ( Monday to Friday) Contact Agency John Scarpellino Jr. RTMC Operations Manager XXXXXXX RTMC Operations Supervisor SWIFT SunGuide Center Cellular Telephone SWIFT SunGuide Center Control Room RTMC Office SWIFT SunGuide Center Control Room TBD FDOT RTMC Manager Etc. Level 1 Incidents: Update Normal Business Hours ( Monday to Friday) Contact Agency John Scarpellino Jr. RTMC Operations Manager XXXXXXX RTMC Operations Supervisor SWIFT SunGuide Center Cellular Telephone SWIFT SunGuide Center Control Room SWIFT SunGuide Center Office SWIFT SunGuide Center Control Room TBD FDOT RTMC Manager Etc. Level 1 Incidents: Start/Clear Off Hours (All other times) Contact Agency John Scarpellino Jr. RTMC Operations Manager XXXXXXX RTMC Operations Supervisor SWIFT SunGuide Center Cellular Telephone SWIFT SunGuide Center Control Room SWIFT SunGuide Center Office SWIFT SunGuide Center Control Room TBD FDOT RTMC Manager Telvent Farradyne Page 185 Revised: 6/2/08

195 Etc. Level 1 Incidents: Update Off Hours (All other times) Contact Agency John Scarpellino Jr. RTMC Operations Manager XXXXXXX RTMC Operations Supervisor SWIFT SunGuide Center Cellular Telephone SWIFT SunGuide Center Control Room SWIFT SunGuide Center Office SWIFT SunGuide Center Control Room TBD FDOT RTMC Manager Etc. Level 2 Incidents: Start/Clear Normal Business Hours ( Monday to Friday) Contact Agency John Scarpellino Jr. RTMC Operations Manager XXXXXXX RTMC Operations Supervisor SWIFT SunGuide Center Cellular Telephone SWIFT SunGuide Center Control Room SWIFT SunGuide Center Office SWIFT SunGuide Center Control Room TBD FDOT RTMC Manager Etc. Level 2 Incidents: Update Normal Business Hours ( Monday to Friday) Contact Agency John Scarpellino Jr. RTMC Operations Manager XXXXXXX RTMC Operations Supervisor SWIFT SunGuide Center Cellular Telephone SWIFT SunGuide Center Control Room SWIFT SunGuide Center Office SWIFT SunGuide Center Control Room TBD FDOT RTMC Manager Etc. Level 2 Incidents: Start/Clear Off Hours (All other times) Contact Agency John Scarpellino Jr. RTMC Operations Manager XXXXXXX RTMC Operations Supervisor SWIFT SunGuide Center Cellular Telephone SWIFT SunGuide Center Control Room SWIFT SunGuide Center Office SWIFT SunGuide Center Control Room TBD FDOT RTMC Manager Etc. Level 2 Incidents: Update Off Hours (All other times) Contact Agency John Scarpellino Jr. RTMC Operations Manager XXXXXXX RTMC Operations Supervisor SWIFT SunGuide Center Cellular Telephone SWIFT SunGuide Center Control Room SWIFT SunGuide Center Office SWIFT SunGuide Center Control Room TBD FDOT RTMC Manager Etc. Level 3 Incidents: Start/Clear Normal Business Hours ( Monday to Friday) Contact Agency John Scarpellino Jr. RTMC Operations Manager XXXXXXX RTMC Operations Supervisor SWIFT SunGuide Center Cellular Telephone SWIFT SunGuide Center Control Room SWIFT SunGuide Center Office SWIFT SunGuide Center Control Room TBD FDOT RTMC Manager Telvent Farradyne Page 186 Revised: 6/2/08

196 Debbie Tower FDOT D1 PIO SWAO Cindy Clemmons-Adente FDOT D1 PIO Bartow Etc. Level 3 Incidents: Update Normal Business Hours ( Monday to Friday) Contact Agency John Scarpellino Jr. RTMC Operations Manager XXXXXXX RTMC Operations Supervisor SWIFT SunGuide Center Cellular Telephone SWIFT SunGuide Center Control Room SWIFT SunGuide Center Office SWIFT SunGuide Center Control Room TBD FDOT RTMC Manager Debbie Tower FDOT D1 PIO SWAO Cindy Clemmons-Adente FDOT D1 PIO Bartow Etc. Level 3 Incidents: Start/Clear Off Hours (All other times) Contact Agency John Scarpellino Jr. RTMC Operations Manager XXXXXXX RTMC Operations Supervisor SWIFT SunGuide Center Cellular Telephone SWIFT SunGuide Center Control Room SWIFT SunGuide Center Office SWIFT SunGuide Center Control Room TBD FDOT RTMC Manager Debbie Tower FDOT D1 PIO SWAO Cindy Clemmons-Adente FDOT D1 PIO Bartow Etc. Level 3 Incidents: Update Off Hours (All other times) Contact Agency John Scarpellino Jr. RTMC Operations Manager XXXXXXX RTMC Operations Supervisor SWIFT SunGuide Center Cellular Telephone SWIFT SunGuide Center Control Room SWIFT SunGuide Center Office SWIFT SunGuide Center Control Room TBD FDOT RTMC Manager Debbie Tower FDOT D1 PIO SWAO Cindy Clemmons-Adente FDOT D1 PIO Bartow Etc. Special Event All members of the Level 1 and Level 2 incident groups, plus: Contact Agency John Scarpellino Jr. RTMC Operations Manager XXXXXXX RTMC Operations Supervisor SWIFT SunGuide Center Cellular Telephone SWIFT SunGuide Center Control Room SWIFT SunGuide Center Office SWIFT SunGuide Center Control Room TBD FDOT RTMC Manager Etc. Child Abduction Alert All members of the Level 1 and Level 2 incident groups, plus: Contact Agency John Scarpellino Jr. RTMC Operations Manager XXXXXXX RTMC Operations Supervisor SWIFT SunGuide Center Cellular Telephone SWIFT SunGuide Center Control Room Telvent Farradyne Page 187 Revised: 6/2/08

197 SWIFT SunGuide Center Office SWIFT SunGuide Center Control Room TBD FDOT RTMC Manager Etc. Administration All members of the Level 1 and Level 2 incident groups, plus: Contact Agency John Scarpellino Jr. RTMC Operations Manager XXXXXXX RTMC Operations Supervisor SWIFT SunGuide Center Cellular Telephone SWIFT SunGuide Center Control Room SWIFT SunGuide Center Office SWIFT SunGuide Center Control Room TBD FDOT RTMC Manager Etc. Construction All members of the Level 1 and Level 2 incident groups, plus: Contact Agency John Scarpellino Jr. RTMC Operations Manager XXXXXXX RTMC Operations Supervisor SWIFT SunGuide Center Cellular Telephone SWIFT SunGuide Center Control Room SWIFT SunGuide Center Office SWIFT SunGuide Center Control Room TBD FDOT RTMC Manager Etc. Testing All members of the Level 1 and Level 2 incident groups, plus: Contact Agency John Scarpellino Jr. RTMC Operations Manager XXXXXXX RTMC Operations Supervisor SWIFT SunGuide Center Cellular Telephone SWIFT SunGuide Center Control Room SWIFT SunGuide Center Office SWIFT SunGuide Center Control Room TBD FDOT RTMC Manager Etc. RTMC Bulletin All members of the Level 1 and Level 2 incident groups, plus: Contact Agency John Scarpellino Jr. RTMC Operations Manager XXXXXXX RTMC Operations Supervisor SWIFT SunGuide Center Cellular Telephone SWIFT SunGuide Center Control Room SWIFT SunGuide Center Office SWIFT SunGuide Center Control Room TBD FDOT RTMC Manager Etc. Global All members of the Level 1 and Level 2 incident groups, plus: Contact Agency John Scarpellino Jr. RTMC Operations Manager XXXXXXX RTMC Operations Supervisor SWIFT SunGuide Center Cellular Telephone SWIFT SunGuide Center Control Room SWIFT SunGuide Center Office SWIFT SunGuide Center Control Room TBD FDOT RTMC Manager Etc. Telvent Farradyne Page 188 Revised: 6/2/08

198 27.3 Backup Event Notification Formats Event Notification Format - Incidents The SWIFT SunGuide Center operations staff should utilize the paging format listed in this section to provide incident and event information. Many county and state agencies receive SWIFT SunGuide Center incident pages; therefore, it is important that SWIFT SunGuide Center operations staff use care when sending these pages to recipients. Double check that the information you are sending is accurate and spelled properly before sending. The SWIFT SunGuide Center incident notifications will be closely monitored by FDOT and SWIFT SunGuide Center management. Information provided is limited due to amount of text that can be received by pagers and cell phones that accept messages. The limit is 119 characters of text, including special characters and header information. The information will be given in all capital letters and provided as follows: Subject Line: 1. Center Identification = FDOT D1 2. Incident Level = ACTIVE L1, ACTIVE L2, ACTIVE L3, CLEARED L1, CLEARED L2, CLEARED L3 Note: Skip this step and go to step 3 the first time after an incident gets upgraded from Level 1 to Level 2 or from Level 2 to Level Incident Level Changes = ACTIVE L1 NOW L2 or ACTIVE L2 NOW L3. Note: When an incident upgrades to a higher level, skip step number 2 and use one of the two phrases given above. Text: 1. Incident Type (i.e. ACCIDENT, ACC ON RIGHT SHOULDER, POLICE ACTIVITY, DISABLED VEHICLE, EMERGENCY ROADWORK, DEBRIS, DELAY, ROAD CLOSED, EXIT RAMP CLOSED, ENTRANCE RAMP CLOSED, FLOODING, etc.) a. Use the type ACCIDENT when an accident clears and only delays remain. b. Use the type ROAD CLOSED when an accident or construction closes a roadway. c. Use the type EXIT RAMP CLOSED or ENTRANCE RAMP CLOSED when an accident or construction closes an exit or entrance ramp. 2. Roadway where the incident occurred (i.e. I-75, CORKSCREW RD, FLORIDA S TURNPIKE, DANIELS PKWY TO I-75 SOUTH, COLONIAL BLVD AT I-75, etc.) 3. Direction of Travel (i.e. NORTH, SOUTH, EAST, WEST) 4. Specific Location Includes at, past, or between exit numbers followed by the roadway abbreviations in brackets (i.e. AT EX 128 [ALICO], PAST EX 131 [DANIELS], EX [HARBOR VIEW-KINGS HWY], etc.) Note that the exit name given in brackets after the exit number is abbreviated exactly like the character formats in the SWIFT SunGuide Center DMS SOP. 5. Fuel Spill Notification Add WITH FUEL SPILL and # GAL, only if a spill is confirmed. Note that the # in # GAL is the number of gallons spilled. 6. Roadway Impact (i.e. 2 RIGHT LANES BLOCKED, RIGHT LANE ON EXIT RAMP BLOCKED, RIGHT LANE ON ENTRANCE RAMP BLOCKED, ALL LANES OPEN, etc.) When the closure is still active, skip this section for the Road Closed and Ramp Closed incident types [do not use Use Other Routes ]. 7. Delays (i.e. NO DELAY, DELAY EX 66-69, EXPECT DELAY, DELAY CLEARED ). Telvent Farradyne Page 189 Revised: 6/2/08

199 a. Use DELAY CLEARED for DELAY incident types when the delay clears. b. Use EXPECT DELAY when delays cannot be confirmed. Delays cannot be confirmed on any other limited access highway or arterial roadway. EXPECT DELAY should be used for these incidents. c. Use EXPECT DELAY in the clear page when all travel lanes open and delays were never verified (this would be the final page for that incident). 3. Operator s Initials 4. Date & Military Time in this format: (Feb. 27, 1356 hours). Note: This format serves as the start time of the incident and is one way to quickly determine the Incident ID. Note: The incident date and start time will stay the same for all pages sent. * Note: When delays clear and normal time of day traffic is observed, the only acceptable word to describe the situation is CLEARED. For example, when delays from exits clear from an earlier incident, the message should read FDOT D1 CLEARED L2: DISABLED VEHICLE I-75 NORTH PAST EXIT 101 [COLLIER BLVD] ALL LANES OPEN. DELAY CLEARED. JS * Note: There are times when abbreviations must be used because of the limited character space for text messaging. The SWIFT SunGuide Center operations staff should do everything possible to avoid abbreviating. On the rare occasion that this should occur, the message should be abbreviated in the following order: Spell VEHICLE as VEH Remove excess spaces Remove excess punctuation Eliminate your middle initial Remove the space between the exit numbers and the exit names Spell LANES as LNS I-75 NORTH should be 75N I-75 SOUTH should be 75S * Note: When information is reported incorrectly in a page, an update page should be sent out immediately. An example of a correction page is given below (notice that this page exceeded the 119 character limit and was abbreviated using the order given in the above note). Subject Line: FDOT D1 ACTIVE L2 Text: ACCIDENT 75N PAST EXIT 139[LUCKETT RD] 3 LEFT LNS BLOCKED(CORRECTS 3 RIGHT LNS)DELAY EX JS * Note: Actions required to manage the incident should be completed prior to paging. * Note: Use the phrase ALL LANES OPEN when travel is resumed for all lanes. * Note: Use the word CLEARED when referring to delay information. The following rules are necessary for clarification and must be strictly adhered to: 1) All the miscellaneous paging messages must be supervisor approved except for the Child Abduction Alerts. For procedures on how to handle paging notifications for Child Abduction Alerts, please consult the Amber Alert Procedure and Incident Paging Message Amber (Child Abduction) Alert sections of this document. 2) An Initial and Cleared page is the correct paging category for Incident start (Subject Line will state Active ) All lanes are open with or without delays (Subject Line will state Cleared ) Telvent Farradyne Page 190 Revised: 6/2/08

200 Traffic resumes to normal time of day volume (Subject Line will state Cleared ) Incident upgrades from Level 1 to Level 2 Incident upgrades from Level 2 to Level 3 The first time a page is sent with fuel spill information 3) An incident must be immediately categorized as a Level 3 incident whenever the incident involves A total roadway closure An overturned tractor trailer or commercial vehicle (with more than two axles) that blocks at least one travel lane A fuel spill greater than 40 gallons Emergency road work projected to last longer than 2 hours Overnight road work that lasts past 0600 hrs Daytime road work that lasts past 1600 hrs A struck pedestrian that blocks at least one travel lane A fatality or possible fatality that blocks at least one travel lane Any crime scene that blocks at least one travel lane 4) An incident is considered to be newsworthy once delays are greater than or equal to 10 miles in length Event Notification Format Amber (Child Abduction) Alert The SWIFT SunGuide Center operations staff must notify the RTMC on-call supervisor or the RTMC Operations Manager before sending an Amber alert event notification. After authorization, the SWIFT SunGuide Center operations staff must send the Amber alert event notification page by using the Child Abduction Alert paging group from the xxxxx@swiftsunguidecenter.com address with Lotus Notes at the top of every hour. Only the District 5 TMC or the FDOT District 1 FDOT RTMC Manager can confirm that a child abduction alert is in effect. If the SWIFT SunGuide Center operations staff receives information of a child abduction alert from another source, they must follow the procedures in the Amber Alert Procedure section of this document. The following format is the supervisor pre-approved message for this situation. Subject Line: 1. Center Identification = FDOT D1 Text: 1. Incident type: AN AMBER ALERT IS IN EFFECT FOR COLLIER COUNTY. THE VEHICLE IS A (vehicle color) (vehicle make) (vehicle model) WITH A (two letter state abbreviation) TAG (license plate number). 2. Operator s Initials 3. Date & Military Time in this format: (Feb. 27, 1356 hours). The following format is the supervisor pre-approved message for child abduction alert cancellations. Subject Line: 1. Center Identification = FDOT D1 Text: 1. Incident type: THE AMBER ALERT FOR SARASOTA COUNTY HAS BEEN CANCELLED. 2. Operator s Initials Telvent Farradyne Page 191 Revised: 6/2/08

201 3. Date & Military Time in this format: (Apr. 03, 0745 hours) Event Notification Format Storm Watch and Storm Warning The SWIFT SunGuide Center operations staff must send a notification page to all SWIFT SunGuide Center Level 1, 2, & 3 incident notification recipients whenever the local Emergency Operations Centers confirm that there is a Storm Watch or a Storm Warning in effect. The following is the supervisor pre-approved message for this situation. Subject Line: 1. Center Identification = FDOT D1 BULLETIN Text: 1. Incident type: A HURRICANE WATCH IS IN EFFECT FOR LEE COUNTY or A HURRICANE WARNING IS IN EFFECT FOR LEE COUNTY. 2. Include shelter information if the SWIFT SunGuide Center has written confirmation from the local Emergency Operations Centers: STORM SHELTERS ARE OPEN or STORM SHELTERS WILL OPEN AT [time]. Note that [time] = 12 A.M., 1 A.M., 2 A.M.,, 10 P.M., 11 P.M. 3. Operator s Initials 4. Date & Military Time in this format: (Feb. 27, 1356 hours) Event Notification Format Shutdown for SWIFT SunGuide Center Power Failure The SWIFT SunGuide Center operations staff must send a notification page to all SWIFT SunGuide Center Level 1, 2, & 3 incident notification recipients whenever the SWIFT SunGuide Center has to partially shut down for a long term power failure. The following is the supervisor pre-approved message for this situation. Subject Line: 1. Center Identification = FDOT D1 Text: 1. POWER FAILURE. ALT NOTIFICATION PROCEDURE IN EFFECT, LTD DETECTION. REACH RTMC: xxx-xxx-xxxx 2. Operator s Initials 3. Date & Military Time in this format: (Feb. 27, 1356 hours). Note: The local Emergency Operations Centers, FHP Dispatch, FDOT District 1 PIO, and the other contacts in the power failure procedures outlined in this document must be contacted manually immediately after sending this page. Give these contacts as much information about our current status as possible Event Notification Format Power Restored at the SWIFT SunGuide Center When power to the SWIFT SunGuide Center is restored, the following message must be sent to all Level 1, 2, & 3 incident notification recipients. Subject Line: 1. Center Identification = FDOT D1 Text: 1. POWER RESTORED. PAGING SYSTEM FUNCTIONAL. CONTACTS WILL RESUME AS NORMAL. 2. Operator s Initials Telvent Farradyne Page 192 Revised: 6/2/08

202 3. Date & Military Time in this format: (Feb. 27, 1356 hours). Note: The local Emergency Operations Centers, FHP Dispatch, FDOT District 1 PIO, and the other contacts in the power failure procedures outlined in this document must be contacted manually immediately after sending this page. These contacts must be informed that the power at the SWIFT SunGuide Center is restored and detection is no longer limited ( fully functional, if applicable.) Event Notification Format SWIFT SunGuide Center Relocated to Alternate Facility The RTMC operations staff must send a notification page to the Global category of the SWIFT SunGuide Center incident notification recipients whenever the SWIFT SunGuide Center has to be relocated to an alternate TMC facility to continue operations. The following is the supervisor pre-approved message for this situation. Subject Line: 2. Center Identification = FDOT D1 Text: 3. SWIFT SUNGUIDE RTMC RELOCATED TO THE (alternate TMC location) TMC. ALT NOTIFICATION PROCEDURE IN EFFECT. REACH RTMC: xxx-xxx-xxxx 4. Operator s Initials 4. Date & Military Time in this format: (Feb. 27, 1356 hours). Note: The local Emergency Operations Centers, FHP Dispatch, FDOT District 1 PIO, and the other contacts in the power failure procedures outlined in this document must be contacted manually immediately after sending this page. Give these contacts as much information about our current status as possible Event Notification Format Operations Resumed at the SWIFT SunGuide Center When the RTMC operations staff leaves the alternate TMC location and resumes operations at the SWIFT SunGuide Center, the following message must be sent to the Global category of the SWIFT SunGuide Center incident notification recipients. Subject Line: 2. Center Identification = FDOT D1 Text: 3. OPERATIONS RESUME IN THE SWIFT SUNGUIDE CENTER. CONTACTS WILL CONTINUE AS NORMAL. 4. Operator s Initials 4. Date & Military Time in this format: (Feb. 27, 1356 hours). Note: The local Emergency Operations Centers, FHP Dispatch, FDOT District 1 PIO, and the other contacts in the power failure procedures outlined in this document must be contacted manually immediately after sending this page. These contacts must be informed that the power at the SWIFT SunGuide Center is restored and detection is no longer limited ( fully functional, if applicable.) Event Notification Format Administration The Administration event notification group is used whenever a text message needs to be sent to internal RTMC contacts only. Examples of internal messages include pages for systems Telvent Farradyne Page 193 Revised: 6/2/08

203 related issues, video wall failures, global DMS and camera failures, problems contacting MVP Marketing for website issues, and other INTERNAL informational type notifications. The format for these INTERNAL messages to the Administration notification group should always be as follows. Subject Line: 1. Center Identification = FDOT D1 RTMC STAFF ADVISORY Text: 1. [appropriate text message in capital letters] 2. Operator s Initials 3. Date & Military Time in this format: (Feb. 27, 1356 hours) Event Notification Format SWIFT SunGuide Center Bulletin (Newsworthy Events) The RTMC Operations Manager or the RTMC on-call supervisor must be notified whenever there is a newsworthy event taking place in the SWIFT SunGuide Center coverage area that concerns traffic. Examples of newsworthy events include: o The construction workers killed or injured on I-75 or any other arterial roadway in FDOT District 1 o A police chase or any police activity that closes I-75 or any other arterial roadway in FDOT District 1 o Any tow truck driver or pedestrian that is struck by a vehicle o A FHP crime scene o An incident that requires an investigation for a fatality or possible fatality (travel lane blocked or shoulders blocked) o Any incident that causes delays that are greater than or equal to 10 miles The notification procedure is as follows: 1. Call the RTMC Operations Manager or the RTMC on-call supervisor 2. If there is no answer from the RTMC Operations Manager or RTMC on-call supervisor within 5 minutes, continue to make contact until someone is reached. 3. Send one page at the start of the incident to the SWIFT SunGuide Center Bulletin event notification group. This page will notify all agencies that requested this type of information. Some sample SPECIAL EVENT pages are as follows, Example #1 Subject Line: FDOT D1 RTMC BULLETIN Text: TOW TRUCK DRIVER STRUCK BY SUV ON I-75 SOUTH PAST EXIT 116[BONITA BEACH] 2 RIGHT LNS BLOCKED. JS /27/07 Example #2 Subject Line: FDOT D1 RTMC BULLETIN Text: FATAL SHOOTING AT WALGREENS, TOLEDO BLADE BLVD CLOSED NORTH OF WEST PRICE BLVD. JS /27/07 Telvent Farradyne Page 194 Revised: 6/2/08

204 4. Send accident and incident event notifications to the appropriate incident level, page type, and time of day event notification categories, as normal procedure Road Ranger Data Entry - Backup Track on manual forms? SwRI to provide spreadsheets for easier system population, post failure? A Road Ranger log (in Microsoft Access) should be opened for each Road Ranger when starting their shifts. The assigned Problem type should be recorded as #21. The Solution type should be recorded as #21 upon shift completion and must be noted on the same Road Ranger log. Telvent Farradyne Page 195 Revised: 6/2/08

205 28 SWIFT SunGuide Disaster Recovery Plan This section describes the disaster recovery plan for the FDOT District 1 SWIFT SunGuide Center facilities and related ITS infrastructure. This plan details how the various organizational units intend to perform their responsibilities in the event of a disaster. The Disaster Recovery Plan defines a disaster as "an occurrence inflicting widespread destruction or distress upon the FDOT District 1 SWIFT SunGuide Center facilities, ITS systems or infrastructure". For the purposes of this document this means that the facilities, computing resources, or major components thereof, are deemed unavailable for operations. This section contains some general assumptions, but does not include all special situations that can occur. Any special decisions for situations not covered in this plan will be made by FDOT District 1 SWIFT SunGuide Center senior management. Invoking this plan implies that a recovery operation has begun and will continue with top priority until workable ITS operations has been re-established Disaster Event Overview Disaster events can be defined in four categories for the FDOT District 1 SWIFT SunGuide Center operations. Each category predefines actions that facilitate rapid management decision making. The four categories provide management with options from handling the disaster event within normal operational resolution capabilities, deploying emergency maintenance repair crews, relocating operations to a contingency site, and adjusting the work plan to rebuild ITS infrastructure resulting from catastrophic damage Initial Failure Under most circumstances, initial failures will be noticed by the SWIFT SunGuide Center operations staff. Depending on the time period the failure is identified, the SWIFT SunGuide Center operations staff will initiate one of the following two actions: 1. Normal Business Hours - During normal business hours, the SWIFT SunGuide Center operations staff will notify the RTMC Shift Supervisor on duty. The RTMC Shift Supervisor will perform preliminary trouble identification and fault isolation procedures. If the failure is not resolved, the situation will be reported to the RTMC Operations Manager. 2. Non-Business Hours During non-business hours, the SWIFT SunGuide Center operations staff will notify the RTMC Shift Supervisor on duty. The RTMC Shift Supervisor will perform preliminary trouble identification and fault isolation procedures. If the failure is not resolved, the situation will be reported to the RTMC on-call supervisor and report the failure. If the scheduled RTMC on-call supervisor does not respond within 10 minutes, contact the RTMC Operations Supervisor and the RTMC Operations Manager, respectively. This notification process should continue until all SWIFT SunGuide Center managers have been contacted or a SWIFT SunGuide Center manager responds. Under certain circumstances, the news media may be present at the SWIFT SunGuide Center. The media may request information or statements during the initial failure process. If this occurs, the SWIFT SunGuide Center operations staff will refer to the SWIFT SunGuide Center SOG document for the guidelines for news media inquiries. Telvent Farradyne Page 196 Revised: 6/2/08

206 28.3 Crisis Assessment The RTMC Shift Supervisor, RTMC Operations Supervisor, or RTMC Operations Manager will be tasked with gathering information on the disaster event and assessing the magnitude of the crisis depending on the severity. If a Category 3 or Category 4 emergency response is necessary, they will initiate a conference with the Crisis Assessment Team about the pending crisis in an effort to decide appropriate actions. The conference notification process may take place in person or over the telephone. The Crisis Assessment Team is comprised of the following members: a) FDOT RTMC Contract Manager b) FDOT RTMC Operations ITS Project Manager c) FDOT Program Manager d) RTMC Contract Manager e) RTMC Operations Manager f) RTMC IT Manager g) RTMC IT Technician h) FDOT Road Ranger Project Manager i) FHP Communications Captain j) FHP Captain k) MCCO Captain This group shall discuss and survey the scope of damage in order to assign a Category 3 or 4 disaster classification, and will formally initiate deployment to the contingency site depending on the severity of the disaster. The Crisis Assessment Team may also decide to downgrade the crisis to a Category 2 classification and initiate the procedures outlined in this section. The FDOT RTMC Contract Manager, or designee, has the ultimate responsibility for evaluating and declaring the disaster classification, as well as assessing the organizational impact on the enterprise and its ongoing operations. In the absence of the FDOT RTMC Contract Manager, the FDOT RTMC Operations ITS Project Manager and the FDOT Program Manager will be responsible for these actions Crisis Designations The crisis classifications are given below: o Category 1 Defined as an ITS device failure that does not have significant impact on ITS operations. Examples include CCTV camera, DMS, or video wall cube malfunctions. A single device failure will be handled utilizing normal operational resolution capabilities. Within this classification, routine management and user communication channels will be utilized. o Category 2 Defined as an ITS subsystem failure. An ITS subsystem failure is the result of simultaneous failure of multiple devices (two or more) and results in disruption to ITS operations. The subsystems are defined as video wall, SWIFT SunGuide Center network, SunGuide, fiber optic communications line, CCTV camera system, or DMS system. Subsystem failures will normally result in the need to implement emergency repair call out procedures, that are covered under existing maintenance contracts. o Category 3 Defined as a catastrophic impact to the FDOT District 1 SWIFT SunGuide Center facility or infrastructure resulting in a complete systems outage that is expected to exceed 48 hours. Examples include water damage, smoke, fire, vandalism, terrorism, lightning, or any other event with system downtime that renders a major portion of the Telvent Farradyne Page 197 Revised: 6/2/08

207 facility unusable for more than 48 hours. Under these circumstances, it is expected that the FDOT District 1 SWIFT SunGuide Center facility will cease operations and relocate to one of the following facilities: District 7 TMC District 4 Palm Beach ITMS District 6 TMC District 4 Broward TMC Other facility as determined by the Crisis Management Team o Category 4 Defined as catastrophic ITS infrastructure damage that results in the need to undergo major reconstruction. Under this condition, the plan is to prioritize the rebuilding of the infrastructure in relation to area transportation needs Coordinating with Other FDOT Districts As the FDOT traffic management centers around the state become more and more interconnected, there is a growing importance for these traffic management centers to advise regional partner traffic management centers of disaster events and systems outages. During a declared Disaster Recovery Plan event, a general notification should be communicated, manually and by text message, by the RTMC Shift Supervisor to the TMC community. This notification is a simple statement that the FDOT District 1 SWIFT SunGuide Center is experiencing a system outage. The estimated duration of the system outage should also be included, if known. For sample general notification formats and content, please refer to the Backup Event Notification Formats section of this document. The SWIFT SunGuide Center operations staff should contact the following traffic management centers when experiencing a disaster event or long-term system outage. o District 7 TMC o District 4 Palm Beach ITMS o District 6 TMC o District 4 Broward TMC o District 5 TMC o Florida s Turnpike TMC Communications with the Media All press releases and media interviews about the crisis, its impact on the operations of the SWIFT SunGuide Center, related recovery operations, the current status of recovery, estimates of damage, and the outlook for future operations shall be conducted through the FDOT District 1 Public Information Officer. Comments about the crisis or disaster shall NOT be offered to reporters or other media representatives by any SWIFT SunGuide Center staff member. This includes requested comments about publicly known aspects and details of the crisis. Any approaches or questions from the media should be directed to the FDOT District 1 Public Information Officer. The dissemination of information to the media through the FDOT District 1 Public Information Officer enables control over the accuracy of the information being released, protects the institutionally sanctioned perspective, and minimizes unwarranted speculation and sensationalism. Telvent Farradyne Page 198 Revised: 6/2/08

208 It is possible that the media will come to the FDOT District 1 SWIFT SunGuide Center unannounced. If this situation occurs, the RTMC on-call supervisor should be contacted and the SWIFT SunGuide Center operations staff should follow the procedures given in the SWIFT SunGuide Center SOG document Roles and Responsibilities Each member of the SWIFT SunGuide Center staff has roles and responsibilities that pertain to their position. The key personnel involved in the SWIFT SunGuide Center Disaster Recovery Plan are: o SWIFT SunGuide Center Operations Staff Responsible for system operation and monitoring inside the control center. They will generally be the first individuals to notice any failures. They are responsible for notifying the RTMC Shift Supervisor. o RTMC Shift Supervisors Responsible for recognizing the initial failure during normal hours, gathering the essential information, and reporting the issue to the RTMC Operations Manager. o RTMC Operations Manager Responsible for assessing the magnitude of the crisis based on the information gathered by the SWIFT SunGuide Center operations staff and RTMC Shift Supervisors. The RTMC Operations Manager can implement Category 1 or 2 disaster recovery procedures. For Category 3 and 4 disasters, the RTMC Operations Manager will contact the FDOT RTMC Contract Manager and participate in the subsequent conference call. The conference call participants will discuss the event and choose an appropriate course of action. Additional responsibilities include communicating situational reports to the FDOT RTMC Contract Manager throughout the crisis. o RTMC IT Technician Responsible for SWIFT SunGuide Center field equipment and communication systems. Will work in conjunction with the RTMC Operations Manager to assess and restore failures. o RTMC IT Manager Responsible for internal SWIFT SunGuide Center computer and network systems. Will work in conjunction with the RTMC Operations Manager and FDOT RTMC Contract Manager to assess and restore failures. o FDOT RTMC Contract Manager Responsible for assessing the magnitude of the crisis based on the information gathered by the RTMC Operations Manager, RTMC IT Technician, and RTMC IT Manager. The FDOT RTMC Contract Manager can implement Category 1, 2, 3, or 4 disaster recovery procedures. For Category 3 and 4 disasters, the FDOT RTMC Contract Manager will coordinate the meeting with the Crisis Assessment Team to discuss events and the appropriate course of action. o RTMC Contract Manager Responsible for monitoring all disaster related events and accessing the impacts to ITS operations in coordination with the RTMC Operations Manager. Responsible for overall management, coordinating, planning related to disaster events. Additional responsibilities include communicating situational reports to FDOT District IV management. Telvent Farradyne Page 199 Revised: 6/2/08

209 28.5 Employee Vacation Status In the event of an implementation of the Disaster Recovery Plan, it shall be the policy of the SWIFT SunGuide Center to honor previously scheduled employee vacations. All employee vacations already in progress will also proceed normally Disaster Recovery Plan Flowcharts The SWIFT SunGuide Center will develop alternate operational contingency sites in the future. The potential alternate locations must have a fully installed SunGuide system in order to be considered. SWIFT SunGuide Center management will decide which alternate contingency site will be utilized depending on the disaster event. The flowcharts are given below. Insert flowcharts here and insert the flowchart descriptions in the sections below Page 1 Flow Chart Description Generally the TMC operators on duty at the RTMC will be the first individuals to identify a disaster event. The disaster event may occur during normal or non-normal business hours. The shift supervisor on duty will gather initial information about the field devices, subsystems, or systems that are not in operation and contact the RTMC Operations Manager to notify them of the disaster event. The RTMC Operations Manager will assess the magnitude of the crisis with the RTMC Contract Manager and initiate a predefined category level depending on the event. For single ITS device failures, the shift supervisor will assign a Category 1 failure and the RTMC operations staff will log the device failure. Category 1 failures are defined as non critical and are to be handled within the normal operational resolution capabilities. For multiple simultaneous ITS device failures defined as a subsystem failure, the RTMC Contract Manager will assign a Category 2 failure that requires emergency repair procedures. The RTMC Contract Manager will contact the RTMC Operations Manager and the RTMC Field Engineer. For multiple systems failures or if the RTMC facility should need evacuation, the RTMC Contract Manager will initiate a conference call with the FDOT RTMC Manager, RTMC Operations Manager, and the RTMC Field Engineer. This management group will discuss the emergency situation and, if needed, relocate operations to one of the contingency sites. The contingency sites have been identified as the FDOT District 7 RTMC, the FDOT District 6 RTMC, the FDOT District 4 Palm Beach ITMS TMC, and the FDOT District 4 Broward TMC. Depending in the nature of the emergency and the expected duration, the management team may decide to reclassify the event as a Category 2 situation and proceed from there Page 2 Flow Chart Description Page 2 of the Disaster Recovery Flow chart further predefines the actions to be followed during a Category 2 failure. The RTMC Contract Manager will perform a more in depth assessment of the crisis and may be required to drive to the location of the crisis. The RTMC Contract Manager will contact the FDOT RTMC Manager, RTMC Operations Manager and RTMC Field Engineer to brief them of the current situation. The RTMC Operations Manager will contact other government agencies and regional TMC centers that are interconnected with the SWIFT SunGuide Center and notify them of system outages and reduced operational status. The Telvent Farradyne Page 200 Revised: 6/2/08

210 RTMC Field Engineer will be responsible for contacting the emergency repair contractor(s) and coordinating the repair procedures. The RTMC Field Engineer will work with the emergency repair contractor(s) and communicate the estimated time to repair or restore full operational capabilities to the RTMC Contract Manager and RTMC Operations Manager. The RTMC Contract Manager will then notify the FDOT RTMC Manager of the estimated repair time and the RTMC Operations Manager will contact the other government agencies and RTMC centers to provide suitable updates. The RTMC Field Engineer will coordinate the procurement of replacement parts, effect repairs, and test the system. Once the system is tested and deemed to be restored to full operational capacity, the RTMC Field Engineer will notify the RTMC Contract Manager who will, in turn, notify the FDOT RTMC Manager, FDOT ITS Program Manager, and RTMC Operations Manager. The FDOT ITS Program Manager shall be responsible for declaring an end to the disaster state. At this point in the process the RTMC Operations Manager shall be responsible for notifying the TMC staff, government agencies, and regional SWIFT SunGuide Center partners that were initially contacted. Additionally, the RTMC Operations Manager shall coordinate the preparation of an after action report detailing the circumstances and events of the disaster, and shall also recommend revisions to the Disaster Recovery Plan Page 3 Flow Chart Description Page 3 of the Disaster Recovery Flowchart further predefines the actions to be followed during a Category 3 failure. This failure requires deployment to the contingency site. The RTMC Contract Manager issues immediate notifications to the FDOT RTMC Manager and the FDOT ITS Program Manager. The RTMC Contract Manager then notifies the RTMC Operations Manager to prepare for staff relocation and dispatches the RTMC IT Technician to the alternate RTMC location to prepare backup SunGuide servers for continued operation. The RTMC Operations Manager notifies the staff of relocation and dispatches two or more operators to the alternate RTMC location. The RTMC Operations Manager will also contact other government agencies and RTMC centers that are interconnected with the SWIFT SunGuide Center and notify them of system outages and deployment to the contingency site. Once the backup systems at the alternate RTMC location are verified to be online and functioning and the operators have arrived, the RTMC Operations Manager will begin operations from the contingency location The RTMC IT Technician must prepare the SunGuide servers at the alternate RTMC location for primary operation and bring the system online. During the above process, the RTMC Field Engineer will contact the emergency repair contractor, conduct a damage assessment review, and prepare a damage access and repair report. The RTMC Field Engineer will give the report to the RTMC Contract Manager who will then distribute it to the FDOT RTMC Manager. The RTMC Operations Manager will contact the other government agencies and RTMC centers and provide suitable updates. The RTMC Field Engineer will coordinate the procurement of replacement parts, effect repairs, and test the system. Once the system is tested and deemed to be restored to full operational capacity, the RTMC Field Engineer will notify the RTMC Contract Manager who will then notify the FDOT RTMC Manager, RTMC Operations Manager, and RTMC IT Technician. The RTMC IT Technician will ready the primary SunGuide servers for operation and bring the systems online at the SWIFT SunGuide Center. The RTMC Operations Manager will have Telvent Farradyne Page 201 Revised: 6/2/08

211 operators positioned at the SWIFT SunGuide Center to be ready to resume normal operation. Once normal is confirmed, the RTMC Operations Manager will recall the operators at the contingency site. After normal operations are restored, the FDOT ITS Program Manager shall be responsible for declaring an end to the disaster state. At this point in the process, the RTMC Operations Manager shall be responsible for notifying the RTMC staff, government agencies, and RTMC partners that were initially contacted. Additionally, the RTMC Operations Manager shall coordinate the preparation of an after action report detailing the circumstances and events of the disaster, and shall also recommend revisions to the Disaster Recovery Plan Page 4 Flow Chart Description Page 4 of the Disaster Recovery Flow chart further predefines the actions to be followed during a Category 4 failure. This failure is reserved for a catastrophic event that results in massive damage to the ITS infrastructure within FDOT District 1. The RTMC Contract Manager will contact the RTMC IT Technician, RTMC Field Engineer, and Project Administrator. The RTMC Field Engineer will conduct an assessment of damage review, contact the emergency maintenance contractor, and prepare a damage assessment and repair report. Based on this report and if possible, the RTMC Contract Manager will dispatch the RTMC IT Technician to the alternate RTMC location to prepare the SunGuide servers (backup or primary) for primary operation and bring systems online. The RTMC Operations Manager notifies the staff of the relocation and dispatches two or more operators to the alternate RTMC location. The RTMC Operations Manager will contact other government agencies and RTMC centers that are interconnected with the SWIFT SunGuide Center and notify them of system outages and deployment to the contingency site. The RTMC Operations Manager will begin operations from the contingency location once the backup systems at the alternate RTMC location are verified to be online and functioning and the operators have arrived. The FDOT ITS Program Manager will review the damage assessment and repair report with the FDOT District 1 Traffic Operations Engineer and make modifications as needed. They will reprioritize the 5 year work plan based on the catastrophic damage and current needs. Telvent Farradyne Page 202 Revised: 6/2/08

212 28.7 End of Disaster State Formal notice of the end of a disaster state shall be given as per the management notifications. In addition, users shall be notified as per this document. Depending on the characteristics and duration of the disaster, this notification may not entail a complete return to normal operations. This notification shall signal the end of specific disaster operations, however TMC Staff The RTMC Operations Supervisor will be responsible for notifying all RTMC staff for the end of Category 3 and 4 emergencies. The RTMC Operations Manager will assume this responsibility in the absence of the RTMC Operations Supervisor. The emergency contact information for the SWIFT SunGuide Center staff is located in the Emergency Contact Information section of this document Assessment Review Following the declaration of the end of the Disaster Recovery Plan, a lessons learned assessment should be conducted by SWIFT SunGuide Center management. After a complete review has been preformed, these procedures will be modified to reflect the changes Training One of the purposes of training is to increase awareness of all parties to the potential threats posed by a disaster, and to acquaint them with the strategies, expectations, procedures and actions required under such emergency conditions. The SWIFT SunGuide Center operations staff training is specifically geared towards achieving an understanding of the expectations of the staff when a disaster is declared. The Disaster Recovery Plan training consists of the following type of activities: o Initial Operator Training o Periodic Testing o Quarterly Plan Review with Senior Management Initial Operator Training The SWIFT SunGuide Center operations staff will be exposed to the disaster recovery plan concepts and procedures during initial operator training. They should be familiar with the location of the plan, the contact lists, and the reporting hierarchy. The Disaster Recovery Plan concepts and procedures will be reviewed with the SWIFT SunGuide Center operations staff during the first staff meeting of every year Periodic Testing Periodically, it is recommended that disaster recovery plan be tested for evaluation purposes. It will also ensure the precise documentation of all recovery activities required in the event of a disaster declaration. These tests may be performed anytime throughout the year, but are suggested to occur approximately every 18 months. To ensure continuous operability, it is also suggested that this scheduled testing should not involve the entire SWIFT SunGuide Center ITS system, but only parts of the overall system. This review and rehearsal process will ensure the following success factors: Telvent Farradyne Page 203 Revised: 6/2/08

213 o Keeping the plan up to date o Proper documentation o Keeping current with the ongoing institutional discussions about crisis management and disaster recovery planning Quarterly Plan Review with Senior Management SWIFT SunGuide Center management will meet quarterly to review existing SWIFT SunGuide Center and ITS conditions that may affect the disaster recovery plan. During the quarterly meeting, changes, additions, and modifications to the plan will be made as a result of practical experience. Additionally, operational procedural changes will also be identified. These quarterly meeting should be scheduled and documented by the disaster recovery plan designee. Telvent Farradyne Page 204 Revised: 6/2/08

214 29 Hurricane and Severe Weather Plan 29.1 Hurricane Categories Hurricanes are categorized using the Saffir/Simpson Hurricane Scale and are judged on wind speed and effects and surf surge. Table 1 lists the different categories and other pertinent information. Table 1 - Saffir/Simpson Hurricane Scale SAFFIR/SIMPSON HURRICANE SCALE Category Wind Velocity Surge Damage Potential mph 4-5 ft No real damage to building structures. Damage primarily to unanchored mobile homes, shrubbery, and trees. Also, some coastal flooding and minor pier damage mph 6-8 ft Some roofing material, door, and window damage. Considerable damage to vegetation, mobile homes, etc. Flooding damages piers and small craft in unprotected moorings may break their moorings mph 9-12 ft Some structural damage to small residences and utility buildings, with a minor amount of curtainwall failures. Mobile homes are destroyed. Flooding near the coast destroys smaller structures with larger structures damaged by floating debris. Terrain may be flooded well inland mph ft More extensive curtainwall failures with some complete roof structure failure on small residences. Major erosion of beach areas. Terrain may be flooded well inland mph+ 18 ft + Complete roof failure on many residences and industrial buildings. Some complete building failures with small utility buildings blown over or away. Flooding causes major damage to lower floors of all structures near the shoreline. Massive evacuation of residential areas may be required Hurricane and Severe Weather Objectives The Hurricane and Severe Weather Plan has the following ITS related objectives: o Plan development o Road Ranger redundant communications o Relocation of Operations Staff o Develop emergency contracts o Train in-house staff to troubleshoot and make repairs to ITS field devices o Utilize vehicle counts and speed data for contra-flow activity and monitoring purposes if visual capabilities are not functional o Develop and maintain a spare parts inventory o Obtain and maintain a minimum number of generators to power critical ITS field devices Telvent Farradyne Page 205 Revised: 6/2/08

215 o Obtain access to an inventory of portable traffic control devices (HAR, DMS, etc.) prior to the emergency event. o Allow for backup communication means for external SWIFT SunGuide Center communication, such as satellite phones Plan Development The most recent version of the Hurricane and Severe Weather Plan is given in this document. This plan will be updated to reflect changes and additions to the procedures as periodic testing and real life events occur Road Ranger Redundant Communications During severe weather, there is a need for redundant communications with the Road Ranger vehicles. The primary method of communications is a private trunk radio system. The Road Ranger vehicles will continue to maintain the cellular telephone service as a backup communications means should the private trunk radio system become unavailable. The existing procedure for switching between systems should be utilized Relocation of Operations Staff The SWIFT SunGuide Center has existing relocation agreements with the other local FDOT traffic management centers. The SWIFT SunGuide Center operations staff may relocate to one of these alternate facilities during severe weather conditions. This will enable FDOT to continue to maintain operations and provide service to the public while ensuring the safety of the operations staff Develop Emergency Contracts The SWIFT SunGuide Center utilizes Transcore as the ITS field equipment maintenance contractor. The contract allows for emergency callout procedures to repair equipment under emergency conditions and during non-standard business hours Repair of ITS Field Devices The dispatch of field personnel to repair ITS field devices will continue normally during severe weather unless otherwise notified by the RTMC Operations Manager or RTMC Operations Supervisor. Several knowledgeable staff members may be considered for ITS field device repair training, but no official program is currently in place Utilize Vehicle Counts and Speed Data Vehicle count information and speed data will be utilized to monitor traffic conditions when a contra-flow plan is executed or the SWIFT SunGuide Center loses functionality of the CCTV camera system Spare Parts Inventory The SWIFT SunGuide Center has a maintenance agreement with Transcore that covers the repair of all critical subsystems and ITS field components. Telvent Farradyne Page 206 Revised: 6/2/08

216 The RTMC IT Manager and RTMC IT Field Technician manage the spare parts inventory and are trained to make critical repairs, when necessary. The inventory of deployed equipment is tracked in the FMT-ITS system Generators for Field Equipment The SWIFT SunGuide Center will develop a list of critical ITS field devices that would need to operate during a major disruption of the electrical power grid. The critical ITS field devices consist of DMS signs and CCTV cameras. The critical ITS field device locations will be based on the existing major diversion and evacuation routes. A list of the critical field devices is given below. o DMS # o DMS # o CCTV # o CCTV # Portable Traffic Control Devices FDOT District 1 utilizes asset maintenance contractors through the FDOT Maintenance Department to cover state roadways when they are in need of portable traffic control devices. These contractors will be notified by the SWIFT SunGuide operations staff whenever this type of equipment is needed Backup Communications for External Contacts The SWIFT SunGuide Center operations staff requires a backup communication system to coordinate field activities with the damage assessment teams that are deployed after the severe weather event ends. In the future, it is possible that the SWIFT SunGuide Center may utilize satellite telephones or a backup radio system to allow for communications with the damage assessment teams, local agencies, FDOT Departments, Road Rangers, and other mobile vehicles Preparation The following actions have been identified as part of the Hurricane and Severe Weather Plan SWIFT SunGuide Facility The Hurricane and Severe Weather Plan identifies several responsibilities related to SWIFT SunGuide Center operations. Many of these responsibilities are also addressed in the SWIFT SunGuide Center Disaster Recovery Plan. The SWIFT SunGuide Center is shared with FHP and MCCO. FDOT is primarily responsible for the maintenance and operation of the building. FDOT is expected to prepare the building and related systems, although FHP and MCCO have an obligation to prepare and monitor certain emergency preparedness procedures. It should be noted, that the SWIFT SunGuide Center is not a hardened facility and could sustain damage during major storms. The center will be staffed until the winds reach a sustained wind velocity of 45 miles per hour. When the wind speed reaches this condition, the operators on duty shall be dismissed from the facility or asked to go to an alternate facility. Operations personnel that decide to stay in the SWIFT SunGuide Center will do so at their own risk. Telvent Farradyne Page 207 Revised: 6/2/08

217 Operations Staffing The SWIFT SunGuide Center will retain normal staffing levels before the hurricane or severe weather event. This includes a minimum of two operators and one shift supervisor. Some events may require additional staffing, however. This determination will be made by the FDOT RTMC Contract Manager and the RTMC Operations Manager. During periods of severe weather conditions, the occurrence of incidents may increase to a level that is difficult to manage. In this case, additional staff may also be required. Shifts may be altered to two twelve-hour shifts per day at the discretion of the RTMC Operations Manager or RTMC Operations Supervisor. These types of shifts are sometimes referred to as Alpha Bravo shifts. Alpha Bravo shifts require less staff, gas consumption, and overall travel time. This allows for the operations staff to prepare personally for the hurricane or severe weather event. These Alpha Bravo shifts may extend for days or weeks after the hurricane or severe weather event Road Ranger Program The SWIFT SunGuide Center will continue to dispatch and coordinate the Road Ranger vehicles as long as the Road Rangers remain operational. FDOT and the Road Ranger contractors will make the determination to reduce or suspend Road Ranger operations because of sustained high winds or other events. All decisions concerning the Road Ranger program will be communicated directly to the SWIFT SunGuide Center operations staff Emergency Operations Centers The local and county emergency operations centers normally operate in a modified integrated Incident Command System / Emergency Support Function (ICS / ESF) organizational structure. FDOT s role in the use and coordination of local resources is tied to two of the 17 ESFs: ESF #1 Transportation and ESF #3 Public Works. The purpose of ESF #1 is to coordinate all emergency transportation resources for the response to and recovery from any disaster in their coverage area. ESF #1 is primarily involved in transporting vulnerable populations to safer locations, and transporting recovery related resources into impacted areas in their coverage area. By policy, all transportation service will be suspended when sustained winds exceed 40 mph or greater as reported by the National Weather Service. The purpose of ESF #3 is to define how the public infrastructure of the EOC coverage area will be restored during and following a disaster in order to save lives and property. Policies of ESF #3 include: o Prioritizing impacted areas based on impact assessment data o Coordinating emergency debris removal on essential transportation routes o Coordinating debris removal and disposal from public property o Prioritizing and implementing temporary emergency structural repairs at vital public facilities, county roads, bridges and drainage systems. o Coordinating road closures o Establishing staging areas and logistical support bases for requested mutual aid resources in coordination with all first response agencies. The EOC activation levels are given below. Level 3 Monitoring (normal) Level 2 Partial activation Level 1 Full activation Telvent Farradyne Page 208 Revised: 6/2/08

218 FDOT Maintenance Upon activation of the EOC, FDOT sends two teams of two individuals to the EOC for the duration of the emergency. These teams work alternate 12-hour shifts. FDOT also has 4-person 24-hour staffing at all the local maintenance facilities. After landfall, FDOT mobilizes six 2-person teams for damage assessment and recovery. FDOT Maintenance s pre-hurricane and pre-severe weather event activities include the lockdown of all bascule bridges when wind speeds reach 40 mph. This determination is made in conjunction with the local emergency operations centers and the Coast Guard. FDOT Maintenance may contact or visit the SWIFT SunGuide Center operations staff to inquire about specific CCTV camera views of the state roadways before and after the hurricane or severe weather event ITS Field Device Preparation The installed ITS field devices will remain in an operational state prior to the hurricane or severe weather event. It will be the responsibility of the RTMC ITS Maintenance Contractor, Transcore, to fill the fuel tanks on the generators whenever the previously identified critical ITS field devices have generators installed. When conduit tests are performed during the non-storm season, the fuel levels of the tanks should be used so they are close to empty Severe Weather Supplies The Swift SunGuide Center will develop a severe weather supplies list every year and procure the approved inventory. The RTMC Operations Manager is responsible for taking inventory and ensuring the correct level of supplies is present. If the supplies are used for a severe weather event, the RTMC Operations Manager will take inventory and facilitate the procurement of new supplies Severe Weather Radio The SWIFT SunGuide Center may utilize a severe weather radio in the future. The RTMC Operations Manager and the RTMC Operations Supervisor will continuously monitor weather reports before and during hurricanes and severe weather events SWIFT SunGuide Center Generator The SWIFT SunGuide Center is equipped with a building generator to supply electrical power during commercial power interrupts. For specific generator procedures, please refer to the Power Failure and Electrical Generator Failure sections of this document SWIFT SunGuide Center Facility Recovery This section describes the events that will occur after the hurricane or severe weather event has passed and it is safe to resume operational status. Immediately after the hurricane or severe weather event is no longer active in the area, the operations staff members that are scheduled for duty will meet at the SWIFT SunGuide Center. The passing of the event will be determined when the national hurricane center declares the Telvent Farradyne Page 209 Revised: 6/2/08

219 storm has passed or the sustained winds decrease to 20 miles per hour or less at the SWIFT SunGuide Center and the residency of the SWIFT SunGuide Center staff. Staff members that are not scheduled to work when the event is no longer active should contact the RTMC Operations Manager, RTMC Operations Supervisor, and the RTMC Shift Supervisor on duty, respectively, to report their circumstances. After the SWIFT SunGuide Center staff meet at the job location, the RTMC Operations Manager or the RTMC Operations Supervisor will resume normal operations. If the SWIFT SunGuide Center has not already relocated operations and is not in a condition to support a safe work environment, the operations staff will be relocated to one of the predesignated contingency sites. This location will be determined by FDOT or the RTMC Operations Manager. If any of the SWIFT SunGuide Center subsystems are not functional, the Disaster Recovery Plan shall be placed into effect Emergency Communication Teams If the SWIFT SunGuide Center does decide to obtain a backup radio system to communicate with the damage assessment teams, Road Rangers, FDOT Departments, etc., then the FDOT RTMC Contract Manager will assemble two Emergency Communication Teams that will be responsible for deploying the backup radio system in the field. If a backup radio system is utilized, one team will install the emergency radio system antenna at the SWIFT SunGuide Center and test the system. The other team will be dispatched to install the emergency radio system antenna in the field and test the system. The Emergency Communication Teams will report back to the SWIFT SunGuide Center once the system is operational Damage Assessment Teams Once the SWIFT SunGuide Center resumes operations, the FDOT RTMC Contract Manager and the RTMC Operations Manager will form three damage assessment teams. These teams will go to the field to assess the damage to the ITS field equipment, power lines, and the state roadway network. Internally, the cellular telephone service, landline communications, personnel cell phones on alternate carriers, text messaging capabilities, and internet connections will be assessed. The SWIFT SunGuide Center operations staff will utilize the CCTV camera system to survey the state roadways and ITS devices, if possible. The operations staff will also open trouble tickets in the Field Equipment and Internal Systems Tracking Microsoft Access database. The Damage Assessment Teams will utilize cellular telephones to communicate with the SWIFT SunGuide Center operations staff. If an emergency radio system is installed or satellite telephones are purchased, communications should be performed with these mediums ITS Field Device and Internal Systems Recovery Once the damage assessment teams complete their assessment, the FDOT RTMC Contract Manager and the RTMC Operations Manager will review the open trouble tickets in conjunction with the ITS Maintenance Contractor and RTMC IT Manager to determine a repair priority list based on operational needs, available spare parts, and estimated repair time. Telvent Farradyne Page 210 Revised: 6/2/08

220 29.5 Hurricane and Severe Weather Flowchart In order to facilitate the hurricane preparations and recovery, a flowchart has been developed. Telvent Farradyne Page 211 Revised: 6/2/08

221 30 Hurricane and Severe Weather Schedule The Plan is broken down into a series of phases and the corresponding steps to be taken up to, during, and immediately following a hurricane or similar conditions. The schedule establishes a general guideline for protective actions before, during and after a Hurricane or similar event. The schedule may be modified to meet hazard constraints, response times, and other conditions that may occur during the weather event. Phase A includes an annual review. It also includes those steps to be performed and items to be maintained and checked as a general preparedness condition during normal times. Phase B is the pre-storm alert stage when a storm is within 72 hours of possible landfall. The SWIFT SunGuide Center will, initiate the alert at the direction of the FDOT RTMC Contract Manager or RTMC Operations Manager. Phase C refers to those pre-storm activities performed during a Hurricane Watch. A hurricane watch is issued for a specified coastal area for which a hurricane or a hurricane-related hazard is a possible threat within 36 hours. Phase D refers to those pre-storm activities performed during a Hurricane Warning. A hurricane warning is issued when a hurricane with sustained winds of 74 miles per hour or higher is expected in a specified coastal area in 24 hours or less. Phase E refers to those post-landfall activities to be performed immediately following a hurricane. It is assumed that all personnel are either activated from or remain within the SWIFT SunGuide Center for the duration of the storm Phase A - Before Hurricane SWIFT SunGuide Center Stock supplies: Drinking water 10 gallons Plastic sheeting to cover equipment racks, video wall, workstations Canned food for three days Flashlights with fresh batteries Portable file boxes to allow relocation of important files (Employees will provide their own blankets, sleeping bags, etc.) Verify contact lists contact lists are periodically verified. If list has not been updated in the last 60 days, verify contact information. Participate in Hurricane coordination meetings and drills Field Device Maintenance Contractor Secure equipment during normal maintenance, ensure all equipment is secure and protected. Telvent Farradyne Page 212 Revised: 6/2/08

222 30.2 Phase B - Hurricane Alert SWIFT SunGuide Center Initiate Hurricane Alert. Check supplies replace any missing items. Test all communications equipment. Verify that personnel are available and ready. Employees should secure home and family prior to reporting for work. Verify that telephone lists are correct. Cancel any scheduled uses of the SWIFT SunGuide Center conference room Field Device Maintenance Contractor Confirm all equipment is secure. Verify that personnel are available and ready. Employees should secure home and family prior to reporting for work Phase C - Hurricane Watch SWIFT SunGuide Center Organize the release of personnel for evacuation of families in the projected hurricane path. Schedule personnel to return to duty as family and home are secured. Recheck emergency supplies. Prepare for securing building and equipment Prepare for remote operation Field Device Maintenance Contractor No action required. Remain operational Phase D - Hurricane Warning SWIFT SunGuide Center Prepare the SWIFT SunGuide Center for the storm (exterior doors, generator). Charge cellular phone batteries. Plug chargers into UPS circuit receptacle to maintain charge. Set refrigerator at coldest setting in anticipation of power outages SWIFT SunGuide Center In the Projected Path of Hurricane Make determination if the SWIFT SunGuide Center is to be relocated to other facility. (If no relocation, refer to ) Prior to relocation to alternate facility: Cover equipment racks, back side of video wall, work stations, printers, other electronic equipment Secure and/or relocate records as necessary Turn off electricity Turn off water Telvent Farradyne Page 213 Revised: 6/2/08

223 If ordered to evacuate, do so immediately. Do not jeopardize your safety by remaining in an evacuation zone SWIFT SunGuide Center Outside the Projected Path of Hurricane SWIFT SunGuide Center will remain operational. If the determination is made to close the ITMS at the end of a shift: Cover equipment racks, back side of video wall, work stations, printers, other electronic equipment Secure and/or relocate records as necessary Turn off electricity Turn off water Field Device Maintenance Contractor The Field Device Maintenance Contractor will perform the activities listed except that all activities will cease once Tropical Storm force winds (sustained winds over 40 mph) are encountered or six (6) hours before the forecast arrival of the storm, whichever comes first, so that contractor personnel can safely return to their homes Phase E - After Hurricane SWIFT SunGuide Center Assess damage to the SWIFT SunGuide Center Assess damage to the field devices and internal systems Re-establish communications Restore operation in accordance with SWIFT SunGuide Center SOG and SWIFT SunGuide Center SOP Record and maintain logs of equipment damage and restoration Coordinate with the local emergency operations centers, FHP, and other local agencies to aid in the safe return of the population and in hurricane relief. Use DMS messages to assist in this regard (approved non-standard messages may be used) Field Device Maintenance Contractor Rapid restoration of the field communications devices is essential for recovery and the safe, orderly return of the population. The SWIFT SunGuide Center operations staff will coordinate with the local emergency operations centers and work with the Field Device Maintenance Contractor to prioritize the restoration of the field devices to best serve the populace. Telvent Farradyne Page 214 Revised: 6/2/08

224 31 SWIFT SunGuide Disaster Recovery Plan Specific Disaster Procedures 31.1 Building Threats and Evacuations The primary evacuation rally point is outside the north side of the building 200 feet from the back entrance at the oversized parking spaces. The secondary rally point is in the front of the building at least 200 feet south of the entrance at the front lobby. Supervisors are responsible for the accountability of their staff. Normally, the senior staff member on duty will: o Assess the situation o Order an evacuation, when necessary o Contact 911 o Take essential equipment when leaving the SWIFT SunGuide Center, if possible and if it can be done safely. Essential equipment includes the SWIFT SunGuide Center cellular telephones, cell phone chargers, and the storage bin that contains the backup CD for blank forms, writing utensils, toolkit, a copy of the SWIFT SunGuide Center SOP, a copy of the SWIFT SunGuide Center SOG, and the SWIFT SunGuide Center Disaster Recovery Plan. o If time allows, take the fire department scanner, weather radio, etc. o Take accountability of the staff at the rally-point o Coordinate with the senior FHP staff member present o Report the incident and actions taken to the RTMC Operations Manager and the FDOT RTMC Manager o Relocate the staff to the closest, safe relocation point determined by the RTMC Operations Manager and the FDOT RTMC Manager. The relocation points will provide the RTMC operations staff with remote operation of the SunGuide System. These relocation points are: Sarasota-Manatee Satellite TMC (will not be operational for interim operations until ~2012), the Lee County EOC (this facility has not been built and we do not have an ETA), FDOT District 7 TMC (connection not anticipated until ~2012), FDOT District 4 Palm Beach ITMS, FDOT District 4 Broward TMC, and FDOT District 6 TMC, respectively. o The RTMC Operations Manager will coordinate all actions with the FDOT RTMC Manager and will be responsible for contacting the RTMC Contract Manager and reporting all actions taken Fire Drill Fire Drills will be scheduled and conducted in accordance with the State of Florida policy and the procedures regarding the requirement for these drills. The staff should exit the building using the closest fire exit and move quickly to the safety rally point. Employees should only take personal items related to immediate safety, such as jackets, when leaving the building Fire The senior staff member on duty will be responsible to monitor the fire condition and order the building evacuation to protect the staff from harm. The steps listed in the Building Threats and Evacuations section of this document should be followed. The Fire Emergency Evacuation Plan for the entire FDOT District 1 SWIFT SunGuide Center is given below. Telvent Farradyne Page 215 Revised: 6/2/08

225 DISTRICT ONE SWIFT SUNGUIDE CENTER FIRE EMERGENCY EVACUATION PLAN PURPOSE: To provide all employees with a procedure to accomplish a safe evacuation of the building in case of fire. Emergency evacuation signs are posted throughout the building. Employees should familiarize themselves with the escape assignments for their area. AUTHORITY: Florida Department of Transportation Loss Prevention Manual and Occupational Safety and Health for General Industry 29 CFR Part SCOPE: District One Headquarters of the Florida Department of Transportation. DEFINITIONS: Searcher The Searcher will travel through their assigned area directing the occupants to the nearest and safest exit. He/she will then inspect their area to make certain that everyone has left the area. He/she will report all clear to his/her Captain upon completion of his/her search. Captain The Captain will be placed in a location where he/she can direct the employees to the nearest and safest exit. After the Searchers have reported all clear, he/she will report to the Major that the building and hallway has been evacuated and all Exit Doors are closed. The Major will be located east (front) of the Main District Office Building. When the building has been evacuated, the switchboard operator and the Major will go outside the building to await the Fire Department s arrival. The Major will direct them to the fire area. The Major will instruct the employees where to congregate (see Attachment #1) until the danger has been brought under control. He/she will also communicate to the employee s further instructions. PROCEDURE: Duties and Responsibilities: Team Captains should ensure that Area Searchers are aware of their duties. Additionally, Team Captains, when arriving at the assigned assembly area, should ensure that all employees are accounted for within their search area. MAJOR: Dennis Hall Primary Carlos Bonilla Primary Larry Lyon Alternate Team Captains are: John Scarpellino Jr. RTMC Operations Supervisor Name Name Telvent Farradyne Page 216 Revised: 6/2/08

226 31.4 Power Failure If a power failure occurs, the system has a generator for emergency power. This generator maintains critical equipment and keeps the RTMC in operation. Under direction of the supervisor, the user shall turn off any non-critical equipment attached to the critical circuit by using the individual on/off switches located on each piece of equipment. This will be done to conserve power and reduce the load on the generator when non-critical equipment is mistakenly on the critical circuit. An uninterruptible power supply is also installed to maintain power to the critical circuit for about 60 minutes, which should be enough time to get the generator started in case it does not automatically switch on. Any critical equipment affected by the loss of power before the generator is started or in the event of generator failure shall be shut down using the shut down procedure listed in the Electrical Generator Failure section of this document for that piece of equipment. When power is restored, the equipment shall be restarted using the normal start-up procedure Bomb Threats Bomb Threats or similar threats to the staff and/or facility will be handled utilizing the existing FDOT and FHP procedures. The senior staff member on duty shall take care of the staff and take action necessary for their protection using sound, logical judgment. Coordination with the FHP dispatch personnel at the RTMC should occur as quickly as possible to handle any emergencies. The steps listed in the Building Threats and Evacuations section of this document should be followed once the evacuation proves necessary. In addition, the Lee County EOC should be alerted of the situation Severe Weather The RTMC will usually remain operational during severe weather. The electrical generator will provide emergency power to the center, if necessary, and maintain internal systems. Therefore, staff members are expected to report to work for all assigned shifts until otherwise notified by a supervisor and should plan accordingly. The complete evacuation of the RTMC may be necessary during a hurricane, tornado, or similar potential disaster. For evacuation procedures, please refer to the Building Threats and Evacuations section of this document. Supervisors should use sound judgment when making the decision to evacuate. The senior staff member on duty will report existing conditions and coordinate the evacuation with the RTMC Operations Supervisor or the RTMC Operations Manager Other Hazardous Conditions The possible combinations of other conditions are too numerous to detail here. In general, the senior staff member in charge will make a determination, in coordination with FHP if possible, if the building should be evacuated due to unusual conditions such as a disgruntled employee returning with a weapon, etc Remote Operation of the SWIFT SunGuide Center Remote operation is defined as the utilization of the SunGuide Software to monitor and control system devices from a location other than the SWIFT SunGuide Center. The RTMC Operations Manager, the RTMC Operations Supervisor, the FDOT RTMC Manager, and the RTMC IT Manager, will be supplied laptop computers with the SunGuide software installed that will allow Telvent Farradyne Page 217 Revised: 6/2/08

227 for remote system operation. The RTMC Operations Manager will be the primary remote user and the RTMC Operations Supervisor, etc. will serve as backups. The primary means of access to SunGuide will be via Virtual Private Network Connection. Remote access will be utilized by an Internet connection. Secondary access will be by connection to the FDOT RTMC server via standard telephone connection. It should be noted that the secondary access method is slower than the primary access from the SWIFT SunGuide Center. Therefore, it is possible that the response time will be greater for such things as DMS messaging. Once this connection is set up, designated RTMC operations staff will have the capability to operate the system and provide incident response remotely from the temporary location. For long term relocations, RTMC management may designate relocation points with an active SunGuide system. These relocation points are currently: the FDOT District 7 TMC, the FDOT District 4 Palm Beach ITMS, the FDOT District 4 Broward TMC, and the FDOT District 6 TMC. Telvent Farradyne Page 218 Revised: 6/2/08

228 32 Homeland Security Policy Homeland security procedures will include efforts to coordinate with the Department of Homeland Security to enhance and reinforce the efforts of Homeland Security. The SWIFT SunGuide Center will work closely with FHP, FDOT, and all other agencies to manage any incidents related to homeland security. Incidents that appear to have homeland security importance will be brought to the attention of the RTMC Operations Manager and/or the FDOT RTMC Manager. The Emergency Contact Information section of this document will be used to acquire appropriate contact information. The RTMC Operations Manager will then direct the RTMC Shift Supervisor on duty regarding the individuals who should be contacted regarding the incident. The SWIFT SunGuide Center CCTV cameras can largely contribute to the detection and monitoring of homeland security related incidents. Any confirmed or suspicious activity should be immediately relayed to FHP dispatch and the RTMC Operations Manager. Homeland Security will be contacted if all parties agree that this is the proper course of action. Video feeds may be provided directly to the Department of Homeland Security, if possible and warranted. It may also prove beneficial for a Department of Homeland Security representative to be stationed in the SWIFT SunGuide Center control room during an emergency. Response to incidents of this type may require overtime and/or the implementation of longer shifts to reduce the number of times the staff has to come to work per week. The operations staff will be contacted and a schedule will be developed to cover the period of the incident. Normally, the SWIFT SunGuide Center will utilize the 12 hours on/12 hours off alpha/bravo style schedule for immediate response. Long-term response may require an alternate schedule to prevent staff burnout. The RTMC Operations Supervisor and RTMC Operations Manager are responsible for the development and implementation of this schedule and will ensure adequate staff is on-duty to cover the period of the incident. All schedule changes must be approved by the FDOT RTMC Manager in writing before implementation. Incidents that could be considered homeland security related include, but are not limited to, the following: o Airplane crashes/hijacking/acts of terrorism o Train derailment (passenger and freight) or hijacking o Barge or container ship crashes o Passenger bus crashes with multiple injuries o Vehicle crashes into buildings (governmental offices) or structures (bridges) o HAZMAT incidents o Large-scale power outages due to disrupted gas or electric service Telvent Farradyne Page 219 Revised: 6/2/08

229 33 Weapons of Mass Destruction Threat and Incident Response A weapon of mass destruction (WMD) includes biological, chemical, nuclear, or explosive materials or devices and any combination thereof. The SWIFT SunGuide Center operations staff should take the following steps for possible or confirmed incidents involving weapons of mass destruction. o Contact a supervisor or the on-call supervisor immediately. o Contact FHP dispatch, bomb squad, fire department, and DEP. o Call to alert the FBI field office at , open 24 hrs. o Call to alert the Local Emergency Operations Centers o Call to alert local county Health Department o Coordinate all activities through the FBI. o Coordinate DMS activation, if appropriate, with the on-call supervisor or the RTMC Operations Manager. Information for field personnel: o Approach upwind of the hazard area. o Avoid being contaminated at the scene or through a victim who has been exposed to the hazard. o Do not move suspicious packages or containers. o Avoid using cell phones, etc., within 300 ft. of a suspect device. Telvent Farradyne Page 220 Revised: 6/2/08

230 34 Continuity of Operations Plan The Continuity of Operations Plan (COOP) has been developed to document the guidelines, support, and resources needed should a disaster impact the Florida Department of Transportation. The plan will be activated when an emergency beyond the scope of standard operating procedures occurs. It is designed to reduce confusion created during a disaster, and provides a framework for recovery and restoration of critical systems, voice/data communications, business processes, and facilities. Telvent Farradyne Page 221 Revised: 6/2/08

231 35 Other Emergency Procedures Telvent Farradyne Page 222 Revised: 6/2/08

232 36 Regional Civilian Evacuation and Contra-Flow Plans The southwest Florida contra-flow evacuation plan exists, but is out of date. FHP and FDOT are currently working on a newer revised version and will be further referenced in this document once it is created and approved. Telvent Farradyne Page 223 Revised: 6/2/08

233 37 Diversion Routes (Future) It is a goal of the SWIFT SunGuide Center to provide accurate and timely information to the traveling public in real-time. Since this may require the utilization of diversion routes, the SWIFT SunGuide Center operations staff must be familiar with the highway system, arterial roadways, and local diversion routes Full Road Closures on I Brush Fires on I-75 Brush fires can occur anywhere in Florida, but because brush fires occur frequently on I-75 on Alligator Alley, specific procedures have been adopted by SEFRTOC for events in this location. The content and structure of the following procedure was taken from the existing SEFRTOC document but some of the wording has been changed to remain consistent with established procedure. I-75 Brush Fire Procedure for Alligator Alley: In Florida, the wildfire season lasts from December until June with May being the peak of the season. There are three sides of the fire behavior triangle: fuels, weather, and topography. Of the three, weather is the least predictable and sudden changes can result in danger to life and property as well as unexpected road closures. Wildfire events along the Alligator Alley portion of I-75 in Broward and Collier Counties account for most of the fire related road closures in south Florida. Disseminating useful information to motorists on a regional basis is a critical part of responding to these closures. The following procedures have been developed to facilitate an efficient regional response to these events. Detection: Upon notification of impending road closures on I-75 south at US-27, SR-29, and Government Road/Snake Road, the SWIFT SunGuide operations staff is responsible for entering all information into the SunGuide software, locating the incident on CCTV if possible, communicating with FHP dispatch to obtain verification, dispatching a Road Ranger to obtain verification, communicating with the FDOT District 4 Broward TMC to obtain verification for closures in Broward County, and coordinating incident details with the Asset Management Contractor and FHP troopers on scene. Verification: Once the location of the closure is verified by one of the aforementioned sources, the SWIFT SunGuide operations staff must make the event active in the SunGuide incident report, generate a SunGuide response plan to post messages on all DMS, and send incident notifications to the Level 3 and Newsworthy contact groups. Notification: As per current policy, center-to-center communication will be initiated immediately upon verification of the road closure. The SWIFT SunGuide operations staff will contact: 511 to request a floodgate message (see the Monitoring / Updates section below for more information) FHP Dispatch Telvent Farradyne Page 224 Revised: 6/2/08

234 511: MCCO FDOT District 4 Broward TMC FDOT District 4 Palm Beach ITMS FDOT District 6 TMC FDOT District 7 TMC Florida s Turnpike TMC The local and statewide 511 agencies will create a global message on their system, called a Floodgate Message, that will be the first event heard by all motorists. Examples include: I-75 Closed at US-27: I-75 is closed at US-27 due to a severe brush fire. The following are possible alternate routes around the closure. For I-75 Eastbound traffic: Take I-75 east to US-27 north, take SR-80 east to the Florida s Turnpike or I-95. I-75 West US-27 north to South Bay, to SR 80 West, back to I-75 in Fort Myers I-75 Closed at US-29: I-75 is closed at US-29 due to a sever brush fire. The following are possible alternate roués around the closure For I-75 Eastbound traffic: Take I-75 east to SR-29 north, take SR-80 east to the Florida s Turnpike or I-95. For I-75 Eastbound traffic: Take I-75 east to SR-29 south, take US-41 east to the Florida s Turnpike or I-95. The 511 agencies will notify the local traffic management centers when a floodgate message is posted so the DMS message content can direct motorists to call 511 for more specific information. Monitoring / Updates: Upon notification/verification of 511 floodgate messaging, the SWIFT SunGuide operations staff will notify the following agencies. FHP Dispatch MCCO FDOT District 4 Broward TMC FDOT District 4 Palm Beach ITMS FDOT District 6 TMC FDOT District 7 TMC Florida s Turnpike TMC Please refer to the FDOT District 1 SWIFT SunGuide DMS SOP document for specific DMS message content. Inquiries: The SWIFT SunGuide operations staff may address inquires from the public by providing the same alternate route suggestions as the 511 floodgate message Full Road Closures on Roadways Other than I-75 Telvent Farradyne Page 225 Revised: 6/2/08

235 37.4 Diversion Route Scenarios Diversion routes are typically only implemented with a full closure of I-75 or I-275 in one or both directions. Local diversions are implemented at the first upstream exit before the incident location. Regional diversions are established at upstream I-75 interchanges that have access to other state road and highway interchanges. Diversion route plans normally detail the specific route that motorists need to take to get from an exit before the road closure to an entrance ramp downstream from the road closure. Traffic signal timing changes, local agency manpower, equipment necessary to guide motorists through the suggested diversion route, maps of the area and infrastructure, and agency contact lists are normally an essential part of complete diversion route plans. Three different sets of diversion plans are currently in existence or in the planning phase. FHP has diversion plans that were created in the 1990 s and are considerably out of date. Several new roadways have been built since these plans were drafted, so they are not suggested for use by FHP. FHP plans to update these diversion routes in the near future and will provide the SWIFT SunGuide Center a copy when completed. The Lee County Traffic Engineering Department has also created diversion plans for I-75 closures in Lee County. These plans are slightly out of date but are more useable. An example of their diversion route plan is given on the following page. FDOT has begun the process to develop diversion route plans for I-75 in District 1. A technical memo for diversion route map needs was drafted by a local vendor that assembled information from existing diversion and evacuation routes from the Collier-Lee TIM Team members, Charlotte-Sarasota-Manatee TIM Team members, county emergency management agencies, published hurricane guides, all-hazard guides, and other sources. More work and agency coordination is required to construct actual diversion route plans from this preliminary document. Notification of several agencies will be made in the case of the establishment or cancellation of a diversion route: o FHP dispatch o Traffic Management Centers in other FDOT Districts, when applicable o The local traffic signal agencies o FDOT District 1 PIO o Local Fire Rescue o Local Police Departments Telvent Farradyne Page 226 Revised: 6/2/08

236 Telvent Farradyne Page 227 Revised: 6/2/08