Presentation on theme: "Lean Manufacturing - Heijunka Leveling SAP Best Practices for Automotive Package (Japan) SAP Best Practices."— Presentation transcript:
Lean Manufacturing - Heijunka Leveling SAP Best Practices for Automotive Package (Japan) SAP Best Practices
Scenario Overview – 1 Purpose The scenario shows how existing tools and functions of the SAP ERP portfolio can be used to convert uneven customer pulls into an even and predictable manufacturing schedule (Heijunka leveling) to enable upstream Kanban supply with SAP Kanban tools according to lean Toyota Production System (TPS) principles, it focuses on a lean production control method within a repetitive manufacturing environment: using Kanban processing for lean replenishment. Benefits Heijunka technique levels uneven customer demands to even production schedule on final assembly line, subsequently, production process at a constant and predictable rate prevents waste caused by the fluctuations in performance. To adopt sequence schedule with setup time optimization instead of equally distribution dispatching, it gets more efficient to avoid muda (waste). Just in time delivery via Kanban pull fulfills lean planning and manufacturing principles. Purpose and Benefits:
Scenario Overview – 2 Enhancement Package 4 for SAP ERP 6.0 Supplier Client: Employee (Professional User) Warehouse Clerk Strategic Planner Production Planner Production Planner (AUTO) Production Supervisor (AUTO) Shop Floor Specialist (AUTO) Supplier Process: Inputting Uneven Planned Independent Requirement Supplier Process: Running MRP Supplier Process: Checking Planning Situation in planning table Supplier Process: Heijunka Leveling – Equally Distribution Dispatching Supplier Process: Heijunka Leveling –Setup time optimization Supplier Process: Monitoring and Rescheduling Heijunka Planning Supplier Process: Calling for Finished Products Using Kanban Pull Supplier Process: Monitoring and Executing Heijunka Scheduling Supplier Process: Receiving Finished Goods into Stock Company Roles Involved in Process Flows: SAP Applications Required: Key Process Flows Covered:
Scenario Overview – 3 Detailed Process Description: Lean Manufacturing - Heijunka Leveling Uneven customer demands for several different products are levelled by a production planner to create an even production schedule (Heijunka schedule) for a finished goods production line. The production worker executes according to this schedule and calls consumed components within an upstream Kanban process. The shipping associate fills the shipping warehouse via Kanban calls from the finished goods production line.
Process Flow Diagram Lean Manufacturing - Heijunka Leveling Supplier Client / Plant 1000 Uneven Planned Independent Requirement MRP Run Check Planning Situation in Repetitive Planning Table Heijunka Leveling – Sub-daily Scheduling Shipping Signal in KANBAN Board – Status Empty Check Assigned Planned Order in Heijunka Leveling Post Goods Receipt in KANBAN Board Heijunka Leveling –Setup Time Optimization
Finished Product, Material Type = FERT Semi-finished Product, material type = HALB Raw Material, material type = ROH A-80-1200_SUP Fan Unit All Types A-80-1100_SUP Coolant Unit Type A A-80-1200_SUP Fan Unit All Types A-80-2000_SUP Air Conditioning Type B A-80-2100_SUP Coolant Unit Type B A-80-1200_SUP Fan Unit All Types A-80-3000_SUP Air Conditioning Type C A-80-3100_SUP Coolant Unit Type C A-80-1200_SUP Fan Unit All Types A-80-4000_SUP Air Conditioning Type D A-80-4100_SUP Coolant Unit Type D Supplier Client / Plant 1000 A-80-1000_SUP Air Conditioning Type A Master Data Lean Manufacturing - Heijunka Leveling
Legend SymbolDescriptionUsage Comments Band: Identifies a user role, such as Accounts Payable Clerk or Sales Representative. This band can also identify an organization unit or group, rather than a specific role. The other process flow symbols in this table go into these rows. You have as many rows as required to cover all of the roles in the scenario. Role band contains tasks common to that role. External Events: Contains events that start or end the scenario, or influence the course of events in the scenario. Flow line (solid): Line indicates the normal sequence of steps and direction of flow in the scenario. Flow line (dashed): Line indicates flow to infrequently- used or conditional tasks in a scenario. Line can also lead to documents involved in the process flow. Connects two tasks in a scenario process or a non-step event Business Activity / Event: Identifies an action that either leads into or out of the scenario, or an outside Process that happens during the scenario Does not correspond to a task step in the document Unit Process: Identifies a task that is covered in a step-by-step manner in the scenario Corresponds to a task step in the document Process Reference: If the scenario references another scenario in total, put the scenario number and name here. Corresponds to a task step in the document Sub-Process Reference: If the scenario references another scenario in part, put the scenario number, name, and the step numbers from that scenario here Corresponds to a task step in the document Process Decision: Identifies a decision / branching point, signifying a choice to be made by the end user. Lines represent different choices emerging from different parts of the diamond. Does not usually correspond to a task step in the document; Reflects a choice to be made after step execution SymbolDescriptionUsage Comments To next / From last Diagram: Leads to the next / previous page of the Diagram Flow chart continues on the next / previous page Hardcopy / Document: Identifies a printed document, report, or form Does not correspond to a task step in a document; instead, it is used to reflect a document generated by a task step; this shape does not have any outgoing flow lines Financial Actuals: Indicates a financial posting document Does not correspond to a task step in a document; instead, it is used to reflect a document generated by a task step; this shape does not have any outgoing flow lines Budget Planning: Indicates a budget planning document Does not correspond to a task step in a document; instead, it is used to reflect a document generated by a task step; this shape does not have any outgoing flow lines Manual Process: Covers a task that is manually done Does not generally correspond to a task step in a document; instead, it is used to reflect a task that is manually performed, such as unloading a truck in the warehouse, which affects the process flow. Existing Version / Data: This block covers data that feeds in from an external process Does not generally correspond to a task step in a document; instead, this shape reflects data coming from an external source; this step does not have any incoming flow lines System Pass / Fail Decision: This block covers an automatic decision made by the software Does not generally correspond to a task step in the document; instead it is used to reflect an automatic decision by the system that is made after a step has been executed. External to SAP Business Activity / Event Unit Process Process Reference Sub- Process Reference Proces s Decisio n Diagram Connection Hardcopy / Document Financial Actuals Budget Planning Manual Proces s Existing Version / Data System Pass/F ail Decisio n