For example the ‘Declaration of product identity’ may not apply to your situation because your supplier always includes your article numbers in the documents he provides.
Or a lot of your technical files may contain a requirement in a transition period, where both the old and new requirement are valid.
If you are ready to always use the new requirement, you can let the old requirement become ‘not applicable’ automatically.
Any requirement fulfillment you define, will be applied to new files you create.
And in existing files, if you change the market release date, region or product category, the requirement fulfillments are applied as well.
The requirement fulfillments are only applied to requirements which have not been set to ‘not applicable’ or ‘fulfilled’ and have no notes and documents linked to them.
So if you manually add a note or document to a requirement or set it to ‘not applicable’, the automatic requirement fulfillments will never overrule what you did.
This allows you to manually make exceptions on a case-by-case basis after the automatic requirement fulfillments were initially applied.
To use automatic requirement fulfillments, go to the ‘Requirement fulfillments’ tab under ‘My account’.
When adding a new requirement, you can choose between setting it to ‘Not applicable’ with an optional note or ‘Fulfilled’ with an optional note or document.
By selecting ‘Apply to all versions’, the fulfillment applies to any version of the requirement, past, present and future.
If you create a fulfillment for a requirement, it automatically applies to all its present and future amendments.
If you want your requirement fulfillment to apply only in specific cases, you can restrict it to one or more file groups, risk levels or product categories.
Only if your technical file matches with one of them, the fulfillment is applied.
