Website Upgrade Incoming - we're working on a new look (and speed!) standby while we deliver the project

Tips on using this forum..

(1) Explain your problem, don't simply post "This isn't working". What were you doing when you faced the problem? What have you tried to resolve - did you look for a solution using "Search" ? Has it happened just once or several times?

(2) It's also good to get feedback when a solution is found, return to the original post to explain how it was resolved so that more people can also use the results.

Determining Risk Impact value and Probability

3 replies [Last post]
SM PUM
User offline. Last seen 10 years 51 weeks ago. Offline
Joined: 15 Nov 2011
Posts: 77
Groups: None

Hi All.

I am Really happy to be with you here on Planning Planet.I am finding it very helpful indeed.Thaks to all of you for contributing and sharing the knowledge.

My Questions are about Primavera Risk Analysis.

Q#1. I need to know the Basis that how the Risk Impact (Low,Medium,High,Very High etc.) . For example if you have a project of say,12 Months, and a Risk is Impacting the Project by say,1 month, then how it is evaluated that this risk belongs to,low,Medium,High or very High Impact category??

Q#2. How should I give accurate values in the Impact Ranges ( i.e Very high (Schedule) = 20 to 40 days or Cost Very High (2000 USD to 3000USD etc.)

i need a guidline from those who are experienced amongst you because i am still junior in this field and need a helping hand.

I have googled this topic for many days and when i failed to reach any solid decision then i have posted this query here on this forum.

 

Mny thanks to all in advance.

Happy planning.

Replies

Yasir Masood - PM...
User offline. Last seen 3 years 52 weeks ago. Offline
Joined: 31 Mar 2008
Posts: 29
Groups: None

Agree with feedbacks provided

Dennis Hanks
User offline. Last seen 8 years 44 weeks ago. Offline
Joined: 17 Apr 2007
Posts: 310

SM;

I wrestled with the same issue, with the same result.  My approach is to subjectively develop the ranges for both cost and schedule, present these to the group for validation, adjust and then run the risk workshop.  No real guidance here, only that every project will likely be different - either in nature (length and cost) or risk aversion/acceptance.

My suggestion is to question the default values and make the changes that you think would reflect Very High, High, Medium, Low, or Very Low risks, or whatever rankings you think appropriate.[I do not think there are any limitations to the number, but I have never tried to develop more]  Remember the real purpose of the rankings is to drive focus to the major risks (threats/opportunities) not necessarily develop the actual impact.  That may come later with mitigation strategies.  

Wish I could be more helpful.  I would be interested in your eventual solution/approach.

 

PS:  Consider using Liquidated Damages as a metric for determining cost and schedule impact.  No experience myself, but it seems like a reasonable approach.

Rafael Davila
User offline. Last seen 6 weeks 3 days ago. Offline
Joined: 1 Mar 2004
Posts: 5241

If you refer to individual risk events related to time and activity duration I suggest looking at Criticality Index and define your own scale. Keep in mind if two activities have the same criticality index say 50% of falling into the critical path it does not means the impact on the overall schedule will be the same.

If you are interested on the impact a specific event might have on the overall job maybe a sensitivity analysis is in order. In  such case I would run the PRA with the event scheduled without risks and again with the event with a risk distribution. If the risk is activity duration and the deterministic schedule shows a high float value relative to its distribution it might be that for such event the difference is none, that is when CI is zero, but when not it shall disclose some difference between the cumulative distribution curves, curves might look similar but in reality they are different, shifted with relation to project start.