Theory of Constraints

https://en.wikipedia.org/wiki/Theory_of_constraints

The theory of constraints (TOC) is a management paradigm that views any manageable system as being limited in achieving more of its goals by a very small number of constraints. There is always at least one constraint, and TOC uses a focusing process to identify the constraint and restructure the rest of the organization around it. TOC adopts the common idiom "a chain is no stronger than its weakest link". That means that organizations and processes are vulnerable because the weakest person or part can always damage or break them, or at least adversely affect the outcome.

The theory of constraints is an overall management philosophy, introduced by Eliyahu M. Goldratt in his 1984 book titled The Goal, that is geared to help organizations continually achieve their goals.^[1] 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^[2] in Germany with publications on power-oriented management theory (Machtorientierte Führungstheorie, 1963) and following with his Energo-Kybernetic System (EKS, 1971), later renamed 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.

The underlying premise of the theory of constraints is that organizations can be measured and controlled by variations on three measures: 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.^[3]

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. 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.^[3]

The five focusing steps

[edit]

TOC is based on the premise that the rate of goal achievement by a goal-oriented system (i.e., the system's throughput) is limited by at least one 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.^[1]

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 constraint has been broken, go back to step 1, but do not allow inertia to cause a system's constraint.^[4]

The goal of a commercial organization is: "Make more money now and in the future",^[5] 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 process of ongoing improvement (POOGI).

These focusing steps are the key steps to developing the specific applications mentioned below.

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 skilled people limits the system. Mental models 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 that shows up in mathematical 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

[edit]

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 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) 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.

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^[6] 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).

The focusing steps, this process of ongoing improvement, have been applied to manufacturing, project management, supply chain/distribution generated specific solutions. Other tools (mainly the "thinking process") also led to TOC applications in the fields of marketing and sales, and finance. The solution as applied to each of these areas are listed below.

Within manufacturing operations and operations management, the solution seeks to pull materials through the system, rather than push them into the system. The primary methodology used is drum-buffer-rope (DBR)^[7] and a variation called simplified drum-buffer-rope (S-DBR).^[8]

Drum-buffer-rope is a manufacturing execution methodology based on the fact the output of a system can only be the same as the output at the constraint of the system. Any attempt to produce more than what the constraint can process just leads to excess inventory piling up.^[9] The method is named for its three components. The drum is the rate at which the physical constraint of the plant can work: the work center or machine or operation that limits the ability of the entire system to produce more. The rest of the plant follows the beat of the drum. Schedule at the drum decides what the system should produce, in what sequence to produce and how much to produce.^[10] They make sure the drum has work and that anything the drum has processed does not get wasted.

The buffer protects the drum, so that it always has work flowing to it. Buffers in DBR provide the additional lead time beyond the required set up and process times, for materials in the product flow. Since these buffers have time as their unit of measure, rather than quantity of material, this makes the priority system operate strictly based on the time an order is expected to be at the drum. Each work order will have a remaining buffer status that can be calculated. Based on this buffer status, work orders can be color coded into Red, Yellow and Green. The red orders have the highest priority and must be worked on first, since they have penetrated most into their buffers followed by yellow and green. As time evolves, this buffer status might change and the color assigned to the particular work order change with it.^[11]^[12]

Traditional DBR usually calls for buffers at several points in the system: the constraint, synchronization points and at shipping. S-DBR has a buffer at shipping and manages the flow of work across the drum through a load planning mechanism.^[13]

The rope is the work release mechanism for the plant. Orders are released to the shop floor at one "buffer time" before they are due to be processed by the constraint. In other words, if the buffer is 5 days, the order is released 5 days before it is due at the constraint. Putting work into the system earlier than this buffer time is likely to generate too-high work-in-process and slow down the entire system.^[14]

High-speed automated production lines

[edit]

Automated production lines achieve high throughput rates and output quantities by deploying automation solutions that are highly task-specific. Depending on their design and construction, these machines operate at different speeds and capacities and therefore have varying efficiency levels.

A prominent example is the use of automated production lines in the beverage industry. Filling systems usually have several machines executing parts of the complete bottling process, from filling primary containers to secondary packaging and palletisation.^[15]

To be able to maximize the throughput, the production line usually has a designed constraint. This constraint is typically the slowest and often the most expensive machine on the line. The overall throughput of the line is determined by this machine. All other machines can operate faster and are connected by conveyors.

The conveyors usually have the ability to buffer product. In the event of a stoppage at a machine other than the constraint, the conveyor can buffer the product enabling the constraint machine to keep on running.

A typical line setup is such that in normal operation the upstream conveyors from the constraint machine are always run full to prevent starvation at the constraint and the downstream conveyors are run empty to prevent a back up at the constraint. The overall aim is to prevent minor stoppages at the machines from impacting the constraint.

For this reason as the machines get further from the constraint, they have the ability to run faster than the previous machine and this creates a V curve.^{[citation needed]}

Supply chain and logistics

[edit]

In general, the solution for supply chains is to create flow of inventory so as to ensure greater availability and to eliminate surpluses.

The TOC distribution solution is effective when used to address a single link in the supply chain and more so across the entire system, even if that system comprises many different companies. The purpose of the TOC distribution solution is to establish a competitive advantage based on extraordinary availability by reducing the damages caused when the flow of goods is interrupted by shortages and surpluses.

This approach uses several new rules to protect availability with less inventory than is conventionally required.

Inventory is held at an aggregation point(s) as close as possible to the source. This approach ensures smoothed demand at the aggregation point, requiring proportionally less inventory. The distribution centers holding the aggregated stock are able to ship goods downstream to the next link in the supply chain much more quickly than a make-to-order manufacturer can.
Following this rule may result in a make-to-order manufacturer converting to make-to-stock. The inventory added at the aggregation point is significantly less than the inventory reduction downstream.
In all stocking locations, initial inventory buffers are set which effectively create an upper limit of the inventory at that location. The buffer size is equal to the maximum expected consumption within the average Replenishment Time ("RT"), plus additional stock to protect in case a delivery is late. In other words, there is no advantage in holding more inventory in a location than the amount that might be consumed before more could be ordered and received. Typically, the sum of the on hand value of such buffers are 25–75% less than currently observed average inventory levels
1. Replenishment Time (RT) is the sum of the delay, after the first consumption following a delivery, before an order is placed plus the delay after the order is placed until the ordered goods arrive at the ordering location.
Once buffers have been established, no replenishment orders are placed as long as the quantity inbound (already ordered but not yet received) plus the quantity on hand are equal to or greater than the buffer size. Following this rule causes surplus inventory to be bled off as it is consumed.
For any reason, when on hand plus inbound inventory is less than the buffer, orders are placed as soon as practical to increase the inbound inventory so that the relationship on Hand + Inbound = Buffer is maintained.
To ensure buffers remain correctly sized even with changes in the rates of demand and replenishment, a simple recursive algorithm called Buffer Management is used. When the on hand inventory level is in the upper third of the buffer for a full RT, the buffer is reduced by one third (and don't forget rule 3). Alternatively, when the on hand inventory is in the bottom one third of the buffer for too long, the buffer is increased by one third (and don't forget rule 4). The definition of "too long" may be changed depending on required service levels, however, a rule of thumb is 20% of the RT. Moving buffers up more readily than down is supported by the usually greater damage caused by shortages as compared to the damage caused by surpluses.

Once inventory is managed as described above, continuous efforts should be undertaken to reduce RT, late deliveries, supplier minimum order quantities (both per SKU and per order) and customer order batching. Any improvements in these areas will automatically improve both availability and inventory turns, thanks to the adaptive nature of Buffer Management.

A stocking location that manages inventory according to the TOC should help a non-TOC customer (downstream link in a supply chain, whether internal or external) manage their inventory according to the TOC process. This type of help can take the form of a vendor managed inventory (VMI). The TOC distribution link simply extends its buffer sizing and management techniques to its customers' inventories. Doing so has the effect of smoothing the demand from the customer and reducing order sizes per SKU. VMI results in better availability and inventory turns for both supplier and customer. The benefits to the non-TOC customers are sufficient to meet the purpose of capitalizing on the competitive edge by giving the customer a reason to be more loyal and give more business to the upstream link. When the end consumers buy more, the whole supply chain sells more.

One caveat should be considered. Initially and only temporarily, the supply chain or a specific link may sell less as the surplus inventory in the system is sold. However, the sales lift due to improved availability is a countervailing factor. The current levels of surpluses and shortages make each case different.

Finance and accounting

[edit]

Holistic thinking applied to the finance application has been termed throughput accounting.^[16] Throughput accounting suggests that one examine the impact of investments and operational changes in terms of the impact on the throughput of the business. It is an alternative to cost accounting.

The primary measures for a TOC view of finance and accounting are: throughput, operating expense and investment. Throughput is calculated from sales minus "totally variable cost", where totally variable cost is usually calculated as the cost of raw materials that go into creating the item sold.^[17]^: 13–14

Critical Chain Project Management (CCPM) are utilized in this area.^[18] CCPM is based on the idea that all projects look like A-plants: all activities converge to a final deliverable. As such, to protect the project, there must be internal buffers to protect synchronization points and a final project buffer to protect the overall project.

Marketing and sales

[edit]

While originally focused on manufacturing and logistics, TOC has expanded into sales management and marketing. Its role is explicitly acknowledged in the field of sales process engineering.^[19] For effective sales management one can apply Drum Buffer Rope to the sales process similar to the way it is applied to operations (see Reengineering the Sales Process book reference below). This technique is appropriate when your constraint is in the sales process itself, or if you just want an effective sales management technique which includes the topics of funnel management and conversion rates.^{[citation needed]}

The thinking processes are a set of tools to help managers walk through the steps of initiating and implementing a project. When used in a logical flow, they help walk through a buy-in process:

Gain agreement on the problem
Gain agreement on the direction for a solution
Gain agreement that the solution solves the problem
Agree to overcome any potential negative ramifications
Agree to overcome any obstacles to implementation

TOC practitioners sometimes refer to these in the negative as working through layers of resistance to a change.

Recently, the current reality tree (CRT) and future reality tree (FRT) have been applied to an argumentative academic paper.^[20]

Despite its origins as a manufacturing approach (Goldratt & Cox, The Goal: A process of Ongoing Improvement, 1992), Goldratt's Theory of Constraints (TOC) methodology is now regarded as a systems methodology with strong foundations in the hard sciences (Mabin, 1999). Through its tools for convergent thinking and synthesis, the "Thinking processes", which underpin the entire TOC methodology, help identify and manage constraints and guide continuous improvement and change in organizations (Dettmer H., 1998).

The process of change requires the identification and acceptance of core issues; the goal and the means to the goal. This comprehensive set of logical tools can be used for exploration, solution development and solution implementation for individuals, groups or organizations. Each tool has a purpose and nearly all tools can be used independently (Cox & Spencer, 1998). Since these thinking tools are designed to address successive "layers of resistance" and enable communication, it expedites securing "buy in" of groups. While CRT (current reality tree) represents the undesirable effects of the current situation, the FRT (the future reality tree), NBR (negative branch) help people plan and understand the possible results of their actions. The PRT (prerequisite tree) and TRT (transition tree) are designed to build collective buy in and aid in the Implementation phase. The logical constructs of these tools or diagrams are the necessary condition logic, the sufficient cause logic and the strict logic rules that are used to validate cause-effect relationships which are modelled with these tools (Dettmer W., 2006).

A summary of these tools, the questions they help answer and the associated logical constructs used is presented in the table below.

	Sufficient thinking "If……. then"	Necessary Thinking "In order to…we must"
What to change?	Current reality tree
What to change to?	Future Reality Tree Negative Branch Reservations	Evaporating cloud
How to change?	Transition Tree	Prerequisite Tree

TOC Thinking Process Tools: Use of these tools are based on the fundamental beliefs of TOC that organizations a) are inherently simple (interdependencies exist in organizations) b) desire inherent harmony (win – win solutions are possible) c) are inherently good (people are good) and have inherent potential (people and organizations have potential to do better) (Goldratt E., 2009). In the book "Through the clouds to solutions" Jelena Fedurko (Fedurko, 2013) states that the major areas for application of TP tools as:

To create and enhance thinking and learning skills
To make better decisions
To develop responsibility for one's own actions through understanding their consequences
To handle conflicts with more confidence and win-win outcomes
To correct behavior with undesirable consequences
Assist in evaluating conditions for achieving a desired outcome
To assist in peer mediation
To assist in relationship between subordinates and bosses^{[citation needed]}

Development and practice

[edit]

TOC was initiated by Goldratt, who until his death was still the main driving force behind the development and practice of TOC. There is a network of individuals and small companies loosely coupled as practitioners around the world. TOC is sometimes referred to as "constraint management". TOC is a large body of knowledge with a strong guiding philosophy of growth.

Criticisms that have been leveled against TOC include:

Claimed suboptimality of drum-buffer-rope

[edit]

While TOC has been compared favorably to linear programming techniques,^[21] D. Trietsch from University of Auckland argues that DBR methodology is inferior to competing methodologies.^[22]^[23] Linhares, from the Getulio Vargas Foundation, has shown that the TOC approach to establishing an optimal product mix is unlikely to yield optimum results, as it would imply that P=NP.^[24]

Unacknowledged debt

[edit]

Duncan (as cited by Steyn)^[25] says that TOC borrows heavily from systems dynamics developed by Forrester in the 1950s and from statistical process control which dates back to World War II. And Noreen Smith and Mackey, in their independent report on TOC, point out that several key concepts in TOC "have been topics in management accounting textbooks for decades."^[17]^: 149 It is also claimed^{[citation needed]} that Goldratt's books fail to acknowledge that TOC borrows from more than 40 years of previous management science research and practice, particularly from program evaluation and review technique/critical path method (PERT/CPM) and the just in time strategy.

A rebuttal to these criticisms is offered in Goldratt's "What is the Theory of Constraints and How Should it be Implemented?", and in his audio program, "Beyond The Goal". In these, Goldratt discusses the history of disciplinary sciences, compares the strengths and weaknesses of the various disciplines, and acknowledges the sources of information and inspiration for the thinking processes and critical chain methodologies. Articles published in the now-defunct Journal of Theory of Constraints referenced foundational materials. Goldratt published an article^[26] and gave talks^[27] with the title "Standing on the Shoulders of Giants" in which he gives credit for many of the core ideas of Theory of Constraints. Goldratt has sought many times to show the correlation between various improvement methods.

Goldratt has been criticized on lack of openness in his theories, an example being him not releasing the algorithm he used for the Optimum Performance Training system.^[28] Some view him as unscientific with many of his theories, tools and techniques not being a part of the public domain, rather a part of his own framework of profiting on his ideas. According to Gupta and Snyder (2009), despite being recognized as a genuine management philosophy nowadays, TOC has yet failed to demonstrate its effectiveness in the academic literature and as such, cannot be considered academically worthy to be called a widely recognized theory. TOC needs more case studies that prove a connection between implementation and improved financial performance.^[29] Nave (2002) argues that TOC does not take employees into account and fails to empower them in the production process. He also states that TOC fails to address unsuccessful policies as constraints.^[30] In contrast, Mukherjee and Chatterjee (2007) state that much of the criticism of Goldratt's work has been focused on the lack of rigour in his work, but not of the bottleneck approach, which are two different aspects of the issue.^[31]

Certification and education

[edit]

The Theory of Constraints International Certification Organization (TOCICO) is an independent not-for-profit incorporated society that sets exams to ensure a consistent standard of competence. It is overseen by a board^[32]^{[non-primary source needed]} of academic and industrial experts. It also hosts an annual international conference. The work presented at these conferences constitutes a core repository of the current knowledge.

^ ^a ^b Cox, Jeff; Goldratt, Eliyahu M. (1986). The goal: a process of ongoing improvement. [Croton-on-Hudson, New York]: North River Press. ISBN 0-88427-061-0.
^ "Beratergruppe Strategie". www.wolfgangmewes.de. Retrieved 17 March 2018.
^ ^a ^b Goldratt, Eliyahu M. (1998). Essays on the Theory of Constraints. [Great Barrington, Massachusetts]: North River Press. ISBN 0-88427-159-5.
^ Eliyahu M. Goldratt. 2004. _The Goal: A Process of Ongoing Improvement, ISBN 978-0-88427-178-9.
^ Theory of Constraints Handbook, ISBN 978-0-07-166554-4, p. 8
^ Blackstone Jr., editor, John H. (2013). APICS Dictionary, 13th Edition. Chicago: APICS self-published. p. 186. ISBN 978-0-9882146-1-3.
^ Goldratt, Eliyahu; Fox, Robert (1986). The Race. [Croton-on-Hudson, New York]: North River Press. pp. 179. ISBN 978-0-88427-062-1.
^ Eli Schragenheim & H. William Dettmer (2000). "Simplified Drum-Buffer-Rope: A Whole System Approach to High Velocity Manufacturing" (PDF). Retrieved 8 December 2007.
^ Goldratt, Eliyahu M. (1986). The Race. Croton-on Hudson, New York: North River Press. pp. 77–97. ISBN 9780884270621.
^ Goldratt, Eliyahu (1990). The Haystack Syndrome:: Sifting Information out of the Data Ocean. New York: New York: North River Press. ISBN 9780884270898.
^ Shri Shrikanth, M (2010). DBR, Buffer Management, and VATI flow classification.
^ J. F. Cox III & J. J. Schleier. Theory of Constraints Handbook. New York: McGraw Hill. pp. 175–210.
^ Schragenheim, e; Dettmer, H. W; Patterson, J. W. (2009). Supply Chain Management at Warp Speed. Boca Raton: Auerbach publications.
^ Russell, G. R.; Fry, T. D (1997). Order review/release and lot splitting in drum-buffer-rope. pp. 35:827–845.
^ 'The planning flexibility bottleneck in food processing industries' (2006) Journal of Operations Management 24(3):287-300, DOI:10.1016/j.jom.2004.11.001
^ Corbett, Thomas (1998). Throughput Accounting. North River Press. p. 160. ISBN 978-0-88427-158-1.
^ ^a ^b Eric Noreen; Debra Smith; James T. Mackey (1995). The Theory of Constraints and its implications for Management Accounting. North River Press. ISBN 0-88427-116-1.
^ Goldratt, Eliyahu M. (1997). Critical Chain. Great Barrington, Massachusetts: North River Press. ISBN 0-88427-153-6.
^ Paul H. Selden (1997). Sales Process Engineering: A Personal Workshop. Milwaukee, Wisconsin: ASQ Quality Press. pp. 33–35, 264–268. ISBN 0-87389-418-9.
^ See the annex of: Vidal, C. 2008.The Future of Scientific Simulations: from Artificial Life to Artificial Cosmogenesis. In Death And Anti-Death, ed. Charles Tandy, 6: Thirty Years After Kurt Gödel (1906–1978) pp. 285-318. Ria University Press.)
^ Qui, Mabel; Fredendall, Lawrence; Zhu, Zhiwei (2002). "TOC or LP? [production control]". Manufacturing Engineer. 81 (4): 190–195. doi:10.1049/me:20020411 (inactive 7 December 2024).{{cite journal}}: CS1 maint: DOI inactive as of December 2024 (link)
^ Trietsch, D. (2005). "From Management by Constraints (MBC) to Management By Criticalities (MBC II)" (PDF). Human Systems Management. 24: 105–115. doi:10.3233/HSM-2005-24109.
^ http://ac.aua.am/trietsch/web/WorkingPaper281.pdf D. Trietsch, From the Flawed "Theory of Constraints" to Hierarchically Balancing Criticalities (HBC), Department of Information Systems and Operations Management, University of Auckland, Working Paper No. 281, May 2004.
^ Linhares, Alexandre (2009). "Theory of constraints and the combinatorial complexity of the product-mix decision". International Journal of Production Economics. 121 (1): 121–129. doi:10.1016/j.ijpe.2009.04.023.
^ Steyn, Herman (2000). "An Investigation into the Fundamentals of Critical Chain Project Scheduling". International Journal of Project Management (19): 363–369.
^ Goldratt, Eliyahu M. (2009). "Standing on the shoulders of giants: production concepts versus production applications. The Hitachi Tool Engineering example". Gestão & Produção. 16 (3): 333–343. doi:10.1590/S0104-530X2009000300002.
^ Archived at Ghostarchive and the Wayback Machine: Eliyahu Goldratt. Standing on the Shoulders of Giants.
^ Rahman, Shams-ur. "Theory of constraints: a review of the philosophy and its applications." International Journal of Operations & Production Management 18.4 (1998): 336-355.
^ Gupta, Mahesh, and Doug Snyder. "Comparing TOC with MRP and JIT: a literature review." International Journal of Production Research 47.13 (2009): 3705-3739
^ Nave, Dave. "How to compare six sigma, lean and the theory of constraints." Quality Progress 35.3 (2002): 73-80.
^ Mukherjee, S. M. and Chatterjee, A. K. (2007). The concept of bottleneck. Working Paper No. 2006-05-01, IIM Ahmedabad
^ "TOCICO Board of Directors - Theory of Constraints International Certification Organization". www.tocico.org. Retrieved 17 March 2018.

Cox, Jeff; Goldratt, Eliyahu M. (1986). The goal: a process of ongoing improvement. [Great Barrington, Massachusetts]: North River Press. ISBN 0-88427-061-0.
Dettmer, H. William. (2003). Strategic Navigation: A Systems Approach to Business Strategy. [Milwaukee, Wisconsin]: ASQ Quality Press. p. 302. ISBN 0-87389-603-3.
Dettmer, H. William. (2007). The Logical Thinking Process: A Systems Approach to Complex Problem Solving. [Milwaukee, Wisconsin]: ASQ Quality Press. p. 413. ISBN 978-0-87389-723-5.
Goldratt, Eliyahu M. (1994). It's not luck. [Great Barrington, Massachusetts]: North River Press. ISBN 0-88427-115-3.
Goldratt, Eliyahu M. (1997). Critical chain. [Great Barrington, Massachusetts]: North River Press. ISBN 0-88427-153-6.
Carol A. Ptak; Goldratt, Eliyahu M.; Eli Schragenheim (2000). Necessary But Not Sufficient. [Great Barrington, Massachusetts]: North River Press. ISBN 0-88427-170-6.
Goldratt, Eliyahu M. (1998). Essays on the Theory of Constraints. [Great Barrington, Massachusetts]: North River Press. ISBN 0-88427-159-5.
Goldratt, Eliyahu M. (1990). Theory of Constraints. [Great Barrington, Massachusetts]: North River Press. ISBN 0-88427-166-8.
Goldratt, Eliyahu M. Beyond the Goal : Eliyahu Goldratt Speaks on the Theory of Constraints (Your Coach in a Box). Coach Series. ISBN 1-59659-023-8.
Lisa Lang (January 2006). Achieving a Viable Vision: The Theory of Constraints Strategic Approach to Rapid Sustainable Growth. Throughput Publishing, Inc. ISBN 0-9777604-1-3.
Goldratt, Eliyahu M. (1990). The haystack syndrome: sifting information out of the data ocean. [Great Barrington, Massachusetts]: North River Press. ISBN 0-88427-089-0.
Fox, Robert; Goldratt, Eliyahu M. (1986). The race. [Great Barrington, Massachusetts]: North River Press. ISBN 0-88427-062-9.
Schragenheim, Eli. (1999). Management dilemmas. [Boca Raton, Florida]: St. Lucie Press. p. 209. ISBN 1-57444-222-8.
Schragenheim, Eli & Dettmer, H. William. (2000). Manufacturing at warp speed: optimizing supply chain financial performance. [Boca Raton, Florida]: St. Lucie Press. p. 342. ISBN 1-57444-293-7.
Schragenheim, Eli, Dettmer, H. William, and Patterson, J. Wayne. (2009). Supply chain management at warp speed: integrating the system from end to end. [Boca Raton, Florida]: CRC Press. p. 220. ISBN 978-1-42007-335-5.{{cite book}}: CS1 maint: multiple names: authors list (link)
Lepore & Cohen, Domenico & Oded (1999). Deming and Goldratt: The Decalogue. Great Barrington (Massachusetts): North River Press. p. 179. ISBN 0884271633.
John Tripp TOC Executive Challenge A Goal Game. ISBN 0-88427-186-2
Goldratt, Eliyahu M. (2003). Production the TOC Way with Simulator. North River Press, Great Barrington, Massachusetts. ISBN 0-88427-175-7.
Stein, Robert E. (3 June 2003). Re-Engineering The Manufacturing System. Marcel Dekker. ISBN 0-8247-4265-6.
Stein, Robert E. (14 February 1997). The Theory of Constraints. Marcel Dekker. ISBN 0-8247-0064-3.
Jacob, Dee; Bergland, Suzan; Cox, Jeff (29 December 2009). Velocity: Combining Lean, Six Sigma and the Theory of Constraints to Achieve Breakthrough Performance. Free Pre. p. 320. ISBN 978-1439158920.
Dettmer, H (1998). Constraint Theory A Logic-Based Approach to System Improvement (PDF).
Fedurko, J. Through Clouds to Solutions: Working with UDEs and UDE clouds. Estonia: Ou Vali Press.

{
  "by": "vegetablepotpie",
  "descendants": 64,
  "id": 40222429,
  "kids": [
    40223693,
    40223667,
    40227737,
    40225997,
    40226058,
    40223246,
    40223522,
    40229753,
    40228896,
    40238560,
    40223131,
    40223704
  ],
  "score": 122,
  "time": 1714567778,
  "title": "Theory of Constraints",
  "type": "story",
  "url": "https://en.wikipedia.org/wiki/Theory_of_constraints"
}

{
  "author": "Contributors to Wikimedia projects",
  "date": "2024-12-07T21:10:00.000Z",
  "description": null,
  "image": "https://upload.wikimedia.org/wikipedia/commons/thumb/a/a2/Factory.svg/100px-Factory.svg.png",
  "logo": "https://logo.clearbit.com/wikipedia.org",
  "publisher": "Wikipedia",
  "title": "Theory of constraints - Wikipedia",
  "url": "https://en.wikipedia.org/wiki/Theory_of_constraints"
}

{
  "url": "https://en.wikipedia.org/wiki/Theory_of_constraints",
  "title": "Theory of constraints - Wikipedia",
  "description": "The theory of constraints (TOC) is a management paradigm that views any manageable system as being limited in achieving more of its goals by a very small number of constraints. There is always at least one...",
  "links": [
    "https://en.wikipedia.org/wiki/Theory_of_constraints"
  ],
  "image": "",
  "content": "<div>\n<p>The <b>theory of constraints</b> (<b>TOC</b>) is a <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Management_paradigm\" title=\"Management paradigm\">management paradigm</a> that views any manageable system as being limited in achieving more of its goals by a very small number of <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Theory_of_constraints#Constraints\">constraints</a>. There is always at least one constraint, and TOC uses <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Theory_of_constraints#The_five_focusing_steps\">a focusing process</a> to identify the constraint and restructure the rest of the organization around it. TOC adopts the common idiom \"a chain is no stronger than its weakest link\". That means that organizations and processes are vulnerable because the weakest person or part can always damage or break them, or at least adversely affect the outcome.\n</p>\n<p>The theory of constraints is an overall <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Management_philosophy\" title=\"Management philosophy\">management philosophy</a>, introduced by <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Eliyahu_M._Goldratt\" title=\"Eliyahu M. Goldratt\">Eliyahu M. Goldratt</a> in his 1984 book titled <i><a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/The_Goal_(novel)\" title=\"The Goal (novel)\">The Goal</a></i>, that is geared to help organizations continually achieve their goals.<sup><a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Theory_of_constraints#cite_note-goal-1\"><span>[</span>1<span>]</span></a></sup> Goldratt adapted the concept to project management with his book <i>Critical Chain</i>, published in 1997.\n</p><p>An earlier propagator of a similar concept was <a target=\"_blank\" href=\"https://en.wikipedia.org/w/index.php?title=Wolfgang_Mewes&amp;action=edit&amp;redlink=1\" title=\"Wolfgang Mewes (page does not exist)\">Wolfgang Mewes</a><sup><a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Theory_of_constraints#cite_note-2\"><span>[</span>2<span>]</span></a></sup> in Germany with publications on <i>power-oriented management theory</i> (Machtorientierte Führungstheorie, 1963) and following with his <i>Energo-Kybernetic System (EKS, 1971)</i>, later renamed <i><a target=\"_blank\" href=\"https://de.wikipedia.org/wiki/Engpasskonzentrierte_Strategie\" title=\"de:Engpasskonzentrierte Strategie\">Engpasskonzentrierte Strategie</a></i> (Bottleneck-focused Strategy) as a more advanced <i>theory of bottlenecks</i>. The publications of Wolfgang Mewes are marketed through the FAZ Verlag, publishing house of the German newspaper <i><a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Frankfurter_Allgemeine_Zeitung\" title=\"Frankfurter Allgemeine Zeitung\">Frankfurter Allgemeine Zeitung</a></i>. However, the paradigm <i>Theory of constraints</i> was first used by Goldratt.\n</p>\n<p>The underlying premise of the theory of constraints is that organizations can be measured and controlled by variations on three measures: <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Throughput_(business)\" title=\"Throughput (business)\">throughput</a>, <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Operational_expense\" title=\"Operational expense\">operational expense</a>, and <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Inventory\" title=\"Inventory\">inventory</a>. 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.<sup><a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Theory_of_constraints#cite_note-essays-3\"><span>[</span>3<span>]</span></a></sup>\n</p><p>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 <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Profit_(economics)\" title=\"Profit (economics)\">profit</a>.  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.<sup><a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Theory_of_constraints#cite_note-essays-3\"><span>[</span>3<span>]</span></a></sup>\n</p>\n<div><h3 id=\"The_five_focusing_steps\">The five focusing steps</h3><p><span><span>[</span><a target=\"_blank\" href=\"https://en.wikipedia.org/w/index.php?title=Theory_of_constraints&amp;action=edit&amp;section=3\" title=\"Edit section: The five focusing steps\"><span>edit</span></a><span>]</span></span></p></div>\n<p>TOC is based on the premise that the rate of <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Goal\" title=\"Goal\">goal</a> achievement by a <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Goal-oriented\" title=\"Goal-oriented\">goal-oriented</a> system (i.e., the system's <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Throughput_(business)\" title=\"Throughput (business)\">throughput</a>) is limited by at least one <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Theory_of_constraints#Constraints\">constraint</a>.\n</p><p>The argument by <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Reductio_ad_absurdum\" title=\"Reductio ad absurdum\">reductio ad absurdum</a> 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.\n</p><p>Only by increasing flow through the constraint can overall throughput be increased.<sup><a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Theory_of_constraints#cite_note-goal-1\"><span>[</span>1<span>]</span></a></sup>\n</p><p>Assuming the goal of a system has been articulated and its measurements defined, the steps are:\n</p>\n<ol><li><i>Identify</i> the system's constraint(s).</li>\n<li>Decide how to <i>exploit</i> the system's constraint(s).</li>\n<li><i>Subordinate</i> everything else to the above decision.</li>\n<li><i>Elevate</i> the system's constraint(s).</li>\n<li><i>Warning!</i> If in the previous steps a <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Theory_of_constraints#Breaking_a_constraint\">constraint has been broken</a>, go back to step 1, but do not allow <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Inertia\" title=\"Inertia\">inertia</a> to cause a system's constraint.<sup><a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Theory_of_constraints#cite_note-goldratt2004-4\"><span>[</span>4<span>]</span></a></sup></li></ol>\n<p>The goal of a commercial organization is: \"Make more money now and in the future\",<sup><a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Theory_of_constraints#cite_note-5\"><span>[</span>5<span>]</span></a></sup> and its measurements are given by <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Throughput_accounting\" title=\"Throughput accounting\">throughput accounting</a> as: throughput, <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Inventory\" title=\"Inventory\">inventory</a>, and <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Operating_expenses\" title=\"Operating expenses\">operating expenses</a>.\n</p><p>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 <i><a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Continual_improvement_process\" title=\"Continual improvement process\">process of ongoing improvement</a></i> (POOGI).\n</p><p>These focusing steps are the key steps to developing the specific <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Theory_of_constraints#Applications\">applications</a> mentioned below.\n</p>\n<p>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.\n</p><p>Types of (internal) constraints\n</p>\n<ul><li>Equipment: The way equipment is currently used limits the ability of the system to produce more salable goods/services.</li>\n<li>People: Lack of <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Skill\" title=\"Skill\">skilled</a> people limits the system. <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Mental_model\" title=\"Mental model\">Mental models</a> held by people can cause behaviour that becomes a constraint.</li>\n<li>Policy: A written or unwritten policy prevents the system from making more.</li></ul>\n<p>The concept of the constraint in Theory of Constraints is analogous to but differs from the <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Constraint_(mathematics)\" title=\"Constraint (mathematics)\">constraint</a> that shows up in mathematical <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Optimization_(mathematics)\" title=\"Optimization (mathematics)\">optimization</a>. 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).\n</p><p>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 <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Limiting_factor\" title=\"Limiting factor\">limiting factor</a> that is preventing the organization from getting more throughput (typically, revenue through sales) even when nothing goes wrong.\n</p>\n<div><h3 id=\"Breaking_a_constraint\">Breaking a constraint</h3><p><span><span>[</span><a target=\"_blank\" href=\"https://en.wikipedia.org/w/index.php?title=Theory_of_constraints&amp;action=edit&amp;section=5\" title=\"Edit section: Breaking a constraint\"><span>edit</span></a><span>]</span></span></p></div>\n<p>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.\n</p>\n<p>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 (<a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Murphy%27s_Law\" title=\"Murphy's Law\">Murphy</a>) before and behind the constraint.\n</p><p>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.\n</p><p>Buffers are <i>not</i> the small queue of work that sits before every work center in a <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Kanban\" title=\"Kanban\">kanban</a> 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).\n</p><p>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.\n</p>\n<p>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<sup><a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Theory_of_constraints#cite_note-6\"><span>[</span>6<span>]</span></a></sup> 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\".\n</p>\n<ul><li>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.</li>\n<li>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.</li>\n<li>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).</li>\n<li>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.</li></ul>\n<p>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>i.e., the intended outcome of the project</i>).\n</p>\n<p>The focusing steps, this process of ongoing improvement, have been applied to <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Manufacturing\" title=\"Manufacturing\">manufacturing</a>, <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Project_management\" title=\"Project management\">project management</a>, <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Supply_chain\" title=\"Supply chain\">supply chain</a>/distribution generated specific solutions. Other tools (mainly the \"thinking process\") also led to TOC applications in the fields of <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Marketing\" title=\"Marketing\">marketing</a> and <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Sales\" title=\"Sales\">sales</a>, and <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Finance\" title=\"Finance\">finance</a>.  The solution as applied to each of these areas are listed below.\n</p>\n<p>Within manufacturing operations and <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Operations_management\" title=\"Operations management\">operations management</a>, the solution seeks to pull materials through the system, rather than push them into the system. The primary methodology used is drum-buffer-rope (DBR)<sup><a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Theory_of_constraints#cite_note-race-7\"><span>[</span>7<span>]</span></a></sup> and a variation called simplified drum-buffer-rope (S-DBR).<sup><a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Theory_of_constraints#cite_note-sdbr-8\"><span>[</span>8<span>]</span></a></sup>\n</p><p>Drum-buffer-rope is a manufacturing execution methodology based on the fact the output of a system can only be the same as the output at the constraint of the system. Any attempt to produce more than what the constraint can process just leads to excess inventory piling up.<sup><a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Theory_of_constraints#cite_note-9\"><span>[</span>9<span>]</span></a></sup> The method is named for its three components. The <i>drum</i> is the rate at which the physical constraint of the plant can work: the work center or machine or operation that limits the ability of the entire system to produce more. The rest of the plant follows the beat of the drum. Schedule at the drum decides what the system should produce, in what sequence to produce and how much to produce.<sup><a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Theory_of_constraints#cite_note-10\"><span>[</span>10<span>]</span></a></sup> They make sure the drum has work and that anything the drum has processed does not get wasted.\n</p><p>The <i>buffer</i> protects the drum, so that it always has work flowing to it. Buffers in DBR provide the additional lead time beyond the required set up and process times, for materials in the product flow. Since these buffers have time as their unit of measure, rather than quantity of material, this makes the priority system operate strictly based on the time an order is expected to be at the drum. Each work order will have a remaining buffer status that can be calculated. Based on this buffer status, work orders can be color coded into Red, Yellow and Green. The red orders have the highest priority and must be worked on first, since they have penetrated most into their buffers followed by yellow and green. As time evolves, this buffer status might change and the color assigned to the particular work order change with it.<sup><a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Theory_of_constraints#cite_note-11\"><span>[</span>11<span>]</span></a></sup><sup><a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Theory_of_constraints#cite_note-12\"><span>[</span>12<span>]</span></a></sup>\n</p><p>Traditional DBR usually calls for buffers at several points in the system: the constraint, synchronization points and at shipping. S-DBR has a buffer at shipping and manages the flow of work across the drum through a load planning mechanism.<sup><a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Theory_of_constraints#cite_note-13\"><span>[</span>13<span>]</span></a></sup>\n</p><p>The <i>rope</i> is the work release mechanism for the plant. Orders are released to the shop floor at one \"buffer time\" before they are due to be processed by the constraint. In other words, if the buffer is 5 days, the order is released 5 days before it is due at the constraint. Putting work into the system earlier than this buffer time is likely to generate too-high work-in-process and slow down the entire system.<sup><a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Theory_of_constraints#cite_note-International_Journal_of_Production_Research-14\"><span>[</span>14<span>]</span></a></sup>\n</p>\n<div><h3 id=\"High-speed_automated_production_lines\">High-speed automated production lines</h3><p><span><span>[</span><a target=\"_blank\" href=\"https://en.wikipedia.org/w/index.php?title=Theory_of_constraints&amp;action=edit&amp;section=10\" title=\"Edit section: High-speed automated production lines\"><span>edit</span></a><span>]</span></span></p></div>\n<p>Automated production lines achieve high throughput rates and output quantities by deploying automation solutions that are highly task-specific. Depending on their design and construction, these machines operate at different speeds and capacities and therefore have varying efficiency levels.\n</p><p>A prominent example is the use of automated production lines in the beverage industry. Filling systems usually have several machines executing parts of the complete bottling process, from filling primary containers to secondary packaging and palletisation.<sup><a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Theory_of_constraints#cite_note-15\"><span>[</span>15<span>]</span></a></sup>\n</p><p>To be able to maximize the throughput, the production line usually has a designed constraint. This constraint is typically the slowest and often the most expensive machine on the line. The overall throughput of the line is determined by this machine. All other machines can operate faster and are connected by conveyors.\n</p><p>The conveyors usually have the ability to buffer product. In the event of a stoppage at a machine other than the constraint, the conveyor can buffer the product enabling the constraint machine to keep on running.\n</p><p>A typical line setup is such that in normal operation the upstream conveyors from the constraint machine are always run full to prevent starvation at the constraint and the downstream conveyors are run empty to prevent a back up at the constraint. The overall aim is to prevent minor stoppages at the machines from impacting the constraint.\n</p><p>For this reason as the machines get further from the constraint, they have the ability to run faster than the previous machine and this creates a V curve.<sup>[<i><a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Wikipedia:Citation_needed\" title=\"Wikipedia:Citation needed\"><span>citation needed</span></a></i>]</sup>\n</p>\n<div><h3 id=\"Supply_chain_and_logistics\">Supply chain and logistics</h3><p><span><span>[</span><a target=\"_blank\" href=\"https://en.wikipedia.org/w/index.php?title=Theory_of_constraints&amp;action=edit&amp;section=11\" title=\"Edit section: Supply chain and logistics\"><span>edit</span></a><span>]</span></span></p></div>\n<p>In general, the solution for <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Supply_chain\" title=\"Supply chain\">supply chains</a> is to create flow of inventory so as to ensure greater availability and to eliminate <a target=\"_blank\" href=\"https://en.wiktionary.org/wiki/surplus\" title=\"wikt:surplus\">surpluses</a>.\n</p><p>The TOC distribution solution is effective when used to address a single link in the supply chain and more so across the entire system, even if that system comprises many different companies. The purpose of the TOC distribution solution is to establish a competitive advantage based on extraordinary availability by reducing the damages caused when the flow of goods is interrupted by shortages and surpluses.\n</p><p>This approach uses several new rules to protect availability with less inventory than is conventionally required.\n</p>\n<ol><li>Inventory is held at an aggregation point(s) as close as possible to the source. This approach ensures smoothed demand at the aggregation point, requiring proportionally less inventory. The distribution centers holding the aggregated stock are able to ship goods downstream to the next link in the supply chain much more quickly than a make-to-order manufacturer can.</li>\n<li>Following this rule may result in a make-to-order manufacturer converting to make-to-stock.  The inventory added at the aggregation point is significantly less than the inventory reduction downstream.</li>\n<li>In all stocking locations, initial inventory buffers are set which effectively create an upper limit of the inventory at that location. The buffer size is equal to the maximum expected consumption within the average Replenishment Time (\"RT\"), plus additional stock to protect in case a delivery is late. In other words, there is no advantage in holding more inventory in a location than the amount that might be consumed before more could be ordered and received. Typically, the sum of the on hand value of such buffers are 25–75% less than currently observed average inventory levels\n<ol><li>Replenishment Time (RT) is the sum of the delay, after the first consumption following a delivery, before an order is placed plus the delay after the order is placed until the ordered goods arrive at the ordering location.</li></ol></li>\n<li>Once buffers have been established, no replenishment orders are placed as long as the quantity inbound (already ordered but not yet received) plus the quantity on hand are equal to or greater than the buffer size. Following this rule causes surplus inventory to be bled off as it is consumed.</li>\n<li>For any reason, when on hand plus inbound inventory is less than the buffer, orders are placed as soon as practical to increase the inbound inventory so that the relationship on Hand + Inbound = Buffer is maintained.</li>\n<li>To ensure buffers remain correctly sized even with changes in the rates of demand and replenishment, a simple recursive algorithm called Buffer Management is used.  When the on hand inventory level is in the upper third of the buffer for a full RT, the buffer is reduced by one third (and don't forget rule 3).  Alternatively, when the on hand inventory is in the bottom one third of the buffer for too long, the buffer is increased by one third (and don't forget rule 4).  The definition of \"too long\" may be changed depending on required service levels, however, a rule of thumb is 20% of the RT. Moving buffers up more readily than down is supported by the usually greater damage caused by shortages as compared to the damage caused by surpluses.</li></ol>\n<p>Once inventory is managed as described above, continuous efforts should be undertaken to reduce RT, late deliveries, supplier minimum order quantities (both per <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Stock_Keeping_Unit\" title=\"Stock Keeping Unit\">SKU</a> and per order) and customer order batching. Any improvements in these areas will automatically improve both availability and inventory turns, thanks to the adaptive nature of Buffer Management.\n</p><p>A stocking location that manages inventory according to the TOC should help a non-TOC customer (downstream link in a supply chain, whether internal or external) manage their inventory according to the TOC process. This type of help can take the form of a vendor managed inventory (VMI). The TOC distribution link simply extends its buffer sizing and management techniques to its customers' inventories. Doing so has the effect of smoothing the demand from the customer and reducing order sizes per SKU. VMI results in better availability and inventory turns for both supplier and customer. The benefits to the non-TOC customers are sufficient to meet the purpose of capitalizing on the competitive edge by giving the customer a reason to be more loyal and give more business to the upstream link. When the end consumers buy more, the whole supply chain sells more.\n</p><p>One caveat should be considered. Initially and only temporarily, the supply chain or a specific link may sell less as the surplus inventory in the system is sold.  However, the sales lift due to improved availability is a countervailing factor. The current levels of surpluses and shortages make each case different.\n</p>\n<div><h3 id=\"Finance_and_accounting\">Finance and accounting</h3><p><span><span>[</span><a target=\"_blank\" href=\"https://en.wikipedia.org/w/index.php?title=Theory_of_constraints&amp;action=edit&amp;section=12\" title=\"Edit section: Finance and accounting\"><span>edit</span></a><span>]</span></span></p></div>\n<p>Holistic thinking applied to the finance application has been termed <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Throughput_accounting\" title=\"Throughput accounting\">throughput accounting</a>.<sup><a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Theory_of_constraints#cite_note-tpa-16\"><span>[</span>16<span>]</span></a></sup> Throughput accounting suggests that one examine the impact of investments and operational changes in terms of the impact on the throughput of the business.  It is an alternative to <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Cost_accounting\" title=\"Cost accounting\">cost accounting</a>.\n</p><p>The primary measures for a TOC view of finance and accounting are: throughput, operating expense and investment. Throughput is calculated from sales minus \"totally variable cost\", where totally variable cost is usually calculated as the cost of raw materials that go into creating the item sold.<sup><a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Theory_of_constraints#cite_note-tocma-17\"><span>[</span>17<span>]</span></a></sup><sup><span>: 13–14 </span></sup>\n</p>\n<p><a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Critical_Chain_Project_Management\" title=\"Critical Chain Project Management\">Critical Chain Project Management</a> (CCPM) are utilized in this area.<sup><a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Theory_of_constraints#cite_note-criticalchain-18\"><span>[</span>18<span>]</span></a></sup> CCPM is based on the idea that all projects look like A-plants: all activities converge to a final deliverable. As such, to protect the project, there must be internal buffers to protect synchronization points and a final project buffer to protect the overall project.\n</p>\n<div><h3 id=\"Marketing_and_sales\">Marketing and sales</h3><p><span><span>[</span><a target=\"_blank\" href=\"https://en.wikipedia.org/w/index.php?title=Theory_of_constraints&amp;action=edit&amp;section=14\" title=\"Edit section: Marketing and sales\"><span>edit</span></a><span>]</span></span></p></div>\n<p>While originally focused on manufacturing and logistics, TOC has expanded into <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Sales_management\" title=\"Sales management\">sales management</a> and <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Marketing\" title=\"Marketing\">marketing</a>. Its role is explicitly acknowledged in the field of <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Sales_process_engineering\" title=\"Sales process engineering\">sales process engineering</a>.<sup><a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Theory_of_constraints#cite_note-Selden-19\"><span>[</span>19<span>]</span></a></sup> For effective sales management one can apply Drum Buffer Rope to the sales process similar to the way it is applied to operations (see Reengineering the Sales Process book reference below). This technique is appropriate when your constraint is in the sales process itself, or if you just want an effective sales management technique which includes the topics of funnel management and conversion rates.<sup>[<i><a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Wikipedia:Citation_needed\" title=\"Wikipedia:Citation needed\"><span>citation needed</span></a></i>]</sup>\n</p>\n<p>The thinking processes are a set of tools to help managers walk through the steps of initiating and implementing a project. When used in a logical flow, they help walk through a <a target=\"_blank\" href=\"https://en.wiktionary.org/wiki/buy-in\" title=\"wikt:buy-in\">buy-in</a> process:\n</p>\n<ol><li>Gain agreement on the problem</li>\n<li>Gain agreement on the direction for a solution</li>\n<li>Gain agreement that the solution solves the problem</li>\n<li>Agree to overcome any potential negative ramifications</li>\n<li>Agree to overcome any obstacles to implementation</li></ol>\n<p>TOC practitioners sometimes refer to these in the negative as working through <i>layers of resistance</i> to a change.\n</p><p>Recently, the <i><a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Current_reality_tree_(theory_of_constraints)\" title=\"Current reality tree (theory of constraints)\">current reality tree</a></i> (CRT) and <i>future reality tree</i> (FRT) have been applied to an argumentative academic paper.<sup><a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Theory_of_constraints#cite_note-20\"><span>[</span>20<span>]</span></a></sup>\n</p><p>Despite its origins as a manufacturing approach (Goldratt &amp; Cox, The Goal: A process of Ongoing Improvement, 1992), Goldratt's Theory of Constraints (TOC) methodology is now regarded as a systems methodology with strong foundations in the hard sciences (Mabin, 1999). Through its tools for convergent thinking and synthesis, the \"Thinking processes\", which underpin the entire TOC methodology, help identify and manage constraints and guide continuous improvement and change in organizations (Dettmer H., 1998).\n</p><p>The process of change requires the identification and acceptance of core issues; the goal and the means to the goal. This comprehensive set of logical tools can be used for exploration, solution development and solution implementation for individuals, groups or organizations. Each tool has a purpose and nearly all tools can be used independently (Cox &amp; Spencer, 1998). Since these thinking tools are designed to address successive \"layers of resistance\" and enable communication, it expedites securing \"buy in\" of groups. While CRT (current reality tree) represents the undesirable effects of the current situation, the FRT (the future reality tree), NBR (negative branch) help people plan and understand the possible results of their actions. The PRT (prerequisite tree) and TRT (transition tree) are designed to build collective buy in and aid in the Implementation phase. The logical constructs of these tools or diagrams are the necessary condition logic, the sufficient cause logic and the strict logic rules that are used to validate cause-effect relationships which are modelled with these tools (Dettmer W., 2006).\n</p><p>A summary of these tools, the questions they help answer and the associated logical constructs used is presented in the table below.\n</p>\n<table>\n<tbody><tr>\n<th></th>\n<th>Sufficient thinking\n<p>\"If……. then\"\n</p>\n</th>\n<th>Necessary Thinking\n<p>\"In order to…we must\"\n</p>\n</th></tr>\n<tr>\n<td><b>What to change?</b></td>\n<td><a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Current_reality_tree_(theory_of_constraints)\" title=\"Current reality tree (theory of constraints)\">Current reality tree</a></td>\n<td>\n</td></tr>\n<tr>\n<td><b>What to change to?</b></td>\n<td>Future Reality Tree\n<p><a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Negative_Branch_Reservations\" title=\"Negative Branch Reservations\">Negative Branch Reservations</a>\n</p>\n</td>\n<td><a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Evaporating_cloud\" title=\"Evaporating cloud\">Evaporating cloud</a>\n</td></tr>\n<tr>\n<td><b>How to change?</b></td>\n<td>Transition Tree</td>\n<td>Prerequisite Tree\n</td></tr></tbody></table>\n<p><b>TOC Thinking Process Tools:</b>\nUse of these tools are based on the fundamental beliefs of TOC that organizations a) are inherently simple (interdependencies exist in organizations) b) desire inherent harmony (win – win solutions are possible) c) are inherently good (people are good) and have inherent potential (people and organizations have potential to do better) (Goldratt E., 2009). In the book \"Through the clouds to solutions\" Jelena Fedurko (Fedurko, 2013) states that the major areas for application of TP tools as:\n</p>\n<ul><li>To create and enhance thinking and learning skills</li>\n<li>To make better decisions</li>\n<li>To develop responsibility for one's own actions through understanding their consequences</li>\n<li>To handle conflicts with more confidence and win-win outcomes</li>\n<li>To correct behavior with undesirable consequences</li>\n<li>Assist in evaluating conditions for achieving a desired outcome</li>\n<li>To assist in peer mediation</li>\n<li>To assist in relationship between subordinates and bosses<sup>[<i><a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Wikipedia:Citation_needed\" title=\"Wikipedia:Citation needed\"><span>citation needed</span></a></i>]</sup></li></ul>\n<div><h2 id=\"Development_and_practice\">Development and practice</h2><p><span><span>[</span><a target=\"_blank\" href=\"https://en.wikipedia.org/w/index.php?title=Theory_of_constraints&amp;action=edit&amp;section=16\" title=\"Edit section: Development and practice\"><span>edit</span></a><span>]</span></span></p></div>\n<p>TOC was initiated by Goldratt, who until his death was still the main driving force behind the development and practice of TOC. There is a network of individuals and small companies loosely coupled as practitioners around the world. TOC is sometimes referred to as \"constraint management\". TOC is a large body of knowledge with a strong guiding philosophy of growth.\n</p>\n<p>Criticisms that have been leveled against TOC include:\n</p>\n<div><h3 id=\"Claimed_suboptimality_of_drum-buffer-rope\">Claimed suboptimality of drum-buffer-rope</h3><p><span><span>[</span><a target=\"_blank\" href=\"https://en.wikipedia.org/w/index.php?title=Theory_of_constraints&amp;action=edit&amp;section=18\" title=\"Edit section: Claimed suboptimality of drum-buffer-rope\"><span>edit</span></a><span>]</span></span></p></div>\n<p>While TOC has been compared favorably to linear programming techniques,<sup><a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Theory_of_constraints#cite_note-21\"><span>[</span>21<span>]</span></a></sup> D. Trietsch from University of Auckland argues that DBR methodology is inferior to competing methodologies.<sup><a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Theory_of_constraints#cite_note-22\"><span>[</span>22<span>]</span></a></sup><sup><a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Theory_of_constraints#cite_note-23\"><span>[</span>23<span>]</span></a></sup> Linhares, from the <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Funda%C3%A7%C3%A3o_Get%C3%BAlio_Vargas\" title=\"Fundação Getúlio Vargas\">Getulio Vargas Foundation</a>, has shown that the TOC approach to establishing an optimal product mix is unlikely to yield optimum results, as it would imply that <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/P_%3D_NP_problem\" title=\"P = NP problem\">P=NP</a>.<sup><a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Theory_of_constraints#cite_note-24\"><span>[</span>24<span>]</span></a></sup>\n</p>\n<div><h3 id=\"Unacknowledged_debt\">Unacknowledged debt</h3><p><span><span>[</span><a target=\"_blank\" href=\"https://en.wikipedia.org/w/index.php?title=Theory_of_constraints&amp;action=edit&amp;section=19\" title=\"Edit section: Unacknowledged debt\"><span>edit</span></a><span>]</span></span></p></div>\n<p>Duncan (as cited by Steyn)<sup><a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Theory_of_constraints#cite_note-steyn-25\"><span>[</span>25<span>]</span></a></sup>\nsays that TOC borrows heavily from <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/System_dynamics\" title=\"System dynamics\">systems dynamics</a> developed by <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Jay_Forrester\" title=\"Jay Forrester\">Forrester</a> in the 1950s and from <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Statistical_process_control\" title=\"Statistical process control\">statistical process control</a> which dates back to World War II. And Noreen Smith and Mackey, in their independent report on TOC, point out that several key concepts in TOC \"have been topics in management accounting textbooks for decades.\"<sup><a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Theory_of_constraints#cite_note-tocma-17\"><span>[</span>17<span>]</span></a></sup><sup><span>: 149 </span></sup> It is also claimed<sup>[<i><a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Wikipedia:Citation_needed\" title=\"Wikipedia:Citation needed\"><span>citation needed</span></a></i>]</sup> that Goldratt's books fail to acknowledge that TOC borrows from more than 40 years of previous management science research and practice, particularly from <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Program_evaluation_and_review_technique\" title=\"Program evaluation and review technique\">program evaluation and review technique</a>/<a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Critical_path_method\" title=\"Critical path method\">critical path method</a> (PERT/CPM) and the <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Just-in-time_(business)\" title=\"Just-in-time (business)\">just in time</a> strategy.\n</p><p>A rebuttal to these criticisms is offered in Goldratt's \"What is the <i>Theory of Constraints</i> and How Should it be Implemented?\", and in his audio program, \"Beyond The Goal\". In these, Goldratt discusses the history of disciplinary sciences, compares the strengths and weaknesses of the various disciplines, and acknowledges the sources of information and inspiration for the thinking processes and critical chain methodologies. Articles published in the now-defunct Journal of <i>Theory of Constraints</i> referenced foundational materials. Goldratt published an article<sup><a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Theory_of_constraints#cite_note-giants-26\"><span>[</span>26<span>]</span></a></sup> and gave talks<sup><a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Theory_of_constraints#cite_note-giantsvideo-27\"><span>[</span>27<span>]</span></a></sup> with the title \"Standing on the Shoulders of Giants\" in which he gives credit for many of the core ideas of Theory of Constraints. Goldratt has sought many times to show the correlation between various improvement methods.\n</p><p>Goldratt has been criticized on lack of openness in his theories, an example being him not releasing the algorithm he used for the Optimum Performance Training system.<sup><a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Theory_of_constraints#cite_note-rahman1998-28\"><span>[</span>28<span>]</span></a></sup> Some view him as unscientific with many of his theories, tools and techniques not being a part of the public domain, rather a part of his own framework of profiting on his ideas.\nAccording to Gupta and Snyder (2009), despite being recognized as a genuine management philosophy nowadays, TOC has yet failed to demonstrate its effectiveness in the academic literature and as such, cannot be considered academically worthy to be called a widely recognized theory.  TOC needs more case studies that prove a connection between implementation and improved financial performance.<sup><a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Theory_of_constraints#cite_note-gupta2009-29\"><span>[</span>29<span>]</span></a></sup>\nNave (2002) argues that TOC does not take employees into account and fails to empower them in the production process.  He also states that TOC fails to address unsuccessful policies as constraints.<sup><a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Theory_of_constraints#cite_note-nave2002-30\"><span>[</span>30<span>]</span></a></sup>\nIn contrast, Mukherjee and Chatterjee (2007) state that much of the criticism of Goldratt's work has been focused on the lack of rigour in his work, but not of the bottleneck approach, which are two different aspects of the issue.<sup><a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Theory_of_constraints#cite_note-31\"><span>[</span>31<span>]</span></a></sup>\n</p>\n<div><h2 id=\"Certification_and_education\">Certification and education</h2><p><span><span>[</span><a target=\"_blank\" href=\"https://en.wikipedia.org/w/index.php?title=Theory_of_constraints&amp;action=edit&amp;section=20\" title=\"Edit section: Certification and education\"><span>edit</span></a><span>]</span></span></p></div>\n<p>The Theory of Constraints International Certification Organization (TOCICO) is an independent not-for-profit incorporated society that sets exams to ensure a consistent standard of competence. It is overseen by a board<sup><a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Theory_of_constraints#cite_note-32\"><span>[</span>32<span>]</span></a></sup><sup>[<i><a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Wikipedia:No_original_research#Primary,_secondary_and_tertiary_sources\" title=\"Wikipedia:No original research\"><span>non-primary source needed</span></a></i>]</sup> of academic and industrial experts.  It also hosts an annual international conference. The work presented at these conferences constitutes a core repository of the current knowledge.\n</p>\n<ul><li><a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Index_of_articles_related_to_the_theory_of_constraints\" title=\"Index of articles related to the theory of constraints\">Index of articles related to the theory of constraints</a></li>\n<li><a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Linear_programming\" title=\"Linear programming\">Linear programming</a></li>\n<li><a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Industrial_engineering\" title=\"Industrial engineering\">Industrial engineering</a></li>\n<li><a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Limiting_factor\" title=\"Limiting factor\">Limiting factor</a></li>\n<li><a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Systems_thinking\" title=\"Systems thinking\">Systems thinking</a> – <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Critical_systems_thinking\" title=\"Critical systems thinking\">Critical systems thinking</a> – <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Joint_decision_trap\" title=\"Joint decision trap\">Joint decision traps</a></li>\n<li><a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Twelve_leverage_points\" title=\"Twelve leverage points\">Twelve leverage points</a> by <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Donella_Meadows\" title=\"Donella Meadows\">Donella Meadows</a></li>\n<li><a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Constraint_(disambiguation)\" title=\"Constraint (disambiguation)\">Constraint (disambiguation)</a></li>\n<li><a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Futures_techniques#Systems_engineering\" title=\"Futures techniques\">Thinklets</a></li>\n<li><a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Throughput_(business)\" title=\"Throughput (business)\">Throughput</a></li>\n<li><a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Rate-determining_step\" title=\"Rate-determining step\">Rate-determining step</a></li>\n<li><a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Liebig%27s_law_of_the_minimum\" title=\"Liebig's law of the minimum\">Liebig's law of the minimum</a></li></ul>\n<div>\n<ol>\n<li><span>^ <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Theory_of_constraints#cite_ref-goal_1-0\"><sup><i><b>a</b></i></sup></a> <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Theory_of_constraints#cite_ref-goal_1-1\"><sup><i><b>b</b></i></sup></a></span> <span>Cox, Jeff; Goldratt, Eliyahu M. (1986). <span><a target=\"_blank\" href=\"https://archive.org/details/goalprocessofo00gold\"><i>The goal: a process of ongoing improvement</i></a></span>. [Croton-on-Hudson, New York]: North River Press. <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/ISBN_(identifier)\" title=\"ISBN (identifier)\">ISBN</a> <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Special:BookSources/0-88427-061-0\" title=\"Special:BookSources/0-88427-061-0\">0-88427-061-0</a>.<span></span></span>\n</li>\n<li><span><b><a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Theory_of_constraints#cite_ref-2\">^</a></b></span> <span><a target=\"_blank\" href=\"http://www.wolfgangmewes.de/wm.htm\">\"Beratergruppe Strategie\"</a>. <i>www.wolfgangmewes.de</i><span>. Retrieved <span>17 March</span> 2018</span>.<span></span></span>\n</li>\n<li><span>^ <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Theory_of_constraints#cite_ref-essays_3-0\"><sup><i><b>a</b></i></sup></a> <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Theory_of_constraints#cite_ref-essays_3-1\"><sup><i><b>b</b></i></sup></a></span> <span>Goldratt, Eliyahu M. (1998). <i>Essays on the </i>Theory of Constraints<i><span></span></i>. [Great Barrington, Massachusetts]: North River Press. <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/ISBN_(identifier)\" title=\"ISBN (identifier)\">ISBN</a> <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Special:BookSources/0-88427-159-5\" title=\"Special:BookSources/0-88427-159-5\">0-88427-159-5</a>.<span></span></span>\n</li>\n<li><span><b><a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Theory_of_constraints#cite_ref-goldratt2004_4-0\">^</a></b></span> <span>Eliyahu M. Goldratt. 2004. _The Goal: A Process of Ongoing Improvement, <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/ISBN_(identifier)\" title=\"ISBN (identifier)\">ISBN</a> <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Special:BookSources/978-0-88427-178-9\" title=\"Special:BookSources/978-0-88427-178-9\">978-0-88427-178-9</a>.</span>\n</li>\n<li><span><b><a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Theory_of_constraints#cite_ref-5\">^</a></b></span> <span>Theory of Constraints Handbook, <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/ISBN_(identifier)\" title=\"ISBN (identifier)\">ISBN</a> <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Special:BookSources/978-0-07-166554-4\" title=\"Special:BookSources/978-0-07-166554-4\">978-0-07-166554-4</a>, p. 8</span>\n</li>\n<li><span><b><a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Theory_of_constraints#cite_ref-6\">^</a></b></span> <span>Blackstone Jr., editor, John H. (2013). <i>APICS Dictionary, 13th Edition</i>. Chicago: APICS self-published. p. 186. <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/ISBN_(identifier)\" title=\"ISBN (identifier)\">ISBN</a> <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Special:BookSources/978-0-9882146-1-3\" title=\"Special:BookSources/978-0-9882146-1-3\">978-0-9882146-1-3</a>.<span></span> </span>\n</li>\n<li><span><b><a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Theory_of_constraints#cite_ref-race_7-0\">^</a></b></span> <span>Goldratt, Eliyahu; Fox, Robert (1986). <a target=\"_blank\" href=\"https://archive.org/details/race00gold/page/179\"><i>The Race</i></a>. [Croton-on-Hudson, New York]: North River Press. pp. <a target=\"_blank\" href=\"https://archive.org/details/race00gold/page/179\">179</a>. <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/ISBN_(identifier)\" title=\"ISBN (identifier)\">ISBN</a> <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Special:BookSources/978-0-88427-062-1\" title=\"Special:BookSources/978-0-88427-062-1\">978-0-88427-062-1</a>.<span></span></span>\n</li>\n<li><span><b><a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Theory_of_constraints#cite_ref-sdbr_8-0\">^</a></b></span> <span>Eli Schragenheim &amp; H. William Dettmer (2000). <a target=\"_blank\" href=\"http://www.goalsys.com/books/documents/S-DBRPaper.pdf\">\"Simplified Drum-Buffer-Rope: A Whole System Approach to High Velocity Manufacturing\"</a> <span>(PDF)</span><span>. Retrieved <span>8 December</span> 2007</span>.<span></span> </span>\n</li>\n<li><span><b><a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Theory_of_constraints#cite_ref-9\">^</a></b></span> <span>Goldratt, Eliyahu M. (1986). <a target=\"_blank\" href=\"https://archive.org/details/race00gold/page/77\"><i>The Race</i></a>. Croton-on Hudson, New York: North River Press. pp. <a target=\"_blank\" href=\"https://archive.org/details/race00gold/page/77\">77–97</a>. <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/ISBN_(identifier)\" title=\"ISBN (identifier)\">ISBN</a> <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Special:BookSources/9780884270621\" title=\"Special:BookSources/9780884270621\">9780884270621</a>.<span></span></span>\n</li>\n<li><span><b><a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Theory_of_constraints#cite_ref-10\">^</a></b></span> <span>Goldratt, Eliyahu (1990). <span><a target=\"_blank\" href=\"https://archive.org/details/haystacksyndrome00gold\"><i>The Haystack Syndrome:: Sifting Information out of the Data Ocean</i></a></span>. New York: New York: North River Press. <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/ISBN_(identifier)\" title=\"ISBN (identifier)\">ISBN</a> <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Special:BookSources/9780884270898\" title=\"Special:BookSources/9780884270898\">9780884270898</a>.<span></span></span>\n</li>\n<li><span><b><a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Theory_of_constraints#cite_ref-11\">^</a></b></span> <span>Shri Shrikanth, M (2010). <i>DBR, Buffer Management, and VATI flow classification</i>.<span></span></span>\n</li>\n<li><span><b><a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Theory_of_constraints#cite_ref-12\">^</a></b></span> <span>J. F. Cox III &amp; J. J. Schleier. <i>Theory of Constraints Handbook</i>. New York: McGraw Hill. pp. 175–210.<span></span></span>\n</li>\n<li><span><b><a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Theory_of_constraints#cite_ref-13\">^</a></b></span> <span>Schragenheim, e; Dettmer, H. W; Patterson, J. W. (2009). <i>Supply Chain Management at Warp Speed</i>. Boca Raton: Auerbach publications.<span></span></span>\n</li>\n<li><span><b><a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Theory_of_constraints#cite_ref-International_Journal_of_Production_Research_14-0\">^</a></b></span> <span>Russell, G. R.; Fry, T. D (1997). <i>Order review/release and lot splitting in drum-buffer-rope</i>. pp. 35:827–845.<span></span></span>\n</li>\n<li><span><b><a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Theory_of_constraints#cite_ref-15\">^</a></b></span> <span>'The planning flexibility bottleneck in food processing industries' (2006) Journal of Operations Management 24(3):287-300, DOI:10.1016/j.jom.2004.11.001</span>\n</li>\n<li><span><b><a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Theory_of_constraints#cite_ref-tpa_16-0\">^</a></b></span> <span>Corbett, Thomas (1998). <i>Throughput Accounting</i>. North River Press. p. 160. <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/ISBN_(identifier)\" title=\"ISBN (identifier)\">ISBN</a> <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Special:BookSources/978-0-88427-158-1\" title=\"Special:BookSources/978-0-88427-158-1\">978-0-88427-158-1</a>.<span></span></span>\n</li>\n<li><span>^ <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Theory_of_constraints#cite_ref-tocma_17-0\"><sup><i><b>a</b></i></sup></a> <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Theory_of_constraints#cite_ref-tocma_17-1\"><sup><i><b>b</b></i></sup></a></span> <span>\nEric Noreen; Debra Smith; James T. Mackey (1995). <span><a target=\"_blank\" href=\"https://archive.org/details/theoryofconstrai0000nore\"><i>The </i>Theory of Constraints<i> and its implications for Management Accounting</i></a></span>. North River Press. <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/ISBN_(identifier)\" title=\"ISBN (identifier)\">ISBN</a> <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Special:BookSources/0-88427-116-1\" title=\"Special:BookSources/0-88427-116-1\">0-88427-116-1</a>.<span></span></span>\n</li>\n<li><span><b><a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Theory_of_constraints#cite_ref-criticalchain_18-0\">^</a></b></span> <span>Goldratt, Eliyahu M. (1997). <i>Critical Chain</i>. Great Barrington, Massachusetts: North River Press. <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/ISBN_(identifier)\" title=\"ISBN (identifier)\">ISBN</a> <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Special:BookSources/0-88427-153-6\" title=\"Special:BookSources/0-88427-153-6\">0-88427-153-6</a>.<span></span></span>\n</li>\n<li><span><b><a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Theory_of_constraints#cite_ref-Selden_19-0\">^</a></b></span> <span>Paul H. Selden (1997). <i>Sales Process Engineering: A Personal Workshop</i>. Milwaukee, Wisconsin: ASQ Quality Press. pp. 33–35, 264–268. <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/ISBN_(identifier)\" title=\"ISBN (identifier)\">ISBN</a> <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Special:BookSources/0-87389-418-9\" title=\"Special:BookSources/0-87389-418-9\">0-87389-418-9</a>.<span></span></span>\n</li>\n<li><span><b><a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Theory_of_constraints#cite_ref-20\">^</a></b></span> <span>See the annex of: Vidal, C. 2008.<a target=\"_blank\" href=\"https://arxiv.org/abs/0803.1087\">The Future of Scientific Simulations: from Artificial Life to Artificial Cosmogenesis</a>. In Death And Anti-Death, ed. Charles Tandy, 6: Thirty Years After Kurt Gödel (1906–1978) pp. 285-318. Ria University Press.)</span>\n</li>\n<li><span><b><a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Theory_of_constraints#cite_ref-21\">^</a></b></span> <span>\nQui, Mabel; Fredendall, Lawrence; Zhu, Zhiwei (2002). \"TOC or LP? [production control]\". <i>Manufacturing Engineer</i>. <b>81</b> (4): 190–195. <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Doi_(identifier)\" title=\"Doi (identifier)\">doi</a>:<a target=\"_blank\" href=\"https://doi.org/10.1049%2Fme%3A20020411\">10.1049/me:20020411</a> (inactive 7 December 2024).<span></span><span><code>{{<a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Template:Cite_journal\" title=\"Template:Cite journal\">cite journal</a>}}</code>:  CS1 maint: DOI inactive as of December 2024 (<a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Category:CS1_maint:_DOI_inactive_as_of_December_2024\" title=\"Category:CS1 maint: DOI inactive as of December 2024\">link</a>)</span></span>\n</li>\n<li><span><b><a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Theory_of_constraints#cite_ref-22\">^</a></b></span> <span>Trietsch, D. (2005). <a target=\"_blank\" href=\"http://ac.aua.am/trietsch/web/MBC_to_MBC_II.pdf\">\"From Management by Constraints (MBC) to Management By Criticalities (MBC II)\"</a> <span>(PDF)</span>. <i>Human Systems Management</i>. <b>24</b>: 105–115. <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Doi_(identifier)\" title=\"Doi (identifier)\">doi</a>:<a target=\"_blank\" href=\"https://doi.org/10.3233%2FHSM-2005-24109\">10.3233/HSM-2005-24109</a>.<span></span></span>\n</li>\n<li><span><b><a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Theory_of_constraints#cite_ref-23\">^</a></b></span> <span><a target=\"_blank\" href=\"http://ac.aua.am/trietsch/web/WorkingPaper281.pdf\">http://ac.aua.am/trietsch/web/WorkingPaper281.pdf</a> D. Trietsch, From the Flawed \"Theory of Constraints\" to Hierarchically Balancing Criticalities (HBC), Department of Information Systems and Operations Management, University of Auckland, Working Paper No. 281, May 2004.</span>\n</li>\n<li><span><b><a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Theory_of_constraints#cite_ref-24\">^</a></b></span> <span>Linhares, Alexandre (2009). \"Theory of constraints and the combinatorial complexity of the product-mix decision\". <i>International Journal of Production Economics</i>. <b>121</b> (1): 121–129. <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Doi_(identifier)\" title=\"Doi (identifier)\">doi</a>:<a target=\"_blank\" href=\"https://doi.org/10.1016%2Fj.ijpe.2009.04.023\">10.1016/j.ijpe.2009.04.023</a>.<span></span></span>\n</li>\n<li><span><b><a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Theory_of_constraints#cite_ref-steyn_25-0\">^</a></b></span> <span>\nSteyn, Herman (2000). \"An Investigation into the Fundamentals of Critical Chain Project Scheduling\". <i>International Journal of Project Management</i> (19): 363–369.<span></span></span>\n</li>\n<li><span><b><a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Theory_of_constraints#cite_ref-giants_26-0\">^</a></b></span> <span>Goldratt, Eliyahu M. (2009). <a target=\"_blank\" href=\"https://doi.org/10.1590%2FS0104-530X2009000300002\">\"Standing on the shoulders of giants: production concepts versus production applications. The Hitachi Tool Engineering example\"</a>. <i>Gestão &amp; Produção</i>. <b>16</b> (3): 333–343. <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Doi_(identifier)\" title=\"Doi (identifier)\">doi</a>:<span><a target=\"_blank\" href=\"https://doi.org/10.1590%2FS0104-530X2009000300002\">10.1590/S0104-530X2009000300002</a></span>.<span></span></span>\n</li>\n<li><span><b><a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Theory_of_constraints#cite_ref-giantsvideo_27-0\">^</a></b></span> <span>Archived at <a target=\"_blank\" href=\"https://ghostarchive.org/varchive/youtube/20211211/C3RPFUh3ePQ\">Ghostarchive</a> and the <a target=\"_blank\" href=\"https://web.archive.org/web/20130303190834/http://www.youtube.com/watch?v=C3RPFUh3ePQ\">Wayback Machine</a>: Eliyahu Goldratt. <a target=\"_blank\" href=\"https://www.youtube.com/watch?v=C3RPFUh3ePQ\"><i>Standing on the Shoulders of Giants</i></a>.<span></span></span>\n</li>\n<li><span><b><a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Theory_of_constraints#cite_ref-rahman1998_28-0\">^</a></b></span> <span>Rahman, Shams-ur. \"Theory of constraints: a review of the philosophy and its applications.\" International Journal of Operations &amp; Production Management 18.4 (1998): 336-355.</span>\n</li>\n<li><span><b><a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Theory_of_constraints#cite_ref-gupta2009_29-0\">^</a></b></span> <span>\nGupta, Mahesh, and Doug Snyder. \"Comparing TOC with MRP and JIT: a literature review.\" International Journal of Production Research 47.13 (2009): 3705-3739</span>\n</li>\n<li><span><b><a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Theory_of_constraints#cite_ref-nave2002_30-0\">^</a></b></span> <span>\nNave, Dave. \"How to compare six sigma, lean and the theory of constraints.\" Quality Progress 35.3 (2002): 73-80.</span>\n</li>\n<li><span><b><a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Theory_of_constraints#cite_ref-31\">^</a></b></span> <span>Mukherjee, S. M. and Chatterjee, A. K. (2007). The concept of bottleneck. Working Paper No. 2006-05-01, IIM Ahmedabad</span>\n</li>\n<li><span><b><a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Theory_of_constraints#cite_ref-32\">^</a></b></span> <span><a target=\"_blank\" href=\"http://www.tocico.org/?page=tocico_board\">\"TOCICO Board of Directors - Theory of Constraints International Certification Organization\"</a>. <i>www.tocico.org</i><span>. Retrieved <span>17 March</span> 2018</span>.<span></span></span>\n</li>\n</ol></div>\n<ul><li>Cox, Jeff; Goldratt, Eliyahu M. (1986). <span><a target=\"_blank\" href=\"https://archive.org/details/goalprocessofo00gold\"><i>The goal: a process of ongoing improvement</i></a></span>. [Great Barrington, Massachusetts]: North River Press. <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/ISBN_(identifier)\" title=\"ISBN (identifier)\">ISBN</a> <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Special:BookSources/0-88427-061-0\" title=\"Special:BookSources/0-88427-061-0\">0-88427-061-0</a>.<span></span></li>\n<li>Dettmer, H. William. (2003). <i>Strategic Navigation: A Systems Approach to Business Strategy</i>. [Milwaukee, Wisconsin]: ASQ Quality Press. p. 302. <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/ISBN_(identifier)\" title=\"ISBN (identifier)\">ISBN</a> <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Special:BookSources/0-87389-603-3\" title=\"Special:BookSources/0-87389-603-3\">0-87389-603-3</a>.<span></span></li>\n<li>Dettmer, H. William. (2007). <i>The Logical Thinking Process: A Systems Approach to Complex Problem Solving</i>. [Milwaukee, Wisconsin]: ASQ Quality Press. p. 413. <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/ISBN_(identifier)\" title=\"ISBN (identifier)\">ISBN</a> <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Special:BookSources/978-0-87389-723-5\" title=\"Special:BookSources/978-0-87389-723-5\">978-0-87389-723-5</a>.<span></span></li>\n<li>Goldratt, Eliyahu M. (1994). <span><a target=\"_blank\" href=\"https://archive.org/details/itsnotluck00gold\"><i>It's not luck</i></a></span>. [Great Barrington, Massachusetts]: North River Press. <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/ISBN_(identifier)\" title=\"ISBN (identifier)\">ISBN</a> <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Special:BookSources/0-88427-115-3\" title=\"Special:BookSources/0-88427-115-3\">0-88427-115-3</a>.<span></span></li>\n<li>Goldratt, Eliyahu M. (1997). <i>Critical chain</i>. [Great Barrington, Massachusetts]: North River Press. <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/ISBN_(identifier)\" title=\"ISBN (identifier)\">ISBN</a> <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Special:BookSources/0-88427-153-6\" title=\"Special:BookSources/0-88427-153-6\">0-88427-153-6</a>.<span></span></li>\n<li>Carol A. Ptak; Goldratt, Eliyahu M.; Eli Schragenheim (2000). <a target=\"_blank\" href=\"https://archive.org/details/necessarybutnots00eliy\"><i>Necessary But Not Sufficient</i></a>. [Great Barrington, Massachusetts]: North River Press. <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/ISBN_(identifier)\" title=\"ISBN (identifier)\">ISBN</a> <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Special:BookSources/0-88427-170-6\" title=\"Special:BookSources/0-88427-170-6\">0-88427-170-6</a>.<span></span></li>\n<li>Goldratt, Eliyahu M. (1998). <i>Essays on the </i>Theory of Constraints<i><span></span></i>. [Great Barrington, Massachusetts]: North River Press. <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/ISBN_(identifier)\" title=\"ISBN (identifier)\">ISBN</a> <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Special:BookSources/0-88427-159-5\" title=\"Special:BookSources/0-88427-159-5\">0-88427-159-5</a>.<span></span></li>\n<li>Goldratt, Eliyahu M. (1990). <i>Theory of Constraints</i>. [Great Barrington, Massachusetts]: North River Press. <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/ISBN_(identifier)\" title=\"ISBN (identifier)\">ISBN</a> <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Special:BookSources/0-88427-166-8\" title=\"Special:BookSources/0-88427-166-8\">0-88427-166-8</a>.<span></span></li>\n<li>Goldratt, Eliyahu M. <i>Beyond the Goal : Eliyahu Goldratt Speaks on the </i>Theory of Constraints<i> (Your Coach in a Box)</i>. Coach Series. <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/ISBN_(identifier)\" title=\"ISBN (identifier)\">ISBN</a> <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Special:BookSources/1-59659-023-8\" title=\"Special:BookSources/1-59659-023-8\">1-59659-023-8</a>.<span></span></li>\n<li>Lisa Lang (January 2006). <i>Achieving a Viable Vision: The </i>Theory of Constraints<i> Strategic Approach to Rapid Sustainable Growth</i>. Throughput Publishing, Inc. <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/ISBN_(identifier)\" title=\"ISBN (identifier)\">ISBN</a> <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Special:BookSources/0-9777604-1-3\" title=\"Special:BookSources/0-9777604-1-3\">0-9777604-1-3</a>.<span></span></li>\n<li>Goldratt, Eliyahu M. (1990). <a target=\"_blank\" href=\"https://archive.org/details/haystacksyndrome00gold\"><i>The haystack syndrome: sifting information out of the data ocean</i></a>. [Great Barrington, Massachusetts]: North River Press. <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/ISBN_(identifier)\" title=\"ISBN (identifier)\">ISBN</a> <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Special:BookSources/0-88427-089-0\" title=\"Special:BookSources/0-88427-089-0\">0-88427-089-0</a>.<span></span></li>\n<li>Fox, Robert; Goldratt, Eliyahu M. (1986). <a target=\"_blank\" href=\"https://archive.org/details/race00gold\"><i>The race</i></a>. [Great Barrington, Massachusetts]: North River Press. <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/ISBN_(identifier)\" title=\"ISBN (identifier)\">ISBN</a> <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Special:BookSources/0-88427-062-9\" title=\"Special:BookSources/0-88427-062-9\">0-88427-062-9</a>.<span></span></li>\n<li>Schragenheim, Eli. (1999). <i>Management dilemmas</i>. [Boca Raton, Florida]: St. Lucie Press. p. 209. <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/ISBN_(identifier)\" title=\"ISBN (identifier)\">ISBN</a> <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Special:BookSources/1-57444-222-8\" title=\"Special:BookSources/1-57444-222-8\">1-57444-222-8</a>.<span></span></li>\n<li>Schragenheim, Eli &amp; Dettmer, H. William. (2000). <i>Manufacturing at warp speed: optimizing supply chain financial performance</i>. [Boca Raton, Florida]: St. Lucie Press. p. 342. <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/ISBN_(identifier)\" title=\"ISBN (identifier)\">ISBN</a> <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Special:BookSources/1-57444-293-7\" title=\"Special:BookSources/1-57444-293-7\">1-57444-293-7</a>.<span></span></li>\n<li>Schragenheim, Eli, Dettmer, H. William, and Patterson, J. Wayne. (2009). <i>Supply chain management at warp speed: integrating the system from end to end</i>. [Boca Raton, Florida]: <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/CRC_Press\" title=\"CRC Press\">CRC Press</a>. p. 220. <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/ISBN_(identifier)\" title=\"ISBN (identifier)\">ISBN</a> <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Special:BookSources/978-1-42007-335-5\" title=\"Special:BookSources/978-1-42007-335-5\">978-1-42007-335-5</a>.<span></span><span><code>{{<a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Template:Cite_book\" title=\"Template:Cite book\">cite book</a>}}</code>:  CS1 maint: multiple names: authors list (<a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Category:CS1_maint:_multiple_names:_authors_list\" title=\"Category:CS1 maint: multiple names: authors list\">link</a>)</span></li>\n<li>Lepore &amp; Cohen, Domenico &amp; Oded (1999). <i>Deming and Goldratt: The Decalogue</i>. Great Barrington (Massachusetts): North River Press. p. 179. <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/ISBN_(identifier)\" title=\"ISBN (identifier)\">ISBN</a> <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Special:BookSources/0884271633\" title=\"Special:BookSources/0884271633\">0884271633</a>.<span></span></li>\n<li>John Tripp TOC Executive Challenge A Goal Game. <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/ISBN_(identifier)\" title=\"ISBN (identifier)\">ISBN</a> <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Special:BookSources/0-88427-186-2\" title=\"Special:BookSources/0-88427-186-2\">0-88427-186-2</a></li>\n<li>Goldratt, Eliyahu M. (2003). <i>Production the TOC Way with Simulator</i>. North River Press, Great Barrington, Massachusetts. <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/ISBN_(identifier)\" title=\"ISBN (identifier)\">ISBN</a> <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Special:BookSources/0-88427-175-7\" title=\"Special:BookSources/0-88427-175-7\">0-88427-175-7</a>.<span></span></li>\n<li>Stein, Robert E. (3 June 2003). <i>Re-Engineering The Manufacturing System</i>. Marcel Dekker. <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/ISBN_(identifier)\" title=\"ISBN (identifier)\">ISBN</a> <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Special:BookSources/0-8247-4265-6\" title=\"Special:BookSources/0-8247-4265-6\">0-8247-4265-6</a>.<span></span></li>\n<li>Stein, Robert E. (14 February 1997). <i>The Theory of Constraints</i>. Marcel Dekker. <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/ISBN_(identifier)\" title=\"ISBN (identifier)\">ISBN</a> <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Special:BookSources/0-8247-0064-3\" title=\"Special:BookSources/0-8247-0064-3\">0-8247-0064-3</a>.<span></span></li>\n<li>Jacob, Dee; Bergland, Suzan; Cox, Jeff (29 December 2009). <i>Velocity: Combining Lean, Six Sigma and the Theory of Constraints to Achieve Breakthrough Performance</i>. Free Pre. p. 320. <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/ISBN_(identifier)\" title=\"ISBN (identifier)\">ISBN</a> <a target=\"_blank\" href=\"https://en.wikipedia.org/wiki/Special:BookSources/978-1439158920\" title=\"Special:BookSources/978-1439158920\">978-1439158920</a>.<span></span></li>\n<li>Dettmer, H (1998). <a target=\"_blank\" href=\"http://www.goalsys.com/books/documents/HICSSPaper.pdf\"><i>Constraint Theory A Logic-Based Approach to System Improvement</i></a> <span>(PDF)</span>.<span></span></li>\n<li>Fedurko, J. <i>Through Clouds to Solutions: Working with UDEs and UDE clouds</i>. Estonia: Ou Vali Press.<span></span></li></ul>\n<ul><li><a target=\"_blank\" href=\"http://www.dbrmfg.co.nz/\">A Guide to Implementing the Theory of Constraints</a></li>\n<li><a target=\"_blank\" href=\"http://www.tocinstitute.org/five-focusing-steps.html\">Five focusing Steps</a></li>\n<li><a target=\"_blank\" href=\"http://www.tocinstitute.org/theory-of-constraints.html\">Theory of Constraints Essentials</a></li>\n<li><a target=\"_blank\" href=\"http://www.victoria.ac.nz/som/research/theory-of-constraints\">Theory of Constraints: A Research Database</a></li></ul>\n</div>",
  "author": "",
  "favicon": "https://en.wikipedia.org/static/favicon/wikipedia.ico",
  "source": "en.wikipedia.org",
  "published": "2003-03-31t08:28:53z",
  "ttr": 1166,
  "type": "website"
}