> 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/downtime-control-registration.md). # Downtime Control Registration #### Overview The module of **Downtime Control** is responsible for structuring and standardizing the **justifications for production stoppages** within Sequor MES. Through it, it is possible to create a **hierarchical tree of justifications**, allowing stoppages to be classified clearly, in an organized and analytical way. This structure is used directly on the shop floor (Titan), ensuring that all stoppages are recorded with **consistency and traceability**. #### Objective * Standardize stoppage reasons * Create a hierarchical analysis structure * Improve the quality of OEE data * Facilitate root cause identification #### Registration Structure The registration consists of: * **Main structure (tree)** * **Levels and sublevels (up to 4 levels)** * **Justifications (final level)** ⚠️ Important rule:\ The **justifications can only be registered at the last level of the structure**. ## 1. Access to the module In BackOffice: Access the module **Downtime Control**

## 2. Main Registration

#### Available fields * **Code**\ Registration identification (e.g., STOP-JUSTIFICATION 01) * **Description**\ Structure name (e.g., Downtime Control) * **Enabled**\ Defines whether the structure will be available for use #### Action * Click on **Save** to create the initial structure ## 3. Tree Structure After saving, the tree structure will be displayed in the left side menu.

This structure allows you to: * Create levels * Organize categories * Define stoppage hierarchy ## 4. Creating Levels #### How to create a level 1. Click the icon **"+" (Add level)** 2. Fill in the data

#### Available fields * **Parent Name**\ Level to which this new level will be linked * **Description**\ Level name (e.g., PLANNED, FAILURES) #### Permissions (optional) * Define which **teams** can view or edit * Option **"Edit only"** to restrict access #### Best practices * Create macro levels first (e.g., Planned / Unplanned) * Avoid too many unnecessary levels * Keep the structure logical and intuitive ## 5. Justification Registration #### How to register a justification 1. Select the **final level** 2. Click on **"+" (Add justification)**

#### Available fields * **Justification (code)**\ Short identification (e.g., REF, SHIFT) * **Justification Description**\ Detailed name (e.g., Meal / Shift change) * **Stop Type** * Planned * Unplanned * **Enabled**\ Defines whether it will be available for use #### Example * Code: REF * Description: Meal - Lunch/Dinner * Type: Planned ## 6. Viewing the Justifications After registration, the justifications will be displayed in a list format containing: * Code * Description * Stop type * Status (active/inactive)

## 7. Complete Structure (Example) #### Hierarchy example: **Level 1** * Planned * Failures **Level 2 (Failures)** * Electrical failure * Mechanical failure **Level 3 (Electrical failure)** * Short circuit * Overload **Final level** * Registered justifications

## 8. System Rules * Maximum of **4 hierarchical levels** * Justifications only at the **last level** * Structure must be **enabled** for use * Hierarchy defines navigation in Titan #### Impact on Titan The operator will use this structure to: * Select the stoppage justification * Correctly classify the event * Feed performance indicators ## 9. Benefits of Downtime Control * Standardization of justifications * Better data quality for OEE * Quick identification of loss causes * Solid foundation for continuous improvement * Reduction of subjectivity in analyses