kopik
Créer
Tech & produitVérifiée par Kopik: Sources officielles relues et réponses testées par Kopik

AI safety functions in machinery: conformity after the Digital Omnibus on AI

Machines whose safety functions rely on machine learning face stricter conformity assessment under the Machinery Regulation. The Digital Omnibus on AI, signed on 8 July 2026, also changed how the AI Act applies to such machinery.

Posez votre question

Compte gratuit requis

Chaque question est indépendante · 1 offertes par mois, puis avec l'abonnement.

Les réponses sont rédigées par un modèle de langage à partir des seuls documents de cette base, avec leurs sources numérotées. Elles peuvent être inexactes et ne constituent pas un conseil juridique, médical ou financier : vérifiez les sources avant toute décision importante.

Self-evolving safety functions are in Annex I, Part A

Annex I, Part A lists safety components with fully or partially self-evolving behaviour using machine learning approaches ensuring safety functions. It also lists machinery with embedded systems of that kind that have not been placed on the market independently, in respect of those systems only.

For Part A categories, the manufacturer must use EU type-examination (module B) followed by conformity to type (module C), full quality assurance (module H) or unit verification (module G). Internal production control (module A) is not one of the options.

What the Digital Omnibus on AI changed

Regulation (EU) 2026/1744 moves the Machinery Regulation from Section A to Section B of Annex I to the AI Act, a sectoral approach intended to avoid overlaps. For that machinery, the AI Act applies only through the provisions referred to in its Article 2(2).

Article 8 of the Machinery Regulation now requires the Commission to adopt delegated acts adding requirements for high-risk AI systems to Annex III. These must reflect Chapter III, Section 2, and Articles 17, 19, 72 and 73 of the AI Act, and apply by 2 August 2028.

Risk assessment for autonomous behaviour

Annex III requires the risk assessment to cover foreseeable hazards arising from the intended evolution of self-evolving behaviour or logic over the machine's lifecycle. It also covers risks from interactions between machines arranged to function as an integral whole.

The human-machine interface must be adapted to the foreseeable characteristics of operators, including for machinery with self-evolving behaviour designed to operate with varying levels of autonomy.

Questions fréquentes

Which standards can be used for AI safety functions before machinery-specific ones exist?

A new Article 20(10) provides that, until such standards or common specifications exist under the Machinery Regulation, high-risk AI systems that comply with those under Articles 40 and 41 of the AI Act are presumed to conform with the related Annex III requirements.

When did the Digital Omnibus on AI enter into force?

Regulation (EU) 2026/1744 was signed in Strasbourg on 8 July 2026. It entered into force on the third day after its publication in the Official Journal of the European Union.

How long does the Commission's power to adopt these AI delegated acts last?

For the delegated acts under the third paragraph of Article 8, the power is conferred for five years from 27 July 2026 and is tacitly extended unless the Parliament or the Council objects. Either institution can revoke it at any time.

Pour les développeurs et les agents

Intégrer / API / MCP

Branchez cette base à Claude, Cursor, ChatGPT ou votre propre application. Chaque requête API ou MCP coûte 0,10 €, débitée de votre crédit Kopik (non facturée si rien n'est trouvé). Il vous faut une clé API : créez-la depuis votre tableau de bord.

MCP pour vos agents

Adresse du serveur MCP de cette base (outils ask_base et search_base) :

URL MCP
https://kopik.io/api/mcp?base=eu-robot-cobot-machinery-safety
Claude Code, Cursor et autres clients
Claude Code
claude mcp add --transport http kopik-eu-robot-cobot-machinery-safety "https://kopik.io/api/mcp?base=eu-robot-cobot-machinery-safety" --header "Authorization: Bearer kpk_…"
Configuration JSON (mcpServers)
{
  "mcpServers": {
    "kopik-eu-robot-cobot-machinery-safety": {
      "url": "https://kopik.io/api/mcp?base=eu-robot-cobot-machinery-safety",
      "headers": {
        "Authorization": "Bearer kpk_…"
      }
    }
  }
}

API REST pour vos applications

mode vaut "answer" (réponse rédigée + sources) ou "passages" (passages bruts seulement). Ajoutez un maxPriceCents facultatif pour plafonner le prix : si la base coûte plus cher, l'appel est refusé sans rien débiter.

curl
curl -X POST https://kopik.io/api/v1/bases/eu-robot-cobot-machinery-safety/query \
  -H "Authorization: Bearer kpk_…" \
  -H "Content-Type: application/json" \
  -d '{"question": "Votre question ici", "mode": "answer"}'

Pour commencer

  1. Créez une clé dans votre tableau de bord et rechargez votre crédit.
  2. Remplacez kpk_… par votre clé.
  3. Tout le détail (réponses, erreurs, exemples JS et Python) : documentation développeurs.