The schedule, the routes, and the reasons.
Job-shop schedules in Project, routes in a solver black box, MRP in the ERP — and none of them agree. Grid keeps planning, routing, and material availability as one resident model: patch an order and only the affected part replans, with honest optimal / feasible / infeasible statuses, never a silent guess.
Monday morning, as source.
# react to the floor, not to a nightly batch WHEN inventory < reorder_point THEN reorder_requested = TRUE END # replan on a calendar you can audit EVERY cron"0 6 * * 1-5" SKIP MISSED THEN replan_stamp = NOW() END
Rules carry admission control — serial or bounded-concurrent — and retention policies, so a burst of floor events queues deliberately instead of stampeding the planner.
A real scheduling engine
Precedence, resource limits, calendars, sequence-dependent changeovers, weighted tardiness — solved natively, rendered on a Gantt surface with visible solve evidence.
What it replaces →Routing & MRP together
Multi-depot capacitated vehicle routing with time windows, and multi-level MRP/ATP that recomputes only what a supply change can actually affect.
What it replaces →Rules with discipline
WHEN triggers with debounce and throttle, serial queues, durable retention — reactions that survive restarts and never double-fire.
Rules & schedules →