Independent fluid-testing and condition-monitoring knowledge
LUBRICANTS & FLUIDSWIKIUnderstand · test · interpret · protectSearchRequest testing
Programme design · 11 min

Build the test slate from failure modes—not a universal package

A useful panel covers fluid condition, contamination and machine wear at a depth justified by the asset, failure mechanisms and maintenance decision.

Reviewed Jul 2026 · Lubricants & Fluids Wiki editorial team
Build the test slate from failure modes—not a universal package technical evidence illustration
Visual field guide

This visual orients the topic; the article explains the evidence controls, method limitations and maintenance decisions in detail.

The same routine panel should not be applied unchanged to a diesel engine, servo hydraulic system, steam turbine and enclosed gearbox. A defensible test slate begins with credible failure modes, asks which evidence can reveal them early enough to act, and defines what happens when a routine signal changes.

Start with the maintenance decision

Define what the programme must improve: detect abnormal wear, control contamination, extend drains, verify incoming fluid, evaluate filtration or diagnose an event. The objective determines the evidence depth and sampling frequency. A low-cost panel that cannot answer the decision is expensive data; an advanced test without an action rule is equally wasteful.

Rank the asset by safety, environmental, production and repair consequence. Add failure-development time, redundancy, sampling accessibility and laboratory turnaround. Critical fast-developing modes may need shorter intervals, field screening or complementary online monitoring rather than simply a larger laboratory panel.

  • Name the asset, compartment and fluid
  • List credible failure modes and their detectable precursors
  • Define the maintenance decision and response time
  • Document the reason for every routine test

Cover three evidence dimensions

A balanced panel considers lubricant or fluid condition, contamination and machine wear. Viscosity, acid or base reserve and infrared condition indicators address the fluid. Water, particles, fuel, soot, glycol or process material address contamination. Elemental analysis, ferrous density, particle morphology and filter debris address machine wear.

Coverage does not mean requesting every available test. It means avoiding a blind dimension. For example, viscosity and elemental analysis alone may miss water-driven corrosion or cleanliness deterioration; elemental spectroscopy alone may under-represent large wear particles. The panel should reflect both the likely mechanism and the response range of the method.

  • Fluid condition: identity, viscosity, degradation and additive reserve
  • Contamination: water, particles, wrong fluid, fuel, coolant or process ingress
  • Wear: fine elements, bulk ferrous debris, particle count and morphology

Separate routine and exception testing

Routine tests should be repeatable, economical and sensitive to the expected precursors. Triggered tests answer a focused question after a trend change, operating event or inspection finding. A rising ferrous signal may trigger PQ, ferrography, filter debris analysis or component-specific sampling; suspected varnish may trigger membrane patch, antioxidant or deposit-tendency work.

Write the trigger before the event occurs. Examples include an unusual rate of change, two correlated indicators, a severity-class transition, visible debris, filter differential-pressure change, overheating or a known contamination incident. Pre-agreed triggers reduce delay and discourage indiscriminate retesting.

  • Routine screen creates the trend
  • Exception test localises or confirms the mechanism
  • Inspection and maintenance findings close the evidence loop

Review the slate as the programme learns

A panel is a controlled hypothesis, not a permanent catalogue. Compare alerts with inspections, replaced components, filters and root-cause findings. Remove tests that never influence decisions only after confirming they do not protect an important failure mode; add or change tests when failures escape detection or false alarms recur.

Keep method, units, sample point and reporting basis stable enough for trend continuity. When a method changes, establish comparability or a new baseline rather than treating two different analytical systems as one uninterrupted history.

Key takeaways

  1. 01Design from asset risk and failure modes
  2. 02Cover fluid, contamination and wear evidence
  3. 03Define routine and triggered tiers
  4. 04Tie every abnormal pattern to a response
  5. 05Use field feedback to improve the panel

References and further reading

  1. POLARIS Laboratories: Get the Most Value from Your Program: Advanced Testing
  2. Machinery Lubrication / Noria: How to Create an Effective Oil Analysis Test Slate
  3. OELCHECK: Test methods for lubricant, coolant and fuel analyses

Continue in the Wiki