Value engineering

Value engineering (VE) is a systematic method to improve the "value" of goods or products and services by using an examination of function. Value, as defined, is the ratio of function to cost. Value can therefore be manipulated by either improving the function or reducing the cost. It is a primary tenet of value engineering that basic functions be preserved and not be reduced as a consequence of pursuing value improvements.[1] The term "value management" is sometimes used as a synonym of "value engineering", and both promote the planning and delivery of projects with improved performance [2]

The reasoning behind value engineering is as follows: if marketers expect a product to become practically or stylistically obsolete within a specific length of time, they can design it to only last for that specific lifetime. The products could be built with higher-grade components, but with value engineering they are not because this would impose an unnecessary cost on the manufacturer, and to a limited extent also an increased cost on the purchaser. Value engineering will reduce these costs. A company will typically use the least expensive components that satisfy the product's lifetime projections.

Due to the very short life spans, however, which is often a result of this "value engineering technique", planned obsolescence has become associated with product deterioration and inferior quality. Vance Packard once claimed this practice gave engineering as a whole a bad name, as it directed creative engineering energies toward short-term market ends. Philosophers such as Herbert Marcuse and Jacque Fresco have also criticized the economic and societal implications of this model. Value engineering is the structural and analytical process that seeks to achieve the value for money.

History

Value engineering began at General Electric Co. during World War II. Because of the war, there were shortages of skilled labour, raw materials, and component parts. Lawrence Miles, Jerry Leftow, and Harry Erlicher at G.E. looked for acceptable substitutes. They noticed that these substitutions often reduced costs, improved the product, or both. What started out as an accident of necessity was turned into a systematic process. They called their technique "value analysis".

Description

Value engineering is sometimes taught within the project management, industrial engineering or architecture body of knowledge as a technique in which the value of a system’s outputs is optimized by crafting a mix of performance (function) and costs. It is based on an analysis investigating systems, equipment, facilities, services, and supplies for providing necessary functions at the lowest life cycle cost while meeting the required targets in performance, reliability, quality, and safety.[3] In most cases this practice identifies and removes unnecessary expenditures, thereby increasing the value for the manufacturer and/or their customers.

VE follows a structured thought process that is based exclusively on "function", i.e. what something "does" not what it is. For example a screw driver that is being used to stir a can of paint has a "function" of mixing the contents of a paint can and not the original connotation of securing a screw into a screw-hole. In value engineering "functions" are always described in a two word abridgment consisting of an active verb and measurable noun (what is being done – the verb – and what it is being done to – the noun) and to do so in the most non-prescriptive way possible. In the screw driver and can of paint example, the most basic function would be "blend liquid" which is less prescriptive than "stir paint" which can be seen to limit the action (by stirring) and to limit the application (only considers paint). This is the basis of what value engineering refers to as "function analysis".[4]

Value engineering uses rational logic (a unique "how" - "why" questioning technique) and the analysis of function to identify relationships that increase value. It is considered a quantitative method similar to the scientific method, which focuses on hypothesis-conclusion approaches to test relationships, and operations research, which uses model building to identify predictive relationships.

In the United States, value engineering is specifically mandated for federal agencies by section 4306 of the National Defense Authorization Act for Fiscal Year 1996,[5] which amended the Office of Federal Procurement Policy Act (41 U.S.C. 401 et seq.):

“Each executive agency shall establish and maintain cost-effective value engineering procedures and processes".
"As used in this section, the term ‘value engineering’ means an analysis of the functions of a program, project, system, product, item of equipment, building, facility, service, or supply of an executive agency, performed by qualified agency or contractor personnel, directed at improving performance, reliability, quality, safety, and life cycle costs".
gollark: It can only occur in unsafe blocks. You could add those (or some pragma or something) to your borrow checker, although based on my limited C observation, hard to check constructs are much more common in it.
gollark: C also has weaker types and requires you to pass (pointer, size) to lots of things, which is also hard to check although *maybe* doable.
gollark: You could detect it, you couldn't verify correctness.
gollark: I guess you could just have `unsafe`/`average_c` blocks for that.
gollark: Pointer arithmetic, for one thing?

See also

References
  1. "Value Methodology Standard" (PDF). Archived from the original (PDF) on 2009-03-19. Retrieved 2008-12-01.
  2. Invernizzi, Diletta Colette; Locatelli, Giorgio; Grönqvist, Marcus; Brookes, Naomi J. (2019-01-28). "Applying value management when it seems that there is no value to be managed: the case of nuclear decommissioning". International Journal of Project Management. 37 (5): 668–683. doi:10.1016/j.ijproman.2019.01.004. ISSN 0263-7863.
  3. Demkin, Joseph A. (2008). The architect's handbook of professional practice (14th ed.). Hoboken: Wiley. ISBN 9780470009574. OCLC 181368866.
  4. The Value Methodology Standard. SAVE International. August 2007.
  5. National Defense Authorization Act for Fiscal Year 1996, Public Law 104-106, accessed 4 March 2016

Further reading
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.