# IT-Connectivity

## Why Production Context is Indispensable

**Machine and sensor data alone are not sufficient** for conducting meaningful analyses in a production environment. Only by linking this data with the so-called **production context** can a complete picture of the manufacturing process emerge. This context includes information such as:

* Which production order or batch was being produced at a given time
* What product was being manufactured
* The resulting quality of the end product
* Additional production-relevant metadata, such as product master data or quality feedback

Only with this additional layer of information, it is possible to obtain precise and meaningful analyses, as well as accurate KPIs and metrics.

This is the result of a timeline that includes all production-relevant information:

<figure><img src="https://4261006941-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSNEuiyRRKwuqtIcaEt45%2Fuploads%2FI6tghiUlFi7m2ZflukZy%2Fimage.png?alt=media&#x26;token=c63cacbc-af0f-402e-8acb-877c047fe7d9" alt=""><figcaption><p>Machine data linked with production context: production orders (purple bars), machine downtimes, and performance trends</p></figcaption></figure>

## Added Value Through Linking Machine and Context Data

Combining production context with machine and sensor data forms the basis for most use cases in manufacturing:

* **Targeted Data Analysis:** Process data can be filtered and compared by production order, product, or quality events – for example, for root cause analysis in case of complaints.
* **Automated OEE Calculation:** Overall Equipment Effectiveness is calculated automatically, by product, and for each machine, order, and site.
* **Performance Benchmarking & Golden Run Detection:** Product-specific performance can be systematically evaluated, and optimization potentials identified by comparing with the best-known production run (Golden Run).

These and many other use cases are only made possible through the intelligent linking of process data with production context – forming the foundation for **data-driven production optimization**.

## How can Production Context be Integrated?

We typically source production context from IT systems such as **ERP**, **MES**, **BDE**, or **QMS**. These systems can also be connected to the **ENLYZE Platform**, creating a continuous data foundation that encompasses both OT and IT data.

If this information is not yet digitally recorded, production orders can alternatively be entered via the ENLYZE App to provide the necessary context.

<table data-view="cards"><thead><tr><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><p><strong>Integration of MES, BDE, ERP Systems</strong></p><p><br>Automatic synchronization with the current booking system.</p></td><td><a href="https://github.com/enlyze/enlyze-docs/blob/main/en/connect/it-connectivity/integration-of-mes-bde-or-erp-systems.md">https://github.com/enlyze/enlyze-docs/blob/main/en/connect/it-connectivity/integration-of-mes-bde-or-erp-systems.md</a></td></tr><tr><td><p><strong>Integration via Machine Data</strong></p><p><br>Reading production assignments from variables in the machine control system.</p></td><td><a href="https://github.com/enlyze/enlyze-docs/blob/main/en/connect/it-connectivity/synchronising-production-context-via-machine-data.md">https://github.com/enlyze/enlyze-docs/blob/main/en/connect/it-connectivity/synchronising-production-context-via-machine-data.md</a></td></tr><tr><td><p><strong>Booking via the ENLYZE App</strong></p><p><br>Manual data entry through the ENLYZE App.</p></td><td><a href="https://github.com/enlyze/enlyze-docs/blob/main/en/connect/it-connectivity/booking-production-orders-via-the-enlyze-app.md">https://github.com/enlyze/enlyze-docs/blob/main/en/connect/it-connectivity/booking-production-orders-via-the-enlyze-app.md</a></td></tr></tbody></table>

## Required Attributes

To link production context in ENLYZE with process data, certain attributes are mandatory.

### **Mandatory Attributes**

These are essential for successful integration.

<table><thead><tr><th width="186.44921875">Attribute</th><th>Description</th></tr></thead><tbody><tr><td>order_code</td><td>Unique identifier of the production order</td></tr><tr><td>product_code</td><td>Identifier of the manufactured product, used for product-specific analyses such as Golden Runs and data sheets</td></tr><tr><td>start</td><td>Start time of the production order (timestamp)</td></tr><tr><td>end</td><td>End time of the production order (timestamp)</td></tr><tr><td>machine_code</td><td>Machine on which the production order was executed</td></tr></tbody></table>

### **Optional Attributes**

Additional attributes that can be synchronized but are not required.

<table><thead><tr><th width="185.80859375">Attribute</th><th>Description</th></tr></thead><tbody><tr><td>quantity_total</td><td><strong>Total quantity</strong> produced within the production order</td></tr><tr><td>quantity_good</td><td>Quantity of <strong>good units</strong> produced</td></tr><tr><td>quantity_bad</td><td>Quantity of <strong>scrap</strong> produced</td></tr></tbody></table>
