OptimalAvailability Studio™Wiki

App home / OptimalAvailability Studio™

Asset Availability Engineered

OptimalAvailability Studio™ Wiki

Reliability engineering that designs availability in, rather than chasing it after the fact. OptimalAvailability Studio™ is where the failure modes are found, the maintenance strategy is decided and the system is modelled – RCM, FMECA, reliability block diagrams, Weibull and RAM. It owns the design and proactive domains of the DIPF curve, upstream of the condition monitoring that OptimalTREND™ runs.

0%
Availability, engineered not hoped for. Reliability is set in design and preserved by precision. This is where both are decided.
Productivity+10–25%
Availability+3–7%
Maintenance cost−8–20%

Where it sits on the platform

OptimalAvailability Studio™ decides the strategy in the design and proactive domains; OptimalTREND™ executes on-condition tasks in the predictive domain; OptimalSPARES™ stocks to the criticality it produces. One reliability model, feeding the estate.

What OptimalAvailability Studio™ does

OptimalAvailability Studio™ takes an asset from function to failure mode to maintenance task and to a modelled system availability. It runs reliability-centred maintenance to SAE JA1011, FMECA to identify and rank the ways things fail, Weibull analysis to read the life out of failure history, reliability block diagrams and Monte Carlo RAM to size redundancy and predict system availability, and it packages the result into a defensible maintenance and spares strategy. It is the engineering that tells the rest of the estate what to do.

0RCM questions, to JA1011
one modelFunctions to tasks to system availability
3DIPF domains owned: design and proactive, feeding predictive

Where to start