Technical Risk Assessment Handbook - Defence Science and ...
Technical Risk Assessment Handbook - Defence Science and ...
Technical Risk Assessment Handbook - Defence Science and ...
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
23<br />
a list for each sub-system of the technologies required to enable that sub-system to<br />
work.<br />
5.15 Evaluate the maturity of each technology. The TRLs defined in Table 2 form<br />
the basis for assessing a technology’s maturity. Each contributing technology for<br />
each sub-system should be examined to assess its maturity <strong>and</strong> these assessments<br />
should be recorded in the TRA.<br />
5.16 Identify c<strong>and</strong>idate technology risk events. If the TRL of a component<br />
technology is assessed as 9, then no further development is required. Accordingly<br />
this technology is not a source of technology risk, although it can still lead to a<br />
technical or integration risk. On the other h<strong>and</strong>, component technologies that are<br />
assessed as TRL less than 9 are potential sources of technology risk. The PSTA<br />
should then assess the likelihood that the technology will not be developed to TRL 9<br />
to meet the required in-service date <strong>and</strong> acquisition schedule, using historical<br />
precedence <strong>and</strong>/or expert judgement. If this is a possibility, then this is a risk source.<br />
The likelihood is assessed as either More Than Likely, Less Than Likely or<br />
Unlikely, as described in paragraph 3.26.<br />
5.17 Once the technology risk sources have been identified, the next activity is to<br />
assess the impact on achieving the project’s objectives if the risk event were to<br />
happen, <strong>and</strong> hence the level of risk. This leads to a risk statement along the lines of:<br />
‘There is a chance that the sub-system will not mature sufficiently in the required<br />
time, which could impact the project’s requirements.’<br />
5.18 These technology risks are then set out using the format at Table 4. As shown<br />
in the Table, an estimate of the likelihood can be provided where there is sufficient<br />
confidence, either as a point estimate or as a range.<br />
Technology TRL Development<br />
required<br />
Battery 9 Same battery<br />
proven in service<br />
on another missile<br />
Guidance<br />
set<br />
5 Shock resistance<br />
still to be<br />
demonstrated<br />
Likelihood<br />
of<br />
technology<br />
not maturing<br />
in time 1<br />
UNLIKELY<br />
(10-15%)<br />
Notes.<br />
1. Likelihood is assessed as More Than Likely, Less Than Likely or Unlikely.<br />
2. Impact is assessed as Minor, Moderate or Major.<br />
3. <strong>Risk</strong> is assessed as Nil, Low, Medium or High.<br />
Table 4: Table of technology risks.<br />
Impact on <strong>Risk</strong> 3<br />
project’s<br />
objectives 2<br />
Moderate<br />
(Could delay<br />
schedule)<br />
Nil<br />
Low<br />
5.19 The Technology <strong>Risk</strong> table is developed for each option <strong>and</strong> included as an<br />
annex in the TRA. Where the technologies are the same for each option, the risk<br />
identification can recorded in the one table.<br />
<strong>Technical</strong> <strong>Risk</strong> <strong>Assessment</strong> <strong>H<strong>and</strong>book</strong> Version 1.1