Fare Collection Concept of Operations and Use Case Review

MARCH 26, 2010 1 : 0 0 - 3 : 0 0 P M

PREPARED BY: PAULA OKUNIEFF & PATRICK CHAN CONSYSTEC Agenda

 Status  Fare Structure Inventory  Use Cases  Fare Calculator: Normal Flow of Control  Fare Calculator: Exception – Using Agency Fare API  Discussion and Issues  Schedule to completion FC Work Status

 3-26-2010 Published first draft Appendix B – Use Case for Fare Calculator  3-25-2010 Published first draft FC ConOps with inventory database  12-23-2009 Completed operational scenarios based on Matrix  9-24-2009 Generated Matrix for Operational Scenarios  9-23-2009 RSTWG  Discuss White Paper (final publication 10 Oct 2009) A transit operator (Agency) has one or more fares (FC_Fare) for different types of services and modes it offers to the public. The fares are driven by the customer’s trip based on when he/she travels (FC_TimePeriod), origin- destination and path of travel (FC_Geographic_Fare_Stru cture), and one or more general rules (BR_BusinessRule_general) such as transfers (BR_Transfer) and eligible rider discounts (BR_Discount). The cost (BR_Discount) depends on the rider (RiderClass) or the group of Regional Inventory of Fares and people who are traveling (RC_Group). Transfers Agency Table

Agency ID Agency Name Agency Acronym Mode 1 CoachUSA Shortline commuter bus 2 Dutchess County bus 3 Long Beach Transit (Nassau) LBT bus

4 MTA Bus LIB bus 5 MTA Long Island Rail Road LIRR commuter rail 6 MTA Metro North Railroad MNR commuter rail

7 MTA Bus NYB bus 8 MTA NYC Transit Bus NYCT bus 9 MTA NYC Transit Subway NYCT subway 10 Transit Bus NJ TRANSIT bus 11 New Jersey Transit Commuter Rail NJ TRANSIT commuter rail

12 New Jersey Transit Light Rail NJ TRANSIT light rail

13 Orange County bus 14 PATH PATH subway 15 Putnam Area Rapid Transit PART bus

16 SCT bus 17 Tappenzee Express TZE bus 18 Transport of Rockland TOR bus 19 Westchester Bee-Line Bus B-Line bus 20 Transit CT bus RC_YoungChild riderClass agencyName riderclass max_age comment discount discount_comment free Connecticut Transit Child 4 Free With Fare-Paying Adult, Limit Three Children per Adult free Dutchess County Child 5 Free Children Under 6 Yrs free Long Beach Transit (Nassau) Child 4 Free Children Under 5 Yrs free MTA Long Island Bus Child 44" Tall and Under Free With Fare-Paying Adult, Limit Three Children per Adult free MTA Long Island Rail Road Child 44" Tall and Under Free With Fare-Paying Adult, Limit Three Children per Adult free MTA Metro North Railroad Child 44" Tall and Under Free With Fare-Paying Adult, Limit Three Children per Adult free MTA New York Bus Child 44" Tall and Under Free With Fare-Paying Adult, Limit Three Children per Adult free MTA NYC Transit Bus Child 44" Tall and Under Free With Fare-Paying Adult, Limit Three Children per Adult free MTA NYC Transit Subway Child 44" Tall and Under Free With Fare-Paying Adult, Limit Three Children per Adult free New Jersey Transit Bus Child 4 Free With Fare-Paying Adult, Limit Three Children per Adult free New Jersey Transit Commuter Child 4 Free With Fare-Paying Adult, Limit Rail Three Children per Adult free New Jersey Transit Light Rail Child 4 Free With Fare-Paying Adult, Limit Three Children per Adult free Suffolk County Transit Child 4 Free Children Under 5 Yrs, with Fare Paying Adult free Tappenzee Express Child 40" Tall and Under Free With Fare-Paying Adult free Transport of Rockland Child 40" Tall and Under Free With Fare-Paying Adult free Westchester Bee-Line Bus Child 44" Tall and Under Free With Fare-Paying Adult, Limit Three Children per Adult Rider Class Summaries

 Free (young child)  Different height and ages  Paying adult (up to 3 children)  Child  Different min/max ages  Youth / Student  Different min/max ages  Student vs. youth  Senior  Start at different ages 60 to 65  Disabled  As designated by the agency Fare Structures / Time Periods

 Different Peak Periods  Even within an agency (e.g., Dutchess)  Geographic Units  Zone - Distance (mostly commuter bus and rail)  Flat  Transfer business rules  Order of use  Time duration between trips  Purchase as “package”  Transfer at certain location(s) -- e.g., don’t leave the system  Direction of travel Use Case:  Covers the situation where Fare travelers are searching for the Calculator transit fare (cost) for a desired The regional fare transit trip that may involve calculator allows travelers to view multiple modes and operators in their total trip costs the New York region. for each trip option based on their  Normal Flow of Control [Normal] selected criteria such  Use of Agency Fare API [Agency API] as origin, destination, travel date/time, user and usage constraints, one way or return trip. Enumeration  Request and verify customer trip of Needs: itinerary (from Trip Plan) Normal  Origin-destination; begin and ending times What are the functions that are  Options for parking used to process the  Order of legs and providers data?  Distance and wait times between legs What are the “data  Trip legs and provider services products” (inputs and outputs) for each  Origin-destination by leg function?  Path / distance by leg  Time begin/end by leg  Mode and service type  Mobility needs Enumeration  Request and verify customer of Needs: usage and discount characteristics Normal  Rider(s) characteristics – age, Fare Promotions, eligibility, number of riders and other options are  Product preference (if available) deferred for now. They are included  Other usage characteristics? here as “hooks”.  Check for Fare Promotions (special cases)  Provide options for other criteria  Fare product types  Payment options / vendor location  Bundled product and promotions Enumeration  Calculate Fare based on logical of Needs: parameters Normal  Total Fare What other  Fare and product/payment method per information should leg be provided to customer?  Instructions for transfer products (e.g., validate ticket; stay in subway; use What information is needed from same Metrocard; purchase tickets Operators about together) their fare structures to provide this information? Enumeration  Request and verify customer trip of Needs: itinerary (from Trip Plan) Agency API  Request and verify customer What if an Agency’s usage and discount characteristics fare structure data is so complex that it is  Provide options for other criteria too difficult to encode?  Calculate Fare based on logical Can they use their parameters Fare API?  Send one or more requests to API trip leg (with one or more usage criteria)  Incorporate fare best value into final result set including Normal results Discussion and Issues

 This fare calculator does not “optimize” an itinerary by fare cost. Should not matter for the purposes of discovering data requirements.  API method may not work to optimize transfer cost between agencies. Next Steps and Schedule

 Review and incorporate comments into Use Case  Publish Use Case by April 13  Develop Planning Use Case and publish in early May  Meet in early May to finalize ConOps  Develop Draft FC Data Profile Requirements Document