View Only
  • 1.  Work Execution - Active Timers on Closed Workorders

    Posted Wed March 11, 2020 04:47 AM

    We've submitted an RFE for this but has anyone experienced this and/or found a workaround?

    Scenario is that a technician starts the timer on a workorder and maybe forgets to stop the timer. The workorder is then COMP and closed, but the technician cannot start the timer on another job as they still have an active timer on  the closed workorder.

    As far as I'm aware starting the timer on Anywhere doesn't create any persistent data to sync back to Maximo Desktop. If it did then we could apply some condition to prevent closure of a workorder if there was an active timer. 

    The labor transaction data sits on the device until the timer is stopped and only way to get around it is to completely reinstall the app


    Christopher Kung


  • 2.  RE: Work Execution - Active Timers on Closed Workorders

    Posted Wed March 11, 2020 11:26 AM

    As a workaround, I suggest leaving a minimum period between the completion and closing of the work order. A good practice is to perform a validation of the work order prior to close it (control if logs, failure mode, expenses, etc. are completed). Also, some transactions originating from PO or Invoices could be pending and cannot be completed if WO is closed. 

    If you do not have any control following the WO completion, you could schedule an escalation that close it automatically some days after completion.

    I hope this helps you !

    Serge Gagnon
    STI Maintenance
    Jonquiere QC

  • 3.  RE: Work Execution - Active Timers on Closed Workorders

    IBM Champion
    Posted Thu March 12, 2020 12:59 AM
    I too have logged an RFE. 

    The fundamental nature of the timer is that unlike Maximo, MA does not create the "half" a transaction in the LABTRANS table.  An option (for the moment) is to have a JS that flags the WO that someone has started a timer, resetting to null once the MA user has stopped the timer, then create a validation script in Mx that stops a user from Closing a work order. 

    However, if somehow your process allows for a user in Mx to complete a work order and this status causes the work order to be removed from the user, then I also overcome this by adding a new status called Field Complete, which is only available to the Tech via a mobile device and then restrict the ability to change to COMP or CLOSE in Mx unless the current status is FIELDCOMP.  There a number of ways to stop the changing of a work order status.

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

  • 4.  RE: Work Execution - Active Timers on Closed Workorders

    Posted Thu March 12, 2020 04:31 AM
    Thank you all for your suggestions

    Christopher Kung