Maximo

Maximo

Come for answers, stay for best practices. All we're missing is you.

 View Only

  • 1.  Work Order Task Condition Points

    Posted Wed December 30, 2020 12:31 PM

    We have routes with assets that have multiple (2) condition points with characteristic meters. Currently, the routes are created with child workorders. Each child workorder has 2 tasks, 1 for each of the condition points. The tasks are used to enter the observation values. Our customer wants to create the routes with task workorders instead of child workorders. Now there will only be 1 task for each asset. I am trying to come up with an easy solution to enter the 2 observation values for the 2 condition points on each task. I would also like a way to link the condition point values back to the originating task work order. I know I can probably provide a link to the condition monitoring application and they could enter the values there.

    Has anyone done anything like this?

    Maximo 7.6.0.9

    Thank you.

    Mary



    ------------------------------
    Mary Mangieri
    Sarasota County Government
    Sarasota FL
    ------------------------------

    #AssetandFacilitiesManagement
    #Maximo


  • 2.  RE: Work Order Task Condition Points

    Posted Mon January 04, 2021 10:22 AM
    Hi Mary,

    I perfectly understand your concerns. This is a typical problem of the end-users: open parent WO first, then navigate to the child WOs, the go to the Plans tab to see the tasks with measurement points. 
    But, you are doing everything right. This is the right way to collect the data about characteristic meters: create the route, add a Job Plan to each asset with meters. Do not change anything there!
    What you need to do to satisfy your users is to change the User Interface side. Think about adding a new tab with a table, which will present all child WOs and their tasks in one place. All that is needed is a new relationship that will link parent WO with child WO's tasks for example:

    wonum in (select wonum from woancestor where ancestor = :wonum and siteid = :siteid) and siteid = :siteid order by wonum

    In the table, you can define columns for WO number, Task number, task description, Measurement Point, Measurement Date, Measurement Value, and all other details needed.

    If you need more support, please let me know.

    Best regards,

    R. Zientara

    ------------------------------
    Robert Zientara
    Solution Expert
    Rodias GmbH
    Weinheim
    ------------------------------

    Original Message


  • 3.  RE: Work Order Task Condition Points

    Posted Tue January 05, 2021 10:18 AM
    Hi Mary,

    I think what you are trying to do is not possible, out of the box.  If you are trying to capture two data points (essentially meter data for an asset or location) per stop on your routes AND use the task observation values, you will not succeed.  The reason?  The task observation (or measurement point and value attributes) values has (have) a one to one relationship on the object, or to be more accurate they are object attributes.  There is not related record that holds these values.  So unless you resort to adding additional "observation" and or "measurement point and value" attributes to the object (WOACTIVITY i.e. WORKORDER)) then you will not be able to accomplish what you are trying to do. 

    The other way to approach this however is to change the paradigm from using the work order to capture your meter reading and simply use the meter reading capabilities on the asset.  That way your user can simply go about the task of taking meter readings.  What is really dependent here is how you want to capture the "cost" of the effort and allocate that cost to your GL accounts.  Please recall that Maximo is a cost accounting system at heart.  The reason you want to capture the cost on the task is to allocate the meter reading cost to the assets location, and thus spreading your labor cost across all assets.  If you are not concerned with that then simply set up a single work order with multiple assets and then have your technician capture the meter readings on the asset artifact instead of on the work order artifact.

    If you are using Maximo Anywhere you can do this either using the Asset Data Management application or still using the work execution  app.  If you set up all your meter readings routes as a single workorder then when you use the meter readings feature on Work Execution you can simply look at all meter readings on the work order and then navigate from asset to asset and capture the meter readings accordingly.  This is still somewhat clunky and I have rewritten this to enable the user to capture the meter readings sequentially (i.e as you move from asset to asset and from meter to meter you can do this on the list view for each asset or for all assets.)

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

    Original Message


Related Content