Skip to Main Content
IBM Sustainability Software - Ideas Portal


This portal is to open public enhancement requests against the products and services belonging to IBM Sustainability Software. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Future consideration
Created by Guest
Created on Apr 7, 2023

Preserve Meter Based PM Target Date Visibility After WO Generation

We propose preserving the next work order projections after the work order has been generated, and until that work order has been completed. In the PM application, Next Work Order Projections are cleared when meter-based PMs generate work orders. Next Work Order Projections are shown on the Meter-Based Frequency tab of the Frequency tab of the PM application and include:

  • pmmeter.readingatnextwo

  • pmmeter.unitstogo (non-persistent)

  • pmmeter.dateofnextwo (non-persistent)

Forms of these values should continue to be visible in the PM application as "redline" measures until the work has been completed. We understand that the reasoning behind clearing these values is that the newly-generated work order is the “Next Work Order” that was projected, so now the projections need to be cleared until the asset returns to service. Also, clearing the data in that section allows PMWOGen to properly generate meter-based work orders.

However, PM work orders are usually generated prior to removing the asset from service, using pmmeter.tolerance and/or pm.leadtime, for the purpose of purchasing related materials and scheduling labor. So once the work order exists, the asset can continue to cycle until pmmeter.readingatnextwo + pmmeter.tolerance (the “redline” date) before the PM needs to be completed. But as Maximo is currently designed, pmmeter.readingatnextwo is unknown after the new work order has generated, so we have no way to know what the redline date is as it approaches. As a result, critical regulatory and risk management timeframes can be missed without resort to tracking systems external to Maximo.

Idea priority Low
Needed By Not sure -- Just thought it was cool
  • Guest
    Reply
    |
    Apr 11, 2023

    To expound on what's been said above, work orders generated from PMs that are timed based benefit from the workorder.targstartdate to know when the PM is due to be completed after work order generation. Meter based PMs do not have benefit equivalent to this from within the "meter based frequency" tab in the PM. If the "pmmeter.tolerance" is used to generate work orders early, the workorder.targstartdate is set as the workorder.reportdate rather than using an estimated date extrapolated from the inputted meter data to date leaving the user not knowing when the asset needs to be removed from service, forcing the creation and utilization of tools outside of Maximo to determine the number of cycles remaining and to derive an estimated date for the asset to be removed from service.


    It should also be mentioned that if the pm.leadtime field is utilized for the purpose of ordering materials on the job plan and the pm.actmeter is not checked, the work order generated from the PM will set the workorder.targstartdate using an estimated date extrapolated from the inputted meter data to date, however the number of cycles remaining is still lost and not visible from within Maximo.