Before expanding a lubrication program, give one released job plan to a qualified technician and watch the task at the machine.
If the technician must call the engineer to identify the point, confirm the lubricant, find the quantity, decide the machine state, or interpret an abnormal condition, the plan is not ready to copy elsewhere.
Apply the same test beyond the route. Can stores verify the delivered product? Can a sample be traced to its point and operating context? Does an abnormal result create owned work? Can the plant show that the correction was completed and reviewed?

What the pilot must prove
A 90-day pilot is closer to commissioning a machine than launching a campaign. Commissioning does not ask whether the equipment looks finished. It asks whether each function works under operating conditions, whether safeguards respond, and whether the handover record is usable. A lubrication pilot should face the same kind of test.
In one bounded area, the pilot needs to verify five things: the technical requirements are defensible, the work can be performed safely, lubricant identity and condition survive the route, abnormal findings reach an authorized owner, and completed actions are checked rather than merely marked closed.
ICML 55.1 describes twelve interrelated areas of lubrication management, with ICML 55.2 providing implementation guidance. A short pilot cannot demonstrate long-term reliability improvement across a plant. It can show whether the plant has a working method worth extending and which defects must be corrected first.
Define the area, ownership, and baseline
Choose a plant area small enough to observe in detail and broad enough to expose real handoffs. State which assets, lubricant stores, transfer paths, sampling points, shifts, and contractors are inside the boundary. Record the exclusions. A vague pilot boundary makes every later result debatable.
Name the sponsor who can remove barriers and the owner who runs the pilot each week. Engineering approves machine requirements. Planning controls released work. Stores protects product identity. Technicians and supervisors test whether the work is practical. Operations and EHS decide the operating and safety constraints. One person may hold more than one role, but no decision should be ownerless.
Build the baseline from evidence the team can reproduce. Useful examples include overdue work by defined task population, open wrong-product risks, known contamination findings, recurring alarms, invalid samples, lubricant consumption, and failures with a credible lubrication connection. Record the date range, source, denominator, exclusions, and data owner beside each measure.
Approve the requirements, then test the work
Every lubrication point needs a technically valid lubricant, quantity, interval, method, and safe machine state. Criticality changes the depth of verification, monitoring, documentation, redundancy, and response priority. It does not make an incorrect or ambiguous task acceptable on a lower-consequence asset.
Trace each approved value to current machine documentation, an engineering calculation, operating evidence, or an authorized technical decision. Record assumptions where load, speed, temperature, environment, duty cycle, bearing arrangement, reservoir volume, or current condition affect the requirement. If the machine or operating duty changes, review the affected values before the next task is released.
| Record group | Information to retain |
|---|---|
| Pilot charter and ownership | Scope, objective, sponsor, owner, review rhythm, and scale criteria |
| Asset and lubrication-point register | Asset, component, point ID, criticality, operating context, and current status |
| Approved lubrication requirements | Lubricant specification, quantity, interval, method, machine state, hardware, and technical basis |
| Field work and competence records | Released procedures, routes, assigned tools, practical verification, and current revisions |
| Condition and action records | Sampling or inspection requirements, results, alerts, owners, actions, and closure evidence |
| Pilot scorecard and change record | Baseline, metric definitions, findings, approved changes, unresolved risks, and scale decision |
Then observe the task with the engineer quiet. The user should be able to identify the point, verify the product and tools, establish the required machine state, apply the approved method and quantity, recognize stop conditions, and complete the record without interpretation from the author.
Grease work deserves an explicit pressure response. The plan needs to identify the fitting, the approved quantity, the relief or purge path where one exists, and the conditions that require a stop. If resistance rises, grease does not flow, or a connection leaks, stop pumping. Never search for a pressurized leak with a hand. Relieve pressure and follow the equipment and site safety procedure before inspection. The Graco high-pressure grease dispenser manual warns against forcing lubricant into a blocked fitting and describes the skin-injection hazard.
Course attendance is not a competence assessment. Define the task standard, verify the required knowledge and safety decisions, observe performance under representative conditions, and record who assessed the person and when reassessment is required.
Product control must travel with the job. Do not approve a substitution because two products appear similar on a list. Verify technical equivalence, compatibility, changeover requirements, affected procedures, and approval authority before the change reaches stores or the machine. The route audit in Audit the Lubricant Route, Not Just the Oil Room shows how product identity and condition can be lost between receiving and application.

Connect samples and findings to decisions
Start with the failure mode and the decision, then select the observation or test. A particle count, water result, temperature reading, ultrasound value, filter inspection, leak, or consumption change has little operational value until the plant knows what condition it may reveal and who can decide the response.
Sampling also needs a controlled context. The STLE fluid-sampling article explains the importance of representative locations, repeatable methods, correct identification, and operating information. Record the point, machine state, timing, flushing method, container, product, and recent work that could affect interpretation.
ISO 4406:2021 defines a code for reporting solid-particle contamination in hydraulic fluid. The code does not select a cleanliness target for a machine. Set the target from current OEM guidance, component sensitivity, operating conditions, lubricant formulation, warranty obligations, and plant risk.
A finding is not closed because it was logged or because a work-order status changed. Use the plant's approved process to complete containment and corrective work, review the required evidence, and have the authorized owner verify the intended condition or formally accept the remaining risk. A recurrence should reopen the reasoning behind the previous action, technical requirement, procedure, hardware, competence, and operating context.
Run the pilot and decide what is safe to copy
The sequence below is a practical operating rhythm, not a promise that every plant will finish the same work on the same date. Move to the next phase only when its gate has been met or the appropriate authority has recorded the remaining risk and decision.
Define and understand
- Approved pilot boundary and owner
- Asset and lubrication-point register
- Current lubricant route
- Baseline and open-risk register
Engineer and test
- Approved machine requirements
- Tested procedures and routes
- Assigned tools and handling controls
- Sampling, response, and competence requirements
Execute and stabilize
- Completed work cycles and record review
- Owned findings and verified corrections
- Revised procedures and scorecard
- Scale decision and remaining-risk list
Use only the measures needed for the scale decision. Define each denominator, review window, data source, owner, exclusions, and consequence before the first result is reported.
- On-time task completion: Tasks completed by their approved due time divided by tasks due
- Evidence completeness: Completed task records containing every mandatory field divided by completed records reviewed
- Sampling-record conformance: Reviewed samples with the required point, machine state, timing, flushing, container, and identification fields confirmed divided by samples reviewed
- Verified action closure: Actions completed by the approved due date and accepted with the required closure evidence divided by actions due
- Repeat finding rate: Eligible points with a recurrence during the defined review window divided by points with a prior finding that remained in service
Do not advance because the quarter has ended or because activity counts look healthy. At the end of 90 days, ask whether the area has approved machine requirements, executable job plans, traceable samples, owned findings, verified corrections, and records the next person can use. Copy only the parts that survived that test.
Test one plant area before you expand
VAS can assess one bounded area, verify the machine requirements and field procedures, and leave your team with a prioritized pilot plan.
Sources and method
This guide uses ICML 55.1 as the lubrication-management reference, ISO 4406 for contamination coding, and technical articles published by STLE for sampling and oil-analysis practice. The 90-day sequence, record set, and scorecard are a proposed VAS pilot method, not requirements of those sources. VAS is a licensed Noria partner. The Noria link below describes Noria's own program-development method.