ENLYZE
🇬🇧 ENLYZE
🇬🇧 ENLYZE
  • Welcome to ENLYZE
  • Getting Started
    • Quickstart
  • Guides
    • Platform Configuration
    • Machine Setup
      • Variable Selection
      • Configuring OEE Data Collection
      • Machine Data Sheet Template
    • Defining Downtime Reasons
    • Downtime Contextualisation
    • Connecting Booking Data
      • Integration of MES, BDE, or ERP-Systems
      • Synchronising Production Context via Machine Data
      • Booking Production Orders via the ENLYZE App
    • SPARK Setup
      • Preparations
      • Installation
      • Connecting to the Manufacturing Data Platform
    • ENLYZE EDGE
      • Accessing the Interface
      • Configuring the Network
      • Setting Up Routes
      • Managing Routes
      • Network Tools
      • Troubleshooting
  • PLATFORM
    • Integrations
      • Grafana
        • Structure of the ENLYZE Data Sources for Grafana
        • Connecting ENLYZE to Grafana
        • Tutorials
          • First steps with Platform Grafana
          • Grafana Basics for Process Monitoring
          • OEE data with Infinity data source
          • Mapping UUIDs to Display Names with Infinity Data Source
      • Power BI
        • Installing the ENLYZE Power BI Integration
        • Structure of the ENLYZE Power BI Connector
        • Tutorials
          • Getting Started with the ENLYZE Power BI Connector
          • Querying Time Series Data from Machine Variables
          • Querying Machine Productivity Metrics
          • Mapping UUIDs to Display Names
          • Calculating Aggregated Timeseries Data
  • EDGE
    • Overview EDGE Functionalities
    • SPARK Edge Device
    • ENLYZE EDGE
  • IT Security
    • IT Security
  • Why is the connection secure even though a warning is displayed
  • How to Choose the Right Integration Scenario?
  • Resources
    • Glossary
Powered by GitBook
On this page
  • Why Production Context is Indispensable
  • Added Value Through Linking Machine and Context Data
  • How can Production Context be Integrated?
  • Required Attributes
  • Mandatory Attributes
  • Optional Attributes
  1. Guides

Connecting Booking Data

Capturing the Production Order Assignment of Your Machines

PreviousDowntime ContextualisationNextIntegration of MES, BDE, or ERP-Systems

Last updated 2 days ago

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:

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.

Required Attributes

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

Mandatory Attributes

These are essential for successful integration.

Attribute
Description

order_code

Unique identifier of the production order

product_code

Identifier of the manufactured product, used for product-specific analyses such as Golden Runs and data sheets

start

Start time of the production order (timestamp)

end

End time of the production order (timestamp)

machine_code

Machine on which the production order was executed

Optional Attributes

Additional attributes that can be synchronized but are not required.

Attribute
Description

quantity_total

Total quantity produced within the production order

quantity_good

Quantity of good units produced

quantity_bad

Quantity of scrap produced

Integration of MES, BDE, ERP Systems

Automatic synchronization with the current booking system.

Integration via Machine Data

Reading production assignments from variables in the machine control system.

Booking via the ENLYZE App

Manual data entry through the ENLYZE App.

Machine data linked with production context: production orders (purple bars), machine downtimes, and performance trends