Hello. My work is trying to update AX to match our build plan but we are running into some roadblocks.
We have a product that runs through a machine with a runtime of 60 minutes. That 60 minutes is the same whether we run 1 or 120 of the product.
When we release a quantity of 1, AX spits out a start time of (let’s say) 1:00 pm and an end time of 2:00 pm.
If we release an order of 5, AX spits our a start of 1:00 pm and an end of 11:00 pm. This gets even more difficult when we hit orders of 100+. In either scenario, it should show a start of 1pm and end of 2 pm.
The “finite” box is not checked on the resources for this but it still extends the run time. How do I get AX to “ignore” quantity or give the same runtime regardless of quantity?
Hello, AXNoob!
Infinite capacity (scheduling) does not mean that lead time is ignored. With infinite scheduling the capacity requirements of other production orders IS ignored, so every production order is scheduled as if there were no other production orders. Lead time of the production order itself is considered, as well as open and closed calendar periods.
In order to always use fixed lead time you need to adjust Formula field on route operation(s). It sounds like you have been using ‘Standard’ value but you should change it to ‘Batch’, for instance (‘Resource batch’ is also an option). Then in Process quantity field specify value of 120 (or whatever is your biggest batch that can be run at once). With this, if you schedule anything up to 120 the lead time will be always the same. With production order quantity 121-240 two batches are required, meaning two hours in your example.
1 Like
Hi, AXNoob,
It sounds like it’s planning for 100 minutes run time per pc (not per batch), which is the way the system is designed. One workaround could be to utilize the Setup Time instead of the Run Time which would then calculate the 100 minutes once (per batch, not per pc) no matter how many quantities you have.
Thank you! I will give this a try and see how it works.
Mike_Swartzentruber,
Question for you based on your reply. How does the system handle varying resources? For example, if I have 100 people vs 1 person. The total runtime should change since I have more resources to complete it, right?
It is still 100 minutes of labor, but it can be completed in 1 (from 12:00 to 12:01) minute since there are 100 people. If there are 50 people, it would be 100 minutes of labor but completed in 2 (12:00 to 12:02) calendar minutes.
Hi,
That’s a good question that I would simply set up the system both ways and see what it produces. I’m sorry but can’t speak to that exact scenario. I would be curious what happens…