ntouk.com - Jerry Fishenden's technology policy blog

Last week saw the publication of the new UK Government policy on open source software (those of you following my tweets will have picked up on this before its launch). It's broadly in line with what had been predicted, focused on the need to ensure best taxpayer value in the procurement of IT services and systems.

I believe it's a sensible and balanced policy that reflects the maturity of the wider debate in the UK. This debate has already largely moved on from the immature "open source versus commercial software" style fallacy of some 5 or so years ago, to one that recognises the spectrum of software development methods and licensing models that exist. The reality of course was always different than the sort of binary or polar opposites that some once tried to suggest (witness for example the open source community at Microsoft). Which is why the attempt by some countries to impose procurement mandates in favour of one particular type of software, such as open source, has not proved successful or cost-effective. Governments need to encourage competition and choice if they are to secure cost-effective, agile IT solutions. And this is what the new Cabinet Office policy is clearly aimed at doing, rather than seeking to distort the market.

As well as reviewing its policy on open source software, the update also included a refresh of thinking around open standards and re-use. I have long been a keen advocate and supporter of moves such as passing over the Microsoft Office file formats to independent, standards-body control. Standards have a key contribution to play in achieving interoperability and despite the artificial controversy stoked up in some quarters by opponents of Microsoft becoming more open, the adoption of Office Open XML as an ISO standard was the right thing to do on so many fronts.

The re-use area has been one that I think has been under-developed, so it's welcome to see this given such a high priority. Initiatives such as the Shared Learning Group have already been focusing on how the public sector can ensure greater efficiencies and service improvements from better sharing. The aim of furthering the ideas of a Sourceforge/Codeplex for smart re-use across the public sector is something that I hope will gather widespread support and momentum from right across the IT spectrum.

As with the work of the Shared Learning Group, it's important however that we don't just look at this from the narrow prism of software alone. After all, software costs only account for a small amount of most IT projects (averaging around 5%). However, some 60%-70% is estimated to go on IT services, notably the use of large systems integrators whose specialism is in bespoking and integrating components from many sources. So what we need to re-use is also best practice around project and programme management and end-to-end solutions rather than just point software alone. There are real savings to be made in streamlining the way solutions are specified, procured and deployed, and some of the biggest of these are going to come from squeezing the high level of services costs traditionally associated with public sector IT projects.

Likewise, we also need to see more real opportunities for small and medium enterprises (SMEs) to become actively engaged with public sector IT projects: after all, despite the government's stated intention of awarding 30% of contracts to SMEs, the top 20 IT suppliers account for over 70% of all spending. And yet 64% of commercial innovations come from small firms.

As with any government policy, it's the reality of how it operates on the ground that will matter of course. And I think that the wider IT community, regardless of where it sits on the software model / commercial model spectrum, will welcome any move that is about smarter procurement, better governance and more efficient and effective use of technology in the public sector. A level playing field in which the best product or service for a particular need can be properly assessed is what we all want to see. And if this new policy helps ensure that happens, it can only be a good thing.

Technorati tags: interoperability open source Cabinet Office technology policy procurement innovation standards