Job Plan Sequences: (semi) Simple Explanation

Job Plan sequences are very cool once you figure them out.  Here’s the basic rundown (assuming you know how to create a PM, and a JOBPLAN, and how to create a WO from a PM).  On each PM is a counter called, oddly enough, “counter.”  This increments each time the PM generates a work order and decrements each time said work order is cancelled.  So basically it shows how many work orders have been processed from the PM.

Say I have a piece of equipment that I need to maintain throughout the year, but some of the things I need to do are monthly, some semiannually (6 month) and some are every year.  Then, I also have a 5 year inspection to do.

Here’s how I would handle this:

  • JP_monthly:  This is my monthly job plan; a basic inspection.
  • JP_semiannual: This is my 6-month maintenance. *Be sure to add the steps from JP_monthly as the inspection needs to be done at the 6 month point as well
  • JP_annual: This is the big maintenance I need to do each year. *Add the monthly to this as well if required.
  • JP_5year: This is my 5-year inspection.  *Be sure to add all steps from the yearly maintenance.

So now here’s how you set up the sequence:

  • *my pm’s counter is a month in this example as it runs on a schedule of monthly
  • JP_monthly: Sequence=1 (i.e. run each count [month] or when no higher sequence runs)
  • JP_semiannual: Sequence=6 (i.e. run each 6 counts[6 months]or when no higher sequence runs)
  • JP_annual: Sequence=12 (i.e. run each 12 counts [year] or when no higher sequence runs)
  • JP_5year: Sequence=60 (i.e. run each 60 counts [5 years] or when no higher sequence runs)

now let say this is a new PM so the counter=0

I want this to start at the annual job plan.  You can manually set the pm counter from the Select Action menu to 11. It will increment to 12 and then use Sequence 12 next time it creates a work order.

Now here’s a little thing to keep in mind.  If you have a PM that needs to run weekly, your basic count will be a week.  The real issue here is going to be that a month is not equal to 4 weeks for all months.  You will have to define a month as an integer multiple of weeks.  So we’re going to call our monthly a 4-week interval.

If we added that to the above list, then things change on the sequences as follows

  • jp_weekly: Sequence=1
  • jp_monthly: Sequence=4 ( again, this is a potential problem, there will be gaps)
  • jp_semiannual: Sequence=26 (this is half a year) or Sequence=24 (6*4weeks there will be a gap each year)
  • jp_annual: Sequence=52 (52 weeks=1 year)
  • jp_5year: Sequence=260 (52weeks*5)

The same would work for PMs that run on yearly schedules:

  • Yearly, 2 year, 5 year for example.
  • Sequences would be 1,2,5.

The system figures out which JP applies based on the counter and sequence:  The JP applying is the highest Sequence where COUNTER/SEQUENCE is an Integer.

Finally, you can “View Sequence” from the Select Action Menu to see what will happen in the future.


Weekly Schedule:

  • week sequence=1
  • month sequence=?
  • quarterly sequence=13
  • semiannual sequence=26
  • yearly sequence=52

Monthly Schedule:

  • month sequence=1
  • quarter sequence=3
  • semiannual sequence=6
  • annual sequence=12

Yearly Schedule:

  • annual sequence=1
  • 2 year sequence=2
  • 5 year sequence=5

Did You Know...

As Maximo Experts, we have developed several add-on products for Maximo that mobilize the work force, simplifies assignments, provides ad-hoc reporting capabilities and facilitates the seamless integration of Service Requests into Maximo.

Check out our products by clicking on the following links: EZMaxMobile, EZMaxPlanner and EZMaxRequest.

Find Out More

5 thoughts on “Job Plan Sequences: (semi) Simple Explanation

  1. Hi David. I have a question about job plan sequencing. If you have multiple different JP’s on a PM, then the PM description will have to be generic. i.e. You cant call the PM annual overhaul if using multiple JP’s. Therefore when the PM generates the WO, the WO will also only have a generic name. Is there a simple solution to make the WO descriptive of the tasks involved without adding JP Description to the list view of wotrack? Thank you for your time.

    1. I’ve had the same issue. I’d like to see text you can append to the end of the PM description as part of the job plan sequence. Another idea is to be able to use variable tags like job plan name or job plan description.

  2. Thanks for sharing the bit about weekly job plan sequence. I learned that Maximo only likes integers in the sequence number, so I have to use either 4 weeks or 5 weeks for a monthly PM that also has a weekly PM.

    My other gripe is with nested job plans. I feel like there should be a way to create PM WOs like we did before nested job plans. Perhaps all nested job plans task ids get rolled up into a single PM WO so you can avoid child work orders.

  3. So, its basically a GCD(Greatest Common Divisor) of the job plan sequence. Any idea to use the same concept on PMs instead of jobplans?

Leave a Reply