CONTROLLING SLIPPAGE
183. The Astute submarine, Type 45 destroyer and
Nimrod MRA4 aircraft programmes have experienced substantial in-service
date slippage. In the Major Projects Report 2007, the total in-service
date slippage for these three programmes was 166 months, some
14 years. The A400M programme has also experienced slippage and
JSF aircraft will not be available to operate from the first of
the new aircraft carriers, which is expected to enter service
in 2014. We asked what the MoD was doing to control the in-service
slippage seen on equipment programmes and the lessons that had
been learned. Mr Gould considered that "time has a different
characteristic from performance and cost" as:
Performance and cost can be bound contractually and
legally. You can say that you will not make a milestone payment
until a certain level of performance has been demonstrated and
so on. You can certainly make the schedule contractually binding,
but you cannot make it obey the laws of physics if it does not
want to. The laws of physics have their results towards the end
of a programme, because you find difficulty in a programme....
when you begin to do your system test and you cannot do that until
you have a prototype on which to do it. What it means is that
you are carrying not so much risk but a degree of uncertainty
into quite a late stage of a complex technological project.[276]
184. Mr Gould said that one of the things the MoD
was now putting back into project management skills, and it needed
to do more, was the requirement "to pay critical attention
to the contractor's schedule and consider whether it is really
credible". He considered that MoD staff needed the ability
"to look at a schedule with as much skill as the contractor".
[277]
185. Substantial
in-service date slippage on major equipment programmes has often
been a result of over-optimistic estimates by contractors of the
likely programme schedule. It is, therefore, worrying to learn
that the MoD only now acknowledges that it needs to include in
the project management skills of its staff the ability to examine
a contractor's programme schedule and consider whether it is credible.
In its response to our report, we look to the MoD to set out how
it plans to up-skill its staff working in defence acquisition,
so that they are able to examine critically the estimates provided
by contractors both in relation to a programme's schedule and
cost.
186. A technique being introduced by the MoD on equipment
projects is Earned Value Management (EVM). Mr Gould explained
that this technique:
requires you to prepare a very detailed work breakdown;
it is a schedule broken down into work packages. That allows you
to measure on a weekly basis exactly what progress is being made
on a project so you can predict problems early on. Therefore,
you know you have control and shared data.[278]
187. EVM is used in the United States on equipment
projects as it is a requirement of the Department of Defense.
The MoD is now using the technique on the Astute submarine and
Nimrod MRA4 programmes and plans to use it on all equipment projects.
Mr Gould told us that the MoD will not make a Main Gate decision
unless the contractor has convinced it that it has "in place
and are sharing with us the management toolsthe EVM techniques
and othersthat we need so they can demonstrate progress".
[279]
188. We note
that the MoD is introducing techniques, such as Earned Value Management,
to improve its visibility of the progress on equipment programmes
and to identify potential problems as early as possible. We look
to the MoD to assess whether the expected benefits are delivered
by such techniques and, where they have been, to ensure that they
are adopted on other programmes. We also expect the MoD to learn
from the experience of the US Department of Defense in using Earned
Value Management, such as on the Joint Strike Fighter programme.
189. There is often a substantial time-lag between
the date an equipment meets its in-service date and the date when
the equipment can be operated by the Armed Forces. For example,
Typhoon achieved its in-service date, defined as the date of delivery
of the first aircraft to the RAF, in June 2003.[280]
However, the first operational squadron of Typhoon aircraft was
formed on 31 March 2006.[281]
Mr Gould said that the MoD would be focusing more:
on the lines of development[282]
as well as training rather than the kit and testing it so that
we look not just at ISD but initial and full operating capability
and work to those schedules. What is now happening on projects
is that when we have enough system performance we start to train
the crews, soldiers or whoever even though there is still some
development to be done so they can effect the final stage of development
and become familiar with the system and get it into service quicker.[283]
190. We
note that the MoD is paying more attention to the date at which
equipment can deliver initial and full operating capability, rather
than just the in-service date. Starting the training of the users
of equipment, even where there is some further development work
to be completed on an equipment programme, should allow the equipment
to enter operational service more quickly.
CHANGE CONTROL
191. One of the criticisms that we have often heard
from industry is that the MoD changes the requirements and specifications
of the equipment it has ordered. These changes lead to increased
costs. CDM acknowledged that there was "requirement creep
.
and customers, in this instance front line commanders, will often
change their minds". He said that the MoD needed to be fairly
rigorous about this, although it might arise because the threat
had changed.[284]
192. We asked how the MoD was addressing the issue
of requirement creep. CDM's view was that there was a good case
for having equipment "that is 80% right now", with an
open architecture that could be built on incrementally as changes
occurred.[285] The
approach which the MoD was seeking to drive forward now was to:
have an open architecture with incremental upgrading
and innovation to be added as required either by the threat or
as research and technology develop something much better.[286]
Mr Gould stressed the need for "good change
control" as a fundamental of good project management.[287]
He said that good change control started with having a "really
good common understanding on both sides as to the project outcome
that is expected".[288]
193. Cost
increases on equipment programmes have often arisen from 'requirement
creep'additions and changes to the specification of equipment
already ordered. We note that the MoD is seeking to address this
by acquiring equipment which meets the vast majorityaround
80%of the military customer's requirement, but which also
has an 'open architecture' allowing incremental upgrading and
innovation to be added later. This appears to be a sensible approach,
but DE&S must ensure that staff who work in project management
have sufficient training in key skills such as good change control.
146 HC (2005-06) 554 Back
147
Defence Committee, Seventh Report of Session 2006-07, The Army's
requirement for armoured vehicles: the FRES programme, HC
511 Back
148
HC (2006-07) 56 Back
149
HC (2007-08) 61 Back
150
National Audit Office, Major Projects Report 2007, HC 98-I
Session 2007-2008 and National Audit Office, Major Projects
Report 2007 Project Summary Sheets, HC 98-II Session 2007-2008 Back
151
Main Gate approval was announced on 25 July 2007, after the period
covered by the Major Projects Report 2007. The Approved Cost at
Main Gate was £3.9 billion and the Approved ISD for the two
carriers was 2014 and 2016 Back
152
HC (2007-08) 61 Back
153
Ibid, p 23 Back
154
Ibid, Q 96 Back
155
Ibid, para 59 Back
156
Ibid, Q 97 Back
157
Ibid, Ev 34 Back
158
Ev 32-33 Back
159
Q 76 Back
160
Q 124 Back
161
Q 76 Back
162
Q 154 Back
163
Qq 155-157 Back
164
HC Deb, 27 February 2008, Col 1576W Back
165
Q 120 Back
166
Q 121 Back
167
Ev 40 Back
168
Q 123 Back
169
Q 123 Back
170
Ev 34-35 Back
171
National Audit Office, Major Projects Report 2007 Project Summary
Sheets, HC 98-II Session 2007-2008, p 143 Back
172
Q 129 Back
173
Q 127 Back
174
Q 128 Back
175
Ministry of Defence, Autumn Performance Report 2007-08 Back
176
HC (2007-08) 61, Q 97 Back
177
Ibid, para 63 Back
178
Q 78 Back
179
Qq 79, 85 Back
180
Q 97 Back
181
Q 98 Back
182
Qq 99-101 Back
183
Ev 42 Back
184
Defence Committee, Eleventh Report of Session 2006-07, Strategic
Lift, HC 462 Back
185
Ibid, paras 74-77 Back
186
HC (2007-08) 61, para 66 Back
187
Ibid, para 67 Back
188
Q 107 Back
189
Ibid Back
190
Ibid Back
191
Ev 42 Back
192
Q 108 Back
193
Q 110 Back
194
Q 111 Back
195
Q 88 Back
196
Q 107 Back
197
HC (2006-07) 159 Back
198
Ibid, paras 75-76 Back
199
The former Minister for Defence Equipment and Support Back
200
HC (2006-07) 159, para 85 Back
201
Ev 35 Back
202
Ev 35-36 Back
203
Ev 36 Back
204
Q 181 Back
205
Q 189 Back
206
Q 184 Back
207
Qq 185-186 Back
208
Q 186 Back
209
Q 187 Back
210
Ibid Back
211
Q 182 Back
212
Ibid Back
213
HC Deb, 18 February 2008, Col 99W Back
214
HC (2007-08) 110, para 67 Back
215
HC (2005-06) 554 Back
216
Ibid, Ev 43 Back
217
Ibid, Ev 40 Back
218
National Audit Office, Major Projects Report 2004 Project Summary
Sheets, HC 1159-II, Session 2003-2004, p 49 Back
219
HC (2005-06) 554, Ev 41 Back
220
Ibid, para 90 Back
221
Defence Committee, Seventh Report of Session 2005-06, The Defence
Industrial Strategy, HC 824, paras 30-34 and 97-99 Back
222
HC (2006-07) 56, paras 49-65 Back
223
Defence Committee, Sixth Report of Session 2006-07, The Defence
Industrial Strategy: update, HC 177, paras 15-20 and 81-87 Back
224
Ibid, para 19 Back
225
Ibid, para 86 Back
226
HC Deb, 25 July 2007, Col 865-866 Back
227
HC Deb, 27 February 2008, Col 1576W Back
228
Ev 33 Back
229
HC Deb, 7 January 2008, Col 20W Back
230
Q 114 Back
231
Q 144 Back
232
Q 115 Back
233
Q 118 Back
234
Q 136 Back
235
Q 137 Back
236
Q 139 Back
237
Q 140 Back
238
Q 141 Back
239
Q 145 Back
240
Q 146 Back
241
Q 153 Back
242
Scottish Affairs Committee, uncorrected transcript of oral evidence
taken on 29 January 2008, Q 42 Back
243
Q 143 Back
244
Q 150 Back
245
Q 177 Back
246
Ev 40 Back
247
Qq 151-152 Back
248
Ev 33 Back
249
Q 148 Back
250
"MoD offered £100m saving on carriers", Financial
Times, 21 January 2008 Back
251
Q 131 Back
252
Ministry of Defence website, Defence News, 11 February
2008, "£35m contract allows assembly of Navy Super Carriers" Back
253
National Audit Office, Major Projects Report 2007 Project Summary
Sheets, HC 98-II, Session 2007-2008, p 75 Back
254
Defence Committee, Second Report of Session 2005-06, Future
Carrier and Joint Combat Aircraft Programmes, HC 554, Ev 42 Back
255
Q 158 Back
256
Q 159 Back
257
Q 160 Back
258
Q 161 Back
259
Q 169 Back
260
Q 171 Back
261
Q 172 Back
262
Q 173 Back
263
Q 175 Back
264
Q 178 Back
265
Q 179 Back
266
The Joint Strike Fighter was selected to meet the requirement
for Joint Combat Aircraft (JCA) Back
267
Q 180 Back
268
Qq 162-163, 165 Back
269
Q 164 Back
270
Q 166 Back
271
Q 81 Back
272
Q 84 Back
273
Q 102 Back
274
Q 103 Back
275
Q 104 Back
276
Q 113 Back
277
Ibid Back
278
Ibid Back
279
Ibid Back
280
National Audit Office, Major Projects Report 2007, HC 98-II
Session 2007-2008, p 159 Back
281
Ibid, p 153 Back
282
The Lines of Development are Concepts & Doctrine, Equipment,
Force Structure, Manpower, Training, and Sustainability (including
Infrastructure) Back
283
Q 113 Back
284
Q 48 Back
285
Q 49 Back
286
Q 50 Back
287
Ibid Back
288
Q 54 Back