Skip to Main Content
Cloud 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 Cloudability
Created by Guest
Created on Jun 19, 2026

Surface the GCP Project Number as a vendor dimension

We are wanting to surface the Project Number as it aligns with AWS/Azure Account ID/Subscription ID. It is a stable and system-controlled unique identifier which doesn't allow confusion between GCP Project Name and GCP Project ID which are often similar.

Idea priority Medium
  • Guest
    Jul 29, 2026

    As part of the Fiserv FinOps chargeback process, we use the account/subscription ID as the unique identifier for chargeback and analyses.  That 12-digit unique identifier found in GCP as Billing ID is not available within Cloudability.

    Right now, the mapping from GCP to Cloudability looks like this:

    • GCP Project Name is mapped to Cloudability Account Name
    • GCP Project ID is mapped to Cloudability Account ID
    • GCP Billing ID (12-digit account identifier) is NOT mapped to Cloudability at all

    Because the Cloudability Account ID field is strictly numeric for both AWS and Azure, it seems logical that the numeric Billing ID for GCP projects should be mapped to the same Cloudability dimension as well to maintain cross-cloud consistency.

    I have attached a screenshot from GCP to illustrate what is being mapped and what is not being mapped.  I have also attached a screenshot from Cloudability showing the same thing.