This article is for plant managers, maintenance managers, production managers and manufacturing engineers who run several aging machines with a limited modernization budget. The question is not whether retrofit is a good idea, but which machine to start with. Measured downtime and breakdown history lets you decide on facts rather than on the impression left by the last breakdown.
- The machine to retrofit first is not always the oldest.
- Only technical stops count when prioritizing.
- A machine’s weight in the flow changes the ranking.
- Safety comes before any data-based ranking.
What CIM Atlantique says about retrofit
CIM Atlantique, an integrator based in Nantes and Normandy working in AI vision, robotics, mechanical design and automation, published Retrofit électrique et mécanique : Modernisez vos machines avec CIM Atlantique (in French), written by Rémi Gueudré. The page defines retrofit as modernizing existing machines rather than replacing them, details three areas (electrical, mechanical, automation), compares retrofit with a new machine and describes a five-step approach that starts with an audit of the existing machine: a full analysis of the machine, its constraints and its obsolescence. Among the expected benefits it lists: “Réduction des arrêts subis et de la maintenance curative.” (in other words: fewer unplanned stops and less corrective maintenance).
That audit qualifies one machine. One decision comes before it: in a fleet of several older machines, which one should be audited and modernized first? This is where measured downtime helps. It does not replace the integrator’s expertise; it helps the plant arrive at the audit with a short, well-argued list.
Why intuition is not enough to prioritize
In many plants, the machine considered the worst is the one with the most spectacular or most recent breakdown. It is not always the one that costs the most. One machine fails rarely but for long periods, another stops thirty times a day for a few minutes, a third never breaks down but is the bottleneck of the shop: their real weight only shows in a measured history qualified by reason.
Signals that point to a candidate machine
The table below lists the most useful indicators for comparing machines before a retrofit. None is enough on its own: it is their combination that makes a candidate stand out.
| Signal | Data to look at | What it can indicate |
|---|---|---|
| Frequent breakdowns | Number of unplanned technical stops per week | Worn components, recurring electrical faults |
| Long repairs | Mean time to repair (MTTR), waiting for parts | Obsolete or hard-to-source parts |
| Repeated micro-stops | Frequency of short stops by reason | Sensors, guides or drives at end of life |
| Position in the flow | OEE of the machine and its neighbors | Bottleneck: every hour lost is lost for the whole shop |
| Scrap after breakdown | Scrap at restart after a technical stop | Settings drift, unstable process |
Separating what a retrofit can fix from what it will not
A retrofit acts on the machine: electrical components, wear parts, guides, PLCs and interfaces. It does not act on organization. Stops for waiting on material, missing operators, long changeovers or planning issues will still be there after the project. For example, a machine that loses most of its time waiting for supply will gain almost nothing from modernization, even if it is the oldest in the fleet.
Hence the importance of qualifying each stop by reason and keeping only time lost to technical causes for prioritization. That is the time a retrofit can reduce, and the time to compare before and after the project.
Step-by-step method to rank the fleet
- Measure over several months. Collect timestamped stops for each candidate machine over a period long enough to cover seasonal variation and rare breakdowns.
- Qualify the reasons. Separate technical causes (breakdown, wear, electrical fault, PLC) from organizational ones (waiting, staffing, changeover).
- Compute technical time lost. For each machine, add up the duration of technical stops and note their frequency and average duration.
- Weight by position in the flow. An hour lost on a bottleneck counts more than an hour lost on a machine with spare capacity.
- Cross-check with known obsolescence. Add what maintenance already knows: unsupported PLC, parts no longer available, risk of a long breakdown.
- Draw up a short list and have it audited. Present two or three machines to the integrator, with their data, for the audit of the existing machine.
- Set a baseline. Keep the pre-project measurement so the gain can be quantified after the retrofit.
Safety and compliance come before any ranking
One caution: prioritizing by downtime is about availability and reliability gains. A machine whose safety or compliance is in question is dealt with first, whatever its history. Downtime data is there to order the rest of the fleet, not to delay making a machine safe.
What TEEPTRAK brings
TEEPTRAK measures OEE, stops and micro-stops in real time. A module wired into the electrical cabinet and a sensor at the line record machine activity automatically, with no connection to the PLC, so older machines with an obsolete or closed PLC can be equipped too. Installation takes about one hour per machine and OEE is available within 48 hours. Stops are timestamped and qualified by reason, providing a comparable basis to rank machines before a retrofit and then measure the gain afterwards. The solution is deployed in more than 700 plants in over 30 countries.
Further reading
- Retrofit électrique et mécanique : Modernisez vos machines avec CIM Atlantique (CIM Atlantique, in French)
- Machine retrofit: measure OEE before and after to quantify the gain
- MTBF MTTR unplanned downtime: measuring equipment reliability
FAQ
How long should you measure before prioritizing? Long enough to see rare breakdowns and activity swings. A few weeks already show frequent stops; several months are better for long, infrequent breakdowns.
Should you always retrofit the oldest machine? No. Age is only one clue. The machine to address first is the one whose technical stops weigh most on the flow, taking obsolescence and safety into account.
Does downtime history replace the integrator’s audit? No. It helps choose which machines to audit and brings facts to the audit. The technical diagnosis of the machine remains the integrator’s job.
0 Comments