Skip to main content

Overview

Oil Sample Analysis is the cornerstone of condition-based maintenance in MicroCBM. By monitoring lubricant condition, you can detect early warning signs of equipment wear, contamination, and impending failures before they cause costly downtime.
Oil samples are collected at designated sampling points on assets and analyzed by labs to track trends over time.

What is Monitored

Each oil sample includes four key measurement categories:

Wear Metals

Trace elements indicating internal component wear:
  • Iron (Fe): Gears, shafts, bearings, cylinders
  • Copper (Cu): Bearings, bushings, thrust washers
  • Aluminum (Al): Pistons, bearings
  • Chromium (Cr): Piston rings, shafts
  • Lead (Pb): Bearings, solder
  • Tin (Sn): Bearings, bushings
Rising wear metal concentrations indicate accelerating component degradation.

Contaminants

External substances that degrade oil quality:
  • Silicon (Si): Dirt, dust, airborne contamination
  • Sodium (Na): Coolant leaks
  • Water (H₂O): Condensation, seal leaks
  • Fuel Dilution: Incomplete combustion

Particle Counts

ISO cleanliness codes measuring particle sizes:
  • 4μm: Fine particles
  • 6μm: Medium particles
  • 14μm: Large particles
Reported as ISO code (e.g., 18/16/13) indicating contamination severity.

Viscosity Levels

Oil thickness at different temperatures:
  • Measured in centistokes (cSt) or centipoise (cP)
  • Indicates oil degradation and additive depletion
  • Deviations suggest oxidation, fuel dilution, or wrong oil grade

Sample History & Trend Analysis

The Sample History page provides powerful trend visualization to identify developing issues.
1

Select Filters

Choose the parameters to analyze:
  • Organization: (SuperAdmin only) Select which organization
  • Site: Filter by site location
  • Asset: Select the equipment
  • Sampling Point: Choose the specific sample location (required)
  • Date Range: Optionally limit the time period
2

Load Chart

Click Load chart to generate the trend visualization.
3

Analyze Trends

Review the line chart showing:
  • X-axis: Sample dates (chronological)
  • Y-axis: Concentration values in ppm (parts per million)
  • Series: Each wear metal and contaminant plotted as a separate line with distinct colors
Look for:
  • Steady increases: Gradual wear
  • Sudden spikes: Catastrophic events
  • Declining trends: Effective corrective actions
4

Investigate Anomalies

Hover over data points to see exact values. If you notice concerning trends:
The chart displays up to 50 samples per query. Use date range filtering to focus on specific periods.

Sampling Points

Sampling points define where oil samples are collected on an asset. Each asset can have multiple sampling points:
  • Engine Oil: Main crankcase
  • Hydraulic System: Reservoir, return line
  • Gearbox: Input, output, or intermediate stages
  • Turbine: Bearing oil, control oil

Creating Sampling Points

  1. Navigate to Sampling Points
  2. Click Add New Sampling Point
  3. Enter:
    • Name and Tag: Descriptive identifier
    • Parent Asset: Link to the equipment
    • Location Details: Where on the asset to sample
  4. Click Create

Sampling Routes

Sampling routes organize multiple sampling points into a scheduled collection sequence for field technicians.

Benefits of Sampling Routes

  • Efficiency: Group nearby sampling points for systematic collection
  • Consistency: Ensure all critical points are sampled on schedule
  • Tracking: Monitor route completion and missed samples
  • Planning: Assign routes to specific technicians or shifts

Creating a Sampling Route

  1. Go to Sampling Routes
  2. Click Add New Sampling Route
  3. Define route details:
    • Route Name: Descriptive identifier
    • Site: Location where samples are collected
    • Frequency: Daily, weekly, monthly, etc.
  4. Add sampling points to the route
  5. Assign technician or team
  6. Save the route

Recording Sample Results

When lab results are received:
1

Navigate to Sample History

Or use the Add Sample button from the sampling point or asset page.
2

Enter Sample Metadata

  • Serial Number: Lab-assigned sample ID
  • Date Sampled: When the sample was collected
  • Lab Name: Testing laboratory
  • Service Meter Reading: Equipment runtime hours
  • Oil in Service: Hours since last oil change
  • Filter Changed: Whether filter was replaced
  • Oil Drained: Amount of oil removed
3

Input Wear Metals

For each element, enter:
  • Element: Fe, Cu, Al, Cr, Pb, Sn, etc.
  • Value: Concentration
  • Unit: ppm (parts per million)
4

Enter Contaminants

Record contamination levels:
  • Type: Si, Na, Water, Fuel
  • Value: Concentration or percentage
  • Unit: ppm or %
5

Add Particle Counts

Input ISO code or individual counts:
  • Size Range: 4μm, 6μm, 14μm
  • Count: Particles per milliliter
6

Record Viscosity

  • Temperature: Test temperature (°C)
  • Viscosity: Value in cSt or cP
7

Set Severity

Assign severity based on lab report: Low, Medium, High, or Critical.
8

Save Sample

Click Create Sample to save the results.
Configure alarm thresholds to automatically flag samples with abnormal values.

Interpreting Results

IndicatorNormalWarningCritical
Wear MetalsStable, low levelsGradual increaseSudden spike or sustained high levels
SiliconLess than 10 ppm10-30 ppmGreater than 30 ppm
WaterLess than 500 ppm500-1000 ppmGreater than 1000 ppm
ViscosityWithin grade spec±10% deviationGreater than 20% deviation
ISO Code18/16/13 or better19/17/14 to 20/18/15Greater than 21/19/16
Always consult OEM specifications and lab recommendations. These are general guidelines only.

Best Practices

  1. Sample Consistently: Take samples at regular intervals and similar operating conditions
  2. Use Clean Bottles: Prevent external contamination during collection
  3. Label Clearly: Include asset tag, sampling point, date, and sampler name
  4. Warm Oil: Sample when oil is at operating temperature for accurate viscosity
  5. Avoid Settling: Don’t sample immediately after shutdown when particles settle
  6. Trend Analysis: Compare results to baseline and previous samples, not just limits
  7. Act on Results: Create recommendations or alarms when trends indicate action needed

Build docs developers (and LLMs) love