Precision machining · breakdown with no alarm
A coolant fault with no alarm at all: a day of diagnosis, brought down to 30 minutes
The machine tool is no longer delivering coolant. The screen stays silent. At this precision machining subcontractor, it took a day to understand why.
About this case
A demonstration on a breakdown the site had already experienced, run with no imported history. Site anonymised.
The situation: the machine no longer delivers coolant, and says nothing
On a machine tool, swarf falls onto a conveyor belt that carries it away. The coolant passes through a filtration system before returning to the tool.
One day, the coolant flow stops. No fault is displayed.
The blocker: with no alarm, you search everywhere
When a machine displays a fault, it guides the search. Here, the screen is silent. The technician checks what they know, tests whatever comes to mind, looks for what is wrong.
According to the site, this diagnosis took a day.
The walkthrough: starting from how it works, rather than from the symptom
The breakdown is replayed during a demonstration, with no past intervention loaded in the tool.
The functional chain of the coolant system
Instead of asking what is wrong, you ask Mimorian how the coolant system works, end to end. It describes the functional chain, component by component.
The filtration system stands out
In this chain, the filtration system appears. It had entered a safe state without reporting a fault. The element stands out in under five minutes.
A test plan to confirm it
Mimorian then builds the test plan that lets you verify this possible cause on the machine, step by step.
The result: a day reduced to half an hour
By following this test plan, a technician identifies the problem in 30 minutes at most, according to the maintenance expert who ran the demonstration. On the site's side, the same diagnosis had taken a day.
The difference lies in the question asked. You find the cause of a breakdown with no alarm by tracing back the functional chain of the machine, and Mimorian can describe how it works, component by component.
A silent screen, a day of searching. The answer was in how the machine works: all it took was tracing it back.
Frequently asked questions
How do you diagnose a breakdown when no alarm is displayed?
By starting from how the machine works rather than from the symptom. In this case, Mimorian described the functional chain of the coolant system, component by component, and the filtration system, which had entered a safe state in silence, appeared.
What is a test plan proposed by Mimorian?
A sequence of ordered checks to confirm or rule out a possible cause on the machine. The technician follows them, notes what they observe, and the diagnosis moves forward on facts.
Does Mimorian work with no breakdown history?
Yes. Here, no past intervention was in the tool. Mimorian relies on how the machine works to propose its diagnostic approach. History, when it exists, enriches it.
A machine that stops without saying anything?
Describe the breakdown to us. We trace back the functional chain of the equipment concerned with you, and you see where it leads.
Explore the other use cases
Industrial SME · key machine
The machine idle for 18 months
No usable documentation, only paper diagrams. Modelled from scratch on site, the machine restarted the same day.
See the use caseHeavy truck manufacturer · assembly line
The fuse diagnosed in 10 minutes
A test in real conditions on an assembly line. Client's written report: 3 parts saved, 1.5 hours of repair avoided.
See the use caseFoundry and machining company · criticality upstream
The part the FMEA never saw
8 hours of downtime for a part never rated critical. Mimorian flags these components upstream, from the documentation.
See the use caseVacuum heat treatment · plant memory
The breakdown that returns every 2 years
Cycle complete, door locked, already experienced 2 years earlier. A diagnostic demonstration on the real machine, imported.
See the use caseAluminium extrusion · diagnosis without history
The cable cut by an aluminium offcut
6 hours of downtime, 4 of them spent on diagnosis. Replayed with Mimorian, with no history: the sensor and its cable pointed out in 12 minutes.
See the use casePlastics processing · machine history
The answer was sitting in the history
More than half a day of downtime the first time. With Mimorian, the cause comes out of the history in 2 minutes, backed by the wiring diagram.
See the use caseHigh-volume production · recurring breakdowns
The breakdown everyone knew about
Known unofficially, never quantified. As soon as the history is imported, two components stand out: 22 and 8 occurrences.
See the use casePharmaceutical packaging · diagnosis and improvement
The cap detected twice
Every bottle rejected. Mimorian confirms a double detection, steers the diagnosis towards the product, then prepares the improvement in 5 minutes instead of an hour.
See the use caseFood & beverage · preventive maintenance
Preventive maintenance with no wiring diagram
No diagram, an empty twin. By the end of the intervention, the machine has its digital twin and the client its report, in the format it expects.
See the use caseSpeciality chemicals · process unit
The filling that would not happen
More than two months of spaced-out interventions. Picked up again with Mimorian from the P&IDs, the search starts from how the unit works and the cause comes out in 45 minutes.
See the use case