Reliability Information Analysis Center Forums Fail Per E6 units?
 Register FAQ Members List Search Today's Posts Mark Forums Read

#1
06-29-2010, 09:14 AM
 CKO Junior Member Join Date: Jun 2010 Posts: 5
Fail Per E6 units?

Hi everyone

I do not quite understand the tabel data "Fail Per E6 units" in NPRD-95 regarding the unit of this number.

To me it seems like it has no unit at all.

Can anyone explain this number to me please, how it is calculated?

Best regards

CKO
#2
06-29-2010, 09:53 AM
 dnicholls Junior Member Join Date: Aug 2008 Posts: 26
NPRD Failure Rate Units

The failure rate units in NPRD are generally in terms of failures per million operating hours. There are failure rate entries, however, that have the letter "M" following them, in which case the units are failures per million miles.
#3
06-30-2010, 03:45 AM
 CKO Junior Member Join Date: Jun 2010 Posts: 5

Ok so does that mean that entries with an M has to be converted if i want them in hours?

Another question is, how is hours related to velocity?
#4
06-30-2010, 08:48 AM
 dnicholls Junior Member Join Date: Aug 2008 Posts: 26

Entries with an M means that we did not have any operating hours associated with the data point (i.e., no velocity information); therefore, it is not possible to convert these entries from Miles to Operating Hours.
#5
07-01-2010, 05:50 AM
 CKO Junior Member Join Date: Jun 2010 Posts: 5

Can anyone verify this(post #4) please?
#6
07-06-2010, 08:52 AM
 Norbyzuka Junior Member Join Date: Jul 2010 Location: FRANCE Posts: 22
Fail per E6 units

Failure rate with "1" E6 unity = 1*10-6/hours = 0.000001/hours
MTBF = 1 000 000 hours
M unity = failure rate / Miles.
some reliability software use "miles = hours" as ram commander without convertion.
I wish that NPRD-2010 will have E6 for all components.

Last edited by Norbyzuka; 07-06-2010 at 08:58 AM.
#7
07-11-2010, 08:28 PM
 Highkeas Member Join Date: Feb 2009 Posts: 33

Quote:
 Originally Posted by dnicholls Entries with an M means that we did not have any operating hours associated with the data point (i.e., no velocity information); therefore, it is not possible to convert these entries from Miles to Operating Hours.
Often for reliability analyses I have to make engineering estimates.
In this case if you have miles just divide operating miles by average speed (make a conservative estimate) and you obtain operating hours.

An educated guess is better than nothing.

But any system should be subjected to testing to ensure it will meeting operating environments and duration.
#8
07-11-2010, 08:30 PM
 Highkeas Member Join Date: Feb 2009 Posts: 33

Quote:
 Originally Posted by Norbyzuka ................ I wish that NPRD-2010 will have E6 for all components.
For mechanical systems it is often operating stress and other factors which drive reliability, not hours to failure.

 Thread Tools Display Modes Linear Mode

 Posting Rules 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 Rules
 Forum Jump User Control Panel Private Messages Subscriptions Who's Online Search Forums Forums Home RIAC Topics     Component Reliability         Electrical Component Reliability         Non-Electrical Component Reliability     Software Reliability     Maintainability/Supportability     Quality     Interoperability     Reliability Models     Data Analysis and Testing     Handbooks and Standards RIAC Products and Services     217Plus     Training Courses General Category     Main Forum     General RIAC WARP Forum     General Comments     Gaps in PoF Model Research     Comments on a Specific Model

All times are GMT -4. The time now is 02:16 PM.