Evaporating cloud
≈ 5 min read
Names in other languages
No names in other languages are held for this entry yet.
Article bodies are English and are not machine-translated. A name in another language is not a translation of the article.
The evaporating cloud is one of the six thinking processes in the theory of constraints (TOC). The evaporating cloud (EC) – also referred to in the literature as "the cloud", or as a "conflict resolution diagram" – is a logical diagram representing a problem that has no obvious satisfactory solution. The most commonly used of the TOC tools, the EC was designed to address conflict or dilemma situations (trade-off situations where there is no acceptable compromise) by diagramming the logic behind the conflict and methodically examining the assumptions behind the logic.
The evaporating cloud is one of the six thinking processes in the theory of constraints (TOC). The evaporating cloud (EC) – also referred to in the literature as "the cloud", or as a "conflict resolution diagram" – is a logical diagram representing a problem that has no obvious satisfactory solution. The most commonly used of the TOC tools, the EC was designed to address conflict or dilemma situations (trade-off situations where there is no acceptable compromise) by diagramming the logic behind the conflict and methodically examining the assumptions behind the logic.
Usage
Building a cloud
The EC has a set format with five boxes, labelled A, B, C, D and D’, where B and C both lead to the goal of A, D leads to B, and D’ leads to C, and D and D’ are in "conflict". The boxes represent two opposing wants that represent the conflict (D, D’), the needs that each want is trying to satisfy (B, C), and a common objective or goal (A) that both needs are trying to fulfil. The lines or arrows connecting the nodes represent the rationale or causal assumptions that are used to link the nodes. When communicating the cloud, the arrows should be read as "in order to" or "because" or "so that". For example: "In order to achieve A we require B because there is no way we can have A without B." Or: "There is no way we can have D and have D’ (read as "D-prime") at the same time." Clouds are "built" by filling in the appropriate boxes with statements about the situation. Both the wording of the statements and the sequence of filling the boxes can be important. Below is a guide to the recommended sequence and questions for building Day-to-day Conflict or Inner Dilemma clouds. Different types of problems have slightly different requirements when it comes to documenting and communicating the underlying conflict. Below is a summary of different types of problems, and the suggested sequence for building and communicating the cloud.
Applications
Goldratt has illustrated the use of the evaporating cloud technique in a discussion of the economic production quantity model. The prerequisite wants are to run large batches (D) and yet to run small batches (D′). These are clearly in conflict. The required need that D is trying to meet is to reduce setup cost (B), whereas the D’ prerequisite needs to reduce carrying cost per unit (C). Both requirements are aimed at the objective (A): to reduce cost per unit. Jelena Fedurko (2011) recommends checking the logic of the EC by reading the logical statements aloud, in the following sequence: In order to reduce cost per unit, we must reduce setup cost per unit. In order to reduce setup cost per unit we must run large batches. in order to reduce cost per unit, we must reduce carrying cost per unit. In order to reduce carrying cost per unit we must run small batches. Running large batches and running small batches are in direct conflict. Running large batches puts in danger the need to reduce carrying cost per unit. Running small batches puts in danger the need to reduce setup cost per unit. According to Fedurko, Reading aloud ... is needed because it explicitly employs the auditory channel as an additional mechanism to process and check the logic. Goldratt claims that each of the logical connections in the EC represent an (often hidden) assumption. One of the most basic fundamentals of logic is, that behind any logical connection there is an assumption. The assumptions behind the above connections can be surfaced by again reading the statements with a "because" clause added. For example, Goldratt surfaces the following assumptions behind the 2nd statement in the example EC: In order to reduce setup cost per unit we must run large batches, because setup cost is fixed and it cannot be reduced. the machine being set up is a bottleneck with no spare capacity. And again, with the 5th statement: Running large batches and running small batches are in direct conflict, because: large is the opposite of small. there is only one meaning to the word "batch". The second assumption is challenged by distinguishing between production batch size (between setups) and transfer batch size (between workstations), and so allowing different sized batches for different purposes.
Notes
References
Text derived from https://en.wikipedia.org/w/index.php?oldid=1346671759 under CC BY-SA 4.0; modifications have been made.