Terms related to data · 3.2.3
data augmentation
making synthetic samples by changing existing data or building on it
What this term settles
This is the sense the standard gives data augmentation. 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. The obligation arrives when the firm writes data augmentation into a control, a specification or a purchase order.
What to do in your practice
Add data augmentation to the vocabulary register and to the onboarding pack. A term that is only in a PDF is not controlled; it is controlled when a new joiner can find it and a reviewer can test it.
Evidence an auditor or regulator asks for
- A controlled vocabulary entry for data augmentation with the citation 3.2.3, an owner and a review date.An auditor can check that the term is controlled rather than assumed.
- A data inventory field that records the entry for each dataset used in training or operation.Shows data augmentation in use in the artefact the firm relies on, not only in a glossary.
- A data quality record with the check, the date and the person who signed it off.The data inventory is organised by system rather than by dataset, so the same data is described twice with different labels.
Common gaps this page catches
- data augmentation is used in the data record behind every AI system without a written definition, so two teams can mean different things.
- A supplier uses the same word with a different boundary and nobody has recorded the difference.
What to prepare before the amendment lands
Add the entry to the register, give it an owner and a review date, and test it against one live artefact this week. The test is the evidence; the register row alone is not.
How to test it here
Take one live artefact rather than a template, find the sentence or field where data augmentation 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 data augmentation at the claim level "definition" and stops where the public record stops.
Common questions
- What does data augmentation mean in ISO 22989?
- making synthetic samples by changing existing data or building on it
- What evidence should we keep for 3.2.3?
- A controlled vocabulary entry for data augmentation with the citation 3.2.3, an owner and a review date. A data inventory field that records the entry for each dataset used in training or operation.
- Is data augmentation a requirement?
- No: data augmentation 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.2.3, 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.
Last updated: 2026-10-21 · Markdown version · Check your vocabulary