Inspections and defects

Combined inspections

In Qarma, inspections can be combined. This means that it’s possible to create one inspection report out of inspections from different orders, or different items on the same order.

Combined inspections are represented in the inspection list by the inspections they are based on. So a combined inspection based on two inspections, one from order A and one from order B, will be represented as two records in the inspection list. They will have separate Inspection ids but share the same Report inspection id (for inspections that are not combined, they two ids are identical). Some properties are pertaining to the combined inspection, for example the Actual sample qty and the defect counts, so you need to take care when summarizing these values. In that case, sample values should be counted only once for each Report inspection id.

Checkpoints can be related to either the overall combined inspection or the underlying inspections. This means that relations between the checkpoints table and the inspections table need to mapped from the Inspection id field of the checkpoint table to both the Inspection id and the Report inspection id.

Defects are only logged for the overall combined inspections, so the defects table can be mapped to the Report inspection id.

Inspections format

The following fields are available for inspections:

Name

Description

Data type

Name

Description

Data type

Inspection id

Unique id for the inspection

String

Report inspection id

For combined inspections, this is the common id for all the inspections involved. For single inspections, the Report inspection id is the same as Inspection id (read more above).

String

Status

Can be Planned, In progress or Report

String

Order number

The order number

String

Order line id

This is the order line id used for data integrations to uniquely match order lines.

String

Item number

The item number

String

Item name

The item name

String

Supplier number

The supplier number

String

Supplier name

The supplier name

String

Inspection type

The type of inspection performed, e.g. Final or Inline.

String

Checklist id

The id of the checklist used for the inspection

String

Checklist name

The name of the checklist used to perform the inspection.

String

Checklist revision

The revision number of the checklist used at the point of time the audit was downloaded

Integer

Inspector conclusion

The conclusion which the inspector selected when submitting the report.

String

Conclusion

The final conclusion chosen. This can differ from inspector conclusion if for example there is an approval flow. In most cases this is the conclusion to use for downstream analysis.

String

Inspector comment

This is the comment made by the inspector when submitting the inspection from the app.

String

Inspector name

The user name of the inspector that performed the inspection.

String

Inspector email

The email of the inspector.

String

Supplier qc

Will be TRUE if the inspector is member of the supplier’s group.

Boolean

Etd

Estimated Time of Departure.

Date

Inspection start time

The time when the first action was taken by the inspector (this could be taking a photo, marking the status of a checkpoint etc. ). It does not reflect the time of download.

DateTime

Inspection end time

The time when the inspector submitted the inspection. Qarma supports off line operations, so there can be a difference between the Inspection end time and the time that the report is available in the system: if the inspector was offline for two hours, the app keeps track of the time when the inspection was submitted, and this time will be the Inspection end time, even if the Qarma server did not receive the data until two hours later.

DateTime

Scheduled inspection date

When the inspection is planned.

Date

Actual sample quantity

The sample qty is the number of pieces to be checked. Normally calculated based on AQL , but depending on permissions, this can be changed by the inspector.

Integer

Quantity available

The number of pieces available for the inspector. For split shipments, this will be the total qty for a specific shipment.

Integer

Quantity available source

Possible values are Combined inspection or Single inspection.

For combined inspections, the value can apply either to each individual inspection or the combined inspection as a whole, depending on how it was set by the inspector.

String

Original total quantity

The original qty on this order as derived from data integration with Qarma, or as manually set on the website prior to inspection.

Integer

Original sample quantity

The sample qty is the number of pieces to be checked. Unless the inspector makes changes during inspection, the Actual sample quantity and the Original sample quantity will be identical.

Integer

Re-inspection of

Shows the Report inspection id of the former inspection, e.g. if this is the 2nd inspection, then this field contains the 1st inspection's Report inspection id.

String

Split shipment of

Shows the Report inspection id of the inspection that was split.

String

Sequence identifier

A textual representation of the inspection sequence, derived from re-inspections and split shipments. For split shipments it will be marked with letters A-Z, and re-inspections with numbers.

As an example, B2 means a re-inspection of the second split shipment inspection.

String

Link to report

Can be used to open the report in Qarma

Link

General minor defects

Number of general defects classified as minor

Integer

General major defects

Number of general defects classified as major

Integer

General critical defects

Number of general defects classified as critical

Integer

Minor defects pieces affected

Number of pieces affected by normal defects classified as minor

Integer

Major defects pieces affected

Number of pieces affected by normal defects classified as major

Integer

Critical defects pieces affected

Number of pieces affected by normal defects classified as critical

Integer

Actual sampling method

The sampling method used for the inspection. If the inspector changed the sampling method, the original one is listed in Original sampling method.

String

Original sampling method

See above

String

Minor defects threshold

The number of minor defects allowed according to AQL

Integer

Major defects threshold

The number of major defects allowed according to AQL

Integer

Critical defects threshold

The number of critical defects allowed according to AQL

Integer

Production unit number

If inspection is linked to a production unit, this will show the production unit’s number (if available)

String

Production unit name

If inspection is linked to a production unit, this will show the production unit’s name

String

Production unit address

If inspection is linked to a production unit, this will show the production unit’s address (if available)

String

Latitude

Tracking based on the last photo taken in this inspection

Float

Longitude

Tracking based on the last photo taken in this inspection

Float

Accuracy

For the GPS coordinates, this is the accuracy

Number

Booking date

If chosen, this will show the booking date of the inspection

Date

Booking note

Will show the booking note of the order

String

Booking last confirmed at

The date of last confirmation of booking date

DateTime

Open corrective actions

Not in use yet

 

Resolved corrective actions

Not in use yet

 

Total corrective actions

Not in use yet

 

Item image

Link to the item image (if any)

Link

Custom fields

Any custom fields (found in “Additional info” from the edit inspection page) included in the export will be included at as the last columns. Note that any custom fields can be included, but needs to be enabled by a Qarma employee. Please contact Qarma support for help.

String

Checkpoints

The following fields are available for checkpoints on inspections:

Name

Description

Data Type

Name

Description

Data Type

Checkpoint id

The id of the inspection’s checkpoint. It's unique to the inspection, meaning that the same checkpoint on another inspection will have a different Checkpoint id even though the same checklist has been used.

String

Master checkpoint id

The id of the master checkpoint. This will only appear for combined inspections where the inspector has made an action on the sub-checkpoint level. This means several Checkpoint ids can refer to the same Master checkpoint id.

String

Checkpoint type

Shows the type of checkpoint, e.g. Standard, Measurements, Barcode.

String

Inspection id

Unique id for the inspection.

String

Report inspection id

For combined inspections, this is the common id for all the inspections involved. For single inspections, the Report inspection id is the same as Inspection id. This is the id to map with the Report inspection id of the inspections table.

String

Checkpoint header

The name of the checkpoint-header in the checklist.

String

Checkpoint

The name of the checkpoint (often a sub-level to the Checkpoint header).

String

Status

The reported status of the checkpoint by the inspector.

String

Comment

The inspectors comments given when setting the status of the checkpoint.

String

Multiple choice

The value selected if the checkpoint is a multiple choice.

String

Score

The score if the checkpoint is a multiple choice.

Integer

max score

The maximum score possible to obtain for a checkpoint with multiple choice.

Integer

Raw data

The raw data of the entire checkpoint presented in JSON format.

JSON

Defects

The following fields are available for defects on inspections:

Name

Description

Data Type

Name

Description

Data Type

Report inspection id

The id of the report that map to the Report inspection id of the inspections table.

String

Defect id

The id of the reported defect. This id is unique to this record, not to be confused with the defect code.

String

Checkpoint id

The id of the checkpoint where the defect was reported (can be empty).

String

Defect severity

The severity selected for the reported defect: Minor, Major or Critical.

String

Quantity affected

The quantity affected by the reported defect. For General defects, there will be an empty value.

Integer

General defect

Is it a general defect or not; If "false" then it's not a general defect, if "true" then it's a general defect.

Boolean

Code hierarchy

This information is presented in a json format. It shows the hierarchy of the defect code that was reported, showing all the levels above the reported defect.

JSON

Top defect type code

Shows the defect code of the top level for the defect that was reported.

String

Top defect type name

Shows the defect name of the top level for the defect that was reported.

String

Parent defect type code

This will only have a value of you have a 3-layered defect list. Then it will show the name of the mid-level defect.

String

Parent defect type name

This will only have a value of you have a 3-layered defect list. Then it will show the code of the mid-level defect.

String

Defect type code

Shows the code of the reported defect.

String

Defect type name

Shows the name of the reported defect.

String

Defect type description

The description of the defect type

String

Comment

Textual description of the defect made by the inspector.

String