Parent Service Package: TM07
< < TM06.2 : TM07.1 : TM08.1 > >

TM07.1: Regional Traffic Management Implementation

This 'implementation' is a holistic view of the TM07 service package, including all Physical Objects, Functional Objects, and Triples associated with the service package. It distinguishes between items that are fundamental to the service and items that are optional. Your specific implementation is likely to include the fundamental items and selected optional items, based on your specific project requirements.

Relevant Regions:

Enterprise
Functional
Physical
Goals and Objectives
Needs and Requirements
Sources
Security
Standards
System Requirements

Enterprise

Development Stage Roles and Relationships
(hide)

Source	Destination	Role/Relationship
Other Traffic Management Centers Developer	Other Traffic Management Centers	Develops (hide) An Enterprise creates the target Resource or Document. The Enterprise that engineers a traffic signal controller (ITS Roadway Equipment), or designs a vehicle (Basic Vehicle) or authors a technical standard will have the Develops role.
Other Traffic Management Centers Developer	Traffic Management Center Developer	Application Interface Specification (hide) The definition of an interface between two application components that operate on two distinct pieces of hardware. The Application Interface Specification is specific to the application in question.
Traffic Management Center Developer	Other Traffic Management Centers Developer	Application Interface Specification (hide) The definition of an interface between two application components that operate on two distinct pieces of hardware. The Application Interface Specification is specific to the application in question.
Traffic Management Center Developer	Traffic Management Center	Develops (hide) An Enterprise creates the target Resource or Document. The Enterprise that engineers a traffic signal controller (ITS Roadway Equipment), or designs a vehicle (Basic Vehicle) or authors a technical standard will have the Develops role.

Installation Stage Roles and Relationships
(hide)

Source	Destination	Role/Relationship
Other Traffic Management Centers Installer	Other Traffic Management Centers	Installs (hide) An Enterprise performs the initial delivery, integration and configuration of the target Resource. This might be a system integrator, a state DOT Enterprise performing its own installation, or a device supplier that performs on-site installation.
Other Traffic Management Centers Owner	Other Traffic Management Centers Installer	Installation Agreement (hide) An agreement whereupon one party installs a system on behalf of a second party.
Other Traffic Management Centers Owner	Other Traffic Management Centers Verifier	Verification Agreement (hide) An agreement for one party to verify that a system owned by the second party operates according to the system's design.
Traffic Management Center Installer	Traffic Management Center	Installs (hide) An Enterprise performs the initial delivery, integration and configuration of the target Resource. This might be a system integrator, a state DOT Enterprise performing its own installation, or a device supplier that performs on-site installation.
Traffic Management Center Owner	Traffic Management Center Installer	Installation Agreement (hide) An agreement whereupon one party installs a system on behalf of a second party.
Traffic Management Center Owner	Traffic Management Center Verifier	Verification Agreement (hide) An agreement for one party to verify that a system owned by the second party operates according to the system's design.

Operations and Maintenance Stage Roles and Relationships
(hide)

Source	Destination	Role/Relationship
Other Traffic Management Centers Maintainer	Other Traffic Management Centers	Maintains (hide) An Enterprise administers the hardware and software that comprise the target Resource. The entity that takes the ‘maintains’ role typically is delegated authority by the entity with the “Owns” or "Manages" roles, depending on the environment. The maintainer interacts with the target Resource so as to keep that Resource in the Operational state.
Other Traffic Management Centers Manager	Other Traffic Management Centers	Manages (hide) The Enterprise that is accountable for performing actions with a Resource, typically in support of one of the key operations-related roles (operates, installs, maintains). This authority is typically delegated by the Enterprise with the "Owns" role, and commonly accomplished by delegation to Human E-Objects with the "operates", "installs" or "maintains" roles, depending on the context.
Other Traffic Management Centers Manager	Other Traffic Management Centers Operator	System Usage Agreement (hide) An agreement granting operational use of a system to a Human with the operates role responsible for management of the system.
Other Traffic Management Centers Operator	Other Traffic Management Centers	Operates (hide) A Human that is accountable for performing actions with a Resource, typically in support of one of the key operations-related roles (operates, installs, maintains). This is the person at the console or behind the wheel.
Other Traffic Management Centers Owner	Other Traffic Management Centers Maintainer	System Maintenance Agreement (hide) An agreement for one party to maintain the operational status of a system on behalf of the party with ownership control of the system.
Other Traffic Management Centers Owner	Other Traffic Management Centers Manager	Operations Agreement (hide) An agreement where one entity agrees to operate a device or application on behalf of another, device/application controlling entity.
Other Traffic Management Centers Owner	Traffic Management Center Maintainer	Maintenance Data Exchange Agreement (hide) An agreement that states one entity will provide data related to maintenance of an application component to the other entity.
Other Traffic Management Centers Owner	Traffic Management Center Owner	Information Exchange Agreement (hide) An agreement to exchange information, which may include data or control information; the exact information to be exchanged may vary from agreement to agreement.
Other Traffic Management Centers Owner	Traffic Management Center User	Service Usage Agreement (hide) An agreement between the provider of a service and a user. Stipulates the terms and conditions of service usage.
Other Traffic Management Centers Owner	Traffic Operations Personnel	Application Usage Agreement (hide) An agreement in which one entity that controls an application component's use gives the other entity the necessary tools and permission to operate that application or application component.
Other Traffic Management Centers Supplier	Other Traffic Management Centers Owner	Warranty (hide) A guarantee or promise made by one entity to another, that provides assurance of the functionality and performance of a subsystem.
Traffic Management Center Maintainer	Traffic Management Center	Maintains (hide) An Enterprise administers the hardware and software that comprise the target Resource. The entity that takes the ‘maintains’ role typically is delegated authority by the entity with the “Owns” or "Manages" roles, depending on the environment. The maintainer interacts with the target Resource so as to keep that Resource in the Operational state.
Traffic Management Center Manager	Traffic Management Center	Manages (hide) The Enterprise that is accountable for performing actions with a Resource, typically in support of one of the key operations-related roles (operates, installs, maintains). This authority is typically delegated by the Enterprise with the "Owns" role, and commonly accomplished by delegation to Human E-Objects with the "operates", "installs" or "maintains" roles, depending on the context.
Traffic Management Center Manager	Traffic Operations Personnel	System Usage Agreement (hide) An agreement granting operational use of a system to a Human with the operates role responsible for management of the system.
Traffic Management Center Owner	Other Traffic Management Centers Maintainer	Maintenance Data Exchange Agreement (hide) An agreement that states one entity will provide data related to maintenance of an application component to the other entity.
Traffic Management Center Owner	Other Traffic Management Centers Operator	Application Usage Agreement (hide) An agreement in which one entity that controls an application component's use gives the other entity the necessary tools and permission to operate that application or application component.
Traffic Management Center Owner	Other Traffic Management Centers Owner	Information Exchange Agreement (hide) An agreement to exchange information, which may include data or control information; the exact information to be exchanged may vary from agreement to agreement.
Traffic Management Center Owner	Other Traffic Management Centers User	Service Usage Agreement (hide) An agreement between the provider of a service and a user. Stipulates the terms and conditions of service usage.
Traffic Management Center Owner	Traffic Management Center Maintainer	System Maintenance Agreement (hide) An agreement for one party to maintain the operational status of a system on behalf of the party with ownership control of the system.
Traffic Management Center Owner	Traffic Management Center Manager	Operations Agreement (hide) An agreement where one entity agrees to operate a device or application on behalf of another, device/application controlling entity.
Traffic Management Center Supplier	Traffic Management Center Owner	Warranty (hide) A guarantee or promise made by one entity to another, that provides assurance of the functionality and performance of a subsystem.
Traffic Operations Personnel	Traffic Management Center	Operates (hide) A Human that is accountable for performing actions with a Resource, typically in support of one of the key operations-related roles (operates, installs, maintains). This is the person at the console or behind the wheel.

Functional

This service package includes the following Functional View PSpecs:

Physical Object	Functional Object	PSpec Number	PSpec Name
Traffic Management Center	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

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
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.
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.

Includes Functional Objects:

Functional Object	Description	Physical Object
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

Includes Information Flows:

Information Flow	Description
device control request	Request for device control action
device data	Data from detectors, environmental sensor stations, roadside equipment, and traffic control devices, including device inventory information.
device status	Status information from devices
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.
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.
traffic image meta data	Meta data that describes traffic images. Traffic images (video) are in another flow.
traffic images	High fidelity, real-time traffic images suitable for surveillance monitoring by the operator or for use in machine vision applications. This flow includes the images. Meta data that describes the images is contained in another flow.
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.

Goals and Objectives

Associated Planning Factors and Goals

Planning Factor	Goal

Associated Objective Categories

Objective Category

Associated Objectives and Performance Measures

Objective	Performance Measure

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

Related Sources

Document Name	Version	Publication Date
None

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
Other Traffic Management Centers
Traffic Management Center

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
Source	Destination	Information Flow	Basis	Basis	Basis
Other Traffic Management Centers	Traffic Management Center	device control request	Moderate	High	Moderate
Other Traffic Management Centers	Traffic Management Center	device control request	Control flows, even for seemingly innocent devices, should be kept confidential to minimize attack vectors. While an individual installation may not be particularly impacted by a cyberattack of its sensor network, another installation might be severely impacted, and different installations are likely to use similar methods, so compromising one leads to compromising all.	Control flows, even for seemingly innocent devices, should have MODERATE integrity at minimum, just to guarantee that intended control messages are received. Incorrect, corrupted, intercepted and modified control messages can or will result in target field devices not behaving according to operator intent. The severity of this depends on the type of device, which is why some devices are set MODERATE and some HIGH.	There should be multiple mechanisms for this information to arrive at the end recipient. If this is the only mechanism, should be raised to MODERATE.
Other Traffic Management Centers	Traffic Management Center	device data	Moderate	Moderate	Low
Other Traffic Management Centers	Traffic Management Center	device data	Contains device identity, location and capabilities. If this information were available to a cybercriminal, it may make his task easier and compromise the systems involved.	If this is corrupted, the other center will not properly understand the device capabilities and not properly leverage them, costing performance.	Probably does not need to be updated often.
Other Traffic Management Centers	Traffic Management Center	device status	Moderate	Moderate	Moderate
Other Traffic Management Centers	Traffic Management Center	device status	Device status information should be concealed, as an unauthorized observer could use this to reverse engineer device control systems.	Device status information needs to be available and correct, or the controlling system may take inappropriate maintenance action, costing time and money.	Device status information needs to be available and correct, or the controlling system may take inappropriate maintenance action, costing time and money.
Other Traffic Management Centers	Traffic Management Center	incident information	High	Moderate	Moderate
Other Traffic Management Centers	Traffic Management Center	incident information	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
Other Traffic Management Centers	Traffic Management Center	road network conditions	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	traffic image meta data	Low	Moderate	Moderate
Other Traffic Management Centers	Traffic Management Center	traffic image meta data	Traffic image data is generally intended for public consumption, and in any event is already video captured in the public arena, so this must be LOW.	While accuracy of this data is important for decision making purposes, applications should be able to cfunction without it. Thus MODERATE generally.	While accuracy of this data is important for decision making purposes, applications should be able to function without it. Thus MODERATE generally.
Other Traffic Management Centers	Traffic Management Center	traffic images	Low	Moderate	Low
Other Traffic Management Centers	Traffic Management Center	traffic images	Traffic image data is generally intended for public consumption, and in any event is already video captured in the public arena, so this must be LOW.	Generally transportation coordination information should be correct between source and destination, or inappropriate actions may be taken.	While useful, there is no signficant impact if this flow is not available.
Traffic Management Center	Other Traffic Management Centers	device control request	Moderate	High	Moderate
Traffic Management Center	Other Traffic Management Centers	device control request	Control flows, even for seemingly innocent devices, should be kept confidential to minimize attack vectors. While an individual installation may not be particularly impacted by a cyberattack of its sensor network, another installation might be severely impacted, and different installations are likely to use similar methods, so compromising one leads to compromising all.	Control flows, even for seemingly innocent devices, should have MODERATE integrity at minimum, just to guarantee that intended control messages are received. Incorrect, corrupted, intercepted and modified control messages can or will result in target field devices not behaving according to operator intent. The severity of this depends on the type of device, which is why some devices are set MODERATE and some HIGH.	There should be multiple mechanisms for this information to arrive at the end recipient. If this is the only mechanism, should be raised to MODERATE.
Traffic Management Center	Other Traffic Management Centers	device data	Moderate	Moderate	Low
Traffic Management Center	Other Traffic Management Centers	device data	Contains device identity, location and capabilities. If this information were available to a cybercriminal, it may make his task easier and compromise the systems involved.	info needs to be accurate and should not be tampered but should be able to cope with some bad data; includes inventory data which could lead to loss of assets if compromised	data should be timely and readily available, but should not have limited consequences if not
Traffic Management Center	Other Traffic Management Centers	device status	Moderate	Moderate	Low
Traffic Management Center	Other Traffic Management Centers	device status	Device status information should be concealed, as an unauthorized observer could use this to reverse engineer device control systems.	info needs to be accurate and should not be tampered but should be able to cope with some bad data' could delay maintenance actions or waste resources checking devices that are actually in good status	status infor should be timely and readily available, but should have very limited consequences if not
Traffic Management Center	Other Traffic Management Centers	incident information	High	Moderate	Moderate
Traffic Management Center	Other Traffic Management Centers	incident information	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
Traffic Management Center	Other Traffic Management Centers	road network conditions	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	traffic image meta data	Low	Moderate	Moderate
Traffic Management Center	Other Traffic Management Centers	traffic image meta data	Traffic image data is generally intended for public consumption, and in any event is already video captured in the public arena, so this must be LOW.	While accuracy of this data is important for decision making purposes, applications should be able to cfunction without it. Thus MODERATE generally.	While accuracy of this data is important for decision making purposes, applications should be able to function without it. Thus MODERATE generally.
Traffic Management Center	Other Traffic Management Centers	traffic images	Low	Moderate	Moderate
Traffic Management Center	Other Traffic Management Centers	traffic images	Traffic image data is generally intended for public consumption, and in any event is already video captured in the public arena, so this must be LOW.	While accuracy of this data is important for decision making purposes, applications should be able to cfunction without it. Thus MODERATE generally.	While accuracy of this data is important for decision making purposes, applications should be able to cfunction without it. Thus MODERATE generally.
Traffic Management Center	Traffic Operations Personnel	traffic operator data	Moderate	Moderate	Moderate
Traffic Management Center	Traffic Operations Personnel	traffic operator data	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 Operations Personnel	Traffic Management Center	traffic operator input	Moderate	High	High
Traffic Operations Personnel	Traffic Management Center	traffic operator input	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.

Standards

Currently, there are no standards associated with the physical objects in this service package. For standards related to interfaces, see the specific information flow triple pages. These pages can be accessed directly from the SVG diagram(s) located on the Physical tab, by clicking on each information flow line on the diagram.

System Requirements

No System Requirements