Article 23
Amendments as tabled
One amendment · ITRE–LIBE amendments 527–776 to the draft report
684 +Addition Julie Rechagneux +7ECR, PfE · ITRE–LIBE “For the switching of services involving the training or operation of artificial intelligence models or other compute-intensive workloads, the…”
14a. In Article 23, the following paragraph 2b is inserted:
For the switching of services involving the training or operation of artificial intelligence models or other compute-intensive workloads, the obligations under paragraph 2 shall be understood as requiring functional portability. Functional portability is ensured where the provider of data processing services enables the customer to:
(a)export trained model parameters, including model weights, in commonly used and interoperable formats;
(b)obtain the configuration necessary to redeploy the workload in an alternative environment, including through infrastructure-as-code templates or equivalent means.
Proprietary compute optimisations that are specific to a given hardware or software environment, and that cannot reasonably be replicated in an alternative environment, shall not be subject to the obligations under paragraph 2, provided that the provider offers equivalent functional performance guarantees for the redeployment of the workload. Such optimisations shall not be used to create obstacles to switching within the meaning of point (a) of paragraph 2.
The technical standards and formats referred to in this paragraph, including any exceptions specific to artificial intelligence and compute-intensive workloads, may be specified in the implementing acts referred to in Articles 30(3) and 33(5).
Justification
Article 23 requires providers to enable data portability, but that requirement is technically unachievable for many AI workloads, in particular large models trained on custom high-performance computing clusters relying on hardware-specific optimisations. The amendment introduces functional portability: export of model parameters in interoperable formats and provision of the configuration necessary to redeploy the workload. Proprietary compute optimisations are exempted only where the provider offers equivalent functional performance guarantees, and may not be used to create obstacles to switching.
- Tabled by
- Julie Rechagneux, Mélanie Disdier, Aleksandar Nikolic, Pierre-Romain Thionnet, Alexandre Varaut, Fabrice Leggeri, Marion Maréchal, Christophe Bay
- Group
- ECR, PfE
- Document
- ITRE–LIBE amendments 527–776 to the draft report
- Printed header
- Article 1 – paragraph 1 – point 14 a (new) / Regulation (EU) 2023/2854 / Article 23 – paragraph 2b (new)