<media type="image" src="…"/>
as a child of <hero>, switching this page to the
full-bleed dark variant.
Recommended : 1920 × 1080 px (16:9)
Formats : PNG · JPEG · WebP · SVG
Off-spec uploads are rejected — aspect ratio outside 16:9 ±2 %, dimensions outside 800 × 450 … 3840 × 2160.
Master scheduling, MRP and finite scheduling — running against the live operational state.
Demand-driven master scheduling, multi-level MRP, capacity profiles per work centre, finite scheduling for constrained resources, what-if analysis for the schedule that the operations team is about to commit to.
Master schedule
Demand-driven production plan over a horizon configured by the operations team. Firm zone, planning zone and forecast zone with the right level of flexibility in each.
Multi-level MRP
Material requirements computed through the BOM levels, with lead-time offset, lot-sizing rules and safety-stock policy applied per item.
Capacity profiles
Work-centre availability calendars, shift patterns, machine and labour capacity tracked separately, maintenance windows reflected.
Finite scheduling
Constrained-resource scheduling for the bottleneck operations; infinite-capacity scheduling for the rest. The combination matches the reality.
What the planning engine covers
Demand integration
Customer orders (firm), forecast (planned), inter-company transfers, safety-stock replenishment — combined into the demand stream that drives the schedule.
MRP run
Net requirements at each BOM level, planned receipts from POs and production orders, suggested actions (release PO, release work order, expedite, reschedule).
Capacity model
Work-centre calendars, shift patterns, planned downtime, machine and labour capacities tracked separately for accurate load computation.
Schedule visualisation
Gantt-style scheduling board with drag-to-reschedule, capacity heatmap, critical-path identification, what-if scenarios saved without committing.
Exception management
Late-promise alerts, capacity-overload warnings, material-shortage predictions surfaced to the planner with named root cause.
Release controls
Work orders released to the floor only when material is allocated and capacity is reserved. No optimistic releases that fail mid-shift.
Why the bottleneck is the schedule
A schedule that treats every work centre as equal is wrong: one or two operations are usually the bottleneck, and everything else is over-capacity. Scheduling every operation finitely creates artificial constraints; scheduling none of them produces optimistic dates that miss reality.
Axional's scheduling engine identifies the bottleneck operations explicitly and schedules them finitely. The non-bottleneck operations are scheduled to feed the bottleneck on time. The commitment date is the bottleneck's commitment; everything else follows.