Picture the weekly review. Output is short and everyone has a reason. The coolant pump, a late tool, a power dip. Nobody has a number, so the loudest explanation wins.
The shift log says 40 minutes of downtime. The machine data, when someone finally pulls it, tells a longer story. The log was not wrong on purpose. It was written from memory at the end of the shift.
Equipment downtime tracking software removes the memory step. The machine reports its own stops, so the meeting starts with facts.
- It detects every stop, records the duration and attaches a reason, with no one writing it down afterwards
- The signal should come from the machine itself. If a person types the stop in, you have a log, not tracking
- The output that matters is a ranked list of causes by total minutes lost, plus MTTR and MTBF per machine
- Industry pricing guides quote roughly 50 to 300 US dollars per machine per month. Leanworx Lite is free for one machine
- You can test it on a single machine in about 30 minutes before spending anything
What equipment downtime tracking software actually does
It answers three questions about every stoppage: when did it start, how long did it last, and what caused it. Done across every machine and every shift, those answers become a map of where production time goes.
| Record | What it captures | Why it matters |
|---|---|---|
| Start and end time | Exact timestamp of each stop and restart | Removes rounded and forgotten stops |
| Duration | Calculated from the timestamps | Makes 3 minute stops visible when they repeat |
| Reason | Breakdown, tooling, material, operator, changeover | Lets you rank causes instead of guessing |
| Machine and shift | Which asset, which team, which hour | Exposes night shift and shift change gaps |
Equipment or machine? The two terms are used interchangeably in search. In practice, buyers on a machine shop floor want CNC and other production machines tracked, which is what this guide focuses on. For the buyer checklist angle, see our downtime tracking software guide .
How the software knows a machine has stopped
This is the question that separates real tracking from a nicer logbook. Ask any vendor to walk you through how a stop at 2 AM on the night shift ends up in the report.
From the machine control
The software reads status through protocols such as Fanuc FOCAS, MTConnect or OPC UA. Exact timing, no human step.
From added sensors
Sensors on power or spindle infer running versus stopped. Useful where the control cannot be read, but adds hardware cost.
Operator entry
Someone presses a button or fills a form. Short stops get skipped and timing drifts.
The numbers it should give you
Raw stops are only the start. Two maintenance metrics turn them into decisions.
MTTR = Total repair time / Number of failures
How long a failure keeps you down on average. Reduce it with spares and clear fault procedures.
MTBF = Total run time / Number of failures
How long a machine runs between failures. If it falls month on month, act before the next breakdown.
The third output is a Pareto: every cause ranked by total minutes lost. Teams usually find the biggest loss is not the dramatic breakdown they remember but a repeating small stop. Our downtime log template shows the manual version of this analysis.
What it costs, with real numbers
Published industry pricing guides put software at roughly 50 to 300 US dollars per machine per month, and many add one time hardware and integration costs on top. Always ask for the total at your machine count, in writing.
| Leanworx plan | Price | Machines | Key inclusions |
|---|---|---|---|
| Lite | Free, no credit card | 1 | Run status, utilization, essential dashboards, email alerts |
| SME | $55 per machine monthly or $540 per machine yearly | Multiple | Mobile alerts, advanced dashboards, trend reports, full data history |
| Pro | Custom | Multi plant | ERP and MES integration, maintenance management, custom dashboards |
Annual billing works out to $45 per machine per month, which saves $120 per machine each year, about 18 percent against monthly billing.
| SME machines | Monthly billing per year | Annual billing per year | You save |
|---|---|---|---|
| 5 | $3,300 | $2,700 | $600 |
| 10 | $6,600 | $5,400 | $1,200 |
| 20 | $13,200 | $10,800 | $2,400 |
A quick payback check. Assume a machine hour is worth Rs 800 and tracking helps you recover 30 minutes a day over 26 working days. That is about Rs 10,400 of machine time a month for one machine. Compare that against the subscription at the day's exchange rate. Swap in your own hour rate and minutes.
Start free on one machine in about 30 minutes
The fastest way to judge any tool is to run it on your own machine. Leanworx Lite is built for that, and the steps are short.
- Fill the form with your machine control, shift timings and time zone
- Leanworx sets up your cloud account for you
- You receive the installer link, instructions and licence key by email
- Install, log in and connect the machine
- Start seeing stops, uptime and utilization
Where Indian shops lose time that nobody records
Leanworx research across 2000 machines found that making downtime visible changed results quickly, in shops of exactly this size.
- › Unaccounted downtime fell 32 to 83 percent once stops were captured automatically
- › Shift change losses fell 43 to 95 percent because handover gaps became measurable
- › Night shifts hide the most. Thin supervision means stops go unlogged until the morning review
- › High mix work multiplies changeovers. Without timestamps, setup time is argued about, not measured
See your own stops this week
Start with one machine on Leanworx Lite, free and with no credit card. Move to SME when you want every machine and mobile alerts.
FAQs:
1. What is equipment downtime tracking software?
It detects when a machine stops, records how long it stayed stopped and captures the reason. The record lets teams rank causes by lost time and fix the biggest one first, instead of relying on shift logs written from memory.
2. How is it different from a CMMS?
Downtime tracking records what happened on the floor. A CMMS manages the maintenance response, such as work orders, schedules and spares. Most shops gain more by tracking downtime first, because the data shows which machines deserve maintenance attention.
3. How does the software know a machine has stopped?
For CNC machines it reads status from the control, for example through Fanuc FOCAS, MTConnect or OPC UA. Because the signal comes from the machine, short stops and exact durations are captured without anyone writing them down.
4. How much does equipment downtime tracking software cost?
Industry pricing guides quote roughly 50 to 300 US dollars per machine per month, often with extra hardware costs. Leanworx Lite is free for one machine. Leanworx SME is 55 US dollars per machine monthly or 540 US dollars per machine yearly. Pro is custom priced.
5. Can I try downtime tracking for free?
Yes. Leanworx Lite monitors one machine for free with no credit card and no commitment. Setup takes about 30 minutes.
6.Which machines does Leanworx Lite support?
Fanuc FOCAS, Haas NGC with MTConnect, Mazak MTConnect, Siemens OPC UA, Mitsubishi M80 and M800, Brother CNC C00 and D00 series, Hurco with MTConnect, and DMG Mori with MTConnect.
You cannot reduce downtime you never recorded.
Pick one machine, track it for two weeks and rank the causes. The first Pareto usually settles the argument about where to start. Then read our guide on the top 5 ways to reduce machine downtime and work the list from the top.