Home / MES Software / Overview

Tracking Downtime

Increase Machine Up Time With Downtime Analysis


  • Real-Time Efficiency Tracking
  • Downtime Data Collection
  • At-a-Glance Executive Dashboards
  • Easy ERP Integration
  • Mobile MES Access
  • Production Scheduling
  • Fast, Customizable Implementation
  • Automatic Data Collection


  • Java SE 8+ (server)
  • Java SE 6+ (client)
  • Dual-Core Processor (32 or 64 bit)
  • 4GB RAM
  • 10GB free HD space
  • (requirements vary by usage)

Supported Operating Systems

  • Windows Server 2003/2008/2012
  • Windows Vista, 7, 8 and 10
  • Ubuntu Linux 8.04 or later
  • Other Java 6+ enabled OSes*

Supported Databases

  • We support any database that has a JDBC driver, including:
  • Microsoft® SQL Server
  • Oracle
  • IBM DB2
  • MySQL
  • PostgreSQL
  • Firebird
  • Others
  • *Ignition is compatible with any Java 6+ enabled operating system. Full support is only offered for listed operating systems.

Identify Top Downtime Reasons

Track downtime to see where to focus efforts to improve availability of manufacturing equipment. Think of it this way, if your production line typically runs at 69% OEE availability, what actions do you take to increase it? Tracking downtime is the key.
Downtime tracking will identify the production cell (machine or process) that is preventing your production line from producing product efficiently.

Automatic Downtime Tracking

Get real-time downtime information with the OEE Downtime Module. Downtime tracking can be done manually, but history has shown that manually-collected downtime information is not accurate and usually is too old to be used effectively. Downtime software can automatically collect reasons for downtime, and compile it for quick and easy viewing.

Track Downtime Manually

The module supports both automatic and manual collection of downtime reasons, or a combination of both.
Monitoring all downtime reasons automatically is the ideal solution - in a perfect world. But in the real world, can be difficult or just not practical cost-wise to detect downtime reasons automatically. For this reason it is important for downtime tracking software to support both automatic reason detection with a manual override.
For example:
if a operator presses the stop button because they see a bottle laying on its side feeding into a filler, then the only automatic reason that can be detected is "operator press stop button". Now the operator should be able to override the reason with more specific information.

Downtime Analysis

Visually identify and drill down to the top downtime causes that affect your operating efficiency with the OEE Downtime Module.
Once the period of time that production cells were not producing product and the associated reasons are recorded, reviewing the downtime analysis summary of the reasons will identify where effort should be focused to improve efficiency.