Skip to content
Event Meet us at IBC 2026 · RAI Amsterdam, 11–14 Sept · EBU stand 10.D21 Plan your visit →
Collaboration in production chain

Broadcast data enrichment and exchange

Turning broadcast logs that identify works inconsistently into data a collective management organisation can act on.

In trial

The problem

A collective management organisation has to pay the rights of works aired on dozens of channels. But broadcast logs identify those works inconsistently from one source to another. Finding the right rights holders therefore means manual reconciliation, spreadsheets, and email exchanges where mistakes are easy. At scale that is around 48 exchanges a year, each carrying in the order of 60000 broadcasts.

How it works

  1. 01

    Import the broadcast data

    An audiovisual archive institute imports its broadcast data into its own TAMIS application.

  2. 02

    Publish to the data space

    Its connector (opens in a new tab) Connector The software component a participant runs, or has run for it, to exchange data inside the data space. It enforces identity, contracts and policies. publishes the dataset into the data space (opens in a new tab) Data space A decentralised infrastructure enabling trustworthy data exchanges based on commonly agreed rules. .

  3. 03

    Match the identifiers

    The identifier registry receives it and runs its matching service. Unresolved cases go to human review inside the registry interface.

  4. 04

    Return the enriched data

    The registry returns the data enriched with standard audiovisual identifiers.

  5. 05

    Expose under contract

    The archive institute exposes the dataset, enriched or not, to the collective management organisation under contract.

  6. 06

    Identify and pay

    The rights manager receives it in its own TAMIS application and uses it to identify rights holders and trigger payments.

Who's involved

  • Holder of the broadcast data

    Data provider and data consumer

  • Identifier registry

    Data provider and service provider

  • Collective management organisation

    Data consumer

What it takes

A connector on each side, a contract covering the exchange, and an agreement on the identifier used as the pivot.

What it changes

  • Duplicates get resolved, and the identifiers spread to the other databases.
  • Rights holders are identified reliably, so royalties reach the right people.
  • The delay before rights are distributed gets shorter.
  • Up to 30% of operating costs saved on rights management, content acquisition and quality control, as announced in the pilot.
  • File tracking and version management on the data holder’s side.
  • Without TAMIS: human reconciliation, spreadsheets, and identification that may simply be wrong.

Want this running in your organisation?

Tell us where you would sit in it. We come back with what it would take on your side, and who else has to be involved.

Book a demo Back to use cases