Jump to content

Design for availability

From Wikipedia, the free encyclopedia
This is an old revision of this page, as edited by Repsieximo (talk | contribs) at 01:10, 13 August 2012 (See also). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Design for Availability is the design of a system considering availability or readiness as the major part of goal specification.

The design parameters might include maintenance and inventory management, operation logistics, Prognostic Health Management (PHM) and reliability of system into the design process.[1] The general purpose of this type of systems is in outcome-based contracts. Availability is a major factor of operational effectiveness along with performance of the system. Minimum required availability of complex system is a key factor of many distributed and repairable systems like ATM network or Airliner.

In Availability-based Contracts[2] instead of parts, supplier is paid for a guaranteed level of services and performance a and system capability, like availability-based tarrif for electric power.[3] The supplier often has to guarantee the availability and preparedness of system at lesser costs by considering the logistics as part of design. The contractor will also have more control over logistics and supply chain of system.

Recent interest in availability contracts that specify a required availability has created an interest in deriving system design and support parameters directly from an availability-based contracts. But, a point to point allocation from parameter of operation and support to meet availability requirement in the performance space, given the required availability distribution is a direct way of design which must be followed by a sensitivity analysis and robustness of parameters. However, determining design parameters from an availability requirement is a stochastic reverse design problem.

Evaluating an availability requirement is a challenge for manufacturers and supporters of systems because determining how to deliver a specific availability is not trivial. The required availability can be defined over the instance of system or over the fleet. It can be defined over different time windows or in different geographical boxes. However availability optimization approaches provide solutions only at selected points in time (not all times), using mean time to failure (or fixed rate demand) and mean time to repair as deterministic values as part of convex optimization.

Availability engineering in network world is generally toward reducing unplanned downtime or planned downtime by providing redundancy or fast switching systems. This area of design is the subject of different discipline with different approach. The main difference between network industry and manufacturing availability is that former is more targeting toward decreasing downtime where as in reliability world it might be seen as using higher reliability part in a cost effective manner.

See also

References

  1. ^ "CALCE e-News March 2012". Calce.umd.edu. Retrieved 2012-08-02.
  2. ^ "UK's Eurofighters Fly To Availability-Based Contracting". Defenseindustrydaily.com. 2011-12-06. Retrieved 2012-08-02.
  3. ^ http://www.fta.dot.gov/documents/Thursday_PM_-_Ronald_Humphrey_-_CRBS-DOT_Round_Table_July_Briefing_Final_RGH.pdf