Skip to Main Content
Cloud Management and AIOps


This is an IBM Automation portal for Cloud Management, Technology Cost Management, Network Automation and AIOps products. 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 Submitted
Workspace Apptio
Created by Guest
Created on Oct 9, 2025

Can we get the sustainability metrics like CO2 emissions and power consumption in Kwh directly from Cloudability into TBM Studio as part of the existing cloudability connector (cldy_monthly_**) ?

Right now you are providing cloud sustainability API supported by the cost reporting endpoints, but once used, it will lead to another extra table with our Apptio model. Also, I see that these 2 sustainability metrices ( but with blank values) are already part of the destination table(s) created on running this existing cldy connector (i.e., cldy_monthly_aws , cldy_monthly_azure) etc., 

If we can get this, another advantage would be in terms of granularity level - we can get these metrics applied to the same level of our existing cloud data in the TBM model

Idea priority Low