Template:System uptime/downtime: Difference between revisions

From ReliaWiki
Jump to navigation Jump to search
(Replaced content with 'Category: For Deletion')
 
(5 intermediate revisions by one other user not shown)
Line 1: Line 1:
===System Uptime/Downtime===
[[Category: For Deletion]]
 
====Uptime,  <math>{{T}_{UP}}</math> ====
<br>
This is the average time the system was up and operating.  This is obtained by taking the sum of the uptimes for each simulation and dividing it by the number of simulations.  For this example, the uptime is 269.137.  To compute the Operational Availability,  <math>{{A}_{o}},</math>  for this system, then:
 
<br>
 
::<math>{{A}_{o}}=\frac{{{T}_{UP}}}{{{T}_{S}}}</math>
<br>
 
====CM Downtime,  <math>{{T}_{C{{M}_{Down}}}}</math> ====
This is the average time the system was down for corrective maintenance actions (CM) only.  This is obtained by taking the sum of the CM downtimes for each simulation and dividing it by the number of simulations.  For this example, this is 39.614.
To compute the Inherent Availability,  <math>{{A}_{I}},</math>  for this system over the observed time (which may or may not be steady state, depending on the length of the simulation), then:
 
<br>
 
::<math>{{A}_{I}}=\frac{{{T}_{S}}-{{T}_{C{{M}_{Down}}}}}{{{T}_{S}}}</math>
 
====Inspection Downtime ====
<br>
This is the average time the system was down due to inspections.  This is obtained by taking the sum of the inspection downtimes for each simulation and dividing it by the number of simulations.  For this example, this is zero because no inspections were defined.
 
====PM Downtime,  <math>{{T}_{P{{M}_{Down}}}}</math>====
<br>
This is the average time the system was down due to preventive maintenance (PM) actions.  This is obtained by taking the sum of the PM downtimes for each simulation and dividing it by the number of simulations.  For this example, this is zero because no PM actions were defined.
<br>
 
====Total Downtime,  <math>{{T}_{Down}}</math>====
<br>
This is the downtime due to all events.  In general, one may look at this as the sum of the above downtimes.  However, this is not always the case.  It is possible to have actions that overlap each other, depending on the options and settings for the simulation.  Furthermore, there are other events that can cause the system to go down that do not get counted in any of the above categories.  As an example, in the case of standby redundancy with a switch delay, if the settings are to reactivate the failed component after repair, the system may be down during the switch-back action.  This downtime does not fall into any of the above categories but it is counted in the total downtime.
<br>
For this example, this is identical to  <math>{{T}_{C{{M}_{Down}}}}.</math>
<br>

Latest revision as of 07:23, 1 August 2012