Fault

Faults are a part of the Quality Handling in Eton as one of the key methods to enhance quality.

See: Topic: Faults

Code ✎

The Fault Code is a numeric identifier used by an operator to reference the fault.

Deduct ✎

Controls whether the operator who is responsible for the fault keeps the earned SMV from the faulty operation, or if the SMV is deducted. Generally if an operator is responsible for the fault, the SMV is deducted and only credited when the repair is completed. E.g. A sewing fault.

The SMV may be credited to the operator if the fault is caused by another operator or is a missed operation. E.g. Repairing someone else work.

Reinspect ✎

Reinspect indicates that the product carrier will go to re inspection after the repair has been completed. The carrier will normally go to the same inspector that inspected it on the first occasion. If that inspector is not available the carrier will go to another available inspection station.

Name ✎

The fault code name.

Description ✎

The fault code description. E.g. Sewing fault.

Fault type ✎

The Fault Type of this fault. Can be Reject, Second Quality or Repair.

Repair Route ✎

Repair route tells the system at which station the repair(s) will be done. See Repair Faults

Reinspection Destinations ✎

Under Reinspect Destinations the system is told where the re-inspection will be done. The options are:-

1. "Inspector" - The product will be sent back for re inspection to the inspector who performed the original inspection.
   Note that this does not apply to inspections done on operations where inspection operation is not the main task. Meaning that addressing re inspection back to the production route is not allowed, unless the inspection made was explicitly configured as of operation type Inspection.
   It is also not applicable if the original inspection operator is not currently working on an inspection station.
   When not applicable to send back to the same inspector, the re inspection destination will fall back on first "Operation" and then possibly on a specified "Fallback Route". If none of the fall backs are applicable, the re-inspection will simply not be done at all.

2. "Inspection" - The product will be sent back for re-inspection at the inspection operation where the original inspection were done.
   Note that this does not apply to inspections done on operations where the inspection operation is not the main task. Meaning that addressing re-inspection back to the production route is not allowed, unless the inspection made was explicitly configured as of operation type Inspection. In which case the re-inspection destination will fall back on any specified "Fallback Route". If the fall back itself is not applicable, the re-inspection will simply not be done at all.

3. "Route" - The re-inspection is addressed using a specified "Re-inspection Route". A dedicated re-inspection route could also include initial buffers to give more capacity to the reinspection process. Note that "Re-inspection Route" is required as soon as "Reinspect" is chosen, but when "Inspector" or "Inspection" is marked the "Re-inspection Route" - then mentioned "Fallback route", works as a possible fallback route.

Reinspection Destinations ✎

The carrier for reinspection is addressed using a specified repair route. A dedicated reinspection route could also include initial buffers to give more capacity to the reinspection process. Note that the "reinspection route" is required as soon as "reinspect" is chosen, but if the "Inspector" is marked the "reinspection route" works only as a fallback.

Allow Multiple Registrations ✎

This fault may be registered multiple times concurrently, but must blame different operations.