MOD DEF STAN 00-49 Issue 3 Defence Standard:- Final .
DRAFTUnclassifiedMODDEF STAN 00-49 Issue 3Defence Standard:- FinalPublication Date ** February 2014Standards for DefenceReliability and MaintainabilityMOD Guide To R&M Terminology Used In RequirementsWARNINGThis is a Draft DocumentNot to be Used as an AgreedDefence StandardDRAFTUnclassified
DRAFTUnclassifiedDEF STAN 00-49 Issue 3ContentsForeword . iiiIntroduction .iv1Scope . 12Related Documents . 13Terminology Used In R&M Requirements . 24Warning . 3Annex A – Reliability . 4A.1Introduction . 4A.2IEC Definitions . 4A.3Reliability Guidance . 4Annex B – Maintainability . 9B.1Introduction . 9B.2IEC Definitions . 9B.3Maintainability Guidance . 9Annex C – Availability .14C.1Introduction .14C.2IEC Definitions .14C.3Availability Guidance .14Annex D – Testability .17D.1Introduction .17D.2IEC Definition .17D.3Testability Guidance .17Annex E – Defining Failure .20E.1Introduction .20E.2IEC Definition .20E.3Failure Definition Guidance .20Unclassifiedii
DRAFTUnclassifiedDEF STAN 00-49 Issue 3ForewordAMENDMENT RECORDAmd NoDateText AffectedSignature and DateREVISION NOTEThis standard is raised to Issue 3 to update its content.HISTORICAL RECORDThis standard supersedes the following:Def Stan 00-49, Issue 2 Reliability and Maintainability MOD Guide to Terminology Definitions dated 6 June2008.a)This Def Stan is designed to offer guidance, primarily to Ministry of Defence (MOD) personnelresponsible for setting and managing requirements, on the terminology used within R&M and how thisterminology might be tailored in order to define Specific, Measurable, Achievable, Realistic andTimebounded (SMART) requirements for different programmes.b)This standard has been produced on behalf of the Defence Material Standardization Committee (DMSC)and the Committee for Defence Equipment Reliability and Maintainability (CODERM).c)This standard has been agreed by the authorities concerned with its use and is intended to be usedwhenever relevant in all future designs, contracts, orders etc. and whenever practicable by amendmentto those already in existence. If any difficulty arises which prevents application of the Defence Standard,UK Defence Standardization (DStan) shall be informed so that a remedy may be sought.d)Any enquiries regarding this standard in relation to an invitation to tender or a contract in which it isincorporated are to be addressed to the responsible technical or supervising authority named in theinvitation to tender or contract.e)Compliance with this Defence Standard shall not in itself relieve any person from any legal obligationsimposed upon them.f)This standard has been devised solely for the use of the MOD and its contractors in the execution ofcontracts for the MOD. To the extent permitted by law, the MOD hereby excludes all liability whatsoeverand howsoever arising (including, but without limitation, liability resulting from negligence) for any loss ordamage however caused when the standard is used for any other purpose.Unclassifiediii
DRAFTUnclassifiedDEF STAN 00-49 Issue 3IntroductionThe MOD considers the term R&M to be generic and interprets it to encompass related specific conceptssuch as availability, supportability, testability etc.IEC 60050-191 contains the R&M terminology to be used forthwith by the MOD in R&M Def Stans.However, as the first source of reference for R&M definitions, IEC 60050-191 is to be regarded as genericand without exception will require tailoring to specific programmes.Defining an R&M parameter for a requirement can be problematic due to the proliferation of definitions,terms and variables, many of which are subjective.Therefore, to ensure that exact and taut R&M requirements and specifications are consistently applied inMOD contracts, it is necessary to ensure that all stakeholders have the same common understanding of theterminology used and how the variables (within the terminology) can be applied.Unclassifiediv
DRAFTUnclassifiedDEF STAN 00-49 Issue 3Standards for Defence - Reliability and Maintainability - MODGuide To R&M Terminology Used In Requirements1ScopeThis Defence Standard is designed to offer guidance, on the terminology used within R&M and, usingexamples, how this terminology might be tailored in order to define SMART requirements for differentprogrammes.The role of the Standard is to provide the building blocks to assist those concerned with setting requirementsto understand how to adapt appropriate definitions, primarily from IEC 60050-191, in order that suitablerequirements can be derived. Consequently, the definitions in Def Stan 00-49 Issue 1 are deemed obsolete.In all cases the requirement(s) must be demonstrable, through analyses and trials if appropriate, using theR&M Case methodology. If not it is likely that achievement of the requirement can not be verified/validatedand/or the User will lack confidence in the delivered solution.This Standard contains a number of examples based on specific definitions selected from IEC 60050-191.The definitions and related terms in each example are examined to provide guidance on how the variationsin their meaning might affect and be utilised in R&M requirements.The examples, being generic in origin, are not designed to be used in their current form; they represent onlya small sample of the available terminology to be used when specifying R&M requirements. Furtherinformation is obtained in the Related Documents listed below and further guidance is available from thesponsor.2Related DocumentsThe following documents and publications are referred to in the text of this Standard:REFERENCEDESCRIPTION OR TITLEIEC 60050-191International Electrotechnical Vocabulary. Chapter 191: Dependability and quality ofserviceIEC 60706-5Maintainability of equipment - Part 5: Testability and diagnostic testingADMP-01Guidance For Developing Dependability RequirementsDef Stan 00-42/3R&M Assurance Guide Part 3 - The R&M CaseDef Stan 00-42/6R&M Assurance Activity Part 6 - Maintainability DemonstrationsDef Stan 00-44R&M Data Collection and ClassificationJSP 886A Glossary of Defence Logistics Support Chain Terms and Definitions Used In JSP886 – The Defence Logistics Support Chain ManualANSI/IEEE: 610.12Standard Glossary of Software Engineering TerminologyWithin this Standard, a Reference to any related document(s) means (for any invitation to tender or contract)the edition and all amendments current at the date of such tender or contract, unless a specific edition isindicated.Unclassified1
DRAFTUnclassifiedDEF STAN 00-49 Issue 3The documents listed below may be obtained from the sources shown:DOCUMENTDOCUMENT SOURCEIEC 60050-191IEC 60706-5IEC Central Office3, rue de VarembéP.O. Box 131CH - 1211 GENEVA 20SwitzerlandPhone: 41 22 919 02 11Fax: 41 22 919 03 00E-mail: IEC Central Officewww.iec.chDefence StandardDirectorate of StandardizationStan 1Kentigern House65 Brown StreetGLASGOW G2 8EXwww.dstan.mod.ukJoint Service PublicationJoint Service Glossary (JSP 110)ADMP-1Please refer to the relevant MOD Project Team.Military Standard (MIL-STD)American National StandardsInstitute / BERKS RG12 4DWInstitute of Electrical &Electronics Engineers (IEEE):610.12 Glossary of SoftwareEngineering TerminologyIHS Group Technical Indexes LtdWilloughby RoadBracknellAC/250 SecretaryArmaments PlanningProgrammes & Policy DirectorateDefence Support DivisionNATO HQ1110 ex.co.ukwww.ansi.orgThe above documents are listed in order of preference and hierarchy and hence infer the hierarchal order ofpreference of sources of MOD R&M terminology for MOD procurement.3Terminology Used In R&M RequirementsPreviously R&M definitions have been spread across a number of standards. Endorsing IEC 60050-191 asthe first source of definitions and terminology to be used in MOD programmes will reduce this anomaly. Theexamples contained in this Standard give guidance on how the selected definitions and related definitionsand terminology can be applied to R&M requirements.A requirement is a need or expectation that is stated, generally implied or obligatory; failure to meet arequirement is normally a non-conformance (see Annex E). User requirements are defined within the UserRequirements Document (URD). The URD is translated into the System Requirements Document (SRD)which provides the basis for a contract between the MOD and a supplier.Many other sources of reference for R&M definitions exist (see Section 2). It is acceptable to use relateddefinitions where they aid the readers understanding of the terminology used. However, the common areasbetween the IEC publication and other definitions should remain paramount (i.e. the IEC definition is the firstsource of reference); all definitions used should include a clear reference to their origin.Unclassified2
DRAFTUnclassifiedDEF STAN 00-49 Issue 3Where IEC 60050-191 does not include a suitable definition, Basic Reliability for example, a suitablealternative source should be used.Some fundamental terms that frequently occur throughout this Standard are:Item [IEC 60050-191]. An item can be a part, component, device, subsystem, functional unit,equipment or system that can be individually considered. An item may consist of hardware, softwareor both. A group of items (e.g. a population of items or a sample), may be considered an item.System [IEC 60050-191]. A system is a set of interrelated items considered together for a definedpurpose. A system is generally defined with a view of performing a definite function. Typically itforms a hierarchical structure e.g. system, subsystem, component etc. A subsystem [IEC 60050191] is a system that is part of a more complex system being considered.Platform. Platform is used as a generic term in this Standard to refer to a solution; e.g. a vehicle,aircraft, ship, network, etc.The definitions selected from IEC 60050-191 as worked examples are contained in the Annexes as follows:Annex AReliabilityAnnex BMaintainabilityAnnex CAvailabilityAnnex DTestabilityAnnex EFailureNote that in order to fulfil the role of this Standard the use of actual definitions is avoided where possible,except at the beginning of each worked example. Subsequently, when a term is used for the first time, thesource of a suitable definition, if appropriate, is included in parenthesis following the term; e.g. reliability [IEC60050-191].4WarningThe Ministry of Defence (MOD), like its contractors, is subject to both United Kingdom and European lawsregarding Health and Safety at Work. All Defence Standards either directly or indirectly invoke the use ofprocesses and procedures that could be injurious to health if adequate precautions are not taken. DefenceStandards or their use in no way absolves users from complying with statutory and legal requirementsrelating to Health and Safety at Work.Unclassified3
DRAFTUnclassifiedDEF STAN 00-49 Issue 3Annex A – ReliabilityA.1IntroductionIt appears obvious that requirements should call for very high values of reliability, as this would mean thatsystems would fail less frequently and consequently cost less in service. However, the risks arising fromnew (often unproven) technologies and the potentially high costs of achieving and/or demonstrating highreliability must be balanced with what is realistically acceptable. In practice this means delivering to the Userthe capability to accomplish (and if necessary sustain) a mission at acceptable technical risk with theminimum cost (taking a risk based approach to requirements setting is ideal). Reliability requirements mustbe realistic and attainable - they should be what are required by the User not what might be desirable.Therefore, it is important to specify the minimum acceptable levels of reliability and, in combination withmaintainability and availability, to do so in a manner that does not impose undue constraints on the designer.It is important to avoid unnecessary limitations on the designers' capacity and flair to achieve a satisfactorybalance between R&M, performance and cost.A.2IEC DefinitionsIEC 60050-191 defines reliability as follows:Reliability (as a performance measure) is the probability of being able to perform as required undergiven conditions for the time intervalReliability (of an item) is the ability to perform under given conditions for a given time interval.A.3Reliability GuidanceA statistical parameter such as reliability cannot be measured directly and repeatably. It can only bemeasured to a level of confidence. Confidence Levels, and their use in requirements, can be a complexarea to cover in a short example; further reading is therefore recommended. The list of Related Documentsin this Standard provides suitable reference material.Typically different levels of reliability will be set for different levels of functionality with critical functionalityhaving higher levels. For vehicles this is typically set as:Mission reliability [IEC 60050-191] is the probability that an item will perform its requiredfunctions for the duration of a specified mission profileBasic reliability is the ability of an item to perform its required functions without failure or defectfor the duration of a specified mission profilePeacetime reliability can be defined in similar terms to mission reliability however; the 'mission'could be any task that the User undertakes outside a theatre of war or operation other than war.While for other systems it might be set as:Critical reliability is the ability of an item to perform its Critical functions without failure for theduration of a specified mission profile. Where Critical may refer to safety and/or mission criticalfunctionMajor reliability is the ability of an item to perform without lost of major functions for the durationof a specified mission profileMinor reliability [IEC 60050-191] is the probability that an item will not suffer minor failures for theduration of a specified mission profileUnclassified4
DRAFTUnclassifiedDEF STAN 00-49 Issue 3Where mission profile is a “typical use profile” specifying how the system will be used and what functionalityis needed during the mission. For a simple system this may be fully functioning for a given time, while for amore complex system this may show what functionality is required on an hour by hour basis over a longduration.Generally speaking mission or critical reliability is the value used to denote the chances of a platformsuccessfully completing an agreed given scenario which for a land based solution may be referred to as aBattle Field Mission (BFM), an aircraft a sortie, etc. Consequently it is the most important reliabilitycharacteristic in terms of evaluating operational effectiveness.Basic or minor reliability relates to all other failures requiring maintenance or restore actions that do notdirectly affect the mission. All corrective maintenance actions are counted, from changing a main assemblyto unscheduled minor adjustments. Basic reliability (which includes all basic and mission failures)determines the burden of effort, costs etc arising from corrective maintenance.Peacetime reliability can be calculated from the combination of all attributable (mission/task) failures and allcritical failures judged to contravene safety / environmental legislation. It is possible, depending on locallegislative demands (and the User's obligations in meeting them), that a version of a peacetime failuredefinition must be specified for an operational deployment.In order to tailor reliability requirements exclusively for each programme the available terminology (from IEC60050-191 as a first source) must be fully understood. The following examples give guidance:Able to PerformBeing able to perform, and performance in general, is concerned with the limiting boundaries of the requiredfunctionality of an item. In order to achieve the mission the User's limits (often the lowest acceptable limits,otherwise known as threshold values) are normally specified. For example:Maximum forward/reverse speed must be achievableMaximum rate of turn must be achievableThe minimum specified number of communication channels must be availableThe minimum specified distance over which it is possible to detect and locate a threat must besustainedA minimum average speed of 30 km/h should be sustainable during the missionAlternately, if measurable, a permissible amount of degradation (a typical threshold value) may beacceptable if the mission would otherwise be unaffected; for example:Degradation in engine power of 20% is acceptableThe sustained achievement of 20% of the maximum attain
IEC 60050-191 International Electrotechnical Vocabulary. Chapter 191: Dependability and quality of service IEC 60706-5 Maintainability of equipment - Part 5: Testability and diagnostic testing ADMP-01 Guidance For Developing Dependability Requirements Def Stan 00-42/3 R&M Assurance Guide Part 3 - The R&M Case Def Stan 00-42/6 R&M Assurance Activity Part 6 - Maintainability Demonstrations Def .
4 Fileamsbook-xepersian.def 3 5 Fileappendix-xepersian.def 3 6 Filearticle-xepersian.def 3 7 Fileartikel1-xepersian.def 3 8 Fileartikel2-xepersian.def 4 9 Fileartikel3-xepersian.def 4 10 Filebackref-xepersian.def 4 11 Filebidituftesidenote-xepersian.def 4 12 Filebidimoderncv-xepersian.def 5 13 Fileboek3-xepersian.def 5 14 Fileboek-xepersian.def 5
NORTHGATE COLOR PALETTE 2 See page 5 for specifications and warranty details. 3 Max Def Burnt Sienna Max Def Moire Black Max Def Driftwood Max Def Pewter Max Def Georgetown Gray Max Def Resawn Shake Max Def Granite Gray Max Def Weathered Wood Max Def Heather Blend Silver Birch CRRC Product ID 0668-0072 Max Def Hunter Green NORTHGATE
MIL-PRF- 6081D Grade 4 4 MIL-PRF-7808L Grade 3 4 MIL-PRF-23699F STD C/I HTS 4 4 4 MK-8, MS-8P, MS-8RK 4 DOD-L-85734 4 DEF-STAN 91-94 (DERD2468) 4 DEF-STAN 91-98 (DERD2487) 4 DEF-STAN 91-99 4 DEF-STAN 91-100 4 DEF-STAN 91-101 Grade OX-27 4 Shell Aviation has a portfolio of minera
Max Def Burnt Sienna Silver Birch Max Def Resawn Shake Max Def Georgetown Gray Mountain Timber Max Def Moire Black Max Def Weathered Wood Max Def Heather Blend color palette max def colors - Look deeper. With Max Def, a new dimension is added to shingles with a richer mixture of surface granules. You get a brighter, more vibrant, more dramatic .
Servomech S.p.A. 01.05.27.BS-ModB.E - Rev. 03 DD (M/Y) 04/21 5 1 MODELS COVERED BY THIS DOCUMENT The present manual is referred to following products: Ball screw jack with travelling nut MA Series: MA 5 BS Mod.B - MA 10 BS Mod.B - MA 25 BS Mod.B - MA 50 BS Mod.B - MA 80 BS Mod.B - MA 150 BS Mod.B - MA 200 BS Mod.B - MA 350 BS Mod.B
OWNER'S MANUAL CENTRAL VACUUM CLEANERS DS MODULAR MOD. DS A01 MOD. DS B01 MOD. DS B02 MOD. DS BC100i MOD. DS C03 MOD. DS CD125i MOD. DS D02 MOD. DS EF125i MOD. DS F03 MOD. DS H02 . Central vacuum cleaner DS F03 125 l- up to 6 operators . 7 Central vacuum cleaner DS H02 175 l- up to 8 operators . 7 Central vacuum cleaner DS .
MIL-PRF-23699F STD 4 C/I 4 HTS 4 4 MK-8, MS-8P, MS-8RK 4 DOD-L-85734 4 DEF-STAN 91-94 (DERD2468) 4 DEF-STAN 91-98 (DERD2487) 4 DEF-STAN 91-99 (DERD2490) 4 DEF-STAN 91-
Neither A. Thomas Perhacs nor Velocity Group Publishing assumes any responsibility for the use or misuse of the concepts, methods and strategies contained in this book. The reader is warned that the use of some or all of the techniques in this book may result in legal consequences, civil and/or criminal. USE OF THIS BOOK IS DONE AT YOUR OWN RISK. (Updated Version, July 2008) As you begin to .
