5
Nov
2010
Goldratt’s Golden Nugget #12
Light blue 2, or: A way to exploit the protective capacity using orders (as opposed to using stock)
(MTA combined with MTO)
In MTA environments there is a need to hold protective capacity. The problem is that in order to use the protective capacity when needed, this capacity is on average idle. In the previous nugget (“light blue 1″, no. 11) we discussed a way to directly exploit the protective capacity; to use this idle capacity to satisfy more sales. The first light blue method is based on the use of protective capacity to produce to stock, which is then offered in segmented markets – dumping markets. The nugget ended with a warning not to use this method if the company cannot find suitable dumping markets. In cases where the company can’t find enough such markets, and consequently a part of the protective capacity is left unutilized, there is another possible method that can enable exploitation of the remaining free protective capacity. This method is based on processing clients’ orders by the protective capacity and therefore it is applicable only in mixed MTA+MTO environments.
Click here to continue reading.
|
||||
26
Jul
2010
Theory of Constraints Golden Nugget
#10 MTA + MTO Mixed environment
In many companies, some SKUs are consumed on a regular basis, whether by one or multiple clients, while other SKUs have a sporadic consumption pattern, either because the demand is rare, or because the SKU is customized for a particular order of the client. In these environments, regular consumption should be supplied immediately from stock (MTA), while sporadically consumed SKUs (as well as exceptionally big orders of regular SKUs1) should be made only to clients’ orders (MTO); in other words, they should operate as a partly MTA, partly MTO environment.
The mechanisms to control both the MTA and the MTO in a mixed environment are the same mechanisms used in an environment of pure MTA or pure MTO. The only difference is that when using load control for providing promised due-dates and for determining the time to release the material for MTO, we regard only the MTO production segment instead of taking into consideration the total capacity and load. More explicitly, the way to allocate the capacity in such mixed environments is as follows: first assign capacity for MTA based on the current coverage; then add 20% protective capacity (Note: The needed protective capacity is not 20% of the total capacity, but only 20% of the capacity required by MTA). The capacity remains is allocated for MTO.
Click here to continue reading.
|
||||
28
Apr
2010
Theory of Constraints Golden Nugget
#7 – Minimum batch progression
(MTO and MTA production)
There are times that a technical consideration at a certain work-center forces us to process a minimum batch which is bigger than the order (e.g. a mixer that requires a minimum of 20 liters). Then, of course, we have no choice but to work on more units than needed for the order. But that doesn’t mean we have to carry those extra units onwards through all the processing chain (after passing the work center responsible for the technical consideration), as is too often done… Click here to continue reading.
|
||||
12
Mar
2010
Theory of Constraints Golden Nugget
#6 – Fine tune of the priority system – an exception
(MTO; Production)
The effectiveness of the priority system stems from the fact that it is robust yet simple; only three priority colors, with a strict instruction not to try being super- accurate and pin point which among the same-colored orders should be processed first. That being said, there is one exception – a unique case where refinement of the priority system is very much needed.
The case we refer to relates to situations where there are product families with considerably different production buffers. In such a situation, a product with a relatively long production buffer might have, at some work-centers, touch time which is indeed negligible relative to its own production buffer (< 10%), but is significant in comparison to another, shorter production buffer (> 1/6). Figure 1 schematically demonstrates the described situation… Click here to continue reading.
|
||||
