Production Logistics and Supply Chain Coordination

Introduction

Production logistics is the coordinated planning and control of materials, information, people, capacity and finished goods as they move from suppliers through production to customers. It connects purchasing, inventory management, production planning, warehousing and distribution. Its purpose is not simply to move materials efficiently, but to synchronise the entire supply chain so that the right product reaches the right customer at the right time, quantity, quality and cost.

A production system may have excellent machines and skilled employees yet perform poorly if materials arrive late, purchasing decisions are disconnected from production schedules, or distribution demand is communicated inaccurately. Coordination therefore requires an integrated view of the supply chain. Material Requirements Planning (MRP), Enterprise Resource Planning (ERP), capacity planning, scheduling, Just-in-Time (JIT), lean systems, the Theory of Constraints (TOC), postponement, decoupling points and bullwhip-effect management are complementary approaches to this problem.

Learning Objectives

By the end of this chapter, students should be able to:

• explain the role of production logistics in supply-chain coordination;
• distinguish MRP, ERP, capacity planning and production scheduling;
• prepare and interpret a basic MRP calculation;
• explain how JIT, lean thinking and TOC improve flow;
• identify postponement and decoupling-point decisions;
• diagnose causes and consequences of the bullwhip effect;
• select appropriate coordination practices for different operating environments; and
• evaluate implementation, technology, governance and performance issues.

1. Production Logistics as an Integrating System

Production logistics has four linked flows:

1. Material flow: raw materials, components, work-in-process and finished products.
2. Information flow: forecasts, orders, inventory records, schedules, capacity data and shipment status.
3. Financial flow: purchase commitments, invoices, working capital and customer payments.
4. Decision flow: choices about sourcing, priorities, batch sizes, capacity and customer allocation.

The flows are interdependent. A sales forecast influences the master production schedule; the schedule creates component requirements; component requirements generate purchasing orders; supplier performance affects production; production completion affects distribution promises. Coordination fails when each function optimises its own measure—for example, purchasing minimises unit price by buying large quantities while production and warehousing suffer from excess inventory.

A useful performance framework considers the trade-off among customer service, cost, speed, dependability, flexibility and quality. Measures should therefore include delivery reliability, schedule adherence, inventory turnover, stockout frequency, total logistics cost, capacity utilisation, forecast error and quality performance rather than purchase price or machine utilisation alone.

2. Planning Architecture: From Demand to Execution

A coordinated planning system normally operates at several time horizons.

Demand management and the Master Production Schedule

The MPS translates a sales or operations plan into time-phased requirements for specific finished products. It must consider customer orders, forecasts, available inventory, existing scheduled receipts, lot sizes, lead times and capacity constraints. An MPS is not merely a sales forecast: it is a feasible commitment subject to resource limitations.

Material Requirements Planning

MRP determines the timing and quantity of component orders or production releases. Its principal inputs are:

• the MPS;
• the bill of materials (BOM), which shows the product structure and usage quantities;
• inventory records, including on-hand balances, scheduled receipts, safety stocks and lead times; and
• planning rules such as lot-for-lot, fixed lot size or economic order quantity.

MRP is generally a dependent-demand system. Demand for a wheel is derived from the planned production of bicycles, whereas demand for a replacement wheel may be independent demand and require forecasting or reorder-point control.

For a simple period-based MRP record, net requirements are calculated as:

where NRₜ is net requirement in period t, GRₜ is gross requirement, SSₜ is desired safety stock, PABₜ₋₁ is projected available balance at the end of the previous period, and SRₜ is scheduled receipt in period t. All quantities must use the same unit and time period. This expression assumes that projected inventory is available to meet requirements and that no additional allocation constraints exist.

Projected available balance is then:

where PORₜ is the planned order receipt. If a lot-for-lot rule is used, PORₜ normally equals NRₜ. Planned order releases are offset backward by the relevant lead time:

where PORL is planned order release and L is lead time measured in periods. The offset assumes that lead time is known and sufficiently stable.

Worked MRP example

A finished product requires two units of component X. The MPS requires 40 finished units in week 2 and 30 in week 3. Therefore, gross requirements for X are 80 and 60 units. Beginning inventory is 50 units, there is a scheduled receipt of 20 units in week 2, safety stock is 10 units, and component lead time is one week. Use lot-for-lot ordering.

For week 2, available stock after the scheduled receipt is 70 units; to finish with 10 units, a planned receipt of 20 is required. For week 3, the opening balance is 10 units and 60 are required, so 60 would appear sufficient if the week-2 planned receipt is included correctly. The table above intentionally illustrates a common planning error: the week-3 net requirement should be calculated from the week-2 ending balance of 10, giving 60 − 10 + 10 safety stock = 60 units, not 80. The corrected schedule is:

This example demonstrates why MRP records must be calculated sequentially. It also shows that a computer-generated plan is only as reliable as its inventory records, BOM, lead times and demand data.

ERP and integrated coordination

ERP extends the logic of MRP across functions such as purchasing, finance, sales, inventory, quality, maintenance, human resources and distribution. A transaction entered in one module can update other modules: a sales order may affect available-to-promise inventory, production requirements, receivables and delivery planning.

ERP benefits include a common database, traceability, standardised processes, faster reporting and improved cross-functional visibility. However, ERP does not automatically create good decisions. Poor master data, unrealistic lead times, inaccurate inventory records or badly designed workflows can produce precisely calculated but operationally wrong plans. Implementation should therefore include data governance, process ownership, user training, controlled changes and periodic validation.

3. Capacity Planning and Production Scheduling

Material feasibility is not the same as production feasibility. A plan may show that all components are available while a bottleneck machine lacks sufficient hours.

Capacity requirements

For a work centre, the basic load relationship is:

where Qᵢ is the quantity of product i, tᵢ is processing time per unit, and setup time is the total time required for product changes. If capacity is measured in machine-hours, all times must be converted to hours.

Available productive capacity can be estimated as:

where N is the number of resources, H is scheduled hours per resource per day or period, D is the number of operating days or periods, U is planned utilisation, and A is availability. The formula assumes that utilisation and availability are defined consistently and do not double-count the same losses.

For example, four machines operate 8 hours per day for 5 days. Planned availability is 90% and utilisation of available time is 80%. Available productive time is 4 × 8 × 5 × 0.90 × 0.80 = 115.2 machine-hours. If scheduled work requires 108 hours, the nominal loading is 108 ÷ 115.2 × 100 ≈ 93.8%. This leaves little protection against variation, so the plan may be technically feasible but operationally fragile.

Scheduling principles

Scheduling assigns jobs to resources and times. Common rules include:

• First come, first served: simple and perceived as fair, but may produce poor flow.
• Shortest processing time: often reduces average flow time, but can delay long jobs.
• Earliest due date: prioritises delivery performance.
• Critical ratio:

A ratio below 1 indicates that the job is behind its required pace. Scheduling rules should reflect the operating objective and be supplemented by human judgement, setup considerations, material availability and bottleneck priorities.

Finite-capacity scheduling recognises actual resource limits; infinite-capacity planning assumes that capacity can be obtained when needed. The former is more realistic but requires reliable data and may expose difficult trade-offs. Schedules should be frozen or protected over a short horizon where changes are costly, while later periods remain flexible.

4. JIT and Lean Production Logistics

Just-in-Time aims to provide materials and products in the required quantity, at the required time and with minimal unnecessary inventory. Lean thinking extends this objective by identifying and removing activities that do not create customer value.

The classic categories of waste include overproduction, waiting, transport, over-processing, inventory, motion and defects; many organisations also include underused human capability. Lean logistics uses pull signals, small lots, reliable processes, standard work, visual management, quick changeovers, supplier development and continuous improvement.

A kanban system authorises replenishment based on actual consumption rather than an unrestrained forecast. A basic container-number relationship is:

where n is the number of containers or kanban cards, D is demand per time period, L is replenishment lead time in the same time unit, S is a safety factor expressed as a decimal, and C is container quantity. The result should be rounded up to a whole number. This formula assumes relatively stable demand, reliable replenishment and uniform container quantities. It is not a substitute for capacity analysis or risk assessment.

If demand is 240 units per day, replenishment lead time is 0.5 day, safety factor is 10% and each container holds 20 units, then n = 240 × 0.5 × 1.10 ÷ 20 = 6.6, so 7 containers are required. Reducing lead time, variability or container size changes the result.

JIT reduces inventory and exposes problems, but it increases sensitivity to supplier disruption, transport delays and quality failures. It should therefore be supported by preventive maintenance, quality at source, supplier capability, contingency planning and rapid problem solving. “Zero inventory” is not a universal objective; appropriate buffers may be economically and ethically necessary for critical items.

5. Theory of Constraints and Flow Coordination

The Theory of Constraints argues that system performance is limited by one or a small number of constraints. Improving non-constraints while leaving the constraint unchanged may create local efficiency without increasing total throughput.

The five focusing steps are:

1. Identify the system constraint.
2. Exploit it by eliminating avoidable idle time and ensuring quality and material availability.
3. Subordinate other activities to the constraint’s requirements.
4. Elevate the constraint by adding capacity, outsourcing, redesigning work or investing in equipment.
5. Repeat when the constraint moves.

TOC commonly uses throughput, inventory and operating expense as high-level measures. Throughput is the rate at which the system generates money through sales, not merely the rate of production. A non-bottleneck producing more than the constraint can consume may increase work-in-process without increasing throughput.

The drum-buffer-rope logic coordinates flow: the drum is the constraint schedule; the buffer protects the constraint from disruption; and the rope controls release of work so that the system does not overload the buffer. This approach complements MRP and lean. MRP plans requirements across time, lean removes waste and TOC focuses managerial attention on the limiting resource.

6. Postponement and Decoupling Points

Postponement delays product differentiation, final configuration or packaging until demand information is more certain. It is especially useful where products share common components but customers require different variants. Examples include delayed colour application, final assembly after order receipt, or packaging products for a particular market near the distribution point.

A postponement decision balances:

• cost of delaying completion;
• cost of holding generic and finished inventory;
• product variety and demand uncertainty;
• final-assembly lead time;
• technical feasibility; and
• customer expectations.

The customer order decoupling point is the point in the supply chain where a product becomes linked to a specific customer order. Upstream of the point, operations may be forecast-driven; downstream, they are order-driven. Common strategies are:

The decoupling point should not be chosen by production alone. It must reflect supply risk, customer service, working capital, product maturity and the economics of variety.

7. The Bullwhip Effect and Supply-Chain Coordination

The bullwhip effect is the amplification of demand variability as information moves upstream from customers to retailers, wholesalers, manufacturers and suppliers. Small changes in final demand can produce large swings in orders, resulting in excess inventory, shortages, overtime, capacity instability and supplier conflict.

Major causes include:

• forecast updating by each tier;
• order batching to reduce transaction or transport cost;
• temporary price promotions and forward buying;
• rationing and shortage gaming; and
• long, variable replenishment lead times.

Forecasting based on orders rather than point-of-sale demand makes each stage react to a distorted signal. A simple variance relationship often used to illustrate the problem under an order-up-to policy is:

where L is replenishment lead time and T is the demand-review interval. This relationship is a simplified analytical result under specific assumptions, including stationary demand, a particular order-up-to policy and consistent information processing. It should not be treated as a universal prediction for every supply chain.

For L = 2 periods and T = 4 periods, the ratio is 1 + 2(2)/4 + 2(2²)/4² = 1 + 1 + 0.5 = 2.5. Thus order variance may be 2.5 times demand variance under the stated assumptions.

Countermeasures include sharing point-of-sale data, reducing lead time, stabilising prices, smaller and more frequent orders, vendor-managed inventory, collaborative planning and replenishment, allocation rules based on past sales rather than inflated orders, and coordinated forecasting. Digital visibility helps only when partners trust the data and agree on decision rights.

8. Coordination Mechanisms and Performance Governance

Coordination requires explicit agreements about information, authority, incentives and exceptions. Useful mechanisms include:

• sales and operations planning meetings;
• integrated business planning;
• supplier scheduling agreements;
• shared forecasts and inventory targets;
• service-level agreements;
• collaborative planning, forecasting and replenishment;
• vendor-managed inventory; and
• joint improvement programmes.

Performance dashboards should connect local measures to system outcomes. A balanced dashboard may include:

Metrics can create harmful behaviour. A purchasing metric based only on price may encourage excessive quantities; a machine-utilisation target may encourage overproduction; an on-time metric without quality control may reward incomplete or defective shipments. Governance should specify metric definitions, data ownership, review frequency and corrective-action responsibilities.

9. Technology, Data and Artificial Intelligence

Modern production logistics uses barcodes, RFID, warehouse-management systems, transport-management systems, IoT sensors, digital twins and cloud-based collaboration. These tools can improve traceability, inventory accuracy, condition monitoring and exception management.

Artificial intelligence can support demand sensing, anomaly detection, predictive maintenance, route planning and supplier-risk analysis. Its value depends on data quality, explainability, cybersecurity and human oversight. A model trained on biased historical purchasing data may reproduce supplier exclusion or systematically disadvantage smaller firms. Automated recommendations should therefore be auditable, monitored for drift and subject to accountable approval when service, safety, employment or regulatory consequences are significant.

Data governance should address master-data ownership, access rights, retention, cybersecurity, confidentiality and the integrity of electronic transactions. Systems should preserve an audit trail for material changes to BOMs, inventory adjustments, supplier records and production priorities.

10. Illustrative Case: Coordinating a Refrigerated Food Supply Chain

Background

FreshBite Foods produces chilled ready meals for supermarkets. It offers 12 meal varieties using many common ingredients. The company experiences frequent stockouts of popular meals, high waste in slow-moving varieties, urgent supplier orders and uneven factory workloads.

Problem analysis

The sales department sends weekly forecasts by product variety. Retailers often promote meals with short notice. Purchasing orders ingredients in large batches to obtain price discounts, while production schedules long runs to maximise equipment utilisation. Finished meals have a short shelf life. Investigation reveals that the company uses forecast-driven production for final packaging even when demand is uncertain. Inventory records for packaging materials are inaccurate, and the main sauce-filling machine is the capacity constraint.

The system therefore combines forecast error, order batching, short shelf life, a bottleneck and conflicting local measures. Increasing finished-goods production would worsen waste rather than improve service.

Approach

FreshBite adopts the following actions:

1. A cross-functional sales and operations process establishes one constrained, time-phased plan.
2. Common sauces and base meals are produced earlier, while final labels and some packaging are postponed until retailer orders are clearer.
3. The sauce-filling machine becomes the drum in a drum-buffer-rope schedule. A protected material buffer is maintained before it, and upstream release is controlled.
4. Packaging and ingredient records are cycle-counted, with ownership assigned to warehouse and production teams.
5. Retail point-of-sale data is shared with suppliers, and ingredient deliveries are moved from large irregular batches to smaller scheduled deliveries.
6. Supplier agreements include quality, temperature-control, delivery and contingency requirements rather than price alone.
7. Performance is reviewed through on-time-in-full delivery, waste, freshness, constraint throughput, forecast bias and supplier reliability.

Outcome

As an illustrative result, the company reduces final-product variety held in stock, improves availability of high-volume meals and lowers obsolete packaging. The principal improvement comes not from one technology, but from aligning the decoupling point, constraint schedule, demand information and supplier replenishment. Management also retains a modest safety buffer for critical ingredients because a purely JIT policy would expose the business to refrigeration and transport disruptions.

Learning points

• Coordination must address the whole flow, not only purchasing cost or machine utilisation.
• Postponement is valuable when common components can be shared and final demand is uncertain.
• TOC directs attention to the resource that limits throughput.
• Accurate data is a prerequisite for MRP and ERP credibility.
• Lean and JIT require reliable processes and risk controls, not blind inventory reduction.

11. Implementation Challenges and Best Practices

Common implementation difficulties include resistance to process ownership, inaccurate master data, unstable engineering changes, unrealistic lead times, inadequate supplier capability, excessive customisation of ERP software and poorly aligned incentives. Organisations may also confuse a planning problem with a software problem.

Best practice is to begin with process mapping and a clearly defined operating model. Establish data standards for item codes, units of measure, BOMs, lead times, calendars and inventory locations. Pilot changes in a product family or facility, measure before-and-after performance, train users and create feedback loops. Senior managers must remove functional barriers and make trade-offs explicit.

A resilient system balances efficiency with protection against disruption. Risk responses may include dual sourcing, qualified alternatives, strategic safety stock, postponement, flexible capacity, supplier development and scenario planning. The appropriate response depends on item criticality, supply-market concentration, recovery time and the consequences of failure.

Ethically responsible coordination includes safe working conditions, fair supplier treatment, transparent sourcing, respect for labour and environmental requirements, and avoidance of coercive delivery practices. Compliance with product safety, transport, customs, data-protection and environmental regulations must be integrated into planning rather than treated as an afterthought.

Chapter Summary

Production logistics coordinates material, information, financial and decision flows from suppliers to customers. MPS converts aggregate intentions into finished-product plans, while MRP explodes those plans through the BOM and offsets requirements by lead time. ERP integrates planning and transactions across functions but depends on accurate master data and sound processes.

Capacity planning tests whether material plans are feasible, and scheduling assigns work to resources according to delivery and flow priorities. JIT and lean reduce waste and use pull-based replenishment, but require reliable processes and appropriate risk buffers. TOC focuses improvement on the system constraint through the five focusing steps and drum-buffer-rope control. Postponement and decoupling points determine where forecast-driven activity changes into customer-order-driven activity.

The bullwhip effect results from amplified demand variation caused by forecasting practices, batching, promotions, rationing and long lead times. Information sharing, shorter lead times, stable commercial policies and collaborative planning reduce it. Effective coordination combines technology, governance, cross-functional metrics, human judgement, resilience and ethical responsibility.

Key Terms

Production logistics: Coordination of materials, information and resources supporting production and delivery.

Material Requirements Planning (MRP): Time-phased planning of dependent component requirements.

Enterprise Resource Planning (ERP): Integrated information system linking organisational functions through shared data and processes.

Master Production Schedule (MPS): Time-phased plan for specified finished products.

Bill of materials (BOM): Structured list of components and quantities required for a product.

Dependent demand: Demand derived from the planned production of another item.

Capacity planning: Assessment and adjustment of resources required to meet planned work.

Finite-capacity scheduling: Scheduling that respects actual resource limits.

Just-in-Time (JIT): Supplying or producing only what is needed, when it is needed.

Lean production: Systematic elimination of waste while improving customer value and flow.

Kanban: Visual or electronic pull signal authorising replenishment.

Theory of Constraints (TOC): Approach that improves system performance by managing its limiting constraint.

Bottleneck: Resource whose limited capacity restricts system throughput.

Postponement: Delaying final differentiation or configuration until demand is clearer.

Decoupling point: Location where forecast-driven supply changes to customer-order-driven activity.

Bullwhip effect: Amplification of demand variability upstream in a supply chain.

Safety stock: Inventory held to protect against uncertainty.

Throughput: Rate at which a system generates output or sales through its constraint.

Sales and operations planning: Cross-functional process aligning demand, supply and resource plans.

Review Questions

Short Answer Questions

1. What are the principal inputs to an MRP system?
2. Why is capacity feasibility different from material feasibility?
3. State the five focusing steps of the Theory of Constraints.
4. What is meant by a customer order decoupling point?
5. Identify three causes of the bullwhip effect.

Long Answer Questions

1. Explain how MPS, MRP and ERP contribute to supply-chain coordination, including their limitations.
2. Compare JIT, lean production and the Theory of Constraints. How can they be used together?
3. Discuss the role of postponement in managing product variety and demand uncertainty.
4. Explain how capacity planning and scheduling influence customer service and inventory.
5. Evaluate governance and data requirements for successful digital production logistics.

Analytical / Application Questions

1. A factory has a single bottleneck that is frequently starved of materials while other machines remain highly utilised. Diagnose the problem using TOC and propose a drum-buffer-rope response.
2. A distributor observes that retail sales vary little, but manufacturer orders vary widely. Analyse the likely bullwhip causes and recommend a coordinated intervention plan.
3. A customised product shares 80% of its components with five other products. Decide where to place the decoupling point and justify your recommendation using cost, service, variety and risk considerations.

Multiple Choice Questions with Answers

Question 1

Which document primarily defines the quantity and timing of finished products in an MRP system?

A. Master Production Schedule

B. Supplier invoice

C. Warehouse picking list

D. Quality audit report

Correct Answer: A. Master Production Schedule

Question 2

A product requires 3 units of component X. If the MPS calls for 50 finished units, what is the gross requirement for X, before considering inventory?

A. 16 units

B. 47 units

C. 53 units

D. 150 units

Correct Answer: D. 150 units

Question 3

Which situation best represents dependent demand?

A. Customer demand for replacement bicycles

B. Demand for tyres derived from planned bicycle production

C. Seasonal demand for bottled water

D. Demand for emergency spare parts

Correct Answer: B. Demand for tyres derived from planned bicycle production

Question 4

A work centre has 120 available machine-hours and a planned load of 108 machine-hours. What is its nominal loading?

A. 90%

B. 10%

C. 112%

D. 228%

Correct Answer: A. 90%

Question 5

In the Theory of Constraints, what should management do immediately after identifying the constraint?

A. Increase inventory everywhere

B. Exploit the constraint

C. Subordinate the constraint to non-bottlenecks

D. Eliminate the sales forecast

Correct Answer: B. Exploit the constraint

Question 6

What is the main purpose of a kanban signal?

A. Authorise replenishment based on consumption

B. Increase batch sizes regardless of demand

C. Replace all capacity planning

D. Record employee attendance

Correct Answer: A. Authorise replenishment based on consumption

Question 7

Which strategy delays final product differentiation until customer demand is clearer?

A. Forward buying

B. Postponement

C. Infinite-capacity scheduling

D. Overproduction

Correct Answer: B. Postponement

Question 8

Which is a common cause of the bullwhip effect?

A. Perfect point-of-sale visibility

B. Stable prices and continuous replenishment

C. Order batching and forecast updating

D. Short, constant lead times

Correct Answer: C. Order batching and forecast updating

Question 9

If daily demand is 240 units, lead time is 0.5 day, safety factor is 10%, and container size is 20 units, how many kanban containers are required after rounding up?

A. 5

B. 6

C. 7

D. 12

Correct Answer: C. 7

Question 10

What is a major limitation of ERP implementation?

A. It cannot store any inventory data

B. It guarantees accurate decisions even with poor data

C. It may produce poor plans when master data and processes are inaccurate

D. It prevents cross-functional information sharing

Correct Answer: C. It may produce poor plans when master data and processes are inaccurate