A production plan that recalculates itself whenever something changes.
Schedules, material use and line sequences built from real capacity and your own history – and rebuilt in minutes when a machine stops or a delivery slips, instead of by one planner over an afternoon.
Solution 02 – Production & planningWorks with your ERP
SAP, ABRA, Helios, SyteLine – we build on top of the ERP you already have.
The board
By hand, and by the planner.
The same twelve sample orders, planned twice: by hand, in the order they arrived, and by the planner – loading dates first, like pallets together. The figures show the difference.
- Changeovers
- 7
- Hours of changeover
- 14 h
- Late for their truck
- 4
- Time saved
- –
By hand, in the order the orders arrived: 4 miss their truck.
- Changeover · 2 h
- Changeover · 2 h
- Changeover · 2 h
- Changeover · 2 h
- Changeover · 2 h
- Changeover · 2 h
- Changeover · 2 h
Click a card to see why it sits where it does.
- Late for its truck
- Under 2 h to spare
- In time
The problem
The plan is out of date by ten in the morning.
Where planning costs the most – in the planner's time, and in the dates the plant cannot keep.
- 01
One planner, one spreadsheet
The schedule lives in a file only one person fully understands. When they are away, the plant runs on last week's plan.
- 02
Capacity is a guess
Machine load becomes visible when the week has already gone wrong, and bottlenecks move faster than the plan does.
- 03
Promised dates are hopes
Sales commits delivery dates before anyone checks capacity or material, so expediting becomes the normal way of working.
What's inside
Five modules, from capacity to the cut.
The capacity model comes first; everything else runs on it. Most plants start with scheduling and extend into material and line decisions.
- 01
Capacity model
Machines, shifts, skills and routings described as they really are – built from your ERP history, not a workshop.
- Machine & shift calendars
- Skill matrix
- Routing times from history
- 02
Scheduling engine
Sequences that respect real constraints: capacity, material, changeovers and due dates.
- Constraint-based sequencing
- Changeover optimisation
- What-if scenarios
- 03
Replanning
A breakdown, a late delivery or a rush order turned into a new feasible plan in minutes.
- Disruption events
- Priority rules
- Plan comparison
- 04
Material & cutting
Cutting, nesting and material choice decided from the plan, so the right sizes are made and less is wasted.
- Cut & nesting plans
- Offcut use
- Material requirements
- 05
Line sequencing
Order sequences that cut changeovers and re-stacking on the line, and machine data read to see where the time really goes.
- Changeover reduction
- Line re-stacking
- Downtime analysis
See it in practice
Where we have already built it.
How it is delivered
One team from first call to production.
- 01DiscoverWalk your process. Map the data that exists – and what doesn't.
- 02DefinePick the one problem where AI pays back first. Business case, not a pilot.
- 03BuildPrototype on your data, engineer the system, validate against reality.
- 04DeployIntegrate with ERP, CAD and the shop floor. On your servers or in a secure cloud in the EU.
- 05Run & extendMaintain it, improve it, extend it to the next line.
What we need from you
- Order, routing and completion history from your ERP – as many years as you keep
- Your workstations, machines and shift calendars
- The rules your planner works by, including the unwritten ones
- A few hours a week from the person who plans today
All under NDA, signed before you send us any data. We usually start on an older export, enough to learn its structure, and move to live data once the system holds up. Access is read-only, your data stays on your servers or in a secure cloud in the EU, never goes to a third party, and is used only to build your system.
First results within 6 weeks, a plan in daily use within 3–5 months
Contact
Tell us the problem. We'll tell you if AI is the answer.
Thirty minutes with a founder. No pitch – a conversation about your process, your data and whether a system would pay for itself.
Or reach us directly
- Matyáš ProkopiusCo-founder
- Adam BulkaCo-founder