> 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/sequor-mes/titan-collection/checklist-module.md). # Checklist Module ## 1. Module Overview The module **Checklist** is used in Titan to ensure that **operational, safety, and process conditions** are checked and recorded during the execution of a **Production Order (PO)**. * The checklist is **always linked to a Production Order and an Operation** * It **cannot be accessed independently** * Its release depends on **trigger conditions configured in the Capacity record** ## 2. Prerequisites for Checklist Release Before the checklist is shown to the operator, it is necessary to complete **the entire workflow below**: ### 2.1. Operator Link with the Equipment * The operator accesses the module **Capacities** * Selects the desired equipment * Confirms the link with the station

*\*This step ensures traceability of who is operating which equipment.* ### 2.2. Selection of the Production Order (PO) * After linking with the equipment, the system presents the list of **available Production Orders** * The operator selects the PO to execute

### 2.3. Selection of the Operation * Within the PO, the operator chooses the **specific operation** to work on (e.g., OP10, OP20, etc.)

*\*Only after selecting the operation does the system assess whether there is an associated checklist.* ## 3. Checklist Release (Trigger Condition) After selecting the operation, the system automatically checks: * Whether there is **a checklist linked to the operation** * Whether the **trigger condition** configured in the **Capacity** has been met Trigger examples: * Start of the operation * First entry * Shift change * Every X hours * Before completing the operation ## 4. Checklist Types ### 4.1. Non-Mandatory Checklist When the checklist is **non-mandatory**, the system displays a notice informing that a checklist is available. The operator can: * **Confirm** and fill out the checklist * **Postpone** after entering the checklist and continuing with production *Filling it out is recommended, but it does not block the process.*

### 4.2. Mandatory Checklist When the checklist is **mandatory**: * The system **blocks the continuation of the operation** * The operator **must fill out the checklist** to continue *It is not possible to produce, complete the operation, or advance in the workflow without the checklist filled out.*

## 5. Checklist Execution After release, the operator is directed to the **main checklist screen**, where the configured items are displayed.

### 5.1. Structure of Checklist Items The items may have different input types, such as: **Text** * Example:\ **GENERAL-REMARKS**\ *Relevant notes before the start of the operation* **Number (with limits)** * Example:\ **HYDRAULIC-PRESSURE**\ Hydraulic system pressure * Minimum value: 85 * Maximum value: 110 \**The system automatically validates whether the entered value is within the allowed range.* **Date** * Example:\ **CUTTING-FLUID-CHANGE**\ Last cutting fluid change **List** * Example:\ **WORKPIECE-CLAMPING**\ Condition of the workpiece fixation ## 6. Documentation and Attachments Some checklist items may have **associated documentation**, such as: * Images * Visual instructions * Operating procedures * Technical manuals ### 6.1. Accessing Documents * The operator can click on the **document icon** * The system displays the list of files linked to the item * It is possible to navigate between available documents and images

*\*This functionality helps ensure the correct execution and standardization of the process.* ## 7. Available Actions in the Checklist At the bottom of the screen, the operator has the following options: * **Save**\ → Saves progress without finishing * **Postpone**\ → Allows pausing the filling process (when the checklist is registered as non-mandatory) * **Completed / Not Completed**\ → Indicates the response status of the checklist items * **Finish**\ → Ends the checklist and allows the production flow to continue *In mandatory checklists, only finishing with all valid items releases the operation.* ## 8. Checklist Completion When clicking on **Finish**: * The system validates all items * Records: * Date and time * Operator * Equipment * PO and Operation * The checklist is associated with the production history

With the checklist completed, the operation can proceed normally. ## 9. Benefits of Using the Checklist ✔ Operational standardization\ ✔ Reduction of failures and deviations\ ✔ Full traceability\ ✔ Support for quality and safety\ ✔ Database for audits and continuous improvements