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 Nov 15, 2012

Ejecutar Estimación UC en JVM separada del proceso de usuario.

Procesos de estimación con muchas UC genera errores tipo out of memory cuando tiene más de 1500 unidades constructivas asociadas. Nosotros les proponemos a ustedes separar el proceso de estimación de UC de Maximo de los procesos de UI (en JVM separadas), de manera de no afectar a los usuarios ni que la cantidad de usuarios conectados afecte los procesos de estimación (muchos usuarios concurrentes en una JVM, reducirían la memoria disponible lo que podría genera el error Out of Memory al ejecutar una o más estimaciones).

Idea priority Urgent
  • 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
    |
    Feb 18, 2013

    I got this one from a meeting with Solex. Basically they have a customer using really huge hierarchies of CUs and the estimating process in CUE application takes longer and, in some cases depending on the server memory availability, it can crash the JVM that users are logged to. This came out also with another set of usability requirements that are being planned for a future release, including the ability to run estimates in background or using crontasks, satisfying also this enhancement request. Having the estimating process as part of a Maximo crontask, its execution could be assigned to a specific JVM in Maximo environment and also have its process monitored by a system administrator.

  • Guest
    Reply
    |
    Nov 30, 2012

    Can you please enter this request in English?

  • Guest
    Reply
    |
    Nov 15, 2012

    Nosotros habiamos ideado una solución parcial:

    Colocar un crontask que procese en otra JVM las estimaciones de UC y en forma secuencial. La idea sería que cuando un usuario necesite estimar una UC, el workflow no llame directamente al proceso de estimación, sino que haga una marca en un tabla de procesamiento para que la tome el crontask desde otra JVM (no interfiriendo con la JVM de UI) y procese las solicitudes de estimación en forma secuencial. Una vez procesada, se deberá indicar en la EUC que el proceso finalizó (podría ser automático por el cambio de estado).
    El objetivo de esto es tener un proceso separado (otra JVM) sólo para procesar las EUC, sin afectar la interfaz de usuario. Incluso podría “caerse” (shut down) el crontask sin afectar al usuario (se podría colocar un proceso que reinicie la JVM en forma automática en tal caso para que la procese en forma “limpia” nuevamente).