300 likes | 500 Vues
FSUTMS Model Status and Standardization. Developments and Future Directions. Florida Model Task Force Meeting Tampa, FL December 13, 2006. Content. Model Conversion Application of Converted Models FSUTMS Framework Future Directions. Model Conversion Process. Model Conversion Steps
E N D
FSUTMS Model Status and Standardization Developments and Future Directions Florida Model Task Force Meeting Tampa, FL December 13, 2006
Content • Model Conversion • Application of Converted Models • FSUTMS Framework • Future Directions
Model Conversion Process • Model Conversion Steps • Citilabs/consultants convert the model • Districts/MPOs review the converted model • Citilabs/Consultants make changes • FDOT/Citilabs provide model specific training • Model Conversion Approach • Cube TRANPLAN as interim • Full Cube Voyager
Model Conversion Training • Model Specific Trainings Provided /Assisted by Citilabs/Central Office • NERPM • TBRPM • CFRPM • Miami-Dade • Lee/Collier • Sarasota/Manatee
Use of Converted Models • Converted Models Being Used • NERPM, Alachua, SERPM, Treasure Coast, CFRPM, TBRPM, Statewide models • Engineering and Planning Studies • Corridor Studies, Master Plans, DRI, PD&E
Completed and On-Going Studies • White Paper • Data Dictionary • Standard Reporting Templates • Review of FSUTMS Default Coefficients and Parameters • New Transit Modeling Framework
FSUTMS Web Portal • Launched on 08/01/2006 • Objectives • Open a communication channel between Model Task Force (MTF), Systems Planning Office (SPO), and Florida modeling/planning community • Build an information and data repository for model developers • Provide a discussion forum for model developers and users
Transit Modeling Framework • Why… • Outdated existing model system and new challenges • FTA regulations on travel forecasts and new QA guidelines • The industry moving towards multi-path modeling • Cube PT provides the tools • Implications to other model components
Transit Modeling Framework • What’s new … • PT “best path” • Two levels– general and New Starts areas • Affected transit modules • Transit access • Network coding • Path building • Mode Choice • Highway modules • Calibration and validation
Transit Modeling Framework • What’s new …(continued) • More focus on observed data • Consistently good transit coding practice • Relies on good highway practice • Highway network coding • Trip distribution • Auto speeds
Transit Modeling Framework • What does it mean … • Decide what area you belong to based on your local transit services and future growth • Modeling needs • Large areas – implementing the new framework immediately • Small areas – wait until next LRTP cycle
Transit Modeling Framework • What does it mean… (continued) • Immediate actions for all areas • Review/Split zones • Update highway network • Centroid connectors • Include required transit related attributes • Standardize field names • Revise transit modal numbers • Collect transit service data
Transit Modeling Framework • What will we do … • Develop required procedures and programs • Walk- and Auto- access connector programs • Path building scripting templates • Transit assignment reporting scripts • Revised mode choice model • Provide guidelines and documentation • Theoretical framework • Applications framework • Transit model validation guidelines
Transit Modeling Framework • What will we do … (continued) • Develop prototype model • Replace the current Olympus model components • Provide samples for network coding and templates • Conduct training workshop • June 06 • More early next fiscal year (Sept/Oct 07) • Provide on-time update on web portal • Documentation, programs, and prototype model • Technical Support (FAQs and online Q/As)
Future Directions • Short Term • Finalize transit modeling framework • Revisit the White Paper and Data Dictionary • Incorporate latest developments • Make more user friendly • Work with districts and MPO to implement the FSUTMS standards
Future Directions • Short Term (continued) • Implement FSUTMS reporting templates • Develop transportation network coding standards • Trip generation model • Comprehensive review of current models • Pursue income based trip generation model • Develop new structure and coefficients if necessary
Future Directions • Short Term (continued) • Model development & application guidelines • Best practice • Model calibration and validation guidelines • Calibration and Validation standards based on Review of Default Parameters Study • Model Applications • Work with Citilabs to provide customized FSUTMS CUBE software
Future Directions • Continuing Efforts • Model training workshops • Improve existing workshops • Develop new workshops as necessary • Assist model specific training • Online education/training • Technical support • Improve and enhance web portal
Future Directions • Long Term • Five-Year Model Development Plan
Questions Thank You !