APTS11-Multimodal Connection Protection (Service Package*)
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
Get the Source Graphic, a Windows Metafile (WMF), in ZIP format.
About this Graphic
Includes Equipment Packages and Subsystems:
Includes Architecture Flows:
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.
Related ITS Applications of ITS Taxonomy
||ITS Application Area
||Operations & Fleet Management
User Services related to this Service Package:
Transaction Set Diagram
The source graphic, a Windows Metafile (WMF), for the TSD can be downloaded here:
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.
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.
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.
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.
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).