<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://epg.modot.org/index.php?action=history&amp;feed=atom&amp;title=130.1_Discussion</id>
	<title>130.1 Discussion - Revision history</title>
	<link rel="self" type="application/atom+xml" href="https://epg.modot.org/index.php?action=history&amp;feed=atom&amp;title=130.1_Discussion"/>
	<link rel="alternate" type="text/html" href="https://epg.modot.org/index.php?title=130.1_Discussion&amp;action=history"/>
	<updated>2026-07-22T17:24:53Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.43.9</generator>
	<entry>
		<id>https://epg.modot.org/index.php?title=130.1_Discussion&amp;diff=59059&amp;oldid=prev</id>
		<title>Hoskir: moved 130.1 to its own page and updated formatting</title>
		<link rel="alternate" type="text/html" href="https://epg.modot.org/index.php?title=130.1_Discussion&amp;diff=59059&amp;oldid=prev"/>
		<updated>2026-07-15T14:04:42Z</updated>

		<summary type="html">&lt;p&gt;moved 130.1 to its own page and updated formatting&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;&amp;lt;div style=&amp;quot;float: right; margin-top: 5px; margin-left: 15px; margin-bottom: 15px;&amp;quot;&amp;gt;__TOC__&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{| style=&amp;quot;margin-left:15px; margin-top: 5px; border:1px solid #a9a9a9; background:#f5f5f5&amp;quot; width=&amp;quot;275px&amp;quot; align=&amp;quot;right&amp;quot; &lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;text-align:center;&amp;quot; | &amp;#039;&amp;#039;&amp;#039;&amp;lt;u&amp;gt;Additional Information&amp;lt;/u&amp;gt;&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
|-&lt;br /&gt;
| ● [[media:130 District Value Engineering Contact.doc|District Value Engineering Coordinator&amp;#039;s Responsibilities]]&lt;br /&gt;
|-&lt;br /&gt;
| ● [[130.3 Project Manager’s Guide|Project Manager&amp;#039;s Guide]]&lt;br /&gt;
|-&lt;br /&gt;
| ● [[130.4 Value Engineering Team Leader Guide|Value Engineering Team Leader Guide]]&lt;br /&gt;
|-&lt;br /&gt;
| ● [[media:130.1 VE Training Evaluation Form.doc|VE Training Evaluation Form]]&lt;br /&gt;
|-&lt;br /&gt;
| ● [http://epg.modot.org/forms/CM/Value_Engineering_Proposal_C_104.pdf Construction Value Engineering Change Proposal (C-104)]&lt;br /&gt;
|-&lt;br /&gt;
| ● [[104.13 Construction Inspection Guidance for Sec 104#104.13.1 Guidance for Sec 104.6|Evaluation Procedures for Construction Value Engineering Change Proposals]]&lt;br /&gt;
|-&lt;br /&gt;
| ● [http://spexternalsignin/sites/de/vep/_layouts/15/start.aspx#/SitePages/VE_Contact.aspx MoDOT Value Engineering Contacts]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==130.1.1 Study Timing==&lt;br /&gt;
VE studies are performed to add value to a project, not to simply reduce costs. VE studies should challenge project scoped that exceed the minimum necessary to deliver the project’s purpose and need. As stated in the law, VE studies are conducted &amp;quot;to provide suggestions for reducing the total cost of the project and providing a project of equal or better quality.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Although only a single study during preliminary design is generally required for a project, VE studies can be performed any time prior to letting  or after award, and even multiple times on an individual project. A study can be conducted at any stage during the design life of the project; however, priority is given to performing the study as early as feasible to maximize the opportunity to implement developed alternatives.  During the study, all aspects of the project may be considered including, but not limited to, location, geometrics, final vertical and horizontal alignments, drainage, construction staging, traffic impacts, TSMO strategies, traffic control, and signalization, pavement and structure details.  In addition, studies in the later phase should consider what additional flexibility can be added and what adjustments can be made to &amp;quot;fine tune&amp;quot; the project prior to letting.&lt;br /&gt;
&lt;br /&gt;
Additional VE analysis should be considered if, during a project’s design, the scope of work is changed significantly from that which was studied previously.  In addition, consideration should be given to an additional study if the previous study will have been conducted more than 10 years prior to the projects letting.&lt;br /&gt;
&lt;br /&gt;
==130.1.2 VE Organization==&lt;br /&gt;
Value Engineering is a critical program and requires statewide participation in order to accomplish the program goals. The Policy and Innovations Engineer manages the overall operation of MoDOT’s VE program. The Policy and Innovations Engineer is responsible for tracking the VE program and reporting its progress to both management and the FHWA. The Policy and Innovations Engineer leads studies and may assist with the initial selection of teams for district VE studies, and provides training guidelines and facilitation. &lt;br /&gt;
&lt;br /&gt;
Each District Engineer selects a district value engineering coordinator (DVEC) to coordinate VE activities in that district. The [[media:130 District Value Engineering Contact.doc|DVEC is responsible]] for the district&amp;#039;s VE program. The DVEC should be at a level consistent with the supervision and management responsibilities of the VE effort. The DVEC is responsible for scheduling the study and making appropriate accommodations for the participants. The DVEC serves as a team member on the VE study to become familiar with the process and leads VE studies, as required, to meet the demands of the program.  The DVEC is also responsible for tracking the district led value engineering studies and ensuring the study results are forwarded to the Policy and Innovations Engineer and entered into the SIMS database for each studied project.  &lt;br /&gt;
&lt;br /&gt;
In any case, the facilitator of the study compiles recommendations from the VE study and submits them in a VE report, for approval as follows: &lt;br /&gt;
* The lowest level decision maker within the project hierarchy can approve and implement VE recommendations that do not change policy, standards, or scope of the original project. A copy of the VE study and the Project Manager’s, District Design Engineer&amp;#039;s or District Engineer&amp;#039;s approval is retained by the district and the Policy and Innovations Engineer. The Policy and Innovations Engineer notifies the team members of the study results and tracks results of each study. &lt;br /&gt;
* The approval of a District Engineer or division engineer is required to approve and implement VE recommendations that change the scope of the original project.  A copy of the VE study and the District Engineer or division engineers’ approval is retained by the district and the Policy and Innovations Engineer.  The Policy and Innovations Engineer tracks results of each study. &lt;br /&gt;
* The approval of the Chief Engineer, or his representative, is required to approve and implement VE recommendations that affect more than one division/district or change policy or standards. The Policy and Innovations Engineer notifies affected divisions, districts and the team members and tracks results of each study. &lt;br /&gt;
&lt;br /&gt;
Approved recommendations are incorporated in the project design.  If an approved recommendation cannot be included, the Project Manager must document the justification for eliminating the recommendation.  This documentation should be submitted with the PS&amp;amp;E and a copy is sent to the Policy and Innovations Engineer.&lt;br /&gt;
&lt;br /&gt;
==130.1.3 Consultant Led VE Studies==&lt;br /&gt;
When consideration is given to using a consultant for conducting a VE study, the Policy and Innovations Engineer should be contacted. If the State Design Engineer approves the use of consultant services for a VE study, the Policy and Innovations Engineer will work with the district to ensure that the selected consultant is qualified and has no conflict of interest for the proposed work.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:130 Value Engineering]]&lt;/div&gt;</summary>
		<author><name>Hoskir</name></author>
	</entry>
</feed>