Defect Tracking template
  • 22 May 2023
  • 2 Minutes to read
  • Contributors

Defect Tracking template

Article Summary


This Article summarizes how the defect tracking template is structured and built.

What purpose does the Defect tracking template serve?

The defect tracking template can be used individually or by supplementing other apps. The app's functions include viewing defect events that occurred during production, reporting defects, and editing defects. The user can assign defect reasons to defect events and store all information in a Tulip Table. The data collected using the app can be easily analyzed and visualized for example on a Pareto chart.

Tulip Table used in the Defect tracking template

The Tulip Table used in the template is called Defect Events. Each row in the table is a defect event that can refer to multiple defects.

Fields of the Defect Events table:

  • ID: Unique ID of the defect event. For the records logged in the Defect Tracking application, it is a random text generated by the application
  • Reported date: The date of recording the defect (remains the same even if the record is updated)
  • Reported by: The nem of the operator who reported the defect
  • Material ID: The physical material (if uniquely identifiable) associated with this deviation
  • Description: Description of the deviation event
  • Quantity: Number of defects
  • Reason: The reason for the defect event
  • Status: The status of the defect event e.g. “new”
  • Location detected: Name of the station, where the defect was detected
  • Photo: An image of the defect complementing the description

App structure

On the View Defects step the user can select a defect event from the interactive table on the left. The details of the event are displayed on the right. This step also functions as a navigation step from where the users can decide if they would like to report a defect, edit a recorded defect event, or view the analytics dashboard.

On the Report Defect step, the user needs to type in the details of the deviation event such as the material ID, the number of defects, and the defect reason. Optionally, they can add defect notes and an image of the defect. By clicking the red Report Defect button, the new defect event is saved to the Defect Events table.

In the Edit Defect step, the user can edit the fields of the record selected in the View Defects step. By clicking the blue Save button the defect event is updated in the Defect Events table.

On the Analytics step, the user can view custom analytics built from the data stored in the Defect Events table.

Was this article helpful?