Topic 46 o 64· Public value in digital government

Value o open data

The value o open data is the problem o estimatin whit government and public data is worth whan it has nae price: it isnae sauld, sae there's nae revenue line, yet releasin it (weather records, transport timetables, postcode boundaries, company registers) demonstrably generates economic and social activity doonstream. Valuin it weel maitters because "it's free tae release" and "it's worthless" are baith wrang, and a saftware ingineer decidin whether tae open an API or a dataset needs a better argument nor either.

Why it maitters

The maist-cited tap-doun estimate comes frae the McKinsey Global Institute's 2013 report "Open data: Unlocking innovation and performance with liquid information", which pit the potential annual value o open data across seven domains — education, transportation, consumer products, electricity, oil and gas, healthcare, and consumer finance — at $3 trillion tae $5 trillion a year globally, through mechanisms includin increased transparency, matchin supply tae demand mair efficiently, and enablin new products and services biggit on the data. That figure is a scenario estimate, nae a meisured outturn, and it is routinely misquotit as if it were revenue government could capture directly, whan the value maistly accrues tae third pairties — businesses, researchers, citizens — uisin the data, which is juist the pynt o openin it raither nor sellin it. The UK's Open Data Institute, co-foondit by Sir Tim Berners-Lee and Sir Nigel Shadbolt in 2012, has since biggit a body o mair granular, bottom-up case studies — sector by sector, dataset by dataset — that are faur mair uisefu for a real business case nor the McKinsey headline nummer, because they shaw the mechanism o value creation, nae juist its aggregate size.

The maths

Open data has nae market price, sae valuation methods staund in for ane; three approaches come up again and again, and nane is enough alane:

1. Cost-avoided / replacement-cost method:
   value ≈ what users would have paid to produce or licence the
   equivalent data themselves — a lower bound, ignores value created
   by uses the original producer never anticipated

2. Market-analogue / downstream-activity method:
   value ≈ revenue or savings generated by businesses/services built
   on the data (e.g. satnav apps built on open mapping and traffic
   data) — captures real economic activity but is hard to attribute
   cleanly to the data release itself (see additionality-and-deadweight)

3. Contingent/stated-preference method:
   value ≈ what users say they would pay, or the time they say it
   saves them — see stated-preference-valuation for the general
   method and its biases

None of these produces a figure as clean as a market price; credible
open data business cases triangulate across two or more, and are
explicit about which mechanism is doing the work.

Wrocht example

Illustrative national mapping/address data release (methodology after ODI-style case studies, figures illustrative of the scale such studies typically find):

Cost-avoided estimate:
  Businesses that would otherwise licence equivalent address-matching
  data commercially, at an estimated average licence cost of £4,000/
  year, across an estimated 15,000 SMEs now using the free open dataset
  = 15,000 × £4,000 = £60,000,000/year in avoided licensing cost alone

Downstream-activity estimate (more speculative, needs a counterfactual):
  New delivery-routing and logistics products built on the open data
  that would not exist, or would be materially worse, without it —
  requires a comparison against the counterfactual of the data staying
  closed or commercially licensed (counterfactual-analysis), because
  some of that activity would happen anyway on paid data at a higher
  price, which is deadweight in the "value created by opening it" sense

A defensible business case reports the cost-avoided figure as the
solid lower bound, and treats the downstream-activity figure as an
upper-bound scenario, not a fact.

For ingineers, the practical open-data-value question is usually narrower nor the national headline figures: does openin this specific API or dataset (raither nor keepin it ahint a pairtner agreement) increase reuise enough tae justify the ongoin cost o documentin, versionin and supportin it as a public interface? That maintenance cost is real and is the coonterpairt tae the big-ance-reuise-aften economics o government-as-a-platform — the twa topics are near cousins, ane aboot shared code and infrastructure, the ither aboot shared data. Ony open data value claim sud be checked agin additionality-and-deadweight afore it gaes in a business case: activity that wad hae happened onywey, on commercially licensed data, isnae value the openin created.

Pitfaws

  • Quotin the McKinsey $3–5 trillion figure as UK-specific or as this dataset's share: it's a global, seven-sector scenario estimate frae 2013 — uisin it as a precise multiplier for a single national dataset misrepresents whit the nummer is.
  • Nae coonterfactual: claimin credit for aw doonstream economic activity biggit on open data, wioot askin hou muckle o it wad hae happened onywey on paid or licensed data at a heicher price (see additionality-and-deadweight and counterfactual-analysis).
  • Confusin cost o production wi value created: a dataset that wis dear tae collect isnae automatically valuable tae release, and a cheap ane isnae automatically low-value — value follaes doonstream uise, nae upstream cost.
  • Ignorin the ongoin maintenance cost o "open": publishin a yin-aff CSV extract isnae the same commitment as rinnin a documentit, versioned, supportit open API — underfundin the latter efter the launch announcement is a common wey o failin.

Sources