Value Engineering That Nobody Asked For
Midway through detailed design of a $90M water treatment plant, you run a value-engineering workshop. The design team proposes a VE alternative that swaps a conventional clarifier train for a membrane system. Capital cost rises by $7M, but the alternative reduces footprint by 40%, cuts chemical operating cost by $900k/yr, and lowers energy use by $400k/yr. It also shortens construction by four months on a site where the owner incurs $250k/month in interim trucking costs. The owner's operations manager is hostile - she was not consulted and believes membranes are 'high maintenance.' The design team has already told the owner the current design is 'complete.'
1. Should this VE alternative be advanced? Show the value case quantitatively and address the non-financial objections.
Read the worked answer
Advance it, but as a decision for the owner, not a fait accompli.
Quantified value (annual, undiscounted):
- Chemical saving: +$900k
- Energy saving: +$400k
- Interim trucking avoided: $250k × 4 months = +$1.0M one-off
- Total recurring benefit: $1.3M/yr
- Capital premium: $7M
- Simple payback on recurring benefits alone: 7.0 / 1.3 ≈ 5.4 years; including the $1.0M one-off, ≈ 4.6 years.
Over a 25-year asset life the recurring benefit is $32.5M against a $7M premium - a strong value case, subject to discounting and to the maintenance-cost assumption.
The real risk is the operations manager, not the numbers. Her objection is legitimate because she will own the asset for decades and was excluded. Do not steamroll her. Instead: (a) acknowledge the design was presented as complete - that was a process failure, own it; (b) convert 'high maintenance' into a testable claim by requesting whole-life maintenance data from comparable installations, including membrane replacement cycles; (c) add membrane replacement to the life-cycle cost model, since it is the single assumption most likely to erode the payback; (d) offer her a role in evaluating the alternative.
If the maintenance data materially worsens the payback, the recommendation should change. That is the point of VE - it is a value test, not a sales pitch.
2. How should the VE study have been structured to avoid this situation?
Read the worked answer
The failure was sequencing and stakeholder scope, not analysis quality.
- VE should run at concept/preliminary design, not after the owner has been told design is complete. The later it runs, the more it reads as criticism of completed work and the more rework it triggers.
- The function analysis should have started from the owner's value criteria - whole-life cost, operability, footprint, resilience - not from the design team's preferred solution. 'High maintenance' is a value criterion; if it had been captured at the start, the maintenance question would have been an input rather than a late objection.
- The operations manager should have been on the workshop team. Operations is a stakeholder with life-cycle ownership; excluding them guarantees resistance.
- The VE team needs the whole-life cost model, including replacement and consumables, before the workshop, so options are compared on the same basis.
- Report through a decision memo to the owner, framing options and trade-offs, rather than presenting a recommendation as a correction.
Lesson: a VE proposal that the asset owner did not help shape will be judged on trust, not on payback.