18.01.2015 Views

Technical Risk Assessment Handbook - Defence Science and ...

Technical Risk Assessment Handbook - Defence Science and ...

Technical Risk Assessment Handbook - Defence Science and ...

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

13<br />

linked to the key objectives of the project. A risk event can affect more than one<br />

objective <strong>and</strong> it is important to consider <strong>and</strong> list all objectives that are impacted. The<br />

risk assessment should be based on the highest impact where multiple objectives are<br />

impacted by a particular risk.<br />

<strong>Risk</strong> criteria<br />

3.24 <strong>Risk</strong> criteria are used to evaluate the significance of risk. The AS/NZS ISO<br />

31000:2009 st<strong>and</strong>ard 9 notes that risk criteria should be adapted to meet the<br />

objectives of the organisation <strong>and</strong> of the risk assessment.<br />

3.25 The following risk criteria have been developed to meet <strong>Defence</strong>’s requirements<br />

of the TRA, that is, to identify technical risks <strong>and</strong> issues for risk treatment <strong>and</strong> issue<br />

resolution, <strong>and</strong> to inform Government of the level of technical risk in a major<br />

project 10 . In some circumstances the PSTA may consider that it may be appropriate<br />

to adopt different risk criteria, such as for a highly-developmental project or for a<br />

project with significant safety risks. In those cases the PSTA may develop<br />

appropriate risk criteria in consultation with the Studies Guidance Group (SGG) of<br />

DSTO Projects <strong>and</strong> Requirements Division, who are responsible for technical risk<br />

policy <strong>and</strong> process in DSTO.<br />

3.26 As part of the risk assessment, each risk event identified is examined to<br />

estimate the likelihood of its occurrence <strong>and</strong> its impact on the project’s objectives to<br />

arrive at the risk itself. Any risk event which is assessed as having a likelihood<br />

greater than 50% is rated as More Than Likely, between 20-50% as Less Than<br />

Likely, <strong>and</strong> less than 20% as Unlikely.<br />

3.27 Once the likelihood is assessed, each risk event is examined to assess the<br />

impact of the event, if it were to occur, on the project’s objectives in terms of the<br />

required performance, supportability, safety, cost or schedule. The impact or<br />

consequence is expressed in terms of either Major, Moderate or Minor as follows:<br />

• Major: significant impact on achieving the project’s objectives, such as a<br />

significant reduction in performance or safety or a major shortfall in<br />

supportability.<br />

• Moderate: moderate impact on achieving the project’s objectives.<br />

• Minor: little impact on achieving the project’s objectives.<br />

3.28 Once the likelihood <strong>and</strong> impact for an event are determined, the risk<br />

assessment is expressed in terms of high (shown in Table 1 as red), medium (yellow)<br />

or low (green) as shown in the risk matrix at Table 1.<br />

9 St<strong>and</strong>ards Australia (2009) <strong>Risk</strong> management - Principles <strong>and</strong> guidelines, AS/NZS ISO 31000:2009<br />

10 Moon, T., Smith, J. <strong>and</strong> Cook, S.C. (2005). Technology Readiness <strong>and</strong> <strong>Technical</strong> <strong>Risk</strong> <strong>Assessment</strong><br />

for the Australian <strong>Defence</strong> Organisation. In Proceedings of the Systems Engineering, Test &<br />

Evaluation Conference, SETE 2005 – A Decade of Growth <strong>and</strong> Beyond, Brisbane, Queensl<strong>and</strong>.<br />

<strong>Technical</strong> <strong>Risk</strong> <strong>Assessment</strong> <strong>H<strong>and</strong>book</strong> Version 1.1

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!