Menu
Light MES · Manufacturing performance platform

Downtime Tracking Software for Production LinesSee line stops as they happen. Know what they cost in OEE.

Fabrico logs stops on connected machines from the PLC, an IoT sensor or a camera (add-on).

  • Live during the shift
  • No end-of-shift logs
  • ISO/IEC 27001
Plant and line OEE. Real Fabrico screen, sample data.Plant and line OEE. Real Fabrico screen, sample data.

Trusted by manufacturing groups

ABBSchaefflerHitachi Energykdc/oneLufthansa TechnikAkzoNobelFicosota

One shift, hour by hour

Many short stops look nothing like one long breakdown, even when the minutes match.

See machine monitoring
Real Fabrico screen, sample data.Real Fabrico screen, sample data.

The stop list names each cause

Reason, planned or unplanned, and when it started.

Real Fabrico screen, sample data.Real Fabrico screen, sample data.

Operators tag the cause at the line

They pick it on a tablet, or scan a machine's QR code to open it.

Stock photo: an operator at the machine.Stock photo: an operator at the machine.

Micro-stops and slow cycles stay separate

You can tell a stopped machine from one running below standard speed.

See OEE software
Real Fabrico screen, sample data.Real Fabrico screen, sample data.

See how it works in a live demo.

FAQs

How do you track machine downtime automatically?

Fabrico reads the machine's own run and stop signal instead of handwritten logs. A stop record opens the moment the signal changes, stamps the start time and counts the length until production resumes.

What are downtime reason codes?

An agreed list of stop causes, such as a jam, a tool change or a missing operator. A fixed list instead of free-text notes is what lets downtime add up by cause.

How long does it take to start tracking downtime?

With hardware, installing and connecting the devices takes about 1 month, and full rollout takes 3 to 4 months. Reason codes, shifts and dashboards are set up with your team along the way.

More detail

How to calculate availability, with an example

Availability is run time divided by planned production time. An example with made-up numbers: a 480 minute shift with 30 minutes of planned breaks leaves 450 planned minutes. A 25 minute breakdown and a 20 minute wait for material take 45 minutes, so run time is 405 minutes, and 405 divided by 450 is 90%. Availability is then multiplied by performance and quality to give OEE. To put a value on the gap to your target OEE, use the OEE calculator.

Downtime analytics by cause, line and shift

Filter downtime by cause, by line and machine, by shift, or by period, to check a change against the weeks before it. Any list exports to Excel, and the REST API and webhooks connect other systems. Groups with several sites can compare plants side by side, which works best when plants agree on the same reason codes. Maintenance is built in, so a repair is linked to the same machine as the stop.

Find out what your losses cost. Recover the output you already own.

See how losses get a price tag in a live demo.

By clicking the Accept button, you are giving your consent to the use of cookies when accessing this website and utilizing our services. To learn more about how cookies are used and managed, please refer to our Privacy Policy e Cookies Declaration