Washdown Is a Process, Not a Claims Event: Monitoring Bosch Motion in UK Food Plants

Ask a UK food plant why a motor failed and the answer often begins with the washdown. The claim form follows, complete with photographs of a water-ingressed terminal box and a bearing that has lost its grease. The argument is understandable but incomplete. Washdown is not an isolated event that invalidates a warranty; it is a repeated process condition. If the motor, installation and monitoring regime are not designed around that process, the failure is predictable. The useful response is engineering, not negotiation.

IP ratings are a boundary condition, not a guarantee

IP66, IP67 and IP69K describe protection against defined water and dust conditions under defined test arrangements. They do not certify chemical compatibility with caustic or acidic cleaning agents. They do not guarantee that a high-pressure jet will never force past a shaft seal. They do not cover thermal cycling, condensation inside a warm enclosure, or a cable gland that was correctly tightened at commissioning and then disturbed during a repair. A motor can carry an impressive IP rating and still fail because the mounting orientation directs spray into a breather, or because the seal material is wrong for the CIP chemistry.

Hygienic design matters as much as the enclosure. Smooth surfaces, drain paths, correct gland selection and a mounting position that avoids pooling are part of the protection. In UK food plants working to BRCGS and EHEDG principles, the equipment boundary is usually well understood. The gap is often the maintenance boundary: the motor is treated as a sealed box rather than a component with seals, bearings, lubricant and cable entries that all interact with the cleaning regime.

What CIP does to bearings and seals

A CIP cycle is a sequence of chemistry, temperature and pressure. The motor may be hot from production, then hit with cooler wash liquor; later it may be rinsed and left wet in a cold room. That thermal shock draws moisture through breathing paths and can emulsify bearing grease. Caustic and acid cleaners attack some elastomers. High-pressure spray finds the weakest point, usually a shaft seal lip or a terminal box gasket. If the motor is mounted shaft-up, water can sit around the seal; if it is mounted in a splash shadow, it may stay wet far longer than the cleaning schedule assumes.

The bearing is often the first casualty, but not always the first symptom. Grease that has been washed out or degraded will show as rising vibration at bearing frequencies, a temperature increase, or audible noise. By the time the bearing is rough enough to hear on the line, the intervention window has usually closed. Seal distress may appear as a slow ingress path, insulation resistance drift, or corrosion in the terminal box. These are trends, not events.

Use the drive as a sensor

Bosch drive diagnostics are underused in washdown applications. Modern drives already calculate or expose motor current, torque, speed, DC bus voltage, power and drive temperature. They record fault history and, on many units, can capture a trace around a trip. The value is not the single alarm; it is the pattern across CIP cycles. A rise in running current at the same product rate, a change in torque ripple, or a growing DC bus disturbance can indicate mechanical or insulation distress before a protective trip.

Set a commissioning baseline after the first full production and CIP cycle, not immediately after installation. Capture the same data at a defined load point. Then compare after each washdown or at least weekly. Look for rate of change rather than absolute thresholds alone. A motor may run at 78% current for years; if it moves to 84% over two months with no product change, that is a signal. Combine drive data with insulation resistance testing and bearing temperature where sensors are fitted. Do not rely on the drive's thermal model to detect water ingress; it is designed for thermal protection, not condition monitoring.

Vibration trending that survives washdown

Handheld vibration routes still have a place, but washdown areas reward permanent or semi-permanent sensors. A sensor that is removed and refitted on a wet, cramped motor can introduce more variability than the fault it is meant to detect. Mount accelerometers on a solid part of the motor or gearbox, protect the cable route, and record the same measurement point every time. Trend overall velocity for rotating faults and high-frequency acceleration for early bearing distress. Take a reading after the CIP cycle as well as during production; some ingress effects appear only when the machine is cold and wet.

The most useful vibration programme is small and disciplined. One route, ten critical motors, a consistent load condition and a named owner will outperform an occasional consultant survey. If a trend moves, inspect the seal, breather, gland and grease condition before changing the motor. The inspection record then becomes evidence for the next design review, not just the next claim.

A practical playbook for UK sites

Start with a zone matrix: dry, splash, washdown and high-risk areas. For each motor, record the IP rating, seal material, lubricant, mounting orientation, cleaning chemicals and CIP temperature. Add the drive ID and the data points available from the drive. Set a baseline after commissioning and after the first CIP cycle. Review drive trends weekly and vibration trends monthly. Define intervention triggers in advance: a bearing temperature rise of 10 K, a current increase of 5% at the same load, a vibration step, or a repeated insulation resistance drop after washdown.

Then act before downtime. Re-grease or replace bearings on condition, not only on the calendar. Check gland torque and seal condition at planned stops. Correct mounting or drainage where water pools. If a motor repeatedly fails in the same washdown position, the answer is usually a specification change, not a stronger warranty argument. The claims process may recover the cost of one motor; it will not recover the production loss.

Washdown is a process condition. Treat it as one, and the maintenance team stops chasing failures after the event and starts planning interventions before the line stops.