Part 3: Regional Central System Interface Standard

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
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

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

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
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

7
Message Types (contd)

• 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.

8
CID to PICC Interaction Messages PICC
Initialization Messages

• Record the creation and issuance of a smart card
  for use in the regional program

9
CID to PICC Interaction Messages Load/Unload
Transaction Messages

• Record the addition and removal of fare products
  and services to/from the smart card

10
CID to PICC Interaction Messages Use Transaction
Messages

• Record the use of the smart card within agency
  systems

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

12
Scheme Control Messages Negative List Messages

• Used to transfer negative list updates from the
  RCS to agency systems

13
Scheme Control Messages Fare Policy Framework
Messages

• Used to transfer regional fare table updates from
  the RCS to agency systems

14
Scheme Control Messages Key Management Messages

• Used to download new authentication key sets from
  the RCS to agency systems

15
Interface to Other Clearing Houses End of Day
Reconciliation Messages

• Provide a summary of the transactions transmitted
  from an agency system to the RCS

• A501 End of Day Position
• A502 - End of Day Transaction Receipt

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.

17
Message Structure (contd)

• 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

18
Message Structure Example
Item Number Data Element Name
1.1 MessageIdentifier
1.2 MessageVersion
1.3 MessageRevision
1.4 LocationDataObject
1.5 VehicleDataObject
1.6 EquipmentDataObject
1.7 PICCDataObject
1.8 DateAndTimeDataObject
1.9 EmployeeDataObject
1.10 ActionEventDataObject
2.1 AuthenticationDataObject
3.1 TAPOAsRead
3.2 PHPOAsRead
3.3 RegionalTPurseObjectAsWritten
3.4 RegionalTPurseXAsWritten
3.5 THOAsWritten
3.6 THOXAsWritten
4.1 UseDeductDataObject
4.2 UseValidationDataObject
Message NameUse of Regional T-Purse
Section 1 When and Where
Section 2 Authentication
Section 3 PICC Data
Section 4 CID Data
19
Message Definition Format

• Messages are defined in a consistent format to
  assist in interpretation

• Use of Regional T-Purse

Message Name Use of Regional T-Purse
Purpose/Use Documents the use of the regional T-Purse only to pay for transit service
Publisher/Creator AFC device
Subscriber(s) Regional Clearing House or Product Owner
Notes
Item Number Data Element Name XML Tag Notes
1.1 MessageIdentifier ltMessageIdentifiergt A401
1.2 MessageVersion ltMessageVersiongt
1.3 MessageRevision ltMessageRevisiongt
1.4 LocationDataObject ltLocationDataObjectgt
1.5 VehicleDataObject ltVehicleDataObjectgt Optional
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

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

22
Evolution of the Standard

• Interface to Agency Central System may be added
• Implementation Guide
• Certification and Testing

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

24
More Information

• Martin Schroeder, P.E., APTA
• mschroeder_at_apta.com
• 202-496-4885