APTS11-Multimodal Connection Protection (Service Package*)

Description

This service package supports the coordination of multimodal services to optimize the travel time of travelers as they move from mode to mode (or to different routes within a single mode). A near term function supported by this service package would be for a single transit agency to coordinate crossing routes so that passengers on one route would have the opportunity to transfer with minimum wait time to another route within the same transit system. The next level of complexity of this service package would be for this coordination to occur across transit agencies, or between transit agencies and other modes of transportation. The most advanced functions of this service package would be to track the route of an individual traveler and ensure that connections are properly scheduled on an individual basis. This final capability represents a long-term functionality, which could be managed either through an Information Serviced Provider or through a Transit Management subsystem.

Service Package Graphic

Remote Transit Information ServicesPersonal Trip Planning and Route GuidanceTransit Center Connection ProtectionInfrastructure Provided Trip PlanningOn-board Connection ProtectionOn-board Transit Fare ManagementTraveler CardMultimodal Transportation Service ProviderOther Transit ManagementRemote Traveler SupportPersonal Information AccessTransit ManagementInformation Service ProviderTransit Vehiclepaymentselected routesrequest for paymentservice requesttransit multimodal informationservice responsemultimodal service datatransit information user requesttransit information user requesttransit service coordinationtransit traveler informationtransit traveler requesttransit trip plantransit trip requesttransit user informationtransit vehicle operator informationtrip confirmationtrip confirmationtrip plantrip plan

Get the Source Graphic, a Windows Metafile (WMF), in ZIP format.
About this Graphic

Includes Architecture Flows:

Source Architecture Flow Destination In Graphic
Information Service Provider selected routes Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Transit Management Yes
Information Service Provider transit trip request Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Transit Management Yes
Multimodal Transportation Service Provider multimodal service data Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Transit Management Yes
Multimodal Transportation Service Provider service response Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Transit Management Yes
Other Transit Management transit service coordination Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Transit Management Yes
Personal Information Access transit information user request Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Transit Management Yes
Personal Information Access trip confirmation Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Transit Management Yes
Remote Traveler Support transit information user request Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Transit Management Yes
Remote Traveler Support trip confirmation Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Transit Management Yes
Transit Management transit trip plan Information Service Provider Yes
Transit Management service request Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Multimodal Transportation Service Provider Yes
Transit Management transit multimodal information Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Multimodal Transportation Service Provider Yes
Transit Management transit service coordination Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Other Transit Management Yes
Transit Management trip plan Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Personal Information Access Yes
Transit Management trip plan Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Remote Traveler Support Yes
Transit Management transit traveler information Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Transit Vehicle 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 Yes
Transit Vehicle transit traveler request Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Transit Management Yes
Transit Vehicle transit user information Transit Management Yes
Transit Vehicle request for payment Traveler Card Yes
Traveler Card payment Transit Vehicle 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.

Associated Planning Factors and Goals

Planning Factor Goal
F. Enhance the integration and connectivity of the transportation system, across and between modes, for people and freight; Enhance the integration and connectivity of the transportation system
G. Promote efficient system management and operation; Increase operational efficiency and reliability of the transportation system

Associated Objective Categories

Objective Category
Integration: Connectivity
System Efficiency: Trip Connectivity

Associated Objectives and Performance Measures

Objective Performance Measure
Reduce door-to-door trip time by X percent by year Y. Average door-to-door trip time.

 
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.

Related ITS Applications of ITS Taxonomy

Classification Category ITS Application Area ITS Application(s)
Intelligent Infrastructure Transit Management Operations & Fleet Management Service Coordination

User Services related to this Service Package:

User Service
2.1 Public Transportation Management
2.2 En-route Transit Information

Transaction Set Diagram





The source graphic, a Windows Metafile (WMF), for the TSD can be downloaded here: TSD

The following discusses how the National ITS Architecture provides the transportation service described by this service package. Each numbered item describes the operation of that portion of the service package identified with the corresponding number on the transaction set diagram.

  1. The Transit Management Subsystem learns of specific traveler trip plans for connections when the traveler, through either an ISPS, PIAS or RTSS, negotiates a specific trip plan (transit trip request, transit trip plan and selected routes). Alternatively, the Transit Management entity may simply know of the expected traveler demand model to need to make specific transit modal connections.

  2. When a traveler pays for a trip (or validates a contract for a trip) on a transit vehicle (TRVS) with their Traveler Card payment instrument, the Transit Vehicle is essentially notified of the travelers presence and specific trip need (request for payment and payment) with possible connection protection requirements.

  3. The TRVS can notify the TRMS of specific transit traveler request or transit user information requirements that may include connection protection as part of normal traveler information operations.

  4. The TRMS now coordinates with Other Transit Management subsystems (transit service coordination) that a transit route needs to wait if necessary for a connection so that specific passengers can make the connection that has been negotiated. Alternatively the TRMS can notify the Multimodal Transportation Service Provider that either there are expected travelers needing to make a connection (transit multimodal information and multimodal service data) or there are specific travelers needing to make the connection (service request and service response).