1 / 14

TSIP: Fare Calculator Profile

TSIP: Fare Calculator Profile. Fare Collection RSTWG 23 September 2009. Discussion Items. Context for Fare Calculator SDP Extension Approach – Bottom Up Use Case Development & Concept of Operations Use Case Development Next Steps. TSIP Project Purpose.

edan
Download Presentation

TSIP: Fare Calculator Profile

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. TSIP: Fare Calculator Profile Fare Collection RSTWG 23 September 2009

  2. Discussion Items • Context for Fare Calculator SDP Extension • Approach – • Bottom Up • Use Case Development & Concept of Operations • Use Case Development • Next Steps

  3. TSIP Project Purpose “a framework to provide a single point of storage, discovery, and access to a variety of transit service information and tools” Including Fare and Transfer Information

  4. Task 2: SDP Extensions • Planning Data • Real Time / Status Data • Fare Data • Task 3: TSIP Requirements • Task 4: External TSIP Requirements • Task 5: Procurement Approach Task & Schedule Task 2 & 3 – 11 Months Task 4 – about Month 6 Task 5 – 11th Month

  5. TSIP Project Systems Engineering Approach

  6. Fare Data – FC TWG (Tasks and Deliverables) White Paper -- Industry scan: Models, tools and issues -- NY Fare Policies

  7. Approach • Bottom-up Approach • Identify all the same, similar and different descriptions of fare structures across the regional NYC operators • Develop classification scheme that describes the categories; agree on the data concept definitions • Describe the relationship among the categories • Document existing fare structures using the classification scheme • Develop Fare Calculator Use Case • Operational scenarios • typical “trip itineraries” • complex transfer structures among multiple agencies

  8. Scan of Operator Fare Policies

  9. Classification Scheme

  10. Example Regional Fare Structure Logical Data Model Describe Relationship among Data Concepts

  11. Use Case Development • Name • Description • Operational Scenarios • Enumeration of Needs • Data Concept Definitions and • “Functional (Pricing Rule) Description

  12. Example Use Case from Real Time Use Case #1. Typical Request for Predicted Service Information Description: “This set of scenarios show typical requests for information by patrons who are using or want to use Public Transit services.” OS #1 -- Traveler @ Home [Office] looking for a trip: Martha, a suburban commuter, fires up her Internet Browser to a bookmarked request that includes her commute trip application. The web page shows the estimated arrival and travel times of the next three buses from Nyack to NYPA. The web site also shows the current travel times for two other transit operators (MNR and Bee-Line) Martha may take. Based on the travel times and convenience, Martha decides to take the CoachUSA bus. This way she won’t have to fight the traffic and look for a parking space once she is in town.

  13. Fare Calculator Use Case Selection • Scope of Fare Calculator Use Cases? • Prices: fare structure and usage parameters • Sales Packages: Products, Charging Methods • Use “real” trip itineraries • Select Use Case Topic Areas: • Use Case #1: Typical in every category • Use Case #2: Exception Handling • Use Case(s) #3-n: Complex Situations • Extract Data Concepts • Identify Relationships and Issues

  14. Next Steps • Recommend Use Case Categories and Operational Scenarios (Today) • Look to existing structures and potential future policy areas • Add additional topics on the wiki until Oct 9. • Develop Draft Use Case (mid-October) • Select and extend operational scenarios • Identify Needs (data concepts and rule sets) • Stakeholder review of operational scenarios and data concept descriptions (early November)

More Related