Join us for an expert-led overview of the tools and concepts you'll need to pass exam PL-300. The first session starts on June 11th. See you there!
Get registeredPower BI is turning 10! Let’s celebrate together with dataviz contests, interactive sessions, and giveaways. Register now.
Hi team,
In the capacity metrics app, I am trying to understand , Add %, Burndown % and Cumulative %
Please can anyone explain this , an example would be great. Does Add and CarryForward are the same?
What does add % of 200 actually mean?
Please help
Solved! Go to Solution.
Hey @msprog ,
Here’s a breakdown of the key terms from the Capacity Metrics App and an explanation of what they mean in the context of the chart you’ve shared:
This refers to new tasks/items being added to the backlog during the time period.
Example: If you have 100 units of carryforward work, and 200 units are added during a specific time interval, the Add % is 200%, meaning the backlog has increased 2x compared to the existing work.
Important Note: Add ≠ CarryForward.
CarryForward is the existing work that hasn’t been cleared.
Add is new work introduced on top of it.
This refers to the percentage of work that was completed or removed from the carryforward during the interval.
If 50% of the carryforward work is completed, the Burndown % will be 50%.
A high burndown % is desirable it shows effective processing of existing tasks.
This is a running total of carryforward represented as a percentage of some baseline (like initial capacity or a fixed threshold).
In your chart, this is shown with the red line (right axis).
It helps monitor long-term trends – whether your backlog is growing or shrinking over time.
Looking at the image:
The green bars represent CarryForward %, showing how much work is being carried over.
The red line (Cumulative %) shows a rising trend, indicating backlog is growing steadily.
In the leftmost bar, the Add % is 200%, which means:
New tasks added in that period were double the current carryforward.
It’s a signal that the team or system is under strain and new work is outpacing the ability to clear existing tasks.
It means: The system received twice the volume of new tasks compared to what was already pending.
Implication: Without a corresponding increase in burndown, the backlog (carryforward) will grow.
If you found this solution helpful, please consider accepting it and giving it a kudos (Like) it’s greatly appreciated and helps others find the solution more easily.
Best Regards,
Nasif Azam
Hi @msprog
We have not received a response from you regarding the query and were following up to check if you have found a resolution. If you find the response helpful, please mark it as the accepted solution and provide kudos, as this will help other members with similar queries.
Thank You!
Hi @msprog
I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions. If my response has addressed your query, please accept it as a solution and give a 'Kudos' so other members can easily find it.
Thank you.
Hi @msprog
Could you please confirm if your query have been resolved the solution provided by @Nasif_Azam , @rohit1991 and @BhavinVyas3003 ? If they have, kindly mark the helpful response and accept it as the solution. This will assist other community members in resolving similar issues more efficiently.
Thank You.
What it is: This shows the percentage increase in memory used compared to the previous time point (usually per hour).
Example: If your dataset used 1 GB at 2 PM and 3 GB at 3 PM:
Add % = ((3 - 1) / 1) * 100 = 200%
So Add % of 200 means: Memory usage has tripled compared to the last period.
What it is: Indicates how much capacity usage was reduced/freed during a time period.
Example: If usage goes from 3 GB to 1.5 GB, that's a 50% burndown.
Useful for seeing how much memory was cleared, either by eviction or refresh completion.
What it is: Running total of capacity used over time, helpful for identifying memory trends or spikes.
High cumulative % may indicate growing memory pressure.
Hi @msprog ,
In Microsoft Fabric’s Capacity Metrics app, Add %, Burndown %, and Cumulative % are metrics that together show how much work is piling up and being processed when your capacity is overloaded. Add % (shown as green bars in the chart) represents the portion of your capacity that was exceeded and thus added to the carryforward backlog (the overage “debt”) in that time window.
For example, an Add % of 200% means the backlog grew by an amount equal to twice your capacity in that interval – a significant overload beyond the 100% capacity limit. Burndown % (blue bars) indicates the percentage of that carryforward backlog that was burned down (processed) once utilization dropped below full capacity, allowing the system to catch up on queued work.
Finally, Cumulative % (the red line) shows the total carryforward backlog at each point in time as a percentage of capacity – essentially the accumulated over-capacity work that still needs to be cleared. In other words, Add % spikes when new work is added to the backlog because the system is over capacity, Burndown % spikes when backlog work is being processed, and the Cumulative % line rises if additions outpace burndowns (indicating a growing carryforward backlog). This means Add measures new overage being added, while carryforward refers to the backlog of deferred work itself (tracked by the rising Cumulative %).
Passionate about leveraging data analytics to drive strategic decision-making and foster business growth.
Connect with me on LinkedIn: Rohit Kumar.
Hey @msprog ,
Here’s a breakdown of the key terms from the Capacity Metrics App and an explanation of what they mean in the context of the chart you’ve shared:
This refers to new tasks/items being added to the backlog during the time period.
Example: If you have 100 units of carryforward work, and 200 units are added during a specific time interval, the Add % is 200%, meaning the backlog has increased 2x compared to the existing work.
Important Note: Add ≠ CarryForward.
CarryForward is the existing work that hasn’t been cleared.
Add is new work introduced on top of it.
This refers to the percentage of work that was completed or removed from the carryforward during the interval.
If 50% of the carryforward work is completed, the Burndown % will be 50%.
A high burndown % is desirable it shows effective processing of existing tasks.
This is a running total of carryforward represented as a percentage of some baseline (like initial capacity or a fixed threshold).
In your chart, this is shown with the red line (right axis).
It helps monitor long-term trends – whether your backlog is growing or shrinking over time.
Looking at the image:
The green bars represent CarryForward %, showing how much work is being carried over.
The red line (Cumulative %) shows a rising trend, indicating backlog is growing steadily.
In the leftmost bar, the Add % is 200%, which means:
New tasks added in that period were double the current carryforward.
It’s a signal that the team or system is under strain and new work is outpacing the ability to clear existing tasks.
It means: The system received twice the volume of new tasks compared to what was already pending.
Implication: Without a corresponding increase in burndown, the backlog (carryforward) will grow.
If you found this solution helpful, please consider accepting it and giving it a kudos (Like) it’s greatly appreciated and helps others find the solution more easily.
Best Regards,
Nasif Azam
User | Count |
---|---|
45 | |
32 | |
30 | |
27 | |
25 |
User | Count |
---|---|
55 | |
54 | |
35 | |
33 | |
28 |