Maximo Open Forum

 View Only
  • 1.  Questions about Job Plans, Tasks, and Responsibilities

    Posted 10-06-2021 13:58
    I'm experimenting with Job Plans.  Why is it that the Plan has the whole assortment of options in the Responsibility section (Supervisor, Owner, Owner Group, Lead, Work Group, Crew Work Group, and Crew), but at the Task level there are only options for Owner, Owner Group, and Crew Work Group?

    Case in point: I was making a Job Plan for repairing a hole in a wall.  This would have two Tasks, one to repair the drywall, to be done by our Construction team; the second to paint, by our painting team.  And I want to establish precedence -- the painting can't start until the drywall patch is done.  So ideally, we could create a Work Order, apply the Job Plan, and that would instantly have two Tasks, properly "assigned" to Owner Group and Work Group (and if the Work Group in turn sets the Lead, fine).  This hierarchy is Flow Controlled to prevent trying to start the painting Task before the drywall Task is done.

    Typically when we will out responsibility fields for a Work Order we use an Owner Group, a Work Group, and a Lead.  So here on the Job Plan, I want the first Task to have both an Owner Group and a Work Group.  I can get the Owner Group well enough, but a Work Group?  I could MAYBE get that with a Flow Action, but (so says the Field Help) that fires when the WO Task is started.  I'd need it when the WO Task is created.

    I thought my solution was going to be a Nested Job Plan, but it appears that if you use a Nested Job Plan you can't use Flow Control to establish precedence.

    How do I get to my dream state, without relying on scripting or on a job planner/scheduler person to process this properly?  Or, why didn't they just add ALL the responsibility fields to the Job Plan Task level when they expanded this to include Owner & Owner Group, circa Maximo v.6?
    #EverythingMaximo
    #WorkManagement

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


  • 2.  RE: Questions about Job Plans, Tasks, and Responsibilities

    Posted 10-07-2021 22:36
    I can't honestly say "why" it is this way. My guess is they expected fewer changes at the task level. For example, the odds that the supervisor changes from the main WO to the task is probably rather small. What I would do in this situation is add custom attributes on JOBTASK for the ones you want to set (LABORCODE/LEAD for example) and use a crossover domain that you associate to the JOBTASKID attribute on WORKORDER. That way when the WO is created those fields will come over.

    ------------------------------
    Steven Shull
    IBM
    ------------------------------