Maximo Anywhere

  • 1.  Labor actuals are editable in Maximo desktop, but not in Anywhere

    Posted Mon June 14, 2021 06:23 PM
    Edited by User1971 Fri June 18, 2021 03:11 AM
    Anywhere Work Technician 7.6.4 (Android):

    My organization has changed the default labor actuals setting so that inside labor transactions don't get automatically approved:
    Changing Labor hours in the Actuals > Labor tab in Work Order Tracking


    Reason: We need to be able to edit/correct actuals after they're saved.



    Anywhere:

    Ideally, my users would be able edit their labor actuals in Anywhere too.

    However, it looks like labor actuals can't be edited in Anywhere, despite the fact that the labor actuals are editable in Maximo desktop .



    Is there a way to make the unapproved labor actuals editable in Anywhere too?

    Examples:
     1. Edit the Regular Hours field.
     2. Or delete the entire record.

    Thanks.


  • 2.  RE: Labor actuals are editable in Maximo desktop, but not in Anywhere

    Posted Mon June 14, 2021 06:30 PM
    Edited by User1971 Fri June 18, 2021 03:16 AM
    For example, what if I configured the Anywhere XML so that the fields are editable? (including a condition that only allows edits if the actuals are unapproved)

    Is Anywhere designed to work like that -- to edit existing actuals? Or is it only designed to create & view actuals?


  • 3.  RE: Labor actuals are editable in Maximo desktop, but not in Anywhere

    Posted Fri June 18, 2021 02:51 AM
    Edited by User1971 Fri June 18, 2021 03:14 AM


    Regarding #1 --
    Edit the Regular Hours field in Labor Details in Anywhere:

    ---------------------------------------------------------------

     - MximoAnywhewre --> apps --> WorkExecution --> artifcat --> app.xml

     - Search for <groupitem id="WorkExecution.ActualLaborDetailView_workOrder_groupitem_6">. There will be <text> tag under it.

     - Replace the abovementioned <text> tag with:
    <text editable="true" id="WorkExecution.ActualLaborDetailView_workOrder_groupitem_6_regularhours_RegularHours" label="Regular Hours" resourceAttribute="regularhours"/>



  • 4.  RE: Labor actuals are editable in Maximo desktop, but not in Anywhere

    Posted Mon June 21, 2021 02:13 PM
    I have been giving this some thought.  It occurs to me this is more of a process issue than a tool issue for you.  IN my opinion your field techs should not be editing their hours. That "should be" a back-office function.  The hours can and should be submitted as is from the field. If there are any issues with pay or accuracy or hours worked on the wrong workorder or whatever that is clarified and "audited" in the back office.  

    Please do this.... When you create the labor transactions on the front end with Anywhere, can you let me know if they labor transactions are still submitted to Maximo as approved or do they appear as unapproved after sent to Maximo?  If they are unapproved then you are home free and have nothing to do technically with the product.  If they are already approved and appear as such on core Maximo, then you have an issue.  That will require code modification to correct, and I would submit a ticket to product development.  If you want to accept internal labor transactions as unapproved, then in my opinion Anywhere should not submit approved only.  This should be an MBO validation process on the backend only with respect the Labor Option you set.

    Now one other thing, if your internal process is such that you really do want your techs to be able to edit their work transactions to submit a "timesheet" at the ned of a pay period (weekly,  bi-weekly, or whatever,) then you can modify with a great deal of effort the application to create a "time sheeting" application.   I led a team for this kind of functionality many years ago (2015) for a client in Australia.  It was expensive to develop and to my knowledge the only one performed.  There could be others but I have not heard of them. It is possible, but it is expensive.

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



  • 5.  RE: Labor actuals are editable in Maximo desktop, but not in Anywhere

    Posted Tue June 22, 2021 01:29 AM
    I was with Bradley as part of that team and yes, as far as I know, it was the only one.  The timesheet app was one on the roadmap for Maximo Anywhere, but for some reason never got built.

    It can be done on Maximo Anywhere, but not cheaply, MAS should be easier due to the fact that now all of Maximo is open to Maximo Mobile.

    ------------------------------
    ===============================
    Craig Kokay,
    Lead Senior Maximo/IoT Consultant
    ISW
    Sydney, NSW, Australia
    Ph: 0411-682-040
    =================================
    #IBMChampion2021
    ------------------------------



  • 6.  RE: Labor actuals are editable in Maximo desktop, but not in Anywhere

    Posted Tue June 22, 2021 10:49 AM
    Edited by User1971 Tue June 22, 2021 10:53 AM
    Thanks Bradley.

    Regarding your question, "When you create the labor transactions on the front end with Anywhere, are the labor transactions submitted to Maximo as approved or do they appear as unapproved after sent to Maximo?"

    It looks like it's working as expected. The labor transaction that was created in Anywhere is UNapproved back in Maximo dekstop, which is good.



    It sounds like it would be straightforward to make the labor transactions editable. Just change editable="false" to editable="true" in the Anywhere XML tag. So if I need to, I'm guessing I could just do that.

    You make some fair points. But from our perspective, if a user makes a silly mistake when entering a labor actual (before the actual is approved), then to us, it doesn't make sense to go to the trouble of arranging with the supervisor to get it fixed. It makes more sense, for the user to be able to fix the UNapproved mistake right then and there.

    Mistakes in Anywhere labor actuals is a pretty common occurrence for our users. Not being able to edit labor actuals (Anywhere and Maximo desktop) is our biggest complaint we're getting from (from all of our divisions). So we feel if everyone is having the same issue, then we need to try to address it. In this case, I don't think I can just tell them to they need to "Be better. You can't correct your mistakes, instead, you need to spend time asking your supervisor to fix them for you." We've found that process to be error-prone in it's own right. (It ends up being a game of telephone...the message ends up getting lost, in terms of what labor actuals need to get fixed, and how.)

    For what it's worth, our labor actuals don't drive pay. They just track the cost of WOs. So that's not as high of a risk, compared to if the labor actuals were being used to drive pay.



    Thanks again for your input. It certainly helps to get other points of view on this...making sure we don't overlooks some critical aspect...


  • 7.  RE: Labor actuals are editable in Maximo desktop, but not in Anywhere

    Posted Tue June 22, 2021 12:57 PM
    Very glad to hear that the labor actuals are appearing as unapproved. That makes sense.  I was lazy and did not want to test it on my VM or to tear into the code to find out whether that attribute was being set in the offline handle or not.  Thanks for the test.

    Regarding your perspective on correcting "silly mistake" in the field I agree with that.  The tis why this is a process question.  If your process is to validate and verify then this is fine.  If you were driving pay (which you are not) then I would say you should not allow the editing.  let the tool do what it does , and then audit and verify in back office.  User will tend to do one of two things when their pay is on the line: either make darned sure it is accurate so they get paid what they are owed, or game the system. (Just the facts man...). since you are not paying them based on the labor actuals then you are correct it is a lower risk.  Now you are courting your technicians to provide best accurate info for their own benefit in the future with respect to reliability measures on labor estimates vs. actuals.

    So to the simple technical aspect you have is the following:  Each of the three views which allow the data entry in the first place are not an issue.  You do however have the "WorkExecution.ActualLaborDetailView".  This shows the existing labor transaction data (as a transition from the list view) already saved to the system (whether they have been transmitted to the server not.) Simply making the attribute as editable is not going to fire any "save" event.  I would suggest you create an action or add a button to update the transaction.  This will require you to call a method which will then perform the action you need.  If you study the ActualLaborHandler and create a custom method in a custom handler you shovel be able to call that from your action or button and have that modify the existing labor transaction record.



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