Government
Running IT services in government
Functional standards, spend controls and the Technology Code of Practice, from an ITSM view.
Most relevant to Central gov Wider public
The framework around government IT
Central government departments and their arm's length bodies run IT services within a set of cross-government standards and controls:
| Instrument | What it does |
|---|---|
| GovS 005 Digital | The functional standard for managing digital, data and technology, including service management and the lifecycle of technology. |
| Technology Code of Practice | Criteria for designing, building and buying technology, used in spend controls. |
| Service Standard | The standard digital services are assessed against. |
| GovS 007 Security | The functional standard for protective security. |
| The Orange Book | HM Treasury's principles for managing risk. |
Spend controls mean significant technology spending needs central approval, judged against the Technology Code of Practice and, for services, the Service Standard. The central digital functions have been reorganised in recent years, so check GOV.UK for who currently runs spend controls and assessments.
Mapping ITSM to the functional standard
GovS 005 expects departments to manage technology services through their whole life: planning, design, delivery, operation, improvement and retirement. ITIL's service value chain maps onto it naturally:
| GovS 005 expectation | ITIL practices |
|---|---|
| Plan and govern digital services | Portfolio management, service financial management, governance |
| Design and deliver | Service design, change enablement, release, deployment |
| Operate and support | Service desk, incident, problem, service request, monitoring |
| Improve | Continual improvement, service level management |
| Manage suppliers | Supplier management, relationship management |
| Retire | Change enablement, records management, decommissioning |
Public sector considerations
- Show value for money: service costs, demand and performance should be visible and traceable, because they'll be scrutinised by finance, audit and Parliament.
- Expect multi-supplier ecosystems (often called service integration and management, or SIAM): you need clear ownership of end-to-end services when several suppliers each run a part.
- Legacy is a security risk: keep an inventory of unsupported technology and a plan for it.
Wider public sector
Local authorities, police, fire, education and other public bodies aren't bound by central government's functional standards and spend controls, but many use them as good practice. The Cyber Assessment Framework, the Service Standard and the Technology Code of Practice all translate well to local government.