UNECE WP.29 R156
Paragraph 7.1.2: Records kept for each update – UNECE WP.29 R156

UNECE WP.29 R156 7.1.2.5: Documentation for every update: purpose, effects, approval status, conditions, safety, security and V&V

What does 7.1.2.5 require?

Documentation for all software updates of the vehicle type describing (a) the purpose, (b) the systems or functions the update may affect, (c) which of them are type approved, (d) whether it affects fulfilment of their requirements, (e) whether it affects any system type approval parameter, (f) whether approval was sought from an approval body, (g) how and under what conditions it may be executed, (h) confirmation it will be conducted safely and securely and (i) confirmation it passed verification and validation. The Interpretation Document: records for (d) and (e) carry the reasoning behind the decision for audit; (g) may be release notes naming safe-state conditions and user or competent-person actions; information may be clustered for multi-purpose updates or a regular class of updates.

Maintained by Gerard BlokdykVerified against the published standard Control text last updated

Other controls in Paragraph 7.1.2: Records kept for each update – UNECE WP.29 R156

Query this from an agent

The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.