Regional Architecture Logo
 

Send Your Comments

E-Mail

Parking Management Equipment Package

Architecture Geographic Scope

Description:

Maintain and distribute parking lot information including static (spaces, hours, charges, etc.) and dynamic (availability, open/closed, etc.) data. Interface to traffic, transit, and traveler information providers.

 

Included in:

Lufkin Intermodal Terminal

Functional Requirements:

1The parking element shall maintain parking lot information including static information such as hours of operation, rates, location, entrance locations, capacity, type, and constraints; as well as dynamic information such as current state of the lot, occupancy, arrival rates, and departure rates.
2The parking element shall distribute parking lot information upon request to traffic management centers, transit management centers for park and ride facilities, and to traveler information providers.
3The parking element manage local dynamic message signs that display messages to travelers such as the parking lot state, number of spaces available, location of entrances, and current charges.
4The parking element shall support requests for parking reservations.
  

User Service Requirements (fully or partially addressed):

1.0TRAVEL AND TRAFFIC MANAGEMENT
1.1PRE-TRIP TRAVEL INFORMATION
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.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.6Real-time information provided by PTTI shall include current parking conditions in key areas.
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.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.2(c)Parking information.
1.8TRAVEL DEMAND MANAGEMENT
1.8.0ITS shall include a Travel Demand Management (TDM) function. Travel Demand Management will generate and communicate management and control strategies that will support and facilitate the implementation of TDM programs, policies and regulations. It consists of two major functions, which are, (1) Increase Efficiency of Transportation System and (2) Provide Wide Variety of Mobility Options.
1.8.1TDM shall include a communications function.
1.8.1.2The communications function shall include the capability to send information and rates needed to implement management and control strategies that respond to changing environments, conditions, and policy needs to include, but not limited to, the following locations of action:
1.8.1.2(a)Parking facilities.
1.8.1.4The communications function shall provide the capability to send information and data as needed to implement management and control strategies that respond to changing environments, conditions, and policy needs to include, but not limited to, the following:
1.8.1.4(c)Parking availability.
1.8.2TDM shall include a processing function.
1.8.2.1The processing function shall provide the capability to generate management and control strategies that facilitate the implementation of policies and regulations designed to address the following:
1.8.2.1(c)Parking management and control.
1.8.2.10The processing function's dynamically generated management and control strategies shall include the parking management and controls to include, but not be limited to, the following:
1.8.2.11The processing function's dynamically generated management and control strategies for parking management and controls shall be based on factors that include, but are not limited to, the following:
1.8.2.11(a)Parking availability.
1.8.3TDM shall include a sensors/control function.
1.8.3.1The sensors/control function shall provide the capability to gather information needed for the generation of management and control strategies to include, but not be limited to the, following:
1.8.3.1(a)Parking availability.
3.0ELECTRONIC PAYMENT
3.1ELECTRONIC PAYMENT SERVICES
3.1.4ITS shall include an Electronic Payment Services Integration (EPSI) feature.
3.1.4.3EPSI shall collect and provide usage data to develop pricing strategies that favor certain transportation modes or routes.
  
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 05-25-2005 using Ronald C. Ice and Associates Web Spinner Technology.