Identified Risk (risk identified by standard project risk management processes)

Description

Remedial Action

Phase 2.1

There are no outstanding risks associated with this sub phase as it is technically complete.

N/A

Phase 2.2

There are no outstanding risks associated with this sub phase as it is technically complete.

N/A

There is a chance that the upgraded F/A-18 A/B Electronic Warfare system will be affected by the inability to adequately test the Electronic Warfare threat libraries leading to an impact on safety.

The Phase 2.3 project developed a Memorandum Of Understanding with Airborne Self Protection Systems Program Office to purchase a new simulator and the identification of lower level activities. Remedial action was successful. Consequently, this risk is to be retired.

Phase 2.3

There is a chance that the F/A-18 A/B Operational Flight Program test program will be affected by the late delivery of the first F/A-18 Electronic Counter Measures (ECM) jammer pod leading to an impact on schedule and performance.

Flight testing commenced on schedule with a modified F─111 variant. However, late delivery of the F/A-18 variant has delayed some elements of the integration testing. This is now being managed as an issue.

There is a chance that Australian Unique Software Loads will not be compatible with HACTS leading to an impact on performance project cost and schedule.

HACTS Program Office is developing mitigation strategies with Key Stakeholders to address the risk and enable future loading of Australian Unique Software Loads.

HACTS

There is a chance that HACTS capability will not be optimised and/or rectified leading to an impact on performance.

HACTS Program Office and Prime contractor are developing a Common Identification Document to capture all Air Combat Group Issues and activities of concern. This document will enable all parties to communicate and prioritise treatment of any known issues.

Emergent Risks (risk not previously identified but has emerged during 2009-10

Description

Remedial Action

Phase 2.3

The delivery of F/A-18 Mission Computer (MC) Australian Unique software load number 8 (Austblock 8) is dependent on delivery of MC data from the US Navy, which is in turn dependent on the flight test program. There is a risk that delays in data delivery from the US Navy, flight testing or Austblock 8 development will delay FOC.

The Austblock 8 developers (Integrated Avionics System Support Facility) have been liaising with the USN regarding data deliverables, and prioritised the deliverables based on the Austblock 8 schedule.

Phase 2.3

The EL/L-8222 Electronic Counter Measures (ECM) pod requires routine servicing (as regularly as six months) and without in-service support arrangements in place, this servicing cannot be completed. There is a risk that because of the late contracting activities, there will be no EL/L- 8222 In-service Support in place by the Final Operating Capability Milestone.

Returning pods to Israel for servicing is not a feasible long term or large scale option due to long transport delays and security issues. The development of a Contract Change Proposal to the Acquisition contract to include minimal support arrangements has been instigated and is being progressed as a high priority. The critical action is to expedite the progression of the EL/L-8222 In-service contract.