Beware of bottleneck hunting!

In the following video interview, Philip Marris (answering Clarke Ching‘s questions) states that the five focusing steps of Theory of Constraints are wrong!

Well it needs some more listening  to understand the wisdom behind the provocative statement.

First, the five focusing steps (5FS) are basically ok. What bothers Philip is the fifth step after the first iteration.

In his view, accepting to go through the 5FS over and over is just bottleneck hunting and accepting the fact that the organization’s “strategy” is defined by the newest or the next bottleneck.

Philip is advocating to select the most suitable bottleneck, in order to keep mastering it, and surround this bottleneck with excess capacity resources. In this way, the bottleneck remains in one’s span of control, instead of moving upstreams to a supplier or to market’s demand, and keeps at the same point for a longer period of time.

If the 5FS are taken literally, this could lead to an exhausting periodic rearrangement around a new bottleneck, reshuffling the cards regarding strategy, sales, operations and so on.

Organisations need stability, especially factories. Therefore, this approach works well in operations.


Check out Marris-Consulting Youtube Channel for more


Bandeau_CH40_sml

View Christian HOHMANN's profile on LinkedIn

Advertisements

One hour of Theory of Constraints experience, first hand

I was fortunate to “participate” in Philip Marris’ interview by Clarke Ching for Clarke’s podcast series. While making sure all the video and sound was properly taped, I listened to the talk. Latter, editing the video, I had more listening. Now that Clarke made the video public, it’s time to share:

Clarke chats with Philip Marris: Advanced thinking & Back to TOC Basics from Clarke Ching


 

What is Theory of Constraints?

The very minimum to know about Theory of Constraints

In order to define Theory of Constraints (ToC), it is necessary to define what a constraint is. A constraint is anything that limits the system (organization, enterprise, group, process…) from achieving higher performance relative to its purpose.

  • A constraint does always exist, otherwise the system would be infinitely successful, constantly achieving higher performance.
  • A constraint can be part of the system or lying outside of it, e.g. supplies limit the transformation of material, dull market limits the sales, regulation limits operations, etc.

Theory of Constraints is a “business philosophy” or “management paradigm” that takes into account the existence of constraints, focuses on the one that limits the performance of the whole system and strives to achieve more of its goal (patients treatment, sales, throughput, sales, whatsoever).

The constraint is often referred to as the weakest link of the chain (metaphor for the whole process), which limits the performance of the chain. It is therefore useless to improve any other link as long as the weakest has not been strengthened. ToC claims to focus on the most critical factor (the weakest link), while Lean in comparison is often deployed in unfocused way, wasting resources to improve any link of the chain without really improving the whole chain.

The notion of constraint is generally easier to understand using the bottleneck metaphor or the piping system.

 

Click on pictures to go see

Once the constraint is identified, Theory of Constraints proposes consistent methods, tools and thinking processes to get the most out of the system, despite the constraint.

Chris HOHMANN

If you liked this post, share it!

View Christian HOHMANN's profile on LinkedIn


Bottleneck explained with water pipes

Among the analogies used to explain the concept of bottleneck resource, core of the Theory of Constraints in operations and manufacturing, the pipes of a hydraulic system is a classic one.

>lisez cet article en français

Here is a hydraulic system made of a succession of pipes of different diameters.

The throughput of this hydraulic system is limited by the section with the thinnest diameter, which chokes the water flow.

If the water flow must increase, increasing the diameter of pipe before or after the bottleneck section is of no interest, the flow is still limited by the thinnest section. The only way to increase the flow is to work to increase the throughput at the bottleneck.

This rule applies for any system with a bottleneck, the system overall throughput is limited by the bottleneck’s throughput.


Recover wasted capacity with SMED

SMED is a systematic approach to quick changeovers in order to minimize machine downtime. It is welcome to recover wasted capacity on a bottleneck resource.

  • A bottleneck is a resource with a capacity, in average, lower or equal to customer’s demand. A true bottleneck runs 24 hours 7 days a week and still cannot supply what is required.
  • A bottleneck is usually very expensive and/or difficult to get. If this is not the case, the solution is obvious: buy additional capacity!

More about bottlenecks.

As a bottleneck is the limiting factor hindering getting more out of the process, hence making money in case of for-profit organizations, and as the bottleneck resource is not easy to duplicate, the best option is to get more through it.

Analyzing the capacity

Almost every resource has a maximum capacity that can seldom be utilized, because of some reasons that waste some of it. The resource’s capacity can be can be depicted by a lab beaker as shown below, with a maximum capacity of 100 (%).

Several events during production will hinder the utilization of the full capacity:

  • Machine downtime
  • Lack of supplies
  • Human rest time
  • Etc.

These events are wasting the precious capacity, just as if our beaker was leaking. Changeovers usually are an important cause of capacity loss.

Reducing drastically the changeover duration with SMED is like fixing the leak and recovering a part of the wasted capacity.

In case of a bottleneck this is very important because the recovered capacity is converted in additional sales without (or delaying) investment in scarce or highly expensive additional resource.


Bandeau_CH12

View Christian HOHMANN's profile on LinkedIn

Constraint vs. bottleneck

In Theory of Constraints lingo, there is a subtle difference between a constraint and a bottleneck.

A bottleneck (resource) is a resource with capacity less or equal to demand while a constraint is a limiting factor to organization’s performance, an obstacle to the organization achieving its goal.

A constraint can be called bottleneck but a bottleneck is not always a constraint.

Let’s take an example of a plant with a subassembly workshop gathering resources A, B and C. The whole process needs another resource D and final assembly consisting of resources E and F. The capacity of each resource is displayed under their letter.

The demand is 100 units per day.

According to definitions we’ll find two bottlenecks: resource B limited to 80 units/day and resource E limited to 60 units/day. Each of these two have a capacity less than daily demand.

Resource B is handicap to resource C and for the whole subassembly workshop, but has little influence on the throughput of the plant. Plant’s throughput is limited by resource E, which is both a bottleneck and the constraint. It is primarily E which hinders the plant to deliver 100 units/day.

Imagine The subassembly is led by a foreman named Hector. Hector’s realm encompasses The resources A,B and C. The final assembly process is his customer.

Hector has significant experience within this company and is well aware B is a bottleneck. Even so Hector may not know anything about Theory of Constraints, his common sense made him discover some good rules to better exploit the bottleneck resource.

For example, Hector organized breaks so that B is never left unmanned and not running, manages to minimize changeovers.

If he knew about Theory of Constraints, he would probably squeeze more throughput from B, for instance placing the quality check before the bottleneck in order to insure only OK parts will be processed by the very limited B. Actually quality check is after C, which sometimes causes B to waste valuable time processing parts that will not pass the quality check, something that could be foreseen before B.

As it is the case in many companies, top management set local productivity objectives and is expecting Hector’s subassembly to run with best productivity. Logically Hector will complain about B’s limitations and keep asking for another investment in a second B. Waiting for this investment, Hector manages to produce daily around 80 units, the best subassembly can do.

In Hector’s eyes B is the constraint, which is true if we consider subassembly alone.

Production manager Isadora has to take care about the whole plant and thus considers the whole process. She doesn’t know either about Theory of Constraints, but her analytical skills and common sense focused her attention onto E, the bottleneck and constraint to the whole process.

Having limited means, she’ll explain Hector that working to increase the capacity of B would have little interest as long as E is the limiting factor for the whole system (the plant). What Isodora did not notice is that as long the daily limit is 60 units/day, some costs could be saved in subassembly if its daily production would be aligned to the capacity of E, for instance overtime and excess inventory carry over costs. But she’s blinded by local productivity objectives set by top management.

Nevertheless, Isadora came close to self-discover the five focusing steps of Theory of Constraints:

  1. Identify the constraint (E)
  2. Exploit the constraint
  3. Subordinate everything to the constraint (e.g. subassembly)
  4. Elevate the constraint
  5. Prevent inertia to become the constraint

If Isadora succeeds to elevate the constraint E, chances are that the B will be the next constraint!


Related: Schragenheim’s concise history of constraints


Bandeau_CH12View Christian HOHMANN's profile on LinkedIn

What is a constraint?

In the Theory of Constraints (ToC) body of knowledge, a constraint is a limiting factor to a process or organization’s performance.

Every process or organization faces at least one constraint, otherwise it could achieve infinite performance.

Easier to understand in physical world

Theory of Constraints originated in manufacturing, while trying to improve production processes flow and resources scheduling. A constraint in a flow is usually called a bottleneck, a metaphor widely accepted and matching the reality everyone can see:

  • flow is slowed by the bottleneck
  • material accumulates in front of the bottleneck
  • subsequent resources in the process are starved from supplies as the bottleneck cannot deliver enough to saturate them

>Learn more about bottleneck resources

With the successes in physical production, the principles of ToC were also used in office and administration work, where files, documents or data flow through processes and face bottlenecks too.

As ToC continued to evolve, it became clear that a limiting factor to the organization’s performance is not always a bottleneck resource, but can be of different nature, like beliefs, policies, decisions, etc.

A new term had to describe the intangible equivalent of the bottleneck. This is where “constraint” appears.

Rules and methods that helped to manage physical bottlenecks were not suitable for broader constraints, so the Thinking Processes were invented to cope with constraints and solve problems.

Thinking Processes (TP) are as well tools (mainly descriptive diagrams and trees) as a structured and logical way to analyze problems and design solutions.

I usually describe Thinking Processes as a subset of Theory of Constraints, even so they tend to represent more and more ToC compared to initial bottleneck management rules, methods and techniques. For me ToC is the whole, TP came later and are a part of ToC, thus a subset.

Bandeau_CH12If you liked this post, share it!

View Christian HOHMANN's profile on LinkedIn

What is a bottleneck resource?

As the name itself suggests, a bottleneck resource is an obstacle to smooth flow in a process.

Consider this process made of five resources R1 to R5.

Resources can be machines, test equipment, ovens, paint shops, and so on. Each resource has its own processing capacity and in a process made of heterogeneous resources, chances are that every capacity is different.

In the diagram* the resource capacity is the aperture of its drain, not the storage capacity which is inventories’ or buffers’ capacity.

*this diagram’s credit goes to Philip Marris, founder and owner of Marris Consulting. A similar diagram is printed on the cover of Philip’s book, one I learned a lot with. Philip and I meet periodically for a chat in Paris, France.

Human resources can be bottlenecks too.

Consider the flow (blue liquid). The global performance (liquid throughput) of the process is limited by the least capacity within the process, which is obviously R3.

The bottleneck betrays itself with huge accumulation in front of it (raw material, parts, crates, orders, files…) and low throughput letting the next resources in the process waiting most of the time.

R4 and R5 could let much more flow through them but they keep being starved by the limited output of R3. R1 and R2 also have bigger capacities than R3 and there is no choice than to store their output in front of R3, or stop R1 and R2 until R3 caught up.

A bottleneck resource is a real bottleneck when its capacity is, in average, lower or equal to customer’s demand. A true bottleneck runs 24 hours 7 days a week and still cannot supply what is required. Conversely a non-bottleneck has excess capacity in regard of demand.

A bottleneck is usually very expensive and/or difficult to get. If this is not the case, the solution is obvious: buy additional capacity!

As a true bottleneck cannot be duplicated that easily, its capacity has to be used very wisely. As the bottleneck resource’s capacity constrains the whole process, this resource is very precious and none of its scarce capacity must be wasted.

The Theory of Constraints (ToC) proposes rules to manage such peculiar resources.

These rules can be found here:

>Read also Bottleneck explained with water pipes

——————————————

Bandeau_CH12