Non-Conformance Module Overview

Purpose of the Non-Conformance Module

The Non-Conformance module helps your organization identify, document, investigate, and resolve instances where a product, service, or process does not meet specified standards or requirements. It provides a structured way to manage these deviations, ensuring corrective actions are taken and quality is maintained.

Key activities managed within this module include:

• Logging detailed reports of non-conformances.
• Classifying non-conformances for analysis and action.
• Guiding the investigation process to find root causes.
• Tracking corrective and preventive measures.
• Overseeing the approval and closure of reports.

Key Concepts

• Non Conformance Report: The main document where all details about a specific non-conformance are recorded and tracked.
• Specification: The defined standard, procedure, or requirement that was not met.
• Process Type (Internal/External): This distinction can affect how a non-conformance is investigated and who is involved.
• Root Cause Analysis: A systematic investigation to determine the fundamental reasons why the non-conformance occurred.
• Corrective Action: Steps taken to eliminate the cause(s) of the non-conformance and prevent its recurrence.
• Disposition: The decision on how to handle a non-conforming item (e.g., rework, scrap, accept as is).

General Workflow

A Non Conformance report typically moves through several stages, indicated by a status and often a visual icon:

1. Draft: You've started a report but haven't submitted it yet.
2. New Report: The report is submitted and awaits review and classification by an Area Quality Representative.
3. Open Report: The report is classified and assigned for detailed investigation to find the root cause and plan corrective actions.
4. Pending Sign-Off: The investigation is complete, and the report is submitted for final review and approval by an Internal Authoriser.
5. Closed: The report is approved, and the non-conformance is considered resolved.

Progressing a report through these stages involves specific actions (like 'Submit', 'Submit to investigator'). The system often sends notifications to the next person responsible at each key transition. For general information on system interactions, refer to 'Understanding Notifications' and 'Submitting Forms' help guides.