Quality Control - [Survey]

Quality Control Module – Introduction Plan

• The Quality Control (QC) Module ensures that materials and finished goods meet predefined quality standards at every critical stock movement.
• The system automatically triggers quality checks during incoming, in-process, and outgoing transactions.
• Each quality check uses predefined test cases per item, validates results against min–max limits, generates a unique reel number, and determines pass or fail status.
• QC reports provide full traceability and support quality monitoring and improvement.

Module Structure

Transactions

1. QC Entry

Masters

1. Test Case Master
2. Item QC Master

• In ItemGrouMst we will define all linked test cases
• We can provide checklist

Reports

1. QC Inspection Report

• Detailed report with system number, test results, machine name, assigned to and status

2. Item-wise & Machine-wise QC Report

• View QC results per item and Machined wise.

3. Transaction-wise QC & Pass vs Fail Summary Report

• QC linked to GRN, Job Work, MIRS, Sales Return
• Overall quality performance summary

QC Entry (Transaction Overview)

QC Entry is the main transaction used to record and validate quality inspection results against business documents.

Key Points

• QC Entry is created by selecting:

1. Document Type (GRN, Jobwork, Production, Invoice, etc.)
2. QC Type (Incoming / Production / Outgoing)
3. Reference No & Reference Date
4. System automatically fetches eligible item lines from the selected document.
5. QC is performed item-wise for all fetched lines.
6. Each QC Entry is assigned a unique system-generated number.

QC Execution

• QC can be performed in:

1. Manual Mode (QC report number, date, status and upload and validation)

• The uploaded document will be validated.

2. System Mode (parameter-based inspection through system)

• Each item is marked as PASS / FAIL / HOLD based on QC results.

Control Logic

• Items marked PASS are allowed for next business actions (stock, production, dispatch).
• Items marked FAIL / HOLD are blocked.

Test Case (Master Overview)

Test Category (Optional)

• High-level classification of inspection type.
• Examples: Dimensional, Visual, Mechanical, Functional, Packaging

Test Case

• Define test parameters with min & max values
• Fields can be Name, Code, Parameter Type, Min Value & Max Value.

Test Parameters

• Individual measurable or verifiable checks under a test case.
• Each parameter follows defined validation rules.
• Examples: Length, Width, Thickness, Surface Finish, Pass / Fail Observation
• Parameter Types - Each test parameter is defined with a type for system validation:

1. Numeric – Min / Max range
2. Boolean – Yes / No
3. List – Pass / Fail / NA

QC Flow – From Incoming to Outgoing

Step-by-Step Working

1. Transaction Incoming Created

• (Stock / GRN / Job Work Receipt / MIRS Receipt / Sales Return / Credit Notes / Sales Order)

2. QC RecordCreated

• Test cases fetched from Item QC Master

3. QC Execution

• User selects machine
• Enters test values

4. System Validation

• Within Min–Max -> Pass
• Outside Range -> Fail

5. Stock Decision

• Pass -> Stock accepted / allowed to move
• Fail -> Stock blocked / rejected / on hold

6. QC Report Generated

• Can be checked to get overall status

Simple QC Flow Diagram

flowchart TD
    A[Stock Transaction IN] --> B{QC Required?}
    B -- Yes --> C[QC Record Created]
    C --> D[QC Inspection]
    D --> E{Min Max Validation}
    E -- PASS --> F[Stock OK]
    E -- FAIL --> G[Stock Blocked]

Not Covered Features like other ERP

• CAPA management (Corrective & Preventive Action)
• SPC charts (Statistical Process Control)
• Supplier rating
• ISO document control