Resource planning

Every constraint your plant has.
One feasible answer in 30 seconds.

Machine eligibility, shifts, maintenance, setup matrices, materials, due dates - solved together, not in spreadsheets.

KFactory Plan
Solving
Solver Output·Optimal Schedule
<30s
Solve Time
8
Hard Constraints
What the solver respects

Hard constraints.
All of them. Every cycle.

Skip one and the schedule is wishful thinking. KFactory honours all eight, simultaneously.

Machine eligibility

Which operations can run where, with required tooling and skill.

Shift patterns

Up to 3 shifts per day, including weekends and holidays.

🔧

Maintenance windows

Planned downtime treated as a hard block, not an afterthought.

🔁

Setup matrix

Sequence-dependent changeovers - A→B costs more than A→A.

Batch splitting

Split a batch across machines when speed beats setup cost.

Transfer times

Move time between machines, including conveyor and AGV legs.

Parallel lanes

Multi-lane processing on machines that run >1 job at a time.

📅

Due dates

Customer commitments - soft, hard, or contractually penalised.

What it optimises

One solver. Three answers.

Pick the objective. The solver finds the best feasible schedule for it.

Objective 1

Minimise makespan

Finish the whole batch as early as possible - even if some orders idle.

Result · Gantt
Best when capacity is the bottleneck
Objective 2

Minimise lateness

Hit every due date - accept some idle time as the price of on-time delivery.

Result · Gantt
Best when SLA penalties matter most
Objective 3

Maximise utilisation

Keep every machine busy. Trade some lateness for higher throughput.

Result · Gantt
Best when fixed costs dominate
At the planner's bench

Where the solver meets the human.

🖱

Drag-and-drop Gantt

Move a task, pin it, and replan the rest - the solver respects your decision.

[Pin] Order #1042 → Mon 08:00
Replan rest of week...
💬

Natural-language assistant

Ask in plain English. Powered by Microsoft Semantic Kernel.

You: Reschedule next week, prioritise Customer X.
KF: Done. 3 changes, 0 slips.
📊

What-if scenarios

Test a rush order before committing. Compare KPIs side-by-side.

Insert Order #1099 (1200u, Thu)
+1.2h makespan · 0 slips · save?
14-day bottleneck heatmap

The week before
the week breaks.

Capacity utilisation · next 14 days
Hot cells = bottleneck risk. Reroute before orders go late.
D1
D2
D3
D4
D5
D6
D7
D8
D9
D10
D11
D12
D13
D14
M1 · CNC
M2 · Press
M3 · Weld
M4 · Paint
M5 · Assy
Idle Overload
Impact calculator

See what KFactory Plan
could be worth to you.

Adjust the sliders to match your operation. The annual impact updates live, based on APICS/ASCM advanced-planning-and-scheduling benchmarks.

Adjust the sliders to match your operation
Production orders per week50
10500
Average changeover time (min)30 min
5120
Planner hours per week on scheduling15 hrs
240
Average employee cost per hour (€)55
€30€120
Estimated annual impact
48,620
per year

How it's calculated: Changeover savings (orders × changeover hours × hourly cost × 52 weeks × 20% reduction) + planner-time savings (hours × hourly cost × 52 weeks × 80% reduction). Based on APICS/ASCM scheduling-optimisation benchmarks.

Technical specification

Built to be trusted.

SpecificationDetail
Solver EngineGoogle OR-Tools CP-SAT
Schedule Generation<30 seconds for typical scenarios
Constraint TypesMachine eligibility, shift patterns, maintenance, setup matrices, batch splitting, transfer times, parallel lanes
Optimisation ObjectivesMinimise makespan · Minimise lateness · Maximise utilisation
Scheduling ModesForward (ASAP) · Backward (JIT)
AI AssistantMicrosoft Semantic Kernel - natural language scheduling
MRPBOM explosion, net requirements, safety stock, shortage alerts
Capacity Analysis7 / 14 / 30-day bottleneck detection
ExportPDF · Excel · CSV
ERP IntegrationStandard API - orders, machines, materials

Hand us
your hardest week.

We'll model your real constraints and run the solver live on a 20-minute demo.

Request a Demo