Talk:Mean down time

Statistics Low‑importance

	This article is within the scope of WikiProject Statistics, a collaborative effort to improve the coverage of statistics on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.StatisticsWikipedia:WikiProject StatisticsTemplate:WikiProject StatisticsStatistics articles
Low	This article has been rated as Low-importance on the importance scale.

Computer science Low‑importance

This article is within the scope of WikiProject Computer science, a collaborative effort to improve the coverage of Computer science related articles on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.Computer scienceWikipedia:WikiProject Computer scienceTemplate:WikiProject Computer scienceComputer science articles

Low

This article has been rated as Low-importance on the project's importance scale.

Things you can help WikiProject Computer science with:

Here are some tasks awaiting attention:

Article requests :
- Requested articles/Applied arts and sciences/Computer science, computing, and Internet
Cleanup :
- Computer science articles needing attention
- Computer science articles needing expert attention
Copyedit :
- Computing
Expand :
- Computer science
Infobox :
- Computer science articles without infoboxes
Maintain :
- Timeline of computing 2020–present
Photo :
- Find pictures for the biographies of computer scientists (see List of computer scientists)
- Computing articles needing images
Stubs :
- Computer science stubs
Unreferenced :
- WikiProject Computer science/Unreferenced BLPs
Project-related :
- Tag all relevant articles in Category:Computer science and sub-categories with {{WikiProject Computer science}}

I believe that MTTR (Mean Time To Repair) does include any and all time regardless of the reason including troubleshooting time, and the time spent otherwise waiting for a component to be brought back to a working state. This is contrary to the statement made in the article. --24.183.216.14 04:47, 26 December 2006 (UTC)[reply]

Hmmmm, thanks for your comment. If this is the case, what is the difference between MDT and MTTR? Also, the R in MTTR can stand for many words, it's not well defined (see MTTR article). If you have a source for saying MTTR includes all down time involved, please, make the appropriate edit. Flippin42

Believe I answered both of these MTR issues by adding components and previous edits to MTTR; I've been short on references so far though. Garykempen (talk) 16:43, 16 September 2009 (UTC)[reply]

From Jones, Logistics Support Analysis Handbook (TAB Books inc.), the time clock for MTTR starts and ends only with the corrective maintenance cycle (fault detection, isolation through checkout). MDT accounts for all including delays where spares, support personnel or tools are not immediately available. MTTR is used in calculating Ai (Inherent Availability) where MDT is used in calculating Ao (Operational Availability).

Down vs. Degraded - How is failure determined?

Can anyone make a clear distinction between downtime and degradation? For example, loss of hydraulic brake on a car is not a 100% failure - one can still downshift and/or use the parking brake. Is the car "down" or merely degraded? How can this be measured? How does one define failure? --96.244.247.130 (talk) 01:23, 4 July 2011 (UTC)[reply]