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 Aug 4, 2025

Forests, Land and Agriculture emissions - Science Based Targets Custom Factors (FLAG emissions)

We have clients that need to report (1) Land use change, (2) Land management net and (3) Land management non-CO2 emissions separately. So in order to do that, we need three separated emission factors for each data type.

Idea priority Urgent
Needed By Yesterday (Let's go already!)
  • Admin
    Michael Dunbar
    Oct 13, 2025

    Thank you for the additional details. I will move this to a future consideration to indicate that we will monitor developments to see what the final guidance will be, coming out of the GHG protocol, ESRS and CSRD, and to see if any of the main factor providers make changes to the way they supply emissions factors.

    However, our view is that we have a working model for tracking and reporting on FLAG emissions that is already being used by some very large clients with significant exposure to FLAG emissions. Separate FLAG data types represent the simplest way to leverage the functionality that already exists in Envizi (targets, virtual accounts, custom factor management, powerReports, etc.). The potential increase in the number of accounts a client may need in order to track FLAG emissions separately is proportionate to the additional value derived from the Envizi solution.

  • Guest
    Oct 3, 2025

    Hi IBM!

    We have provided more information about this idea and why it is a needed development in Envizi. There is also a use case as an example. We would appreciate if you took this idea for further consideration. The additional information can be found in the attachment.

    Sincerely, Henna 

  • Guest
    Sep 16, 2025

    Hi,

    Do we have any updates on it?

  • Guest
    Aug 15, 2025

    Hi, 

    The problem with this approach is that having more data types equals a bigger amount of accounts for the clients which can make higher the price of using Envizi, therefore we think that the submitted idea will be the best solution.

    I spoke with the client and they can involve their experts to provide further clarifications.

    Kind regards,

    Arturo Leon

  • Admin
    Michael Dunbar
    Aug 6, 2025

    Hi @Guest - we have several clients who track FLAG emissions in our platform already. They do so using data types specific to FLAG activities (enteric fermentation, manure management, deforestation, land conversion, etc). While Envizi does not currently have a library of managed factors relevant to these areas, clients are able to use custom factors where these are required.

    Since these activities are tracked in separate data types and data type categories, this data can easily be separated for reporting.

    Adding additional fields to our factors and modifying the downstream calculations and reporting is a major undertaking. We do not see the need given that this data can be derived and reported on using the existing functionality.

    Can you clarify if/why you feel that the existing approach with FLAG data types and custom factors is not sufficient for your reporting needs?