PLANNING RSTWG
Review of Planning Concept of Operations & Requirements
Tasks
Agenda
Context for Regional Planning SDP ExtensionReview Planning Concept of Operations
Overview and process Needs
Requirements Approach Planning Data Concepts
Next Steps
“ A F R A M E W O R K T O P R O V I D E A S I N G L E P O I N T O F S T O R A G E , D I S C O V E R Y, A N D A C C E S S T O A VA R I E T Y O F
T R A N S I T S E R V I C E I N F O R M AT I O N A N D T O O L S ”
I N C LU D I N G
R E G I O N A L T R A N S I T P L A N N I N G D ATAF O R R E G I O N A L T R A N S I T P L A N N E R S
TSIP Project Purpose
Task & ScheduleTask 2 & 3 – 11 Months
Task 4 – about Month 7
Task 5 – 11th Month
Task 2: SDP Extensions Planning Data Real Time / Status Data Fare Data
Task 3: TSIP RequirementsTask 4: External TSIP
RequirementsTask 5: Procurement
Approach
SDP Planning Extension – Planning TWG(Tasks and Deliverables)
Concept of OperationsAddendum
for Regional Planning
(includes Use Cases for regional Planning Data
needs)
Functional RequirementDocuments
(1) Planning Performance Measures from SDP
(2) Additional SDP Data Req’ts
Corridor Study Use Case
TIP/RTP/Air Quality Conformity Use Case
Prototype SDP XML Schema Extension
Demonstration
Validate SDP XML Documents with Downstream Application
Planning Application or Report
Final Deliverables
(1) SDP Guidance Documents(2) SDP XML Schema (final)
(3) Updated Functional Requirements Document & Conceptual Data Reference Model
Physical Data Model
Market Studies Use Case
Transit Study/MIS Use Case
Two white papers:-- scan of NY regional planning-- industry scan: emerging tools
Completed
TSIP Project Systems Engineering Approach
Concept of Operationsfor
Regional Service Data Repository & Portal
(includes TSDEA Use Cases, Portal and SDP Extension
UC)
System RequirementsFor
TSIP Implementation Includes family of SDP data models and XML Schema
Trip Planning Use Cases & ConOps Addendum
RT Status Use Case
Fare Calculator Use Case
SDP, Calendar and Extension XML Schema &
open source code
Specifications and Request for Proposal
Final Deliverables
(1) SDP and Extension Guidance Documents(2) SDP XML Schemas(3) Requirements Document & Conceptual Data Reference Models for all SDP / SDP Extensions(4) Demonstration results (conversion software from native Agency data to SDP to downstream applications)
SDP / SDP Extension Requirements
Portal Use Cases
SDP Extensions
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 JulyFirst Planning RSTWG Meeting: 19 June (half
day)
Planning ConOps Overview
IntroductionCurrent SystemPlanning Data Profile ConceptUse Case DescriptionsEnumeration of NeedsRoles & ResponsibilitiesAppendices (A-G)
Glossary Use Cases #1-#4 White Papers 1 & 2
Enumeration of Needs
DataData FormatFunctional
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 data4. 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
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)
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
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
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
Data Format Needs
Profile: NYBPMFormat: comma separated values (csv) for
Excel
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-
polygonAbility to compare two identical data sets and
identify changes Save a request to use at a later date
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.
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 rulesIdentify exceptions, constraints, issues
Note: system requirements for functions and encoding approaches will be included in the TSIP Portal Specifications (Task 3)
Example: Location (Definitions, Data Usage)
Example: Location (Req’ts Description)
Example: Location (Attributes)
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