Technical Risk Assessment Handbook - Defence Science and ...
Technical Risk Assessment Handbook - Defence Science and ...
Technical Risk Assessment Handbook - Defence Science and ...
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
9<br />
Establishing the context<br />
Communication <strong>and</strong> consultation<br />
<strong>Risk</strong> assessment<br />
<strong>Risk</strong> identification<br />
<strong>Risk</strong> analysis<br />
<strong>Risk</strong> evaluation<br />
Monitoring <strong>and</strong> Review<br />
<strong>Risk</strong> treatment<br />
Figure 3: <strong>Risk</strong> management process<br />
Basis for assessing risk<br />
3.6 As defined in the AS/NZS ISO 31000:2009 st<strong>and</strong>ard, risk is the effect of<br />
uncertainty on objectives. The DMO Project <strong>Risk</strong> Management Manual 2010 (PRMM)<br />
states that the Government considers that a successful project is:<br />
‘a project that delivers a fit-for-purpose capability, as approved by<br />
Government, within the approved budget <strong>and</strong> schedule’ .<br />
3.7 ‘Fit for purpose’ according to the PRMM means that the delivered system is<br />
capable of conducting the missions required of it over its expected life. This includes<br />
the mission system <strong>and</strong> support system, cross-system design characteristics such as<br />
supportability, <strong>and</strong> support arrangements such as Australian Industry Involvement.<br />
3.8 To ensure a successful project, the project sets objectives for performance,<br />
supportability, safety, cost <strong>and</strong> schedule which must be met (as defined in the<br />
PRMM). Accordingly the technical risk assessment must be made against the<br />
objectives of the project. Further, the technical risk is assessed against the proposal<br />
for which approval is sought; that is the option set being presented to Government.<br />
3.9 The overall context <strong>and</strong> scope for a project is defined by the Preliminary<br />
Operational Concept Document (POCD) at First Pass <strong>and</strong> by the Operational<br />
Concept Document (OCD) at Second Pass. The required capability or performance<br />
<strong>Technical</strong> <strong>Risk</strong> <strong>Assessment</strong> <strong>H<strong>and</strong>book</strong> Version 1.1