Maximo Open Forum

Experts,

I am back again with one more ask. Is anyone able to assist with the below?  Is this a candidate for Maximo Job Plan sequencing?  This would be a meter-based PM.  Job plans will be rewritten to incorporate previous JP tasks where needed. Trying to wrap our heads around this one.

The initial PM will fire PM/Job Plan JP 1000HRT19 at meter reading 1,000

Then, when the meter reading reaches 2,000, we need JP 2000HRT19 to generate

Then, when the meter reading reaches 3,000, generate JP 3000HRST19

When the meter reads 4000, generate JP 4000HRST19

At 5,000, generate 1000HRT19 again

Then at 6,000 generate 6000HRST19

At 7,000 start the entire sequence over again.

We set this up using the following sequence:

JP 1000HRT19 = 1

JP 2000HRT19 = 2

JP 3000HRT19 = 3

JP 4000HRT19 = 4

JP 6000HRT19 = 6

But this only works for the first cycle through, then the forecasting gets crazy due to the way sequencing is intended to function. Just want to make sure we aren't missing anything here. 

Thank you everyone for your assistance & time. 

#EverythingMaximo

------------------------------
Jess Schmitz
Projetech Inc.
------------------------------

I understand that the premise is that the cycle is 1-2-3-4-1-6 then 1-2-3-4-1-6 then 1-2-3-4-1-6, repeating.  So the quick answer is no.

The PM relies on the PM Counter to say which JP is due.  Remember, when the PM is generated it's always counter+1.  As an example, the current counter is 23 which means when generating the PM it will be 24.

Current counter + 1/sequence and if there is zero remainder, then that's the JP to be used, in this case, it is seq 1.  i.e. 24/6=8.and t will stop there.  Whereas if you had another JP with seq of 9 24/9 = 2.67 so that would not be the JP.

When you say that it then goes wild, that is not true as it's working done the sequences from highest to lowest.

Maximo will not repeat the pattern 1-2-3-4-1-6 way down the track.

In order to have this work you would have to either use an automation script that will reset the pm counter to 0 everytime the counter is set to 6 or be using  Maximo Asset Configuration Manager where there is a progressive inspection program (PIP).

------------------------------
Regards,
Craig Kokay
ISW
Maximo Practice Manager
eMail: ckokay@isw.net.au
Phone: +61-411-682-040

#IBMChampion2022
------------------------------

Hi Craig

thinking out loud. What if you'd made a small automation script that resets the pm counter to 0 when the max(jpsequence) is reached?
this would reinstate the first round of jobplans. Downside is that the pm counter is no longer a "life time counter", but I believe there are other ways to determine the pm history  

rgds, ruud 

------------------------------
ruud peters
vanderlande
------------------------------

Original Message:
Sent: 07-23-2022 00:34
From: Craig Kokay
Subject: Is this PM sequence a candidate for Maximo Job Plan sequencing?

I understand that the premise is that the cycle is 1-2-3-4-1-6 then 1-2-3-4-1-6 then 1-2-3-4-1-6, repeating.  So the quick answer is no.

The PM relies on the PM Counter to say which JP is due.  Remember, when the PM is generated it's always counter+1.  As an example, the current counter is 23 which means when generating the PM it will be 24.

Current counter + 1/sequence and if there is zero remainder, then that's the JP to be used, in this case, it is seq 1.  i.e. 24/6=8.and t will stop there.  Whereas if you had another JP with seq of 9 24/9 = 2.67 so that would not be the JP.

When you say that it then goes wild, that is not true as it's working done the sequences from highest to lowest.

Maximo will not repeat the pattern 1-2-3-4-1-6 way down the track.

In order to have this work you would have to either use an automation script that will reset the pm counter to 0 everytime the counter is set to 6 or be using  Maximo Asset Configuration Manager where there is a progressive inspection program (PIP).

------------------------------
Regards,
Craig Kokay
ISW
Maximo Practice Manager
eMail: ckokay@isw.net.au
Phone: +61-411-682-040

#IBMChampion2022
------------------------------

Hi Ruud,

I've already suggested the automation script or there is an alternative when using Maximo ACM.

As for the PM counter being useful as a lifetime counter is something I've never found to be of any use.  The main reason is that the PM counter can be reset anytime using the Set PM Counter menu action.  I have never heard of anyone using the PM counter for anything other than setting the point in the maintenance cycle the PM should be when initially created.  I say this because you might have PM sequence equating to monthly, six-monthly, annual and three-yearly and you are in fact one month past the second annual inspection.  This would require you to change the PM counter before you start generating the PM so the three-yearly is due in 11 months.

If anyone has found value in the PM counter, other than the above example, I would interested to hear the use case.

------------------------------
Regards,
Craig Kokay
ISW
Maximo Practice Manager
eMail: ckokay@isw.net.au
Phone: +61-411-682-040

#IBMChampion2022
------------------------------

Original Message:
Sent: 07-26-2022 00:51
From: ruud peters
Subject: Is this PM sequence a candidate for Maximo Job Plan sequencing?

Hi Craig

thinking out loud. What if you'd made a small automation script that resets the pm counter to 0 when the max(jpsequence) is reached?
this would reinstate the first round of jobplans. Downside is that the pm counter is no longer a "life time counter", but I believe there are other ways to determine the pm history  

rgds, ruud 

------------------------------
ruud peters
vanderlande
------------------------------


Original Message:
Sent: 07-23-2022 00:34
From: Craig Kokay
Subject: Is this PM sequence a candidate for Maximo Job Plan sequencing?

I understand that the premise is that the cycle is 1-2-3-4-1-6 then 1-2-3-4-1-6 then 1-2-3-4-1-6, repeating.  So the quick answer is no.

The PM relies on the PM Counter to say which JP is due.  Remember, when the PM is generated it's always counter+1.  As an example, the current counter is 23 which means when generating the PM it will be 24.

Current counter + 1/sequence and if there is zero remainder, then that's the JP to be used, in this case, it is seq 1.  i.e. 24/6=8.and t will stop there.  Whereas if you had another JP with seq of 9 24/9 = 2.67 so that would not be the JP.

When you say that it then goes wild, that is not true as it's working done the sequences from highest to lowest.

Maximo will not repeat the pattern 1-2-3-4-1-6 way down the track.

In order to have this work you would have to either use an automation script that will reset the pm counter to 0 everytime the counter is set to 6 or be using  Maximo Asset Configuration Manager where there is a progressive inspection program (PIP).

------------------------------
Regards,
Craig Kokay
ISW
Maximo Practice Manager
eMail: ckokay@isw.net.au
Phone: +61-411-682-040

#IBMChampion2022

Craig, 

Thank you for reaffirming and breaking down for me what I believed was going on with this ask. I am going to look into the mentioned add-on's as well. 

All,

Thank you for your time, attention and detailed responses around this ask. I really appreciate everyone's input and plan to look into the suggestions made around automation scripts and escalations. I am very impressed with this community and how many took the time to give their detailed assistance! 

Everyone has touched on some great options available to me and being educated around this will help me going forward as I continue to work with future PM's/JP's.  

Thank you for sharing your knowledge with me!


------------------------------
Jess Schmitz
Projetech Inc.
------------------------------

Original Message:
Sent: 07-23-2022 00:34
From: Craig Kokay
Subject: Is this PM sequence a candidate for Maximo Job Plan sequencing?

I understand that the premise is that the cycle is 1-2-3-4-1-6 then 1-2-3-4-1-6 then 1-2-3-4-1-6, repeating.  So the quick answer is no.

The PM relies on the PM Counter to say which JP is due.  Remember, when the PM is generated it's always counter+1.  As an example, the current counter is 23 which means when generating the PM it will be 24.

Current counter + 1/sequence and if there is zero remainder, then that's the JP to be used, in this case, it is seq 1.  i.e. 24/6=8.and t will stop there.  Whereas if you had another JP with seq of 9 24/9 = 2.67 so that would not be the JP.

When you say that it then goes wild, that is not true as it's working done the sequences from highest to lowest.

Maximo will not repeat the pattern 1-2-3-4-1-6 way down the track.

In order to have this work you would have to either use an automation script that will reset the pm counter to 0 everytime the counter is set to 6 or be using  Maximo Asset Configuration Manager where there is a progressive inspection program (PIP).

------------------------------
Regards,
Craig Kokay
ISW
Maximo Practice Manager
eMail: ckokay@isw.net.au
Phone: +61-411-682-040

#IBMChampion2022
------------------------------

can you duplicate 1000HRT19 for 5000HRT19?

------------------------------
keith simmons
Aquitas Solutions
------------------------------

Hi Keith,

That won't work as PM's don't repeat the the 1-2-3-4-1-6 pattern for a long while.  What's being asked is really to have a repeating pattern, sequencing is not like that as Maximo always starts with the current counter + 1, then divideds each JP sequence start from the largest sequence value into that result i.e. 24/6 = 4 with a remainder of 0, so it uses that JP against the sequence of 6.  Instead, if the counter is 27 + 1, then 28/6 = 4.67.  As there is a 0.67 remainder, it's not sequence 6, so it moves onto the next largest sequence being 4, so (27+1)/6 = 7.00 which means it will use that JP.

So, this is why your idea does not work.

Maximo for Transportation does have something that could also work.  It has PM relationships.  One thing that PM relationships do it activate/deactivate a PM(s) when the current PM is generated.

So you can set this up.
PM1 (JP1000) Active initially, when this is generated it will activate PM2 and inactivate itself
PM2 (JP2000) Inactive initially, when this is generated it will activate PM3 and inactivate itself
PM3 (JP3000) Inactive initially, when this is generated it will activate PM1 and inactivate itself

This is great where there are different frequencies or you only want to do the initial PM say at 1,000 km (once only), then the next fires at 5,000 km (once only), then it's at 15,000 km thereafter.  It would look like this:
PM1 (JP1000) Active, when this is generated it will activate PM2 and inactivate itself. Freq=1000 km
PM2 (JP6000) Inactive initially, when this is generated it will activate PM3 and inactivate itself. Freq=5000 km
PM3 (JP15000) Inactive initially, no other PM relationship is set. Freq=15,000 km

------------------------------
Regards,
Craig Kokay
ISW
Maximo Practice Manager
eMail: ckokay@isw.net.au
Phone: +61-411-682-040

#IBMChampion2022
------------------------------

Original Message:
Sent: 07-25-2022 16:55
From: keith simmons
Subject: Is this PM sequence a candidate for Maximo Job Plan sequencing?

can you duplicate 1000HRT19 for 5000HRT19?

------------------------------
keith simmons
Aquitas Solutions
------------------------------

Craig is correct; no amount of Sequencing is going to meet the stated requirements.

However, assuming the OP doesn't have the Transportation piece, what about an Escalation?  The main WHERE clause would just be

pmnum = 'yourpmnum'

And the first Escalation Point would have

WHERE pmcounter % 6 = 0 

and this would execute an Action to set the JPNUM to    JP 6000HRT19


Then the second Escalation Point would be 

WHERE pmcounter % 5 = 0 and pmcounter % 6 != 0

and this would execute an Action to set the JPNUM to  JP 1000HRT19

And keep following this pattern, until you have 6 Escalation Points firing 5 different actions.

HOWEVER. . .following that pattern, when you get to the last one, you'll probably run into an issue of having 2 Escalation Points firing the same action.  So, either wrap that 1 Action into 2 identical Action Groups and apply a different Action Group to each of the Escalation Points where it uses JP 1000HRT19, or combine those two Escalation Points with an OR statement.

So:
Esc. Pt. 1:   WHERE pmcounter % 6 = 0 and jpnum != '6000HRT19'
Action: SETVALUE of jpnum to 6000HRT19

Esc. Pt. 2:   WHERE (pmcounter % 5 = 0 and pmcounter % 6 != 0) OR (pmcounter % 2 != 0 and pmcounter % 3 != 0 and pmcounter % 4 != 0 and pmcounter % 5 != 0 and pmcounter % 6 != 0) and jpnum != '1000HRT19'
Action: SETVALUE of jpnum to 1000HRT19

Esc. Pt. 3:   WHERE pmcounter % 4 = 0 and pmcounter % 5 != 0 and pmcounter % 6 != 0 and jpnum != '4000HRT19'
Action: SETVALUE of jpnum to 4000HRT19

Esc. Pt. 4:   WHERE pmcounter % 3 = 0 and pmcounter % 4 != 0 and pmcounter % 5 != 0 and pmcounter % 6 != 0 and jpnum != '3000HRT19'
Action: SETVALUE of jpnum to 3000HRT19

Esc. Pt. 5:   WHERE pmcounter % 2 = 0 and pmcounter % 3 != 0 and pmcounter % 4 != 0 and pmcounter % 5 != 0 and pmcounter % 6 != 0 and jpnum != '2000HRT19'
Action: SETVALUE of jpnum to 2000HRT19




PS: I know my SQL there is overkill.  When the Escalation runs, Maximo will evaluate the Escalation Points in order and when it finds a match, it will perform the associated Action and/or Notification, and then won't evaluate against the other conditions.  So, for example, if the PMCounter = 24, in my setup above, it would execute against the first Escalation Point and stop; it wouldn't consider that it could also divide cleanly by 4, 3, and 2.  So, the clause     pmcounter % 6 != 0      doesn't HAVE TO be in the other WHERE clauses on the other Escalation Points, but it may help for readability.

PPS: Make sure you set the Escalation to run more frequently than the meter would possibly gain 1000 units.




------------------------------
Travis Herron
Pensacola Christian College
------------------------------

Original Message:
Sent: 07-25-2022 21:44
From: Craig Kokay
Subject: Is this PM sequence a candidate for Maximo Job Plan sequencing?

Hi Keith,

That won't work as PM's don't repeat the the 1-2-3-4-1-6 pattern for a long while.  What's being asked is really to have a repeating pattern, sequencing is not like that as Maximo always starts with the current counter + 1, then divideds each JP sequence start from the largest sequence value into that result i.e. 24/6 = 4 with a remainder of 0, so it uses that JP against the sequence of 6.  Instead, if the counter is 27 + 1, then 28/6 = 4.67.  As there is a 0.67 remainder, it's not sequence 6, so it moves onto the next largest sequence being 4, so (27+1)/6 = 7.00 which means it will use that JP.

So, this is why your idea does not work.

Maximo for Transportation does have something that could also work.  It has PM relationships.  One thing that PM relationships do it activate/deactivate a PM(s) when the current PM is generated.

So you can set this up.
PM1 (JP1000) Active initially, when this is generated it will activate PM2 and inactivate itself
PM2 (JP2000) Inactive initially, when this is generated it will activate PM3 and inactivate itself
PM3 (JP3000) Inactive initially, when this is generated it will activate PM1 and inactivate itself

This is great where there are different frequencies or you only want to do the initial PM say at 1,000 km (once only), then the next fires at 5,000 km (once only), then it's at 15,000 km thereafter.  It would look like this:
PM1 (JP1000) Active, when this is generated it will activate PM2 and inactivate itself. Freq=1000 km
PM2 (JP6000) Inactive initially, when this is generated it will activate PM3 and inactivate itself. Freq=5000 km
PM3 (JP15000) Inactive initially, no other PM relationship is set. Freq=15,000 km

------------------------------
Regards,
Craig Kokay
ISW
Maximo Practice Manager
eMail: ckokay@isw.net.au
Phone: +61-411-682-040

#IBMChampion2022
------------------------------


Original Message:
Sent: 07-25-2022 16:55
From: keith simmons
Subject: Is this PM sequence a candidate for Maximo Job Plan sequencing?

can you duplicate 1000HRT19 for 5000HRT19?

------------------------------
keith simmons
Aquitas Solutions

based on what I have heard so far, and really not getting to deep, I would likely explore adding a new attribute(s) to pm's and executing a cron script state machine to address providing a method to express scheduling that does not depend on periodic frequency. I would likely look at modifying the state of the underlying PM record/objects to leverage as much base functionality as possible. I wouldn't expect the forecast tool to work correctly... (I would likely spend way too much time on a solution :-) )

------------------------------
keith simmons
Aquitas Solutions
------------------------------

Hi Keith,

As I started my reply as a confused person, I had an ah-hah moment.

Firstly, can you reduce my confusion around your statement "that does not depend on periodic frequency".  An example would be great.

My ah-hah moment was reflecting on the solution I have given where the PM counter is reset after reaching the max(sequence).  This does not assist with the forecast so that it matches.  I haven't looked into how the forecasting can be altered to also 'reset' the counter.  Well I did just look and hopefully, it should be the LTDPMCOUNT field in the PMFORECASTJP object



------------------------------
Regards,
Craig Kokay
ISW
Maximo Practice Manager
eMail: ckokay@isw.net.au
Phone: +61-411-682-040

#IBMChampion2022
------------------------------

Original Message:
Sent: 07-26-2022 10:34
From: keith simmons
Subject: Is this PM sequence a candidate for Maximo Job Plan sequencing?

based on what I have heard so far, and really not getting to deep, I would likely explore adding a new attribute(s) to pm's and executing a cron script state machine to address providing a method to express scheduling that does not depend on periodic frequency. I would likely look at modifying the state of the underlying PM record/objects to leverage as much base functionality as possible. I wouldn't expect the forecast tool to work correctly... (I would likely spend way too much time on a solution :-) )

------------------------------
keith simmons
Aquitas Solutions
------------------------------