CRP back scheduling

eabalon

New Member
Version MFG/Pro eB

I set up a work center with 9 machines and 1 op/mach. The work center capacity for 2 shifts is 9 x 16hrs = 144.

I have a work order with order date and release date = today while due date = tomorrow. The total operation run time to produce the order qty (based on the routing) is 126.

I run 24.1 then check Work center Load summary. The 1st operation was scheduled to start a day before the due date while the rest of the operation was scheduled on the due date. The work center can accomodate the order qty in just 1 day, why does CRP do back schedule?
 
Version MFG/Pro eB

I set up a work center with 9 machines and 1 op/mach. The work center capacity for 2 shifts is 9 x 16hrs = 144.

I have a work order with order date and release date = today while due date = tomorrow. The total operation run time to produce the order qty (based on the routing) is 126.

I run 24.1 then check Work center Load summary. The 1st operation was scheduled to start a day before the due date while the rest of the operation was scheduled on the due date. The work center can accomodate the order qty in just 1 day, why does CRP do back schedule?
Since you entered the WO today and released it today the system consumed the remaining hours of today and then what was left it put into tomorrow because the release date was today. If you change your release date to tomorrow things should come right.

I know that if today is Thursday the 4th and you add a WO with a due date of Thursday the 4th and the routing says it will take 3 days to build, CRP will back schedule it to Monday the 1st. It is how the functionality works. I think QAD assumes you won't do something like that or if you do, the problem becomes visible and you fix it.
 
Back
Top