You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From testing myself, thinking about needs during their season, and then discussion with the users: We will want a version of this during the season, as actual events are entered. At each stage of the supply chain, they will want to re-schedule forward based on what actually happened at the last completed stage.
This should be done based on the relative quantities in the plan, not based on the recipe.
I think we could start with a schedule forward one stage at a time, rather than the whole plan. Or both. But one stage at a time is not that hard for users.
There are details to be worked out:
should the option be by column (process specification) or by input or output column?
should it only be allowed starting at the last column with events entered? If not, what are the rules where events have been entered?
This issue includes both supply-driven and demand-driven recalculations now. They can probably be done in the same manner, with consistent UX. More design needed.
1 week
This need some discussion with the users, including if to do it, how to do it, and the priority.
The text was updated successfully, but these errors were encountered: