Hi Team,We noticed that when we would Refresh the PRD, the Backflush would schedule EVERY item to end at the Due date and flow backwards even if they go through the same work center (see two lines below). However our Work Center Capacity is currently set at 1, which to me would mean that it would only be able to process one item at a time and thus the items should be staggered in serial, not stacked in parallel. Would you happen to know why the jobs are scheduling on top of each other even though our Work Center Capacities are set to 1?One thing I have determined is that the issue seems to be with Items who only have an interaction in a Work Center. If items have a component/sub-component relationship, then they are correctly scheduling the sub-component to be completed before the component can starts its routing (See below, the sub-component ASWP is correctly scheduled before the finished components ASWK & ASWP).However the ASWK and ASWT are scheduled to start and finish at the same time. They both share the same Work Center, and can be completed in any order, but the Work Center should only be able to do 1 at a time (e.g. Capacity = 1?)
NAV/BC thinks of infinite capacity when looking at Routing and applying to MPS. So how to you crate capacity constraints. Follow these steps:
You must set up production resources that you regard as critical and mark them to accept a finite load instead of the default infinite load that other production resources accept. A capacity-constrained resource can be a work center or machine center that you have identified as a bottleneck and would like to establish a limited, finite load for.
NAV/Business Central does not support detailed shop floor control. It plans for a feasible utilization of resources by providing a rough-cut schedule, but it does not automatically create and maintain detailed schedules based on priorities or optimization rules.
On the Capacity-Constrained Resources page, you can make setup that avoids overload of specific resources and ensure that no capacity is left unallocated if it could increase the turn-around time of a production order. In the Dampener (% of Total Capacity) field, you can add dampener time to resources to minimize operation splitting. This enables the system to schedule load on the last possible day by exceeding the critical load percent slightly if this can reduce the number of operations that are split.
When planning with capacity-constrained resources, the system ensures that no resource is loaded above its defined capacity (critical load). This is done by assigning each operation to the nearest available time slot. If the time slot is not big enough to complete the entire operation, then the operation will be split into two or more parts placed in the nearest available time slots.
Note: Operations on work centers or machine centers that are set up as constrained resources will always be planned serially. This means that if a constrained resource has multiple capacities, then those capacities can only be planned in sequence, not in parallel as they would be if the work or machine center was not set up as a constrained resource. In a constrained resource, the Capacity field on the work center or machine center is greater than 1. In case of operation splitting, the setup time is only assigned once because it is assumed that some manual adjustment is done to optimize the schedule.
make sure your Shop Calendars are calculated to apply parameters.
Hope this helps.