Final Design Plans for a Complete Plans, Specifications, and Estimates Submittal for SP 5508-130 and 2505-64

Location:	Minnesota
Posted:	Jun 29, 2026
Due:	Jul 28, 2026
Agency:	State Government of Minnesota
Type of Government:	State & Local
Category:	89 - Subsistence (Food)
Publication URL:	To access bid details, please log in.

Brief Description: S.P. 5508-130 is an Unbonded Concrete Overlay (UBOL) on southbound (SB) US 52, from the south junction of MN 60 to the 5th St. NW overpass (Br. 55079) in Oronoco. S.P. 2505-64 includes conversion of the existing SB US 52 Entrance ramp from the CSAH 11 Interchange in Pine Island. The proposed project will convert the existing southbound entrance ramp into a hybrid, two-way frontage road and freeway entrance ramp. This new, hybrid frontage road/entrance ramp allows for connectivity of properties and businesses to the CSAH 11 interchange, while allowing for closure of a direct access point along southbound US 52, while maintaining access to SB US 52. The project includes final design deliverables for a complete Plans, Specifications, and Estimates (P.S.&E.) submittal for State Projects (S.Ps). 5508-130 and 2505-64 for a December 1, 2027 Letting.

Date posted: 06/29/2026
Due date: 07/28/2026

Attachment Preview

MnDOT Contract No. 1063367

Exhibit A: Specifications, Duties, and Scope of Work

SP 5508-130/2505-64 (tied) SB US 52 UBOL and WFR Project

Table of Contents

1. Project Overview................................................................................................................................... 2

2. Project Management (Source Type 1010) ............................................................................................ 7

3. Public Engagement................................................................................................................................ 9

4. National Pollutant Discharge Elimination System (NPDES) Construction Stormwater (CSW) General

Permit.......................................................................................................................................................... 10

5. DNR Public Waters Permit (Source Code 1010).................................................................................. 11

6. Roadway Design Plans and Division S Special Provisions (Source Type 1250) ................................... 11

7. Supplemental Design Surveys (Source Code 1021) ............................................................................ 16

8. Transportation Management Plan (TMP) ........................................................................................... 17

9. Hydraulic Design (Source Code 1141)................................................................................................. 18

10. ADA Final Field walk and Design (Source Code 1250) ................................................................... 22

11. Traffic Control/Staging Plan (Source Code 1254) .......................................................................... 24

12. The Pavement Marking Plan (Source Code 1255) ......................................................................... 27

13. Signing Plan (Source Code 1255) ................................................................................................... 29

14. Lighting Plan (Source Code 1252) .................................................................................................. 33

15. Cost Share and Detour Agreement Support .................................................................................. 36

16. Project Turn-In (Source Code 1250)............................................................................................... 37

17. Utility Coordination (Source Code 1195) ....................................................................................... 39

18. Quality Management ..................................................................................................................... 42

MnDOT Contract No. 1063367

Exhibit A: Specifications, Duties, and Scope of Work

Scope of Work

1. Project Overview

1.1. Independent Contractor

1.1.1. The Contractor agrees it is acting in the role of an independent contractor. The Contractor, and

its employees and subcontractors, will not be considered employees of the State for any reason. The

Contractor acknowledges that it is responsible for its own financial control. The Contractor has

negotiated the payment for this contract with the State, which may result in a profit or loss for the

Contractor. The Contractor also acknowledges that it is responsible for the behavioral control of itself,

its operations, and its staff. The Contractor is solely responsible for determining the means, methods,

and sequence of performing the work covered by this contract. The State has included deliverable dates

in this contract, not to provide a “sequence” of work but because the State must coordinate these

deliverables with (1) the State’s financial plans, (2) other contracts managed by the State, and (3) work

performed by the State’s own staff. The parties have mutually drafted and agreed upon a scope of work.

The level of detail used to describe the work is intended only to establish minimum standards and

ensure consistency across the hundreds of projects managed by the State; the Contractor remains

responsible for determining the means and methods of performing the work to meet or exceed those

requirements. The State will not directly supervise the Contractor’s work but will provide oversight and

monitoring, as required by Minnesota Statutes §16C.08 and 23 CFR Part 172.5, to ensure compliance

with the terms, conditions, and specifications of this contract. At the conclusion of this contract, the

State will evaluate the Contractor’s performance under this contract for potential use in future

evaluations and selections as required by Minnesota Statutes §16C.08 and 23 CFR Part 172.5.

1.2. General Statement of Scope of Work

The project includes final design deliverables for a complete Plans, Specifications, and Estimates

(P.S.&E.) submittal for State Projects (S.Ps). 5508-130 and 2505-64 for a December 1, 2027 Letting. The

two aforementioned S.P.s are to be delivered as TIED plan set for a single contract letting under a

COMPLEX B plan turn-in process. The Final Plan Set deliverable will include (but are not limited to): Final

Road Plans (grading and surfacing); Hydraulic/Water Resources Plans ; ADA Plans; Staging and Traffic

Control Plans; Signing Plans; Lighting Plans; Utility Plans; Noisewall Plans; Environmental Management

Plan (EMP); and Stormwater Pollution Prevention Plans (SWPPP)

Final Bridge Plans for Br. 25X12 and Br. 55079 Repair Plans will be furnished by the MnDOT Bridge

Office.

1.3. Project Background

S.P. 5508-130 is an Unbonded Concrete Overlay (UBOL) on southbound (SB) US 52, from the south

junction of MN 60 to the 5th St. NW overpass (Br. 55079) in Oronoco.

S.P. 2505-64 includes conversion of the existing SB US 52 Entrance ramp from the CSAH 11 Interchange

in Pine Island. The proposed project will convert the existing southbound entrance ramp into a hybrid,

two-way frontage road and freeway entrance ramp. This new, hybrid frontage road/entrance ramp

allows for connectivity of properties and businesses to the CSAH 11 interchange, while allowing for

closure of a direct access point along southbound US 52, while maintaining access to SB US 52.

1.4. Web-Based Teleconferencing

1.4.1. The Contractor must provide the means for the project team to meet via web-based

teleconferencing that allows participants to view the desktop of the meeting organizer. Participants

MnDOT Contract No. 1063367

Exhibit A: Specifications, Duties, and Scope of Work

must be able to “take control” of the virtual desktop as needed to point out things on the file being

displayed. Voice communication may occur via computer or phone.

1.5. Source Type Codes and P6 Activity Codes

1.5.1. Every deliverable must list a P6 activity code that matches the P6 activity in the P6 schedule.

The Contractor may 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.

1.5.2. If requested by the State's Project Manager, every deliverable must list a source type code.

The source type code may be used in the Contractor’s invoice to subtotal the deliverables together

under that source type code.

1.5.3. The Contractor is not required to know how to use Primavera P6 (P6) or work within the

program itself unless stated in Project Management section. The Contractor is, however, expected to

understand the concept of Critical Path Method scheduling, understand hardcopy reports printed by the

P6 schedule, update the hardcopy reports, and recommend changes to the schedule to reflect changes

in the scope or flow of work.

1.6. Milestones and Contract Completion Timeline

• Design Quality Management Plan Submittal…………………………….20 working days after NTP

• 30% Plan Submittal………………………………………………………………..November 16th, 2026

• 60% Plan Submittal………………………………………………………………..March 9th, 2027

• 90% Plan (District Review) Submittal……………………………………..June 24th, 2027

• 95% Plan Submittal………………………………………………………………..August 16th, 2027

• Post Turn-in/Construction Phase Support……………………………….December 15th, 2029

1.7. Format of Deliverables

1.7.1. Plain Language

a. All documents or exhibits specifically designed to be used by the public must be developed in “plain

language.” Executive Order 14-07 requires the Office of the Governor and all Executive Branch agencies

to communicate with Minnesotans using plain language and defines plain language as a communication

that an audience can understand the first time they read or hear it. Additional information is available at

ADA Plain Language. To meet the requirements of this executive order, the Contractor will:

i. Use language commonly understood by the public

ii. Write in short and complete sentences

iii. Present information in a format that is easy to find and easy to understand

iv. Clearly state directions and deadlines to the audience

b. Technical documents, presentations, spreadsheets, and drawings used by technical staff do not

need to be in plain language.

1.7.2. Accessibility Standards

1.7.3. Software

a. Report source files must be in current versions of Microsoft Word and Microsoft Excel. Files must

be delivered to the State by email. For very large files, the Consultant may need to post the files to the

ProjectWise folder(s) established for the project.

MnDOT Contract No. 1063367

Exhibit A: Specifications, Duties, and Scope of Work

b. CADD deliverable source files must meet the State’s Level 2 Enhanced CADD Data Delivery

Specifications.

c. All applicable spatial data and maps created in Geographic Information System (GIS) software must

be provided in a standard shapefile format (.shp) that is compatible with current versions of ArcMap

software.

d. All source files also must be converted to Adobe Acrobat (.pdf extension), and the PDF must be

searchable, with scanned pages eliminated except for signature pages.

1.7.3.2. The Contractor must comply with the State of Minnesota’s Accessibility Standards for all

documents or exhibits specifically designed to be used by the public. The State of Minnesota’s

Accessibility Standards are based on 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

Accessibility/Accommodations and include:

a. Providing interpreters, translators, or other special accommodation.

b. Providing documents in an alternative format.

c. Following the PDF accessibility guidance.

1.7.3.3. The State of Minnesota’s Accessibility Standard also includes:

a. All videos must include closed captions, audio descriptions, and a link to a complete transcript.

b. All documents, presentations, spreadsheets, drawings, and other material must be provided in an

accessible format. Native files must be provided in an editable format. Acceptable formats include

InDesign, Word, and Excel.

c. All materials intended for downloading and printing must be labeled as such, and the content must

be provided in an accessible format.

1.7.3.4. Technical documents, presentations, spreadsheets, and drawings used by technical staff do

not need to comply with the State of Minnesota’s Accessibility Standard.

1.7.3.5. All outward-facing Microsoft Word documents to be used during the project must be designed

with Americans with Disabilities Act (ADA)-accessible features, including alt text and screen-reader

compatibility.

1.7.4. All deliverables must be provided in electronic file format.

1.8. Standards and Guidance

1.8.1. All design must be conducted by or under the direct supervision of a Professional Engineer

licensed in Minnesota.

1.8.2. All survey work must be conducted by or under the direct supervision of a Professional Land

Surveyor.

1.8.3. All design work must be done in conformance with the current version of State approved

CADD standards (currently Bentley OpenRoads Designer CONNECT edition 25.00.00.184), following

Level 2 Enhanced CADD Data Delivery Specifications. Further details can be found at

https://www.dot.state.mn.us/digital-delivery/cadd.html

1.8.4. The Contractor will incorporate the State’s current digital delivery standards (P-SED) into all

applicable design and plan development tasks. This includes preparation of required digital models,

exchange data, and plan sheets in accordance with the latest MnDOT Guide for Digital Delivery of

Project-Specific Electronic Data (P-SED). All digital deliverables shall be considered contractual and must

meet MnDOT’s Level 2 Enhanced CADD Data Delivery Specifications.

MnDOT Contract No. 1063367

Exhibit A: Specifications, Duties, and Scope of Work

1.8.5. All field data must be provided in Global Information/Positioning Systems (GIS/GPS)/County

Coordinates – NAD83 (1996) County Datum and NAVD 88 vertical datum Bentley OpenRoads Designer

CONNECT edition 25.00.00.184), and Microsoft Excel/Word formats.

1.8.6. Failure of this scope of work to list a specific standard under a specific deliverable does not

absolve the Contractor’s obligation to comply with all laws, regulations, and standards that apply to

highway projects within the State of Minnesota. The Contractor must 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

the State.

1.8.7. Websites have been supplied to the Contractor for some of the standards and guidance

documents listed for convenience only in an effort to help the Contractor locate the required standard

or guidance. The websites are not guaranteed to be correct. It is ultimately the Contractor’s

responsibility to locate the required standard and to determine if the standard has been modified

pursuant to this Contract.

1.8.8. All deliverables must be prepared in accordance with MnDOT Transportation Project

Development Process (TPDP).

1.8.9. Additional requirements for standards may be provided within the scope tasks that follow.

1.9. Items Provided by the State

1.9.1. The State will provide the following items. Some items must be provided at notice to proceed.

Other items are developed as the project progresses. The Contractor is responsible for requesting the

needed information when it is available during the project development

a. As-built plans (if available)

b. Base mapping: topography, tin, DTM, right-of-way, property lines

c. MicroStation files of base mapping, cross-sections, utilities, detail design plans/layout and

construction plans

d. Existing alignment/survey

e. Construction limits

f. Project limits

g. Right-of-way information

h. Proposed right-of-way acquisition map

i. Pavement recommendations and material design recommendations

j. Sample plan

k. Example or existing Stormwater Pollution Prevention Plan (SWPPP) and title sheet

l. Project scoping document

m. Staff approved layout with design memo

n. Special provisions template and guidance information

o. Required agreements

p. In-place lighting plans

q. Traffic data and available traffic analyses/studies

i. MnDOT Traffic Engineering Manual

ii. Minnesota Manual on Uniform Traffic Control Devices (MN MUTCD)

iii. State StreetLight license

This is the opportunity summary page. It provides an overview of this opportunity and a preview of the attached documentation.

Daily notification on new contract opportunities

With GovernmentContracts, you can:

Find more opportunities and win more business
Receive daily alerts for all new bid opportunities
Get contract opportunities matched to your business

ONE WEEK FREE TRIAL

Final Design Plans for a Complete Plans, Specifications, and Estimates Submittal for SP 5508-130 and 2505-64

Attachment Preview

See also