Design for Reconstruction of TH 16 Through Houston and Replacement of Bridge 95111

Location:	Minnesota
Posted:	Jan 7, 2026
Due:	Feb 5, 2026
Agency:	State Government of Minnesota
Type of Government:	State & Local
Category:	C - Architect and Engineering Services - Construction Y - Construction of Structures and Facilities
Publication URL:	To access bid details, please log in.

Attachment Preview

MnDOT Contract No. 1061542

State Project 2801-90

Exhibit C: Specifications, Duties, and Scope of Work

Table of Contents

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

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

3. Quality Management Plan (Source Type 1010) ................................................................................. 12

4. Stakeholder and Public Involvement (Source Type 0054) ................................................................. 13

5. Base Mapping/Data Gathering (Source Type 1021)........................................................................... 18

6. Traffic Engineering for Scoping (Source Type 1015) .......................................................................... 19

7. Conceptual Geometric Design Development (Source Code 1140) .................................................... 21

8. Bridge Scoping (Source Code 1003 .................................................................................................... 24

9. Project Scoping Report (Source Code 1003) ...................................................................................... 25

10. Wetland Delineation (Statewide) (Source Type 1071) .................................................................. 25

11. Programmatic Categorical Exclusion (Source Code 1071) ............................................................. 28

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

General Permit ............................................................................................................................................ 29

13. Traffic Counts (Source Code 1014) ................................................................................................ 30

14. Design Memorandum/Exceptions/Completion of Complete Streets Documentation (Source Code

1150) 32

15. Transportation Management Plan (TMP) ...................................................................................... 33

16. Staff-Approved Layout (Source Code 1140) .................................................................................. 36

17. Construction Limits (Source Code 1200) ....................................................................................... 38

18. Municipal Consent (Source Type 1140) ......................................................................................... 39

19. Roadway Design Plans and Division S Special Provisions (Source Type 1250) .............................. 40

20. Stormwater Design (Source Code 1141)........................................................................................ 45

21. Hydraulic Design (Source Code 1141)............................................................................................ 51

22. ADA Design (Source Code 1250) .................................................................................................... 53

23. Visual Quality Summary (Source Code 1071) ................................................................................ 54

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

25. Pavement Marking Plan (Source Code 1255) ................................................................................ 61

26. Signing Plan (Source Code 1255) ................................................................................................... 62

27. Lighting Plan (Source Code 1252) .................................................................................................. 66

28. Project Turn-In (Source Code 1250)............................................................................................... 69

29. Utility Coordination (Source Code 1195) ....................................................................................... 72

MnDOT Contract No. 1061542

Design for Reconstruction of TH 16 Through Houston and Replacement of Bridge 95111

State Project 2801-90

Exhibit C: 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

1.2.1.

The State is in need of a professional, technical assistance for project scoping, preliminary

design, and detail design for the reconstruction of Minnesota Trunk Highway (TH) 16

through the city of Houston and the replacement of Bridge #95111. The project includes,

but is not limited to, project scoping following the State’s scoping process (MnDOT Scoping

Process), conceptual geometric design development, project management, public and

stakeholder engagement and coordination, base mapping/data gathering, traffic

engineering for scoping, traffic counts, environmental studies, environmental

documentation, construction limits, design memorandum, intersection control evaluation,

preliminary and final level 1 geometric layout, preliminary and detail drainage design,

traffic management plan, highway design, bridge design, traffic engineering, Americans

with Disabilities Act (ADA) design, lighting design, signing design, pavement marking design,

utility coordination, special provisions, construction plans, and construction support.

1.3. Project Background

The project begins on Trunk Highway (TH) 16, approximately 0.16 miles west of the

Houston city limits, just east of Poppe Road (Reference Point 268+00.832). It continues

through the city of Houston and ends at Bridge #95111, located 0.12 miles east of the

intersection of TH 16 and TH 76 (Reference Point 270+00.622). The existing pavement on

Page 2 of 75

MnDOT Contract No. 1061542

Design for Reconstruction of TH 16 Through Houston and Replacement of Bridge 95111

State Project 2801-90

Exhibit C: Specifications, Duties, and Scope of Work

TH 16 is in poor condition. According to the transportation project charter, the scope

includes resurfacing approximately 0.5 miles of pavement both east and west of the city.

Within the city limits of Houston, TH 16 is designated for full urban reconstruction. This

work will be guided by a complete streets safe systems approach, ensuring that all users

are considered in the design and function of the roadway. The eastern terminus of the Root

River Trail is located just north of this highway segment, and the D6 Bicycle Plan prioritizes

a future trail connection between the Root River Trail and La Crescent. As such, bicycle

facilities on TH 16 will be evaluated as part of the project.

Drainage issues within the city are known and will be addressed during construction.

Additionally, the city of Houston will coordinate replacement of municipal sewer and water

utilities as part of the project. Early and ongoing engagement with the city and other

stakeholder groups will be essential during both the project scoping and final design

phases.

At the eastern end of the project, Bridge #95111—a double aluminum arched culvert with

concrete headwalls—will be replaced.

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 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

State Project 2801-90 is scheduled for letting on October 23, 2030. The Contractor will submit

deliverables to meet the following milestones:

Scoping Stakeholder Engagement Meeting #1 (PRM1035)....................April 23, 2026

Conduct Scoping Meeting #2 (MS310).................................................... May 28, 2026

Conduct Scoping Meeting #3 (MS320).............................................. October 15, 2026

Page 3 of 75

MnDOT Contract No. 1061542

Design for Reconstruction of TH 16 Through Houston and Replacement of Bridge 95111

State Project 2801-90

Exhibit C: Specifications, Duties, and Scope of Work

Scoping Document Complete (MS175) ........................................... December 3, 2026

Inform Stakeholders of Final Scope (PRM2010) ..................................January 7, 2027

Conduct Schedule Concurrence Meeting (MS330)..........................February 16, 2027

Conduct Project Design Kick off Meeting (PMM1010) ........................March 16, 2027

Prepare Preliminary Design Memo (DME1000)...................................... May 11, 2027

Geometric Layout Initiation Meeting (LAY1030) ......................................June 3, 2027

Public Meeting #1 (STK1000) ................................................................ August 5, 2027

Submit Preliminary Geometric Layout & Profile (LAY1040) ........ September 14, 2027

Determine Preliminary Staging (TMP0900) .................................... November 9, 2027

Submit Final Geometric Layout & Profile (LAY1050) .......................February 24, 2028

Submit Final Construction Limits (LIM1020)........................................March 23, 2028

Public Meeting #2 (STK1010) ..................................................................April 13, 2028

Layout Approved (MS185) ...................................................................... May 25, 2028

Construction Limits Approved (LIM1050) ............................................... May 25, 2028

Submit 30% Roadway Plans (PLN3000) .............................................February 6, 2029

Environmental Document Approved (MS150).....................................March 22, 2029

Submit 60% Roadway Plans (PLN6000) .............................................. August 30, 2029

Public Meeting #3 (STK1020) ........................................................ December 11, 2029

Submit 90% Roadway Plans (PLN9000) ...............................................January 8, 2030

Submit 95% Roadway Plans (PLN9500) ...............................................March 19, 2030

Conduct District and CO Turn In Meeting (TUR2050) ............................. May 15, 2030

State’s Central Office Final Plan Turn In (TUR2090) ............................. August 8, 2030

1.6.1.

The P6 project schedule will be used for contractual due dates. The late start and the late

finish dates included in the project schedule are the contractual due date deadlines for this

contract. The Contractor agrees to collaborate with the State’s project Manager to

maintain a buffer of project float during project development. Project float is defined as the

difference between the Early and Late Finish dates in the P6 project schedule. Project float

of 20 to 40 days minimum for tasks early in the project schedule will be maintained while

float will be gradually reduced to single digits by the final project tasks.

1.7. Format of Deliverables

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

1.7.2. Software

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

Excel. Files must be delivered to the State by Bentley ProjectWise Explorer.

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.

Page 4 of 75

MnDOT Contract No. 1061542

Design for Reconstruction of TH 16 Through Houston and Replacement of Bridge 95111

State Project 2801-90

Exhibit C: Specifications, Duties, and Scope of Work

1.7.3. 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.4. Accessibility Standards

1.7.4.1. 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 accommodations.

b. Providing documents in an alternative format.

c. Following the PDF accessibility guidance.

1.7.4.2. 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.4.3. 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.4.4. 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.5. All deliverables must be provided in electronic file format.

Page 5 of 75

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

Design for Reconstruction of TH 16 Through Houston and Replacement of Bridge 95111

Attachment Preview

See also