No Capacity Interruption

 

The command No Capacity Interruption makes sure that when the current resource is scheduled to start, the capacity is available to start on time. Valid interruptions are non-working times for the resource, such as shifts or weekends where the resource is unavailable.  No Capacity Interruption is a checkbox in the Operations Grid.

 

As an example, a job has the following operations:

 

Ident   No Cap Interrupt       Status

10                                           

20      Yes

30      Yes

40      Yes

50

 

When the above job is scheduled, there cannot be a capacity Interruption between the following operations:

 

10 and 20

20 and 30

30 and 40

 

The scheduler would need to find where there is open capacity to meet the above rules and thus may need to move all the operation start times around. 

 

If an operation is in process and is a No Capacity Interruption as in the example below:

 

Ident   No Cap Interrupt       Status

10                               I                                              

20      Yes

30      Yes

40      Yes

50

 

The above rule for scheduling No Capacity Interruption still applies, so if operation 10 is loaded first as it is in process, 20 to 40 must also be loaded immediately following operation 10 to ensure there are no capacity gaps.  If, for some reason, there is a capacity interruption between any of the operations 10 through 40, the schedule cannot resolve the conflict as it is being forced to schedule the operations at fixed times because 10 is in process.  Therefore, the scheduler will still schedule the operations even if there is a capacity gap, and will warn the user with a message to the schedule log. 

 

If operation 10 is completed and operation 20 is not in process as in:

 

Ident   No Cap Interrupt       Status

10                               C                                            

20      Yes

30      Yes

40      Yes

50

 

The scheduler would assume that 20 is in process because there should not be a gap between 10 and 20 even though 10 has completed. 

 

In the example below, the operations are started out of sequence:

 

Ident   No Cap Interrupt       Status

10                                                                                         

20      Yes                      I

30      Yes

40      Yes

50

 

In this case, the scheduler cannot resolve the conflict.  For example, the first day of the schedule is Monday and operation10 starts on Wednesday, but 20 says it is in process and must be started on the first day of the schedule – Monday.  In this case, the scheduler would schedule operations 30 and 40 after operations 20.  10 would be the rogue operation (possible because someone forgot to set it as I or C) and a warning message would be printed to the schedule log.