Why Some Chemical Lot Sizing is Actually a Fleet Problem

Introduction

There's a divide in the process industry that standard planning software completely misses: packaged versus bulk. If you ship paint in 5-gallon pails or additives in drums, your logistics work like e-commerce. The container is a sunk cost, it goes out the door and never comes back, and you never think about it again. Standard inventory math handles that fine.

But if you ship bulk product in railcars or ISO tanks, you're running a closed loop. The container is a capital asset that has to come back before you can use it again, and most planning software has no idea. It treats every shipment as a one-way trip. For your packaged lines, that's harmless. For your bulk fleet, it's the blind spot that shuts the plant down, because if you ignore the return trip of your "packaging," you're not just risking higher freight. You're risking a plant with full silos and nothing to load them into.

The container is an asset, not a wrapper

Standard inventory models like EOQ size production runs around holding cost and demand. That logic assumes the container is disposable, so it never enters the math, which is correct for a pail or a drum: you fill it, ship it, and it's gone. The cost of the container is already in the product cost, and there's nothing to get back.

A railcar is the opposite. It's a six-figure capital asset, and you have a fixed number of them. So your production isn't actually limited by your tanks or your reactors, it's limited by how many empty cars you have to fill right now. You can have full silos, open capacity, and firm orders, and still be unable to make a thing, because every car you own is somewhere out on the network, full, waiting to be unloaded. The constraint moved from the plant to the fleet, and the standard model can't see it.

Your inventory is rolling down the track

In bulk, the most common way to grind production to a halt isn't running out of raw material. It's running out of empty cars. The industry has a name for why: the rolling warehouse. Your inventory isn't sitting in a tank at the plant, it's strung out across hundreds or thousands of miles of track, in transit, at the customer, waiting to be unloaded, and on the way back.

That means the number that actually governs your plant is the return trip time, how long each car takes to complete its full cycle out and back. Plan as if your cars are always available and you'll schedule production you have no way to ship, then watch the plan collapse the first week a stretch of long-haul deliveries ties up the fleet. The return trip isn't a logistics detail to clean up later. It's a hard production constraint, and if you're not planning it, you're planning a shutdown you haven't scheduled yet.

From "cut the order" to "justify the car"

When the fleet is the bottleneck, most schedulers do the only thing they can: treat the car count as a fixed wall and cut the plan to fit it. "We've got 100 cars, so we turn away the order." That keeps the plan feasible, and it quietly caps the business at the size of the current fleet, with no one ever asking whether that's the right size.

The better question is whether the fleet should be bigger, and that's a math question, not a gut call. WonForge models the fleet as a real constraint in the network plan, the number of cars, their cycle, the return trip time, so the plan reflects what your logistics can actually move, not what your plant could theoretically make. And because it's one model, you can test the other version: run a scenario with more cars and see exactly what the added capacity unlocks, the extra volume you could ship, the orders you could stop turning away, the profit that comes with them. Leasing more cars stops being a cost argument and becomes an investment you can size with numbers. You move from managing shortages to justifying equipment with hard math.

Frequently Asked Questions