1、NOTE: MlL-STD-l814 has been redesignated as a handbook, and is to be used for guidancepurposes only. This document is no longer to be cited as a requirement. For administrativeexpediency, the only physical change from MlL-STD-l814 is this cover page. However, thisdocument is no longer to be cited as
2、 a requirement. If cited as a requirement, contractors maydisregard the requirements of this document and interpret its contents only as guidance.I NOT MEASUREMENTSENSITIVEMIL-HDBK-181414 Februaw 1997SUPERSEDINGMIL-STD-1814NOTICE 114 February 1997DEPARTMENT OF DEFENSEHANDBOOKINTEGRATED DIAGNOSTICSTH
3、ISHANDBOOK IS FOR GUIDANCEONLYDO NOT CITE THIS DOCUMENTAS A REQUIREMENTAMSC WA AREA GDRQDISTRIBUTIONSTATEMENTA. Approved for public release; distribution is unlimited.Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-MIL-STD-1814FOREWORD1. This militar
4、y standard is approved for use by the Aeronautical Systems Division,Department of the Air Force, and is available for use within the disrnbution limitations noted onthe cover page.2. Beneficial comments (recommendations, additions, deletions) and any pertinent data whichmay be of use in improving th
5、is document should be addressed to: ASD/EhT3S, Wrigh-.Patteraon AFB OH 45433-6503 by using the Standardization Document Improvement Proposal(DD Form 1426) appearing at the end of this document or by letter.3. This standard is one of two documents that address incorporating Integrated Diagnostics(fD)
6、 into Air Force weapon system acquisition programs. The other document is AFGS-87256.WARNINGINFORMATION SUBJECT TO EXPORT CONTROL LAWSThis document contains information subject to the International Traffic in Arms Regulation(ITAR) and/or the Expost Administration Regulal.ion (EAR) of 1979 which may
7、not beexporrcd;released, or disclosed to foreign nationals inside or outside thel_Jnitcd States withoutfust obtaining an export license. A violation of the IrAR or EAR maybe subject to a penaltyof up to .10 years imprisonment and a fine of $100,000 under 22 U.S.C. 2278 or section 2410of the Export A
8、dministration Actof 1979. Include this notice with any reproduced portion ofthk document.DESTRUCTION NOTICE: MIL-STD-1814, (USAF) is an unclassified, limited document.Destroy unclassified, limited documents by any method that will prevent disclosure orreconstrucuon of the document.This documentconta
9、insTechnicatDatamnsidered“tok a resourceunder t 402b.3 of DoDRegulationNumber54X).7-Rand is noi a “record”rq uiredto bereleasedunderthe Freedomof InformationActiiProvided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-(/MIL-STD-1814TABLE OF CONTENTSIwmQN1. S
10、COPE1.1 SCOPE1.2 PURPOSE1.3 APPLICABILITY1.3.1 Application guidance1.3.1.1 Organization1.3.1.2 Usage1.3.1.3 Example1.4 TAJLORING OF REQUIREMENTS1.4.1 Diagnostic capability1.4.2 Integrated diagnostic approach1.4.3 Integrated diagnostic process“, APPLICABLE DOCUMENTS2.1 GOVERRX4ENTDOCUMENTS2.1.1 Speci
11、fications, standards, and handbooks2.2 ORDER OF PRECEDENCE3. REQUIREMENTS3.1 DEVELOPMENT3.1.1 nonal Reauirem3.1.1.1 Diagnostic inputs to the SON3.1.1.2 Diagnostic inputs to the PMD3.1.2 on Phstsg3.1.2.1 Dl;gnostic segments of the PMP sections3.1.2.l.a Mc.ciiilcationplanning3.1.2.2 Diagnostic segment
12、s of the RFP3.1.2.3 Diagnostic segments of program plans3.1.2.3.1 Data sharing UtS3.1.2.4 Diagnostic requirements derivation and allocation3.1.2.5 Diagnostic inputs to the TEMP3.1.2.6 Diagnostic capability SRR3.1.2.7 Diagnostic specifications3.1.2.8 Diagnostic inputs to the SORD “3.1.2.9 Diagnostic
13、inputs to the DSRD3.1.2.10 Diagnostic inputs to SCPPAGENIAIN APPEX111144557 317 317 317 317 337 3328; 337 357397 417 447 477 488 49s 508 528 53IIllProvided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-MIL-STD-1814TABLE OF CONTENTS(cont.)SE.a!QN3.1.33.1.3.1
14、3.1.3.l.a3.1.3.23.1.3.33.1.3.3.13,1.3,43.1.3.53.1.3.63.1.3.73.1.3.83.1.3.93.1.3. !03.1.3.113.1.43.1.4.13.1,4.l.a3.1.4.23.1.4.33.1.4.3.13.1.4.43.1.4.4.13.1.4.53.1.4.63.1.4.73,1.4.7.13.1.4.7.23.1.4.7.33.1.4.83.1.4.8.13.1.4.93.1.4.9.13.1.4.103.1.4 .10.13.1.4.113.1.4.123.1.4.13 3.1.4.143.1.4.153.1.4.163
15、.23.?.13.2.23.2.33.2.43.2.4. ”Demo nstration/Vrr,i (Demlvai) PhaseDrostic segments of die PMPMdilcaaon kmningDiagnostic segments of the RFPDiagnostic segments of program plansEstablish data sharing plansDiagnostic system engineering studies and analysesDiagnostic maturation and 8 678 709 719 749 789
16、 799 809 819 829 8310 10610 10710 10810 10910 11110 11310 11710 11710 11810 11910 12111 12211 12311 12411 12911 13111 13211 .13411 .13511 13511 13511 136II 13711 13812 139Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-MIL-STD-1814TABLE OF CONTENTS (
17、cont.)SEmoNPAGEWA.ETEN3.2.4.2 Update verncal test traceabiMy masrix3.2.4.3 Diagnostic performance assessment and evaluation3.2.5 Change approval process3.2.6 Program management responsibility oansfer3.3 DEPLOYMENT3.3.1 Deployed diagnostic element performance assessment3.3.1.1 Deployed diagnostic ele
18、ment corrective action4. VERIFICATiONS4.1 DEVELOPMENT4.1.1 nal ReauuementS4.1.1.1 Diagnostics inputs to dse SON4.1.1.2 Diagnostic inputs to the PI4.1.24.1.2.14.1.2.l.a4.1.2.24.1.2.34.1.2.3.14.1.2.44.1.2.54.1.2.6”4.1.2.74.1.2.84.1.2.94.1.2.104.1.34.1.3.14.1.3.l.a,4.1.3.24.1.3.34.1.3.3.14.1.3.44.1.3.5
19、4.1.3.64.1.3.74.1.3.84.1.3.94.1.3.104.1.3.11CO mx_Exdamn “onPhaseDi;enostic inouts to the PMP sectionsMilcation planningDiagnostic segments of the RFPDiagnostic segments of program plansData sharing plansDiagnostic requirements derivation and allocationDiagnostic inputs to the TEMPDiagnostic capabil
20、ity SRRDiagnostic specificationsDiagnostic inputs to the SORDDiagnostic inputs to the DSRDDiagnostic inputs to SCPal) I64.1.4.7-4. 1.4.7.14.1.4.7.24.1.4.7.34.1.4.84.1.4.8.14.1.4.94.1.4.9.14.1.4.104:1.4 .10.14.1.4.114.1.4.124.1.4.134.1.4.144.1.4.154.1.4.164.24.2.14.2.24.2.34.2.44.2.4.14.2.4.24.2.4.34
21、.2.5c 4.2.64.34.3.14.3.1.15.5.15.2Mcdificacion planningDiagnostic segment of the RFPDiagnostic segment of prognmr plansDevelop/Update data sharing plansDiagnostic preliminary design IDiagnostic inputs to hardware and software specificationsDiagnostic data collection and maturation planningPreliminar
22、y Design ReviewsDiagnostic dew designDesign embedded diagnostics capabtiry fnterface with engineering disciplines and lotics supponDiagnostic trtpucsto hardware and software specitlcationsDiagnostic related plansUpdate diagnosacinputs to the TEMPUpdate diagnostic inputs to the SORD and the RCMUpdate
23、 diagnostic inputs to the DSRDCritical Design ReviewDiagnostic segments of the Test Reqttirwnents ReviewFabricate and provide external diagnostic elementsDiagnostic segment of DT Appwdx A, ID Handbook: %ticmal., guidmce, and lessons learned R.! .Guidancej fc4 eati rewir9nwot d vefifi-tiOn LessonsLe=
24、ned Ifmmd In fhe main body 4.1.2,3 enruatin. . . .L.,. Appendices B through H:;Guidance for 12.ilCXitIg01 PeffO1tiW? 1 APPENDICF”- K . . .,;,-!sand verilicaticms.”.2.-. .:.-.,: : .-.;: . . . . - .APPENDIXI “IIAppendix 1,Roadnwp: FlowofID SC?Wes through acquisitica; F Smt-dard Wicg 01 sig.iticzmt lWB
25、. . . . . . . . . . . . . . . . . . . . . . . . . . . Raadrnsp r 1. Starf by# determiningapplicablerequirement. Phase. Taskindex J.Qjc -Xxxx xxXXxx xx. . . .Figure 2 Organizationand UseofIDMIL-STD-18141.3,1.3 Example. A contmcor incorporating diagnostics into various plwrs for a progrJnlin LheConcep
26、t Exploration Phase would go to the ConcepI Explomtion section of theRoxicrrap, in this case p. 277. and note hat the tox tided “Diagnostic segments ofprogram! . ” L .“.- / . , -3-.-, -., ,“,Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-MIL-S D-181
27、4.,plans” and annotated with 3.1.2.3 addresses the area of concern. Looking for 3.1.2.3 irr theTable, of Contents (p. iii) reveafs that its requirement :statement is on p. 7. The appendixinformation (rationale, guidance, lessons learned) is on p. 39. The veriflca!ion statement (p. vof the table of c
28、ontents) is 4.1.2.3 on D. 13 and its aupendix information is on r).40. Note thata vefilcaaon is immediately behind it; correspcrndti”grequirement in Appendix”A, whiferequirements and verifications are in separate sections in the main body.1.4 TAILORING OF REQUIREMENTS. This standard does not require
29、 theestablishmentof a new or separate organization for integrated diagnostics. The individualrequirements should be stated so that existing engineering disciplines cart jmplement integrateddiagnostics requirements by augmenting their programs.1.4.1 Diagnostic capability. The diagnostic capability di
30、scussed in this document coversa systems ability to detect faults and to isolate the causes of hose faults to provide statusinformation upon which to base decisions, such as is an aircraft safe to fly, what needs to bereplaced or repaired to restore a function, or has a component been successfully r
31、epaired. Theability of diagnostics to provide information upn which to b= decisions is an integral part ofa weapons systems ability to accomplish its mission. This diagnostic capability is illustedin Figure 3.tow%WSTSMCPEWT If in wemtic.n A Iunctica is ! Lwng Ferbmed)W! item has tailed. causinp WIt
32、in awakm Ilmctbll la ml be perlc.nnedlKITFYAUTCWATICRECCw=GuuAm SVSTEMMAINTAINERCunpabb tesl parameten d Pmcedwos)m.lhewmmmkaawati-ab m!.Irem. Tlw Iowsl level com$mnen!mat can be rs8c8d, repaired, mpmgrammti u recenfqumdu iho apecir IWOI01tneim-nm,rO_ ti rwfi.imrn w rti ,7xsrfainrs.Figure 3 Diagnost
33、ic Capability1.4.2 Integrated diagnostic approach. An integrated approach to achieving a balanceddiagnostic capabtity has dte following key feames.1 The integration of embedded, support equipment, and manual techniques to providecomplete coverage of diagnostic istformation needs4Provided by IHSNot f
34、or ResaleNo reproduction or networking permitted without license from IHS-,-,-MIL-STD-18142. The integration of +1 needs for diagnostic information to minimize overall diagnosticsrequired and opmruze performance (Diagnostics embedded for mission reasons can storefault data useful for maintenance)1.4
35、.3 Integrated diagnostic process. The ID process is intended to work in a systemengineering environment. It requires a team approach in which all aspects of an acquisition(performance, support, production, etc.) are considered from the beginning and addressedinteractively throughout a program. Prope
36、rly tailoring and applying diagnostic requirements asdepicted on the Roadmap will ensure that diagnostics is considered at tie proper points in anacquisition program. It is up to overall program management to ensure that the proper systemengineering environment is provided so rhat these requirements
37、 can be satisfied.Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-MIL-STD-18142. APPLICABLE DOCUMENTS2.1 GOVERNMENT DOCUMENTS2.1.1 Specifications, standards, and handbooks. The following specifications,stmdmds, mdhmdtiks fomapmof ttisdument totheexte
38、nt specified herein, Unlessotherwise specified, the issues of these documents are ose listed in the issue of theDepartment of Defense Index of Specifications arrciStandards (DODISS) and supplementthereto, cited in the solicitation (see 6.2).Military SpecificationsAFGS-87256 Integrated Diagnostics (I
39、D AFGS )(Unless otherwise indicated, copies of federal atrd military specifications, standards, andhandbooks are available from the Standardization Docume!sts Order Desk, Building 4D,Robbins Avenue, Philadelphia, PA 19111-5094.)2.2 ORDER OF PRECEDENCE. In the event of a conflict between the text of
40、thisdwtrment and dre references cited herein, the text of this document takes precedence. Nothingin this document, however, supersedes applicable laws apcjregulations unless a specificexemption has been obtained.6Provided by IHSNot for ResaleNo reproduction or networking permitted without license fr
41、om IHS-,-,-MIL-STD-18143. REQUIREMENTS -The requirements stated herein address the diagnostics activities depicted in the Appendix IRoadmap. They are organized by life cycle phase, as is the Roadmap. They define the stepsand procedures necessay for imegraring tie diagnostic pieces with each other an
42、d with theoverall weapon system/equipment life cycle.3.1 DEVELOPMENT. The Development section covers the following life cycle phases, atdte indicated section numbers.Operational Requirements (3.1.1)Concept Exploration (3.1.2)Demonsuation and Validation (3.1.3)Full-Scale Development (3. 1.4)3.1.1 3.1
43、.1.1 Diagnostic inputs to the Statement of Operational Need. Diagnosticinputs to the Statement of Operational Need (SON) must be provided to establish dre basis fordeveloping the diagnostic capability.3.1.1.2 Diagnostic inputs to the Program Management Directive. Diagnosticinputs to the Program Mana
44、gement Directive (PMD) must be provided to ensure that adequateattention is paid to diagnostics by the acquisition agency3.1.23.1.2.1 Diagnostic segments of the Program Management Plan sections. Theapproach to satisfying diagnostic requirements must be included in the appropriate sections ofdse Air
45、Force program Management Plsn (PM.P)3.1.2.l.a Modification planning. Include the approach to satisfying diagnosticrequirements in modification plans.3.1.2.2 Diagnostic segments of the Request For Proposal. The sections of theRequest For Proposal (RFP) that address diagnostic issues shall be prepared
46、.3.1.2.3 Diagnostic segments of program plans. Diagnostic inputs to the variousconuactor-prepared management plans must be prepared.3.1.2.3.1 Data sharing plans. The contractor shall establish and implement formaI datasharing plans to ensure that functional organizations, team members, and suixonmac
47、tors haveaccess to current diagnostic development information throughout the concept explorationphase.3.1.2.4 Diagnostic requirements derivation and allocation. Diagnosticrequirements and initial diagnostic approaches based on weapon system needs shall be defined.3.1.2.5 Diagnostic inputs to the Tes
48、t and Evahsation Master Plan. Diagnosticinputs shall be incorporated into the Test and Evaluation Master Plan (TEMP).3.L2.6 Diagnostic capability during System Requirements Review. A review ofa71diagnostic requirements and the analysis that lead to the selection of the preferred diagnosticapproach shall be included dtig the System Requirements Review (SRR).7Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-MIL.STD-18143,1.2.7 Diagnostic specifications. Diagnosic requirements resulting from thepreliminary
