Below are the first 10 and last 10 pages of uncorrected machine-read text (when available) of this chapter, followed by the top 30 algorithmically extracted key phrases from the chapter as a whole.
Intended to provide our own search engines and external engines with highly rich, chapter-representative searchable text on the opening pages of each chapter.
Because it is UNCORRECTED material, please consider the following text as a useful but insufficient proxy for the authoritative book pages.
Do not use for reproduction, copying, pasting, or reading; exclusively for search engines.
OCR for page 37
Findings of Peer Review of Interoperable Smartcard Programs 37
· TVMs;
· Customer service terminal (CST);
· Fare transaction processor (FTP) on-board, handheld portable, and standalone;
· Central data collection system; and
· Driver display unit (DDU).
Customers will be able to load value to their RFC card at TVMs, customer service offices, and
retail outlets, or by mail, phone, or autoload, and via the Internet. In addition to transit fare pay-
ment, the RFC Project is considering opportunities to use the card for parking payment and tran-
sit employee identification and building access.
3.1.4.1 Fare Policies
The following fare policies and customer features define the RFC program:
· Card Fee--Planned: no fee during conversion period, card fee (e.g., $3 to $4) after the intro-
ductory period concludes;
· Fare Products--E-cash, fixed-period passes, and transit ride products (electronic ticket-
books), intra/inter-operator transfers;
· Fare Categories--Planned: Adult, youth, senior/disabled, and operator employee; and
· Other Features--Planned: Balance protection/fare replacement, autoload, and Internet sales.
3.1.4.2 Transit Benefit Program
A transit benefit program is planned that will allow cardholders to load pre-tax and employer-
sponsored transit benefits to their RFC cards.
3.1.4.3 Loyalty Benefits Program
A "frequent rider" program to reward riders with free rides is being considered.
3.1.5 Go-To Card
Metro Transit, which serves the Minneapolis/St. Paul area, is developing the Go-To Card, a
smartcard-based fare payment system. The goal of the Go-To Card project is to modernize an
aging fare collection system and to speed passenger boarding. In January 2002, Metro Tran-
sit awarded a contract to CTS to implement the Go-To Card system in the seven-county
Minneapolis/St. Paul metropolitan region. The card will be accepted on the Twin Cities bus and
the Hiawatha light-rail line. During December 2003 and the first half of 2004, Metro Transit per-
formed hardware and software testing. Full public rollout has been scheduled for early 2006.
The equipment procured includes rail and bus validators, TVMs, and a central system. The
ticket machines for this system are unique in that they are programmed with four languages--
English, Spanish, Hmong, and Somali. TVMs vend magnetic-stripe tickets and add value to
smartcards. Cardholders can also load value to their Go-To Card at ticket stores, participating
retail locations, and via an interactive voice response (IVR) system. Internet loads are also
planned.
The Go-To Card system uses a MiFare ISO 14443 Type A smartcard that will be integrated into
the following equipment:
· TVMs,
· Platform and onboard card validators,
· Handheld read/write devices,
· Retail POS terminals, and
· Central system.
