ISO 22989 Revision Checker
ISO/IEC 22989:2022/FDAmd 1 Amendment 1: Generative AI Stage 50.00 Planning date 16 Feb 2027, an estimate 117 defined terms · 23 clause pages

Home / Vocabulary

Terms related to AI · 3.1.30

robotics

the science and practice of designing, making and using robots

  • definition
  • Defined term
  • ISO/IEC 22989:2022/FDAmd 1
  • Last updated: 2026-10-21

What this term settles

This is the sense the standard gives robotics. A firm is free to use another sense, but then the difference belongs in its own glossary rather than in an assumed shared language.

Who it binds

Nothing here creates an obligation by itself, and the obligation for robotics arrives when the firm writes the term into a control, a specification or a purchase order.

What to do in your practice

Take the firm's own definition of robotics, put it beside this one and mark the differences. Each difference is either a deliberate local choice or an inconsistency to fix.

Evidence an auditor or regulator asks for

  • A controlled vocabulary entry for robotics with the citation 3.1.30, an owner and a review date.
    An auditor can check that robotics is controlled rather than assumed.
  • An AI system inventory field that records the entry for each system, with its owner. The row names robotics.
    Shows robotics in use in the artefact the firm relies on, not only in a glossary.
  • A policy or procedure sentence that uses the entry in this sense. The record carries the robotics entry and its date.
    The policy borrows the word but not the boundary, so a supplier system and an in-house model are treated as the same kind of thing. The gap is tested against robotics.
Ask your teamWhere does the firm use the term robotics, and can the owner point to the entry it relies on?

Common gaps this page catches

  • robotics is used in the AI vocabulary a policy reaches for first without a written definition, so two teams can mean different things.
  • The entry for robotics exists in a glossary but not in the system record, so the two disagree at the point of use.

What to prepare before the amendment lands

Take the next policy revision and replace the loose use of robotics with the entry and its citation. Record the change in the vocabulary change log.

How to test it here

Take one live artefact rather than a template, find the sentence or field where robotics is used, and put this page beside it. Record the answer, the artefact and the date, because that record is the evidence and a glossary entry on its own is only an intention.

What this page does not claim

The page does not reproduce the standard, certify the firm or predict the wording the amendment will use; it states robotics at the claim level "definition" and stops where the public record stops.

Common questions

What does robotics mean in ISO 22989?
the science and practice of designing, making and using robots
What evidence should we keep for 3.1.30?
A controlled vocabulary entry for robotics with the citation 3.1.30, an owner and a review date. An AI system inventory field that records the entry for each system, with its owner. The row names robotics.
Is robotics a requirement?
No: robotics is a definition or clause of a terminology standard, and it becomes binding only when a firm writes it into a policy, a contract or a procedure, or when another standard incorporates it.

Related units

Source. ISO/IEC 22989:2022, Clause 3.1.30, Terms and definitions. Open the ISO public entry. Retrieved 21 October 2026.

https://www.iso.org/obp/ui/en/#iso:std:iso-iec:22989:ed-1:v1:en

ISO catalogue record 88145, the amendment status, stage and dates. Catalogue record 74296, the base standard.

Claim level: definition. The definition is in the public preview. This page states it in our own words and does not reproduce the text.

Built from the public ISO record and the public clause 3 entries. No clause text is reproduced. How the record is built.

Last updated: 2026-10-21 · Markdown version · Check your vocabulary