Hi All,


if CrewType is chosen on JobPlan, Maximo's default behaviour is to explicitly set Quantity to 1.
I managed to change that behaviour, and now I am able to edit the Quantity on JobPlan.
(achieved via an automation script on JOBLABOR.AMCREWTYPE).

However, when the JobPlan is applied to a WO, it still explicitly sets the QUANTITY for CrewType as 1 on WPLABOR.
I wrote a script for run action on attribute JPNUM for WORKORDER, however it hasn't solved the issue, possibly because
there is no foreign key from JOBLABOR to WPLABOR.

Has anyone encountered this before or can think of a reason as to why IBM has designed and implemented crew types
in this fashion?
#AssetandFacilitiesManagement
#Maximo

Crew Type is defined in the Crew Type application.  If you need a larger crew for the work to be done then redefine the crew in the Crew Type application and use that redefined crew for the job.  A job will use a crew.  If the job requires two crews, then make the definition for the two crews into a single crew and choose the newly defined crew for the job required. @Andrew Jeffery does a really nice job of explaining crew types here.

------------------------------
Bradley K. Downing , MBA
IBM Certified Adv. Deployment Prof. Maximo v7.6.1
IBM
Bakersfield CA
------------------------------

"Why would I need more than 1 of a Crew Type?" Maybe replacing the light poles on a street is a good example. It sounds like you want to have 1 WO with a Planned Labor for a Crew Type of Light Pole and Quantity 5. The implication here is that the crews will sort themselves out with regard to which poles should be replaced by which crew. I think it would be better planning to have a Parent WO for replacing the lights on the street with a Child WO for each individual pole, and then each Child WO would only need 1 of the Light Pole Crew Type in its Planned Labor.

Using this example, I think the reason IBM "designed and implemented crew types in this fashion" was to promote good planning.

------------------------------
Blessings,
Jason Uppenborn
Sr. Technical Maximo Consultant
Ontracks Consulting
------------------------------

Thank you @Bradley Downing and @Jason Uppenborn.

So it would appear that this requires more of a functional solution than a technical one.

@Steven Shull  any thoughts?​

------------------------------
K Kunnuthara
------------------------------

Trying to go against Maximo intended design is often fraught with issues where you can spend a significant amount time trying to keep it working and/or troubleshooting issues that arose. Especially when it comes to determining if it's your customization or Maximo that is at fault. And then down the road someone could decide to wipe it all out as they want to get Maximo closer to out of box. We see this quite a bit where organizations heavily customized Maximo to try and adjust Maximo to their business processes instead of tweaking their business processes to better align with Maximo which made upgrading difficult so they didn't do it. Quite often we've seen organizations basically obliterate it and start over (just loading their data into a new system). I definitely see this more of a functional review of how you're using crews and agree with Jason & Bradley on this.

If you're adamant you want to do this, I would look at using joblaborid on WPLABOR as your crossover event as you should be able to retrieve the quantity from the record that way. We've used it to cross over other fields in the past.

------------------------------
Steven Shull
Director of Development
Projetech Inc
Cincinnati OH
------------------------------

Original Message:
Sent: Fri July 03, 2020 01:25 AM
From: K Kunnuthara
Subject: CrewType Quantity

Thank you @Bradley Downing and @Jason Uppenborn.

So it would appear that this requires more of a functional solution than a technical one.

@Steven Shull  any thoughts?​

------------------------------
K Kunnuthara
------------------------------

@Steven Shull
Thank you for those inputs.

Yes, I am speaking with the schedulers at this client to see how we could avoid customizations​ for this issue.

------------------------------
K Kunnuthara
------------------------------