Category Archives: Government IT

Met Office has IBM secondee as CIO

By Tony Collins

The Met Office gained ministerial approval to appoint an IBM employee for a year as secondee CIO, until the end of October 2011, according to information released under the FOI Act.

It appears that the salary of the IBM executive David Young is being paid, at least in part, by the Met Office. In documents released under the FOI Act the Met Office has redacted [edited out] details of Young’s proposed remuneration and performance bonus.

As a trading fund within the Department for Business, Innovation and Skills, the Met Office is required to operate on a commercial basis. It was part of the Ministry of Defence at the time of Young’s appointment. His recruitment was approved by the Secretary of State.

Internal emails show that the Met Office apparently overcame a recruitment ban and constraints on secondments.

Having your CIO seconded from your biggest IT supplier may be novel but it could be controversial because of the perception of a potential conflict of interest.

It would not the first time a public authority has been involved in a controversy after seconding an IBM employee as head of IT.

In 1993 a report of the district auditor criticised the then Wessex Regional Health Authority after it transpired that a member of the health authority was a director of IBM. The IBM director at Wessex promoted a controversial and successful bid for core systems to be supplied to the health authority by IBM and Andersen Consulting (later Accenture). The director later asked that his letter lobbying for the contract be destroyed.

The auditor also found that the Wessex authority bought an IBM mainframe without proper legal authority, the members of the authority having not been informed. The authority paid an unnecessarily high sum for the mainframe and there were doubts the machine was needed. A decision to proceed with the purchase of the mainframe at Wessex was made on the advice of the regional health authority’s new regional information systems manager who was an IBM secondee.

The Met Office, however, has given full consideration to the potential for a conflict of interest in appointing Young as its CIO. It said in a statement this week:

“Full consideration of any potential conflicts of interest regarding David Young’s appointment were fully considered prior to his appointment and his terms of engagement specifically cover these.

“The Met Office complies with specific rules set by the government with regard to procurement and purchases of IT equipment must be agreed by the Met Office Executive.”

The Met Office is one of IBM’s biggest customers. It says on its website: “We are now using an IBM supercomputer which can do more than 100 trillion calculations a second. Its power allows it to take in hundreds of thousands of weather observations from all over the world which it then takes as a starting point for running an atmospheric model containing more than a million lines of code.”

The Met Office reports that Young is responsible for the organisation’s IT strategy and ensuring that it adapts to support the business strategy.

Its website says that Young worked for IBM but does not make it clear he is still employed by the company while on secondment to the Met Office. It says that before joining the Met Office he “held a number of executive position within the IT industry, working for IBM, CSC and Siemens”.

Young’s Linked In profile says he is CIO at the Met Office and Director, System zStack and Mainframe Platform, Central Eastern Europe, Middle East and Africa at IBM.

In response to an FOI request by Dave Orr, the Met Office has released internal emails relating to Young’s recruitment and later appointment. Young is described in the Met Office’s Register of Interests 2010/11 as an “Executive, IBM UK Ltd (non-active)”.

The email exchanges show that the Met Office was keen and anxious to employ Young. Talks over Young’s recruitment, initially as Chief Technology Officer, began in July last year and took several months to conclude.

In August 2010 John Hirst, Chief Executive at the Met Office, wrote to Young mentioning, among other things, a ban on recruitment.

“It was good to talk to you on the phone this afternoon. This is to confirm that you are interested in joining us at the Met Office and we are interested in offering you a post.

“As we discussed there are issues of the recruitment ban, terms of secondment and security clearances amongst others but we have both declared an intent to try and get something organised between us.”

Also in August 2010 Diana Chaloner, the Met Office’s Director of Human Resources, emailed IBM on the costs and restrictions relating to the “possible secondment of David Young”.

Her email said: “I will need to get confirmation from John Hirst (our CE) before committing to the costs as outlined below. Whilst I don’t see it as a problem, I do also need to seek a way to overcome external secondee restrictions placed on us by central government recently. I will attempt to get this moving as quickly as possible at this end.”

In another email to IBM in August 2010, Chaloner referred again to the costs of seconding Young. She said:

“Following John’s earlier meeting with David (in his garden!) Alan Dickinson [then the Met Office’s Director of Science and Technology] and I met him last week. John has now spoken to David and is keen to try to progress a secondment. I know David is very keen too, but inevitably, with all the various restrictions placed on us, cost may be an issue, as will enabling the secondment contract to be approved.

“Whilst this might be quite challenging , I think there are usually ways to manage these things, so would really like to understand cost and timing…”

The following month, September 2010, Chaloner emailed Hirst on the need for Young’s appointment to be approved.

Her email has in the subject heading: “IBM Confidential: Secondment of David Young to the Met Office”.  Says the email: “At the moment we cannot give a precise date for David to start his secondment. I did mention in an earlier email that there are some added constraints across Government, and one of those is around recruitment and secondments…”

In October 2011 Hirst emailed IBM about a possible delay in appointing Young. “I am sorry this has taken so long and been more complex than anticipated but the rules of engagement have changed at least twice over the last couple of months and therefore keeping things moving forward steadily has been more difficult. I am still confident we can conclude this although I have suggested to David we might need a weeks (sic) delay in starting … the contracts are signed and sitting in my draw awaiting final clearance of the admin hurdles so there is no decrease in my intent to make this happen.”

On 29 November 2011 Chaloner wrote to Hirst saying that Young’s appointment needed the approval of the Secretary of State. “… The situation is looking very positive but we require final approval from Secretary of State. I was told that there seemed no reason for the secondment not to be approved, but it has to go through the appropriate channels. I can only apologise in the delay in David starting, and continue to nudge it from this end, almost on a daily basis.”

Young was appointed by the end of December 2010. The business case for a new Chief Technology Officer (which became a CIO role) says the secondment from IBM would finish on 31 October 2011. It says there is a “need to bring a professional IT expert into the organisation, to reshape the function in order to achieve greater efficiency in delivery of information technology, as well as ensure it is fit for purpose in the future, hence the need, at this time, to manage this as a short term secondment.”

The Job Description, which is headed “Management in Confidence”, says the IBM secondee will “lead the IT function in the effective delivery of 24/7 IT services and enhance our world leading supercomputing and infrastructure capabilities to secure achievement of future corporate objectives.” The main responsibilities will include directing and co-ordinating 300 information technology, programme/project management professionals, and support staff…”

The job also involves overseeing the “selection, acquisition, development and installation of major information systems”. It further includes the need to “determine and manage all outsourced  external IT service provision as appropriate to meet service level agreements.”

Comment:

There is nothing wrong with the Met Office’s decision to hire an IBM secondee except perhaps that it underlines the reliance of the public sector on its major suppliers.

It’s clear that the Met Office has struggled hard to employ David Young because of his expertise. Nobody would understand the Met Office’s IBM systems better than IBM.

But we have seen evidence from the National Audit Office that suppliers all too often understand customer installations in the public sector better than the civil servants know their own systems. In the case of the NPfIT, auditors had to rely on suppliers to explain what they had been paid and why.

It’s time for the civil service to build up its expertise so that it ceases to rely on suppliers that dominate government IT.

One reason it’s hard for civil servants to innovate?

By Tony Collins

James Gardner has seen for himself the institutional obstacles to innovation. . He was, in effect, chief innovator [CTO] at the Department for Work and Pensions. He now works for Spigit.

In a blog on the need for innovators to have “courageous patience” he quotes the British politician Tony Benn who used to be Minister of Technology in the Wilson government:

“It’s the same each time with progress. First they ignore you, then they say you’re mad, then dangerous, then there’s a pause and then you can’t find anyone who disagrees with you.”

He also quotes Warren Bennis who, he says, established leadership as a credible academic discipline:

“Innovation— any new idea—by definition will not be accepted at first. It takes repeated attempts, endless demonstrations, monotonous rehearsals before innovation can be accepted and internalized by an organization. This requires courageous patience.”

Patience comes easily in the civil service but courage? The courage to spend a little with inventive SMEs rather than a lot with large systems integrators? Perhaps this is why it’s so hard to get central departments to innovate.

Some ways to change government practices

By Tony Collins

Mark Foden, a consultant to the public sector, says that transformation is much more likely to come about through collaboration and small incremental changes than strong-arm tactics such as mandation and regulation.

He also suggests that rather than pay high-cost contractors, government should pay more for talented specialists – and possibly pay them much more than their managers.

Foden has worked within government for many years and has seen some of what works and doesn’t. He advocates the use of internal social networks within and across departments.

He sets out his views in a critique of a report of the Public Accounts Committee on Information Communications and Technology in government.

Foden’s views are to some extent in line with the so-called “nudge” non-regulatory approach to behaviour change. Nudge was used originally by Richard Thaler and Cass Sunstein who define it as:

“… any aspect of the choice architecture that alters people’s behaviour in a predictable way without forbidding any options or significantly changing their economic incentives. To count as a mere nudge, the intervention must be easy and cheap to avoid. Nudges are not mandates. Putting the fruit at eye level counts as a nudge. Banning junk food does not”.

These are some of the points Foden makes:

Systemic change. It isn’t enough to change policy, process and structure and hope that deeper, more systemic, changes will naturally follow.

Targets. There is a deep-grained, almost unquestioned, culture of using targets to control performance. “Often, targets drive target-meeting behaviours rather than performance-improving ones…Measuring, on the other hand, is crucial; but it must be used in the spirit of learning and developing rather than explicitly for controlling…”

Language. Be careful how you use expressions such as “buy-in” and “deliver”.  Buy-in suggests something that is decided by one group of people then ‘sold’ to another. This is just not a great model for helping civil servants feel involved and empowered. “If people are going to play an important part in achieving something then they must be, and feel, involved from the beginning. Just using terms like this creates the wrong dynamic. Rather than cautioning about not achieving buy-in the Public Accounts Committee should be encouraging more-open, more-inclusive behaviours.” Deliver, says Foden, is too transactional. “I just can’t get the ‘deliver a parcel’ sense out of my head: something neatly packaged then sent to a recipient at a specific time. Managing change is just not about this.”

SMEs. “To get benefit from working with SMEs Government will need to bend, in perhaps significant ways; and people will need to behave differently. This is new territory: time should be taken to experiment and find out what approaches flourish. The useful approaches should be developed – incrementally – in much the same way the strategy proposes IT be developed. And this may take years.

Lean. “Change cannot be made by feeding new policy into an old machine. “Government will need to reshape (and that’s not ‘reorganise’) itself dramatically – perhaps using ideas like Lean – and, to do that, it will need to foster new behaviours; like being more open, being naturally collaborative and being more entrepeneurial. The Efficiency and Reform Group [of the Cabinet Office] should attend explicitly to nurturing such new behaviours.

Pay specialists more than their managers? “If government wants more talent, then it must be able pay the market rate for the people it needs and then provide them with hugely satisfying work in an affirming, supportive environment so that they stay around. This will be far cheaper and, in most cases, better than hiring long-term contractors. If this means paying specialists (sometimes considerably) more than their managers, so be it. There’s a real cultural hump to be got over here.”

More on Mark Foden’s views

MPs criticise PFI value for money and the MoD’s failure to invest in effective logistics systems

By David Bicknell

Two parliamentary committees, the Treasury Select Committee and the Public Accounts Committee, have today made strong criticisms about the use of private finance initiatives (PFI) and of IT systems for defence logisitics.

In its report, the Treasury Select Committee suggested that PFI funding for new infrastructure, such as schools and hospitals, does not provide taxpayers with good value for money and stricter criteria should be introduced to govern its use.

The Committee’s chairman, Andrew Tyrie MP, said:

“PFI means getting something now and paying later. Any Whitehall department could be excused for becoming addicted to that. We can’t carry on as we are, expecting the next generation of taxpayers to pick up the tab. PFI should only be used where we can show clear benefits for the taxpayer. We must first acknowledge we’ve got a problem. This will be tough in the short term but it should benefit the economy and public finances in the longer term.

“PFI should be brought on balance sheet. The Treasury should remove any perverse incentives unrelated to value for money by ensuring that PFI is not used to circumvent departmental budget limits. It should also ask the OBR to include PFI liabilities in future assessments of the fiscal rules. 

We must also impose much more robust criteria on projects that can be eligible for PFI by ensuring that as much as possible of the risk associated with PFI projects is transferred to the private sector and is seen to have been transferred.”

In its report on the defence logistics supply chain, the Public Accounts Committee was critical that the MoD had made little progress in resolving long-standing problems with its supply chain information, despite giving previous assurances to the Committee.

Its recommendations for improving future performance include the following comments:

The Department accepts that historic underinvestment has meant its management information systems and the underlying IT systems are not up to the task. In particular, its spending on IT systems has not kept pace with the need to upgrade those systems.

 “The Department has made investments in new data systems – for example £66 million has been spent on the Management of the Joint Deployed Inventory system which tracks equipment in theatre – and more is planned.

“In 2010, the Department signed an £803 million, 11-year contract with Boeing for the provision of the Future Logistics Information Services project. Under this contract, Boeing is required to bring together 270 different data systems operated by 50 different contractors, which should provide a complete and coherent set of data for managers to use.

“Separately, the Department has now approved an additional £75 million to upgrade some of the defence base inventory management systems that are now at critical risk of failure.

“The implementation of the Future Logistics Information Services project, including the additional upgrade to the warehouse inventory management IT system, will not be complete until 2014. The Department told us it would take a long time to upgrade systems and data, in part because of the need to ‘cleanse’ the data – otherwise the poor quality information the Department currently holds would simply be transferred onto a better IT system.

“We are very concerned that, until the systems are fully rolled out in 2014, the high risk of system failure will remain in systems that are critical to supporting front line troops. To ensure that there is no further slippage in this critical area, the Department has provided us with a plan of the scheduled projects for improving data systems and has promised to report back in six and twelve months on how it is performing against its milestones.”

(Tony Collins is away this week.  But he’ll be back shortly to offer his unique insight on Government and public sector IT projects)