Reliability Simplified Reliability Simplified
The reliability ecosystem

The RS
Platform.

Our consulting builds your program; the RS Platform keeps it alive, a single ecosystem where every site has the tools to run reliability long after the engagement ends.

How the ecosystem fits together

A layer above your CMMS.

Criticality sits in a spreadsheet. Failure analysis sits in a document somebody wrote after a bad week. Strategy sits inside the CMMS, and the reasoning behind it sits in someone’s head until they leave. The platform is where that reasoning gets decided and remembered.

The layer above
RS Platform
Strategy decided, recorded and kept auditable. Your CMMS stays the execution engine.
↻ stronger every pass
01
Capture
Assets, BOM, failures
02
Prioritize
Criticality, risk
03
Analyze
FMEA, RCA
04
Decide
Strategy on record
05
Execute
PMs in the CMMS
06
Verify
Did it hold?
07
Standardize
Into the library

Most programs reset when people move on. A connected one gets sharper with age instead of fading.

WHERE ARE WE GOING

The platform exists to hold a reliability program together — the register, the criticality, the strategy and the reasoning behind it — so the work survives turnover and gets sharper each year. It is built in horizons.

RS Platform — Asset register Sample record
Functional location Equipment type Criticality
PLT-01-PU-1420A M_PUM_CENF · centrifugal pump A
PLT-01-PU-1420B M_PUM_CENF · centrifugal pump B
PLT-01-HX-2210 M_HEX_SHTU · shell & tube B
PLT-02-FN-3040 M_FAN_CENF · induced draft fan C
PLT-02-CV-3115 M_VAL_CTRL · control valve A
1,284 locations · BOM attached to 1,190
The roadmap Direction, not a release calendar
01 You are here
Horizon 01 · Built and in use on client programs

The record of record

One structured home for assets, criticality and strategy, built on library content instead of a blank database.

  • Asset register & BOM
  • Criticality assessment
  • Lubrication routes
  • Coverage analytics
02 You are here
Horizon 02 · In development

Strategy that builds itself

Failure modes, PM content and root-cause findings connected, so a fix in one place updates the strategy everywhere.

  • FMEA / RCM engine
  • PM builder & optimization
  • RCA engine
  • Risk register & mitigation
03 You are here
Horizon 03 · Direction we are building toward

A program that learns

Operational and condition data flowing in, patterns surfaced automatically, intervals adjusted on evidence rather than habit.

  • Operational data connector
  • Condition-based triggers
  • RS Insight pattern detection
  • Fleet-wide benchmarking
Inside the app

The master reliability library.

Every equipment type sits in a Category → Class → Type hierarchy, and every type opens into its failure modes, causes and controls.

RS Platform — Master Reliability Library
RS Platform Master Reliability Library: the Centrifugal Pump profile with its failure modes, causes and controls
Hierarchy
Category → Class → Type. 348 types across 61 object classes, every one built to the same depth.
Failure modes
Each type opens into its components, failure modes and effects, with prevent and detect controls named.
Controls
Every cause carries its own prevention and detection task, so the strategy is traceable to a reason.
Hover a marker to read the screen

Reliability data — failure rate, MTBF, MTTR — is never estimated. It is populated from licensed reliability data sources or your own site failure history, and left blank until it is real.

Example output

A real job plan.

This is what a craftsman receives: one controlled format, with limits and acceptance criteria printed on the page.

PM Job Plan PM-M_PUM_CENF-Q01 · Rev 3
Asset
P-1420A · Feed charge pump
Equipment class
M_PUM_CENF
Criticality
A — high
Frequency
Quarterly (91 days)
Craft
Millwright + lube tech
Estimated duration
2.5 h · 2 persons
Condition
Running route, no shutdown
Standard
Safety
  • ·LOTO required to remove coupling guard
  • ·Hearing protection, FR coverall, face shield
  • ·Hot surface — housing may exceed 150 °F
  • ·Confirm seal flush isolated before opening pot
Tools
  • ·Vibration data collector, 2 accelerometers
  • ·IR thermometer
  • ·Torque wrench, 0–300 ft-lb
  • ·Dial indicator set, feeler gauges
  • ·Oil sample bottle, labeled
Parts kitted
  • ·Seal cartridge — CRITICAL spare
  • ·Bearing set, drive + non-drive — CRITICAL
  • ·Coupling element, elastomer
  • ·VG 68 turbine oil, 1 qt
  • ·Gasket kit, casing drain
# Step Acceptance criteria Result
01
Record operating point
Suction and discharge pressure, flow, motor amps.
Within ±10% of design curve point
02
Vibration survey
Overall velocity, drive and non-drive bearing, H/V/A.
≤ 0.14 in/s RMS · alarm 0.30
03
Bearing temperature
IR reading at both bearing housings.
≤ 180 °F · ΔT ≤ 40 °F over ambient
04
Mechanical seal check
Inspect seal support system and leakage path.
No visible leakage · pot level between marks
05
Lube oil condition
Level, colour, water contamination; pull sample.
Level at sight-glass centre ±1/8 in · no cloudiness
06
Coupling inspection
Guard off, inspect elastomer element and fasteners.
No cracking · backlash ≤ 1/16 in
07
Baseplate and hold-downs
Check grout condition and hold-down bolt torque.
250 ft-lb · no cracked grout or soft foot
Failure modes addressed: seal face failure · bearing wear-out · impeller erosion · misalignment Pass / Fail per step · defects raise a follow-up work order

Quantitative limits, not “check condition.” Any craft running this plan on this pump gets the same answer, and the result is a data point the program can learn from.

Next step

See it on your assets.

We will open the library against the equipment classes you actually run, and show you what would load into your CMMS.