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 Feb 3, 2016

Enhancements to the PM Module - PM.COUNTER

PM.Counter:

This attribute has multiple uses which is in correct. It should server one dedicated purpose i.e. reflect a single entity. These are the multiple things that the counter is trying to denote. As Per http://www-01.ibm.com/support/knowledgecenter/SSLL84_7.1.2/com.ibm.lsci.doc_7.1.2/pm/c_pm_counter.html

a) The preventive maintenance (PM) counter specifies the number of work orders generated from a PM since the first start date.
b) You can change the value of the PM counter, typically if you want the PM to use a different job plan than the one that is scheduled to be next

Issues:
As soon as the counter is manipulated to adjust for a specific job plan it will never again reflect the number of work orders that were generated from this PM. So statement a) is instantly rendered untrue.

Secondly, if multiple generated WOs are cancelled then the PM counter is out of whack again as it is only adjusted for the last cancelled WO.

So what is the significance of the counter and what is one to gather when viewing the pm.counter? Is it really the number of WOs that were generated or is it something else ?

Recommendation:
1. Statement a) needs to be reworded at the very least to accommodate for cancelled WOs.
2. We need a distinct counter PM.JobplanAdjuster which is dedicated to adjusting the next job plan on the PM.

Idea priority Medium
  • Guest
    Reply
    |
    Mar 14, 2022

    I can't support this. It could be renamed, but I've never, never, dreamt that it was anything else than a counter than can be reset. In using ACM, it can reset the counter, so this product alone means that it's working as designed. Why would you need to know how many work orders have been/ Just run a SQL query or add a tab to show this information.

  • Guest
    Reply
    |
    Aug 19, 2016

    I'd say the PM counter is purely for the MOD function to divide the PM counter with a job plan sequence. Like you said, since it can reset... no point in really saying it counts the number of work orders generated.

    From: http://www.ibm.com/support/knowledgecenter/SSLL9G_7.1.2/com.ibm.oil.doc_7.1.2/pm/c_pm_counter.html

    Preventive maintenance counters

    The preventive maintenance (PM) counter specifies the number of work orders that were generated from a PM since the first start date.

    You can view the current counter setting on the PM tab. The counter is set to zero when you insert a new PM record. It increases each time you generate a top-level work order from the PM. Child work orders do not increase the counter value on the top-level PM.

    When you generate a work order from a PM with a job plan sequence, the job plan with the highest sequence number that divides evenly into the value in the Counter field is selected. If no sequence number meets this criterion, the primary job plan (sequence number one) is used.

    You can change the value of the PM counter, typically if you want the PM to use a different job plan than the one that is scheduled to be next.