Revision and change management in the technical file

Technical explanation

For assemblies based on manufacturer instructions, the components must be evaluated together. Standard editions and manufacturer documents can also change over time. Therefore, the fact that a document's file name stays the same does not show that its content is the same. The impact of a technical change is evaluated on the basis of the product identification, the actual composition of the assembly and the applicable document versions.

Source: S017, S062

Topic-specific checkpoints

Source: S017, S062

How to evaluate it in practice

For each change, state what changed, why, and which records may be affected. Instead of reusing the old assembly identification, link the new revision to the product history. Link content approval not to a text summary but to the revision and the content hash value; if the text changes, do not automatically treat the old approval as valid. Separate different types of change, such as a product change, a correction to web copy and a typo. Any required re-verification must be a decision of the technical authority.

Original editorial recommendation; not a clause of a standard.

Frequently asked questions

If only the fitting supplier changes, does the old assembly approval still apply?

Not automatically. The new part must be evaluated in terms of the combination and the application.

Source: S017, S062