Value engineering
Based on Wikipedia: Value engineering
In 1954, a shipyard in Philadelphia was tasked with building a vessel, but the blueprints called for a specific type of steel that simply did not exist due to wartime scarcity. The engineers at General Electric, led by Lawrence Miles, Jerry Leftow, and Harry Erlicher, did not halt production. Instead, they scoured the market for acceptable substitutes. What they discovered was accidental but profound: the alternative materials they found were not only available but often cheaper and, in some cases, superior to the original specifications. This moment of necessity birthed a systematic process that would eventually reshape the global economy, a methodology known initially as "value analysis" and later as "value engineering."
Value engineering is not merely about cutting costs; it is a rigorous, philosophical approach to the relationship between what something does and what it costs to make it do that. At its core lies a simple, almost mathematical definition: value is the ratio of function to cost. If you can improve the function while holding the cost steady, value rises. If you can hold the function steady while lowering the cost, value rises. The methodology posits that every component, material, and process in a product or project serves a specific function. The goal is to preserve the "basic function"—the essential reason the product exists—while ruthlessly eliminating the costs that do not contribute to that function.
This distinction is critical. In the world of value engineering, a screwdriver is not defined by its physical form as a tool for turning screws. If a worker is using that screwdriver to stir a can of paint, the screwdriver's function in that moment is not "turn screw," but "blend liquid." By stripping the object down to its most fundamental, non-descriptive verb-noun pairing—active verb, measurable noun—engineers can detach themselves from the assumption that the original design is the only way to achieve the result. This abstraction allows for radical innovation, but it also opens the door to a darker interpretation of efficiency that has haunted the modern industrial age.
The Genesis of Efficiency
The story of value engineering begins in the crucible of World War II. The United States, mobilizing for a global conflict, faced a paradox: it needed to produce an unprecedented volume of war materiel, yet it was choking on shortages of skilled labor, raw materials, and critical component parts. The supply chains were fractured, and the traditional engineering mindset of "use the best material available" was no longer viable.
At General Electric, Lawrence Miles and his team were forced to look for substitutes. They noticed a pattern that defied conventional wisdom. When they replaced a scarce, expensive material with a readily available alternative, the cost often dropped, but the product's performance did not suffer. In many instances, the substitute improved the product. They realized that the high cost of the original materials was not always a reflection of superior utility, but often a result of habit, lack of information, or rigid specification.
Miles, Leftow, and Erlicher codified these observations into a technique they called "value analysis" or "value control." It was a structured way of asking "why" and "how" at every step of the production process. Why does this part need to be made of steel? How else could we achieve the same strength? This was not a cost-cutting exercise in the sense of simply buying the cheapest option; it was a functional analysis to ensure that every dollar spent contributed directly to the product's purpose.
The success of this approach was so evident that it quickly moved beyond the private sector. In 1957, the U.S. Navy's Bureau of Ships, recognizing the potential for massive savings and improved performance in shipbuilding, established a formal program of value engineering. They placed Lawrence Miles and Raymond Fountain, another GE veteran, in charge of overseeing the initiative. This marked the transition of value engineering from an internal corporate curiosity to a national strategic asset.
The Double-Edged Sword of Planned Obsolescence
While the origins of value engineering were rooted in solving supply chain crises and improving efficiency, the philosophy soon evolved to address a different, more cynical market reality: planned obsolescence. The logic of value engineering is seductive. If a marketer expects a product to become stylistically or practically obsolete within three years, why design it to last ten?
From a purely economic standpoint, building a product to exceed its expected market life is an inefficiency. It imposes an unnecessary cost on the manufacturer, which is ultimately passed on to the purchaser. Value engineering dictates that the product should be built with the least expensive components that satisfy the projected lifetime of the item. If the product is designed to last only three years, the components should not be over-engineered to last a decade.
This approach, however, has a corrosive side effect. By aligning the product's physical lifespan exactly with its market lifespan, value engineering became the primary engine of planned obsolescence. Products began to deteriorate faster, not because of a lack of innovation, but because of a calculated decision to use components that were "just good enough" for the short term. This practice has led to a widespread association between value engineering and inferior quality.
The cultural critic Vance Packard, in his influential works, argued that this practice gave the entire engineering profession a bad name. He suggested that creative engineering energies were being diverted from solving long-term problems to serving short-term market ends. Instead of building things that endure, engineers were being asked to design things that fail. Philosophers like Herbert Marcuse and Jacque Fresco also criticized the economic and societal implications of this model. They saw it as a system that prioritized the turnover of goods over the well-being of the user and the sustainability of the environment.
The tension here is fundamental. Value engineering, in its purest form, seeks to eliminate waste. But who defines what is waste? Is it waste to build a toaster that lasts twenty years if the market only expects it to last five? The value engineering mindset says yes, that is waste. But the consumer, the community, and the environment might say no. The "value" in value engineering is defined by the ratio of function to cost, but if the "function" is artificially limited by a marketing timeline, the entire calculation is skewed.
The Mechanics of Function
To understand how value engineering operates on a day-to-day level, one must understand its unique language and logic. The process is based exclusively on "function." It ignores what something is and focuses entirely on what it does.
In a standard engineering review, a team might look at a part and see a "bracket." In a value engineering session, that bracket is described by its function, usually in a two-word abridgment consisting of an active verb and a measurable noun. For example, instead of "bracket," the function might be "support weight." This linguistic shift is not just semantics; it is a cognitive tool. By describing the function in the most non-descriptive way possible, the team removes the bias of the original design.
Consider the screwdriver again. If the team focuses on the object as a "screwdriver," they will think of other screwdrivers. If they focus on the function "blend liquid," they might realize that a spoon, a stick, or even a specialized mixing tool could perform the task more cheaply or effectively. The most basic function is "blend liquid," which is less limiting than "stir paint." "Stir paint" limits the action to stirring and the application to paint. "Blend liquid" opens the possibility of any liquid, any blending method.
This functional analysis is supported by a "how-why" questioning technique. Engineers ask "how" this function is achieved, then "why" it needs to be achieved that way. This rational logic is similar to the scientific method, focusing on hypothesis and conclusion to test relationships. It is also akin to operations research, using model building to identify predictive relationships. The goal is to identify the relationships that increase value.
However, this focus on function can be dangerous if the analysis is superficial. Critics argue that value engineering is sometimes taught as a technique where the value of a system's outputs is optimized by distorting the mix of performance and cost. It investigates systems, equipment, and services for providing necessary functions at a "superficially low life cycle cost" while meeting misunderstood requirement targets in performance, reliability, quality, and safety.
In many cases, this practice identifies and removes necessary functions of value expenditures, thereby decreasing the capabilities of the manufacturer and their customers. What is often disregarded in this pursuit of low cost are the expenditures related to equipment maintenance and the relationships between employees, equipment, and materials. For example, a machinist may be unable to complete their quota because a drill press is temporarily inoperable due to a lack of maintenance. The material handler may fail to do their daily checklist, tally, log, and invoice of maintenance and materials. These are not just "costs" to be trimmed; they are the essential functions that keep the system running. When value engineering cuts these, it may lower the initial cost but destroy the long-term value.
The Government Mandate
The influence of value engineering grew so significant that it eventually became a matter of federal law in the United States. Since the 1970s, the U.S. Government's General Accounting Office (GAO) has recognized the benefit of value engineering. In 1992, L. Nye Stevens, the Director of Government Business Operations Issues within the GAO, issued a statement referring to "considerable work" done by the GAO on the subject. He recommended that value engineering be adopted by "all federal construction agencies."
The mandate became even more concrete with the passage of the National Defense Authorization Act for Fiscal Year 1996. Section 4306 of this act specifically mandated value engineering for federal agencies, amending the Office of Federal Procurement Policy Act. This legislation was a response to the realization that the government, as the world's largest purchaser, was wasting billions of dollars on inefficient designs and over-engineered solutions.
Earlier, in 1990, a bill known as HR 281, the "Systematic Approach for Value Engineering Act," had been proposed. This bill sought to mandate the use of VE in major federally-sponsored construction, design, or IT system contracts. Its objective was clear: reduce all costs, including initial and long-term costs, and improve quality, performance, productivity, efficiency, promptness, reliability, maintainability, and aesthetics.
The Federal Acquisition Regulation (FAR), specifically Part 48, provides the direction for federal agencies on the use of VE techniques. The regulation offers two distinct approaches. The first is an incentive approach, where a contractor's participation is voluntary. Under this model, a contractor may, at its own expense, develop and submit a "value engineering change proposal" (VECP) for agency consideration. If the proposal is accepted, the contractor shares in the savings. The second approach is a mandatory program, where the agency directs and funds a specific VE project.
This legislative framework ensured that value engineering was not just a theoretical exercise but a required component of government contracting. It forced a systematic review of every major project, ensuring that the "function" of the project was prioritized over the "form" or the historical precedent.
The Grenfell Tower Inquiry and the Erosion of Trust
While the United States embraced value engineering as a tool for efficiency, the United Kingdom faced a stark reckoning with its consequences. The inquiry into the Grenfell Tower fire of 2017 highlighted the dangers of applying value engineering without a deep understanding of the trade-offs involved. The inquiry report was highly skeptical of the whole endeavor, questioning the very definition of "value" in a safety-critical context.
The report noted that in theory, "value engineering" involves making changes to the design or specification that reduce cost without sacrificing performance. However, the inquiry concluded that in practice, it was often "little more than a euphemism for reducing cost." The report stated:
substituting a cheaper product for a more expensive one or altering the design or scope of the work in a way that reduces cost almost invariably involves a compromise of some kind, whether in content, performance or appearance.
The Grenfell Tower tragedy involved the replacement of original cladding materials with cheaper, more flammable alternatives. This decision was driven by value engineering discussions aimed at reducing the cost of the refurbishment. The inquiry found that the "value" was calculated solely in terms of financial savings, while the "cost" of the compromised performance—specifically, the safety of the building's residents—was either ignored or underestimated.
This case serves as a grim warning of what happens when the "function" of a building (providing safe shelter) is subordinated to the "cost" of construction. It exposed a systemic failure where the rigorous functional analysis of value engineering was either bypassed or applied in a way that stripped away the essential safety margins. The lawfulness of undertaking value engineering discussions with a supplier in advance of contract award was one of the key issues highlighted, raising questions about the transparency and accountability of the process.
The Path Forward: Value-Driven Design
In the wake of these controversies, experts have begun to propose improvements to the traditional value engineering model. Dr. Paul Collopy, a professor at the University of Alabama in Huntsville in the ISEEM department, has recommended an improvement known as "Value-Driven Design." This approach seeks to address the shortcomings of the traditional model by integrating a more holistic view of value that includes reliability, safety, and long-term sustainability.
The traditional value engineering model, as practiced in many sectors, risks becoming a tool for "muntzing"—a term derived from the television industry for cutting corners to save money. It can lead to overengineering in some areas and underengineering in others, creating a system that is fragile and prone to failure. The challenge is to maintain the rigorous functional analysis of value engineering while ensuring that the "basic functions" are not reduced as a consequence of pursuing value improvements.
The Society of American Value Engineers (SAVE), established in 1959 and known as SAVE International since 1996, continues to promote the principles of value engineering. However, the organization also acknowledges the need for a more nuanced application of the method. The goal is to ensure that value engineering remains a tool for innovation and efficiency, rather than a mechanism for planned obsolescence or safety compromise.
As we look to the future, the lessons of value engineering are clear. It is a powerful methodology that can save billions of dollars and improve the performance of products and projects. But it requires a disciplined, ethical application. The definition of "value" must be broad enough to include the long-term well-being of the user, the environment, and society. The "function" must be understood not just as what the product does today, but what it must do tomorrow, next year, and for the next generation.
The story of value engineering is a story of human ingenuity, born from the necessity of war and refined by the demands of the market. It is a story of how we choose to allocate our resources, how we define quality, and how we balance the immediate needs of the economy with the enduring needs of the world. As we move forward, the challenge is to ensure that this tool serves humanity, rather than reducing us to mere consumers of disposable goods. The value of a product should not be measured only by its price tag, but by its ability to serve its purpose with integrity, reliability, and respect for the user.
In the end, value engineering is not just a technique; it is a philosophy. It asks us to look at the world and ask, "Does this need to be here? Does this need to cost this much? Is there a better way?" These are questions that have the power to transform industries, but they also carry the weight of responsibility. When answered correctly, they lead to a world of abundance and efficiency. When answered poorly, they lead to a world of waste and risk. The choice, ultimately, lies with the engineers, the managers, and the policymakers who wield this powerful tool.