Cover Image

Not for Sale



View/Hide Left Panel
Click for next page ( 72


The National Academies | 500 Fifth St. N.W. | Washington, D.C. 20001
Copyright © National Academy of Sciences. All rights reserved.
Terms of Use and Privacy Statement



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 71
Findings of Data Flows Between Agencies 71 Table 15. Configuration and usage data matrix. Configuration Data Description/Examples Business Rules Fare Policies and Transfer Rules Software Version Control Software in Device, Valid Device in System Hot List Bad Cards Action List Prepaid Autoload Localization Rules Rules that Apply to Specific Services Such as Express Bus Device Configuration Ensure Bus Device is for Bus Security Keys Keys to Unlock Data on Card for Write Function Usage Data Description/Examples Fare-Payment Value Amount Deducted from Card Fare-Payment Type Stored Value, Monthly Pass Add Value Amount Added to Card Autoload Amount Automatically Loaded Event Pass-Back Disabled to Conduct Multiple Transactions Alarm Bad Card, Hotlisted Card Detected Table 15 provides an overview and examples for each type of data that flows through a smart- card fare payment system. 5.3 Analysis of Data Flows Because of the performance requirements of transit operations, the smartcard does not per- form any calculations with the exception of dynamic encryption. Dynamic encryption occurs as the data are transferred between the card and reader. The card-based microprocessors are not fast enough to conduct card-based fare calculations at this stage of technology development while passengers are boarding a bus or passing through a faregate. In the transit environment, the smartcard serves as a secure data repository for fare value. 5.3.1 Data on the Smartcard Table 16 lists the minimum data required on the card to clear and settle transactions for an interoperable smartcard payment system. This also assumes that the physical and security layers are compatible. A detailed discussion of the information exchange layers between the card and reader is provided in Section 4.2. These minimum data requirements are based on analysis con- ducted as part of the design-review process for projects such as TransLink. 5.3.2 Operation Data Flows The operation data flows provide the basis for identifying the functionality that the API will need to accommodate. The API functional requirements will be identified in Appendix A. Fig- ure 14a shows the data flows that occur during normal system operation and identifies the tiers relevant for each data element. Figure 14b provides a functional description of each tier and iden- tifies where the data elements reside in the system architecture flow.

OCR for page 71
72 Smartcard Interoperability Issues for the Transit Industry Table 16. Minimum data required on card. Card Data Product Data Journey Data Card Product Agency Identification Identification Identification Number Number Number Card Issuer Product Date and Time of Identification Validity Journey Event Patron Profile Period Entry and Exit Code Electronic Location of Card Validity Purse Journey Period Route Number Station/ Central Agency Local Device Card System System Consolidation Tier Tier Tier Tier Tier Configuration Data Configuration Data Hot List Action List Software Version Control Security Keys Device Configuration Localization Rules Usage Usage Data Data Transactions Autoload Events Alarms Figure 14a. Data flow analysis.

OCR for page 71
Findings of Data Flows Between Agencies 73 Clearing Clearing and and settlement settlement System management Central Central System System Tier Tier Funds Reporting Funds transfer transfer Configuration Configuration Data Configuration Data (CD) Data (CD (CD Usage Usage Data Usage Data (UD) Data (UD) (UD) Hot Hot list list Transaction Transaction record record Software Software (application (application management) management) Payment Payment Device Device configuration configuration Add Addvalue value Addvalue Localization Localization rules rules Autoload Autoload Business Business rules rules Events Events Agency Agency wide wide consolidation consolidation Reporting Agency Agency System System Tier Tier Device Device management management System monitoring Fare table management CD CD UD UD Pass Pass through through to to local local tier tier Pass Pass through through for for local local tier tier to to central central system system Local Local device device management management Event Event data data Alarm Alarm Maintenance Maintenance actions actions Local consolidation System management Station/Local Station/Local Transactions "agency" Systems configuration Consolidation Consolidation Tier Tier validation Local device management CD CD UD UD Device Device configuration Configuration Configuration Payment Payment location location (vehicle, (vehicle, station) station) Device Device validity validity Payment Payment time time and anddate date Software Software version version Device Device ID ID Hot Hot list list Added Added value value Transaction Transaction processing processing Card configuration Device Device Tier Tier Transaction Card validation (security) Transaction consolidation consolidation CD CD UD UD Card Card validity validity Fare Fare payment payment value value Remaining Remaining value value Fare Fare payment payment type type Autoload Autoload Added Added value value Device Device authentication authentication Card Card Tier Tier Transit Transit application application data data storage storage Key Key Figure 14b. Functional data flow matrix.