How demand score is calculated

[Mohammad1]

According to ServiceNow documentation, the score is calculated this way: ((10 - Risk) + Size + Value) / 3. However, going to a fresh developer instance, it seems to totally ignore the Size. Please check the below 2 screenshots. In both screenshots, I have set the same value in the Risk and Value fields. The only difference is the Size field. However, the Score value remained the same despite the change in Size field.

Screenshot 1:

Screenshot 2:

[Rae Ann Prasnic]

Have you looked at this article? How Demand and Projects are Calculated

Let me know if this helps, Rae Ann

[Mohammad1]

Thank you Rae,

Actually, your article is one of the things that I looked at and confused me even more. Sorry for that 🙂 In your article you said that the score is calculated this way: (Inverted Risk rating + Inverted Size rating + Value rating) / 3. Although this makes sense for me, but it contradicts with what is in Now Learning, where it says that only the risk is inverted, not also the Size.

However, regardless of the confusion it has caused, the article still doesn't answer my question above. In ServiceNow instance, it seems to totally ignore the Size field.

[Rae Ann Prasnic]

No hard feelings. 😉 What state is your Demand in? Have you played with moving through the states (e.g., Screening) to see how the score is impacted?

Rae Ann

[Mohammad1]

Thank you.

I tried with a number of projects with different states. Currently, I'm trying with a project and I moving it from 1 state to another (including Screening and Qualified). I'm manually editing the Risk, Size and Value. What is also weird is that the score is calculated differently depending on the state. So, with the same values in Risk, Size and Value, it calculated the score as 5 when the state was Screening, when it became Qualified, I changed the values saved and then changed them back to the original values and saved, the calculated score this time is 6.3.

I can give you access to my developer instance (it's a very fresh instance by the way).

Don't you experience this behavior at your instance?