MnDOT Contract Number: 1062474
Exhibit A: Specifications, Duties, and Scope of Work
Preliminary and Final Design for State Project (SP) 4705-51
Project Overview
Independent Contractor
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.
Project Background
The intersection of Trunk Highway (TH) 12 and County State Aid Highway (CSAH) 34 in the City of
Litchfield has recently been reviewed with an Intersection Control Evaluation (ICE) Study with Meeker
County, City of Litchfield, and State. The recommendation coming out of the study is a single lane
roundabout (RAB).
General Statement of Scope of Work – The purpose of this contract is to provide the State with Project
development and deliverables needed to bring SP 4705-51 to letting on schedule. The products and
services needed for this project include but are not limited to; project management, public and agency
involvement, geometric layout, construction limit roll plot, environmental studies, traffic engineering,
design surveys, hydraulics engineering, utility coordination, ADA detailed design, detailed design,
environmental permits, post-letting construction design support, quality control management, and
subsurface utility engineering.
Web-Based Teleconferencing
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
1
MnDOT Contract Number: 1062474
Exhibit A: Specifications, Duties, and Scope of Work
control” of the virtual desktop as needed to point out things on the file being displayed. Voice
communication should occur via computer but may be by phone upon request if suitable for the entire
team.
Format of Deliverables
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.
2. Accessibility Standards
A) 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:
I. Providing interpreters, translators, or other special accommodations.
II. Providing documents in an alternative format.
III. Following the PDF accessibility guidance.
B) The State of Minnesota’s Accessibility Standard also includes:
I. All videos must include closed captions, audio descriptions, and a link to a complete
transcript.
II. 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.
III. All materials intended for downloading and printing must be labeled as such, and
the content must be provided in an accessible format.
C) Technical documents, presentations, spreadsheets, and drawings used by technical staff do
not need to comply with the State of Minnesota’s Accessibility Standard.
D) 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.
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.
2
MnDOT Contract Number: 1062474
Exhibit A: Specifications, Duties, and Scope of Work
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 ArcGIS Pro 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.
E) All deliverables must be provided in electronic file format.
Standards and Guidance
1. All design work must be conducted by or under the direct supervision of a Professional Engineer
licensed in Minnesota.
2. All survey work must be conducted by or under the direct supervision of a Professional Land
Surveyor licensed in Minnesota.
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.
4. All field data must be provided in GIS/Global Positioning System (GPS)/County Coordinates –
NAD83 (1996) or NAD83 (2011) County Datum and NAVD 88 vertical datum (check with District
Surveys staff for correct datums), current State Bentley OpenRoads Designer CE standards, and
Microsoft Excel/Word formats.
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 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.
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.
7. All deliverables must be prepared in accordance with the Minnesota Department of
Transportation (MnDOT) Transportation Project Development Process (TPDP).
8. Additional requirements for standards may be provided within the scope tasks that follow.
9. State uses the Primavera P6 (P6) scheduling tool. Scheduling deliverables must be in line with P6
format and work package dictionary.
3
MnDOT Contract Number: 1062474
Exhibit A: Specifications, Duties, and Scope of Work
Section 1.0 – Project Management (Source Type 1010)
1.1 - Project Kickoff Meeting – The Contractor will coordinate and conduct a Project Kickoff Meeting via
Microsoft Teams. The purpose of the meeting will be to establish communications protocol, and
ProjectWise folder structure. The project team will also discuss known issues, immediate deliverable
needs and schedule.
Prior to the meeting:
1. The State will provide available deliverables for the contractor to review. The contractor will
then provide and discuss additional needs at the meeting.
2. The Contractor will provide a schedule prior to the meeting for the State to review and
discuss at the meeting.
3. The State’s Project Manager and Design Manager will create a list of key contacts for each
District Functional Group and provide it to the Contractor. Key contacts will be included on
all review and comment resolution meetings. The key contacts list will be updated as
needed prior to each review and comment resolution meeting request.
4. The Contractor will provide the list of key team members that will be working on the
project.
The Contractor will also prepare and distribute draft meeting minutes within 2 business days after the
meeting and final meeting minutes within 2 business days after receiving State’s comments on the draft
minutes.
1.2 - Public Engagement Kickoff Meeting- The Contractor will coordinate and conduct a Public
Engagement Kickoff Meeting via Microsoft Teams. The meeting will discuss the team’s approach to the
project specific public engagement. This meeting will also be used to develop a list of key stakeholders
and businesses and develop a strategy of communication. The Contractor will prepare and distribute the
draft meeting minutes within 2 business days after the meeting and final meeting minutes within 2
business days after receiving State’s comments on the draft minute
1.3 - Project Management Team (PMT) Meetings – Contractor will coordinate and conduct PMT
Meetings. Tasks include agenda preparation, meeting facilitation, follow-up, and a summary of activities
and outcomes from each meeting. Meetings will be conducted via Microsoft Teams unless otherwise
approved by the State’s Project Manager. Tasks also include routine communications, including biweekly
Microsoft Teams meetings with the State’s Project Manager, Design Manager, and other functional
groups as needed which will include agenda and meeting minutes. The Contractor will also prepare and
distribute draft meeting minutes within 2 business days after each meeting and final meeting minutes
within 2 business days after receiving State’s comments on the draft minutes. Contractor will evaluate
the need to add meetings to resolve project or design decisions, as approved by the State’s Project
Manager.
1.4 - Geometric Layout Review Meetings – Contractor will coordinate and conduct a geometric layout
handoff meeting to discuss preliminary layout work completed to date along with approximately six
4
MnDOT Contract Number: 1062474
Exhibit A: Specifications, Duties, and Scope of Work
additional Geometric Layout Review Meetings. Due to the complexity of roundabout development, the
Contractor should anticipate over the shoulder review meetings as well. The meetings will take place via
Microsoft Teams. The Contractor will also prepare and distribute draft meeting minutes within 2
business days after each meeting and final meeting minutes within 2 business days after receiving
State’s comments on the draft minutes.
1.5 - Hydraulic Review Meetings – Contractor will coordinate and conduct Hydraulic Review Meetings
as soon as possible after the execution of the contract, starting with existing hydrology and hydraulics
and moving into proposed hydrology and hydraulics once the conceptual geometric layout has been
completed. The proposed hydraulics will coincide with the Geometric Layout Review Meetings and
continue through the construction limit roll plots and plan sheet submittals. During the hydraulic review
meetings, the Contractor and State will discuss needed hydraulic changes. The meetings will take place
via Microsoft Teams. The Contractor will hold up to four additional hydraulic review meetings with the
State’s Project Manager and other State staff, as needed. These are supplemental meetings beyond
those explicitly called for elsewhere in this Scope of Work. The Contractor will prepare agendas and
facilitate the supplemental meetings. The Contractor will also prepare and distribute draft meeting
minutes within 2 business days after each meeting and final meeting minutes within 2 business days
after receiving State’s comments on the draft minutes.
1.6 - Construction Limit Roll Plot Review Meetings – Contractor will coordinate and conduct up to three
Construction Limit Roll Plot Review Meetings to discuss scope elements and their impacts. The meetings
will take place via Microsoft Teams. The Contractor will also prepare and distribute draft meeting
minutes within 2 business days after each meeting and final meeting minutes within 2 business days
after receiving State’s comments on the draft minutes.
1.7 - Right-Of-Way (ROW) Coordination Meetings – Contractor will coordinate and conduct up to 3
ROW coordination Meetings. This is to determine parcels that may be impacted by the project and will
need title acquisition. The Contractor will conduct ROW coordination meetings as needed coinciding
with the development of the construction limit roll plot, plan submittals and continuing until all ROW
needs are identified. These meetings may start earlier if State’s Project Manager feels it is necessary.
The Contractor will keep a ROW issues list to keep track of issues and document key decisions. The
meetings will be held via Microsoft Teams.
1.8 - Cultural Resources Unit (CRU) Impact Coordination Meetings – Contractor will coordinate and
conduct up to 2 Cultural Resource Impact Coordination Meetings. These meetings are to identify Areas
of Potential Effect (APE). The Contractor will conduct CRU impact coordination meetings as needed
coinciding with the development of the construction limit roll plot and continuing until all CRU needs are
identified. These meetings may start earlier if State’s Project Manager feels it is necessary. The
Contractor will keep a CRU issues list to keep track of potential issues and document key decisions. The
meetings will be held via Microsoft Teams.
1.9 - Contaminated Materials Management Team (CMMT) Coordination Meetings – Contractor will
coordinate and conduct CMMT Coordination Meetings. The Contractor will hold one CMMT
5
This is the opportunity summary page. It provides an overview of this opportunity and a preview of the attached documentation.