< < TM08 : TM09 : TM10 > >

TM09: Integrated Decision Support and Demand Management

This service package recommends courses of action to transportation operators in a corridor, downtown area, or other heavily traveled area. Recommendations are based on an assessment of current and forecast transportation network performance and environmental conditions. Multi-modal transportation operational strategies are created that consider all modes and all roads in the travel area to correct network imbalances and effectively manage available capacity. As part of the operational strategies, this service package may also recommend lane restrictions, transit, parking, and toll strategies to influence traveler route and mode choices to support active demand management programs and policies managing both traffic and the environment. Operational strategies, including demand management recommendations, are coordinated to support operational decisions by each transportation operator that are consistent with the recommended strategy. All recommended operational strategies are based on historical evaluation, real-time assessment, and forecast of the roadway network performance based on predicted travel demand patterns. This service package also collects air quality, parking availability, transit usage, and vehicle occupancy data to support operational strategies that manage and balance capacity and demand.

Relevant Regions: Australia, Canada, European Union, and United States

Enterprise

Development Stage Roles and Relationships

Installation Stage Roles and Relationships

Operations and Maintenance Stage Roles and Relationships
(hide)

Source Destination Role/Relationship
Emergency Management Center Maintainer Emergency Management Center Maintains
Emergency Management Center Manager Emergency Management Center Manages
Emergency Management Center Owner Emergency Management Center Maintainer System Maintenance Agreement
Emergency Management Center Owner Emergency Management Center Manager Operations Agreement
Emergency Management Center Owner Traffic Management Center Maintainer Maintenance Data Exchange Agreement
Emergency Management Center Owner Traffic Management Center Owner Information Exchange Agreement
Emergency Management Center Owner Traffic Management Center User Service Usage Agreement
Emergency Management Center Owner Traffic Operations Personnel Application Usage Agreement
Emergency Management Center Supplier Emergency Management Center Owner Warranty
Emissions Management Center Maintainer Emissions Management Center Maintains
Emissions Management Center Manager Emissions Management Center Manages
Emissions Management Center Owner Emissions Management Center Maintainer System Maintenance Agreement
Emissions Management Center Owner Emissions Management Center Manager Operations Agreement
Emissions Management Center Owner Traffic Management Center Maintainer Maintenance Data Exchange Agreement
Emissions Management Center Owner Traffic Management Center Owner Information Exchange Agreement
Emissions Management Center Owner Traffic Management Center User Service Usage Agreement
Emissions Management Center Owner Traffic Operations Personnel Application Usage Agreement
Emissions Management Center Supplier Emissions Management Center Owner Warranty
Event Promoter System Maintainer Event Promoter System Maintains
Event Promoter System Manager Event Promoter System Manages
Event Promoter System Owner Event Promoter System Maintainer System Maintenance Agreement
Event Promoter System Owner Event Promoter System Manager Operations Agreement
Event Promoter System Owner Traffic Management Center Maintainer Maintenance Data Exchange Agreement
Event Promoter System Owner Traffic Management Center Owner Information Exchange Agreement
Event Promoter System Owner Traffic Management Center User Service Usage Agreement
Event Promoter System Owner Traffic Operations Personnel Application Usage Agreement
Event Promoter System Supplier Event Promoter System Owner Warranty
Maint and Constr Management Center Maintainer Maint and Constr Management Center Maintains
Maint and Constr Management Center Manager Maint and Constr Management Center Manages
Maint and Constr Management Center Owner Maint and Constr Management Center Maintainer System Maintenance Agreement
Maint and Constr Management Center Owner Maint and Constr Management Center Manager Operations Agreement
Maint and Constr Management Center Owner Traffic Management Center Maintainer Maintenance Data Exchange Agreement
Maint and Constr Management Center Owner Traffic Management Center Owner Information Exchange Agreement
Maint and Constr Management Center Owner Traffic Management Center User Service Usage Agreement
Maint and Constr Management Center Owner Traffic Operations Personnel Application Usage Agreement
Maint and Constr Management Center Supplier Maint and Constr Management Center Owner Warranty
Other Traffic Management Centers Maintainer Other Traffic Management Centers Maintains
Other Traffic Management Centers Manager Other Traffic Management Centers Manages
Other Traffic Management Centers Owner Other Traffic Management Centers Maintainer System Maintenance Agreement
Other Traffic Management Centers Owner Other Traffic Management Centers Manager Operations Agreement
Other Traffic Management Centers Owner Traffic Management Center Maintainer Maintenance Data Exchange Agreement
Other Traffic Management Centers Owner Traffic Management Center Owner Information Exchange Agreement
Other Traffic Management Centers Owner Traffic Management Center User Service Usage Agreement
Other Traffic Management Centers Owner Traffic Operations Personnel Application Usage Agreement
Other Traffic Management Centers Supplier Other Traffic Management Centers Owner Warranty
Other Transit Management Centers Maintainer Other Transit Management Centers Maintains
Other Transit Management Centers Manager Other Transit Management Centers Manages
Other Transit Management Centers Owner Other Transit Management Centers Maintainer System Maintenance Agreement
Other Transit Management Centers Owner Other Transit Management Centers Manager Operations Agreement
Other Transit Management Centers Owner Transit Management Center Maintainer Maintenance Data Exchange Agreement
Other Transit Management Centers Owner Transit Management Center Owner Information Exchange Agreement
Other Transit Management Centers Owner Transit Management Center User Service Usage Agreement
Other Transit Management Centers Supplier Other Transit Management Centers Owner Warranty
Parking Management Center Maintainer Parking Management Center Maintains
Parking Management Center Manager Parking Management Center Manages
Parking Management Center Owner Parking Management Center Maintainer System Maintenance Agreement
Parking Management Center Owner Parking Management Center Manager Operations Agreement
Parking Management Center Owner Traffic Management Center Maintainer Maintenance Data Exchange Agreement
Parking Management Center Owner Traffic Management Center Owner Information Exchange Agreement
Parking Management Center Owner Traffic Management Center User Service Usage Agreement
Parking Management Center Owner Traffic Operations Personnel Application Usage Agreement
Parking Management Center Supplier Parking Management Center Owner Warranty
Payment Administration Center Maintainer Payment Administration Center Maintains
Payment Administration Center Manager Payment Administration Center Manages
Payment Administration Center Owner Payment Administration Center Maintainer System Maintenance Agreement
Payment Administration Center Owner Payment Administration Center Manager Operations Agreement
Payment Administration Center Owner Traffic Management Center Maintainer Maintenance Data Exchange Agreement
Payment Administration Center Owner Traffic Management Center Owner Information Exchange Agreement
Payment Administration Center Owner Traffic Management Center User Service Usage Agreement
Payment Administration Center Owner Traffic Operations Personnel Application Usage Agreement
Payment Administration Center Supplier Payment Administration Center Owner Warranty
Traffic Management Center Maintainer Traffic Management Center Maintains
Traffic Management Center Manager Traffic Management Center Manages
Traffic Management Center Manager Traffic Operations Personnel System Usage Agreement
Traffic Management Center Owner Emergency Management Center Maintainer Maintenance Data Exchange Agreement
Traffic Management Center Owner Emergency Management Center Owner Information Exchange Agreement
Traffic Management Center Owner Emergency Management Center User Service Usage Agreement
Traffic Management Center Owner Emissions Management Center Maintainer Maintenance Data Exchange Agreement
Traffic Management Center Owner Emissions Management Center Owner Information Exchange Agreement
Traffic Management Center Owner Emissions Management Center User Service Usage Agreement
Traffic Management Center Owner Event Promoter System Maintainer Maintenance Data Exchange Agreement
Traffic Management Center Owner Event Promoter System Owner Information Exchange Agreement
Traffic Management Center Owner Event Promoter System User Service Usage Agreement
Traffic Management Center Owner Maint and Constr Management Center Maintainer Maintenance Data Exchange Agreement
Traffic Management Center Owner Maint and Constr Management Center Owner Information Exchange Agreement
Traffic Management Center Owner Maint and Constr Management Center User Service Usage Agreement
Traffic Management Center Owner Other Traffic Management Centers Maintainer Maintenance Data Exchange Agreement
Traffic Management Center Owner Other Traffic Management Centers Owner Information Exchange Agreement
Traffic Management Center Owner Other Traffic Management Centers User Service Usage Agreement
Traffic Management Center Owner Parking Management Center Maintainer Maintenance Data Exchange Agreement
Traffic Management Center Owner Parking Management Center Owner Information Exchange Agreement
Traffic Management Center Owner Parking Management Center User Service Usage Agreement
Traffic Management Center Owner Payment Administration Center Maintainer Maintenance Data Exchange Agreement
Traffic Management Center Owner Payment Administration Center Owner Information Exchange Agreement
Traffic Management Center Owner Payment Administration Center User Service Usage Agreement
Traffic Management Center Owner Traffic Management Center Maintainer System Maintenance Agreement
Traffic Management Center Owner Traffic Management Center Manager Operations Agreement
Traffic Management Center Owner Transit Management Center Maintainer Maintenance Data Exchange Agreement
Traffic Management Center Owner Transit Management Center Owner Information Exchange Agreement
Traffic Management Center Owner Transit Management Center User Service Usage Agreement
Traffic Management Center Owner Transportation Information Center Maintainer Maintenance Data Exchange Agreement
Traffic Management Center Owner Transportation Information Center Owner Information Exchange Agreement
Traffic Management Center Owner Transportation Information Center User Service Usage Agreement
Traffic Management Center Supplier Traffic Management Center Owner Warranty
Traffic Operations Personnel Traffic Management Center Operates
Transit Management Center Maintainer Transit Management Center Maintains
Transit Management Center Manager Transit Management Center Manages
Transit Management Center Owner Other Transit Management Centers Maintainer Maintenance Data Exchange Agreement
Transit Management Center Owner Other Transit Management Centers Owner Information Exchange Agreement
Transit Management Center Owner Other Transit Management Centers User Service Usage Agreement
Transit Management Center Owner Traffic Management Center Maintainer Maintenance Data Exchange Agreement
Transit Management Center Owner Traffic Management Center Owner Information Exchange Agreement
Transit Management Center Owner Traffic Management Center User Service Usage Agreement
Transit Management Center Owner Traffic Operations Personnel Application Usage Agreement
Transit Management Center Owner Transit Management Center Maintainer System Maintenance Agreement
Transit Management Center Owner Transit Management Center Manager Operations Agreement
Transit Management Center Supplier Transit Management Center Owner Warranty
Transportation Information Center Maintainer Transportation Information Center Maintains
Transportation Information Center Manager Transportation Information Center Manages
Transportation Information Center Owner Traffic Management Center Maintainer Maintenance Data Exchange Agreement
Transportation Information Center Owner Traffic Management Center Owner Information Exchange Agreement
Transportation Information Center Owner Traffic Management Center User Service Usage Agreement
Transportation Information Center Owner Traffic Operations Personnel Application Usage Agreement
Transportation Information Center Owner Transportation Information Center Maintainer System Maintenance Agreement
Transportation Information Center Owner Transportation Information Center Manager Operations Agreement
Transportation Information Center Supplier Transportation Information Center Owner Warranty

Functional

This service package includes the following Functional View PSpecs:

Physical Object Functional Object PSpec Number PSpec Name
Emergency Management Center Emergency Incident Command 5.1.1.3 Collect Incident And Event Data
5.1.3 Communicate Emergency Status
5.1.4 Manage Emergency Response
5.3.2 Dispatch Vehicle
5.3.4 Assess Response Status
5.3.6 Maintain Vehicle Status
5.7.2 Provide Disaster Response Coordination
Emissions Management Center Emissions Zone Management 1.5.1 Provide Emissions Operations Personnel Interface
1.5.2 Process Pollution Data
Maint and Constr Management Center MCM Work Activity Coordination 9.2.1 Schedule M&C Activities
9.2.2 Status Current M&C Activities and Transportation Infrastructure
9.2.4 Manage M&C Map Data
MCM Work Zone Management 9.1.7 Process Road Network Information
9.2.1 Schedule M&C Activities
9.2.2 Status Current M&C Activities and Transportation Infrastructure
9.2.3.5 Collect Roadside Equipment Status
9.2.5 Provide M&C Center Personnel Interface for Maint
9.3.1.1 Operate Work Zone Devices
9.3.2.2 Collect Work Zone Data
9.3.2.3 Generate Work Zone Information for Distribution
Parking Management Center Parking Coordination 1.2.5.1 Provide Parking Lot Static Data
1.2.5.11 Provide Parking Manager Interface
1.2.5.12 Manage Loading Zone Use
1.2.5.2 Coordinate Other Parking Data
1.2.5.4 Determine Dynamic Parking Lot State
7.2.1.9 Manage Parking Lot Reservations
Payment Administration Center PAC Payment Administration 5.4.2 Process Violations for Tolls
7.1.1.3 Manage Bad Toll Payment Data
7.1.1.6 Collect Probe Data From Toll Transactions
7.1.1.7 Update Toll Price Data
7.1.1.8 Register for Advanced Toll Payment
7.1.1.9 Manage Toll Processing
7.1.8 Exchange Data with Other Payment Administration
7.4.1.8 Manage Shared Use Payments
7.4.4.1 Process Electric Charging Payments
7.6.1.2 Calculate Vehicle Road Use Payment Charges
7.6.1.4 Manage Road Use Charging Price Data
7.6.1.5 Manage Road Use Charges Processing
7.6.5 Exchange Road Use Charging Data with Other Payment Administration
7.6.6.1 Provide Road Use Charging Services User Interface
7.6.8 Provide Road Use Charging Enforcement Interface
7.7 Administer Multimodal Payments
Traffic Management Center TMC Demand Management Coordination 1.1.2.1 Process Traffic Data for Storage
1.1.2.2 Process Traffic Data
1.2.1 Select Strategy
1.2.6.1 Maintain Traffic and Sensor Static Data
1.4.1 Provide Traffic Operations Personnel Demand Interface
1.4.2 Collect Demand Forecast Data
1.4.3 Implement Demand Management Policy
TMC Regional Traffic Management 1.1.3 Generate Predictive Traffic Model
1.1.4.1 Retrieve Traffic Data
1.1.4.2 Provide Traffic Operations Personnel Traffic Data Interface
1.1.5 Exchange Data with Other Traffic Centers
1.2.2.2 Determine Indicator State for Road Management
1.2.6.1 Maintain Traffic and Sensor Static Data
1.3.2.2 Review and Classify Possible Incidents
1.3.2.6 Manage Traffic Routing
1.4.2 Collect Demand Forecast Data
6.5.10 Coordinate Operational Strategies
TMC Traffic Management Decision Support 1.3.4.2 Provide Traffic Operations Personnel Incident Interface
1.3.5 Manage Incident Response Planning and Traffic Management Decision Support
TMC Traffic Network Performance Evaluation 1.1.2.1 Process Traffic Data for Storage
1.1.2.2 Process Traffic Data
1.1.3 Generate Predictive Traffic Model
1.1.4.1 Retrieve Traffic Data
1.1.4.2 Provide Traffic Operations Personnel Traffic Data Interface
1.1.5 Exchange Data with Other Traffic Centers
1.2.6.1 Maintain Traffic and Sensor Static Data
1.2.6.2 Provide Static Data Store Output Interface
1.3.2.1 Store Possible Incident Data
1.4.1 Provide Traffic Operations Personnel Demand Interface
1.4.2 Collect Demand Forecast Data
1.4.4 Calculate Forecast Demand
Transit Management Center Transit Center Multi-Modal Coordination 4.1.4 Collect and Process Transit Vehicle Data
4.2.1.2 Generate Transit Schedules
4.2.1.3 Produce Transit Service Data for External Use
4.2.1.4 Provide Transit Operations Personnel Interface for Services Generation
4.2.1.7 Provide Interface for Other Transit Management Data
4.2.1.8 Provide Interface for Transit Service Raw Data
Transportation Information Center TIC Data Collection 6.2.1 Collect Misc Traveler Information
6.2.2 Collect Traffic Data
6.2.3 Collect Transit Operations Data
6.2.4 Collect Multimodal Data
6.2.5 Collect Situation and Sensor Data From Vehicles
6.2.6 Collect Emergency Traveler Data
6.5.4 Process Travel Services Provider Data
6.6.2.3 Provide Route Segment Data for Other Areas
7.4.2 Collect Price Data for Traveler Information Use
TIC Trip Planning 6.1.1 Provide Trip Planning Information to Traveler
6.1.2 Confirm Traveler's Trip Plan
6.1.3 Provide Operator Interface for Trip Planning Parameters
6.10 Manage Traveler Profiles
6.2.1 Collect Misc Traveler Information
6.2.2 Collect Traffic Data
6.5.4 Process Travel Services Provider Data
6.5.9 Provide Traveler Alert Interface
6.6.1 Provide Multimodal Route Selection
6.6.2.1 Calculate Vehicle Route
6.6.2.2 Provide Vehicle Route Calculation Data
6.6.3 Provide Operator Interface for Route Parameters
6.6.4 Select Transit Route
6.6.5 Select Other Routes
7.1.6 Distribute Advanced Charges and Fares
7.2.4 Distribute Advanced Tolls and Fares
7.3.2 Distribute Advanced Tolls and Parking Lot Charges
7.4.1.3 Process Driver Map Update Payments
7.4.1.4 Process Traveler Map Update Payments
7.4.1.6 Process Traveler Trip and Other Services Payments
7.4.3 Route Traveler Advanced Payments

Physical

The physical diagram can be viewed in SVG or PNG format and the current format is SVG.
SVG Diagram
PNG Diagram


Display Legend in SVG or PNG

Includes Physical Objects:

Physical Object Class Description
Emergency Management Center Center The 'Emergency Management Center' represents systems that support incident management, disaster response and evacuation, security monitoring, and other security and public safety-oriented ITS applications. It includes the functions associated with fixed and mobile public safety communications centers including public safety call taker and dispatch centers operated by police (including transit police), fire, and emergency medical services. It includes the functions associated with Emergency Operations Centers that are activated at local, regional, state, and federal levels for emergencies and the portable and transportable systems that support Incident Command System operations at an incident. This Center also represents systems associated with towing and recovery, freeway service patrols, HAZMAT response teams, and mayday service providers.

It manages sensor and surveillance equipment used to enhance transportation security of the roadway infrastructure (including bridges, tunnels, interchanges, and other key roadway segments) and the public transportation system (including transit vehicles, public areas such as transit stops and stations, facilities such as transit yards, and transit infrastructure such as rail, bridges, tunnels, or bus guideways). It provides security/surveillance services to improve traveler security in public areas not a part of the public transportation system.

It monitors alerts, advisories, and other threat information and prepares for and responds to identified emergencies. It coordinates emergency response involving multiple agencies with peer centers. It stores, coordinates, and utilizes emergency response and evacuation plans to facilitate this coordinated response. Emergency situation information including damage assessments, response status, evacuation information, and resource information are shared The Emergency Management Center also provides a focal point for coordination of the emergency and evacuation information that is provided to the traveling public, including wide-area alerts when immediate public notification is warranted.

It tracks and manages emergency vehicle fleets using real-time road network status and routing information from the other centers to aid in selecting the emergency vehicle(s) and routes, and works with other relevant centers to tailor traffic control to support emergency vehicle ingress and egress, implementation of special traffic restrictions and closures, evacuation traffic control plans, and other special strategies that adapt the transportation system to better meet the unique demands of an emergency.
Emissions Management Center Center The 'Emissions Management Center' provides the capabilities for air quality managers to monitor and manage air quality. These capabilities include collecting emissions data from distributed emissions sensors (included in ITS Roadway Equipment) and directly from connected vehicles. The sensors monitor general air quality and also monitor the emissions of individual vehicles on the roadway. The measures are collected, processed, and used to support environmental monitoring applications.
Event Promoter System Center 'Event Promoter System' represents Special Event Sponsors that have knowledge of events that may impact travel on roadways or other modal means. Examples of special event sponsors include sporting events, conventions, motorcades/parades, and public/political events. These promoters interface to the ITS to provide event information such as date, time, estimated duration, location, and any other information pertinent to traffic movement in the surrounding area.
Maint and Constr Management Center Center The 'Maint and Constr Management Center' monitors and manages roadway infrastructure construction and maintenance activities. Representing both public agencies and private contractors that provide these functions, this physical object manages fleets of maintenance, construction, or special service vehicles (e.g., snow and ice control equipment). The physical object receives a wide range of status information from these vehicles and performs vehicle dispatch, routing, and resource management for the vehicle fleets and associated equipment. The physical object participates in incident response by deploying maintenance and construction resources to an incident scene, in coordination with other center physical objects. The physical object manages equipment at the roadside, including environmental sensors and automated systems that monitor and mitigate adverse road and surface weather conditions. It manages the repair and maintenance of both non-ITS and ITS equipment including the traffic controllers, detectors, dynamic message signs, signals, and other equipment associated with the roadway infrastructure. Weather information is collected and fused with other data sources and used to support advanced decision support systems.

The physical object remotely monitors and manages ITS capabilities in work zones, gathering, storing, and disseminating work zone information to other systems. It manages traffic in the vicinity of the work zone and advises drivers of work zone status (either directly at the roadside or through an interface with the Transportation Information Center or Traffic Management Center physical objects.)

Construction and maintenance activities are tracked and coordinated with other systems, improving the quality and accuracy of information available regarding closures and other roadway construction and maintenance activities.
Other Traffic Management Centers Center Representing another Traffic Management Center, 'Other Traffic Management Centers' is intended to provide a source and destination for information exchange between peer (e.g. inter-regional) traffic management functions. It enables traffic management activities to be coordinated across different jurisdictional areas.
Other Transit Management Centers Center Representing another transit operations center, 'Other Transit Management Centers' is intended to provide a source and destination for information flows between peer transit management centers. It enables transit management activities to be coordinated across geographic boundaries or jurisdictions.
Parking Management Center Center The 'Parking Management Center' manages one or more parking lots by providing configuration and control of field infrastructure, user account management and interfaces with financial systems to manage payment. This p-object takes the back office portion of the Parking Management System's functionality as it was defined in ARC-IT 8.3 and prior.
Payment Administration Center Center The 'Payment Administration Center' provides general payment administration capabilities and supports the electronic transfer of funds from the customer to the transportation system operator or other service provider. Charges can be recorded for tolls, vehicle-mileage charging, congestion charging, or other goods and services. It supports traveler enrollment and collection of both pre-payment and post-payment transportation fees in coordination with the financial infrastructure supporting electronic payment transactions. The system may establish and administer escrow accounts depending on the clearinghouse scheme and the type of payments involved. It may post a transaction to the customer account, generate a bill (for post-payment accounts), debit an escrow account, or interface to a financial infrastructure to debit a customer designated account. It supports communications with the ITS Roadway Payment Equipment to support fee collection operations. As an alternative, a wide-area wireless interface can be used to communicate directly with vehicle equipment. It also sets and administers the pricing structures and may implement road pricing policies in coordination with the Traffic Management Center.
Traffic Management Center Center The 'Traffic Management Center' monitors and controls traffic and the road network. It represents centers that manage a broad range of transportation facilities including freeway systems, rural and suburban highway systems, and urban and suburban traffic control systems. It communicates with ITS Roadway Equipment and Connected Vehicle Roadside Equipment (RSE) to monitor and manage traffic flow and monitor the condition of the roadway, surrounding environmental conditions, and field equipment status. It manages traffic and transportation resources to support allied agencies in responding to, and recovering from, incidents ranging from minor traffic incidents through major disasters.
Traffic Operations Personnel Center 'Traffic Operations Personnel' represents the people that operate a traffic management center. These personnel interact with traffic control systems, traffic surveillance systems, incident management systems, work zone management systems, and travel demand management systems. They provide operator data and command inputs to direct system operations to varying degrees depending on the type of system and the deployment scenario.
Transit Management Center Center The 'Transit Management Center' manages transit vehicle fleets and coordinates with other modes and transportation services. It provides operations, maintenance, customer information, planning and management functions for the transit property. It spans distinct central dispatch and garage management systems and supports the spectrum of fixed route, flexible route, paratransit services, transit rail, and bus rapid transit (BRT) service. The physical object's interfaces support communication between transit departments and with other operating entities such as emergency response services and traffic management systems.
Transportation Information Center Center The 'Transportation Information Center' collects, processes, stores, and disseminates transportation information to system operators and the traveling public. The physical object can play several different roles in an integrated ITS. In one role, the TIC provides a data collection, fusing, and repackaging function, collecting information from transportation system operators and redistributing this information to other system operators in the region and other TICs. In this information redistribution role, the TIC provides a bridge between the various transportation systems that produce the information and the other TICs and their subscribers that use the information. The second role of a TIC is focused on delivery of traveler information to subscribers and the public at large. Information provided includes basic advisories, traffic and road conditions, transit schedule information, yellow pages information, ride matching information, and parking information. The TIC is commonly implemented as a website or a web-based application service, but it represents any traveler information distribution service.

Includes Functional Objects:

Functional Object Description Physical Object
Emergency Incident Command 'Emergency Incident Command' provides tactical decision support, resource coordination, and communications integration for Incident Commands that are established by first responders at or near the incident scene to support local management of an incident. It supports communications with public safety, emergency management, transportation, and other allied response agency centers, tracks and maintains resource information, action plans, and the incident command organization itself. Information is shared with agency centers including resource deployment status, hazardous material information, traffic, road, and weather conditions, evacuation advice, and other information that enables emergency or maintenance personnel in the field to implement an effective, safe incident response. It supports the functions and interfaces commonly supported by a mobile command center. Emergency Management Center
Emissions Zone Management 'Emissions Zone Management' identifies existing and potential emissions hot spots and coordinates with transportation agencies and their systems to establish low emissions zones to manage air quality in these areas. Through this coordination, the geographic boundary, restrictions, and pricing for the low emissions zone are established and adjusted. Emissions Management Center
MCM Work Activity Coordination 'MCM Work Activity Coordination' disseminates work activity schedules and current asset restrictions to other agencies. Work schedules are coordinated with operating agencies, factoring in the needs and activities of other agencies and adjacent jurisdictions. Work schedules are also distributed to Transportation Information Centers for dissemination to the traveling public. Maint and Constr Management Center
MCM Work Zone Management 'MCM Work Zone Management' remotely monitors and supports work zone activities, controlling traffic through dynamic message signs (DMS), Highway Advisory Radio (HAR), gates and barriers, and informing other groups of activity (e.g., traveler information, traffic management, other maintenance and construction centers) for better coordination management. Work zone speeds, and delays, and closures are provided to the motorist prior to the work zones. This application provides control of field equipment in all maintenance areas, including fixed and portable field equipment supporting both stationary and mobile work zones. Maint and Constr Management Center
PAC Payment Administration 'PAC Payment Administration' provides administration and management of payments associated with electronic toll collection, parking payments, and other e-payments. It provides the back office functions that support enrollment, pricing, reduced fare eligibility, payment reconciliation with financial institutions, and violation notification to enforcement agencies. It also supports dynamic pricing to support demand management, allow/block-list management and token validation. Payment Administration Center
Parking Coordination 'Parking Coordination' supports communication and coordination between equipped parking facilities and also supports regional coordination between parking facilities and traffic management systems. Coordination with traffic management supports local traffic control coordination in and around the parking facility and broader regional coordination. It also shares information with transit management systems and information providers to support multimodal travel planning, including parking reservations capabilities. Information including current parking availability, system status, and operating strategies are shared to enable local parking facility management that supports regional transportation strategies. Parking Management Center
TIC Data Collection 'TIC Data Collection' collects transportation-related data from other centers, performs data quality checks on the collected data and then consolidates, verifies, and refines the data and makes it available in a consistent format to applications that support operational data sharing between centers and deliver traveler information to end-users. A broad range of data is collected including traffic and road conditions, transit data, emergency information and advisories, weather data, special event information, traveler services, parking, multimodal data, and toll/pricing data. It also shares data with other transportation information centers. Transportation Information Center
TIC Trip Planning 'TIC Trip Planning' provides pre-trip and en route trip planning services for travelers. It receives origin, destination, constraints, and preferences and returns trip plan(s) that meet the supplied criteria. Trip plans may be based on current traffic and road conditions, transit schedule information, and other real-time traveler information. Candidate trip plans are multimodal and may include vehicle, transit, and alternate mode segments (e.g., rail, ferry, bicycle routes, and walkways) based on traveler preferences. It also confirms the trip plan for the traveler and supports reservations and advanced payment for portions of the trip. The trip plan includes specific routing information and instructions for each segment of the trip and may also include information and reservations for additional services (e.g., parking) along the route. Transportation Information Center
TMC Demand Management Coordination 'TMC Demand Management Coordination' provides the capability to gather information on regional toll, parking, and transit usage and request changes to pricing and other mechanisms to manage overall transportation demand. Traffic Management Center
TMC Regional Traffic Management 'TMC Regional Traffic Management' supports coordination between Traffic Management Centers in order to share traffic information between centers as well as control of traffic management field equipment. This coordination supports wide area optimization and regional coordination that spans jurisdictional boundaries; for example, coordinated signal control in a metropolitan area or coordination between freeway operations and arterial signal control within a corridor. Traffic Management Center
TMC Traffic Management Decision Support 'TMC Traffic Management Decision Support' recommends courses of action to the traffic operator based on current and forecast road and traffic conditions. Traffic incidents, special events, maintenance activities and other events or conditions that impact capacity or demand are monitored. Historical data and models are used to compare the impact of potential courses of action and make recommendations to the operator. Decisions are supported through presentation of filtered and fused network-wide road and traffic conditions that identify network imbalances and recommended courses of action. The recommended actions may include predefined incident response plans, signal timing plan changes, DMS/HAR messages, truck restrictions, lane control strategies, metering strategies, and adjustment of variable speed limits. Multimodal strategies may also be recommended that include suggested transit strategies and suggested route and mode choices for travelers. Once a course of action is selected, traffic operations personnel implement these actions within the Traffic Management Center and coordinate the response with other centers in the region. Traffic Management Center
TMC Traffic Network Performance Evaluation 'TMC Traffic Network Performance Evaluation' measures traffic network performance and predicts travel demand patterns to support traffic flow optimization, demand management, and incident management. It collects traffic data from sensors and surveillance equipment as well as input from other Traffic Management Centers, emissions management, transit operations, and event promoters and uses this information to measure traffic network performance. It collects route planning information from transportation information centers and integrates and uses this information to predict future traffic conditions. The planned control strategies can be passed back to the transportation information center so that the intended strategies can be reflected in future route planning. Traffic Management Center
Transit Center Multi-Modal Coordination 'Transit Center Multi-Modal Coordination' supports transit service coordination between transit properties and coordinates with other surface and air transportation modes. As part of service coordination, it shares schedule and trip information, as well as transit transfer cluster (a collection of stop points, stations, or terminals where transfers can be made conveniently) and transfer point information between Multimodal Transportation Service Providers, Transit Agencies, and ISPs. An interface to Traffic Management also supports demand management strategies. Transit Management Center

Includes Information Flows:

Information Flow Description
air quality information Aggregated region-wide measured air quality data and possible pollution incident information.
event plans Plans for major events possibly impacting traffic.
fare and price information Current transit, parking, and toll fee schedule information.
incident information Notification of existence of incident and expected severity, location, time and nature of incident. As additional information is gathered and the incident evolves, updated incident information is provided. Incidents include any event that impacts transportation system operation ranging from routine incidents (e.g., disabled vehicle at the side of the road) through large-scale natural or human-caused disasters that involve loss of life, injuries, extensive property damage, and multi-jurisdictional response. This also includes special events, closures, and other planned events that may impact the transportation system.
logged vehicle routes Anticipated route information for guided vehicles, special vehicles (e.g., oversize vehicles) or groups of vehicles (e.g., governor's motorcade) that may require changes in traffic control strategy.
maint and constr work plans Future construction and maintenance work schedules and activities including anticipated closures with anticipated impact to the roadway, alternate routes, anticipated delays, closure times, and durations.
parking information General parking information and status, including current parking availability, parking pricing, and parking space availability information, including features like number and type of electric charging spots.
road network conditions Current and forecasted traffic information, road and weather conditions, and other road network status. Either raw data, processed data, or some combination of both may be provided by this flow. Information on diversions and alternate routes, closures, and special traffic restrictions (lane/shoulder use, weight restrictions, width restrictions, HOV requirements) in effect is included.
roadway maintenance status Summary of maintenance fleet operations affecting the road network. This includes the status of winter maintenance (snow plow schedule and current status).
toll data Current toll schedules for different types of vehicles as well as advanced toll payment information.
traffic operator data Presentation of traffic operations data to the operator including traffic conditions, current operating status of field equipment, maintenance activity status, incident status, video images, security alerts, emergency response plan updates and other information. This data keeps the operator appraised of current road network status, provides feedback to the operator as traffic control actions are implemented, provides transportation security inputs, and supports review of historical data and preparation for future traffic operations activities.
traffic operator input User input from traffic operations personnel including requests for information, configuration changes, commands to adjust current traffic control strategies (e.g., adjust signal timing plans, change DMS messages), and other traffic operations data entry.
transit service coordination Schedule coordination or AVL information shared between local/regional transit organizations. This includes coordination of connections and control parameters between transit properties as well as coordination of transit-related maintenance activities.
transit system data Current transit system operations information indicating current transit routes and fares, 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.
transportation operational strategies Operational strategies for each operating agency in a transportation corridor, downtown area, or other travel-impacted area, providing an integrated operations strategy for the freeways, tollways, arterials, transit services, parking facilities, and other transportation-related facilities in the area. These strategies can include dynamic adjustments to transit fares and tolls, parking fees and restrictions, dynamic lane restriction changes, and other active demand management strategies.
work zone information Summary of maintenance and construction 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.

Goals and Objectives

Associated Planning Factors and Goals

Planning Factor Goal
A. Support the economic vitality of the metropolitan area, especially by enabling global competitiveness, productivity, and efficiency; Improve freight network
D. Increase the accessibility and mobility of people and for freight; Reduce congestion
E. Protect and enhance the environment, promote energy conservation, improve the quality of life, and promote consistency between transportation improvements and State and local planned growth and economic development patterns; Protect/Enhance the Environment
F. Enhance the integration and connectivity of the transportation system, across and between modes, for people and freight; Enhance integration and connectivity
G. Promote efficient system management and operation; Improve efficiency
I. Improve the resiliency and reliability of the transportation system and reduce or mitigate stormwater impacts of surface transportation; Improve resiliency and reliability

Associated Objective Categories

Objective Category
Special Event Management: Entry/Exit Travel Times
Special Event Management: Mode Shift from SOV
Special Event Management: Multi-Agency Coordination and Training
System Efficiency: Cost of Congestion
System Efficiency: Delay
System Efficiency: Duration of Congestion
System Efficiency: Energy Consumption
System Efficiency: Extent of Congestion
System Efficiency: Intensity of Congestion (Travel Time Index)
System Efficiency: Travel Time
System Efficiency: Vehicle Miles Traveled
System Options: Mode Share
System Options: Transit Use
System Reliability: Non-Recurring Delay
Travel Demand Management: Auto Commuter Trip Reduction Programs
Travel Demand Management: Parking Management

Associated Objectives and Performance Measures

Objective Performance Measure
Achieve X percent alternative (non-SOV) mode share in transit station communities (or other destinations) by year Y. Percent of all trips made using alternative modes in transit station communities.
Annual rate of change in regional average commute travel time will not exceed regional rate of population growth through the year Y. Average commute trip travel time (minutes).
Biannually increase preferred parking spaces for carpool/vanpool participants within downtown, at special events, and among major employers by X percent within Y years. Number of preferred parking spaces for carpool/vanpool participants.
Decrease the percent of special event attendees traveling to the event in single-occupancy vehicles by X percent in Y years. Percent of special event attendees using single-occupancy vehicles each year for selected events.
Implement parking pricing for X communities every Y years. Number of communities with priced parking stalls.
Implement shared parking for X communities every Y years. Number of communities with shared parking.
Improve average travel time during peak periods by X percent by year Y. Average travel time during peak periods (minutes).
Increase active (bicycle/pedestrian) mode share by X percent by year Y. Share of trips by each mode of travel.
Increase alternative (non-SOV) mode share for all trips by X percent within the next Y years. Share of trips by each mode of travel.
Increase average transit load factor by X percent by year Y. Number of riders on various transit units per trip at peak travel times.
Increase park-and-ride lot capacity by X percent over Y years. Capacity of park & ride lots.
Increase passenger miles traveled per capita on transit by X percent by year Y. Number of passenger miles traveled per capita.
Increase the number of agencies with special event management responsibilities that use interoperable communications by X percent in Y years. Number of agencies special event management responsibilities using interoperable communications.
Increase the number of residents/commuters receiving information on parking pricing and availability within Y years. Number of residents/commuters receiving information on parking pricing and availability.
Increase the percent of special event attendees using park & ride lots by X percent in Y years. Percent of special event attendees utilizing park & ride lots each year for selected events.
Increase the percent of special events with dedicated shuttle service by X percent in Y years. Percent of special events with dedicated shuttle service for selected events during a 1-year period.
Increase the percentage of special event stakeholder agencies participating in a regional event management team to X percent by year Y. Percent of stakeholder agencies participating agencies in a regional special event management team.
Increase transit mode share by X percent by year Y during peak periods. Percent of all peak-period trips made by transit.
Increase transit mode share by X percent by year Y. Percent of all trips made by transit.
Maintain the rate of growth in facility miles experiencing recurring congestion as less than the population growth rate (or employment growth rate). Percent of lane-miles (or rail) operating at LOS F or V/C > 1.0
Reduce commuter vehicle miles traveled (VMT) per regional job by X percent in Y years. Commuter VMT per regional employee.
Reduce excess fuel consumed due to congestion by X percent by year Y. Excess fuel consumed (total or per capita).
Reduce hours of delay per capita by X percent by year Y. Hours of delay (person-hours).
Reduce hours of delay per capita by X percent by year Y. Hours of delay per capita.
Reduce hours of delay per driver by X percent by year Y. Hours of delay (person-hours).
Reduce hours of delay per driver by X percent by year Y. Hours of delay per driver.
Reduce non-special event VMT in the event area during events by X percent in Y years. Non-special event VMT in the event area during events over a year.
Reduce per capita SOV commute trip rate by X percent in Y years. SOV commute trips per capita.
Reduce SOV vehicle trips by X percent through travel demand management strategies (e.g., employer or residential rideshare) by year Y. Share of employees walking, biking, telecommuting, carpooling/vanpooling, riding transit, driving alone.
Reduce the annual monetary cost of congestion per capita for the next X years. Cost (in dollars) of congestion or delay per capita.
Reduce the daily hours of recurring congestion on major freeways from X to Y by year Z. Hours per day at LOS F or V/C > 1.0 (or other threshold).
Reduce the number of hours per day that the top 20 most congested roadways experience recurring congestion by X percent by year Y. Hours per day at LOS F or V/C > 1.0 (or other threshold).
Reduce the percentage of facility miles (highway, arterial, rail, etc.) experiencing recurring congestion during the peak period by X percent by year Y. Percent of lane-miles (or rail) operating at LOS F or V/C > 1.0
Reduce the regional average travel time index by X percent per year. Travel time index (the average travel time during the peak period, using congested speeds, divided by the off-peak period travel time, using posted or free-flow speeds).
Reduce the share of major intersections operating at LOS Z by X percent by year Y. Percent of intersections operating at LOS F or V/C > 1.0
Reduce total energy consumption per capita for transportation by X percent by year Y. Total energy consumed per capita for transportation.
Reduce total fuel consumption per capita for transportation by X percent by year Y. Total fuel consumed per capita for transportation.
Reduce total person hours of delay (or travel-time delay per capita) by time period (peak, off-peak) caused by all transient events such as traffic incidents, special events, and work zones. Total person hours of delay during scheduled and/or unscheduled disruptions to travel.
Reduce total person hours of delay (or travel-time delay per capita) by time period (peak, off-peak) caused by scheduled events, work zones, or system maintenance by x hours in y years. Travel time delay during scheduled and/or unscheduled disruptions to travel.
Reduce total person hours of delay (or travel-time delay per capita) by time period (peak, off-peak) caused by unscheduled disruptions to travel. Total person hours of delay during scheduled and/or unscheduled disruptions to travel.
Reduce vehicle miles traveled per capita by X percent by year Y. Average VMT per capita per day, per week, or per year.

 
Since the mapping between objectives and service packages is not always straight-forward and often situation-dependent, these mappings should only be used as a starting point. Users should do their own analysis to identify the best service packages for their region.

Needs and Requirements

Need Functional Object Requirement
01 Traffic Operations need to be able to use current and forecast road and traffic conditions to develop traffic management plans. TIC Trip Planning 01 The center shall provide the capability to provide specific pre-trip and en route directions to travelers (and drivers), including costs, arrival times, and transfer points.
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.
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 Traffic Operations need to be able to develop operational decisions based upon analysis of current and forecast road and traffic conditions. TMC Traffic Management Decision Support 03 The center shall compare the impact of potential courses of action and make recommendations to the operator.
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.
03 Traffic Operations need to be able to collect information describing multi-source, real-time data (both infrastructure and vehicle based) on arterials, freeways, and transit systems to develop operational decisions that can be applied to corridors or to the region as a whole. Emergency Incident Command 02 The center shall provide incident command communications with public safety, emergency management, transportation, and other allied response agency centers.
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.
Emissions Zone Management 01 The center shall provide other agencies air quality information.
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.
MCM Work Zone Management 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.
Parking Coordination 02 The parking element shall provide parking management data to traffic management centers upon request as part of the implementation of demand management programs in the region. This could include changes to hours of operation or pricing.
TIC Data Collection 02 The 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.
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.).
TMC Traffic Management Decision Support 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.
TMC Traffic Network Performance Evaluation 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.
Transit Center Multi-Modal Coordination 03 The center shall accept requests from traffic management to change routes and schedules as part of the implementation of demand management strategies.
04 Traffic Operations needs to be able to collect information from transit, parking, and toll operations in order to support development of demand management strategies. PAC Payment Administration 14 This center shall maintain and publish the prices for the electronic payment system.
15 The center shall provide the HOT pricing information, including variable pricing based on calendar, time of day, vehicle type and passenger occupancy.
21 The center shall provide toll pricing information to other transportation centers.
TMC Demand Management Coordination 01 The center shall collect and store toll pricing data from payment administration centers, including the price for each road segment to which a toll applies, with the time and date for when it applies.
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.
03 The center shall collect and store transit fare and schedule information from transit management centers.
04 The center shall collect and store current transit, parking, and toll fee schedule information provided by regional traveler information centers.
05 The center shall send requests to payment administration centers to change pricing, modify restrictions, or modify operations of a toll road facility.
06 The center shall send requests to parking management providers to change the current parking lot charging structure.
07 The center shall send requests to transit management centers to change the current transit services - schedules or fares of the transit services including park-and-ride lots.
TMC Traffic Network Performance Evaluation 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.
Transit Center Multi-Modal Coordination 01 The center shall coordinate schedules and services with traffic management, parking management, and event planning systems.
05 Traffic Operations needs to be able to implement demand management strategies in order to correct network imbalances and effectively manage available capacity. TMC Traffic Management Decision Support 02 The center shall identify network imbalances and potential courses of action.
TMC Traffic Network Performance Evaluation 03 The center shall collect and store anticipated route information from traveler information centers to support overall network performance evaluations and predictions.
06 Traffic Operations needs to be able to collect emissions data to support development of demand management strategies. TMC Traffic Network Performance Evaluation 02 The center shall collect wide-area pollution data from emissions management centers to support overall network performance evaluations.

Related Sources

Document Name Version Publication Date
ITS User Services Document 1/1/2005


Security

In order to participate in this service package, each physical object should meet or exceed the following security levels.

Physical Object Security
Physical Object Confidentiality Integrity Availability Security Class
Emergency Management Center High Moderate Moderate Class 4
Emissions Management Center Moderate Moderate Moderate Class 2
Event Promoter System Moderate High Moderate Class 3
Maint and Constr Management Center Moderate High High Class 5
Other Traffic Management Centers High High Moderate Class 4
Other Transit Management Centers Moderate Moderate Moderate Class 2
Parking Management Center Moderate Moderate Moderate Class 2
Payment Administration Center Moderate Moderate Moderate Class 2
Traffic Management Center High High High Class 5
Transit Management Center Moderate Moderate Moderate Class 2
Transportation Information Center High Moderate Moderate Class 4



In order to participate in this service package, each information flow triple should meet or exceed the following security levels.

Information Flow Security
Source Destination Information Flow Confidentiality Integrity Availability
Basis Basis Basis
Emergency Management Center Traffic Management Center incident information High Moderate Moderate
This data contains all of the information regarding the incident. This could include personal information regarding persons involved in the incident. It could also include sensitive information regarding special events or closures. Minor discrepancies in this data should not have a catastrophic effect, but it should be reasonably controlled and accurate. A few missed messages should not have a significant effect. However, most messages should make it through and the EMC should be able to know if the TMC has received a message.
Emissions Management Center Traffic Management Center air quality information Not Applicable Moderate Low
This flow does not contain any personal or confidential information, and the data contained is eventually intended for public consumption. Information for general distribution should have at least some guarantee that it was correctly transmitted. If this information were incorrect, people could be exposed to higher levels of pollution than they would intend, which could be harmful to people with medical conditions such as asthma. Not a key flow for any service package. If an application is developed that relies on this flow, may change to MODERATE.
Event Promoter System Traffic Management Center event plans Moderate High Moderate
This will include PII of the event contact person, which should be protected from casual viewing. This flow will also include details of the planned event, which in some circumstances might not be entire public information and so again, should not be casually viewable. Personal contact information needs to be correct, but so do the details of the planned event because of the potential severity of the event's impact. Generally the more significant the potential impact of the event, the higher this should be, but never below MODERATE. There should be other mechanisms for getting this information, otherwise it would match integrity.
Maint and Constr Management Center Traffic Management Center maint and constr work plans Low High High
This data is eventually intended for public dissemination, and is also shared with many centers. If incorrect or unavailable this could result in a vehicle being somewhere it should not be due to work zone impacts, which could have an impact on the infrastruture and the vehicle, including potential incidents (consider a large vehicle with narrow or height-restricted roadway). If incorrect or unavailable this could result in a vehicle being somewhere it should not be due to work zone impacts, which could have an impact on the infrastruture and the vehicle, including potential incidents (consider a large vehicle with narrow or height-restricted roadway).
Maint and Constr Management Center Traffic Management Center roadway maintenance status Low Moderate Moderate
Roadway maintenance status data is distributed to a host of places including travelers, so there is no justification for obfuscation. Road maintenance data needs to be accurate and available so that the TMC can make appropriate decisions. Inappropriate decisions may significantly affect traffic and individual travel experiences. Road maintenance data needs to be accurate and available so that the TMC can make appropriate decisions. Inappropriate decisions may significantly affect traffic and individual travel experiences.
Maint and Constr Management Center Traffic Management Center work zone information Low Moderate Moderate
Eventually intended for public distribution, so no need to obfuscate. Information needs to be timely and correct so that appropriate actions are taken on the part of the receiver. Trip plans, corresponding maintenance actions, transit and emergency vehicle routes, etc.; DISC: WYO believes this to be HIGH. Information needs to be timely and correct so that appropriate actions are taken on the part of the receiver. Trip plans, corresponding maintenance actions, transit and emergency vehicle routes, etc.
Other Traffic Management Centers Traffic Management Center incident information High Moderate Moderate
This data contains all of the information regarding the incident. This could include personal information regarding persons involved in the incident. It could also include sensitive information regarding special events or closures. Incident response and planning details need to be accurate or incorrect decisions or expectations may result, having a significant impact on mobility and operations. Real-time access to incident response information is important to management of transportation assets and incident response assets, but does not warrant 'High' because this flow is about adjacent centers, and has no direct impact on the response being given.
Other Traffic Management Centers Traffic Management Center road network conditions Low Moderate Moderate
No harm should come from seeing this data, as it is eventually intended for public consumption. While accuracy of this data is important for decision making purposes, applications should be able to corroborate the data in many instances. Thus MODERATE generally. Depends on the application; if mobility decisions that affect large numbers of travelers are made based on this data, then it is MODERATE. In more modest circumstances, it may be LOW.
Other Traffic Management Centers Traffic Management Center transportation operational strategies Moderate Moderate Moderate
No PII is involved. However this flow should contain coordinated response information: how various transportation related entities respond to different conditions. This type of information is block intelligence that could be useful to an attacker or criminal, and thus should not be distributed in the clear. If this information is corrupted or modified, transportation management entities may not have well integrated plans for one or more operational scenarios, impacting mobility and safety in those conditions. Given that this data exchange is likely the product of personal work between agencies, and that follow up is likely, justify MODERATE and not HIGH. Probably not updated often, but could contain large amounts of information; additionally in times of crisis may need some more update, so MODERATE justifiable.
Other Transit Management Centers Transit Management Center transit service coordination Moderate Moderate Moderate
Coordination between transit systems is generally not sensitive, however this flow may include information related to serving individual connection protection requests that are sensitive. If this information is not timely or correct, transit agencies may not properly coordinate, leaving some users unserved. If this information is not timely or correct, transit agencies may not properly coordinate, leaving some users unserved.
Parking Management Center Traffic Management Center parking information Moderate Moderate Moderate
Does not include PII, but does include usage information for a managed facility that implies a number of vehicles. While this is observable information, it could be considered competitive, and regardless is accessible without being physically present, which is its own barrier. Generally transportation coordination information should be correct between source and destination, or inappropriate actions may be taken. Most likely not a frequently updated flow. Typically MODERATE for applications with a high degree of commercial vehicle parking, but could be LOW otherwise.
Payment Administration Center Traffic Management Center toll data Low Moderate Low
Should be public information, little benefit to obscuring this information. Since actors may use this information to plan their travels, it must be correct. Corruption or manipulation of this data may lead them to make suboptimal decisions, costing time and/or money. This flow probably does not update often. The information within is distributed via many routes.
Traffic Management Center Emergency Management Center transportation operational strategies Moderate Moderate Moderate
No PII is involved. However this flow should contain coordinated response information: how various transportation related entities respond to different conditions. This type of information is block intelligence that could be useful to an attacker or criminal, and thus should not be distributed in the clear. If this information is corrupted or modified, transportation management entities may not have well integrated plans for one or more operational scenarios, impacting mobility and safety in those conditions. Given that this data exchange is likely the product of personal work between agencies, and that follow up is likely, justify MODERATE and not HIGH. Probably not updated often, but could contain large amounts of information; additionally in times of crisis may need some more update, so MODERATE justifiable.
Traffic Management Center Emissions Management Center transportation operational strategies Moderate Moderate Moderate
No PII is involved. However this flow should contain coordinated response information: how various transportation related entities respond to different conditions. This type of information is block intelligence that could be useful to an attacker or criminal, and thus should not be distributed in the clear. If this information is corrupted or modified, transportation management entities may not have well integrated plans for one or more operational scenarios, impacting mobility and safety in those conditions. Given that this data exchange is likely the product of personal work between agencies, and that follow up is likely, justify MODERATE and not HIGH. Probably not updated often, but could contain large amounts of information; additionally in times of crisis may need some more update, so MODERATE justifiable.
Traffic Management Center Event Promoter System transportation operational strategies Moderate Moderate Moderate
No PII is involved. However this flow should contain coordinated response information: how various transportation related entities respond to different conditions. This type of information is block intelligence that could be useful to an attacker or criminal, and thus should not be distributed in the clear. If this information is corrupted or modified, transportation management entities may not have well integrated plans for one or more operational scenarios, impacting mobility and safety in those conditions. Given that this data exchange is likely the product of personal work between agencies, and that follow up is likely, justify MODERATE and not HIGH. Probably not updated often, but could contain large amounts of information; additionally in times of crisis may need some more update, so MODERATE justifiable.
Traffic Management Center Maint and Constr Management Center transportation operational strategies Moderate Moderate Moderate
No PII is involved. However this flow should contain coordinated response information: how various transportation related entities respond to different conditions. This type of information is block intelligence that could be useful to an attacker or criminal, and thus should not be distributed in the clear. If this information is corrupted or modified, transportation management entities may not have well integrated plans for one or more operational scenarios, impacting mobility and safety in those conditions. Given that this data exchange is likely the product of personal work between agencies, and that follow up is likely, justify MODERATE and not HIGH. Probably not updated often, but could contain large amounts of information; additionally in times of crisis may need some more update, so MODERATE justifiable.
Traffic Management Center Other Traffic Management Centers incident information High Moderate Moderate
This data contains all of the information regarding the incident. This could include personal information regarding persons involved in the incident. It could also include sensitive information regarding special events or closures. Minor discrepancies in this data should not have a catastrophic effect, but it should be reasonably controlled and accurate. A few missed messages should not have a significant effect. However, most messages should make it through and the TMC should be able to know if the EMC has received a message.
Traffic Management Center Other Traffic Management Centers road network conditions Low Moderate Moderate
encrypted; but no harm should come from seeing this data info needs to be accurate and should not be tampered but should be able to cope with some bad data; should be able to confirm conditions by other mechanisms condition info should be timely and readily available so that TMCs are aware of current traffic info, conditions, restrictions, etc. but should not have severe/catastrophic consequences if not
Traffic Management Center Other Traffic Management Centers transportation operational strategies Moderate Moderate Moderate
No PII is involved. However this flow should contain coordinated response information: how various transportation related entities respond to different conditions. This type of information is block intelligence that could be useful to an attacker or criminal, and thus should not be distributed in the clear. If this information is corrupted or modified, transportation management entities may not have well integrated plans for one or more operational scenarios, impacting mobility and safety in those conditions. Given that this data exchange is likely the product of personal work between agencies, and that follow up is likely, justify MODERATE and not HIGH. Probably not updated often, but could contain large amounts of information; additionally in times of crisis may need some more update, so MODERATE justifiable.
Traffic Management Center Parking Management Center transportation operational strategies Moderate Moderate Moderate
No PII is involved. However this flow should contain coordinated response information: how various transportation related entities respond to different conditions. This type of information is block intelligence that could be useful to an attacker or criminal, and thus should not be distributed in the clear. If this information is corrupted or modified, transportation management entities may not have well integrated plans for one or more operational scenarios, impacting mobility and safety in those conditions. Given that this data exchange is likely the product of personal work between agencies, and that follow up is likely, justify MODERATE and not HIGH. Probably not updated often, but could contain large amounts of information; additionally in times of crisis may need some more update, so MODERATE justifiable.
Traffic Management Center Payment Administration Center transportation operational strategies Moderate Moderate Moderate
No PII is involved. However this flow should contain coordinated response information: how various transportation related entities respond to different conditions. This type of information is block intelligence that could be useful to an attacker or criminal, and thus should not be distributed in the clear. If this information is corrupted or modified, transportation management entities may not have well integrated plans for one or more operational scenarios, impacting mobility and safety in those conditions. Given that this data exchange is likely the product of personal work between agencies, and that follow up is likely, justify MODERATE and not HIGH. Probably not updated often, but could contain large amounts of information; additionally in times of crisis may need some more update, so MODERATE justifiable.
Traffic Management Center Traffic Operations Personnel traffic operator data Moderate Moderate Moderate
Backoffice operations flows should have minimal protection from casual viewing, as otherwise imposters could gain illicit control or information that should not be generally available. Information presented to backoffice system operators must be consistent or the operator may perform actions that are not appropriate to the real situation. The backoffice system operator should have access to system operation. If this interface is down then control is effectively lost, as without feedback from the system the operator has no way of knowing what is the correct action to take.
Traffic Management Center Transit Management Center transportation operational strategies Moderate Moderate Moderate
No PII is involved. However this flow should contain coordinated response information: how various transportation related entities respond to different conditions. This type of information is block intelligence that could be useful to an attacker or criminal, and thus should not be distributed in the clear. If this information is corrupted or modified, transportation management entities may not have well integrated plans for one or more operational scenarios, impacting mobility and safety in those conditions. Given that this data exchange is likely the product of personal work between agencies, and that follow up is likely, justify MODERATE and not HIGH. Probably not updated often, but could contain large amounts of information; additionally in times of crisis may need some more update, so MODERATE justifiable.
Traffic Management Center Transportation Information Center transportation operational strategies Moderate Moderate Moderate
No PII is involved. However this flow should contain coordinated response information: how various transportation related entities respond to different conditions. This type of information is block intelligence that could be useful to an attacker or criminal, and thus should not be distributed in the clear. If this information is corrupted or modified, transportation management entities may not have well integrated plans for one or more operational scenarios, impacting mobility and safety in those conditions. Given that this data exchange is likely the product of personal work between agencies, and that follow up is likely, justify MODERATE and not HIGH. Probably not updated often, but could contain large amounts of information; additionally in times of crisis may need some more update, so MODERATE justifiable.
Traffic Operations Personnel Traffic Management Center traffic operator input Moderate High High
Backoffice operations flows should have minimal protection from casual viewing, as otherwise imposters could gain illicit control or information that should not be generally available. Backoffice operations flows should generally be correct and available as these are the primary interface between operators and system. Backoffice operations flows should generally be correct and available as these are the primary interface between operators and system.
Transit Management Center Other Transit Management Centers transit service coordination Moderate Moderate Moderate
Coordination between transit systems is generally not sensitive, however this flow may include information related to serving individual connection protection requests that are sensitive. If this information is not timely or correct, transit agencies may not properly coordinate, leaving some users unserved. If this information is not timely or correct, transit agencies may not properly coordinate, leaving some users unserved.
Transit Management Center Traffic Management Center transit system data Low Moderate Low
Coordination information between transit and traffic agencies, if compromised, has no obvious impact. Coordination information between transit and traffic agencies needs to be correct, or trip errors (improper dispatch, lack of service) may occur. Some dynamism in this flow, depending on the level of interactivity and coordination, this might be Low.
Transportation Information Center Traffic Management Center fare and price information Low Moderate Moderate
Does not contain any personal or confidential information. While accuracy of this data is important for decision making purposes, the greatest impact if manipulated or incorrect data would be financial and likely limited in scope. For example, making all options appear less expensive than an attacker's route of fiduciary interest, driving revenue to his route. This is undesireable and significant, but not catastrophic. Thus MODERATE generally. While accuracy of this data is important for decision making purposes, applications should be able to function without frequent updates. Thus MODERATE generally.
Transportation Information Center Traffic Management Center logged vehicle routes High Moderate Moderate
These are planned routes that could include predictive information of where a high value target will be at a particular time. A attacker with hostile intent could use this as the basis for an attack. Since this will be used to modify traffic control to support special vehicle movements, and change to or incorrect reception of this data will reduce the effectiveness of those changes to some degree, and could have a substantial negative affect. Consequently, a MODERATE level of integrity checking and consistent availability is justified. Since this will be used to modify traffic control to support special vehicle movements, and change to or incorrect reception of this data will reduce the effectiveness of those changes to some degree, and could have a substantial negative affect. Consequently, a MODERATE level of integrity checking and consistent availability is justified.

Standards

The following table lists the standards associated with physical objects in this service package. For standards related to interfaces, see the specific information flow triple pages.

Name Title Physical Object
NEMA TS 8 Cyber and Physical Security Cyber and Physical Security for Intelligent Transportation Systems Maint and Constr Management Center
Payment Administration Center




System Requirements

System Requirement Need
001 The system shall provide incident command communications with public safety, emergency management, transportation, and other allied response agency centers. 03 Traffic Operations need to be able to collect information describing multi-source, real-time data (both infrastructure and vehicle based) on arterials, freeways, and transit systems to develop operational decisions that can be applied to corridors or to the region as a whole.
002 The system 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. 03 Traffic Operations need to be able to collect information describing multi-source, real-time data (both infrastructure and vehicle based) on arterials, freeways, and transit systems to develop operational decisions that can be applied to corridors or to the region as a whole.
003 The system shall provide other agencies air quality information. 03 Traffic Operations need to be able to collect information describing multi-source, real-time data (both infrastructure and vehicle based) on arterials, freeways, and transit systems to develop operational decisions that can be applied to corridors or to the region as a whole.
004 The system 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 03 Traffic Operations need to be able to collect information describing multi-source, real-time data (both infrastructure and vehicle based) on arterials, freeways, and transit systems to develop operational decisions that can be applied to corridors or to the region as a whole.
005 The system 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 03 Traffic Operations need to be able to collect information describing multi-source, real-time data (both infrastructure and vehicle based) on arterials, freeways, and transit systems to develop operational decisions that can be applied to corridors or to the region as a whole.
006 The system 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. 03 Traffic Operations need to be able to collect information describing multi-source, real-time data (both infrastructure and vehicle based) on arterials, freeways, and transit systems to develop operational decisions that can be applied to corridors or to the region as a whole.
007 The system shall maintain and publish the prices for the electronic payment system. 04 Traffic Operations needs to be able to collect information from transit, parking, and toll operations in order to support development of demand management strategies.
008 The system shall provide the HOT pricing information, including variable pricing based on calendar, time of day, vehicle type and passenger occupancy. 04 Traffic Operations needs to be able to collect information from transit, parking, and toll operations in order to support development of demand management strategies.
009 The system shall provide toll pricing information to other transportation centers. 04 Traffic Operations needs to be able to collect information from transit, parking, and toll operations in order to support development of demand management strategies.
010 The system shall provide parking management data to traffic management centers upon request as part of the implementation of demand management programs in the region. This could include changes to hours of operation or pricing. 03 Traffic Operations need to be able to collect information describing multi-source, real-time data (both infrastructure and vehicle based) on arterials, freeways, and transit systems to develop operational decisions that can be applied to corridors or to the region as a whole.
011 The system 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 Traffic Operations need to be able to collect information describing multi-source, real-time data (both infrastructure and vehicle based) on arterials, freeways, and transit systems to develop operational decisions that can be applied to corridors or to the region as a whole.
012 The system shall provide the capability to provide specific pre-trip and en route directions to travelers (and drivers), including costs, arrival times, and transfer points. 01 Traffic Operations need to be able to use current and forecast road and traffic conditions to develop traffic management plans.
013 The system shall collect and store toll pricing data from payment administration centers, including the price for each road segment to which a toll applies, with the time and date for when it applies. 04 Traffic Operations needs to be able to collect information from transit, parking, and toll operations in order to support development of demand management strategies.
014 The system 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. 04 Traffic Operations needs to be able to collect information from transit, parking, and toll operations in order to support development of demand management strategies.
015 The system shall collect and store transit fare and schedule information from transit management centers. 04 Traffic Operations needs to be able to collect information from transit, parking, and toll operations in order to support development of demand management strategies.
016 The system shall collect and store current transit, parking, and toll fee schedule information provided by regional traveler information centers. 04 Traffic Operations needs to be able to collect information from transit, parking, and toll operations in order to support development of demand management strategies.
017 The system shall send requests to payment administration centers to change pricing, modify restrictions, or modify operations of a toll road facility. 04 Traffic Operations needs to be able to collect information from transit, parking, and toll operations in order to support development of demand management strategies.
018 The system shall send requests to parking management providers to change the current parking lot charging structure. 04 Traffic Operations needs to be able to collect information from transit, parking, and toll operations in order to support development of demand management strategies.
019 The system shall send requests to transit management centers to change the current transit services - schedules or fares of the transit services including park-and-ride lots. 04 Traffic Operations needs to be able to collect information from transit, parking, and toll operations in order to support development of demand management strategies.
020 The system 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. 03 Traffic Operations need to be able to collect information describing multi-source, real-time data (both infrastructure and vehicle based) on arterials, freeways, and transit systems to develop operational decisions that can be applied to corridors or to the region as a whole.
021 The system 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.). 03 Traffic Operations need to be able to collect information describing multi-source, real-time data (both infrastructure and vehicle based) on arterials, freeways, and transit systems to develop operational decisions that can be applied to corridors or to the region as a whole.
022 The system 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 deman 01 Traffic Operations need to be able to use current and forecast road and traffic conditions to develop traffic management plans.
023 The system shall identify network imbalances and potential courses of action. 05 Traffic Operations needs to be able to implement demand management strategies in order to correct network imbalances and effectively manage available capacity.
024 The system shall compare the impact of potential courses of action and make recommendations to the operator. 02 Traffic Operations need to be able to develop operational decisions based upon analysis of current and forecast road and traffic conditions.
025 The system 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. 03 Traffic Operations need to be able to collect information describing multi-source, real-time data (both infrastructure and vehicle based) on arterials, freeways, and transit systems to develop operational decisions that can be applied to corridors or to the region as a whole.
026 The system shall include multimodal strategies that include suggested transit strategies and suggested route and mode choices for travelers. 03 Traffic Operations need to be able to collect information describing multi-source, real-time data (both infrastructure and vehicle based) on arterials, freeways, and transit systems to develop operational decisions that can be applied to corridors or to the region as a whole.
027 The system shall provide an interface to center personnel to input control parameters for the decision support process and receive recommended actions and supporting information presentation. 02 Traffic Operations need to be able to develop operational decisions based upon analysis of current and forecast road and traffic conditions.
028 The system shall provide transportation operational strategies to other centers. 02 Traffic Operations need to be able to develop operational decisions based upon analysis of current and forecast road and traffic conditions.
029 The system 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. 01 Traffic Operations need to be able to use current and forecast road and traffic conditions to develop traffic management plans.
030 The system shall collect wide-area pollution data from emissions management centers to support overall network performance evaluations. 06 Traffic Operations needs to be able to collect emissions data to support development of demand management strategies.
031 The system shall collect and store anticipated route information from traveler information centers to support overall network performance evaluations and predictions. 05 Traffic Operations needs to be able to implement demand management strategies in order to correct network imbalances and effectively manage available capacity.
032 The system 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 cur 04 Traffic Operations needs to be able to collect information from transit, parking, and toll operations in order to support development of demand management strategies.
033 The system 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. 03 Traffic Operations need to be able to collect information describing multi-source, real-time data (both infrastructure and vehicle based) on arterials, freeways, and transit systems to develop operational decisions that can be applied to corridors or to the region as a whole.
034 The system 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. 03 Traffic Operations need to be able to collect information describing multi-source, real-time data (both infrastructure and vehicle based) on arterials, freeways, and transit systems to develop operational decisions that can be applied to corridors or to the region as a whole.
035 The system shall use the collected information to measure overall current and forecast network performance and predict travel demand patterns. 03 Traffic Operations need to be able to collect information describing multi-source, real-time data (both infrastructure and vehicle based) on arterials, freeways, and transit systems to develop operational decisions that can be applied to corridors or to the region as a whole.
036 The system shall coordinate schedules and services with traffic management, parking management, and event planning systems. 04 Traffic Operations needs to be able to collect information from transit, parking, and toll operations in order to support development of demand management strategies.
037 The system shall accept requests from traffic management to change routes and schedules as part of the implementation of demand management strategies. 03 Traffic Operations need to be able to collect information describing multi-source, real-time data (both infrastructure and vehicle based) on arterials, freeways, and transit systems to develop operational decisions that can be applied to corridors or to the region as a whole.