How a use case gets into TAMIS

What to bring

• The data you hold, and the data you need. Naming both is most of the work.
• Who else has to be involved for the exchange to make sense. A use case with a single participant (opens in a new tab) Participant An organisation admitted to the data space, identified under its rules and able to exchange within it. is a tool, not an exchange.
• What goes wrong today. The cost of the current situation is what makes a use case worth building.
• What would have to be true for you to rely on it: identifiers, contracts, quality, timing.
• Nothing confidential. A first description does not need your figures.

What happens next

1. 01

   You send a description through the contact form. A few paragraphs are enough to start.

2. 02

   We come back to you, and we work out the exchange together: what moves, between whom, and on what terms.

3. 03

   We look for the other participants it needs, and we help you find them. That search is part of the work, not a condition you have to meet first.

4. 04

   It enters the roadmap as a concept, and appears on this site with that status, honestly. A case still looking for a counterpart says so, rather than disappearing.

5. 05

   It becomes a trial when partners commit to running it with real data.

Who decides

You can. Governance is open: a participant can develop its own use case and bring it into the data space (opens in a new tab) Data space A decentralised infrastructure enabling trustworthy data exchanges based on commonly agreed rules. , and the TAMIS team is there in support, to make sure what you build stays interoperable with the rest. What the partners arbitrate together is the shared roadmap, not permission to have an idea. The criterion is not novelty: it is whether the exchange is useful to more than one participant, and whether someone is ready to run it.