Difference between revisions of "Ticketing, reservations, and fare collection system interoperability"
Jump to navigation
Jump to search
Aaronantrim (talk | contribs) (created diagram of fare systems for fixed-route transit page - link to Google Doc) |
Aaronantrim (talk | contribs) m (add link to mobile fare payment) |
||
(One intermediate revision by the same user not shown) | |||
Line 1: | Line 1: | ||
− | Below: Functions separate and related stack of functions in fare payment, ticketing, and reservations in fixed-route transit. This is a sketch of how transit fare and ticketing systems might interact with related systems. Currently, offerings from [[moovel]] and other mobile payment vendors consolidate trip tools and ticketing in a single app. However, transit customers choose from a variety of real-time and trip planning applications. There are currently limited mechanisms to enable quick fare payment from these various applications. | + | Below: Functions separate and related stack of functions in fare payment, ticketing, and reservations in fixed-route transit. This is a sketch of how transit fare and ticketing systems might interact with related systems. Currently, offerings from [[moovel]] and other [[mobile fare payment]] vendors consolidate trip tools and ticketing in a single app. However, transit customers choose from a variety of real-time and trip planning applications. There are currently limited mechanisms to enable quick fare payment from these various applications. |
− | [[File:Conceptual | + | [[File:Conceptual diagrams of fare systems for fixed-route transit.png]] |
See working links in [https://docs.google.com/drawings/d/1zhXU0FirjcqkiGTa7yUPYy-r_iU6MTK5VVdJwzuk3uY/edit Google Docs version]. | See working links in [https://docs.google.com/drawings/d/1zhXU0FirjcqkiGTa7yUPYy-r_iU6MTK5VVdJwzuk3uY/edit Google Docs version]. |
Latest revision as of 22:34, 19 December 2016
Below: Functions separate and related stack of functions in fare payment, ticketing, and reservations in fixed-route transit. This is a sketch of how transit fare and ticketing systems might interact with related systems. Currently, offerings from moovel and other mobile fare payment vendors consolidate trip tools and ticketing in a single app. However, transit customers choose from a variety of real-time and trip planning applications. There are currently limited mechanisms to enable quick fare payment from these various applications.
See working links in Google Docs version.