If we have over 100 WOs with the same target start date, does the Scheduler product expect us to manually drag the WOs across to a number of days to match the craft availability ?  (no optimization available in this instance)

Good afternoon, Tom

Short answer = Yes.

With such a large volume, it may be correct that you have generated (PMs?) these to occur on the same date.  Without the optimization engine, the spreading out of the workload is your job.  How else do you expect Maximo to know that you're overloaded?  But are you?

If you have 80 hours of work for one day, and have 10 tradespeople that match the craft requirements, then you are not overloaded.

If you have established some sort of relationship between the work orders using a work order hierarchy and or using precedence/successor, then initially you can use the CPM method.

One thing you should look at, if these are PM-based, is how you have spread the PMs in the first place.  There are companies that do a once-a-month PM run, causing all the resulting work orders to start on the 1st of the month, and then manually move the scheduling dates.  I am not keen on this method.

You still, no matter what, are the optimization engine if you have not installed one.

If we have over 100 WOs with the same target start date, does the Scheduler product expect us to manually drag the WOs across to a number of days to match the craft availability ?  (no optimization available in this instance)

Good afternoon, Tom

Short answer = Yes.

With such a large volume, it may be correct that you have generated (PMs?) these to occur on the same date.  Without the optimization engine, the spreading out of the workload is your job.  How else do you expect Maximo to know that you're overloaded?  But are you?

If you have 80 hours of work for one day, and have 10 tradespeople that match the craft requirements, then you are not overloaded.

If you have established some sort of relationship between the work orders using a work order hierarchy and or using precedence/successor, then initially you can use the CPM method.

One thing you should look at, if these are PM-based, is how you have spread the PMs in the first place.  There are companies that do a once-a-month PM run, causing all the resulting work orders to start on the 1st of the month, and then manually move the scheduling dates.  I am not keen on this method.

You still, no matter what, are the optimization engine if you have not installed one.

If we have over 100 WOs with the same target start date, does the Scheduler product expect us to manually drag the WOs across to a number of days to match the craft availability ?  (no optimization available in this instance)

HI Craig, is it possible to determine and define a critical path within a PM hierarchy? If so, is there an abundance of documentation on how this is achieved?

Good afternoon, Tom

Short answer = Yes.

With such a large volume, it may be correct that you have generated (PMs?) these to occur on the same date.  Without the optimization engine, the spreading out of the workload is your job.  How else do you expect Maximo to know that you're overloaded?  But are you?

If you have 80 hours of work for one day, and have 10 tradespeople that match the craft requirements, then you are not overloaded.

If you have established some sort of relationship between the work orders using a work order hierarchy and or using precedence/successor, then initially you can use the CPM method.

One thing you should look at, if these are PM-based, is how you have spread the PMs in the first place.  There are companies that do a once-a-month PM run, causing all the resulting work orders to start on the 1st of the month, and then manually move the scheduling dates.  I am not keen on this method.

You still, no matter what, are the optimization engine if you have not installed one.

If we have over 100 WOs with the same target start date, does the Scheduler product expect us to manually drag the WOs across to a number of days to match the craft availability ?  (no optimization available in this instance)