Talk:Availability

WikiProject Systems
This article is within the scope of WikiProject Systems, which collaborates on articles related to systems and systems science.
???  This article has not yet received a rating on the project's quality scale.
???  This article has not yet received a rating on the project's importance scale.
WikiProject Engineering
This article is within the scope of WikiProject Engineering, a collaborative effort to improve the coverage of engineering 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.
???  This article has not yet received a rating on the project's quality scale.
???  This article has not yet received a rating on the project's importance scale.

Definition

Some content has been moved to Forty-nine charismatic virtues. Peter Manchester 13:15, 25 Nov 2003 (UTC)

I'm trying to find a definition of Availability that can be sensibly used in a legal document relating to a web site hosting service. The current definition on Wikipedia doen't seem to fulfil this requirement. I'm sure there is a service-related definition of Availability in ITIL somewhere, but I haven't yet found it. Can anybody help with this? penis

heyyy what up —Preceding unsigned comment added by 174.88.195.11 (talk) 23:12, 27 January 2010 (UTC)

Dubious definition

The article states the following:

Limiting (or steady-state) availability is represented by[citation needed]

${\displaystyle A=\lim _{t\rightarrow \infty }A(t).}$

Limiting average availability is also defined on an interval ${\displaystyle (0,c]}$ as,

${\displaystyle A_{\infty }=\lim _{c\rightarrow \infty }A_{c}=\lim _{c\rightarrow \infty }{\frac {1}{c}}\int _{0}^{c}A(t)\,dt,\quad c>0.}$

I don't see how this can be accurate, however. The steady-state availability definition as stated doesn't look like it would converge. This appears to be more of an "instantaneous" availability that is evaluated as t gets large, which seems like a dubious procedure to me. I suspect a definition like:

${\displaystyle A=\lim _{c\rightarrow \infty }A_{c}.}$

is probably more accurate for steady-state (limiting) availability. 70.250.239.119 (talk) 02:22, 23 August 2010 (UTC)

Inherent and Operational Availability

I read earlier today on Talk:Mean down time:

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).

This is good info, I'd like to include it, but I'm not sure what the best way to do that is. At a minimum, I believe the article needs to mention inherent availability and operational availability. 70.250.239.119 (talk) 02:30, 23 August 2010 (UTC)

Mission Capable Rate

The military's notion of mission capable rate is a special case of system availability, so I've linked a number of pages that mention this term to this page. We should probably redirect mission capable rate to this page also. 70.250.190.30 (talk) 00:31, 19 September 2010 (UTC)

Sounds swell. I've created the redirect. bahamut0013wordsdeeds 02:53, 19 September 2010 (UTC)

Available isn't available ?

The current definition seems MIL-STD based, should there be mention of alternative views?

For example in Semiconductor Equipment and Materials International SEMI-E10 specification or Reliability, Availability, and Maintainability, see http://www.semi.org/en/Standards/CTR_031244 -- see paper on Measuring Supercomputer RAS. I've also seen Availability and the different ways to calculate it

The alternative seems looking from a viewpoint of post-fact reporting on actual production measurements rather than a calculated KPP. I'm also thinking the military KPP usage has availability measured against time supposed to be up -- so 'scheduled downtime' does not count - and the SEMI usage has any downtime counted as downtime, and then focuses on how much uptime went to engineering tasks, idle time, and how much of actual runtime is in restart and rework time.

Anyone have viewpoint on including other measures in the article ? Markbassett (talk) 20:56, 30 July 2015 (UTC)

When you have finished reviewing my changes, please set the checked parameter below to true or failed to let others know (documentation at {{Sourcecheck}}).