the lean opportunity
DESCRIPTION
Understanding the potential weaknesses of kanban and how APS can overcome these weaknesses to support your lean initiatives.TRANSCRIPT
The Future of Lean and APS
By Mike Liddell
Lean Scheduling International
The Lean Opportunity
Lean Scheduling International 2
Today’s Agenda
Why Lean Is So Important?
Why all this creates a massive opportunity?
What is Demand Driven Lean?
Why Lean Fails?
Lean Scheduling International 3
Lean Manufacturing
Lean manufacturing is a strategy for improving the manufacturing process by identifying and eliminating wasteful steps.
What is Lean?
Lean Scheduling International 4
Traditional Manufacturing
Work Centers
Batch & Queue
MPS
MRP Push
Lean Manufacturing
Cells & Lines
Continuous Flow
Heijunka
Kanban Pull
What’s the Difference?
Lean Scheduling International 5
Benefits Reduced Inventories
Lean Scheduling International 6
Benefits Increased Throughput
Lean Scheduling International 7
Benefits Reduced Lead Times
Results improved as Processes Improved
Batch & Queue Weeks
LeanHours
------------------------------------------------------Lead Times----------------------------------------------------------
It is very helpful to look back in time and understand how and why Lean evolved
Understanding Lean
MRP/MRPII and ERP
APICS spread the message that MRPII/ERP could do anything and everything. All you needed was:
Enough training! Enough discipline!
Mid 1980’s
MRPII
MRP/MRPII Problems
INVENTORIESFOR MOST MANUFACTURERS ALL WAS NOT WELL!!!
ON-TIME DELIVERIES
The Evolution of Lean - JIT
Just-in-Time Production (JIT) was the result of work done at Toyota:• Sakichi Toyoda • Kiichiro Toyoda• Taiichi Ohno
Their thinking was heavily influenced by:• W. Edwards Deming• Henry Ford.
Mid 1980’s
The Evolution of Lean - JIT
JIT with Kanban seemed like the perfect answer to the perceived limitations of MRPII:• It was simple• It was visual• It was not dependent on technology• It was quickly adopted by big companies like GE, HP
& Emerson
The Evolution of Lean
The Evolution of Lean - TPS
Early 1990’s
JIT Evolves into TPS
The Evolution of Lean - TPS
The main objectives of TPS were to eliminate: • overburden (muri)
• inconsistency (mura)
• waste (muda)
“ If you do not improve the process how can you expect the results to change” Taiichi Ohno
The evolution of Lean
Lean Transformation
Industrial Engineers Take Control:• “Lean out” the shop floor layout and production
processes• Become Lean experts (Black Belts)• Banish the use of MRPII/ERP systems on the shop
floor.
A Power shift away from IT
The Lean Plunge
Many companies were not able to sustain their Lean benefits:
• Only 19% of companies were able to successfully implement Lean (Bain & Co. Study)
• Generally impact on the bottom line was disappointing• There were massive problems with variable demand
Real World Consequences of Lean
• There was a Problem with variable demand->Shortages
-> Panic (Decision makers had no Visibility)
-> Schedulers Return to Excel & ERP
-> Returned to Manual Expediting
Conclusion - Like ERP, Lean was not able to manage Change/Volatility
Lean Scheduling International 20
But Who is the Weakest Link?
The Unexpected Answer is:
Manual Heijunka and Kanban
Lean Scheduling International 21
What is Kanban?
Kanban is also a scheduling system that tells you: what to produce when to produce it how much to produce
Kanban is a pull system that triggers replenishment of material based on buffer depletion.
Lean Scheduling International 22
What is Heijunka
Heijunka blends Customer Kanbans and Stocking Kanbans to level production.
A Heijunka box uses Customer Kanbans to visually smooth production.
Lean Scheduling International 23
Kanban’s Dirty Little Secret
The number of Kanban cards is based on yearly historical demand data
Lean Scheduling International 24
Heijunka’s Dirty Little Secret
There must be enough capacity to catch up if they fall behind
Lean Scheduling International 25
KanbanBecause Kanban sizes are not dynamic [Kanban has no inherent ability to self correct]… Kanban is NOT actually tied to current demand patterns!
The Conclusion
Lean Scheduling International 26
In order for Kanban to work effectively Kanban sizes must be just right:
• Not too small
• Not too big
The Goldilocks Syndrome
Lean Scheduling International 27
Scenario 1
What happens when Kanban’s are too small?
Lean Scheduling International 28
Scenario 1 – Manufactured Item
Lean Scheduling International 29
Scenario 1 – Manufactured Item
Results:• Slow to see demand• Manually create
additional Card• No way of prioritizing
Cell1• Stock Out & Late
Delivery
Lean Scheduling International 30
Scenario 2
What happens when Kanban’s are too big?
Lean Scheduling International 31
Scenario 2 – Manufactured Item
Lean Scheduling International 32
Scenario 2 – Manufactured Item
Lean Scheduling International 33
Scenario 2 – Manufactured Item
Results:• Too much inventory• No foreseeable demand• Unnecessary
consumption of Cell1 capacity
Lean Scheduling International
The 8 Limitations of Kanban
Unfortunately Kanban sizes are only a small part of the problem!!!
Page 34
Lean Scheduling International
The 6 Limitations of Kanban & Heijunka
1. Not Connected to Current Demand Patterns (Kanban Sizes)
2. Too Manual Too Slow To React to Change Too Time Consuming (resizing, expediting, lost cards) Too Local (Decision makers have no visibility)
3. Unable to Accurately Prioritize Upstream Work
4. Unable to Intelligently Sequence Upstream Work
5. One way Communication – No Feedback Loop
6. No “What-if” Functionality
Page 35
Lean Scheduling International 36
Broken Connection
The Evolution of APS
Let’s look at the evolution of APS over the same timeframe
The Evolution of APS
Another group was taking a different approach to addressing the fundamental planning problems built into MRP/MRPII
– Infinite Capacity– Time Buckets– Backward Scheduling– Average queue times and fixed setup times
Late 1980’s
The Evolution of APS
• Early adaptors were influenced by The Goal and TOC• Early scheduling software was called FCS software• FCS software recognized that machines had a finite
capacity.
The evolution of APS
The evolution of APS
Although FCS was an improvement it was usually stand alone and limited in its ability to model other real world constraints.
– Secondary Constraints– Materials– Complex Calendars
The Evolution of APS
• FCS becomes APS • APS solutions (like Preactor) provide a complete tool set
for modeling real world constraints• Additional functionality includes:
– Powerful Sequencing Engines– Easy integration with ERP & MES– Synchronizes Multiple Constraints (machines, materials, tools &
operators)– Able to Build unique solutions with Customized Rules
Mid 1990’s
The evolution of APS
APS Results
The ability to accurately schedule thousands of orders in seconds had a massive impact on manufacturers who were struggling to manage CHANGE.• Improved Efficiencies• Improve On-Time deliveries• Reduced Cycle Times• Improved Customer Service and Bottom Line
The Future
The limitation of Lean is that it wasn’t connected to current demand
The limitation of APS is that it didn’t necessarily improve the process
The Future
MRP/MRPIIERP
TOC FCS APS
JITKanban
TPS, Lean, FA, VMSix Sigma, Heijunka
1980's 1990's 2000's 2010's
Demand DrivenLean
Lean Scheduling International 47
Demand Driven Lean
APS
APS connects Static Lean to Customer Demand .
Demand Driven Opportunity
Use APS to create innovative solutions that Deliver Demand Driven Lean Solutions:• Automate Heijunka• Dynamically Manage Kanban Buffers• Communicate Between Schedule & Shop Floor • Provide Visibility and What-If Functionality for Decision
Makers• Prioritize, Sequence & Synchronize Upstream Cells
Use Static Lean To Improve the Process
Lean Scheduling International 49
Stay Tuned Next Year
Thank you!!!