This idea is to offer a simplified method of scheduling using what is called "Duration based" scheduling for those companies that do not do finite scheduling. This offers the scheduling to offer more of a block scheduling window for each operation instead of minute by minute scheduling like the current scheduling engine offers.
This is an intriguing idea. We could see this working in combination with the classic method. Our initial operations are very variable and could be done this way with only minor concern for overload. Our subsequent operations are labor intensive, complicated, and potentially very long - so they are bottlenecks and would need to be scheduled down to the hour/minute including some queue times. I like the idea, and Iād like to hear what some others think.
Now, if we could just get operations to ācontinueā across operator (P-type resources) shifts - then the scheduler would be perfect for us.
In my world, if we did this, each operation could have an option on how it is scheduledā¦ so op 10 could be duration based, and op 20 could be work based. best of both worlds.
Another SAMPLE USE of this type of scheduling came from a customer. They had an operation that was defined as āget permitsā where they had to get the permits from the city to perform the work. The permit process took a DURATION of 14 days, but the actual āworkā was only a couple of hoursā¦ but those hours were scattered across the 14 days, so there was no really good way to schedule the work. IN that case, we did create a BPM to āadjustā the scheduled start and end date on the operation, while allowing the hours to drive the cost.