ITS Architecture Implementation Program
time lapse photo of traffic traveling down and exiting from a freeway at night
21st Century Operations Using 21st Century Technologies

Memphis Area Regional ITS Architecture

ITS Functional Requirements

Report Version 1.1

April 15, 2002

Prepared for the Tennessee Department of Transportation

Memphis Area ITS Functional Requirements

To effectively deliver ITS services in the Memphis area, each system must perform certain functions. A functional requirement can be written for each function that an element needs to perform. The lists below detail the primary functional requirements for the major ITS elements in the Memphis area. These requirements are high-level functional requirements, not detailed design requirements.

Stakeholder: Arkansas Highway Patrol
System: Arkansas Highway Patrol Dispatch

This system shall:

  • receive 9-1-1 and 7-digit local access calls.
  • collect available information about the caller and the reported emergency.
  • forward information on emergency about emergency to other systems that formulate and manage the emergency response.
  • collect and store emergency information that is collected in the course of emergency operations.
  • provide emergency data to operations personnel and other data users and archives in the region.
  • efficiently dispatch emergency vehicles to an incident.
  • provide safe and efficient routes based on real-time traffic information.
  • develop and store emergency response plans.
  • manage overall coordinated response to emergencies.
  • track the availability of resources and assist in the appropriate allocation of resources for a particular emergency response.
  • provide coordination between multiple allied agencies before and during emergencies to implement emergency response plans and track progress through the incident.
  • receive mayday messages, determine an appropriate response, and either use internal resources or contact a local agency to provide that response.

Stakeholder: Arkansas State Highway and Transportation Department
System: Arkansas Commercial Vehicle Administration

This system shall:

  • provide administrative capabilities including database management and administrator-to-roadside and administrator-to-administrator interfaces.
  • manage the electronic credentials database for a state, perform reconciliation of mileage and fuel taxes, and interface with roadsides performing credential checks.
  • communicate and coordinate with other state commercial vehicle administrations.
  • collect and store information on commercial vehicles.
  • make data available to other data users and archives in the region.
  • support the exchange of safety and credentials data among jurisdictions.
  • support the exchange of safety and credentials data between agencies (for example, an administrative center and the roadside check facilities) within a single jurisdiction.
  • collect data from multiple authoritative sources and package it into snapshots (top-level summary and critical status information) and profiles (detailed and historical data).
  • ensure that safety criteria are available for automated roadside safety checks.
  • collect and review carrier safety data and determine the carrier safety rating based on supplied criteria.

Stakeholder: Arkansas State Highway and Transportation Department
System: Arkansas Commercial Vehicle Field Equipment

This system shall:

  • document violations and forward the information to the commercial vehicle if available and to the commercial vehicle administration for processing as part of the normal credentials processing package.
  • communicate two-way with approaching properly equipped commercial vehicles at mainline speeds.
  • read tags for automated vehicle identification and credential checking.
  • appropriately screen all vehicles, not just those that are equipped.
  • process data from commercial vehicle along with database information to determine whether a pull-in message is needed.
  • generate random pull-in messages with provisions for facility operators and enforcement officials to have manual override capabilities.
  • automate the roadside safety inspection process including the use of hand held devices to rapidly inspect the vehicle and driver.
  • automate the roadside safety inspection process including the support of automated mainline speed reading of on-board safety data to rapidly screen the vehicle and driver.
  • collect, store, maintain, and provide safety data and access historical safety data after receiving identification from vehicles at mainline speeds or while stopped at the roadside.
  • write the results of screening and summary safety inspection back onto a tag.
  • process safety data and issue pull-in messages or provide warnings to the driver, carrier, and enforcement agencies.
  • support the concept of a last clearance event record (e.g. trip ticket) carried on the vehicle's tag.
  • perform roadside high speed weigh in motion.

Stakeholder: Arkansas State Highway and Transportation Department
System: Arkansas TMC

This system shall:

  • collect, store, and provide electronic access to traffic surveillance data.
  • control systems for efficient freeway management including integration of surveillance information with freeway geometry, vehicle control such as ramp metering, DMS, and HAR.
  • interface to coordinated traffic systems for information dissemination to the public.
  • detect and verify incidents.
  • analyze and reduce collected data from traffic surveillance equipment, including planned incidents and hazardous conditions.
  • formulate an incident response minimizing the incident potential, incident impacts, and/or resources required for incident management.
  • propose and facilitate the dispatch of emergency response and service vehicles as well as coordinate response with all appropriate agencies.
  • analyze, control, and optimize area-wide traffic flow.
  • perform wide area optimization integrating control of a network signal system with control of freeway, considering current demand as well as expected demand with a goal of providing traffic adaptive control while balancing inter-jurisdictional control issues to achieve regional solutions.
  • communicate with other TMCs to receive and transmit traffic information to other jurisdictions within the region.
  • collect and store traffic information that is collected in the course of traffic operations.
  • provide traffic data to operations personnel or other data users and archives in the region.
  • monitor and diagnosis field equipment remotely to detect failures, issue problem reports, and track the repair or replacement of the failed equipment.

Stakeholder: Center City Commission
System: Center City Downtown Parking System

This system shall:

  • collect and store parking information that is collected in the course of parking system operations.
  • provide parking data to operations personnel or other data users and archives in the region.
  • support electronic payment of parking fees.
  • detect and classify properly equipped vehicles entering and exiting the parking facility
  • maintain information on parking availability and pricing structure information.
  • enable processing of financial transactions and external coordination.
  • detect and classify vehicles entering and exiting the parking facility.
  • measure parking facility occupancy to support parking operations and traveler information services.

Stakeholder: City of Bartlett Traffic Department
System: City of Bartlett TCC

This system shall:

  • collect, store, and provide electronic access to traffic surveillance data.
  • monitor highway-rail intersection (HRI) equipment at the roadside which manages highway traffic.
  • receive additional information on approaching trains and detect and report obstructions in the HRI.
  • remotely monitor and report the status of the roadside equipment.
  • generate status requests and remote control plan updates.
  • receive periodic status updates in the absence of a request or asynchronously in the event of a detected failure or other unsafe condition at the intersection.
  • detect and verify incidents.
  • analyze and reduce collected data from traffic surveillance equipment, including planned incidents and hazardous conditions.
  • formulate an incident response minimizing the incident potential, incident impacts, and/or resources required for incident management.
  • propose and facilitate the dispatch of emergency response and service vehicles as well as coordinate response with all appropriate agencies.
  • analyze, control, and optimize area-wide traffic flow.
  • perform wide area optimization integrating control of a network signal system with control of freeway, considering current demand as well as expected demand with a goal of traffic adaptive control while balancing inter-jurisdictional control issues to achieve regional solutions.
  • communicate with other TMCs to receive and transmit traffic information to other jurisdictions within the region.
  • monitor and manage the traffic flow at signalized intersections.
  • analyze and reduce the collected data from traffic surveillance equipment and develop and implement control plans for signalized intersections.
  • develop and implement control plans that coordinate signals at many intersections.
  • disseminate incident related information to travelers, potential travelers, and private information service providers.
  • collect and store traffic information that is collected in the course of traffic operations.
  • provide traffic data to operations personnel or other data users and archives in the region.
  • monitor and diagnosis field equipment remotely to detect failures, issue problem reports, and track the repair or replacement of the failed equipment.
  • notify utility company of problems with utilities.

Stakeholder: City of Bartlett Traffic Department
System: City of Bartlett Traffic Field Equipment

This system shall:

  • monitor traffic flow.
  • monitor surveillance equipment and interfaces and report detected abnormalities.
  • control traffic signals.
  • receive vehicle signal priority requests and send requests to traffic signal controllers accordingly.
  • monitor the traffic signal equipment and interfaces and report detected abnormalities.
  • display traffic information on equipment along the roadway including DMS and HAR.
  • monitor DMS and HAR equipment and interfaces and report detected abnormalities.
  • manage highway traffic at highway-rail intersections (HRIs).
  • provide pre-emption of adjacent signalized intersections when activated on notification by interfaced wayside equipment of an approaching train.
  • monitor the HRI equipment and interfaces and report detected abnormalities through the wayside equipment and traffic management center.

Stakeholder: City of Bartlett Public Works Department
System: City of Bartlett Public Works

This system shall:

  • respond to resource request.
  • send response to requesting agency.
  • notify transportation and emergency agencies of planned construction and street closures.

Stakeholder: City of Collierville Traffic Department
System: City of Collierville TCC

This system shall:

  • collect, store, and provide electronic access to traffic surveillance data.
  • monitor highway-rail intersection (HRI) equipment at the roadside which manages highway traffic.
  • receive additional information on approaching trains and detect and report obstructions in the HRI.
  • remotely monitor and report the status of the roadside equipment.
  • generate status requests and remote control plan updates.
  • receive periodic status updates in the absence of a request or asynchronously in the event of a detected failure or other unsafe condition at the intersection.
  • detect and verify incidents.
  • analyze and reduce collected data from traffic surveillance equipment, including planned incidents and hazardous conditions.
  • formulate an incident response minimizing the incident potential, incident impacts, and/or resources required for incident management.
  • propose and facilitate the dispatch of emergency response and service vehicles as well as coordinate response with all appropriate agencies.
  • analyze, control, and optimize area-wide traffic flow.
  • perform wide area optimization integrating control of a network signal system with control of freeway, considering current demand as well as expected demand with a goal of traffic adaptive control while balancing inter-jurisdictional control issues to achieve regional solutions.
  • communicate with other TMCs to receive and transmit traffic information to other jurisdictions within the region.
  • monitor and manage the traffic flow at signalized intersections.
  • analyze and reduce the collected data from traffic surveillance equipment and develop and implement control plans for signalized intersections.
  • develop and implement control plans that coordinate signals at many intersections.
  • disseminate incident related information to travelers, potential travelers, and private information service providers.
  • collect and store traffic information that is collected in the course of traffic operations.
  • provide traffic data to operations personnel or other data users and archives in the region.
  • monitor and diagnosis field equipment remotely to detect failures, issue problem reports, and track the repair or replacement of the failed equipment.

Stakeholder: City of Collierville Traffic Department
System: City of Collierville Traffic Field Equipment

This system shall:

  • monitor traffic flow.
  • monitor surveillance equipment and interfaces and report detected abnormalities.
  • control traffic signals.
  • receive vehicle signal priority requests and send requests to traffic signal controllers accordingly.
  • monitor the traffic signal equipment and interfaces and report detected abnormalities.
  • display traffic information on equipment along the roadway including DMS and HAR.
  • monitor DMS and HAR equipment and interfaces and report detected abnormalities.
  • manage highway traffic at highway-rail intersections (HRIs).
  • provide pre-emption of adjacent signalized intersections when activated on notification by interfaced wayside equipment of an approaching train.
  • monitor the HRI equipment and interfaces and report detected abnormalities through the wayside equipment and traffic management center.

Stakeholder: City of Collierville Public Works Department
System: City of Collierville Public Works

This system shall:

  • respond to resource request.
  • send response to requesting agency.
  • notify transportation and emergency agencies of planned construction and street closures.

Stakeholder: City of Germantown Traffic Department
System: City of Germantown TCC

This system shall:

  • monitor highway-rail intersection (HRI) equipment at the roadside which manages highway traffic.
  • receive additional information on approaching trains and detect and report obstructions in the HRI.
  • remotely monitor and report the status of the roadside equipment.
  • generate status requests and remote control plan updates.
  • receive periodic status updates in the absence of a request or asynchronously in the event of a detected failure or other unsafe condition at the intersection.
  • detect and verify incidents.
  • analyze and reduce collected data from traffic surveillance equipment, including planned incidents and hazardous conditions.
  • formulate an incident response minimizing the incident potential, incident impacts, and/or resources required for incident management.
  • propose and facilitate the dispatch of emergency response and service vehicles as well as coordinate response with all appropriate agencies.
  • analyze, control, and optimize area-wide traffic flow.
  • perform wide area optimization integrating control of a network signal system with control of freeway, considering current demand as well as expected demand with a goal of traffic adaptive control while balancing inter-jurisdictional control issues to achieve regional solutions.
  • communicate with other TMCs to receive and transmit traffic information to other jurisdictions within the region.
  • monitor and manage the traffic flow at signalized intersections.
  • analyze and reduce the collected data from traffic surveillance equipment and develop and implement control plans for signalized intersections.
  • develop and implement control plans that coordinate signals at many intersections.
  • disseminate incident related information to travelers, potential travelers, and private information service providers.
  • collect and store traffic information that is collected in the course of traffic operations.
  • provide traffic data to operations personnel or other data users and archives in the region.
  • monitor and diagnosis field equipment remotely to detect failures, issue problem reports, and track the repair or replacement of the failed equipment.

Stakeholder: City of Germantown Traffic Department
System: City of Germantown Traffic Field Equipment

This system shall:

  • monitor traffic flow.
  • monitor surveillance equipment and interfaces and report detected abnormalities.
  • control traffic signals.
  • receive vehicle signal priority requests and send requests to traffic signal controllers accordingly.
  • monitor the traffic signal equipment and interfaces and report detected abnormalities.
  • display traffic information on equipment along the roadway including DMS and HAR.
  • monitor DMS and HAR equipment and interfaces and report detected abnormalities.
  • manage highway traffic at highway-rail intersections (HRIs).
  • provide pre-emption of adjacent signalized intersections when activated on notification by interfaced wayside equipment of an approaching train.
  • monitor the HRI equipment and interfaces and report detected abnormalities through the wayside equipment and traffic management center.

Stakeholder: City of Germantown Public Works Department
System: City of Germantown Public Works

This system shall:

  • respond to resource request.
  • send response to requesting agency.
  • notify transportation and emergency agencies of planned construction and street closures.

Stakeholder: MATA
System: MATA Automated Call Center

This system shall:

  • collect, process, store, and disseminate transit traveler information.
  • maintain a database of local area transit services available to travelers with up-to-the-minute information.
  • include the latest available information on transit routes and schedules, transit transfer options, transit fares, and real-time schedule adherence.
  • provide users with real-time travel related information en-route to assist the travelers in making decisions about transfers and modification of trips.
  • provide interactive traveler information.

Stakeholder: MATA
System: MATA Fixed Route Vehicles

This system shall:

  • automate planning and scheduling by collecting data for schedule generation.
  • automatically determine optimum scenarios for schedule adjustment.
  • support two-way voice communication between the transit vehicle driver and a facility, two-way data communication between the transit vehicles and a facility, on-board safety sensor data to be transmitted from the transit vehicles to a facility, and data transmission from individual facilities to a central facility for processing/analysis.
  • use transit vehicle mileage data to automatically generate preventative maintenance schedules for each bus by utilizing vehicle tracking data and storing with a trip computer.
  • monitor on board the vehicle in real-time, and transmit information via two-way communication to the management center.
  • collect data required to determine accurate ridership levels and implement variable and flexible fare structures.
  • support use of a fare medium for all applicable surface transportation services, allow the traveler to pay without stopping, have payment media automatically identified as void and/or invalid and eligibility verified, and allow for third party payment.
  • provide expansion into other uses for payment medium such as retail and telephone and for off-line billing for fares paid by agencies shall be supported.
  • support two-way voice communication between the transit vehicle driver and a facility, two-way data communication between the transit vehicles and a facility, sensor data to be transmitted from the transit vehicles to a facility, and data transmission from individual facilities to a central facility for processing/analysis if desired.
  • monitor the safety of transit vehicles using on-board safety sensors, processors and communications from on-board system.
  • support fleet management with automated mileage and fuel reporting and auditing.
  • request signal priority from equipment on the roadside.
  • track transit vehicle and transmit location to dispatch.

Stakeholder: MATA
System: MATA Light Rail Vehicles

This system shall:

  • use transit vehicle mileage data to automatically generate preventative maintenance schedules for each bus by utilizing vehicle tracking data and storing with a trip computer.
  • monitor on board the vehicle in real-time, and transmit information via two-way communication to the management center.
  • collect data required to determine accurate ridership levels and implement variable and flexible fare structures.
  • support use of a fare medium for all applicable surface transportation services, allow the traveler to pay without stopping, have payment media automatically identified as void and/or invalid and eligibility verified, and allow for third party payment.
  • provide expansion into other uses for payment medium such as retail and telephone and for off-line billing for fares paid by agencies shall be supported.
  • support two-way voice communication between the transit vehicle driver and a facility, two-way data communication between the transit vehicles and a facility, sensor data to be transmitted from the transit vehicles to a facility, and data transmission from individual facilities to a central facility for processing/analysis if desired.
  • monitor the safety of transit vehicles using on-board safety sensors, processors and communications from on-board system.
  • support fleet management with automated mileage and fuel reporting and auditing.
  • request signal priority from equipment on the roadside.
  • track transit vehicle and transmit location to dispatch.

Stakeholder: MATA
System: MATA Plus Vehicles

This system shall:

  • use transit vehicle mileage data to automatically generate preventative maintenance schedules for each bus by utilizing vehicle tracking data and storing with a trip computer.
  • monitor on board the vehicle in real-time, and transmit information via two-way communication to the management center.
  • forward paratransit dispatch requests to the driver and forward acknowledgements to the center.
  • assist the driver in managing multi-stop runs associated with demand responsive, flexibly routed transit services.
  • collect data required to determine accurate ridership levels and implement variable and flexible fare structures.
  • support use of a fare medium for all applicable surface transportation services, allow the traveler to pay without stopping, have payment media automatically identified as void and/or invalid and eligibility verified, and allow for third party payment.
  • provide expansion into other uses for payment medium such as retail and telephone and for off-line billing for fares paid by agencies shall be supported.
  • support two-way voice communication between the transit vehicle driver and a facility, two-way data communication between the transit vehicles and a facility, sensor data to be transmitted from the transit vehicles to a facility, and data transmission from individual facilities to a central facility for processing/analysis if desired.
  • monitor the safety of transit vehicles using on-board safety sensors, processors and communications from on-board system.
  • support fleet management with automated mileage and fuel reporting and auditing.
  • track transit vehicle and transmit location to dispatch.

Stakeholder: MATA
System: MATA Transit Management Center

This system shall:

  • accept collected data required to determine accurate ridership levels and implement variable and flexible fare structures.
  • support use of a fare medium for all applicable surface transportation services, have payment media automatically identified as void and/or invalid and eligibility verified, and allow for third party payment.
  • allow two-way voice communication between the transit vehicle driver and a facility, two-way data communication between the transit vehicles and a facility, sensor data to be transmitted from the transit vehicles to a facility, and data transmission from individual facilities to a central facility for processing/analysis.
  • allow fixed-route services to develop, print and disseminate schedules and automatically update customer service operator systems with the most current schedule information.
  • use current vehicle schedule adherence and optimum scenarios for schedule adjustment.
  • collect the latest available information for a transit service and make it available to transit customers and to Information Service Providers for further distribution.
  • provide information to customers at transit stops and other public transportation areas before they embark and on-board the transit vehicle once they are enroute.
  • provide information including the latest available information on transit routes, schedules, transfer options, fares, real-time schedule adherence, current incidents, weather conditions, and special events.
  • provide tailored information (e.g, itineraries) to individual transit users when requested.
  • support schedule coordination between transit properties and coordinates with other surface and air transportation modes.
  • monitor key transit locations and transit vehicles with both video and audio systems automatically alerting operators and police of potential incidents.
  • support traveler activated alarms including responding to terrorist incidents.
  • monitor transit vehicle locations and determine vehicle schedule adherence.
  • furnish users with real-time travel related information, continuously updated with real-time information from each transit system within the local area of jurisdiction, inclusive of all transportation modes, from all providers of transportation services, and provide users with the latest available information on transit routes, schedules, transfer options, fares, real-time schedule adherence, current incidents conditions, weather conditions, and special events.
  • support two-way voice communication between the transit vehicle driver and a facility, two-way data communication between the transit vehicles and a facility.
  • collect and store transit information that is collected in the course of transit operations.
  • provide transit data to operations personnel or other data users and archives in the region.
  • provide advanced maintenance functions for the transit property.
  • collect operational and maintenance data from transit vehicles, manages vehicle service histories, and monitors drivers and vehicles.
  • collect vehicle mileage data and use it to automatically generate preventative maintenance schedules for each vehicle by utilizing vehicle tracking data from a prerequisite vehicle tracking equipment package.
  • provide information to proper service personnel to support maintenance activities and records and verify that maintenance work was performed.
  • receive special events and real-time incident data from the traffic management center and assigns operators to vehicles and transit routes.
  • receive information about incidents involving transit vehicles from the Transit Management system in order to dispatch tow trucks and other repair vehicles.
  • automate and support the assignment of transit vehicles and drivers to enhance the daily operation of a transit service.
  • assign drivers to routes or service areas in a fair manner while minimizing labor and overtime services, considering driver preferences and qualifications, and automatically tracking and validating the number of work hours performed by each driver.

Stakeholder: MATA
System: MATA Transit Website Server

This system shall:

  • collect, process, store, and disseminate transit traveler information.
  • maintain a database of local area transit services available to travelers with up-to-the-minute information.
  • include the latest available information on transit routes and schedules, transit transfer options, transit fares, and real-time schedule adherence.
  • provide users with real-time travel related information en-route to assist the travelers in making decisions about transfers and modification of trips.
  • provide interactive traveler information.

Stakeholder: MATA
System: MATA Traveler Info Kiosks

This system shall:

  • send formatted traffic advisories including accurate traveling information concerning available travel options and their availability, and congestion information at kiosks.
  • accept a common fare medium for all applicable surface transportation services, to pay without stopping, have payment media automatically identified as void and/or invalid and eligibility verified.
  • provide real-time travel-related information to transit users at transit stops, multi-modal transfer points, and other public transportation areas.
  • provide the latest available information on transit routes, schedules, transfer options, fares, real-time schedule adherence, and special events.
  • supports general annunciation and/or display of imminent arrival information and other information of general interest to transit users.
  • provide information tailored for individual transit users.

Stakeholder: Memphis City Fire Services
System: Memphis City Fire Dispatch

This system shall:

  • receive transferred emergency calls.
  • collect available information about the caller and the reported emergency.
  • forward information on emergency on emergency to other systems that formulate and manage the emergency response.
  • collect and store emergency information that is collected in the course of emergency operations.
  • provide emergency data to operations personnel and other data users and archives in the region.
  • efficiently dispatch emergency vehicles to an incident.
  • track emergency vehicles.
  • provide safe and efficient routes based on real-time traffic information.
  • develop and store emergency response plans.
  • manage overall coordinated response to emergencies.
  • track the availability of resources and assist in the appropriate allocation of resources for a particular emergency response.
  • provide coordination between multiple allied agencies before and during emergencies to implement emergency response plans and track progress through the incident.

Stakeholder: Memphis City Fire Services
System: Memphis City Fire Vehicles

This system shall:

  • provide dispatch and routing information.
  • track fire vehicle and transmit location to dispatch.
  • preempt signals via short range communication directly with traffic control equipment at the roadside.
  • provide safe and expedient arrival on the incident scene.
  • provide a direct interface between the emergency vehicle and incident management personnel.

Stakeholder: Memphis City Police Department
System: Memphis City Police Dispatch

This system shall:

  • receive 9-1-1 and 7-digit local access.
  • transfer emergency calls to appropriate system.
  • collect available information about the caller and the reported emergency.
  • forward information on emergency to other systems that formulate and manage the emergency response.
  • collect and store emergency information that is collected in the course of emergency operations.
  • provide emergency data to operations personnel and other data users and archives in the region.
  • efficiently dispatch emergency vehicles to an incident.
  • provide safe and efficient routes based on real-time traffic information.
  • develop and store emergency response plans.
  • manage overall coordinated response to emergencies.
  • track the availability of resources and assist in the appropriate allocation of resources for a particular emergency response.
  • provide coordination between multiple allied agencies before and during emergencies to implement emergency response plans and track progress through the incident.
  • receive mayday messages, determine an appropriate response, and either use internal resources or contact a local agency to provide that response.

Stakeholder: Memphis City Police Department
System: Memphis City Police Vehicles

This system shall:

  • provide dispatch and routing information.
  • provide safe and expedient arrival on the incident scene.
  • provide a direct interface between the emergency vehicle and incident management personnel.

Stakeholder: Memphis City Police Department
System: MPD Special Events System

This system shall:

  • collect, store and provide planned events that might impact traffic.
  • collect, store and provide planned road closures.

Stakeholder: Memphis City Traffic Department
System: Memphis City TOC

This system shall:

  • collect, store, and provide electronic access to traffic surveillance data.
  • monitor highway-rail intersection (HRI) equipment at the roadside which manages highway traffic.
  • receive additional information on approaching trains and detect and report obstructions in the HRI.
  • remotely monitor and report the status of the roadside equipment.
  • generate status requests and remote control plan updates.
  • receive periodic status updates in the absence of a request or asynchronously in the event of a detected failure or other unsafe condition at the intersection.
  • detect and verify incidents.
  • analyze and reduce collected data from traffic surveillance equipment, including planned incidents and hazardous conditions.
  • formulate an incident response minimizing the incident potential, incident impacts, and/or resources required for incident management.
  • propose and facilitate the dispatch of emergency response and service vehicles as well as coordinate response with all appropriate agencies.
  • provide traffic signal priority for transit vehicles.
  • analyze, control, and optimize area-wide traffic flow.
  • perform wide area optimization integrating control of a network signal system with control of freeway, considering current demand as well as expected demand with a goal of traffic adaptive control while balancing inter-jurisdictional control issues to achieve regional solutions.
  • communicate with other TMCs to receive and transmit traffic information to other jurisdictions within the region.
  • monitor and manage the traffic flow at signalized intersections.
  • analyze and reduce the collected data from traffic surveillance equipment and develop and implement control plans for signalized intersections.
  • develop and implement control plans that coordinate signals at many intersections.
  • disseminate incident related information to travelers, potential travelers, and private information service providers.
  • collect and store traffic information that is collected in the course of traffic operations.
  • provide traffic data to operations personnel or other data users and archives in the region.
  • monitor and diagnosis field equipment remotely to detect failures, issue problem reports, and track the repair or replacement of the failed equipment.

Stakeholder: Memphis City Traffic Department
System: Memphis City Traffic Field Equipment

This system shall:

  • monitor traffic flow.
  • control traffic signals.
  • provide pre-emption of adjacent signalized intersections.
  • receive vehicle signal priority requests and send requests to traffic signal controllers accordingly.
  • display traffic information on equipment along the roadway including DMS and HAR.
  • manage highway traffic at highway-rail intersections (HRIs) when activated on notification by interfaced wayside equipment of an approaching train.
  • accept additional information about the arriving train from the wayside equipment so that the train's direction of travel, its estimated time of arrival, and the estimated duration of closure may be derived.
  • convey information to the driver prior to, or in context with, warning system activation.
  • detect an entrapped or otherwise immobilized vehicle within the HRI and provide an immediate notification to the wayside interface equipment and traffic management.
  • monitor the HRI equipment and interfaces and report detected abnormalities through the wayside equipment and traffic management center.

Stakeholder: Memphis MPO
System: Memphis MPO Archive

This system shall:

  • collect data from multiple data sources.
  • store data in a focused repository.
  • perform quality checks on the incoming data, error notification, and archive to archive coordination.
  • collect a focused set of data and serve a particular user community.
  • collect, integrate, and summarize transportation data from multiple sources and serve a broad array of users within a region.
  • provide advanced data analysis, summarization, and mining features that facilitate discovery of information, patterns, and correlations in large data sets.
  • collect and archive traffic, roadway, and environmental information for use in off-line planning, research, and analysis.

Stakeholder: Memphis-Shelby County Emergency Operations Center
System: Memphis-Shelby County EMA System

This system shall:

  • collect and store emergency information that is collected in the course of emergency operations.
  • provide emergency data to operations personnel and other data users and archives in the region.
  • efficiently dispatch emergency vehicles to an incident.
  • provide safe and efficient routes based on real-time traffic information.
  • develop and store emergency response plans.
  • manage overall coordinated response to emergencies.
  • track the availability of resources and assist in the appropriate allocation of resources for a particular emergency response.
  • provide coordination between multiple allied agencies before and during emergencies to implement emergency response plans and track progress through the incident.

Stakeholder: Memphis-Shelby County Health Department
System: Memphis-Shelby County Emissions Management System

This system shall:

  • collect and store air quality and emissions information.
  • provide air quality and emissions data to operations personnel or other data users and archives in the region.
  • assimilate and store air quality measures and roadside collected emissions data.
  • distribute general air quality measures as general traveler information and to other agencies in the region.
  • analyze the collected roadside emissions to detect, identify, and notify concerned parties regarding vehicles that exceed emissions standards.

Stakeholder: Memphis-Shelby County Health Department
System: Memphis-Shelby County Emissions Sensors

This system shall:

  • monitor emissions and general air quality and communicate the collected information back to the emissions management system where it can be monitored, analyzed, and used.
  • support point monitoring of individual vehicle emissions as well as general monitoring of standard air quality measures.

Stakeholder: Memphis-Shelby County Planning and Development
System: Memphis Area Rideshare

This system shall:

  • collect, process, store, and disseminate traveler ridematching information.
  • maintain a database of travelers and their work routes and provide connectivity between travelers taking similar routes.
  • provide dynamic rideshare matches including rider and driver information and reservations.
  • collect and store traveler information that is collected in the course of ridematching operation.
  • provide ridematching data to operations personnel or other data users and archives in the region.

Stakeholder: Mississippi DOT
System: Mississippi Commercial Vehicle Administration

This system shall:

  • provide administrative capabilities including database management and administrator-to-roadside and administrator-to-administrator interfaces.
  • manage the electronic credentials database for a state, perform reconciliation of mileage and fuel taxes, and interface with roadsides performing credential checks.
  • communicate and coordinate with other state commercial vehicle administrations.
  • collect and store information on commercial vehicles.
  • make data available to other data users and archives in the region.
  • support the exchange of safety and credentials data among jurisdictions.
  • support the exchange of safety and credentials data between agencies (for example, an administrative center and the roadside check facilities) within a single jurisdiction.
  • collect data from multiple authoritative sources and package it into snapshots (top-level summary and critical status information) and profiles (detailed and historical data).
  • ensure that safety criteria are available for automated roadside safety checks.
  • collect and review carrier safety data and determine the carrier safety rating based on supplied criteria.

Stakeholder: Mississippi DOT
System: Mississippi Commercial Vehicle Field Equipment

This system shall:

  • document violations and forward the information to the commercial vehicle if available and to the commercial vehicle administration for processing as part of the normal credentials processing package.
  • communicate two-way with approaching properly equipped commercial vehicles at mainline speeds.
  • read tags for automated vehicle identification and credential checking.
  • appropriately screen all vehicles, not just those that are equipped.
  • process data from commercial vehicle along with database information to determine whether a pull-in message is needed.
  • generate random pull-in messages with provisions for facility operators and enforcement officials to have manual override capabilities.
  • automate the roadside safety inspection process including the use of hand held devices to rapidly inspect the vehicle and driver.
  • automate the roadside safety inspection process including the support of automated mainline speed reading of on-board safety data to rapidly screen the vehicle and driver.
  • collect, store, maintain, and provide safety data and access historical safety data after receiving identification from vehicles at mainline speeds or while stopped at the roadside.
  • write the results of screening and summary safety inspection back onto a tag.
  • process safety data and issue pull-in messages or provide warnings to the driver, carrier, and enforcement agencies.
  • support the concept of a last clearance event record (e.g. trip ticket) carried on the vehicle's tag.
  • perform roadside high speed weigh in motion.

Stakeholder: Mississippi DOT
System: Mississippi TMC

This system shall:

  • collect, store, and provide electronic access to traffic surveillance data.
  • control systems for efficient freeway management including integration of surveillance information with freeway geometry, vehicle control such as ramp metering, DMS, and HAR.
  • Interface to coordinated traffic systems for information dissemination to the public.
  • detect and verify incidents.
  • analyze and reduce collected data from traffic surveillance equipment, including planned incidents and hazardous conditions.
  • formulate an incident response minimizing the incident potential, incident impacts, and/or resources required for incident management.
  • propose and facilitate the dispatch of emergency response and service vehicles as well as coordinate response with all appropriate agencies.
  • analyze, control, and optimize area-wide traffic flow.
  • perform wide area optimization integrating control of a network signal system with control of freeway, considering current demand as well as expected demand with a goal of traffic adaptive control while balancing inter-jurisdictional control issues to achieve regional solutions.
  • communicate with other TMCs to receive and transmit traffic information to other jurisdictions within the region.
  • collect and store traffic information that is collected in the course of traffic operations.
  • provide traffic data to operations personnel or other data users and archives in the region.
  • monitor and diagnosis field equipment remotely to detect failures, issue problem reports, and track the repair or replacement of the failed equipment.

Stakeholder: Mississippi Highway Patrol
System: Mississippi Highway Patrol Dispatch

This system shall:

  • receive 9-1-1 and 7-digit local access calls.
  • collect available information about the caller and the reported emergency.
  • forward information on emergency about emergency to other systems that formulate and manage the emergency response.
  • collect and store emergency information that is collected in the course of emergency operations.
  • · provide emergency data to operations personnel and other data users and archives in the region.
  • efficiently dispatch emergency vehicles to an incident.
  • provide safe and efficient routes based on real-time traffic information.
  • develop and store emergency response plans.
  • manage overall coordinated response to emergencies.
  • track the availability of resources and assist in the appropriate allocation of resources for a particular emergency response.
  • provide coordination between multiple allied agencies before and during emergencies to implement emergency response plans and track progress through the incident.
  • receive mayday messages, determine an appropriate response, and either use internal resources or contact a local agency to provide that response.

Stakeholder: Mississippi Municipalities
System: Mississippi Municipal TCC

This system shall:

  • collect, store, and provide electronic access to traffic surveillance data.
  • monitor highway-rail intersection (HRI) equipment at the roadside which manages highway traffic.
  • receive additional information on approaching trains and detect and report obstructions in the HRI.
  • remotely monitor and report the status of the roadside equipment.
  • generate status requests and remote control plan updates.
  • receive periodic status updates in the absence of a request or asynchronously in the event of a detected failure or other unsafe condition at the intersection.
  • detect and verify incidents.
  • analyze and reduce collected data from traffic surveillance equipment, including planned incidents and hazardous conditions.
  • formulate an incident response minimizing the incident potential, incident impacts, and/or resources required for incident management.
  • propose and facilitate the dispatch of emergency response and service vehicles as well as coordinate response with all appropriate agencies.
  • analyze, control, and optimize area-wide traffic flow.
  • perform wide area optimization integrating control of a network signal system with control of freeway, considering current demand as well as expected demand with a goal of traffic adaptive control while balancing inter-jurisdictional control issues to achieve regional solutions.
  • communicate with other TMCs to receive and transmit traffic information to other jurisdictions within the region.
  • monitor and manage the traffic flow at signalized intersections.
  • analyze and reduce the collected data from traffic surveillance equipment and develop and implement control plans for signalized intersections.
  • develop and implement control plans that coordinate signals at many intersections.
  • disseminate incident related information to travelers, potential travelers, and private information service providers.
  • collect and store traffic information that is collected in the course of traffic operations.
  • provide traffic data to operations personnel or other data users and archives in the region.
  • monitor and diagnosis field equipment remotely to detect failures, issue problem reports, and track the repair or replacement of the failed equipment.

Stakeholder: Municipal Fire Prevention Bureau
System: Municipal Fire Dispatch

This system shall:

  • receive 9-1-1 and 7-digit local access.
  • collect available information about the caller and the reported emergency.
  • forward information on emergency to other systems that formulate and manage the emergency response.
  • collect and store emergency information that is collected in the course of emergency operations.
  • provide emergency data to operations personnel and other data users and archives in the region.
  • efficiently dispatch emergency vehicles to an incident.
  • provide safe and efficient routes based on real-time traffic information.
  • develop and store emergency response plans.
  • manage overall coordinated response to emergencies.
  • track the availability of resources and assist in the appropriate allocation of resources for a particular emergency response.
  • provide coordination between multiple allied agencies before and during emergencies to implement emergency response plans and track progress through the incident.

Stakeholder: Municipal Fire Prevention Bureau
System: Municipal Fire Vehicles

This system shall:

  • provide dispatch and routing information.
  • preempt signals via short range communication directly with traffic control equipment at the roadside.
  • provide safe and expedient arrival on the incident scene.
  • provide a direct interface between the emergency vehicle and incident management personnel.

Stakeholder: Municipal Police Department
System: Municipal Police Dispatch

This system shall:

  • receive 9-1-1 and 7-digit local access.
  • collect available information about the caller and the reported emergency.
  • forward information on emergency on emergency to other systems that formulate and manage the emergency response.
  • collect and store emergency information that is collected in the course of emergency operations.
  • provide emergency data to operations personnel and other data users and archives in the region.
  • efficiently dispatch emergency vehicles to an incident.
  • provide safe and efficient routes based on real-time traffic information.
  • develop and store emergency response plans.
  • manage overall coordinated response to emergencies.
  • track the availability of resources and assist in the appropriate allocation of resources for a particular emergency response.
  • provide coordination between multiple allied agencies before and during emergencies to implement emergency response plans and track progress through the incident.
  • receive mayday messages, determine an appropriate response, and either use internal resources or contact a local agency to provide that response.

Stakeholder: Municipal Police Department
System: Municipal Police Vehicles

This system shall:

  • provide dispatch and routing information.
  • preempt signals via short range communication directly with traffic control equipment at the roadside.
  • provide safe and expedient arrival on the incident scene.
  • provide a direct interface between the emergency vehicle and incident management personnel.

Stakeholder: Shelby County Engineering
System: Shelby County TCC

This system shall:

  • monitor and manage the traffic flow at signalized intersections.
  • communicate with other TMCs to receive and transmit traffic information to other jurisdictions within the region.
  • monitor highway-rail intersection (HRI) equipment at the roadside which manages highway traffic.
  • receive additional information on approaching trains and detect and report obstructions in the HRI.
  • remotely monitor and report the status of the roadside equipment.
  • generate status requests and remote control plan updates.
  • receive periodic status updates in the absence of a request or asynchronously in the event of a detected failure or other unsafe condition at the intersection.
  • detect and verify incidents.
  • analyze and reduce collected data from traffic surveillance equipment, including planned incidents and hazardous conditions.
  • formulate an incident response minimizing the incident potential, incident impacts, and/or resources required for incident management.
  • propose and facilitate the dispatch of emergency response and service vehicles as well as coordinate response with all appropriate agencies.
  • analyze, control, and optimize area-wide traffic flow.
  • perform wide area optimization integrating control of a network signal system with control of freeway, considering current demand as well as expected demand with a goal of traffic adaptive control while balancing inter-jurisdictional control issues to achieve regional solutions.
  • analyze and reduce the collected data from traffic surveillance equipment and develop and implement control plans for signalized intersections.
  • develop and implement control plans that coordinate signals at many intersections.
  • disseminate incident related information to travelers, potential travelers, and private information service providers.
  • collect and store traffic information that is collected in the course of traffic operations.
  • provide traffic data to operations personnel or other data users and archives in the region.
  • monitor and diagnosis field equipment remotely to detect failures, issue problem reports, and track the repair or replacement of the failed equipment.

Stakeholder: Shelby County Engineering
System: Shelby County Traffic Field Equipment

This system shall:

  • monitor traffic flow.
  • monitor surveillance equipment and interfaces and report detected abnormalities.
  • control traffic signals.
  • receive vehicle signal priority requests and send requests to traffic signal controllers accordingly.
  • monitor the traffic signal equipment and interfaces and report detected abnormalities.
  • display traffic information on equipment along the roadway including DMS and HAR.
  • monitor DMS and HAR equipment and interfaces and report detected abnormalities.
  • manage highway traffic at highway-rail intersections (HRIs).
  • provide pre-emption of adjacent signalized intersections when activated on notification by interfaced wayside equipment of an approaching train.
  • monitor the HRI equipment and interfaces and report detected abnormalities through the wayside equipment and traffic management center.

Stakeholder: Shelby County Fire Department
System: Shelby County Fire Dispatch

This system shall:

  • receive transferred emergency calls.
  • collect available information about the caller and the reported emergency.
  • forward information on emergency on emergency to other systems that formulate and manage the emergency response.
  • collect and store emergency information that is collected in the course of emergency operations.
  • provide emergency data to operations personnel and other data users and archives in the region.
  • efficiently dispatch emergency vehicles to an incident.
  • provide safe and efficient routes.
  • develop and store emergency response plans.
  • manage overall coordinated response to emergencies.
  • track the availability of resources and assist in the appropriate allocation of resources for a particular emergency response.
  • provide coordination between multiple allied agencies before and during emergencies to implement emergency response plans and track progress through the incident.

Stakeholder: Shelby County Fire Department
System: Shelby County Fire Vehicles

This system shall:

  • provide dispatch and routing information.
  • provide safe and expedient arrival on the incident scene.
  • provide a direct interface between the emergency vehicle and incident management personnel.

Stakeholder: Shelby Public Works Department
System: Shelby County Public Works

This system shall:

  • respond to resource request.
  • send response to requesting agency.
  • notify transportation and emergency agencies of planned construction and street closures.

Stakeholder: Shelby County Sheriff Department
System: Shelby County Sheriff Dispatch

This system shall:

  • receive 9-1-1 and 7-digit local access.
  • transfer emergency calls to appropriate system.
  • collect available information about the caller and the reported emergency.
  • forward information on emergency to other systems that formulate and manage the emergency response.
  • collect and store emergency information that is collected in the course of emergency operations.
  • provide emergency data to operations personnel and other data users and archives in the region.
  • efficiently dispatch emergency vehicles to an incident.
  • provide safe and efficient routes based on real-time traffic information.
  • develop and store emergency response plans.
  • manage overall coordinated response to emergencies.
  • track the availability of resources and assist in the appropriate allocation of resources for a particular emergency response.
  • provide coordination between multiple allied agencies before and during emergencies to implement emergency response plans and track progress through the incident.
  • receive mayday messages, determine an appropriate response, and either use internal resources or contact a local agency to provide that response.

Stakeholder: Shelby County Sheriff Department
System: Shelby County Sheriff Vehicles

This system shall:

  • provide dispatch and routing information.
  • provide safe and expedient arrival on the incident scene.
  • provide a direct interface between the emergency vehicle and incident management personnel.

Stakeholder: TDOT
System: TDOT Environmental Monitoring Sensors

This system shall:

  • measure environmental conditions and communicate the collected information back to the server where it can be monitored and analyzed.
  • measure temperature and, precipitation.
  • measure road surface temperature, moisture, icing, salinity, and other measures.

Stakeholder: TDOT
System: TDOT Environmental Monitoring Server

This system shall:

  • collect, analyze and store environmental information.
  • issue warnings to agencies in the region when hazardous conditions are detected.
  • distribute the environmental data to operations personnel or other data users and archives in the region.

Stakeholder: TDOT
System: TDOT Freeway Service Patrol Dispatch

This system shall:

  • receive transferred emergency calls.
  • collect available information about the caller and the reported emergency.
  • forward information on emergency to other systems that formulate and manage the emergency response.
  • collect and store emergency information that is collected in the course of emergency operations.
  • provide emergency data to operations personnel and other data users and archives in the region.
  • efficiently dispatch emergency vehicles to an incident.
  • track service patrol vehicles.
  • provide safe and efficient routes based on real-time traffic information.

Stakeholder: TDOT
System: TDOT Freeway Service Patrol Vehicles

This system shall:

  • provide dispatch and routing information.
  • provide a direct interface between the emergency vehicle and incident management personnel.

Stakeholder: TDOT
System: TDOT RTMC

This system shall:

  • collect, store, and provide electronic access to traffic surveillance data.
  • control systems for efficient freeway management including integration of surveillance information with freeway geometry, vehicle control such as ramp metering, DMS, and HAR.
  • interface to coordinated traffic systems for information dissemination to the public.
  • detect and verify incidents.
  • analyze and reduce collected data from traffic surveillance equipment, including planned incidents and hazardous conditions.
  • formulate an incident response minimizing the incident potential, incident impacts, and/or resources required for incident management.
  • propose and facilitate the dispatch of emergency response and service vehicles as well as coordinate response with all appropriate agencies.
  • communicate with other TMCs to receive and transmit traffic information to other jurisdictions within the region.
  • assimilate current and forecast road conditions and weather information using a combination of weather service information and an array of environmental sensors deployed on and about the roadway.
  • use information to more effectively deploy road maintenance resources, issue general traveler advisories, and support location specific warnings to drivers.
  • disseminate incident related information to travelers, potential travelers, and private information service providers.
  • collect and store traffic information that is collected in the course of traffic operations.
  • provide traffic data to operations personnel or other data users and archives in the region.
  • monitor and diagnosis field equipment remotely to detect failures, issue problem reports, and track the repair or replacement of the failed equipment.

Stakeholder: TDOT
System: TDOT RTMC Field Equipment

This system shall:

  • monitor traffic flow.
  • monitor surveillance equipment and interfaces and report detected abnormalities.
  • display traffic information on equipment along the roadway including DMS and HAR.
  • monitor DMS and HAR equipment and interfaces and report detected abnormalities.
  • control traffic on ramps to freeways.

Stakeholder: TDOT
System: TDOT RTMC Website Server

This system shall:

  • collect, process, store, and disseminate traffic information including latest available information on traffic and highway conditions, and current situation information in real-time including incidents, road construction, recommended routes, current speeds on specific routes, and current weather situations.
  • provide interactive traveler information.

Stakeholder: TDOT Headquarters Planning Office
System: TDOT Planning Traffic Archive

This system shall:

  • collect and store traffic of data in a focused repository.
  • perform quality checks on the incoming data, error notification, and archive to archive coordination.
  • provide advanced data analysis, summarization, and mining features that facilitate discovery of information, patterns, and correlations in large data sets.
  • collect and archive traffic, roadway, and environmental information for use in off-line planning, research, and analysis.
  • select and format data to facilitate local, state, and federal government data reporting requirements.

Stakeholder: Tennessee Department of Safety
System: Tennessee Commercial Vehicle Administration

This system shall:

  • provide administrative capabilities including database management and administrator-to-roadside and administrator-to-administrator interfaces.
  • manage the electronic credentials database for a state, perform reconciliation of mileage and fuel taxes, and interface with roadsides performing credential checks.
  • communicate and coordinate with other state commercial vehicle administrations.
  • collect and store information on commercial vehicles.
  • make data available to other data users and archives in the region.
  • support the exchange of safety and credentials data among jurisdictions.
  • support the exchange of safety and credentials data between agencies (for example, an administrative center and the roadside check facilities) within a single jurisdiction.
  • collect data from multiple authoritative sources and package it into snapshots (top-level summary and critical status information) and profiles (detailed and historical data).
  • ensure that safety criteria are available for automated roadside safety checks.
  • collect and review carrier safety data and determine the carrier safety rating based on supplied criteria.

Stakeholder: Tennessee Department of Safety
System: Tennessee Commercial Vehicle Field Equipment

This system shall:

  • document violations and forward the information to the commercial vehicle if available and to the commercial vehicle administration for processing as part of the normal credentials processing package.
  • communicate two-way with approaching properly equipped commercial vehicles at mainline speeds.
  • read tags for automated vehicle identification and credential checking.
  • appropriately screen all vehicles, not just those that are equipped.
  • process data from commercial vehicle along with database information to determine whether a pull-in message is needed.
  • generate random pull-in messages with provisions for facility operators and enforcement officials to have manual override capabilities.
  • automate the roadside safety inspection process including the use of hand held devices to rapidly inspect the vehicle and driver.
  • automate the roadside safety inspection process including the support of automated mainline speed reading of on-board safety data to rapidly screen the vehicle and driver.
  • collect, store, maintain, and provide safety data and access historical safety data after receiving identification from vehicles at mainline speeds or while stopped at the roadside.
  • write the results of screening and summary safety inspection back onto a tag.
  • process safety data and issue pull-in messages or provide warnings to the driver, carrier, and enforcement agencies.
  • support the concept of a last clearance event record (e.g. trip ticket) carried on the vehicle's tag.
  • perform roadside high speed weigh in motion.

Stakeholder: Tennessee Emergency Management Agency
System: Tennessee EMA System

This system shall:

  • assist local emergency management agencies when requested.
  • develop and store emergency response plans including hazmat incidents.
  • manage overall coordinated response to emergencies.
  • track the availability of resources and assist in the appropriate allocation of resources for a particular emergency response.
  • provide coordination between multiple allied agencies before and during emergencies to implement emergency response plans and track progress through the incident.

Stakeholder: Tennessee Highway Patrol
System: Tennessee Highway Patrol Dispatch

This system shall:

  • receive 9-1-1 and 7-digit local access calls.
  • collect available information about the caller and the reported emergency.
  • forward information on emergency about emergency to other systems that formulate and manage the emergency response.
  • collect and store emergency information that is collected in the course of emergency operations.
  • provide emergency data to operations personnel and other data users and archives in the region.
  • efficiently dispatch emergency vehicles to an incident.
  • provide safe and efficient routes based on real-time traffic information.
  • develop and store emergency response plans.
  • manage overall coordinated response to emergencies.
  • track the availability of resources and assist in the appropriate allocation of resources for a particular emergency response.
  • provide coordination between multiple allied agencies before and during emergencies to implement emergency response plans and track progress through the incident.
  • receive mayday messages, determine an appropriate response, and either use internal resources or contact a local agency to provide that response.

Stakeholder: Tennessee Highway Patrol
System: Tennessee Highway Patrol Vehicles

This system shall:

  • provide dispatch and routing information.
  • provide safe and expedient arrival on the incident scene.
  • provide a direct interface between the emergency vehicle and incident management personnel.
Office of Operations