APTS04-Transit Fare Collection Management (Market Package*)Market Package Graphic Transaction Set Diagram DescriptionThis market package manages transit fare collection on-board transit vehicles and at transit stops using electronic means. It allows transit users to use a traveler card or other electronic payment device. Readers located either in the infrastructure or on-board the transit vehicle allow electronic fare payment. Data is processed, stored, and displayed on the transit vehicle and communicated as needed to the Transit Management Subsystem. Two other market packages, ATMS10: Electronic Toll Collection and ATMS16: Parking Facility Management also provide electronic payment services. These three market packages in combination provide an integrated electronic payment system for transportation services.Includes Equipment Packages and Subsystems:
Includes Architecture Flows:Early DeploymentThis market package has been identified as an early deployment due to a promising combination of low risk implementation characteristics, developing public or private markets for the package, and tangible system or user benefits. This Market Package provides immediate and tangible benefit to transit users who enjoy the convenience of an electronic fare medium. The benefits of more efficient, cashless operations also accrue to the implementing transit agencies. These deployments are possible in the interim while industry standards move towards the ultimate goal of a common fare medium that transcends transportation modes and regions and may be applied in other consumer transactions.ITS Goals Supported
* * Features that almost satisfy every aspect of the goals * * * Features completely satisfy every aspect of the goals User Services related to this Market Package:
Problem / Solution Pairs this Market Package Addresses
Hypertext Architecture Version 6.1 generated on 1/7/2009 from the following databases Physical Architecture dated 12/15/2008, Logical Architecture dated 12/2/2008, Market Packages dated 12/14/2008, Security dated 11/13/2008, User Services dated 4/9/2007, Theory of Operations dated 12/14/2008, AppMap dated 12/19/2008 and the SDOMAP dated 12/12/2008 |