What Is VAVE? Value Analysis and Value Engineering Guide
VAVE is sometimes mistaken for a cost-cutting exercise. It's better understood as a discipline for finding cost that adds no functional value — and removing exactly that, no more and no less.
What is VAVE?
VAVE — Value Analysis and Value Engineering — is a structured method for evaluating design, material, or process alternatives to reduce cost or improve function without compromising a part's required performance. The two halves of the name describe two related activities applied at different points in a product's life.
Value analysis vs value engineering
Value engineering happens during design, before a part is released to production — evaluating alternative materials, geometries, or processes while changes are still cheap. Value analysis happens on a part already in production, reviewing it against current cost and process options to find savings that weren't available or considered the first time around. Both follow the same underlying method: define the part's required function, identify what's currently costing money to deliver that function, and test alternatives that deliver the same function for less.
The VAVE methodology
- Define function, not feature — separate what the part must do from how it currently does it
- Cost the current design — usually via a bottom-up should-cost model, so the baseline is defensible
- Generate alternatives — material substitution, process change, part consolidation, supplier change, tolerance relaxation
- Cost each alternative — and check it against the required function, not just the price
- Validate and implement — confirm the alternative meets specification before committing to an engineering change
VAVE in practice: a real example
On a recent DC-DC converter teardown, a VAVE workshop generated 13 distinct ideas — material substitution, process changes, and supplier changes — contributing to a 39% body-cost reduction and a further 28% PCBA cost reduction once batch quantities were optimised. None of these required compromising the converter's required function; all of them removed cost that wasn't buying any.
Common VAVE mistakes
The most common failure mode is treating VAVE as a pure cost-cutting exercise disconnected from function — proposing changes that do reduce cost but also quietly reduce margin for error, reliability, or manufacturability. The discipline only works when every alternative is validated against the part's actual functional requirement, not just its current specification.
Key takeaways
- VAVE separates a part's required function from its current cost, then tests alternatives that deliver the same function for less
- Value engineering happens pre-release; value analysis happens on parts already in production
- A defensible should-cost baseline makes VAVE alternatives easy to evaluate and easy to justify in a design review
- The discipline fails when cost reduction is pursued without validating against actual functional requirements
Frequently asked questions
What is VAVE?
Value Analysis and Value Engineering — a structured method for evaluating design, material, or process alternatives to reduce cost or improve function without compromising a part's required performance.
What is the difference between value analysis and value engineering?
Value engineering happens during design, before a part is released to production. Value analysis happens on a part already in production, reviewing it against current cost and process options. Both follow the same underlying method.
Is VAVE the same as cost cutting?
No — cost cutting reduces price without necessarily checking function. VAVE specifically tests whether a proposed change still delivers the part's required function before it's adopted, which is what distinguishes it from an unstructured cost reduction exercise.
What kinds of changes typically come out of a VAVE workshop?
Material substitution, process changes, part consolidation, tolerance relaxation, and supplier changes are the most common categories — often several of each generated in a single structured workshop against one part or assembly.
Do you need a should-cost model to run VAVE?
It's not strictly required, but it makes the process far more effective — a defensible should-cost baseline lets a VAVE team evaluate each proposed alternative against a real cost number, rather than relying on supplier quotes or intuition.
