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 Not under consideration
Created by Guest
Created on Sep 19, 2011

CU Estimating – Compatible Units Sub-Tab / Excessive Entry Required for Station, etc. (18392 033 000 / 20110908-05)

Prior to T&D 7.1.1, the Compatible Units sub-tab consisted of a Work Sets table and a Compatible Units table. When adding a row to the Compatible Units table, the Station and Work Set would default to the values from the highlighted row on the Work Sets table. This design was cumbersome because only a few Stations/Work Set combinations could be viewed in the upper table and CUs could only be entered/viewed for a single Station at a time. The re-designed T&D 7.1.1 UI eliminated the upper table and allowed the CU table to display all CUs (Station Details) for the entire Estimate Version at one time regardless of Station or Work Set but provided the Filter Row capability for users to filter as they see fit.

Although this design is much better than the previous one, there was an unintended consequence to this change. Now, when a user clicks "New Row" on the Compatible Units sub-tab, the Station defaults to the Station that has the focus on the Stations sub-tab and the Work Set defaults to 0. That means that to avoid having to manually enter the Station on CU rows for Stations other than the first, the user has to continuously go back to the Stations sub-tab to highlight a different Station and return to the CU sub-tab to add the CUs to it.

In the prototype for the UI re-design, this concern was addressed by adding 3 non-persistent attributes to the PlusDEstVersion object to store default values for Station, Work Set, and Work Function. These non-persistent fields were updated anytime the user modified the corresponding field on a related PlusDStnDetail record and used as default values when a new CU/StnDetail is added. Thus if a user adds a CU to Station 001, the next row added will default to Station 001. If the user then changes the Station to 002, the next row added will default to Station 002. The same is true with the Work Set and Work Function fields.

Idea priority High
  • Guest
    Reply
    |
    Oct 29, 2015

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - Internet of Things
    Product family - Asset Management
    Product - Maximo for Utilities

    For recording keeping, the previous attributes were:
    Brand - Tivoli
    Product family - Asset Management
    Product - Maximo for Utilities

  • Guest
    Reply
    |
    Oct 25, 2011

    This RFE will be addressed in a future release.

  • Guest
    Reply
    |
    Sep 19, 2011

    This issue was initially reported via ESR as PMR 18392 033 000. The support rep, Alice Degawa, suggested I create this RFE after getting the following response from L3/Dev:

    "The suggestions made by Julio make sense and should be addressed by a RFE. Some scenarios like how customer uses the UI and how many CUs and Stations usually are being created aren't clear to development and we need to use this expertise from Julio to provide a better user experience in this piece of Utilities."