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.

<strong>The</strong> <strong>Nimrod</strong> <strong>Review</strong><br />

10A.105 In the light of the above, there can be little doubt that Martyn Mahy and QinetiQ were expecting to conduct<br />

their own “review” of the completed NSC in due course, and to check and comment upon the substance and<br />

detail of what they found. <strong>The</strong> fact that there were no formal instructions to do so qua ISA was unfortunate;<br />

but QinetiQ’s status as ‘independent advisor’ in relation the NSC was clearly regarded as sufficient at the<br />

time.<br />

BAE Systems’ price for Phase 2<br />

59 10A.106 <strong>The</strong> WBS gave rise to a price estimate of £228,859.75 inclusive of profit. <strong>The</strong>re was some complaint from<br />

the IPT that this was too high. BAE Systems’ Commercial Department assured the IPT that BAE Systems was<br />

not “trying it on” and that the estimate had been based on the Statement of Work which had been jointly<br />

developed by Richard Oldfield and Frank Walsh and that since the NSC was a “high risk” project, it attracted<br />

the appropriate risk factor. (It is difficult to see, however, that searching archived reports might be said to<br />

be “high risk”.) On 23 January 2004, the commercial branch of the <strong>Nimrod</strong> IPT authorised BAE Systems to<br />

carry out the Phase 2 work for a price of £212,048.40. A six month period was allowed, with a start date of<br />

4 February 2004 and a finish date of 30 July 2004.<br />

BAE Systems’ own evidence<br />

10A.107 <strong>The</strong> <strong>Review</strong> has had to piece together the story of Phase 2 of the production of the NSC from the personal<br />

archives and notebooks of BAE Systems’ personnel that came to light very late in the day. A number of<br />

contemporaneous personal notebooks of BAE Systems’ personnel were produced, together with dozens<br />

of volumes of minutes of internal BAE Systems meetings, correspondence and other contemporaneous<br />

documents.<br />

Witness K [BAE Systems]’s Notebooks<br />

10A.108 <strong>The</strong>se contemporaneous documents and records proved illuminating. Of particular importance were the<br />

manuscript notebooks of Witness K [BAE Systems], an engineer in Mech Systems, whose line manager was<br />

Eric Prince (BAE Systems’ Flight Systems and Avionics Manager). <strong>The</strong>se provided a detailed and meticulous<br />

record of events as they unfolded, as well as a remarkably candid commentary of his unvarnished views at<br />

the time. On the surface, there was no reason to suppose that this project was not progressing relatively<br />

smoothly, with no major problems and with all those involved on the BAE Systems side confident in how they<br />

were going about it and confident as regards completing it on time and according to budget. <strong>The</strong> reality,<br />

however, was very different. Almost from the outset, the project was beset by delays, doubts and divisions.<br />

Early problems<br />

10A.109 <strong>The</strong>re were a number of problems which manifested themselves right from the outset regarding BAE Systems’<br />

handling of Phase 2. First, a lack of clear direction by BAE Systems’ management team as to how, in practice,<br />

the hazard mitigation process was to be carried out and the precise methodology to be employed. <strong>The</strong><br />

project management was poor from the start. Second, the man-hour estimates for the mitigation exercise<br />

were inadequate. It transpired that the original estimates given by the specialist departments had been for<br />

document searches only, and did not include time spent on analysing them. Third, the initial document<br />

searches revealed little by way of developmental reports in the archives which could be used for the purposes<br />

of hazard mitigating evidence. This was contrary to what had been envisaged and expected. Fourth, there<br />

were manpower resources problems, particularly with the Electrical Systems. Fifth, a difference of opinion<br />

as to approach, coupled with a clash of personalities, quickly led to significant tensions developing between<br />

two key members of the BAE Systems’ team (Chris Lowe and Witness K [BAE Systems]). <strong>The</strong>se tensions<br />

were allowed to fester and cause an element of paralysis of the project for some months. <strong>The</strong>se problems<br />

persisted. I analyse these issues further in Chapter 11.<br />

59 See Order Pricing dated 9 December 2003.<br />

214

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

Saved successfully!

Ooh no, something went wrong!