RFP-CR50I35InterchangeFinalDesign.pdf

REQUEST FOR PROPOSAL (RFP)

QUALIFICATION BASED SELECTION (QBS)

County State Aid Highway 50 and I-35 Interchange Final Engineering Design

(Lakeville, MN)

County Project No. 50-033 City Project No. 26-05 MnDOT State Project No. 1980-100 Federal Funding No. 019-650-021

Release Date: August 4, 2026

Proposal Due Date: September 1, 2026, 2:00 P.M.

Dakota County Transportation Department Western Service Center 14955 Galaxie Avenue

Apple Valley, MN 55124

For additional information please contact:

Susan Wimberly

Susan.Wimberly@co.dakota.mn.us 952-891-7183 mailto:name@co.dakota.mn.us

Table of Contents

REQUEST FOR PROPOSAL (RFP)

INTRODUCTION AND PROGRAM DESCRIPTION

A. Purpose B. Program Description

SCOPE OF SERVICES

GENERAL INSTRUCTIONS FOR CONTRACTOR

A. Contact Person B. Questions C. Addenda/Clarifications D. Examination of Proposal Documents E. Pre-Contractual Expenses F. Contract Award G. Public Records and Requests for Confidentiality H. Joint Offers I. Dakota County Rights

SUBMISSION OF PROPOSAL

A. Proposal Submittal B. Proposal Format C. Proposal Contents

TIMELINE AND BUDGET

A. Program Timeline B. Contract Negotiations and Contract Proposals C. Payment for Services

PROPOSAL EVALUATION CRITERIA

ATTACHMENTS – INCLUDING FORMS TO BE COMPLETED

ATTACHMENT A: Deliverables and Scope of Services ATTACHMENT B: Project Milestones

ATTACHMENT C: STANDARD ASSURANCES

ATTACHMENT D: INSURANCE TERMS

ATTACHMENT E: SAMPLE CONTRACT

ATTACHMENT F: DIGITAL ACCESSIBILITY REQUIREMENTS

ATTACHMENT G: NON-COLLUSION, CONFLICT OF INTEREST, AND LOBBYING STATEMENT

ATTACHMENT H: TRADE SECRET FORM

ATTACHMENT I: Solicitation of Disadvantaged Business Enterprises (DBE) ATTACHMENT J: Disadvantaged Business Enterprises (DBE) Special Provisions ATTACHMENT K: Dakota County Parcel Sketch Guidance

INTRODUCTION AND PROGRAM DESCRIPTION

A. Purpose Dakota County, in partnership with the City of Lakeville and the Minnesota Department of Transportation (MnDOT), is seeking proposals from qualified consultants to provide professional engineering design and related services to complete final design of the MnDOT approved diverging diamond layout and other planned improvements to the Interstate 35 (I-35) interchange at County State Aid Highway (CSAH) 50/5 and the surrounding area in Lakeville, Minnesota.

A “Qualification Based Selection” method will be used to review proposals submitted in response to this RFP.

B. Program Description This project will complete final design for the MnDOT approved diverging diamond interchange layout. The work includes designing roadway, ramp terminal, trail, driveway, and intersection improvements along CSAH 50 (Kenwood Trail) from Kenrick Ave to Klamath Trail. It also includes design of improvements to I-35, Kenyon Ave (west of I-35), and Kenrick Ave (east of I-35) from CSAH 60 to CSAH 46. The project also adds an auxiliary lane to northbound I-35 from CSAH 50 to just north of the Metro Transit/Kenrick Ave Park and Ride on ramp. There is potential for innovative solutions to address access issues throughout the project and specifically at 175th Street North and CSAH 50/5 intersection.

A previous contract has completed preliminary engineering up to about 30% plan /layout stage. A structured handoff of preliminary design information will be scheduled after Notice to Proceed. The county will also provide access to preliminary design files. The preliminary engineering design contract will end with these deliverables:

• Completed Phase I and Phase II Environmental Site Assessment (ESA) – currently drafting Phase II

• Non-programmatic Categorical Exclusion decision document and associated environmental documents, including a Noise Analysis Report – currently pending FHWA and MnDOT approval

• Interstate Access Modification Report (IAMR) – currently pending FHWA and MnDOT approval

• MnDOT Project Layout – currently pending MnDOT approval

• A Visual Quality Management Plan to guide development of the VQM, which must be completed early to define bridge aesthetics

• A Bridge Type Study: MnDOT will complete the FADR for the I-35 bridges only

• A Level 1 Traffic Management Plan

The above project files and other pertinent files will be posted on a project OneDrive site for interested firms to review as they prepare their proposals. To download and review all files on project site please email the Dakota County Project Manager Susan Wimberly (Susan.Wimberly@CO.DAKOTA.MN.US) to request site access.

Close coordination will be required with MnDOT’s I-35 improvement project (MnDOT No. 1980-99). MnDOT’s project will resurface I-35 from the I-35 split to CSAH 70. It will also repair the I-35 bridges over Lake Marion and replace the bridges over 205th Street. It is scheduled to be let in State Fiscal Year 2030 and is expected to take about a year and half to complete.

The consultant is expected to propose and manage a clear, efficient, and well-defined process to meet all scope requirements. This RFP and the associated scope of services (Attachment A) are structured to meet State and Federal funding requirements supporting the current final design engineering work and to prepare for the future use of federal funds in separate subsequent contract work (right-of-way and construction). Responses to this RFP are public information under the Minnesota Data Practices Act (Minnesota Statutes Chapter 13).

The goal of this RFP is to develop a complete, turn-key, and fully signed set of 100% construction plans, specifications, and bid package for a MnDOT administered construction project scheduled for a September 2028 letting. Final deliverables will include a completed construction costs estimate, all necessary permits, and a specifications package prepared in compliance with trunk highway, state aid, and county requirements for bid letting and construction. The selected consultant will also be responsible for all supporting deliverables and for managing and coordinating processes to lead Dakota County, MnDOT, the City of Lakeville, and all other relevant stakeholders.

Secured State and Federal Funding Dakota County has applied for and received both state and federal funding assistance for design and construction of the proposed project and it is included in the Dakota County and Lakeville CIPs and MnDOT STIP. Dakota County continues to apply for additional funding support for full project implementation. The current secured funding is:

CP 50-33 Funding Sources Amount Remarks Federal Congressionally Directed Spending (2023)

$5,040,000 Design – 20% non-federal match required

Federal Congressionally Directed Spending (2026)

$2,000,000 Construction – 20% non-federal match required

MnDOT Trunk Highway Appropriations (2025)

$40,800,000 Construction but only MnDOT owned infrastructure

MN Highway Freight Program (2026)

$7,000,000 Construction – 20% non-federal match required

State General Obligation Bond Appropriation

$6,000,000 Design, ROW, and Construction of locally owned infrastructure

Sharing of Information The consultant will host a file sharing site to allow the project management team to share and receive files.

mailto:Susan.Wimberly@CO.DAKOTA.MN.US

SCOPE OF SERVICES

The scope of work generally includes assisting Dakota County with tasks necessary to complete the final design of a diverging diamond interchange and surrounding improvements at I-35 and County Road 50/5 in Lakeville.

Required consultant services include but are not limited to:

• Public involvement

• Visual Quality Manual (VQM) development

• Environmental documentation updates and permits

• Field survey

• Utility coordination

• Geotechnical work, pavement evaluation, and foundations analysis

• Final stormwater management and hydraulics design

• Final roadway and geometric design plans, construction staging, cost estimates (including freeway segments, roadways, trails, intersections, and related elements)

• Traffic analysis, Traffic Management Plan (TMP) updates, signal design

• Preliminary and final structural design for bridges, noise walls, and related features

• Right-of-way mapping, appraisals, relocation services, and other tasks necessary to support project approvals.

Public involvement, project management, and risk/quality management will also be integral to an efficient and effective work plan and delivery process.

A detailed description of the specific tasks and anticipated deliverables is described in Attachment A – Deliverables and Scope of Work.

Consultants are encouraged to propose additional tasks/subtasks and refinements to the RFP recommended scope if such work will substantially improve the results of the project.

Responders must not include price information either in the body of their proposal or as a separate submittal.

GENERAL INSTRUCTIONS FOR CONTRACTOR

A. Contact Person

The primary point of contact for this RFP is:

Susan Wimberly, Senior Project Manager Dakota County Transportation Department 14955 Galaxie Avenue Apple Valley, MN 55124 Susan.Wimberly@CO.DAKOTA.MN.US Phone: 952-891-7183 Fax: 952-891-7588

In addition, a team of county staff will regularly review and comment on the work. A Project Management Team (PMT) will work to provide direction and support toward successful completion of the project and will participate in the review of submittals by the consultant. In addition to one or more representatives from the consultant, the PMT will be comprised of representatives identified and designated by Dakota County, the City of Lakeville, and MnDOT.

The City of Lakeville Project Manager is:

Zach Johnson, City Engineer City of Lakeville 20195 Holyoke Avenue

Lakeville MN 55044 Phone: 952-985-4501

Email: zjohnson@lakevillemn.gov mailto:zjohnson@lakevillemn.gov

The MnDOT Project Manager is:

Mohamoud Mire, South Area Engineer for Dakota County MnDOT Metro District 1500 County Road B2 W

Roseville, MN 55113 Phone: 651-234-7500

Email: mohamoud.mire@state.mn.us

The MnDOT Project Manager for 1980-99 I-35 Improvements is:

Nicole Stromgren, Project Manager MnDOT Metro District 1500 County Road B2 W

Roseville, MN 55113 Phone: 651-234-7724

Email: nicole.stromgren@state.mn.us

B. Questions Questions regarding this RFP must be submitted by email and must be received no later than 2:00 p.m.

August 18, 2026.

Responses to the questions submitted will be posted on the County’s website no later than 5:00 p.m.

August 27, 2026, at Doing Business - Request For Bids, Proposals and Information:

http://www.co.dakota.mn.us/Government/DoingBusiness/BidProposalsInformation/Pages/default.aspx

C. Addenda/Clarifications Any revisions or modifications to the RFP shall be made by County staff in a written addendum and posted on the County’s website at Doing Business – Request for Bids, Proposals and Information at http://www.co.dakota.mn.us/Government/DoingBusiness/BidProposalsInformation/Pages/default.aspx.

No verbal modification will be binding.

D. Examination of Proposal Documents By submitting an RFP, the Contractor represents that he or she has thoroughly examined and become familiar with the work required under this RFP and that he or she is capable of performing quality work to achieve the objectives of this RFP.

E. Pre-Contractual Expenses Pre-contractual expenses are expenses incurred by the Contractor in: 1) preparing its proposal in response to this RFP; 2) submitting that proposal to the County; or 3) any other expenses incurred by the Contractor prior to the date of execution of the proposed contract. The County shall not, in any event, be liable for any pre-contractual expenses incurred by the Contractors in the preparation of their proposals. Contractors shall not include any such expenses as part of their proposals.

F. Contract Award Issuance of this RFP and receipt of proposals does not commit Dakota County to award a contract.

Dakota County reserves the right to postpone proposal review at its own convenience, to accept or reject proposals based on evaluation of the submitted information, to accept other than the lowest cost proposal, to negotiate with other than the selected Contractor should negotiations with the selected Contractor be terminated, to negotiate with more than one Contractor simultaneously, or to cancel all or part of this RFP.

G. Public Records and Requests for Confidentiality Pursuant to the Minnesota Government Data Practices Act, Minnesota Statutes Section 13.591, the names of all entities that submitted a timely proposal to Dakota County will be public once opened. All other information remains private until Dakota County has completed negotiating a contract with the selected Responder. After a contract has been negotiated, all information received is public information except “trade secret” information as defined in Minnesota Statutes Section 13.37. All information submitted by a Responder therefore shall be treated as public information by Dakota County unless the Responder properly requests that information be treated as a confidential trade secret at the time of submitting the bid/proposal.

Any request for confidential treatment of trade secret information in a Responder’s proposal must sufficiently describe the facts that support the classification of information as confidential trade secret. The mailto:mohamoud.mire@state.mn.us mailto:nicole.stromgren@state.mn.us http://www.co.dakota.mn.us/e_government/bids/bids_rfps.htm request must include the name, address, and telephone number of the person authorized by the Responder to answer any inquiries by Dakota County concerning the request for confidentiality. This information shall be provided on the Trade Secret Information Form, see Attachment E. Dakota County reserves the right to make the final determination of whether data identified as confidential trade secret by a Responder falls within the trade secret exemption in the Minnesota Government Data Practices Act.

The envelope or mailing container of any documents submitted with the proposal that the Responder believes contain confidential trade secret information must be clearly marked as containing confidential trade secret information. Each page upon which trade secret information appears must be marked as containing confidential trade secret information.

In addition to marking the documents as confidential, the Responder must submit one paper and one digital copy of the bid/proposal from which the confidential trade secret information has been excised. The confidential trade secret information must be excised in such a way as to allow the public to determine the general nature of the information removed while retaining as much of the document as possible.

The Responder’s failure to request confidential treatment of confidential trade secret information pursuant to this subsection will be deemed by Dakota County as a waiver by the Responder of any confidential treatment of the trade secret information in the bid/proposal.

Requests by the public for the release of information held by Dakota County are subject to the provisions of the Minnesota Government Data Practices Act, Minnesota Statutes Chapter 13. Responders are encouraged to familiarize themselves with these provisions prior to submitting a proposal.

By submitting this proposal, Responder agrees to indemnify and hold the County, its agents and employees, harmless from any claims or causes of action relating to the County’s withholding of data based upon reliance on the representations that the information is a trade secret as defined in Minnesota Statutes Section 13.37 and therefore is not public, including the payment of all costs and attorney fees incurred by the County in defending such an action.

Public Data Requests can be submitted on the County's website:

https://www.co.dakota.mn.us/Government/DataPractices/Pages/default.aspx

H. Joint Offers Where two or more Contractors desire to submit a single proposal in response to this RFP, they should do so on a prime-subcontractor basis rather than as a joint venture. Dakota County intends to contract with a single firm and not with multiple firms doing business as a joint venture.

I. Dakota County Rights County staff may investigate the qualifications of any Contractor under consideration, require confirmation of information furnished by Contractor, and require additional evidence of qualifications to perform the work described in this RFP. County staff reserves the right to:

• Reject any or all proposals if such action is in the public interest;

• Cancel the entire RFP;

• Issue a subsequent RFP;

• Remedy technical errors in the RFP process;

• Appoint evaluation committees to review proposals;

• Establish a short list of Contractors eligible for interview after evaluation of written proposals;

• Negotiate with any, all, or none of the RFP respondents; and

• Reject and replace one or more subcontractors.

This RFP does not commit Dakota County to enter into a contract, nor does it obligate Dakota County to pay for any costs incurred in preparation and submission of proposals or in anticipation of a contract.

SUBMISSION OF PROPOSAL

A. Proposal Submittal The Contractor must review the attached specifications, scope of services, and exhibits and submit one

(1) electronic copy of the proposal by September 1, 2026, 2:00 P.M. to susan.wimberly@co.dakota.mn.us.

https://www.co.dakota.mn.us/Government/DataPractices/Pages/default.aspx mailto:email@co.dakota.mn.us

B. Proposal Format

1. All proposals by corporations shall bear the official seal of the corporation, if applicable, along with the signature of a duly authorized officer of the corporation.

2. All text and exhibits should be succinct and relevant to the RFP requirements.

3. The proposal text will not exceed twenty-five (25) pages, not including the cover letter or any appendix attachments which are optional per further appendix instructions below.

4. Illustrative graphics (i.e., layouts, organizational charts, schedules, etc.) are allowed on 11" x

17" format pages. Otherwise, proposals will be prepared on 8-1/2” x 11” format pages, with sequentially numbered pages throughout the report or by section. All text and exhibits should be succinct and relevant to the RFP requirements.

C. Proposal Contents The proposal must include, at a minimum, the following sections:

1. Letter of Transmittal:

The proposal must be submitted on the firm’s official business letterhead. The letter is to transmit the proposal and must identify all materials and enclosures being forwarded collectively as a response to this RFP.

Include, at a minimum, the following:

a. Identification of the offering firm(s), including name, address, and telephone number of each firm;

b. Acknowledgment of receipt of RFP addenda, if any;

c. Name, title, address, telephone, fax numbers and e-mail address of contact person during period of proposal evaluation;

d. A statement to the effect that the proposal shall remain valid for a period of not less than

120 days from the date of submittal; and

e. Signature of a person authorized to bind the offering firm to the terms of the proposal.

2. Project Understanding, Work Plan, and Project Approach:

Describe the project understanding and approach proposed by your firm as well as specific role(s) and responsibilities. Focus on the issues you believe are significant for successful completion; note specific approach(es); describe how you intend to use background information to help manage contract costs; note any unique options to be pursued; and provide a brief outline of your approach to complete the RFP’s tasks, emphasizing the benefits of your approach, with possible unique methods to deliver the scope and to manage quality. Consultants should demonstrate their understanding by using their own words rather than repeating content provided in this RFP.

Construction Perspective during design - Explain the approach this team will use to address and identify potential issues with design before construction. Explain the approach to ensure that the designs have accounted for appropriate existing conditions. Give examples of items that can cause problems during construction that design reviewers are aware of from past lessons learned. Explain how you will manage those items. These items may not be key items to project success, but they are items required to be done correctly and may have been missed or ignored until it was realized too late that they are causing a problem.

Describe how your firm will support and enhance the overall project. How your team will utilize your flexibility within your team to complete the tasks in a timely manner. Discuss what additional staff or resources may be used to meet these needs. Describe how staff will interact with various stakeholders and ensure approvals are timely.

Partnering or Teaming - Explain the responder’s approach to enhancing project delivery and quality during the final design phase of the project. Also explain how this team members will communicate and collaborate with the PMT and other stakeholders.

Schedule- Explain your approach to ensure submittals will be reviewed within established timelines.

Describe how you will manage changes in the deadlines, number and types of submittals, including how you will adjust staff or resources when workload increases or decreases. Explain how your team will collaborate with different functional units to make sure each submittal gets a complete review and timely review.

3. Key Personnel Qualifications and Experience:

Propose one or more person(s) that will fill each of the roles below, it is acceptable for key personnel to be assigned to multiple roles. Demonstrate how your team meets the following qualifications:

• Project Manager: Must be licensed to practice engineering within the State of Minnesota.

Must demonstrate project management experience with similar projects of similar scope including diverging diamond interchanges, balancing multiagency stakeholders, and interchange projects. Provide a description of the Project Manager and their qualifications for this project and a detailed list of previous projects worked on that are relevant to the project.

• Design Manager: Must be licensed to practice engineering within the State of Minnesota.

Provide examples of similar experience of roles and relevant work performed on previous projects that relate specifically to this role. Examples provided must be within the last 10 years. Description must include a brief explanation of the size and complexity of the highway projects, and the role preformed. If they have bridge design experience it should be included.

• Other Key Personnel: Provide a list of key personnel assigned to this project. Identify areas of expertise and if they have worked with the Project Manager on previous projects or in similar roles. The connection between the team’s organization and task/delivery assignments should be easily understood.

o Bridge Design, Geotechnical, and Foundations Engineer(s) o Roadway Design Engineer o Traffic Engineer o Drainage Engineer o Utility Coordinator o Construction Perspective Support Engineer o Visual Quality Manager o Quality Manager and Quality Reviewers o Real Estate Appraiser with experience in commercial properties o Relocation Advisor with commercial experience in facilities with petroleum waste

• Other staff must have the training and expertise necessary to complete the work as required.

• Staff resumes are required in a separate appendix. The purpose of this section is for your firm to provide information detailing the background and experience of project personnel. Explain what makes your team the most qualified.

• If subconsultants are to be used on this project, responders must also outline their background and experience, including examples of similar work done by each subconsultant.

Responders must also provide a list of the subconsultants’ personnel who will perform work on the project, detailing their training and work experience.

• Explain key personnel’s availability and time commitments to the project. What other time commitments they have and how they will balance their workload. For example, a percent of time committed to the relevant phases of this project versus percent of time committed to other projects, with conditional statements as necessary.

• Explain how your team’s organizational structure will coordinate and balance with the client’s organization structure including coordination with MnDOT.

• Note the county must be notified of any changes in personnel assigned to the project.

Similarly, the County will notify the consultant if there are any changes to the County’s assigned personnel.

MnDOT, City, or County performance evaluation data (for similar services) may be taken into consideration as part of this rating factor.

4. Team Organization and Performance on Similar Projects In this section, state in writing or provide an organization chart showing the team members and key personnel. Identify the team members’ areas of responsibility. Provide subcontractors’ company name, address, contact person, email and telephone number.

Describe previous similar projects that the team was involved with, including projects with similar public involvement, construction staging and design efforts, that also addressed MnDOT and federal requirements. Include projects that required working with multiple stakeholders and coordination with projects administered by other agencies.

5. Quality Management/Control/Assurance Explain the approach to ensure delivery of quality products in a timely manner that conform to established standards, procedures, and deliverable requirements. The proposal should identify the roles, methods, processes, and tools used to assure and implement the project’s quality plan.

6. Pre-Award Audit Requirement:

The successful responder will be required to submit pre-award audit information and comply with audit standards.

All design services performed under this contract shall comply with 23 CFR 172 and all applicable MnDOT policies governing the procurement and administration of engineering and design‑related consultant services. This includes adherence to qualifications‑based selection, federal cost principles, design documentation requirements, and MnDOT’s consultant oversight processes.

Consultants and subconsultants must comply with the indirect cost rate requirements of 23 CFR

172.11 and MnDOT’s Consultant Services indirect cost rate policies.

7. Conflict of Interest The Contractor must identify any potential conflict of interest it may have with this proposal. See Attachment G: Non-Collusion and Conflict of Interest Statement.

8. Exceptions and Deviations Any exceptions to the requirements in this RFP must be included in the proposal submitted by the Contractor. Segregate such exceptions as a separate element of the proposal under the heading “Exceptions and Deviations.”

9. Contract Terms and General Conditions The Dakota County standard Contract Terms and General Conditions are included within this RFP document, including Attachment A: Deliverables and Scope of Services. Proposals should indicate the firm’s willingness to agree to these provisions.

10. Registration and Good Standing All responders must be in compliance with Minnesota law governing transaction of business in the State of Minnesota. Upon award of the contract, the County will verify compliance prior to contracting.

TIMELINE AND BUDGET

A. Program Timeline

This RFP will be conducted according to the following tentative schedule. This tentative schedule may be altered at any time at the discretion of County staff. The term of the contract to be awarded under this RFP is anticipated to be November 2026 through December 2030 but may be adjusted to accommodate unforeseen delays. A more detailed proposed schedule is included in Attachment B.

1. Release: August 4, 2026

2. Questions Due: August 18, 2026

3. Responses to Questions Posted: August 26, 2026

4. Proposals Due: by 2:00 p.m. September 1, 2026

5. Contractor Selection: September 15, 2026

6. Selected Contractor’s Tasks, Schedule, Budget Due: September 22, 2026

7. Contract Negotiations Complete: October 6, 2026 (Begin MnDOT preaudit)

8. Anticipated Contract Start Date: November 13, 2026 (County Board approval 11/10/26)

9. Contract End Date: December 31, 2030

B. Contract Negotiations and Contract Proposals Contract Negotiations and Proposals will be evaluated, and a successful responder will be chosen based on qualifications only. The successful responder will be required to submit a detailed scope of services and budget promptly (within 5 business days) after notification of selection. Dakota County and the successful responder will then meet to negotiate the final scope of services and compensation. If Dakota County and the successful responder are unable to agree upon a scope of services and compensation within a https://mblsportal.sos.state.mn.us/ reasonable time (as determined by Dakota County, in its sole discretion), then Dakota County may declare negotiations to be at an impasse and may commence negotiations with the next highest-ranked responder.

C. Payment for Services Contractor must identify the budget necessary to perform the services identified in the Scope of Services.

The Contractor, when establishing cost estimates for the total Program, shall include all direct expenditures, such as, but not limited to: Contractor fees, travel costs, necessary material purchases (subject to County approval), etc. Materials provided to Contractors as a part of their participation in the Program, such as labels, containers and compostable bags, will be procured by the County. Indirect rates or overhead costs – such as rent, utilities, or incidental copying – will not be allowed under this contract.

The consultant shall submit a cost estimate based on hourly charges and reimbursables up to a maximum not to exceed total for all work within the scope of the project. The consultant’s budget is to include the chargeable hourly rate of each team member, the anticipated number of hours spent on the project for each team member, and the fee maximum. The overall fee shall reflect a maximum not to exceed based on the sum of the tasks.

Billing for completed services shall be based upon a monthly invoice submitted by the Contractor. The invoice shall indicate the hours of labor performed by each person charging time to the Program, their charge out rate, and itemizations of the reimbursable expenses charged to the Program. County staff will have the right to inspect the Program timesheets. The invoice must also indicate the total contract amount, the total paid to date, the remaining amount to be paid, and the estimated percent of Program completed. County staff, at staff’s option, may retain a portion of the total fee to ensure that sufficient fees are available to complete the Program.

PROPOSAL EVALUATION CRITERIA

The award shall be based on, but not limited to, the following factors:

1. Project Understanding, Work Plan, and Approach (30%) – conceptual and technical approach to design and general approach (for example, delivery priorities and proposed tools or techniques to provide good value). A clear understanding and innovative approach of the project scope, complexities, focus areas, deliverables, project decisions/approvals, and scheduling/relationships of tasks (may include perspectives and refinements of tasks, approaches to coordinate tasks, deadlines for deliverables, and methods to complete the project efficiently and effectively, limiting re-statement of scope from Attachment A).

2. Key Staff Qualifications and Experience (45%) – qualifications and experience of the Project Manager, Design Manager, and key support staff proposed to work on the project, experience on previous similar projects, and availability of the key staff members.

3. Recent Team Performance on Similar Projects (20%): Describe previous similar projects that the team was involved with, including projects with similar public involvement, construction staging and design efforts, including those addressing MnDOT State Aid and federally funded project requirements.

4. Quality Control (5%) – demonstrate QA/QC roles and planning to ensure the delivery of quality products by proactively identifying and managing risks and balancing quality management with scope, schedule, and budget.

If considered necessary to complete evaluations and reach a recommendation, Dakota County and the partners will invite two or more consultant teams to interviews.

Proposals will be evaluated, and a successful responder will be chosen based on qualifications only. The successful responder will be required to submit a detailed scope of services and budget promptly (within 5 business days) after notification of selection. Dakota County and the successful responder will then meet to negotiate the final scope of services and compensation. If Dakota County and the successful responder are unable to agree upon a scope of services and compensation within a reasonable time (as determined by Dakota County, in its sole discretion), then Dakota County may declare negotiations to be at an impasse and may commence negotiations with the next highest-ranked responder.

Dakota County anticipates that the evaluation and selection will be completed by mid-September 2026

Responders must not include price information either in the body of their proposal or as a separate submittal.

ATTACHMENTS – INCLUDING FORMS TO BE COMPLETED

A. Deliverables and Scope of Services B. Project Milestone and Proposed Schedule C. Dakota County Standard Assurances D. Dakota County Insurance Terms E. Dakota County Sample Professional Services Contract F. Digital Accessibility Requirements G. Non-Collusion and Conflict of Interest Form (to be completed and submitted with proposal) H. Trade Secret Information Form (to be completed and submitted with proposal) I. Solicitation of Disadvantaged Business Enterprises (DBE) Statement (to be completed and submitted with proposal) J. Disadvantaged Business Enterprises (DBE) Special Provisions K. Parcel Sketch Guidelines

ATTACHMENT A: Deliverables and Scope of Services

ATTACHMENT A: DELIVERABLES AND SCOPE OF SERVICES

CSAH 50 and I-35 Interchange (CP 50-33; MnDOT SP No. 1980-100)

Table of Contents

INTRODUCTION AND PROGRAM DESCRIPTION

General Scope and Proposal Objectives Contract Negotiations, Cost Proposal, and Audited Rates Task 1 – Project Management and Agency Coordination Task 2 – Public Involvement Task 3 – Visual Quality Manual Task 4 - Environmental Documentation Updates and Permits Task 5 – Field Survey Task 6 – Public and Private Utility Identification and Coordination Task 7 – Geotechnical Review, Pavement Evaluation, Phase II ESA Follow Up Task 8 – Stormwater Management, Hydraulics, Permit Requirements Task 9 – Roadway Geometric Design Plans; Construction Staging; Cost Estimates Task 10 – Traffic Management Plan (TMP) Updates and Implementation Task 11 – Signal Design Task 12 – Traffic Management System Coordination Task 13 – Bridge and Structures Design

13.1 Preliminary Bridge Design

13.2 Final Bridge Design

13.3 Load Rating

13.4 Approach Panel Design & Detailing

Task 14 – Noise Wall Design Task 15 – Right-of-Way Mapping, Parcel Sketches, Appraisals, Relocation Task 16 – Construction Package, Bidding, Award, and Administration Support Task 17 – Optional Tasks (identified by consultant)

Dakota County CSAH 50/I-35 Interchange Final Design RFP Attachment A – COUNTY PROJECT NO. 50-33 A-1

INTRODUCTION AND PROGRAM DESCRIPTION

General Scope and Proposal Objectives This project will complete final design for the MnDOT approved diverging diamond interchange layout. It includes:

• Replacement of I-35 bridges over County Road 50/5.

• County Road 50/5 generally remains along its existing alignment and using the existing bridge portal under I-35.

• An additional westbound through lane would be constructed along County

Road 50/5 through the interchange area.

• Trails running in the median area of the interchange and on each side of

Country 50/5, north and south of the interchange.

• An auxiliary lane will be added to northbound (NB) I-35 from the County

Road 50/5 I-35 on ramp to just north of the transit on ramp (Metro Transit/Kenrick Ave Park and Ride).

• Realignment of both the frontage roads. Kenrick Avenue and Kenrick Circle on the east side of I-35 and Kenyon Avenue on west side.

• Detours will be required, while the I-35 bridges over County Road 50/5 are being rebuilt and County Road 50/5 is closed from Kenyon Avenue to 175th Street, and possibly while the Kenrick Ave (East Frontage Road) is being realigned and closed to through traffic.

• Construction of several stormwater ponding locations near the interchange area.

• Several proposed traffic signals:

o At the intersection with 175th Court o Near SE ramp connection o Near SW ramp connection o Near NE ramp connection o At intersection with Kenyon Avenue

• Drainage (grading) improvements

• Lighting improvements

There is potential for innovative solutions to address access issues throughout the project and specifically at 175th Street and CSAH 50/5 intersection.

The project limits include the interchange area, on CSAH 50/5 (CSAH 50) extending through the Kenrick Ave and Klamath Trail intersections. It also includes I-35, Kenyon Ave (west of I-35), and Kenrick Ave (east of I-35) from 185th Street (CSAH 60) to 162nd Street (CSAH 46).

Consultants are encouraged to propose additional tasks/subtasks and refinements to the RFP recommended scope if such work will substantially improve the results of the project.

Construction plans are expected to be advertised in fall 2028, with construction beginning in 2029.

Close coordination will be required with MnDOT’s I-35 improvement project (MnDOT No. 1980-99) between the I-35 split and CSAH 70. MnDOT’s project will resurface I-35 from the I-35 split to CSAH 70. It will also repair the I-35 bridges over Lake Marion and replace the bridges over 205th Street. Which is scheduled to be let in State Fiscal Year 2030 and is expected to take about a year and half to complete. It is assumed MnDOT will administer both construction projects.

Contract Negotiations, Cost Proposal, and Audited Rates Proposals will be evaluated, and a successful responder will be chosen based on qualifications only. The successful responder will be required to submit a detailed scope of services and budget promptly (within 5 business days) after notification of selection. Dakota County and the successful responder will then meet to negotiate the final scope of services and compensation. If Dakota

RFP Attachment A – COUNTY PROJECT NO. 50-33 A-2

County and the successful responder are unable to agree upon a scope of services and compensation within a reasonable time (as determined by Dakota County, in its sole discretion), then Dakota County may declare negotiations to be at an impasse and may commence negotiations with the next highest-ranked responder.

Dakota County anticipates that the evaluation and selection will be completed by mid- September 2026.

Responders must not include price information either in the body of their proposal or as a separate submittal.

The negotiation requirements will also include submittal of pre-award audit information to MnDOT and Dakota County and the recommended consultant and all subconsultants must comply with MnDOT audit standards. Failure to provide the requested data in a timely manner may result in disqualification; therefore, all consultants and subconsultants are advised to prepare in advance for contract scope and cost negotiations and for the audit requirements.

Task 1 – Project Management and Agency Coordination Management of the project will include communication with the county, the cities of Burnsville and Lakeville, MnDOT, the Federal Highway Administration (FHWA), the Dakota County Board, Metropolitan Council, Minnesota Valley Transit Authority and other agencies and local groups.

1.1 Administration

Administration of the project will include agendas, meetings, minutes, progress reports, invoicing, contract amendment requests (if necessary), cost and schedule updates, billing preparation, other non-technical work, communication with the necessary project personnel, and all other work to ensure all the project tasks are completed on time, within budget, and in accordance with state and federal laws, rules, and regulations. The consultant will discuss the upcoming tasks for the next billing cycle and keep county project manager up to date on budget concerns and discuss how the consult is planning to stay on budget.

1.2 Ongoing Project Management Communications and Tools will include

• Regular Progress Meetings – The consultant’s Project Manager (PM) will meet virtually with County’s Program Manager weekly or semi-weekly as needed to review the progress of the work, schedule and budget status, and other key upcoming initiatives.

Considerations may also include resource needs and "burn rate" to aid in budget management.

• Monthly Project Management Team (PMT) Meetings – PMT meetings are expected to focus on staff representing Dakota County, the City of Lakeville, and MnDOT. These meetings may also be used periodically to supplement technical coordination with other involved agencies or specialists. The consultant will prepare the agendas and minutes within one week following the meeting.

• Project Instructions and Quality Management – Develop and implement tools such as Project Instructions, a Project Management Plan, Work Plans, and a Quality 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 to ensure delivery of quality products. Develop a project risk register or similar tools to track and mitigate large cost and schedule risks. The consultant’s Quality Management Plan (QMP) will specify QA/QC procedures to be performed throughout the project to ensure delivery of a quality product in a timely manner, conforming to contract

RFP Attachment A – COUNTY PROJECT NO. 50-33 A-3 requirements. The QMP must be developed in accordance with MnDOT’s current QMP Manual, located at: www.dot.state.mn.us/design/qmp/index.html.

• Subconsultant Management and Oversight – Manage, coordinate, direct, and monitor subconsultant services based on roles and all applicable contracts.

• Action Item Log – Create and maintain a running action item log including a Comment Resolution Log for all 30/60/95% submittals and a Decisions Log documenting all key design choices.

1.3 Schedule Management and Progress Reports/Invoices

Create and actively maintain a detailed schedule using Primavera P6 or other commercially available scheduling software. At a minimum the schedule will include durations and due dates for all deliverables listed in this scope of work. Related activities will include:

• Monthly progress and status reports, including a description of the past months activities and lookahead for the coming month(s)

• Invoices submitted in a timely manner – Bill monthly throughout the duration of the project, no later than ten (10) days after the completion of each the month. All invoices will clearly define the percentage of project completion, and the percentage of project billed to date for each work task and the total project. All invoices will be submitted by email to DCTransportation.Invoices@co.dakota.mn.us and copied to the County’s Project Manager.

• Electronically deliver all project correspondence monthly to Dakota County for project archival, this includes minutes, logs, emails, etc.

• Schedule Updates – Electronic schedule to be updated monthly and sent electronically to the County’s project manager in PDF format.

1.4 Coordination

The consultant will coordinate activities with the FHWA, MnDOT, cities of Burnsville and Lakeville, Dakota County Board, Metropolitan Council, and other agencies and representatives as needed. The consultant will also coordinate project management activities with utility owners and property owners when necessary. Other project management coordination will include:

• MnDOT State Aid – Separate from PMT meetings, the consultant will initiate and coordinate activities and reviews with MnDOT State Aid, including a State Aid project kickoff meeting and other coordination steps as advised by the consultant.

• Meeting Plan – The consultant’s proposal should address the assumed number and approximate scheduling of agency/group coordination meetings within this task or in other tasks below as appropriate.

• MnDOT Review – the consultant should assume various meetings for MnDOT review among the necessary working groups (GDSU, Traffic, ADA, Ped/Bike, etc) much like a MnDOT final design consultant contract requires.

• MnDOT File Storage - Store all deliverables in an organized electronic document management system and make deliverables available to the State’s project manager as needed whether the file is incomplete, in draft form, or the final deliverable by ProjectWise or email. This includes providing CAD files to the State’s project manager for use by the district functional groups.

• Web Page Updates – The consultant will provide information/content and graphics periodically for inclusion on the project webpage. It is likely that the County and MnDOT will both have project websites. The consultant may also propose hosting a project website.

http://www.dot.state.mn.us/design/qmp/index.html mailto:DCTransportation.Invoices@co.dakota.mn.us

RFP Attachment A – COUNTY PROJECT NO. 50-33 A-4

Task 2 – Public Involvement

2.1 Overall Task Requirements

This task will be organized to follow a consultant-prepared Public Involvement Plan (PIP), to leverage appropriate content from other tasks, and by using proven methods from similar projects to build understanding of design choices, develop consensus, overall awareness, project timeline, and other project changes. In general, the task should leverage the resources of the consultant and County/other staff to effectively contact, educate, and build trust with stakeholders. The consultant can assume the level of public involvement will be similar to a MnDOT interstate interchange project.

The PIP must include a program of meetings and support for:

• General public and property owner engagement – This work, will include meetings for the project area’s general public and smaller-group meetings in focus groups or with individual property owners to address project details.

• Technical or agency staff engagement – The technical review function will include meetings as specified in tasks often outside of Task 2, for example in Task 1 PMT meetings. The outreach plan must coordinate the timing of reviews with agency staff through various stages of project delivery and stakeholder input.

• Policy Maker Engagement – This least-frequent level of Task 2 engagement will include consultant support for engagement with elected representatives, including: the Lakeville City Council and members; the Dakota County Board and selected Commissioners;

state and federal legislators; and staffers working with elected officials as needed.

The consultant’s proposal should refine the Task 2 scope by providing an overall approach to public involvement to facilitate acceptance within the project schedule. The approach will involve many stakeholders in the proposed design, using efficient and creative communications tools and steps to both inform and meet in-person with as many project neighbors as possible, while representing Dakota County, the City of Lakeville, and MnDOT.

All public-facing content will follow applicable guidance on plain language and ADA accessibility standards as described in Attachment F: Digital Accessibility Requirements and at www.dot.state.mn.us/consult/adaplainlanguage.html. Dakota County Project Manager and Communications staff will maintain the County project website, with consultant support required to provide recommended content/attachments, updates, and links to consultant-hosted web tools as recommended in the PIP and in the final contract scope. Final approvals of public-facing content will be subject to reviews and approvals by Dakota County Transportation and Communications staff and other reviewers as needed.

Consultants may wish to modify the anticipated meetings and deliverables included in the descriptions below. Please note recommendations and assumptions in the proposal work plan.

2.2 Public Information Meetings

The consultant will develop and conduct an estimated three (3) general-public participation and input open-house style meetings (consultant proposals can outline alternative approaches). Public participation meeting project mailings and press releases will be necessary to promote the meetings. The consultant will prepare documents to be used for mailing and supply necessary handouts and presentation materials at the public meetings. The Consultant will package and mail all notices required and will provide notice to stakeholders through social media. They will provide content to MnDOT, the County, and the City to post on their websites or social media accounts.

2.3 Property Owner and Small-Group Meetings

The consultant will coordinate with Dakota County and the City of Lakeville to prepare for and conduct meetings with private property owners, business representatives, and others most affected http://www.dot.state.mn.us/consult/adaplainlanguage.html

RFP Attachment A – COUNTY PROJECT NO. 50-33 A-5 by the project. The consultant may propose the number and approach for small-group meetings with owners and stakeholders most directly impacted by the planned project. Meetings will be prioritized based on work phase, potential property impacts, and coordination needs to make project decisions. Opportunities to schedule meetings consecutively and with more than one stakeholder per meeting should be considered.

2.4 Stakeholder Outreach Content Support

In coordination with deliverables prepared for other tasks, the consultant will provide design drawings, exhibits, renderings, handouts, and layouts for use in the public involvement process.

The required deliverables for Task 2 include: