Talk:Reliability, availability and serviceability

From Wikipedia, the free encyclopedia
Jump to navigation Jump to search
WikiProject Computing (Rated Start-class, Mid-importance)
WikiProject iconThis article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology 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.
Start-Class article Start  This article has been rated as Start-Class on the project's quality scale.
 Mid  This article has been rated as Mid-importance on the project's importance scale.
 

I'm not sure if this is correct to say: "...availability measures how often it is available for use, even though it may not be functioning correctly..." or "...so have ideal availability, but may be unreliable, with frequent data corruption..." AFAIK, "availability" is supposed as the "probability of operating as intended". When also we say uptime/total_time, by "uptime" we mean the time which system is running correctly. not just running. — Preceding unsigned comment added by 109.69.228.213 (talk) 10:43, 15 January 2014 (UTC)

if u increase the availabilty of a system then i don't think that one can say it as unreliable. if u are able to provide a bounded down time then we can be sure on the availbilty of the system for providing the services, which in turn is your reliability. isn't it?

You need to be careful about distinguishing between reliability, which is related to the rate at which a system operates without failure, and availability, which is the rate at which a system operates irrespective of whether failures occur or not. If you do not have resources such as manpower or spare parts to correct the system when it goes down, or if the repair time is lengthy, then downtime can quickly add up, making the system unavailable, but not impacting reliability at all. —Preceding unsigned comment added by 70.251.0.28 (talk) 00:40, 28 December 2010 (UTC)

Extended Floating Point Precision and Decimal Floating Point as RAS features?[edit]

I don't think 128-bit floating point or decimal floating point belong in this article. Nice features, but disjoint to the topic of RAS. If nobody objects strenuously I intend to remove that line item. jsavit

Integrated Logistic Support[edit]

This article is strikingly similar to the Integrated logistics support (ILS) article. Perhaps there is a way that these articles can be related, without developing two separate articles? For now, I'm going to add some see also links, but I'm not sure this is the best approach. FWIW, ILS seems to be a much more comprehensive approach, and is more logistics focused. However, I would venture to say that that is mostly due to the complexity (in physical terms, not logical terms)) of the systems involved. 70.251.0.28 (talk) 00:54, 28 December 2010 (UTC)

Not limited to hardware[edit]

IBM coined the term RAS to refer to software as much as or more than to hardawre. Shmuel (Seymour J.) Metz Username:Chatul (talk) 21:03, 10 July 2013 (UTC)