The Lubrication Program Most Plants Neglect

Key takeaways

• Lubrication is responsible for a large share of bearing and rotating-asset failures, and it is the maintenance task most plants run worst. The PM schedule says "lubricate," the technician applies grease, the box gets ticked, and a meaningful fraction of those applications are wrong amount, wrong type, or wrong frequency.
• The four lubrication failure modes are over-greasing, under-greasing, contamination, and wrong-product. All four are invisible until the bearing fails, and all four look identical in the failure record as "bearing failure" unless the investigation goes deeper.
• A working lubrication program is built on three things most plants lack: a lubricant identity per lubrication point (not per asset), a quantified application standard (grams, not "until it feels right"), and contamination control at the storage and dispensing stage.
• The single biggest improvement is usually colour-coding and single-point identity: every lubrication point gets a tag specifying the exact lubricant and exact quantity, and the grease guns are colour-matched so the wrong product physically cannot be applied.

Why lubrication is the worst-run PM task

Lubrication looks simple, which is exactly why it is run badly. "Lubricate the bearing" sounds like a task that does not need much specification. The technician knows how to operate a grease gun; the PM schedule says do it monthly; the box gets ticked. Everyone moves on.

The problem is that lubrication is precise work disguised as routine work. The right lubricant, the right amount, applied the right way, into a clean fitting, these specifics are the difference between extending bearing life and causing the failure the lubrication was supposed to prevent.

Most plants treat the task as routine and get routine results: a steady stream of bearing failures that get logged as "bearing failure" and never traced back to the lubrication practice that caused them.

The article on the preventive maintenance schedule covers how lubrication tasks fit into the broader PM cadence; this piece is about getting the lubrication itself right.

The four lubrication failure modes

1. Over-greasing

The most common and the most counterintuitive. More grease is not better. Over-greasing a sealed bearing builds pressure, blows the seal, and lets contamination in, or churns the grease until it overheats and breaks down. Many "we greased it regularly and it still failed" bearings failed because of the greasing, not despite it.

The fix is a quantified standard: a specific number of grams or pumps per point, not "until grease comes out the other side."

2. Under-greasing

The opposite, less common but still significant. A point that needs grease monthly gets it quarterly because the schedule slipped, or gets a token amount because the technician was rushing. The bearing runs dry, overheats, fails. This one usually traces to PM compliance gaps, the lubrication PM kept getting deferred.

3. Contamination

Clean grease applied through a dirty fitting carries contamination straight into the bearing. The grease itself can also be contaminated, stored in an open container, dispensed with a dirty gun, exposed to the plant environment. Contamination is the failure mode most plants do not even consider, because the grease looked clean going in. The piece on root cause analysis covers how contamination failures masquerade as random bearing failures.

4. Wrong product

Most plants stock five to fifteen different lubricants. Applying the wrong one, a high-temperature grease where a standard grease was specified, or mixing incompatible grease types, degrades performance and can cause chemical breakdown. With a grease cart carrying multiple products and no forcing function, wrong-product application is a matter of when, not if.

The three foundations of a working program

1. Lubricant identity per point, not per asset

The unit of lubrication is the lubrication point, not the asset. A single asset can have multiple points needing different lubricants. The program assigns a specific lubricant identity to each point, documented, tagged at the point, and reflected in the PM task. The technician does not decide which grease; the tag tells them.

2. Quantified application standard

Every point gets a quantity: 3 grams, 5 pumps, 10cc. The quantity comes from the bearing size, the speed, and the OEM specification, calculated once per point and documented. "Apply until it feels right" is replaced with a number. The article on manufacturing KPIs covers how lubrication-related failure trends feed back into the standard.

3. Contamination control

Sealed lubricant storage, dedicated dispensing equipment per product, clean fittings (wipe before greasing, replace damaged grease nipples), and filtration where the application volume justifies it. This is the foundation most plants skip entirely, and it is the one that prevents the failure mode nobody was looking for.

The single-point identity system

The highest-leverage practical change most plants can make is colour-coded single-point identity:

• Every lubrication point gets a coloured tag indicating the exact lubricant and quantity.
• Each lubricant has a designated colour.
• The grease guns, transfer containers, and storage are colour-matched to the lubricant.
• The technician matches the colour on the tag to the colour on the gun. Wrong product becomes a colour mismatch they would have to actively ignore.

This system eliminates the wrong-product failure mode almost entirely, because the forcing function is visual and physical rather than dependent on the technician remembering which point gets which grease.

Plants that implement colour-coded single-point identity typically see wrong-product applications drop close to zero and bearing failures attributable to lubrication fall by a meaningful margin within two quarters. The piece on the work order management system covers how the point identity and quantity get embedded into the recurring lubrication task.

How to build the program from where you are

The realistic rollout, one quarter:

1. Weeks 1-3: Survey every lubrication point on the critical asset classes. Document the point, the specified lubricant, the OEM quantity, the frequency. Most plants discover they do not have this documented anywhere; the survey is the foundation.
2. Weeks 4-6: Rationalise the lubricant list. Most plants stock more lubricants than they need; consolidating to the minimum set reduces wrong-product risk and simplifies storage.
3. Weeks 7-9: Implement colour-coding. Tag the points, colour-match the equipment, train the technicians.
4. Weeks 10-12: Fix contamination control at storage and dispensing. Sealed containers, dedicated equipment, clean-fitting discipline.

By the end of the quarter the plant has a documented, quantified, contamination-controlled lubrication program on its critical assets, and a measurable expectation that lubrication-attributable failures will decline over the following two quarters.

How Fabrico fits

The lubrication program works in any CMMS that supports recurring tasks with structured details.

Where a unified OEE + CMMS platform helps is that the lubrication task carries the point identity and quantity (not just "lubricate the asset"), and the bearing-failure trend on lubricated assets is visible against the lubrication-completion record, so the team can actually tell whether the lubrication program is preventing the failures it targets.

Fabrico is built for that workflow. To see how lubrication-point detail looks against your asset hierarchy, book a demo .

Frequently asked questions

How do we calculate the correct grease quantity per point?

The standard SKF regreasing formula uses the bearing outer diameter and width: quantity in grams ≈ 0.005 × outer diameter (mm) × width (mm). It assumes the housing has a path for excess grease to escape; for a fully sealed bearing with no relief, use roughly half. The OEM spec overrides the formula where available.

The exact number matters less than having a documented number that replaces "until it feels right."

How often should we re-lubricate?

Frequency depends on bearing speed, temperature, and load, it is calculable per point but most plants start from the OEM recommendation and adjust based on the failure trend. Over-frequent lubrication is as harmful as under-frequent; the frequency is part of the standard, not a default monthly.

What about automatic lubrication systems?

Auto-lubers solve the frequency and quantity problem on the points they cover, which is valuable on hard-to-reach or high-frequency points. They do not solve contamination or wrong-product at the refill stage, and they fail silently, a clogged auto-luber under-greases without anyone noticing. They are a useful tool on specific points, not a complete program.

How do we handle grease compatibility?

Different grease thickeners can be chemically incompatible; mixing them can cause the grease to break down. The lubricant rationalisation step should map compatibility, and the colour-coding prevents accidental mixing. When changing a point from one grease to another, the bearing should be purged of the old grease first.

What is the most common implementation mistake?

Treating lubrication as a single PM task ("lubricate the asset") rather than as a set of point-specific tasks with individual lubricant identities and quantities. The per-point granularity is what makes the program work; the per-asset granularity is what produces the failures.