i6eal.de
DEEN
Start a project
← Back to AI procurementPermanent official procedure thread

Deutschland – Entwicklung von kundenspezifischer Software – Dienstleistungen & Erstellungs-/Anpassungsleistungen für GenAI-Bots

This dossier follows one source-issued procedure identifier. It separates what official notices report from what is not published and does not infer relationships from names.

Data state 20 Jul 2026, 13:36Thread observed from 21 May 2026 to 24 June 2026
Open machine-readable dossier ↗Open latest official notice ↗
Official procedure identifier
2ee7f9bd-71ca-4181-bbb8-a61eaf20e0ad
Source system
TED / EU
Latest observed event
Tender
Notices
2
Versions
4
Events
4
Reported lots
1
Reported awards
0
Reported contracts
0
Official lifecycle

The published procedure thread

Nodes follow publication time. They do not claim that the underlying work began or ended on those dates.

  1. Tender9ce7b3f5-63f9-420d-9ca5-e45926aad9e0
  2. Tender9ce7b3f5-63f9-420d-9ca5-e45926aad9e0
  3. Tender2b6af0d1-557f-4e14-ba26-1b62bbc06f04
  4. Tender2b6af0d1-557f-4e14-ba26-1b62bbc06f04
Reported parties

Who the source names in this procedure

Buyer and supplier roles are reproduced separately as reported. Their appearance here does not prove a relationship outside this procedure.

Reported buyers

  • BITMARCK GmbH

Reported suppliers

Not published

Separately reported money

No synthetic contract total

Estimate, award, framework, paid and other source values retain their own kind, scope and currency. They are never added together here.

No positive monetary value is published for this procedure.

Notice-by-notice evidence

Every retained official event

Open the official publication attached to an event to inspect the source context.

Showing 4 of 4 retained events.

  1. TenderTender
    Published notice identifier
    2b6af0d1-557f-4e14-ba26-1b62bbc06f04
    Official form code
    competition
    Open official source ↗
  2. TenderTender
    Published notice identifier
    2b6af0d1-557f-4e14-ba26-1b62bbc06f04
    Official form code
    competition
    Open official source ↗
  3. TenderTender
    Published notice identifier
    9ce7b3f5-63f9-420d-9ca5-e45926aad9e0
    Official form code
    competition
    Open official source ↗
  4. TenderTender
    Published notice identifier
    9ce7b3f5-63f9-420d-9ca5-e45926aad9e0
    Official form code
    competition
    Open official source ↗
Procedure structure

Lots, awards and contracts reported by the source

Lots

1

The source reports 1; individual details are not retained in this bounded dossier.

Awards

0

None reported in this bounded projection.

Contracts

0

None reported in this bounded projection.

Cancellations

0

None reported in this bounded projection.

Modifications

0

None reported in this bounded projection.

Completions

0

None reported in this bounded projection.

Evidence boundary

Link quality and AI relevance are separate claims

The thread is retained only through an official procedure identifier. That link quality does not by itself prove AI relevance.

Link basis
Exact thread using the official procedure identifier
Link evidence tier
Exact thread within one source system
Collection signal — not a relevance rating
Collector confidence “high” from deterministic keyword rules
Matched AI terms
Generative KI
Missing fields mean
not reported by the bounded source projection
Projection source
TED / EU
Generated
20 Jul 2026, 13:36

There is no independent content assessment of actual AI relevance. Matched terms are collected across the exact source thread; later award, contract or modification notices may no longer repeat the AI wording that selected the thread.

Official sources

Inspect the published links

These are the official URLs retained by the dossier.

Showing 2 of 2 unique source links.

Reading rules

Keep these limits in view

  • A missing field means not reported in the bounded public projection.
  • Each money value is a separate source claim, not verified public spending.
  • Reported entities are source roles and do not allocate an award or contract value.
  • Names, titles, dates and values never create a procedure join.
  • Procedure threads from different source systems remain separate.
  • One procedure thread may cover multiple lots, contracts or call-offs.
  • An exact procedure cohort may include later notices or call-offs that no longer repeat the AI keyword which selected the thread.
  • Flattened TED arrays do not create buyer–supplier or other relationship edges.

i6eal (2026): Deutschland – Entwicklung von kundenspezifischer Software – Dienstleistungen & Erstellungs-/Anpassungsleistungen für GenAI-Bots — public AI procurement procedure dossier, data state 20 July 2026. https://i6eal.de/en/ki-vergabe/verfahren/ted-procedure-2ac63c67071cf8b3cad90de0209edb07/

Compare this thread with the complete procurement index

Back to AI procurementView all tools
Related tools

Useful next steps

These tools complement the current result.

View all tools
IndexAI innovation pathFollow evidence-backed links from EU funding to reported research outputs—and see exactly where patents or procurement cannot yet be joined safely.IndexAI research & transferWhich research products does OpenAIRE link to publicly funded AI projects? Publications, datasets, software, access metadata and citation signals, joined to CORDIS projects by exact grant identifiers.Data reportGerman state AI evidence monitorCompare three separate public evidence lanes across all 16 German states: exactly assigned AI system profiles, AI-related procurement and physical infrastructure—without a composite score or invented ranking.