1. PLANNING RSTWG Review of Planning Concept of Operations & Requirements Tasks

2. Agenda Context for Regional Planning SDP Extension Review Planning Concept of Operations  Overview and process  Needs Requirements Approach  Planning Data Concepts Next Steps

3. “A FRAMEWORK TO PROVIDE A SINGLE POINT OF STORAGE, DISCOVERY, AND ACCESS TO A VARIETY OF TRANSIT SERVICE INFORMATION AND TOOLS” INCLUDING REGIONAL TRANSIT PLANNING DATA FOR REGIONAL TRANSIT PLANNERS TSIP Project Purpose

4. Task & Schedule Task 2 & 3 – 11 Months Task 4 – about Month 7 Task 5 – 11 th Month 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

5. SDP Planning Extension – Planning TWG (Tasks and Deliverables) Two white papers: -- scan of NY regional planning -- industry scan: emerging tools Completed

6. TSIP Project Systems Engineering Approach

7. Planning Concept of Operations Development Published Final ConOps – posted 10 September 2009  Comments were due on 8 Sept COB; no comments received Draft ConOps – posted 11 August 2009  ConOps webinar: 28 July Final Planning Use Cases – posted 11 August 2009  Incorporated changes recommended by RSTWG Draft Use Cases – posted between 13-19 July First Planning RSTWG Meeting: 19 June (half day)

8. Planning ConOps Overview Introduction Current System Planning Data Profile Concept Use Case Descriptions Enumeration of Needs Roles & Responsibilities Appendices (A-G)  Glossary  Use Cases #1-#4  White Papers 1 & 2

9. Enumeration of Needs Data Data Format Functional

10. Data Needs 1. Need to access transit service information by temporal categories. 2. Need to access scheduled transit service information from operators 3. Need to access summary planning data 4. Need to access summary planning data by the following Transit Service information categories and subcategories 5. Need to compare transit service information and planning data from different time periods

11. Data Needs, detailed 1. Need to access transit service information by temporal categories. 2. Need to access scheduled transit service information from operators by  Routes, routes by route direction, trips, patterns, modes  Activation and deactivation dates (schedule version)  Revisions, special schedules and detours  Transit Stops including complex stops, amenities, passenger access components, portals  Fare and transfer policies (by operator and among operators)

12. Data Needs, detailed 3. Need to access summary planning data including:  Ridership (bus and rail)  Passenger loads, boardings, alightings and transfers  Span of service  Accessibility such as ADA information on transit vehicles and facilities  Service type  Transfer connection opportunities  Running times  Headways / Frequencies  Service quality data (indicators such as schedule adherence, quality index)  Fare policies and fare collection data  Ridership origin-destination data

13. Data Needs, detailed 4. Need to access summary planning data by the following Transit Service information categories and subcategories  Routes (by route direction) or Transit Path (by stopping pattern)  Trips (by route)  Accessibility of vehicle operating trip  Transit Stops

14. Data Needs, detailed 5. Need to compare transit service information and planning data from different time periods  New service  Eliminated service  Expanded service  Changed service

15. Data Format Needs Profile: NYBPM Format: comma separated values (csv) for Excel

16. Functional Needs Query by Transit Data Concept (SDP data concepts) Query by Agency (SDP or extension) Query by temporal and spatial analytical parameters  Temporal categories include year, period, day type/date, time  Spatial analysis includes -- Points-in-polygon; Paths-in- polygon Ability to compare two identical data sets and identify changes  Save a request to use at a later date

17. Functional Needs, cont. Ability to add new data concepts or adapt existing data concepts from a data dictionary Enable collaboration among regional planners on new and refined data concepts, formats and content. Enable ability for planners to send questions and receive responses from Data Providers on their data.

18. Next Step: Develop Planning Data Concept Wiki Pages Define data concepts with respect to industry definitions and local usage Describe requirements  For data concept  Describe attributes Describe business rules Identify exceptions, constraints, issues Note: system requirements for functions and encoding approaches will be included in the TSIP Portal Specifications (Task 3)

19. Example: Location (Definitions, Data Usage)

20. Example: Location (Req’ts Description)

21. Example: Location (Attributes)

22. Next Steps Describe Data Concept White Paper  Initiate discussion on the wiki on the “Data Concept” pages  Draft pages complete: Oct 13  White paper due Oct 19 Develop Planning Data Requirements document  Includes data model of data concepts  Draft Req’ts Document: Oct 26  Final Req’ts Document: Nov 11 XML Schema (data definitions and tags)  Due Nov 16