Value Engineering versus Cost Cutting

by Jonathan McGaha | June 8, 2011 12:00 am

People disagree about the definition of value engineering but the common goal is to reduce cost

By Thomas Taylor

Thomas Taylor

The VE process has been around for a long time. First created by either accident or necessity by Lawrence D. Miles, a staff engineer for General Electric in 1947, the process set out to reduce the cost, increase productivity and improve the quality of the good or service that was being brought to market. The United States Department of Defense defines VE as “an analysis of the functions of a program, project, system, product, item of equipment, building, facility, service or supply of an executive agency, performed by qualified agency or contractor personnel, directed at improving performance, reliability, quality, safety and life cycle costs.” If the goal of value engineering is to strike the perfect balance between cost and value, then why is increased value so seldom found as a result of a VE exercise? There is no one answer to this question because, in my experience, people in the industry use their own definitions and variations of the process.

A Difference of Perspective

If you ask your team to provide a definition of value engineering, the answer you receive will likely vary, sometimes drastically, depending on which member of the team you ask. An architect once told me the act of value engineering is nothing more than design assassination. Most all of the contractors I know think VE is a cost-reduction effort because the owner does not want to pay for what the designers put into the plan and specifications. More often than not, owners believe their delivery team is responsible for analyzing each element of the project and acting accordingly to deliver the highest quality for the lowest cost. In other words, every member of the team is starting the exercise from a different vantage point. There is no common definition or goal other than reducing the cost.

The Context of the VE Exercise

Just recently, I was asked to participate in a value engineering exercise by the owner of a large development. The quantity surveyor working with the project team requested ideas from individual members of the team in order to assemble a potential list of items that the owner would be provided for consideration. Once the list was created, the team was asked to participate in a group exercise to review and draw conclusions about each potential VE item. Some of the items contained on the list and their associated cost impact are as follows:

On the surface, eliminating any of these items may seem to be reasonable and the combined savings is significant. However, the team was asked to participate in a value engineering exercise. Each of these items needed to be evaluated in a larger context if the owner was to receive both an increased value and a decreased cost through this exercise. Some questions they should have considered include the following:

Clearly Define the Goal

The next time your team is asked to participate in a value engineering exercise, take a moment and make sure that every participant knows and understands what the expected outcome is. Having everyone on the team start from the same place and work with the same definition will go a long way in helping to strike that ultimate balance between the project cost and what the owner values.


Thomas Taylor, a 29-year veteran of the construction industry and noted expert on sustainability, is the general manager of St. Louis-based Vertegy. His recent book, “Guide to LEED 2009: Estimating and Preconstruction Strategies,” provides step-by-step information about the LEED 2009 for New Construction process. To learn more about Vertegy or Taylor’s new book, visit www.vertegyconsultants.com[1] for more information.

Endnotes:
  1. www.vertegyconsultants.com: http://www.vertegyconsultants.com

Source URL: https://www.metalarchitecture.com/articles/value-engineering-versus-cost-cutting/