05.04.2013 Views

The Nimrod Review - Official Documents

The Nimrod Review - Official Documents

The Nimrod Review - Official Documents

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

10A.39<br />

10A.40<br />

Chapter 10A – <strong>Nimrod</strong> Safety Case: <strong>The</strong> Facts (Phases 1 and 2)<br />

Systems had “insufficient resource”, specifically in the Safety and Certification Department, fully to support<br />

the programme. This was echoed by Eric Prince in relation to the workload of the Systems Department on 3<br />

October 2002 at the internal NSC launch meeting. Eric Prince explained in evidence that the department was<br />

at the time “unusually busy” dealing with <strong>Nimrod</strong> and VC10 operational modifications, maintenance queries<br />

(PDS tasks) and putting together estimates.<br />

BAE Systems’ personnel were required to operate under tight budgetary constraints. <strong>The</strong> NSC was a ‘noncore’<br />

project and, therefore, had to be separately budgeted for and the man-hours monitored. If the manhours<br />

estimate was exceeded, BAE Systems’ Commercial Department had to be consulted. In an internal<br />

e-mail dated 8 October 2002, BAE Systems’ Customer Support warned Richard Oldfield (presciently): “we<br />

mustn’t go down the route of excessive planning/ undertaking tasks we have not budgeted for, and therefore<br />

will eat away at the hours we have.” Richard Oldfield explained that he and Chris Lowe seemed to have a<br />

“different idea” from Eric Prince and Witness C [BAE Systems] of what was involved in the project and this<br />

needed to be resolved. It is not clear, however, that this was ever resolved.<br />

It is regrettable that more thought and planning was not given by BAE Systems at an early stage to the<br />

question of resources for the NSC. <strong>The</strong> issue of inadequate manpower resources was to resurface regularly<br />

in the next couple of years and have a significant impact during the latter stages of finalising Phase 2 of the<br />

NSC in the summer of 2004.<br />

11 June 2002: QinetiQ Task <strong>Review</strong> Meeting<br />

10A.41<br />

At a QinetiQ Task <strong>Review</strong> Meeting (TRM) on 11 June 2002, it was noted that the PSWG had met in March<br />

2002 and, although QinetiQ’s role was still to be defined, “their involvement is not in doubt”. QinetiQ<br />

personnel did indeed remain involved in the NSC throughout, but the nature of their involvement was not<br />

what it should have been.<br />

August 2002: BAE Systems’ proposal for Phase 1<br />

10A.42<br />

10A.43<br />

In its formal Proposal for Phase 1 of the NSC dated August 2002, BAE Systems reiterated the theme:<br />

“By virtue of a range of traditional methods (certification and qualification/integrity<br />

testing), there is already a high level of confidence in the prevailing level of safety of<br />

<strong>Nimrod</strong> types. However, there is currently a lack of structured argument and supporting<br />

evidence formally recorded and maintained.” (emphasis added)<br />

<strong>The</strong> Proposal provided that the Zonal Hazard Analysis (ZHA) was to be the same as that for the Jaguar.<br />

10A.44 <strong>The</strong>re were to be two phases to the NSC process: Phase 1: the identification and initial assessment of hazards,<br />

the production of the Fault Tree and the completion of the ZHA. An important element of this phase was said<br />

to be the visit to, and assessment of, an MR2 and an R1; Phase 2: <strong>The</strong> population of the Hazard Log (HL) with<br />

evidence ‘mitigating’ each hazard identified during Phase 1.<br />

BAE Systems’ price for Phase 1<br />

10A.45<br />

Due to the short timescale, only one interim review meeting with the <strong>Nimrod</strong> IPT was proposed for Phase<br />

1. <strong>The</strong> price quoted by BAE Systems for Phase 1 of the NSC was £118,972, including 12% profit. This was<br />

based on an estimate of 1,524 man hours. Richard Oldfield explained in interview with the <strong>Review</strong> that it was<br />

difficult for BAE Systems to quote for the whole task because there were so many unknowns. Accordingly,<br />

BAE Systems decided to quote initially for Phase 1 only, before deciding what Phase 2 might entail. (It should<br />

be noted that the actual profit made by BAE Systems on Phase 1 was, in fact, 26.1%, primarily due to the<br />

man hours allocated to contract risk not being utilised, and the number of project management hours being<br />

less than originally estimated. By way of comparison, BAE Systems was in due course to make a loss of 8%<br />

on Phase 2, due to the actual number of hours recorded being greater than that estimated).<br />

199

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

Saved successfully!

Ooh no, something went wrong!