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
  • Integration Options
  • API Access
  • Direct Database Access
  • Supported Data Structures
  • 1. Order Table
  • 2. Booking Table
  • What Information is Required for an Integration?
  • How is the Integration Performed?
  1. Guides
  2. Connecting Booking Data

Integration of MES, BDE, or ERP-Systems

Automatic Synchronization of the Production Context via Direct Integration of MES, BDE, or ERP Systems

PreviousConnecting Booking DataNextSynchronising Production Context via Machine Data

Last updated 2 days ago

The integration of your booking systems can currently only be performed by an ENLYZE integration expert. This service is billed based on effort using a daily rate. Please contact your ENLYZE representative for further information.

Integration Options

API Access

If your booking system provides an API that includes the , we can connect to the system through this interface.

One of our integration experts will coordinate with your designated contact person to define which data points are relevant, where they originate from, how the API can be accessed. Then the necessary ETL (Extract, Transform, Load) job to synchronize the data with the ENLYZE platform will be developed.

Direct Database Access

If your booking system runs on-premise, the simplest integration method is often direct database access. For this, we use our edge device SPARK, which connects directly to the database.

The connection can be made using an existing SPARK device from the machine network or via a dedicated SPARK device specifically for integrating your MES or ERP system. If a corporate firewall exists between SPARK and the booking system, it must be configured to allow outgoing connections to the IP address and TCP port of the server. Incoming connections from the booking system to the SPARK do not need to be permitted.

Additionally, a read-only user account is required for the relevant areas of the database server. This approach is mutually beneficial, as it ensures ENLYZE's read operations are clearly separated and traceable from other users’ operations. Only essential data is shared, and all write operations are technically blocked.

We support the following databases:

Supported Databases

Microsoft SQL Server

MySQL

MariaDB

Oracle Database

PostgreSQL

Supported Data Structures

To enable automatic synchronization of the production context, we support two types of structures:

1. Order Table

Contains one row per production order, with all relevant information summarized:

order_code
product_code
start
end
machine_code

AB-12345

25-1002

2022-01-11 06:27:00+00:00

2022-01-11 11:37:00+00:00

M1

AB-67890

25-1002

2022-01-11 12:10:00+00:00

2022-01-11 17:37:56+00:00

M1

2. Booking Table

Contains one row per booking transaction. Multiple bookings related to one order are grouped using the same order_code.

Timestamp
order_code
product_code
machine_code
event

2022-01-11 06:27:00+00:00

AB-12345

25-1002

M1

START

2022-01-11 08:23:55+00:00

AB-12345

25-1002

M1

END

2022-01-11 12:10:00+00:00

AB-67890

25-1002

M1

START

2022-01-11 17:37:56+00:00

AB-67890

25-1002

M1

END

What Information is Required for an Integration?


How is the Integration Performed?

Since every system is unique, each integration is tailored to your specific configuration. If you are interested in automatic synchronization, we recommend a joint discussion with us and your system experts to determine the best approach.

Our integration experts will then work together with your team to define the detailed integration strategy. An individual ETL job is then developed to ensure a continuous data flow into the ENLYZE platform.

mandatory attributes