Table of Contents - APTAStandards.com
Table of Contents - APTAStandards.com Table of Contents - APTAStandards.com
4.0 ANALYSIS OF STANDARDS AND SPECIFICATIONS Each of the standards and specifications in this section were analyzed for their adherence to the criteria outlined in Section 3.0 and their overall relevance to the UTFS effort. The information presented in this section was obtained through various including: channels • Discussions with transit operator personnel, smart card equipment vendors and project managers • A review of public information (web sites and project documents) • Booz Allen’s direct involvement through engagements with the planning, design and implementation of many of the regional fare payment systems. Exhibit 4-1 illustrates the documentation that met the entire project screening criteria explained in Section 3, and are included in the analysis presented in this section. Exhibit 4-1 Documentation That Met All Criteria Document Issuer Smart Card Standards Title Comments European Committee for Standardization (CEN) Smart Card Specifications CEN TC278/IFM Analyzed in detail ITSO Integrated Transport Smartcard Organization (ITSO) Analyzed in detail Smart Card Standards (non-Transit) International Standards Organization (ISO/IEC) ISO/IEC 8583 Analyzed in detail Smart Card Specifications (non-Transit) OFX Vendor Specifications Open Financial Exchange (OFX) Analyzed in detail Agent Systems Vending Equipment Interface (VEI) Analyzed in detail Cubic CID Edge Interfaces Analyzed in detail ERG APTA WG4 Transaction Definitions Analyzed in detail Smart Card Project Specific Specifications Metropolitan Transportation Commission (MTC) ® TransLink Analyzed in detail Port Authority New Regional Analyzed in detail York/New Jersey Interoperability (PANY/NJ) Specification (RIS) Part 4 Page 12
These standards and specifications were subjected to detailed analysis in order to assess their level of applicability to UTFS WP4 efforts. The established criteria for the level of applicability were developed based on the input from the APTA Financial Committee’s Interface Specification Functional Description and Booz Allen’s experience in implementing regional fare payment systems. The criteria included: • Common Message Structure that is supported by all data exchange • Message Types that are applicable to UTFS WP4 proposed messages • Data Elements that are specific to the transit industry • Message Sequences that support an organized flow of data • Security Requirements to allow for the protection of sensitive transit data and the fiscal integrity of the larger payments scheme implemented for all participant in a region • Timing and Routing that dictates the operational requirements of the system • Usability of the standard or specification by APTA The following sections include the detailed analysis for each of the standards and specifications listed in the Exhibit 4-1. 4.1 ISO/IEC 8583 4.1.1 Description of the Standard ISO/IEC 8583 is designed as an interface standard enabling messages to be exchanged between systems that employ different application specifications. This standard offers application designers freedom from overall design constraints because messages can be converted to the format of this interface for international interchange to take place. This international standard uses a concept called bitmap, whereby each data element is assigned a pos ition indicator in a control field (or bitma p). A “1” in the assigned position indicates the presence of a data element in a specific message, and a “0” in the assigned position, indicates the absence of a data element. This will allow application designers to choose variable length data elements and messages, and the flexibility to utilize data element types that are best suited for a specific application. The standard is designed to accommodate real-time “request-response,” and batch and file transfer type information exchange. It can also be utilized for both peer-to-peer and centralized settlement schemes due to its flexible design. ISO/IEC 8583 specifies a well-defined message structure, and message format and content. It is widely used in the financial industry, particularly in the handling of all credit and debit card transactions among financial institutions and merchants around the world. Page 13
- Page 1 and 2: SMART CARD STANDARDS AND SPECIFICAT
- Page 3 and 4: 4.4.7 Security Requirements........
- Page 5 and 6: Document History Revision Reason Fo
- Page 7 and 8: Acronym List UTFS Universal Transit
- Page 9 and 10: technology to achieve interoperabil
- Page 11 and 12: This report encompasse s the review
- Page 13 and 14: Identify S m art Card Indust ry S t
- Page 15: The standards and specifications th
- Page 19 and 20: Although there is no “one-to-one
- Page 21 and 22: 4.1.4.2 Card Management Data The st
- Page 23 and 24: with ISO/IEC 7816-6, there is no re
- Page 25 and 26: these messages constitutes a file.
- Page 27 and 28: Phone interviews and/or email corre
- Page 29 and 30: The ITSO message body consists of i
- Page 31 and 32: Exhibit 4.2-2 Product Types Type Co
- Page 33 and 34: Capability Values or RFU Product Pr
- Page 35 and 36: opted to contract these services ou
- Page 37 and 38: e given careful consideration for a
- Page 39 and 40: - Transaction date and time - Trans
- Page 41 and 42: cardholder related data as in the c
- Page 43 and 44: CLIENT Exhibit 4.3-9 OFX Security S
- Page 45 and 46: may well be eliminated if, and when
- Page 47 and 48: Exhibit 4.4-4 Condition Dialogue St
- Page 49 and 50: 4.4.7 Security Requirements The Mes
- Page 51 and 52: Application Retailer Product Retail
- Page 53 and 54: Exhibit 4.6-1 CID Edge Interface Me
- Page 55 and 56: 4.6.8 Timing and Routing The CID Ed
- Page 57 and 58: 4.7.4.1 Transaction Data The “Far
- Page 59 and 60: 4.7.4.3 System and Device Data The
- Page 61 and 62: Following the authentication proces
- Page 63 and 64: Data” transaction messages propos
- Page 65 and 66: Field Name Description reading the
4.0 ANALYSIS OF STANDARDS AND SPECIFICATIONS<br />
Each <strong>of</strong> the standards and specifications in this section were analyzed for their<br />
adherence to the criteria outlined in Section 3.0 and their overall relevance to the<br />
UTFS<br />
effort.<br />
The information presented in this section was obtained through various<br />
including:<br />
channels<br />
• Discussions with transit operator personnel, smart card equipment<br />
vendors and<br />
project managers<br />
• A review <strong>of</strong> public information (web sites and project documents)<br />
• Booz Allen’s<br />
direct involvement through engagements with the planning, design<br />
and implementation <strong>of</strong> many <strong>of</strong> the regional fare payment systems.<br />
Exhibit<br />
4-1 illustrates the documentation that met the entire project screening criteria<br />
explained in Section 3, and are included in the analysis presented in this section.<br />
Exhibit 4-1 Documentation That Met All Criteria<br />
Document Issuer<br />
Smart Card Standards<br />
Title Comments<br />
European Committee for<br />
Standardization (CEN)<br />
Smart Card Specifications<br />
CEN TC278/IFM<br />
Analyzed in detail<br />
ITSO Integrated Transport<br />
Smartcard<br />
Organization (ITSO)<br />
Analyzed in detail<br />
Smart Card Standards (non-Transit)<br />
International Standards<br />
Organization (ISO/IEC)<br />
ISO/IEC 8583 Analyzed in detail<br />
Smart Card Specifications (non-Transit)<br />
OFX<br />
Vendor Specifications<br />
Open Financial<br />
Exchange (OFX)<br />
Analyzed in detail<br />
Agent Systems Vending Equipment<br />
Interface (VEI)<br />
Analyzed in detail<br />
Cubic CID Edge Interfaces Analyzed in detail<br />
ERG APTA WG4<br />
Transaction Definitions<br />
Analyzed in detail<br />
Smart Card Project Specific Specifications<br />
Metropolitan<br />
Transportation<br />
Commission (MTC)<br />
®<br />
TransLink<br />
Analyzed in detail<br />
Port Authority New Regional<br />
Analyzed in detail<br />
York/New Jersey Interoperability<br />
(PANY/NJ)<br />
Specification (RIS)<br />
Part 4<br />
Page 12
Change language