Regional Architecture Logo
 

Send Your Comments

E-Mail

Personal Provider-Based Route Guidance Equipment Package

Architecture Geographic Scope

Description:

This Equipment package coordinates with an ISP-Based route planning service to select a suggested route plan that is tailored to the traveler's preferences. Coordination may continue during the trip so that the route plan can be modified to account for new information. Many equipment configurations are possible including systems that provide a basic route plan to the traveler as well as more sophisticated systems that can provide transition by transition guidance to the traveler along a multi-modal route plan.

 

Included in:

Private Traveler Personal Computing Devices

Processes:

6.8.1.1.1Determine Personal Portable Device Guidance Method
6.8.1.1.2Provide Personal Portable Device Dynamic Guidance
6.8.1.2Provide Personal Portable Device Guidance Interface
6.8.1.4Update Traveler Navigable Map Database
6.8.3.3Provide Traveler Personal Interface
  

User Service Requirements (fully or partially addressed):

1.0TRAVEL AND TRAFFIC MANAGEMENT
1.1.0ITS shall include a Pre-Trip Travel Information (PTTI) capability to assist travelers in making mode choices, travel time estimates, and route decisions prior to trip departure. It consists of four major functions, which are, (1) Available Services Information, (2) Current Situation Information, (3) Trip Planning Service, and (4) User Access. Information is integrated from various transportation modes and presented to the user for decision making.
1.1.3PTTI shall include a Trip Planning Service.
1.1.3.2PTTI shall provide the capability for users to specify transportation parameters that are unique to their individual needs.
1.1.3.2.1PTTI shall provide the capability for users to specify a desired destination.
1.1.3.2.2PTTI shall provide the capability for users to specify a planned departure location.
1.1.3.2.3PTTI shall provide the capability for users to specify their desired departure time.
1.1.3.2.4PTTI shall provide the capability for users to specify their desired arrival time.
1.1.3.2.5PTTI shall provide the capability for users to specify their maximum acceptable travel time.
1.1.3.2.6PTTI shall provide the capability for users to specify their maximum acceptable number of mode changes.
1.1.3.2.7PTTI shall provide the capability for users to specify a maximum number of transfers.
1.1.3.2.8PTTI shall provide the capability for users to specify their preferred route(s) or segment of route(s).
1.1.3.2.9PTTI shall provide the capability for users to specify their preferred transportation mode(s).
1.1.3.2.10PTTI shall provide the capability for users to specify their preferred weather conditions.
1.1.4PTTI shall provide the capability for User Access.
1.1.4.2PTTI shall provide the capability for users to access the system over multiple types of electronic media.
1.1.4.2.1Access media shall comply with the Americans with Disabilities Act (ADA) legislation.
1.3ROUTE GUIDANCE
1.3.0ITS shall include a Route Guidance (RG) function. Route Guidance will provide travelers with directions to selected destinations. Four functions are provided, which are, (1) Provide Directions, (2) Static Mode, (3) Real-Time Mode, and (4) User Interface.
1.3.1RG shall include the capability to Provide Directions to travelers.
1.3.1.1The Provide Directions function shall provide travelers with directions to their selected destination locations.
1.3.1.2The Provide Directions function shall issue directions to travelers based on information about current conditions of transportation systems.
1.3.1.2.1Current transportation system conditions upon which directions to travelers is based shall include, but not be limited to, the following:
1.3.1.3The Provide Directions function shall issue traveler directions that are simple and easy to understand, providing turning instructions on which way to turn onto including, but not limited to, the following:
1.3.2RG shall include a Static Mode for issuing information to travelers.
1.3.2.2Static Mode infrastructure systems shall provide the capability to have two-way communications between the traveler and the infrastructure.
1.3.2.3The Real-Time Mode shall provide the capability for autonomous operation of mobile based systems.
1.3.2.3.1Autonomous Mobile Based systems shall have the capability to operate independent of infrastructure.
1.3.3RG shall include a Real-Time Mode for issuing information to travelers.
1.3.3.2The Real-Time Mode shall include the capability to operate in either or both of the following two configurations:
1.3.3.2.2If current real-time information is included in route determination, the system shall be denoted as an Infrastructure-based real-time system.
1.3.3.3The Real-Time Mode shall provide the capability for autonomous operation of mobile-based systems.
1.3.4RG shall include a User Interface function.
1.3.4.1The User Interface function shall provide the capability for travelers to access the system by utilizing interactive devices that include, but are not limited to, the following:
1.3.4.1(b)Keypads.
1.3.4.1(c)Touch sensitive devices.
1.3.4.1(d)Computer generated voice.
1.3.4.1(e)Voice recognition system.
1.3.4.2Mobile systems shall use the best information available to provide routing instructions.
1.3.4.2.1Mobile systems shall provide the capability for individual travelers to customize the routing selected for them.
1.3.4.2.2Mobile systems shall allow customization of traveler's routing based on certain conditions specified by the traveler to include, but not be limited to, the following:
1.3.4.3Infrastructure-based systems shall permit individual travelers to customize their routing selection.
1.4.0ITS shall include a Ride Matching and Reservation (RMR) function. Ride Matching and Reservation will provide travel users with information on rideshare providers. Three major functions are provided, which are, (1) Rider Request, (2) Transportation Provider Services, and (3) Information Processing. This will also include a billing service to the providers.
1.4.1RMR shall include a Rider Request capability.
1.4.1.1Rider Request shall provide the capability for a traveler to request a ride by placing a single request from a facility to include, but not be limited to, the following:
1.4.1.2Rider Request shall provide a traveler the capability to request a specific itinerary by specifying, but not be limited to, the following:
1.4.1.3Rider Request shall provide the traveler with the available ridesharing options, based on the traveler's request and specified itinerary.
1.4.1.4Rider Request shall also include the capability to perform real-time ridematching by instantly matching rider and driver.
1.5TRAVELER SERVICES INFORMATION
1.5.2TSI shall include an Information Access function that allows travelers to access the available information.
1.5.2.5Information Access shall provide the capability for travelers to access the TSI information via any of, but not limited to, the following methods:
1.5.2.5(b)Dial-up telephone lines.
1.5.2.5(c)Computers at home.
1.5.2.5(d)Computers in the office.
2.0PUBLIC TRANSPORTATION MANAGEMENT
2.3.0ITS shall include a Personalized Public Transit (PPT) function.
2.3.1The PPT shall include a Rider Request function.
  
The detailed process and user service requirement traceability information on this page was extracted from the National ITS Architecture. Consult the National ITS Architecture web site for more information.

Last updated on 02-06-2003 using Ronald C. Ice and Associates Web Spinner Technology.