|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
ID |
Name |
GridPP |
LCG |
EDG |
Apps |
Infrast. |
Interop. |
|
|
|
Li |
Im |
Risk |
Li |
Im |
Risk |
Li |
Im |
Risk |
Li |
Im |
Risk |
Li |
Im |
Risk |
Li |
Im |
Risk |
|
R1 |
Recruitment/retention
difficulties |
|
|
|
1 |
2 |
2 |
2 |
2 |
4 |
2 |
2 |
4 |
2 |
2 |
4 |
|
|
|
|
R2 |
Sudden loss of key
staff |
|
|
|
1 |
4 |
4 |
1 |
3 |
3 |
1 |
3 |
3 |
1 |
3 |
3 |
|
|
|
|
R3 |
Minimal Contingency |
|
|
|
|
|
|
1 |
2 |
2 |
2 |
2 |
4 |
1 |
2 |
2 |
|
|
|
|
R4 |
GridPP deliverables
late |
|
|
|
|
|
|
1 |
3 |
3 |
4 |
2 |
8 |
|
|
|
|
|
|
|
R5 |
Sub-components not
delivered to project |
2 |
4 |
8 |
2 |
3 |
6 |
2 |
3 |
6 |
|
|
|
2 |
3 |
6 |
|
|
|
|
R6 |
Non take-up of
project results |
|
|
|
2 |
1 |
2 |
1 |
4 |
4 |
1 |
4 |
4 |
|
|
|
|
|
|
|
R7 |
Change in project
scope |
|
|
|
1 |
1 |
1 |
2 |
2 |
4 |
1 |
1 |
1 |
|
|
|
|
|
|
|
R8 |
Bad publicity |
2 |
2 |
4 |
1 |
3 |
3 |
1 |
3 |
3 |
|
|
|
|
|
|
|
|
|
|
R9 |
No publicity |
2 |
1 |
2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
R10 |
External software dependence |
|
|
|
2 |
4 |
8 |
1 |
4 |
4 |
2 |
3 |
6 |
|
|
|
|
|
|
|
R11 |
Lack of monitoring of staff |
|
|
|
1 |
2 |
2 |
2 |
2 |
4 |
1 |
3 |
3 |
1 |
2 |
2 |
|
|
|
|
R12 |
Withdrawal of an experiment |
1 |
4 |
4 |
1 |
4 |
4 |
1 |
2 |
2 |
|
|
|
|
|
|
|
|
|
|
R13 |
Lack of cooperation between Tier
centres |
|
|
|
1 |
4 |
4 |
|
|
|
|
|
|
1 |
2 |
2 |
|
|
|
|
R14 |
Scalablity problems |
|
|
|
3 |
3 |
9 |
2 |
3 |
6 |
|
|
|
1 |
3 |
3 |
|
|
|
|
R15 |
Software maintainability problems |
|
|
|
3 |
2 |
6 |
1 |
3 |
3 |
|
|
|
|
|
|
|
|
|
|
R16 |
Technology shifts |
1 |
3 |
3 |
1 |
4 |
4 |
1 |
3 |
3 |
|
|
|
|
|
|
|
|
|
|
R17 |
Repitition of research |
3 |
2 |
6 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
R18 |
Lack of funding to meet LCG PH-1
goals |
|
|
|
1 |
3 |
3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
R19 |
Adequate persistency solution not
ready |
|
|
|
|
|
|
|
|
|
1 |
3 |
3 |
|
|
|
|
|
|
|
R20 |
Conflicting software requirements |
|
|
|
|
|
|
|
|
|
4 |
1 |
4 |
2 |
2 |
4 |
|
|
|
|
R21 |
Tier-A hardware fails to meet
requirements |
|
|
|
|
|
|
|
|
|
1 |
3 |
3 |
|
|
|
|
|
|
|
R22 |
Other Hardware fails to meet
requirements |
|
|
|
|
|
|
|
|
|
|
|
|
1 |
1 |
1 |
|
|
|
|
R23 |
Hardware physical risk (large scale) |
|
|
|
|
|
|
|
|
|
|
|
|
1 |
4 |
4 |
|
|
|
|
R24 |
Hardware physical risk (small scale) |
|
|
|
|
|
|
|
|
|
|
|
|
2 |
2 |
4 |
|
|
|
|
R25 |
Hardware procurement problems |
|
|
|
|
|
|
|
|
|
|
|
|
2 |
2 |
4 |
|
|
|
|
R26 |
LAN Bottlenecks |
|
|
|
|
|
|
|
|
|
|
|
|
2 |
1 |
2 |
|
|
|
|
R27 |
Tier-2 organisation fails |
|
|
|
|
|
|
|
|
|
|
|
|
1 |
2 |
2 |
|
|
|
|
R28 |
Tier-2 hardware not used as planned |
|
|
|
|
|
|
|
|
|
|
|
|
2 |
1 |
2 |
|
|
|
|
R29 |
SYSMAN effort inadequate |
|
|
|
|
|
|
|
|
|
|
|
|
3 |
3 |
9 |
|
|
|
|
R30 |
Firewalls interfere with Grid |
|
|
|
|
|
|
|
|
|
|
|
|
1 |
3 |
3 |
|
|
|
|
R31 |
Inablility to establish trust
relationships |
|
|
|
|
|
|
|
|
|
|
|
|
2 |
2 |
4 |
|
|
|
|
R32 |
Security inadequate to operate Grid |
|
|
|
|
|
|
|
|
|
|
|
|
1 |
3 |
3 |
|
|
|
|
R33 |
GGF does not establish standards |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1 |
3 |
3 |
|
R34 |
Minimal open source code development |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2 |
2 |
4 |
|
R35 |
Failure of international cooperation |
|
|
|
1 |
4 |
4 |
|
|
|
|
|
|
|
|
|
1 |
4 |
4 |
|
R36 |
e-Science and GridPP divergence |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2 |
2 |
4 |
|
R37 |
Institutes do not embrace Grid |
1 |
3 |
3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
R38 |
Grid is not stable enough for use |
4 |
2 |
8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
R39 |
Delay of the LHC |
2 |
2 |
4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
R40 |
Lack
of future funding |
2 |
4 |
8 |
|
|
|
2 |
2 |
4 |
|
|
|
|
|
|
|
|
|
|
R41 |
Network backbone failure |
|
|
|
|
|
|
|
|
|
|
|
|
0 |
4 |
0.4 |
|
|
|
|
R42 |
Network backbone bottleneck |
|
|
|
|
|
|
|
|
|
|
|
|
1 |
2 |
2 |
|
|
|
|
Alt-i-r |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|