Final Design, SP 2735-212 TH 100

Location:	Minnesota
Posted:	Aug 4, 2026
Due:	Aug 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.

Attachment Preview

MnDOT Contract No. 1063872

Exhibit C: Specifications, Duties, and Scope of Work

1. Project Overview

1.1. Independent Contractor

1.1.1.

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

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

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

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

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

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

methods, and sequence of performing the work covered by this contract. 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. State will not

directly supervise the Contractor’s work but will provide oversight and monitoring, as required

by Minnesota Statutes §16C.08 and 23 Code of Federal Regulations (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.

Conduct all work necessary to: prepare 100 percent and Final 100 percent Project Plans

including roadway design, Americans with Disabilities Act (ADA) design, traffic signal design,

signing design, lighting design, pavement marking design, traffic control design, hydraulics

design, drainage plans, stormwater pollution prevention plans; prepare project permits; provide

simulation modeling of staging alternatives and coordinate development of traffic control and

staging plan; provide construction support.

1.3. Project Background

1.3.1. State Project (SP) 2735-212 is a roadway and bridge rehabilitation project along Trunk Highway

(TH) 100 in Hennepin County with a scheduled letting date of March 22, 2028. Construction

would begin Summer 2028 and extend through 2029.

1.3.1.1. The primary work type is roadway rehabilitation, with work including bituminous mill and

overlay, concrete pavement rehabilitation, bridge rehabilitation, traffic signal replacement, and

sidewalk and curb ramp reconstruction. The project also includes the removal of bridge 27042

and the southbound access to John Martin Drive in Brooklyn Center.

1.3.1.2. The primary work type on bridges 27039, 27040, 27754, 27754A, 27788, 27789, 27789A, and

27960 is a deck mill and overlay. The primary work type on bridges 27752 and 27752A is a deck

flood seal with joint replacement. The primary work type of bridges 27913, 27914, and 27982

are deck replacement.

1.4. Web-Based Teleconferencing

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

MnDOT Contract No. 1063872

Exhibit C: Specifications, Duties, and Scope of Work

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 and Primavera (P6) Activity Codes

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

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

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

that source type.

1.5.3.

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

itself unless stated in Project Management section. 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

1.6.1. The late start and the late finish dates included in the project schedule are the contractual due

dates for this contract. See attached project schedule.

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 either email or FTP.

b. Computer Aided Design and Drafting (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.

MnDOT Contract No. 1063872

Exhibit C: Specifications, Duties, and Scope of Work

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

Portable Document Format (PDF) must be searchable, with scanned pages eliminated

except for signature pages.

1.7.3.1.

Contractor must comply with the MnDOT of Minnesota’s Accessibility Standards for all

documents or exhibits specifically designed to be used by the public. MnDOT 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.3.2. 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.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.3.4. All outward-facing Microsoft Word documents to be used during the project must be designed

with 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 current State Bentley OpenRoads Designer

CE standards, following Level 2 Enhanced CADD Data Delivery Specifications.

1.8.4.

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

Coordinates – NAD83(2011) County Datum and NAVD 88 vertical datum, MicroStation

OpenRoads Designer 2025, and Microsoft Excel/Word formats.

1.8.5.

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. 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.6. Websites have been supplied to the Contractor for some of the standards and guidance

MnDOT Contract No. 1063872

Exhibit C: Specifications, Duties, and Scope of Work

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.7. All deliverables must be prepared in accordance with State Transportation Project

Development Process (TPDP).

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

1.8.9. State uses the Primavera P6 scheduling tool. Scheduling deliverables must be compatible with

P6 format and work package dictionary.

1.9. Items Provided by the State

1.9.1.

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

Other items are developed as the project progresses. 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. Existing design files including CAD files, model files, excel files, and other files as

developed prior to the 60% submittal

f. Staff approved layout

g. Construction limits

h. Project limits

i. Right-of-way information

j. Proposed right-of-way acquisition map

k. Pavement recommendations and material design recommendations

l. Sample plan

m. Current Guide for Digital Delivery of Project-Specific Electronic Data (P-SED) Guide-

Digital-Delivery-P-SED-20251107-ADA-38665265-v9

n. 60% Plan and 60% Plan Comments

o. Example or existing/draft Stormwater Pollution Prevention Plan (SWPPP) and title

sheet

p. Project scoping document

q. Staff approved layout with design memo

r. Special provisions template and guidance information

s. Required agreements

t. District-modified standard detail sheets

u. In-place lighting plans

v. In-place signal plans

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

x. TMS plans and specifications

MnDOT Contract No. 1063872

Exhibit C: Specifications, Duties, and Scope of Work

y. Time and Traffic specifications

z. Process B project submittal letter template

aa. Foundations recommendations

bb. ADA design recommendations

cc. Final plans for completed projects on the corridor

dd. State risk register template

ee. State lighting records

ff. State signing records

gg. State TMS records

hh. Transportation Asset Management System (TAMS)

ii. State survey request form

jj. Geotechnical investigation including borings

kk. Materials design recommendation including borings

ll. Existing soil boring information

mm. Soil borings and foundation recommendations

nn. Existing drainage systems plans

iv. Hydinfra inventory table and map of existing drainage system with asset

information including material type, dimensions, coordinates, and condition

ratings

v. GIS shapefiles of storm drainage features in the project area that have been

recorded in the TAMS Hydinfra database

vi. Known existing drainage flooding and erosion issue areas

vii. Piezometers and groundwater elevation data

viii. Borings of pond, infiltration, or filtration locations

2. Project Management (Source Type 1010)

2.1. Project Coordination and Administration (P6 Activity Code OPM1000)

2.1.1.

Project management includes work necessary for communicating and completing the project

tasks on time and within budget. Contractor must not reassign the project manager or their

primary duties without the written consent of the State’s project manager. The Contractor’s

staff must have the training and expertise necessary for the work tasks to which they are

assigned.

2.1.2. Meeting summaries must be submitted no later than one business day after each meeting and

a final meeting summary must be submitted no later than three business days after receiving

comments on summary notes.

2.1.3. Contractor will:

a. Prepare invoices accompanied by:

i. A cover letter explaining the general status of the project, including at a

minimum the work completed to date, the anticipated remaining efforts, and

required schedule changes

ii. Progress report form

iii. Supporting data for direct expenses

iv. An updated project status report reflecting P6 activities identified by the

State’s project manager

b. Manage, coordinate, direct, and monitor subcontractor services, including reviewing

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

Final Design, SP 2735-212 TH 100

Attachment Preview

See also