The planner checks the data, and Outlay builds and costs the schedule.

Outlay does the arithmetic of who and what can run where, and when, then re-costs each run from the floor.

From reviewed data to a schedule in one action.

The planner checks the data. Outlay does the arithmetic of who and what can run where, and when.

1
Load demand and master data
Items, recipes, routes, resources and demand come in from your systems or a spreadsheet, each record showing its source and what is missing.
2
Generate the schedule
Outlay plans every operation against finite machine time and qualified labour, with changeovers, allergens and material feeds as hard rules.
3
Run it in the cockpit
Plan and actual sit side by side on one Gantt, and any run lights up the chain it depends on and the work it feeds.
4
Let the floor re-cost it
Each reading from the line re-derives the run's projected cost and margin against standard while the shift is still going.

Cockpit · Thursday

On plan

Each work order takes the first slot where its machine, its crew and the run feeding it are ready.

Changeover time sits between runs, and an arrow runs from each batch to the run it feeds.

The run on it, and every run that depends on it downstream, is flagged at once.

The chain moves to the next slots that work, and margin against standard settles at its new projection.

Talk to Libra about loading your master data and generating a schedule against the machines, people and standards you actually have.

Tell us how you plan today, and we will show you the product and what it would need from you.