Common use of Traffic Data and Projections Clause in Contracts

Traffic Data and Projections. The Engineer shall develop the opening-year, design-year (opening year +20) and pavement design year (opening year + 30) travel forecasts, and related traffic analysis in coordination with State Transportation and Programming Division (TPP). The developed traffic projections shall be utilized for design and environmental analysis. The Engineer shall develop traffic forecasts for the main lanes, ramps, cross streets, interchanges, intersections, and frontage roads for no-build and build alternatives. These projections shall include graphic representations of the anticipated daily movements along the corridor (suitable for inclusion in the design schematic and environmental document) and the Traffic Analysis for Highway Design table. The Engineer shall prepare a Traffic Projections Methodology memo, based on the information provided in the traffic analysis package. The Engineer shall review the proposed methodology with the State and shall refine it based on these discussions. Traffic volumes developed by the Engineer will be submitted to TPP for review and approval, and the Engineer will revise the traffic volumes based on TPP’s comments. DocuSign Envelope ID: 81680129-218F-4A62-86EE-68C3C135A630 i. Financial Plan and Project Management Plan The Engineer shall prepare a Financial Plan (FP) and Project Management Plan (PMP) in accordance with the most recent FHWA Financial Plan Guidance, for submission by the State to the FHWA Division Office for review and approval. The purpose of the FP is to document the project cost estimate and revenue structure and provide reasonable assurance that sufficient financial resources shall be available to implement and complete the project as planned. The FP shall cover topics such as the project cost estimate, revenue structure, funding resources, project implementation over time based on the available financial resources, and the cost and revenue assumptions used in development. a. The initial FP shall consist of at least five main sections including: ▪ Cost Estimate. ▪ Implementation Plan. ▪ Financing and Revenues. ▪ Cash Flow. ▪ Risk Identification and Mitigation Factors. b. The Engineer shall prepare for and attend a cost estimate review (CER) workshop with the State and the FHWA to develop and review information for inclusion in the FP such as cost estimation procedures and tools, identifying funding sources and revenues, and project implementation schedules. In preparation for the CER, the Engineer shall conduct a risk analysis assessment, provide cost spreadsheets and models for input into the FHWA’s probability modeling software, review and provide comments on the CER summary report, and update cost information in the initial FP to reflect confidence limits established during the CER. c. The Engineer shall provide annual updates (AUs) to the Initial FP reflecting changes in project finances and funding resources. Each update shall include revisions to the five main sections mentioned above as well as discussions of significant cost or revenue changes, comparisons to previous plan estimates, and explanations of mitigating actions taken to adjust for deviations. d. The Engineer shall submit the PMP, FP and FP AUs to the State for review and comment. For scoping purposes, it is assumed that the initial drafts of the FP and FP AUs shall be reviewed concurrently by the District, and the State’s Design and Finance Divisions. The Engineer shall address the State’s comments and prepare a revised draft for review by the FHWA. The Engineer shall address FHWA comments and prepare the DocuSign Envelope ID: 81680129-218F-4A62-86EE-68C3C135A630 final FP (up to three revision cycles from the State and FHWA) for the State to submit to the FHWA for approval. To document each revision cycle, the Engineer shall develop comment response forms that includes the comments, comment numbers, page and line numbers of draft where comments originated, page and line numbers where revisions can be located, and the responses.

Traffic Data and Projections. The Engineer shall develop the opening-year, design-year (opening year +20) and pavement design year (opening year + 30) travel forecasts, and related traffic analysis in coordination with State Transportation and Programming Division (TPP). The developed traffic projections shall be utilized for design and environmental analysis. The Engineer shall develop traffic forecasts for the main lanes, ramps, cross streets, interchanges, intersections, and frontage roads for no-build and build alternatives. . The Engineer shall collect ▇▇-▇▇▇▇ ▇▇-▇▇▇▇▇▇▇▇▇▇▇/▇▇▇ ▇▇▇ approach traffic volume counts as needed for turning movements at intersections. These projections shall include graphic representations of the anticipated daily movements along the corridor (suitable for DocuSign Envelope ID: 211A8780-3A56-4C71-A0A9-95EA90C5E646 inclusion in the design schematic and environmental document) and the Traffic Analysis for Highway Design table. The Engineer shall prepare a Traffic Projections Methodology memo, based on the information provided in the TPP traffic analysis package. The Engineer shall review the proposed methodology with the State and shall refine it based on these discussions. Traffic volumes developed by the Engineer will be submitted to TPP for review and approval, and the Engineer will revise the traffic volumes based on TPP’s comments. DocuSign Envelope ID: 81680129-218F-4A62-86EE-68C3C135A630 i. Financial Plan and Project Management Plan The Engineer shall prepare a Financial Plan (FP) perform traffic operational analyses for all mainlane, ramps and Project Management Plan (PMP) in accordance with frontage roads within the most recent FHWA Financial Plan Guidance, added project limits using the Highway Capacity Software and utilizing Synchro for submission by the State to the FHWA Division Office for review and approvalintersections. The purpose analysis will be performed for the future peak hour AM and PM no-build and one (1) build alternative for opening and design years. Capacity analysis will be used to determine future levels of the FP is to document the project cost estimate and revenue structure and provide reasonable assurance that sufficient financial resources shall be available to implement and complete the project as planned. The FP shall cover topics such as the project cost estimate, revenue structure, funding resources, project implementation over time based on the available financial resources, and the cost and revenue assumptions used in development. a. The initial FP shall consist of at least five main sections including: ▪ Cost Estimate. ▪ Implementation Plan. ▪ Financing and Revenues. ▪ Cash Flow. ▪ Risk Identification and Mitigation Factors. b. The Engineer shall prepare for and attend a cost estimate review (CER) workshop with the State and the FHWA to develop and review information for inclusion service in the FP such as cost estimation procedures no-build and tools, identifying funding sources and revenues, and project implementation schedules. In preparation for the CER, the Engineer shall conduct a risk analysis assessment, provide cost spreadsheets and models for input into the FHWA’s probability modeling software, review and provide comments on the CER summary report, and update cost information in the initial FP to reflect confidence limits established during the CER. c. The Engineer shall provide annual updates one (AUs1) to the Initial FP reflecting changes in project finances and funding resources. Each update shall include revisions to the five main sections mentioned above as well as discussions of significant cost or revenue changes, comparisons to previous plan estimates, and explanations of mitigating actions taken to adjust for deviations. d. The Engineer shall submit the PMP, FP and FP AUs to the State for review and comment. For scoping purposes, it is assumed that the initial drafts of the FP and FP AUs shall be reviewed concurrently by the District, and the State’s Design and Finance Divisionsbuild alternative networks. The Engineer shall address the State’s comments develop recommendations from operational analyses and prepare a revised draft for review by the FHWA. The Engineer shall address FHWA comments and prepare the DocuSign Envelope ID: 81680129-218F-4A62-86EE-68C3C135A630 final FP (up to three revision cycles from the State and FHWA) incorporate them into one technical memorandum for the State to submit to project. It is assumed that there will be one round of comments which will result in a Draft and Final Report. Traffic analysis technical memorandum will include the FHWA for approval. To document each revision cycle, following sections:  Introduction  Methodology  Traffic Analysis  Turn Bay Recommendations at the Engineer shall develop comment response forms that includes the comments, comment numbers, page added intersections  Summary of Conclusions and line numbers of draft where comments originated, page and line numbers where revisions can be located, and the responses.Recommendations

Traffic Data and Projections. The Engineer shall develop the opening-year, design-year (opening year +20) and pavement design year (opening year + 30) travel forecasts, and related traffic analysis in coordination with State Transportation and Programming Division (TPP). The developed traffic projections shall be utilized for design and environmental analysis. The Engineer shall develop traffic forecasts for the main lanes, ramps, cross streets, interchanges, intersections, and frontage roads for no-build and build alternatives. . The Engineer shall collect ▇▇-▇▇▇▇ ▇▇-▇▇▇▇▇▇▇▇▇▇▇/▇▇▇ ▇▇▇ approach traffic volume counts as needed for turning movements at intersections. These projections shall include graphic representations of the anticipated daily movements along the corridor (suitable for inclusion in the design schematic and environmental document) and the Traffic Analysis for Highway Design table. The Engineer shall prepare a Traffic Projections Methodology memo, based on the information provided in the TPP traffic analysis package. The Engineer shall review the proposed methodology with the State and shall refine it based on these discussions. Traffic volumes developed by the Engineer will be submitted to TPP for review and approval, and the Engineer will revise the traffic volumes based on TPP’s comments. The Engineer shall perform traffic operational analyses for all mainlane, ramps and frontage roads within the added project limits using the Highway Capacity Software and utilizing Synchro for the intersections. The analysis will be performed for the future peak hour AM and PM no-build and one (1) build alternative for opening and design years. Capacity analysis will be used to determine future levels of service in the no-build and one (1) build alternative networks. DocuSign Envelope ID: 816801298B0EE02C-218F-4A62E455-86EE-68C3C135A630 i. Financial Plan and Project Management Plan 423C-9476-3FA4EBD98809 The Engineer shall prepare a Financial Plan (FP) develop recommendations from operational analyses and Project Management Plan (PMP) in accordance with the most recent FHWA Financial Plan Guidance, for submission by the State to the FHWA Division Office for review and approval. The purpose of the FP is to document the project cost estimate and revenue structure and provide reasonable assurance that sufficient financial resources shall be available to implement and complete the project as planned. The FP shall cover topics such as the project cost estimate, revenue structure, funding resources, project implementation over time based on the available financial resources, and the cost and revenue assumptions used in development. a. The initial FP shall consist of at least five main sections including: ▪ Cost Estimate. ▪ Implementation Plan. ▪ Financing and Revenues. ▪ Cash Flow. ▪ Risk Identification and Mitigation Factors. b. The Engineer shall prepare for and attend a cost estimate review (CER) workshop with the State and the FHWA to develop and review information for inclusion in the FP such as cost estimation procedures and tools, identifying funding sources and revenues, and project implementation schedules. In preparation incorporate them into one technical memorandum for the CER, the Engineer shall conduct a risk analysis assessment, provide cost spreadsheets and models for input into the FHWA’s probability modeling software, review and provide comments on the CER summary report, and update cost information in the initial FP to reflect confidence limits established during the CER. c. The Engineer shall provide annual updates (AUs) to the Initial FP reflecting changes in project finances and funding resourcesproject. Each update shall include revisions to the five main sections mentioned above as well as discussions of significant cost or revenue changes, comparisons to previous plan estimates, and explanations of mitigating actions taken to adjust for deviations. d. The Engineer shall submit the PMP, FP and FP AUs to the State for review and comment. For scoping purposes, it It is assumed that there will be one round of comments which will result in a Draft and Final Report. Traffic analysis technical memorandum will include the initial drafts of following sections: a) Introduction b) Methodology c) Traffic Analysis d) Turn Bay Recommendations at the FP and FP AUs shall be reviewed concurrently by the District, and the State’s Design and Finance Divisions. The Engineer shall address the State’s comments and prepare a revised draft for review by the FHWA. The Engineer shall address FHWA comments and prepare the DocuSign Envelope ID: 81680129-218F-4A62-86EE-68C3C135A630 final FP (up to three revision cycles from the State and FHWA) for the State to submit to the FHWA for approval. To document each revision cycle, the Engineer shall develop comment response forms that includes the comments, comment numbers, page and line numbers of draft where comments originated, page and line numbers where revisions can be located, and the responses.added intersections