As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only. Moving forward, myibi is our community platform to learn, share, and collaborate. We have the same Focal Point forum categories in myibi, so you can continue to have all new conversations there. If you need access to myibi, contact us at myibi@ibi.com and provide your corporate email address, company, and name.

Basis is the standard on which 100% is based. It prevents divide-by-zero in situations where you might have a target of 0, because in descending measures your target is the denominator in the calculation.

If you set a basis of 10 on a descending measure, and the target is 0, and your actual is 10, then you are at 0% achieved. If the basis were 20, you'd be at 50% achieved.

Not sure why this isn't in the doc but we'll correct that.

We still were a little unsure, so for clarification, are either of these interpretetations correct?

1. In the situation where a descending measure's target is zero, the basis value is used instead of the target value to avoid division by zero. In this case is the formula to calculate Percent of Target Reached (% Achieved): (Basis - Actual) / Basis? This would would work for the first 2 examples below.

How would this work if the basis were 20 and the actual were 10? Using (Basis - Actual) / Basis, (10 - 20) / 20 = -0.5, which is -50%.

2. The other interpretation we came up with was: (Actual - Basis) / (Basis - Target) which would be used regardless of whether the target is 0 or not for a descending measure.

We also need to be able to explain all this to our end users who supply the info we use to create the measures.

This is the first time using Focal Point so I hope I am doing this properly. I have been trying to figure out the best way to calculate % target reached for descending measures. I understand that using Basis value avoids the Dividing by 0 issue but what if the target equals the Basis value? Aren't we back to the dividing by 0 issue. Also, I have found that if your target and actual numbers are greater than the basis value the Basis value calculation gives incorrect results. If there were a way to ensure that there were never targets of 0, wouldn't it always be best to use the Target Value calculation for % target reached for descending measures? Any thoughts?

For some reason I cannot fathom, a complete description of Basis isn't in the doc...

PMF calculates Percent Reached for descending Meausres by dividing the Target into the Actual value and multiplying the result by 100. If the descending Measure had a Target of 0, this would have resulted in a Divide by Zero, which would have been mathematically invalid. Special handling is therefore required for Measure Targets that are set to zero.

In cases where you had a target of 1 or a fractional target, and an Actual that was many multiples higher (e.g., a Target of .05 and an Actual of 25), you would see a seemingly abnormally high Percent Reached (sometimes so high as to overflow and display ******* as the Percent Reached).

Basis controls where you would have zero Percent Reached. The basis is the point you would exceed with your Descending Measure greater than which your Percent Reached would start moving into the negative. Any Actuals that were greater would show a negative Percent Reached; any that were less will show a positive Percent Reached. Setting the Basis gives you control over how Percent Reached is calculated so you can see more reasonable-looking Percents Reached.

How Descending Measure Basis Handling Works

The special handling lets you pick a defined numeric value as your zero crossing for Percent Reached. The value can be sufficiently large that you would never exceed it, or you can adjust it as needed until your numbers look reasonable.

If you set a Basis for a Descending Measure, the calculation for Percent Reached subtracts the Actual from the Basis amount and the Target for the Basis amount, which rebalances the Percent Reached to give you more control when Target numbers get very small.

----- What this means: If the target for your descending measure SUMS out to equal the basis exactly (and note that if your measure uses continuous rather than discrete values the odds of this are QUITE LOW), you would in concept hit a divide by zero but you never do, since we defend against divide by zero deterministically by setting set Pct Reached to 0 rather than having "undetermined value" for an answer (and/or having WebFOCUS throw an error halting processing).

Hope this helps.

Bob Jude Ferrante Director of Business and Development WebFOCUS Performance Management Bob_Ferrante@ibi.com 917-339-5105

I'll take any questions about PMF - business or technical - anytime!

I have now moved on to our "Range" measures. I was trying to figure out the formula for %target reached. I thought I had it: (Target-ABS(Actual-Target))/Target. This works most of the time but still not for everything. Do you know the formula? Thanks,

Hi Bob, I guess I need to clarify that I am a Business Analyst, not a developer. I do not have the capability to look at system files or code. If there is a manual I could look there. Otherwise I need to try to get help from other people. Thanks

If Target ever SUMs to a zero amount we set it to 0.

This doesn't show all the breakpoints we calculate to draw the colours (we do those based on applying thresholds you set), but all use the same pattern.

Hope this helps. Note that it's pretty tedious to type this stuff into this primitive online editor so I hope I didn't make any typing errors. But this should give you an idea.

Bob Jude Ferrante Director of Business and Development WebFOCUS Performance Management Bob_Ferrante@ibi.com 917-339-5105

I'll take any questions about PMF - business or technical - anytime!