Machine and mold fit
A container can only run on machines that take its mold, head tooling, and trimming setup. Make that eligibility explicit per product rather than keeping it in the scheduler’s head.
Blow molding scheduling
Turn bottle and container orders into a machine-feasible schedule that accounts for which machines can run each container, your output per hour, the changeover minutes you enter for mold and color changes, and delivery dates.
30 days free · No credit card required · No automatic charge
Who this is for
Production managers running a handful of blow molding machines with molds that mostly stay with one machine.
Schedulers juggling resin and color changes across HDPE, PP, or PET containers in a spreadsheet.
Plant managers who need a shared view of delivery risk and case-level traceability without an ERP project.
Real scheduling constraints
A container can only run on machines that take its mold, head tooling, and trimming setup. Make that eligibility explicit per product rather than keeping it in the scheduler’s head.
Real output depends on cycle time and cavitation for each container on each machine. Enter the demonstrated containers per hour for each machine/product pair instead of one plant-wide rate.
Mold swaps, purges, and color changes take different amounts of time depending on what ran before. A natural-to-white switch is not the same as white-to-natural.
Machines that run two shifts and machines that run around the clock need different usable hours, so a promise date has to come from each machine’s own calendar.
Order-to-schedule example
Order: 180,000 one-gallon natural HDPE jugs, due in eight production days, on a container that two machines are approved to run.
RunMark considers only the two approved machines, sizes the run from each machine’s configured jugs-per-hour rate, and reserves the changeover minutes from whatever product runs before it on the chosen machine.
The scheduler sees the calculated finish against the due date. When the run is released, case labels carry product, machine (line), run, production date, order reference, and unit sequence.
One connected workflow
Set which containers each machine can run. Each machine is a line in RunMark.
Use containers per hour for each machine and product, worked out from your own cycle time and cavitation.
Enter setup minutes for each product-to-product switch on a machine—mold, resin, or color. The optimizer reserves that time before each run.
See whether calculated run timing supports the customer promise before the order reaches the floor.
Generate case or pallet labels from the scheduled run, with run and unit numbers.
Spreadsheet scheduling compared
| Spreadsheet workflow | RunMark workflow |
|---|---|
| Which machine takes which mold lives in one person’s memory. | Machine/product eligibility is explicit and reusable. |
| Run length is recalculated by hand when cycle time or quantity changes. | Timing follows the configured rate for that machine and product. |
| Color and mold changes are pencilled in as a guess. | Setup time from your changeover table occupies visible machine time. |
| Case labels are typed from the order sheet. | Labels start from the same persisted production run. |
Relevant RunMark capabilities
Start with the machines, containers, and open orders you already track. Model a mold that moves between machines by making each machine eligible for it—RunMark does not reserve molds as a separate resource. The 30-day trial needs no credit card.
Pricing is one plan at $249/month or $2,490/year, with unlimited lines, orders, and SKUs, after a 30-day free trial.
Frequently asked questions
No. RunMark schedules machines (lines), not molds as a separate shared resource, so it will not stop the same mold being planned on two machines at once. It fits best where molds mostly stay with one machine.
Enter the resulting output rate—containers per hour—for each machine and product. RunMark schedules from that rate; it does not model cycle time or cavities as separate fields.
Partly. RunMark’s optimizer reserves the changeover minutes you enter for each product pair before each run, never places runs closer together than that allows, and weighs changeover time against due dates. If the optimizer is unavailable, a simpler fallback scheduler drafts the schedule instead; the draft review shows which one produced it. The fallback also reserves your changeover minutes before and after every run it places, but it places orders one at a time in due-date order instead of weighing them all together. Neither searches for the sequence with the least total changeover across the week.
No. Each order is scheduled as one run on one machine; RunMark does not model multi-step routings.
Available label fields include product, production date, line (machine), run number, unit number, order reference, part number, and company identity.
No. The 30-day trial requires no credit card and creates no automatic charge.