> 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/capabilities.md). # Capabilities The module **Capabilities** is one of the structural pillars of Sequor MES. It is responsible for defining **how each production process will be executed on the shop floor**, turning operational rules, times, resources, and controls into a standardized workflow for operation. Each capability represents the combination of **product + process + execution rules**, serving as the basis for Titan to guide the operator during production and record reliable data. In a single record, the Capability brings together: * Production process structure * Operational sequence * Cycle times * Consumed materials * MAP (Process Auxiliary Means) * Notes / operational remarks * Mandatory checklists * KPI targets * Required skills * Production routes * Integrations with IoT signals * Publishing and versioning Once published, the capability becomes **the factory's official operational recipe**, used by Titan to guide operators, validate rules, and record production execution. ## 1. Accessing the module In the Sequor MES main menu, access: **Sequor MES → Capability**

## 2. General Screen The **General** tab concentrates the main identification data for the Capability. It defines the master data for the process that will be detailed in the following steps.

#### Available fields #### Capability Number Unique code for the capability registered in the system. It may follow the company's internal numbering or the automatic Sequor MES standard. #### Status Indicates the current state of the record: * **Editable** → allows changes * **Published** → official version released for operational use #### Description Name of the production process. Example: * Aluminum Housing Manufacturing * Final Battery Assembly * Structural Welding #### Material Code and description of the item produced by this capability. #### Version Current version number of the capability. Automatically updated with each new publication. #### Version Date Date of the last publication. #### Created By User responsible for the initial record.
The General tab defines **what will be produced**. The next steps detail **how it will be produced**. ## 3. Process Tab The **Process** represents the operational flow of the capability. The production operations that make up the process are registered there.

Example: * OP10 – Primary Machining * OP20 – Drilling and Finishing * OP30 – Final Assembly Each operation may have: * Responsible team * Equipment / Workstation * Alternative operation * Manual consumption * Specific resources and parameters * Operational rules for Titan #### Operation Structure Each operation line contains: #### Operation Production step code. #### Operation Description Clear name of the activity performed. #### Team Team responsible for the operation. #### Equipment / Station Machine, line, or production station where the activity will be performed. #### Parent Operation Allows creating production hierarchies when necessary. #### Alternative Operation Allows configuring alternative routes for execution. #### Manual Consumption Defines which materials will be reported manually during execution. #### **Parallel Production** Allows the OP to be executed on multiple machines simultaneously. #### Enabled Defines whether the operation is released for use. ## 4. Process Tab Details When expanding an operation, the system provides the operational parameterization tabs. ### 4.1. Times Defines the standard times used by the operation.

#### Examples #### Setup Time Time required to prepare the machine or workstation. Example: 10 min #### Production Time Standard time per part or cycle. Example: 1.5 min/part #### Slack Time Planned operational margin. Example: 0.5 min #### Impact on the system These times feed into: * Production capacity * OEE * Operational efficiency * Rhythm displayed in Titan * Industrial planning ### 4.2. Materials Defines the materials consumed by the operation.

#### Examples * Aluminum Billet Ø120 * Soluble Oil * M8 Screw * Structural Adhesive #### **Available fields** #### Quantity Quantity consumed per cycle, part, or batch. #### Unit Unit of measure. #### Validate Quantity Requires confirmation of the consumed quantity. #### Confirm Material Requests manual validation from the operator. #### Reading Requires code / MTU / traceability reading. ### 4.3. MAP (Process Auxiliary Means) Defines devices, tools, or auxiliary resources used in the operation.

#### Examples * Pneumatic Clamping Device * Digital Caliper 150 mm * Welding Jig * Electronic Torque Wrench #### Objective Ensure that the operator knows which resources must be available before execution. #### Enabled Defines whether the MAP will be required operationally. ### 4.4. Notes The **Notes** define operational remarks available to the operator in Titan. They are linked to structures previously registered in the reporting modules.

#### Examples #### Quality Record of defects or nonconformities. #### Stops Record of the production stop cause. #### Quadrants Physical location of the defect on the part. #### Operation in Titan During the operation, the operator accesses the reports enabled for that capability. This ensures standardized data collection. ### 4.5. Checklist Defines mandatory checks during the operation.

#### Examples * Check part clamping * Validate hydraulic pressure * Check lubrication * Confirm applied torque #### Fields #### Enabled Defines whether the checklist will be available. #### Triggers Defines when the checklist will be executed.

Possibilities: * Order Start * Order End * Operation Start * Operation End * Setup Start * Setup End * Shift Change * Operator Change * Hour by Hour * Free * Produced Quantity #### Mandatory When enabled, it blocks continuation without filling it out. ### 4.6. KPI Targets Allows registering operational targets by operation.

#### Examples #### OEE * Lower: 75 * Nominal: 82 * Upper: 90 #### Quality * Lower: 95 * Nominal: 98 * Upper: 100 #### Performance * Lower: 80 * Nominal: 90 * Upper: 100 #### Availability * Lower: 85 * Nominal: 92 * Upper: 100 ### Objective Display targets in Titan and monitor operational performance in real time. ### 4.7. Skills Defines training, certifications, or documents required to execute the operation.

#### Examples * NR10 * NR12 * CNC Operation * Certified Welder #### Fields #### Required Document Requires a valid document. #### Enabled Activates the operational requirement. #### Rule in Titan If configured, only authorized operators will be able to start the operation. ### 4.8. Parallel Production The functionality of **Parallel Production** allows the same production operation to be executed simultaneously on different equipment, provided they belong to the same equipment group configured in the process. This feature addresses industrial scenarios where there is a need for: * increased production capacity; * parallel production cells; * equivalent equipment; * operational balancing; * simultaneous execution of the same operation. With Parallel Production enabled, Sequor MES allows multiple operators and machines to execute the same operation concurrently, while maintaining: * consolidated control of the OP balance; * individual traceability by equipment; * real-time update of the production balance; * integrity of production reporting. #### Purpose of the functionality Parallel Production allows the execution of an operation to be distributed across different machines without losing centralized control of the Production Order. The system automatically consolidates all production carried out by the equipment linked to the operation. #### How to configure Parallel Production The configuration is done directly in the **Process** Capability tab. #### Prerequisites To use the functionality: * the operation must have a **Equipment Group** configured; * the flag **Parallel Production** must be enabled; * the equivalent equipment must belong to the same group. #### Equipment Group In Parallel Production, the configuration stops using just one specific piece of equipment and starts working with a group of equivalent machines.

#### Example Configured group: `Machining Group` Equipment belonging to the group: * CNC ROMI D760 01 * CNC ROMI D760 02 * CNC ROMI D760 03 All of them will be able to execute the same operation simultaneously. #### Parallel Operation Configuration In the Process tab: * define the Equipment Group; * enable the flag: * **Parallel Production**

When active: * the operation can be started on multiple pieces of equipment; * the system controls the operation balance in a shared way; * Titan updates the data in real time via broadcast. ### 4.8.1. Alternative Operation + Parallel Production The functionality also supports alternative operations working together with parallel production. #### Operational example Main operation: `OP10 - Primary Machining` Alternative operation: `OP30 - OP10 Alternative` OP30 belongs to the same production flow as OP10, but uses another equipment group. #### Availability rule When a piece of equipment belonging to the alternative operation's group starts execution: * the priority operation is no longer available; * preventing concurrent duplicate execution on incompatible routes. The same behavior occurs in reverse. #### Operational behavior After starting the operation: * different operators can produce simultaneously; * each machine generates its own reports; * the system automatically totals all production. #### Consolidated control of the order balance The Production Order balance is shared among all equipment executing the operation. #### Practical example Production Order: `100 pieces` Simultaneous execution: | Equipment | Production | | --------- | ---------- | | Machine 1 | 50 pieces | | Machine 2 | 50 pieces | Result: * total production = 100 pieces; * order balance = 0; * operation ended correctly. #### Real-time update Sequor MES performs continuous updates via broadcast between active equipment. This ensures that: * operators view the updated balance; * there is no excess production; * the order close is synchronized. #### Label and report control Although the balance is consolidated, reports continue to be recorded individually by machine. #### Important rules * label generation occurs per equipment; * the system does not combine production from two machines on a single label; * traceability remains individual. #### Traceability maintained Even in parallel execution, the system continues recording: * operator; * equipment; * time; * quantity produced; * reports carried out. This ensures full operational traceability and industrial auditability. ## 5. Production Routes The **Production routes** defines the flow between production operations. It determines: * how the operation reports production * whether it prints labels * whether approval is required * whether it uses IoT * which operation the flow will follow after completion

### 5.1. General Operation Settings #### Source Operation Current route operation. #### Printing Allows label or document generation when reporting production. #### Automatic Printing Automatically prints according to the configuration. #### Printer Linked printing equipment. #### Label Label template used. ### 5.2. Batch Reporting Allows operating by batch instead of individual unit. #### Fields #### Batch Size Quantity that makes up a batch. #### Qty. per Cycle Quantity produced per event/cycle. ### 5.3. Mandatory Approval When enabled, approval is required before production is completed.

By clicking the approval icon, it is possible to configure: * Approval team responsible * Approval level * Requirement

Widely used in critical processes, inspection, or quality release. ### 5.4. Automatic Counting (IoT) Allows production to be captured automatically through a machine signal. When enabled, the system starts using the configured signal to perform automatic counting.

#### IoT Link Defines which signal, PLC, sensor, or IoT source will be used. #### Default behavior When only **Automatic Counting** is active: * The parts are recorded as **Counted** * Used for operational monitoring * They are not automatically counted as OK production Ideal for visual tracking and process validation. #### Validate Reporting When enabled together with automatic counting: Each signal received is directly counted as **OK production** of the Production Order. That is: * increments PO production * updates operational progress * feeds official indicators Ideal for automated lines with high reliability of the machine signal. ### 5.5. Restricted Total Quantity Limits production reports to the planned quantity of the Production Order.

#### Example PO planned for 100 pieces. Even if there are rejects or leftovers, the system will not allow reporting above 100 units. #### Benefit Prevents overproduction from being recorded in the system. #### Good Pieces-Based Control Makes the production limit consider only approved pieces. #### Example PO = 100 pieces Production: * 95 good * 5 rejected There will still be 5 good pieces missing to complete the PO. #### Benefit Highly recommended for environments where the production goal is to deliver a net good quantity. ### 5.6. Container Reporting The functionality of **Container Reporting** allows production entries to be made based on weight, using containers configured in the process and, optionally, direct integration with industrial scales via IoT. This functionality was developed mainly for processes where production control occurs by: * weight; * segregation; * scrap; * scrap; * granular materials; * industrial waste; * recyclable materials. The goal is to allow the operator to perform production reporting automatically considering: * gross weight; * container tare; * effective net weight; * automatic scale integration. #### Purpose of the functionality Container Reporting allows turning production logging into an automated and traceable process, reducing operational errors and eliminating manual net weight calculations. #### Configuration in the Capacity module The feature is enabled directly in the tab **Production routes**. #### Required settings

#### Enable the flag: * **Container Reporting** #### Configure: * **IoT Link** The IoT Link defines which equipment or scale will be used for automatic weight integration. Container Reporting enabled #### Scale integration When a scale is integrated into the process: * the weight can be received automatically; * the operator does not need to type it manually; * the system updates the value in real time. #### Default flow After selecting the action: **Report / Segregate** the system displays: * quantity/weight field; * selection of the container used; * integrated scale weight (when configured). #### Container Selection The operator must select the container used in the reporting. The system automatically uses: * registered tare of the container; * net weight calculation; * correct deduction from the production balance. ### 5.7. Destination Operation Defines which operation the flow will follow after completion.

#### Fields #### Destination Operation Next step in the process. #### Transition Type Examples: * Sequential * Parallel * Alternative #### Priority Defines precedence between multiple destinations. ### 5.8. Adding New Routes It is possible to add new operations directly to the route structure.

This makes it easier: * process expansion * multiple production paths * reprocessing * operational parallelism ## 6. Capacity Publication After completing the registration: 1. Select the capacity 2. Click on **Publish** 3. Confirm the action

After publication: * the version becomes official * the record is no longer editable * it becomes used by Titan ## 7. Versioning When editing a published capacity, the system creates a new version.

#### Result * preserved history * full traceability * change security ## 8. Version History Allows you to view: * version * status * date * responsible user

## 9. Benefits of the Capacity module The Capacity module ensures: #### Operational Standardization Everyone executes the process the same way. #### Full Integration with Titan The operator receives exactly the configured flow. #### Data Reliability Times, production, consumption, and quality follow structured rules. #### Industrial Scalability Allows processes to be replicated across lines, plants, and units. #### Complete Traceability Every change is recorded by version. #### Foundation for Industry 4.0 Integration with: * IoT * automation * real-time indicators * smart production control