Good judgement, too many options
Planners know their line better than any software, but nobody can compare every possible run order by hand, so rules of thumb fill the gap.

Decision intelligence for industrial operations
Every line runs at the pace of its constraint. An hour lost at the bottleneck is an hour of throughput lost for the whole line, and it lands straight on your P&L. ModelWeave finds your constraint, cuts the changeovers that starve it, protects it with the right buffer, releases work at its pace (drum-buffer-rope) and tightens the roster around it. Then it shows, sum by sum, what each change does to throughput, cost and profit.
Investment becomes a calculated decision too: before you buy a machine or add a shift, ModelWeave shows whether the constraint is really short of hours and tests what the extra capacity would save, so capital goes where it raises throughput.
Every figure is labelled: proven, measured, tested, unknown or a ModelWeave default.
Same orders, same week. The filler is the constraint here, so every hour saved there is an hour of throughput for the whole line.
Optimisation doesn't guess. Every saving is a sum you can check, every plan is re-checked against your rules before you see it, and anything we don't know is labelled as unknown.
Planners know their line better than any software, but nobody can compare every possible run order by hand, so rules of thumb fill the gap.
Useful for drafting and summarising. They predict likely text, so an answer can read well and still break a rule, or quote a figure nobody calculated.
Your rules become constraints and your costs become a sum to make as small as possible.
A line's output is set by one station, its bottleneck. An hour lost there is an hour lost for the whole line; an hour saved at a station with spare time saves money, not output.
We compare the work each station has to do with the time it really has, week by week. The station with the least to spare is your bottleneck. Takt time, the pace your demand sets, is one of the checks we use.
The five focusing steps below guide the plan: fewer changeovers at the bottleneck station, a buffer that protects it, and work released at its pace (drum-buffer-rope). When the bottleneck moves, the report names the new one.
The bottleneck tells ModelWeave where to focus. The plan itself is chosen on your operating costs (changeovers, late orders, stock, labour and overtime), and output through the bottleneck station is shown next to it.
Most of the cost a planner can influence sits in four places. None of them shows up as a single line in the accounts, which is why they are easy to live with.
Every switch stops the station, and a full clean also uses water, chemicals, energy and product. At the constraint, those hours come straight off the line's throughput.
Schedule optimisation finds a cheaper run order.
Retailers fine late or short deliveries, and a late order often drags others with it. The cost is real even when no one invoices it.
Schedule optimisation weighs lateness against changeovers.
Work released too early queues between stations. It ties up cash and space, and food products lose shelf life while they wait.
Inventory buffer optimisation sets stock levels and release times.
Overtime often covers time lost elsewhere, and rosters built by hand rarely match each shift to the work that actually needs doing.
Workforce optimisation builds a roster within your rest rules.
Pick what sounds familiar and we'll suggest the modules. Change the ticks as you like: the panel shows what you would upload, what you get back, and an example result.
1What sounds familiar?
2Your modules
| Changeovers at the filler | 19 → 11 a week |
|---|---|
| Late-delivery penalties | £35,000 a year lower |
| Waste and cleaning, from fewer changeovers | £51,360 a year lower |
| Yearly effect on profit | £86,360 |
Figures from our illustrative example, Kettle & Co Foods. Your results depend on your line and your data.
Takes you to a short request form; your picks come with you.
No integration project. You upload the spreadsheets you already keep; ModelWeave matches the columns and you confirm them.
Orders, process steps, changeovers and shifts, as CSV or Excel. A template sits beside every upload.
ModelWeave builds your line: each station's own calendar, efficiency and downtime, in real clock time.
ModelWeave searches for the cheapest plan it can find in the time allowed.
The plan runs through many simulated weeks with breakdowns, so you see the risk as well as the saving.
An independent check re-verifies every rule. The report writes out every saving as a sum.
Each statement in a ModelWeave report says how we know it. If a claim can't be backed, we don't make it.
Worked out by arithmetic from your data.
Order 1042 cannot be on time: its material arrives too late for the hours it needs.
From simulating your line through many weeks with breakdowns.
Every order on time in 71% of simulated weeks.
An alternative was tried, and we say which rule decided it.
Grouping by allergen first was tried: it cost more in late orders.
Your data doesn't say, so we don't pretend it does.
Material dates were not uploaded, so material is assumed available.
ModelWeave's own setting, used where your files are blank.
Repair time at Capping: 30 minutes, a ModelWeave default.
The example sentences are illustrative. In your report they use your orders, stations and figures.
Files you upload are never retained or stored: they're held in memory while you work and cleared when you sign out.
Worker data uses codes, never names.
No public sign-up. Every account is set up by us, for a business email address. Your email address is used only for your account and to reply to you, and is never sold or shared.
Tell us what you make and which modules interest you. We'll set up your workspace and a free trial, and you can start with our sample data before you upload anything.