Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Version published after converting to the new editor

When a potential non-conformance is identified, the first step is to document the incident. Documentation requirements vary depending on the source and type of the non-conformance. For example, a failure at test might require certain critical information such as re-creating steps and production unit information. A customer incident might require documentation including customer name and address, account manager, or other customer-related details. 

Properly documenting the nature of a non-conformance is an important part of the initiation process. You use a non-conformance profile to specify documentation requirements for non-conformances, including: 

...