< < TM02 : TM02 : TM02 > >

TM02: Wide-Area Wireless Communications

Use Wide Area Wireless communications to collect traffic information from participating vehicles.

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

Enterprise

Development Stage Roles and Relationships

Installation Stage Roles and Relationships

Operations Stage Roles and Relationships
(hide)

Source Destination Role/Relationship

Maintenance Stage Roles and Relationships

Functional

This service package includes the following Functional View PSpecs:

Physical Object Functional Object PSpec Number PSpec Name

Physical

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

Physical diagrams have not been developed for this application yet.


Display Legend in SVG or PNG

Includes Physical Objects:

Physical Object Class Description

Includes Functional Objects:

Functional Object Description Physical Object

Includes Information Flows:

Information Flow Description

Goals and Objectives

Associated Planning Factors and Goals

Planning Factor Goal
D. Increase the accessibility and mobility of people and for freight; Reduce congestion
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
J. Enhance travel and tourism. Support travel and tourism

Associated Objective Categories

Objective Category
Arterial Management: Traffic Monitoring and Data Collection
Freeway Management: Transportation Management Centers
Special Event Management: Use of Technology
Traveler Information: Data Collection and Sharing on Travel Conditions

Associated Objectives and Performance Measures

Objective Performance Measure
Field data collection is conducted either through floating car studies or other methods at least once every Y years on major signalized arterials and X years on minor signalized arterials. Number of field data collection studies performed every Y and X years on major and minor signalized arterials, respectively.
Increase the percent of major special events using ITS-related assets (e.g., roadside cameras, dynamic message signs, vehicle speed detectors) to detect and manage special event entry/exit bottlenecks and incidents by X percent in Y years. Percent of special events using ITS-related assets to detect and manage incidents/bottlenecks at entry/exit routes of the events.
Increase the percent of modes in the region that share their traveler information with other modes in the region to 100 percent by Y year. Percent of modes in the region that share their traveler information with other modes.
Increase the percent of regional transportation system monitored by the TMC for real-time performance. Percent of regional transportation system monitored by the TMC for real-time performance.
Increase the percent of the transportation system in which travel conditions can be detected remotely via CCTV, speed detectors, etc. to X percent by Y year. Percent of the transportation system in which travel conditions can be detected remotely via CCTV, speed detectors, etc.
Increase the percent of transportation facilities whose owners share their traveler information with other agencies in the region to X percent by Y year. Percent of transportation facilities whose owners share their traveler information with other agencies in the region.

 
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

  • 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
Security levels have not been defined yet.



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
Security levels have not been defined yet.

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.





Needs and Requirements

Need Functional Object Requirement

System Requirements

No System Requirements