> 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/production-control-module.md).

# Production Control Module

The module of **Production Control** is the **heart of operational execution** in Sequor MES. It is where planning becomes real production, connecting **equipment, operators, production orders, and operations** into a single continuous and traceable flow.

To enable this module, the operator must link to the workstation, select the Production Order and the operation to be executed, and then begin operating in a guided, safe, and standardized environment, where all actions are recorded in real time.

During execution, Sequor MES collects essential production data, such as **produced quantities, operation times, defect entries, and stoppage events**, ensuring full visibility of what is happening on the shop floor. This data can be recorded manually or automatically, when integrated with the equipment, respecting the production cycles of each machine.

Production Control acts as the central link between the other system modules, feeding areas such as **Quality, Maintenance, Planning, and Performance Analysis**, and ensuring that operational and strategic decisions are based on reliable, structured, and up-to-date data.

## **1. Prerequisites for using the module**

Before accessing Production Control, it is necessary that:

* The operator is **logged in to Titan**
* The operator is **linked to a piece of equipment / workstation**
* There is at least one **released Production Order**
* The Order has **planned operations** for the selected equipment

> ⚠️ Without these links, the module is not enabled for execution.

### **1.1. Equipment Selection (Capacity)**

When accessing Titan, after opening the "Capabilities" module, the operator sees the list of **equipment or workstations** available for linking.

Each capability card shows:

* Workstation/Equipment Code
* Workstation/Equipment Description
* Visual availability status
* Credential if there is a linked operator

<figure><img src="https://2582153898-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwAMVKtJedtiJ4RrzXGfp%2Fuploads%2Fhky9K1HfHoc5dTP9jMnG%2F4%20-%20esta%C3%A7%C3%A3o%20de%20trabalho.png?alt=media&amp;token=404bc543-506e-4277-ad4f-e86b10445c57" alt=""><figcaption><p>Equipment / Workstation Selection</p></figcaption></figure>

#### Available actions

* Search for equipment by name or code
* Select equipment manually
* Access only equipment linked to the operator

> This link defines **where** production will be executed and tracked.

### **1.2. Production Order Selection**

After selecting the equipment, the system shows the list of **available Production Orders** for that capability.

For each PO, the following are shown:

* Production Order Code
* Produced item
* Planned quantity
* Lead time
* Planned start date/time

<figure><img src="https://2582153898-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwAMVKtJedtiJ4RrzXGfp%2Fuploads%2Fl9aJcCrRU0iAMihfJ2xz%2FSelecionar%20OP.png?alt=media&amp;token=3886dd2c-269d-4e3d-ba76-6350ffdc238b" alt=""><figcaption><p>Production Order Selection</p></figcaption></figure>

#### Objective of this step

Ensure that the operator executes **only compatible orders** with the selected equipment.

### **1.3. Operation Selection**

When selecting a Production Order, the operator must choose **which operation will be executed**.

Each operation shows:

* Operation code (e.g., OP10, OP20)
* Operation description
* Planned quantity
* Produced quantity
* Total production time
* Production Order Code
* Code and description of the material/product to be produced

<figure><img src="https://2582153898-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwAMVKtJedtiJ4RrzXGfp%2Fuploads%2FJKxqyiqvTn8xMdED7sHG%2FSelecionar%20opera%C3%A7%C3%A3o.png?alt=media&amp;token=f3ee294d-ffbf-4442-84b4-ce8da8d72942" alt=""><figcaption><p>Operation Selection</p></figcaption></figure>

> ⚠️ The system requires explicit selection of the operation before starting execution.

To start production, the system asks for confirmation of the link:

> “Do you want to link to operation OPXXXXXX?”

<figure><img src="https://2582153898-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwAMVKtJedtiJ4RrzXGfp%2Fuploads%2Fy80g0XZmOBv2MxaN2OYu%2FIniciar%20Opera%C3%A7%C3%A3o.png?alt=media&amp;token=1034d16d-acf9-43e6-9770-766153bc9c50" alt=""><figcaption><p>Operation Link Confirmation</p></figcaption></figure>

When confirming:

* The operator becomes **active in the operation**
* Production time starts being counted
* The operation enters status **In progress**

## **2. Main Production Control Screen**

After linking, the operator accesses the main execution screen.

<figure><img src="https://2582153898-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwAMVKtJedtiJ4RrzXGfp%2Fuploads%2F6fREr5u2Ijeq3RnFzBjp%2FTela%20principal%20Cont%20Prod.png?alt=media&amp;token=c3880d52-08e2-4440-8531-056a23f0b261" alt=""><figcaption><p>Production Control - Home Screen</p></figcaption></figure>

#### Information displayed at the top

* Selected equipment
* Production Order
* Operation in progress
* Planned quantity (QTY)
* Produced quantity (OK)
* Scrap quantity
* Total production time

#### Operational status

* **Machine Producing** (green visual indicator)
* Time is counted automatically while the operation is active

### 2.1. Informational Widgets on the Production Control Screen

The screen of **Production Control** Titan has informative widgets that provide the operator and supervision with a real-time view of the operation status, productivity, quality, and equipment availability.

These components help with quick decision-making and allow continuous monitoring of production execution.

#### 2.1.1. Production Control

The widget **Production Control** shows the operational information of the Production Order currently being executed.

This data allows the operator to track production progress and process performance.

**Displayed information**

| Field                | Description                                                      |
| -------------------- | ---------------------------------------------------------------- |
| **Current Batch**    | Identifies the batch currently in production.                    |
| **Batch Size**       | Total quantity planned for the batch in progress.                |
| **Pieces per Cycle** | Number of pieces produced in each operational cycle.             |
| **Production**       | Shows production progress relative to the planned quantity.      |
| **Cycle Time**       | Shows the average cycle time of the operation.                   |
| **Previous**         | Lists orders or operations previously executed on the equipment. |
| **OEE**              | Overall Equipment Effectiveness indicator.                       |

> **Note:** The information is updated in real time as entries are made in the system.

**OEE (Overall Equipment Effectiveness)**

The indicator **OEE** measures the equipment's operational efficiency, considering availability, performance, and quality.

**Formula**

```
OEE = Availability × Performance × Quality
```

**Interpretation**

| Range      | Interpretation             |
| ---------- | -------------------------- |
| Below 60%  | Low efficiency             |
| 60% to 80% | Acceptable operating range |
| Above 85%  | Operational excellence     |

> OEE is automatically fed by production, stoppage, and scrap entries made in Titan.

#### 2.1.2. Help Chain

The widget **Help Chain** shows indicators related to support requests opened during production execution.

Its purpose is to allow monitoring of operational support and quick identification of bottlenecks.

**Displayed information**

| Field                | Description                                                   |
| -------------------- | ------------------------------------------------------------- |
| **Real Time**        | Accumulated time of open requests.                            |
| **Total Requests**   | Total number of registered tickets.                           |
| **Open Tickets**     | Number of tickets that are still awaiting service or closure. |
| **Open Ticket Time** | Time elapsed since the oldest ticket was opened.              |
| **Latest Tickets**   | Summary history of recent tickets.                            |

> The data is automatically updated as tickets are opened and closed.

#### 2.1.3. Documentation

The widget **Documentation** shows the number of documents linked to the operation in progress. To access the documents, simply click the widget and the document directory will be displayed for document viewing.

These documents may include:

* Work instructions;
* Operational procedures;
* Technical drawings;
* Process specifications;
* Quality documents.

**Displayed information**

| Field               | Description                                                                |
| ------------------- | -------------------------------------------------------------------------- |
| **Total Documents** | Number of documents available for consultation during operation execution. |

> The documentation is configured in BackOffice and made automatically available to the operator according to the operation performed.

#### 2.1.4. Quality

The widget **Quality** shows indicators related to the quality of the production performed.

This information helps monitor the defect rate and identify production deviations.

**Displayed information**

| Field                 | Description                                                                               |
| --------------------- | ----------------------------------------------------------------------------------------- |
| **Defective Pieces**  | Number of scrapped pieces relative to the total produced.                                 |
| **Quality Indicator** | Percentage calculated based on the relationship between good pieces and defective pieces. |

> The indicator is updated automatically according to the scrap entries made by the operator.

#### 2.1.5. Equipment Availability Timeline

The timeline provides a time-based view of equipment usage throughout the shift or production period.

It allows quick visualization of the equipment's operational states and identification of production or unavailability periods.

**Timeline Objectives**

* View the equipment's operational history;
* Identify productive periods;
* Analyze interruptions and stoppages;
* Assist in analyzing availability and OEE.

**Visual interpretation**

The colors shown in the timeline represent the equipment's operational states.

Example:

| Color  | Meaning                                             |
| ------ | --------------------------------------------------- |
| Green  | Equipment in production                             |
| Yellow | Equipment stoppage period **with justification**    |
| Red    | Equipment stoppage period **without justification** |

> Equipment availability is updated in real time according to the entries made in Titan.

#### Benefits of Informational Widgets

The widgets were developed to provide the operator and supervision with a consolidated view of the operation, allowing:

* Real-time production monitoring;
* Tracking operational efficiency;
* Quality control;
* Fast ticket and support management;
* Consultation of operational documents;
* Analysis of equipment availability.

> This information supports operational decision-making and strengthens traceability and continuous improvement of production processes.

## **3. Production Reporting**

Production reporting can occur in two ways:\
1\) Manual Reporting\
2\) Automatic Reporting

### 3.1. Manual Reporting

Used when there is no direct integration with the equipment.

* The operator clicks on **Report**
* Informs the produced quantity
* Confirms the entry
* The system automatically updates:
  * Produced quantity
  * Remaining balance
  * Progress bar
  * Production time

<figure><img src="https://2582153898-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwAMVKtJedtiJ4RrzXGfp%2Fuploads%2FnmhC9Yqovv3DhQHoEPLc%2FReporte%201.png?alt=media&amp;token=3fc4d3cb-ca75-49b6-a994-55751455b068" alt=""><figcaption><p>Access to Manual Reporting</p></figcaption></figure>

<figure><img src="https://2582153898-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwAMVKtJedtiJ4RrzXGfp%2Fuploads%2FvBT88b8Ayn4pF93kZk75%2FReporte%202.png?alt=media&amp;token=e2ecc720-f2b3-49da-af37-69afd4ea7f47" alt=""><figcaption><p>Entry of produced quantity</p></figcaption></figure>

<figure><img src="https://2582153898-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwAMVKtJedtiJ4RrzXGfp%2Fuploads%2FuUFLrL3bWpxIn6RkAxDz%2FReporte%203.png?alt=media&amp;token=106e5012-fc71-48aa-9335-e5f5d93193d9" alt=""><figcaption><p>Operation Progress Update</p></figcaption></figure>

### 3.2. Automatic Reporting (Machine Integration)

The functionality of **Production Entry with Automatic Collection** allows Sequor MES to capture signals directly from equipment or IoT devices to count produced pieces during the execution of an operation.

This integration allows the system to receive automatic signals from the machine, ensuring greater reliability in production data and reducing the need for manual operator intervention.

Automatic collection can operate in two distinct modes:

* **Visual Counting (Recorded)** — used only for monitoring production by the operator.
* **Automatic Production Reporting** — where each received signal automatically generates an official production record.

This functionality ensures that only signals received **during the actual execution of the operation** are considered, avoiding distortions caused by signals generated outside the production context.

When there is integration:

* The system receives the cycles automatically
* Reporting occurs without operator intervention
* Quantities and times are updated in real time

#### 3.2.1. Automatic Collection Setup in the Operation

The automatic collection setup is performed in the **Capabilities module (Capability)**, in the **Production Routes**tab, during the registration or editing of the production operation.

For each IoT link configured in the operation, the following parameters are available:

#### **IoT Link**

Defines the IoT device or signal source responsible for sending counting events to the system.

<figure><img src="https://2582153898-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwAMVKtJedtiJ4RrzXGfp%2Fuploads%2FUco05rLMaOXpqMDlTb0y%2FCapacidade%20-%20IoT%20Link.png?alt=media&amp;token=09bc72fb-708b-4411-8d97-aa179adff2b4" alt=""><figcaption><p>Capabilities - IoT Link</p></figcaption></figure>

#### **Automatic counting**

When enabled, Sequor MES begins listening for counting events coming from the linked IoT device.

If disabled, no automatic counting signal will be considered for the operation.

<figure><img src="https://2582153898-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwAMVKtJedtiJ4RrzXGfp%2Fuploads%2FwVh0yOqEttSbW1V65tZG%2FCapacidade%20-%20contagem%20autom%C3%A1tica.png?alt=media&amp;token=5c3566b9-2da8-4d14-9aff-12ef7a92b101" alt=""><figcaption><p>Capabilities - Automatic counting</p></figcaption></figure>

When the operation is configured with:

* **Counting by Signal = Active**
* **Use as Report = Disabled**

Sequor MES then performs only the **visual counting of produced pieces**.

In this scenario, the signals sent by the IoT device are used exclusively to monitor production by the operator.

The count is displayed in Titan through the field **Recorded**.

<figure><img src="https://2582153898-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwAMVKtJedtiJ4RrzXGfp%2Fuploads%2F80ls4HIISrQu1ScDg9Rj%2FReporte%20automatico%20apurado.png?alt=media&amp;token=85468760-78ea-4eb3-9c78-bde4c35963bc" alt=""><figcaption><p>Automatic counting - Recorded pieces</p></figcaption></figure>

**Characteristics of visual counting**

In this mode:

* the count is maintained only during operation execution
* the value is updated in real time
* no official production record is generated

Therefore, this count **does not generate**:

* production reports
* MTU
* serialization
* labels
* inventory movement

#### **Validate entry**

Defines how automatic counting will be used in the system.

When enabled:

* Each received signal is treated as a **official production report**.

When disabled:

* The count will be used only for visual monitoring of production.

<figure><img src="https://2582153898-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwAMVKtJedtiJ4RrzXGfp%2Fuploads%2Fbv8N4lSNxTq0biBjS7Gs%2FCapacidade%20-%20validar%20apontamento.png?alt=media&amp;token=cad4644d-d164-4dcc-a0f9-0fb5d59ffb3a" alt=""><figcaption></figcaption></figure>

When the operation is configured with:

* **Counting by Signal = Active**
* **Use as Report = Active**

each received signal from the IoT device is treated as a **official production report**.

In this mode, Sequor MES automatically performs the same flow used in **manual reporting**.

Each signal increment can generate:

* production record
* MTU generation (when applicable)
* label generation
* automatic printing (when configured)
* operation balance update
* Production Order progress update

All records are saved in the same tables used by the standard manual reporting flow, ensuring complete consistency between entry methods.

This approach avoids creating parallel production flows and maintains the integrity of industrial data.

<figure><img src="https://2582153898-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwAMVKtJedtiJ4RrzXGfp%2Fuploads%2F9IOlcEha5pLXtndLi4v8%2FReporte%20automatico%20apurado%20e%20pe%C3%A7as%20ok.png?alt=media&amp;token=ed26f3e6-2e6c-4df7-be68-42eb8a1e1d22" alt=""><figcaption><p>Validate entry - Recorded + Reported pieces</p></figcaption></figure>

#### 3.2.2. Validity Rules for IoT Signals

To ensure the reliability of production data, Sequor MES applies strict validation rules to signals received from IoT devices.

A counting signal will only be considered valid when, at the time it is received:

* there is an **active Production Order** in the system
* the **operation is in status In Progress**
* the **equipment linked to the IoT signal is associated with the current operation**

If any of these conditions are not met:

* the signal is **discarded automatically**
* the event **is not recorded**
* no data is stored or accumulated

⚠️ Important

The system **does not keep signal buffers** and **does not process events retroactively**.

This means that signals generated before the start of operation execution will not be considered later.

This approach ensures that production data reflects only the actual execution of the operation.

#### 3.2.3. Benefits of Automatic Production Collection

The integration between Sequor MES and IoT devices significantly increases the reliability and automation of production control.

#### Among the main benefits are:

**Greater reliability of production data**

Automatic collection reduces dependence on manual entries and eliminates typing errors or omissions.

**Full traceability of execution**

Each signal received is linked to:

* equipment
* operation
* production order
* exact moment of execution

This ensures full traceability of the production process.

**Greater accuracy in calculating industrial indicators**

Automatic collection directly contributes to the reliability of indicators such as:

* OEE (Overall Equipment Effectiveness)
* equipment productivity
* operational efficiency
* real-time production

**Alignment with the real flow of the shop floor**

Context validation prevents signals generated outside the execution period from being considered.

This avoids common distortions in environments where equipment can generate signals even without active production.

**Solid foundation for industrial automation**

This feature allows Sequor MES to operate in an integrated way with connected industrial environments, aligning with the principles of **Industry 4.0**, where machines, systems and operators share data in real time.

## **4. Access to Defect Control (Scrap)**

Defect reporting can be accessed in two ways:

* Via the **side menu**
* Via the button **Scrap** on the bottom bar of the screen

<figure><img src="https://2582153898-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwAMVKtJedtiJ4RrzXGfp%2Fuploads%2Feag3LZZb4UWQQpCKY42x%2FRefugo%201.png?alt=media&amp;token=db580f66-a45f-4ee1-ba90-396225f1fdcb" alt=""><figcaption><p>Access to Defect Control (Scrap)</p></figcaption></figure>

This module is directly integrated with Production Control.

### **4.1. Types of Defect Reporting**

The system allows two types of entry:

**Reporting by Produced Piece**

* The defect is assigned to the final product
* The production balance is adjusted
* The system **automatically reflects the impact on components**

**Reporting by Component**

* The defect affects only the selected component
* The balance of produced pieces **is not changed**
* Ideal for intermediate process losses

<figure><img src="https://2582153898-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwAMVKtJedtiJ4RrzXGfp%2Fuploads%2Fou79YiappV4NLWfxgoCX%2FRefugo%202.png?alt=media&amp;token=b9f5d6d4-8845-493c-8682-032591dcfede" alt=""><figcaption><p>Scrap Entry</p></figcaption></figure>

### **4.2. Selection of Defect Type**

The defects are organized in a **classification tree**, ensuring standardization and later analysis.

<figure><img src="https://2582153898-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwAMVKtJedtiJ4RrzXGfp%2Fuploads%2F5CxOsPWqQ6jN2QzqPgtC%2FRefugo%203.png?alt=media&amp;token=db4ab0a1-8446-43e8-876c-20789097242e" alt=""><figcaption><p>Defect Tree</p></figcaption></figure>

Category examples:

* Structural
* Functional
* Surface

Examples of defects:

* Surface cracks
* Burrs
* Scratches
* Stains

> The tree can have multiple levels, depending on the client's configuration.

### **4.3. Defect Quantity Entry**

After selecting the defect:

* The operator enters the quantity
* The system validates whether there is available balance
* The impact is calculated automatically

<figure><img src="https://2582153898-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwAMVKtJedtiJ4RrzXGfp%2Fuploads%2F81gJwXjFW7Q48VR5lGyG%2FRefugo%204.png?alt=media&amp;token=6a2ef21a-cda6-4bd5-b440-71d9ffa67cdd" alt=""><figcaption><p>Scrap quantity entry</p></figcaption></figure>

### **4.4. Defect Observations**

The operator can include additional notes:

* Defect context
* Apparent cause
* Action taken

<figure><img src="https://2582153898-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwAMVKtJedtiJ4RrzXGfp%2Fuploads%2FNVlPP6R2QXWOTguzf3nf%2FRefugo%205.png?alt=media&amp;token=90f60ced-dbfb-4ded-9682-192ed0376050" alt=""><figcaption><p>Field to add notes</p></figcaption></figure>

This information enriches quality analysis and traceability.

\
**Confirmation of Entry**

Before finishing, the system displays a confirmation:

> “Are you sure you want to add the defect?”

<figure><img src="https://2582153898-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwAMVKtJedtiJ4RrzXGfp%2Fuploads%2F2JlfNZxzBfgytYnv0hVR%2FRefugo%206.png?alt=media&amp;token=0accbffd-ba37-4b53-b324-fbf7279a891a" alt=""><figcaption><p>Entry confirmation</p></figcaption></figure>

After confirming:

* The defect is recorded
* The balances are updated
* The operation history is enriched

### **4.5. Consolidated Scrap View**

On the scrap screen, the operator views:

* Total produced
* Total scrapped
* Scrap by component
* Possibility of removal

<figure><img src="https://2582153898-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwAMVKtJedtiJ4RrzXGfp%2Fuploads%2FiCXSMq6mF5b9pglnTlAF%2FRefugo%207.png?alt=media&amp;token=c6685bf5-8b26-430c-8a34-5b968dd217fa" alt=""><figcaption><p>Scrap Tracking</p></figcaption></figure>

## **5. Completion of the Operation**

When execution is finished:

* The operator clicks on **Finish Operation**
* The time is closed
* The operation is released
* The data is available for analysis in the BackOffice

<figure><img src="https://2582153898-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwAMVKtJedtiJ4RrzXGfp%2Fuploads%2FssJ1HAAqjpaTAUS6WFxb%2FConcluir%201.png?alt=media&amp;token=1d8e9369-d8cd-4d31-9307-d4bc733b7da3" alt=""><figcaption><p>Finish Operation</p></figcaption></figure>

<figure><img src="https://2582153898-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwAMVKtJedtiJ4RrzXGfp%2Fuploads%2FeFNz9X2L4NVgrkJJDORX%2FConcluir%202.png?alt=media&amp;token=83e941f0-ff99-4629-a08c-3b5c4b3bea52" alt=""><figcaption><p>Completion confirmation</p></figcaption></figure>

## **6. Benefits of Production Control**

The module of **Production Control** of Sequor MES acts as the **operational core of the factory**, connecting planning, execution, quality, and performance in a single continuous data flow.

Its main function is **to turn what was planned into actual execution**, with full traceability and reliable data for decision-making.

#### **Standardized and guided execution on the shop floor**

* The operator executes only **flows allowed by the planning**
* Execution standardization regardless of shift or operator
* Less dependence on tacit knowledge

#### **Full traceability of production**

* Detailed record of:
  * Equipment used
  * Responsible operator
  * Production Order
  * Operation performed
  * Real execution time
* Audit capability by piece, batch, or component
* Consolidated history for process and quality analyses

#### **Reliable, real-time entries**

* Simple and quick manual reporting
* Direct integration with equipment for automatic entry
* Elimination of paper entries or parallel spreadsheets
* Data always up to date for supervision and management

#### **Accurate management of times and efficiency**

* Real measurement of production time by operation
* Clear separation between:
  * Productive time
  * Downtime
  * Unproductive time
* Solid basis for calculating:
  * Operational efficiency
  * Machine performance
  * Production bottlenecks

#### **Native integration with quality and scrap**

* Defect entry integrated with execution
* Clear differentiation between:
  * Defects per produced piece
  * Defects per component
* Automatic reflection of impacts on balances
* Structured basis for analyzing losses and recurring causes

#### **Consistent basis for industrial indicators**

The data generated by Production Control directly feeds indicators such as:

* OEE (Availability, Performance and Quality)
* Scrap rate by operation
* Productivity by operator and equipment
* Efficiency by Production Order
* Actual versus planned lead time

#### **Scalability and alignment with Industry 4.0**

* Works independently or integrated with machines
* Scalable for different levels of automation
* Prepared for hybrid environments (manual + automatic)
* Connects the shop floor to corporate systems

#### **Data reliability for the BackOffice**

* Structured and standardized data
* Reduction of rework in information consolidation
* Direct integration with modules for:
  * Planning
  * Quality
  * Maintenance
  * Performance analysis

#### **Single integrated view of production**

Production Control eliminates information silos and creates a **continuous data line**, from planning to final execution, ensuring that:

> *What was produced, how it was produced and with what efficiency* is always visible and reliable.
