FDOT ATMS Software Enhancement

Project Description: The FDOT ATMS Software Enhancement Project will coordinate changes/enhancements to the SunGuide Software that help improve the safety and efficiency of Florida's surface transportation system.

Project Status: Planned

Project Stakeholders:

• County City and Local Emergency Management Agencies
• County City and Local Traffic Engineering
• FDOT Data Archiving
• FDOT Districts
• FDOT State Traffic Engineering and Operations Office
• Floridas Turnpike Enterprise
• Private Sector ISPs

Project Service Packages:

• TM02: Vehicle-Based Traffic Surveillance (Wide Area Probe Surveillance)
• TM07: Regional Traffic Management (FDOT ATMS Integration)
• TM09: Integrated Decision Support and Demand Management (Integrated Corridor Management)
• TI01: Broadcast Traveler Information (FL 511 - FDOT Operations)
• PS12: Disaster Response and Recovery (County Emergency Operations Center)
• PS13: Evacuation and Reentry Management (County Emergency Operations Center)
• DM01: ITS Data Warehouse (FDOT SunGuide Archiving)

Project Information Flows:

Information Flow	Source Element	Destination Element	Status
archive status	SunGuide Data Archive	FDOT District Transportation Management Centers using SunGuide	Planned
archived data products	SunGuide Data Archive	FDOT District Transportation Management Centers using SunGuide	Planned
current infrastructure restrictions	FDOT District Construction and Maintenance	FDOT District Transportation Management Centers using SunGuide	Planned
data query publication	FL511	FDOT District Transportation Management Centers using SunGuide	Planned
device control request	County City and Local Traffic Control Systems	FDOT District Transportation Management Centers using SunGuide	Planned
device data	County City and Local Traffic Control Systems	FDOT District Transportation Management Centers using SunGuide	Planned
device status	County City and Local Traffic Control Systems	FDOT District Transportation Management Centers using SunGuide	Planned
emergency plan coordination	County City and Local EOCs/Warning Points	FDOT District Transportation Management Centers using SunGuide	Planned
emergency traffic control request	County City and Local EOCs/Warning Points	FDOT District Transportation Management Centers using SunGuide	Planned
equipment maintenance status	FDOT District Construction and Maintenance	FDOT District Transportation Management Centers using SunGuide	Planned
evacuation information	County City and Local EOCs/Warning Points	FDOT District Transportation Management Centers using SunGuide	Planned
incident information	County City and Local EOCs/Warning Points	FDOT District Transportation Management Centers using SunGuide	Planned
incident information	County City and Local Traffic Control Systems	FDOT District Transportation Management Centers using SunGuide	Planned
incident information	FDOT District Construction and Maintenance	FDOT District Transportation Management Centers using SunGuide	Planned
incident response status	County City and Local EOCs/Warning Points	FDOT District Transportation Management Centers using SunGuide	Planned
maint and constr resource response	FDOT District Construction and Maintenance	FDOT District Transportation Management Centers using SunGuide	Planned
maint and constr work plans	FDOT District Construction and Maintenance	FDOT District Transportation Management Centers using SunGuide	Planned
resource request	County City and Local EOCs/Warning Points	FDOT District Transportation Management Centers using SunGuide	Planned
road network conditions	County City and Local Traffic Control Systems	FDOT District Transportation Management Centers using SunGuide	Planned
road network conditions	Other FDOT District TMCs	FDOT District Transportation Management Centers using SunGuide	Planned
road network traffic situation data	Private Sector Traveler Info Services	FDOT District Transportation Management Centers using SunGuide	Planned
threat information	County City and Local EOCs/Warning Points	FDOT District Transportation Management Centers using SunGuide	Planned
traffic images	County City and Local Traffic Control Systems	FDOT District Transportation Management Centers using SunGuide	Planned
transportation system status	County City and Local EOCs/Warning Points	FDOT District Transportation Management Centers using SunGuide	Planned

Project Functional Requirements (Element - Functional Object):

• County City and Local EOCs/Warning Points - Emergency Early Warning System
• 01: The center shall monitor information from Alerting and Advisory Systems such as the Information Sharing and Analysis Centers (ISACs), the National Infrastructure Protection Center (NIPC), the Homeland Security Advisory System (HSAS), etc. The information may include assessments (general incident and vulnerability awareness information), advisories (identification of threats or recommendations to increase preparedness levels), or alerts (information on imminent or in-progress emergencies).
• 02: The center shall receive incident information from other transportation management centers to support the early warning system.
• 03: The center shall support the entry of alert and advisory information directly from the emergency system operator.
• 04: The center shall receive potential incident information from social media sources to support the early warning system.
• 05: The center shall provide the capability to correlate alerts and advisories, incident information, and security sensor and surveillance data.
• 06: The center shall broadcast wide-area alerts and advisories to traffic management centers for emergency situations such as severe weather events, civil emergencies, child abduction (AMBER alert system), military activities, and other situations that pose a threat to life and property.
• 07: The center shall broadcast wide-area alerts and advisories to transit management centers for emergency situations such as severe weather events, civil emergencies, child abduction (AMBER alert system), military activities, and other situations that pose a threat to life and property.
• 08: The center shall broadcast wide-area alerts and advisories to toll administration centers for emergency situations such as severe weather events, civil emergencies, child abduction (AMBER alert system), military activities, and other situations that pose a threat to life and property.
• 09: The center shall broadcast wide-area alerts and advisories to traveler information service providers for emergency situations such as severe weather events, civil emergencies, child abduction (AMBER alert system), military activities, and other situations that pose a threat to life and property.
• 10: The center shall broadcast wide-area alerts and advisories to maintenance centers for emergency situations such as severe weather events, civil emergencies, child abduction (AMBER alert system), military activities, and other situations that pose a threat to life and property.
• 11: The center shall broadcast wide-area alerts and advisories to other emergency management centers for emergency situations such as severe weather events, civil emergencies, child abduction (AMBER alert system), military activities, and other situations that pose a threat to life and property.
• 12: The center shall broadcast wide-area alerts and advisories to commercial vehicle administration centers and roadside check facilities for emergency situations such as severe weather events, civil emergencies, child abduction (AMBER alert system), military activities, and other situations that pose a threat to life and property.
• 13: The center shall process status information from each of the centers that have been sent the wide-area alert.
• 14: The center shall coordinate the broadcast of wide-area alerts and advisories with other emergency management centers.
• 15: The center shall present the alert and advisory information and the status of the actions taken in response to the alert by the other centers to the emergency system operator as received from other system inputs.


• County City and Local EOCs/Warning Points - Emergency Environmental Monitoring
• 01: The center shall collect current and forecast road and weather information from weather service providers (such as the National Weather Service and value-added sector specific meteorological services).
• 02: The center shall collect road network conditions data, including advisories, from traffic management and traveler information centers.
• 03: The center shall collect asset restrictions information from roadway maintenance operations.
• 04: The center shall assimilate current and forecast road conditions and surface weather information to support incident management.
• 05: The center shall provide the road and weather warning and advisories to the emergency responders.


• County City and Local EOCs/Warning Points - Emergency Evacuation Support
• 01: The center shall manage inter-agency coordination of evacuation operations, from initial planning through the evacuation process and reentry.
• 02: The center shall develop and exchange evacuation plans with allied agencies prior to the occurrence of a disaster.
• 03: The center shall provide an interface to the emergency system operator to enter evacuation plans and procedures and present the operator with other agencies’ plans.
• 04: The center shall coordinate evacuation destinations and shelter needs with shelter providers (e.g., the American Red Cross) in the region.
• 05: The center shall provide evacuation information to traffic, transit, maintenance and construction, rail operations, and other emergency management centers as needed.
• 07: The center shall request traffic management agencies to implement special traffic control strategies and to control evacuation traffic, including traffic on local streets and arterials as well as the major evacuation routes.
• 08: The center shall provide traveler information systems with evacuation guidance including basic information to assist potential evacuees in determining whether evacuation is necessary and when it is safe to return.
• 09: The center shall monitor the progress or status of the evacuation once it begins and exchange tactical plans, prepared during the incident, with allied agencies.
• 10: The center shall monitor the progress of the reentry process.
• 11: The center shall submit evacuation information to toll administration centers along with requests for changes in the toll services or fee collection during an evacuation.
• 12: The center shall retrieve information from public health systems to plan for and implement evacuations or in-place sheltering for biological, chemical, radiation, and other public health emergencies.
• 13: The center shall make use of population and housing data to plan for and implement evacuations or in-place sheltering for biological, chemical, radiation, and other public health emergencies.
• 14: The center shall maintain information on the population of an area in the event of an evacuation, including addresses, types of facility (residence, multi-family dwelling, commercial retail, commercial office, etc.), and special considerations (storage of flammable liquids, special needs residents.


• County City and Local EOCs/Warning Points - Emergency Incident Command
• 01: The center shall provide tactical decision support, resource coordination, and communications integration for first responders to support local management of an incident.
• 02: The center shall provide incident command communications with public safety, emergency management, transportation, and other allied response agency centers.
• 03: The center shall track and maintain resource information and action plans pertaining to the incident command.
• 04: The center shall share incident command information with other public safety agencies including resource deployment status, hazardous material information, rail incident information, evacuation advice as well as traffic, road, and weather conditions.
• 05: The center shall assess the status of responding emergency vehicles as part of an incident command.
• 06: The center shall provide other agencies real-time information on the current conditions at the incident scene.
• 07: The center shall collect modeling program outputs to support emergency dispatch and staging of personnel and equipment, e.g. predicted HAZMAT plumes or crash severity predictions.
• 10: The center shall collect on-scene reports to support emergency dispatch and staging of personnel and equipment.
• 11: The center shall provide situational awareness information to emergency responders about an incident, both en-route and while they are on-scene.
• 12: The center shall provide status of the current conditions at the incident scene to arriving responders.


• County City and Local EOCs/Warning Points - Emergency Response Management
• 01: The center shall provide strategic emergency response capabilities provided by an Emergency Operations Center for large-scale incidents and disasters.
• 03: The center shall provide the capability to implement response plans and track progress through the incident by exchanging incident information and response status with allied agencies.
• 04: The center shall develop, coordinate with other agencies, and store emergency response plans.
• 05: The center shall track the availability of resources and coordinate resource sharing with allied agency centers including traffic, maintenance, or other emergency centers.
• 06: The center shall allocate the appropriate emergency services, resources, and vehicle (s) to respond to incidents, and shall provide the capability to override the current allocation to suit the special needs of a current incident.
• 07: The center shall receive event scheduling information from Event Promoters.
• 08: The center shall support remote control of field equipment normally under control of the traffic management center including traffic signals, dynamic message signs, gates, and barriers.
• 09: The center shall provide the capability to remotely control and monitor CCTV systems normally operated by a traffic management center.
• 10: The center shall provide the capability to request transit resource availability from transit centers for use during disaster and evacuation operations.
• 11: The center shall assimilate the damage assessment of the transit, traffic, rail, maintenance, and other emergency center services and systems to create an overall transportation system status, and disseminate to each of these centers and the traveling public via traveler information providers.
• 12: The center shall provide information to the media concerning the status of an emergency response.
• 13: The center shall provide the capability for center personnel to provide inputs to the management of incidents, disasters and evacuations.
• 14: The center shall collect information about the status of the recovery efforts for the infrastructure during disasters.
• 15: The center shall provide the overall status of infrastructure recovery efforts to traveler information providers and media.
• 16: The center shall provide the capability to communicate information about emergency situations to local population through the Emergency Telecommunications System.
• 17: The center shall provide the capability to identify neighborhoods and businesses that should be informed of an emergency situation based on information collected about incidents including their severity, impacted locations, and recovery schedule.
• 18: The center shall retrieve information from public health systems to increase preparedness for, and implement a response to biological, chemical, radiation, and other public health emergencies.
• 19: The center shall manage coordinated inter-agency responses to incidents at an international border.
• 20: The center shall receive temporary facility restrictions that are imposed during maintenance and construction that may impact emergency response.
• 21: The center shall receive proposed maintenance and construction work plans, analyze the activity as a possible incident requiring emergency response, and provide work plan feedback to the sending center.


• County City and Local EOCs/Warning Points - Emergency Secure Area Sensor Management
• 01: The center shall remotely monitor and control security sensor data collected in secure areas including facilities (e.g. transit yards) and transportation infrastructure (e.g. bridges, tunnels, interchanges, roadway infrastructure, and transit railways or guideways). The types of security sensor data include environmental threat (e.g. chemical agent, toxic industrial chemical, biological, explosives, and radiological sensors), infrastructure condition and integrity, intrusion and motion, and object detection sensors. The data may be raw or pre-processed in the field.
• 02: The center shall remotely monitor and control security sensor data collected in traveler secure areas, which include transit stations, transit stops, rest areas, park and ride lots, and other fixed sites along travel routes (e.g., emergency pull-off areas and travel information centers). The types of security sensor data include environmental threat (e.g. chemical agent, toxic industrial chemical, biological, explosives, and radiological sensors), intrusion and motion, and object detection sensors. The data may be raw or pre-processed in the field.
• 04: The center shall exchange security sensor data with other emergency centers.
• 05: The center shall identify potential security threats based on collected security sensor data.
• 06: The center shall verify potential security threats by correlating security sensor data from multiple sources.
• 08: The center shall exchange threat analysis data with Alerting and Advisory Systems and use that data in local threat analysis processing.
• 09: The center shall disseminate threat information to other agencies, including traffic, transit, maintenance, rail operations, and other emergency management centers.
• 11: The center shall request activation of barriers and safeguards on request from center personnel.
• 12: The center shall maintain the status of the security sensor field equipment.


• County City and Local EOCs/Warning Points - Emergency Secure Area Surveillance
• 01: The center shall remotely monitor video images and audio surveillance data collected in secure areas including facilities (e.g. transit yards) and transportation infrastructure (e.g. bridges, tunnels, interchanges, roadway infrastructure, and transit railways or guideways). The data may be raw or pre-processed in the field.
• 02: The center shall remotely monitor video images and audio surveillance data collected in traveler secure areas, which include transit stations, transit stops, rest areas, park and ride lots, and other fixed sites along travel routes (e.g., emergency pull-off areas and travel information centers). The data may be raw or pre-processed in the field.
• 03: The center shall remotely monitor video images and audio surveillance data collected on-board transit vehicles. The data may be raw or pre-processed in the field.
• 04: The center shall exchange surveillance data with other emergency centers.
• 05: The center shall identify potential security threats based on collected security surveillance data.
• 06: The center shall verify potential security threats by correlating security surveillance data from multiple sources.
• 07: The center shall remotely control security surveillance devices in secure areas including facilities (e.g. transit yards) and transportation infrastructure (e.g. bridges, tunnels, interchanges, roadway infrastructure, and transit railways or guideways).
• 08: The center shall remotely control security surveillance devices in traveler secure areas, which include transit stations, transit stops, rest areas, park and ride lots, and other fixed sites along travel routes (e.g., emergency pull-off areas and travel information centers).
• 09: The center shall remotely control security surveillance devices on-board transit vehicles.
• 11: The center shall exchange traveler images with other emergency management centers to support traveler image matching.
• 12: The center shall respond to control data from center personnel regarding security surveillance data collection, processing, threat detection, and image matching.
• 13: The center shall monitor maintenance status of the security sensor field equipment.


• County City and Local Traffic Control Systems - TMC Evacuation Support
• 01: The center shall coordinate planning for evacuation with emergency management centers - including pre-planning activities such as establishing routes, areas to be evacuated, timing, etc.
• 02: The center shall support requests from emergency management centers to preempt the current traffic control strategy, activate traffic control and closure systems such as gates and barriers, activate safeguard systems, or use driver information systems to support evacuation traffic control plans.
• 03: The center shall coordinate evacuation information and controls with other traffic management centers.
• 04: The center shall coordinate execution of evacuation strategies with emergency management centers - including activities such as setting closures and detours, establishing routes, updating areas to be evacuated, timing the process, etc.
• 05: The center shall provide road network conditions and traffic images to support evacuations.


• County City and Local Traffic Control Systems - TMC Incident Detection
• 01: The center shall receive inputs from the Alerting and Advisory System concerning the possibility or occurrence of severe weather, terrorist activity, or other major emergency, including information provided by the Emergency Alert System.
• 02: The center shall collect and store traffic flow and image data from the field equipment to detect and verify incidents.
• 03: The center shall receive inputs concerning upcoming events that would effect the traffic network from event promoters and traveler information service providers.
• 04: The center shall exchange incident and threat information with emergency management centers as well as maintenance and construction centers; including notification of existence of incident and expected severity, location, time and nature of incident.
• 05: The center shall support requests from emergency management centers and border inspection systems to remotely control sensor and surveillance equipment located in the field.
• 06: The center shall provide road network conditions and traffic images to emergency management centers to support the detection, verification, and classification of incidents.
• 07: The center shall provide video and traffic sensor control commands to the field equipment to detect and verify incidents.


• County City and Local Traffic Control Systems - TMC Incident Dispatch Coordination
• 01: The center shall exchange alert information and status with emergency management centers. The information includes notification of a major emergency such as a natural or man-made disaster, civil emergency, or child abduction for distribution to the public. The information may include the alert originator, the nature of the emergency, the geographic area affected by the emergency, the effective time period, and information and instructions necessary for the public to respond to the alert. This may also identify specific information that should not be released to the public.
• 02: The center shall coordinate planning for incidents with emergency management centers - including pre-planning activities for disaster response, evacuation, and recovery operations.
• 03: The center shall support requests from emergency management centers to remotely control sensor and surveillance equipment located in the field, provide special routing for emergency vehicles, and to provide responding emergency vehicles with signal preemption.
• 04: The center shall exchange incident information with emergency management centers, maintenance and construction centers, transit centers, information service providers, and the media including description, location, traffic impact, status, expected duration, and response information.
• 05: The center shall share resources with allied agency centers to implement special traffic control measures, assist in clean up, verify an incident, etc. This may also involve coordination with maintenance centers.
• 06: The center shall receive inputs concerning upcoming events that would effect the traffic network from event promoters, traveler information service providers, media, border crossings, and rail operations centers.
• 07: The center shall provide road network conditions and traffic images to emergency management centers, maintenance and construction centers, and traveler information service providers.
• 08: The center shall monitor incident response performance and calculate incident response and clearance times.
• 09: The center shall exchange road network status assessment information with emergency management and maintenance centers including an assessment of damage sustained by the road network including location and extent of the damage, estimate of remaining capacity, required closures, alternate routes, necessary restrictions, and time frame for repair and recovery.
• 10: The center shall coordinate information and controls with other traffic management centers.
• 11: The center shall receive inputs from emergency management and transit management centers to develop an overall status of the transportation system including emergency transit schedules in effect and current status and condition of the transportation infrastructure.


• County City and Local Traffic Control Systems - TMC Regional Traffic Management
• 01: The center shall exchange traffic information with other traffic management centers including incident information, congestion data, traffic data, signal timing plans, and real-time signal control information.
• 02: The center shall exchange traffic control information with other traffic management centers to support remote monitoring and control of traffic management devices (e.g. signs, sensors, signals, cameras, etc.).


• County City and Local Traffic Control Systems - TMC Traffic Information Dissemination
• 01: The center shall remotely control dynamic messages signs for dissemination of traffic and other information to drivers.
• 02: The center shall remotely control driver information systems that communicate directly from a center to the vehicle radio (such as Highway Advisory Radios) for dissemination of traffic and other information to drivers.
• 03: The center shall collect operational status for the driver information systems equipment (DMS, HAR, etc.).
• 04: The center shall collect fault data for the driver information systems equipment (DMS, HAR, etc.) for repair.
• 05: The center shall retrieve locally stored traffic information, including current and forecasted traffic information, road and weather conditions, traffic incident information, information on diversions and alternate routes, closures, and special traffic restrictions (lane/shoulder use, weight restrictions, width restrictions, HOV requirements), and the definition of the road network itself.
• 06: The center shall distribute traffic data to maintenance and construction centers, transit centers, emergency management centers, parking facilities, and traveler information providers.
• 07: The center shall distribute traffic data to the media.
• 08: The center shall provide the capability for center personnel to control the nature of the data that is available to non-traffic operations centers and the media.
• 09: The center shall collect current lane configurations status for the driver information systems equipment (DMS, HAR, etc.).
• 10: The center shall provide traffic information in both data stream and graphical display.
• 11: The center shall provide drivers low emission zone restriction or fees information.
• 12: The center shall receive alert notification of a major emergency such as a natural or man-made disaster, civil emergency, or child abduction for distribution to the public from emergency management.
• 13: The center shall receive low emission zone information from emission management.
• 14: The center shall provide operators information on the state of transportation system operations within the low emissions zone.
• 15: The center shall coordinate information dissemination with other traffic management centers.


• FDOT District Transportation Management Centers using SunGuide - Center Data Collection
• 01: The center shall collect transportation data such as traffic operational data, transit data, vehicle data, weather data, freight data, event logs, etc. and make it available for ITS Archives upon request.
• 02: The center shall assign quality control metrics and meta-data to be stored along with the data. Meta-data may include attributes that describe the source and quality of the data and the conditions surrounding the collection of the data.
• 03: The center shall receive and respond to requests from ITS Archives for either a catalog of the traffic data or for the data itself.
• 04: The center shall be able to produce sample products of the data available.
• 05: The Center shall collect operational data from other Centers.
• 06: The Center shall collect operational data from other Centers.


• FDOT District Transportation Management Centers using SunGuide - Emergency Data Collection
• 01: The center shall collect emergency service data, emergency vehicle management data, emergency vehicle data, sensor and surveillance data, threat data, and incident data.


• FDOT District Transportation Management Centers using SunGuide - Emergency Early Warning System
• 01: The center shall monitor information from Alerting and Advisory Systems such as the Information Sharing and Analysis Centers (ISACs), the National Infrastructure Protection Center (NIPC), the Homeland Security Advisory System (HSAS), etc. The information may include assessments (general incident and vulnerability awareness information), advisories (identification of threats or recommendations to increase preparedness levels), or alerts (information on imminent or in-progress emergencies).
• 02: The center shall receive incident information from other transportation management centers to support the early warning system.
• 03: The center shall support the entry of alert and advisory information directly from the emergency system operator.
• 04: The center shall receive potential incident information from social media sources to support the early warning system.
• 05: The center shall provide the capability to correlate alerts and advisories, incident information, and security sensor and surveillance data.
• 06: The center shall broadcast wide-area alerts and advisories to traffic management centers for emergency situations such as severe weather events, civil emergencies, child abduction (AMBER alert system), military activities, and other situations that pose a threat to life and property.
• 07: The center shall broadcast wide-area alerts and advisories to transit management centers for emergency situations such as severe weather events, civil emergencies, child abduction (AMBER alert system), military activities, and other situations that pose a threat to life and property.
• 08: The center shall broadcast wide-area alerts and advisories to toll administration centers for emergency situations such as severe weather events, civil emergencies, child abduction (AMBER alert system), military activities, and other situations that pose a threat to life and property.
• 09: The center shall broadcast wide-area alerts and advisories to traveler information service providers for emergency situations such as severe weather events, civil emergencies, child abduction (AMBER alert system), military activities, and other situations that pose a threat to life and property.
• 10: The center shall broadcast wide-area alerts and advisories to maintenance centers for emergency situations such as severe weather events, civil emergencies, child abduction (AMBER alert system), military activities, and other situations that pose a threat to life and property.
• 11: The center shall broadcast wide-area alerts and advisories to other emergency management centers for emergency situations such as severe weather events, civil emergencies, child abduction (AMBER alert system), military activities, and other situations that pose a threat to life and property.
• 12: The center shall broadcast wide-area alerts and advisories to commercial vehicle administration centers and roadside check facilities for emergency situations such as severe weather events, civil emergencies, child abduction (AMBER alert system), military activities, and other situations that pose a threat to life and property.
• 13: The center shall process status information from each of the centers that have been sent the wide-area alert.
• 14: The center shall coordinate the broadcast of wide-area alerts and advisories with other emergency management centers.
• 15: The center shall present the alert and advisory information and the status of the actions taken in response to the alert by the other centers to the emergency system operator as received from other system inputs.


• FDOT District Transportation Management Centers using SunGuide - Emergency Environmental Monitoring
• 01: The center shall collect current and forecast road and weather information from weather service providers (such as the National Weather Service and value-added sector specific meteorological services).
• 02: The center shall collect road network conditions data, including advisories, from traffic management and traveler information centers.
• 03: The center shall collect asset restrictions information from roadway maintenance operations.
• 04: The center shall assimilate current and forecast road conditions and surface weather information to support incident management.
• 05: The center shall provide the road and weather warning and advisories to the emergency responders.


• FDOT District Transportation Management Centers using SunGuide - Emergency Evacuation Support
• 01: The center shall manage inter-agency coordination of evacuation operations, from initial planning through the evacuation process and reentry.
• 02: The center shall develop and exchange evacuation plans with allied agencies prior to the occurrence of a disaster.
• 03: The center shall provide an interface to the emergency system operator to enter evacuation plans and procedures and present the operator with other agencies’ plans.
• 04: The center shall coordinate evacuation destinations and shelter needs with shelter providers (e.g., the American Red Cross) in the region.
• 05: The center shall provide evacuation information to traffic, transit, maintenance and construction, rail operations, and other emergency management centers as needed.
• 07: The center shall request traffic management agencies to implement special traffic control strategies and to control evacuation traffic, including traffic on local streets and arterials as well as the major evacuation routes.
• 08: The center shall provide traveler information systems with evacuation guidance including basic information to assist potential evacuees in determining whether evacuation is necessary and when it is safe to return.
• 09: The center shall monitor the progress or status of the evacuation once it begins and exchange tactical plans, prepared during the incident, with allied agencies.
• 10: The center shall monitor the progress of the reentry process.
• 11: The center shall submit evacuation information to toll administration centers along with requests for changes in the toll services or fee collection during an evacuation.
• 12: The center shall retrieve information from public health systems to plan for and implement evacuations or in-place sheltering for biological, chemical, radiation, and other public health emergencies.
• 13: The center shall make use of population and housing data to plan for and implement evacuations or in-place sheltering for biological, chemical, radiation, and other public health emergencies.
• 14: The center shall maintain information on the population of an area in the event of an evacuation, including addresses, types of facility (residence, multi-family dwelling, commercial retail, commercial office, etc.), and special considerations (storage of flammable liquids, special needs residents.


• FDOT District Transportation Management Centers using SunGuide - Emergency Incident Command
• 01: The center shall provide tactical decision support, resource coordination, and communications integration for first responders to support local management of an incident.
• 02: The center shall provide incident command communications with public safety, emergency management, transportation, and other allied response agency centers.
• 03: The center shall track and maintain resource information and action plans pertaining to the incident command.
• 04: The center shall share incident command information with other public safety agencies including resource deployment status, hazardous material information, rail incident information, evacuation advice as well as traffic, road, and weather conditions.
• 05: The center shall assess the status of responding emergency vehicles as part of an incident command.
• 06: The center shall provide other agencies real-time information on the current conditions at the incident scene.
• 07: The center shall collect modeling program outputs to support emergency dispatch and staging of personnel and equipment, e.g. predicted HAZMAT plumes or crash severity predictions.
• 08: The center shall collect information about freight or cargo to support emergency dispatch and staging of personnel and equipment, e.g. cargo manifest or HAZMAT information.
• 10: The center shall collect on-scene reports to support emergency dispatch and staging of personnel and equipment.
• 11: The center shall provide situational awareness information to emergency responders about an incident, both en-route and while they are on-scene.
• 12: The center shall provide status of the current conditions at the incident scene to arriving responders.


• FDOT District Transportation Management Centers using SunGuide - Emergency Response Management
• 01: The center shall provide strategic emergency response capabilities provided by an Emergency Operations Center for large-scale incidents and disasters.
• 02: The center shall manage coordinated inter-agency responses to and recovery from large-scale emergencies. Such agencies include traffic management, transit, maintenance and construction management, rail operations, and other emergency management agencies.
• 03: The center shall provide the capability to implement response plans and track progress through the incident by exchanging incident information and response status with allied agencies.
• 04: The center shall develop, coordinate with other agencies, and store emergency response plans.
• 05: The center shall track the availability of resources and coordinate resource sharing with allied agency centers including traffic, maintenance, or other emergency centers.
• 06: The center shall allocate the appropriate emergency services, resources, and vehicle (s) to respond to incidents, and shall provide the capability to override the current allocation to suit the special needs of a current incident.
• 07: The center shall receive event scheduling information from Event Promoters.
• 08: The center shall support remote control of field equipment normally under control of the traffic management center including traffic signals, dynamic message signs, gates, and barriers.
• 09: The center shall provide the capability to remotely control and monitor CCTV systems normally operated by a traffic management center.
• 11: The center shall assimilate the damage assessment of the transit, traffic, rail, maintenance, and other emergency center services and systems to create an overall transportation system status, and disseminate to each of these centers and the traveling public via traveler information providers.
• 12: The center shall provide information to the media concerning the status of an emergency response.
• 13: The center shall provide the capability for center personnel to provide inputs to the management of incidents, disasters and evacuations.
• 14: The center shall collect information about the status of the recovery efforts for the infrastructure during disasters.
• 15: The center shall provide the overall status of infrastructure recovery efforts to traveler information providers and media.
• 16: The center shall provide the capability to communicate information about emergency situations to local population through the Emergency Telecommunications System.
• 17: The center shall provide the capability to identify neighborhoods and businesses that should be informed of an emergency situation based on information collected about incidents including their severity, impacted locations, and recovery schedule.
• 18: The center shall retrieve information from public health systems to increase preparedness for, and implement a response to biological, chemical, radiation, and other public health emergencies.
• 19: The center shall manage coordinated inter-agency responses to incidents at an international border.
• 20: The center shall receive temporary facility restrictions that are imposed during maintenance and construction that may impact emergency response.
• 21: The center shall receive proposed maintenance and construction work plans, analyze the activity as a possible incident requiring emergency response, and provide work plan feedback to the sending center.


• FDOT District Transportation Management Centers using SunGuide - Emergency Secure Area Sensor Management
• 01: The center shall remotely monitor and control security sensor data collected in secure areas including facilities (e.g. transit yards) and transportation infrastructure (e.g. bridges, tunnels, interchanges, roadway infrastructure, and transit railways or guideways). The types of security sensor data include environmental threat (e.g. chemical agent, toxic industrial chemical, biological, explosives, and radiological sensors), infrastructure condition and integrity, intrusion and motion, and object detection sensors. The data may be raw or pre-processed in the field.
• 02: The center shall remotely monitor and control security sensor data collected in traveler secure areas, which include transit stations, transit stops, rest areas, park and ride lots, and other fixed sites along travel routes (e.g., emergency pull-off areas and travel information centers). The types of security sensor data include environmental threat (e.g. chemical agent, toxic industrial chemical, biological, explosives, and radiological sensors), intrusion and motion, and object detection sensors. The data may be raw or pre-processed in the field.
• 03: The center shall remotely monitor and control security sensor data collected on-board transit vehicles. The types of security sensor data include environmental threat (e.g. chemical agent, toxic industrial chemical, biological, explosives, and radiological sensors) and object detection sensors. The data may be raw or pre-processed in the field.
• 04: The center shall exchange security sensor data with other emergency centers.
• 05: The center shall identify potential security threats based on collected security sensor data.
• 06: The center shall verify potential security threats by correlating security sensor data from multiple sources.
• 07: The center shall perform threat analysis based on correlations of security sensor and surveillance data.
• 08: The center shall exchange threat analysis data with Alerting and Advisory Systems and use that data in local threat analysis processing.
• 09: The center shall disseminate threat information to other agencies, including traffic, transit, maintenance, rail operations, and other emergency management centers.
• 10: The center shall respond to control data from center personnel regarding security sensor data collection, processing, threat detection, and threat analysis.
• 11: The center shall request activation of barriers and safeguards on request from center personnel.
• 12: The center shall maintain the status of the security sensor field equipment.


• FDOT District Transportation Management Centers using SunGuide - Emergency Secure Area Surveillance
• 01: The center shall remotely monitor video images and audio surveillance data collected in secure areas including facilities (e.g. transit yards) and transportation infrastructure (e.g. bridges, tunnels, interchanges, roadway infrastructure, and transit railways or guideways). The data may be raw or pre-processed in the field.
• 02: The center shall remotely monitor video images and audio surveillance data collected in traveler secure areas, which include transit stations, transit stops, rest areas, park and ride lots, and other fixed sites along travel routes (e.g., emergency pull-off areas and travel information centers). The data may be raw or pre-processed in the field.
• 03: The center shall remotely monitor video images and audio surveillance data collected on-board transit vehicles. The data may be raw or pre-processed in the field.
• 04: The center shall exchange surveillance data with other emergency centers.
• 05: The center shall identify potential security threats based on collected security surveillance data.
• 06: The center shall verify potential security threats by correlating security surveillance data from multiple sources.
• 07: The center shall remotely control security surveillance devices in secure areas including facilities (e.g. transit yards) and transportation infrastructure (e.g. bridges, tunnels, interchanges, roadway infrastructure, and transit railways or guideways).
• 08: The center shall remotely control security surveillance devices in traveler secure areas, which include transit stations, transit stops, rest areas, park and ride lots, and other fixed sites along travel routes (e.g., emergency pull-off areas and travel information centers).
• 09: The center shall remotely control security surveillance devices on-board transit vehicles.
• 10: The center shall match traveler video images against a database from the Alerting and Advisory Systems of known images that may represent criminals and terrorists.
• 11: The center shall exchange traveler images with other emergency management centers to support traveler image matching.
• 12: The center shall respond to control data from center personnel regarding security surveillance data collection, processing, threat detection, and image matching.
• 13: The center shall monitor maintenance status of the security sensor field equipment.


• FDOT District Transportation Management Centers using SunGuide - MCM Data Collection
• 01: The center shall collect maintenance and construction data (such as field equipment status, infrastructure status, maintenance and construction activity data) gathered from roadway, traffic, and other maintenance and construction sources.


• FDOT District Transportation Management Centers using SunGuide - MCM Incident Management
• 01: The maintenance center shall receive inputs from the Alerting and Advisory System concerning the possibility or occurrence of severe weather, terrorist activity, or other major emergency, including information provided by the Emergency Alert System.
• 02: The maintenance center shall exchange alert information and status with emergency management centers. The information includes notification of a major emergency such as a natural or man-made disaster, civil emergency, or child abduction. The information may include the alert originator, the nature of the emergency, the geographic area affected by the emergency, the effective time period, etc.
• 03: The maintenance center shall exchange incident and threat information with emergency management centers as well as traffic management centers; including notification of existence of incident and expected severity, location, time and nature of incident.
• 04: The maintenance center shall coordinate planning for incidents with emergency management centers - including pre-planning activities for disaster response, evacuation, and recovery operations.
• 05: The maintenance center shall respond to requests from emergency management to provide maintenance and construction resources to implement response plans, assist in clean up, verify an incident, etc. This may also involve coordination with traffic management centers and other maintenance centers.
• 06: The maintenance center shall exchange road network status assessment information with emergency management and traffic management centers including an assessment of damage sustained by the road network including location and extent of the damage, estimate of remaining capacity, required closures, alternate routes, necessary restrictions, and time frame for repair and recovery.
• 07: The maintenance center shall provide work zone activities affecting the road network during traffic incidents including the nature of the maintenance or construction activity, location, impact to the roadway, expected time(s) and duration of impact, anticipated delays, alternate routes, and suggested speed limits.
• 08: The maintenance center shall receive information indicating the damage sustained by transportation assets, derived from aerial surveillance, field reports, inspections, tests, and analyses to support incident management.
• 09: The maintenance center shall receive evacuation information including evacuation zones, evacuation times, and reentry times from emergency operation centers.


• FDOT District Transportation Management Centers using SunGuide - MCM Roadway Maintenance
• 01: The center shall maintain an interface with asset management systems to track the inventory, restrictions, repair needs and status updates of transportation assets (pavement, bridges, signs, etc.) including location, installation and materials information, vendor/contractor, current maintenance status, standard height, width, and weight restrictions.
• 02: The center shall respond to requests from emergency management and traffic management centers for hazard removal, field equipment repair, and other roadway maintenance.
• 03: The center shall exchange information with administrative systems to support the planning and scheduling of maintenance activities. This information includes: equipment and consumables resupply purchase request status, personnel qualifications including training and special certifications, environmental regulations and rules that may impact maintenance activities, and requests and project requirements from contract administration.
• 04: The center shall provide emergency management and traffic management centers with information about scheduled maintenance and construction work activities including anticipated closures and impact to the roadway, alternate routes, anticipated delays, closure times, and durations.
• 05: The center shall collect the status and fault data from roadside equipment, such as traffic, infrastructure, and environmental sensors, highway advisory radio and dynamic message signs, automated roadway treatment systems, barrier and safeguard systems, cameras, traffic signals and override equipment, ramp meters, short range communications equipment, security sensors and surveillance equipment, etc., and provide a cohesive view of equipment repair needs.
• 06: The center shall collect the status and fault data from the centers that operate the equipment, including data for traffic, infrastructure, and environmental sensors, highway advisory radio and dynamic message signs, automated roadway treatment systems, barrier and safeguard systems, cameras, traffic signals and override equipment, ramp meters, short range communications equipment, security sensors and surveillance equipment, etc., and provide a cohesive view of equipment repair needs.
• 07: The center shall receive equipment availability and materials storage status information from storage facilities to support the scheduling of roadway maintenance and construction activities.
• 08: The center shall collect current and forecast traffic and weather information from traffic management centers and weather service providers (such as the National Weather Service and value-added sector specific meteorological services).
• 11: The center shall track the status of roadway maintenance and construction activities by monitoring collected data from the dispatched vehicles and equipment.
• 12: The center shall report the status of roadway maintenance activities to the centers that operate the equipment.


• FDOT District Transportation Management Centers using SunGuide - MCM Work Activity Coordination
• 01: The center shall provide work zone activities affecting the road network including the nature of the maintenance or construction activity, location, impact to the roadway, expected time(s) and duration of impact, anticipated delays, alternate routes, and suggested speed limits. This information may be augmented with images that provide a visual indication of current work zone status and traffic impacts.
• 02: The center shall provide status information about scheduled maintenance and construction activities including anticipated closures and impact to the roadway, alternate routes, anticipated delays, closure times, and durations. The information is provided to other management centers such as traffic, emergency, transit, traveler information providers, other maintenance centers, multimodal transportation providers, rail operations, and the media.
• 05: The Center shall provide road infrastructure restriction information to other Centers.
• 07: The center shall exchange rail schedules and work plans with rail operations centers.


• FDOT District Transportation Management Centers using SunGuide - MCM Work Zone Management
• 02: The center shall control the collection of work zone status information including video images from cameras located in or near the work zone.
• 03: The center shall disseminate work zone information to other agencies and centers including traffic, transit, emergency management centers, other maintenance centers, traveler information centers, and the media.
• 04: The center shall control traffic in work zones by providing remote control of dynamic message signs, highway advisory radio systems, gates, and barriers located in or near the work zone.
• 05: The center shall exchange information with administrative systems to support the planning and scheduling of work zone activities. This information includes: equipment and consumables resupply purchase request status, personnel qualifications including training and special certifications, environmental regulations and rules that may impact maintenance activities, and requests and project requirements from contract administration.
• 06: The center shall collect real-time information on the state of the road network including current traffic and road conditions to support work zone scheduling and management.


• FDOT District Transportation Management Centers using SunGuide - TIC Connected Vehicle Traveler Info Distribution
• 01: The center shall collect traveler information for distribution including traffic and road conditions, incident information, maintenance and construction information, event information, transit information, parking information, and weather information.
• 02: The center shall distribute location relevant traveler information to short range communications equipment at the roadside.
• 03: The center shall provide the capability for a system operator to monitor connected vehicle system operation and control the type and update frequency of traveler information that is distributed.
• 04: The center shall send eco-driving recommendations to connected vehicles so that the vehicle or the driver can adjust their driving behavior to save fuel and reduce emissions.


• FDOT District Transportation Management Centers using SunGuide - TIC Data Collection
• 01: The center shall collect, process, and store traffic and highway condition information, including incident information, detours and road closures, event information, recommended routes, and current speeds on specific routes.
• 02: The transportation information center shall select real-time information on the state of the regional transportation system including current traffic and road conditions, weather conditions, transit information, parking information, special event and incident information.
• 07: The center shall collect, process, and store current and forecast road conditions and surface weather conditions.
• 08: The center shall collect, process, and store event information.
• 09: The center shall collect, process, and store air quality information.
• 10: The center shall collect, process, and store freight specific traveler information.
• 11: The center shall collect, process, and store border crossing information.
• 14: The center shall collect evacuation information including evacuation zones, evacuation times, and reentry times.
• 15: The center shall collect alert information and status from emergency management centers. The information includes notification of a major emergency such as a natural or man-made disaster, civil emergency, or child abduction for distribution to the public.
• 16: The center shall collect road condition information for freeways, arterials, and secondary roads that are used as freight routes.
• 17: The center shall collect emissions information, including information from low emission zone operations.
• 18: The center shall collect information concerning members of the population that may require additional assistance in the event of an evacuation, including the names of household members, address, special needs, and any care giver information (nurse or hospice service that may want to keep track of their patient’s status).
• 21: The center shall provide environmental road data to other transportation centers and weather processing systems.
• 22: The center shall collect, store and exchange transportation-related regulations with other transportation centers.


• FDOT District Transportation Management Centers using SunGuide - TIC Operations Data Collection
• 01: The center shall collect traveler information data, such as parking lot data, rideshare data, road network use data, vehicle probe data, and other data from traveler information system operations.
• 04: The center shall receive and respond to requests from ITS Archives for either a catalog of the traveler information data or for the data itself.


• FDOT District Transportation Management Centers using SunGuide - TIC Situation Data Management
• 01: The center shall collect traffic probe data (speeds, travel times, etc.) from appropriately equipped vehicles and short range communications equipment.
• 02: The center shall collect environmental probe data (air temperature, exterior light status, wiper status, traction control status, etc.) from appropriately equipped vehicles and short range communications equipment.
• 03: The center shall collect road condition data from probe-equipped transit vehicles via transit management centers.
• 04: The center shall collect probe data from toll administrative centers containing travel times between toll collection points for those vehicles equipped for electronic toll collection; the data may be aggregated and processed at the sending center.
• 05: The center shall aggregate collected traffic probe data, calculate route segment travel times, route segment speeds, route usage, and road weather information for dissemination to other centers.


• FDOT District Transportation Management Centers using SunGuide - TIC Traveler Information Broadcast
• 01: The center shall disseminate traffic and highway condition information to travelers, including incident information, detours and road closures, event information, recommended routes, and current speeds on specific routes.
• 06: The center shall disseminate weather information to travelers.
• 07: The center shall disseminate event information to travelers.
• 08: The center shall disseminate air quality information to travelers.
• 09: The center shall provide traffic and incident data to the media.
• 10: The center shall provide the capability for a system operator to control the type and update frequency of broadcast traveler information.


• FDOT District Transportation Management Centers using SunGuide - TMC Data Collection
• 01: The center shall collect traffic management data such as operational data, event logs, etc.
• 02: The traffic management center shall assign quality control metrics and meta-data to be stored along with the data. Meta-data may include attributes that describe the source and quality of the data and the conditions surrounding the collection of the data.
• 03: The traffic management center shall receive and respond to requests from ITS Archives for either a catalog of the traffic data or for the data itself.
• 04: The traffic management center shall be able to produce sample products of the data available.


• FDOT District Transportation Management Centers using SunGuide - TMC Demand Management Coordination
• 02: The center shall collect and store parking information from parking management providers including lot locations, features (e.g. ability to handle oversized vehicles), capacity, type, hours of operation and rates.


• FDOT District Transportation Management Centers using SunGuide - TMC Evacuation Support
• 01: The center shall coordinate planning for evacuation with emergency management centers - including pre-planning activities such as establishing routes, areas to be evacuated, timing, etc.
• 02: The center shall support requests from emergency management centers to preempt the current traffic control strategy, activate traffic control and closure systems such as gates and barriers, activate safeguard systems, or use driver information systems to support evacuation traffic control plans.
• 03: The center shall coordinate evacuation information and controls with other traffic management centers.
• 04: The center shall coordinate execution of evacuation strategies with emergency management centers - including activities such as setting closures and detours, establishing routes, updating areas to be evacuated, timing the process, etc.
• 05: The center shall provide road network conditions and traffic images to support evacuations.


• FDOT District Transportation Management Centers using SunGuide - TMC Incident Detection
• 01: The center shall receive inputs from the Alerting and Advisory System concerning the possibility or occurrence of severe weather, terrorist activity, or other major emergency, including information provided by the Emergency Alert System.
• 02: The center shall collect and store traffic flow and image data from the field equipment to detect and verify incidents.
• 03: The center shall receive inputs concerning upcoming events that would effect the traffic network from event promoters and traveler information service providers.
• 04: The center shall exchange incident and threat information with emergency management centers as well as maintenance and construction centers; including notification of existence of incident and expected severity, location, time and nature of incident.
• 05: The center shall support requests from emergency management centers and border inspection systems to remotely control sensor and surveillance equipment located in the field.
• 06: The center shall provide road network conditions and traffic images to emergency management centers to support the detection, verification, and classification of incidents.
• 07: The center shall provide video and traffic sensor control commands to the field equipment to detect and verify incidents.


• FDOT District Transportation Management Centers using SunGuide - TMC Incident Dispatch Coordination
• 01: The center shall exchange alert information and status with emergency management centers. The information includes notification of a major emergency such as a natural or man-made disaster, civil emergency, or child abduction for distribution to the public. The information may include the alert originator, the nature of the emergency, the geographic area affected by the emergency, the effective time period, and information and instructions necessary for the public to respond to the alert. This may also identify specific information that should not be released to the public.
• 02: The center shall coordinate planning for incidents with emergency management centers - including pre-planning activities for disaster response, evacuation, and recovery operations.
• 03: The center shall support requests from emergency management centers to remotely control sensor and surveillance equipment located in the field, provide special routing for emergency vehicles, and to provide responding emergency vehicles with signal preemption.
• 04: The center shall exchange incident information with emergency management centers, maintenance and construction centers, transit centers, information service providers, and the media including description, location, traffic impact, status, expected duration, and response information.
• 05: The center shall share resources with allied agency centers to implement special traffic control measures, assist in clean up, verify an incident, etc. This may also involve coordination with maintenance centers.
• 06: The center shall receive inputs concerning upcoming events that would effect the traffic network from event promoters, traveler information service providers, media, border crossings, and rail operations centers.
• 07: The center shall provide road network conditions and traffic images to emergency management centers, maintenance and construction centers, and traveler information service providers.
• 08: The center shall monitor incident response performance and calculate incident response and clearance times.
• 09: The center shall exchange road network status assessment information with emergency management and maintenance centers including an assessment of damage sustained by the road network including location and extent of the damage, estimate of remaining capacity, required closures, alternate routes, necessary restrictions, and time frame for repair and recovery.
• 10: The center shall coordinate information and controls with other traffic management centers.
• 11: The center shall receive inputs from emergency management and transit management centers to develop an overall status of the transportation system including emergency transit schedules in effect and current status and condition of the transportation infrastructure.


• FDOT District Transportation Management Centers using SunGuide - TMC Regional Traffic Management
• 01: The center shall exchange traffic information with other traffic management centers including incident information, congestion data, traffic data, signal timing plans, and real-time signal control information.
• 02: The center shall exchange traffic control information with other traffic management centers to support remote monitoring and control of traffic management devices (e.g. signs, sensors, signals, cameras, etc.).


• FDOT District Transportation Management Centers using SunGuide - TMC Situation Data Management
• 01: The center shall collect traffic probe data from vehicles via roadside field equipment.
• 02: The center shall collect road condition data from probe-equipped transit vehicles via transit management centers; the data may be aggregated and preliminarily processed at the sending center.
• 03: The center shall collect traffic data from traveler information centers based on data from their subscriber vehicles; the data may be aggregated and initial link time calculations performed at the sending center.
• 04: The center shall collect probe data from payment administrative centers containing travel times between toll collection points for those vehicles equipped for electronic toll collection; the data may be aggregated and processed at the sending center.
• 05: The center shall collect operational status for the roadside probe data collection equipment.
• 06: The center shall collect fault data for the roadside probe data collection equipment for repair.


• FDOT District Transportation Management Centers using SunGuide - TMC Traffic Information Dissemination
• 01: The center shall remotely control dynamic messages signs for dissemination of traffic and other information to drivers.
• 02: The center shall remotely control driver information systems that communicate directly from a center to the vehicle radio (such as Highway Advisory Radios) for dissemination of traffic and other information to drivers.
• 03: The center shall collect operational status for the driver information systems equipment (DMS, HAR, etc.).
• 04: The center shall collect fault data for the driver information systems equipment (DMS, HAR, etc.) for repair.
• 05: The center shall retrieve locally stored traffic information, including current and forecasted traffic information, road and weather conditions, traffic incident information, information on diversions and alternate routes, closures, and special traffic restrictions (lane/shoulder use, weight restrictions, width restrictions, HOV requirements), and the definition of the road network itself.
• 06: The center shall distribute traffic data to maintenance and construction centers, transit centers, emergency management centers, parking facilities, and traveler information providers.
• 07: The center shall distribute traffic data to the media.
• 08: The center shall provide the capability for center personnel to control the nature of the data that is available to non-traffic operations centers and the media.
• 09: The center shall collect current lane configurations status for the driver information systems equipment (DMS, HAR, etc.).
• 10: The center shall provide traffic information in both data stream and graphical display.
• 11: The center shall provide drivers low emission zone restriction or fees information.
• 12: The center shall receive alert notification of a major emergency such as a natural or man-made disaster, civil emergency, or child abduction for distribution to the public from emergency management.
• 13: The center shall receive low emission zone information from emission management.
• 14: The center shall provide operators information on the state of transportation system operations within the low emissions zone.
• 15: The center shall coordinate information dissemination with other traffic management centers.


• FDOT District Transportation Management Centers using SunGuide - TMC Traffic Management Decision Support
• 01: The center shall provide center personnel with an integrated regional view of current and forecast road and traffic conditions including traffic incidents, special events, maintenance activities and other events or conditions that impact capacity or demand.
• 02: The center shall identify network imbalances and potential courses of action.
• 03: The center shall compare the impact of potential courses of action and make recommendations to the operator.
• 04: The recommended actions shall include predefined incident response plans, signal timing plan changes, DMS/HAR messages, lane control strategies and freeway control strategies including ramp metering, interchange metering, and mainline metering.
• 05: The recommended actions shall include multimodal strategies that include suggested transit strategies and suggested route and mode choices for travelers.
• 06: The center shall provide an interface to center personnel to input control parameters for the decision support process and receive recommended actions and supporting information presentation.
• 07: The center shall provide transportation operational strategies to other centers.


• FDOT District Transportation Management Centers using SunGuide - TMC Traffic Network Performance Evaluation
• 01: The center shall monitor, analyze, and store traffic sensor data (speed, volume, occupancy) collected from field elements under remote control of the center to support overall network performance evaluations.
• 02: The center shall collect wide-area pollution data from emissions management centers to support overall network performance evaluations.
• 03: The center shall collect and store anticipated route information from traveler information centers to support overall network performance evaluations and predictions.
• 04: The center shall exchange information with transit management centers including details current transit routes, the level of service on each route, and the progress of individual vehicles along their routes for use in forecasting demand and estimating current transportation network performance.
• 05: The center shall exchange traffic information with other traffic management centers, including incidents, congestion data, traffic data, signal timing plans, and real-time signal control information to support overall network performance evaluations.
• 06: The center shall provide an interface to the archive data repository to enable the operator to retrieve historical operating data for use in planning to predict future traffic patterns and conditions.
• 07: This center shall use the collected information to measure overall current and forecast network performance and predict travel demand patterns.


• FL511 - TIC Connected Vehicle Traveler Info Distribution
• 01: The center shall collect traveler information for distribution including traffic and road conditions, incident information, maintenance and construction information, event information, transit information, parking information, and weather information.
• 02: The center shall distribute location relevant traveler information to short range communications equipment at the roadside.
• 04: The center shall send eco-driving recommendations to connected vehicles so that the vehicle or the driver can adjust their driving behavior to save fuel and reduce emissions.


• FL511 - TIC Data Collection
• 01: The center shall collect, process, and store traffic and highway condition information, including incident information, detours and road closures, event information, recommended routes, and current speeds on specific routes.
• 02: The transportation information center shall select real-time information on the state of the regional transportation system including current traffic and road conditions, weather conditions, transit information, parking information, special event and incident information.
• 03: The center shall collect, process, and store maintenance and construction information, including scheduled maintenance and construction work activities and work zone activities.
• 04: The center shall collect, process, and store transit routes and schedules, transit transfer options, transit fares, and real-time schedule adherence information.
• 05: The transportation information center shall collect, process, and store parking information, including location, availability, and fees.
• 06: The center shall collect, process, and store toll fee information.
• 07: The center shall collect, process, and store current and forecast road conditions and surface weather conditions.
• 08: The center shall collect, process, and store event information.
• 09: The center shall collect, process, and store air quality information.
• 10: The center shall collect, process, and store freight specific traveler information.
• 11: The center shall collect, process, and store border crossing information.
• 12: The center shall collect information on transit schedule and service changes that adapt the service to better meet needs of responders and the general public in an emergency situation, including special service schedules supporting evacuation.
• 13: The center shall collect evacuation shelter information including location, hours of operation, special accommodations, and current vacancy/availability information.
• 14: The center shall collect evacuation information including evacuation zones, evacuation times, and reentry times.
• 15: The center shall collect alert information and status from emergency management centers. The information includes notification of a major emergency such as a natural or man-made disaster, civil emergency, or child abduction for distribution to the public.
• 16: The center shall collect road condition information for freeways, arterials, and secondary roads that are used as freight routes.
• 17: The center shall collect emissions information, including information from low emission zone operations.
• 18: The center shall collect information concerning members of the population that may require additional assistance in the event of an evacuation, including the names of household members, address, special needs, and any care giver information (nurse or hospice service that may want to keep track of their patient’s status).
• 19: The center shall collect, store and process multimodal transportation service information (for example, from ferry, rail and airline operators), including current ferry and rail schedule and airport status information and transfer points.
• 20: The center shall collect, store and process information related to service providers, such as hospitals, auto-repair, dining, fueling and emergency services.
• 21: The center shall provide environmental road data to other transportation centers and weather processing systems.
• 22: The center shall collect, store and exchange transportation-related regulations with other transportation centers.


• FL511 - TIC Situation Data Management
• 01: The center shall collect traffic probe data (speeds, travel times, etc.) from appropriately equipped vehicles and short range communications equipment.
• 02: The center shall collect environmental probe data (air temperature, exterior light status, wiper status, traction control status, etc.) from appropriately equipped vehicles and short range communications equipment.
• 03: The center shall collect road condition data from probe-equipped transit vehicles via transit management centers.
• 04: The center shall collect probe data from toll administrative centers containing travel times between toll collection points for those vehicles equipped for electronic toll collection; the data may be aggregated and processed at the sending center.
• 05: The center shall aggregate collected traffic probe data, calculate route segment travel times, route segment speeds, route usage, and road weather information for dissemination to other centers.


• FL511 - TIC Traveler Information Broadcast
• 01: The center shall disseminate traffic and highway condition information to travelers, including incident information, detours and road closures, event information, recommended routes, and current speeds on specific routes.
• 02: The center shall disseminate maintenance and construction information to travelers, including scheduled maintenance and construction work activities and work zone activities.
• 03: The center shall disseminate transit routes and schedules, transit transfer options, transit fares, and real-time schedule adherence information to travelers.
• 04: The center shall disseminate parking information to travelers, including location, availability, and fees.
• 05: The center shall disseminate toll fee information to travelers.
• 06: The center shall disseminate weather information to travelers.
• 07: The center shall disseminate event information to travelers.
• 08: The center shall disseminate air quality information to travelers.
• 09: The center shall provide traffic and incident data to the media.
• 10: The center shall provide the capability for a system operator to control the type and update frequency of broadcast traveler information.


• FL511 - TIC Trip Planning
• 15: The center shall generate route plans to account for parking availability.


• Other FDOT District TMCs - TMC Regional Traffic Management
• 01: The center shall exchange traffic information with other traffic management centers including incident information, congestion data, traffic data, signal timing plans, and real-time signal control information.
• 02: The center shall exchange traffic control information with other traffic management centers to support remote monitoring and control of traffic management devices (e.g. signs, sensors, signals, cameras, etc.).


• Other FDOT District TMCs - TMC Traffic Management Decision Support
• 01: The center shall provide center personnel with an integrated regional view of current and forecast road and traffic conditions including traffic incidents, special events, maintenance activities and other events or conditions that impact capacity or demand.
• 02: The center shall identify network imbalances and potential courses of action.
• 03: The center shall compare the impact of potential courses of action and make recommendations to the operator.
• 04: The recommended actions shall include predefined incident response plans, signal timing plan changes, DMS/HAR messages, lane control strategies and freeway control strategies including ramp metering, interchange metering, and mainline metering.
• 05: The recommended actions shall include multimodal strategies that include suggested transit strategies and suggested route and mode choices for travelers.
• 06: The center shall provide an interface to center personnel to input control parameters for the decision support process and receive recommended actions and supporting information presentation.
• 07: The center shall provide transportation operational strategies to other centers.


• Other FDOT District TMCs - TMC Traffic Network Performance Evaluation
• 01: The center shall monitor, analyze, and store traffic sensor data (speed, volume, occupancy) collected from field elements under remote control of the center to support overall network performance evaluations.
• 02: The center shall collect wide-area pollution data from emissions management centers to support overall network performance evaluations.
• 03: The center shall collect and store anticipated route information from traveler information centers to support overall network performance evaluations and predictions.
• 05: The center shall exchange traffic information with other traffic management centers, including incidents, congestion data, traffic data, signal timing plans, and real-time signal control information to support overall network performance evaluations.
• 06: The center shall provide an interface to the archive data repository to enable the operator to retrieve historical operating data for use in planning to predict future traffic patterns and conditions.


• SunGuide Data Archive - Archive Data Repository
• 01: The center shall collect data from centers.
• 02: The center shall collect data catalogs from one or more data sources. A catalog describes the data contained in the collection of archived data and may include descriptions of the schema or structure of the data, a description of the contents of the data; e.g., time range of entries, number of entries; or a sample of the data (e. g. a thumbnail).
• 03: The center shall store collected data in an information repository.
• 04: The center shall perform quality checks on collected data.
• 05: The center shall notify the system operator of errors related to data collection, analysis and archival.
• 06: The center shall include capabilities for archive to archive coordination.
• 07: The center shall provide the capability to execute methods on the incoming data such as cleansing, summarizations, aggregations, or transformations applied to the data before it is stored in the archive.
• 08: The center shall collect data from data distribution systems and other data sources.
• 09: The center shall respond to requests from the administrator interface function to manage center-sourced data collection.
• 10: The center shall respond to requests from the administrator interface function to manage the archive data.
• 11: The center shall respond to requests for archive data from archive data users (centers, field devices).
• 12: The center shall provide a mechanism for archive data users to request archive data by meta-data range.
• 13: The center shall associate meta-data with archived data, including catalog data, statistical products determined from method execution and data longevity.


• SunGuide Data Archive - Archive Situation Data Archival
• 01: The center shall collect data from roadside devices.
• 02: The center shall respond to requests from the administrator interface function to manage field-sourced data collection.
• 03: The center shall provide the capability to adjust the collection of field-sourced data based on the statistical measures.
• 04: The center shall collect vehicle traffic probe data for performance monitoring and analysis.
• 05: The center shall be capable of archiving vehicle traffic probe data.
• 06: The center shall provide the capability to execute methods on the incoming field data such as aggregation and statistical measures before the data is stored in the archive.
• 07: The center shall respond to requests from the administrator interface function to select and manage data stored in the archive.

Project Solutions:

• (None-Data) - Guaranteed Secure Internet (ITS)
• (None-Data) - Secure Internet (ITS)
• US: ADMS - Secure Internet (ITS)
• US: TMDD - NTCIP Messaging
• US: WZDx - Guaranteed Secure Internet (ITS)

Project Operational Concepts:

Roles and Responsibilities

• Floridas Turnpike Enterprise
• Collects transportation data for use in the associated system (e.g. databases, models, analytical tools, user interface devices) analyses with their tools.
• Operates and maintains SunGuide as a transportation management platform.


• Private Sector ISPs
• Provide road network information.


• County City and Local Emergency Management Agencies
• Coordinate emergency plans and maintenance resources with local maintenance and construction agencies.
• Coordinate emergency plans, emergency transit schedules, and the status of emergency transit systems with regional transit agencies.
• Coordinate incident and threat information (as part of an early warning system) with RTMCs; regional emergency management agencies; regional maintenance and construction agencies; and regional transit agencies.
• Coordinate incident response and incident reports with Floridas SEOC, local EOCs, and FDOT District EOCs.
• Coordinate incident response and incident reports with the county sheriff, county fire/EMS, county EOC, local police, local fire/EMS, the FHP, and other public safety agencies.
• Develop and coordinate county/region wide emergency plans; evacuation and re-entry plans; and disaster management plans with regional emergency management agencies; traffic management agencies; transit management agencies; and maintenance and construction


• FDOT State Traffic Engineering and Operations Office
• Collect traffic information; incident information; multimodal information; maintenance and construction information; work zone information; and weather information, and provide it to the public via Florida 511 and private sector information providers
• Coordinate and share traveler information with Florida 511 and all private sector traveler ISPs in the state.
• Coordinate archiving information with other regional safety or crash data collection systems.
• Coordinate emergency information with state, county and local emergency management agencies.
• Coordinate maintenance information between FDOT TMCs and FDOT district, county and local maintenance divisions and private contractors.
• Coordinate traffic archive data with third party archive providers.
• Coordinate traffic information with archive data providers.
• Coordinate traffic information with county and local traffic control systems.
• Coordinate transit information with transit providers.
• Coordinate transportation information between FDOT and other Florida TMCs.
• Coordinate with commercial vehicle onboard safety and security monitors for driver logs, onboard safety information, and safety inspection records.
• Coordinate with private and third party information service providers.
• Coordinate with the FHP for enforcement of CVO violations.
• Distribute maintenance and construction information to Florida 511, FDOT TMCs, and private traveler information providers.
• Operate and monitor commercial vehicle platoons on FDOT highways.
• Provide commercial vehicle parking information to private fleet systems, the FTE operations centers, and the FDOT RTMCs.


• FDOT Districts
• Collects transportation data for each FDOT District for use in the associated system (e.g. databases, models, analytical tools, user interface devices) analyses with their tools.
• Manages and maintains a complete inventory of FDOT mobile resources, including generators and dynamic message signs.
• Operates and maintains SunGuide as a transportation management platform.


• County City and Local Traffic Engineering
• Coordinate road network conditions and incident information.


• FDOT Data Archiving
• Accesses SunGuide Data Archive data provided by SunGuide systems for a broad range of uses (e.g. planning, research, analysis, operations).