Category:139 Design - Build - Revision history

Hoskir: updated per RR4068 updated link to FHWA Des Bld Pro Agreement

2025-06-12T19:17:05Z

updated per RR4068 updated link to FHWA Des Bld Pro Agreement

Hoskir: Text replacement - "External Civil Rights" to "Business Development and Compliance"

2025-01-09T21:18:42Z

Text replacement - "External Civil Rights" to "Business Development and Compliance"

← Older revision		Revision as of 16:18, 9 January 2025
Line 389:		Line 389:
	:::i. The design DBE goals are based on the percentage of DBE design consultants that are available and qualified to perform a portion of the design on the project.		:::i. The design DBE goals are based on the percentage of DBE design consultants that are available and qualified to perform a portion of the design on the project.

	:::ii. The construction DBE goals would be based on the percentage of DBE subcontractors that are available and qualified to perform a portion of the construction work on the project. The methodology of setting each goal should be the same that is used for design-bid-build projects, and should be requested through the [https://modotgov.sharepoint.com/sites/ec Division of ~~External Civil Rights~~].		:::ii. The construction DBE goals would be based on the percentage of DBE subcontractors that are available and qualified to perform a portion of the construction work on the project. The methodology of setting each goal should be the same that is used for design-bid-build projects, and should be requested through the [https://modotgov.sharepoint.com/sites/ec Division of Business Development and Compliance].

	::'''h.''' The RFQ may also include requirements regarding the submitter’s legal structure, bonding capacity and additional financial requirements, if any. On most projects, assurance of required bonding capacity of the submitters is adequate to show financial capability. Design-Build contracts may be for larger amounts of money and in such cases, companies must have the ability to bond that amount. In the case of The New I-64, the design-build contractor teams were required to have bonding capacity of more than $400 million. The I-64 teams included national design-build companies and prime contractor and design firms from St. Louis. In this instance all of these companies made up the prime contracting team.		::'''h.''' The RFQ may also include requirements regarding the submitter’s legal structure, bonding capacity and additional financial requirements, if any. On most projects, assurance of required bonding capacity of the submitters is adequate to show financial capability. Design-Build contracts may be for larger amounts of money and in such cases, companies must have the ability to bond that amount. In the case of The New I-64, the design-build contractor teams were required to have bonding capacity of more than $400 million. The I-64 teams included national design-build companies and prime contractor and design firms from St. Louis. In this instance all of these companies made up the prime contracting team.
Line 722:		Line 722:

	===139.8.2.5 Proposal Evaluations===		===139.8.2.5 Proposal Evaluations===
	When the final proposals and price allocations are received, the price allocations will be separated from the proposals and will not be opened until completion of the proposal evaluations. Before proposal evaluations begin, the proposal documents undergo a compliance review to ensure the proposal is a complete, responsive proposal. Staff from ~~External Civil Rights~~ should review proposals for DBE compliance. Pursuant to state statute, at least two responsive proposals must be received in order to award the design-build contract.		When the final proposals and price allocations are received, the price allocations will be separated from the proposals and will not be opened until completion of the proposal evaluations. Before proposal evaluations begin, the proposal documents undergo a compliance review to ensure the proposal is a complete, responsive proposal. Staff from Business Development and Compliance should review proposals for DBE compliance. Pursuant to state statute, at least two responsive proposals must be received in order to award the design-build contract.

	A confidential Proposal Evaluation Procedures document shall be created for each design-build project. The document shall include details of maintaining confidentiality of the proposals, scoring team organization and roles, scoring procedures and evaluation criteria, including compliance reviews. Each member of the scoring team shall sign the [[media:139.1.3.doc\|Confidentiality Agreement (Form 139.1.3)]] and the [[media:Form 139.8.2.5a.docx\|Proposal Conflict of Interest Form( Form 139.8.2.5)]]. Past experience has shown that holding preparation meetings with each scoring team in advance of receiving the proposals is very beneficial. Teams should be reminded that the rating method specified in the ITP must be used. After scoring is complete, The Project Director, with input from evaluation team members if needed, will prepare a Final Recommendation Report.		A confidential Proposal Evaluation Procedures document shall be created for each design-build project. The document shall include details of maintaining confidentiality of the proposals, scoring team organization and roles, scoring procedures and evaluation criteria, including compliance reviews. Each member of the scoring team shall sign the [[media:139.1.3.doc\|Confidentiality Agreement (Form 139.1.3)]] and the [[media:Form 139.8.2.5a.docx\|Proposal Conflict of Interest Form( Form 139.8.2.5)]]. Past experience has shown that holding preparation meetings with each scoring team in advance of receiving the proposals is very beneficial. Teams should be reminded that the rating method specified in the ITP must be used. After scoring is complete, The Project Director, with input from evaluation team members if needed, will prepare a Final Recommendation Report.

Hoskir at 19:12, 12 December 2024

2024-12-12T19:12:57Z

← Older revision		Revision as of 14:12, 12 December 2024
Line 1,360:		Line 1,360:
	A verb is a word that expresses existence, action, or occurrence.		A verb is a word that expresses existence, action, or occurrence.

	[[Category:~~100_General~~]]		[[Category:100_GENERAL]]

Hoskir at 20:57, 26 November 2024

2024-11-26T20:57:38Z

← Older revision		Revision as of 15:57, 26 November 2024
Line 1,359:		Line 1,359:

	A verb is a word that expresses existence, action, or occurrence.		A verb is a word that expresses existence, action, or occurrence.

			[[Category:100_General]]

Hoskir: /* 139.9.2 Contract Invoicing and Payment */ updated per RR3856

2024-03-26T17:22:38Z

139.9.2 Contract Invoicing and Payment: updated per RR3856

← Older revision		Revision as of 12:22, 26 March 2024
Line 800:		Line 800:
	If errors are found on the Contractor invoice, the Project Director, Deputy Project Director or designated staff should contact the Contractor and request a corrected invoice. The invoice should be sent back to the Contractor for corrections, and '''they must re-date the invoice''' and re-submit to MoDOT. If the Contractor makes an error and requests more reimbursement than allowed by the contract, the Project Director, Deputy Project Director or designated staff may submit the invoice and authorize payment of an amount less than the invoice requests. The reasons for paying an amount different than the amount allowed by the Contract or Contractor invoice must be clearly documented.		If errors are found on the Contractor invoice, the Project Director, Deputy Project Director or designated staff should contact the Contractor and request a corrected invoice. The invoice should be sent back to the Contractor for corrections, and '''they must re-date the invoice''' and re-submit to MoDOT. If the Contractor makes an error and requests more reimbursement than allowed by the contract, the Project Director, Deputy Project Director or designated staff may submit the invoice and authorize payment of an amount less than the invoice requests. The reasons for paying an amount different than the amount allowed by the Contract or Contractor invoice must be clearly documented.

	After the invoice has been reviewed and approved by the project team, it must be submitted electronically to Financial Services at Contractual.Payments@modot.mo.gov. The invoice submittal should include the following:		After the invoice has been reviewed and approved by the project team, a Daily Work Report will be created in AWP for the dollar amount to be paid. Once the DWR is approved, an Estimate shall be generated and approved by the Project Director or designated staff for the current Estimate pay period that corresponds to the invoice approval date.
			:Note: For contracts awarded before March 1 2024 that have been submitting vouchers for contractor payments can continue using this procedure for the life of the contract. The following guidelines shall be used:

			After the invoice has been reviewed and approved by the project team, it must be submitted electronically to Financial Services at [mailto:Contractual.Payments@modot.mo.gov Contractual.Payments@modot.mo.gov]. The invoice submittal should include the following:

	:*Project Name		:*Project Name
Line 810:		Line 813:

	Each invoice must be submitted with the necessary supporting documentation and must be numbered in sequential order and label the final invoice as FINAL. The invoice shall be based on the total incurred cost during the invoice period.		Each invoice must be submitted with the necessary supporting documentation and must be numbered in sequential order and label the final invoice as FINAL. The invoice shall be based on the total incurred cost during the invoice period.

	The Project Director, Deputy Project Director or designated staff should make every effort to see that the contractor is paid in a timely manner, the goal being 30 days. Missouri law states that the contractor is entitled to interest if the invoice is not paid in 45 days. The 45-day period starts when all questions about the invoice have been addressed and agreed to by both parties.

	Design-Build owner consultant invoices should be submitted using the Contractual Payments Library.		Design-Build owner consultant invoices should be submitted using the Contractual Payments Library.

Hoskir: /* 139.10.7.1 Commonly Encountered Terms and Situations */ changed geopak to OpenRoads Designer

2024-01-16T14:17:40Z

139.10.7.1 Commonly Encountered Terms and Situations: changed geopak to OpenRoads Designer

← Older revision		Revision as of 09:17, 16 January 2024
Line 1,172:		Line 1,172:
	:*''' shall:''' Use this word to express a command, or what is mandatory. In Contract Documents, “shall” is generally preferred over “will” when describing requirements of the Contractor.		:*''' shall:''' Use this word to express a command, or what is mandatory. In Contract Documents, “shall” is generally preferred over “will” when describing requirements of the Contractor.

	:*''' software:''' Spell out as one word. Do not use the phrase “software program,” as this is redundant. Spell out any software product names as they appear on the products, and include vendor names on first use. For example, MicroStation by Bentley Systems Inc., ~~GEOPAK~~ by Bentley Systems Inc., and AutoCAD by Autodesk Inc.		:*''' software:''' Spell out as one word. Do not use the phrase “software program,” as this is redundant. Spell out any software product names as they appear on the products, and include vendor names on first use. For example, MicroStation by Bentley Systems Inc., OpenRoads Designer by Bentley Systems Inc., and AutoCAD by Autodesk Inc.

	:*''' stormwater:''' Spell out as one word.		:*''' stormwater:''' Spell out as one word.

Hoskir: /* 139.10.2.2 Project Financial Plan */

2023-01-27T15:37:55Z

139.10.2.2 Project Financial Plan

← Older revision		Revision as of 10:37, 27 January 2023
Line 973:		Line 973:
	:* Projects with program costs under $100 million do not require a FP.		:* Projects with program costs under $100 million do not require a FP.
	:* Projects with program costs over $100 million but less than $500 million require a FP. No FHWA approval of the FP is required unless identified in the PoDI Process and/or requested by the FHWA. Approval of the project FP will be provided by the Chief Financial Officer, or the CFO’s representative.		:* Projects with program costs over $100 million but less than $500 million require a FP. No FHWA approval of the FP is required unless identified in the PoDI Process and/or requested by the FHWA. Approval of the project FP will be provided by the Chief Financial Officer, or the CFO’s representative.
	:* Projects with program costs between $100M and $500M do not require FHWA approval of the FP and annual updates, however they must be provided upon request.		:* Projects with program costs between $100M and $500M do not require FHWA approval of the initial FP and annual updates, however they must be provided upon request.

	===139.10.2.3 Project Management Plan===		===139.10.2.3 Project Management Plan===

Hoskir: /* 139.10.2.2 Project Financial Plan */ added EPG 139.10.2.3 per RR 3566

2023-01-27T15:34:38Z

139.10.2.2 Project Financial Plan: added EPG 139.10.2.3 per RR 3566

← Older revision		Revision as of 10:34, 27 January 2023
Line 974:		Line 974:
	:* Projects with program costs over $100 million but less than $500 million require a FP. No FHWA approval of the FP is required unless identified in the PoDI Process and/or requested by the FHWA. Approval of the project FP will be provided by the Chief Financial Officer, or the CFO’s representative.		:* Projects with program costs over $100 million but less than $500 million require a FP. No FHWA approval of the FP is required unless identified in the PoDI Process and/or requested by the FHWA. Approval of the project FP will be provided by the Chief Financial Officer, or the CFO’s representative.
	:* Projects with program costs between $100M and $500M do not require FHWA approval of the FP and annual updates, however they must be provided upon request.		:* Projects with program costs between $100M and $500M do not require FHWA approval of the FP and annual updates, however they must be provided upon request.

			===139.10.2.3 Project Management Plan===
			Projects with an estimated total cost of $500 million or a project that has been otherwise identified by FHWA as a major project, must prepare and submit a Project Management Plan (PMP). Project Management Plans are submitted to the FHWA division office for approval.

			For the purposes of determining whether a project's estimated cost exceeds $500 million, FHWA will use the total cost estimate for the project scope set forth in the NEPA decision document. The total cost of the project is the value of all resources necessary to perform the preliminary engineering (including the cost of NEPA and other environmental documentation), right-of-way, environmental mitigation, construction, project management, public outreach, and costs of external third party work such as utility and railroad relocations regardless of funding source or administering agency.

			The Project Management Plan should be in accordance with FHWA's guidance: [https://www.fhwa.dot.gov/majorprojects/pmp/guidance17.cfm Project Management Plan Guidance for Major Projects]

	==139.10.3 File Storage Structure==		==139.10.3 File Storage Structure==

Hoskir: /* 139.9.3.1.1 Quality Management Plan (QMP) */

2023-01-27T14:56:20Z

139.9.3.1.1 Quality Management Plan (QMP)

← Older revision		Revision as of 09:56, 27 January 2023
Line 859:		Line 859:
	:* A list of QA hold points and a procedure for addressing any issues found during the QA hold point inspections including notification, correction, and establishing a new hold point.		:* A list of QA hold points and a procedure for addressing any issues found during the QA hold point inspections including notification, correction, and establishing a new hold point.
	:* The frequency of review of the quality management system by the Contractor’s top management and the procedure for making revisions to the QMP.		:* The frequency of review of the quality management system by the Contractor’s top management and the procedure for making revisions to the QMP.
	:* References to specific applicable QC/QA plans such as asphaltic concrete pavement or ~~Portland~~ cement concrete pavement.		:* References to specific applicable QC/QA plans such as asphaltic concrete pavement or portland cement concrete pavement.
	:* Forms to be used by the QC and QA staff.		:* Forms to be used by the QC and QA staff.
	:* Format for the weekly schedule and work plans.		:* Format for the weekly schedule and work plans.

Hoskir: /* 139.9.3.1.1 Quality Management Plan (QMP) */

2023-01-27T14:55:11Z

139.9.3.1.1 Quality Management Plan (QMP)

← Older revision		Revision as of 09:55, 27 January 2023
Line 837:		Line 837:

	====139.9.3.1.1 Quality Management Plan (QMP)====		====139.9.3.1.1 Quality Management Plan (QMP)====
	The contractor shall develop, implement, and maintain a Quality Management Plan (QMP) that will ensure the work meets or exceeds all contract requirements, and provides a record of acceptance of the work and material. The QMP shall address all QC and QA inspection and test requirements of the construction ~~work~~ The QMP shall be continuously improved throughout the delivery of the entire Project. Any QMP modifications require the approval of MoDOT’s Project Director. All modifications shall be tracked in an indexed table containing QMP version numbers, revision dates and corresponding section(s) changed with each revision.		The contractor shall develop, implement, and maintain a Quality Management Plan (QMP) that will ensure the work meets or exceeds all contract requirements, and provides a record of acceptance of the work and material. The QMP shall address all QC and QA inspection and test requirements of the construction Work. The QMP shall be continuously improved throughout the delivery of the entire Project. Any QMP modifications require the approval of MoDOT’s Project Director. All modifications shall be tracked in an indexed table containing QMP version numbers, revision dates and corresponding section(s) changed with each revision.

	MoDOT and FHWA’s approval of the Quality Management Plan is required prior to issuing NTP2. The approved QMP shall be considered a Book 3 Contract Document and must be approved by MoDOT before any construction takes place.		MoDOT and FHWA’s approval of the Quality Management Plan is required prior to issuing NTP2. The approved QMP shall be considered a Book 3 Contract Document and must be approved by MoDOT before any construction takes place.

← Older revision		Revision as of 14:17, 12 June 2025
Line 11:		Line 11:
	\|[[media:139 Sample Project Goals.pdf\|Sample Project Goals]]\|\| \|\|[http://www.gpo.gov/fdsys/pkg/CFR-2013-title23-vol1/xml/CFR-2013-title23-vol1-part636.xml 23 CFR Part 636]		\|[[media:139 Sample Project Goals.pdf\|Sample Project Goals]]\|\| \|\|[http://www.gpo.gov/fdsys/pkg/CFR-2013-title23-vol1/xml/CFR-2013-title23-vol1-part636.xml 23 CFR Part 636]
	\|-		\|-
	\|[~~[media~~:~~139 FHWA Design Build Program Agreement Oct 2020a~~.pdf\|FHWA Design-Build Program Agreement]]\|\| \|\|[https://revisor.mo.gov/main/OneSection.aspx?section=227.107 Missouri Design-Build Statute 227.107]		\|[https://epg.modot.org/forms/general_files/DE/Design_Build_Partnering_Agreement.pdf FHWA Design-Build Program Agreement]\|\| \|\|[https://revisor.mo.gov/main/OneSection.aspx?section=227.107 Missouri Design-Build Statute 227.107]
	\|-		\|-
	\|[[media:139.8 Design Build Process Checklist.docx\|Design-Build Process Checklist]]\|\| \|\|[http://www.fhwa.dot.gov/publications/research/infrastructure/12039/12039.pdf FHWA Quality Tech Brief]		\|[[media:139.8 Design Build Process Checklist.docx\|Design-Build Process Checklist]]\|\| \|\|[http://www.fhwa.dot.gov/publications/research/infrastructure/12039/12039.pdf FHWA Quality Tech Brief]
Line 279:		Line 279:
	{\|style="padding: 0.3em; margin-left:7px; border:2px solid #a9a9a9; text-align:center; font-size: 95%; background:#f5f5f5" width="350px" align="right"		{\|style="padding: 0.3em; margin-left:7px; border:2px solid #a9a9a9; text-align:center; font-size: 95%; background:#f5f5f5" width="350px" align="right"
	\|-		\|-
	\|[~~[media~~:~~139 FHWA Design Build Program Agreement Oct 2020a~~.pdf~~\|MoDOT/~~FHWA Design-Build Program Agreement]]		\|[https://epg.modot.org/forms/general_files/DE/Design_Build_Partnering_Agreement.pdf FHWA Design-Build Program Agreement]
	\|}		\|}

	Since the Design-Build process can be complex and involve time critical reviews and approvals, the [~~[media~~:~~139 FHWA Design Build Program Agreement Oct 2020a~~.pdf~~\|MoDOT/~~FHWA Design-Build Program Agreement]] outlines the Missouri Division of FHWA’s involvement on Design-Build projects. The purpose of the Design-Build Program Agreement is to ensure that MoDOT and FHWA have an understanding of the level of involvement, approval actions, roles, responsibilities and processes that FHWA will provide on Design-Build projects. The agreement addresses the Design-Build procurement process, the [[127.14 National Environmental Policy Act (NEPA) Classification and Documents\|NEPA process]] as it relates to Design-Build, the [[234.1 Access to Interstate Highways\|Access Justification Report (AJR)]] process and other approval requirements during contract execution.		Since the Design-Build process can be complex and involve time critical reviews and approvals, the [https://epg.modot.org/forms/general_files/DE/Design_Build_Partnering_Agreement.pdf FHWA Design-Build Program Agreement] outlines the Missouri Division of FHWA’s involvement on Design-Build projects. The purpose of the Design-Build Program Agreement is to ensure that MoDOT and FHWA have an understanding of the level of involvement, approval actions, roles, responsibilities and processes that FHWA will provide on Design-Build projects. The agreement addresses the Design-Build procurement process, the [[127.14 National Environmental Policy Act (NEPA) Classification and Documents\|NEPA process]] as it relates to Design-Build, the [[234.1 Access to Interstate Highways\|Access Justification Report (AJR)]] process and other approval requirements during contract execution.

	Required FHWA Approval Actions:		Required FHWA Approval Actions:
Line 294:		Line 294:
	'''Document Review Procedures'''		'''Document Review Procedures'''

	FHWA-Missouri Division designated Transportation Engineer (TE) will typically be the FHWA representative for Federal involvement while implementing FHWA's PoDI Process and required project involvement. Other reviews may be required in accordance with the PoDI process. The TE will serve as MoDOT’s main point of contact for Design-Build projects. Feedback resulting from reviews will be provided to MoDOT within timeframes included in the [~~[media~~:~~139 FHWA Design Build Program Agreement Oct 2020a~~.pdf~~\|MoDOT/~~FHWA Design-Build Program Agreement]]. The project team shall also coordinate with Central Office staff, including the Design-Build Coordinator, regarding procurement document reviews. Internal reviews should occur prior to FHWA reviews, but can be performed concurrently if needed. It is important to allow for adequate review time when developing the project procurement schedule. The project team may use the [[media:139.8.1.xls\|Review Comment Response Sheet (RCRS) Form (Form 139.8.1)]] to collect and respond to comments.		FHWA-Missouri Division designated Transportation Engineer (TE) will typically be the FHWA representative for Federal involvement while implementing FHWA's PoDI Process and required project involvement. Other reviews may be required in accordance with the PoDI process. The TE will serve as MoDOT’s main point of contact for Design-Build projects. Feedback resulting from reviews will be provided to MoDOT within timeframes included in the [https://epg.modot.org/forms/general_files/DE/Design_Build_Partnering_Agreement.pdf FHWA Design-Build Program Agreement]. The project team shall also coordinate with Central Office staff, including the Design-Build Coordinator, regarding procurement document reviews. Internal reviews should occur prior to FHWA reviews, but can be performed concurrently if needed. It is important to allow for adequate review time when developing the project procurement schedule. The project team may use the [[media:139.8.1.xls\|Review Comment Response Sheet (RCRS) Form (Form 139.8.1)]] to collect and respond to comments.

	=139.8 Design-Build Procurement Process=		=139.8 Design-Build Procurement Process=
Line 502:		Line 502:

	====139.8.2.2.4 Additional Applicable Standards (AAS) and Design Exceptions ====		====139.8.2.2.4 Additional Applicable Standards (AAS) and Design Exceptions ====
	AASs and Design Exceptions shall be submitted by each proposer using forms provided in the RFP. AASs should be submitted using [[media:139.8.2.2(b).xls\|Form 139.8.2.2(b)]]. Design exceptions must be documented on the [[media:139.8.2.2(c).xls\|Design Exceptions Form (Form 139.8.2.2(c))]] and detailed on the [[media:139.8.2.2(d).docx\|Design Exception Information Form (Form 139.8.2.2 (d))]]. Proposers shall be responsible for submitting enough information about the AAS or DE so that it can be adequately evaluated. The project team should encourage submittals of AASs and DEs early in the technical discussions. The project team will provide feedback regarding the acceptability of the AASs and design exceptions either verbally during the meetings or in writing (via e-mail or the secure SharePoint site). The project team will also consult with FHWA to obtain concurrence or approval, as described in the [~~[media~~:~~139 FHWA Design Build Program Agreement Oct 2020a~~.pdf\|FHWA Design-Build Program Agreement]].		AASs and Design Exceptions shall be submitted by each proposer using forms provided in the RFP. AASs should be submitted using [[media:139.8.2.2(b).xls\|Form 139.8.2.2(b)]]. Design exceptions must be documented on the [[media:139.8.2.2(c).xls\|Design Exceptions Form (Form 139.8.2.2(c))]] and detailed on the [[media:139.8.2.2(d).docx\|Design Exception Information Form (Form 139.8.2.2 (d))]]. Proposers shall be responsible for submitting enough information about the AAS or DE so that it can be adequately evaluated. The project team should encourage submittals of AASs and DEs early in the technical discussions. The project team will provide feedback regarding the acceptability of the AASs and design exceptions either verbally during the meetings or in writing (via e-mail or the secure SharePoint site). The project team will also consult with FHWA to obtain concurrence or approval, as described in the [https://epg.modot.org/forms/general_files/DE/Design_Build_Partnering_Agreement.pdf FHWA Design-Build Program Agreement].

	====139.8.2.2.5 Environmental Commitments and Access Justification Reports====		====139.8.2.2.5 Environmental Commitments and Access Justification Reports====
	For some projects environmental commitments have been made prior to the RFP. In these instances it is important to document environmental commitments, and evaluate any proposed changes to the commitments. In these cases, the project team will provide a list of environmental commitments in a spreadsheet. In accordance with the RFP, a NEPA re-evaluation or revision may be required, depending on the content of each Proposal. As described in the [~~[media~~:~~139 FHWA Design Build Program Agreement Oct 2020a~~.pdf\|FHWA Design-Build Program Agreement]], to prepare for any potential revision, each proposer may be asked to use the [[media:139.8.2.2(e).xls\|Environmental Commitments Form (Form 139.8.2.2(e))]] to request any commitment revisions. This form may not be necessary for all projects.		For some projects environmental commitments have been made prior to the RFP. In these instances it is important to document environmental commitments, and evaluate any proposed changes to the commitments. In these cases, the project team will provide a list of environmental commitments in a spreadsheet. In accordance with the RFP, a NEPA re-evaluation or revision may be required, depending on the content of each Proposal. As described in the [https://epg.modot.org/forms/general_files/DE/Design_Build_Partnering_Agreement.pdf FHWA Design-Build Program Agreement], to prepare for any potential revision, each proposer may be asked to use the [[media:139.8.2.2(e).xls\|Environmental Commitments Form (Form 139.8.2.2(e))]] to request any commitment revisions. This form may not be necessary for all projects.

	For some interstate projects, an Access Justification Report may be required. As described in the FHWA Design-Build Program Agreement, to prepare for a potential AJR revision, a proposer may be asked to submit a draft AJR revision, in advance of their proposal submittal to obtain concurrence from FHWA.		For some interstate projects, an Access Justification Report may be required. As described in the FHWA Design-Build Program Agreement, to prepare for a potential AJR revision, a proposer may be asked to submit a draft AJR revision, in advance of their proposal submittal to obtain concurrence from FHWA.
Line 709:		Line 709:
	{\|style="padding: 0.3em; margin-left:7px; border:2px solid #a9a9a9; text-align:center; font-size: 95%; background:#f5f5f5" width="350px" align="right"		{\|style="padding: 0.3em; margin-left:7px; border:2px solid #a9a9a9; text-align:center; font-size: 95%; background:#f5f5f5" width="350px" align="right"
	\|-		\|-
	\|Details on project authorization are available in the [~~[media~~:~~139 FHWA Design Build Program Agreement Oct 2020a~~.pdf\|FHWA~~/MoDOT~~ Design-Build Program Agreement]].		\|Details on project authorization are available in the [https://epg.modot.org/forms/general_files/DE/Design_Build_Partnering_Agreement.pdf FHWA Design-Build Program Agreement].
	\|-		\|-
	\|An [[media:139 Project Certification Example.pdf\|example of project certification]] is available.		\|An [[media:139 Project Certification Example.pdf\|example of project certification]] is available.
Line 1,005:		Line 1,005:
	:* NTP 2 (approximately 3 months after NTP 1)		:* NTP 2 (approximately 3 months after NTP 1)

	When developing a detailed procurement schedule, teams should look at the time it will take to develop the contract documents. Teams should include document review times in the detailed schedule to ensure enough time is allowed for the required reviews. A best practice is to talk with FHWA and [https://modotgov.sharepoint.com/sites/DE/SitePages/Environmental-&-Historic-Preservation.aspx Design's Environmental Studies section] when developing the project schedule, so they can anticipate required resources. See the [~~[media~~:~~139 FHWA Design Build Program Agreement Oct 2020a~~.pdf\|FHWA~~/MoDOT~~ Design-Build Program Agreement]] for topic specific review times.		When developing a detailed procurement schedule, teams should look at the time it will take to develop the contract documents. Teams should include document review times in the detailed schedule to ensure enough time is allowed for the required reviews. A best practice is to talk with FHWA and [https://modotgov.sharepoint.com/sites/DE/SitePages/Environmental-&-Historic-Preservation.aspx Design's Environmental Studies section] when developing the project schedule, so they can anticipate required resources. See the [https://epg.modot.org/forms/general_files/DE/Design_Build_Partnering_Agreement.pdf FHWA Design-Build Program Agreement] for topic specific review times.

	==139.10.5 Contract Incentives==		==139.10.5 Contract Incentives==