BUSI 615 Week 5 Discussion Board 3 thread Example

Discussion Board 3: Integrated Logistics Information Systems

BUSI 615 Logistics, Discussion Board 3 (thread)

Thread by [Student Name]

The stove manufacturer and its warehouse figures are composites standing in for the firm a student would choose; the research cited is real, and the requirements follow Liberty's public course guide for BUSI 615.

Thread

Most of the case for an integrated logistics information system rests on visibility: everyone in the chain sees the same inventory and demand data. My argument in this thread is that visibility is the smaller benefit. The larger one is speed and smoothness, meaning orders that move through the chain faster and in smaller, steadier quantities. A system justified only by visibility often disappoints, while a system designed to compress the order cycle usually pays for itself.

Distribution requirements planning as integration

This week's chapters on distribution requirements planning show what integration means in practice. Harlan Ridge Stoveworks, the composite stove maker from the earlier forums, ships to its dealers through regional warehouses. Suppose its warehouse in Columbus, Ohio, expects to sell 60, 60, 80 and 80 PS-40 pellet stoves in the next four weeks, starts with 150 on hand, keeps 40 as safety stock, receives full trailers of 120 and waits one week for a shipment from the plant.

That bottom row matters most. Those planned shipments, added to the same figures from every other warehouse, become the gross requirements at the plant, which then drive the master production schedule and, through MRP, the orders for motors and steel. DRP thus links the distribution network to the factory with one time-phased logic. Without it, the plant would see only the orders warehouses happened to send, after the fact.

The table also shows the problem. Trailer-sized shipments of 120 turn steady weekly sales into lumpy demand at the plant: 120 one week, nothing the next. Multiply that across several warehouses and stove models, and the plant faces the same batching distortion that classmates discussed in Forum 1.

What the evidence says

Cachon and Fisher (2000) modeled a supplier serving several retailers and compared a policy that used shared demand and inventory data with one that relied only on orders. Full information sharing lowered supply chain costs by 2.2 percent on average, with a maximum of 12.1 percent across their scenarios. They then examined two other benefits of information technology: faster order processing, which shortens lead times, and cheaper order processing, which makes smaller batches economical. Cutting lead times nearly in half reduced costs by about 21 percent on average, and halving batch sizes reduced them by about 22 percent. In their model, information that arrives faster and in smaller pieces was worth roughly ten times as much as information that is merely shared.

The result does not mean visibility is worthless; it means visibility pays most when it changes how orders flow. Survey research points the same way. Closs and Savitskie (2003) studied logistics information technology and found that integration of information inside the firm and with customers was associated with better customer service performance. Rai et al. (2006) surveyed 110 supply chain and logistics managers in manufacturing and retail and found that integrated IT infrastructure supported a higher-order capability to integrate information, physical and financial flows across the supply chain, which in turn was linked to stronger firm performance. In both studies the benefit came from coordinated processes built on the technology, not from the technology alone.

What this means for the stove maker

For Harlan Ridge, the evidence suggests three priorities for an integrated logistics system, in order. First, shorten the replenishment cycle by connecting warehouse DRP directly to the plant's schedule, so that a planned shipment becomes plant demand the same day rather than at a weekly meeting. Second, make smaller shipments economical, for example by building mixed trailers that carry several stove models and spare parts, so the Columbus warehouse can order 60 mixed units weekly instead of 120 of one model every other week. Third, add dealer sales data where large dealers will share it, which improves the forecast feeding the DRP record. Each step can be measured separately, so the firm will know which one paid off.

Notice that only the third priority is about visibility in the usual sense. The first two change the speed and size of the flow, which is where Cachon and Fisher found most of the value. They also connect to this week's chapters on channel design: a firm that can ship smaller, faster loads may need fewer warehouses, since dealers can be replenished from the plant directly in some regions.

Where integration can disappoint

None of this happens automatically, and the chapters on channel management explain why. A logistics system that spans firms depends on partners who have their own systems, priorities and reasons for caution. Many of Harlan Ridge's dealers are family businesses that track stock in a spreadsheet or a basic point-of-sale program, and asking them to transmit weekly sales in a standard format is a real burden. The firm would need to make participation easy, perhaps through a simple web portal, and offer something in return, such as guaranteed replenishment within a set number of days for dealers who share data.

Inside the firm, integration fails most often on data rather than software. A DRP record is only as accurate as the warehouse's on-hand balance, the safety stock setting and the lead time recorded for each lane. If the Columbus warehouse's count is off by twenty stoves, or the system still assumes one week when trucks now take ten days, the plan will ship too little or too late with full confidence. The textbook's emphasis on record accuracy in MRP applies with equal force to distribution.

Finally, faster cycles have costs. Mixed trailers require more picking at the plant, and weekly shipments mean more loads and possibly higher freight per stove. The case for speed holds only when the savings in inventory and lost sales exceed those added handling and transport costs, which a firm should estimate before committing.

A question for classmates

Classmates who work in distribution will know better than I do how these projects are justified in practice, so I have a practical question: when your firm invested in a warehouse or transportation system, was the business case written around visibility or around shorter cycle times? And did the results match what the case promised, or did the savings show up somewhere the case never looked, such as fewer emergency shipments or less overtime at the plant?

References

Cachon, G. P., & Fisher, M. (2000). Supply chain inventory management and the value of shared information. Management Science, 46(8), 1032-1048. https://doi.org/10.1287/mnsc.46.8.1032.12029

Closs, D. J., & Savitskie, K. (2003). Internal and external logistics information technology integration. The International Journal of Logistics Management, 14(1), 63-76. https://doi.org/10.1108/09574090310806549

Rai, A., Patnayakuni, R., & Seth, N. (2006). Firm performance impacts of digitally enabled supply chain integration capabilities. MIS Quarterly, 30(2), 225-246. https://doi.org/10.2307/25148729