Value Analysis

Revision as of 19:34, 28 February 2018

Abstract

Value Analysis is a systematic tool which can be used to improve the value of a product or process by analyzing its constituent components and the associated costs ^[1]. The overall objective is to find improvements to the components by reducing their cost and/or increasing the value of the functions.

This article will describe each step required to perform a Value Analysis as well as suggesting tools that can be used during each step. The Article can be used as a template when performing a Value Analysis.

History of Value Engineering

The origins of the Value Analysis goes back to World War II. During the war, there was a shortage of both labor and materials which resulted in companies had to search for substitutions to their existing products in order to still meet demand. This value-based approach led to General Electric (GE) noticing that substitutions often resulted in reduced cost, improvement of the product or both. GE took this Value Engineering approach out of necessity but it resulted in a systematic process which still has wide application to today. ^[2]. The specific process originated in 1947 from Lawrence D. Miles and is known as Value Analysis ^[3].

Value Analysis as a tool

In order to understand the how Value Analysis can be used as a tool, it is necessary to define the word “Value”. Value has no clear definition but when used in Value Analysis it is defined as a Function’s performance relative to its cost ^[1].

Value=(Function Performance)/cost

, where the function is defined as the effect produced by a product or by one of its elements, in order to satisfy customer needs and the Cost is defined as the resources required to achieve the function.

As can be understood from the equation, the value is not only about minimizing the cost. As long as the increase of the function’s performance is relatively higher than the increase of cost, the value of the function will still increase. This differentiates a Value Analysis from typical cost reduction approaches ^[3].

The Value Analysis Process

A specific process has been developed when applying Value Analysis on an existing product or element. The process is broken down into a preparatory phase and five main phases. Each phase contains its own course of action and goal. The following section will describe each phase in more detail and suggest tools/techniques that can assist when performing a Value Analysis

The section can be used as a Framework for general application.

Value Analysis Framework

Preparatory phase

Objective: To define the project scope and forming the team that is going to perform the analysis.

When identifying what is to be analyzed Portfolio Management techniques, such as the BCG Matrix^[4], can be used to ensure that the effort is put in the right place.

A question companies should ask themselves is:

Which product or process would benefit the company most if subject to an increase in value?

A value Analysis requires significant work and it should be avoided trying to increase value to a process/product unless it provides a significant increase in value for the company. A mean-variance analysis can be used when weighing the risk against expected return. As a Value Analysis has a high engineering cost the investment should be made on a solid foundation.

To successfully conclude a thorough Value Analysis, it is important that the right qualities are found within the team. Some of the important qualities include an understanding of material properties, creativity and large focus on details^[3]. It can be beneficial to use tools such as Competency mapping and considering the Five Stages of Team Development when forming the team. Focus groups can be used to help to understand the general market perception towards changes in an existing product.

A successful Value Analysis is largely dependent on every person within the team has a common understanding of the project scope. Therefore it is also of great importance that the right project manager is chosen. It could be beneficial to consult with existing standards such as PMBOK, ISO 21500 or IMPA. All standards are listed in the Further Readings Section.

Phase 1: Information

 Objective: Identify and prioritize customers and collect information available about the identified product/process. 

In this phase, it is necessary to identify and prioritize stakeholders. A stakeholder is in the ISO 21500 standard defined as "a person, group or organization that has interests in, or can affect, be affected by, or perceive itself to be affected by, any aspect of the project" ^[5].

In a Value Analysis stakeholders from all classifications have great importance ^[6].

• Outward Stakeholders: Functions should satisfy customer need. A product has no value if there are no customers and this stakeholder should always be prioritized highly in a Value Analysis.
• Downward Stakeholders: Knowledge comes from within the project group. The competencies within the group should comply with the task at hand.
• Upward: The upward stakeholders hold the resources to finance the Value Analysis and implementation of changes to the product/process.

Mention something about general stakeholder management?

Besides stakeholder management, it is also critical to collect all facts about the identified subject. Collect cost breakdowns, drawings, specifications, manufacturing data etc. Focus on what the customers want and need? What characteristics of the scope can be modified to increase value and/or reduce costs? This subject should be discussed in detail with stakeholders, to get a true appreciation of the relevant functions.

Phase 2: Analysis

Objective: Perform a functional analysis to identify all functions within the scope. 

Actions and applicable tools:

A Functional Analysis is performed to identify the relevant functions. All functions have an importance as well as a cost. Costs are quantified and functions are sorted by their importance. The relationship of Importance and Cost can be compared to a cost-benefit analysis. Having the lowest possible cost will always be the optimal scenario but Functional Analysis focuses on the lowest cost to provide a given function. Minimizing the cost at the expenditure of an important function is not desirable and finding the balance between function importance and cost is critical. This phase is considered as the key step of the whole methodology as it represents the translation of customer needs into functions.

The functions can be divided into two categories: ^[7].

• Basic: The function for which the user or buyer purchases the product and constitutes the real value to the customer.  This function is not subject for modification during the Value Analysis.
• Secondary: Secondary functions are the assisting functions that makes it possible to realize the basic function. Significant cost is related to the secondary functions and these will be the target when performing value engineering work such as Value Analysis.

In this phase, FAST (Function Analysis System Technique) should be applied. The Technique used to create a graphical representation illustrating the logical relationships between the functions based on the questions “How” and “Why”. How, is answered by the function on the right, and is the method to perform that function Why, is answer by the function to its left, which expresses the goal of that function A good rule to remember in constructing a FAST Model is to build in the How direction and test the logic in the Why direction. (KILDE PÅ DEN BITCH)

A simplified illustration of the FAST Technique is presented in Figure??

List of References

1. ↑ ^{1.0 1.1} "Value Analysis and Function Analysis System Technique [1]"
2. ↑ History of Value Engineering [2]
3. ↑ ^{3.0 3.1 3.2} "Techniques of Value Analysis and Engineering: 3rd Edition, Lawrence D. Miles"
4. ↑ "Fundamentals of Strategy: 3rd Edition, Gerry Johnson et al."
5. ↑ "Guidance on project management, DS/ISO 21500, Danish Standards, 2013"
6. ↑ "Stakeholder Management, Article on Apppm Wiki [3]"
7. ↑ Techniques of Value Analysis and Engineering: 3rd Edition, Lawrence D. Miles