Schedule Risk Analysis
Schedule Risk Analysis
Schedule Risk Analysis
Agenda
Introduction
USAF Approach to Schedule Risk
Design changes
Staffing Manufacturing problems
Contracting problems
Customer (government) not supportive
Cannot get subcontractor under contract
William Cashman, Why Schedules Slip
Air Force Institute of Technology (AFIT) Masters Thesis, 1995
Design Unit 1
Uniform
Mean 105, Sigma 8.67
Triangular
Mean 103, Sigma 6.25
BetaPERT
Mean 102, Sigma 5.54
Normal
Specify Mean and Sigma
16
Start
Design
Unit
Build
Unit
Test
Test
Unit
Unit
Finish
Task
Scheduled
Min
Most Likely
Max
Design 1
100
90
100
120
Build 1
200
170
200
250
Test 1
50
40
50
90
What is a Simulation?
How do you find total project results?
Cannot add distributions
Must combine distributions
80% Target is
6/23
implying a
schedule
contingency
of 38 days
Offsetting Underestimation of
Duration Risk the Trigen Function
Often risk workshops or even risk interviews will
result in Minimum and Maximum ranges that are
too narrow
People tend to anchor on the schedule duration and
adjust the extremes insufficiently
Some are just inexperienced and / or timid
23
The ranges on Build 2 are the same as before, but the Trigen specification is that the
range from 170d to 250d covers only 80% of the total. To cover 100% of the
probability the Min and Max have to be wider
24
25
26
Task
Design 1
Build 1
Test 1
Design 2
Build 2
Test 2
Recognizing bias
in the durations
Max
120
250
90
130
270
100
27
Uncorrelated Uncertainty
Independent duration ranges applied to the
activities on the same path will exhibit some
cancelling out some will be long in their
distributions in the same iterations while
others may be short or middling duration
If someone says that the range for the path is,
say, + 10% and 5%, applying these ranges
to the activities will result in a much narrower
total path uncertainty
28
Correlated Uncertainty
To cause the + 10% and = 5% range for the
entire path we need to specify a correlation
between the activities durations of 100%
(perfect positive correlation) between each
pair of durations
29
Build Unit 1
Test Unit 1
Start
Finish
Design Unit 2
Build Unit 2
Test Unit 2
Task
Design 1
Build 1
Test 1
Design 2
Build 2
Test 2
Max
120
250
90
120
250
90
32
The P-80 is
now 2 July
not 23 June
33
95%
11-Jul-25
17-Jul-15
34
35
37
Using the simple 2-path schedule. Four risks are specified. The first is a general risk
about engineering productivity, which may be under- or over-estimated, with 100%
probability. It is applied to the two Design activities
38
39
With this risk, the Construction Contractor may or may not be familiar with the
technology, the probability is 40% and the risk impact if it happens is .9, 1.1 and 1.4. It is
applied to the two Build activities
40
41
Activity 1
Activity 1
43
Activity 1
Activity 1
Uncertainty Not
Correlated: .85, 1, 1.2
Adding uncorrelated uncertainty reduces
correlation (Activity 1, Activity 2) to 86%
44
Activity 1
Activity 1
45
47
50
51
We create a 4-activity probabilistic branch, adding 4 activities: Root Cause Analysis, Plan
the recovery, Execute the Plan and Retest
Notice that they all have a remaining duration of 0 working days they will not affect the
schedule unless they occur
52
53
54
55
56
57
Set Probability of
Winter Weather Event to 50%
58
59
Monsoon Calendar
Prohibits Offshore Installation (1)
60
Monsoon Calendar
Prohibits Offshore Installation (2)
Notice that the installation activities are, mostly,
nominally before the monsoon season that
occurs November - February
Exception to this is that the last Installation activity,
CPP Topsides, is already scheduled to complete in
November
61
> Add Monsoon Calendar > Apply to Installation tasks > Window > add the impact and dates >
Enable this calendar
62
63
64
65
66
67
68
69
70
71
72
Run Prioritization
View the Risk List in Priority Order
73
106
37
16
16
11
4
0
-2
188
140
328
The Grid view shows the risks in priority order, determined by Monte Carlo
Simulation of the project schedule, with their Days Saved.
(C) 2014 Hulett & Associates, LLC
74