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
  • Prerequisites
  • Accessing the Downtime UI
  • How to Contextualise a Downtime
  • Assigning a Reason
  • Splitting a Downtime
  1. Guides

Downtime Contextualisation

PreviousDefining Downtime ReasonsNextConnecting Booking Data

Last updated 8 days ago

Providing reasons for machine downtimes is essential for analyzing and improving production performance. At ENLYZE, this process is called downtime contextualisation.

This guide walks you through assigning reasons to detected downtimes in the ENLYZE platform.

Prerequisites

Before you start, ensure that:

  • Downtime detection is configured for the relevant machine

  • Downtime reasons have been defined in your ENLYZE configuration Defining Downtime Reasons

Accessing the Downtime UI

Downtime contextualisation is performed through the ENLYZE App:

You can access the contextualisation interface in two ways:

  1. Production Overview Panel. It is located on the app's home page and shows downtimes per machine for the selected time range.

  1. Downtime Section. Provides the complete list of downtimes across all machines. Use the dropdown in the upper-left corner to filter by machine.

To begin contextualising, simply click on the downtime entry you'd like to edit.

How to Contextualise a Downtime

The contextualisation interface shows an overview of the selected downtime and the downtime editor:

Assigning a Reason

  • Browse the predefined reasons, organized by categories and groups.

  • Click a reason to assign it directly to the downtime.

  • Optionally, add a comment for clarification.

  • Click Save (bottom right) to apply your changes.

  • Click Cancel (bottom left) to discard your changes and restore the previous state

Splitting a Downtime

To split a downtime into multiple parts:

  1. Define time intervals

  2. Assign reasons to each segment individually.

Once a downtime is contextualised, the information becomes available in the ENLYZE Manufacturing Data Platform. This means it can be used by any connected service or application for reporting, analysis, or optimization.

Click the scissors icon below the downtime plot

➡️
➡️
app.enlyze.com
Configuring Downtime Detection