Maximo Open Forum

 View Only

  • 1.  Can you restrict WO visibility based on status?

    Posted 12 days ago

    Folks - We are having an issue with techs grabbing work orders that have not yet been approved to them or scheduled out and completing them outside their assigned work. I know, it sounds like it would be a good "problem" to have, but when new, "easier" jobs are being done almost immediately and there are 165 other WO's in the craft's backlog that existed WAY before this new request came in, it's an issue.

    I'm wondering if there's a permissions setting in the Security Groups application that would allow us to restrict a technician from finding a Work Order that's in any other status except 'APPR', for example?

    Thanks in advance,
    Amy Briggs
    The Jackson Laboratory
    Bar Harbor, ME 


    #EverythingMaximo
    #MaximoUserGroups
    #WorkManagement

    ------------------------------
    Amy Briggs
    Maintenance Planner
    The Jackson Laboratory
    Bar Harbor, ME
    207-288-6356
    ------------------------------


  • 2.  RE: Can you restrict WO visibility based on status?

    Posted 12 days ago

    You could accomplish this a few different ways in Maximo. If they have their own application for executing the work, you can create an application restriction for the app either in the Global Data Restrictions dialog of the Security Groups application or in Application Designer. 

    If you need it to be enforced for a subset of users, you can create a data restriction on the security group(s). If you setup a qualified data restriction on the WORKORDER object with a condition that restricts it to the statuses you want them to see, that would get enforced in any application where WORKORDER is the main object (WOTRACK, QUICKREP, etc.). When you do the condition, just make sure that you enable them to see any WOs they create as well. Otherwise, they will get an error when they try to save which will prevent them from creating work orders.



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

    Original Message


  • 3.  RE: Can you restrict WO visibility based on status?

    Posted 12 days ago

    Thanks so much for that info, Steven. I may reach out to you offline to get a few more pointers in how to set up a data restriction on a security group. ��

     

    Amy Tellier-Briggs

    Maintenance Planner, The Jackson Laboratory

    Maine | Connecticut | California | Florida | Japan | China

    (207) 288-6356 t | (207) 266-4347 m

    amy.briggs@jax.org | she/her pronouns

    www.jax.org

     

    Subscribe to JAX e-newsletters at http://www.jax.org/subscribe

    Follow JAX on Facebook, X, LinkedIn or Instagram

     

    The Jackson Laboratory: Leading the search for tomorrow's cures

     

    ---

    The information in this email, including attachments, may be confidential and is intended solely for the addressee(s). If you believe you received this email by mistake, please notify the sender by return email as soon as possible.



    Original Message


  • 4.  RE: Can you restrict WO visibility based on status?

    Posted 9 days ago

    I achieve similar results with a combination of methods:

    1. Conditional expressions on the WOSTATUS and WOCHANGESTATUS objects that would only allow certain people (not Technicians) to Approve the Work Order.
    2. Setting Technicians up with a default query on the mobile app they use, so it only shows them Work Orders assigned to them that have been Approved.

    The end result is, yes, they could "see" the Work Order that hasn't been approved yet, but they'd have to work for it.  And even if they found it, they can't do anything with it.

    I prefer this approach (read-only access to all Work Orders but edit access only if it is assigned to them and approved) so that, at least in theory, a Technician could observe some problem while out in the field and could see if a Work Order already exists for it.



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

    Original Message


  • 5.  RE: Can you restrict WO visibility based on status?

    Posted 8 days ago

    Sounds like a good solution, Travis. The problem on our end is they know how to search for other stuff, and often WILL. It's interesting how they complain that they don't have enough time in their day to put their time and notes on a work order in Maximo, and yet seem to have lots of time to search for work that hasn't been assigned to them yet. ;)

    How do you apply conditional expressions on the WOSTATUS and WOCHANGESTATUS objects?

    Thanks,
    Amy



    ------------------------------
    Amy Briggs
    Maintenance Planner
    The Jackson Laboratory
    Bar Harbor, ME
    207-288-6356
    ------------------------------

    Original Message


  • 6.  RE: Can you restrict WO visibility based on status?

    Posted 8 days ago
    1. Go to Database Configuration.  Fetch the WOCHANGESTATUS object. If you previously haven't done so for some other reason, you'll need to create a relationship to the WORKORDER table.  Caveat: WOCHANGESTATUS does not have the SiteID or OrgID fields.  I simply made the relationship to be defined upon   wonum = :wonum     --- this might be problematic in a multisite/multiorg environment, which is not my situation.  In the example code below, I named this relationship     pcc_workorder
    2. Go to Conditional Expression Manager.  You'll end up creating 2 similar Expressions, one that you'll apply to WOCHANGESTATUS and another that you'll apply to WORKORDER.  Sample code below -- here I am specifying what the current status must be, including a couple of custom statuses we added (with the purpose of excluding other custom statuses we use that otherwise would have been able to go to INPRG per the out-of-the-box design; and then making it so only the Work Order's Lead or Supervisor can change the status:
      /*This is the code I would use on the WORKORDER object*/
:status in ('NEW', 'CNTRCTSIGN', 'WPCOND', 'APPR', 'WMATL', 'PAUSED') and (:&PERSONID& = :lead or :&PERSONID& = :supervisor )

/*This is the code I would use on the WOCHANGESTATUS object*/
:wostatus in ('NEW', 'CNTRCTSIGN', 'WPCOND', 'APPR', 'WMATL', 'PAUSED') and (:&PERSONID& = :pcc_workorder.lead or :&PERSONID& = :pcc_workorder.supervisor)


    3. Go to Domains.  Fetch the WOSTATUS Domain.  Continuing on from the previous step, we'll apply those conditions to the INPRG status.  Find the row in the Domain where Value = INPRG.  Then at the bottom of the dialog box, click View/Modify Conditions.  Add a row, choose the Condition that you made for use with WORKORDER, and then put WORKORDER as the Object Name.  Make a second row, this time choosing the other Condition and use WOCHANGESTATUS for the Object Name.

    Pretty sure that's it.  Well, except that I made my Conditions much more complex, and made custom Conditions for all the possible statuses.  But the point is here, you can create restrictions that wouldn't allow the Technicians to Approve the Work Order -- either prevent them completely (that's what I do) or perhaps allow them to Approve it under some condition (e.g. it's been scheduled but not approved).  You'd just have to define what your business process needs to look like.  

    But if you don't even want your users to see what hasn't been approved for them yet, then you should be using Security Groups --> Data Restrictions --> Object Restrictions instead.



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

    Original Message


Related Content