ATIS08-Dynamic Ridesharing (Service Package*)

Description

This service package provides dynamic ridesharing/ride matching services to travelers. This service could allow near real time ridesharing reservations to be made through the same basic user equipment used for Interactive Traveler Information. This ridesharing/ride matching capability also includes arranging connections to transit or other multimodal services.

Service Package Graphic

Infrastructure Provided Trip PlanningPersonal Interactive Information ReceptionVehicle Trip Planning and Route GuidanceRemote Interactive Information ReceptionInfrastructure Provided Dynamic RidesharingISP Traveler Data CollectionMap Update ProviderTransit ManagementInformation Service ProviderPersonal Information AccessVehicleRemote Traveler SupportTraveler CardTravelerMultimodal Transportation Service Providermap updatestrip plandemand responsive transit plandemand responsive transit requesttrip requesttrip confirmationtrip plantrip requesttrip confirmationrequest for paymentpaymentrequest for paymentpaymenttraveler interface updatestraveler inputstraveler interface updatestraveler inputsmultimodal information requestmultimodal informationtrip plantrip requesttrip confirmation

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

Includes Architecture Flows:

Source Architecture Flow Destination In Graphic
Driver driver inputs Vehicle No
Financial Institution transaction status Information Service Provider No
Information Service Provider payment request Financial Institution No
Information Service Provider ISP operations information presentation ISP Operator No
Information Service Provider map update request Map Update Provider No
Information Service Provider multimodal information request Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Multimodal Transportation Service Provider Yes
Information Service Provider trip plan Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Personal Information Access Yes
Information Service Provider trip plan Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Remote Traveler Support Yes
Information Service Provider demand responsive transit request Transit Management Yes
Information Service Provider trip plan Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Vehicle Yes
ISP Operator ISP operator inputs Information Service Provider No
Map Update Provider map updates Information Service Provider Yes
Multimodal Transportation Service Provider multimodal information Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Information Service Provider Yes
Personal Information Access trip confirmation Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Information Service Provider Yes
Personal Information Access trip request Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Information Service Provider Yes
Personal Information Access traveler interface updates Traveler Yes
Personal Information Access request for payment Traveler Card Yes
Remote Traveler Support trip confirmation Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Information Service Provider Yes
Remote Traveler Support trip request Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Information Service Provider Yes
Remote Traveler Support traveler interface updates Traveler Yes
Remote Traveler Support request for payment Traveler Card Yes
Transit Management demand responsive transit plan Information Service Provider Yes
Traveler traveler inputs Personal Information Access Yes
Traveler traveler inputs Remote Traveler Support Yes
Traveler Card payment Personal Information Access Yes
Traveler Card payment Remote Traveler Support Yes
Vehicle driver updates Driver No
Vehicle trip confirmation Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Information Service Provider Yes
Vehicle trip request Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Information Service Provider 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
A. Support the economic vitality of the metropolitan area, especially by enabling global competitiveness, productivity, and efficiency; Support regional economic productivity and development
D. Increase the accessibility and mobility of people and for freight; Enhance mobility, convenience, and comfort for transportation system users
E. Protect and enhance the environment, promote energy conservation, improve the quality of life, and promote consistency between transportation improvements and State and local planned growth and economic development patterns; Reduce environmental impacts
G. Promote efficient system management and operation; Increase operational efficiency and reliability of the transportation system

Associated Objective Categories

Objective Category
Special Event Management: Mode Shift from SOV
System Efficiency: Cost of Congestion
System Efficiency: Delay
System Efficiency: Duration of Congestion
System Efficiency: Energy Consumption
System Efficiency: Extent of Congestion
System Efficiency: Intensity of Congestion (Travel Time Index)
System Efficiency: Travel Time
System Efficiency: Vehicle Miles Traveled
System Options: Mode Share
Travel Demand Management: Carpool/Vanpool

Associated Objectives and Performance Measures

Objective Performance Measure
Achieve X percent alternative (non-SOV) mode share in transit station communities (or other destinations) by year Y. Percent of all trips made using alternative modes in transit station communities.
Annual rate of change in regional average commute travel time will not exceed regional rate of population growth through the year Y. Average commute trip travel time (minutes).
Create and share regional carpool/vanpool database with Z number of employers per year. Number of employers with access to regional carpool/vanpool database.
Decrease the percent of special event attendees traveling to the event in single-occupancy vehicles by X percent in Y years. Percent of special event attendees using single-occupancy vehicles each year for selected events.
Improve average travel time during peak periods by X percent by year Y. Average travel time during peak periods (minutes).
Increase alternative (non-SOV) mode share for all trips by X percent within the next Y years. Share of trips by each mode of travel.
Increase the number of carpools by X percent over the next Y years. Share of household trips by each mode of travel.
Increase the percent of special event attendees using park & ride lots by X percent in Y years. Percent of special event attendees utilizing park & ride lots each year for selected events.
Increase the percent of special events with dedicated shuttle service by X percent in Y years. Percent of special events with dedicated shuttle service for selected events during a 1-year period.
Increase use of vanpools by X percent over the next Y years. Share of household trips by each mode of travel.
Maintain the rate of growth in facility miles experiencing recurring congestion as less than the population growth rate (or employment growth rate). Percent of lane-miles (or rail) operating at LOS F or V/C > 1.0
Provide carpool/vanpool matching and ridesharing information services by year Y. Availability of carpool/vanpool matching and ridesharing information services.
Reduce excess fuel consumed due to congestion by X percent by year Y. Excess fuel consumed (total or per capita).
Reduce hours of delay per capita by X percent by year Y. Hours of delay (person-hours).
Reduce hours of delay per capita by X percent by year Y. Hours of delay per capita.
Reduce hours of delay per driver by X percent by year Y. Hours of delay (person-hours).
Reduce hours of delay per driver by X percent by year Y. Hours of delay per driver.
Reduce SOV vehicle trips by X percent through travel demand management strategies (e.g., employer or residential rideshare) by year Y. Share of employees walking, biking, telecommuting, carpooling/vanpooling, riding transit, driving alone.
Reduce the annual monetary cost of congestion per capita for the next X years. Cost (in dollars) of congestion or delay per capita.
Reduce the daily hours of recurring congestion on major freeways from X to Y by year Z. Hours per day at LOS F or V/C > 1.0 (or other threshold).
Reduce the number of hours per day that the top 20 most congested roadways experience recurring congestion by X percent by year Y. Hours per day at LOS F or V/C > 1.0 (or other threshold).
Reduce the percentage of facility miles (highway, arterial, rail, etc.) experiencing recurring congestion during the peak period by X percent by year Y. Percent of lane-miles (or rail) operating at LOS F or V/C > 1.0
Reduce the regional average travel time index by X percent per year. Travel time index (the average travel time during the peak period, using congested speeds, divided by the off-peak period travel time, using posted or free-flow speeds).
Reduce the share of major intersections operating at LOS Z by X percent by year Y. Percent of intersections operating at LOS F or V/C > 1.0
Reduce total energy consumption per capita for transportation by X percent by year Y. Total energy consumed per capita for transportation.
Reduce total fuel consumption per capita for transportation by X percent by year Y. Total fuel consumed per capita for transportation.
Reduce trips per year in region by X percent through carpools/vanpools. Number of person trips by carpool/vanpool in region.
Reduce trips per year in region by X percent through carpools/vanpools. Number of trips in region.
Reduce vehicle miles traveled per capita by X percent by year Y. Average VMT per capita per day, per week, or per year.

 
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 Transportation Demand Management Ride Sharing/Matching

User Services related to this Service Package:

User Service
1.4 Ride Matching And Reservation
1.8 Travel Demand Management
2.3 Personalized Public Transit

Transaction Set Diagram

Note that this transaction set diagram (TSD) is only 1 of the 3 TSDs and so only a portion of the numbered items below refer to the TSD.
ATIS08 transaction set diagrams: Part 1, Part 2, Part 3,



The source graphic, a Windows Metafile (WMF), for the TSDs can be downloaded here: TSD Part 1, TSD Part 2, TSD Part 3,

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 entire process is under the asynchronous monitoring (ISP operations information presentation) and control (ISP operator inputs) by the ISP Operator.

  2. Periodically, possibly by subscription or by regularly scheduled requests (map update request), Information Service Providers may request and download map updates from a Map Update Provider.

  3. Schedule information for alternate mode transportation providers such as train, ferry, air and bus (multimodal information) can be received by Information Service Providers as either direct response to their multimodal information request or as subscription transactions.

  4. Optionally, asynchronously, and as often as desired, a Driver may request (driver inputs) a ride match.

  5. Once a route is requested by the Driver (driver inputs), a continuous cycle occurs (through Step 8), beginning with the driver’s ride-match request being sent (trip request). The ride-match request the Driver enters may be on behalf of the passengers using his shuttle service or it may be his own individual trip.

  6. The Information Service Provider sends a suggested ride-match and its associated information (trip plan) back to the Vehicle.

  7. The Vehicle Subsystem presents the ride-match to the Driver (driver updates), and then the Driver either accepts the match (and the cycle stops) or asks for another match (and the cycle repeats – back to Step 5).

  8. Once the Driver has accepted a ride-match, a confirmation that the match has been accepted is sent back to the ISP (trip confirmation).

  9. An ISP may present a request for payment (payment request) and then receive transaction status on that request from a Financial Institution. This would depend upon whether there is a fee for the ride-matching service.

  10. Optionally, asynchronously, and as often as desired, a Traveler (passenger) may request (traveler inputs) a ride-match via personal computing device or kiosk.

  11. Once a ride-match is requested by the Traveler (traveler inputs), a continuous cycle occurs (through Step 16), beginning with the traveler’s match request being sent (trip request).

  12. One way a ride-match request can be satisfied is through paratransit or other demand responsive transit service. If this is acceptable to the Traveler, a demand responsive transit request is sent to the Transit Management Subsystem for a plan. If paratransit services can fulfill the ride request, then a demand responsive transit plan is returned to the ISP.

  13. The Information Service Provider sends a suggested ride-match and its associated information (trip plan) back to the device that originated the ride-match request (Step 11).

  14. The ride-match is then presented to the Traveler (traveler interface updates), and then the Driver either accepts the match (and the cycle stops) or asks for another match (and the cycle repeats – back to Step 11).

  15. Optionally, in conjunction with the financial transaction with the Financial Institution (step 20 below), a request for payment and corresponding payment may be made using the Traveler Card. If payment is required for the information request, and the Traveler Card is capable of making the payment, the transaction with the Financial Institution may not occur. This Traveler Card payment may be a minimum charge merely required just to use a public device such as a kiosk, and a separate transaction charge may also be required, depending upon the service.

  16. Once the Traveler has accepted a ride-match, a confirmation that the match has been accepted is sent back to the ISP (trip confirmation).

  17. If the ride-match included the use of paratransit or other demand responsive transit (from Step 13), then notification is sent back to confirm that usage and a request to do the pick-up (demand responsive transit request).

  18. An ISP may present a request for payment (payment request) and then receive transaction status on that request from a Financial Institution. This would depend upon whether there is a fee for the ride-matching service.