EM04-Roadway Service Patrols (Market Package*)

Market Package Graphic       Transaction Set Diagram

Description

This market package supports roadway service patrol vehicles that monitor roads that aid motorists, offering rapid response to minor incidents (flat tire, accidents, out of gas) to minimize disruption to the traffic stream. If problems are detected, the roadway service patrol vehicles will provide assistance to the motorist (e.g., push a vehicle to the shoulder or median). The market package monitors service patrol vehicle locations and supports vehicle dispatch to identified incident locations. Incident information collected by the service patrol is shared with traffic, maintenance and construction, and traveler information systems.

Includes Equipment Packages and Subsystems:

Includes Architecture Flows:

Source Architecture Flow Destination In Graphic
Emergency Management emergency operations status Emergency System Operator Yes
Emergency Management emergency dispatch requests Emergency Vehicle Subsystem Yes
Emergency Management incident information Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Information Service Provider Yes
Emergency Management incident information Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Maintenance and Construction Management Yes
Emergency Management incident information Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Traffic Management Yes
Emergency System Operator emergency operations inputs Emergency Management Yes
Emergency Vehicle Subsystem emergency dispatch response Emergency Management Yes
Emergency Vehicle Subsystem emergency vehicle tracking data Emergency Management Yes
Emergency Vehicle Subsystem incident status Emergency Management Yes
Location Data Source position fix Emergency Vehicle Subsystem Yes
    - This icon indicates that the associated architecture flow either has been or will be addressed by ITS Standards. Select the architecture flow for more information on relevant standards activities.

Early Deployment

This market package has been identified as an early deployment due to a promising combination of low risk implementation characteristics, developing public or private markets for the package, and tangible system or user benefits. This Market Package plays an important role in identifying problems that occur on arterials or the freeway by traveling sections of the roadway that typical have incidents. This Market Package is a key component to enhancing safety in conjunction with the Incident Management Market Package.

Rural Development

For the Traffic Management Rural Development Track, this market package is applicable to a significant number of rural user needs, may require some augmentation for the rural environment. It addresses the needs of the broad rural development track by the following: Allows the coordination among emergency services agencies and traffic management, to provide incident status and severity information.

For the Emergency Services Rural Development Track, this market package is highly applicable to rural user needs and suitable for the rural environment. It addresses the needs of the broad rural development track by the following: Allows emergency patrol agencies to traverse roadway segments to identify problems in the traffic stream to allow for rapid response.

ITS Goals Supported

    ITS Goal Satisfaction Level
    Increase Transportation System Efficiency and Capacity *
    Improve Safety * * *
    Reduce Energy Consumption and Environmental Costs *
    Increase Economic Productivity * *
    Create an Environment for an ITS Market *
    * Features that marginally satisfy the goals
    * * Features that almost satisfy every aspect of the goals
    * * * Features completely satisfy every aspect of the goals

User Services related to this Market Package:

Problem / Solution Pairs this Market Package Addresses

Hypertext Architecture Version 6.1 generated on 1/7/2009 from the following databases
Physical Architecture dated 12/15/2008,
Logical Architecture dated 12/2/2008,
Market Packages dated 12/14/2008,
Security dated 11/13/2008,
User Services dated 4/9/2007,
Theory of Operations dated 12/14/2008,
AppMap dated 12/19/2008 and the
SDOMAP dated 12/12/2008