Below are the minutes for the Regional Transportation Advisory Committee meeting, held on Friday, May 20, 2005, from 9:00 a.m. to 11:00 a.m. in the Training Room 679 (6th Floor), at the Clark County Public Service Center, 1300 Franklin Street, Vancouver, Washington. The agenda for this meeting is also available.

Minutes

I. Call to Order and Approval of Minutes

The meeting of the Regional Transportation Advisory Committee was called to order on Friday, May 20, 2005 at 9:00 a.m. in the Conference Room (6th Floor) at the Public Service Center, 1300 Franklin Street Vancouver, Washington. Dean Lookingbill, Transportation Director, served as Chair for the meeting. Those in attendance follow:

Justin Clary		City of Ridgefield
Lynda David		RTC
Mark Garrity		WSDOT
Mark Harrington		RTC
Bob Hart		RTC
Dean Lookingbill		RTC
Mike Mabrey		Clark County
Timilee Pederson		City of Washougal
Ed Pickering		C-TRAN
Matt Ransom		City of Vancouver
Sandi Roberts		RTC
Dale Robins		RTC
Wade Strange		SW Clean Air Agency
Bill Wright		Clark County
Phil Wuest		City of Vancouver

Dean Lookingbill, RTC, asked for any changes or corrections to the April 15, 2005, meeting minutes.

PHIL WUEST, CITY OF VANCOUVER, MOVED FOR APPROVAL OF THE APRIL 15, 2005 MINUTES AND JUSTIN CLARY, CITY OF RDIGEFIELD, SECONDED THE MOTION. THE MOTION WAS UNANIMOUSLY APPROVED.

II. 2005-2007 MTIP Correction C-TRAN, Action

Dale Robins, RTC, stated that RTC’s policy has been to keep agencies informed of all changes to the Metropolitan Transportation Improvement Program (MTIP), including minor project corrections. C-TRAN is requesting the title of their “Vancouver Mall Transit Center” project be changed to “Vancouver Transit Center”. Dale pointed out by dropping “Mall” from the title is more consistent with potential relocation of the facility. C-TRAN has discussed the need for this change with FTA, and they have expressed support for this change. Dale pointed out that the C-TRAN MTIP correction request letter and amended STIP project sheet are attached to the memorandum. Ed Pickering said C-TRAN had conducted some analysis of alternative site locations in Orchards, close to C-TRAN office, a site at Vancouver Mall Drive, Andresen and the K-Mart site. After some RTAC discussion, Dean Lookingbill summarized and said RTC would make the administrative change.

III. 2004 Congestion Monitoring Report, Action

Dale Robins, RTC, presented the 2004 Congestion Monitoring Report and said it represents the sixth year for this annual report. Dale said, prior to 2000, the transportation system performance focused on a single corridor congestion index for each of the congestion management corridors. Over time, the report has been expanded to include travel time, speed, vehicle occupancy, transit ridership, bus capacity, intersection delay, areas of concern, and other transportation system related information. The 2004 Congestion Monitoring Report continues the collection and reporting of baseline data.

Dale said the Congestion Monitoring Report measures and quantifies average weekday congestion in the AM and PM peak periods. Dale pointed out that while the report quantifies congestion per a set criteria, it is recognized that the individual motorist’s view of congestion varies according to their tolerance for travel delay. Dale noted the congestion management system is designed to focus on regional travel characteristics. Transportation corridor segments were selected as the basic unit for describing the performance of the system. The corridor approach that incorporates parallel routes and transit services also provides a regional orientation and responds to the multimodal and alternative travel themes of the Federal Transportation Act. Dale pointed out the 2004 congestion management system includes 30 regionally significant transportation corridors within the Clark County region.

Dale reviewed each map: 

1. Congestion Management Network, 
2. Vehicle Volumes, 
3. P.M. Vehicle Volumes, 
4. A.M. Capacity Ratio, 
5. P.M. Capacity Ratio, 
6. A.M. Corridor Travel Speed, 
7. P.M. Corridor Travel Speed, 
8. A.M. Speed as Percent of Speed Limit, 
9. P.M. Speed as Percent of Speed Limit, 
10. P.M. Intersection Delay, 
11. P.M. Auto Occupancy, 
12. P.M. Truck Percentage, 
13. A.M. Transit Seat Capacity Used, 
14. P.M. Transit Seat Capacity Used, 
15. P.M. Transit Seats as Percent of Lane Capacity, 
16. A.M. Areas of Concern: Volume to Capacity Ratio, 
17. P.M. Areas of Concern: Volume to Capacity Ratio, 
18. A.M. Areas of Concern: Speed, and 
19. P.M. Areas of Concern: Speed.

Dale said the congestion monitoring report also highlights concerns at more specific locations. Using the individual CMS corridor segment data, areas of concern are identified. Areas of concern are defined as segments within an individual corridor with volume to capacity (V/C) ratio greater than 0.9 or a travel speed 60% or less of the posted speed limit. Dale reviewed the tables attached to the memorandum and highlighted the areas of concern cross-referenced with transportation solutions identified in existing transportation plans. Dale said the tables reference the location of the areas of concern by jurisdiction, peak hour traffic volume, and estimated completion of cross-referenced improvement. Dean Lookingbill asked RTAC members to look at the tables and let RTC staff know if there are changes. Matt Ransom, City of Vancouver, noted some changes. Phil Wuest, City of Vancouver, asked if there was a way to link the CMS program with VAST and Congestion Mitigation/Air Quality (CMAQ).

BILL WRIGHT, CLARK COUNTY, MADE THE MOTION FOR ENDORSEMENT OF THE CONGESTION MANAGEMENT REPORT AND TO FORWARD IT TO THE RTC BOARD OF DIRECTORS. MATT RANSOM, CITY OF VANCOUVER, SECONDED THE MOTION. IT WAS UNANIMOUSLY APPROVED.

IV. Amendment of MTIP Project Screening and Selection Criteria, Action

Dale Robins, RTC, said the Metropolitan Transportation Improvement Program (MTIP) identifies and prioritizes federally funded and regionally significant projects across all travel modes and Clark County jurisdictions. The MTIP includes a priority list of projects to be carried out in each of the next three years and a financial plan that demonstrates how it can be implemented. Dale said as part of the MTIP development process, RTC programs a set of regionally selected federal projects. Dale said the RTC Board of Directors adopted the overall MTIP development process in 1993. Although the overall MTIP process has remained the same, the screening and selection criteria have changed over the years and RTC staff has met with staff of local agencies over the past month to further refine the criteria. The goal is to build upon the MTIP process utilized in previous years that helps the region leverage competitive dollars; while encouraging projects that offer mobility, encourage economic development, and improve safety.

The member agency staff recommended that the project screening criteria remain the same except the maximum regional federal funding per project be lowered from $3 million to $2 million. Participants felt that with limited funding, a $2 million cap will allow additional projects to receive funding. The recommended project screening criteria would be amended as follows:

1. All projects must be consistent with the Metropolitan Transportation Plan (MTP) and Local Comprehensive Plans. Road projects that add additional capacity must be listed in the MTP. 
2. All projects must support the regional transportation system. Road projects must be federally classified as an urban collector/rural minor arterial or above to use STP-TMA funding. 
3. Projects competing for STP-Regional and/or CMAQ funds must be an improvement project. STP-Regional/CMAQ funds will not be used for maintenance. 
4. A maximum of $2 million of regional federal funds (STP-Regional/CMAQ per project. To exceed the $2 million maximum, a project would need approval by RTAC and the RTC Board of Directors. 
5. Submitted projects should be ready to proceed and have a reasonable timeline for implementation.

Dale said the member agency staff recommended that the selection criteria be amended to more closely align with selection criteria used by the Transportation Improvement Board (TIB). Dale pointed out, to the most part, the MTIP selection criteria remained very similar to those used in previous years. The range of selection criteria includes Mobility (20 pts.), Multimodal (15 pts.), Safety (20 pts.), Economic Development (20 pts), Financial/Implementation (15 pts), and Air Quality (10 pts.). Dale said for CMAQ projects, the same criteria would be used except that the air quality points will be multiplied by three.

Dale reviewed the “Needs Criteria”. Dale recommended a few changes to the criteria, including the following: 

1. Under Mobility/Truck Route add one point for routes with a truck percentage of 4% or greater. This will allow facilities with above average truck percentage to score a point as a truck route. 
2. Under Multimodal/Reduction of Single Occupant Vehicles change the points to a range of 1-2 points. This will provide two points for adding bike or pedestrian facilities to a corridor and one point for maintaining bike or pedestrian facilities in a corridor. 
3. Under Multimodal/CTR add one point if a project servers an employment center. This would provide a point for encouraging non-motorized transportation to an employment center with 50 or more employees without a CTR employer. 
4. Under Safety/Existing Conditions add a point for a corridor without center turn lane or turn pockets. Projects without turn lane or pockets can create a safety issue as vehicle stop in a travel late to make left turns. Project would need to correct this safety concern to receive a point. RTAC members concurred with Dale’s suggestions.

Committee members expressed some concern about the ability of a smaller city to compete for funding given the recommended criteria. No solution was suggested but RTAC members recommended that this concern should be expressed to the RTC board of Directors.

PHIL WUEST, CITY OF VANCOUVER, MADE A MOTION TO RECOMMEND TO THE RTC BOARD OF DIRECTORS THE ADOPTION OF THE REVISED MTIP PROJECT SCREENING AND SELECTION CRITERIA AS LISTED IN THE MEMORANDUM AND AS DISCUSSED AND CHANGED BY RTAC MEMBERS. BILL WRIGHT, CLARK COUNTY, SECONDED THE MOTION AND IT WAS UNANIMOUSLY APPROVED.

V. Vancouver Area Smart Trek: 2005/2006 Program Management, Action

Bob Hart, RTC, referred RTAC to the meeting packet Memo and noted a change on the last page in regard to the total budget for the 2005/2006 VAST Program. The total budget should be $174,000; $150,000 in federal CMAQ and $24,000 in local match.

Bob gave RTAC members an overview of the Vancouver Area Smart Trek program and said a memorandum of understanding (MOU) was signed and executed in May 2001 that formed the VAST Steering Committee made up of: RTC, the City of Vancouver, the Washington State Department of Transportation, Clark County, C-TRAN, the City of Camas, and the Oregon Department of Transportation.

Bob said with RTC Board support, a Communications Infrastructure MOU was executed in November 2004 that provided the framework to define the use, sharing, and maintenance of communications infrastructure for intelligent transportation system communications needs. The concept of an agreement for communications infrastructure was initiated by the Steering Committee in order to provide more structured rules between the agencies on how communications infrastructure is used, especially fiber which is shared among the agencies. The MOU also authorized the formation of the VAST Communications Infrastructure Committee (CIC).

Bob highlighted the VAST Advanced Traveler Information System and said the key issue to the development of a good traveler information system is the identification of a “host” or lead agency that will be responsible for the development and operation of the system. Bob pointed out that the host agency is responsible for pulling information from several sources, fusing the data, and packaging it for distribution to the public. Bob reviewed the key issues: 

1. WSDOT act as the host for improved traveler information. This adds to and builds upon WSDOT’s existing ATIS foundation. The WSDOT currently provides camera images and incident/construction notification on the state system within the southwest region and throughout the state. 
2. Expansion of WSDOT website to show the full Portland-Vancouver metro area and the main ODOT freeways (I-5 and I-205) and web camera images. 
3. Expansion of WSDOT website to show static information such as road construction, road/lane closures from local transportation agencies. 
4. Expansion of WSDOT website to include video images from City and County traffic cameras. 
5. Expansion of WSDOT website to show congestion flow map information on the freeways within the Vancouver urban area including the two Columbia River bridges and on the freeways within the Portland metro area.

Bob reviewed the Communications Maintenance Agreements for Fiber Assets and said the VAST CIC, made up of both transportation and information technology staff from the partner agencies, has cooperatively developed a template covering the use and maintenance of fiber assets to maximize communications resources and improve efficiency. The maintenance agreement template and supplemental worksheets for documenting shared fiber had been agreed to by the CIC. Internal agency and legal review is expected to occur this summer.

Bob highlighted the Fiber Asset Management – Shared Database and said the VAST CIC and the Steering Committee have also agreed on the development of a shared fiber asset management system database and mapping package. The software package OPSInSight, which uses a GIS ESRI platform and allows mapping and documentation of fiber and communications assets, will be procured. The shared database will be able to easily identify items such as fiber routes, types and attributes, including agency ownership, as well as fiber strands in-use and available. This shared database will allow better communications infrastructure documentation and asset management within individual agencies and more importantly for the VAST partners, it will facilitate better use of existing communications resources, minimizing duplication and maximizing the benefit of communications infrastructure investments. Bob reviewed the procurement of OSPInSight licenses for agencies and discussed the responsibility for future data entry costs to maintain the database and for annual maintenance and technical support costs of OSPInSight.

Bob reviewed the specific activities anticipated in 2005/2006 that include: 

1. Procurement of OSPInSight software for the VAST Agencies, 
2. Training of agency staff in the use of OSPInSight and a workshop to prepare for building the fiber asset database, 
3. Completion and execution of fiber sharing agreements, 
4. Review operational program and 20-year plan, 
5. Discussion and analysis of standards for fiber and other telecommunications equipment, 
6. Data archive development for the retrieval and transfer of information, transfer media, quality control, and aggregation of electronic and other data.

ED PICKERING, C-TRAN, MADE THE MOTION FOR THE RTC BOARD OF DIRECTORS TO SUPPORT THE REQUEST TO WSDOT FOR THE CMAQ FUNDS FOR THE 2005/2006 VAST PROGRAMS. JUSTIN CLARY, CITY OF RIDGEFIELD, SECONDED THE MOTION. IT WAS UNANIMOUSLY APPROVED.

VI. MTP Update: Status Report, Discussion

Lynda David, RTC, presented a status report on the MTP update. She said the purpose of the agenda item is to provide a progress report on Metropolitan Transportation Plan (MTP) update activities with emphasis on 

1. the designated regional transportation system, and 
2. development of the 2030 regional travel forecast model.

Lynda said the State Regional Transportation Planning Program Planning Standards requires that the designated MTP regional transportation system include: 

1. All state transportation facilities and services, 
2. All local freeways, expressways, and principal arterials, 
3. All high-capacity transit systems, 
4. All other transportation facilities and services, including airports, transit services and facilities, roadways, rail facilities, marine transportation facilities etc. that the RTPO considers necessary to complete the regional plan, and 
5. Any transportation facility or service that regional need or impact places in the plan, as determined by the RTPO. 

Attached to the memorandum was the existing, adopted MTP version of the “2023 Regional Transportation System.” Lynda asked RTAC members to let her know if they think changes should be made to add routes to the designated transportation system. Lynda said at a minimum, the map will need to be updated to reflect changes to C-TRAN’s fixed-route transit system. Dean pointed out when we are finished with updating this regional system; we want to make sure it is a regional system that everyone agrees upon.

Lynda noted that over the past few months, RTC staff has worked with local jurisdictions and agencies to provide an overview of various areas of Clark County at monthly Board meetings. The presentations have focused on connected land use, economic development and transportation issues. In February the Salmon Creek I-5/134th and 139th Street interchange project was highlighted, in March the focus was on the Vancouver City Center Vision Project, in April North County transportation issues were presented, in May the focus was on East County and in June will be on Central/East Vancouver transportation issues. Information and data provided in the MTP update will rely on information from these presentations as well as information from local Comprehensive Plans, Washington’s Transportation Plan and Highway System Plan as well as transportation system analysis from the regional travel forecast model.

Mark Harrington, RTC, said that a 2023 model run, based on the September 2004 adopted 2023 comprehensive growth management plan land uses, is complete and will be provided to local jurisdictions for Transportation Impact Fee program update. Mark said RTC staff is moving forward with the 2030 travel demand model. Make distributed a chart “2030 Land Use Forecast for MTP Update and 2030 Travel Demand Forecast” showing household, retail employment, and total employment data by UGA for years 2000, 2023 (adopted Comprehensive Plan) and 2030 (for MTP update). Mark also reviewed thematic maps showing the TAZ allocation of the 2023 to 2030 growth increment based on the percent of total county growth between 2023 and 2030. He highlighted maps showing households growth, employment growth and retail employment growth. Mark asked that RTAC members check the maps and notify RTC if there appear to be discrepancies.

Lynda reminded RTAC members that to be eligible for federal funding, capacity improvement projects must be listed in Appendix A of the MTP. Projects listed in Appendix A are included in the air quality conformity analysis.

Mark and Lynda reviewed some of the transportation network assumptions made in the first round of 2030 travel demand modeling for the MTP update. Mark said he needed some clarification on travel lanes to be assumed on 137th Avenue as it approaches Fourth Plain and on a potential interchange on Padden Parkway at Andresen, which is in close proximity to I-205. Lynda pointed out inconsistency between Ridgefield’s proposed widening of Pioneer Street (SR-501) that is not currently in a WSDOT plan.

Dean Lookingbill said results from the 2030 travel forecast model and further discussion on project assumptions would be presented at the June meeting.

VII. Other Business

A. RTAC Members

B. RTC Staff

Dean Lookingbill, RTC, said that jurisdictions should be thinking about applications for federal Transportation Enhancement funding. He said this region would have about $2 million in federal enhancement dollars. Dale said to call or e-mail him if there are questions about project eligibility etc. Project applications are likely due this summer.

The meeting was adjourned at 11:10 a.m. The next meeting will be Friday, June 17, 2005.

For More Information Contact:

Regional Transportation Council
1300 Franklin Street, Floor 4
Vancouver, Washington 98660

Tel: 360-397-6067
Fax: 360-397-6132
E-mail: info@rtc.wa.gov

Served by C-TRAN Route 3.
If you have special needs, please contact RTC.