Inspections

The Inspections module is the means by which you define your own structured quality tests within Commander4j. It is part of the broader Quality Control system and is used in conjunction with Quality Control Sample labelling and the Update Samples and Results Analysis and Reporting screens.

Structure

Inspections are organised into a three-level hierarchy:

Inspection

The top-level definition — for example, Finished Product Sensory Check or Packaging Integrity Audit. An Inspection groups together all the Activities that make up a particular type of quality check.

Activity

A sub-section within an Inspection — for example, Visual Checks or Microbiological Tests. Each Inspection can contain one or more Activities.

Test

An individual test within an Activity — for example, Colour, Foreign Body Check, or pH Value. Each Test defines what the operator is expected to record.

Test Input Types

Each Test is configured to accept one of the following types of input:

• Free text — the operator types a value directly
• Numeric — the operator enters a number, optionally validated against min/max limits
• Selection List — the operator picks from a predefined list of values maintained in Selection Lists

The label shown to the operator for each test field can be customised using the Dictionary, which maps internal field names to meaningful, context-specific prompts.

Using Inspections

Once an Inspection has been configured, it is assigned to a Quality Control Sample record. When operators update sample results via the Update Samples screen, they work through each Activity and Test defined in the Inspection, entering results into a spreadsheet-style grid. Completed results are then available for analysis via the Results Analysis and Reporting screens.