Clarity

Hi All, reaching out to the PPM Community to see whether this is possible through configuration only (but not holding out hope).

We have successfully deployed the base configuration of Clarity for basic Project and Portfolio Management, including the definition of the risk heatmap into the 'Risk Score Setup'. See below.

This translates to a risk heatmap that if coloured looks like below tiered for only 3 levels of scoring of "Low", "Medium", or "High" (while still being calculated with a multiplied score between 1 to 25).

The disconnect for us is that our Risk team, while being happy with a 5 x 5 scoring, want to tier the calculated risks in the map on 5 levels. See below.

The challenge is that I have tried to investigate whether I can change the lookup referenced in the 'Risk Score Setup' to include two additional values for "Very Low" and "Very High". The only lookup that I can find (that I assume the function references) is 'Risk Rating (Standard - LMH)' which is "System Restricted". Therefore I can't extend this.

And the values are restricted to:

Am I on the right path in which lookup is support the values for selection? If not, have any of you been able to extend the lookup so that there is a 5 tiers in the 'Risk Score Setup'?

Some previous comments related to this;

5-point Risk Assessment Scale 

System-Restricted Lookup Risk Rating (ID=RCF_STANDARD_LMH) does not allow for full implementation to expand Risk Score Setup 

I think that the final gist of the earlier discussions was "configure your own score-system" (but that has downsides too).

EDIT : having said that, the latest documentation does suggest that you can add new values to the RCF_STANDARD_LMH lookup - here ; Project Risks, Issues, Change Requests, and Action Items - CA PPM - 15.3 - CA Technologies Documentation ( in the "Configure the Risk Score Matrix Using Custom Values" section)

Thanks Dave_3.0. We are still on 15.2 but will be migrating to 15.3 in the next month or two (still on the old UI). Following through on this documentation for 15.3, this is not available to us in our current environment.

yeah you are right, I don't see the same information in the documents for 15.2 - I don't immediately see anything about this in the release notes for 15.3 though either - might be worth raising a case with CA support to get the detailed "back-story" on all this then?

(or unless anyone from support/engineering would like to add in here?)