< < PM02 : PM02 : PM02 > >

PM02: Infrastructure-Based Monitoring

Use sensors/traffic detectors in the park and ride facility to detect and monitor vehicle ingress and egress and parking space occupancy in the park and ride facility. Within this implementation, detectors can be located to derive estimated parking space occupancy based on monitored ingress and egress or detectors can be included per parking space for more granular tracking and management of individual parking space availability. Current parking information is shared with drivers, traveler information providers, and the providers of ride services for those exiting their parked vehicles. Those using the park and ride facilities also receive information on available ride services, including pickup locations and times.

Relevant Regions: Australia, Canada, European Union, and United States

Enterprise

Development Stage Roles and Relationships

Installation Stage Roles and Relationships

Operations Stage Roles and Relationships
(hide)

Source Destination Role/Relationship

Maintenance Stage Roles and Relationships

Functional

This service package includes the following Functional View PSpecs:

Physical Object Functional Object PSpec Number PSpec Name

Physical

The physical diagram can be viewed in SVG or PNG format and the current format is SVG.

Physical diagrams have not been developed for this application yet.


Display Legend in SVG or PNG

Includes Physical Objects:

Physical Object Class Description

Includes Functional Objects:

Functional Object Description Physical Object

Includes Information Flows:

Information Flow Description

Goals and Objectives

Associated Planning Factors and Goals

Planning Factor Goal
D. Increase the accessibility and mobility of people and for freight; Reduce congestion
F. Enhance the integration and connectivity of the transportation system, across and between modes, for people and freight; Enhance integration and connectivity
G. Promote efficient system management and operation; Improve efficiency
J. Enhance travel and tourism. Support travel and tourism

Associated Objective Categories

Objective Category
System Options: Mode Share
System Options: Transit Use
System Options: Travel Time - Transit Compared to Auto
Transit Operations and Management: Park-and-Ride Support
Transit Operations and Management: Traveler Information

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.
Equip X shelters/platforms with real-time arrival displays annually. Number of shelters/platforms equipped with real-time arrival displays per year.
Improve average transit travel time compared to auto in major corridors by X minutes per year for Y years. Transit to auto travel time differential for a given period (daily, hourly, or peak hours), on a given portion of the system (system wide, by facility type, or by corridor).
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 average transit load factor by X percent by year Y. Number of riders on various transit units per trip at peak travel times.
Increase passenger miles traveled per capita on transit by X percent by year Y. Number of passenger miles traveled per capita.
Increase pedestrian and bicycle access to park-and-ride lots by X percent within Y years. Percent of park-and-ride areas with pedestrian and bicycle access.
Increase the number of automobile and bicycle spaces by X percent within Y years for lots currently experiencing X percent utilization. Number of auto/bicycle spaces at the park-and-ride lots
Increase transit mode share by X percent by year Y during peak periods. Percent of all peak-period trips made by transit.
Increase transit mode share by X percent by year Y. Percent of all trips made by transit.
Increase traveler awareness of park-and-ride lots by X percent within Y years. Number of users aware of park-and-ride lots in their region.
Maintain a travel time differential between transit and auto during peak periods of X percent for Y years. Transit to auto travel time differential for a given period (daily, hourly, or peak hours), on a given portion of the system (system wide, by facility type, or by corridor).
Reduce per capita SOV commute trip rate by X percent in Y years. SOV commute trips per capita.
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 travel time differential between transit and auto during peak periods by X percent per year for Y years. Transit to auto travel time differential for a given period (daily, hourly, or peak hours), on a given portion of the system (system wide, by facility type, or by corridor).

 
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.

Needs and Requirements

Need Functional Object Requirement

Related Sources

  • None


Security

In order to participate in this service package, each physical object should meet or exceed the following security levels.

Physical Object Security
Physical Object Confidentiality Integrity Availability Security Class
Security levels have not been defined yet.



In order to participate in this service package, each information flow triple should meet or exceed the following security levels.

Information Flow Security
Source Destination Information Flow Confidentiality Integrity Availability
Basis Basis Basis
Security levels have not been defined yet.

Standards

Currently, there are no standards associated with the physical objects in this service package. For standards related to interfaces, see the specific information flow triple pages.





Needs and Requirements

Need Functional Object Requirement

System Requirements

No System Requirements