Consultant: System Safety, R&M Engineering Editor

 

My expertise consists in working with Commercial and Military prime contractors, vendors, and sub-vendors to expedite System Safety, R&M, System & Sub-System Hardware Integration, Testing and the Produce-ability of electrical-mechanical hardware to satisfy certification of prime contract agreement to federal or civil law.

 

System Safety:

 

The purpose of this task is to legally document a System Safety Analysis (SSA) to identify safety critical areas, provide an initial assessment of hazards of the individual mechanical or electro-mechanical sub-systems or systems and to identify requisite hazard controls and follow-on actions.  This hazard analysis will systematically identify and evaluate hazards, both real and potential, for their elimination or control to an acceptable level.  They are usually developed to MIL-STD 882 B, through F, SAE ARP 4761 Series and the Code of Federal Regulations (CFR) 25:1309

 

FRACAS:

 

Failure Reporting, Analysis and Corrective Action System (FRACAS) is a developed software system that provides a framework for controlling corrective action processes.  It is used in an industrial environment to collect, record and analyze system failures.

 

My Engineering Expertise:

 

System Safety, Systems Integration, Reliability ILS / RAM-D, R&M, Manufacturing, Produce-ability and Logistics for Aircraft, Military Hardware and Commercial Systems.

Also, Analytical background in FMEA, FMECA, FRACAS, Fault Trees and the implementation and mitigation of field test incident or failure reports (TIRs / FIRs) by DOD CARs.

 

Computer Familiarization:

 

Software tools MS Office Programs, RELEX, Remedy, ITEM, CAFTA, PRISM, FaulTrease, Fault Tree Pro+, FRACAS, ADOBE 7, through 10, MS Access Programs, MS Visio, Company Proprietary Software, and RFFlow.  Documents and Standards: Mil- Stds-1629, 217, 338, 38510, 472, 810, 882, 883, The Code of Federal Regulations, SAE J-1739, and SAE ARP 4761.

 

Reliability Predictions:

 

  1. Mean Time between Failures (MTBF) expressed in hours or miles for commercial and military applications.

  2. Failure Rate is usually expressed in Failures per 106 or 109 hours.

  3. For example, a system with a predicted MTBF of 1000 hours, on average the system experiences one failure in 1000 hours of operation or a Failure Rate of 1000 per 106 hours an acceptable level.  It is usually developed to Mil-Std 882-B, through  F, SAE ARP 4761 Series and CFR 25:1309

  4. Failure rate, Mean Time Between Failure (MTBF), Mean Time Between Repair or Replace (MTBR) cannot be calculated without proper testing by a qualified environmental test engineer.
  5. If electro-mechanical hardware is properly tested there are ways to calculate hardware failure rate.

  6. To calculate Failure Rate you must have Test, Use, or Historical Service Data.

 

Estimated_Failure_Rate_Chart

 

Or 799.8 failures for every million hours of operation.

To develop Failure Rate, MTBF, MTBR, or any other reliability data, first you must have test or use data.

 

 

Contact Me: 408-910-8604

 

Email:  jim@jimgodby.com

 

www.jimgodby.com