Add one NB note beneath the “AI Safety” definition in Annex 5, Section 1.1, item 4, clarifying that the definition uses “safety” in the functional-safety sense and that hazards affecting AI-based safety functions may be initiated by malicious actions or arise from personal data processing, and that assurance of AI systems interacts with cybersecurity and data-privacy requirements such as UN R155 and ISO/SAE 21434.
Proposal to modify para. 4.2.5.2 to replace ‘management of changes in data and operational distributions’ with ‘management of changes in data and process assurance’. Where a closed-loop data chain is applied to vehicle AI systems safety development activities, evidence of safety assurance capability of the complete closed-loop data chain shall be provided, including safety assurance descriptions for data collection, data processing, and data annotation processes. Where data training is used as an improvement measure for functional insufficiency, relevant analysis shall be conducted and the rationality of the data shall be justified to ensure the improved system meets system-level safety-related requirements.
Proposal to insert a sentence in para. 2.2.1 clarifying that decision trees can be learned from data and not all are manually specified rule systems, and to modify para. 2.2.5 to state that Generative AI models can use different architectures, with some being Transformer-based and potentially foundation or general-purpose AI models.
Proposal to modify the definition of concept drift in para. 3.2.9.2 and Annex 2, para. 6.2 to clarify that concept drift arises when changes alter the relationship between inputs and target outputs, and that a change in input distribution alone does not necessarily imply a change in this relationship.
Proposal to modify the definition of Validation Data to replace ‘a final’ with ‘candidate’ and append clarification that it is used for model selection or tuning while independent test data used for final performance reporting are not used for model selection or tuning, and add a definition of Test Data as data used to evaluate the final selected model and not used for fitting, model selection or tuning, with a note on dataset separation to avoid leakage between sets.
Proposal to modify Annex 1, 1.1.2 to replace the clause beginning ‘and such applications fall within the scope’ with language clarifying that applications fall within the first mode of AI use only where AI is part of the regulated product and directly performs or supports a safety-relevant function, and to add that AI tools used solely for development or assessment fall under section 2.3.3.
Proposal to add working definitions for uncertainty quantification, aleatoric uncertainty, epistemic uncertainty, and uncertainty-aware action at the end of section 1.3 of AI-11-03, Annex 5. These definitions do not replace definitions in applicable standards and support general discussion of uncertainty and its effects on action.
Proposal to append sentences to paragraph 2 addressing uncertainty-related risks propagated from upstream to downstream AI modules and supporting uncertainty-aware action, and to paragraph 3 considering whether uncertainty information remains meaningful when used by downstream AI modules and how it affects the resulting action.
No matching agenda items.