Stage 1: pilot from November 2026
The venue files its certificates once, league and city read along
One venue file replaces PDF packages to league, city and, later, insurers. Expiry dates show up 60 days early.
- Arena
- League
- Federation
- Public authority
Problem
Today the venue emails PDFs to the league, the regional federation, the city and the insurer. Each body asks separately and checks expiry dates for itself. It happens that a federation demands another venue at short notice because a certificate is missing.
Solution
The venue operator creates one venue file per venue: about 25 master data fields and five certificates with issuer and expiry date. All Participants read master data, the league sees status and expiry, the regional federation sees detail, and an insurer later sees released inspection values. An obligation sends expiry notices 60, 30 and 7 days early, and in the pilot a person triggers the notice.
Benefit
A league with about 80 venues saves an estimated 80 to 160 hours of checking per season (assumption: 1 to 2 hours per venue). An expiry shows up 60 days early, not only when the venue must change.
Data providers
- Venue operator
- Floor manufacturer (later)
Data consumers
- League
- Regional federation
- City
- Insurer (later)
Possible partners (not yet confirmed)
- Opiquad Arena
- Vero Volley
Data objects (technical identifiers)
sport-arena-hallenakte-stammdatensport-arena-hallenakte-nachweisesport-arena-hallenakte-detail-pdfsport-ausruester-bodenzertifikat-fivbsport-arena-pruefwerte-versicherung