With the success of Lean Manufacturing, it is common these days to hear people say we are Leaning out the process. But do people really understand what Leaning out means.
I have come to realize that the phrase Leaning out means different things to different people. Here is the list of some of them...
- optimizing material movement
- removing obstacles in the process
- re-arranging the area
- re-arranging people
- removing clutter
- doing more with less
Although all of the above are good interpretation of the term "leaning out". I think most people undermine the true meaning of the term which is to remove all non value added activities in a process to improve flow. But why is flow important? And above all what should flow?
I think the term "leaning out a process" is used rather loosely at all levels of the enterprise without understanding the true meaning.
Have you heard the term "Leaning out"? What thoughts come to your mind when you hear this term? Drop us a line at info@sybeq.com
Showing posts with label lean system. Show all posts
Showing posts with label lean system. Show all posts
Friday, December 30, 2011
Thursday, December 30, 2010
How to level the load in production?
The concept of load leveling requires careful analysis of production volumes and schedules so that production makes same quantity of parts both by volume and product mix everyday.
The steps for leveling the load include:
1. Take the total volume of customer orders in a period by product type.
2. Determine the quantity of parts by product so that the same volume needs to be produced by product type.
3. Analyze the time required to make a part by product type and time required for changeover.
4. Plan a stable production schedule so that plant floor doesn't have to deal with fluctuations.
The goal of leveling the load is planning to work at a consistent pace in production making a mix of parts so that the equipment and people are working at the same pace without stopping or being stressed.
Because of this production is not rushed for deliveries giving production folks enough time to implement standard work and avoid errors.
The key to find the mixed model that works for your process/line. Once the mixed model is determined, production has to make the same quantity, mix of products and repeat it everyday.
Load leveling presents many challenges:
- The concept of load leveling is counter intuitive to batch manufacturing where the focus is to run a batch of same product as long as you can and run it efficiently. Load leveling on the other hand says it is okay to changeover from one product to another. In fact load leveling encourages multiple changeovers in a day or a shift.
- Due to the mixed model approach, there may be some amount of finished goods inventory when implementing load leveling. This may make some Lean experts unhappy as they view inventory as waste.
Ultimately it is important to look at the risk of carrying some inventory to satisfy customer demand or make the customer wait for the product they need.
- Load leveling won't be successful without having quick changeovers i.e. reducing changeover time.
Taiichi Ohno explained this with the story of the race between the tortoise and the rabbit. The slow and steady tortoise wins the race. Ohno said it is desirable to be slower but consistent tortoise as it causes less waste than the speedy rabbit who races then stops to rest.
The steps for leveling the load include:
1. Take the total volume of customer orders in a period by product type.
2. Determine the quantity of parts by product so that the same volume needs to be produced by product type.
3. Analyze the time required to make a part by product type and time required for changeover.
4. Plan a stable production schedule so that plant floor doesn't have to deal with fluctuations.
The goal of leveling the load is planning to work at a consistent pace in production making a mix of parts so that the equipment and people are working at the same pace without stopping or being stressed.
Because of this production is not rushed for deliveries giving production folks enough time to implement standard work and avoid errors.
The key to find the mixed model that works for your process/line. Once the mixed model is determined, production has to make the same quantity, mix of products and repeat it everyday.
Load leveling presents many challenges:
- The concept of load leveling is counter intuitive to batch manufacturing where the focus is to run a batch of same product as long as you can and run it efficiently. Load leveling on the other hand says it is okay to changeover from one product to another. In fact load leveling encourages multiple changeovers in a day or a shift.
- Due to the mixed model approach, there may be some amount of finished goods inventory when implementing load leveling. This may make some Lean experts unhappy as they view inventory as waste.
Ultimately it is important to look at the risk of carrying some inventory to satisfy customer demand or make the customer wait for the product they need.
- Load leveling won't be successful without having quick changeovers i.e. reducing changeover time.
Taiichi Ohno explained this with the story of the race between the tortoise and the rabbit. The slow and steady tortoise wins the race. Ohno said it is desirable to be slower but consistent tortoise as it causes less waste than the speedy rabbit who races then stops to rest.
Thursday, October 28, 2010
Using a Pull system not so Lean
One of the key lean tools is implementing kanban which uses the pull system. Lean is all about moving away from the traditional push system toward the pull system. In a lean enterprise, it is always recommended not to push parts or information to the next process step. The focus is to pull parts when the downstream process step requests for parts/information.
Some Lean practitioners rave about the pull systems they have implemented. However experienced Lean practitioners don't give much credit to pull systems. This is because...
1. Lean is all about removing waste.
2. When waste cannot be removed, there is inventory in process or at the final stage. This inventory needs to be managed in the best way possible. In such situations, a pull system is used.
Implementing the pull system is an indication that waste is still present. This is a good starting point for reducing waste but it is definitely the final goal. The Lean implementation team should not stop at implementing the pull system. In fact the team should continuously work toward removing waste altogether and not use the pull system.
As rightly said by Jeffery Liker in the book Toyota Way "Flow where you can, pull where you must". The ultimate goal to make value flow as smoothly as possible.
Some Lean practitioners rave about the pull systems they have implemented. However experienced Lean practitioners don't give much credit to pull systems. This is because...
1. Lean is all about removing waste.
2. When waste cannot be removed, there is inventory in process or at the final stage. This inventory needs to be managed in the best way possible. In such situations, a pull system is used.
Implementing the pull system is an indication that waste is still present. This is a good starting point for reducing waste but it is definitely the final goal. The Lean implementation team should not stop at implementing the pull system. In fact the team should continuously work toward removing waste altogether and not use the pull system.
As rightly said by Jeffery Liker in the book Toyota Way "Flow where you can, pull where you must". The ultimate goal to make value flow as smoothly as possible.
Tuesday, September 28, 2010
VSM during early stages of Lean implementation
How many Value Stream Maps should be created at the start of Lean implementation?
We typically hear this question from...
1. Users who have recently learned the Value Stream Mapping tool
2. Organizations who are new to Lean implementation, just starting out on their lean journey
Start the Lean implementation with a few (say 2 to 3) value stream maps for processes that have the most non value adding activities (waste).
Why just 2 to 3?
Because of several reasons..
1. Creating Value Streams is a time consuming activity.
- Teams creating these maps have to walk the value stream and capture information
about material and information flows.
- Teams have to then create the current state map, identify waste and the Lean
tools they plan to use, create the future state map.
2. After creating the maps in the meeting room, now teams have to actually go and implement the Lean tools in the value stream. This is the most challenging part as this may take anywhere from a few days to few weeks. There are many aspects of the implementation like corporate culture, motivation level of people, management involvement, complexity of the process that could play a role.
3. Getting rid of all the waste in the process may require several cycles of going from the current to the future state. After all Lean is a journey of continuously removing waste.
How many value streams have you worked with? How many value streams did you start with when your organization was in early phases of Lean implementation?
Send us your questions or comments at info@Sybeq.com
We typically hear this question from...
1. Users who have recently learned the Value Stream Mapping tool
2. Organizations who are new to Lean implementation, just starting out on their lean journey
Start the Lean implementation with a few (say 2 to 3) value stream maps for processes that have the most non value adding activities (waste).
Why just 2 to 3?
Because of several reasons..
1. Creating Value Streams is a time consuming activity.
- Teams creating these maps have to walk the value stream and capture information
about material and information flows.
- Teams have to then create the current state map, identify waste and the Lean
tools they plan to use, create the future state map.
2. After creating the maps in the meeting room, now teams have to actually go and implement the Lean tools in the value stream. This is the most challenging part as this may take anywhere from a few days to few weeks. There are many aspects of the implementation like corporate culture, motivation level of people, management involvement, complexity of the process that could play a role.
3. Getting rid of all the waste in the process may require several cycles of going from the current to the future state. After all Lean is a journey of continuously removing waste.
How many value streams have you worked with? How many value streams did you start with when your organization was in early phases of Lean implementation?
Send us your questions or comments at info@Sybeq.com
Thursday, September 23, 2010
Where to begin mapping Value Streams?
In the last post we talked about the different questions lean pratitioners have about implementing Value Stream Mapping.
The question of where to begin mapping value streams actually requires understanding the definition of value stream.
Lean practitioners need to have the ability to clearly identify and define a value stream.
A Value Stream is a stream of activities required to satify a customer need. The value stream starts with the customer who may be external or internal and ends where it is has a logical end. What this means is...
1. Start with the customer. First, define who is the customer and what do they need.
2. With this defined, start Walking the value stream backwards one step at a time.
3. Stop wherever it seems to be a logical stopping point.
While doing the above steps do not restrict the value stream by functions or departments. This is because a value stream may cross multiple departments. The ultimate goal of value Stream Mapping is to map how the stream works starting with the customer first and ends where it is a logical stopping point.
Do you face the challenge of where to begin mapping value streams? Tell us about your VSM implementation. Email: info@sybeq.com
The question of where to begin mapping value streams actually requires understanding the definition of value stream.
Lean practitioners need to have the ability to clearly identify and define a value stream.
A Value Stream is a stream of activities required to satify a customer need. The value stream starts with the customer who may be external or internal and ends where it is has a logical end. What this means is...
1. Start with the customer. First, define who is the customer and what do they need.
2. With this defined, start Walking the value stream backwards one step at a time.
3. Stop wherever it seems to be a logical stopping point.
While doing the above steps do not restrict the value stream by functions or departments. This is because a value stream may cross multiple departments. The ultimate goal of value Stream Mapping is to map how the stream works starting with the customer first and ends where it is a logical stopping point.
Do you face the challenge of where to begin mapping value streams? Tell us about your VSM implementation. Email: info@sybeq.com
Monday, August 30, 2010
How to Map Value Streams in the real world?
Over the years we have heard many questions about Value Stream Mapping from people who are new to VSM as well those who have used VSM before.
Questions like these are not uncommon...
Where to begin mapping the Value Stream?
How many Value Stream Maps should be created to begin Lean implementation?
What about overlapping Value Streams?
How to handle parallel Value Streams?
How much information should be captured on the Value Stream Maps?
We will try to address the above questions in the next few posts.
In this post we would like to address the reason for the above questions. The primary reason for VSM questions is the way most people think. In Lean thinking, Value is defined by the customer and it flows across multiple functions. The focus of VSM is to capture the flow of material and information across the functions by actually walking the stream. Additional information like process and wait time along with information about the person working at the process step is also captured on the Value Stream Map. Overall lead time can also be calculated and displayed on the map.
Most of the confusion around VSM is because people think about process maps or about the function/department they work in.
This is because most organizations still think about department efficiency or process steps. Value Stream Mapping crosses multiple functions in the organization.
The steps to map Value Streams is explained in the article How to Map Value Streams?on our website.
Questions like these are not uncommon...
Where to begin mapping the Value Stream?
How many Value Stream Maps should be created to begin Lean implementation?
What about overlapping Value Streams?
How to handle parallel Value Streams?
How much information should be captured on the Value Stream Maps?
We will try to address the above questions in the next few posts.
In this post we would like to address the reason for the above questions. The primary reason for VSM questions is the way most people think. In Lean thinking, Value is defined by the customer and it flows across multiple functions. The focus of VSM is to capture the flow of material and information across the functions by actually walking the stream. Additional information like process and wait time along with information about the person working at the process step is also captured on the Value Stream Map. Overall lead time can also be calculated and displayed on the map.
Most of the confusion around VSM is because people think about process maps or about the function/department they work in.
This is because most organizations still think about department efficiency or process steps. Value Stream Mapping crosses multiple functions in the organization.
The steps to map Value Streams is explained in the article How to Map Value Streams?on our website.
Saturday, August 21, 2010
Becoming lean without reducing mura
In the last post we covered the importance of balancing muri and mura to remove muda (waste) in the process. But what do you do when mura or unevenness in production cannot be controlled?
We often hear manufacturers say that production volumes change everyday sometimes every hour as the customer demand is constantly changing. In today's world the business has to do what the customer wants or be prepared to face consequences of lost sales, lost customer etc.
Most customers today demand what they need when they need it. Businesses that can cater to this need survive.
So how does the business remain lean inspite of these flucutations in production volume?
The business can be ready for such fluctuations by accounting for it beforehand. The manufacturer can plan for this by taking 3 simple steps...
1. Carry a small finished goods inventory to satisfy the customer demand in case the demand suddenly rises. The question becomes how much? Carry enough inventory to allow production to run smoothly without stressing the plant people and equipment. Carrying too much inventory is a form of waste and not recommended in a lean system. Too much inventory will hide problems and tie up cash in form of product cost, floor space occupied to store the product etc.
2. Plan for producing quantities that do not push the plant over limits. This will allow the plant to pace production so that the total cycle time is met. Process steps can be run below takt time to meet customer demand.
3. Leadership should think ahead with the foresightedness of planning for leveling the production load so that customer demand is met.
Do you experience irregularities in production? How do you manage such production irregularities and being lean at the same time?
Write to us at info@sybeq.com about your experiences and challenges in your lean journey.
We often hear manufacturers say that production volumes change everyday sometimes every hour as the customer demand is constantly changing. In today's world the business has to do what the customer wants or be prepared to face consequences of lost sales, lost customer etc.
Most customers today demand what they need when they need it. Businesses that can cater to this need survive.
So how does the business remain lean inspite of these flucutations in production volume?
The business can be ready for such fluctuations by accounting for it beforehand. The manufacturer can plan for this by taking 3 simple steps...
1. Carry a small finished goods inventory to satisfy the customer demand in case the demand suddenly rises. The question becomes how much? Carry enough inventory to allow production to run smoothly without stressing the plant people and equipment. Carrying too much inventory is a form of waste and not recommended in a lean system. Too much inventory will hide problems and tie up cash in form of product cost, floor space occupied to store the product etc.
2. Plan for producing quantities that do not push the plant over limits. This will allow the plant to pace production so that the total cycle time is met. Process steps can be run below takt time to meet customer demand.
3. Leadership should think ahead with the foresightedness of planning for leveling the production load so that customer demand is met.
Do you experience irregularities in production? How do you manage such production irregularities and being lean at the same time?
Write to us at info@sybeq.com about your experiences and challenges in your lean journey.
Subscribe to:
Posts (Atom)