Unit 5: Value Engineering Studies
Expert-defined terms from the Professional Certificate in Value Engineering course at London School of Business and Administration. Free to read, free to share, paired with a professional course.
Alternative Analysis #
Alternative Analysis
Concept #
Systematic comparison of different design or construction options.
Explanation #
This process evaluates each alternative against functional requirements, cost, risk, and schedule to identify the most advantageous solution.
Example #
Comparing steel versus aluminum framing for a warehouse roof to determine which delivers required span strength at lower life‑cycle cost.
Practical application #
Used early in project definition to shape scope and budget.
Challenges #
Requires reliable data for each alternative; bias can emerge if stakeholder preferences dominate the analysis.
Baseline Cost #
Baseline Cost
Concept #
The reference cost against which value‑engineering savings are measured.
Explanation #
It represents the originally projected cost before any value‑engineering study, often derived from the preliminary estimate.
Example #
A baseline cost of $15 million for a municipal building serves as the benchmark for subsequent savings.
Practical application #
Enables clear quantification of cost‑saving opportunities.
Challenges #
Baseline may be inaccurate if based on outdated assumptions, leading to misleading savings percentages.
Benefit‑Cost Ratio (BCR) #
Benefit‑Cost Ratio (BCR)
Concept #
Quantitative indicator of economic efficiency.
Explanation #
Calculated by dividing total benefits by total costs; a BCR greater than 1.0 indicates a favorable investment.
Example #
A BCR of 1.8 for a daylight‑harvesting system shows that projected energy savings are 80 % higher than the installation cost.
Practical application #
Helps prioritize value‑engineering proposals.
Challenges #
Assigning monetary values to intangible benefits (e.g., improved user comfort) can be subjective.
Brief of Requirements (BOR) #
Brief of Requirements (BOR)
Concept #
Document that outlines functional and performance needs.
Explanation #
The BOR captures the essential objectives that the design must satisfy, serving as the foundation for functional analysis.
Example #
A BOR for a hospital wing may include “provide 24‑hour patient monitoring” as a functional need.
Practical application #
Guides the identification of unnecessary costs.
Challenges #
Incomplete or ambiguous BORs can lead to misdirected value‑engineering efforts.
Cost Function #
Cost Function
Concept #
Mathematical relationship linking cost to design variables.
Explanation #
It expresses how changes in size, material, or process affect overall cost, enabling rapid cost estimation during alternative evaluation.
Example #
Cost = a + b·(area)^0.8 for interior finish material, where “a” and “b” are calibrated coefficients.
Practical application #
Used in early‑stage screening of alternatives.
Challenges #
Accuracy depends on the quality of historical data and relevance to the current project.
Cost Reduction #
Cost Reduction
Concept #
Decrease in projected cost without sacrificing required functions.
Explanation #
Achieved through redesign, material substitution, process improvement, or scope modification.
Example #
Replacing custom‑fabricated steel brackets with standard‑size brackets reduces material and labor costs by 12 %.
Practical application #
Primary objective of value‑engineering studies.
Challenges #
Must avoid hidden costs that emerge later in construction or operation.
Cost Savings #
Cost Savings
Concept #
Monetary amount saved relative to the baseline.
Explanation #
Calculated as Baseline Cost minus Revised Cost after implementing a value‑engineering proposal.
Example #
A $500 k reduction on a $20 million project yields a 2.5 % overall saving.
Practical application #
Demonstrates the financial impact of value‑engineering recommendations.
Challenges #
Savings must be validated against realistic performance expectations.
Critical Path Method (CPM) #
Critical Path Method (CPM)
Concept #
Scheduling technique that identifies the sequence of activities determining project duration.
Explanation #
By analyzing activity durations and dependencies, CPM highlights tasks where time reductions can yield schedule benefits.
Example #
Accelerating the structural steel erection critical path by 10 days reduces overall construction time.
Practical application #
Supports value‑engineering proposals that target schedule improvements.
Challenges #
Over‑compression may increase risk or cost; accurate activity estimates are essential.
Function #
Function
Concept #
The purpose or service that a component provides.
Explanation #
In value engineering, functions are expressed in a “verb‑noun” format (e.g., “support weight”).
Example #
The function of a curtain wall is “enclose building envelope.”
Practical application #
Basis for identifying cheaper ways to achieve the same function.
Challenges #
Misidentifying functions can lead to inappropriate alternatives.
Functional Analysis #
Functional Analysis
Concept #
Systematic breakdown of a product or system into its constituent functions.
Explanation #
By separating essential from non‑essential functions, analysts can target cost reduction while preserving performance.
Example #
A FAST diagram for a parking garage may reveal that “provide vehicle shelter” is the primary function, while “enhance aesthetic appeal” is secondary.
Practical application #
Drives the generation of value‑engineering ideas.
Challenges #
Requires multidisciplinary expertise to capture all functional interdependencies.
Functional Cost #
Functional Cost
Concept #
Portion of total cost attributed to a specific function.
Explanation #
Determined by assigning cost to each function based on its contribution to the overall system.
Example #
In a HVAC system, the “condition air” function may account for 45 % of total system cost.
Practical application #
Highlights high‑cost functions where value engineering can have greatest impact.
Challenges #
Allocation can be ambiguous when functions are tightly coupled.
Functional Cost Ratio (FCR) #
Functional Cost Ratio (FCR)
Concept #
Ratio of functional cost to total project cost.
Explanation #
FCR = (Function Cost ÷ Total Cost) × 100 %; higher ratios indicate functions that dominate expense.
Example #
An FCR of 30 % for “structural support” signals a prime candidate for cost‑saving measures.
Practical application #
Prioritizes focus areas for the value‑engineering team.
Challenges #
Requires accurate functional cost estimates; errors distort prioritization.
Functional Requirement (FR) #
Functional Requirement (FR)
Concept #
Specification that defines what a function must achieve.
Explanation #
FRs set measurable targets (e.g., load capacity, thermal resistance) that alternatives must meet.
Example #
FR for a fire‑resistant wall: “maintain integrity for 2 hours under fire exposure.”
Practical application #
Ensures that cost reductions do not compromise essential performance.
Challenges #
Over‑specification can limit viable alternatives; under‑specification may lead to non‑compliant solutions.
Functional Specification #
Functional Specification
Concept #
Document describing functions and their performance standards.
Explanation #
Provides the language for translating user needs into design criteria.
Example #
A functional specification for a lighting system may state “deliver 300 lux average illumination on work planes.”
Practical application #
Serves as a reference during alternative evaluation.
Challenges #
Ambiguities in wording can cause misinterpretation of intent.
Function‑Cost Matrix #
Function‑Cost Matrix
Concept #
Tabular tool that cross‑references functions with associated costs.
Explanation #
The matrix lists each function alongside its cost, enabling quick visual identification of cost drivers.
Example #
A matrix showing “water distribution” at $2 million and “metering” at $0.3 million.
Practical application #
Facilitates brainstorming sessions by highlighting high‑cost functions.
Challenges #
Maintaining accuracy requires frequent updates as design evolves.
Function‑Based Design #
Function‑Based Design
Concept #
Design approach that starts with functions and works outward to solutions.
Explanation #
Designers ask “what must be done?” before “how will it be done,” encouraging innovative, cost‑effective solutions.
Example #
Instead of specifying a concrete slab, the team asks “support floor loads” and then explores steel decking, timber joists, or prefabricated panels.
Practical application #
Aligns design decisions with client objectives.
Challenges #
May conflict with traditional “material‑first” mindsets in some firms.
Function Identification #
Function Identification
Concept #
Process of naming and describing each function within a system.
Explanation #
Typically performed using workshops, interviews, and document reviews.
Example #
Identifying “allow natural ventilation” as a function for an office façade.
Practical application #
Foundation for generating alternative ideas.
Challenges #
Over‑looking minor functions can result in missed savings.
Function Index #
Function Index
Concept #
Metric that ranks functions by cost impact.
Explanation #
Calculated by dividing each function’s cost by the total cost, then ordering descending.
Example #
Function Index shows “foundation” at 22 %, “roof system” at 18 %, etc.
Practical application #
Directs the value‑engineering team to the most lucrative targets.
Challenges #
Dependent on reliable cost data; any error propagates through the ranking.
Function‑Performance Matrix #
Function‑Performance Matrix
Concept #
Grid that maps functions against performance criteria.
Explanation #
Helps assess how each alternative satisfies functional and performance goals.
Example #
Matrix comparing “thermal insulation” function against R‑value, cost, and installation time.
Practical application #
Supports decision‑making when multiple criteria compete.
Challenges #
Balancing quantitative and qualitative criteria can be subjective.
Function‑Structure Diagram #
Function‑Structure Diagram
Concept #
Visual representation linking functions to physical components.
Explanation #
Shows which components fulfill each function, clarifying interdependencies.
Example #
Diagram linking “support load” function to columns, beams, and foundations.
Practical application #
Reveals opportunities for component consolidation or substitution.
Challenges #
Complex systems may produce intricate diagrams that are hard to interpret.
Function‑Value Ratio (FVR) #
Function‑Value Ratio (FVR)
Concept #
Ratio of functional cost to functional value (benefit).
Explanation #
FVR = (Function Cost ÷ Function Value) × 100 %; lower values indicate higher value.
Example #
A function with cost $200 k and value $800 k yields an FVR of 25 %.
Practical application #
Prioritizes functions where cost reductions will most improve overall value.
Challenges #
Assigning monetary value to functions (especially non‑tangible) can be contentious.
General Cost Model #
General Cost Model
Concept #
Broad‑scale model that predicts cost based on generic parameters.
Explanation #
Utilizes industry‑wide data to estimate cost for early‑stage designs where detailed quantities are unavailable.
Example #
Using a cost per square foot model for office building shell estimation.
Practical application #
Provides quick cost feedback during brainstorming.
Challenges #
May lack precision for unique or innovative designs; requires calibration to local market conditions.
Gross Savings #
Gross Savings
Concept #
Total monetary reduction before accounting for implementation expenses.
Explanation #
Calculated as Baseline Cost minus Revised Cost; does not subtract the cost of the change itself.
Example #
A proposal reduces project cost by $1 million; gross savings = $1 million.
Practical application #
Initial metric to gauge the attractiveness of a proposal.
Challenges #
Must be adjusted for implementation costs to avoid overstating benefits.
Implementation Cost #
Implementation Cost
Concept #
Expenses incurred to apply a value‑engineering change.
Explanation #
Includes engineering, procurement, labor, and potential disruption costs.
Example #
Installing a prefabricated wall system saves $200 k but requires $30 k additional fabrication coordination; implementation cost = $30 k.
Practical application #
Subtracted from gross savings to determine net benefit.
Challenges #
Often underestimated, leading to reduced actual savings.
Incremental Cost #
Incremental Cost
Concept #
Additional cost associated with a specific change relative to the baseline.
Explanation #
Represents the net effect of the change after accounting for both added and eliminated costs.
Example #
Switching from copper to aluminum wiring adds $15 k in material but saves $10 k in labor; incremental cost = $5 k.
Practical application #
Helps assess whether a proposal truly reduces overall cost.
Challenges #
Requires detailed cost breakdowns for accurate calculation.
Integrated Project Delivery (IPD) #
Integrated Project Delivery (IPD)
Concept #
Collaborative project delivery method that aligns all participants toward shared goals.
Explanation #
IPD contracts incentivize cost and schedule performance, making value‑engineering efforts more effective.
Example #
An IPD project for a hospital includes owner, architect, and contractor sharing savings from a value‑engineering study.
Practical application #
Encourages early stakeholder involvement and transparent cost data.
Challenges #
Requires cultural shift and legal frameworks to manage risk sharing.
Life‑Cycle Cost (LCC) #
Life‑Cycle Cost (LCC)
Concept #
Total cost of ownership from acquisition through disposal.
Explanation #
LCC aggregates capital, operation, maintenance, and end‑of‑life costs, discounted to present value.
Example #
A high‑efficiency HVAC system may have higher upfront cost but lower energy expenses, resulting in lower LCC over 20 years.
Practical application #
Supports decisions that favor long‑term value over short‑term savings.
Challenges #
Accurate forecasting of future energy prices and maintenance needs is difficult.
Life‑Cycle Assessment (LCA) #
Life‑Cycle Assessment (LCA)
Concept #
Environmental impact analysis covering a product’s entire life.
Explanation #
Quantifies resources consumed and emissions produced at each stage (raw material extraction, manufacturing, use, disposal).
Example #
LCA shows that recycled steel frames have 30 % lower embodied carbon than virgin steel.
Practical application #
Integrates environmental considerations into value‑engineering decisions.
Challenges #
Data intensity and methodological variability can complicate comparisons.
Macro‑Value Engineering #
Macro‑Value Engineering
Concept #
Value‑engineering study applied at program or portfolio level.
Explanation #
Examines multiple projects or a whole program to identify systemic cost‑saving opportunities.
Example #
Reviewing a series of school construction projects to standardize wall systems and achieve economies of scale.
Practical application #
Generates large‑scale savings and policy recommendations.
Challenges #
Requires coordination across diverse project teams and alignment of objectives.
Market Price Index #
Market Price Index
Concept #
Statistical indicator reflecting changes in construction material costs.
Explanation #
Used to adjust baseline cost estimates to current market conditions.
Example #
Applying a 4 % increase from the latest steel price index to a baseline estimate.
Practical application #
Keeps value‑engineering proposals realistic under fluctuating market rates.
Challenges #
Index may not capture regional variations or specific product shortages.
MEP (Mechanical, Electrical, Plumbing) #
MEP (Mechanical, Electrical, Plumbing)
Concept #
Integrated system of building services.
Explanation #
MEP components often present significant cost and schedule opportunities for value‑engineering analysis.
Example #
Consolidating HVAC ductwork with plumbing riser shafts reduces penetrations and material waste.
Practical application #
Early MEP involvement can uncover savings before detailed design.
Challenges #
Complex interdependencies can make changes risky if not fully coordinated.
Methodology #
Methodology
Concept #
Structured approach used to conduct a value‑engineering study.
Explanation #
Typically includes phases such as information gathering, functional analysis, idea generation, evaluation, and implementation.
Example #
A five‑step methodology adopted by a consultancy: (1) Define scope, (2) Perform functional analysis, (3) Generate alternatives, (4) Evaluate proposals, (5) Document savings.
Practical application #
Provides consistency across projects and facilitates training.
Challenges #
Rigid adherence may limit creativity; flexibility is needed for unique project contexts.
Net Savings #
Net Savings
Concept #
Gross savings minus implementation cost.
Explanation #
Represents the true financial benefit after accounting for all expenses associated with the change.
Example #
Gross savings of $250 k less implementation cost of $30 k yields net savings of $220 k.
Practical application #
Primary metric presented to senior management for decision approval.
Challenges #
Accurate estimation of implementation cost is essential; otherwise net savings can be overstated.
Net Present Value (NPV) #
Net Present Value (NPV)
Concept #
Present value of net cash flows over a project's life.
Explanation #
NPV = ∑ (Cash Flow_t ÷ (1 + r)^t) where r is the discount rate; positive NPV indicates a financially viable option.
Example #
An energy‑saving retrofit with an NPV of $150 k over 10 years signals a worthwhile investment.
Practical application #
Allows comparison of proposals with different cash‑flow timing.
Challenges #
Selecting an appropriate discount rate and forecasting future cash flows involve judgment.
Non‑Value‑Adding Activity (NVA) #
Non‑Value‑Adding Activity (NVA)
Concept #
Task that consumes resources without contributing to functional value.
Explanation #
Identified during process mapping; eliminating NVA can reduce cost and schedule.
Example #
Redundant design review cycles that do not improve quality are NVA.
Practical application #
Streamlines the value‑engineering workflow.
Challenges #
Stakeholders may resist removal of familiar but inefficient practices.
Opportunity Cost #
Opportunity Cost
Concept #
Value of the best alternative foregone when a decision is made.
Explanation #
In value engineering, recognizing opportunity cost helps justify a change that may have higher upfront expense but yields greater overall benefit.
Example #
Choosing a higher‑specification façade that costs $100 k more but saves $300 k in energy over 20 years.
Practical application #
Provides a broader perspective beyond immediate cost.
Challenges #
Quantifying intangible benefits (e.g., brand image) can be difficult.
Optimisation #
Optimisation
Concept #
Process of making a system as effective as possible within given constraints.
Explanation #
In value engineering, optimisation seeks the lowest cost that still meets functional requirements.
Example #
Using linear programming to allocate material quantities that minimise total cost while satisfying structural strength constraints.
Practical application #
Generates data‑driven recommendations.
Challenges #
Model complexity and data availability may limit practical use.
Owner’s Objectives #
Owner’s Objectives
Concept #
Goals that the project owner aims to achieve.
Explanation #
May include cost minimisation, schedule acceleration, sustainability, and risk mitigation.
Example #
An owner prioritises “minimum life‑cycle cost” for a public school building.
Practical application #
Guides the focus of the value‑engineering study.
Challenges #
Conflicting objectives (e.g., low cost vs high sustainability) require trade‑off analysis.
Pareto Principle (80/20 Rule) #
Pareto Principle (80/20 Rule)
Concept #
Approximation that 80 % of effects come from 20 % of causes.
Explanation #
Applied in value engineering to concentrate effort on the few functions that drive most of the cost.
Example #
Identifying that 70 % of total cost is tied to structural framework and façade systems.
Practical application #
Efficient allocation of analysis resources.
Challenges #
Not all projects follow the exact 80/20 distribution; misapplication may overlook smaller, high‑impact items.
Performance Specification #
Performance Specification
Concept #
Document that defines the required performance of a system without prescribing how to achieve it.
Explanation #
Allows designers to explore multiple solutions that meet the same performance target.
Example #
Specifying “U‑value ≤ 0.30 W/m²·K” for walls rather than dictating specific insulation material.
Practical application #
Encourages innovative, cost‑effective alternatives.
Challenges #
Stakeholders may demand specific products, limiting flexibility.
Plan of Execution (POE) #
Plan of Execution (POE)
Concept #
Detailed schedule and resource allocation for implementing value‑engineering changes.
Explanation #
Outlines tasks, responsibilities, timelines, and milestones required to realise approved proposals.
Example #
POE for a façade redesign includes design finalisation (2 weeks), procurement (4 weeks), and installation (6 weeks).
Practical application #
Ensures that savings are realised on time.
Challenges #
Integration with existing project schedule can be complex; delays may erode anticipated benefits.
Portfolio Value Engineering #
Portfolio Value Engineering
Concept #
Application of value‑engineering principles across a collection of projects.
Explanation #
Enables organisations to standardise components, leverage bulk purchasing, and share best practices.
Example #
A government agency implements a common modular wall system across 12 schools, achieving cumulative savings of $5 million.
Practical application #
Drives systemic cost efficiencies.
Challenges #
Requires coordination among diverse project teams and alignment of specifications.
Preliminary Cost Estimate #
Preliminary Cost Estimate
Concept #
Early‑stage cost projection based on limited design information.
Explanation #
Typically expressed as a range (e.g., ± 30 %) and used to set budget expectations.
Example #
A preliminary estimate of $10 million for a community centre informs the feasibility study.
Practical application #
Provides the baseline for evaluating value‑engineering savings.
Challenges #
High uncertainty can affect the perceived magnitude of savings.
Project Charter #
Project Charter
Concept #
Formal document authorising a project and outlining its objectives, scope, and stakeholders.
Explanation #
In value‑engineering studies, the charter defines the authority to conduct analysis and implement changes.
Example #
Charter authorises a $200 k budget for a value‑engineering workshop on a hospital expansion.
Practical application #
Secures senior management support and resource allocation.
Challenges #
Inadequate charter detail may lead to scope creep or insufficient authority.
Project Scope #
Project Scope
Concept #
The totality of work required to deliver the project’s objectives.
Explanation #
Clear scope definition is essential to avoid “scope creep” that can mask true savings.
Example #
Scope includes structural, envelope, and interior finishes but excludes site landscaping.
Practical application #
Guides functional analysis and alternative generation.
Challenges #
Over‑broad scope can dilute focus; overly narrow scope may miss valuable opportunities.
Quality Function Deployment (QFD) #
Quality Function Deployment (QFD)
Concept #
Methodology that translates customer requirements into design specifications.
Explanation #
QFD matrices link desired qualities to engineering characteristics, supporting value‑engineering decisions.
Example #
Mapping “energy efficiency” requirement to HVAC system sizing, insulation thickness, and glazing type.
Practical application #
Aligns cost‑saving ideas with customer priorities.
Challenges #
Requires extensive data collection and cross‑functional collaboration.
Rate of Return (ROR) #
Rate of Return (ROR)
Concept #
Percentage gain on an investment over a period.
Explanation #
Calculated as (Net Savings ÷ Implementation Cost) × 100 %; higher ROR indicates more attractive proposals.
Example #
A proposal with net savings of $200 k and implementation cost of $40 k yields a ROR of 500 %.
Practical application #
Helps rank proposals when budget is limited.
Challenges #
Does not consider time value of money; should be used alongside NPV.
Reference Project #
Reference Project
Concept #
Previously completed project used as a benchmark.
Explanation #
Provides cost, schedule, and performance data for comparative analysis.
Example #
Using the cost data from a 2018 office tower to estimate baseline for a similar 2026 project.
Practical application #
Improves accuracy of cost functions and savings forecasts.
Challenges #
Differences in location, codes, or technology may limit relevance.
Regression Analysis #
Regression Analysis
Concept #
Statistical method to model relationship between variables.
Explanation #
Generates cost equations by fitting historical data to predictors such as area, volume, or material type.
Example #
Deriving a cost per square foot model for concrete floors based on past projects.
Practical application #
Enables rapid cost estimation for alternative designs.
Challenges #
Quality of the model depends on data integrity and relevance.
Reliability Index #
Reliability Index
Concept #
Metric assessing the confidence level of cost or schedule estimates.
Explanation #
Higher index indicates greater estimate stability; often expressed as a probability (e.g., 80 % confidence).
Example #
A reliability index of 0.9 for a cost estimate suggests low variance.
Practical application #
Guides risk mitigation strategies.
Challenges #
Requires robust statistical analysis; may be misunderstood by non‑technical stakeholders.
Return on Investment (ROI) #
Return on Investment (ROI)
Concept #
Ratio of net benefit to investment cost.
Explanation #
ROI = (Net Savings ÷ Implementation Cost) × 100 %; expressed as a percentage.
Example #
ROI of 250 % indicates that for every dollar spent, $2.50 of net benefit is realised.
Practical application #
Communicates financial value in familiar business terms.
Challenges #
Does not account for time value of money; should be complemented with NPV.
Risk Register #
Risk Register
Concept #
Document listing identified risks, their impacts, and mitigation actions.
Explanation #
In value‑engineering studies, the register tracks risks introduced by proposed changes.
Example #
Risk of schedule delay due to unfamiliar prefabricated wall installation.
Practical application #
Supports informed decision‑making and contingency planning.
Challenges #
Maintaining an up‑to‑date register requires ongoing monitoring.
Risk Management #
Risk Management
Concept #
Systematic process of identifying, analysing, and responding to project risks.
Explanation #
Ensures that cost‑saving proposals do not create unacceptable new risks.
Example #
Conducting a risk assessment before adopting a novel fire‑suppression system.
Practical application #
Balances cost reduction with project resilience.
Challenges #
Over‑focus on risk avoidance may suppress innovative ideas.
Schedule Compression #
Schedule Compression
Concept #
Techniques used to shorten project duration.
Explanation #
Value engineering may propose design changes that reduce construction time, yielding schedule savings.
Example #
Prefabricated structural modules cut erection time by 30 %.
Practical application #
Provides additional value when time is a critical driver.
Challenges #
Accelerated schedules can increase labor costs or reduce quality if not managed carefully.
Scope Creep #
Scope Creep
Concept #
Uncontrolled expansion of project scope without corresponding adjustments to time, cost, or resources.
Explanation #
Can mask the true effectiveness of value‑engineering savings.
Example #
Adding extra lobby finishes after the value‑engineering study is complete.
Practical application #
Requires strict change control to preserve documented savings.
Challenges #
Stakeholder demands and regulatory changes often fuel creep.
Stakeholder Analysis #
Stakeholder Analysis
Concept #
Identification and assessment of individuals or groups affected by the project.
Explanation #
Determines who must be consulted or convinced for value‑engineering proposals to be accepted.
Example #
Engaging facility managers early to validate maintenance cost assumptions.
Practical application #
Enhances adoption of cost‑saving ideas.
Challenges #
Conflicting stakeholder priorities may impede consensus.
Standard Cost Code #
Standard Cost Code
Concept #
Predefined coding system for categorising costs.
Explanation #
Enables consistent tracking and reporting of savings across projects.
Example #
Using CSI MasterFormat codes to capture “03 – Concrete” expenses.
Practical application #
Facilitates aggregation of functional cost data.
Challenges #
Inconsistent use across disciplines can lead to misallocation.
Strategic Value Engineering #
Strategic Value Engineering
Concept #
Long‑term, organization‑wide approach to embed value‑engineering principles.
Explanation #
Aligns procurement, design standards, and training with value‑engineering objectives.
Example #
A utility company adopts a corporate policy to evaluate all new plant designs through a value‑engineering lens.
Practical application #
Generates sustained, cumulative savings.
Challenges #
Requires cultural change and senior‑leadership commitment.
Sustainability Index #
Sustainability Index
Concept #
Metric that combines environmental, social, and economic performance.
Explanation #
Allows comparison of alternatives on broader value beyond cost alone.
Example #
An alternative wall system scores 0.85 on the sustainability index versus 0.70 for the baseline.
Practical application #
Supports decisions where environmental stewardship is a priority.
Challenges #
Quantifying social impacts can be subjective; weighting of criteria may vary.
Target Cost #
Target Cost
Concept #
Desired cost level after applying value‑engineering measures.
Explanation #
Established by the owner or project sponsor as a benchmark for savings.
Example #
Target cost of $12 million for a $15 million baseline project implies a 20 % reduction goal.
Practical application #
Drives the intensity of the value‑engineering effort.
Challenges #
Unrealistically low targets may encourage undesirable compromises.
Technical Feasibility #
Technical Feasibility
Concept #
Assessment of whether an alternative can be practically implemented.
Explanation #
Considers material availability, skill requirements, code compliance, and constructability.
Example #
Evaluating whether a high‑strength composite panel can be installed with existing crew skills.
Practical application #
Filters out ideas that are theoretically attractive but impractical.
Challenges #
May be underestimated if specialized expertise is lacking.
Trade‑off Analysis #
Trade‑off Analysis
Concept #
Systematic comparison of competing objectives (e.g., cost vs. performance).
Explanation #
Quantifies the impact of choosing one alternative over another across multiple dimensions.
Example #
Selecting a façade material that reduces cost by 10 % but lowers insulation R‑value by 15 %.
Practical application #
Provides balanced recommendations to decision makers.
Challenges #
Requires agreeing on weighting factors for disparate criteria.
Value #
Value
Concept #
Ratio of function to cost; higher value means more function per unit cost.
Explanation #
Core principle that guides the search for cost‑effective solutions.
Example #
Replacing a custom‑fabricated metal railing with a standard‑size rail reduces cost while maintaining safety function, thus increasing value.
Practical application #
The ultimate metric for evaluating proposals.
Challenges #
Function must be correctly defined; otherwise value calculations become misleading.
Value Index #
Value Index
Concept #
Numerical indicator that ranks functions or alternatives based on their value.
Explanation #
Calculated as Function Value ÷ Function Cost; higher index signals better value.
Example #
A lighting system with an index of 4.2 versus 2.8 for the baseline indicates superior value.
Practical application #
Prioritises which functions merit deeper analysis.
Challenges #
Assigning monetary value to non‑monetary functions can be contentious.
Value Engineering Change Statement (VECS) #
Value Engineering Change Statement (VECS)
Concept #
Formal document describing a proposed change, its justification, and expected savings.
Explanation #
Includes description, affected drawings, cost estimate, schedule impact, and risk assessment.
Example #
VECS for substituting a standard door hardware set outlines a $12 k saving and 2‑day installation reduction.
Practical application #
Provides a transparent record for approval and audit.
Challenges #
Requires detailed data; incomplete statements may be rejected.
Value Engineering Study (VES) #
Value Engineering Study (VES)
Concept #
Comprehensive analysis to improve project value by reducing cost while maintaining function.
Explanation #
Conducted in phases (information, function, creative, evaluation, development, presentation) to systematically generate and implement savings.
Example #
A VES on a hospital wing identified $1.2 million in savings through façade redesign and equipment standardisation.
Practical application #
Core deliverable of Unit 5.
Challenges #
Time‑intensive; success depends on stakeholder participation and data quality.
Value Engineering Workshop #
Value Engineering Workshop
Concept #
Collaborative session where multidisciplinary participants generate ideas.
Explanation #
Facilitated by a value‑engineering leader, the workshop uses techniques such as “what‑if” analysis to stimulate innovative alternatives.
Example #
A two‑day workshop yields 45 ideas, of which 12 become formal proposals.
Practical application #
Accelerates idea generation and fosters team ownership.
Challenges #
Dominant personalities may skew ideas; structured facilitation is essential.
Value Engineering Leader (VEL) #
Value Engineering Leader (VEL)
Concept #
Individual responsible for guiding the value‑engineering process.
Explanation #
Tasks include planning, data collection, leading workshops, evaluating proposals, and reporting savings.
Example #
A senior engineer appointed as VEL coordinates between design and construction teams.
Practical application #
Ensures methodological consistency and alignment with project goals.
Challenges #
Balancing VEL duties with other project responsibilities can be demanding.
Value Engineering Report (VER) #
Value Engineering Report (VER)
Concept #
Formal document summarising study results, proposals, and savings.
Explanation #
Includes executive summary, methodology, functional analysis, alternative evaluation, and financial analysis.
Example #
VER for a civic centre presents $2 million in net savings with a 12‑month schedule reduction.
Practical application #
Serves as the basis for senior management approval.
Challenges #
Must be clear, concise, and supported by robust data to gain acceptance.
Value Index #
Value Index
Concept #
Metric expressing the relationship between function and cost for a given alternative.
Explanation #
Calculated as (Function Value ÷ Cost) × 100; higher values denote more efficient solutions.
Example #
Alternative A has a value index of 1.8 versus baseline 1.0, indicating superior value.
Practical application #
Assists in ranking alternatives objectively.
Challenges #
Requires consistent valuation methodology across alternatives.
Value Management #
Value Management
Concept #
Systematic approach to maximise function while minimising cost throughout a project’s life‑cycle.
Explanation #
Extends beyond design to include procurement, construction, operation, and disposal phases.
Example #
Implementing a maintenance‑friendly mechanical system that reduces O&M costs by 15 % over 20 years.
Practical application #
Aligns all project decisions with long‑term value objectives.
Challenges #
Requires continuous monitoring and willingness to adapt after handover.
Value Proposition #
Value Proposition
Concept #
Statement that articulates the benefits of a proposed change to stakeholders.
Explanation #
Communicates how the alternative delivers functional, financial, or strategic advantages.
Example #
“Adopting modular wall panels reduces construction time by 20 % and yields $300 k in net savings.”
Practical application #
Persuades decision makers to adopt the recommendation.
Challenges #
Must be tailored to the audience’s priorities; overly technical language may hinder acceptance.
Value‑Engineering Change #
Value‑Engineering Change
Concept #
Approved modification resulting from a value‑engineering study.
Explanation #
Captures the revised design, cost impact, schedule effect, and risk mitigation.
Example #
Substituting a high‑performance glazing system with a lower‑cost alternative that still meets daylighting requirements.
Practical application #
Realises the documented savings.
Challenges #
Requires rigorous verification to ensure functional equivalence.
Value‑Engineering Cost Model #
Value‑Engineering Cost Model
Concept #
Predictive model that estimates the cost impact of functional changes.
Explanation #
Integrates functional cost data with cost‑saving coefficients derived from historical studies.
Example #
Model predicts a 7 % cost reduction for each