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

Producer space

A record (opens in a new tab) Record The whole set of metadata held about one audiovisual work, kept as a single living object instead of scattered across spreadsheets and systems. created once, enriched automatically, and shared on the producer terms with each counterpart, who accepts it without re-keying.

In trial

The problem

A title is described, an identifier is looked up, a synopsis is written. Then it evaporates at the next handoff and gets re-keyed from scratch.

Every handoff loses metadata. Then someone rebuilds it.

Without TAMIS · re-keyed each handoff

Title · re-typed ISAN · looked up again Director · re-typed Synopsis · lost Barcode · still empty

No single handoff does anything wrong. It is the repetition that costs.

With TAMIS · found at its source, with provenance

Title · kept ISAN · kept Director · kept Synopsis · kept Barcode · kept

The same fields, as they were written: each one keeps who wrote it, and when.

How it works

  1. 01

    Create the record once

    The producer registers the work in its producer space. Auto-extraction pre-fills what it can: no blank form, no double entry.

  2. 02

    Enrich automatically

    ISAN (opens in a new tab) ISAN International Standard Audiovisual Number: the ISO identifier of an audiovisual work, which stays the same wherever the work travels. lookup and trusted registries add authoritative fields, each stamped with its provenance and date.

  3. 03

    Share selectively

    The producer decides what leaves the producer space, and for whom. Each counterpart receives what was agreed with it, on the producer’s terms.

  4. 04

    The counterpart receives validated metadata

    The record arrives clean and schema-valid, in a format the receiving systems can accept as-is.

  5. 05

    Corrected once, at the source

    A later correction is made in the producer space, where the value was produced. There is one place that holds what counts, so nobody has to guess which copy is right.

Who's involved

  • Production company

    Data provider

  • Post-production and delivery partners

    Data provider and data consumer

  • Broadcaster or distributor

    Data consumer

  • Identifier registry

    Data provider and service provider

What it takes

A 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. on the producer side, a contract covering each exchange, and an identifier agreed on before the work moves. Nothing is copied into a central store: the production keeps its data where it already is, and decides what each partner may read.

What it changes

  • No re-keying at hand-off
    The record arrives schema-valid, in a form the broadcaster’s systems accept as-is. The same fields are not typed a second time, so they cannot diverge a second time either.
  • Every field carries its origin
    Each value is stamped with where it came from and when. A disputed field can be traced back to its source instead of being argued over.
  • The producer decides what leaves
    The metadata stays in the producer space, and each counterpart receives what was agreed with it, nothing more. Sharing further is a decision taken once, not the side effect of sending a file.
  • Rights get paid to the right people, faster
    A work correctly identified in broadcast data is a work whose rights holders can be found. That means the right money reaching the right people, and reaching them sooner. See how broadcast data enrichment works

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