The Technique of Value Engineering (VE) in Architecture

From apppm
(Difference between revisions)
Jump to: navigation, search
Line 27: Line 27:
  
 
==== Preparation Phase ====
 
==== Preparation Phase ====
: understanding the project, first touch
+
: ''understanding the project, first touch''
  
 
In this step it is important for the value engineering team to be familiar with the project, which means that the team has to understand the need and the specifications that the customer demands and wants for the final product, especially what is to be studied and when.  
 
In this step it is important for the value engineering team to be familiar with the project, which means that the team has to understand the need and the specifications that the customer demands and wants for the final product, especially what is to be studied and when.  
  
 
==== Information Phase ====
 
==== Information Phase ====
: gathering of data
+
: ''gathering of data''
  
 
In this phase, the team has to research and investigate deeper about the project. Some parts have to be clear now, like the functions of each element and the design procedure. The deeper the research, the better the outcome and the understanding. Some really good and helpful questions are the following:  
 
In this phase, the team has to research and investigate deeper about the project. Some parts have to be clear now, like the functions of each element and the design procedure. The deeper the research, the better the outcome and the understanding. Some really good and helpful questions are the following:  
Line 49: Line 49:
  
 
==== Function Analysis Phase ====
 
==== Function Analysis Phase ====
: analysis of the project, clarification of the purpose
+
: ''analysis of the project, clarification of the purpose''
 
==== Creative Phase ====
 
==== Creative Phase ====
: production of ideas which correspond the needs
+
: ''production of ideas which correspond the needs''
 
==== Evaluation Phase ====
 
==== Evaluation Phase ====
: synthesizing the ideas
+
: ''synthesizing the ideas''
 
==== Development Phase ====
 
==== Development Phase ====
: review and selection of the most suitable ideas
+
: ''review and selection of the most suitable ideas''
 
==== Presentation Phase ====
 
==== Presentation Phase ====
: presentation to the clients
+
: ''presentation to the clients''
 
==== Implementation Phase ====
 
==== Implementation Phase ====
: realization of the selected by the client’s ideas
+
: ''realization of the selected by the client’s ideas''
  
 
== Limitations ==
 
== Limitations ==

Revision as of 18:20, 20 February 2022

Developed by Aikaterini Deli

Contents

Abstract

Value Engineering (VE) is a sequence of procedures aiming to meliorate the value of the final product by having a better management through the overall steps, always considering the cost. Value Engineering is an organizing tool with origins from the science of Project Management which had been used during the World War II by “General Electric Co” and nowadays it is an approach commonly used for planning building projects.

Most of the companies follow this technique in order to minimize the cost but not the basic function of the product. In the architectural field, the engineers are facing plenty of composite projects which have to meet the needs and requirements of their clients and also being in time and in budget. For this reason, the VE technique is preferable from large architectural offices because of the status of their clients. The bigger the project, the greater the need for examining continuously the budget through the design process.

In a nutshell, Value Engineering is an organized creative review of the needs and requirements of the client which are satisfied through the functions of the product, always underlining its quality and its low life cycle cost.

Big Idea

The idea was born at General Electric Co in the 1940s by the engineers Lawrence Miles, Jerry Leftow, and Harry Erlicher. The combination of the high demand of products with the shortage of raw materials, created the need for seeking alternative materials which will be in the same cost and function levels with the first ones. This process was named Value Engineering. Nowadays, Value Engineering is consisted by a multi-disciplined team which purpose is to identify and reduce unnecessary costs and poor performance, while maintaining product quality. Functional Analysis System Technique (FAST) diagrams illustrate the phases. The value engineering team has four to six members with complementary expertise in different disciplines.[1]

This tool can be applied at any step in a project, from the pre-workshop preparation to the post-workshop implementation.[2] The Society of American Value Engineers (SAVE) was formed in 1959 as a professional society dedicated to the advancement of VE through a better understanding of the principles, methods, and concepts involved. [3] According to the Value Methodology Standard from the SAVE, value engineering can be described by the following 8-phases:

  1. Preparation Phase
  2. Information Phase
  3. Function Analysis Phase
  4. Creative Phase
  5. Evaluation Phase
  6. Development Phase
  7. Presentation Phase
  8. Implementation Phase

Application

The tool is supposed to be used by following the below phases.

Preparation Phase

understanding the project, first touch

In this step it is important for the value engineering team to be familiar with the project, which means that the team has to understand the need and the specifications that the customer demands and wants for the final product, especially what is to be studied and when.

Information Phase

gathering of data

In this phase, the team has to research and investigate deeper about the project. Some parts have to be clear now, like the functions of each element and the design procedure. The deeper the research, the better the outcome and the understanding. Some really good and helpful questions are the following:

  1. How
  2. What
  3. Why
  4. Where
  5. When
The Verb - Noun Approach

The Verb - Noun Approach is well known between the value engineering team, as they set the questions "What this function does?" and "What is this fuction?", which are aswered by a verb and noun respectively. Some advantages about this technique can be summarized like these:

  1. The success of this approach makes clear that the team has understood the function and it is capable to describe it in two words.
  2. With this technique, it is way easier to not be confused. This is a common phenomenon as the functions are plenty and it is not easy to seperate the different meanings of each.


Function Analysis Phase

analysis of the project, clarification of the purpose

Creative Phase

production of ideas which correspond the needs

Evaluation Phase

synthesizing the ideas

Development Phase

review and selection of the most suitable ideas

Presentation Phase

presentation to the clients

Implementation Phase

realization of the selected by the client’s ideas

Limitations

As everywhere, in this technique is easy to detect the limitations, which are man-made [4]. Some of these are the following:

  • Difficulties in the communication inside the multidisciplinary team
  • Lack of motivation
  • Lack of knowledge
  • Persistence from stakeholders for even less cost

References

  1. Sievert, R. W. (1991). A review of value engineering as an effective system for planning building projects. Project Management Journal, 22(1), 31–38.
  2. SAVE International Value Standard, VALUE METHODOLOGY STANDARD, (SAVE International Value Standard, 2015)
  3. https://www.wbdg.org/resources/value-engineering
  4. https://www.yourarticlelibrary.com/marketing/value-analysis-meaning-phases-merits-and-limitations/49178
Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox