TCRP Report 115: Smartcard Interoperability Issues for the Transit Industry

Questions? Call 800-624-6242

About | Ordering | New

LoginRegister

| Items in cart [0]

The National Academies Press

Rights & Permissions

Free PDF Access

Sign in to download PDF book and chapters

Free Resources

Display this book
on your site!

Related Titles

TCRP Report 115: Smartcard Interoperability Issues for the Transit Industry (2007)
Transit Cooperative Research Program (TCRP)

Citation Manager Export the bibliographic data for this book in your chosen format
Web Search Builder Use this book's key terms to search within this book, across our collection, or across the Web.
Skim This Chapter Skim this chapter and use this chapter's key terms to search within this book.
Reference Finder Paste in your own text to find books that relate to your topic.

Citation Manager

Transportation Research Board. "2.1.1 Establishing a Governing Body or Project Sponsor." TCRP Report 115: Smartcard Interoperability Issues for the Transit Industry. Washington, DC: The National Academies Press, 2007.

Please select a format:

Page
16


E-mail Share on facebook Facebook Share on delicious Delicious Share on stumbleupon Stumble Share on twitter Twitter More Sharing ServicesMore

Click to move to next page (17)

Page
16

Front Matter (R1-R9)

Chapter 1 - Introduction (3-3)

1.2 Elements of Fare Payment Interoperability (4-4)

1.3 Interoperability Across Regions (5-5)

1.4 Interoperability Beyond Transit (6-6)

1.5.1 Acceptance of Contactless Bank Cards (7-8)

1.5.3 Multiple Payment-Enabled Devices (9-9)

1.6 Hypothetical Examples - Interoperability Between WMATA and TransLink (10-10)

1.6.1 Information to Be Exchanged for Payment (11-12)

1.6.3 Process for Determining the Net-Settlement Position (13-13)

2.1 Management and Organizational Issues (14-14)

2.1.1 Establishing a Governing Body or Project Sponsor (15-16)

2.1.2 Identifying and Mitigating Operational Differences (17-17)

2.1.3 Establishing a Framework for Program Funding (18-18)

2.1.4 Creating a Rollout Schedule (19-19)

2.1.5 Developing a Contracting Strategy (20-21)

2.2.2 Funds Pool Management (22-22)

2.2.3 Financial Exposure and Risk Associated with Advanced Features (23-23)

2.3.2 New Processes (24-24)

2.4 Equipment Design Issues (25-25)

2.5.2 Supplier Behavior (26-26)

2.5.3 Supplier Compliance with Available Standards (27-27)

Chapter 3 - Findings of Peer Review of Interoperable Smartcard Programs (28-28)

3.1.1 SmarTrip (29-33)

3.1.2 TransLink (34-34)

3.1.3 Chicago Card (35-35)

3.1.4 Central Puget Sound Regional Fare Coordination (RFC) Project (36-36)

3.1.5 Go-To Card (37-37)

3.1.6 Orlando Regional Alliance for Next Generation Electronic Payment System (ORANGES) (38-38)

3.1.7 Go Ventura (39-39)

3.1.8 Transit Access Pass (TAP) (40-40)

3.1.9 Compass (41-41)

3.1.10 Octopus (42-42)

3.1.11 EZ-Link (43-43)

3.1.12 Oyster (44-44)

3.2.1 Commonalities and Differences (45-46)

3.2.2 Current Trends and New Developments (47-47)

3.4.2 SmarTrip (48-48)

3.5 Summary (49-50)

4.1 Industry Interoperability Analysis (51-51)

4.2.1 Physical Layer (52-56)

4.2.2 Data Layer (57-59)

4.2.3 Application Layer (60-60)

4.2.4 Security Layer (61-66)

4.3 Gap Analysis (67-68)

5.1 Development of Conceptual Fare Payment System Architecture (69-69)

5.2 Identification of the Data Types (70-70)

5.3.2 Operation Data Flows (71-73)

6.1 Scope of the Data-Management Policy (74-74)

6.2.1 Data Location (75-75)

6.3 Identification of Stakeholders and Their Roles and Responsibilities (76-76)

6.4 Other RequirementsPrivacy (77-77)

6.5 Current Trends (78-78)

7.1 Use of Standard API in Proof of Concept (79-82)

7.2 Development of AFC Simulator (83-84)

7.3 Demonstration (85-85)

7.4 Conclusion (86-86)

Chapter 8 - Conclusions (87-91)

Appendix A - Set of Functionality for a Standard API (92-99)

Abbreviations used without definitions in TRB publications (100-100)