APTS03-Demand Response Transit Operations (Market Package*)

Market Package Graphic       Transaction Set Diagram

Description

This market package performs automated dispatch and system monitoring for demand responsive transit services. This service performs scheduling activities as well as operator assignment. In addition, this market package performs similar functions to support dynamic features of flexible-route transit services. This package monitors the current status of the transit fleet and supports allocation of these fleet resources to service incoming requests for transit service while also considering traffic conditions. The Transit Management Subsystem provides the necessary data processing and information display to assist the transit operator in making optimal use of the transit fleet. This service includes the capability for a traveler request for personalized transit services to be made through the Information Service Provider (ISP) Subsystem. The ISP may either be operated by a transit management center or be independently owned and operated by a separate service provider. In the first scenario, the traveler makes a direct request to a specific paratransit service. In the second scenario, a third party service provider determines that the paratransit service is a viable means of satisfying a traveler request and makes a reservation for the traveler.

Includes Equipment Packages and Subsystems:

Includes Architecture Flows:

Source Architecture Flow Destination In Graphic
Information Service Provider demand responsive transit request Transit Management Yes
Information Service Provider selected routes Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Transit Management Yes
Maintenance and Construction Management current asset restrictions Transit Management Yes
Maintenance and Construction Management roadway maintenance status Transit Management Yes
Maintenance and Construction Management work zone information Transit Management Yes
Traffic Management incident information Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Transit Management Yes
Traffic Management road network conditions Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Transit Management Yes
Transit Management demand responsive transit plan Information Service Provider Yes
Transit Management transit and fare schedules Information Service Provider Yes
Transit Management transit schedule adherence information Information Service Provider Yes
Transit Management transit operations status Transit Operations Personnel Yes
Transit Management route assignment Transit Vehicle Operator Yes
Transit Management transit vehicle operator information Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Transit Vehicle Subsystem Yes
Transit Operations Personnel transit operations personnel inputs Transit Management Yes
Transit Vehicle Operator transit vehicle operator availability Transit Management Yes
Transit Vehicle Operator transit vehicle operator inputs Transit Vehicle Subsystem Yes
Transit Vehicle Subsystem demand response passenger and use data Transit Management Yes
Transit Vehicle Subsystem transit vehicle operator display Transit Vehicle Operator 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. As with the fixed route operations package, this Market Package provides many of the core operations and planning functions that would be required by the larger demand responsive fleet.

Rural Development

For the Crash Prevention and Security Rural Development Track, this market package is applicable to rural user needs, but has limitations for the rural environment. It addresses the needs of the broad rural development track by the following: Allow transit agencies to receive traffic information (e.g., congestion levels, accidents) to allow them to make route changes to mitigate the potential for secondary incidents.

For the Rural Transit and Mobility 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: Systems that provide automatic scheduling and provide support for dynamic vehicle routing. The transit agency or a local information service provider can provide vehicle routing directions. System also aids in schedule and route adherence.

For the Tourism and Travel Rural Development Track, this market package is applicable to rural user needs, but has limitations for the rural environment. It addresses the needs of the broad rural development track by the following: Services that provide driver assignment and vehicle routing for paratransit vehicles (e.g., dial-a-ride) while considering traffic conditions.

ITS Goals Supported

    ITS Goal Satisfaction Level
    Increase Transportation System Efficiency and Capacity *
    Enhance Mobility * *
    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