Welcome
Upcoming SlideShare
Loading in...5
×

Like this? Share it with your network

Share
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
398
On Slideshare
398
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
6
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide
  • If you have already spoke to these cells in explaining the circle chart, just skip past them and tell your audience that you spoke to this on the previous chart and this is for their reference.
  • This cell depicts a pictorial view of the process to achieve a Lean Enterprise. Note that the process repeats itself - Lean is a never ending process Identify value - Ask: Is this something for which the customer would be willing to pay? or Does the activity change the form, fit, or function of the product or service? Value stream - Determine the set of all actions required to bring a product/service into the hands of the customer -- order to delivery, cradle to grave, design concept to launcht. Actions fall into 3 categories. Value-activity The activity does provide value to the customer Non-value added activity that cannot be avoided due to uncontrollable constraints Non-value added activity that can be eliminated (Studies have shown) Production typically has about 5-10% of total processing time that adds value Business Processes typically have about 1 to 0.5% value added time Flow - is the progressive achievement of tasks along the value stream with minimal queues, no stoppages, scrap, or backflows Pull - No one upstream should produce a product or service until the downstream customer asks for it. Material or information in only presented when needed and requested Perfection - Strive for perfection, not just to get ahead of your current competition.
  • This cell depicts the 7 types of waste as defined by Taichi Ohno of Toyota along with techniques to eliminate waste. Examples: Waiting: Late delivery of info or product; product or information sitting in a queue waiting for the next step Unnecessary motion: Data sent to wrong person, redundant activities Processing: Too many design changes, Excessive custom formatting (AOP), Unnecessary serial production Inventory: Preparing/receiving reports that are not needed, Stock-piling of parts or product; building ahead of customer demands Moving items: Just because you are busy getting or moving something doesn’t mean that you are performing value-added work. Making too much: unnecessary email traffic;WIP build-up; reports that are no longer useful Fixing defects: The farther along in a process that defects are found, the more expensive it is to fix them. Business processes also have a cost of poor quality, though it is rarely measured.
  • Again, some examples of poor leveling of work to Takt Time. The bottom example, tries to depict a situation in which one out of the four original workers (25%) could be removed entirely if they can eliminate 22 sec of non-value added activity. When leveling a work cell in the “real” world (since it is very difficult to get stations perfectly balanced), it is a good idea to try and set it up so that you have a “downward sloping curve”; ie worker A’s cycle time may be 100 sec, worker B’s cycle time may be 98 sec, worker C’s cycle time may be 97 sec, and so on. This gives the cell a natural pull system which is more easily sustained.
  • Compare and contrast a stream with its eddies and pools where water may sit and stagnate or run in the opposite direction of the current vs. a water pipe which has fast flowing water and no chance for stagnation. Examples: business process - Software Control Library removed 10 queues to help increase flow (should have gotten into leveling) manufacturing - Manchester post-coat (prior to workshop) didn’t know when you’d get a product thru unless it was hand carried (expedited). Set up with leveled work stations and standard WIP to reduce cycle time and establish a predictable flow of 17 hrs.
  • MRP is a push system. The required amount is released based on a schedule not according to need A pull system replenishes need when required by the next operation
  • Top scenario is a push system: feast and famine for the operators, don’t know when you can get anything out, etc. Bottom scenario is the pull system
  • We need to provide the employees with the most efficient way to perform the task that meets our safety requirements in areas such as ergonomics As turnover occurs the process is documented so there is no loss in process technique, quality efficiency etc. The documented process yields certain measurable performance factors that are a baseline for future reference In providing the most efficient way to produce the product in terms of quality, the probability of error is reduced which increases the yield to the customer
  • Design forms and databases with error proofing techniques in mind Examples: 1. Expense Reports designed a new form for handing in expense reports. All reports must be submitted in a special green envelop (eliminates sorting). This envelop also has a checklist on the front that must be filled out before the expense report will be accepted. (Eliminated almost all the errors for missing data that the checklist asks about) 2. Environmental Effects Engineering implemented a Design Capture Worksheet that requires all bidding activity to define a better scope of the testing required, and reminds design engineers of the often forgotten information required when performing qualification testing. (Eliminating unnecessary delays in bidding and makes sure that all the details are captured in the bid)
  • The earlier you catch a mistake the less costly it is. Ask the audience how they treat errors in the products they buy. Fix the errors at the source. Better yet find ways to error proof.
  • The idea behind this cell is to instigate a second set of eyes for detecting errors, but not relying on end of the line inspection. Each step in the process has the responsibility to check the most common problems from the process step in front of it. Once this check is complete, the process completes their part of the task.

Transcript

  • 1. Welcome Supply Management and Lean Manufacturing
  • 2. Supply Chain Management ref: “Designing and Managing the Supply Chain”, Simchi-Levi et al., 2000. Chapters 1, 4 and 8.
  • 3. Supply Chain Management
    • The term supply chain was first introduced by Houlihan (1984), and has since been defined in different ways:
    • "A supply chain is a system through which organizations deliver their products and services to their customers." (Poirier and Reiter, 1996).
    • "A supply chain is an integrated process wherein raw materials are manufactured into final products, then delivered to customers (via distribution, retail, or both)." (Benita, 1999).
  • 4. A Simple Supply Chain Model
  • 5. Complexity of Supply Chains
    • Likely to be complex due to:
    • The large mesh of inter-linked suppliers, manufacturers and distributors.
    • The fact that each participant (supplier, manufacturer and distributor) may be a member of a large number of other supply chains.
    • The dynamic nature of the supply chain.
  • 6. Supply Chains
    • It takes a cereal carton more than three months to move from the factory to supermarkets (Simchi-Levi et al. 2000).
    • In 1997 supply chain issues in the United States consumed 10 percent of the U.S. Gross National Product (GNP)
    • Lead time reduction of increasing importance:
      • reduced inventory levels
      • reduced obsolescence
      • improved response to customers
  • 7. Supply Chain Example Johnson Controls Chrysler Ford General Motors Technotrim Milliken & Company Lear Favesa Soft Trim Suppliers Dudek & Bock Spring Rockford Spring R. R. Spring Hardware Suppliers Canadian Fab Douglas & Lomason Collins & Aikman Textileather Specialty Screw Excel/Atwood
  • 8. Supply Chains Chrysler 30% Chrysler 70% Supply Chain Cost in the Average New Vehicle? Trend
  • 9. Lean Manufacturing
  • 10. Lean Guiding Principles PERFECTION PULL FLOW VALUE STREAM VALUE
  • 11. Types of Waste Waiting - Time spent waiting on items required to complete task (i.e., Information, material, supplies, etc.) Unnecessary Motion - Any motion that does not add value to product or service. Processing - Effort and time spent processing information or material that is not adding value Inventory - Material or information that is waiting for processing Moving items - Transporting information or material by mail, cart, conveyor, or foot travel Making too much -Producing more information or product than the ultimate customer requires Fixing defects - Time spent repairing or reworking material or information
  • 12. Lean Toolkit
    • Workload Leveling
    • Flow Processes
    • Pull Systems
    • Standard Work
    • Visual Controls
    • Error Proofing
    Lean Tools
  • 13.
    • Enables the process to run as efficiently as possible, using the minimum number of people
    • Maximizes the utilization of each person
    • Makes a process more predictable
    Workload Leveling Lean Toolkit
  • 14.
    • Workload Leveling
    TT Worker A B C D Won’t Make Plan Worker A B C D Lots Of Free Time TT TT Worker A B C D Poor Balance Worker A B C D TT 100 100 Only 22 Sec. More To Save 25% On Labor Lean Toolkit
  • 15.
    • A basic principle of Lean is to make value flow as quickly as possible through the Value Stream
      • Must have quick decisions, made at the lowest possible level
        • Eliminate approvals
      • Must have information available to the “new” decision makers
    Establishing Flow and Pull Lean Toolkit
  • 16.
    • Flow Processes
    • All operations within a process should be rearranged in a sequential fashion with minimal distance between operations
      • Isolated functional activities should be co-located as much as possible with the rest of the process activities
      • Office layouts should be process/activity oriented versus functional
      • Isolated machines should be moved and incorporated into the line as much as possible
    • Flow assumes that material/products will not be stagnant at any point and time from receiving to the shipping of finished products
    • The intent of continuous flow is to increase the velocity of and make the cycle time predictable
    Lean Toolkit
  • 17.
    • Pull Systems
    • A Pull System is a way to manage the Lean Enterprise System
    • Pull System vs. Push System
      • A Pull System occurs when the previous process produces only as many products that are consumed by the following process
      • A Push System produces just as many units as it can and sends them to the next process whether the next process needs them or not
    • Pull Systems minimize waste
    • Strive for Single-Piece Flow, to minimize wait times & queues
    Lean Toolkit
  • 18.
    • Pull Vs. Push
    PROCESS C PROCESS B PROCESS A PROCESS C PROCESS B PROCESS A Lean Toolkit
  • 19. Pull Vs. Push in Product Development Verification Design/ Code Requirements Definition Verification Design/ Code Requirements Definition This engineer could be helping with requirements definition This pile of system requirements goes through the process like a rat through a snake.
  • 20.
    • Represents the current best, easiest, and safest way to do a job
      • Documented processes constantly change as employees make continuous improvements
    • Preserves know-how and expertise
    • Provides a way to measure performance
    • Provides a means for preventing recurrence of errors and minimizing variability
    • Improves schedule compliance, customer satisfaction, productivity, and cost competitiveness
    Standard Work Lean Toolkit
  • 21.
    • Takt Time (Available Work Time / Daily Demand)
    • Work Sequence (Sequence of Tasks performed)
    • Standard WIP (The minimum number of parts in a process that are required for work to progress)
    • Note: To apply these in the office environment, the process must be:
        • Observable
        • Repetitive
    Elements of Standard Work Lean Toolkit
  • 22.
    • Visual Controls are means, devices, or mechanisms that help us manage our processes in order to:
    • Use Visual Controls to:
      • Make the problems, abnormalities, or deviation from standards visible to everyone so that corrective action can be taken
      • Display the process status in an easy to see format
      • Provide instruction
      • Convey information
      • Provide immediate feedback to the team
    Visual Control & Visual Management Lean Toolkit
  • 23.
    • “ How we are doing” at a glance
      • What we are working on
      • The level of performance
    • Providing information immediately to people working in the area
    • Promotes communication
    Visual Control - The Concept Visual Management - The Concept “ The ability to manage a system or process by metrics that are visual to the workplace” Lean Toolkit
  • 24.
    • Error Proofing
    • Error Proofing is a way to prevent an error from being created or potentially passed to the next operation of a process
      • Allows people to concentrate on their work without paying unnecessary attention to preventing mistakes
    • Error proofing techniques include:
      • Use of different colored paper for different processes
      • Colored files/binders
      • Checklists
      • Log sheets
      • Screen prompts
    Lean Toolkit
  • 25.
    • Early Detection of Errors Lowers Costs
    • Defects Own Next End of Final End user’s
    • Found at: Process Process Line Inspection Hand
    • Cost to $1 $10 $100 $1000 $10000
    • the Company:
    • Impact to Very Minor Rework/ Significant Warranty
    • the Company: Minor Delay Reschedule Rework Reputation
    • Delay Lost Market
    Lean Toolkit
  • 26.
    • Successive Checks
    Process B Check A Check B Process C Process A SW Engineer A SW Engineer B SW Engineer C Process A Problems 1. 2. 3. Process B Problems 1. 2. Lean Toolkit
  • 27. Review Participation Successive Checks in Product Development Software Design Peer Review Peer Review Code Requirements Definition Systems Engineer Software Engineer Software Team Member Engineers work with producers and customers of their processes in order to ensure a quality result. Systems Participation Verification Engineer … Prevent problems at end of development cycle. Also work with other experts and key end consumers to ensure that critical tasks can be accomplished. Verification, for example. Lean Toolkit
  • 28. Successful Lean Tool Implementations
    • Travel Expense Reporting
      • Single-piece flow, process standardization, error proofing
      • 50% reduction in cycle time
      • 48% productivity improvement
      • 60% reduction in travel distance
    Lean Toolkit