Maximo Open Forum

Hello all,  currently we use Person Groups on Job Plans to categorize work in start centers.

I would like to remove person groups from the job plan because it limits the re-usability of that job plan across sites/organizations.

We could use the work group on the PM instead, but I was curious if anyone had any other ideas that I may not have thought of.

The goal is to begin using Job Plans without a site or org since we use similar equipment globally.

Thank you,

#Administration
#EndUser
#EverythingMaximo
#WorkCenters
#WorkManagement

------------------------------
Danny Richardson
Maximo Administrator Manager
Technimark LLC
------------------------------

This IBM documentation may point you in the right direction: https://www.ibm.com/docs/en/maximo-for-aviation/cd?topic=application-assigning-work&utm

------------------------------
Lucas Pletz
Naviam
------------------------------

Danny, if the persongroup values were useful as an organizing framework but you want to eliminate the restrictive impact of populating that field on jobplan, you could create a user defined field to carry the same information on the job plan and then clear out the persongroup field. If you need a completely different organizing framework for the job plans and classtructureid does not do the trick, you could create an ALN domain for your new field and use it alone or perhaps in combination with classtructureid.

------------------------------
Nancy Lerner
Brio Consulting
------------------------------

Hi Danny, we removed the person group from the JP and only use the Work Group on the PM.

Reasoning; staff changes in each department and flexibility to alter the assigned person at the drop of a hat. 

We use, Garage, Electrical, General Hand, Engineer, Contractor, Mechanic, Apprentice.

Regards, Greg. 

------------------------------
Greg Dyer
Port Nelson Ltd
------------------------------

Hi Danny,

Excellent idea of making the JP's agnostic unless there is a need to make it specific to the org/site, but then again, you can do that on the task and resources anyway.

Moving the Work Group to the PM does make sense; however, please note that although the person group is at the system level, the team members can be made specific to the org/site if needed.  I have seen this work very successfully.  In other words, you can have the one team say MAINT, but the make-up of that team varies based on the org/site set, and of course, if you don't use the org/site that team member works across all org/sites.

You also talk about reusability, but what does that mean?  If you define on the JP that the work group is MAINT, are you saying that you have a different person group set up, like MAINT-OP, MAINT-AB where OP and AB are different sites?  Therefore, you couldn't make the JP agnostic and would have to have duplicates.  But using the feature that I have pointed of a) yes, make the JP agnostic b) use the org/site feature for the team member on the person group, means you can reduce the number of person groups.

Either way will work.

------------------------------
Craig Kokay
Principal Consultant
COSOL

email: craig.kokay@cosol.global
#IBMChampion
------------------------------