The RCSC will provide services to all Smar Trip participants and operators in the DC, Maryland, and Northern Virginia regions. CTS also received a contract in July 2003 to supply POS devices and the data network concentrator and to make upgrades to existing systems to support the regional program.

The RCSC will consist of the customer service center, Findings of Peer Review of Interoperable Smartcard Programs 29 30 Sm artcard Interoperability Issues for the Transit Industry Table 7. Physical-Layer Features W a s h i n g t o n , D C , S m a r T r i p S a n F r a n c i s c o , T r a n s L i n k 1 0 C h i c a g o , C h i c a g o C a r d S e a t t l e , R F C 1 0 M i n n e a p o l i s , G o - T o C a r d C e n t r a l F l o r i d a , O R A N G E S V e n t u r a C o u n t y , G o V e n t u r a L A C o u n t y , T A P 1 0 S a n D i e g o , C o m p a s s 1 0 L o n d o n , O y s t e r H o n g K o n g , O c t o p u s S i n g a p o r e , E Z - L i n k No11. CTS and ERG are working with WMATA to integrate their respective systems.

• Section 3.2 identifies the commonalities in the information shared among agencies partici- pating in the listed interoperable programs.

• Section 3.3 discusses current trends and new developments being considered or pursued within the smartcard programs, including – Payment for parking, bridges, and highway tolls; – Applications for financial institutions and retail; and – Expanded security and biometrics features.

The physical-layer results of the survey are presented in Table 7.

The data-layer results of the survey are presented in Table 8.

Metrorail vendors also vend magnetic tickets for non-Smar Trip cardholding customers; these tickets can only be used in the rail system. N/ADNADNA DNA N/A DNA N/A DNA DNA DNA DNADNA PROFelica PROPRO PRO N/ADNAPRO PROPRO DNA PROIf no, what do you use? 2The current reader for rail (Cubic’s Go CARD reader) is not compliant, but they are procuring a system of buses that will use Cubic’s Tri-Reader, which is compliant and would modulate between Types A and B. 4The cards are not compliant, but the system could be compliant if compliant cards are used. Nil 1 2 8 Nil 5 6 UC Nil 7 Nil Notes: 1Transaction/purse sequence numbers serve to identify gaps in data 2The back-end system does not carry any value so the server will charge the patron’s account, and when the threshold goes below 10 dollars, an email is sent to the patron.

An implementation that will expand the Smar Trip functionality to surrounding transit providers is under way. 5The card type is Mifare Type A, which is compliant for Parts 1 and 2, but not fully compliant for Part 4. 9As allowed by ISO 7816, a subset of APDU commands has been implemented. Listed information is “as planned.” Key = Yes DNA = Does Not Apply PRO = Proprietary N/A = Not Available DES = Data Encryption Standard 3DES = Triple DES Findings of Peer Review of Interoperable Sm artcard Program s 31 7 Data-Layer Features W a s h i n g t o n , D C , S m a r T r i p S a n F r a n c i s c o , T r a n s L i n k C h i c a g o , C h i c a g o C a r d S e a t t l e , R F C M i n n e a p o l i s , G o - T o C a r d C e n t r a l F l o r i d a , O R A N G E S V e n t u r a C o u n t y , G o V e n t u r a L A C o u n t y , T A P S a n D i e g o , C o m p a s s L o n d o n , O y s t e r H o n g K o n g , O c t o p u s S i n g a p o r e , E Z - L i n k 1. -Card ID # -Card Issuer ID # No -Patron Profile Code (Age/Disability) No -Patron Language No No N/A No No No No No No No No N/A No 2. -Fare Product ID # 3 3 3 3 N/A -Fare Product Validity Period 3. -Agency ID # N/A -Date/time of specific transaction -Entry/exit location of patron No 4. Also, there is a bonus program that provides 1 dollar back for every 10 dollars spent on the card.

Paul-Minneapolis, MN (com/tafsinformation.html) 28 C H A P T E R 3 Findings of Peer Review of Interoperable Smartcard Programs • Orlando Regional Alliance for Next Generation Electronic Payment System (ORANGES)— Central Florida ( • Go Ventura—Ventura County, CA ( • Transit Access Pass (TAP)—Los Angeles County, CA (net) • Compass—San Diego County, CA (sdcommute.com) • EZ-Link—Singapore ( • Octopus—Hong Kong ( • Oyster—London (gov.uk/content/ticketsoyster/asp) This chapter is organized as follows: • Section 3.1 presents an overview of the above programs with respect to their smartcard, reader, and hardware design.

It also discusses their business policies and related data elements.

These critical elements are identified in Chapter 4.

Key policies affecting interoperability are also part of the survey, because establishing policies that tie agencies participating in an interoperable fare payment system together is equally impor- tant to technology decisions.

In the past, employers were burdened with hav- ing to distribute paper Metrochek fare cards and vouchers.