It’s Sunday morning, and in an empty office, the air conditioning stops working. The desks will be fine, but the temperature-controlled server room won’t be. With interruption to business, tens of thousands of dollars in equipment, and potential damage to company reputation on the line, you’re about to find out what the Technicians have known for months…the air conditioner is faulty. How can you ensure this information goes up the chain?


Risk Priority Numbers (RPNs) placed on your most critical systems will alert you to a problem before it occurs. While RPN is not new, calculating it off real data (versus prediction) is. eSAM’s RPN uses backfed reliability and KPIs to alert you to real problems before they happen.

An RPN is Severity (of a system going offline) X Detectability (of seeing a problem before it occurs) X Occurrence (how often problems are happening). If your Enterprise Asset Management (EAM) system is set up properly, your failure codes, critical systems, Technician work records, and company-defined Severity, Detectability, and Occurrence all work together to automatically feed RPNs and KPIs for you, putting critical system visibility where it needs to be.

Not sure how to get started? Let the experienced consultants at EDI help.

RPN (Risk Priority Number) – Business Process Highlight