Many lubricant performance claims are technically correct, but lubricants still fail in real applications.
Why technically correct lubricants still fail in practice
Over time, new machines or installations are added to the asset portfolio. With that, new lubricants are introduced and existing product portfolios are often reconsidered. On paper, this creates opportunities for improvement. In practice, there is rarely time to fully review those changes.
Product rationalisation or the introduction of new lubricants may look straightforward, but they introduce uncertainty. What works in one application does not automatically hold in another. Turbines, compressors, and hydraulic systems each operate under different conditions, contamination levels, and maintenance regimes.
Decisions to change are often based on limited data, from product testing as well as from the actual application. As a result, uncertainty remains. The consequences of being wrong can be significant: downtime, warranty exposure, and performance disputes.
Test data, specifications, or experience from other systems do not always translate directly to the actual operating context.
This is where Proof of Performance becomes relevant as a way to build and interpret application-specific evidence.
Two different questions Proof of Performance is used to answer
In practice, Proof of Performance is used to answer two fundamentally different questions. Confusion starts when these questions are treated as one.
Decision Proof, the operational question
The first question is operational: What does this mean for operation, reliability and maintenance decisions?
In this role, Proof of Performance supports choices for improvements or interventions, for example:
Improvements:
- Does it reach the expected and planned oil drain interval?
- Do the used oil analysis and machine data confirm the expected performance?
- Does it actually realise the expected savings?
- Does it reduce lubricant portfolio complexity?
- Does it reduce lubricant mixing errors or misuse?
Interventions:
- intervening now versus managing until a scheduled maintenance window
- adjusting operating boundaries or duty cycles
- changing maintenance strategy or monitoring focus
- validating whether an intervention improved stability under real operating conditions.
“Intervention” does not automatically mean “resolution”. In many real systems the first goal for intervention is stabilisation, buying time safely until a scheduled maintenance window. System data & used oil analysis must show whether that stabilisation is actually holding.
The same evidence that supports an operational decision often becomes the starting point for a second question: What can we credibly say about performance and where are the boundaries?
Claim Proof, the technical and commercial question
The second question is commercial and technical: What can we credibly claim about performance, both technical and financial and under what conditions?
Here, Proof of Performance supports:
- defensible performance claims and qualification language
- credible case studies, technical description and white papers
- substantiated financial and operational value, including cost savings, energy savings and operational improvements
- alignment between R&D, application engineering, product management, marketing, and sales
- fewer disputes about what datasheets and specifications really mean.
Boundary conditions and assumptions
Proof of Performance becomes useful when assumptions are made explicit. It is strongest when it clarifies:
- what was measured and what was not
- the application conditions such as load, environment, and duty cycle
- maintenance, operating and failure history
- data sources and their limitations, including test data, specifications, used oil analysis and condition monitoring.
What Proof of Performance cannot do on its own
Proof of Performance is powerful, but it is not magic.
On its own, it cannot:
- reliably explain causality in complex systems
- guarantee future behaviour under different conditions
- replace engineering judgement.
Minimum viable proof versus full proof
In real organisations, Proof of Performance rarely starts as a complete validation programme. It often starts as minimum viable proof: sufficient evidence to support a decision or claim, while acknowledging what is still unknown.
This:
- prevents overclaiming
- keeps messaging aligned with evidence
Outcome formats
To remain effective, Proof of Performance should deliver explicit outputs:
- Internal decision support: a clear decision logic explaining what changed and what action is taken
- External claim substantiation: bounded, defensible performance statements with explicit assumptions.
- Sales enablement assets: case briefs, technical notes, or white‑paper inputs aligned with engineering reality.
Key takeaway
Proof of Performance is not a single‑purpose proof engine. It is a discipline for keeping technical truth consistent across:
- application reality
- decision‑making and
- credible communication.
In practice, performance data, decisions and communication are closely connected.
This is the foundation of how technical performance is validated in practice and how a structured approach connects data to decisions and claims.
Contact us to discuss your situation or specific questions.