Transcription
NOT MEASUREMENTSENSITIVEMIL-STD-97317 April 1992SUPERSEDING(See section 6.4)MILITARY STANDARDCONFIGURATION MANAGEMENTAMSC No. D6728AREA CMANDistribution Statement A: Approved for public release; distribution is unlimited
FOREWORD1.DepartmentsThisMilitaryand AgenciesStandardof theis approvedDepartmentofforuseDefenseby all(DoD) .MIL-STD-973is jointlysponsoredby theOfficeof the2.TheSecretaryof Defenseand the JointLogisticsCommanders.primarypurposeof thisstandardis to tionmanagementstandardizationAs a resultof ficantlyreducesthenumberof rdsin theDoD inventory.Althoughsupersededby MIL-STD-973areidentifiedin Section6.consolidationis theprimarypurposeof thisinitiative,Some requirementsfromMIL-STD-973doescontainnew material.supersededstandardshavebeenmodifiedto clarifyambiguitiesorSome obsoleteor redundantto nand Logisticdeletedentirely.Support(CALS) has beenaddressedin thisissueto theextentsome new requirementshavebeenidentifiedAlsotpracticable.and included.Thisstandardhas beendevelopedforuse by both3.Towardthisend,thetermcontractorsand Governmentactivities.has beenusedthroughoutto denotean activity“contractor”performingany of therequirementsof thisstandard.Acan be eithera contractoror Governmentactivity.“contractor”Whereverit is necessaryto tingand thetaskingactivity(i.e., theActivitywhichawardsa contractto a chtasksanotherGovernmentactivity,or a contractorwhichtasksa subcontractor), thetermhas beenusedthroughoutto ementsof thisstandardon ionthecharacteristicsstandarddefinesthe equirementsof configurationtheyapplyto defensematerielitems.is a managementdisciplineappliedtomanagementlifecycleto ensurethatovertheiritems(CIS)of CIS t5.beenincludedin thisstandard.bothhardwareand mentsforsoftwarehaveWhererequirementsarecommon totheyareshown as requirementsnot common to bothhardwareand
MIL-STD-973--softwareitems,theyareshown as requirementssoftwareconfigurationitems(CSCIS)or hardwareitems(HWCIS) , as ments(recommendations,additions,deletions)and any pertinentdatawhichmay be of useinimprovingthisdocumentshouldbe addressedto:Chief,PolicyDivision,CALS Evaluationand ch,VA tImprovement(DD Form 1426)appearingat theend of thisdocumentorletter.iiiPlansand5203by usingProposalby
MIL-STD-973CONTENTSPAGEPARAGRAPH.11. . . . . . . . . . .and handbooks. . . . . . . . . . . .22233DEFINITIONS. . . . . . . . . . . . . . . . .Acronymsusedin thisstandard. . . . . . .AdvanceChangeStudyNotice(ACSN) . . . . .AllocatedBaseline(ABL). . . . . . . . . contractualimplementation. . . .ConfigurationBaseline. . . . . . . . . . .Blockchangeconcept. . . . . . . . . . . .Classificationof defects. . . . . . . . .Commercialand GovernmentEntity(CAGE) CodeComputerdatabase. . . . . . . . . . . . .Computerdatadefinition. . . . . . . . . .Computersoftware. . . . . . . . . . . . .ComputerSoftwareComponent(CSC). . . . ftwaredocumentation. . . . . .ComputerSoftwareUnit(CSU) . . . . . . . .Configuration. . . . . . . . . . . . . . .Configurationaudit. . . . . . . . . . . . . . B).1 . . . .Configurationdocumentation. . . . . . . .Configurationidentification. . . . . . . .ConfigurationItem(CI). . . . . . . . . .ConfigurationManagement(CM). . . . . . .ConfigurationManagementPlan(CMP). . . .ConfigurationStatusAccounting(CSA). . .Contractor. . . . . . . . . . . . . . . .Criticalitem. . . . . . . . . . . . . . .Data. . . . . . . . . . . . . . . . . . .Defect. . . . . . . . , . . . . . . . . .Deficiencies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44666777777777888888889991.21.3SCOPE. PLICABLEDOCUMENTS . . .Governmentdocuments. Orderof precedence. 273.283.293.303.311.1.1.of. . . . . . . . . .requirementsiv. 1110101010101010.
3.743.753.76Designchange. . . . . . . . . . . . . .Developmentalconfiguration. . . . . . . .Deviation. . . . . . . . . . . . . . . .Engineeringchange. . . . . . . . . . . .Engineeringchangejustificationcode. . .Engineeringchangepriorities. . . . . . .EngineeringChangeProposal(ECP). . . . .EngineeringChangeProposaltypes. . . . .Engineeringrelease. . . . . . . . . . . .EngineeringReleaseRecord(ERR). . . . .Evaluation. . . . . . . . . . . . . . . .Exchangeabilityof items. . . . . . . . .Firmware. . . . . . . . . . . . . . . . .Fit. . . . . . . . . . . . . . . . . . .Form. . . . . . . . . . . . . . . . . . .Function. . . . . . . . . . . . . . . . .Functionalarea. . . . . . . . . . . . .FunctionalBaseline(FBL). . . . . . . . .Functionalcharacteristics. . . . . . . .FunctionalConfigurationAudit(FCA). . . . . . . . . . . . . . . . . . .HardwareConfigurationItem(HWCI). . . .IntegratedLogisticsSupport(ILS). . . .Interchangeableitem. . . . . . . . . . .Interface. . . . . . . . . . . . . . . .Interfacecontrol. . . . . . . . . . . . .InterfaceControlDrawing(ICD). . . . . .InterfaceControlWorkingGroup(ICWG). .Interoperability. . . . . . . . . . . . .Item. . . . . . . . . . . . . . . . . . .Lifecycle. . . . . . . . . . . . . . . .Lifecyclecost. . . . . . . . . . . . .Manufacturer’scode. . . . . . . . . . . .Material. . . . . . . . . . . . . . . . .Non-conformance. . . . . . . . . . . . .Non-developmentalItem(NDI). . . . . . .Non-recurringcosts. . . . . . . . . . . .Noticeof Revision(NOR). . . . . . . . .Original. . . . . . , . . . . . . . . . .( C )”1 1 1 RProductBaseline(PBL). . . . . . . . . .ProductConfigurationDocumentation(PCD) .Recurringcosts. . . . . . . . . . . 2121313131313131313131313131414141414141414151515
3.943.953.963.973.98Release. . . . . . . . . . . . .Repair. . . . . . . . . . . . . .Replacementitem. . . . . . . . .Retrofit. . . . . . . . . . . . .Rework. . . . . . . . . . . . . .Software. . . . . . . . . . . . .Specification. . . . . . . . . . .SpecificationChangeNotice(SCN) .Substituteitem. . . . . . . . . .Supportequipment. . . . . . . . .Survivability. . . . . . . . . . .System. . . . . . . . . . . . . .Technicaldata. . . . . . . . . .Technicaldatapackage. . . . . .Technicaldocumentation. . . . . .Technicalreviews. . . . . . . . .Trainingequipment. . . . . . . .Unit. . . . . . . . . . . . . . .Version. . . . . . . . . . . . .Waiver. . . . . . . . . . . . . .Work BreakdownStructure(WBS). .Work breakdownstructureelement.0 184.3.14.3.24.3.34.44.54.64.7GENERAL REQUIREMENTS. . . . . . . . . . . . .Basicrequirements. . . . . . . . . . . . .Planning. . . . . . . . . . . . . . . . . .SupportComputer-aidedAcquisitionand Logistic(CABS ). . . . . . . . . . . . . . . . . . .Data distribution/access. . . . . . . .*.Automatedprocessingand submittalof data.Interactiveaccessto digitaldata. . . . .Configurationidentification. . . . . . . .Configurationcontrol. . . . . . . . . . . .ConfigurationStatusAccounting(CSA) . . . .Configurationaudits. . . . . . . . . . . 3.2DETAILED REQUIREMENTS . . . . . . .Purpose. . . . . . . . . . . �sCM Plan. . . . . .Work BreakdownStructure(WBS).Technicalreviews. . . . . . . .Configurationidentification. .Purposeof configurationidentificationItemselection. .Configuration.4.4.14.24.3vi. 24242424242425. 25.26—
MIL-STD-973CONTENTSPAGEPA 5.3.5.2.15.3.5.2.25.3.5.2.35.3.5.2.4‘-. 5.4.2.15.4.2.2Developmentalconfiguration. . . . . . . . . . .Documentationlibra;y. . . . . . . . . . . . . .Drawinglibrary. . . . . . . . . . . . . . . .SoftwareDevelopmentLibrary. . . . . . . . . .Configurationbaselines. . . . . . . . . . . . .Configurationbaselinesand theirconfigurationdocumentation. . . . . . . . . . . . . . . . .FunctionalConfigurationDocumentation(FCD). .AllocatedConfigurationDocumentation. . . . . .ProductConfigurationDocumentation. . . . . . .Maintenanceof configurationdocumentation. . .Engineeringreleaseand correlationofmanufacturedproducts. . . . . . . . . . . . . .Specificationreleaseand approval. . . . . . .RequirementsforEngineeringReleaseRecords(ERRs). . . . . . . . . . . . . . . . . . . . .UseofERRs. . . . . . . . . . . . . . . . . .Initialrelease. . . . . . . . . . . . . . . .Changerelease. . . . . . . . . . . . . . . . .Consolidationof multiplechangesintoa singleERR. .’. . . . . . . . . . . . . . . . .Configurationidentifiers. . . . . . . . . . .CAGE Code. . . . . . . . . . . . . . . . . . .Governmenttypedesignatorsand nomenclature. .Documentnumbers. . . . . . . . . . . . . . . .Part/itemidentificationnumbers. . . . . . . .Softwareidentifiers. . . . . . . . . . . . . .Serial/lotnumbers. . . . . . . . . . . . . . .Governmentserialnumbers. . . . . . . . . . . .Reuseof serialnumbers. . . . . . . . . . . . .Productidentification/marking. . . . . . . . .Softwaremarkingand labeling. . . . . . . .Firmwarelabeling. . . . . . . . . . . . . . . . . . . . . . . .NDI , COTS, and PDI labelingInterfacemanagement. . . . . . . . . . . . . .Interfacerequirements. . . . . . . . . . . . .Requirementsforan InterfaceControlWorkingGroup(ICWG). . . . . . . . . . . . . . . . . .ICWGmembership. . . . . . . . . . . . . . . .ICWGChairmanship. . . . . . . . . . . . . . . .Configurationcontrol. . . . . . . . . . . . . .Purposeof configurationcontrol. . . . . . . .RequirementsforEngineeringChanges. . . . . .The engineeringchangeprocess. . . . . . . . .Administrativerequirements. . . . . . . . . . 3031313131323232323233333333343434
.4.2.4.23.41.11.21.31.41.11.2Classificationof engineeringchanges. .Classifyingengineeringchangesto aprivatelydevelopeditem. . . . . . . . .Contentof EngineeringChangeProposals(ECPS). . . . . . . . . . . . . . . . . .Unrelatedengineeringchanges. . . . . .RevisionsofECPS. . . . . . . . . . . .Supportingdata. . . . . . . . . . . . .Classifieddata. . . . . . . . . . . . .ClassI EngineeringChangeProposals. . .ClassI ECP decisions. . . . . . . . . .Targetfortechnicaldecisionon ClassIECPS. . . . . . . . . . . . . . . . . .ECP authorization. . . . . . . . . . . .ClassI compatibilityengineeringchangesDisapprovalof ECPS. . . . . . . . . . .ClassI ECP justificationcodes. . . . .ClassI ECPtypes. . . . . . . . . . . .Preliminarychangeproposal. . . . . . .Use of preliminaryECPS (TypeP) . . . . .Use of AdvanceChangeStudyNotice(ACSN)Use of FormalECP (TypeF) . . . . . . . .ClassI engineeringchangepriorities. .ExpeditingClassI engineeringchangeswithpriorityof emergencyor urgent. . . . .FormatforClassI engineeringchanges. .ClassI engineeringchangesduringconceptdemonstrationand validationexploration,ClassI engineeringchangesduringengineeringand manufacturingdevelopmentClassI engineeringchangesduringproductionand support. . . . . . . . . .Relatedengineeringchanges. . . . . . .Relatedengineeringchanges- singleprimeprimeRelatedengineeringchanges- singlemultipleprocuringactivities. . . . .Relatedengineeringchanges- separateprimes. . . . . . . . . . . . . . . . .Same engineeringchange- prime/subcontractorcoordination. . . . . . . .Same engineeringchange- severalcontractors. . . . . . . . . . . . . . .ClassII engineeringchanges. . . . . . .ClassII engineeringchangeformat. . . .Class11 justificationcodes. . . . . . 4545.48.48.484949.50.50.50.50505051—
5.4.8.2.15.4.8.2.25.4.8.2.35.4.8.2.4Concurrencein ClassII changes. .Approvalof Class11 changes. . . .Non-custodyof tion(RFD). . . . . . . . . . . . . . .Restrictionson deviations. . . . .Recurringdeviations. . . . . . . .Classificationof deviations. . . .Minor. . . . . . . . . . . . . . .Major. . . . . . . . . . . . . . .Critical. . . . . . . . . . . . .Format. . . . . . . . . . . . . .Dispositionof deviations. . . . .Minordeviations. . . . . . . . . .Criticaland majordeviations. .RequirementsforRequestsforW iverRestrictionson waivers. . . . . .Recurringwaivers. . . . . . . . .Classificationof waivers. . . . .Minor. . . . . . . . . . . . . . .Major. . . . . . . . . . . . . . .Critical. . . . . . . . . . . . .Format. . . . . . . . . . . . . .Dispositionof WZtiVerS . . . . . . .Minorwaivers. . . . . . . . . . .Criticaland majorwaivers. . . . .Partssubstitutions. . . . . . . .RequirementsforSpecificationChangeNotices(SCNs). . . . . . . . . . .SCNcoverpage. . . . . . . . . .Attachmentsto proposedSCN. . . .Supersession. . . . . . . . . . .ApprovedSCN. . . . . . . . . . .Changedpages. . . . . . . . . . .RequirementsforNoticesof Revision(NORS) . . . . . . . . . . . . . . .Configurationcontrol(shortformprocedure). . . . . . . . . . . . .Purpose. . . . . . . . . . . . . .RequirementsforECPS. . . . . . .ECPformat. . . . . . . . . . . .,ExpeditingECPS. . . . . . . . . .Revisions. . . . . . . . . . . . .ECPcoverage. . . . . . . . . . . .ix.515151. . . . . . . . . . . . . . . . . . . . . . .(RFW). . . . . . . . . . . . . . . . . . . . . . 5758585858.59.59595959606060.
6.3.35.6.3.45.6.3.5ECP supportingdata. . . . . . . .ECPapproval. . . . . . . . . . .Disapproval. . . . . . . . . . . .Requirementsfordeviations. . . .Restrictionson deviations. . . . .Recurringdeviations. . . . . . . .Deviationformat. . . . . . . . . .Deviationsignificantfactors. . .Deviationreviewand approval. . .Requirementsforwaivers. . . . . .Restrictionson waivers. . . . . .Recurringwaivers. . . . . . . . .Waiverformat. . . . . . . . . . .Waiversignificantfactors. . . . .Waiverreviewand approval. . . . .ConfigurationStatusAccounting(CSA)PurposeofCSA. . . . . . . . . . .CSA requirements. . . . . . .Preferredinformationsystem. . . .Retentionof historicaldatabase.CSAdataelements. . . . - . . . .Contractorfocalpoint. . . . . . .CSA analysisrequirements. . . . .Reportingaccomplishmentof retrofitchanges. . . . . . . . . . . . . .Configurationaudits. . . . . . . .Contractorparticipationandresponsibilities. . . . . . . . . .Subcontractorsand suppliers. . . .Location. . . . . . . . . . .Contractorrequirements. . . . . .Governmentparticipation. . . . . ents. . . . . . .Contractorresponsibility. . . . .Verificationproceduresand requirementsPost-auditactions. . . . . . . . .FCA CertificationPackage. . . . .PhysicalConfigurationAudit(PCA) .Contractrequirements. . . . . . .Contractorresponsibility. . . . .PCA proceduresand requirements. .Post-auditactions. . . . . . . . .PCA CertificationPackage. . . . . x. . .6060606061616161616262626262626363636363636464. .0.6464.s.“.6464656567677070717474748282848989 —
MIL-STD-973CONTENTSPAGEPARAGRAPHNOTES. . . . . . . . . . . . . . . .Intendeduse. . . . . . . . . . .Tailoringguidanceforcontractualapplication. . . . . . . . . . . .Useof.TableII. . . . . . . . . .Explanationof codes. . . . . . . .SamplewordingforcontractualtaskingInvokinga completesetof requirementsTailoringout equirements. . . . . . . . . . .Specifictailoringnotes. . . . . .UseofTableIII. . . . . . . . . .Explanationof codes. . . . . . . ngnotes. . . . . .Data requirements. . . . . . . . .Supersessiondata. . . . . . . . .Subjectterm(keyword)listing. 101. . 101. 108. 108. 115. 115. 117. 118. 119. 120. gureFigureFigureFigureFigureFigureFigureFigure3a. -3b.4.5a. -5g.6.7a. -7k.8a.8b.9a.9b.9C.9d .9e.9f.9g .10.11.12.AdvancechangeStudyNotice. . . . . . . . .42SampleEngineeringChangeProposalMessageFormat. . . . . . . . . . . . . . . . . . .4768-69SampleAuditActionItemsList. . . . . .SampleFCA Checklist. . . . . . . . . . . . .7275-81SampleFCA CertificationPackage. . . . .SamplePCA Checklist. . . . . . . . . . . . .8590-100SamplePCA CertificationPackage. . . . .EngineeringReleaseRecord. . . . . . . . . . ineeringChangeProposal- Page1 . . . . . 163EngineeringChangeProposal- Page2 . . . . . 164EngineeringChangeProposal- Page3 . . . . . 165EngineeringChangeProposal- Page4 . . . . . 166EngineeringChangeProposal- Page5 . . . . . 167EngineeringChangeProposal- Page6 . . . . . 168EngineeringChangeProposal- Page7 . . . . . 169RequestforDeviation/Waiver. . . . . . . . . 175SpecificationChangeNotice. . . . . . . . . 180Noticeof Revision. . . . . . . . . . . . . . 185xi
MI L- ationapplicationsguideforuseof CSA tasksof DD Form 1692withMIL-STD-973. . . . . . S CONFIGURATION MANAGEMENT (CM) PLAN .ENGINEERING RELEASE RECORDS AND CORRELATION OFMANUFACTURED PRODUCTS . . . . . . . . . . . . . .INSTRUCTIONSFOR THE PREPAW4TION OF AN ENGINEERINGRELEASE RECORD (ERR) UTILIZINGDD FORMS 2617AND2617C. . . . . . . . . . . . . . . . . . .INSTRUCTIONSFOR THE PREPA TIONOF AN ECPUTILIZINGDD FORMS 1692 THROUGH 1692/6. . . . .INSTRUCTIONSFOR THE PREPAIU TION OF REQUEST FORDEVIATION/WAIVERUTILIZINGDD FORM 1694. . . . .INSTRUCTIONSFOR THE PREPA TIONOF SPECIFICATIONCHANGE NOTICE UTILIZINGDD FORM 1696. . . . . .INSTRUCTIONSFOR THE PREPARATION OF NOTICE OFREVISION UTILIZINGDD FORM 1695. . . . . . . . .CONFIGURATION STATUS ACCOUNTING (CSA) REQUIREMENTSAND RECORDS. . . . . . . . . . . . . . . . . .CSADATAELEMENTS. . . . . . . . . . . . . . . .REPORTING THE ACCOMPLISHMENT OF RETROFIT CHANGESxii.134.141.170.176.181.186. 202. 225—
ludingof tec Scope.whichareto be selectivelyapplied,as required,thelifecycleof any configurationitem(CI):a.1.2SCOPEwhollyor partiallynon-developmentaldatais requiredor software,orforwithGovernmentfunds,itemswhen thedevelopmentto sticssupport,or interfaceThisstandardADDlicabilitv.activitiesand contractorswhoof configurationmanagement.reasoncontrol.appliesto DepartmentaretaskedwiththeofofThisstandardis applicableYailorinqof requirements.1.3onlyto theextentspecifiedin thetaskingdirectiveor of Work paragraphsandin thetaskingdirectiveoror portionsthereof,Appendices,(See6.2 tionof isstandardto be appliedto a specificprogramwillbetailoredto (includingjointand combinedinteroperability), missioncriticality,and logisticssupportof theCIS.
ents.Theand handbooks.standards,Specifications,2.1.1and handbooksform a rwisethisdocumentto theextentspecifiedherein.theissuesof thesedocumentsare thoselistedin thespecified,issueof theDepartmentof DefenseIndexof SpecificationsandStandards(DODISS)and supplementthereto,citedin lityProgramRequirementsTagsand BandsforPlates,Identificationof EquipmentTechnicalData MIL-STD-970AbbreviationsforUse on Drawings,and on Specifications,Standardsand d StorageIdentificationMarkingof USMilitaryPropertyDefinitionsof eeringManagementWork Standardsand Specifications,Orderof PreferencefortheSelectionof2
mmunitionData CardLot Numberingof Ammunition(Validated)LogisticSupportAnalysisDoD Requirementsfora nmentCorrectiveActionand erial,Aircraft,Gasand icalData PreparedByor For theDepartmentof emSoftwareQualityProgramDoD ardscopiesof federal(Unlessotherwiseindicated,and onDocumentsOrderDesk,BuildingPA 19111-5094.)Avenue,Philadelphia,and militaryavailablefromthe4D, 700 RobbinsThe mentdocumentfernsa partof thisdocumentto ifiedherein.thosecitedin thesolicitation.CATALOGINGHANDBOOK andfromtheCreek,MIIn theeventof a conflict2.2Orderof recedence.betweenthetextof thisdocumentand thereferencescitedNothinginthetextof a specificexemptionhas beenobtained,inwhichcasetheexceptionwillbe identifiedin thetextand citedin thesolicitation.
inDEFINITIONSThethisstandard.as nLogisticsAgencyActivityAddressCode
MIL-STD-973--L.u.DODISS-ofDepartmentand mentFurnishedEquipmentad.HWCIHardwareae.1 CDInterfaceControlDrawingaf.I umentah.ILSIntegratedai.IRSInterfaceRequirementsaj . 5AuditDocumentation
Compliancebc . bf.VECPValueEngineeringbg . tureA documentwhich(ACSN) .NoticeAdvanceChanaeStudv3.2insteadof a preliminaryEngineeringChangeProposalmav be used,to identifyan ideaor problemin orderto obtain(D Form 1692),authorizationto submita formalroutineEngineeringChangeProposal.The initiallyapproved(ABL) .AllocatedBaseline3.3documentationdescribingan item’sfunctional,interoperability,and fsystemor a withinterfacingconfigurationitems,additionaland theverificationrequiredto demonstratedesignconstraints,theachievementof allocated(ACD) eplus6aThe.—.
MIL-STD-973 .3.5A roval/contractualimplementation.The acceptancetheGovernmentof a documentas completeand approveddocumentationis subjectto 3.6Blockchanqeconce t.For hardwareconfigurationitems,an esa number(i.e.,a block)of consecutiveproductionunitsof theconfigurationitemto havean identicalconfigurationon deliveryand in operation.(Usingthisconcept,the productionrun is dividedinto“blocks”of units.Theproductionlineincorporationpointfora proposedECP is delayedto coincidewiththefirstunitof thenextblock,or retrofitisrequiredat leastforallalready-deliveredunitsof thecurrentblock.)For aselinehas nd thesimultaneousimplementationof a numberofroutinesoftwarechangesto minimizethenumberof interimversionsand .SeeMIL-STD-109.3.8Commercialand GovernmentEntitv(CAGE) Code.A fivepositionalphanumericcodewitha numericin thefirstand edto UnitedStatesand thedesignof itemssuppliedto a GovernmentMilitaryorCivilAgencyor assignedto UnitedStatesand ctorsin themechanicalinterchangeof datarequiredby MILSCAP and theService/AgencyAutomatedData Processing(ADP) systems.The dbase.byA collectiona computer.3.10Commterdatadefinition.3.11Com onfigurationComputeritemSoftwarethatisofSeedataina mputersoftware.ItemSeeDoD-STD-2167.(CSCI).A
MIL-STD-973TechnicaldataorCom tings,regardlessof media,information,design,or detailsof apabilitiesand limitationsof thesoftware;software;or prov
management as they apply to defense materiel items. Configuration management is a management discipline applied to configuration items (CIS) over their life cycle to ensure that the characteristics of CIS meet defined user requirements. 5. configuration management requi
