Value Engineering
Value Engineering (VE) is a structured, function-oriented method for improving the value of a construction project, where value equals function divided by cost. In the PMI Construction Professional (PMI-CP) framework, VE sits within Scope and Change Order Management because it examines what the project must deliver and finds alternative ways to deliver those functions at lower life-cycle cost without sacrificing required performance, quality, safety, or reliability. VE is not simple cost cutting. Removing scope or downgrading quality to save money is scope reduction, not value engineering. True VE preserves or improves essential functions. VE usually follows the Value Methodology Job Plan, which has these phases: information gathering, function analysis (often using FAST diagrams to separate basic and secondary functions), creative brainstorming of alternatives, evaluation of ideas against cost, risk, schedule, and constructability, development of recommendations with supporting data, presentation to decision makers, and implementation. Multidisciplinary teams of designers, contractors, owners, facility operators, and specialists typically conduct VE workshops. Timing is critical. VE delivers the most benefit early, during concept and schematic design, when the cost of change is low and the ability to influence outcomes is high. Late VE often triggers redesign, rework, delays, and claims. From a change management perspective, any accepted VE proposal changes the scope baseline, so it must pass through the formal integrated change control process. That means impact analysis on cost, schedule, risk, and quality, approval by the change control board or owner, and updates to drawings, specifications, the scope statement, and the WBS. Many contracts include a Value Engineering Change Proposal (VECP) clause that lets contractors submit ideas after award and share the resulting savings with the owner, which encourages innovation. Project managers must document the original design intent, keep stakeholders aligned, verify compliance with codes and owner requirements, and track realized savings. Done well, VE optimizes life-cycle cost, constructability, sustainability, and stakeholder satisfaction.
Value Engineering in Construction Scope and Change Order Management (PMI-CP)
1. Introduction
Value Engineering (VE) is a structured, team-based method for improving the value of a project. The team analyzes the functions of a design, system, material, or process, then looks for other ways to deliver those functions at a lower life-cycle cost. Quality, performance, reliability, safety, and other owner requirements must not be reduced.
In the PMI-CP domain of Scope and Change Order Management, VE matters because it is a legitimate, controlled way to change scope or design. Any VE proposal that is accepted changes the project baseline. It therefore has to pass through the formal change control process.
2. Why Value Engineering Is Important
Cost optimization: VE often cuts project costs, commonly by 5 to 15 percent of the studied elements. It does this without giving up the function the owner needs.
Life-cycle thinking: VE looks at the total cost of ownership, not just the initial capital cost. That includes construction, operation, maintenance, energy, replacement, and disposal.
Scope clarity: Function analysis forces stakeholders to say what each element must actually do. This reduces ambiguity and scope creep.
Risk reduction: VE can find constructability problems, long-lead items, supply chain risks, and design conflicts early.
Stakeholder alignment: VE workshops bring together owners, designers, contractors, operators, and specialists. This builds shared understanding and buy-in.
Schedule improvement: Other materials or methods, such as prefabrication or modular construction, can shorten durations.
Sustainability: VE can bring in more energy-efficient or environmentally responsible options.
Contractual incentives: Many public and private contracts include VE clauses. Under these clauses, the contractor and owner share the savings from accepted Value Engineering Change Proposals (VECPs).
3. What Value Engineering Is
VE was developed by Lawrence D. Miles at General Electric in the 1940s, when material shortages during World War II forced engineers to find substitutes. Today SAVE International promotes it, and many government agencies require it on projects above certain cost thresholds. Examples include the U.S. Federal Highway Administration and the U.S. Army Corps of Engineers.
The Value Equation:
Value = Function / Cost
Value can go up in four ways:
- Keep the function the same and reduce the cost.
- Improve the function and keep the cost the same.
- Improve the function and reduce the cost, which is the ideal outcome.
- Improve the function a great deal with a modest cost increase, as long as the value ratio still rises.
Key Concepts:
Function: What an item must do, stated as an active verb plus a measurable noun. Examples are 'support load', 'enclose space', and 'control temperature'.
Basic function: The main purpose the item exists for.
Secondary functions: Supporting or aesthetic functions. Some are required and some may be unnecessary.
Life-Cycle Cost (LCC): The total cost over the asset's useful life.
FAST diagram: A Function Analysis System Technique diagram. It maps functions logically by asking HOW (moving right) and WHY (moving left).
What VE is NOT:
- It is not simply cost-cutting or 'cheapening' the project. Lowering quality or removing required functions is scope reduction, not VE.
- It is not a design review that only looks for errors.
- It is not a one-person activity. VE is a multidisciplinary team effort.
- It is not an excuse to bypass change control.
Related Terms:
Value Analysis: The same method applied to existing products or completed designs.
Value Management: A broader umbrella term covering VE across the whole project lifecycle.
Value Engineering Change Proposal (VECP): A formal proposal, usually from the contractor after award, that recommends a change to reduce cost while keeping function.
Constructability Review: A related but separate review focused on how buildable the design is.
4. When Value Engineering Should Be Performed
The ability to influence cost is highest early in the project and drops sharply as design progresses. The cost of making changes rises over time. So:
- Concept and schematic design (about 0 to 35 percent design): This is the best time for VE. Savings potential is greatest and the cost of change is lowest.
- Design development (about 35 to 60 percent): VE is still very effective.
- Construction documents: Changes cost more because of redesign.
- Construction phase: VE happens through VECPs submitted by contractors. Savings are still possible, but redesign, re-permitting, and schedule impacts reduce the net benefit.
Exam questions often test whether you know that early VE yields the greatest benefit.
5. How Value Engineering Works: The VE Job Plan
SAVE International describes a standard Job Plan with three main stages and six workshop phases.
Pre-Workshop (Preparation):
- Define the scope and objectives of the study.
- Select a multidisciplinary team led by a certified facilitator, often a CVS (Certified Value Specialist).
- Gather data: drawings, specifications, cost estimates, schedules, owner requirements, and constraints.
- Build cost models to find high-cost elements. The Pareto principle applies: about 20 percent of elements often make up about 80 percent of cost.
Workshop (the six phases):
Phase 1: Information. Understand the project, owner goals, constraints, and current design. Identify cost drivers.
Phase 2: Function Analysis. Define functions using verb-noun pairs. Classify them as basic or secondary. Build a FAST diagram. Calculate worth versus cost to find poor-value areas. This phase is what makes VE different from ordinary cost reduction.
Phase 3: Creative (Speculation). Brainstorm as many alternative ways to perform the functions as possible. Judgment is suspended, so quantity of ideas comes first.
Phase 4: Evaluation (Analysis). Screen and rank the ideas against criteria such as cost, performance, risk, schedule, and maintainability. Tools include weighted matrices, pros and cons lists, and life-cycle cost analysis.
Phase 5: Development. Turn the best ideas into written VE proposals. Each proposal includes technical details, sketches, cost estimates, life-cycle cost, risks, and implementation requirements.
Phase 6: Presentation. Present the recommendations to the owner and decision-makers.
Post-Workshop:
- Implementation: The owner accepts, rejects, or modifies each proposal. Accepted proposals go through formal change control. Baselines (scope, cost, schedule), drawings, and specifications are updated.
- Follow-up: Track the savings actually realized, document lessons learned, and update the organizational process assets.
6. Value Engineering in Contracts: VECPs and Savings Sharing
During construction, VE is usually handled through a Value Engineering Change Proposal (VECP) clause.
- The contractor identifies a way to reduce cost without reducing function, quality, or performance.
- The contractor submits a VECP with supporting documentation: a description, the cost comparison, schedule impacts, and any effects on other elements.
- The owner, together with the designer of record, reviews the VECP. The owner has the right to accept or reject it.
- If accepted, it is issued as a formal change order that modifies the contract.
- Net savings are shared according to the contract, often 50/50 between owner and contractor. Some government contracts use different splits, and some share future operation and maintenance savings.
- The designer of record should check technical adequacy. This protects design liability and preserves code compliance.
The savings-sharing incentive encourages contractors to bring their construction expertise forward instead of keeping cost savings to themselves.
7. Integration with Scope and Change Order Management
- Change control: Every accepted VE recommendation is a change. It must be documented, assessed for impact on scope, cost, schedule, quality, and risk, then approved by the appropriate authority, such as the Change Control Board or the owner. After that it is communicated and incorporated into the baselines.
- Scope baseline: The WBS, scope statement, and specifications may need updating.
- Cost and schedule baselines: Revised estimates and schedules must reflect the change.
- Quality management: Make sure the substitution meets the required standards, codes, and owner requirements.
- Risk management: New materials or methods can bring new risks. Examples include supplier reliability, unfamiliar installation methods, and warranty issues.
- Stakeholder engagement: End users, operators, regulators, and permitting authorities may need to be consulted.
- Documentation: Keep records of VE studies, decisions, and approvals. They support claims avoidance and audit trails.
8. Common Pitfalls
- Treating VE as cost-cutting that lowers quality or removes required scope.
- Doing VE too late, when changes are expensive.
- Skipping function analysis and going straight to brainstorming.
- Ignoring life-cycle costs. For example, choosing a cheaper roof that needs replacement twice as often.
- Not involving the designer of record, which creates liability and coordination problems.
- Putting accepted VE ideas in place without formal change orders or baseline updates.
- Team resistance, such as designers getting defensive. A skilled facilitator and a positive framing help prevent this.
9. Practical Example
A hospital design specifies a custom curtain wall system costing $4.2 million. The VE team does a function analysis. The basic function is 'enclose building', and the secondary functions are 'admit light', 'resist weather', and 'provide aesthetics'.
The team proposes a unitized, prefabricated curtain wall with equivalent thermal and structural performance. It costs $3.5 million and cuts installation time by 6 weeks. Life-cycle analysis shows equal or better energy performance. The owner approves.
The change goes through change control. The architect revises the drawings, the cost and schedule baselines are updated, and the contractor and owner share the savings according to the VECP clause. Function is kept, cost and schedule go down, and value goes up.
10. Exam Tips: Answering Questions on Value Engineering
Tip 1: Remember the core definition. VE keeps or improves function while reducing life-cycle cost. If an answer choice reduces quality, performance, or required scope, it is NOT value engineering. Watch for distractors that describe 'cheapening' the project.
Tip 2: Function analysis is the heart of VE. If asked what makes VE different from ordinary cost reduction, choose function analysis, verb-noun definitions, or FAST diagrams.
Tip 3: Early is best. Questions about timing usually reward the answer that places VE in the early design phases, when influence is highest and the cost of change is lowest.
Tip 4: VE changes still need change control. If a scenario describes a contractor or team member who wants to put a VE idea in place right away, the correct response is almost always to submit it through the formal change control process. That means a VECP or change request, impact analysis, and owner or CCB approval before implementation. Never choose 'implement immediately since it saves money'.
Tip 5: The owner decides. Owners, and designers of record for technical validity, approve or reject VE proposals. Contractors propose; they do not unilaterally decide.
Tip 6: Think life-cycle cost. If one option has a lower first cost but higher maintenance or operating costs, the VE-oriented answer weighs total cost of ownership.
Tip 7: Know the Job Plan order. The order is Information, Function Analysis, Creative, Evaluation, Development, Presentation, followed by implementation and follow-up. Questions may ask which phase comes next, or in which phase judgment is suspended. Judgment is suspended in the Creative phase.
Tip 8: Savings sharing. Understand that VECP clauses give contractors an incentive through shared savings. A question may ask why contracts include them. The answer is to encourage contractor innovation and cost reduction while keeping function.
Tip 9: Multidisciplinary team. VE is performed by a diverse team with a facilitator, not by one individual. Answers that involve key stakeholders, including operators and maintenance staff, are usually preferred.
Tip 10: Update the baselines and documents. After a VE proposal is approved, expect follow-on actions. These include updating the scope, cost, and schedule baselines, revising drawings and specifications, communicating with stakeholders, and recording lessons learned.
Tip 11: Distinguish related concepts.
- Constructability review focuses on buildability.
- Scope reduction removes deliverables.
- Gold plating adds unrequested features.
- VE optimizes function against cost.
Read carefully to find which concept the scenario describes.
Tip 12: Watch for ethical and quality red flags. If a 'VE' proposal would breach codes, safety standards, sustainability commitments, or contract specifications without approval, reject it or escalate it. PMI values professional responsibility and quality.
Tip 13: Use the value formula. If a question gives numbers, calculate Value = Function / Cost, or compare cost-to-worth ratios. A high cost-to-worth ratio, often greater than 2, signals a good VE opportunity.
Tip 14: Choose proactive answers. Exams generally favor responses where the project manager actively facilitates VE, analyzes impacts, consults stakeholders, and follows the process. Reactive or unilateral actions are usually wrong.
11. Quick Summary
- VE is a systematic, function-based, team approach to improving value.
- Value = Function / Cost, with life-cycle cost in view.
- The greatest benefit comes early in design.
- It follows a structured Job Plan with function analysis at its core.
- During construction it works through VECPs, often with shared savings.
- All accepted VE changes go through formal change control and baseline updates.
- VE never means sacrificing required quality, safety, or performance.
Master these principles and you will be ready to answer PMI-CP exam questions on Value Engineering confidently.
PMI-CP - Value Engineering Example Questions
Test your knowledge of Value Engineering
Question 1
In a Function Analysis System Technique (FAST) diagram used in value engineering, what does the function placed just outside the left scope line represent?
Question 2
In traditional value methodology usage, what distinguishes value analysis from value engineering?
Question 3
During the evaluation phase of a value engineering workshop for a transit station at 30% design, the team scores 40 ideas in a weighted criteria matrix. Every top-ranked idea cuts first cost but raises maintenance effort, yet the owner's business case stresses 40-year operations and station availability. The project manager learns that the design team set the criteria weights before the workshop, with no input from the owner. What should the project manager do NEXT?