Regional Architecture Logo
 

Send Your Comments

E-Mail

Remote Basic Information Reception Equipment Package

Architecture Geographic Scope

Description:

This Equipment package shall provide the capability for travelers to interface with the ISP Subsystem Basic Information Broadcast Equipment package and receive formatted traffic advisories including accurate traveling information concerning available travel options and their availability, and congestion information at the Remote Traveler Support Subsystem.

 

Included in:

Sun Metro Transit Kiosks
TxDOT Rest Areas/Visitor Center Kiosks

Processes:

6.3.2Inform Traveler
6.3.3Provide Traveler Kiosk 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.1PTTI shall provide travelers with Available Services Information on travel, for their use.
1.1.1.1PTTI shall provide users with available services information that is timely.
1.1.1.1.1PTTI shall provide users the latest available information on transit routes.
1.1.1.1.2PTTI shall provide users the latest available information on transit schedules.
1.1.1.1.3PTTI shall provide users with the latest available schedule adherence information.
1.1.1.1.4PTTI shall provide users the latest available information on transit transfer options.
1.1.1.1.5PTTI shall provide users the latest available information on transit fares.
1.1.1.1.6PTTI shall provide users information on accessing ridematching services.
1.1.2PTTI shall provide the capability for users to access the Current Situation Information on transportation systems.
1.1.2.1PTTI shall provide the latest available information on the current status of transportation services.
1.1.2.1.1Real-time information provided by PTTI shall include the current condition of any incidents, including rural incidents such as high winds, extreme temperature, and falling rocks.
1.1.2.1.2Real-time information provided by PTTI shall include the current status of any accidents or incidents.
1.1.2.1.3Real-time information provided by PTTI shall include the current condition of any road construction.
1.1.2.1.4Real-time information provided by PTTI shall include any currently recommended alternate routes.
1.1.2.1.5Real-time information provided by PTTI shall include the current speeds on specific routes.
1.1.2.1.6Real-time information provided by PTTI shall include current parking conditions in key areas.
1.1.2.1.8Real-time information provided by PTTI shall include the current weather situation.
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.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.1(a)Telephones (including hearing-impaired capability).
1.4.1.1(b)Kiosks.
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.0ITS shall include a Traveler Services Information (TSI) function. Traveler Services Information provides travelers with service and facility data for the purpose of assisting prior to embarking on a trip or after the traveler is underway. The functions which are included in this capability are Information Receipt and Information Access. This will provide the traveler with a "yellow pages" type of capability.
1.5.2TSI shall include an Information Access function that allows travelers to access the available information.
1.5.2.1Information Access shall provide the capability for travelers to request and receive general information about the local area.
1.5.2.2Information Access shall provide the capability for travelers and centers to request and receive information about the location of facilities and the quality of specific services provided in an area to include but, not be limited to, the following:
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(f)Public area kiosks.
1.5.2.6Information Access shall provide the capability for travelers to access TSI information from public kiosk locations which include, but are not limited to:
1.5.2.6(a)Rest areas.
1.5.2.6(b)Activity centers.
1.5.2.6(c)Tourist attractions.
1.5.2.6(d)Service plazas.
1.5.2.6(e)Airports.
1.8TRAVEL DEMAND MANAGEMENT
1.8.2TDM shall include a processing function.
1.8.2.3Strategies developed by the processing function shall include the guidance for the operation of physical systems that:
1.8.2.3(a)Monitor traffic.
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.
2.3.1.3Rider Request shall provide the capability to notify a requester of the fact that a trip assignment has been made including the time at which the vehicle is expected at the point of departure.
2.3.1.4Rider Request shall include the capability to notify the requester that the transit vehicle's arrival is imminent.
  
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 09-27-2003 using Ronald C. Ice and Associates Web Spinner Technology.