More than a production calendar. The scheduler understands the character of each resource: machine cycle times, tank capacity and hold times, pump flow rates. It then builds a schedule around the constraints that genuinely exist on the shop floor.
Machines, tanks, and pumps cannot be treated with the same formula. The scheduler computes duration from the character of the resource in use, rather than from a duration figure typed in by hand.
| Resource type | How duration is determined |
|---|---|
| Machine | Setup time plus cycle time multiplied by the production quantity. |
| Tank | Based on volume and hold time. If the volume exceeds capacity, the scheduler can allocate to the next tank while respecting the available piping connections. |
| Pump | Based on volume divided by flow rate. Transfer duration is computed from the pump's flow capacity rather than entered manually. |
Per-resource constraints can include tank capacity, minimum and maximum hold time, cleaning, cooldown, maintenance windows, and pump rates for both inbound and outbound transfers.
An intermediate tank is in use from the moment filling starts until its entire contents have been moved out. Counting only the dwell time can make a schedule look free when the tank is still tied up by a running process.
| Phase | Duration | Example at 1000 kg |
|---|---|---|
| Fill in | Lot volume ÷ pump rate in | 1000 L ÷ 100 L/min = 10 minutes, and can overlap with the pump-out of the preceding process |
| Wait | Minimum hold time | 30 minutes, no overlap |
| Fill out | Lot volume ÷ pump rate out | 1000 L ÷ 50 L/min = 20 minutes, and can overlap with the downstream process |
| Total occupancy | — | 60 minutes, not just the 30 minutes of hold time |
What planners usually want settled before trusting their production schedule to a system.
Both. Machines, tanks, pumps, capacity, hold times, and piping topology can all act as scheduling constraints directly, so process manufacturing does not have to be treated as an exception.
No. With Drum-Buffer-Rope, the scheduler can identify the constraint resource itself and build the schedule to protect throughput around it.
Yes. Cleaning, cooldown, maintenance windows, working calendars, and labour availability can all form part of a resource's constraints, so the schedule reflects real operating conditions more closely.