Skip to main content

Pull Production vs Push Production in Six Sigma

The concepts of Pull Production and Push Production are central to operations management and are highly relevant in the context of Six Sigma, particularly as Six Sigma often integrates with Lean Manufacturing principles to reduce waste and improve process flow.

The key distinction lies in what triggers the production or work.

1. Push Production System

  • Trigger: Forecasted demand or a pre-determined schedule.

  • Mechanism: Work or products are produced based on a prediction of future need, then pushed downstream to the next step or to inventory, regardless of whether the next step is ready for it.

  • Inventory: Tends to result in high inventory levels (finished goods, work-in-process), as production is decoupled from actual customer consumption. This is often called a "Just-in-Case" approach.

  • Six Sigma/Lean Relevance: Push systems are often associated with waste (Muda), particularly Overproduction (producing more than needed) and high Inventory (which ties up capital and can become obsolete). Six Sigma projects often target the inefficiencies and lack of flexibility inherent in a pure push system.

  • Advantage: Can leverage economies of scale by producing in large batches, and products are generally available for immediate shipping.

2. Pull Production System

  • Trigger: Actual customer demand or a signal from the next downstream process.

  • Mechanism: Production or work is only initiated when the next process or the final customer pulls it. A signal (like a Kanban card or empty bin) indicates that material or work is needed, and only then does the upstream process start work.

  • Inventory: Aims for minimal inventory (Just-in-Time or JIT) as products are only made when ordered.

  • Six Sigma/Lean Relevance: The Pull Principle is a core pillar of Lean Manufacturing (which often complements Six Sigma). It is designed to eliminate the wastes of overproduction and excess inventory, improving flow and reducing lead time. A core element of a pull system is an explicit limit on Work-In-Process (WIP).

  • Disadvantage: Can struggle to meet sudden, large, or unpredictable spikes in demand if the system is not highly flexible.

FeaturePush SystemPull System
Production TriggerForecasted Demand/ScheduleActual Customer Order/Demand Signal
Inventory PhilosophyJust-in-Case (High Inventory)Just-in-Time (Low Inventory)
FlowProducts are "pushed" downstream.Demand "pulls" products upstream.
GoalMaximizing production output and utilization.Minimizing waste, inventory, and lead time.
Six Sigma/Lean ViewSource of waste (Overproduction, Inventory).Lean ideal; focus on value-added flow.
WIP LimitNo explicit limit.Explicitly limited (e.g., via Kanban).

Conclusion for Six Sigma

In the context of continuous improvement, Six Sigma and Lean methodologies generally advocate for a Pull System because it is fundamentally focused on reducing waste (specifically overproduction and excess inventory) and aligning production directly with customer value.

Many companies, however, operate with a Hybrid Push-Pull System, where the initial stages (e.g., raw material procurement, common sub-assembly) are based on a push/forecast, and the final stages (e.g., final assembly, customization) are triggered by a customer pull.

Example:

Pull Production:
Industry: Automotive manufacturing.


Push Production:
Industry: Food and Beverage (e.g., chocolate or candy companies), mass-market household goods, and other staples.
Labels:

Comments

Post a Comment

Popular posts from this blog

Certified Enterprise Architect Professional (CEAP) - Module 5 - Architecture Frameworks

Architecture Frameworks: An Architecture Framework is a theoretical structure that has the purpose of developing, executing, and maintaining an Enterprise Architecture. Advantages of EA framework: Simplify Breaks down areas of the business process Organise business components and create and identify relationships between business Determine the scope Customization in the existing framework Disadvantages of EA framework: Need to follow process Provides only direction and not information It's based on goal and objective Need creativity and proactive thinking Zachman Framework: The Zachman Framework is a widely used model in Enterprise Architecture (EA) that provides a structured way to classify and organize an organization's information infrastructure by defining different perspectives from various stakeholders, allowing for a holistic view of the enterprise and facilitating alignment between business needs and technology solutions; essentially acting as a template to organize arc...
Post a Comment
Read more

Scaled Agile Framework (SAFe)

The Scaled Agile Framework (SAFe) is a set of organizational and workflow patterns for implementing agile practices at an enterprise scale. The framework is a body of knowledge that includes structured guidance on roles and responsibilities, how to plan and manage the work, and values to uphold. Scrum is a simple, flexible approach to adopting Agile that's great for small teams. SAFe is an enterprise-wide Agile framework designed to help bring Agile beyond the team and into the company as a whole. Scaled Agile has built a comprehensive level that includes all the four layers called the team, program, large solutions, and portfolio level. 4 Layers: Portfolio - Strategy, Vision, Roadmap, Strategy goal, Decision making, Budget, Portfolio level metrics,  Program - Align multiple teams towards a common mission, Bring together all the Agile teams, transparency, collaboration, and synchronisation, Scrum of Scrums, Product Owners to define the overall vision. Large Solutions - ar...
Post a Comment
Read more

Certified Enterprise Architect Professional (CEAP) - Module 4 - Architecture Precursors

 Architecture Precursors: Precursors to modern Enterprise Architecture (EA) include early frameworks like IBM's Business Systems Planning (BSP), which focused on aligning business strategy with information systems, as well as other Information Systems (IS) architecture methodologies that emerged in the 1970s and 80s, emphasizing the connection between business processes and IT systems, laying the groundwork for the holistic view of an organization that EA represents today; the "Master Plan for Information Systems" by Evans and Hague is also considered a foundational concept in this area. Drivers: internal / external pressure enforce to change the system Aims & Directives: Aims:  Goals Objectives Requirements Directives: Principles (example: Principles can be associated with business, data, applications, infrastructure, or security) Policies (example: Members of the public have minimal access to data) Business Rules (example: A rule directs and restricts a procedure)
Post a Comment
Read more