Resources

What-if scheduling, a putaway widget, and root-cause investigations get their own module

Planners can now save and run what-if scheduling scenarios before committing to a change. A new operator widget combines job-order handling with putaway, and root-cause investigation work moved out from under Quality into its own module.

Planners can now build a what-if scheduling scenario, save it, and see how it plays out before touching the real schedule.

A scenario runs against the same capacity math as the live schedule and comes back with a verdict, so a planner can rule out a bad idea before it goes on the real schedule.

Try it before you commit

  • Model demand as a single date, a spread, or a recurring pattern
  • See a Feasible, Tight, or Infeasible verdict across the horizon you set
  • Get the likely bottleneck, and compare two scenarios side by side

One widget for putaway

A new operator widget puts job-order selection and putaway execution in the same panel. An operator picks the job order, works the putaway queue with simple skid counts, and the job order’s actuals update as they go, no switching screens to reconcile the two.

Investigations get their own module

Root-cause investigation and corrective-action work used to live as a tab inside Quality. It’s now a module of its own, with its own dashboard, case list, issue list, and kanban board, so a case doesn’t get lost inside someone else’s queue.

Alongside that, a new quality gate can require a form to be submitted and pass before the next production step is allowed to start.

Improvements
  • Materials Summary gets a Run MRP button and a reorder-point alerts section
  • Capacity utilization widget relabelled with a corrected formula and dynamic time buckets
Fixes
  • Fixed an issue where editing a production order's start and end time did not save correctly
  • Fixed a warehouse load-creation error triggered by gaps in a site's load-number sequence