Topic: Build Start/End Dates
|By: Guest||Posted on: Nov 18 2020 at 02:08:46 AM|
I would like to check i am entering WO's correctly.
I have an sub assembly (CSAS)order that has a build date of 11/11. The job will take around a week to complete.
I have another WO for the top level product, that requires this sub assembly, with a build date of the 20/11.
When running the shortage forecast report, the WO due on the 11th is shown at the bottom of the list for that item, the requirement for the top level is at the top, so it shows as overdue.
Why is the 11/11 at the bottom of the list, is build date the expected complete date or the start date (if it's the complete date, component requirements would not be ordered on time)?
|By: Support||Posted on: Nov 18 2020 at 03:37:59 AM|
|I understand your question - please give me some time to look at this more closely before posting a definitive answer.|
|By: Guest||Posted on: Nov 18 2020 at 03:43:01 AM|
|Just to add, i can now see that if i add a supplier lead time this is added to the shortage report order by date, but again, if the WO's build date is based on completion date - Minimrp does not know how long it takes to build the WO, so the component lead time does not really mean anything.|
If the build date is based on start date, as soon as you go past this start date, Minimrp will show the shortage report for that item, in the wrong order.
|By: Support||Posted on: Nov 18 2020 at 11:09:59 AM|
|You are correct - the 'Build Date' is the date that it expects you to take the components from your inventory to start building. The Build Date is used, with the components' lead times, to generate shortage reports for the components that will be required to build the sub assembly.|
The confusion arises because, in the case of CSAS assemblies, they are treated by the Top Level as components but we don't actually have an expected "Arrival" date for them.
But leave this with me a while longer to see if there's any way to include a 'completion' date or some kind of lead time into a CSAS work order without adding more complexity to MiniMRP.
I will add though that you're the first person in 25 years to ever mention this so I can only assume that most users finish their CSAS builds on the same day - or quick enough that it doesn't matter - or they're ahhpy enpugh to accept the limitation because, after all, MiniMRP is not intended to be a fully loaded ERP/MRP system and it does have limitations. This may end up being one of those limitations that users accept. or not.
But. As I said. I'll take a look and if it's a simple tweak I'll see what we can do about it.
|By: Guest||Posted on: Nov 20 2020 at 05:05:48 AM|
|I understand, we will wait and see if you are able to add anything.|
|By: Support||Posted on: Nov 21 2020 at 05:02:50 AM|
|I just wanted to come back and say that we haven't forgotten about this.|
Looking back at the original post at the top of ths page I'd say there's two separate issues here.
Let's ignore, for a moment, the discussion about different Work Order "Start" and "End" dates. I want to explain why In the current version you see your work order for the 11/Nov BELOW the work order for 24th/Nov. You obviously expected the WorkOrders to appear in date order.
The shortage forecast is based around those two columns "Qty required" and "Qty On Order". In other words "Demand" and "Supply". The events are then sorted in Date order.
Normally you would be correct. If a demand is scheduled to be served by a supply of the necessary quantity then there's no shortage and the rows do not appear in the report at all.
But. If you run the report and any scheduled 'Supply' date was missed (The supply did not occur on the scheduled date) then MiniMRP can not know when the supply will occur (or if it ever occur?). The scheduled supply date is in the past. It can't be trusted so the date must be ignored. Worst case scenario is assumed and the supply is placed at the bottom after all demands so as to force a shortage drawing your attention to the problem.
as I said above. If you had looked at the report on, say, the 10th, then those work orders would not have appeared in the report at all. They do appear in the report because the scheduled supply date is in the past and you have a potential problem.
|By: Support||Posted on: Nov 21 2020 at 05:09:06 AM|
|That other issue where we discussed having separate Start date and scheduled completion date.|
I will say that if, in a future update, we did allow separate start and completion dates then the report would still show overdue work orders at the bottom, forcing a shortage, if the scheduled completion date is in the past.
Anyway. We're still looking at this. I'll come back when I have more to say about it.
|By: Guest||Posted on: Nov 22 2020 at 06:39:24 AM|
|Thankyou for looking into this.|
I totally understand what you have explained. If the sub assembly had a build time calculated (from a unit time, like a lead time) then this could be added to the required date, and if the works orders are then overdue, you could correctly re-schedule them making everything align, obviously currently that would not help.
|By: Support||Posted on: Dec 22 2020 at 05:44:52 AM|
|Work Orders different start/end dates.|
This has now been done.
|By: Guest||Posted on: Dec 22 2020 at 06:56:24 AM|
|Fantastic - thats a great improvement.|
Thankyou for adding this.
|By: Support||Posted on: Dec 23 2020 at 05:33:25 AM|
|Although somebody told me a couple of days ago that the date selectors for the start and end dates didn't work as smoothly as they should. Something about the Left[<] and Right[>] arrows to scroll months.|
Work on that should be in progress. I need to check how that's going.
In the meantime. If you have that problem. To scroll a few months just click on the actual month word and it zooms out allowing you to pick any month with a single click. Quicker than clicking the arrow button to step a month at a time.
But. As I said. will check that left/right arrow thing and have an update released if necesary
Reply - add a comment to this topic.
You may enter letters, numbers and standard punctuation only. HTML and other scripts/tags will be rejected.