Plastics processing · machine history
A breakdown that cost half a day of downtime, found in the history in 2 minutes
The rotary table rotates, the hatch stays open, and the screen shows no fault. At this plastics processing site, this breakdown had already stopped a machine for more than half a day. Yet the solution existed, somewhere in the history.
About this case
A demonstration on the site's real data (wiring diagrams and machine history), on a breakdown it had already experienced. Site anonymised.
The situation: a breakdown already experienced, an answer nobody can find
On one of the site's machines, the rotary table rotates but the hatch stays open. No fault appears on the screen. The first time, the machine stayed down for more than half a day.
The maintenance manager knows this breakdown well. During the demonstration, the maintenance manager describes it to Mimorian to see what it finds.
The blocker: the information exists, but you still have to find it
The right intervention is somewhere in the machine's history, among all the others. Finding it takes the team 15 to 20 minutes, provided they know what to look for.
But a silent screen leaves the technician with no lead. The site's experience is there, in a file consulted by hand.
The walkthrough: querying the history as you would talk to a colleague
The wiring diagrams and the machine history were imported before the demonstration. The maintenance manager describes the symptom, live.
The diagram and the history cross-checked
Mimorian matches the symptom described against the wiring diagram, the documentation and the machine's past interventions.
Two possible causes already experienced
It brings up two leads the site has already come across: a rotary table positioning problem, and an incorrect locking feedback signal.
The sensor at fault, pointed out
Mimorian narrows the search to a sensor jammed during rotation. The maintenance manager confirms: replacing that sensor is indeed what had fixed the breakdown.
The result: the history becomes an answer
About two minutes to bring up the element at fault, against 15 to 20 minutes of manual searching, and more than half a day of downtime the first time the breakdown occurred.
The site had nothing to re-enter. Its history, as it kept it, became searchable in everyday language, cross-checked with the machine's diagram. The next time the hatch stays open, the answer will be there.
A silent screen, half a day of downtime the first time. The answer was already in the history: all it took was being able to ask it.
Frequently asked questions
Do I need a clean, structured history to use Mimorian?
No. In this case, the history came from a file kept by the site, imported as it was. Mimorian reads interventions written in everyday language and matches them to the machine's wiring diagram, with no fault codes or prior configuration.
How do you trace a breakdown when no fault is displayed?
By starting from the symptom observed rather than from a code. Here, "the rotary table rotates but the hatch stays open" was enough: Mimorian brought up two possible causes already experienced, then the sensor at fault.
What does a maintenance team gain by querying its history?
Search time first: about two minutes instead of 15 to 20 in this case. Above all, the team starts again from what has already worked on this machine, rather than restarting the diagnosis of an already solved breakdown from scratch.
Is your breakdown history gathering dust in a file?
Bring it along with the diagrams of one machine. We show you what it answers when queried on a breakdown you know.
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 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 casePrecision machining · breakdown with no alarm
The coolant flow stopped with no alarm
A silent screen, a day of diagnosis. Starting from the functional chain, Mimorian points to the filtration system and proposes a test plan: 30 minutes at most.
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