BUSI 615 Week 6 Discussion Board 3 replies Example

Discussion Board 3: Replies to Classmates

BUSI 615 Logistics, Discussion Board 3 (two replies)

Thread by [Student Name]

The two classmates and their threads are composites standing in for the forum's own posts; the research cited is real, and the requirements follow Liberty's public course guide for BUSI 615.

Reply to Jordan

Jordan, your thread made a persuasive case that case-level RFID tags would let your grocery chain's distribution center see every pallet of produce from receiving to the outbound dock. I agree the tags create more data than barcode scans, since they are read automatically as cases pass a portal. My reply asks a narrower question: what would the chain learn from that data that it could act on, given this week's focus on transportation?

Delen et al. (2007) worked with actual RFID data that a major retailer collected for the cases one of its large suppliers shipped. Readers were placed at points such as the distribution center's dock doors and at stores, where readers covered receiving, the backroom and the doors to the sales floor. The authors converted raw read events into measures of the time between movements, for example how long a case waited in a store's backroom before reaching the shelf. Their argument was that these interval measures, not the reads themselves, are where the business value lies, because they reveal where product sits idle. They also reported data-quality problems that early users faced, including cases that were not read at some points.

Applied to your distribution center, the most useful measure might be the time between a produce case arriving at the outbound dock and leaving on a truck. If cases routinely wait six hours because outbound trucks are scheduled for store convenience rather than freshness, the tags would make that visible in a way no one would find by walking the floor. That links directly to this week's chapter on transportation: the fix would not be more tags but a different dispatch schedule, perhaps more frequent smaller loads to high-volume stores. Tags show where a case waited; only a planning decision can stop it from waiting there next week.

The missed reads matter too. If a portal fails to record 5 percent of cases, a manager could wrongly conclude that product disappeared or that a door was unused. Before trusting interval measures, the chain should audit read rates by door and by product type, since cases of water-heavy produce are known to be harder to read than dry goods.

The interval data could also feed capacity planning on the receiving side. If tag reads show that inbound trailers from growers sit at the yard for two hours on Monday mornings but only twenty minutes midweek, the distribution center has a dock capacity problem concentrated on one day, not a general shortage of doors. Staggering grower appointments across the week might solve it without new construction. That is the kind of decision this week's capacity chapter has in mind: matching a fixed resource, here dock doors and receiving crews, to a demand pattern that the firm can partly shape.

I also wonder about cost. Tags on every case of low-margin produce add up quickly. Would your chain start with tagging returnable plastic crates, which are reused for months, rather than disposable cases? That approach would give much of the timing information you described at a fraction of the tag cost.

Reply to Elena

Elena, your thread described the transportation management system your third-party carrier installed last year and the improvement in on-time pickups that followed. You credited the system's route optimization for most of the gain. I found your example convincing, but I want to suggest another explanation, because the evidence on logistics technology points to the way people work together around the system as much as to the algorithms inside it.

Sanders and Premus (2005) surveyed firms to test how IT capability relates to collaboration and performance. They found that IT capability was directly linked to firm performance and also to collaboration inside the firm and with outside partners such as suppliers and customers. Their conclusion for managers was that technology investments should be judged partly by whether they make collaboration easier, not only by the tasks they automate.

Your thread contained a detail that fits this view. You mentioned that the system lets shippers enter pickup requests directly, so dispatchers see next-day loads by early afternoon rather than in the evening. That change is collaborative: shippers and dispatchers now share one picture of tomorrow's work hours earlier. Route optimization depends on it, because an optimizer working with half the next day's loads cannot build efficient routes. It is possible that much of your improvement came from earlier, shared information rather than from the routing logic.

This week's chapter on capacity planning suggests a next step. If shippers are already entering requests, the carrier could ask its largest customers to forecast weekly volumes a few weeks ahead, then plan truck and driver capacity against those forecasts in the way a plant checks its schedule against capacity before committing. The carrier would avoid both idle trucks and turned-away loads during peaks. Such a practice requires trust, since customers must believe their forecasts will be used to serve them better rather than to raise rates.

A capacity plan of that kind would also change how the carrier sells. Instead of quoting rates load by load, it could offer committed capacity to customers who forecast reliably, with a discount for steady volume and a premium for last-minute requests. Contract freight already works on a similar principle, trading committed volume for a lower rate than the spot market, and the logic matches the textbook's distinction between planning capacity in advance and reacting to demand as it arrives. The transportation management system would then become the record of those commitments, showing which customers forecast accurately and which do not. Over a year, the carrier would learn whose forecasts it can plan around and whose it should treat with caution, which is itself a form of collaboration the software enables but cannot create.

There is also a test you could run. Comparing on-time performance for shippers who enter requests online with those who still call or email would show whether the collaborative channel, rather than the optimizer, drives the improvement. If the online shippers perform much better, the carrier's priority should be bringing the remaining customers onto the portal. Do you know roughly what share of your carrier's customers now use it?

References

Delen, D., Hardgrave, B. C., & Sharda, R. (2007). RFID for better supply-chain management through enhanced information visibility. Production and Operations Management, 16(5), 613-624. https://doi.org/10.1111/j.1937-5956.2007.tb00284.x

Sanders, N. R., & Premus, R. (2005). Modeling the relationship between firm IT capability, collaboration, and performance. Journal of Business Logistics, 26(1), 1-23. https://doi.org/10.1002/j.2158-1592.2005.tb00192.x