New Jersey Statewide ITS Architecture


Menu
Region Home
Stakeholders
Inventory by Stakeholder
Inventory by Entity
Sausage Diagram
Market Packages by Functional Area
Market Packages by Stakeholder
Market Package Descriptions
Equipment Package Descriptions
Architecture Flow Descriptions
Project Documents
Send Your Comments

 

Equipment Package: Remote Interactive Information Reception

Description: This equipment package shall provide the capability for travelers to interface with the ISP Subsystem Infrastructure equipment packages including the Interactive Infrastructure Information equipment package, the Infrastructure Provided Route Selection, Yellow Pages and Reservation, and Dynamic Ridesharing equipment packages. These capabilities shall be provided using the Remote Traveler Support Subsystem equipment such as kiosks and other interactive displays.
Included In: NJDOT Kiosks
NJTA Kiosks
Processes: 6.3.1 - Get Traveler Request
6.3.2 - Inform Traveler
6.3.3 - Provide Traveler Kiosk Interface
6.3.4 - Update Traveler Display Map Data at Kiosk
7.3.4 - Provide Remote Terminal Traveler Card Interface
7.5.2 - Provide Traveler Roadside Traveler Card Interface
7.5.4 - Provide Traveler Kiosk Traveler Card Interface
User Service Requirements: 1.0 - TRAVEL AND TRAFFIC MANAGEMENT
1.1 - PRE-TRIP TRAVEL INFORMATION
1.1.0 - ITS 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.1 - PTTI shall provide travelers with Available Services Information on travel, for their use.
1.1.1.1 - PTTI shall provide users with available services information that is timely.
1.1.1.1.1 - PTTI shall provide users the latest available information on transit routes.
1.1.1.1.2 - PTTI shall provide users the latest available information on transit schedules.
1.1.1.1.3 - PTTI shall provide users with the latest available schedule adherence information.
1.1.1.1.4 - PTTI shall provide users the latest available information on transit transfer options.
1.1.1.1.5 - PTTI shall provide users the latest available information on transit fares.
1.1.1.1.6 - PTTI shall provide users information on accessing ridematching services.
1.1.2 - PTTI shall provide the capability for users to access the Current Situation Information on transportation systems.
1.1.2.1 - PTTI shall provide the latest available information on the current status of transportation services.
1.1.2.1.1 - Real-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.2 - Real-time information provided by PTTI shall include the current status of any accidents or incidents.
1.1.2.1.3 - Real-time information provided by PTTI shall include the current condition of any road construction.
1.1.2.1.4 - Real-time information provided by PTTI shall include any currently recommended alternate routes.
1.1.2.1.5 - Real-time information provided by PTTI shall include the current speeds on specific routes.
1.1.2.1.6 - Real-time information provided by PTTI shall include current parking conditions in key areas.
1.1.2.1.8 - Real-time information provided by PTTI shall include the current weather situation.
1.1.3 - PTTI shall include a Trip Planning Service.
1.1.3.1 - PTTI trip planning service shall provide the users with information needed for planning an upcoming trip.
1.1.3.1.1 - Based on user specified parameters PTTI shall provide users with a calculated itinerary.
1.1.3.2 - PTTI shall provide the capability for users to specify transportation parameters that are unique to their individual needs.
1.1.3.2.1 - PTTI shall provide the capability for users to specify a desired destination.
1.1.3.2.2 - PTTI shall provide the capability for users to specify a planned departure location.
1.1.3.2.3 - PTTI shall provide the capability for users to specify their desired departure time.
1.1.3.2.4 - PTTI shall provide the capability for users to specify their desired arrival time.
1.1.3.2.5 - PTTI shall provide the capability for users to specify their maximum acceptable travel time.
1.1.3.2.6 - PTTI shall provide the capability for users to specify their maximum acceptable number of mode changes.
1.1.3.2.7 - PTTI shall provide the capability for users to specify a maximum number of transfers.
1.1.3.2.8 - PTTI shall provide the capability for users to specify their preferred route(s) or segment of route(s).
1.1.3.2.9 - PTTI shall provide the capability for users to specify their preferred transportation mode(s).
1.1.3.2.10 - PTTI shall provide the capability for users to specify their preferred weather conditions.
1.1.4 - PTTI shall provide the capability for User Access.
1.1.4.1 - PTTI shall provide the capability for users to access the system from multiple distributed locations.
1.1.4.1.3 - PTTI shall provide the capability for users to access the system from major trip generation sites.
1.4.0 - ITS 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.1 - RMR shall include a Rider Request capability.
1.4.1.1 - Rider 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.2 - Rider Request shall provide a traveler the capability to request a specific itinerary by specifying, but not be limited to, the following:
1.4.1.2(b) - Time of pick-up and drop-off.
1.4.1.2(c) - Origin.
1.4.1.2(d) - Destination.
1.4.1.2(e) - Specific restrictions or preferences.
1.4.1.3 - Rider Request shall provide the traveler with the available ridesharing options, based on the traveler's request and specified itinerary.
1.4.1.4 - Rider Request shall also include the capability to perform real-time ridematching by instantly matching rider and driver.
1.5 - TRAVELER SERVICES INFORMATION
1.5.0 - ITS 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.2 - TSI shall include an Information Access function that allows travelers to access the available information.
1.5.2.1 - Information Access shall provide the capability for travelers to request and receive general information about the local area.
1.5.2.2 - Information 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.5 - Information 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.6 - Information 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.8 - TRAVEL DEMAND MANAGEMENT
1.8.2 - TDM shall include a processing function.
1.8.2.3 - Strategies developed by the processing function shall include the guidance for the operation of physical systems that:
1.8.2.3(a) - Monitor traffic.
2.0 - PUBLIC TRANSPORTATION MANAGEMENT
2.3.0 - ITS shall include a Personalized Public Transit (PPT) function.
2.3.1 - The PPT shall include a Rider Request function.
2.3.1.3 - Rider 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.4 - Rider Request shall include the capability to notify the requester that the transit vehicle's arrival is imminent.
3.0 - ELECTRONIC PAYMENT
3.1 - ELECTRONIC PAYMENT SERVICES
3.1.0 - ITS shall include an Electronic Payment capability. Electronic Payment Services allows travelers to pay for transportation services by electronic means. Four functions are provided, which are, (1) Electronic Toll Collection, (2) Electronic Fare Collection, (3) Electronic Parking Payment, and (4) Electronic Payment Services Integration.
3.1.3 - Electronic Payment shall include an Electronic Parking Payment (EPP) capability.
3.1.3.1 - EPP shall provide the capability to pay for parking without the use of cash.
5.0 - EMERGENCY MANAGEMENT
5.1 - EMERGENCY NOTIFICATION AND PERSONAL SECURITY
5.1.3 - ENPS shall include a Remote Security and Emergency Monitoring (RSEM) function to create an environment of safety in secure areas.
5.1.3.4 - RSEM shall include a Monitor Alert Levels (MAL) function.
5.1.3.4.3 - MAL shall increase system preparedness as the likelihood of an incident increases, including:
5.1.4 - ENPS shall include a Wide Area Alert (WAA) function to notify the public in emergency situations using ITS driver information and traveler information capabilities.
5.1.4.1 - WAA shall notify transportation operators and information providers when an emergency situation occurs that requires public notification.
5.1.4.1.1 - The WAA notification shall identify the originator, the nature of the emergency, the geographic area affected by the emergency, the effective time period, and information and instructions necessary for the public to respond to the alert.
5.1.4.1.2 - The WAA shall provide necessary information for emergencies including, but not limited to, child abductions, severe weather watches and warnings, military activities, civil emergencies, other natural and human-caused disaster advisories, and law enforcement warnings.
5.1.4.2 - WAA shall use available dynamic message signs, highway advisory radio, in-vehicle displays, 511 and other telephone information systems, traveler information web sites, transit vehicle information systems, message display boards, and other information systems to provide the WAA information to the public.
5.1.4.2.1 - WAA shall tailor the information provided for individual driver and traveler information systems, limiting messages to short notifications for human-factors limited devices like dynamic message signs.
5.1.4.3 - WAA shall keep the WAA initiator apprised of the current status of public notification, including an accounting of the driver and traveler information resources that are being utilized.
5.1.4.4 - WAA shall notify transportation operators and information providers when public notification is no longer required.
5.1.5 - ENPS shall include a Protect Sensitive Traveler Information (PSTI) function to inhibit distribution of traveler information that is deemed to be sensitive.
5.1.5.1 - PSTI shall notify transportation operators and information providers when access to information from ITS surveillance and sensor systems must be restricted.
5.1.5.2 - The PSTI notification shall identify the geographic area, time, specific devices, and/or other information necessary to determine the traveler information that must be protected.
5.1.5.3 - PSTI shall restrict access to traveler information for the affected area until access restrictions are removed.
5.1.5.4 - PSTI shall notify transportation operators and information providers when traveler information access restrictions are removed.

Last updated: 02-11-05