> For the complete documentation index, see [llms.txt](https://help.sequorplatform.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.sequorplatform.io/documentacao/documentation-en/registrations/registrations-backoffice/defect-control-registration.md).
# Defect Control Registration
#### Overview
The module of **Defect Registration** is responsible for structuring and standardizing the **types of defects identified in the production process**.
Just like in Downtime Control, this module allows you to create a **hierarchical structure (tree)** of classification, ensuring that defect reports on the shop floor are carried out in a **consistent, traceable, and analytical**.
This structure will be used directly in scrap and quality reporting in Titan.
#### Objective
* Standardize defect classification
* Create hierarchy for quality analysis
* Make it easier to identify scrap causes
* Improve quality indicators (scrap, rework)
#### Registration Structure
The registration consists of:
* **Main structure (tree)**
* **Levels and sublevels (defect categories)**
* **Justifications (final defects)**
⚠️ Important rule:\
The **defects must be registered at the last level of the structure**.
## 1. Access to the module
In BackOffice:
Access the module **Defect Registration**
Defect Control App
## 2. Main Registration
General information
#### Available fields
* **Defect Number**\
Registration identifier (e.g.: DEF-001)
* **Description**\
Structure name (e.g.: Defect Justification)
* **Enabled**\
Defines whether the registration will be available for use
#### Action
* Click on **Save** to create the initial structure
## 3. Tree Structure
After saving, the structure will be displayed in the left side menu.
Left menu in tree structure
This tree allows you to:
* Create defect categories
* Organize analysis levels
* Standardize reporting
## 4. Creating Levels
#### How to create a level
1. Click the button **"+" (Add level)**
2. Fill in the data
Level Creation
#### Available fields
* **Parent**\
Defines the level hierarchy
* **Level Name**\
Category name (e.g.: Structural, Surface)
#### Best practices
* Create broad categories at the beginning (macro)
* Evolve into more specific subcategories
* Avoid very complex structures
## 5. Defect Registration (Justifications)
#### How to register a defect
1. Select the **final level of the tree**
2. Click on **"+" (Add justification)**
Add Justification
Justification Creation
#### Available fields
* **Justification Number**\
Defect code (e.g.: QUEB, DEFO, FISS)
* **Justification Description**\
Defect name (e.g.: Structural breakage)
* **Enabled**\
Defines whether it will be available for use
#### Example
* Code: QUEB
* Description: Structural breakage
## 6. Defect View
After registration, defects will be displayed in a list containing:
* Defect number
* Description
* Status (active/inactive)
Justifications
## 7. Complete Structure (Example)
Defect Tree
#### Hierarchy example:
**Level 1**
* Structural
* Surface
**Level 2 (Surface)**
* Stains
* Scratches
* Burrs
* Cracks
**Level 3 (Cracks)**
* Cold crack
* Hot crack
* Crater crack
* Throat crack
**Final level**
* Registered defects
## 8. System Rules
* Mandatory hierarchical structure
* Defects only in the **last level**
* Registration must be **enabled** for use
* Hierarchy defines navigation in Titan
#### Impact on Titan
The operator will use this structure to:
* Register defects during production
* Report scrap accurately
* Classify quality issues
## 9. Benefits of Defect Registration
* Standardization of reports
* Better quality analysis
* Reduced subjectivity
* Quick identification of scrap causes
* Solid foundation for continuous improvement
