1 REGIONAL SERVICE PLANNING WEBSITE

15
1 REGIONAL SERVICE PLANNING WEBSITE www.regionalserviceplanning.o rg/

Transcript of 1 REGIONAL SERVICE PLANNING WEBSITE

Page 1: 1 REGIONAL SERVICE PLANNING WEBSITE

1

REGIONAL SERVICEPLANNINGWEBSITE

www.regionalserviceplanning.org/

Page 2: 1 REGIONAL SERVICE PLANNING WEBSITE

2

Page 3: 1 REGIONAL SERVICE PLANNING WEBSITE

3

Page 4: 1 REGIONAL SERVICE PLANNING WEBSITE

4

Page 5: 1 REGIONAL SERVICE PLANNING WEBSITE

5

Page 6: 1 REGIONAL SERVICE PLANNING WEBSITE

6

Page 7: 1 REGIONAL SERVICE PLANNING WEBSITE

7

Page 8: 1 REGIONAL SERVICE PLANNING WEBSITE

8

Page 9: 1 REGIONAL SERVICE PLANNING WEBSITE

9

Page 10: 1 REGIONAL SERVICE PLANNING WEBSITE

10

Entity’s Name

Please Describe

Contact info

Type of request

Page 11: 1 REGIONAL SERVICE PLANNING WEBSITE

11

Questions ?

Page 12: 1 REGIONAL SERVICE PLANNING WEBSITE

12

Public Transportation Resources Inventory

• Legislative requirement for TxDOT

• Opportunity to coordinate with RSP Lead Entities

Page 13: 1 REGIONAL SERVICE PLANNING WEBSITE

13

Key tasks:– Establish objectives and potential uses of the data– Structure data collection instrument and database– Maximize use of existing data (NTD, TxDOT, etc.)– Pilot test data collection instrument– Collect data with assistance of Lead Entities– Synthesize data and prepare report for each region– Provide process for annual update

Page 14: 1 REGIONAL SERVICE PLANNING WEBSITE

14

Inventory: Data Categories• Providers of public

transportation• Agencies that fund or purchase

public transportation• User/ client and trip eligibility• Service area, span of service,

and mode(s)• Ridership• Fleet inventory (size, condition,

fuel, technology)

• Financial: funding sources, operating and capital expenses

• User fee or fare structure• Coordination: on-going and

opportunities• Constraints (geographic, client,

trip purpose, funding)• Purchased transportation/ Use

of Private-for-Hire vehicles (PHV)

Page 15: 1 REGIONAL SERVICE PLANNING WEBSITE

15

Inventory Schedule

• Two weeks: complete development of objectives/data uses

• Two weeks: complete development and testing of data collection instrument

• Six weeks: complete data collection• Two weeks: complete necessary follow-up• One week: make database available