Skip to content

Scheduling & Capacity

Eryxon Flow includes a simple capacity-based scheduler for planning operations across your production cells. It allocates work based on cell capacity and your factory calendar—not a full APS optimizer, but enough to get a clear capacity overview and planned dates on every operation.

  1. Click Auto Schedule on the Capacity Matrix page
  2. The scheduler fetches incomplete jobs and their not-started operations; active and completed work keeps its existing plan
  3. Jobs are sorted by due date (respecting any manual overrides)
  4. Operations are allocated to their assigned cells day by day, respecting daily capacity limits
  5. Dates and daily allocations are saved together in one transaction

If not-started operations already have planned dates, a confirmation modal warns you before overwriting them. Existing allocations remain in place when an operation cannot be replanned. The result names how many operations were scheduled and how many still need attention. Work behind an active predecessor without a known finish stays unscheduled.

Each cell (work center) has a capacity_hours_per_day setting, configured in Admin → Stages & Cells. The scheduler never exceeds this daily limit—large operations overflow to subsequent working days.

Navigate to Admin → Factory Calendar to configure:

  • Holidays — No work scheduled (capacity = 0)
  • Closures — Factory closed (capacity = 0)
  • Half days — Reduced capacity (multiplier = 0.5)
  • Working days — Full capacity

Calendar entries override the working week configured for the workshop.

Admins can override a job’s due date without changing the original ERP-provided date. The scheduler uses the override when prioritizing which jobs to schedule first. Override a due date from the Jobs list by clicking the calendar icon.

The Capacity Matrix page at Admin → Capacity Matrix shows:

  • Cell utilization by date in a color-coded grid
  • Green ≤50% · Yellow ≤80% · Orange ≤100% · Red overloaded
  • Click any cell/date to see which operations are allocated
  • Operations are scheduled in job due date order, not optimized for throughput
  • No cross-job dependency tracking
  • Only cell capacity is considered, not worker availability or materials
  • No what-if scenario simulation

For complex scheduling needs, use a dedicated APS tool and sync dates via the REST API, CSV Import, or the MCP server.