CONGESTION MANAGEMENT PROCESS UPDATE & STATUS

Transcription

1 CONGESTION MANAGEMENT PROCESS UPDATE & STATUS OF THE SYSTEM REPORT Anchorage Bowl & Chugiak-Eagle River Project Management Plan prepared for Municipality of Anchorage prepared by with Solstice Alaska Consulting, Inc. Parsons Brinckerhoff September

2

3 Table of Contents 1.0 Introduction Work Tasks Task 1 Project Management and Administration...3 Objective...3 Approach Task 2 Project Public Involvement Plan (PIP) and Implementation...6 Objective...6 Approach Task 3 Congestion Management Process Update and Data Management Plan, CMP Implementation Plan, and CMP Maintenance Plan...7 Objective...7 Approach Task 4 Status of the System Report 2014 with Web-Based Dashboard...13 Objective...13 Approach Deliverables and Labor Effort Milestones Deliverables Effort Project Plan Schedule Assumptions Constraints Project Organization Project Team Organization Responsibilities and Communication Risk Identification and Mitigation Quality Assurance Plan and Quality Control Policy...24 i

4

5 List of Tables Table 1.1 The Four Dimensions of Congestion...2 Table 3.1 Project Milestones...14 Table 3.2 Key Deliverable Dates...15 Table 3.3 Hours Allocation...18 Table 3.4 Apportion of Financial Resources...19 Table 4.1 Project Schedule...20 Table 5.1 Contact Information for CS Management Team...23 iii

6

7 1.0 Introduction All metropolitan areas with populations greater than 200,000 residents, known as Transportation Management Areas (TMA), are required by the Moving Ahead for Progress in the 21st Century (MAP 21) Act to develop a Congestion Management Process (CMP). The Federal Highway Administration (FHWA) defines the CMP as a systematic and regionally accepted approach for managing congestion that provides accurate, up-to-date information on transportation system performance and assesses alternative strategies for congestion management that meet state and local needs. The CMP is intended to move these congestion management strategies into the funding and implementation stages. In addition, elements of the CMP, such as performance measures and project priorities, also are intended to link or integrate directly with the goals, objectives, and overall development of an agency s Regional Transportation Plan (RTP) and support ongoing planning activities. The Anchorage Metropolitan Area Transportation System (AMATS, part of the Community Development Department at the Municipality of Anchorage) developed its most recent CMP (as part of the 2035 Metropolitan Transportation Plan (MTP) for the Anchorage Bowl) to meet the unique needs of the Anchorage metropolitan area. The CS team will update the CMP to address not only congestion management needs of the region that have emerged since its last update, but also develop consistent methods to support the region s 2014 Status of the System Report as well as to ensure MAP 21 compliance. In addition, the CS team will ensure direct linkages (performance measures, project evaluations and priorities, data collection needs, etc.) of the CMP/Status of the System (SOS) Update to various ongoing efforts underway in the region, including the MTP, Transportation Improvement Program (TIP), and the concurrent Anchorage Regional ITS Architecture Update. AMATS CMP included ongoing methods to provide information on the performance of the transportation system and on alternative strategies that best manage congestion and enhance mobility. Our intent is to provide AMATS with an updated CMP that uses an objectives and data-driven, performance-based approach to managing congestion, which emphasizes effective management of existing facilities through use of travel demand and operational management strategies that also addresses related congestion relief, transit ridership reductions, mobility, preservation, economic growth, health, and safety goals of both the CMP and MTP. Critically, the CS team recommends that the CMP Update be closely coordinated and linked to the concepts developed in the Anchorage Regional ITS Architecture Plan between these two closely related plans. We suggest that not only the technical elements of each study be closely linked to ensure this consistency required by the AMATS in their overall planning process, but to also link the public participation processes of each to better maximize the agency s resources. This linkage will also reduce the potential burden to participating stakeholders to consolidate workshops and meetings which reduces the need for multiple meetings and agendas for participating stakeholders. To be effective, the CMP must follow the eight processing steps defined by the FHWA in the Congestion Management Process: A Guidebook, and be integrated with the planning process through its data and analysis functions, as well as through associated analytical tools. The CS 1

8 team will leverage and be consistent with the information already prepared by the AMATS in their planning process (MTP, latest Status of the System Report in 2010, etc.) to help update the CMP with integrated planning processes, performance measures, technical tools, and partner agency stakeholder input. Where strategies have not yet been defined or implemented in previous plans, the CS team will work with the AMATS stakeholders and the ITS Architecture Update team to define strategies that depend on other data sources and local knowledge. This collaborative process will help us paint a picture of the exact dimensions of congestion in different parts of the Anchorage region and frequent causes of congestion, and therefore address the highest priority types of strategies (Table 1.1). Table 1.1 The Four Dimensions of Congestion Spatial. How much of the system is congested? The image presents an example of a metropolitan highway network with 20 percent of all miles congested. Temporal. How long does congestion last? The image presents an example of a metropolitan highway network with congestion from 6:00 a.m. through 10:00 a.m. Severity. How much delay is there or how low are travel speeds? The image shows that for the same percentage of miles congested, the number of vehicles and total hours of vehicular delay can be different. Variability. How does congestion change from day to day? The image shows how the severity and location of congestion can change from day to day. More variation in travel time indicates less reliable travel. A reliable system would have consistent levels of congestion from hour to hour and day to day. We envision that when the CMP Update and Status of the System Report are completed, they will be MAP-21 compliant, and provide AMATS with integrated tools, measures, and projects that support the current MTP and Anchorage Regional ITS Architecture Plan Update among other ongoing planning of the agency. This Project Management Plan (PMP) presents our work plan for the project and establishes protocols for management, organization, coordination, and communication procedures between 2

9 the CS team, its designated Project Manager, and AMATS/MOA and agency stakeholders. The remainder of the PMP is organized as follows: Section 2: Work Tasks Section 3: Deliverables and Labor Effort Section 4: Project Plan Section 5: Project Organization 2.0 Work Tasks 2.1 Task 1 Project Management and Administration Objective Through a designated Contractor Project Team, the Cambridge Systematics team (CS team), and Contract Project Manager, to effectively coordinate and manage work tasks, public and stakeholder outreach, technical analysis and deliverables, and critical path (milestone) activities to maintain the project schedule, ensure successful project coordination, communication, and completion with ongoing Municipality of Anchorage (AMATS) activities such as the Metropolitan Transportation Plan (MTP) and Intelligent Transportation Systems (ITS) Architecture Plan Update, and to meet MAP 21 requirements. Approach We will prepare a PMP to establish protocols for management, organization, coordination, and communication procedures between the CS team, its designated Project Manager, and AMATS/MOA and agency stakeholders. The CS team will use the PMP to present and define progress reporting and invoicing methods and schedules; project controls, budget, and schedule adherence; management processes with our subconsultants and AMATS; quality assurance and control program; and coordination internally as well as with the AMATS Project Team. We will finalize the PMP within one month of contracting. This document will guide our project management process and all ongoing management activities for the 12-month schedule of the CMP Update. Our subtasks and associated work steps are presented below. Subtask 1.1 Project Team and Project Manager The CS team and Project Manager will work with the AMATS to establish the protocols to manage the CMP Update. We will work with the AMATS to establish the participants and schedule for the AMATS Project Team (consisting of the CS team Project Manager, AMATS Project Manager, and selected AMATS and Alaska Department of Transportation (DOT) and Public Facilities (DOT&PF) staff), which will be the primary group responsible for managing the 3

10 technical direction of the update. We will use this process to communicate with the AMATS Project Team about schedule, quality assurance and control, milestone delivery adherence, and technical oversight. Work elements for this Subtask will include the following: Project Team and Weekly Teleconferences. We will conduct weekly status meetings with AMATS Project Team to provide status updates for the project related to budget, schedule, and other issues. Each meeting will be up to 30 minutes in length if needed. One day in advance of each meeting, we will agendas, material, and other topics for each discussion to AMATS for approval. We will provide summary s of each meeting to the AMATS Project Team Project Team Meeting. The CS team will conduct an initial organizational (kickoff) meeting at the start of the project to outline the specific technical tasks, communication protocols, and milestone schedule of the project We also will conduct subsequent monthly meetings with the AMATS Project Team to coordinate project activities. As with the weekly meetings, we will provide agendas and associated presentation materials to the AMATS Project Team two days prior to each meeting for review, revision, and approval. We anticipate our initial kickoff meeting will be in-person and up to four hours in length at the start of the project. Subsequent monthly meetings, each up to two hours, will be held both by telephone and in-person, throughout the project. Subtask 1.2 Project Technical Team We will work with the AMATS Project Team to create a Project Technical Team consisting of agency stakeholder staff, including staff from various regional, local, and state agencies involved in transportation planning and policy in the Anchorage region, as well as standing committee members from various AMATS and AMATS groups (e.g., AMATS Freight and Bicycle and Pedestrian Advisory Committees, among many others identified in AMATS RFP). The goal of this process is to engage with agency stakeholder on the development of the CMP and to ensure that all interested agencies interests are both understood and integrated into the congestion management process Project Technical Team Meetings. The CS team will work with the AMATS Project Team to identify a meeting schedule (we suggest every other month) to coordinate project activities with this larger body of agency stakeholders. As with the monthly Project Team Meetings, we will provide agendas and associated presentation materials to the AMATS Project Manager two days prior to each meeting for review, revision, and approval. Within two days of each meeting, we will provide a summary of the meetings by . We anticipate that these meetings, each up two hours, will be held both by telephone and in-person over the course of the project. The meetings will coincide with the Project Team Meetings, with both happening on the same days so project resources can be better managed. Subtask 1.3 Project Administration Requirements As part of the PMP developed earlier, we will work with the AMATS project manager to prepare and finalize the project administration requirements for the project including monthly progress 4

11 report and web site formats; work plan schedule; deliverable formats and requirements; and GIS mapping and data requirements to be used for the CMP Update. Each work element is presented below Project Schedule and Records Maintenance. The CS team and CS Project Manager will maintain the project schedule and manage and maintain the project record of activities for the CMP Update. As we suggested above, the PMP will contain the process for which we will manage the administrative record for this project, including all project schedule and maintenance activities. A review of the schedule will be conducted on a monthly basis, or more frequently if required. Any deviations or future risks to schedule adherence will be documented in a log similar to that shown in Table A-1 (p. 5-22). Corrective actions will be identified in the log along with a timeframe and resolution will be noted when achieved. This record will be maintained throughout the project Monthly Progress Reports. We will prepare monthly progress reports and invoices for AMATS review and approval by the fifth of each month. Progress reports will be formatted per AMATS requirements, and outline completed and ongoing work performed and percentages completed by Task; outline expected work to be conducted the next month; identify problems encountered; and provide corrective solutions to meet those problems. If needed, updated schedules will be provided after consultation with AMATS Contractor Project Web Site/AMATS Project Web Site. The CS team will work with the AMATS to define protocols and processes for storing and displaying CMP Update information both locally and on the AMATS web site. We will use existing AMATS processes for posting information on their web sites for the MTP Update and other planning processes, including defining deliverable formats (PDF, Microsoft Word, other), schedules, and reference materials Project Work Plan and Task Schedule. As stated previously, through our development of the PMP, we will outline the specific work plan by task, budget, and deliverable schedule for the project, and present this to the AMATS Project Team. This will include meeting schedules, and schedules for posting web site documents and other material. We also will prepare a quality assurance/quality control (QA/QC) process as a critical component of the PMP and project. We will employ our QA/QC process throughout the schedule including an database to track communication with AMATS and our subconsultants. We will keep AMATS abreast of the status of all tasks/subtasks, including issues and revisions to the technical procedures and deliverables as dictated through the QA/QC process Deliverables Requirements. The CS team will adhere to all AMATS and AMATS protocols and processes for document preparation and delivery. We will submit each draft deliverable to the AMATS Project team for review, comment, and finalization. Upon receipt of comments from AMATS Project Team members, we will finalize each deliverable. We will provide all final deliverables on five Compact Disks (CD) using Microsoft Word (2003 compatible) and PDF versions adhering to all AMATS processes. We will adhere to AMATS information technology/geographic information systems (IT/GIS) Standards from 2008 to submit all GIS-based technical information as well. 5

12 Deliverable. Draft and Final PMP, including summaries of all subtasks/ work elements above (see Tasks 2, 3, and 4 for specific deliverables). 2.2 Task 2 Project Public Involvement Plan (PIP) and Implementation Objective To work with AMATS to prepare and implement a PIP and provide associated materials and presentations, and provide on-line interviews and questionnaires to gather input from agency stakeholders specifically established for the CMP Update, and to provide specific CMP materials and deliverables that support AMATS ongoing public involvement process for the current MTP Update. Approach The CS team will work with the AMATS Project Team to define and implement an appropriate PIP for the CMP Update. We envision the PIP for the CMP will primarily be a process to engage the region s agency stakeholders, and not to directly engage the general public in our process. Rather, we recommend working with AMATS staff and the consultant currently updating the MTP to provide specific CMP material as part of the MTP PIP. We recommend this strategy and process because it will provide the AMATS with a common process for engaging the public, thus reducing the confusion that could result from having multiple public outreach underway at one time, while maximizing general public participation in the planning process. The CS team, specifically CS and Solstice, will work with the AMATS to design and implement this process as presented below. Subtask 2.1 Develop and Implement an Approved PIP As stated above, the PIP for the CMP Update will be focused on agency stakeholders input, primarily from the Project Technical Team and key regional agency stakeholders. We will convene up to six meetings at key project milestones (e.g., define CMP objectives, document best practices, etc.) to gather critical input and insights from these stakeholders which, once established in Task 1, should include a comprehensive representation of all stakeholder agencies and standing committees in the region responsible for multimodal (road, bike, pedestrian, transit), ITS and operations, freight, and overall MTP planning and policy in the region. Meetings will occur early in the process (defining CMP Objectives) and continue throughout the project schedule to ensure that the stakeholders inputs are fully integrated into the planning process. We will work with AMATS to establish the agendas, presentation materials, on-line surveys and interview guides, and other materials for these meetings and this PIP process. We will work with the AMATS Project Team, as the primary advisory group for the CMP, to identify all standing committees and stakeholder interests to participate in the process and finalize the PIP for implementation. We will follow the communication protocols as shown in Subtask 1.2 Project Technical Team for submitting and presenting information during these meetings. We also will work with the AMATS and its MTP Team to develop 6

13 specific CMP materials for use in their PIP, specifically for general public review, input, and discussion. As part of this process, the CS team will prepare material to the specifications of the MTP Team for public meetings and be prepared to help assist with and attend MTP PIP meetings as necessary. It is assumed that AMATS will notify the CS team of MTP public meeting dates at least one month prior to the meeting. Subtask 2.2 Public Involvement Plan Elements Per the process identified above, we will work with the AMATS to prepare specific meeting agendas and material to obtain as much input as possible from agency stakeholders comprising the Project Technical Team established in Task 1. PIP elements will include at least six meetings held throughout the course of the schedule to engage and obtain direct inputs from AMATS stakeholders in all aspects of the CMP Update. Three of the AMATS meetings will take place in person, and three will be held via teleconference/webinar. We recommend implementing at least two stakeholder on-line surveys to solicit input to support the development of Task 3 CMP elements related to 1) CMP objectives, network characteristics, and supportable performance measures; and 2) critical regional bottlenecks and congestion issues, preliminary congestion analysis, and assessment of multimodal project strategies to mitigate congestion. We will use the meetings to present results of these surveys and to identify progress in addressing and developing all of the eight elements of the CMP in Task 3, and also the Status of the System Report in Task 4. We will work with AMATS to establish the agendas, presentation materials, on-line surveys and interview guides, and other materials for the AMATS meetings, as well as lead the presentation. The last element envisioned for this process will be a plan to identify, format, and display congestion related topics as part of the MTP s PIP, including ways in which the CS team and AMATS Project team will engage the general public in understanding congestion issues in the region. Deliverable. Draft and Final Public Involvement Plan. 2.3 Task 3 Congestion Management Process Update and Data Management Plan, CMP Implementation Plan, and CMP Maintenance Plan Objective Update the CMP for the Anchorage region using the Federal Highway Administration s (FHWA) eight elements for congestion management planning to be MAP 21 compliant, and to support ongoing CMP Implementation and Maintenance activities as well as to develop and maintain consistency and linkages with ongoing MTP, Transportation Improvement Program (TIP), and ITS Architecture Plan activities. 7

14 Approach Our analysis, conducted in this task, will form the foundation for the CMP Update, including defining the specific CMP requirements of meeting the AMATS MTP update needs, MAP 21 requirements, and FHWA s Congestion Management Process: A Guidebook (FHWA CMP Guidebook). We will use our team s expertise in developing a broad array of regional CMPs, bringing to bear best CMP practices that can provide the AMATS with value to support to development of the CMP. We will follow the eight processing steps of the FHWA CMP Guidebook to update the CMP as well as focus on our detailed understanding of the process, analytical tools, and specific elements of AMATS previous CMP. This will ensure that the CS team and AMATS Project Team will not reinvent the entire congestion management process, but rather take and use the most appropriate elements of this previous work. In addition, understanding the region s latest CMP developed as part of the 2035 MTP and how elements can be built into the update will be important goals. We also will assess how this information will be built into the AMATS CMP implementation and management plans, and subsequent Status of the System Report for The specific Subtasks to be conducted in Task 3 are presented below. Subtask 3.1 Follow FHWA 8-Step Process for a Performance-Based, Objectives- Driven Approach In Subtask.1, we outline the specific work elements and technical reports of the CMP update the CMP, following the specific eight steps outlined by FHWA Develop Regional Objectives for Congestion Management. Using the FHWA CMP Guidelines and best practices we have compiled from other regions as our guide, we will work with the AMATS Project Team to identify the regional objectives of the CMP. Understanding the AMATS intended path, goals, policies, and objectives to complete the MTP Update, ongoing travel modeling and data collection activities, AMATS previous CMP efforts (e.g., 1994 Congestion Management Program), as well as understanding the perspectives of agency stakeholders will all be important factors to define these objectives. These factors will lead to smart objectives that are realistic (e.g., implementable and fundable), specific to the Anchorage region (e.g., locally meaningful and relevant), agreed upon by agency stakeholders, and achievable over different time periods. The FHWA CMP Guidebook and MAP 21 provide flexibility in how regions define their objectives for congestion management, and we will work with AMATS and its stakeholders to define the objectives, link them to performance measures and expected outcomes (e.g., single-occupant auto reductions, transit ridership increases), and link CMP projects and programs to the MTP Update currently underway that work best for the region. Deliverable. Draft and Final Technical Report 1.0: CMP Objectives and Goals Define the CMP Area and Network. We will review the existing CMP network, define, and implement a new multimodal CMP network for the Anchorage region consistent with the latest MTP. We will perform a thorough review and analysis of the existing CMP network that consists of principal (major) arterials and above in urban areas and selected 8

15 minor arterials and above in rural areas, including all freeways, major arterials, and many other roadways within the metropolitan area. We will review the network to verify that transit routes, bicycle and pedestrian systems, and planned improvements to these systems within the region are adequately represented in the CMP network. The CS team will draw on our experience from our previous work with the AMATS to ensure that freight routes are represented in the CMP. In addition, we will identify areas experiencing significant growth, and incorporate needed additions to the existing CMP network. Deliverable. Draft and Final Technical Report 2.0: CMP Area and Network Summary Develop Multimodal Performance Measures. Performance measures will be identified to address the goals and objectives defined earlier and be applied in the CMP to understand congestion problems, assess potential solutions, and evaluate implemented strategies for all travel modes and operations strategies. We will develop a short list of measures for the CMP based on best practices, adopted measures used by the AMATS in various efforts, and (currently under development) MTP Update. Equally important, measures such as reliability, that address operations and ITS strategies and assess the variability in congestion due to nonrecurring events, and other congestion reducing strategies such as improving accessibility, will be introduced and assessed in this process. We will define a larger set of potential measures by a variety of factors (easily understood measures, supported by available data and models, provide consistency with other planning processes and provide a recognizable measure and comparison of congestion) to help inform AMATS and its agency stakeholders about the applicability of the measures. We then will work with AMATS and the AMATS Project Team to identify a recommended, short list of measures for the CMP, keeping the total number of measures to a small yet meaningful set of indicators. Deliverable. Draft and Final Technical Report 3.0: CMP Multimodal Performance Measures Monitor System Performance/Data Management Plan. Closely coordinated with identified performance measures and performance monitoring standards and protocols, the CS team will compile a list of potential data types and sources for consideration in the CMP. We will review previous and emerging data types that support the CMP performance measures, evaluations, as well as the region s ongoing MTP and ITS Architecture planning processes. The CS team will work closely AMATS to develop a matrix representing the data with embedded evaluation and weighting criteria to assess and rank each data type. Using this matrix, we will identify data gaps and desired data collection to support the CMP Update, MTP, and other regional planning efforts. In addition, once each item is evaluated and ranked, we will present recommendations to AMATS for consideration into the CMP Update. We also will use this matrix to support corridor analysis as part of the Status of the System Report to help identify bottleneck locations in the region; review and update processes for sharing information with stakeholder agencies and the public; and identifying options for improving data collection to support system monitoring. We will support AMATS with our extensive experience in using traditional data (e.g., traffic volumes, delay) as well as newer data (e.g., travel time reliability) and data sources (e.g., INRIX and AirSage) to support CMPs. We also have used these data sources for a variety of other analyses including carbon footprint evaluations, data management using GIS, tracking major land use developments and growth, system crashes, 9

16 and non-recurring congestion, among others. Following the recommendation and adoption of data for the CMP Update, we will develop monitoring standards and protocols for the adopted data and supporting performance measures. This will include being as consistent as possible with prior CMP monitoring and/or developing standards/protocols that allow comparative evaluation between prior and new CMP data. Deliverable. Draft and Final Technical Report 4.0: Data Management Plan Analyze Congestion Problems and Needs. We will review existing AMATS CMP analysis techniques and potential alternative and/or new techniques for application based on best practices, available data, and existing methods of analysis. We will use Level of Service as the primary measure of congestion, to evaluate roadways such as freeways and principle arterials, freight and passenger oriented corridors, intersections, and other known bottlenecks. We also recommend using Level of Mobility (LOM) measures to determine the State of Congestion within the region, including designations at four levels (based on volume-tocapacity ratios), which include Tolerable, Moderate, Serious, and Severe. We will use the recommended procedures to identify congestion problems and bottlenecks throughout the region, and by corridor, subarea, project, and other locational levels acceptable to AMATS. In this work element, we also will identify analysis tools for potential application with the Anchorage regional travel demand model and available and new sketch planning tools (e.g., Travel Time Index, IDAS, and U.S. EPA COMMUTER Models that CS developed) to test the effectiveness of selected strategies. These tools will be applied to help us outline the system s deficiencies and needs as well as help us identify and assess potential congestion mitigation strategies in work element Deliverable. Draft and Final Technical Report 5.0: Congestion Problems and Needs Identify, Evaluate, and Select Strategies. Once the supporting data are collected and analyzed (3.1.4) and the regional congestion problems, bottlenecks, and needs are assessed (3.1.5), we will identify the types of projects and strategies that best mitigate congestion in the Anchorage region. The primary project sources will be based on AMATS reports (1994 CMP, 2035 MTP CMP process, TIP, others) in addition to defining specific new projects that meet congestion needs. Obviously, the strategies we identify and assess also will comply with the CMP objectives defined earlier by AMATS and its stakeholders in work element We will only define projects, actions and programs, and/or strategies that best meet the unique characteristics and needs of the Anchorage region s transportation land use and system, and that can be achieved and implemented. We also will take into account previous AMATS CMP strategies and prepare a refined list of programs, actions, and projects by several categories of multimodal projects and solutions (e.g., TDM category with telecommuting, alternative work schedules, operations, non-recurring congestion, safety, transit marketing). We will test the analysis procedures of project strategies to relieve congestion for two corridors as specified by the AMATS, Glenn Highway and Northern Lights Boulevard. Strategies will consist of individual strategies and combinations of strategies to assess effectiveness. We will report the results of the pilot using a matrix presenting project costs and potential congestion relief gains. Also, as part of work element 3.1.5, we will work with AMATS to recommend sketch planning models and tools that provide state-of-the practice analysis capabilities to this 10

17 planning process. The best practices results, previous AMATS CMPs, and stakeholder input will be used to refine the categories (TDM, pricing, operations, transit, road capacity, fleet, land use, others) and list of strategies within each category. We then will use available regional travel demand model and available and new sketch planning tools (e.g., TTI, IDAS and U.S. EPA COMMUTER Models) to test the effectiveness of selected strategies. Deliverable. Draft and Final Technical Report 6.0: Selected Strategies Program Selected Strategies/CMP Implementation Plan. After we identify and assess the projects, actions and programs, and strategies that best mitigate congestion for the pilots and region, we will work with AMATS to define how to implement and program these projects as part of the CMP Update. We will map each to how they best mitigate congestion in the region, by the three levels of analysis recommended in the FHWA CMP Guidebook regional, corridor, and project levels. For example, a TDM Program can be targeted for all three levels and can be defined to meet the needs of all three levels; and the COMMUTER Model can be used to assess TDM programs at all three levels. An Operations Program could be focused on all three levels as well, but may be more suited for corridor and intersection specific mitigation strategies. In this process, we will review Anchorage s single occupancy vehicle checklist to identify projects that add capacity to the region s network and work with the AMATS to thoroughly identify other potential multimodal alternatives to roadway capacity that may reduce congestion and emissions and recommend ways to better track congestion management projects for incorporation into the SOV checklist and TIP process. Through this process, we also will develop a flow-chart defining the steps and schedules for integrating CMP projects into the various AMATS/AMATS planning processes and documentation, including iterative feedback processes. We will work with AMATS and its partners to define the projects, actions and programs, and strategies and associated funding strategies and levels, processes to incorporate the findings into the overall region s planning process, and develop a process to track project process, including the design of before and after evaluation studies for each of the three levels, which will form the basis of congestion mitigation projects for the CMP Update. We also will link these projects to the ongoing MTP and ITS Architecture Update processes while working with AMATS as well. Deliverable. Draft and Final Technical Report 7.0: CMP Implementation Plan Evaluate Strategy Effectiveness. The data obtained in earlier work elements will be used to illustrate the location, duration, and extent of congestion for the region at baseline conditions, and forecasted with the financially constrained projects being evaluated by AMATS in the MTP Update. Regional travel demand model outputs will be used (along with other sketch planning analysis tools defined in earlier work elements) to calculate performance measures and evaluate the congestion impacts, and identify potential benefits by the specific region, subregion, corridor, and project levels required by AMATS in its current MTP Plan process. We will use actual measured data on changes in travel time, speed, mode share, or trip reduction, for example, to directly measure or indirectly measure the CMP performance measures for the no-build and build conditions. We will evaluate the impacts of selected individual strategies and test up to two combined, overall strategies that include the best performing individual projects. We will allocate benefits by subregion to help explain to 11

18 stakeholders the nature of the distribution of benefits and identify a process for the AMATS to conduct periodic assessments (including before and after study processes defined in work element 3.1.7) of projects to test their ongoing effectiveness and viability for congestion mitigation. For example, though a CMP strategy might be implemented on a particular roadway in one community, the benefactors may in fact be those traveling on parallel roadways who reside in other communities. Deliverable. Draft and Final Technical Report 8.0: Strategy Effectiveness Refine System Performance Monitoring/Data Management Plan. Through an iterative process with the CS team, the AMATS, and the AMATS Project Team, we will refine various Subtask 3.1 work elements as necessary to create as meaningful a CMP as possible for the region. In particular, we will revisit and potentially refine, as necessary, the performance measures and data management plans, as well as other work elements related to supporting the CMP Update process. (Potential) Deliverable. Revised Technical Reports 3.0: CMP Multimodal Performance Measures and 4.0: Data Management Plan. Subtask 3.2 Maintenance Plan The maintenance plan will include our thorough review of the various Federal and regional reports, recommendations, and guidance pertaining to AMATS CMP development and staffing needs for ongoing use. As part of this process, we will outline the specific recommendations from the AMATS Project Team, map and document the CMP Update s compliance to MAP 21 requirements, and provide a thorough understanding of how the CMP Update meets regional planning needs with the MTP Update, TIP, ITS Architecture Plans, and other regional studies. We also will define specific AMATS roles in maintaining and managing the CMP, how the CMP should be used in regional transportation planning and policy. Deliverable. Draft and Final Technical Report 9.0: CMP Maintenance Plan. Subtask 3.3 Final CMP Update Deliverables We have created a new Subtask presenting the final deliverables of the CMP Update. We will use all nine of the draft and final technical reports conducted in this Task to prepare the final CMP, with each report representing a chapter or section of the Final CMP. We will provide three hard copies of the Final CMP and one electronic copy each of the PDF and Microsoft Word versions of the Final CMP. 12

19 2.4 Task 4 Status of the System Report 2014 with Web- Based Dashboard Objective To update the Status of the System Report to represent 2014 conditions and present updated multimodal system results as well as specific congestion related material prepared in Task 3, using a user-friendly web-based dashboard for display and access to the system s traveling public. Approach The SOS Report, last updated in 2010, presents a snapshot of transportation conditions, including congestion hot spots and bottlenecks, for the Anchorage Bowl and Chugiak-Eagle River region. The CS team will update the SOS Report 2014 to, at a minimum, compliment the CMP Update, ongoing MTP update, and concurrent ITS Architecture Plan with current multimodal transportation conditions, expected trends in localized (routes, intersections) and system wide congestion bottlenecks and issues, and assessments of the effectiveness of previous congestion mitigation strategies and/or projects. We also will develop a new dashboard, designed specifically to display meaningful and easy to understand statistics representing multimodal transportation conditions and congestion statistics for the region. Subtask 4.1 Status of the System Report 2014 CS developed the AMATS first SOS including the implementation of procedures to collect travel times for specific corridors designed to monitor and assess congestion over time. We will work with the AMATS to design a travel time collection program, potentially using available real-time information and a combination of manual and real-time surveys, to assess specific corridors to compare travel times to 2010 conditions. We will focus this data collection on selected primary corridors of interest to the AMATS. We also will prepare, report, and display multimodal travel statistics for the region that consider transit ridership, roadway level of services, pedestrian and bicycle usage, freight and interregional connections, crashes, emissions, and other transport performance metrics using user-friendly and meaningful maps, displays, and figures. We will use the AMATS format for the previous SOS Reports to maintain consistency with congestion reporting for the region. Subtask 4.2 Web-Based Dashboard The CS team will work with the AMATS to develop and present a web-based dashboard representing the transportation system conditions in the Anchorage region. We have developed

20 a variety of dash-board s for agencies to meet their specific needs for congestion management, long-range transportation, performance system monitoring, and performance evaluations, and will tailor the dashboard that best meets the AMATS needs. We anticipate that dashboard reports and graphics will be developed in consultation with AMATS and implemented for those that have source data in available and usable format. Capability to add reports in the future will be incorporated. Figure 3.2 presents an example dashboard we prepared for the Virginia DOT that is available to the public for their access and review and shows how well the DOT is performing in the following areas: construction; maintenance; engineering; finances; safety; operations; and environment. We will help the AMATS define the transportation system statistics that best represent conditions in the region for integration with the dashboard, and implement it through the AMATS web site. Deliverable. Draft and Final Status of the System Report 2014 and Web-based Dashboard. We will provide three hard copies of the Final Report and Dashboard, and one electronic copy each of the PDF and Microsoft Word versions of the Final Report and Dashboard. The dashboard will be interactive in that it will allow users to select reports from a pre-specified list that will be developed during this task. 3.0 Deliverables and Labor Effort 3.1 Milestones This project will be driven by the following key project milestones. Table 3.1 Project Milestones Milestone Title Associated Task Milestone Date Kickoff Meeting Task 1 July 24, 2014 Final CMP Update Report Task 3 Feb. 27, 2015 Draft Status of the System Report 2014 Task 4 April 9, 2015 Web-Based Dashboard Task 4 June 30, Deliverables The following table of deliverables will be maintained throughout the duration of the project and will be submitted to AMATS on a monthly basis as part of our project progress reports. 14

21 Table 3.2 Key Deliverable Dates Task Deliverable Task Dependency 1. Project Management & Administration Project Kick-off Meeting Notice to Proceed Due Date Date Submitted July 24, 2014 July 24, 2014 Status Complete Weekly Status Meetings with AMATS Project Team (up to 30 minutes each) N/A Weekly To be scheduled Monthly Project Coordination Meetings with AMATS Project Team (11 meetings, up to 2 hours each) Project Technical Team Meetings (5 meetings) *In person N/A October 9, 2014 November 6, 2014 December 4, 2014* January 8, 2015 February 12, 2015* March 12, 2015 April 9, 2015* May 14, 2015 June 11, 2015 N/A Oct. 9, 2014 Dec. 4, 2014* Feb. 12, 2015* April 9, 2015* June 11, 2015 To be scheduled Monthly Progress Reports N/A Monthly by the fifth of each month 15

22 Task Deliverable Task Dependency Due Date Date Submitted Status Draft/Final Project Management Plan Project Kickoff Meeting Draft - August 11, Draft - August 11, Final September 10, Project Public Draft/Final Public Project Kickoff Draft Draft Involvement Plan (PIP) & Involvement Plan Meeting August 12, 2014 August 12, 2014 Implementation Final September 10, 2014 One-page handout for use in MTP PIP N/A TBD Public comment sheet for use in MTP PIP N/A TBD Attend 2 MTP public meetings N/A TBD Draft/Final Online Survey Tool #1 N/A Draft Sept. 8, 2014 Draft Sept. 8, 2014 Final Sept. 17, 2014 Conduct Online Survey #1 Online Survey Tool #1 Sept , 2014 Draft/Final Online Survey Tool #2 N/A Draft Oct. 6, 2014 Final Oct. 17, 2014 Conduct Online Online Survey Oct , Survey #2 Tool # CMP Update, Draft/Final Tech. Conduct Online Draft Oct. Implementation, & Maintenance Report 1.0: CMP Objectives and Goals Survey #1 3, 2014 Final Oct. 17, 2014 Draft/Final Tech. N/A Draft Oct. Report 2.0: CMP Area and Network Summary 17, 2014 Final Dec. 12,

23 Task Deliverable Task Dependency Due Date Date Submitted Status Draft/Final Tech. Report 3.0: CMP CMP Objectives and Goals Draft Oct. 31, 2014 Multimodal Performance Measures Final Dec. 12, 2014 Draft/Final Tech. Report 4.0: Data Management Plan Draft/Final Tech. Report 5.0: Congestion Problems & Needs Draft/Final Tech. Report 6.0: Selected Strategies Draft/Final Tech. Report 7.0: CMP Implementation Plan CMP Multimodal Performance Measures Data Management Plan Congestion Problems & Needs Selected Strategies Draft Nov. 14, 2014 Final Dec. 12, 2014 Draft Nov. 26, 2014 Final Dec. 12, 2014 Draft Dec. 12, 2014 Final Feb. 27, 2015 Draft Jan. 2, 2015 Final Feb. 27, 2015 Draft/Final Tech. Report 8.0: Strategy Effectiveness CMP Implementation Plan Draft Jan. 30, 2015 Final Feb. 27, 2015 Draft/Final Tech. Report 9.0: CMP Strategy Effectiveness Draft Feb. 13, 2015 Maintenance Plan Final Feb. 27, 2015 Final CMP Update Report CMP Maintenance Plan Final Feb. 27, Status of the System Report Draft/Final Status of the System Report Congestion Problems & Draft April 9, with Web- Based Dashboard 2014 Needs Final June 30,

24 Task Deliverable Task Dependency Due Date Date Submitted Status Web-Based Dashboard Status of the System Report Final June 30, Effort We anticipate that completion of the project will require an estimated 462 man-hours, for a total contract amount of $79,968. Table 3.3 shows the share of hours by staff. Table 3.4 shows how the financial resources will be apportioned amongst staff, by task and firm, as a percent of the total proposed budget. Table 3.3 Hours Allocation Task 1 Task 2 Task 3 Task 4 Total Hours Total Percent of Project Hours Dan Krechmer, Project Manager % Dena Snyder, Deputy Project Manager % Tazeen Mahtab, Web-Based Software % Analyst % Production % Total % Parsons Brinckerhoff Les Jacobson, Supervisor % Erin Ehlinger, Engineer % Mary Chiu, Engineer % Total % Solstice Alaska Consulting, Inc. Carla SlatonBarker % Total % TOTAL HOURS % 18

25 Table 3.4 Apportion of Financial Resources Task 1 Task 2 Task 3 Task 4 Total Cost Total Percent of Project Cost $7,415 $10,308 $19,301 $24,998 $62,022 78% Parsons Brinckerhoff - - $6,236 - $6,236 8% Solstice Alaska Consulting, Inc. - $4, $4,320 5% Other Direct Costs $95 $2,520 $4,695 $80 $7,390 9% TOTAL COST $7,510 $17,148 $30,232 $25,078 $79, % 4.0 Project Plan 4.1 Schedule The period of performance for this project is 12 months, with the project starting on July 3, The Phase I CMP Update will be completed by February 27, 2015 (8 months), and the Phase II Status of the System Report will start on February 3, 2015 and be completed by June 30, 2015 (5 months). The schedule of deliverables is provided in Table 3.2 above. This project will be driven by the milestones indicated in this plan (Table 3.1). Missing these key milestones will impact the overall project schedule. 19

26 Table 4.1 Project Schedule 4.2 Assumptions The project assumptions are as follows: For most deliverables, it is assumed that AMATS/AMATS staff will provide review comments within one (1) week of receiving deliverables. Final versions of deliverables will be provided within one (1) week of receiving AMATS/AMATS review comments. For the online survey tools, it is assumed that AMATS/AMATS staff will provide review comments within three (3) working days, after which the online survey tools will be finalized. It is assumed that AMATS staff or their MTP consultant will handle all meeting logistics for the MTP PIP public meetings, as well as facilitate the meetings and present CMP update related content. The CS Team will provide support by attending two (2) public outreach meetings and soliciting and documenting public comments regarding the CMP update. The online survey will be conducted for a five (5) day period. The CS Team will follow up with non-responders via phone call and after three (3) days to encourage them to respond. The results of Subtasks and online survey #1 will be presented at the October 9, 2014 meeting of the AMATS Technical Advisory Committee. The deliverables for these tasks will be finalized within one week of the meeting. 20

27 The results of Subtasks and online survey #2 will be presented at the December 4, 2014 meeting of the AMATS Technical Advisory Committee. The deliverables for these tasks will be finalized within one week of the meeting. The results of Subtasks will be presented at the February 12, 2015 meeting of the AMATS Technical Advisory Committee. The Final CMP will be finalized within two weeks of the meeting. The results of Subtask 4.1 will be presented at the April 9, 2015 meeting of the AMATS Technical Advisory Committee. The results of Subtask 4.2 will be presented at the June 11, 2015 meeting of the AMATS Technical Advisory Committee. 4.3 Constraints The constraints for the project are as follows: We assume the budget is fixed for the work that is currently planned. The Phase I CMP Update must be completed by February 27, The Phase II Status of the System Report and Web-Based Dashboard must be completed by June 30, Project Organization 5.1 Project Team Organization Cambridge Systematics will be prime consultant responsible for the day-to-day management and technical activities of the project. CS will lead all project tasks. Parsons Brinckerhoff will support all project tasks related to ITS and Operations strategies and analysis, ensuring a strong link to the ITS Architecture Update. Solstice Alaska Consulting, Inc. will support the public involvement activities for this effort. Dan Krechmer, a Principal of CS and our proposed Project Manager, will provide day-to-day management and technical oversight for the entire effort and lead Tasks 1, 2, and 4. Dena Snyder, an Associate of CS, is our proposed Deputy Project Manager. Ms. Snyder will be responsible for leading Task 3 CMP Update, and supporting all other project tasks. This management team will be supported by key CS and subconsultant staff. Tazeen Mahtab, a Software Engineer with CS, will develop the CMP and Status of the System Report dashboard as part of Task 4. Les Jacobson of PB will provide senior technical advice to the team, while Erin Ehlinger of PB will support the ITS and Operations technical analysis in Task 3. Carla SlatonBarker of Solstice will support the public participation planning process in Task 2. The 21