We are using APPs 10 and trying to schedule operations in sequence so they do not plan to start in parallel. We have created a new work centre which only has one operations that travels through the work centre, set the ‘ concurrent operations’ to NOT Allowed - Group start in sequence (work centre below)
when the MRP schedules the operations it plans for the operations to start before the previous operation is finished. In the routing there is 0 Overlap and a crew size of 1, its physically impossible to do this, why is the system scheduling in this way?
regards
Jamie
Page 1 / 1
The setting in Shop Floor Reporting Settings for Concurrent Operations has no effect on the scheduling of operations. This setting simply determines if 1) clocking onto concurrent operations is permissible in this WC (Allowed/Not Allowed) and 2) when multiple operations in the WC are started simultaneously, should they use the same clocking sequence ID (Group Start in Sequence) or different clocking sequence IDs (Group Start in Parallel).
The Start/Finish dates in the Operations per Work Centre are calculated by the infinite scheduling logic based on the Need Dates of each shop order requisition.
Not sure, though, how the operations on some requisitions are scheduled to end at 08:00 and others are scheduled to end at 13:30 on the same date, unless you are using an Order Gap Time.
Also, how many resources are in this Work Center, and are you using APB or CBS for finite scheduling?
EDIT: never mind this, these are all requisitions.
Hi Matt
all operations are backwards scheduled and the inventory parts has a 1 day shop order time gap to level out the supply of inventory.
on the resource tab we only have one resource in the work centre.
could it be to do with the labour class in the routing as we use labour class CTSW were we have 5 employees linked to? (see below)
