Mobius Institute
At 8:10 on a Monday morning, a gearbox on Line 2 is due for grease.
The work order is closed ten minutes later. On the screen, the task is green. At the machine, the fitting is difficult to reach, the grease gun is not clearly identified, and nobody checks whether old grease has somewhere to escape.
The schedule says the work happened. It cannot tell you whether the right product reached the right point in the right amount.
This is how a plant can have hundreds of lubrication tasks and still live with hot bearings, contaminated oil, repeat top-ups and failures that seem to arrive without warning.
The missing piece is control: who owns the decision, which product is approved, how the work is performed, what evidence is recorded and what happens when reality does not match the plan.
Ninety days will not transform an entire site. It is enough time to take one important area, find the weak links, build a method people can follow and see whether that method holds up during normal operations.
A green work order proves that someone clicked complete. It does not prove that the machine received the right care.
The schedule was never the whole program
A lubrication route is a calendar. It can remind someone that a bearing is due for grease. It cannot confirm that the gun contains the approved product, the fitting is clean, the quantity is right or the bearing can purge safely.
The wider system is where many programs become fragile. Engineering may choose the product. Stores receives it. Maintenance applies it. A laboratory reports on its condition. When those decisions live in separate files and separate conversations, the machine carries the gaps.
ICML 55.1 reflects this wider view by organizing lubrication management across twelve connected areas. Field execution, lubricant control, competence, condition monitoring and management review are not separate projects. They are different parts of the same promise to the asset.
The first 90 days should expose where that promise breaks. Keep the scope small enough that the team can see the work clearly and fix what it finds.
Days 1 to 30: walk the lubricant path
Start with shoes on the plant floor, not a mouse in the CMMS. Choose one production area or asset family where the consequence of poor lubrication is easy to understand. Give one person enough authority to bring maintenance, operations and stores into the same conversation.
The first month should feel more like an investigation than a rollout. Stand beside the machine. Find every lubrication point. Confirm the product, quantity, method, interval, operating condition and responsible role. If a value is unknown, record the uncertainty instead of borrowing an answer from the nearest machine.
Then follow the lubricant in the other direction. Begin where it enters the site and trace the container through storage, transfer, application, sampling and disposal. Every handoff is a chance for contamination or confusion to enter the process.
Open drums, shared funnels, faded labels and damaged breathers are obvious findings. The harder findings are tasks that look sensible on screen but cannot be performed safely or consistently at the machine.
- Can a technician identify the exact point without guessing?
- Is the approved product clear on the machine, the container and the task?
- Can the work be performed safely under actual access and operating conditions?
- Would a supervisor know what evidence proves the task was done correctly?
Days 31 to 60: make the right action the easy action
By day 31, the team should know where the work is ambiguous. Now it can remove that ambiguity.
A useful instruction is not a paragraph copied from a manual. It names the exact point and approved product. It states the quantity, method and safe condition for the task. It explains what normal looks like and when the technician must stop and ask for help.
Use the night-shift test. Hand the instruction to a trained person who did not write it. Can that person find the point, choose the right equipment, complete the work and record the result without calling the author? If not, the instruction still depends on tribal knowledge.
The lube room needs the same treatment. Sealed containers, dedicated transfer equipment, clear identification and controlled receiving practices make the correct choice easier before anyone reaches the machine. Colour and symbols can help, but they should support the written specification rather than replace it.
Sampling deserves its own field check. A convenient sample port is not automatically a representative one. The location, method, flushing practice and test slate should match the machine and the failure modes the team is trying to see.
Days 61 to 90: let the plant argue back
A tidy procedure can survive a meeting and still fail on Tuesday night. The last month is where the plant gets to challenge the design.
Run the pilot during normal operations. Let production priorities, awkward access, shift changes and urgent work put pressure on it. Observe a sample of tasks in the field without turning every visit into an announced audit.
When someone misses a task or invents a workaround, do not begin with blame. Ask whether the point was accessible, the instruction was clear, the right tool was available and the escalation path made sense. A workaround is often the process telling you where it is weak.
Bring oil-analysis findings into the same review. A high particle count or water result needs machine context, a named decision owner and a way to confirm closure. Forwarding a laboratory report is not the same as responding to it.
Keep the weekly exception conversation short enough that it actually happens. The team needs to leave knowing what changed, who owns the next action and what evidence will close it.
- What happened, and what else changed at the same time?
- Did the approved method fit the machine and its operating condition?
- Who owns the correction, and what evidence will prove it is closed?
- Is this a local issue, or could the same weakness exist elsewhere?
Completion is the weakest number on the dashboard
A plant can report 98 percent schedule compliance and still have dirty transfer containers, wrong-product events and repeat bearing problems. Completion is useful, but it is the beginning of the review rather than the verdict.
Read execution and machine condition together. Did the task happen as designed? Did the lubricant stay clean and dry? Did abnormal consumption fall? Were confirmed exceptions acted on before the next sample or failure?
Keep the scorecard small. Every measure should lead to a conversation or a decision. If nobody knows what action a number should trigger, it is decoration.
Establish the baseline before announcing a target. Asset criticality, operating conditions and the maturity of the current program all shape what useful improvement looks like.
At day 90, scale the evidence
The day-90 review should not be a victory lap. Walk the pilot with the technician, supervisor, stores representative and analyst who lived with it. Ask what became easier, where people still had to improvise and which machine conditions actually changed.
Scale the controls that people can execute and supervisors can verify. Fix the access, data and workflow problems that still produce workarounds. Expand by asset family or production area so the next group inherits a tested method rather than a large presentation.
Some findings will justify hardware, filtration or software investment. Others will be solved by a label, a sample port, a clearer job plan or a named decision owner. The pilot helps the plant spend money where the work has already shown a need.
Ninety days does not finish a plant-wide program. It earns the right to take the next step with less guesswork.
The goal is not a perfect lubrication slide. It is a machine that receives the same correct care on a quiet morning, a busy afternoon and a short-staffed night shift.
What to watch
Six signals that show whether control is improving.
| Measure | What to review | Cadence |
|---|---|---|
| Task quality | Critical tasks completed on time and to the approved method | Weekly |
| Exceptions | Missed work, abnormal use, access problems and repeat defects | Weekly |
| Product control | Wrong, mixed or unidentified lubricant findings | Weekly |
| Contamination | Cleanliness, moisture or ingress exceptions against asset targets | Per sample |
| Condition response | Time from confirmed exception to action and verified closure | Monthly |
| Standard quality | Instructions corrected after field observation or failure review | Monthly |
Before you expand
What should be true at day 90.
Each point should be visible in the work itself, not only documented in a presentation.
- One accountable person can explain the pilot boundary and the decisions that belong inside it.
- A technician can find every critical point and approved product without guessing.
- Lubricants remain identified and protected from receiving through application.
- Each task is safe, specific and usable during the shift when it is actually performed.
- Sampling locations and tests reflect the machine and the failures the team needs to detect.
- Exceptions reach a named owner and stay open until evidence confirms closure.
- Supervisors can verify task quality without relying only on completion status.
- The team knows what is ready to expand and what needs another round of work.
Common questions
Questions teams ask before they start.
Can a machinery lubrication program really be built in 90 days?
Not across an entire plant. Ninety days is enough to establish ownership, verify one focused group of assets, improve the work and test a controlled pilot before deciding what should expand.
What is the first step in improving a lubrication program?
Choose one important but manageable area and name the person who owns the decisions. Without a boundary and an owner, an audit usually becomes a long list that nobody is clearly responsible for closing.
Do we need lubrication-management software before starting?
No. A controlled register can support the pilot when ownership, revision control and task evidence are clear. Select software after the team understands the data, workflow and reporting it must support.
Which training supports lubrication-program implementation?
Machinery Lubrication I builds shared fundamentals, Machinery Lubrication II develops program-design depth, and Machinery Lubrication Engineer focuses on plant-wide leadership. Oil-analysis roles can add the relevant MLA pathway.
