Pharmaceutical packaging · diagnosis and improvement
Every bottle rejected: a cap detected twice, then the improvement
On a pharmaceutical packaging line, the machine rejects every bottle. The technician on site looks for the reason. The maintenance expert called in to assist sees the machine for the first time that very day.
About this case
A real on-site intervention, carried out by a maintenance expert with Mimorian. Site anonymised.
The situation: a line that rejects everything
On a bottling line, the machine rejects everything. The technician on site looks for the reason. The maintenance expert who steps in sees the machine for the first time that day.
The blocker: an unfamiliar machine, a hunch to confirm
The expert quickly suspects a double detection: for every bottle, the machine seems to count two. Faced with equipment you have never seen before, a hunch remains a hunch. Before touching anything, you need facts.
Some machines trigger on the sensor's rising edge, then start a delay timer precisely to ignore an unintended second detection. Here, something was getting through.
The intervention: from confirmed diagnosis to improvement
On site, the expert photographs the machine and talks it through with Mimorian.
Sensors identified from a photo
The expert photographs the sensors. Mimorian reads their markings, finds them on the wiring diagram and explains the role of each.
The lead confirmed by tests
The expert puts forward the double detection lead. Mimorian provides factual elements and proposes a series of tests. The tests confirm it: detection is from above, and the slightly curved cap is detected at the start, lost in the middle, then detected again at the end. The machine thinks it sees two bottles.
The product, rather than the machine
The search leaves the machine and concentrates on the product. The cause is the shape of the cap, and the answer lies in how it is detected.
From sketch to improvement proposal
The expert sketches an angled detection by hand and sends the sketch to Mimorian, which structures the improvement proposal and searches for suitable sensors and technologies.
The result: a reliable diagnosis, an improvement proposed
The diagnosis is confirmed by facts, and the search concentrates on the cap rather than on the machine. The expert leaves with a structured improvement proposal and a selection of sensors.
On this last step, Mimorian did in five minutes what would have taken at least an hour of searching and comparing components on the internet, according to the expert. The troubleshooting and the improvement fit into the same intervention.
A slightly curved cap, seen twice by the sensor, and a whole line rejected. The cause was in the product, and the improvement option in a sketch.
Frequently asked questions
How does Mimorian help with a machine you have never seen?
It identifies components from a photo of their markings, finds them on the wiring diagram and explains their role. The person intervening tests a hunch against factual elements and tests, and moves forward on facts.
Is Mimorian also useful for improvement?
Yes. In this case, after the diagnosis, the expert sent a hand-drawn sketch of an angled detection. Mimorian structured the improvement proposal and searched for suitable sensors and technologies, in five minutes instead of an hour of searching.
Why does a double detection cause rejects?
The machine counts the products passing through. If one bottle triggers the sensor twice, it thinks it sees two and rejects the whole line. Here, the curved shape of the cap interrupted detection midway through its passage.
A line rejecting with no apparent reason?
Show us the machine and its diagrams. We show you how Mimorian helps confirm the cause, then prepare the improvement.
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 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 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