Editing Theory of constraints (section)

== History ==
The theory of constraints is an overall [[management philosophy]], introduced by [[Eliyahu M. Goldratt]] in his 1984 book titled ''[[The Goal (novel)|The Goal]]'', that is geared to help organizations continually achieve their goals.<ref name=goal>{{cite book |author1=Cox, Jeff |author2=Goldratt, Eliyahu M. |title=The goal: a process of ongoing improvement |url=https://archive.org/details/goalprocessofo00gold |url-access=registration |publisher=North River Press |location=[Croton-on-Hudson, New York] |year=1986 |isbn=0-88427-061-0 }}</ref> Goldratt adapted the concept to project management with his book ''Critical Chain'', published in 1997.

An earlier propagator of a similar concept was [[Wolfgang Mewes]]<ref>{{cite web|url=http://www.wolfgangmewes.de/wm.htm|title=Beratergruppe Strategie|website=www.wolfgangmewes.de|access-date=17 March 2018}}</ref> in Germany with publications on ''power-oriented management theory'' (Machtorientierte Führungstheorie, 1963) and following with his ''Energo-Kybernetic System (EKS, 1971)'', later renamed ''[[:de:Engpasskonzentrierte Strategie|Engpasskonzentrierte Strategie]]'' (Bottleneck-focused Strategy) as a more advanced ''theory of bottlenecks''. The publications of Wolfgang Mewes are marketed through the FAZ Verlag, publishing house of the German newspaper ''[[Frankfurter Allgemeine Zeitung]]''. However, the paradigm ''Theory of constraints'' was first used by Goldratt.

===Key assumption===
The underlying premise of the theory of constraints is that organizations can be measured and controlled by variations on three measures: [[Throughput (business)|throughput]], [[operational expense]], and [[inventory]]. Inventory is all the money that the system has invested in purchasing things which it intends to sell. Operational expense is all the money the system spends in order to turn inventory into throughput. Throughput is the rate at which the system generates money through sales.<ref name=essays>{{cite book |author=Goldratt, Eliyahu M. |title=Essays on the ''Theory of Constraints'' |year=1998 |publisher=North River Press |location=[Great Barrington, Massachusetts] |isbn=0-88427-159-5 }}</ref>

Before the goal itself can be reached, necessary conditions must first be met. These typically include safety, quality, legal obligations, etc.  For most businesses, the goal itself is to make [[Profit (economics)|profit]].  However, for many organizations and non-profit businesses, making money is a necessary condition for pursuing the goal.  Whether it is the goal or a necessary condition, understanding how to make sound financial decisions based on throughput, inventory, and operating expense is a critical requirement.<ref name=essays />

===The five focusing steps===
TOC is based on the premise that the rate of [[goal]] achievement by a [[goal-oriented]] system (i.e., the system's [[Throughput (business)|throughput]]) is limited by at least one [[Theory of constraints#Constraints|constraint]].

The argument by [[reductio ad absurdum]] is as follows: If there was nothing preventing a system from achieving higher throughput (i.e., more goal units in a unit of time), its throughput would be infinite – which is impossible in a real-life system.

Only by increasing flow through the constraint can overall throughput be increased.<ref name=goal/>

Assuming the goal of a system has been articulated and its measurements defined, the steps are:

# ''Identify'' the system's constraint(s).
# Decide how to ''exploit'' the system's constraint(s).
# ''Subordinate'' everything else to the above decision.
# ''Elevate'' the system's constraint(s).
# ''Warning!'' If in the previous steps a [[Theory of constraints#Breaking a constraint|constraint has been broken]], go back to step 1, but do not allow [[inertia]] to cause a system's constraint.<ref name=goldratt2004>Eliyahu M. Goldratt. 2004. _The Goal: A Process of Ongoing Improvement, {{ISBN|978-0-88427-178-9}}.</ref>

The goal of a commercial organization is: "Make more money now and in the future",<ref>Theory of Constraints Handbook, {{ISBN|978-0-07-166554-4}}, p. 8</ref> and its measurements are given by [[throughput accounting]] as: throughput, [[inventory]], and [[operating expenses]].

The five focusing steps aim to ensure ongoing improvement efforts are centered on the organization's constraint(s).  In the TOC literature, this is referred to as the ''[[Continual improvement process|process of ongoing improvement]]'' (POOGI).

These focusing steps are the key steps to developing the specific [[#Applications|applications]] mentioned below.

===Constraints===
A constraint is anything that prevents the system from achieving its goal. There are many ways that constraints can show up, but a core principle within TOC is that there are not tens or hundreds of constraints. There is at least one, but at most only a few in any given system. Constraints can be internal or external to the system. An internal constraint is in evidence when the market demands more from the system than it can deliver. If this is the case, then the focus of the organization should be on discovering that constraint and following the five focusing steps to open it up (and potentially remove it). An external constraint exists when the system can produce more than the market will bear. If this is the case, then the organization should focus on mechanisms to create more demand for its products or services.

Types of (internal) constraints
* Equipment: The way equipment is currently used limits the ability of the system to produce more salable goods/services.
* People: Lack of [[skill]]ed people limits the system. [[Mental model]]s held by people can cause behaviour that becomes a constraint.
* Policy: A written or unwritten policy prevents the system from making more.

The concept of the constraint in Theory of Constraints is analogous to but differs from the [[Constraint (mathematics)|constraint]] that shows up in mathematical [[optimization (mathematics)|optimization]]. In TOC, the constraint is used as a focusing mechanism for management of the system.  In optimization, the constraint is written into the mathematical expressions to limit the scope of the solution (X can be no greater than 5).

Please note: organizations have many problems with equipment, people, policies, etc. (A breakdown is just that – a breakdown – and is not a constraint in the true sense of the TOC concept). The constraint is the [[limiting factor]] that is preventing the organization from getting more throughput (typically, revenue through sales) even when nothing goes wrong.

===Breaking a constraint===
If a constraint's throughput capacity is elevated to the point where it is no longer the system's limiting factor, this is said to "break" the constraint. The limiting factor is now some other part of the system, or may be external to the system (an external constraint). This is not to be confused with a breakdown.

===Buffers===
Buffers are used throughout the theory of constraints. They often result as part of the exploit and subordinate steps of the five focusing steps. Buffers are placed before the governing constraint, thus ensuring that the constraint is never starved. Buffers are also placed behind the constraint to prevent downstream failure from blocking the constraint's output. Buffers used in this way protect the constraint from variations in the rest of the system and should allow for normal variation of processing time and the occasional upset ([[Murphy's Law|Murphy]]) before and behind the constraint.

Buffers can be a bank of physical objects before a work center, waiting to be processed by that work center. Buffers ultimately buy you time, as in the time before work reaches the constraint and are often verbalized as time buffers. There should always be enough (but not excessive) work in the time queue before the constraint and adequate offloading space behind the constraint.

Buffers are ''not'' the small queue of work that sits before every work center in a [[kanban]] system although it is similar if you regard the assembly line as the governing constraint. A prerequisite in the theory is that with one constraint in the system, all other parts of the system must have sufficient capacity to keep up with the work at the constraint and to catch up if time was lost. In a balanced line, as espoused by kanban, when one work center goes down for a period longer than the buffer allows, then the entire system must wait until that work center is restored. In a TOC system, the only situation where work is in danger is if the constraint is unable to process (either due to malfunction, sickness or a "hole" in the buffer – if something goes wrong that the time buffer can not protect).

Buffer management, therefore, represents a crucial attribute of the theory of constraints. There are many ways to apply buffers, but the most often used is a visual system of designating the buffer in three colors: green (okay), yellow (caution) and red (action required). Creating this kind of visibility enables the system as a whole to align and thus subordinate to the need of the constraint in a holistic manner. This can also be done daily in a central operations room that is accessible to everybody.

===Plant types===
There are four primary types of plants in the TOC lexicon. Draw the flow of material from the bottom of a page to the top, and you get the four types. They specify the general flow of materials through a system, and also provide some hints about where to look for typical problems. This type of analysis is known as VATI analysis<ref>{{Cite book|title=APICS Dictionary, 13th Edition|last=Blackstone Jr., editor|first=John H.|publisher=APICS self-published|year=2013|isbn=978-0-9882146-1-3|location=Chicago|pages=186}}</ref> as it uses the bottom-up shapes of the letters V, A, T, and I to describe the types of plants. The four types can be combined in many ways in larger facilities, e.g. "an A plant feeding a V plant".
* V-plant: The general flow of material is one-to-many, such as a plant that takes one raw material and can make many final products.  Classic examples are meat rendering plants or a steel manufacturer. The primary problem in V-plants is "robbing," where one operation (A) immediately after a diverging point "steals" materials meant for the other operation (B). Once the material has been processed by A, it cannot come back and be run through B without significant rework.
* A-plant: The general flow of material is many-to-one, such as in a plant where many sub-assemblies converge for a final assembly. The primary problem in A-plants is in synchronizing the converging lines so that each supplies the final assembly point at the right time.
* T-plant: The general flow is that of an I-plant (or has multiple lines), which then splits into many assemblies (many-to-many). Most manufactured parts are used in multiple assemblies and nearly all assemblies use multiple parts. Customized devices, such as computers, are good examples. T-plants suffer from both synchronization problems of A-plants (parts aren't all available for an assembly) and the robbing problems of V-plants (one assembly steals parts that could have been used in another).
* I-plant: Material flows in a sequence, such as in an assembly line. The primary work is done in a straight sequence of events (one-to-one). The constraint is the slowest operation.

From the above list, one can deduce that for non-material systems one could draw the flow of work or the flow of processes, instead of physical flows, and arrive at similar basic V, A, T, or I structures. A project, for example, is an A-shaped sequence of work, culminating in a delivered product (''i.e., the intended outcome of the project'').