Exhibit A Scope of Work and Deliverables

Transcription

1 xxxx General Statement of Scope of Work 4 General Information and Requirements 4 Background 4 Draft Schedule & Contract Completion Timeline 4 Source Type Codes and P6 Activity Codes 4 Standards 5 Items provided by State 5 Plain Language and Accessibility Standards 5 Plain Language 5 Accessibility Standards 5 Page 1 of 31 Tasks 6 1 Project Management, Coordination, and Meetings (Source Type Code 1010) Schedule (P6 Activity OPM1000 Perform Ongoing Project Management) Monthly Progress Meetings (P6 Activity OPM1000 Perform Ongoing Project Management) Project Instructions and Quality Assurance (P6 Activity OPM1000 Perform Ongoing Project Management) Subcontractor Management and Oversight (P6 Activity OPM1000 Perform Ongoing Project Management) Risk Analysis and Tracking (P6 Activity OPM1000 Perform Ongoing Project Management) 7 2 Public Involvement Plan (PIP) (Source Type Code 0054) Initial PIP Deliverables PIP Deliverables Project Analysis (P6 Activity PIP1000) Stakeholder Identification (P6 Activity PIP1010) Conflict Identification (P6 Activity PIP1020) Conflict Mapping (P6 Activity PIP1030) Conflict Assessment (P6 Activity PIP1040) Public Involvement Strategy (P6 Activity PIP1050) 9 3 Request Scoping Input (Source Type Code 1003) (P6 Activity FDB1000) 9 4 Preliminary Environmental Investigation (Source Type Code 1071) Early Notification Memo (P6 Activity ENM1000) Identify Section 4(f) (P6 Activity SFF0900) Determine Level of Air Quality Analysis (P6 Activity AIR1000) Determine Level of Noise Analysis (P6 Activity NOI1000) Identify Section 6(f) (P6 Activity SSF0900) Identify Environmental Justice Issues for Alternatives (No P6 EAW 1020) Contamination Database Review (Part of RFR1002) Develop Draft Purpose and Need Statement (P6 Activity AAA1110) 12 5 Alternatives Evaluation (Source Type Code 1071) Draft Project Alternatives Report (P6 Activity PMM1020) Logical Termini Report (P6 Activity AAA1030) Benefit-Cost Analysis for Alternative Screening (P6 Activity AAA1300) Alternatives Evaluation (P6 Activity AAA1050) Alternatives Evaluation Presentation to Project Team (P6 Activity AAA1050) 15 6 Preliminary Traffic Studies (Source Type Code 1016) Traffic Counts (P6 Activity TFC1000) Prepare Traffic Forecasts and ESALs (P6 Activity TRF1000) Existing Traffic Conditions Report (P6 Activity TFM1000 & TFM1010) Traffic Operations Analyses (P6 Activity TFM 1020, TFM 1030, TFM 1040 and TFM 1050) Alternative Evaluation Modeling (P6 Activity TFM 1040) Travel Demand Forecasts for Alternative Evaluation VISSIM Analysis for Alternative Evaluation 18

2 6.4.2 Travel Demand Forecasts (P6 Activity TFM 1020) Travel Demand Modeling and Forecast Report Sensitivity Analysis on Travel Demand Modeling VISSIM Modeling and Analysis for No-Build and Preferred Alternative (P6 Activity TFM 1050) Building of Base Model Opening Year No-Build Alternative Traffic Analysis Horizon Year No-Build Alternative Traffic Analysis Opening Year Build Alternative Traffic Analysis Horizon Year Build Alternative Traffic Analysis Sensitivity Analysis on VISSIM Modeling 20 7 Preliminary Transportation Management Plan (TMP) (Source Type Code 1254) Define Staging Alternatives TMP (P6 Activity MTM1000) 21 8 Geometric Layouts (Source Type Code 1140) Draft Preliminary Geometric Layout Alternatives (P6 Activity LAY1030) Submit Survey Request (P6 Activity Code SUR1000) 22 9 Drainage Overview Map (Source Type Code 1141) Initial Drainage Overview Map for Alternatives Evaluation (P6 Activity AAA1200) Identify Floodplain Impacts for Alternatives (P6 Activity AAA1200) Cost Estimates (Source Type Code 1003) Draft Preliminary LWD Estimates (P6 Activity AAA1040) Final Preliminary LWD Estimates (P6 Activity AAA1045) Bridge Evaluation (Source Type Code 1003) Bridge Evaluation of Alternatives Accelerated Bridge Construction (ABC) Alternatives Evaluation Cross Sections and Construction Limits of Alternatives (Source Type Code 1200) (P6 Activities LIM1000 & LIM1010) Value Engineering (Source Type Code 1068) (P6 Activity VEA 1010 & VEA1020) 26 Future work to be included in future amendments 26 Public Involvement Plan (Source Type Code 0054) 26 Initial Design Project Baseline (Source Type Code 1003) 27 Design Memorandum (Source Type Code 1150) 27 Visual Quality Manual (Source Type Code 1071) 27 Regulatory File Review (Source Type Code 1071) 28 Noise Analysis (Source Type Code 1071) 28 Air Quality Analysis (Source Type Code 1071) 28 Section 6(f) (Source Type Code 1071) 29 Section 4(f) (Source Type Code 1071) 29 Environmental Document (Source Type Code 1071) 29 Traffic Studies (Source Type Code 1016) 29 Mainline Staging Alternatives Modeling 29 Local Traffic Mitigation 29 Transportation Management Plan (TMP) (Source Type Code 1254) 30 Layouts (Source Type Code 1140) 30 Preliminary Geometric Layout & Profile (P6 Activity LAY1040) 30 Staff Approved Layout 30 Right of Way Construction Limits (Source Type Code 1200) 30 Municipal Consent (Source Type Code 1140) 30 Hydraulics Design (Source Type Code 1141) 31 ADA Recommendations (Source Type Code 1250) 31 Bridge Scoping and Structure Determination (Source Type Code 1003) 31 Page 2 of 31

3 Geotechnical Investigation (Source Type Code 1190) 31 Inspection and Cleaning of Stormwater Features (Source Type Code 1141) 31 THE REMAINDER OF THIS PAGE HAS BEEN INTENTIONALLY LEFT BLANK Page 3 of 31

4 General Statement of Scope of Work Assist State in the development of a Non-Programmatic Categorical Exclusion with a preferred alternative, including but not limited to public involvement and outreach, alternatives analysis, cost estimates, traffic operational analysis, Traffic Management Plan (TMP), preliminary drainage overview map, construction limits, staff approved layout and right of way (R/W) acquisition report. General Information and Requirements Background This Project is located on US-10 from approximately 0.2 miles west of Bridge 9713 (TH 169/TH 47/Ferry Street over US 10) to Bridge 9717 (US 10 over BNSF Railroad) for a total length of about 1 mile in Anoka. The purpose of this contract is to conduct the necessary scoping and project development to facilitate a 2022 start of construction. The current RPs are from to The State has identified the need to complete the replacement of Bridge 9700 (US 10 over Rum River). The Rum River is designated a Wild and Scenic River. In addition, there are several other bridges in the project limits that would require evaluation. It expected that Bridge 9714 (Mississippi River Regional Trail over US 10) and Bridge 9715 (4th Avenue over US 10) will require reconstruction if either the US 10 profile increases or the proposed auxiliary lanes, eastbound and westbound from Ferry Street to 7th Avenue, are included in the final layout. It is expected that the replacement of Bridge 9714 and 9715 would only require one replacement structure. Construction on Bridge 9716 (US 10 over 7th Avenue) and Bridge 9717 will be held to maintenance only, with a maintenance scope provided by the State. The State recently completed a study of the TH 169/TH 47/Ferry Street Interchange (FSI) with US 10 with the goal of evaluating feasibility of possible improvements at this interchange. The results of that contract will be used to provide direction for this contract. Out of that study, a Single Point Urban Interchange (SPUI) was selected to be advanced for submission of Regional Solicitation funding. While that study pointed towards a SPUI as the current best alternative for potential addressing congestion and geometric issues at FSI, ultimate detail design and funding limitations might point towards a different solution. The City of Anoka (City) is pursuing corridor improvements on US 10 west of this Project. The proposed City improvements include grade separation of Thurston Ave and Fairoak Ave with US 10 among other improvements to the corridor. Independently, the State programmed the replacement of Bridge 9700 (US 10 over Rum River). The proximity of the City and State projects in both location and construction year, as well as the impactful nature of those projects on traffic has encouraged the State to evaluate other improvements needed in this corridor that could be included in the State project. Draft Schedule & Contract Completion Timeline State will provide a draft P6 schedule. The tasks in this scope of work match the activities in that schedule. The Late Finish dates for the activities in that schedule are the due dates for the tasks in this scope of work once agreed upon with the Contractor. The overall project goal is to have a project letting by September Some activities in the draft P6 schedule provided by the State are placeholders in the schedule and will require input from the Contractor on how they will be linked within the schedule and their proposed original durations. These activities can be identified by an original duration of 7 Days. Additionally, Contractor will need to evaluate the entire schedule for accuracy and feasibility for project delivery and provide corrections where needed. Hitting the proposed letting date should be considered a primary goal, but moving the letting date back would be considered if warranted by schedule. Source Type Codes and P6 Activity Codes Every deliverable will list a Source Type Code and a P6 Activity Code. The Source Type Code is used in the consultant contract budget and invoice to subtotal the deliverables together under that source type code. Page 4 of 31

5 The P6 Activity code matches the P6 activity in the P6 schedule. The Contractor can use this code to understand the due dates for that deliverable in the schedule, and how the activity relates to other activities in the schedule. The overall goal is to get the Contractor deliverables and cost estimate for the Contract proposal to match the format and organization of the P6 schedule as much as possible. The Contractor is not required to know how to use Primavera P6 or work within the program itself. The Contractor is expected to understand the concept of Critical Path Method scheduling, be able to understand hard copy reports printed by the P6 schedule, update the hardcopy reports using a pencil, and recommending changes to the schedule to reflect changes in the scope or flow of work. Standards Comply with all State, Federal, and local standards, laws and regulations related to the scope of work and project area. Work must comply with the latest edition or revision of that standard in effect on the Proposal Due Date, including any amendments in effect on that date, unless otherwise specified in the Contract or otherwise directed by State. Items provided by State Draft P6 project schedule. State Metro District s LWD cost estimate template and guidance for usage Available planimetric mapping, TIN model, right of way and utility information, using the following datums: o Vertical datum: NAVD 88 o Horizontal datum: NAD 1986 (1996 HARN adj) TH 10/47/169 (Ferry Street) Interchange Evaluation & Funding Study Summary Report TH 47 and BNSF Railway Overpass Feasibility Study Final Report: o Limited Phase 1 Environmental Site Assessment for TH 47 near BNSF Incomplete scoping report including initial scoping responses from Metro functional groups. US 10 and I-94 Travel Shed Evaluation PDFs Plain Language and Accessibility Standards Plain Language Provide all documents or exhibits specifically designed to be used by the public in Plain Language. Technical documents, presentations, spreadsheets, and drawings used by technical staff do not need to be in plain language. Executive Order requires the Office of the Governor and all Executive Branch agencies to communicate with Minnesotans using Plain Language. As defined in Executive Order 14-07, Plain Language is a communication which an audience can understand the first time they read or hear it. Additional information can be read at this website: To achieve that, the successful responder will take the following steps in the deliverables: Use language commonly understood by the public; Write in short and complete sentences; Present information in a format that is easy-to-find and easy-to-understand; and Clearly state directions and deadlines to the audience. Accessibility Standards Comply with the State of Minnesota s Accessibility Standard ( ) for all documents or exhibits specifically designed to be used by the public. Technical documents, presentations, spreadsheets, and drawings used by technical staff do not need to be in plain language. The State of Minnesota s Accessibility Standards entail, in part, the Web Content Accessibility Guidelines (WCAG) 2.0 (Level AA) and Section 508 of the Rehabilitation Act, as amended. Additional requirements can be found at this website: and include: Page 5 of 31

6 Providing interpreters, translators or other special accommodations, Providing documents in an alternative format, Following the PDF accessibility guidance. Compliance with the State of Minnesota s Accessibility Standard includes, but is not limited to, the specific requirements as follows: All videos must include closed captions, audio descriptions and a link to a complete transcript; All documents, presentations, spreadsheets, drawings, and other material must be provided in an accessible format. In addition, provide native files in an editable format. Acceptable formats include InDesign, Word and Excel; and All materials intended for downloading and printing such as promotional brochures, must be labeled as such and the content must additionally be provided in an accessible format. Tasks 1 Project Management, Coordination, and Meetings (Source Type Code 1010) This task focuses on effective communication and coordination of the contract work to expedite the decision-making process and maintain the scheduled completion dates. The project manager s team will also be responsible to transferring/saving electronic files/deliverables to State s ProjectWise system prior to requesting State s review of said task/deliverable. 1.1 Schedule (P6 Activity OPM1000 Perform Ongoing Project Management) Modify the draft P6 schedule supplied by State by analyzing the work required to complete this project, evaluating each Work Package s duration and networking to create a schedule that will accomplish the September 24, 2021 letting date. Create and actively maintain a detailed schedule, using the State s Enterprise Project Management System (EPMS) Primavera P6 software, herein referred to as P6. Update the schedule monthly in time for the monthly invoicing and progress meetings and at other times deemed necessary to allow the use of the schedule as an effective management tool. At a minimum the schedule will include durations and due dates for all deliverables listed in this scope of work. Deliverable: One electronic schedule to be updated monthly. Twelve updates. Format: All files submitted electronically. State s Enterprise Project Management System (EPMS) Primavera P6 software. Monthly reports must be in Adobe Acrobat (pdf extension). Due: The first revised schedule is due within 40 business days of Notice to Proceed with monthly updates on progress. Standard: Critical Path Method (CPM). State s Enterprise Project Management System (EPMS) Primavera P6 software. State Review: Five business days. Contractor Update: Five business days. 1.2 Monthly Progress Meetings (P6 Activity OPM1000 Perform Ongoing Project Management) Contractor s Project Manager will meet with State s Project Manager once per month to review the monthly progress and invoices. Contractor s Project Manager will solicit feedback from State s Project Manager to assess whether all services meet or exceed the requirements of the project. If needed, Contractor will direct changes to personnel and/or procedures to correct identified deficiencies and implement opportunities for improvements. Deliverable: Twelve informal meetings to review invoices and progress. Format: All files submitted electronically. Meeting may be in person, teleconference, or web conference. Send to State s Project Manager at completion of meeting documenting that meeting occurred per work order requirements. Due: Monthly at the same time as the invoices. Standard: Meeting minutes are not required. Page 6 of 31

7 State Review: During the meeting. Contractor Update: Update invoices within 5 business days. 1.3 Project Instructions and Quality Assurance (P6 Activity OPM1000 Perform Ongoing Project Management) Develop tools (Project Instructions, Work Plans, and a Quality Assurance Plan) to establish budgets, roles, and responsibilities for the project team members throughout the project. Provide project oversight, leadership to the project team, and facilitate team meetings. Perform Quality Assurance/Quality Control (QA/QC) functions throughout the project duration to ensure delivery of a quality product. Develop resource utilization tool to indicate "burn rate" to aid in budget management. Deliverable: Electronic copies of project instructions, work plans, and quality assurance plan for the Work Order Contract. Format: Microsoft Word 2013 document (docx extension) and Adobe PDF. Standard: None. Schedule: Within 15 business days from notice to proceed. State Review: 5 business days. Final submittal: 5 business days after State review. 1.4 Subcontractor Management and Oversight (P6 Activity OPM1000 Perform Ongoing Project Management) Manage, coordinate, direct, and monitor subcontractor services. This includes review of progress reports, deliverables, schedule and invoices. Deliverable: Twelve monthly invoices, progress reports and deliverables. Format: As stated within this contract for specific items. Standard: As stated within this contract for specific items. Schedule: Throughout contract. State Review: Monthly Final submittal: 5 business days after State review. 1.5 Risk Analysis and Tracking (P6 Activity OPM1000 Perform Ongoing Project Management) Develop a project risk register to track large cost and schedule risks in the project. Deliverable: Electronic copy of risk register maintained regularly throughout project Format: Microsoft Excel 2013 spreadsheet, using MnDOT Risk Register Template Standard: As stated within this work order contract for specific items. Schedule: Throughout contract. State Review: Quarterly Final submittal: 5 business days after State review. 2 Public Involvement Plan (PIP) (Source Type Code 0054) Develop and implement the Public Involvement Plan (PIP). PIP consists of nine steps: 1) Project Analysis 2) Stakeholder Identification 3) Conflict Identification 4) Mapping 5) Assessment, 6) Strategy 7) Implementation and Management Page 7 of 31

8 8) Resolution, Review, and Regeneration 9) Post-Project Analysis Establish ongoing project coordination with all stakeholders including, but not limited to: State State s Project Manager State Functional Groups FHWA Metropolitan Council Metro Transit Department of Natural Resources Anoka County City of Anoka Other Governmental Agencies Private and Public Utilities Separate SUE Contractor working for State Other agencies as required Assumptions: This work will deliver the first 6 PIP steps, listed above, and finish with the first PIP Strategy. One or more amendments will be written to deliver PIP steps 7 to 9, which are the implementation and completion of the PIP. Municipal Consent activities will follow State's Highway Project Development Process (HPDP) manual, Municipal Consent section. Assumes Municipal Consent is needed from Anoka. Up to eight PIP Project Management Team (PMT) meetings (one PMT meeting per month). PMT members to include State employees only. Each meeting is 1 hour not including travel. One PIP work session with MnDOT staff only. Assume a 4 hour meeting not including travel. One PIP work session with MnDOT, City of Anoka, Anoka County, Metropolitan Council, and Metro Transit. Assume a 4 hour meeting not including travel. Create a Strategic Advisory Group (SAG) to review goals, objectives, alternatives, and receive executive input. Meet with the SAG monthly seven times. Assume each meeting is 1.5 hours long not including travel. The exact membership of the SAG is not precisely known at this time. Assume the SAG will be made up of key State Staff, FHWA staff, Metropolitan Council, Metropolitan Transit, City staff, County staff and MnDNR as a minimum. Additional members may be neighborhood representatives, and other representatives of key organizations, e.g. trucking, biking, cultural, etc. Up to four Technical Advisory Committee (TAC) meetings. Assume the TAC is mainly to go over the traffic modeling. Membership will be MnDOT staff, FHWA, Metropolitan Council, City of Anoka and Anoka County. Other stakeholders may need to be added. Up to 4 hours per meeting including travel. Two public information meetings as part of Public Involvement Plan (open house format). Each meeting is 3 hours long not including travel. 2.1 Initial PIP Deliverables Deliverable: Eight PMT meetings. One PIP work session with MnDOT staff only. One PIP work session with key stakeholders. Seven SAG meetings. Four TAC meetings. Two public information meetings. Format: Meetings. Create hardcopy exhibits as needed. Create agendas and minutes of meetings. All files submitted electronically in Microsoft Word 2013 document (docx extension). Complete package in Adobe Acrobat (pdf extension) and pdf should be created by using Adobe Acrobat to convert the source file to a pdf whenever possible with the use of scanned pages minimized if not eliminate with the exception of actual signature pages. Standard: Coordinate with State to determine standard State Review: 7 calendar days. Page 8 of 31

9 Contractor Update: 7 calendar days. 2.2 PIP Deliverables Project Analysis (P6 Activity PIP1000) Thorough project research will be conducted and scaled to the size of the project or policy. The Project Goals Statement will be formalized. Deliverable: Document explaining all the project goals from major goals to minor goals Stakeholder Identification (P6 Activity PIP1010) Internal and external stakeholders will be identified, including agencies, elected and appointed officials, advocacy groups, businesses and adjacent property owners/tenants. Includes creating the membership to the PMT, SAG, and TAC. Deliverable: Document identifying all stakeholders. Create membership document of PMT, SAG and TAC. Sample stakeholder template is included in Items Provided by State Conflict Identification (P6 Activity PIP1020) Existing and potential issues will be identified related to the identified stakeholders.. Deliverable: Document identifying all conflicts Conflict Mapping (P6 Activity PIP1030) An influence/interest grid of stakeholders will be produced. Relationships between stakeholders will be mapped, including alliances, relationships with friction, broken relationships, relationships that don t exist and relationships that need to exist. Power imbalances and triggering events which may create issues will be indicated. Deliverable: Influence/interest grid document Conflict Assessment (P6 Activity PIP1040) Conflicts will be reviewed for likelihood of occurring, risk to the project for time, scope and budget, and risk to the agency s reputation. Deliverable: Assessment document that explains risk of each conflict Public Involvement Strategy (P6 Activity PIP1050) Possible options for resolution will be generated by the team with a focus on identifying impacts, outcomes, strategies and planned responses. The Contractor will develop practices that may be used to ensure the opportunity for involvement for all individuals and/or groups within the project area. Deliverable: Strategy document. Format: All files submitted electronically. Report written in Microsoft Word 2013 document (docx extension). May use Microsoft Excel 2013 (xlsx extension). Complete package in Adobe Acrobat (pdf extension) and pdf should be created by using Adobe Acrobat to convert the source file to a pdf whenever possible with the use of scanned pages minimized if not eliminate with the exception of actual signature pages. Due: To be determined upon completion of the schedule. See State s sample schedule for intent. Standard: As determined during Project Analysis State Review: 7 calendar days. Contractor Update: 7 calendar days. 3 Request Scoping Input (Source Type Code 1003) (P6 Activity FDB1000) Begin the process to complete the Metro District Scoping Report. Coordinate with the MnDOT Functional Areas to request scoping input. Provide a response to all scoping worksheet questions. The response will either state that the Page 9 of 31

10 question has be evaluated and there are no needs associated with this project, or state that there is a problem or need that requires further investigation. Worksheets included in the Metro District Scoping Report are: Bridge Contamination Investigation Design Environmental Engineering Maintenance Materials Pedestrians and Bicycles Planning Project Management Regional Traffic Management Center (RTMC) Right of Way State Aid Surveys Team Transit Traffic Engineering Utilities Water Resources Engineering Deliverable: Respond to all scoping worksheet questions identifying needs that require further investigation. Format: Metro Scoping Database. Standard: Metro Scoping Database. State and FHWA Review: Along with the Metro Scoping Report. Contractor Update: Along with the Metro Scoping Report 4 Preliminary Environmental Investigation (Source Type Code 1071) The activities in this section have been identified as critical to completion of the Alternatives Evaluation. 4.1 Early Notification Memo (P6 Activity ENM1000) The Early Notification Memo for this project will be distributed by State. The Contractor will need to meet with the MnDOT Metro District Project Documentation group to discuss the content of the ENM and responses received. Deliverable: Meet with MnDOT Functional Group Format: This information received from the ENM responses will be compiled into the Preliminary Environmental Investigation to aid in alternative review. Standard: MnDOT Highway Project Development Process (HPDP) State Review: 5 days Contractor Update: 1 day 4.2 Identify Section 4(f) (P6 Activity SFF0900) The proposed project has trails and park land adjacent to State right-of-way in the project area. Work with FHWA to identify Section 4(f) properties. Map the 4(f) properties and document the potential impacts to them, such as showing potential construction limits within the properties with area of impact measured. Section 4(f) resources in the project area include a recreational river (Rum River), and local trails. A public golf course is located just west/northwest of the project area. Deliverable: Map of known 4(f) properties adjacent to the project with documentation on potential impacts. Format: All files submitted electronically. Report written in Microsoft Word 2013 document (docx extension). Complete package in Adobe Acrobat (pdf extension) and pdf should be created by using Adobe Acrobat to Page 10 of 31

11 convert the source file to a pdf whenever possible with the use of scanned pages minimized if not eliminate with the exception of actual signature pages. Standard: EA standards referenced herein. State and FHWA Review: Along with the Metro Scoping Report. Contractor Update: Along with the Metro Scoping Report 4.3 Determine Level of Air Quality Analysis (P6 Activity AIR1000) Determine if the threshold for a federal quantitative air quality analysis is crossed with the 20-year traffic forecast. Meet with Metro District Air Quality Specialist and Office of Environmental Services staff to determine MSAT modeling analysis methodologies. Deliverable: One electronic memorandum stating requirements for air quality monitoring and proposed MSAT modeling analysis methodologies. Format: All files submitted electronically. Report written in Microsoft Word 2013 document (docx extension). Complete package in Adobe Acrobat (pdf extension) and pdf should be created by using Adobe Acrobat to convert the source file to a pdf whenever possible with the use of scanned pages minimized if not eliminate with the exception of actual signature pages. Standard: EA standards referenced herein. State and FHWA Review: Along with the Metro Scoping Report Contractor Update: Along with the Metro Scoping Report 4.4 Determine Level of Noise Analysis (P6 Activity NOI1000) Assumptions: Assumes no noise exemption request/noise exemption report application. Follow current MnDOT Noise Requirements and Guidance available at: Analyze the project and applicable state and federal standards and will determine the level of noise analysis that will be required for the project. Work with State s Central Office and Metro District Noise Analysis Units to gain concurrence on the Contractor s determination. Deliverable: One electronic memorandum stating required level of Noise Analysis. Format: All files submitted electronically. Report written in Microsoft Word 2013 document (docx extension). Complete package in Adobe Acrobat (pdf extension) and pdf should be created by using Adobe Acrobat to convert the source file to a pdf whenever possible with the use of scanned pages minimized if not eliminate with the exception of actual signature pages. All source files from model. Standard: All noise analysis modeling will be performed using approved FHWA and State noise model currently TNM 2.5 and 2017 MnDOT Noise Requirements State and FHWA Review: Along with the Metro Scoping Report. Contractor Update: Along with the Metro Scoping Report. 4.5 Identify Section 6(f) (P6 Activity SSF0900) Review the database of LAWCON funded facilities in the vicinity of the project area and provide a map showing these properties. Document the potential impacts to them, such as showing potential construction limits within the properties with area of impact measured. It is not expected that this project will impact any 6(f) properties and this activity will work to confirm that assumption. Deliverable: Map of known 6(f) properties adjacent to the project with documentation on potential impacts. Format: All files submitted electronically. Report written in Microsoft Word 2013 document (docx extension). Complete package in Adobe Acrobat (pdf extension) and pdf should be created by using Adobe Acrobat to convert the source file to a pdf whenever possible with the use of scanned pages minimized if not eliminate with the exception of actual signature pages. Standard: EA standards referenced herein. Page 11 of 31

12 State and FHWA Review: Along with the Metro Scoping Report. Contractor Update: Along with the Metro Scoping Report. 4.6 Identify Environmental Justice Issues for Alternatives (No P6 EAW 1020) Preliminary analysis and information will be collected from desktop resources to identify if environmental justice issues exist within the project corridor. This information will be compiled into the Preliminary Environmental Investigation to aid in alternative review. 4.7 Contamination Database Review (Part of RFR1002) MnDOT is doing a contaminated materials review under a separate contract. This task will involve coordination with MnDOT consultant to coordinate where investigation is needed and when information is needed to meet the project schedule. The information provided by the MnDOT consultant will be compiled into the Preliminary Environmental Investigation to aid in alternative review 4.8 Develop Draft Purpose and Need Statement (P6 Activity AAA1110) Develop draft purpose and need statement. This will be reviewed with the State and FHWA. This task assumes up to three revisions of the statement. The Project Need statement will identify transportation problems along the project corridor. The Project Purpose statement will summarize the project objectives and goals for addressing some or all of the project needs, and will summarize regional transportation plans regarding the project corridor. At a minimum, but not limited to, the following items need to be incorporated into the Purpose and Need as necessary with particular attention to any additional issues noted by FHWA: Coordination with other separate projects occurring within this projects limits scheduled in relative close proximity to this project Analysis defining logical termini Traffic operations outlining current traffic problems Describe current geometric deficiencies Safety Analysis/Crash Analysis Pedestrian connectivity and surrounding land uses Project Need Statement will summarize and explain transportation needs based on: o State MnSHIP and/or the Metro District 20 Year Plan. Project Purpose Statement will summarize regional transportation plans for this corridor, and explain the project objectives and goals. Regional transportation plans are listed below. o Metropolitan Council s 2040 Transportation Policy Plan, Chapter 4, o State Metro District s Transportation System Plan Deliverable: One electronic Draft Purpose and Need Statement Format: All files submitted electronically. Report written in Microsoft Word 2013 document (docx extension). Complete package in Adobe Acrobat (pdf extension) and pdf should be created by using Adobe Acrobat to convert the source file to a pdf whenever possible with the use of scanned pages minimized if not eliminate with the exception of actual signature pages. Standard: Must use the July 2013 version of the MN EAW located on the Environmental Quality Board s website at: The FHWA s guidebook or State s HPDP must be used as guidance to ensure that the National Environmental Policy Act laws have been fulfilled in the EA/EAW. Refer to the following web sites: and Guidance for Preparing and Processing Environmental and Section 4(f) Documents, Federal Highway Administration Technical Advisory A. Page 12 of 31

13 State and FHWA Review: Arrange a meeting within 2 weeks of submitting to State with both State and FHWA staff in attendance. Contractor Update: The outcome of the meeting will determine the amount of work needed to complete the Final Purpose and Need Statement. 5 Alternatives Evaluation (Source Type Code 1071) The alternatives to be evaluated include: No Build Rum River Bridge Replacement (with underclearance increase of 6 inches, 1 foot and 2 feet) Improvements at US 169/TH 47/Ferry Street Interchange with US 10. Assumes modeling two types of interchanges at this location which reconstruct Bridge 9713 and one alternative that would maintain the existing structure. These alternatives will include variations that assume current gate control and a grade separation at TH 47 and BNSF Railroad at approximately TH 47 RP Eastbound and Westbound auxiliary lane on US 10 from 7 th Ave N to US 169/TH 47/Ferry Street Removal of US 169/TH 47/Ferry Street Interchange One alternative for carrying a barrier separated trail across the Rum River Bridge and connecting to local streets on either side of the river. The alternatives evaluation is a key deliverable that must be understood by the public. Develop alternatives evaluation documents, presentations, spreadsheets, drawings, and other material meant for use by the public in a plain language and accessible format. Supporting documentation created during project development does not need to meet the plain language and accessible format, but select information from those materials will need to be converted into plain language and accessible format before it is released to the public. This task will require information from several other tasks in this scope to be completed, such as alternatives layouts, cost estimates, traffic modeling, and preliminary environmental investigation. Explain why all rejected alternatives were rejected. The remaining alternatives must be described in detail with an illustrative project layout. 5.1 Draft Project Alternatives Report (P6 Activity PMM1020) The draft project alternatives report will identify all of the alternatives considered during the project development process and provide illustrative examples. The draft project alternatives report will need to be reviewed by FHWA, State, and other stakeholders. The completion of this task and the meeting between FHWA and State must occur early in the project to determine how much work will be needed to complete the alternatives analysis. The draft project alternatives report will include the alternatives identified in the Alternatives Evaluation section. Deliverable: One electronic Draft Project Alternatives Report Format: All files submitted electronically. Report written in Microsoft Word 2013 document (docx extension). Complete package in Adobe Acrobat (pdf extension) and pdf should be created by using Adobe Acrobat to convert the source file to a pdf whenever possible with the use of scanned pages minimized if not eliminate with the exception of actual signature pages. Standard: Must use the latest version of the MN EAW located on the Environmental Quality Board s website at: The FHWA s guidebook or State s HPDP must be used as guidance to ensure that the NEPA laws have been fulfilled in the environmental document. Refer to the following web sites: and Guidance for Preparing and Processing Environmental and Section 4(f) Documents, FHWA A. State and FHWA Review: Arrange a meeting within 1 week of submitting to State with both State and FHWA staff in attendance. Contractor Update: 2 weeks Page 13 of 31

14 5.2 Logical Termini Report (P6 Activity AAA1030) Create a logical termini write-up detailing the reasons for the end points of the project. The logical termini and the purpose and need statement influence each other, because the logical termini analysis can influence the outcome of the purpose and need just as the purpose and need can influence the outcome of the logical termini. The FHWA has a particular interest in this topic. Guidance from the FHWA Environmental Guidebook explains the following about logical termini: Logical termini for project development are defined as (1) rational end points for a transportation improvement, and (2) rational end points for a review of the environmental impacts. The environmental impact review frequently covers a broader geographic area than the strict limits of the transportation improvements. In the past, the most common termini have been points of major traffic generation, especially intersecting roadways. This is due to the fact that in most cases traffic generators determine the size and type of facility being proposed. However, there are also cases where the project improvement is not primarily related to congestion due to traffic generators, and the choice of termini based on these generators may not be appropriate. The next section will show some examples where this is the case. Choosing a corridor of sufficient length to look at all impacts need not preclude staged construction. Therefore, related improvements within a transportation facility should be evaluated as one project, rather than selecting termini based on what is programmed as short range improvements. Construction may then be "staged," or programmed for shorter sections or discrete construction elements as funding permits. Use the travel demand and VISSIM modeling scope described herein to help provide data needed during the analysis and write-up of this task. Deliverable: One electronic logical termini write-up Format: All files submitted electronically. Report written in Microsoft Word 2013 document (docx extension). Complete package in Adobe Acrobat (pdf extension) and pdf should be created by using Adobe Acrobat to convert the source file to a pdf whenever possible with the use of scanned pages minimized if not eliminate with the exception of actual signature pages. Standard: Must use the latest version of the MN EAW located on the Environmental Quality Board s website at: The FHWA s guidebook or State s HPDP must be used as guidance to ensure that the NEPA laws have been fulfilled in the environmental document. Refer to the following web sites: and Guidance for Preparing And Processing Environmental and Section 4(f) Documents, FHWA A. State and FHWA Review: Arrange a meeting within 2 weeks of submitting to State with both State and FHWA staff in attendance. Contractor Update: 2 weeks 5.3 Benefit-Cost Analysis for Alternative Screening (P6 Activity AAA1300) The purpose of this benefit-cost analysis is to compare alternatives during the initial screening of alternatives. Obtain alternative cost estimates and results from the traffic forecasting, and VISSIM operations modeling tasks and format data to be used in benefit-cost analysis for the alternatives plus the No Build. Conduct an incremental benefit-cost analysis for the No Build, and the Build alternatives. Results shall be reported in terms of net present value and benefit-cost ratio. The data, methods, and results of the benefit-cost analysis will be documented in a technical memorandum and submitted to State s Project Manager for review. Deliverable: One electronic technical memorandum. Format: All files submitted electronically. Report written in Microsoft Word 2013 document (docx extension). Complete package in Adobe Acrobat (pdf extension) and pdf should be created by using Adobe Acrobat to covert the source file to a pdf whenever possible with the use of scanned pages minimized if not eliminated with the exception of actual signature pages. Standard: To be coordinated with Met Council and State staff. Page 14 of 31

15 State Review: 14 calendar days Contractor Update: 14 calendar days. 5.4 Alternatives Evaluation (P6 Activity AAA1050) The Project Alternatives Evaluation Report will be completed when the following tasks are completed and conclusions can be drawn from those tasks: Draft project alternatives report Alternative layouts Alternative cost estimates Initial drainage overview map Traffic modeling TMP and Staging Evaluation Benefit-Cost Analysis Americans with Disabilities Act (ADA) field review Preliminary Environmental Investigation This evaluation will rank any remaining alternatives and provide the State with justification of the ranking. Specific evaluation criteria will be identified working with a Technical Advisory Committee to rank the alternatives. The appropriate measures for each criterion will be identified and an analysis of each alternative will be completed for each criterion. A matrix summarizing the results will be prepared. The Contractor will make a recommendation on which alternatives have most merit and support that recommendation within the report. Assume that project alternatives report will include the alternatives identified in the Alternatives Evaluation section. Deliverable: One electronic Project Alternatives Evaluation Report Format: All files submitted electronically. Report written in Microsoft Word 2013 document (docx extension). Complete package in Adobe Acrobat (pdf extension) and pdf should be created by using Adobe Acrobat to convert the source file to a pdf whenever possible with the use of scanned pages minimized if not eliminate with the exception of actual signature pages. Standard: Must use the latest version of the MN EAW located on the Environmental Quality Board s website at: The FHWA s guidebook or State s HPDP must be used as guidance to ensure that the NEPA laws have been fulfilled in the EA/EAW. Refer to the following web sites: and Guidance for Preparing And Processing Environmental and Section 4(f) Documents, FHWA A. State and FHWA Review: Arrange a meeting within 2 weeks of submitting to State with both State and FHWA staff in attendance. Contractor Update: 2 weeks 5.5 Alternatives Evaluation Presentation to Project Team (P6 Activity AAA1050) The Alternatives Evaluation Report will be summarized in a presentation to the project team including all pertinent stakeholders. The purpose of this presentation will be for the Contractor to summarize the alternatives studied and support the alternatives report. Deliverable: One presentation meeting assumed to be two hours in length Format: Microsoft PowerPoint 2013 document (pptx extension) and Adobe Acrobat (pdf) copy of presentation Standard: To be coordinated with State Project Manager State Review: 14 calendar days Contractor Update: 14 calendar days. Page 15 of 31

16 6 Preliminary Traffic Studies (Source Type Code 1016) Model and analyze US 10 for existing and proposed conditions for all alternative concepts that would impact traffic mobility (i.e. traffic conditions will not need to be modeled to account for differing profiles within a single concept). The modeling will conform to the current State modeling requirements that can be found at the web site, and are incorporated herein by reference. The mainline model limits will be from Round Lake Boulevard (CSAH 9) on US 10 to Ramsey Boulevard (CSAH 56) on US 10. On US 169 the model will go from West Main Street (MSAS 134) to US 10. On TH 47 the model will go from US 10 to the Anoka County Fairgrounds, including studying the difference to the model between the current gated condition across the BNSF railroad tracks and an overpass. The traffic modeling will include the alternatives identified in the Alternatives Evaluation section. 6.1 Traffic Counts (P6 Activity TFC1000) Collect current traffic count data for the trunk highway system included in the traffic model using the MnDOT Traffic Information System (TIS). This information will be used in the various traffic models in this scope of work. Deliverable: One electronic report. Data will need to be inputted into the various traffic models describe in this scope. Format: All files submitted electronically. Report written in Microsoft Word 2013 document (docx extension). Complete package in Adobe Acrobat (pdf extension) and pdf should be created by using Adobe Acrobat to convert the source file to a pdf whenever possible with the use of scanned pages minimized if not eliminate with the exception of actual signature pages. Standard: Report. State and FHWA Review: 14 calendar days Contractor Update: 14 calendar days 6.2 Prepare Traffic Forecasts and ESALs (P6 Activity TRF1000) Prepare a traffic forecast and ESAL report for the trunk highway system. This information is only to be used to create the Materials Design Recommendation for the trunk highway system. Deliverable: One electronic report. Format: All files submitted electronically. Report written in Microsoft Word 2013 document (docx extension). Complete package in Adobe Acrobat (pdf extension) and pdf should be created by using Adobe Acrobat to convert the source file to a pdf whenever possible with the use of scanned pages minimized if not eliminate with the exception of actual signature pages. Standard: Report. State and FHWA Review: 14 calendar days Contractor Update: 14 calendar days 6.3 Existing Traffic Conditions Report (P6 Activity TFM1000 & TFM1010) Develop an Existing Traffic Conditions Report discussing the field observations, and explains the existing geometric and operational deficiencies. Provide information about locations of existing bottleneck conditions, high weave areas, and mainline queue lengths. Review data for this project that relates to traffic counts, turning movements, signal timing, ramp metering, and geometrics as supplied by State and other agencies, by accessing State s Metro website, and by accessing State s data extraction workstation. If data obtained is more than two years old, the Contractor will obtain more recent data. Conduct field review of the traffic operations during the AM and PM peak periods to aid in the calibration of the base model and to verify geometric and operations. Consultant has the option to review corridor operation from State s RTMC facility during both peak periods. To schedule and coordinate corridor operations, contact the RTMC Operations staff at (651) Page 16 of 31

17 Create the Existing Conditions Modeling to support the report including calibration of a VISSIM model for the corridor for existing conditions. Deliverable: One electronic report with associated traffic modeling. Format: All files submitted electronically. Report written in Microsoft Word 2013 document (docx extension). Complete package in Adobe Acrobat (pdf extension) and pdf should be created by using Adobe Acrobat to convert the source file to a pdf whenever possible with the use of scanned pages minimized if not eliminate with the exception of actual signature pages. Standard: Report. The modeling will conform to the current State modeling requirements that can be found at the web site, and are incorporated herein by reference. State and FHWA Review: 14 calendar days Contractor Update: 14 calendar days 6.4 Traffic Operations Analyses (P6 Activity TFM 1020, TFM 1030, TFM 1040 and TFM 1050) This task and its subtasks make up the P6 Schedule activities: TFM1020 TFM1030 TFM1040 TFM 1050 Deliverable: Traffic modeling report including, o Travel demand forecast and analysis, o Sensitivity analysis on travel demand modeling, o VISSIM modeling and analysis, o VISSIM base model calibration report, o Sensitivity Analysis on VISSIM Modeling, o Comparison of alternatives. Draft electronic reports for review and comment. Electronic final reports. All pertinent modeling files required to replicate all model runs and results. o Includes all subtasks for this task. Format: All files submitted electronically. Report that is approximately 10 pages or less written in Microsoft Word 2013 document (docx extension). Complete package in Adobe Acrobat (pdf extension) and pdf should be created by using Adobe Acrobat to covert the source file to a pdf whenever possible. Standard: Requirement found at this website State Review: 14 calendar days Contractor Update: 14 calendar days Alternative Evaluation Modeling (P6 Activity TFM 1040) Coordinate with FHWA and the State to determine what alternatives will be evaluated as part of the alternative evaluation modeling. This evaluation will consist of high-level travel demand forecasting and VISSIM analysis. More detailed analysis will be conducted for the preferred alternative which is described in upcoming sections of the scope. Perform modeling and analysis for morning (AM) and afternoon (PM) peak conditions for a No-build and the alternatives listed in the Alternatives Evaluation section. Assumptions: Existing travel demand modeling (including model validation) will occur before this task begins. No build forecasts will be developed before this task begins. Page 17 of 31