Workflow Modules
Plan the forecast by customer and SKU. Shortfalls show up early as reorder recommendations. A person approves each one before it becomes a purchase order.
How it works
Edit the forecast by customer and SKU, see projected on-hand turn a gap into a reorder recommendation, and test a change in a scenario before you publish it.
Forecast worksheet
Plan by customer and SKU, period by period, across whatever horizon your site is set up for. Change a number for one customer’s SKU and the totals recompute as you type. A snapshot keeps the version you published, so you can always see what the floor is running against.
Forecast rules
Type a rule the way you’d say it. No formula. Scope it to one account and SKU, or the whole worksheet. If it conflicts with a rule already running, it’s flagged. If the parser can’t act on the sentence, it comes back unchanged.
Projected on-hand
Projected on-hand runs your forecast against inventory, period by period, so a shortfall on a part number shows up weeks before it bites. Demand imports from the system that raises the orders and refreshes on its own schedule. Maintenance and repair demand is projected right beside production demand.
Needs ordering
Material requirements roll up from the bill of materials and the plan. Whatever falls short of the reorder point, safety stock and lot size you’ve set comes back as a reorder recommendation. A person approves it before it becomes a purchase order.
Demand orders
Every forecast row traces back to the demand and sales orders it came from, listed right beside it. Each import carries a time stamp, so you know exactly what the number in front of you reflects.
Requirements scenario
A scenario carries its own set of demand periods, so testing a change never touches the plan the floor is running against. Compare it to the snapshot you published. Nothing on the live plan changes until you publish the scenario yourself.
Plan handoff
Your forecast is one input to the rest of the platform. The Scheduling Engine sequences the jobs it calls for, and run readiness is checked against the materials it expects on hand. The Demand Planner doesn’t run the floor and it doesn’t buy: you approve every order a recommendation produces.
Type a rule the way you'd say it and the worksheet recomputes right away, with no formula and no overnight batch. A conflict with a rule already running comes back flagged so you can check it.
A scenario runs against its own set of demand periods, separate from the plan the floor is running against. Compare it to the snapshot you published, then publish it yourself when it's ready.
No. Demand imports from the system that already holds it, and the forecast worksheet plans on top of that.
As a plain sentence. It’s parsed into a rule, scoped to an account and SKU or the whole worksheet, and checked for conflicts.
No. It produces reorder recommendations, and a person turns one into a purchase order.
Yes. A scenario carries its own demand periods, and snapshots keep the version you published.
30 minutes on your demand data and how the Demand Planner shows a shortfall before it lands.
We use cookies to understand how the site is used and to connect form submissions to earlier visits. No analytics or marketing cookies are set until you choose. Privacy Policy