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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
Thank you for the idea, however we don't believe this would increase the accuracy of reporting. Tags and associated effective dates apply to 'monthly normalized' data, not account records.
For background, Envizi receives records that can have intra-month start and end dates, eg. 15-Jan-2024 to 10-Mar-2024. In this example, Jan has 16 days, Feb has 29 days and Mar has 10 days for a total of 55 days of data. Envizi then normalizes this data month by applying the prorata number of days to the records quantity field.
Month
Days
Percentage
Quantity
Normalized amount
Jan
16
16 / 55 = 29.1%
120
35.0
Feb
29
29 / 55 = 52.7%
120
63.3
Mar
10
10 / 55 = 18.2%
120
21.8
If you then need to apply tags to this data, it can only be done in a way that can include or exclude the monthly normalized amount. So applying a tag that is effective Feb and Mar 2024 will exclude the value from Jan of 35.0, and this is appropriate since it has already taken into account the prorated calculation of 16/31 days for Jan.
On the other hand, if it was possible to apply a tag to the day, eg 20-Jan-2024 to 10-Feb-2024, this logically won't work since we no longer have the information about 'day within the month' after monthly normalization has occurred. In the database, we only store values at the monthly level for reporting.
If I've misunderstood what you're trying to achieve or can provide a better description of the use case, le me know.
This would be really good because you could align the tag dates to the actual activity dates for the account etc.
This would really help improve the accuracy of reporting
This would be super useful!