The Elsmar Cove Forum and Site Map The Elsmar Cove Wiki More Free Files The Elsmar Cove Forums Discussion Thread Index Post Attachments Listing Failure Modes Services and Solutions to Problems Elsmar cove Forums Main Page Elsmar Cove Home Page

Go Back   The Elsmar Cove Forum > Manufacturing, Service, and Business Systems Processes > Reliability Analysis - Predictions, Testing and Standards


Language / Translation
New Threads Feeds
RSS Feed       RSS Feed
Follow Elsmar
Facebook Link    Facebook Link    Twitter Feed
Monitor the Forum
Monitor New Forum Posts
Popular Recent Topics
Tag Cloud
Sponsor Links











$ Contributor Forum Access
Courtesy Quick Links

Links that Elsmar Cove visitors will find useful in your quest for knowledge:


Howard's International Quality Services

Atul's Symphony Technologies

Dave Scott's Scott Quality Solutions

Praxiom Research Group


NIST's Engineering Statistics Handbook

IRCA - International Register of Certified Auditors

SAE - Society of Automotive Engineers

Quality Digest Portal

IEST - Institute of Environmental Sciences and Technology

ASQ - American Society for Quality


All the Important Standards and Related Web Sites in the World

Tags
mean time to repair, mil-hdbk-472, mttr (mean time to repair)
Reply
 
Thread Tools Search this Thread Rate Thread Content Display Modes
  #1  
Old 13th April 2001, 08:39 AM
Michael Busha
Unregistered Guest

 
Posts: n/a
Let Me Help You Calculating MTTR - Mean Time To Repair - MIL-HDBK-472, Procedure V, Method A.

I put this in the Statistics forum first but maybe it's better put here. Does anyone know a quick and dirty way to calculate MTTR? We have two kinds of solenoid valves, one is ISO rated, the other is not. I want to prove that the MTTR of the ISO rated valve is not significantly different from that of the non ISO rated valve. We have the capability of actually disassembling and reassembling both valves to get an accurate measure. Is there a formula I can plug the values into? Thanks for any help. The results of this analysis could save my company $40,000.
Reply With Quote

Sponsored Links
  #2  
Old 17th April 2001, 11:19 AM
Dan De Yarman
Unregistered Guest

 
Posts: n/a
Question

Have you contacted the manufacturer(s) to see what they recommend? If you are a QS-9000 TE Supplement registered company you should be requiring your suppliers to follow Section I of the TE Supplement requirements manual. That includes MTTR, MTBF, and whatever else you specify on your purchase order.

Keep in mind that MTTR and MTBF assume that the peson(s) reairing the item (the valve in your case) has both the knowledge and the tools to perfom the repair unless your Customer tells you otherwise. In terms of a "nice and easy" formula, I don't know of one. Sorry I couldn't be of anymore help.

Anyone else know of a way?

Dan
Reply With Quote
Sponsored Links

  #3  
Old 14th March 2004, 05:08 AM
Marc's Avatar
Marc Marc is offline
Your Elsmar Cove Host

Registration Date: Jan 1996
Location: West Chester, Ohio - USA
Age: 60
 
Posts: 17,879
Thanks Given to Others: 3,101
Thanked 2,387 Times in 1,535 Posts
Blog Entries: 4
Karma Power: 753
Karma: 16814
Marc is appreciated, and has over 1700 Karma points.
Marc is appreciated, and has over 1700 Karma points.Marc is appreciated, and has over 1700 Karma points.Marc is appreciated, and has over 1700 Karma points.Marc is appreciated, and has over 1700 Karma points.Marc is appreciated, and has over 1700 Karma points.Marc is appreciated, and has over 1700 Karma points.Marc is appreciated, and has over 1700 Karma points.Marc is appreciated, and has over 1700 Karma points.Marc is appreciated, and has over 1700 Karma points.Marc is appreciated, and has over 1700 Karma points.Marc is appreciated, and has over 1700 Karma points.Marc is appreciated, and has over 1700 Karma points.
Send a message via AIM to Marc Send a message via Skype™ to Marc
Default

mean time to repair (MTTR): The total corrective maintenance time divided by the total number of corrective maintenance actions during a given period of time.

corrective maintenance: 1. Maintenance actions carried out to restore a defective item to a specified condition. 2. Tests, measurements, and adjustments made to remove or correct a fault.

Also see MIL-HDBK-472, Procedure V, Method A.

http://www.eventhelix.com/RealtimeMa...ailability.htm

Maintainability and Availability

Maintainability Standards & Handbooks

MIL-STD-470B Maintainability Program Requirements for Systems and Equipment
This document includes application requirements, tailorable maintainability program tasks, and an appendix with an application matrix and guidance and rationale for task selection. The topics covered are program surveillance and control, design and analysis, modeling, allocations, predictions, failure mode and effects analysis, and maintainability design criteria. Each task item includes a purpose, task description, and details to be specified. Software maintainability is not covered by this document.

MIL-STD-471A Maintainability Verification/Demonstration/Evaluation
This document provides procedures and test methods for verification, demonstration, and evaluation of qualitative and quantitative maintainability requirements. It also provides for qualitative assessment of various integrated logistic support factors related to and impacting the achievement of maintainability parameters and item downtime, e.g. technical manuals, personnel, tools and test equipment, maintenance concepts and provisioning.

MIL-HDBK-472 Maintainability Prediction
This document is to familiarize project managers and design engineers with maintainability prediction procedures. It provides the analytic foundation and application details of five prediction methods. Each procedure details applicability, point of application, basic parameters of measure, information required correlation, and cautionary notes. The highlights of each maintainability prediction procedure are presented in a clear and intelligible manner and include useful supplementary information applicable to specific procedures. Maintainability Prediction Procedures I and III are applicable solely to electronic systems and equipments. Procedures II and IV can be used for all systems and equipments. In applying Procedure II to non-electronic equipments the appropriate task times must be estimated. Procedure V can be used to predict maintainability parameters of avionics, ground and shipboard electronics at the organizational, intermediate and depot levels of maintenance.

DOD-HDBK-791 Maintainability Design Techniques
This handbook supplies information on incorporating maintainability into Army materiel design. It defines maintainability and discusses its importance, quantitative measurement, and incorporation into the design process. Other subjects discussed in detail cover simplification, standardization and interchangeability, accessibility, modularization, identification and labeling, testability and diagnostic techniques, preventive maintenance, human factors, and environmental factors as they relate to maintainability.

MIL-STD-1591 On Aircraft, Fault Diagnosis, Subsystems, Analysis/Synthesis of
This document establishes uniform criteria for conducting trade studies to determine the optimal design for an on-aircraft fault diagnosis/isolation system. This document is applicable where a selection can be made between such alternatives as central computer controlled on-board centrally polled built-in test equipment (BITE), decentralized BITE, detached Aerospace Ground Equipment (AGE), etc., or combinations of the preceding. The fault diagnosis/isolation systems of interest are those used to diagnose/isolate faults at the flight line (organizational) level of maintenance. This document also provides a cost model and a maintainability labor power model.

MIL-STD-1843 Reliability-Centered Maintenance for Aircraft, Engines and Equipment
This document, which is based on the Airline/Manufacturer Maintenance Program Planning Document MSG-3, outlines the procedures for developing preventive maintenance requirements through the use of Reliability-Centered Maintenance Analysis (RCMA) for Air Force aircraft and engine systems, aircraft and engine structures and equipment, including peculiar and common Support Equipment (SE) Communications and Electronics (C-E) equipment, vehicles, weapons and other similar equipment items.

MIL-STD-2084 Maintainability of Avionic & Electronic Systems and Equipment
This document covers the common maintainability design requirements to be used in military specifications for avionic and electronic systems and equipment.

MIL-STD-2165A Testability Programs for Electronic Systems & Equipment
This document is intended to prescribe a systematic approach for establishing and conducting a testability program. It describes a uniform approach to testability program planning, establishment of diagnostic concepts and testability (including BIT) requirements, testability and test design and assessment, and requirements for conducting testability program reviews. Relevant tasks in this document are to be applied during the conceptual phase, demonstration and validation phases, full-scale development phase and production phase of the acquisition process.

DOD-STD-1701 Hardware Diagnostic Test System Requirements
This document establishes the general procedures, terms and conditions governing the preparation and completion of a hardware diagnostic test system.

MIL-STD-2173 Reliability-Centered Maintenance Requirements for Naval Aircraft, Weapons Systems and Support Equipment
This document is used to provide procedures for a Reliability-Centered Maintenance analysis for naval aircraft, weapons systems, and support equipment. This document is used during development of new systems and equipment, and by analysts and auditors within the Naval Air Systems Command for determining preventive maintenance requirements and developing age exploration requirements. The document can also be used to update the initial reliability-centered maintenance analysis and analyze newly discovered failure modes.

MIL-STD-001591A Subsystem Analysis/Synthesis of Command, Control & Communication (C3) System Component Fault Diagnosis
This document establishes uniform criteria for conducting trade studies to determine the optimal design for command, control and communication system and component fault diagnosis/isolation subsystems, These types of systems are referred to as Fault Identification & Test Subsystems (FITS). FITS include the hardware and/or software necessary for the detection and isolation of failures.

Many systems are repairable; when the system fails — whether it is an automobile, a dishwasher, production equipment, etc. — it is repaired. Maintainability is a measure of the difficulty to repair the system. More specifically, maintainability is:

The measure of the ability of a system to be retained in, or restored to, a specified condition when maintenance is performed by personnel having specified skill levels, using prescribed procedures and resources, at each prescribed level of maintenance and repair.

Military Handbook 472 (MIL-HDBK-472) defines six components of maintainability, which are discussed below.

1. Elemental Activities are simple maintenance actions of short duration and relatively small variance that do not vary appreciably from one system to another. An example of an elemental activity is the opening and shutting of a door.
2. Malfunction Active Repair Time consists of:
1. Preparation time
2. Malfunction verification time
3. Fault location time
4. Part procurement time
5. Repair time
6. Final malfunction test time Items a–f above are composed of elemental activities.
3. Malfunction Repair Time consists of:
1. Malfunction active repair time
2. Malfunction administrative time
4. System Repair Time is the product of malfunction repair time and the number of malfunctions.
5. System Downtime includes:
1. System logistic time
2. System repair time
3. System final test time
6. Total System Downtime is a combination of the distributions of
1. Initial delay
2. System downtime

MIL-HDBK-472 provides a procedure for predicting maintainability based on the structure described above. The philosophy of the procedure is based on the principles of synthesis and transferability. The synthesis principle involves a buildup of downtimes, step-by-step, progressing from the distribution of downtimes of elemental activities through various stages culminating finally with the distribution of system downtime. The transferability principle embodies the concept that data applicable to one type of system can be applied to similar systems, under like conditions of use and environment, to predict system maintainability.

Other useful maintainability references are Military Standard 470, which describes a maintainability program for systems and equipment, and Military Standard 471, which provides procedures for maintainability verification, demonstration, and evaluation.

Availability is a measure of the readiness of a system. More specifically, availability is:

A measure of the degree to which a system is in an operable and comitable state at the start of a mission when the mission is called for at a random time.

There are three categories of availability.

1. Inherent Availability is the ideal state for analyzing availability. It is a function only of the mean time to fail, MTBF, and the mean time to repair, MTTR; preventive maintenance is not considered. Inherent availability is defined as Ai = MTBF/(MTBF + MTTR)

2. Achieved Availability includes preventive maintenance as well as corrective maintenance. It is a function of the mean time between maintenance actions, MTMA, and the mean maintenance time, MMT. Achieved availability is defined as Aa = MTMA/(MTMA + MMT)

3. Operational Availability includes preventive maintenance, corrective maintenance, and delay time before maintenance begins, such as waiting for parts or personnel. It is a function of the mean time between maintenance actions and the mean down time, MDT, and is defined as Ao = MTMA/(MTMA + MDT)

It is important to note that the type of availability being described is often not distinguished. Many authors simply refer to "availability," MTTR may be the equivalent of MMT or MDT, and MTBF may be the equivalent MTMA.
Attached Files: 1. Scan for viruses before using, 2. Please report any 'bad' files by Reporting the post it is in, 3. Use at your Own Risk.
File Type: pdf calculating_mtbf.pdf (107.2 KB, 687 views)
File Type: doc STD132 - Reliability and Maintainability Predictions for FX-30.doc (100.5 KB, 390 views)
__________________
A Search is a terrible thing to waste!
One Test is Worth 1000 Expert Opinions - The plural of anecdote is not data - Correlation does not imply Causation
We can't solve problems by using the same kind of thinking we used when we created them. - Unknown
Reply With Quote
Reply

Lower Navigation Bar
Go Back   The Elsmar Cove Forum > Manufacturing, Service, and Business Systems Processes > Reliability Analysis - Predictions, Testing and Standards

Bookmarks

Tags
mean time to repair, mil-hdbk-472, mttr (mean time to repair)


Visitors Currently Viewing this Thread: 1 (0 Registered Visitors and 1 Unregistered Guests)
 
Thread Tools Search this Thread
Search this Thread:

Advanced Forum Search
Display Modes Rate Thread Content
Rate Thread Content:

Forum Posting Settings
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Discussion Threads
Discussion Thread Title Thread Starter Forum Replies Last Post or Poll Vote
The status of MIL-HDBK-217G Allan66 Reliability Analysis - Predictions, Testing and Standards 6 12th August 2010 07:11 AM
Mean time to failure (MTTF) & Mean time to recover/repair (MTTR) blitz Reliability Analysis - Predictions, Testing and Standards 2 9th July 2009 06:14 AM
MIL-HDBK 57B - Listing of Fastener Manufacturers' Identification Symbols hoogie Various Other Specifications, Standards, and related Requirements 3 15th December 2006 06:07 AM
Where can I get a readable copy of MIL-HDBK-472 and Notice 1? sanford.walker Documentation Control Systems, Procedures, Forms and Templates 1 10th April 2006 05:36 PM
MTTR - Quick and dirty way to calculate Mean Time To Repair - Solenoid valves Michael Busha SPC Monitoring and Statistical Analysis Techniques 6 17th April 2001 09:25 AM



The time now is 02:51 AM. All times are GMT -4.
The time zone can be changed in your UserCP --> Options.



   

All Y'All Come Back Now, Y' Hear?

Made With A Mac! FreeBSD OS Powered by Apache!
Using php4 Forums provided and maintained by Marc Smith Database by MySQL

FAIR USE and CORRECTNESS NOTICE: This site contains copyrighted material the use of which has not always been specifically authorized by the copyright owner. We are making such material available in our efforts to advance understanding of environmental, political, human rights, economic, democracy, scientific, and social justice issues, etc. We believe herein constitutes a 'fair use' of any such copyrighted material as provided for in section 107 of the US Copyright Law. In accordance with Title 17 U.S.C. Section 107, the material on this site is distributed without profit to those who have expressed a prior interest in receiving the included information for research and educational purposes. For more information go to: http://www.law.cornell.edu/uscode/17/ If you wish to use copyrighted material from this site for purposes of your own that go beyond 'fair use', you must obtain permission from the copyright owner. In addition, I do not guarantee the correctness of the content. The risk of using content from the Elsmar Cove web site and forums remains with the user/visitor.

Responsibility Statement: Each person is responsible for anything they post in the Elsmar Cove forum. Neither I, Marc Timothy Smith, nor any of the forum Moderators, are responsible for the content of posts people make. Liability for post content resides with the poster as does interpretation and/or acceptance and/or use of advice by the reader.

Complaints: If you have a complaint with a post in a forum discussion thread, including Content in general, fighting, flaming, copyright infringement, defamation and/or 'slander', please use the 'Report This Post Report This Post Button button which appears at the top of every post in every thread.

Site courtesy of:
Marc Timothy Smith - Cayman Business Systems, 8466 Lesourdsville-West Chester Road, West Chester, Ohio 45069-1929 - USA
(513) 341-6272

If you are having problems Registering, Activating your Registration, or other problems, you can phone me in the US. I'm not here 24/7/365, but if I'm here I'll try to help.
The Elsmar Cove Web Site is *CopyFree*
no new posts