1 / 24

Part 3: Regional Central System Interface Standard

Part 3: Regional Central System Interface Standard. Talking Technology and Transportation (T3) May 17, 2006 Using Standards to Make “Smart” Choices. David Mcilwraith Booz Allen Hamilton. UTFS Elements of Standardization. PART 3 – Regional Central System Interface Specification.

dior
Download Presentation

Part 3: Regional Central System Interface Standard

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Part 3: Regional Central System Interface Standard Talking Technology and Transportation (T3) May 17, 2006 Using Standards to Make “Smart” Choices David Mcilwraith Booz Allen Hamilton

  2. UTFS Elements of Standardization PART 3 – Regional Central System Interface Specification PART 4 – System Security Planning and Implementation Guideline PART 2 – Contactless Fare Media Data Format and Interface Standard Using Standards to Make “Smart” Choices

  3. General Scope of the Part 3 Standard • Applies to regional smart card-based fare collection systems • Two or more transit agencies using a common smart card • Agency specific as well as regional fare products on the card can be accommodated • Defines the messages between the Regional Central System (RCS) and the fare collection system • Uses existing standards and common practices where possible Using Standards to Make “Smart” Choices

  4. General Purpose of thePart 3 Standard • Allow system components from multiple vendors to communicate with one Central System • Allow multiple transit agencies within a region to share a common Central System • Transit agencies can join a regional system at different times • Existing individual agency systems can form a regional system • Once the vendor implements the standardized interface, standard is developed, it can be reused elsewhere in other projects Using Standards to Make “Smart” Choices

  5. General Description of the Part 3 Standard • Messages originate either at a CID (i.e. card device), Agency Central System, or the Regional Central System • Message definitions consist of a set of Data Objects, which are in turn made up of Data Elements • The Standard consists of a set of messages, with each message defined by a set of Data Objects and Data Elements • Each message has a unique identifier • Messages are transmitted using XML (Extensible Markup Language) Message Object 1 Object 2 Object 3 Object n Object Identifier Object Data Elements Using Standards to Make “Smart” Choices

  6. Message Types The Part 3 Standard groups messages into three categories: • CID to PICC Interaction Messages used to transfer transaction data • PICC Initialization • Fare Product and Service Load and Unload Transactions • Use Transactions and RCS Acknowledgements Using Standards to Make “Smart” Choices

  7. Message Types (cont’d) • Scheme Control Messages Convey information relating to the operation of the card or device. • Action list • Negative List • Fare policy framework • Key management • Interface to Other Clearing Houses A minimal set of messages required to allow for financial clearing and settlement between two regional systems. Using Standards to Make “Smart” Choices

  8. CID to PICC Interaction MessagesPICC Initialization Messages • Record the creation and issuance of a smart card for use in the regional program Using Standards to Make “Smart” Choices

  9. Record the addition and removal of fare products and services to/from the smart card CID to PICC Interaction MessagesLoad/Unload Transaction Messages Using Standards to Make “Smart” Choices

  10. CID to PICC Interaction MessagesUse Transaction Messages • Record the use of the smart card within agency systems Using Standards to Make “Smart” Choices

  11. Scheme Control Messages Action List Messages • Used to transfer autoload requests from the RCS to agency systems and to record the addition, removal, and use of autoload services Using Standards to Make “Smart” Choices

  12. Scheme Control Messages Negative List Messages • Used to transfer negative list updates from the RCS to agency systems Using Standards to Make “Smart” Choices

  13. Scheme Control Messages Fare Policy Framework Messages • Used to transfer regional fare table updates from the RCS to agency systems Using Standards to Make “Smart” Choices

  14. Scheme Control Messages Key Management Messages • Used to download new authentication key sets from the RCS to agency systems Using Standards to Make “Smart” Choices

  15. Interface to Other Clearing Houses End of Day Reconciliation Messages • A501 – End of Day Position • A502 - End of Day Transaction Receipt • Provide a summary of the transactions transmitted from an agency system to the RCS Using Standards to Make “Smart” Choices

  16. Message Structure • Most messages send information generated by the CID to the RCS (usually via a local computer, and an Agency Central System). • These messages consist of data extracted from and added to the PICC and data generated by the CID. • These messages have a common general structure, although the actual content will vary with message type. Using Standards to Make “Smart” Choices

  17. Message Structure (cont’d) • For these messages, Message Data Objects and Elements are grouped into four sections: • 1: When and where used data – information on when and where the transaction occurred • 2: Authentication data – used to validate the message • 3: PICC data – information used or modified on the PICC as part of the transaction • 4: CID data – information created by the CID as part of the transaction Using Standards to Make “Smart” Choices

  18. Message Structure: Example Message Name:Use of Regional T-Purse Section 1: When and Where Section 2: Authentication Section 3: PICC Data Section 4: CID Data Using Standards to Make “Smart” Choices

  19. Message Definition Format • Messages are defined in a consistent format to assist in interpretation • Use of Regional T-Purse Using Standards to Make “Smart” Choices

  20. Advantages of Adoption • Interoperability • Transit agencies can accept other agencies smart cards • Agency systems can be procured and implemented at different times • Reduced Cost • Reduced need for customization and re-engineering • Transit agencies can purchase equipment from multiple vendors (competitive procurement) • Potential to share costs through common operations Using Standards to Make “Smart” Choices

  21. Mechanism for Adoption & Use • Achieve consensus for UTFS adoption among participating agencies • Define business rules for regional program participation (including ownership, governance, regional fare products, fee and revenue sharing) • Identify distinct messages and implementation approach to be used within the region • Establish RCS with support for selected messages • Procure new (or modify existing) systems to support XML-based messages exchanges with RCS Using Standards to Make “Smart” Choices

  22. Evolution of the Standard • Interface to Agency Central System may be added • Implementation Guide • Certification and Testing Using Standards to Make “Smart” Choices

  23. Review Points • Comprehensive message set to allow for standardization in communication with Regional Central System • Flexibility to allow for different scenarios • Full definitions of data elements and objects for each message type • Uses XML for message transmission Using Standards to Make “Smart” Choices

  24. More Information Martin Schroeder, P.E., APTA mschroeder@apta.com 202-496-4885 Using Standards to Make “Smart” Choices

More Related