6.2 Clause
Sensory input processing
The group covers what the system takes in from the world: images, video, sound, text, sensor signals and other observations. The description is meant to say which inputs are supported, under what conditions, and what happens when the input is outside them.
What this settles
Input is where many failures begin and where vendor claims are vaguest. A system that works on clean scanned text may fail on a photograph, a dialect, a noisy room or a damaged sensor, and the capability claim rarely says so.
Who it binds
The organisation, as a method choice. Where the input is personal data, accessibility or safety relevant, the duties come from those regimes and need their own assessment.
What to do in your practice
Record the supported input envelope: formats, languages, resolutions, noise levels and lighting. Then record the behaviour outside it, including rejection and human fallback. Test the edges, not only the centre.
Evidence an auditor or regulator asks for
| An input envelope with formats, languages and environmental limits. | States the conditions the claim depends on. |
|---|---|
| An edge-case test set and its results. | Shows the behaviour outside the centre. |
| A rejection and fallback note. | Proves the system fails visibly rather than silently. |
What input would a real user present that our test set has never seen, and what happens then?
Common gaps this page catches
- The input envelope is undocumented, so users assume any format works.
- Only clean sample data is tested, and the failure appears in production.
- Out-of-envelope input is accepted silently and produces a confident wrong answer.
What to prepare before publication
Collect 50 real-world edge inputs from users and run them through the system. Publish the envelope with the capability claim.
How to test it here
Take one live system rather than a template, find the field or sentence where Sensory input processing is used, and put this page beside it. Record the answer, the artefact and the date. A glossary entry on its own is an intention; a dated record beside a live artefact is evidence.
What this page does not claim
The page does not reproduce the draft, does not know the descriptor wording that the public preview withholds, and does not certify the system or the organisation. It states the unit at the claim level "capabilities group" and stops where the public record stops.
Common questions
- What does Sensory input processing mean in ISO/IEC DIS 42102?
- The group covers what the system takes in from the world: images, video, sound, text, sensor signals and other observations. The description is meant to say which inputs are supported, under what conditions, and what happens when the input is outside them.
- What evidence should we keep for 6.2?
- An input envelope with formats, languages and environmental limits. An edge-case test set and its results.
- Is Sensory input processing a requirement?
- No. The draft is a descriptive framework. It sets no management system requirement and no conformity test. It becomes binding only when a contract, a regulator or a management system adopts it.
Related units
Last updated: · Markdown version · Check your system