MnDOT Contract No. 1061785
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 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.
This contract includes preliminary and final highway design for State Projects (SP) 6917-149
(Trunk Highway (TH) 53 Northbound (NB) Bridge Replacement over Saint Louis River) and
SP 6917-155 (TH 53 / County State Aid Highway (CSAH) 16 Reduced Conflict Intersection
(RCI)). Preliminary design will include preparation of a Level 1 geometric layout related to
the bridge replacement which will require a vertical alignment grade raise and the
proposed RCI. Final design will include preparation of Construction Limits Map,
Contaminated Materials Management Team (CMMT) Coordination Map, and project final
design milestone submittals (30%, 60%, 90%, 95% and 100% design submittals). The
Contractor’s tasks under this contract will include, but are not limited to, project
management, approved geometric layout, construction limits, preliminary and final
roadway design, lighting design, stormwater design, temporary traffic control plans,
National Pollution Discharge Elimination System (NPDES) permit, pavement marking plans,
signing plans, utility coordination, public engagement support, environmental
documentation, traffic engineering study, special provisions, cost estimating, and
construction design support.
State’s Bridge Office will be responsible for the structural design of the replacement bridge.
The Contractor will be responsible for the roadway design of approaches, approach panels,
geometrics, drainage, traffic control, construction staging plans and permitting exhibits
necessary to facilitate both roadway and bridge construction, as well as all other non-
structural elements. The Contractor shall coordinate with the Bridge Office throughout pre-
design and plan development stages to ensure compatibility between roadway and
structural bridge design elements.
1
MnDOT Contract No. 1061785
Exhibit A: Specifications, Duties, and Scope of Work
1.2.1.1. For SP 6917-149, the proposed project includes:
a. Remove existing Bridge 6602.
b. Construct new three span bridge 69146 over Saint Louis River. Proposed bridge
structure assumes an approximate 3-ft grade raise to TH 53 NB.
c. Reconstruct TH 53 NB bridge approaches to accommodate grade raise.
d. Utilize inplace cross-overs north and south of inplace bridge to facilitate
construction. Remove cross-overs at the conclusion of the project.
e. Provide traffic control and staged construction to complete both projects in a
single construction season.
f. Provide new ditching, culvert and storm sewer revisions to accommodate removal
of inplace cross-overs and rehabilitate existing culverts.
g. Replace all signs within the project limits.
h. Provide centerline and shoulder rumble strips.
i. Provide new pavement markings.
j. Remove and replace existing guardrail.
1.2.1.2. For SP 6917-155, the proposed project includes:
a. Construct new RCI at the intersection of TH 53 and Townline Road / Ellsmere Road
(CSAH 16 / Unorganized Territory (UT) 9132). RCI is anticipated to include
pedestrian and All-Terrain Vehicle/snowmobile trail crossing across TH 53.
b. Re-align Townline Road / Ellsmere Road approaches and reconstruct/re-align
adjacent multi-use trail affected by project.
c. Provide intersection lighting at the RCI.
d. Provide traffic control and staged construction to complete both projects in a
single construction season.
e. Provide new ditching, culvert and storm sewer revisions to accommodate removal
of inplace cross-overs within the project limits and the new RCI.
f. Replace all signs within the project limits. Provide new signage to accommodate
the new RCI configuration.
g. Provide centerline and shoulder rumble strips.
h. Provide new pavement markings.
1.3. Web-Based Teleconferencing
1.3.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.4. Source Type Codes and Primavera P6 (P6) Activity Codes
1.4.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.4.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.4.3. The Contractor is not required to know how to use P6 or work within the program itself
unless stated in Project Management section. The Contractor is, however, expected to
2
MnDOT Contract No. 1061785
Exhibit A: Specifications, Duties, and Scope of Work
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.5. Milestones and Contract Completion Timeline
Final Geometric Layout (LAY1050)
August 12, 2026
Final Construction Limits (LIM1020)
October 21, 2026
Final CMMT Work Map for Drilling (ESA0900)
October 28, 2026
30% Detailed Design Submittal (PLN3000)
April 12, 2027
60% Detailed Design Submittal (PLN6000)
September 2, 2027
90% Detailed Design Submittal (PLN9000)
January 31, 2028
95% Submittal Design Submittal (PLN9500)
April 4, 2028
Plan Turn-In (MS230)
May 2, 2028
Letting (MS270)
September 27, 2028
1.6. Format of Deliverables
1.6.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 Americans with Disabilities Act (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.6.2. Accessibility Standards
1.6.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 or ProjectWise
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.
3
MnDOT Contract No. 1061785
Exhibit A: Specifications, Duties, and Scope of Work
d. All source files also must be converted to Adobe Acrobat (Portable document
format (.pdf) extension), and the PDF must be searchable, with scanned pages
eliminated except for signature pages.
1.6.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 accommodations.
b. Providing documents in an alternative format.
c. Following the PDF accessibility guidance.
1.6.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.6.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.6.3.5. 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.6.4. All deliverables must be provided in electronic file format.
1.7. Standards and Guidance
1.7.1. All design must be conducted by or under the direct supervision of a Professional Engineer
licensed in Minnesota.
1.7.2. All survey work must be conducted by or under the direct supervision of a Professional
Land Surveyor.
1.7.3.
All design work must be done in conformance with current State Bentley OpenRoads
Designer (ORD) Connect Edition (CE) standards, following Level 2 Enhanced CADD Data
Delivery Specifications.
1.7.4.
All field data must be provided in GIS/Global Positioning Systems (GPS)/County Coordinates
– the North American Datum of 1983 (NAD 83) (1996) County Datum and the North
American Vertical Datum of 1988 (NAVD 88) vertical datum (check with District Surveys
staff for correct datums), current Bentley ORD CE standards, and Microsoft Excel/Word
formats.
1.7.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. The Contractor must comply with
4
MnDOT Contract No. 1061785
Exhibit A: Specifications, Duties, and Scope of Work
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.7.6.
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.7.7. All deliverables must be prepared in accordance with the State Transportation Project
Development Process (TPDP).
1.7.8. Additional requirements for standards may be provided within the scope tasks that follow.
1.7.9. The State uses the P6 scheduling tool. Scheduling deliverables must be compatible with P6
format and work package dictionary.
1.8. Items Provided by the State
1.8.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. Base mapping: topography, Triangulated Irregular Network (tin), Digital Terrain
Model (DTM), right-of-way, property lines
b. MicroStation files of base mapping, cross-sections, utilities, detail design
plans/layout and construction plans
c. Proposed right-of-way acquisition map
d. Pavement recommendations and material design recommendations
e. Sample plan
f. Example or existing/draft Stormwater Pollution Prevention Plan (SWPPP) and
title sheet
g. Project scoping document
h. Special provisions template and guidance information
i. Required agreements
j. Wetland delineation report and permitting
k. Early Notification Memo (ENM)
l. District-modified standard detail sheets
m. Time and Traffic specifications
n. Process B project submittal letter template
o. Draft ADA design recommendations
p. State signing records
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. The Contractor must not reassign the project
5
This is the opportunity summary page. It provides an overview of this opportunity and a preview of the attached documentation.