Skip to content
Value Analysis and Value Engineering | Part 2 of 6

Function Analysis: Two Words That Change the Discussion

How to describe what a product does as verb plus noun, sort basic and supporting functions and build a function tree with how and why.

“Mechanical seal” invites one question: who sells it cheaper. “Seal shaft” invites several: how else can a shaft be sealed, how long does the seal have to last, and what does a leak cost the customer. The second set of questions is where savings and improvements come from, and the only thing that separates them from the first is how the team writes two words.

Verb plus noun, and nothing else

A function says what the product does. It does not say how the product is built. Four rules keep the description honest.

Use an active verb and a noun: seal shaft, move coolant, contain pressure. Choose a verb that can be measured, so that the function can later be compared with a requirement: move coolant is measured in cubic meters per hour at a given head, provide performance is measured in nothing. Leave the solution open: connect system, not flange according to drawing. Keep one function per line, because a line that says contain pressure and resist corrosion will be costed twice and improved never.

Six to ten functions are enough for a product the size of a pump. The coolant pump in this series has eight.

Function Type Measured by
Move coolant Basic m3 per hour at 20 m head
Convert energy Basic Overall efficiency in percent
Contain pressure Supporting Test pressure in bar
Seal shaft Supporting Seal life in hours
Support rotation Supporting Bearing life in hours
Connect system Supporting Installed length in mm
Protect product Supporting Salt spray hours
Enable service Supporting Seal change time in minutes

Basic functions are the reason the product exists. Supporting functions make the basic functions possible or acceptable. Unwanted effects such as noise, heat and vibration get a list of their own, because limiting them also costs money.

How to get the list

Take the product apart before the meeting and lay the parts on a table with a label for weight, cost and supplier. Then work through them. For every component the team asks one question: what is this for? Every answer goes on a card as a verb and a noun. Cards that say the same thing are merged. The cards are sorted into basic functions, supporting functions and unwanted effects. Every function gets a measure with a unit, and the list is reviewed with sales and service, who hear what customers actually say about the product.

A competitor product on the same table is worth an hour of discussion. It performs the same functions with other solutions, and the differences are the first ideas.

The function tree

The tree arranges the functions by dependency. Read it to the right by asking how, and to the left by asking why.

Supply coolant to the machine. How? Move coolant and convert energy. How is coolant moved? By containing pressure, sealing the shaft and supporting the rotation. Why is the shaft sealed? To move coolant. Why is coolant moved? Because the machine needs cooling.

When both questions give sensible answers along every branch, the tree is complete. It is also the best completeness check the method has. Every component must appear under at least one function. A component that appears nowhere was either forgotten in the function list, or it is in the product for a reason nobody can name any more. Both findings are worth having.

For the CP 40 the tree produced one correction and one surprise. The nameplate, written off as packaging, turned out to serve enable service, and the base plate served nothing except connect system, a function the team had never looked at as a cost. In the next step that function gets a price.

Newsletter

One Lean idea.
Every two weeks.