FSUTMS Model Status and Standardization Developments and Future

FSUTMS Model Status and Standardization Developments and Future Directions Florida Model Task Force Meeting Tampa, FL December 13, 2006

Content v Model Conversion v Application of Converted Models v FSUTMS Framework v Future Directions 2

Model Conversion Process v Model Conversion Steps Citilabs/consultants convert the model q Districts/MPOs review the converted model q Citilabs/Consultants make changes q FDOT/Citilabs provide model specific training q v Model Conversion Approach Cube TRANPLAN as interim q Full Cube Voyager q 3

Model Conversion Training v Model Specific Trainings Provided /Assisted by Citilabs/Central Office NERPM q TBRPM q CFRPM q Miami-Dade q Lee/Collier q Sarasota/Manatee q 4

Model Conversion Status Model Name Conversion Status QA Status 1 Bay County TPO Model Cube Voyager In Process 2 Broward County MPO Model Cube Voyager Complete 3 Collier/Lee County MPO Model Cube Voyager In Process 4 D-1 Districtwide Model Pending 5 D-5 Districtwide Model (CFRPM) Cube/TRANPLAN Complete 6 Desoto County Model Cube Voyager In Process 7 Florida-Alabama TPO Model Cube Voyager In Process 8 Alachua County MPO Model Cube Voyager Complete 9 Glades County Model Cube Voyager In Process 10 Hardee County Model Cube Voyager In Process 11 Hendry County Model Cube Voyager In Process 12 Highlands County Model Cube Voyager In Process 13 Miami-Dade MPO Model Cube/TRANPLAN In Process 5

Model Conversion Status Model Name Conversion Status QA Status 14 Northeast Regional Planning Model Cube Voyager Complete 15 Okaloosa-Walton TPO Model Cube Voyager In Process 16 Orlando (Metroplan) MPO Model Cube/TRANPLAN Complete 17 Palm Beach MPO Model Cube Voyager Complete 18 Polk County TPO Model Cube Voyager In Process 19 Putnam County Model Cube Voyager In Process 20 Sarasota/Manatee MPO Model Cube Voyager In Process 21 Southeast Regional Planning Model Cube/TRANPLAN Complete 22 Tallahassee-Leon QRS Model Pending 23 Capital Region MPO Model Cube Voyager In Process 24 Tampa Bay Regional Planning Model Cube/TRANPLAN Complete 25 Treasure Coast Regional Model Cube Voyager Complete 26 Florida Statewide Model Cube Voyager Complete 6

Use of Converted Models v Converted q Models Being Used NERPM, Alachua, SERPM, Treasure Coast, CFRPM, TBRPM, Statewide models v Engineering q and Planning Studies Corridor Studies, Master Plans, DRI, PD&E 7

Completed and On-Going Studies v White Paper v Data Dictionary v Standard Reporting Templates v Review of FSUTMS Default Coefficients and Parameters v New Transit Modeling Framework 8

FSUTMS Launcher/Interface 9

FSUTMS Launcher/Interface 10

FSUTMS Web Portal v Launched on 08/01/2006 v Objectives Open a communication channel between Model Task Force (MTF), Systems Planning Office (SPO), and Florida modeling/planning community q Build an information and data repository for model developers q Provide a discussion forum for model developers and users q 11

WWW. FSUTMSONLINE. NET 12

New Training Model - Olympus 13

Olympus Model File Structure 14

Olympus Model User Interface 15

Olympus Special Applications 16

Transit Modeling Framework v Why… Outdated existing model system and new challenges q FTA regulations on travel forecasts and new QA guidelines q The industry moving towards multi-path modeling q Cube PT provides the tools q Implications to other model components q 17

Transit Modeling Framework v What’s new … PT “best path” q Two levels– general and New Starts areas q Affected transit modules q Transit access u Network coding u Path building u Mode Choice u Highway modules q Calibration and validation q 18

Transit Modeling Framework v What’s new …(continued) More focus on observed data q Consistently good transit coding practice q Relies on good highway practice q Highway network coding u Trip distribution u Auto speeds u 19

Transit Modeling Framework v What does it mean … Decide what area you belong to based on your local transit services and future growth q Modeling needs q Large areas – implementing the new framework immediately u Small areas – wait until next LRTP cycle u 20

Transit Modeling Framework v What q does it mean… (continued) Immediate actions for all areas Review/Split zones u Update highway network u § Centroid connectors § Include required transit related attributes § Standardize field names Revise transit modal numbers u Collect transit service data u 21

Transit Modeling Framework v What q will we do … Develop required procedures and programs Walk- and Auto- access connector programs u Path building scripting templates u Transit assignment reporting scripts u Revised mode choice model u q Provide guidelines and documentation Theoretical framework u Applications framework u Transit model validation guidelines u 22

Transit Modeling Framework v What q will we do … (continued) Develop prototype model Replace the current Olympus model components u Provide samples for network coding and templates u q Conduct training workshop June 06 u More early next fiscal year (Sept/Oct 07) u q Provide on-time update on web portal Documentation, programs, and prototype model u Technical Support (FAQs and online Q/As) u 23

Future Directions v Short Term Finalize transit modeling framework q Revisit the White Paper and Data Dictionary q Incorporate latest developments u Make more user friendly u q Work with districts and MPO to implement the FSUTMS standards 24

Future Directions v Short Term (continued) Implement FSUTMS reporting templates q Develop transportation network coding standards q Trip generation model q Comprehensive review of current models u Pursue income based trip generation model u Develop new structure and coefficients if necessary u 25

Future Directions v Short q Term (continued) Model development & application guidelines Best practice u Model calibration and validation guidelines u Calibration and Validation standards based on Review of Default Parameters Study u Model Applications u q Work with Citilabs to provide customized FSUTMS CUBE software 26

FSUTMS CUBE Menu System 27

Future Directions v Continuing q Efforts Model training workshops Improve existing workshops u Develop new workshops as necessary u Assist model specific training q Online education/training q Technical support q Improve and enhance web portal q 28

Future Directions v Long q Term Five-Year Model Development Plan 29

Questions 30