Hardy–Littlewood inequality: Difference between revisions
small grammar edit |
|||
Line 1: | Line 1: | ||
'''Operational Availability''' is a management concept that evaluates the following.<ref>{{cite web|url=http://doni.daps.dla.mil/OPNAV.aspx|title=Opnav Instruction 4790.7: Maintenance Policy for United States Navy Ships|publisher=US Navy Operations}}</ref> | |||
* Diagnostic down time | |||
* Criticality | |||
* Fault isolation down time | |||
* Logistics delay down time | |||
* Corrective maintenance down time | |||
Any failed item that is not corrected will induce operational failure. <math>A_o</math> is used to evaluate that risk. Operational failure is unacceptable in any situation where the following can occur. | |||
* Capitol equipment loss | |||
* Injury or loss of life | |||
* Sustained failure to accomplish mission | |||
==History== | |||
Aircraft systems, ship systems, missile systems, and space systems have a large number of failure modes that must be addressed with limited resources. | |||
Formal reliability modeling during development is required to prioritize resource allocation before operation begins. Estimated failure rates and logistics delay are used to identify the number of forward positioned spare parts required to avoid excessive down time. This is also used to justify the expense associated with redundancy. | |||
Formal availability measurement is used during operation to prioritize management decisions involving upgrade resource allocation, manpower allocation, and spare parts planning. | |||
== Principle == | |||
Operational availability is used to evaluate the following performance characteristic. | |||
:<math> A_o = 0.9 \approx 877 \ hours \ down \ time \ per \ year</math> | |||
:<math> A_o = 0.99 \approx 87 \ hours \ down \ time \ per \ year</math> | |||
:<math> A_o = 0.999 \approx 8 \ hours \ down \ time \ per \ year</math> | |||
:<math> A_o = 0.9999 \approx 52 \ minutes \ down \ time \ per \ year</math> | |||
:<math> A_o = 0.99999 \approx 5 \ minutes \ down \ time \ per \ year</math> | |||
The following data is collected for maintenance actions while in operation to prioritize corrective funding. | |||
* Diagnostic down time is required to identify the amount of time spent perform maintenance when [[fault reporting]] does not support [[condition-based maintenance]]. | |||
* Criticality identifies level of risk associated with loss of mission, injury or loss of life, and capitol equipment. | |||
* Fault isolation down time is required to identify the amount of time spent locating a failure. | |||
* Logistics delay down time is required to identify the amount of time required to obtain replacement parts or software. | |||
* Corrective maintenance down time is required to identify the amount of time required to install and reconfigure replacement parts and software. | |||
This data is applied to the [[reliability block diagram]] to evaluate individual availability reduction contributions using the following formulas. | |||
:<math>A_{o}^{D} = \left( \frac{ Total \ Time }{Total \ Time + Diagnostic \ Down \ Time } \right) </math> | |||
:<math>A_{o}^{FI} = \left( \frac{ Total \ Time }{Total \ Time + Fault \ Isolation \ Down \ Time } \right) </math> | |||
:<math>A_{o}^{L} = \left( \frac{ Total \ Time }{Total \ Time + Logistics \ Down \ Time } \right) </math> | |||
:<math>A_{o}^{C} = \left( \frac{ Total \ Time }{Total \ Time + Corrective \ Down \ Time } \right) </math> | |||
Redundant items do not contribute to availability reduction unless all of the redundant components fail simultaneously. | |||
Operational Availability is the overall availability considering each of these contributions. | |||
:<math>A_o = A_{o}^{D} \times A_{o}^{FI} \times A_{o}^{L} \times A_{o}^{C}</math> | |||
==See also== | |||
* [[Active redundancy]] | |||
* Operational availability | |||
* [[Reliability block diagram]] | |||
==External links== | |||
{{Empty section|date=March 2013}} | |||
==References== | |||
{{Reflist}} | |||
[[Category:Maintenance]] | |||
[[Category:Engineering concepts]] | |||
[[Category:Reliability engineering]] | |||
[[Category:Safety]] | |||
[[Category:Fault tolerance]] | |||
[[Category:Fault-tolerant computer systems]] |
Revision as of 20:53, 16 November 2013
Operational Availability is a management concept that evaluates the following.[1]
- Diagnostic down time
- Criticality
- Fault isolation down time
- Logistics delay down time
- Corrective maintenance down time
Any failed item that is not corrected will induce operational failure. is used to evaluate that risk. Operational failure is unacceptable in any situation where the following can occur.
- Capitol equipment loss
- Injury or loss of life
- Sustained failure to accomplish mission
History
Aircraft systems, ship systems, missile systems, and space systems have a large number of failure modes that must be addressed with limited resources.
Formal reliability modeling during development is required to prioritize resource allocation before operation begins. Estimated failure rates and logistics delay are used to identify the number of forward positioned spare parts required to avoid excessive down time. This is also used to justify the expense associated with redundancy.
Formal availability measurement is used during operation to prioritize management decisions involving upgrade resource allocation, manpower allocation, and spare parts planning.
Principle
Operational availability is used to evaluate the following performance characteristic.
The following data is collected for maintenance actions while in operation to prioritize corrective funding.
- Diagnostic down time is required to identify the amount of time spent perform maintenance when fault reporting does not support condition-based maintenance.
- Criticality identifies level of risk associated with loss of mission, injury or loss of life, and capitol equipment.
- Fault isolation down time is required to identify the amount of time spent locating a failure.
- Logistics delay down time is required to identify the amount of time required to obtain replacement parts or software.
- Corrective maintenance down time is required to identify the amount of time required to install and reconfigure replacement parts and software.
This data is applied to the reliability block diagram to evaluate individual availability reduction contributions using the following formulas.
Redundant items do not contribute to availability reduction unless all of the redundant components fail simultaneously.
Operational Availability is the overall availability considering each of these contributions.
See also
- Active redundancy
- Operational availability
- Reliability block diagram
External links
References
43 year old Petroleum Engineer Harry from Deep River, usually spends time with hobbies and interests like renting movies, property developers in singapore new condominium and vehicle racing. Constantly enjoys going to destinations like Camino Real de Tierra Adentro.