NOT MEASUREMENT SENSITIVE MIL-STD-973 17 April 1992 SUPERSEDING (See section 6.

4)

MILITARY STANDARD
CONFIGURATION MANAGEMENT

AMSC No. D6728

AREA CMAN

Distribution Statement A: Approved for public release; distribution is unlimited

FOREWORD 1. Departments This Military and Agencies Standard of the is approved Department for use Defense by all (DoD) .

of

MIL-STD-973 is jointly sponsored by the Office of the 2. The Secretary of Defense and the Joint Logistics Commanders. primary purpose of this standard is to consolidate configuration management requirements which were previously scattered throughout several configuration management standardization As a result of this consolidation effort, MIL-STD-973 documents. significantly reduces the number of configuration management Those standards that are standards in the DoD inventory. Although superseded by MIL-STD-973 are identified in Section 6. consolidation is the primary purpose of this initiative, Some requirements from MIL-STD-973 does contain new material. superseded standards have been modified to clarify ambiguities or Some obsolete or redundant to resolve inconsistencies. requirements from superseded standards have been modified or Computer-aided Acquisition and Logistic deleted entirely. Support (CALS) has been addressed in this issue to the extent some new requirements have been identified Alsot practicable. and included. This standard has been developed for use by both 3. Toward this end, the term contractors and Government activities. has been used throughout to denote an activity “contractor” performing any of the requirements of this standard. A can be either a contractor or Government activity. “contractor” Wherever it is necessary to differentiate between the contractor Government Contracting and the tasking activity (i.e. , the Activity which awards a contract to a contractor, the Government Program Management Office which tasks another Government activity, or a contractor which tasks a subcontractor) , the term has been used throughout to denote the activity “Government” imposing the requirements of this standard on the other. 4. This management as Configuration configuration the characteristics standard defines the ~equirements of configuration they apply to defense materiel items. is a management discipline applied to management life cycle to ensure that over their items (CIS) of CIS meet defined user requirements. requirements for software have Where requirements are common to they are shown as requirements not common to both hardware and

configuration management 5. been included in this standard. both hardware and software items, Where requirements are for CIS.

ii

MIL-STD-973
--

software items, they are shown as requirements software configuration items (CSCIS) or hardware items (HWCIS) , as applicable.

for

computer configuration

6. Beneficial comments (recommendations, additions, deletions) and any pertinent data which may be of use in improving this document should be addressed to: Chief, Policy Division, CALS Evaluation and Integration Office, Leesburg Pike, Suite 1403, Falls Church, VA 22041-3466, the self-addressed Standardization Document Improvement (DD Form 1426) appearing at the end of this document or letter.

Plans and 5203 by using Proposal by

iii

MIL-STD-973

CONTENTS PARAGRAPH 1.
1.1

PAGE SCOPE . . Scope . Applicability Tailoring . . of . . . . . . . . . . . . . . requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
q

1.2 1.3 2. 2.1 2.1.1 2.1.2 2.2 3. 3.1 3.2 3.3 3.4 3.5 3.6 3.7 3.8 3.9 3.10 3.11 3.12 3.13 3.14 3.15 3.16 3.17 3.18 3.19 3.20 3.21 3.22 3.23 3.24 3.25 3.26 3.27 3.28 3.29 3.30 3.31

. . . . . . . . .

1 1
1 1

APPLICABLE DOCUMENTS . . . Government documents . . Specifications, standards, Other Government documents Order of precedence . .

. . . . . . . . . . . . and handbooks . . . . . . . . . . . . .

2 2 2 3 3 4 4 6 6 6 7 7 7 7 7 7 7 7 7 8 8 8 8 8 8 8 8 9 9 9

DEFINITIONS . . . . . . . . . . . . . . . . . Acronyms used in this standard . . . . . . . Advance Change Study Notice (ACSN) . . . . . Allocated Baseline (ABL) . . . . . . . . . . Allocated Configuration Documentation (ACD) Approval/contractual implementation . . . . Configuration Baseline . . . . . . . . . . . Block change concept . . . . . . . . . . . . Classification of defects . . . . . . . . . Commercial and Government Entity (CAGE) Code Computer database . . . . . . . . . . . . . Computer data definition . . . . . . . . . . Computer software . . . . . . . . . . . . . Computer Software Component (CSC) . . . . . Computer Software Configuration Item (CSCI) Computer software documentation . . . . . . Computer Software Unit (CSU) . . . . . . . . Configuration . . . . . . . . . . . . . . . Configuration audit . . . . . . . . . . . . . . . . Configuration control Configuration Control B;a;d.(;CB). 1 . . . . Configuration documentation . . . . . . . . Configuration identification . . . . . . . . Configuration Item (CI) . . . . . . . . . . Configuration Management (CM) . . . . . . . Configuration Management Plan (CMP) . . . . Configuration Status Accounting (CSA) . . . Contractor. . . . . . . . . . . . . . . . . Critical item . . . . . . . . . . . . . . . Data. . . . . . . . . . . . . . . . . . . . Defect. . . . . . . . . , . . . . . . . . . Deficiencies. . . . . . . . . . . . . . . . iv

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
q

_.

10 10 10 10 10 10 10

MIL-STD-973 CONTENTS PARAGRAPH 3.32 3.33 3*34 3.35 3.36 3.37 3.38 3.39 3.40 3*41 3.42 3*43 3.44 3.45 3.46 3.47 3.48 3.49 3.50 3.51 3.52 3.53 3.54 3.55 3.56 3.57 3.58 3.59 3.60 3.61 3.62 3.63 3.64 3.65 3.66 3.67 3.68 3.69 3.70 3.71 3.72 3.73 3.74 3.75 3.76 Design change. . . . . . . . . . . . . . . Developmental configuration . . . . . . . . Deviation. . . . . . . . . . . . . . . . . Engineering change . . . . . . . . . . . . Engineering change justification code . . . Engineering change priorities . . . . . . . Engineering Change Proposal (ECP) . . . . . Engineering Change Proposal types . . . . . Engineering release . . . . . . . . . . . . Engineering Release Record (ERR) . . . . . Evaluation . . . . . . . . . . . . . . . . Exchangeability of items . . . . . . . . . Firmware . . . . . . . . . . . . . . . . . Fit. . . . . . . . . . . . . . . . . . . . Form . . . . . . . . . . . . . . . . . . . Function . . . . . . . . . . . . . . . . . Functional area. . . . . . . . . . . . . . Functional Baseline (FBL) . . . . . . . . . Functional characteristics . . . . . . . . Functional Configuration Audit (FCA) . . . Functional Configuration Documentation (FCD) Hardware . . . . . . . . . . . . . . . . . Hardware Configuration Item (HWCI) . . . . Integrated Logistics Support (ILS) . . . . Interchangeable item . . . . . . . . . . . Interface. . . . . . . . . . . . . . . . . Interface control . . . . . . . . . . . . . Interface Control Drawing (ICD) . . . . . . Interface Control Working Group (ICWG) . . Interoperability . . . . . . . . . . . . . Item . . . . . . . . . . . . . . . . . . . Life cycle . . . . . . . . . . . . . . . . Lifecyclecost. . . . . . . . . . . . . . Manufacturer’s code . . . . . . . . . . . . Material . . . . . . . . . . . . . . . . . Non-conformance. . . . . . . . . . . . . . Non-developmental Item (NDI) . . . . . . . Non-recurring costs . . . . . . . . . . . . Notice of Revision (NOR) . . . . . . . . . Original . . . . . . , . . . . . . . . . . Physical characteristics Physical Configuration Aud;t.(~C~)” 1 1 1 R Product Baseline (PBL) . . . . . . . . . . Product Configuration Documentation (PCD) . Recurring costs . . . . . . . . . .. . . . v . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R . . . PAGE

10 10
10 10 10 10 10 10 10 10 12 12 12 12 12 12 12 12 12 12 12 12 13 13 13 13 13 13 13 13 13 13 13 13 14 14 14 14 14 14 14 14 15 15 15

0 .85 3. . . . . . . .89 3. . . . . .81 3. Replacement item . .1 4. . .6 4. .1 5. .87 3. .80 3. . . . . . . . . . . . . . .3. . . . . . . . . . . . . . . . . . . .98 4. . Configuration vi .2. .91 3. . . . . 24 24 24 24 24 24 25 . . . . .15 . . . Technical documentation . . Specification Change Notice (SCN) . . . . .90 3. . . . . . . .1 5. . . . . . Purpose. . . . . Automated processing and submittal of data . . . . . . . . . . . . . .3 5. . . . . .*. . . . . . . .78 3. . . 25 . . . . . . . . . . . . . . . . . . . . .1 5. . . . . Configuration audits . . . . . .86 3. . . . . . . Retrofit . . . . . Specification . . . . .3. . . . . . . . . . . . . . . .94 3. . . . Configuration identification . . PAGE . . Technical data package . Interactive access to digital data . Data distribution/access . . . . . . . . . . . . . . . Configuration management administration Contractor’s CM Plan . . . . Purpose of configuration identification Item selection . Substitute item . . . . . . . . . . . . . Version. . . . . . Technical reviews .93 3. . . .82 3.7 5.3 5. . . . . . . . . . . Unit . . . . . . . . . . . . . . Support equipment . . . . . . . . . . . Work Breakdown Structure (WBS) . .3. . .2 4. . . . . . . .3. . 26 — . . . . .2. .3.2 5. . . . . . . . . . . .95 3. Configuration control .2 4.2 5.96 3. . . . . . . . Configuration Status Accounting (CSA) . . . . . .3 4. . . . . . . . .79 3. . . . . . . . . . . . .92 3. . . . . . . . . . . . . . . Work Breakdown Structure (WBS) . . . . . . Technical reviews . . . . . . . . . . .2 Release. . . . . . . . . .MIL-STD-973 CONTENTS PARAGRAPH 3. . . . . . . Repair . . .77 3. . . . . . . . .5 4. . . . Survivability . . . Support Computer-aided Acquisition and Logistic (CABS ) . . . .83 3. . . . . . . . . Work breakdown structure element . . . . . . System . . . Rework . . . . . . . . . . . . . . . . . . . . . Planning . . . . . . . .3 4. . . . . . . . . . . . . . . . . . . .97 3. . . . . . . . . . . . . . . Technical data . . q                 15 15 15 15 15 15 15 15 15 15 15 16 16 16 16 17 17 17 17 17 17 18 18 18 19 19 19 20 21 21 22 22 GENERAL REQUIREMENTS . . . . .84 3. . . . . . . . . . . .1 4. . . . . . . . . . . Training equipment . Software . . . . . . . . . .2. . . . . . . . . . . . . . . . . . .88 3. . . . . . . 4. . . . . 5. . . . . . . . Configuration identification . . . . . . . . . . . Waiver . . . . . . . . . DETAILED REQUIREMENTS . . . . . .4 4. . . . . . . . . Basic requirements . . . . . . . . .

2. . .7 5. .3. .2 5. . .4. .3. . . . .2. . . . . . . Software identifiers . . Reuse of serial numbers . .2 3. . . .. .2 5. . . . . .5. . . . . .4. . . . . .6. . Purpose of configuration control . . . . . . . . . . . . . . . . .6. .1 5. . . . . . . . . . .3 3.1. . . . 5. . .3. . . . .1 PAGE Developmental configuration. ._.6. . . .6.3. . . . . .3. .3 3. . . .4. . . .5. . . . .3 5. . . Specification release and approval . .3. .4 5. . .2.MIL-STD-973 CONTENTS PA RAGRAPH 5. . .2 5. . .6.6 5. . . . . .3. . . . . . .7.3 5. . . . . . . . . . . . . . . . . . . Configuration baselines .6 5.’. .1 5.2 5. . Firmware labeling.2 . . .3. . . . .. . .2 5. . . COTS. Administrative requirements . . 5. .3. . 5. . Change release . . . . . . . 3. .3. . . . . . .2. . 5.3. . . . . . . .3.2 5. . . . .3. . . .3. .5.3. . . .6. .1 5. 1. . Functional Configuration Documentation (FCD) . .7. . . .1 5. . 5. . . . . . . . Requirements for an Interface Control Working Group (ICWG) . . . ICWGmembership. .6. . . . . . . .3. . . .7. . .3 5. . . .2.1 5. . .4. . .3. .3. .7. . . Drawing library. . . . . . . . . . . . . . . . .3. . . ICWGChairmanship . . . . . .4. . Government serial numbers . . vii 26 26 26 26 27 27 27 27 28 28 28 28 29 29 29 29 29 30 30 30 30 30 30 30 31 31 31 31 32 32 32 32 32 33 33 33 33 34 34 34 . . . . . . . . . . .6. . .4 ‘-. . . . . .4.7. . . . and PDI labeling Interface management . .3. . Initial release. . . . . . . .3. . . Software Development Library . . . . . . .1. . . . .5. . . Serial/lot numbers . . The engineering change process .1 3. .2. . Requirements for Engineering Release Records (ERRs) . . . . . . . .2 5. .2. .1 5.5. . . . . . . . . . Configuration baselines and their configuration documentation. . . . . . . . . . . Part/item identification numbers .y . . . Configuration identifiers. .3. . . . .5 5. . . .3.6. . .3. 5.. . . CAGE Code. . Government type designators and nomenclature . .7 5. Requirements for Engineering Changes . . . . . . . . Documentation libra. . . . .1 5.6.4 5. . Product Configuration Documentation .4 3. 5. .4. UseofERRs. . . . . .2 5. . . . Allocated Configuration Documentation . . . . . Configuration control . . . . . . . . . . .6. . . . .6.3. NDI .3. . . . . . . . .2 5. . . .7.3.5 5.1 5.4. . . . . Maintenance of configuration documentation . Software marking and labeling. . . .2. Engineering release and correlation of manufactured products . .6. . .2 5. . . . . . . .3. . .7. . . . . . . Consolidation of multiple changes into a single ERR. .6. . . . .3. . .4. . . . . . . . . . . . Interface requirements . .3. . . Document numbers .3.3 5. . . .5. . . . . . Product identification/marking . . . . . . . . .1 5. . . . .3. .1 5. . . . . . . .

. Related engineering changes .3. . . . .2.4 5.2 5. . . . . . . . .4 5.2. . . 5. . .2. .1 1. . . . . . .5. .6 5. . . . . . .4.3 5. .3 5. . . . . .3 5. . . .2. .2. . . Classified data . . . .several contractors .2.2. .2. .2. . Classifying engineering changes to a privately developed item . .1 5. . .3.4 1. Use of preliminary ECPS (Type P) . . . . .3. . .2. .4. .2.4.4.4.2. . . . . .5 5.2. . . .3. . . . Class I ECP justification codes .2. . Related engineering changes .1 5. Class II engineering change format . .4. .3 5.5. Class I ECPtypes . .4. Use of Advance Change Study Notice (ACSN) Use of Formal ECP (Type F) .2.4. .2.prime/ subcontractor coordination . . . . . .2. .3.2. . . . .1 5.4. . .4.3. . . Class I engineering changes during concept demonstration and validation exploration.single prime prime Related engineering changes .4. . . . . .2. Supporting data . . . . . . . . . . Class I ECP decisions . . .2.3. . .5 5. .2. . .2. . .4 5. . . . . . . . . . .5. .6. Preliminary change proposal . . Same engineering change . . .4. . Class I engineering changes during engineering and manufacturing development Class I engineering changes during production and support . .3. .4. viii . . . . . . . .4.2 5. .4.3. .3. . . Class I compatibility engineering changes Disapproval of ECPS . . . .4. . . .2 5. . . .4. 5. .4. . . .3. . . .3. . .2 5. . . .3.4. . . .4 1. . Class 11 justification codes . . . ECP authorization . Unrelated engineering changes .4.2. . .4. . . . Content of Engineering Change Proposals (ECPS) . .4. .4. Related engineering changes .4. Class I Engineering Change Proposals . .3.1 5.2. .1 5.6. . . .3. . . .3. Format for Class I engineering changes . . .3.2.2.3.3. .4. . . . .3. .1 5.3 5. . . .2. 5.3.4. Class I engineering change priorities . Revisionsof ECPS . . . . .2. .3 5. .4.2. .2 1.4. .separate primes. .2. . . Target for technical decision on Class I ECPS.3. . . .3.4.single multiple procuring activities . . . . 5. . . . . .2.1 1. . .4.6. .2. Class II engineering changes .2 — . . 5. .1 5.2.4. . . .4.4.2 Classification of engineering changes .4. . . . . 5. .2. . . .2.4. . .3 1. . . . .3. . . .3.2 5. . .2.1 5. .6. 5. . .4. .2.3.2.3. .6. .2. . .2. PAGE 34 36 36 36 36 37 37 37 38 38 38 38 39 39 41 41 41 41 43 43 45 45 48 48 48 49 49 50 50 50 50 50 50 51 - 3.4.3.MIL-STD-973 CONTENT PARAGRAPH 5. . .2 5. Same engineering change . .2.3. . . . Expediting Class I engineering changes with priority of emergency or urgent . . .3.

4. . .4 Concurrence in Class II changes . . . Configuration control (short form procedure) . . . .4.4. Requirements for Requests for W~iver Restrictions on waivers .3.3.3 5. Requirements for Specification Change Notices (SCNs) . . . . . . . . . .6. . . . .3. . . .8. . . . Minor . . SCNcoverpage. . . . . . . . . . . . . . .Expediting ECPS . .2 5. .1 5. . . .4.6. . Minor . . . . . . .1 5.4. . . . .5. . . . . . .4.4. . . Classification of waivers . . .3 5. . . . Critical. Non-custody of the original drawings Requirements for Requests for Deviation (RFD) . . . . . . . . . . . . .1 5.6 5. . . . .4.5 5.4. .4. . . . . .4. . .4 5. .4. .4. . . .4. . . .6.4. . . . . . . . . .4. . . .4. .4. ECPformat.4.5 5. . . . . . . . . . ECPcoverage. . . . . . . .1 5. . . . . . .8. . . . . .4.4. . . . . . . . . .MIL-STD-973 CONTENTS PARAGRAPH 5. .4.2. . . .4 5. . . . .3. .4. . . . . . . . . Critical and major deviations . . . . .4.8. . Major . . . . Attachments to proposed SCN . .3.4. . ix . . .5. . . .4. .3.4. . . . . . . . . . . . . . . . . . . . . . . .3 5. . . . . Classification of deviations . . .7 5.2. . . . . .8. . . Approval of Class 11 changes . . . . . . . .2 5. . . .2. . . . Critical and major waivers . .1 5. . . . . . . . . . . . . . . Parts substitutions .2 5. . . .4. . . .4. . .2 5. . . . .5 5.3.4. . . .4.3.8 5. . . .3.4. .4. . . . .4.4. . .3 5. . Requirements for Notices of Revision (NORS) . . . . .1 5. . . . . Purpose . . . . .2. . . . .2 5. . . . . . . .4. . . . . . . .2 5. . .4. . . . . . . . . . . . . . . .4. . . . .3 5. . . . . . . . . . . . . . . . .8. . . . . . . . . . . Minor deviations . . . .4 5. .2 5. . .1 5. . . .1 5. .4. Disposition of deviations . Format. . . . Restrictions on deviations . .4.8. . . . . .3. .2. . .1 5. . . . Recurring deviations .6. . . . . . .PAGE 51 51 51 51 52 52 52 52 53 53 53 53 53 54 54 54 54 54 55 55 55 55 56 56 56 56 57 57 58 58 58 58 59 59 59 59 59 60 60 60 L .3. . . . . . . . ApprovedSCN. . . . . . . .3. . . . . .3. . . .4 5.4. Format. . . . . . . . Disposition of WZtiVerS . . Changed pages . . . . . . .3.2. Minor waivers . . .6. . . . . (RFW) . . . Supersession. . . . .3. Critical. . . Requirements for ECPS . . . . . . . . . Major .2 5. . . .4. .5. . . .4 5. .4.5. . .4. .4. . . . Revisions .4. . .3 5. . . .4. . . .4. . . . .2. . . . . . . . . . . . . .5 5.2 5. . . . . . . Recurring waivers .4. . . . .3 5. .3.5 5.4. . .4. .3 5.4. . . . . . . .4. . .

. . . . . . . 0 . . . . .8 5. . . . . . . . . .3 5. . . . . .4 5.4. . . . . . . . . . .5. . . . . .5 5. . . .2. “ . .8. 60 60 60 60 61 61 61 61 61 62 62 62 62 62 62 63 63 63 63 63 63 64 64 64 64 64 64 65 65 67 67 70 70 71 74 74 74 82 82 84 89 89 — . . . . . . . Contractor requirements . CSA analysis requirements . . Contract requirements . Verification procedures and requirements Post-audit actions . . PCA procedures and requirements . . . Contractor focal point . .3 5. .4. . .6. . . . .6. . . . .4 5. Deviation review and approval . . . . Retention of historical data base . .2.6. .2. q . . . . . . . . . . .6. ECPapproval. . .3. .2 5.3 5. . . . . . Recurring waivers . .5. . .6. . . . . . .. Post-audit actions . . .2.4. . . .8. .4 5. . . FCA Certification Package . . . .5. .2 5. .4. q .8. . . . . . . .8. .4. . . s . . . Restrictions on waivers .7 5. . .6. . .6 5.1. .6. . Disapproval .6.3. PCA Certification Package . .3 5. .8. . . . . . . . .3 5. . .3. . .5. .4. . .1.7 5.1 5. . . . . . .1 5. . . . . q . . . . . . .3. . . .8. Contractor responsibility . . . . . . . .8. . .4 5. . . . .5 5. . .4. . . . .2 5. . . . . . . . .1 5. . . . . . .1. . . . . Functional Configuration Audit (FCA) Contract requirements .4. .8. . . . Contractor responsibility .3. . Deviation significant factors .4. . . . . Physical Configuration Audit (PCA) .5.3. . .8. . Location. . . .5 ECP supporting data . . .6 5. CSAdata elements . . . .2. Preferred information system . . . Government participation . .3.4. . . .4. . . . .2 5.8. . . Configuration Status Accounting (CSA) Purposeof CSA. . Waiver format .6. . . Subcontractors and suppliers . x . . . . . . . .6.1 5. . . . . . .6 5. .5. .3 5. q . . . . . Waiver review and approval . . . . . . .MIL-STD-973 CONTENTS PARAGRAPH 5. .2 5. . . . . .3 5. . . . .1 5. . . . . Requirements for waivers .4.4. . . . . . q . . . . Recurring deviations . . . .1 5.4 5. . . . . . . . .4.3.5 5. . . . . . .8. .5.4 5.5 5. . . . .4. . . . . Reporting accomplishment of retrofit changes . . .5. CSA requirements . . .4.3. . . . q q - .4. .6. . .4. .1.2. . . . .6. . Deviation format . Requirements for deviations .8. . .8. . q . . . . . . .4 5. .5 5. . .6.3 5. . . . .2. . . Contractor participation and responsibilities . . . Restrictions on deviations .8.4. Waiver significant factors . .3. .6. .2 5.1 5. . . Configuration audits .4.5 5. . . . .8. . .2 5.6.6. . . . . . . . . .6. . . . . . . .2. .

. . 2. . . . 115 .1. . . . 8b. . 169 Request for Deviation/Waiver . . 120 . . . . .1. . . . .1 6. .Page 3 . . . . . . . . . . . 9b. .2. Sample wording for contractual tasking Invoking a complete set of requirements Tailoring out specific requirements Identifying specific applicable requirements. .2 6. 9e. . . 117 . . . . . . . .1 6.Page 7 . . 185 NOTES . . -3b. . 9a. . . .3 6. . .2.2 6. 12. . . 115 . . . . 9g . Explanation of codes . . . . . . 165 Engineering Change Proposal . . .2 6. . . .2.3 6. 47 68-69 Sample Audit Action Items List . .Page 1 . 167 Engineering Change Proposal . . . . . . . . Engineering Release Record . .3 6. .1. . . 108 . . . . . . -5g. . . . . .3 6. . . . . . . 101 101 101 107 107 108 . .. . . . . .2. . . . 6. . . Advance change Study Notice .1. . . .Page 5 . .MIL-STD-973 CONTENTS PARAGRAPH 6. . .1 6. .140 Engineering Change Proposal . . . 139 Engineering Release Record Continuation Page. Sample FCA Checklist . 3a. . . . . . . . . 5a.2. . 175 Specification Change Notice . .1. . . . 6. . . 11. . . . . . Specific tailoring notes . . .Table II . . . . 72 75-81 Sample FCA Certification Package . . . Tailoring guidance for contractual application . . . . . . . . . . . 120 G- xi . . . . . .Page 6 .1. . . . 8a. . . 7a. . . PAGE . . Useof. . .2 6. . . 101 .1 6. Sample PCA Checklist . . . 9f. 85 90-100 Sample PCA Certification Package . .2.5 FIGURE Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure 1. . . . .2. . . . . . . .2 6. Supersession data . 163 Engineering Change Proposal . . . . . . . . . . 118 . . . . .2. . .2. . . . . . . . . . UseofTableIII .2.2. . . Explanation of codes . 166 Engineering Change Proposal . . Subject term (key word) listing . . . . . . . . .Page 2 . . . . . . . . . . . . . . . . . . . . . .101 . Sample wording for contractual tasking Specific tailoring notes . .2. . . . . . . .2. 4.1 6.2. . 164 Engineering Change Proposal . 108 . . . . . . . . . 168 Engineering Change Proposal . . . . . . 42 Sample Engineering Change Proposal Message Format. 10. . . . 119 . . Data requirements . . . . Intended use. . . . . . .2. . . 9C. 180 Notice of Revision . . .Page 4 .4 6. . . . 9d . . . .2. . .2. . . . . . . . -7k.

. . . . . . . . . . . . . CSADATAELEMENTS . . . . 202 . . . INSTRUCTIONS FOR THE PREPARATION OF NOTICE OF REVISION UTILIZING DD FORM 1695 . . INSTRUCTIONS FOR THE PREPA~TION OF SPECIFICATION CHANGE NOTICE UTILIZING DD FORM 1696 . . . . . . . . . 122 129 Life cycle Tailoring Application applications guide for use of CSA tasks of DD Form 1692 with MIL-STD-973 . INSTRUCTIONS FOR THE PREPAW4TION OF AN ENGINEERING RELEASE RECORD (ERR) UTILIZING DD FORMS 2617 AND2617C . .MI L. 141 170 176 181 . . . . . . . . CONFIGURATION STATUS ACCOUNTING (CSA) REQUIREMENTS AND RECORDS. . . . . .STD-973 CONTENTS TABLE I II III Appendixes A B CONTRACTOR’S CONFIGURATION MANAGEMENT (CM) PLAN . . . . . . . . . . . . . . . . . . . 46 102 116 c D E F G H I J . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225 xii — . . . INSTRUCTIONS FOR THE PREPA~TION OF AN ECP UTILIZING DD FORMS 1692 THROUGH 1692/6 . . . . . . . . . . . ENGINEERING RELEASE RECORDS AND CORRELATION OF MANUFACTURED PRODUCTS . . . . . . . . . .186 .134 . . . INSTRUCTIONS FOR THE PREPAIU+TION OF REQUEST FOR DEVIATION/WAIVER UTILIZING DD FORM 1694 . . REPORTING THE ACCOMPLISHMENT OF RETROFIT CHANGES . . . .

as required. specifically identify the appropriate applicable paragraphs and in the tasking directive or or portions thereof. or interface This standard ADDlicabilitv. and logistics support of the CIS.2 Defense application configuration management for logistics support. of of b. the life cycle of any configuration item (CI): Developed including of tec~ical equipment Designated integration.MIL-STD-973 1. items when the development to support off-the-shelf reason control. (See 6. mission criticality. intended use (including joint and combined interoperability) . Appendices. complexity.1 requirements throughout a. wholly or partially non-developmental data is required or software. 1.2 for specific tailoring guidance.3 only to the extent specified in the tasking directive or contract Contracts invoking this standard will Statement of Work (SOW). activities and contractors who of configuration management. size. or for with Government funds. This standard defines configuration management Scope. which are to be selectively applied. .) The contract SOW. applies to Department are tasked with the --- This standard is applicable Yailorinq of requirements. selection of necessary configuration management requirements from this standard to be applied to a specific program will be tailored to suit the life-cycle phase. 1. SCOPE 1.

Order of Preference for the Selection of 2 . and on Specifications.1 and handbooks form a part of following specifications. Government APPLICABLE DOCUMENTS 2. 2. Specifications. Preparation of Parts Control Program Standards and Specifications.1 documents. standards. cited in the (See 6. MILITARY SPECIFICATIONS Quality Program Requirements Tags and Bands for Plates. Identification of Equipment Technical Data Packages. The and handbooks. and Related Terms (Notice of Validation) Specification Practices Engineering Management Work Breakdown Structures for Defense Material Items System Safety Program Requirements Military Specifications and Associated Documents.MIL-STD-973 2. Standards and Technical Documents Engineering Drawing Practices Quality Assurance Terms and Definitions Marking for Shipment and Storage Identification Marking of US Military Property Definitions of Item Levels. Unless otherwise this document to the extent specified herein. standards.1. issue of the Department of Defense Index of Specifications and Standards (DODISS) and supplement thereto. Item Exchangeability. Models.2) solicitation. General Specification for Inspection System Requirements MIL-Q-9858 MIL-P-15024 MIL-T-31OOO MIL-I-45208 MILITARY STANDARDS MIL-STD-12 MIL-STD-1OO MIL-STD-109 MIL-STD-129 MIL-STD-130 MIL-STD-280 MIL-STD-490 MIL-STD-499 MIL-STD-881 MIL-STD-882 MIL-STD-961 MIL-STD-965 MIL-STD-970 Abbreviations for Use on Drawings. the issues of these documents are those listed in the specified.

Building PA 19111-5094. The following other Other Government documents. those cited in the solicitation. CATALOGING HANDBOOK H4/H8 (Copies of Commander. 700 Robbins copies of federal (Unless otherwise indicated. and handbooks are specifications.1. MI In the event of a conflict 2. . 49017-3084. Assignment of Marking Technical Data Prepared By or For the Department of Defense Defense System Software Development Defense System Software Quality Program DoD Automated Information Systems (AIS) Documentation Standards and military available from the 4D. herein.MIL-STD-973 -. however. between the text of this document and the references cited Nothing in the text of this document takes precedence.) Cataloging Defense Handbook Government for Commercial Entity Codes and Handbook H4/H8 Logistics Services are available Center. Philadelphia. Aircraft. Serial. 2.2 Government document ferns a part of this document to the extent Unless otherwise specified. supersedes applicable laws and this document. in which case the exception will be identified in the text and cited in the solicitation. standards. the issues are specified herein. Battle from the Creek.2 Order of ~recedence. MIL-STD-1167 MIL-STD-1168 MIL-STD-1388-1 MIL-STD-1388-2 DOD-STD-1467 MIL-STD-1520 MIL-STD-1559 MIL-STD-1806 DOD-STD-2167 DOD-STD-2168 DOD-STD-7935 Ammunition Data Card Lot Numbering of Ammunition (Validated) Logistic Support Analysis DoD Requirements for a Logistic Support Analysis Record Software Support Environment Corrective Action and Disposition System for Nonconforming Material Numbers. Gas and Engine Module Turbine Engine. Standardization Documents Order Desk. regulations unless a specific exemption has been obtained. ) Avenue.

1 Acronyms standard are a. Administration Control Design Data Review Requirements Item Management Status Software Status Software Description Logistics of of Agency Defense Defense List Accounting Component Accounting Configuration Report Item Activity Address Code . i. Information Management Systems Control List and Government Entity Office Board f. o. j. s. 9. n. c. h. P“ q“ r. k. m. 3. as follows: Baseline Configuration Change Study ABL ACD ACSN AIS AMSDL CAGE CAO CCB CDR CDRL CI CM CSA Csc CSAR CSCI DID DLA DOD DODAAC- Allocated Allocated Advance Automated Acquisition Requirements Commercial Contract Configuration Critical Contract Configuration Configuration Configuration Computer Configuration Computer Data Defense Department Department Item Documentation Notice System and Data d. t. 1. DEFINITIONS The acronyms used in this used defined in this standard. b.MIL-STD-973 3. e.

ar. ai. L. ae. aa. ao. Analysis Board Sets Item Training Non-Developmental Notice National Product Physical Product of Revision Stock Baseline Configuration Configuration Number Audit Documentation 5 . ac. af. ag. an. LSA ak. x. ah. aj . ap. Data Use Identifier Change and Baseline Configuration Configuration Furnished Furnished Configuration Control Control Design Logistics Requirements Support Review Data Equipment Item Drawing Working Document Support Specification Group Audit Documentation Proposal Development w. aq. ab. ad. al. Y“ Engineering Engineering Functional Functional Functional Government Government Hardware Interface Interface Interface Integrated Interface Logistics Material Mobile Manufacturing z. DODISSDUI ECP EMD FBL FCA FCD GFD GFE HWCI 1 CD I CWG IDD ILS IRS of Department and Standards Defense Index of Specifications v. MRB MTS NDI NOR NSN PBL PCA PCD -. am.MIL-STD-973 -- u.

aw. bb. and interface characteristics that are allocated from those of system or a higher level configuration item. Documentation approved changes. PDI PDR PPSL RFD RFW SPS SDL SCN sow TCTO Privately Preliminary Program Request Request Software Software Specification Statement Time Test Version Value Value Work Developed Design Parts For For Item Review List Selection Deviation Waiver Product Development Specification Library Notice Change of Work Compliance Readiness Technical Review Order bc . Allocated Baseline 3. be. au. av. to identify an idea or problem in order to obtain (D~ Form 1692). The a 6 . bf. ax. VDD VE VECP Description Engineering Engineering Breakdown Document Change Structure Proposal bg .2 instead of a preliminary Engineering Change Proposal mav be used. the achievement of those specified characteristics.MIL-STD-973 as. authorization to submit a formal routine Engineering Change Proposal. at. ba. WBS A document which (ACSN) . interoperability.3 documentation describing an item’s functional. The initially approved (ABL) . TRR bd. az.4 approved Allocated allocated Configuration baseline plus (ACD) . interface requirements with interfacing configuration items. ay. .—. additional and the verification required to demonstrate design constraints. Notice Advance Chanae Studv 3. 3.

(Csc) .8 Commercial and Government Entitv (CAGE) Code. ) For computer software configuration items. A Component Configuration computer software. once the product baseline has been established. DoD-STD-2167. 2AAA5). .g. software.9 capable 3. 3.5 A~~roval/contractual implementation. 3*7 Classification of defects. or retrofit is required at least for all already-delivered units of the current block. The acceptance the Government of a document as complete and suitable for its intended use. the production run is divided into “blocks” of units. For hardware configuration items. The CAGE data provides the data base for the Cataloging Handbook H4/H8 Series.11 3. A fiveposition alphanumeric code with a numeric in the first and last positions (e.13 configuration of Computer data being processed Commter Com~uter Computer Computer item data base.. primarily for identifying contractors in the mechanical interchange of data required by MILSCAP and the Service/Agency Automated Data Processing (ADP) systems. 2AA45. The production line incorporation point for a proposed ECP is delayed to coincide with the first unit of the next block.. by A collection a computer. --- 3. See See of data in a form definition.e. 27340.12 3. Item See DoD-STD-2167. Approval/contractual implementation of configuration documentation means that the approved documentation is subject to the Government’s configuration control procedures. 2A345. (Using this concept. Software Software that is DoD-STD-2167. a block) of consecutive production units of the configuration item to have an identical configuration on delivery and in operation.10 3. an engineering change implementation concept that designates a number (i. assigned to United States and Canadian organizations which manufacture and/or control the design of items supplied to a Government Military or Civil Agency or assigned to United States and foreign organizations. the concept requires the accumulation and the simultaneous implementation of a number of routine software changes to minimize the number of interim versions and related documentation. by 3.MIL-STD-973 >. 3. (CSCI). See MIL-STD-109.6 Block chanqe conce~t.

configuration See “Functional audit”. 3. audit” 3. Confiu uration 3.16 functional and physical characteristics of existing or planned software or a combination thereof as set hardware. explains the capabilities and limitations of the software. and product baselines. namely the functional. configuration documentation are the functional configuration the allocated configuration documentation. recommends approval or disapproval of proposed waivers and deviations from a CI’S current approved configuration documentation. software.17 and Configuration “Physical audit. constitute the current approved from those baselines.19 justification. The three levels of evolutionary increasing levels of detail. See DoD-STD-2167. evaluation. and maintained through three distinct developed. or provides operating instructions for using or supporting computer software during the software’s operational life cycle.21 documentation that identifies and defines the item’s functional The configuration documentation is and physical characteristics. approval or disapproval and the implementation of all approved of proposed changes. allocated. changes. 3. a technical The Configuration documentation.MIL-STD-973 Technical data or Com~uter software documentation. 3. approved. information. plus approved changes CI’s life cycle.20 Configuration Control Board of technical and administrative representatives who recommend approval or disapproval of proposed engineering changes to a CI’S The board also current approved configuration documentation. or details of computer which documents the requirements. design. There are three formally designated configuration documentation. configuration Configuration documentation Conficiuration baseline. 3. A board composed (CCB) . in the configuration of a CI after establishment of the configuration baseline(s) for the CI. coordination. control.14 including computer listings. the Configuration. firmware.18 formally designated by the Government at a specific time during Configuration baselines. For purposes of this standard. and the documentation. The systematic proposal. 3. regardless of media.15 Com~uter Software Unit (Csu) . configuration baselines in the life cycle of a configuration item. product configuration documentation. 3. forth in technical documentation and ultimately achieved in a product. 8 .

their item an end separate is an use to configuration items. and physical .24 a. and the establishment of configuration ba. the (2) Record and report information needed to manage the data files effectively. and other contract requirements. Configuration identification includes the’ selection of CIS.. 9 .g. the issuance of numbers and other identifiers affixed to the CIS and to the technical documentation that defines the CI’S configuration. As applied to digital data files (See MIL-HDBK-59). working. the release of CIS and their associated configuration documentation. application of selected configuration identification and configuration status accounting principles to: (1) Uniquely identify the digital data files. including the status of updated versions of files. including versions of the files and their status (e. the determination of the types of configuration documentation required for each CI. including the status of proposed changes and implementation status of approved changes. Conficluration As applied applying surveillance (1) (2) (3) Item (CI~. 3. a discipline technical and administrative direction over the life cycle of items to: document the functional and of configuration items. and Record and report information needed to manage configuration items effectively. drawings. Audit configuration items to verify conformance specifications. interfac~ control documents. released. configuration items Identify and characteristics Control related changes to documentation. to (4) b.elines for CIS. including internal and external interfaces. 3. approved).23 Configuration aggregation of hardware function and is designated configuration management.MIL-STD-973 3. A configuration or software that satisfies by the Government for Management (CM) .22 Configuration identification. submitted.

having a contract with corporation. maintenance. a. d. 3. The recording (CSA~. approved the changes. in for 3. configuration documentation and waivers The status of proposed to the configuration. the Government for the design. Inadequate (or erroneous) item configuration documentation which has resulted. 3. c.31 a.25 defining (including or program. 3.30 3. Contractor. and technical. regardless of administrative. Conditions in accordance configuration consist in any current or of two types. Plan will be implemented for a particular acquisition 3. manufacture. See MIL-STD-490. above functions is considered to be a contractor for configuration management purposes. Configuration Status Accounting of information needed to manage configuration items including: A record of the and identification approved configuration numbers.MIL-STD-973 The document (CMP) . Critical Data. medium or Recorded information. See MIL-STD-109. Defect. Deficiencies or characteristics with the item’s documentation. An individual. or supply of items under the terms of modification.27 association or other service.- . A Government activity performing any or all of the a contract. company. item. or may result. partnership. of deviations.26 and reporting effectively. Configuration how configuration policies and Management management procedures) 3. including of any nature.29 characteristics. units of the item that do not meet the requirements the item. are not item which approved b. Deslcln chanqe. managerial. b. Deficiencies. changes. The implementation status all The configuration of item in the operational units of inventory. See “engineering change”. financial. development.28 3.32 10 .

40 Enqineerinq documentation or an intended use.33 Develo~mental configuration. 3. It is under the developing contractor’s configuration control and describes the design definition and implementation.35 configuration in the life . documentation of cycle of the item. 3. The priority (emergency. 3. to depart from a particular requirement(s) of an item’s current approved configuration documentation for a specific number of units or a specified period of time. A specific written authorization. A proposed by which the change the Government for is if 3. justified.41 release En q ineerin configuration item release. granted prior to the manufacture of an item. and. A record used to . (ECP~. 3. 3. 3. A term covering the subdivision of Class I Engineering Change Proposals on the basis of the completeness of the available information delineating and defining the engineering change. ordered and implemented. 3. They will be identified as preliminary or formal.39 Enqineerinq Chanqe Proposal types. and submitted to approval or disapproval.34 Deviation.36 indicates Enqineerinq chanqe.37 Enqineerinq Chanqe priorities. The developmental configuration for a configuration item consists of the contractor’s internally released hardware and software designs and associated .MIL-STD-973 3. routine) assigned to a Class I engineering change which determines the relative speed at which the Engineering Change Proposal is to be reviewed. evaluated. urgent. Enaineerinu the reason for A change to a configuration the current item at approved any point which chanue justification a Class I engineering code.38 Enqineerinq Chanqe Proposal engineering change and the documentation described.) documentation. The contractor’s design and associated technical documentation that defines the evolving configuration of a configuration item during development. 11 ( ERR )_. A code change. approved. (A deviation differs from an engineering change in that an approved engineering change requires corresponding revision of the item’s current approved configuration whereas a deviation does not. An action whereby is officially made available configuration for its q Release Record documentation.technical documentation until establishment of the formal product baseline.

items. an item.42 3. Computer software and Items made of material.43 3. other visual parameters form denotes software. 3. DoD-STD-2167.45 ~. prior to acceptance. are excluded. (mechanical. lethality. and safety. size.50 Functional characteristics. physically part of interface another item. tools. 3. the basis to Function. the requirements specified in its functional configuration documentation. Audit Configuration 3. technical documentation such as weapons.MIL-STD-973 3. electrical. speed.47 designed 3.51 Yunct ional examination of functional characteristics to verify that item. interface characteristics and the to demonstrate the achievement of those Quantitative performance 3. The initially approved Baseline a system’s or item’s functional. electronic. including operational and parameters and design constraints. vehicles. The Documentation approved changes.44 or Evaluation. Functional logistic parameters and their respective tolerances. system other of the such system on 3.( FCD1 . 12 . and their components pneumatic). reliability.46 Form. See MIL-STD-280. shape. (FBL) . and verification required specified characteristics. hydraulic. perform. weight. interconnect ability of an item to or become an integral The 3. Exchangeability Firmware. A distinct group together with requirements which. aircraft.53 Hardware. such as range. characteristics include all performance parameters. which uniquely characterize the language and media. of a configuration the item has achieved and allocated .49 Functional documentation describing interoperability. 3. forms the next lower-level breakdown of function. dimensions. The action or actions which of all an Functional area. mass.48 performance groupings. ships. The with See See of DoD-STD-2168. item is and For 3. maintainability.52 Functional approved functional Configuration baseline plus The formal (FCA)_. computers.

62 Item.60 Interface Control Workinq Grou~ (ICWG1. support.58 Interface control.59 Interface control drawing or functional interfaces items Control Documentation (ICD) . through disposal 3. operation. beginning with concept of the item. 3. and of It where See “Commercial and Government 13 . 3. acquisition. 3. and controlling all functional characteristics relevant to the interfacing provided by one or more organizations. of identifying. applicable. Loqistics item. total cost to the Government system over its life cycle. The process documenting. (ILS}. configuration item.55 Integrated MIL-STD-1388-1. Item sum ort See (HWCI) . required The functional to exist at 3. code.65 Manufacturer’s (CAGE) code”. and agencies to exchange operations) or with an enable them to operate 3. contractors. disposal.63 Life cvcle. acquisition. MIL-STD-280.54 that Hardware Configuration is hardware. Entity 3.56 3. A generic term covering and logistics support definition and continuing of all phases of an item. and physical of two or more item A configuration See 3. other documentation which depicts of related or co-functioning Interface physical items.MIL-STD-973 3.61 Intero~erabilitv. 3. and 3. MIL-STD-280.64 Life cvcle cost. or other agencies. including resolution of interface problems and documentation of interface agreements. and physical a common boundary. For programs which encompass a system. The acquisition and ownership of that includes the cost of development. an ICWG is established to control interface activity among the Government. See The ability of the defense services information with each other (joint allied system (combined operations) to effectively together.57 characteristics Interchangeable Interface. or a computer software configuration item design cycle.

c. and in use by the Services. 3. and software. a. of a configuration to establish or verify Phvsical Configuration Audit 3. Items obtained marketplace. computer manuals. Physical characteristics. failure of systems. lists. Item covers material available from little or no development effort NDIs include: a domestic or foreign commercial developed activities. will be incurred if an engineering change are independent of the quantity of items of redesign. these are costs. (SD-2) Non-recurrinu 3. tolerances. Non-develo~mental 3. is approved and which changed. 3. such as cost As applied to ECPS. foreign with Federal governments which mutual defense and DoD acquisition Items already developed by can be supplied in accordance cooperation agreements and regulations. A document (NOR) . or other after Engineering design activity used to define referenced Change document or 3. respective data Oriqinal. special tooling. file(s) The current of record. a unit or product to item a _ Non-conformance.66 Material. and their The formal ( PCA ) . associated documents which require revision Proposal approval.73 examination of the “as-built” configuration item against its technical documentation the configuration item’s product baseline. documentation. stores. The specified requirements. expressions of material dimensions.68 is a broad generic term that wide variety of sources with required by the Government.MIL-STD-973 3.72 qualitative composition. fit. Items other already Defense from Non-developmental (NDI)_. finishes.71 digital 3. supplies. such as form. Quantitative and features. hardware. b.70 Notice of Revision revisions to drawings. equipment.69 which one time costs. 14 .67 conform to A generic term covering including related and spares. or t@.Sting. and Government agencies.

See or MIL-STD-280. (PCD) . The incorporation resulting from an approved engineering current approved product configuration accepted and/or operational items. The for each costs . Costs which are each service or document incurred ordered. the product baseline of a configuration item may consist of the actual equipment and software.85 Rework. and Substitute See See MIL-STD-1520. 3. to (SCN) .80 Retrofit. The designation by the document is complete and suitable for use.78 3.76 Recurrinu changed or for Documentation approved changes.77 Release. 3.81 3. item.75 Product Conficiuration approved product baseline plus item 3. See MIL-STD-280. See MIL-STD-280. 3. 3. an and computer software item or facility in to avoid abortive mission. S~ecification transmit.84 propose.87 withstand impairment 3. In addition to this documentation. The capability a hostile environment without of its ability to accomplish System.86 euui~ment.82 3. A document a specification. Equipment operate 3. contractor that a Release means that configuration control 3.83 3. used to Chanqe Notice record changes item. The initially approved documentation describing all of the necessary functional and physical characteristics of the configuration item and the selected functional and physical characteristics designated for production acceptance testing and tests necessary for support of the configuration item. MIL-STD-961. intended environment. required to maintain. Specification.88 Survivability. its or SUE) port 3.79 L.MIL-STD-973 3. 3. the document is subject to the contractor’s procedures. Re~lacement See MIL-STD-1520. of a system suffering an its designated 15 . “Computer See of new design parts change to an item’s documentation into already software” in DoD-STD-2167.74 Product Baseline (PBL] . Software. test. Repair.

United “Definitions”) 2302.MIL-STD-973 Technical data is recorded 3. and drawings. performance characteristics. orders that meet the criteria of this may also be classified as technical States Code. 16 . manufacture. hard audio and visual displays.g. The reviews are conducted at logical transition points in the development effort to identify and correct problems resulting from the work completed thus far before the problems can disrupt The reviews provide a method or delay the technical progress. and logistics b. a. maintenance. manual normally includes operation and instructions. and support of a system or equipment can be formatted into a technical manual.. and acceptance test procedures.90 3.89 Technical data. (3) Technical definition manuals. c. A series of system engineering 3. Technical data which provides instructions for the installation. (2) data may be presented in any form (e. of a data is required to define and document an design or product configuration (sufficient duplication of the original items) and is used production. or management data or other cost or pricing. (Title 10. activities by which the technical progress on a project is assessed relative to its technical or contractual requirements. other documents which define the physical geometry.92 Technical reviews. procedures This copy. operation. A technical data package should include all engineering associated lists. material composition. training. See See “Technical “Technical data”. parts lists or parts and related technical information or exclusive of administrative procedures. data packaue. magnetic tape. or other electronic devices) . assembly.91 Technical Technical documentation. Technical engineering to allow to support activities. Section 3. disks. information (regardless of the form or method of recording) scientific or technical nature (including computer software documentation) relating to supplies procured by an agency. information incidental to contract administration. data”. process descriptions. administrative. Technical data does not include computer software or financial. engineering. (1) A technical maintenance breakdown.

and related software which: a.98 17 . Are kept consistent in design. See MIL-STD-280. construction. Are used depicting. by or train maintenance and simulating.96 A written authorization to accept an item. and provide b.— MIL-STD-973 for the contractor and Government to determine that the development of a configuration item and its documentation met contract requirements. See MIL-STD-881. software. Waiver. in order to 3.94 An identified and documented body of 3.95 Version.93 types of maintenance audio-visual training have and aids. the Government. 3. or both. Modifications to a version of software (resulting in new version) require configuration management actions by either the contractor. or portraying characteristics of an operator personnel the operational item or facility. element. which during manufacture. devices. All operator training hardware. is found to depart from specified requirements.97 a Work Work Breakdown breakdown Structure structure (WBS). 3. or after having been submitted for Government inspection or acceptance. See MIL-STD-881. 3. but nevertheless is considered suitable for use “as is” or after repair by an approved method. Unit. Traininq euuipment. maintenance to 3. configuration with such items required training capability.

Configuration management and methodologies) . Configuration Configuration Configuration Configuration identification. status audits. The contractor’s configuration to generate and test the product.1 Basic requirements.2 Planninq. b. management system shall consist of the following elements: a. and physical parts For software. d. managers. Planning shall be consistent with the objectives of a cycle. configuration management planning shall include: a. the system representing or comprising the product. physical media. The objectives and of each element.MIL-STD-973 4. continuous improvement program which includes the analysis of identified problem areas and correction of procedures as The contractor’s necessary to prevent reoccurrence. and the contracted phase(s) of the life scope and complexity. d. of this standard (SOW) to CIS and by as accounting. The contractor shall plan a configuration 4. shall address the evolving developmental configuration and implementation and test) used support environments (engineering. 18 . management relationships. internal configuration management system for the control of all configuration documentation. control. Contractors shall implement the requirements identified in the contract statement of work shall insure compliance with those requirements subcontractors. techniques. resources (tools. GENERAL REQUIREMENTS The contractor shall implement an 4. The configuration organizational Responsibilities management of the applicable configuration configuration management management and program b. their standard. management program in accordance with the requirements of this tailored appropriately for the particular CI(S). c. and authority organization of configuration c.

other contractors. security. storage. modem) acknowledgement submitted by electronically transferring by the contractor to the Government. Contract Data distribution codes. or topic heading.g. The contractor’s planning shall address all in the contract. and maintenance are concerned. Requirements List (CDRL) distribution. transfer of processable data files. Access to data shall be limited in accordance with the applicable as well as by data rights. of receipt will be generated at the 19 end . Acquisition management in and Logistics accordance and f. and submitted or approved unless data status level (released. a. 4.3.. as applicable in accordance with the format and content requirements for the data specified in the contract. over the The contractor shall propose performance period of the contract. processes. DD Form 1692 for an ECP). When data are (e. and submittal of data. transfer. To Rrocessinff Automated 4. The contractor shall 4. reports and forms. any requirements that may be changes clause of the contract. CCBS.MIL-STD-973 e.3 Computer-aided Acquisition and Louistic SUP Port Configuration documentation shall be provided in either hard copy data transfer. 9.g. the contractor may provide form (e. assign distribution codes in accordance with MIL-STD-1806.3. the contractor shall use automated processing and electronic submittal techniques. when Where the data requirement is for a specified in the contract. integrity.3. Support (CALS) with paragraph (CALS~.. interactive access to data through contractor integrated technical or a combination of the above. security requirements. . as applicable. management policies. program managers. Computer-aided configuration 4. agencies. configuration management technical data requirements of the contract as far as data handling.. foreign Configuration procedures.1 Data distribution/access. methods.g. as applicable and in accordance with the to the Government. imposed on the Government that will require associated contractor effort to maintain the security and integrity of shared data. as specified information services. processing. the data on an electronic version of the form or may sequentially address the essential and applicable data elements of the Textual submitted data by block number or title. . data in electronic form shall be by paragraph number. records. other Government governments) . Coordination with internal and external agencies (e.2 facilitate processing of submitted data. (See MIL-HDBK-59) otherwise specified).

versions of are receipt. acceptance.. Interactive requirements. contractor shall implement a method of error detection for data transfer to insure deliverable data products are capable of being recreated in human readable format. for (2) (3) (4) (5) (6) 4. The contractor shall implement procedures and control data during the contractor As a minimum. and accounting. Any data technical data in the data base at all times. query and extraction of data and shall 20 . if any. the contractor’s integrated technical where contractually specified. shall have a unique identifier (e. acknowledgement of receipt by the contractor shall be The generated at the end of the transmission. convention shall distinguish an altered (annotated. with Government specified review and approval Each submitted digital data file requirements. review and update cycle. to identify and Government these Identification of data files submitted to the Government for review. Indication automatic Data status of data time constraints. annotation. b.MIL-STD-973 When data is electronically of the transmission.g. transferred by the Government to the contractor. and “submitted” To assure file integrity. How data How changes and changes from are transmitted. comment and as applicable in accordance approval/disapproval. procedures shall address: (1) c.3. The contractor shall maintain the current status approved) of all digital (working. return. service pre-defined In addition to access to diqital data. submitted. redlined) file version from the originally submitted file version by renaming it as a separate working status file. the file naming status. shall.3 the above information accommodate previous Notification/acknowledgement or acceptance. indicated. file name) which shall indicate file version. released. electronically transferred by the contractor to the Government shall be so identified.

that will be used to establish the configuration baseline(s) The contractor shall also identify the required by the contract.5 Configuration control. Naming purpose access of temporary working of annotation/mark whether of indicating approval. automatic approval) the Government’s Automated disposition Re-identification status of on data acceptance (e. and the identifiers affixed to the CIS and to the technical documentation As a part that comprises the CIS’ configuration documentation. f.4 identification shall include the selection of CIS. implement procedures that define the control files during the Government’s and contractor’s the following As a minimum.. Means of indicating essential/suggested. d. by the Government. internal configuration control measures to the configuration prior to the time that it is baselined documentation for each CI. for of data bases and interactive review shall be defined: Request for or annotation.g. the determination of the types of configuration documentation issuance of numbers and other required for each CI. and logging of access of the for read-only file(s) is required. any. and update cycles. of the configuration identification process. accounting. The contractor shall apply configuration 21 . e. provisional as applicable. by any links in the contractor’s review and approval chains. a. if marked version up. tracking of h. as acceptance. a comment/annotation up versions. b. Re-identification Method of acceptance. or rejection. How data is to be accessed. and of changed files. including required changes. the documentation recommend.MIL-STD-973 -. The contractor shall apply 4. the contractor shall subject to Government agreement. or 9“ Time constraints. 4. i. Configuration Configuration identification. c. documentation that will be internally controlled in the developmental configuration for each CI.

Configuration audits are 4. status of to final proposed engineering approval/contractual audits of and affect of major the c. of all CIS - Provide effective means. b.MIL-STD-973 and its item. and (4) preparing Specification Change Notices.7 Configuration audits. for (1) proposing engineering changes to CIS.6 Conficmration Status implement a CSA system. status authorized the of each the traceability of all baselined configuration effectivity changes changes from documentation 9“ Report the configuration and installation to all CIS at all status of locations. shall shall 4. Provide original CI. Ensure implementation of approved changes. Record and report the status requests for deviations and configuration of a CI. as applicable. Record and report the changes from initiation implementation. The contractor (CSA) . Identify the documentation each CI. Accounting As a minimum. arid their approved control measures to each configuration documentation. Record and to include identified report the the status discrepancies. this standard. (2) requesting deviations or waivers pertaining to such items. The configuration control a. c. : a. f. of the Functional Configuration Configuration audits consist Audit (FCA) and the Physical Configuration Audit. (PCA) . and report implementation e. (3) preparing Notices of Revision. 22 . performed before establishing a product baseline for the item. Ensure effective configuration baselined configuration in accordance with program shall: contrci documentation. results of configuration and final disposition of all waivers critical which d. Record changes. the CSA system current approved and identification configuration number associated with b.

of the item shall: a. tasked with the development or production terms of the contract. of of discrepancies the FCA/PCA. b. Support Participate identified the conduct of the FCA/PCA.— MI L>-STD-973 . contractors are changed. in the resolution during the conduct ---- 23 . Additional PCAS may be performed during production for selected changes to the item’s configuration documentation or when in accordance with the The contractor.

2 ensure traceability of CIS is invoked in the contract.2. and Implement accordance changes the activities required with the approved plan. Confiwration management administration.2.3 Technical reviews.2 5.1 Management the contract procedures characteristics a.1 Purpose.3). c. detailed requirements that should be selectively configuration management program. 24 . The Contractor’s Configuration Contractor’s CM Plan. and to be used to manage the functional and physical The contractor shall: of the assigned CI(S) . The contractor shall when MIL-STD-881 The contractor shall ensure that 5.2. Plan shall be in accordance with the requirements of and shall describe the processes. Submit the plan the CDRL. technical review process shall include evaluating the adequacy of the type and content of the configuration documentation. ascertaining that the configuration documentation is under formal Government and/or internal configuration control. (WBS) .MIL-STD-973 5. Develop the in accordance (See 6. 5. methods. Contractor’s with the and Configuration requirements thereto by of in Management Plan Appendix A accordance standard with in b. Structure to the WBS elements this Work Breakdown 5. the configuration management representatives participate in all technical reviews conducted in accordance with the contract The role of configuration management in the requirements. DETAILED REQUIREMENTS is to identify applied to a The purpose of this section 5. and determining whether problems/action items identified at the review will require submittal of Engineering Change Proposals against the current approved configuration documentation.

e. b. are embedded contractually in alterable in the i. The purpose Purpose of configuration identification.. microprocessor the marking with their between the and other and 9“ of h. upon Government approval/contractual implementation of the applicable configuration and in accordance with contract documentation. allocated. d. Select CIS. configuration be used to define Select configuration configuration baselines Establish a release documentation. for both and software: hardware a. Establish the functional. and identifiers and where embedded . 5. or labeling of items and applicable identifiers enables item. into documentation a controlled and for to CI. and product baselines at the appropriate points in the system/CI life cycle. applicable object code. 5. Assigning serial and lot numbers. configuration identification. documentation for each system interfaces.3 Configuration identification.1 of configuration identification shall be to incrementally establish and maintain a definitive basis for control and status To accomplish accounting for a CI throughout its life cycle.MIL-STD-973 -. to establish the CI effectivity of each configuration each item of hardware and software. as necessary.3. configuration associated data. Assign identifiers to CIS and their component parts associated configuration documentation. Define and document Enter each item of configuration computer software source code developmental configuration. electronically (firmware) 25 . f. the contractor shall. requirements. Ensure that documentation correlation documentation. c. including revision and version numbers where appropriate. Ensure that source and specified.

all CIS associated with any given development program are not necessarily designated as CIS at the Computer hardware will be treated as CIS. The problem/change report shall describe the corrective action needed and the actions taken to resolve the problem.3. resolution is achieved. The contractor shall prepare a problem/change report to describe each problem detected in software or documentation that has been placed under internal configuration control.MIL-STD-973 5. This process shall be used to control the documentation and repositories containing the elements of the developmental configuration.3. However. The contractor shall 5. library.3. Computer software will be treated as CSCIS throughout the life of the program regardless of how the software will be stored. The contractor shall establish drawing library and implement procedures for controlling the drawings.3 Software Develo~ment Library. The contractor shall select and recommend potential CIS to the Government.3 Developmental configuration. establish and implement a developmental configuration management process.3. computer aided design (CAD) . same point in time. The final CI selection will be made by the Government.1 Documentation establish a documentation controlling the documents library. 26 .3. 5. These reports shall serve as input to the corrective action process. and computer aided manufacturing (CAM) instructions residing within the drawing library.3. library residing The contractor shall and implement procedures within the documentation for - 5. and records of the problems are maintained for the life of the contract.2 Drawinu library.3. 5. The contractor shall implement a corrective action process for handling all problems detected in the products under internal configuration control.3. The corrective action process shall ensure that all detected problems are promptly reported. action is initiated on them. The contractor establish a software development library (SDL) and implement procedures for controlling the software residing within the shall a SDL. status is tracked and reported. Any item requiring logistics support or designated for separate procurement is a CI.2 Configuration Item selection.

MIL-STD-973 Configuration management Configuration baselines. 5.3.4 normally employs three types of configuration baselines, the and product baselines, to provide for the functional, allocated, progressive definition and documentation of the requirements and design information describing the various CIS designated for a system. The contractor shall recommend to the Government the in accordance with the order of types of specifications, preference criteria contained in MIL-STD-970, that should be used the actual specifications provided to define each CI; however, Those shall be those ultimately ordered in the contract. specifications are subject to review and approval/contractual The appropriate baseline for implementation by the Government. each CI shall be established with the approval/contractual implementation of that specification as defined in the contract. Configuration baselines and their configuration 5.3.4.1 The contractor shall establish configuration documentation. baselines for all CIS in accordance with the terms of the the configuration contract. The FCD, ACD, and PCD defining Each baselines shall be mutually consistent and compatible. succeeding level of configuration documentation from FCD to ACD and be a detailed extension of, its to PCD shall be traceable to, If a conflict arises between levels of predecessor(s) . documentation, the order of precedence shall be (1) FCD, (2) ACD, and (3) PCD.
.

(FCD) . Functional Configuration Documentation 5.3.4.1.1 The contractor shall define the documentation required for the functional baseline in accordance with the requirements of the contract. The FCD shall be in the form of a system specification or a prime item development specification for a for a system, single item development program plus other applicable The FCD shall also identify the configuration documentation. documentation for selected items which are to be integrated or such as items separately developed or interfaced with the CI, currently in the inventory. The Allocated Configuration Documentation (ACD) . 5.3.4.1.2 contractor shall define the documentation required for the allocated baseline in accordance with the requirements of the The ACD shall define requirements allocated from the contract. The ACD shall FCD or from a higher level CI to a lower level CI. be in the form of development or requirement specifications, referenced interface control drawings/documents, and other Requirements may be allocated to applicable documentation.

27

_

.

MIL-STD-973 facilitate development management the management of complex CIS, to facilitate and integration of system components, or to attention on critical or high-risk components. the focus

5.3.4. 1.3 Product Configuration Documentation (PCDI . The contractor shall define the documentation reuuired for the product baseline to a level of detail commensurate with logistics support requirements and procurement strategies, in accordance with the requirements of the contract. The PCD shall be in the form of product, material, and process specifications, engineering drawings, military specifications, and other technical documentation comprising a complete technical data package for the CI. The PCD may also be in the form of the actual software media. The PCD shall prescribe the necessary physical and functional characteristics of the CI and the verifications required to demonstrate required performance. The contractor shall document the PCD as specified in the contract. 5.3.4.2 Maintenance of configuration documentation. the related configuration baseline has been established, contractor shall control and maintain the originals of current approved configuration documentation for all configuration items specified in the contract. the the Once

5.3.5 Enqineerinq release and correlation of manufactured products. The contractor shall establish an engineering release system and shall use the system to issue configuration documentation to functional activities (e.g., manufacturing, logistics, quality assurance, acquisition) and to authorize the use of configuration documentation associated with an approved configuration. The contractor shall maintain current and historical engineering release information for all configuration documentation of all configuration items and their component parts. The engineering release system shall interrelate with the contractor’s internal system of controls to assure that all approved Class I engineering changes have been incorporated in production items as specified. The contractor’s engineering release and control system shall meet the minimum information content requirements and tracking capabilities specified in Appendix B for verifying that manufactured products correlate with the released engineering data. 5.3.5.1 Specification release and a~~ roval . The contractor shall include on each CI specification a contractor’s release signature indicating that the document has been reviewed and is suitable for its intended use. In addition, the contractor shall submit each such specification to the Government for an approval signature. Approval by the Government will normally be accomplished on the version of the specification submittpd for a 28

_

MIL-STD-973 Completion of the release and approval activities baseline. indicates mutual acceptance by the Government and the contractor as defined in the specification and of the CI’S requirements, After approval the specification referenced documents. establishes the appropriate baseline. 5.3.5.2 ~~ When required by contract, the 5.3.5.2.1 Use of ERRs. contractor shall utilize a DD Form 2617, “Engineering Release completed in accordance with the requirements of Record”, Appendix C to release new or revised configuration documentation (If additional space is needed to the Government for approval. to list documentation, a DD Form 2617C, “Engineering Release The Government Record Continuation Page” shall be used.) approved ERR releases the configuration documentation for use by The contractor shall all contractor and Government activities. also ensure that information about the newly released and into the CSA approved configuration documentation is incorporated (See 6.3) information system. Configuration documentation Initial release. 5.3.5.2.2 including the incorporation of shall be initially released, related information into the configuration status accounting by means of a Government-approved ERR. information system, software or combinations thereof configuration documentation, shall only be released as a complete that establish a baseline, package, ready for approval and contractual implementation by the except under extraordinary circumstances as approved Government, by the Government. Changes to the released Chanqe release. 5.3.5.2.3 configuration documentation shall only be accomplished as a result of an approved Class I or Class II engineering change. Such change releases shall be accomplished utilizing the ERR. The releases shall only be accomplished when the complete package of affected documentation is ready for simultaneous release, except under extraordinary circumstances as approved by the Government. 5.3.5.2.4 Unrelated ~. document provided a. All Consolidation ECPS may be that: apply of multiple combined into chanues a single into a sinqle revision to a Requirements for Enqineerinu Release Records

changes

to

the

same

end

item.

29

MIL-STD-973
-

b. c. 5.3.6 configuration as described

All

changes

apply ECP was

to

the

same

revision/version. for each unrelated change.

A separate

processed be

Configuration documentation below.

identifiers. shall

CIS assigned

and their unique

identifiers

CAGE Code. The design activities and the 5.3.6.1 manufacturers of CIS shall be identified by the Government which shall be affixed to all CIS, their assigned CAGE Code, configuration documentation, subordinate parts and assemblies, software media and products. Each Government tv~ e designators and nomenclature. 5.3.6.2 CI that is designated by the Government for control, tracking and logistics purposes shall be assigned Government type designators and nomenclature in accordance with the requirements of the contract. An identification number shall Document numbers. 5.3.6.3 be assigned and applied to specifications and all revisions in accordance with MIL-STD-961 or MIL-STD-490, and to engineering associated lists and ancillary documents and all drawings, revisions in accordance with MIL-STD-1OO. Part/item 5.3.6.4 part/item identification its subordinate parts with MIL-STD-1OO (e.g. is created) . A discrete identification numbers. number shall be assigned to each CI and and assemblies and be changed in accordance , whenever a non-interchangeable condition

For each CSCI, the Software identifiers. 5.3.6.5 contractor shall identify its corresponding Computer Software For each Components (CSCS) and Computer Software Units (CSUS). contractor shall issue/obtain a software CSCI, Csc, and CSU the which shall consist of a name or number, and a identifier, version identifier, and shall relate the software to its associated software design documentation; revision; and release date. The contractor shall embed the software and version and provide a method for identifiers within the source code, display of the software and version identifier data to the user upon command. Serial/lot numbers. 5.3.6.6 serial/lot numbers to like items, identified with a specific items, otherwise specified in the contract. 30 The contractor shall assign or to groups (lots) of like Government nomenclature, unless The serial/lot numbers

MIL-STD-973
-—

shall

be: a. b. A maximum of 15 alphanumeric the last 4 numeric. Unique, consecutive, with that specific characters, with for at all least items

and non-duplicating nomenclature. serial numbers. that shall be by the contractor. The affixed

Government 5.3.6.6.1 identify the serial numbers designated deliverable CIS

Government will to Government

The original serial Reuse of serial numbers. 5.3.6.6.2 number of a unit/item/CI shall not be changed even when a change affecting interchangeability may require rework and serial numbers shall not be Once assigned, reidentification. reused for the same item/unit/CI. Unless otherwise Product identification/markinq. 5.3.6.7 all CIS including parts, assemblies, specified in the contract, sets and ether pieces of military property shall be marked units, in accordance with MIL-STD-130 or identification plates/ nameplates in accordance with MIL-P-15024. 5.3.6.7.1 of labeling a. Software markinu software shall be as and labeling. follows: The marking and

Software identifier and version and Computer Identification Number (CPIN) , where applicable, be embedded in the source code header.

Program shall

b.

Each software medium (e.g., magnetic tape, disk) containing copies of tested and verified software entities shall be marked with a label containing, providing cross-reference to, a listing of the applicable software identifiers of the entities ccntains.

or it

c.

Media for deliverable CSCIS shall be labeled with the Government Contract number, CSCI Number, CPIN or other Government identifier (if applicable), Design activity Media Number (e.g., 1 of 2, 2 of 2) if there CAGE Code, are multiple units per set and copy number of the medium or media set (if there is more than one copy being delivered). Media copy numbers shall distinguish software media from its identical new version of software is issued, be assigned. starting from 1, shall 31 each copy of the Each time a copies. new copy numbers,

d.

if the device is assembly.3.7 Interface management. the CI shall be re-identified modified CI. 5.3. The contractor shall establish associate contractor agreements with interfacing contractors governing the conduct of interface control. the contractor shall be responsible for defining and controlling all The contractor shall ensure the interfaces below the ACD level. 32 . and documented and controlled requirements of the contract.3.3) in the baselined configuration documentation.3. Workina Group 5.7. shall be labeled on an identification plate or decal located adjacent to the nameplate on the equipment containing the firmware. on the be next labeled higher on Where both the hardware device and the embedded code are controlled via a single engineering drawing. When a CI is wholly to satisfy Government as a Government in accordance with the b. both the unloaded device part number and the software identifier of the embedded code.3 NDI .7. Prior to the PBL. the part number representing the device with the code embedded shall comprise the label. for the system and its configuration items shall be identified as a part of the system engineering process. developed with private funding and modified requirements. the device or. as follows: a. Those interface requirements which must be controlled by the Government during the development of the system shall be incorporated into the FCD and/or ACD as applicable. and PDI labeling.6. shall comprise the label.MIL-STD-973 5.6.7. 5.2 Firmware labeling. the use of an ICWG will be specified by ~. the software identification(s) In addition. 5. Such interface requirements defined in baselined specifications shall be subject to the configuration control requirements of this standard. compatibility and interoperability among the various hardware and software components for which he is the design activity and between those components and the interfaces/components specified (See 6.7. Where the PCD for the source code consists of a software product specification.3. the contract and the interface control contractor will be identified.2 Beauirements for an Int erface Control When required. including version number.1 The interface requirements Interface reuuirements. too Firmware shall small. COTS .

minutes of the ICWG meetings. and release only of approved configuration changes into CIS and their related Configuration control begins with configuration documentation. and the approved/contrac-tually implemented by the Government.2. Configuration control is the control.luration systematic proposal.2.7. evaluation. approval or disapproval implementation of all CI after establishment CI . for for recording and distributing the coordinating ECPS as required. the ACDS. PCDS contractually invoked by using the FCD. for providing the meeting space and administrative support. and controlling interface control documentation reflecting the ICWG decisions. 5. the ACDS.1 Purpose of conficluration control.2 the interface control contractor shall act as the chair for the ICWG and shall be accountable to the Government to report The interface problems as they are surfaced by the ICWG.7. and the Configuration control continues throughout the the Government. 33 . the establishment of the functional baseline and continues as further configuration baselines are established for the CIS. The following requirements shall apply life cycle of the CI. for updating. MIL-STD-973 --- The contractor shall be 5. and the in the configuration of approved changes. for interface decisions when they can be implemented within the current scope of the contracts of the participants.4 Confic. complete impact of the proposed changes. shall implement a configuration control function that ensures documentation of the regulation of the flow of proposed changes.4. releasing. justification. The contractor designated as ICWG Chairmanship. “contractor shall be responsible for scheduling ICWG meetings. and for distributing copies of such released interface control documentation to other ICWG participants. coordination of proposed changes. for distributing interface control documentation to be addressed at conducting the ICWG meetings.3. PCDS which have been only to the FCD.. responsible for providing a representative to the ICWG who is empowered to commit the contractor to specific interface actions for assuring that the representative is present and agreements. for making the upcoming ICWG.3. 5. of the configuration baseline(s) for the a The contractor 5. for providing draft interface control at all ICWG meetings. and for ensuring that updated interface control documentation reflecting the ICWG decisions is distributed within the time frame agreed to by the affected participants.1 ICWG membership. documentation at a specified period prior to the ICWG meeting where it will be discussed.

of the apply change to in accordance for h. changes An Engineering to the current any enqineerinq following of by process. chanqe elements a need for Chanqes. of Determination Establishment the engineering Review Disposition Preparation Submittal Incorporation changes in applicable. 5. including. ECP to the the evaluation of of the the an change.4.2. 9“ The the for Enqineerinq be required for documentation. as contractually applicable. The FCD or ACD. f. requests 5. Note: waivers. Class I if: a. Classification disagreements shall be referred to the Government for final decision. An 5. to determine if they would be impacted The change shall be as a result of implementing the change.MIL-STD-973 5. b.1 Classification of enqineerinq engineering change shall be classified as Class I or Class 11 by the preparing contractor in accordance with this standard. in) engineering when with deviations the and of approved (or concurred the documentation. chanqes. or to any combination or discrete portion thereof. shall be determined to be Class I by examining the factors below. of a classification I or Class II. c.4 . e. ECP.4. Class I ECPS shall be referred to the Government for approval or disapproval.2. in the the The contractor configuration control change. A proposed engineering change to a CI. extent that any outside specified is affected once established.4.2. d. Implementation contract. Similar steps shall of and the contractor change as Class of change.2. of the following requirements limits or specified tolerances: 34 to the would be — .1 include a.2 Requirements Change Proposal shall approved configuration shall process.2 Administrative reauirements. negotiation into the contract. Government.

once established. (1) Performance. spares. — characteristics. all and 35 . (2) (3) (4) (5) (6) Minor NOTE : be made only accompanying Government. software. b. Reliability. requirements in the clarifications and corrections as an incidental part of the otherwise SCN or NOR. unless to FCD or ACD shall next Class I ECP and directed by the will affect the or will impact A chanae to the PCD. of the following: one or more (1) (2) (3) GFE . affecting to such extent identification as (6) (7) Interchangeability. survivability. Configuration is required. characteristics. Safety.2. Compatibility or interfacing CIS. or replaceability as applied to CIS. Weight.4. FCD or”ACD as described in 5. substitutability. equipment/software.2. maintainability moment of or inertia. Preset adjustments or schedules operating limits or performance to require assignment of a new number.MIL-STD-973 -. balance. and to subassemblies and parts except the pieces parts of non-reparable subassemblies. Interface Electromagnetic Other technical specifications. to specified support trainers the extent la interoperability equipment or or training that retrofit with support devices/ action (4) (5) Delivered operation and maintenance manuals for which adequate change/revision funding is not provided in existing contracts.

function. to a Drivatelv shall be specified item or factors is negotiated on other or function Class I. design. Any (1) (2) (3) (4) Cost fees. effects factors may be added to the effects on form. When Government approval is required by the engineering changes.3.4.4.3 The DD Forms 1692 .lc. human-engineering of the to following the c. enqineerincl chanqes 5. DD Form 1692 (Page 1) shall be used. when alterations or changes to the initial ECP are necessary.1 be required objective.2 Classifvinq develo~ed item.2. the same ECP shall be identified by the entry of “R2”. Engineering Change Proposal Pages shall be prepared in accordance with Appendix D for Class I 1-7.2.4. shall distinct 5. Content of Enuineerinci 5.2. Contract Contractual Scheduled guarantees deliveries.3) by the contractor for Class 11 changes. The first revision to an ECP shall be identified by the entry of Further revisions of “R1” in the revision block of the ECP form. contractual Government or items drawings. An engineering change to a PDI classified Class I when it affects the contractually or logistics support of an form. between the Government and the contractor.2.2. When a greater degree of control in 5.4.2. The date of the ECP shall be the submission date of the revision. Major revised revisions package to of an ECP shall be made as DD Form 1692-1692/6 and 36 a complete attachments. “R3”.4.2. Skills. etc.2. biomedical factors including warranties.2. contract for Class II engineering changes.2. (See 6.MIL-STD-973 (8) (9) Sources defined of by CIS or repairable source-control training. Unrelated for each enqineerina engineering A separate chanqes. are incentives at any factors affected: and level or manning. a. change which has its ECP own An ECP shall be revised 5. fit factors which classify an engineering change as Chanqe Proposals ( ECPS 1.3. contract milestones. fit. If Government approval of Class II engineering local forms may be used changes is not required by the contract.2 Revisions of ECPS . .1692/6.

Correct deficiencies.3. A summary of any testing done by the contractor to validate concepts or new technology to be employed in the proposed engineering change shall be presented in the supporting data.— MIL-STD-973 b. SUDP ortinq 5. Classified data essential to the evaluation and disposition of an ECP shall be submitted separately in accordance with the approved security procedures and referenced in the unclassified portion of the ECP. Make a significant in the operational supportability of and measurable capabilities the system or 37 .4.g.3 Class I enqineerinq chanqe ~roposals. Block 19 of the ECP form should include information as to whether the revision is a resubmittal. The contractual DD Form 254 or DoD Contract Security Classification Specification applies. and details of such test data shall be provided if it is vital to the decision regarding acceptance of the change.2. provide revised form.4. the information which differs from the original ECP shall be clearly identified in a manner similar to the marking of change pages for specifications.2. or clarifications) may be made by attaching new or pages to a reaccomplished Page 1 of the ECP c. revisions to an ECP (such as those which correct add or delete information. the ECP should be unclassified. When practicable. or provides change pages to the existing ECP. test data and analyses) as specified in the contract to justify and describe the change and to determine its total impact including assessments of changes to system operational employment characteristics. changes are those required to: a. Class engineering changes should be limited to those which are necessary or offer significant benefit to the Government. change I Such Add or modify requirements. detailed cost proposal data. In either case. update pricing.2. interface or interoperability effectiveness or logistics item. 5.2.4 Classified data.3. b.2. LSA data. Formal ECPS shall be supported by drawings and other data (e. 5. replacing the existing ECP in its entirety. c. Minor errors.4.3 data . .

e. c.1. and ECP complexity.3. Authorization of the change granted by the Government will include reference to the ECP by number. revision (if applicable).2. 5.1. and date. Unless such incompatibilities. In addition. Such authorization will normally not occur until the Government has performed a review for technical adequacy and supportability.2.2. a Class I compatibility ECP shall be required within 30 days after initial notification.4. Class I com~atibilitv enqineerinq chanues. MIL-STD-973 d.4. Effect substantial life cycle costs/savings. The target recognizing the program. Emergency Urgent Routine 48 hours 30 calendar days 90 calendar days Unless otherwise specified 5.1 Class I ECP decisions. receipt of contractual authorization shall constitute the sole authority for the contractor to effect a Class I change. Where further action is necessary due to “lead time” the contractor may initiate procurement or consideration. Emergency and urgent ECPS should be proposed based upon the targets below unless otherwise agreed to Processing targets between the contractor and the Government. system.4) will be the following: a.3.2.3 This category of change is intended to allow expeditious corrective action when the need for a change has been discovered during system or item functional checks or during installation The contractor shall notify the Government by and checkout. or Prevent slippage in an approved production schedule. The criticality of the need for decision will dictate the actual processing time for ECPS.1 Taruet for technical decision on Class I ECPS. including estimated costs and schedules.–T . 3.4.4.2 ECP authorization.3. All aspects of the compatibility definition (reference paragraph 5. 38 corrective action otherwise prohibited by the contract. The message shall define the need for a compatibility change and identify factors that will be impacted. 5. written message within 48 hours after determining that a compatibility change is necessary. be implemented immediately by the contractor to resolve may then . 5.2.1.3.2. b.4. by the Government.2b) must apply.3. for routine ECPS will be tailored to maximize cost effectiveness.4. but only for the specific item(s) situated in the location at which the deficiency was originally discovered. for technical decision on Class I ECPS assigned the various priorities (see 5.

The contractor assumes total risk for implementation of such a change prior to Government authorization. Code D shall be assigned to an engineering change which is required to eliminate a deficiency. - (2) (3) c. Such separate codes are used to 39 .2 Class I ECP justification codes. a. Interface (Code B~.3.2.2. b.MIL-STD-973 manufacturing action and shall advise the Government with a change message referencing the serial number(s) and locations of additional items involved. 5.4. Contractual coverage completing the formal documentation of the engineering change will not reflect an increase in contract price for the corrective action in production and to delivered items in-warranty or otherwise stipulated in the contract. When the Government disapproves an ECP. except in those cases where the Government caused the incompatibility. Code C shall be assigned to an engineering change to correct a deficiency with the following characteristics: (1) The need.1. for the change has been discovered during the system or item functional checks or during installation and checkout and is necessary to make the system or item work.3. the one which is the most descriptive or significant shall be assigned to the ECP. By assigning the compatibility code the contractor is declaring that the effort required to accomplish the change is considered to be within the scope of the existing contract except for changes caused by the Government. Correction of deficiency (Code D]. Justification codes corresponding with the criteria necessary for beneficial engineering changes are listed below. the originator will be notified in writing within 30 calendar days of the decision and will be given the reason(s) for the disapproval. Com~atibilitv (Code C). unless a more descriptive separate code applies. Code B shall be assigned to an engineering change proposed to eliminate incompatibility between CIS. 5.4.4 Disa~~ roval of ECPS. If more than one of these codes are applicable.

operation and support cost model has been included in the contract. Code S shall be assigned to an engineering change for correction of a deficiency which is required primarily to eliminate a hazardous condition. e. plus the costs resulting from necessary associated changes in delivered items. Value enuineerinu (VE) [Code V). interface. This code applies when production to the current configuration documentation either is impracticable or cannot be accomplished without delay.. . 40 . Cost reduction (Code R]. should include all effects on cost and price for the effort and requirements covered by the contract(s) currently in effect for this contractor.MIL-STD-973 identify deficiencies of the nature of safety. and in items When a life cycle cost and/or produced by others. Code O shall be assigned to an engineering change which will make a significant effectiveness change in operational capabilities or logistics support. logistics support. When this code is assigned. a system hazard analysis per MIL-STD-882 shall be included with the ECP . Production stou~ac?e (Code P). but which is not being submitted pursuant to the Value Engineering The savings in life cycle cost clause of the contract. O~erational or louistics su~~ Ort (Code 01. d. Code V shall be assigned to an engineering change which will effect a net life cycle cost reduction and which is submitted pursuant to the VE clause of the contract. Safety (Code S). f. Code R shall be assigned to an engineering change which will provide a net total life cycle cost savings to the Government.— 9“ h. or compatibility. the ECP shall also include the costs expected to result from the implementation of this change into all future production and spare items projected to be procured for the program and all projected operation and support costs for operation of the total inventory of items by the Government. Code P shall be assigned to an engineering change which is required to prevent slippage in an approved production schedule.

An ACSN .3. A determination regarding the desirability of continuing expenditures required to further develop the proposal.1 Preliminary chanqe rro~osal. 5.3.1. the contractor and the Government should agree on the need for detailed information to be provided about the change idea involved.2 Prior to the preparation of a formal Routine ECP. It shall include a summary of the proposed change. d. A preliminary ECP may be prepared and submitted for one of the following purposes: a.3.1. or.1 Use of ~reliminarv ECPS (Type P). -- A preliminary evaluation relative to the merits of the proposed change (e. The type of Class I ECP appropriate to the circumstances shall be selected in accordance with the following definitions and guidelines.3.2. A preliminary 5.2.4.3. its impact on related areas. or To supplement a message relative to an emergency or urgent priority ECP when it is impracticable to submit a formal ECP within 30 calendar days. and a justification. installation of a proposed change for the purpose of evaluation and testing prior to making a final decision to proceed with a proposed change) . change proposal is the type which may be submitted to the Government for review prior to the availability of the information necessary to support a formal ECP. To furnish the Government with available information order to permit: (1) in . preliminary and formal.3 Class I ECPS. or a contractor letter summarizing the change idea.MIL-STD-973 Class I ECP tv Des.4. (2) b. Use of Advance Chanqe Study Notice (ACSN) .3.2. There are two types of 5.4.g. c.3. 5. or To propose a software change prior to the development of the actual coding changes and to obtain Government approval to proceed with software engineering development. To provide alternative proposals.4.2. shall be used by either the contractor or the Government to identify a 41 .

mtssmn An. mcrezsed reliabdiry. sckdulc sh page. NEED FOR CHANGE (Explain (f) how q nd wfwn need was rcc ~d. (3) how chwrge wfl m!prow system. J wrd Performtncc r /y trnprowd qn DESCRIPTION OF CHANGE 15TUOV (OwscrI& harchware modfrcatmn #mprowmwrc @portwwty Rough sketcks or dmgrams may & qttached or study recomrne~ to q mphty th~s to correct ~xrlptmn) q problem or to c#pltaltze on -- ALTERNATIVES TO SUGGESTEO CHANG[ / STUDY (Ezphm rdat~w dewtbrhry of q ach dtw~twq way tomcw needfor chmgc. PR 92 A Figure 1. cost. ORIGINATOR a TYPED NAME (Fjrs?. (2J Impart of nor makmg cfmge. cngmqertng torts. Q 9.g high’ mwttwrmcr UW9N. mcludmg ) cost 1 PROGRAM OFFtCt (Fmc Mddle Jnmd. Wcretsed field mpo~. znd. Ztp Cocje) m S ACSN NUMBER L. rubscarma rewew merr(ng. M/4flr OFFICE /nlft4/ L4St) TYPED NAME b SIGNATURE C DATE SIGNED (WMAIWO) 3 Contractor I TYPED NAME (fret Mddlc Inmd LJstJ b SIGNATURE c DATE SIGNED ( YvMMDO) DD Form2616. L*sTJ b SIGNATURE C DATE SIGNED (YYMMDD) B TYPED NAME 2 CONTRACT I ADMIHIS7RATION (WT. LmTl b ADDRESS (S(r?c(. \ubsys?ems. ITEM AFFECTED (ldwwfy COflCrJfiJ $yswms.MIL-STD-973 — b. c g. MIMIc h#rja/. or components I q ffeclcdby rfwngt) r. City stJt~. when powbl?. r@duc# WC rexdcs. confrtrf qndtrrms. Advance Change Study Notice 42 . c. mkty hszwd.

3. Otherwise.4 priority shall be assigned to each Class I ECP based upon the The assigned priority will determine the following definitions. Detailed instructions on completion of DD Form 2616 are (When ACSNS are noted in Blocks 6 through 10 of the form.4. The proposed priority is assigned by ordered. ) If the contractor originates a change idea. -- A Class 1 enuineerin~ chanae Priorities. may seriously compromise national security. In any case.4. the required information shall be provided for Government review.2 the type which provides engineering information and other data in sufficient detail to support formal change approval/contractual implementation.MIL-STD-973 (Emergency.2. Emerqencv. or discontinuance of further testing or development pending resolution of the condition. if not accomplished without delay. the contractor shall not proceed with the preparation of the formal ECP until directed to do so by The contractor shall use DD Form 2616. topic for a change proposal. the contractor shall provide additional information about the change to the Government for further study. To correct a hazardous condition which may result in fatal or serious injury to personnel or in extensive damage or destruction of equipment. the contractor shall evaluate the change idea (and any alternative courses of action identified by the Government) . required by the contract. or suspension of the item operation. A formal ECP is 5.3. and record type ECPS do not require an ACSN prior to submittal. when specified in the contract.3) the CM Plan. Change Study Notice (ACSN).2.) Use of Formal ECP (Tv~e FL. a. (A hazardous condition usually will require withdrawing the item from service temporarily. time frame in which the ECP is to be reviewed. the originator and will stand unless the Government has a valid “reason for changing the priority. the procedures shall be documented in (See 6. “Advanced the Government. and implemented. or 43 (2) .). compatibility. An emergency priority shall be assigned to an engineering change proposed for either of the following reasons: (1) To effect a change in operational characteristics which. urgent.3. the contractor shall proceed with preparation of the formal Routine ECP. and if in agreement with the change idea. evaluated. 5. Upon receipt of a Government-originated ACSN.” Figure 1. If authorized to do so by the contract or the ACSN transmittal letter.

- b. may seriously compromise the mission effectiveness of deployed equipment. the uncorrected existence of which could result in (A injury to personnel or damage to equipment. when lead time will necessitate slipping approved production or deployment schedules if the change was not incorporated) . or forces. or (2) (3) (4) (5) (6) (7) 44 . would cause a schedule slippage or increase cost. potentially hazardous condition compromises safety and embodies risk.) .MIL-STD-973 (3) To correct a system halt (abnormal termination) in the production environment such that CSCI mission accomplishment is prohibited. if not accomplished expeditiously. An urgent priority shall be assigned to an engineering change proposed for any of the following reasons: (1) To effect a change which. or To meet significant contractual requirements (e. but within reasonable limits. To correct critical CI files that are being degraded. permits continued use of the affected item provided the operator has been informed of the hazard and appropriate precautions have been defined and distributed to the user. or To correct a potentially hazardous condition. software. To correct unusable output critical to mission accomplishment. or To effect a significant net life cycle cost savings to the Government.. through value engineering or through other cost reduction efforts where expedited processing of the change will be a major factor in realizing lower costs.g. Urqent . if delayed. as defined in the contract. or To effect an interface change which.

MIL-STD-973 —. Method and date of the original communication.4. preliminary or formal ECP shall carry the same ECP number as the written message and shall include reference to: a. The following paragraphs.4. To effect a change in operational characteristics to implement a new or changed regulatory requirement with stringent completion date requirements issued by an authority higher than that of the functional proponent. c. All If the communications shall be identified by the ECP number.3. if any.2.5 Format for Class I enqineerincl chanqes.1 prioritv of emerqencv or uraent. message. electronic transmission or other expeditious means. b. proposed engineering change when emergency or urgent is not applicable.3. However. prescribe the pages of the DD Form 1692 series that are required to fully document the impact of the (See 6. and followed by a formal ECP within 30 days after the first communication unless otherwise specified by the Government. Ex~editinu Class I enaineerina chanqes with 5.4. personal contact. it shall be confirmed by written message in a format essentially similar to Figure 2 within 24 hours. other than the initial communication or written message for emergency or urgent changes (see 5. DD Form 1692 series shall be prepared in accordance with Appendix D and used for proposing Class I engineering changes.4. (8) . a preliminary ECP may be submitted within a 30 day period followed The by a formal ECP at a specified interval thereafter.2. and Table I. Individuals contacted.4.3. 45 . . Source of resultant contractual direction. ECPS carrying a priority of emergency shall. A routine priority shall be assigned to a Routine. initial communication regarding a proposed change was by other than written message. The 5.2. be reported to the Government by telephone.3) engineering change. if it is impractical to complete a formal ECP within 30 days due to the necessity for extensive development. c. and ECPS carrying a priority of urgent may.1) .

namd (a) Sy9mmw. thmn m sdtdda Isiws %p 7 u~ CI!M t40T REOUlflED NOT REQUIRED REWIRED d Th. AND PAGE 1ss2 P* 1 USAGE Ca+w Shwl Concept Demonstration Engmeermgand Production andDeployrnenl Exploration andValidation Manufacturing Operations andSupporl andDefinition Development REWIRED Only* hound Cw-rlala am 10 b mntrow REWIRED COW Bhoa w-m lb ECP REWIRED Chw ~ w-z.m4u=0d USED m s— -rfmmdddr~ECPa uSED w su~ m Ws2i3 Pap 6 Mew ChM NOT REOUIRED WT REOUIRED ma~ddt ECPS REWIREO i: Thombb m thw Z2%z’nln USED to S-* tx+titcnshcm n REOUIRED t: Tlumtsadwdti add*!wkm USEOm: S-=4u. DD FORM Life cycle applications of DD Form 1692 LIFECYCLE PHASES NO./.ywsmmd~e - ~~ Tam~wuchcaorI~hcdunoa PM I tpd-mn nods Iobodlanpd & mud Iewl (c) ~ wadldmundud~ calm -C e b.ECPt erlg!otumclrlnlmwr FIEOUIRED# (q lhom wo roktd hwwmdwm ECPS~ymg 10 (b) q - btmmor-d m~ W9 Wd lb) -tm-offim=ds~ *.mMmmhu uSED IO Stuw e. Ctmngd la pEties on Pmdlm COdgvmlon Mowlflmm waoflo WT REOUIRED NOT REOLMRED REWIRED hon. h ECP REWIRED -$hwtwlmm!m Itu ECP lEW1 P-2 ENm Ftmctmal Alamad culf~mlm Idmttlmm NOT REOUIRED REWIRED uSED m.d~ --d wlh daisn dump 9 ctmn@ ddmdtrf. kti ~ mmt~umon mcslrn! REWIRED REOUIRED # USED: w Onc’nb@vmmOd~ln tunaamd &lSumul w dw tidam a P) Ud m t.UuIDh~ -Numb tiulm Bdmw* dmnpmnu. Ple+~ md 3 REWIRE USED m ~dttimd~mrwatud RnfIgumm dmml-m.mmativbctmq08n rmnmM6sh!wyti*tum 9-0 m— Ontytan 46 . (a) ham .MIL-STD-973 Table I. ~ U* mdqwq w —=m don tWTUU and Lqdm uSED to: Pz mpmm0fmMnil&08 d mud0n lb @mtu ~ @-w lmzn =4 EmN@ Tdal Cal 1(am mm) NOT REOUIRED WT REOUIRED REOUIREOt#im: (a) ECPrqIm c4mv m -m m! ~] Fulvm pmdlic+mn q q ml m~ m mdudng dat~ddklqtha ~d-w ~IRED uSEO IO Ttiu* w bfrpu4 1W4 p5 EaInmd ~wn$9 swmvy ~ E(% Ml REOUIRED NOT REQUIRED REOUIREO ~.

The ECP shall be accomplished on serialnumbers at an estimated cost of against contracts: (Show breakout by contract umber. ) 3. AdditionalInformation may be includedwhen available. Action requiredto correctthe condition(s) (or emergency)conditionis: (This paragraph shall provide a description of the proposed engineering change. CAGE Code ECP Number 1.— MIL-STD-973 (Orlglnator name.) 5. ) noted by the urgent 2. Spares e. include a statement to that effect. Software a. Interim be provided: (address aPPl~cab~@ areas) d. The followingsupportequipmentmust be modified (or new support equipmentmust be delivered) concurrently with this change: (If there is no effect on support to equipment. .) n 4. code and phone number of the person to be contacted. However. reporting and initiating action to correct urgent or emergencyconditionsshallnot be delayedpendingthe availability additional of information. Point of contactfor this change is (Provide the name. ) Is required because (Statereason for action and reference applicable documents. Other b. address. 7. TechnicalManuals c. Training support 6. part number or type designation. Sample Engineering Change Proposal Message 47 .) Figure 2. (Show urgent (or emergency) priority engineering change action affecting contract Item nomenclature. date and standardmessagetransmittal information not shown below) Government Contract No.

4.3. but the blocks on Page 2 of the ECP form shall be completed to summarize significant effects on specifications.1 Class I enqineerinq chanqes durinq concept DD Form 1692.5.3 Class c. Enqineerinq Chanqe Proposal. (See Appendix D) shall be used as a cover sheet to summarize the engineering change . this page must be submitted. Page 2“. the detailed text of proposed changes in each of these specifications is furnished as enclosures.5.3.3. changes in the hardware or software of such existent or subsequent prototype models shall be described on DD Form 1692-2.4 I enqineerinq chanqes durinq production and SUPPort . DD Form 1692/1 “Engineering Change Propcsal (ECP). . (See Appendix D) shall be used to describe proposed changes in the mission.3. As required. performance. Pages 4. and other requirements of the specification.2. Class I enqineerinq chanqes durinq enqineerinq development. (See Appendix D) .4 . If changes DD Form 1692/1 (Page 2) may be required. b.MIL-STD–973 5.2. demonstration and validation.2. are proposed to the current approved FCD or ACD.1692/6. DD Form 1692/1 (Page 2) shall be used to describe changes from the FCD or ACD defined by the system specification and each pertinent item specification.4. (See Appendix D) . when applicable.2 and manufacturing a. 48 . 5.5. “Engineering Change Proposal (ECP) Page 3“.3.2. b. 5. 5. 6 and/or 7 shall-be used-as prescribed in 5. exploration. a. “Engineering Change Proposal (ECP). DD Form 1692 (Page 1) shall be used as the cover sheet to summarize the engineering change. DD Forms 1692/3 . Page l“.5. If prototypes of items are undergoing operational evaluation or service tests. DD Form 1692 (Page 1) shall be used as the cover sheet to summarize the engineering change. _ d.

3.sinale Drime. Related enaineerinu chanaes. such entries need be made by a prime contractor only to the extent such data are available to the prime.2.6 5. When such an engineering change is proposed and when the basic item and other items affected by related engineering changes are the 49 . The net total life cycle cost impacts (increase or decrease) of the individual related ECPS shall be summarized together with all related ILS costs which have not been included in the individual ECPS. with applicable enclosures.3. A desired engineering change in one item (the basic engineering change) may require related engineering changes in other items in order to retain (or attain) either an interface match or compatibility and interoperability of associated items. information shall be included in Blocks 40 through 47. Entries regarding related ECPS of other prime contractors shall be made by integrating contractors. 5.6. d.6.3 or when new trainers or support equipment will be required as a result of the ECP .6. otherwise. f. software and associated updating of documentation.4. e.4.3. DD Form 1692/5 (Page 6) and/or DD Form 1692/6 (Page 7) is not required if the revision in the schedule can be fully described either in Block 19 of DD Form 1692 (Page 1) or by reference therein to a revised schedule for the subject item. DD Form 1692/2 (Page 3) . Entries in the column headed “other costs/savings” to the Government need be made only to the extent estimated costs/savings data are available to the contractor. DD Form 1692/5 (Page 6) and/or DD Form 1692/6 (Pa9e 7) (See Appendix D) is required if there is a revision in the schedule actions other than delivery of the item which is the Subject of the ECP. logistics and operations.2. DD Form 1692/4 (Page 5) (See Appendix D) is applicable either when there are related ECPS as described by 5. shall be used to identify the effects of the proposed Retrofit change to the PCD.2.4.4.3.2. DD Form 1692/3 (Page 4) (See Appendix D) shall be used to tabulate the net life cycle cost impact of the individual ECP.MIL-STD-973 c.1 and 5. When required. DD Form 1692/5 (Page 6) and/or DD Form 1692/6 (Page 7) shall be used as a graphic presentation of the time ph~sing of major actions involved in all related engineering changes to hardware.1 Related enuineerinq chanqes .

Coordinating contractors are not required to provide cost and pricing data to other contractors. The ECP shall include data on the extent and results of such coordination.4. When the contractor. he shall coordinate the ECP with the other prime contractor(s) prior to submission. When a desired engineering change in one item (the basic engineering change) requires related engineering changes in other items which are the responsibility of other prime contractors who are participating in a specific item development or production program. 50 . Unless otherwise specified.prime/subcontractor coordination.2. the basic ECP and its impact on other items shall be coordinated by the originating contractor as required prior to submission to the Government.sinqle Drime multi~le Drocurinq activities.2.6.1 Class II enqineerina chanue format.4. the Government will conduct such coordination of ECPS as it deems necessary.2.4. 5.3.3 Related enqineerinq chanqes . to the related ECPS of the other prime contractors.6.4. Related ECPS submitted to the Government shall be identified by the basic number plus a separate dash number for each procurement activity.several contractors.2. shall cross-reference the basic and other related ECPS. The coordinated basic ECP shall include data showing the extent of coordination and its results. Likewise. DD Form 1692 (Page 1) (See Appendix D) shall be used as format for submittal of Class II engineering changes to obtain Government approval. 5.4.6.4 Class II enqineerinq chanues.separate Primes.4. The technical basis for the change and technical effects of the change shall be coordinated. as the prime contractor to the Government for an item. initiates an ECP on that item. 5.4.5 Same enqineerinq chanqe .2.6.2. The basic ECP number shall be assigned to the ECP applicable to the item which is the immediate objective of the desired ECP.3. An engineering change which impacts none of the Class I factors specified in 5. when applicable and available. - 5.2.4 Same enqineerinq chanqe . is also a subcontractor to another prime contractor(s) for that same item.2.3. when submitted by its separate prime.4. 5. the basic and each related ECP.3. 5. when the Government has contracts with two or more prime contractors for the same item.MIL-STD-973 responsibility of a single prime contractor. the ECP package shall include both the basic and all such related engineering changes.2 Related enqineerinq chanqes .1 shall be classified as a Class II engineering change.

4 applies.4. Unless 5. 5.2. When the Government has required by contract that it approve each Class II change. d. Description of the engineering change. As a minimum.2. Change document number.2. contractor or his subcontractors do not have custody of the original drawings delineating the detail design. f. When the 5. Government concurrence prior to or concurrent with the release of the Class 11 change.2. Name and part number of next higher assembly. Class II justification codes.4.4 or 5. Reason for making the engineering change.3 Requirements for Reauests for Deviation (RFD) .2 codes for Class I engineering changes need not be applied to a Class II engineering change. All Government contract number(s) for which the change will apply.3 Concurrence in Class 11 chanues. The justification 5. the format used to obtain Government concurrence only shall include: a.1.4. Name and part number of item affected.4. The contractor assumes total risk for implementation of changes prior to notification of Government concurrence.4.2. otherwise specified by the Government.4. Government review of Class II changes during production will consist of a technical evaluation of the change and of material substitutions to support concurrence in The contractor shall obtain classification recommendations.4.4.4 ADDroval of Class II chanues. or unless 5. and when compliance with such drawings is a contract requirement.4.5 Non-custody of the oriuinal drawinqs.3. e.MIL-STD-973 \ The DD Form or the contractor’s own form shall be used as format for submittal of Class II engineering changes to obtain Government concurrence in classification only. 5.4.2. b. each Class II engineering change is subject to approval by the Government prior to implementation as specified in the contract. unless a request for a deviation has been approved in accordance 51 .4. the contractor shall not implement the change until approved by the Government. The contractor shall not manufacture items for acceptance by the Government that incorporate a known departure from requirements. c.4.

. or maintenance (e.MIL-STD-973 with the requirements of this standard. then the need for an engineering change.3 or 5. it is probable that either the requirements of the documentation are too stringent or the corrective action of the manufacturer was ineffective. operation or maintenance procedures. Where it is determined that a change should be permanent. The deviation consists of a departure which does not involve any of the factors listed in 5. 5.3. major. Authorized deviations are a temporary departure from requirements and do not constitute a change to the FCD. or compatibility with trainers or test sets) shall not be requested.4. a Class I or Class II engineering change must be processed in accordance with this standard.or PCD.3.4.3. repair parts. Prior to manufacture of an item.3. logistic interoperability. If it is necessary for a contractor to request a deviation for the same situation with the same item more than two times.3.3.3 Classification of deviations. If a proposed deviation is recurring (a repetition or extension of a previously approved deviation) . if a contractor considers it necessary to temporarily depart from the requirements. critical deviations and deviations which would affect service operation.3.3.4. 5.1 Restrictions on deviations. Submittal of recurring deviations is discouraged and shall be minimized.1 when: a. 5.4.2 or When the configuration documentation defining the requirements for the item classifies defects in requirements and the deviations consist of a departure from a requirement classified as minor. . rather than a deviation. Classification disagreements shall be referred to the Government for decision. the contractor may request a deviation. A deviation shall be designated as minor - b.3.4. if that is the case.g. or minor by the originator in accordance with this standard. (See MIL-STD-109) 52 Minor. 5. ACD. Each request for deviation shall be designated as critical. an engineering change should be submitted. The effectivity of the request for deviation normally should not include the entire remaining number of deliverable units on the contract.2 Recurrinq deviations. Deviations do not apply to software code listings.4. Unless unusual circumstances exist. shall be addressed between the Government and the contractor.

Unless otherwise 5.3. reliability. (See Appendix E) .MIL-STD-973 . L 53 . A deviation shall be designated as major The deviation consists of a departure involving: (1) health.4. 5.3. (5) weight and size. a contractor designed form. When the configuration documentation defining the requirements for the item classifies defects in requirements and the deviations consist of a departure (See from a requirement classified as critical. b.4. .2 when: a. Unless otherwise specified by 5. minor deviations shall be authorized (or disapproved) for the Government by the activity authorized to approve or concur in classification of Class II changes. A deviation shall be designated as b. by Appendix E.3. survivability. the contractor shall use DD Form 1694. 5. and minor deviations should be approved or disapproved within 15 calendar days of receipt by the Government. or durability of the item or its repair parts. maintainability.3. requests for critical or major deviations should be approved or disapproved within 30 calendar days of receipt by the Government. (4) effective use or operation.3) prepared in accordance with Appendix E. the form shall be (See 6. specified in the contract. “Request for Deviation/Waiver”.3. or (6) appearance (when a factor) or When the configuration documentation defining the requirements for the item classifies defects in requirements and the deviations consist of a departure (See from a requirement classified as major. MIL-STD-109) Critical.4. If DD Form 1694 is used. the Government. The deviation consists of a departure or involving safety . or a letter to request a Each request shall contain all information required deviation. MIL-STD-109) 5. Major.. (3) interchangeability.3 critical when: a. (2) performance.4 Format.1 Minor deviations.3.5.3.4. Unless otherwise specified.4.5 Disposition of deviations.

4. 54 .4.4. 5. Unless otherwise specified by the Government.4.4.5. if that is the case.4. repair parts.4. or compatibility with trainers or test sets) shall not be requested. it is probable that either the requirements of the documentation are too stringent or the corrective action of the manufacturer was ineffective. _ 5.g. The contractor shall not offer.2 Critical and maior deviations. unless a request for waiver has been approved in accordance with this standard. 5.3. major.3 Classification of waivers. rather than a waiver. Unless unusual circumstances exist. If it is necessary for a contractor to request a waiver for the same situation with the same item more than two times (or for the remainder of the contracted quantity of deliverable units) .4 Requirements for Reuuests for Waiver [RFWI . a Class I or Class 11 engineering change must be processed in accordance with this standard. critical waivers and waivers which would affect service operation.2 Recurrinq waivers. Classification disagreements shall be referred to the Government for decision. an engineering change should be submitted. or PCD.4 . If a proposed waiver is recurring (a repetition or extension of a previously approved waiver) . operation or maintenance procedures. then the need for an engineering change. or minor by the originator in accordance with this standard. logistic interoperability. Submittal of recurring waivers is discouraged and shall be minimized. Authorized waivers apply to a specific quantity of manufactured items and do not constitute change to the FCD.1 Restrictions on waivers. The effectivity of the request for waiver normally should not include the entire remaining number of deliverable units on the contract.MIL-STD-973 5. ACD. Each request for waiver shall be designated as critical. Waivers do not apply to software code listings. or maintenance (e. Where it is determined that a change should be permanent. it is determined that the item is considered suitable for use “as is” or after repair by an approved method. for acceptance by the Government. 5. The contractor may process a request for waiver if. during or after manufacture of an item which incorporates a known departure from requirements. critical and major deviations shall only be approved by a Government contracting officer. items that incorporate a known departure from requirements. shall be addressed between the Government and the contractor. .

A waiver shall be designated as minor b.3. A waiver shall be designated as 5. (3) interchangeability.2.4. Format. (4) effective use or operation.2 when: a. documentation requirements involving: (2) performance.3 of acceptance of an item having a contract or configuration does not involve any of the factors or 5.4.3 critical when: a.4 shall use DD Form 1694 (See Appendix E) .4.4.4. (See MIL-STD-109) Maior. or maintainability of the item or its repair parts.4.3. (5) weight. When the configuration documentation defining the requirements for the item classifies defects in requirements and the waivers consist of a departure from a requirement classified as minor. or a letter to request a waiver.4. a contractor designed Each request shall form. The waiver consists nonconformance with documentation which listed in 5. or (6) appearance (when a factor) . major The waiver consists of acceptance of an item having a nonconformance with contract or configuration (1) health. the contractor 5. 55 .1 when: a.4.4.4.3. When the configuration documentation defining the requirements for the item classifies defects in requirements and the waivers consist of a departure from a requirement classified as major. The waiver consists of acceptance of an item having a nonconformance with contract or configuration documentation involving safety. (See MIL-STD-109) b.4.MIL-STD-973 5. 5.3. survivability.3. or When the configuration documentation defining the requirements for the item classifies defects in requirements and the waivers consist of a departure from a requirement classified as critical. A waiver shall be designated as b.4. Unless otherwise specified. reliability. (See MIL-STD-109) Critical. Minor.

waivers shall be dispositioned by the local Material Review Board (MRB) when such a board is properly constituted.5 Disposition of waivers.4. the form shall be prepared in accordance with Appendix E. Substitution of a non-repairable part for an item for which the contractor has configuration documentation custody shall not require a Class I or Class II engineering change or a request for deviation or waiver when: (1) The part is identified as an authorized substitute or superseding part in a military specification or standard. critical and major waivers shall only be approved by a Government contracting officer. requests for critical or major waivers should be approved or disapproved within 30 calendar days of receipt by the Government. or 56 . Unless otherwise specified by 5. minor - Critical and maior waivers.4. part substitution for parts identified in the current approved configuration documentation of an item from the product baseline through the remainder of the item’s life cycle shall conform as follows: a. contract.4. or in the absence of such MRB by the Contract Administration Office (CAO). in the contract.4. Unless otherwise 5. to be a preferred part over the original.2 specified by the Government. and The part will not be installed in equipment to be submitted for verification and reliability demonstration tests. and minor waivers should be approved or disapproved within fifteen calendar days of receipt by the Government.1 Government. by the contractor having configuration documentation custody over the item.5.4. Unless otherwise specified by the Minor waivers.5.4. 5. (See 6.MIL-STD-973 contain all information required by Appendix E. Substitution of a non-repairable part shall require a Class II engineering change when: (1) The part substituted is determined. If DD Form 1694 is used.4. – - (2) b.3) Unless otherwise specified 5.5 Parts substitutions.

6. concurrent with the preparation of an ECP.3 (Related engineering changes separate primes) .4. in accordance with Appendix F. All other parts substitutions shall be subject to the Class I or Class II engineering change as applicable.s not desired shall require submission of a Request for Deviation (RFD) or Request for Waiver (RFW).6 Requirements for Specification Chanqe Notices (SCNS) .2.4. its SCN sequence number related to that revision of the specification shall not thereafter be (SCN numbers changed or assigned to another ECP/SCN package. for each specification The which would require revision if the ECP were approved. likewise. ) However. SCN(S) shall be submitted to the Government with the ECP for In the situation approval and authorization.4.5a or 5. prepare a separate proposed DD Form 1696.5b and for which a permanent change i. the originating contractor shall prepare and coordinate the SCN(S) with other prime contractors along with the ECP . Errors of a minor nature (such as typographical errors. The SCN number is entered in the appropriate block on the DD Form 1696. SCNS may be If this occurs. or any revisions thereto. or disapproval. the approved by the Government out of sequence. beginning with SCN 1. (See 6. the contractor shall.4. d. except as an incidental part of the next technically required ECP and accompanying proposed SCN effecting that CI specification.3) SCN cover Daae. discussed in paragraph 5. DD Form 1696 shall be changed to reflect the other SCNS approved since it was proposed. “Specification Change Notice”. 57 .MIL-STD-973 (2) c. some of the attached change pages might have to be revised to reflect the current wording as of the approval date. etc. and the approved SCN shall carry the same number. Once an SCN has been submitted to the Government along with an ECP. In accordance with the requirements of the contract. associated with disapproved ECPS are not reused. Part substitutions which do not meet the requirements of 5. The DD Form 1696 shall serve as a 5.) shall not be corrected. - 5. due to differing change processing/approval time periods. SCNS for a newly revised specification are also sequentially numbered starting again with SCN 1.1 SCNS for a specification are sequentially numbered cover page.3.4. The proposed SCN. The contractor does not have configuration documentation custody. punctuation.6.

or A proposed specification revision. The contractor will receive approved SCNS from the Government concurrent with contractual authorization. where more practical. or Table and by citing the words/information to be changed in “From/To” format.3 the resubmitted SCN shall retain the same basic and resubmitted.4. and all portions affected indicated by symbols (e. and shall use the approved SCNS as authorization to update the specifications in accordance with the approved SCNS .) in the margin.5 Chanqed paqes. identified with the same number as the specification to be superseded with a new revision letter. b. page.4.6. or Replacement new specification pages in format suitable to be substituted for existing pages. and all portions affected identified with symbols in the margin or containing a note explaining that the changes are too extensive to be identified. However. Figure.6. All portions affected by the change shall be indicated by a S}fnbo] in the’margin 58 — .g. Pages containing detailed information about the exact proposed changes to the specification by reference to the paragraph.4. and changes distributed with previous SCNS remain in effect unless changed or canceled by an SCN of later issue. identified with the specification number and SCN approval date. the summary of current changes shall be a cumulative summary as of the date of approval of the latest SCN. prepared to the same format.. 5. SCN number but must be reidentified as a superseding revision (starting with RI for each SCN) to avoid confusion with any previous submittals of the SCN.2 Attachments to ~ro~osed SCN.. change bars. SuPersession.6. The attachments to - the proposed SCN shall be: a. numbered with the same numbers of the pages they replace plus a suffix letter where additional pages are needed to replace a page (e. new Pages 5 and 5a replace old Page 5). — When a proposed SCN must be revised 5. as transmittal of change pages from previous change is concerned.4. asterisks etc. 5.MIL-STD-973 5. Updated and reissued pages shall be complete reprints of pages suitable for incorporation by removal of old pages and insertion of new pages.4 ADP roved SCN. c. An approved SCN also provides a summary listing of pages affected by all previously approved changes to that particular SCNS are not cumulative insofar revision of the specification.g.6.

3) 5. Loca 1 reproduction of this form. required prior to implementation of an ECP which affects contract cost. fee. 5. schedule.2 Requirements for ECPS. both sides of the sheet shall be reissued. ) (See 6.4. and only the page on one side of a sheet is affected by the change. privately developed items (e.3) instructions for DD Form 1692 (Page 1) in Appendix D. When changed pages are issued for specifications with pages printed on both sides of a sheet. or other affected document in accordance with Appendix G. procedure will only be applicable when specifically required by the contract. associated list.4.8.4. When a permanent change is desired. The purpose of the short form procedure is for use with multi-application items or items for which the prescribed detail design was not developed by the contractor and for which the contractor can not be expected to know the total impact of a proposed change. 59 . The short form shall be prepared in accordance with the (See 6.. The DD Form 1695.4 .3.1 Purpose. 4. an ECP is required. or technical requirements specified either in the contract or in the configuration documentation prescribed directly by its identifying number in the contract. The DD Forms 1692 through 1692/6 shall be used for submittal of engineering changes (other than any initial communication or written message) . effected by the ECP are not controlled by the ECP preparing activity.2. as illustrated by Figure 9. The unchanged side shall be reprinted without change and shall not carry the date of the change or be included in the change summary as being affected by the change.8. ItNoticeof RevisiOn”l (See Appendix G) shall be utilized to describe the exact change(s) to be made to each drawing. is Automated processing may be used in accordance with authorized.g.7 Requirements for Notices of Revision (NORSI . to the configuration documentation prescribed by the Contractual authorization shall be contract. commercial off-the-shelf items) .4. when the contracting activity has determined that the application The short form of change control to such items is necessary. - 5.1 ECP format. when specified as a data requirement (NORS are normally applicable where documents in the contract. 5.8 Confic7uration control (short form ~rocedure~.MIL-STD-973 adjacent to the change and encompassing all changed portions.8. 5. The Government will normally be responsible for determination of possible effects of engineering changes on higher level or associated items and similarly for It may also be applied to impact of deviations and waivers.

4. ECPS originated by subcontractors may be included as supporting data.4. b. 5. in the ExDeditinq contractor’s judgement.8. if a contractor considers it necessary to temporarily depart from the mandatory requirements of the specification or drawings. Items shall not be delivered incorporating a known departure from documentation unless a request for deviation has been approved in accordance with the requirements of this standard.3 Requirements for deviations.2.MIL-STD-973 5. 5. shall not be covered by the same ECP. a written ECP in accordance with this standard shall be submitted as soon as practicable.8.2 ECPS .2.5 ECP SUDD ortinq data. When an ECP is disapproved.3.8. a deviation relating to an alternative material. other technical documentation or parts thereof and the information.2.8.8. 5. may be initiated by telephone. Approval of an ECP will be The signature on the ECP form of the contracting activity or a review activity specifically identified in the contract and by the return of an approved copy to the contractor.7 Disa~ Droval .2. but not later than 30 calendar days after the first communication. personal contact.4. as required to justify and describe the change.2. As an example.4. functional.3 Revisions.4 Unrelated engineering changes ECP coveraue. process. the contractor may request that a deviation be authorized.4. message.4. or electronic transmittal to be followed by the contractor’s written statement within three (3) work days.8. requires immediate action.2. or dimensional requirement may be requested. a separate ECP shall be prepared for each engineering change.8. 5. An ECP which. ECP a~~ roval. Prior to manufacture 5. or unless otherwise contractually 60 .4.6 achieved by: a. or Modification when the ECP affects the contract. of an item. 5.2. the Government will notify the contractor of such disapproval in writing within 30 calendar days of the disapproval date giving the reason(s) for disapproval.2. An ECP shall be revised when major alterations or changes to the initial ECP are necessary in accordance with 5. rather. ECPS shall be supported by marked copies of drawings.4. If the initial reaction by the addressee of the communication is favorable.2 of this standard.

8.3.2. Deviation format.3. Unless unusual 5. 61 .8. or PCD. survivability. (4) interchangeability.2 Recurrinci deviations. it is probable that either the requirements of the documentation are too stringent or the corrective action If it is necessary for a of the manufacturer was ineffective. or (8) cost to the Government. For parts substitutions which do not require authorized. .8. affect service operation or maintenance should not be submitted Such changes that will affect or authorized as deviations.8.8. Deviations affecting one or more of the factors listed in 5.3) Deviation significant factors. (2) safety. an ECP must be processed in accordance with 5. circumstances exist.3. (7) appearance (when a factor). deviation is recurring (a repetition or extension of a previously approved deviation) .4.4.4.5 Deviation review and a~lmoval.3. maintainability.4. reliability. shall be addressed between the Government and the contractor.4. specifications. Submittal of recurring 5.4. requests for deviations see 5. requests for deviations affecting safety Requests for deviations which would shall not be submitted.3.4. (3) performance. then the need for an engineering change.4. or durability of the item or its repair parts.4 factors are significant in evaluating the effects of a deviation: (1) health.8.4 will be approved (or disapproved) for the Government by the CAO. Where it is determined that a change should be permanent. contractor to request a deviation for the same situation with the same item more than two times.3. If a proposed deviations is discouraged and shall be minimized. Local reproduction of the form is authorized.4. FCD. Unless otherwise specified in the contract. minor deviations which do not affect any factor listed in 5. Authorized deviations are a temporary departure from requirements and do not constitute a change to the ACD.8. with Appendix E.4 can be authorized only by the Requests PCO or their specifically designated representative. The following 5.3. (See 6. DD Form 1694 (See Appendix E) 5.MIL-STD-973 -.5. (5) effective use or operation. rather than a deviation. 5. (6) weight. drawings or technical manuals shall be proposed and processed as ECPS.1 Restrictions on deviations.3 shall be used for all requests for deviations unless otherwise The form shall be prepared in accordance specified by contract. for deviations will be processed within 30 calendar days of receipt by the Government.

4 Waiver significant factors. shall be addressed between the Government and the contractor. 5. 62 . requests for waivers affecting safety will not be authorized. DD Form 1694 (See Appendix E) 5. survivability. then the need for an engineering change. it is probable that either the requirements of the documentation are too stringent or the corrective action of the manufacturer was ineffective.MIL-STD-973 - Supplies or services 5.4. waivers which have an effect on any of the factors listed in 5. Waiver format. An item which through error during manufacture does not conform to the specified configuration documentation shall not be delivered to the Government unless a waiver has been processed and granted in accordance with this standard. ) 5. which do not conform in all respects to the contract requirements normally are rejected. or (8) cost to the Government. \/alvers wh~ch and forwarded to the PCO with recommendations. (See 6.8. 5. rather than a waiver.4.4.5 Waiver review and approval.8.4.8.8. The form shall be prepared in accordance with Appendix E.4. Submittal of recurring waivers is discouraged and shall be minimized.4 shall be reviewed by the CAO. as appropriate.8.4. ECPS shall be used for such deficiencies. Unless otherwise specified by the procuring activity.8.4.4. If a proposed waiver is recurring (a repetition or extension of a previously approved waiver) . maintainability. circumstances exist. waivers which involve only defects classified as “minor” and which do not affect any of the factors listed in 5. (7) appearance (when a factor).4. (5) effective use or operation.4 Requirements for waivers. If it is necessary for a contractor to request a waiver for the same situation with the same item more than two times (or for the remainder of the contracted quantity of deliverable units) . The following factors are significant in evaluating the effects of a waiver: (1) health.8. or durability of.4 will be reviewed and dispositioned by the cognizant CAO. (6) weight.the item or its repair parts. reliability.4. Unless otherwise specified by the procuring activity. Critical and major waivers shall be submitted to the PCO for approval or disapproval.4.1 Unless unusual Restrictions on waivers.2 Recurrinq waivers.8.4. (See MIL-STD-1520 for additional guidance. Minor waivers will be approved or disapproved by the CAO . (2) safety. (3) performance.3 shall be used for all requests for waivers unless otherwise specified by contract.4.4. Local reproduction of the form is authorized.4. (4) interchangeability.3) 5.

8. maintain. The contractor’s information system shall be capable of meeting contractual requirements for CSA . (See 6. deliver. 5. in total or by specific elements identified by the Government. .3 Preferred information system.5. and economical manner in satisfying their assigned responsibilities. Requests for waivers will be processed within 30 calendar days of receipt by the Government.5. operate. and the actual configuration of units of CIS. refurbish. 5. for transfer in a format specified in the contract. CIS in a timely. the processing and implementation of changes to CIS and their associated documentation.4. such additional information shall be provided as supplements to the existing system without disrupting the existing system or requiring the generation of a completely new system for the Government. 5. produce.MIL-STD-973 affect one or more of the factors listed in 5. —. The contractor shall retain a complete historical record of all the information required by the Government to be stored in the system. Where information beyond the existing contractor system is required by the Government to be included in the data base or in the formatted output. etc.4. inspect.2 CSA requirements.5 Conficauration Status Accounting (CSA). establishes requirements for CSA of the documentation and identification numbers which describe CIS.3) 5.5. An adequate and accurate CSA will enhance program and functional manager’s capabilities to identify. The contractor shall utilize the data elements identified and defined in Appendix I as a guide in the preparation of all applicable CSA records and reports.5. as tailored in the contract.4 can be granted only by the PCO or a specifically designated representative..5. Such historical information shall be formatted and maintained in such a manner that it can readily be copied. Appendix H. efficient. (See 6.1 Purpose of CSA. repair.3) 61. The purpose of CSA is to assure accurate identification of each CI and delivered unit so that the necessary logistics support elements can be correctly programmed and made available in time to support the CI. 5. 5.4 Retention of historical data base.5 CSA data elements. The contractor shall provide CSA information from the contractor’s information system to the maximum extent possible.

(1) verify Corrective actions shall be evaluated to: that problems have been resolved.7 The contractor shall CSA analvsis requirements.6 Contractor focal Point.5. review and analyze CSA data. adverse trends have been reversed. in accordance with retrofit instructions.6. addition: a. When potential or actual problems/ delinquencies which impact the Government are detected. as appropriate . the shall contact the Government within one business day contractor In to establish a course of action to rectify the situation.1. and changes have been correctly implemented in the appropriate processes and products. 5.1 Contractor participation and responsibilities. (See 6.6.1 Subcontractors and supPliers. at other contractor-operated activities. The 5.8 Re~ortinq accomplishment of retrofit chanqes.5. 5. either for prolonged use or for specific retrofit action. 5. Appendix J delineates the detailed procedures for reporting accomplishment of retrofit changes by the contractor. b.3) FCA and PCAS will normally be 5. and (2) to determine whether additional problems have been introduced. conducted by the Government prior to acceptance of a CI and prior to establishing the PBL. and at Government operated activities. vendors. 64 .MIL-STD-973 5. contractor shall be responsible for supporting Government conducted configuration audits in accordance with the following requirements except as amended by the contract.5. The contractor shall be responsible for insuring that subcontractors. Analysis shall be performed to detect trends in the problems reported. When units already accepted by the Government are returned to the contractor. These procedures shall be used to report accomplishment . and suppliers participate in Government configuration audits.5 Configuration audits. The contractor shall identify a focal point for the CSA system to interface with the data base users. at the contractor’s home plant. as directed by the Government . the contractor shall document the incorporation of all retrofit changes to those units in his custody and shall report the status of those units.

f. fabrication. responsible for establishing the time.3) Conference agenda. Accordingly. ]0 k. Personnel from each engineering. process sheets. Test results. Meeting minutes including resulting audit action items. drawings. Isolation of the item(s) and detailed parts to be reviewed. (See 6. configuration audit in consonance with schedule.2 Location. if approved by the Government.MIL-STD-973 --- Unless otherwise specified in the 5.3) Applicable specifications. This includes the following items to the extent appropriate for the type and scope of audit required by the contract: a. and other documentation as deemed necessary by Government FCA/PCA teams. (See 6. data sheets. Unencumbered access to the areas and facilities of incoming inspection. Configuration audit plan. schedules. Conference room(s).6.6. (See 6. and agenda for each the master milestone the Government.1. production. manuals.3 Contractor requirements.1. i. 5. and design and test data. b.3) Tools and inspection equipment (including coordinate measuring machines with operators) necessary for evaluation and verification. manufacturing and quality department to be available for discussion in their respective areas. the configuration audits shall be conducted at the contractor’s facility or at a designated subcontractor facility. subject to coordination with 65 . and testing. The contractor shall be place. Statement of Work (SOW). c. e. This 9“ h. the contractor shall be required to provide the necessary resources and material to perform the audit effectively. d. Copies of inspection reports.

d< 66 - . be prepared to discuss in technical detail any of the presented material within the scope of the audit.3b for a sample Audit Action Item List) and process each one. including identification of responsible have been established which activities and suspenses.. reports. minutes of each daily session shall be available for review by both the contractor and Government personnel at the beginning of the next day’s session. during side meetings shall be summarized in the main meeting at an appointed time. trade study results. system engineering data. deviations. e. Designate a co-chairperson for each configuration Participating contractor and subcontractor audit. recommended courses of action resulting from presentations or Conclusions from discussions conducted discussions. The minutes of the overall audit shall be available for review by the Government prior to the departure of the audit team from the audit location. or mockups. c.g. action items. specifications. producibility analysis results. Minutes shall be recorded and shall consist of significant questions and answers. Official acknowledgement by the Government of the accomplishment of the audit shall not be interpreted as approval of statements made in the minutes or of matters discussed at the audit and does not relieve the contractor from requirements which are part of the contract. conclusions. manuals. Record all discrepancies identified by the audit team (See Figure 3a .should be accomplished sufficiently in advance of each audit to allow adequate preparation for the meeting by both the contractor In addition. personnel or those chosen to make presentations shall - b. drawings. and appropriate comments shall be read into the official minutes. the contractor shall: and the Government: a. Provide an acceptable method to record inputs to official meeting minutes. until it is closed out or suitable residual tasks. Recommendations not accepted should also be recorded The together with the reason for non-acceptance. Insure that each configuration audit schedule is compatible with the availability of the necessary information and contract articles. as a part of the audit activities. hardwaref software. risk analysis results.

to indicate that the audit is not considered accomplished until the (2) satisfactory completion of resultant action items. The Government will: Provide a co-chairperson.2 Functional Configuration Audit [FCA) .to indicate Disapproval seriously inadequate.1. (3) -. except as otherwise required by the contract. Government will evaluate the results of each configuration audit in accordance with the following identifiers: (1) c. Review the daily minutes and ensure that they reflect all significant Government inputs. Clearly record all action items in the minutes and identify both the Government and/or contractor action required for each action item’s resolution. configuration item’s and system’s performance against its Test data for the FCA approved configuration documentation. b. the test data shall be 67 . Provide formal acknowledgement to the contractor of the accomplishment and results of each configuration audit The after receipt of configuration audit minutes. Publish the official minutes. d. e. Contingent approval -.— MIL-STD-973 will lead to the close out of the discrepancy/action item.6.to indicate that the audit was satisfactorily completed. if required by the The objective of the FCA shall be to verify the contract.4 a.6. 5. Approval -. Provide to the contractor prior to the audit the name. organization. A Functional Configuration Audit shall be conducted for each configuration item for which a separate development or requirements specification has been baselined. that the audit was 5. If a prototype or preproduction article is not produced. Government ~articipation. shall be that collected from the test of the configuration of the item that is to be formally accepted or released for production (prototype or preproduction article). and for the overall system. and security clearance of each participating individual.

CONTRACT NUMBER CAGE CODE ACTION ITEM ORIGINATOR NAME PHONE ORGANIZATION CONFIGUFU4TIONITEM NOMENCLATURE SERIAL PART ~BE~ AF~ n N’UMBE~ AFEE!L2ED DOCUMENT PAGE PAFWGRJQH FORWARDED BY : GROUP LDR TEAM LDR Figure 3a.PART I PROBLEM IDENTIFICATION FCA CONTRACTOR PCA CONTROL NO.MIL-STD-973 AUDIT ACTION ITEM LIST . Sample Audit Action Item L~s: 68 .

MIL-sTD-973 AUDIT ACTION ITEM LIST . Sample Audit Action Item List .PART II FCA PCA — CONTROL NO ASSIGNED ~ SUSPENSE ASSIGNED w SUSPENSE CONTRACTOR GOVERNMENT NAME SIGNATURE DATE ORIGINATOR AUDIT TEAM GOVERNKENT CONTIWCTOR Figure 3b.Continued 69 .

the following information (1) (2) Contractor representation. and actual accomplishment dates for the FCAS shall be recorded in the CSA information system.6. Status of test programs to test configuration items with automatic test equipment (when applicable) . and identifies each deficiency by deficiency report number. the FCA for complex In cases where item verification can only be — items may be conducted in increments. Identification (a) (b) (c) of items to be audited: Nomenclature. Contractor for review prior to the FCA.2 a.6. 70 . includes a cross reference to the test plan. the contractor shall to the Government: ~rovide ‘ Prior to the audit date. the contractor shall make the final draft copy of the CI product specification available specified to the Government in the contract. inspections. Subject to prior Government approval. The contractor shall provide a matrix for each CI at the FCA that identifies the requirements of sections three and four of the specifications. (3) Current listing of all deviations/waivers against the CI. completely determined after system integration and testing. and test report. The CI.1 Contract requirements. involved. results of demonstrations. test procedures. 5. shall not be audited separately without prior Government approval of the FBL and ABL for the CI. In addition. res~onsibility.2.MIL-STD-973 that collected from test of the first production article. The matrix shall be made a part of the FCA minutes. In such cases.2. The schedule dates. Specification identification number. or system. or system. the (final) FCA shall be conducted using the results of these tests. either requested of or approved by the Government. CI identification. as 5. (4) b. a final FCA may be conducted to ensure that all requirements of the FCA have been satisfied. and analyses for each requirement.

The contractor shall prepare an FCA check sheet which identifies documents to be audited and tasks to be accomplished at the FCA for the CI. An audit of formal test plans. The 5. The following testing information shall be available for the FCA team. A complete list of tests required by the test (To be requirements but not yet performed. and a general presentation of the entire Cl test The effort delineating problem areas as well as accomplishments. audit should also include: a. A complete list of successful tests if detailed test data are not recorded. requirements that were not met. specifications. (5) c.2. all discrepancies shall be clearly established and documented. descriptions. specifications. contractor shall provide the FCA team with a briefing for each CI being audited and shall delineate the test results and findings As a minimum. performed as a system or subsystem test. 71 . the discussion shall include CI for each CI. The contractor’s test procedures and results reviewed for compliance with specification requirements. A sample FCA Checklist is shown in Figure 4. (1) (2) (3) (4) Test plans.MIL-STD-973 c. Deficiencies shall be documented and made a part of the FCA minutes. Interface requirements and the testing of these Completion dates for requirements shall be reviewed. procedures. and procedures shall be made and compared against the official test data. The results shall be checked for completeness and accuracy. shall be b. and reports for the CI. A complete list of successfully accomplished tests during which pre-acceptance data was recorded. including a proposed solution to each item. an account of the ECPS incorporated and tested as well as proposed.3 Verification procedures and reauirements.6.) Preproduction test results.

Verification Testing Witnessed 8. Verification Testing Completed 4.- NOMENCLATURE CI IDENTIFIER DATE CONTRACTOR REQUIREMENTS 1.MIL-STD-973 . Verification Available Test Results Compiled & 5. Sample FCA 72 Checklist . Verification Test Procedures Submitted 3. Verification Test Data and Results Reviewed and Approved COMMENTS FIGURE 4. Verification Test Procedures Reviewed and Approved 7. Waiver/Deviation List Prepared YES NO 2. Facilities for Conducting FCA Available 6.

(e. For those requirements which cannot be completely verified through the use of testing. storage allocation data and timing. A list of the contractor’s internal configuration documentation of the HWCI shall be reviewed to insure that the contractor has documented the physical configuration of the HWCI for which the test data are verified. the FCA shall determine whether adequate analyses or simulations have been accomplished and whether the results of the analyses or simulations are sufficient to insure that the CI meets the requirements in the specification.MIL-STD-973 -. Review all documents which comprise or describe the contents or the use of the software product for format and completeness. procedures. For CSCIS the following additional requirements apply: (1) shall e. f. Acknowledge accomplishment of partial completion of the FCA for those CIS whose verification is contingent upon completion of integrated system testing. and sequencing characteristics for compliance with specified requirements. 9“ -. All ECPS that have been approved shall be reviewed to ensure that they have been technically incorporated and verified.g. Appropriate corrections shall be made before a CI is subjected to a reverification. or furnished with. i. An audit of the test reports shall be performed to validate that the reports are accurate and completely describe the CI tests. h. User’s Manual. Test reports. VDD) 73 (2) . . CIS which fail to pass quality requirements are to be analyzed as to the cause of failure to pass. jb Review data base characteristics. the drawings. Drawings of the CI parts which are to be provisioned shall be selectively sampled to assure that test data essential to manufacturing are included on.. d. and data used by the FCA team shall be made a matter of record in the FCA minutes. SPS.

5g.6. the contractor shall: a. PCA for a CI shall not be started unless the FCA for the CI has already been accomplished or is being accomplished concurrent with the PCA. listings. After successful completion of the audit and the establishment of a PBL. 5. Review the listing of all versions of the developmental and non-developmental software for the CSCIS that are in the software library.2. The PCA also determines that the acceptance testing requirements prescribed by the documentation is adequate for acceptance of production units of a CI by quality assurance The PCA includes a detailed audit of engineering activities. (3) (4) (5) k. drawings. specifications. and operation and support documents for CSCIS.2. b.3 Phvsical Configuration the formal examination of the as-built The against its design documentation. Preliminary and Critical Design Review (CDR) minutes shall be examined to ensure that all findings have been incorporated and completed. all subsequent changes are processed by formal engineering change action. Review the findings of all internal CM and software QA audits of the CSCI. Audit (PCA). and design documentation.MIL-STD-973 Review the records that reflect the changes made to the developmental configuration for the CSCI. A sample FCA FCA Certification Packaue. Accomplish residual tasks for which they were identified as the responsible activity. package is shown in Figures 5a . c. The PCA shall include an audit of the released engineering documentation and quality control records to make sure the as-built or as-coded 74 .6. technical data. Publish copies of the FCA minutes. The PCA shall be of a CI configuration in the 5.5 certification 5. After the FCA is completed.6.4 post-audit actions. tests utilized in production of CIS. Record the accomplishment and results of the FCA CSA Record for each CI audited.

Sample FCA Certification Package 75 .— MIL-STD-973 ECA c~WIcATIQ~ for CI IDENTIFIER(s) CONTRACT NO. T PACKAQ_ EQUIPMENT MANUFACTURERS APPROVED BY (CONTmCTOR) (GOVERNMENT) DATE DATE FIGURE 5a.

MI L-STD-973 SCOPE : Functional Configuration Configuration Item: S1 Irle~ ..Continued 76 . Sample FCA Certification Package . item’s FIGURE 5b. Audit (FCA) Was conducted on the followlng ~ The purpose of this FCA was to verify that the configuration performance complied with the Development Specification.

for comments.Continued 77 .) Attached is a list of the documents reviewed. See Attachment Attached of is a list of deficiencies. Sample FCA Certification Package . Check One u u Procedures and results reviewed satisfy the requirements and are accepted. procedures and interface documents shall be (All test reviewed to assure that the documents have been approved by the Government. Signature(s) q FCA Team Member(s) q Sub-Team Chairperson Figure 5c. All test data sheets shall be reviewed to assure that the test was witnessed by a representative of the Government. and certified. 1 Software) Date: Contract: Contractor: CI Identifier: The verification test/analysis results have been reviewed to ensure that testing is adequate. properly done.MIL-STD-973 IFIQTION (For Equipment/Computer NO.

record any part of the FCA which fails to meet or standards but is not an approved waiver/deviation. and standards.Continued 78 .heck One n The equipment(s)/computer Software listed on Certification Sheet No . specifications B. See Attachment Attached is a summary of FCA discrepancies. is to determine the extent to which the equipment (s)/computer software undergoing FCA vary from one application specifications and standards and to form a basis for satisfactory compliance with these specifications ana In accordance with this paragraph. of T- R@v& FIGURE 5d.MIL-STD-973 FCA ~ (For Equipment/Computer Contract: Contractor: CI Identifier: Software) Date : . A review of all deviations/waivers to The purpose military specifications and standards that have been approved. waivers have been reviewed with the following results: . D Signature(s) of FCA Team Member(s) * q Sub-TeamChairperson All approvedwaiversand DGV L deviationsto militaryspecifications and standardsshall be reviewed and recorded. all applicable deviations/ standards. Sample FCA Certification Package . 1 of this report complies with all applicable specif~catlons for comments. Also. List the deviations/waivers against the equipment/computer softwarebeing FCA’d that were reviewed.

Continued .MIL-STD-973 -. FIGURE 5e. Sample FCA Certification 79 Package .

Test Procedures S~ec_Re~ TP Re f _ Description Test Result 1- -—--— -—— 1 -J I I t--——— ---1 —— ——— -- A --— —- tt- ‘‘------i —-— ——— ‘- -1 ---1 I I I t- ——— -—- -- f- ——— -- ——— 7I -— r ---- I 1 SampleFCA Certification paclcage Continued 80 FIGURE 5f.wON/TFSi~NG RE VIEW Configuration Specification Item Nomenclature No. ..— MIL-STD-973 - TT T SPECIF.

Continued 81 .MIL-STD-973 FIGURE 5g. FCA Certification Package.

1 Contract requirements. and VDD shall be a part of the PCA. actual accomplishment dates. (the test manager should be b.2 provide Contractor res~onsibilitv.MIL-STD-973 For software. Identification Numbers. for the PCAS shall be recorded in the CSA information system. The contractor shall the following information to the Government: Contractor representation in attendance) . 82 . b. Specification CI Identifiers. - The schedule dates. Serial (2) (3) (4) Identification Number. A list delineating all deviations/waivers against the CI either requested or Government approved. as specified in the contract. Interface Design Document. and 5. of items to be audited by: Nomenclature. CAGE Codes. configuration is reflected by this documentation.6. In addition. approved engineering changes shall be incorporated into new revisions of the applicable configuration documentation prior to the PCA. Numbers.3. Satisfactory completion of a PCA and approval of the product specification are necessary for the Government to establish the PBL for a CI. and Government-.3. (7) c. (5) (6) Drawing and Part Numbers. a. All internally-. the product specification. the contractor shall make the final draft copy of the product specification available to the Government for review prior to the PCA. The PCA shall be conducted on a unit of the item selected jointly by the Government and the contractor.6. Identification (1) a. 5.

programmer’s manuals. to Current approved issue of hardware development and software and interface requirements specifications to include approved SCNS and approved deviations/ waivers. Identification test. Complete shortage list. for software. Receiving Report. Proposed DD Form 250.MIL-STD-973 d. maintenance manuals. (lo) FCA minutes (11) Findings/Status (12) Program parts selection list. diagnostic manuals.” “Material Inspection and (7) (8) (9) Approved nomenclature and nameplates. including operators manuals. Engineering drawing index including revision letters. (13) Interface Design Document for software. Assemble and make available to the audit all data describing the item include: (1) PCA team at time of configuration. etc. of Quality Assurance Programs. for each CI. of all changes actually made during (2) 83 . VDDS . illustrated parts breakdown. Acceptance test procedures and associated test data. e. Reference information to the CI being audited as follows: (1) (2) (3) (4) (5) (6) CI product specification. A list delineating both approved and outstanding changes against the CI. Operating and support manuals.

actions shall be performed as part of each PCA: a. 9* The following 5.3.6. manufacturing instruction sheets or computer-aided manufacturing (CAM) data related to drawings and computer-aided (CAD) presentations of specified parts design (5) identified by the Government. inspection of drawings (and/or CAD presentations) and associated manufacturing instructions (and/or CAM data) may be accomplished on a valid sampling basis. any discrepancies between the manufacturing instructions (and/or CAM data) and the design details and changes in the drawings (and/or CAD presentations) will be reflected in the hardware.MIL-STD-973 (3) (4) Identification completed. identified by the Government co-chairperson. Since the hardware is built in accordance with the manufacturing instructions (and/or CAM data). shall be reviewed to determine their accuracy and insure that they include the authorized changes reflected in the engineering drawings (and/or CAD presentations) and the hardware. A sample PCA Checklist is shown in Figure 6. of all required changes not All configuration documentation. In manufacturing instructions. The purpose of this review is to insure that the manufacturing instructions (and/or CAM data) accurately reflect all design details contained in the drawings (and/or CAD presentations) . A representative number of drawings (and/or CAD presentations) and associated manufacturing instruction sheets (and/or CAM data) for each item of hardware. Unless otherwise directed by the Government co-chairperson. Identify any difference between the physical configurations of the selected production unit and the development unit(s) used for the FCA and shall certify or demonstrate to the Government that these differences do not degrade the functional characteristics of the selected units.3 PCA Procedures and requirements. required to identify the CI. or electronic representations of the same. 84 . f.

changes.— —— —— Control design deviations/waivers. [a) (b) (c) {12) (13) (14) Review Review Ensure characteristics. (9) (10) Review Review Computer (11) Review system Software System allocation User’s Operator’s document. —— and resuiLs. and the (:) (2) Approved A list flnai dellneac]nq draft of the confiquratlon approved and ~tem product chanqes speclflcat~on. t4anuals. . ( ‘ ‘ ) COmpuLer Descrlptior and each updated software (12) Current set of llstlnqs of design portrayal for (13) (14) ~ (11 Define Product Basellne. —— —— —— software Preliminary Preliminary Data and base sequencing CIS for the and and detail detail following: Software Software storage requirements.”’ review ‘“MaLerlal and Draw~ng maintenance. hardware. LisL of shortage test llst. items installed processed the necessary in through approval the deliverable been that Component interface allocation design descriptions. des]qn CI.— —— —— copy Sof:ware of all Version sof:ware manuals. manuais. Software and Proqramner’s Firmware Support Manuals.t. Data. procedures Index. Characterlstlcs. 2ocumer. computer software. Sample PCA Checklist 85 . Manual. outstanding conflquratlon (3) (4) (5) {6) {7) (e) Complete Acceptance Engineering OperaLlnq. aqa]nst !he YES —— —— —— NO both ]tem. Review Review. shall be available. pian of RighLs appropriate should the PPSL have or and in packaging status that all that on —— —— —— the PCP. and associated Lest daLa. item. Manual. Identlfled is available have been documen~atlor. and processed that the through hardware does not the PCP buL were conLaln jtems that not (see HIL-STD-9651 —— FIGURE 6. and lllusLraLed board parts acclons and breakdown on waivers. . —— —— —— —— —— Report. Proposed Approved Manuscript Inspect~on Receiving (9) (10] nameplates. documentation following tasks shall be accomplished at the PCA. test and procedures unincorporated —— . approved DD Forrr nomenclature material 252. charts and timing requirements. proposed contractor’s DD 250. Eng~neerlng Release and Change System. acceptance shortages deSCrlpLlOnS or other means —— —— —— —— FCA minutes Parts for each Selection conflquracion List Program (PPSL)(seeMIL-STD-965). are should . CI —— . {2) [3) {4) [5) {6) (7) (8) Specification Drawing Review Review Review Examine Review and Validation.MIL-STD-973 P~A cm!xLLu The following hardware.

MIL-STD-973 b. and examine the CI to insure that the proper parts are actually installed. As a minimum. (5) (6) 86 . Discrepancies/comments. part numbers and serial number markings called out on the drawing (and/or (2) (3) CAD presentation) shall be identified on the manufacturing instructions (and/or CAM data) . Release records shall be checked to insure all drawings (and/or CAD presentations) reviewed are identified. the following inspections shall be accomplished for each drawing (and/or CAD presentation) and associated manufacturing instructions (and/or CAM data) : (1) Drawing number identified on manufacturing instructions (and/or CAM data) shall match the latest released drawing (and/or CAD presentation). The number of any drawings (and/or CAD shall containing more than five presentations) outstanding changes attached to the drawing be recorded. Nomenclature descriptions. (3) (4) c. The following minimum information shall be recorded in the minutes for each drawing (and/or CAD presentation) reviewed: (1) _ Drawing number/title (include revision letter). A sample of part numbers reflected on the drawing. (4) Drawings (and/or CAD presentations) and associated manufacturing instructions (and/or CAM data) shall be reviewed to ascertain that all approved changes have been incorporated into the CI. List of materials on manufacturing instructions (and/or CAM data) shall match materials identified on the drawing (and/or CAD presentations) . Check to insure compatibility with the Program Parts Selection List. (2) List of manufacturing instructions and/or CAM data (numbers with change letter/titles) associated with this drawing.

For CI acceptance. Insure that approvals by the Government are present where required. and procedures will be used. to assure that it accurately identifies. e. The PCA team shall determine any acceptance tests to be reaccomplished.—— – MIL-STD-973 . or similar internal support activity. systems. and tracks changes to the software and documentation. The Program Parts Selection List (PPSL) shall be compared to the HWCI/engineering drawing package to ensure only approved parts are listed. The contractor’s system shall meet the information and capabilities requirements of Appendix B as a minimum. and reserves the right to have representatives of the Government witness all or any portion of the required audits. Audit the contractor’s engineering release and change control system against the requirements in Appendix B to ascertain that the system is adequate to properly control the processing and formal release of engineering changes. or tests. The contractor’s formats. inspections. controls. This includes interim releases of spares/repair parts provisioned prior to PCA to ensure delivery of currently configured spares/repair parts. 9“ h. test data and procedures shall comply with product specifications. 87 . f. CIS which fail to pass acceptance testing shall be repaired if necessary and shall be retested by the contractor either in the manner specified by the PCA team leader or in accordance with procedures in the ~roduct s~ecification. (See MIL-STD-965) Review of all records of baseline configuration for the CI by direct comparison with the contractor’s engineering release system and change control procedures to verify that the configuration being produced accurately reflects released engineering data. (7) The drawings (and/or CAD presentations) of a major assembly/black box of the HWCI shall be checked for continuity from top drawing down to piece-part drawing. Audit the software library. (8) d.

CIS which have demonstrated compliance with the product The PCA specification will be approved for acceptance. Review all documents which will comprise the product specification for format and completeness. the following actions shall be performed by the PCA team on each CSCI being audited: (1) k. As a minimum. Review the annotated listings for compliance with approved coding standards. team shall certify by signature that the CI has been built in accordance with the drawings and specifications.) to ensure conformance with Section 5 of the software requirements specifications. 1. Compare detailed design descriptions with the software listings for accuracy and completeness. ) (4) (5) (6) (7) 88 . of these manuals should be withheld until system testing to ensure that the procedural contents are correct. correctness. etc. and adequacy to operate and support (Formal verification or acceptance the CSCI(S). tags. incorporation of comments made at Test Readiness Review (TRR). witnessed by confirming the inspection and test of equipment end items at point of Inspection and tests shall have been a Government representative. Examine actual CSCI delivery media (disks. ). tapes.MIL-STD-973 i. and data descriptions. and (2) (3) Review the design descriptions for proper entries. labels. Review FCA minutes for recorded discrepancies actions taken. symbols. references. Present data subcontractor manufacture. Review all required operation and support documents for completeness. The PCA team shall review the prepared back-up data (all initial documentation which accompanies the CI) for correct types and quantities to ensure adequate coverage at the time of shipment to the user.

MIL-STD-973 -. (9) 5. Post-audit actions. The regenerated CSCI shall be compared to the actual CSCI delivery media to insure they are identical. The contractor will be notified in writing by the Government of acceptance or rejection of the PCA.5 Certification 89 . PCA Certification Packaue.4 a. using deliverable or Government owned support software. The results of the PPSL review will be included in the final PCA minutes. 5.3.3. (8) Examine the related documentation to ensure that the relationship of the CSCI to the parts. For firmware. the contractor shall publish and distribute copies of PCA minutes as specified in the contract. b. that each CSCI can be regenerated. Accomplish residual tasks for which they were identified as the responsible activity. Demonstrate. A sample PCA Package is shown in Figures 7a-7k. c. or rejection of the PCA and requirements for reaccomplishment.6. Where follow-on acquisition of the firmware items is intended.6. After completion of the PCA. ensure that the information completely describes the requirements for installation of the CSCI into the programmable parts or assemblies and that this information describes the requirements for verification that the installation has been properly implemented. of PCA status and discrepancies to be corrected. ensure that the documentation has been accomplished to the level of detail necessary for the intended reprocurement. components or assemblies that store the executable forms of the CSCI is properly described.

MIL-STD-973 ON P~ - CI IDENTIFIER: CONTRACT NO. Sample PCA Certification Packaqe 90 . PRIME CONTRACTOR: EQUIPMENT MANUFACTURERS: APPROVED BY (Designee) (CONTRACTOR) APPROVED BY (Designee) (GOVERNMENT) DATE DATE FIGURE 7a.

A note showing the variance between what exists and what is acceptable.A note explaining. rhe establishment of a product baseline for equipment/computer software is lot to be construed as meeting Government requirements for delivery of an operational system meeting approved acceptance criteria. or criticizing the difference Detween writings. COMMENT . or criticizing the meaning of a writing. illustrating. but corrective action is NOT necessaryto successfully accomplish the PCA. Items of this nature shall be rectified by the contractor prior to successful accomplishment of a PCA. illustrating. FIGURE 7b. Items of this nature should be explored by the contractor and/or the Government.MIL-STD-973 scop~lpuwos~ - Scope: A Physical Configuration Audit (PCA) was conducted on the following end items of equipment/computer software: ~~ UELWMML XUALNQA WIN ~ The purpose of the PCA was to ensure accuracy of the identifying documentation and to establish a product baseline.A note explaining. Sample PCA Certification Package .Continued 91 . DISCREPANCY .

DPAWING NO.MIL-STD-973 p~A cE~Io!’J SHEET NQ1l (For Equipment/Computer Software) Contract: Contractor: Date: The following documents of the issue and date shown comprise the product baseiine for the listed equipmefit(s)/computer software: ASSEMBLY TOP SPEC NZ.Continued 92 . Sample PCA Certification Package . ~QTJI~~ENT/coMpTJT’ER ISSUE SOFTWARE NOMENCLATURE Signature(s) of PCA Team Member(s) q * q ““ Team Chairperson q Sub-Team Chairperson FIGURE 7c.

2 P~A rk&BTIFIcA210N (ForEquipment/Computer Software) Contract : Contractor: Date: Specifications have been reviewed and l~w and va~. ~~ Specifications reviewed and validated: EQUIPMENT/COMPUTER 2.Continued I 93 .) I FIGURE 7d. Each specification shall serve as the basic document for configuration control of the subject configuration items. Signature(s) of PCA Team Metier(s) q * q * Team Chairperson “ Sub-Team Chairperson The detailed A. See attachment for a list of discrepancie~. below shall be reviewed for compliance with the applicable requirements. Va~. 1. therefore. See attachment u •1 q The Product Specifications are unacceptable. B. They shall. specifications listed in paragraph B.MIL-STD-973 SHEFT NO. The information contained within the specifications shall be audited at the PCA. constitute the for comments. validated to assure that they adequately define the configuration item and the necessary testing. PCA Certification Package . product baseline. mobility/transportability and packaging requirements Check One The Product Specifications are complete and adequately define the configuration item. Specifications Reviewed and Disapproved: (Provide attachment for causes.

the PCA drawing review sub-teams: FIGURE 7e. that part numbers agree with the drawings. 1 (Equipment) Contractor: Contract: Date: Drawings have been compared with the equipment to ensure that the latest drawing change letter has been incorporated into the equipment. u •1 Signature(s) of PCA Team Member(s) q q Sub-Team Chairperson The following drawings were reviewed by A. HWCI/engineering drawing package. Attachment is a list of discrepancies.Continued 94 .KUION SB~~~ No. parts approved and listed on PPSL. attachment u •1 The drawings are compatible with the applicable contract Program Parts Selection List (PPSL).ECA CWUE. See for conunents. and that the drawings are complete and accurately describe the equipment. Check One The drawings are complete and accurately describe the equipment. Sample PCA Certification Package .

~ FIGURE 7f.Continued 95 . The acceptance test procedures have Ce Te~t PIo~ults been reviewed for adequacy and the acceptance test results have been reviewed to ensure that the testing has been properly done and certified. See attachment Attachment discrepancy= is a list of is a list of the documents reviewed. Attachment Check One •1 •1 Procedures and results reviewed satisfy the requirements and for comments..E B. Sample PCA Certification Package. are accepted. The following acceptance test results documentation were reviewed by the ATR Sub-Team: DOCUMENT mB. were reviewed by the ATP Sub-Team: DOCUMENT ~~ TITT.MIL-STD-973 PCA C&RUW2i~4 (Equipment) Contract: Contractor: Date : . Signature(s) of PCA Team Member(s) q q Sub-Team Chairperson P Test P~ The following acceptance test procedures A.

Zheck One o c1 There are no shortages or unincorporated design changes.” shall be reviewed by the Government or their designated representatives for a determination of what changes should be accomplished in the field and what changes should be accomplished at the contractor’s facility. The Government shall also determine if the reported shortages and unincorporated changes are complete. is a list of shortages and/or unincorporated design Attachment changes. Sample PCA Certification Package . List the shortages and unincorporated design changes that were .P~A ~~RU.ignature(s) of PCA Team Member(s) q q Sub-Team Chairperson i.- . including the agreed-to correctiv~ action. . 5 .~ (—QlrlQf& All shortages and of ed Deunincorporated design changes listed on the proposed DD Form 250. and the recommended corrective action required. “Material Inspection and Receiving Report.EKAUoN ~< ~ NO. FIGURE 7g.“ and other records have been reviewed.Continued 96 . ~ reviewed in compliance with requirements. (For Equipment/Computer Software) >ontract: Contractor: Date: The shortages and Unincorporateddesign changes listed on the proposed DD Form 250 “Material :nspection and Receiving Report.

all applicable deviations/waivers have been reviewed with the following results: Signature(s) of PCA Team Member(s) q q Sub-Team Chairperson 1@w Pr All approved waivers and deviations to military specifications and standards shall be reviewed and recorded. and standards. The purpose is to determine the extent to which the equipment(s)/computer software undergoing PCA vary from applicable specifications and standards and to form a basis for satisfactory compliance with these specifications and standards. List the deviations/waivers against the equipment/ computer softwarebeing PCA’d that were reviewed Revti FIGURE 7h. Sample PCA Certification Package . Also.MIL-STD”973 c~oI’J SH’Z’?T NO. — is a list of discrepancies and/or c1 In accordance with this paragraph. i-w !< /Dev~ Check One D The equipment(s)/computer software listed on Certification Sheet NO 1 of this report complies with all applicable specifications for comments.Continued 97 . 6 (For Equipment/Computer Software) Contract : Date : Contractor: A review of all deviations/waivers to military specifications and standards that have been approved. record any part of the PCA which fails to meet specifications or standards but is not an approved waiver/deviation. See attachment Attachment comments.

Continued 98 . Attachment is a list of discrepancies and/or comments. shortages. and certain specified discrepancies uncovered at the PCA shall be included in the DD Form 250. Sample PCA Certification Package .— MIL-STD-973 ~7 (For Equipment/Computer Software) Contract: Date : Contractor : 750. FIGURE 7i. ~t ion of Pr~ DD Foxm 75Q The proposed DD Form 250 shall be examined for completeness and an”accurate definition of the equipment/computer software. Check One n The DD Form 250 adequately defines the equipment/computer software and all unaccomplished tasks are included as deficiencies. B. Unaccomplished tasks. If the equipment/computer software is to be shipped from the plant. the Program Office representative will recommend to the Contract Administrative Office that the DD Form 250 be executed in accordance with the terms of the contract. c1 Signature(s) q of PCA Team Member(s) * Sub-Team Chairperson A. The DD Furm 250 has been examined to ensure that it adequately defines the equipment/computer software and that unaccomplished tasks are included as deficiencies. BesJU& Include a statement that the proposed DD Form 250 was examined and recommended.

The contractor’s engineering release system and change control procedures have >een reviewed to ensure that they are adequate to properly control the >rocessing and formal release of engineering changes.Continued 99 . c1 ignature(s) of PCA Team Member(s) Sub-Team Chairperson — FIGURE 7j. Sample PCA Certification Package . engineering changes. See attachment Attachment is a list of deficiencies. ~a (For Equipment/Computer Software) Contract: Contractor: Date : .. Zheck One •1 The contractor’s engineering release system and change control procedures are adequate for the processing and formal release of for conunents.

cies. Check One The contractor’s Logistic Plan for pre-operational support will fulfill the acquisition phase requirements and is compatible with operational phase needs. 9 Date (Equipment) Logistics Suppcrt Plan for Pre-operational Support has been reviewed to ensure that it is adequate to support the acquisition phase and is compatible with the operational phase maintenance concept and support requirements. of ~ Prtito & Long Lead Time items released. are all of current configuration at time of PCA or are in work. Attachment is a list of deficier. Package. . Signature(s) of PCA Team Member(s) q q Sub-Team Chairperson FIGURE 7k. Where basic items may be upgraded by rework or modification these actions have been verified as accomplished or in process based upon design change nctice. 2. and items provisioned.. prior to PCA. u c1 Attachment is a list of deficiencies.MIL-STD-973 PCA CERTIFICATION Contlact: Contractor : SHEET NO. WPw Check One Long lead time items and provisioned items processed. prior to PCA have been reviewed to ensure that obsolete items resulting from pre-PCA design changes are purged from the system.Continued Sample PCA Certification 100 - .

when certain subparagraphs will need to be tailored out.2.2. the subparagraphs are listed. but is not mandatory. the Engineering and Manufacturing Development (EMD). B. and the Operation and Support (OPS) phases of the life cycle. The NOTE column contains a “pointer” to a specific Note (see 6.2. from Appendix H. 6. The requirements of this standard must be tailored for application to programs involving items of various levels of complexity in various phases of their life cycle. . ) 6. should be invoked in your contract. Where the subparagraphs are normally invoked as a unit by citing the lead paragraph.3) that will provide further guidance in tailoring the requirement.1.. The SMPL (sample wording) column provides a recommendation on which of the sample tasking wording to use (by reference to samples A.2 Tailorinq quidance for contractual a~~ lication.1 Intended use. but no tailoring guidance is provided for the individual subparagraphs.MIL-STD-973 . or when they may be separately tailored into. to the blank spaces (e. The columns are arranged to identify the normal application in the Demonstration and Validation (D/V). the Production and Deployment (PRD). the contract. 101 .1 Use of Table II.g. N/A .1 Explanation of codes. 6. or C in 6.This code is used to designate IItitle-only” paragraphs that would not normally be invoked to incorporate all subparagraphs into the contract.2. Table III is provided to help you decide which status accounting tasks. NOTES (This section contains information of a general or explanatory nature that may be helpful. if applicable. [1] or [2]) in the sample. 6.1. A number of codes are used in Table II to indicate the applicability of a specific requirement to a specific phase of the program.2) and. Table II is provided to help you decide which requirements from sections 4 and 5 should be invoked in your contract.1. The following codes are used: a.6. separate tailoring guidance is provided for those specific subparagraphs.

3.3 c(1) c(2) c(1) c(1) c(1) c(1) 5.3.M MIE a gy 4.2.1 5.3.3.2.3.S.1 w WA N/A NIA MOST MOST ALL NJA ALL ALL ALL ALL NfA t41A NJA MOST ~ST ALL OPT fWA WA WA OPT WA NIA c B(3) OPT MOST No WA ALL OPT OPT WA d 5.3.5 4.1.3 5.5.3.2.3.1 5.1 5.3 5.7 5 5.4.1 5.3.4 4.5.3.3.4.3.1.6 MOST OPT MOST OPT MOST OPT MOST OPT b b B(3) B(3) 4.4 5.4.2.3.1 4.3 5.3.5.1.3.3.3.5 :L? ALL ALL OPT @ f f B(l) B(3) B(3) ALL ALL ALL ALL ALL ALL ALL OPT MOST ALL OPT ALL OPT c(1) B(I) OPT OPT ALL MOST ALL OPT ALL FEw m MOST FEw f I i B(3) B(3) B(3) B(31 c(1) 5.2.1 5.3. Tailoring guide for use with MIL-STD-973 EAEAd~ 4 4.2 4.2 5.2.3 4.1 5.2 4.3.2 5.MIL-STD-973 Table II.4.1 GENERAL REQUIREMENTS pJi Basic Roquwoments Planning Computor-aided aoq and logist~support (CALS) Data distnbutionl-ss Electronic transfar of data Intoractivm -as to digitddata Config identification Conf~ur8tion control Configuration status atxtg Configuration q udits DETAILED REQUIREMENTS Purposo Config mgt administration Contractors CM Plan Inmkas APPENDIX A] Workbreakdown structuro Tachmcal roviows Config idontif=tion Purposa of mnfig idantif Confkwration item salaction DovoloprnontaJ configuration Oaumontation librwy Drawing Iibmry Softwara Davd Library (SOL) Configuration Ba@inaa Configuration Bas91ino/config documentation Funct Confii Docurnantation Alhx Config Docurrmtation Product Config Docurrmtation Maint of confia doournontation Egrg rafaasa and cerrdation of mulufactwod products [krvokoa APPEPmlx 1 B Spacikation roloaaWappvl Roqts for Engrg FM R~rda Usa of Engrg Rol Rawrds [hvokaa APPENDIX C] Initial ralaass Chango roloasa Con801id8tion of multi* c%m into q sirqla ERR ? p Q.5.3.3.4 5.2 5.3 5.2.2 5.2 5.3.3 5.3 4.3.1 5.2 5.2 5.1.3.4 .4 ALL FEw ALL OPT ALL OPT c(2) c(1) OPT k A(1) A(2) 102 — .5.3.

4 5.3.7.2.1.4.1 5.2 !$’f$T OPT OPT SLCT P q ~ q c(1) B(1) B(3) 5.4.6.3.2.2.2.4.3.3.6 5.6.4.3.2.3.4 5.3 5.2.2 .3.3.7.2 5.3.2.3 .4.6.3.3.6.4.2 .7 5.2 5.3.6.4.3.7.7 5.3.1 5.3.5 5.1 .2 .6.4.2 .1 5.1 S.1 5.4.3.7.3 5.4.2.3.2 5.3.f f f I B(3) B(3) B(3) B(3) B(3) B(3) B(3) 5.6.2 . COTS.3.2.4.2 .2 5.6.6.2 5.7.3 5.6 S.3 5.3.3.2 5.3. Tailoring guide for use with MIL-STD-973 .6.2 5.2.2.4.6.7.3.3.7.MIL-STD-973 Table II.2 5. Configuration ~dentdiers CAGE Cd.4.2.3.2 5.2.1.4.2.4 5.2.2 5.1 5.2.4.4.Continued EAELt~ 5.3.M p S& FEw FEw FEw FEW No No No NJA ALL FEW FEw SLCT ALL OPT ALL OPT f f m n m O.4.6.2 5.1.4 Configuration control Purpose of config control Roqts for Engineering Changes The qngrg chango procass Administrative requiromonts Classification of angrg chgs Classifying q ngrg chg to PDI Content of ECPS Inwkas APPX D] Unrelated engrg changas Revisions of ECPC Supgmrting data Ctaasifiad data class I Ongrg Chg pposals CIQSSI ECP tisiona Tgt for tach dac&Cb I ECP ECP authorization Clo 1Oompat angrg Chgs Disappn)vaJ of ECPS Class I ECP justif cadas WA ALL ALL ALL ALL ALL WA ALL ALL ALL ALL ALL OPT ALL ALL ALL ALL ALL ALL WA ALL ALL ALL ALL ALL NJA ALL ALL ALL ALL ALL OPT ALL ALL ALL ALL ALL ALL WA ALL ALL ALL ALL ALL WA ALL ALL ALL ALL ALL OPT ALL ALL ALL ALL ALL ALL NfA ALL ALL ALL ALL ALL z C(I) c(l) B(1) r B(3) B(2) FEw ALL ALL ALL ALL ALL ALL WA ALL ALL ALL ALL ALL d B(3) 5.2 B(l) 103 .3 5.6. and PDI labeling Interfaca managornent lntofl~ raqulroments Rqts for an ICWG ICWG membership tCWG ch~nnansh~ ALL ALL ALL ALL MOST MOST EMQ ALL ALL ALL ALL MOST MOST ALL OPT ALL MOST MOST MOST OPT WA ALL OPT OPT SLCT EM ALL ALL ALL ALL MOST MOST ALL OPT ALL MOST MOST MOST OPT Q.3.1.3.1 5.1 5.2.6.1 5.4. Govt type desighomenclature Document numbars ParVitem ldentlf numbers Software identifiers Serialllotnurnbsrs Government sarial numbsrs Reuse of seriaJ numbers Product identif/marking Sottwaro markingAabeling Firmware labeling NDI.

R ALL ALL ALL OPT ALL ALL ALL ALL ALL ALL OPT ALL ALL ALL ERR ALL ALL ALL OPT ALL ALL ALL QM ALL ALL ALL OPT ALL ALL ALL NQLE s s SM.5 5.4.3.2 .1 5.5 5.2 .4.of Adv Chg Study Notica Usa of formal ECP (Type F) Class I q ngrg chg prioritii Exped Cls I ECPS W@fitM~ ofornargoncyor urgent Format for Cls I q ngrg *W Class I q ngrg chg6 during comxpf .3.3.4 5.3.3.4 5.4.3.3.3 5.5.5.2 .2 5.2 .2 .5.6. Rol q ngrg chgs-singh primamutti p~~ ~itias Rel ogrg chgs-aaparato primas same egrg chg-prima/sub coord same q grg chg-sav contractors Class II q ngineoring changes crass II q ng * format Class II just’L tion in Chs II Ohgs conc~ Approval of class II Chgs Nonastodv of otiinal tigs Requirements for Rqwsts W Deviation (WDS) RosWions on dovia!ions Recurnng deviations Ckasifkation of doviationa Minor w EM.6 5.4.2 .2.3 54.3 .3.2.1 5.6.6.3.3.4.3 No ALL ALL B(3) 5.4.1 5.4.4.3.3.5 5.2.4 5.1 5.1 u3AunmE ClassIECPtypes Prelimmary change proposal Use of pralim ECPS (TYP W U.4.2 No No ALL W No B(3) 5.2 . Tailoring guide for use with MIL-STD-973 .2 ALL %T OPT OPT OPT No No No No No No No ALL ALL OPT OPT OPT OPT FEw FEw FEw SLCT SLCT No ME ALL ALL OPT OPT ALL ALL OPT OPT OPT OPT ALL ALL ALL SLCT SLCT OPT ALL t t t t u B(3) B(3) B(3) 0(3) B(3) B(1) OPT OPT ALL ALL ALL SLCT SLCT OPT ALL u u v W.2 .4.4.EL B(3) B(3) 5.3.1 5.4.4.1 5.4.4.4.3.4.4.3.4 5.2.4.5.2.2.1.2 5.3.12 5.3.2 5.3.2.3.4.3 5.4.3.3.4.5 5.4.2 .4.6.2.4.2.3.4.3.x@or.1 5.3 5.4.51 ALL ALL ALL No ALL No ALL NO B(3) 5.3.4.3.4 5.3.4.4.4.2 5.Continued &g&J 5:4.3.3:3.4.2.3.3.2 5.2.4.3 5.z B(3) B(3) B(3) A(1) ~ Crind Format [klvokas APPENDIXq Disposition of deviations Minor deviations Critical and major deviations A(2) 104 . dernhml Class I qngrg chgs during Engw and Mfg H (EMD) Class I q ngrg chgs during production and support Rolatod onginoonng changes Rol q ngrg chgs-singls prim.4.4.4.3.2 .6.4.2.MIL-STD-973 - Table 11.

3.2.3.4.8.2 5.3 5.1 5.5 .5.4.3 5.2.3 i.2.4.4..4 . .4 i.4.3.1 5.2.8.2 -L A(1) 5.4.0 5.4..4.4.8.3.8.2.3.4.4.4.4.4..8.6.4.6.4.8.4 5.2 c(l) Ql?l_ .4.4.8.8.6.2 5.4.4 .5 No 2PT OPT z A(l) A(2) A(2) 105 .l 5.8.Continued EwBAMmE Reqwementsfor forWa~(RWs) Requests mNo 9JQ No 4LL MOTE x.4. .4 Restrictions on waivers Recwrnngwaivers Classif-tlonof waivers Minor Major Crmcai Format [Inwkes APPENDIX El A(2) 5.4.8.MIL-STD-973 .5.3.2 5.6.7 Disposition of waivem Minor waiwrs Critical ard maior waivers Parts substitutions Rqts for Spec Change Notices (SCNs) [Invobs APPX q SCN cowr page Attachments to proposed SCN Superoesaion Approved SCN Chanraect mQOS Rqts for Notkes of R6vision (NORs) [Inwkss APPX G] Conflg ctrf (Shoft-fm Procd) Purpose Requirements for ECPS EC? format ftnvritee APPENDIX D] yeclln:g ECPS ..4. - No No OPT OPT y .4.8.4.2 i.4.2.4..4.8.- Table II.4.4.4.6..4.3.7 .6 5.5 5.2 !..l .4.3 .4..3 5.4. &yd Tailoring guide for use with MIL-STD-973 .8.4.4.4.4.8.2 5.5 5..1 5.5 5.4.3 5. ECP oovorago ECP supporting data ECP ~al Dieecmmaf Requimnents for deviations Restrictions on doviatiom Rocurnng doviatlons Deviation forrn8t [Intdas APPENDIX ~ Deviation signitioant factors Deviation retiw and mproval No ALL No ALL 4LL 4LL ALL ALL z z wA(I) A(2) -.4.4.2.4.6 i.2 5..4.1 .1 5.3.8..

7 5.5.8 Contractor focal point CSA malysis requiromonts Reporting ~omp of retro chgs [Invokes APPENDIX JJ Configuration q udits Contractor parttirespons Subcontractors qnd suppliers Location Contractor reqta Govomrnent part ici@on Functional Conf Audit (FCA) Contraca reqta Contractor responsibility Verif promdum and qta Post-audit aotiona FCA Citification P&age physical Config Audit (pCA) Contract wqts Contractor responsibility PCA ~UrOS and rqta Poet-audil actions PCA ~rlitition PacAaQo ALL FEw No ALL FEw No ALL OPT OPT ALL OPT OPT E!(3) B(3) B(2) 5.0.6.3 5.2 5.2 5.5.2.4.6.6.5.3 5.-Em -m- m A(2) OPT OPT ALL ALL ALL ALL ALL ALL 8(1) B(2) ALL ALL ALL 5.MIL-STD-973 Table II.6 5.6.3.1.3.1 5.4.4.4.6.4. Tailoring guide for use with MIL-STD-973 .6.8.6.2.3 5.4.1 5.0.8.3 5.8.Continued H 5.4 5.1 5.4.4.2.4.5 5. OPT 2PT OPT A(1) 106 .6.0.6.4 5.4.3.5.3 5.6.3.5.1.6.5 5.2.6 5.4 5.2.5 Profwred information system Rotontion of histor data baso CSA data .4 5.1.1 5.5 5.5.Iomonts APPENDIX 11 [Irwikes OPT ALL OPT ALL ALL ALL ALL ALL ALL B(2) 5.6.1 5.5.1.2 TIT~ Raquiremeots wawors for Restrichona onwaNers %curringwawars Wawr fonmat [Invokes APPENDIX ~ Waiver significant factors Wtiver review and appr oval Config Status A~tg (CSA) Purpew of CSA CSA requirements [Invokes APPENDIX Hj -mi.1 5.2 5.2 5.3 5.6.5 WA No WA ALL WA ALL N/A OPT A(l) ALL No A(I) .2 5.4 5.6.6.5.6.6.4 54.3.

2 6.. and the task should include that wording. [NOTE: if an Appendix is invoked by the paragraph. 5.This code indicates that this is an optional requirement for this phase. with the understanding that there may be a few exceptions.1 Invokinq a complete set of reauirements.3) and subparagraphs. ) SLCT . e. paragraph [11 (e. E ~.2.This code indicates that the requirement is almost always invoked for this phase. normally. 107 . 9“ 6.This code indicates that the requirement is almost never invoked for this phase. If an Appendix other than Appendix H (CSA) is invoked within the paragraph. FEW . (Usually this relates to a requirement that is normally invoked in a later phase of the program.. The requirements of the standard are arranged so that.This code indicates that this requirement is one of a group of “either/or” requirements that must be selected if the lead paragraph is invoked for that phase.q. Based on the notes provided.. all subparagraphs of that lead paragraph are then applied to the contract. you will have to determine whether to invoke it in your contract.2.1. SAMPLE A: The contractor shall (e. it is intended that the entire Appendix be invoked. Sample wordinq for contractual taskinq. NO .2.4. include] and Appendix ~21 (e. f. with the understanding that there may be a few exceptions.1. OPT . d.MIL-STD-973 b. ~rocess reauests for deviation from the current a~proved configuration documentation) in accordance with MIL-STD-973.This code indicates that this is an optional requirement for this phase but that only a few programs may want to utilize it.q.q. c. MOST . ALL . they can be invoked by reference to a lead paragraph.This code indicates that most programs would invoke this requirement in their contract for this phase. in large part. only one of the group should be selected.

3.. enqineerinq chanqes) and subparagraphs. the only exceptions are for the electronic transfer of data (4. some programs may not want to use the capabilities. and for the audits (4.MIL-STD-973 6. rll (e. [NOTE: The number in parentheses at the beginning of each note is the number of the primary paragraph(s) to which it applies. - (e.7.1. (CSA) is invoked within the paragraph..2. [NOTE: paragraph rll le. and the task should include that wording.2.1.2 Some of the Tailorinu out specific requirements.2. capability to interactively access the contractor’s data base will be applied only to selected programs where such access to “real-time” data is necessary to (4. and [31 5.3 Identifying specific ap~ licable requirements. manaqe the SAMPLE C: The contractor shall in accordance ed interfaces of the items beinq develo rJ ) and .3.4. b. c1 * 5. paragraph(s) if an Appendix is invoked by the paragraph. include] and Appendix 6. L except that paracmaph(s~ Appendix (21 does not apply.7).4.3) of data submittal 108 - .2. requirements of this standard are provided for use in specific circumstances. for the interactive access to digital data (4.3 Specific tailorincl notes.3.2. While the use of electronic will become nearly universal.2. this will be especially true in the next few years while The requirement for the this technology is maturing. ~ [NOTE: f21 .3. it is intended that the entire Appendix be invoked.1 ) with MIL-STD-973. Other requirements in this standard are intended to be invoked by themselves as we select specific parts of a general CM tasking If an Appendix other than Appendix H for a particular program.4) 6. {e.1. The following specific tailoring information is provided to supplement the guidance provided in Table II. (4) The General Requirements of a standard are normally invoked on all contracts without tailoring.q.2 and 4.l document Class II SAMPLE B: The contractor shall in accordance with MIL-STD-973.41 if an Appendix is invoked by the paragraph include] and (31 (eoq. ] a. 5.3.2.3).q. You will have to decide whether to tailor them out for your program. one (or more) of the subparagraphs will have to be tailored out even though all of the other subparagraphs under the lead paragraph still apply.2) .4. In this standard.q.

(5. revision.1/ 5.2. 5. we want the contractor to internally control the developmental documentation once it has been released and prior to its being baselined by the government. The CM Plan may be used as a guidance document. During Demonstration/Validation and EMD phases.1) Many major systems will require the identification of the FCD in the Concept Exploration phase and the baselining of the FCD in the Demonstration/Validation phase.3.4. (5.2) Most contracts will invoke these paragraphs. l.3. 5. such control is still required for changes the contractor is developing. However. A primary criterion will be the size of the contractor and the availability of a data base in the contractor’s organization to provide the needed information.3.3. (See also 6.6.7) This paragraph would be invoked on every contract which invokes the detailed FCA (5.3. on a small program.3.7/5. f.3. when it is desired that the contractor use Government-issued drawing numbers and/or part numbers. based on the preference of the program. this requirement could vastly increase the contract cost.3.6.) L d.2. who does not have such a capability.6.3. or it may be invoked (by referencing the number. For a small contractor.6.5.ad and se. Also.7. On smaller programs e. and date) as a contractually binding requirement. since they will involve the development and production of both hardware and software. (5. so this requirement might continue to be invoked. they are not required when the contractor’s CM program has been certified.2/5.6.3) tasks of this standard.1) CM Plans are usually required as a part of the first phase of the program.3.7.2) or PCA (5.6. (5. this requirement should be 109 .4/5. 9“ which start with EMD phase. only the appropriate paragraph(s) should be invoked.3.3.1. c. that requirement should be cited. with updates provided at least with the transition to the next phase of the development. (4. Once into the Production phase.MIL-STD-973 successfully manage the program.3) The developmental configuration terminology has been expanded to include both developmental hardware and software.6. When a contract involves strictly one or the other.3.

if that is the case. especially for correction of deficiencies.3. All other programs will normally establish the PBL as a part of the Production phase effort. for major systems. ]0 110 . the ABL will be established as a part of the EMD tasking. Once the Production phase is reached.2) Most programs which include a Demonstration/Validation phase will include the requirement to generate the draft ACD during that phase.3. many programs rely only on the PCD for definition of their requirements for the items they are buying.4.1. the documentation is usually maintained by the managing DOD service.4.4.— — MIL-STD-973 invoked in that contract. Others (mainly larger systems) continue to invoke the FCD as the overall requirement for the capabilities of all of the items they are buying. Others continue to invoke the ACD as the overall requirement for the capabilities of the particular item they are buying.1. too. Most programs will require the (5. h. some transfer control of the originals to the program office. (5.1. (5. In the Operation and Support phase. Programs including software may require the establishment of the PBL for the software during the Programs which plan to compete the EMD phase. Many programs continue with contractor maintenance of the originals throughout the production phase. production contract for the item(s) being developed should require the establishment of the PBL as a part of the EMD effort. Most programs will require the contractor to maintain the original copies of the configuration documentation during the Demonstration/Validation and EMD phases. especially for correction of deficiencies determinations. Once production phase is reached.3) identification of the PCD during the EMD phase.4) i. the requirement for compliance with the FCD should be continued during the EMD phase. MIL-STD-490 (program-unique) specifications for the ACD and PCD should be ordered as “two-part” specifications.3. many programs rely only on the PCD for definition of their requirements for the items they are buying.

The continuing requirement for the issue of the serial numbers is usually invoked in the production contract(s) .3. P“ q“ .7. o.1) For some specialized types of equipment.3.2) The Interface Control Working Group (ICWG) is required primarily when the Government has awarded several contracts to different contractors for the It may development of different pieces of a system.6. this requirement must be invoked specifically for the equipment involved.7.MIL-STD-973 .3) Most contracts should invoke this lead paragraph to incorporate the entire section of However. if a follow-on production or spares buy is awarded to a contractor other than the original design activity. n. deliverable units are adequately identified. using a specific form called an release be accomplished Engineering Release Record. of your program.3. Also. 5.3.6. (5.3. requirements on configuration identifiers. (5. it may be advantageous to invoke this requirement if you want the serial numbers for the delivered units to continue in an unbroken string even though the CAGE changes.5. then this requirement is needed.— .7.3. 5.6. the paragraph on NDI/COTS/PDI numbering should be tailored out unless it is appropriate. control of interfaces below the ACD level is provided through control of the detail design invoked in the product baseline and the PCD. the Government issues the serial numbers to be affixed If such equipment is a part to the deliverable units.6. 111 1.3.7) Product marking is most critical during the production and support phases to make sure that the However. m.6.6. (5.1) Once programs reach the Production phase.6.6.3. (5. k.1) When the government begins releasing it sometimes requires that the approved documentation. . this task will normally be invoked in the EMD phase to require the contractor to establish the procedures and evaluate the medium to be used to accomplish this marking.2) The requirements for the contractor to plan for (and sometimes start) issuing serial numbers is usually invoked for the EMD phase. (5. If a detail design is not invoked for production.3. (5.6. (5.

6.2.3. 4) Since Class II engineering changes apply only to the product baseline.1 and 5. thus.4.MIL-STD-973 also be utilized where several different DOD agencies/ services must meet regularly with one or more contractors developing the system. 112 .2. If an ICWG is needed. r.2 . when the situation cited exists. along with the requirement for the “related changes for a single prime”. u. only subparagraph “c” under the preliminary ECP requirement should be invoked to cover its use for Emergency and Urgent ECPS. then the contractor’s role as either a member or as the chair/member must be identified.7.3.4.4.7.4. If product baselines will be established as a part of the EMD phase. this set of paragraphs is applicable primarily in the production phase and beyond. t. this requirement should be invoked to define the requirement for Government approval of the Class 11 changes. invoke 5.4/5.2 using Sample A.3. there would be no related ECPS. the contract must specifically cite the use of either the preliminary ECP or the ACSN for this purpose.1.4. If the ACSN is invoked. invoke 5.2. (5.5) If the contractor will not have control of originals of the “drawings”. (5.4.2.7. if contractor is to be the ICWG chair and a member.3.2 and tailor out 5.4.5) These tasks are normally not required during the Demonstration/Validation phase since the allocated baselines would not be established until the end of this phase or the beginning of the EMD phase.2.2) When the program wants to obtain brief preliminary information about routine Class I engineering changes. then this task would be invoked for use once the PBL(s) is established.6.4.3.2.4. You will have to evaluate your acquisition strategy to determine whether they will apply.3.4.3. (5. not both.2.4. this requirement should not be invoked.4. (5.3/5. the v. These tasks would only be invoked. The contract must specify that either !Iconcurrence” or “approval” of the Class II changes applies by citing the appropriate subparagraph.3.3.1. If contractor is to be a member. PDI) are not involved in the program. ~ s.2. (5.5.2) If privately-developed items (NDI.2.2. COTS.

however. and beyond. (5. This requirement is used in place of the requirements (see 5. the Army may require NORS for the specifications in lieu of the SCNS. deviations.4). normally do not apply to the EMD phase.2) for a complete ECP (set of -1692 forms).4. Requirements for SCNS (see 5. In Y“ z.2) The status accounting information available in the demonstration/validation phase is limited. The procedure is used almost exclusively when the producing contractor is not the activity that designed the item and cannot be expected to know the complete logistics impact of a change.4) This set of paragraphs on Requests for Waiver is most commonly invoked during the production phase Waivers and beyond in production and spares contracts.4.7) Notices of revision normally apply when the activity proposing an engineering change does not control the originals of the documentation affected. (5. (5.4. and waivers is normally invoked as a complete package. Deviations may also be applicable to the EMD phase.4.3) This set of paragraphs on Requests for Deviation is most commonly invoked during the production phase. (5.7) may also be invoked. 113 . aa. the contract task should specify that NORS are required only for those drawings/documents directly affected by the proposed change. most programs would track the needed information internally rather than requiring the contractor to do it. x.4.8) The Short-form procedure for ECPS.3). deviation (see 5.4.] When the program requires draft NORS to be submitted with the ECP. when it will be necessary to accept early test prototypes that will not fully comply with the performance requirements of the FCD and/or ACD. The need for NORS occurs almost exclusively in the production phase and beyond. It is normally used only for changes to drawings (the SCN is now authorized for use whether the ECP originator controls the original or not) . (5. This happens only in the production phase and beyond.MIL-STD-973 w. [In situations where the originals of the specifications affected by an ECP are not controlled by the ECP originator. on production and spares contracts.6) and for NORS (see 5. even then it is applicable to only a few contracts outside of the Army.5.4.4. which normally takes control of the document originals at the end of the EMD phase. and waiver (see 5.4. when required.

if part of the EMD prior to. ad. the accomplishment of same CI. Appendix H is also invoked. Government personnel accomplish this task. the EMD phase units are usually “pre-production prototypes”.2) The FCAS for each CI (and for applicable) are normally required as a contract. (5. the system. although they are often delayed until after some.MIL-STD-973 later phases.6.6.5. ae. so the PCA task for hardware items is normally invoked in the first production contract when the development contractor has been preselected (usually in the acquisition strategy) to be the production contractor.7) Retrofit involves delivered production units.5) If you want the contractor personnel to accomplish the task of monitoring the information system. ab. this task should be invoked. (5. or all. For hardware. so the tasking only applies to the production (and later) phase.3) The PCAS for CSCIS are usually required as a part of the EMD phase contract. PCAS would be required in the EMD contract (to establish a product baseline for the competition) and in the first production contract (to update the approved product configuration documentation to match the final 114 . Normally. They should be accomplished concurrent with. NOTE: By invoking this requirement. using Table III as a guide. and if the new parts will be installed by the contractor. - (5. the PCA can then be accomplished on an actual production unit. to identify the specific types of information your program will require from the contractor. or the PCA for the ac. then this requirement should be invoked in that contract so that the CSA and maintenance records for the delivered units can be updated. the contractor would be required to provide increasing amounts of the information for government use. As ECPS are submitted which involve retrofit of parts by contractor personnel. this task should be added to the contract as a part of the ECP. you MUST tailor that Appendix. If a new contract is to be awarded solely for the development of a modification to an existing system.5. If the production program is to be competed. (5. however. of the integration (into system hardware) testing has been completed. and of notifying you when problems arise with the items or changes reflected in the information system.

2.1 Explanation of codes. However. Table III cites the applicability of both “minimum” and “optional” tasks.. 6. each revision would be a resubmittal of the complete data file in accordance with 4. Most of the Appendices in this The standard are intended to be invoked as a complete package.2. an ECP would be submitted as a digital data file.2.2 is not contractually invoked. requirements in Appendix H are the only ones that require tailoring.2). and when submittal of changed pages only is not desired.2.2.2b permits submittal of changed pages (hardcopy submittal) only.4. but that is usually necessary only when there has been a “shutdown” of the production line for a significant length of time or when a new contractor has won the competition for a (share of a) production contract. A number of words are used in Table III to designate the activity (i. af.3.e.3 provides some brief guidance on the application of the various paragraphs and the related Tasks on contracts.2. . 6.4.3. The columns are arranged to identify the normal application in the Demonstration/Validation. buying. It is possible that PCAS would be invoked in a later production contract. the Production.. 5.2.2. Table III has been included to provide guidance on the applicability of the various paragraphs and Tasks in Appendix H to a particular phase of a program. this paragraph must be specifically tailored out in the contract. 201) are normally considered to be “minimum” information system requirements. (5. When this is the case.2 is contractually invoked.2 provides some sample wording to be used in invoking these Tasks on a contract while paragraph 6. contractor. either of these.e.2. Tasks designated with a number of the format “X1X” are normally considered to be “optional tfrequirements.g.2.2 Use of Table III. and subsequent revisions to an ECP would be submitted as updated versions of that data file (i. when paragraph 4. or the support activity) normally held responsible for the Task information elements during each phase 115 .2b) If paragraph 4.3..3.2. Paragraph 6. Tasks designated with a number of the format “XOX” (e. and the Operation and Support phases of the life cycle.3.MIL-STD-973 production design). the Engineering and Manufacturing Development.

SUPPORT ACTIVITY REOUIRED CONTRACTOR OPTIONAL CONTRACTOR OPTIONAL CONTRACTOR OPTK)NAL CONTRACTOR OPTiONAL CONTRACTOR OPTIONAL CONTRACTOR OPTIONAL CONTRACTOR OPTIONAL REWIRED CONTRACTOR REWIRED SUPPORT ACTIVITV Approved Change Implement Spacifitzition Drawing Sottware Techmcal Spares Suppon Retrofit As-Built Manual RECOMMENDED BUYNG ACTIVITY OPTIONAl BUYING ACTIVl~ NOT APPLICABLE NOT APPLICABLE NOT APPLICABLE NOT APPLICABLE NOT Applicable NOT APPLICABLE NOT ipPLtCAEiLE NOT APPLICABLE NOT APPLICABLE NOT APPLICABLE NOT APPLICABLE II OPTIONAL SUPPQRT ACTIVITY OPTIONM sup~RT AcTlvl~ OPTIONAL SUPPORT ACTIVIW OPT)ONAL SUPPORT ACTIVITY OPTIONAL SUPPORT ACTIVllW OPTIONAL SUPPORT ACTIVITY OPTIONAL NOT APPLICABLE Purchase Equipment Kit Development Reczxd History * TASK 501 TASK 502 TASK 503 TASK 601 TASK 602 Maintenance Retrofit History Audtt Action REWIRED REOUIRED UPPDRT ACTIVITY SUPPORT ACTIVITY REOUIRED REOUIRED uPPORT ACTIVITY SUP REOUIFSED AS APPROPRIATE BUYING ACTIVIT%’ BUYING ACTIVl_W OPTIONAL kern Status Aud/t Actson hem History I 116 .A. LIFECYCLEPHASE BASELINE(S) NORMALLY IN EFFECT TASK 101 FuumoMU ULOCATSOMssuMi APPLICATION OF CSA TASKS Spacifioaticsn Revision Level Spedfication Revision History Drawing RevisiorI Level Drawing Rtstision History software Version Level Software Indentured Program Changes Change Change Version Listing Contracts in Pr~ss History Event Date History REOUIRED CONTRACTOR REOUIRED CONTRACTOR NOT APPLICABLE NOT APPLICABLE NOT APPLICABLE NOT Applicable NOT Applicable RECOMMENDED BUYING ACTIVITh REOUIRED BUYING ACTIVtT) RECOMMENDED BUYING Acmvln NOT RECOMMENDED BUYING ACTIVITY NOT RECOMMENDED BUYING ACTIVITI NOT RECOMMENDED BUYtNG ACTIVITY ~6D TSnem uxmlv mu T on 0 REOUIRED CONTRACTOR REWIRED CONTRACTOR NOT APPLICABLE NOT APPLICABLE NOT Applicable NOT APPLtCAELE NOT APPLICABLE RECOMMENDED BUYING ACTIVITY REOUIRED BUYING ACTIVITt RECOMMENDED BUYING ACTIVITI RECOMMENDED BUYtNG ACTIVITY RECOMMENDED BUYING ACTIVl~ REOUIRED CONTRACTOR REWIRED CONTRACTOR REOUIRED CONTRACTOR REOUIRED CONTRACTOR REOUIRED CONTRACTOR REOUIRED CONTRACTOR REWIRED SUPPORT ACTIVITY REOUIRED PPORT ACTIVITY REWIRED PPORT ACTIVITY FSEWIRED SUPPORT ACTIVITY REWIRED SUPWRT ACTIVITY TASK 102 TASK 103 TASK 104 TASK 105 TASK TASK TASK ltX 107 111 TASK 201 TASK 202 TASK 211 REWIRED PPORT ACTIVITY REOUIRED REWIRED CONTRACTOR PWRT ACTIVITY RECOMMENDED 1 RECOMMENDED BUYS4G ACTIVITY SUPPORT ACTIVIT# REOUIRED REWIRED BUYtNG ACTIVIW ~p~RT AcTlvl~ RECOMMENDED RECOMMENDED BUYMG ACTIVITY RECOMMENDED BUYING ACTIVIH OPTIONAL SUPPORT ACTIVITY OPTIONM SUPPORT ACTIVITY TASK 212 Change Event History TASK 213 Date Search RECOWAENDED BUYING ACTIVITY MOlnmo n’mnMN.MIL-STD-973 TABLE III.cllwr?u RECOMMENDED CONTRACTOR OPTiONAA CONTRACTOR NOT APPLICABLE NOT APPLICABLE NOT APPLICABLE NOT APPLICABLE NOT APPLICABLE NOT APPLICABLE NOT APPLICABLE NOT APPLICABLE NOT APPLICABLE REWIRED BUYING ACTIVITY OPTIONAL BUYING ACTIVITY TASK 301 TASK 401 TASK 411 TASK 412 TASK 413 TASK 414 TASK 415 TASK 416 TASK 417 Approved Changes OPTIONAL RECOMMENDED SUPPORT ACTIVITY BUYING ACTIVITY 1 WEo REWIRED ‘Un:g%g%mm .

active SAMPLE D: The contractor shall provide fulfilling the requirements chanqe Drocessinc7 information) (eQq. Task must be specifically cited to constitute a contractual If a particular requirement appears to be requirement. . d. of the program. Appendix H 6.normallY.normally. this is used for “optional” are excessive for the phase of the program or which are required only in later phases for programs with critical readiness/availability requirements and/or with very complex logistics support systems. 201 and 202) . as follows: a.2. the support activity will normally have the total responsibility. optional . a b. . required . recommended .21 of MIL-STD-973.3. -— e.. not recommended requirements which not c.normally. it cannot be completely invoked (nor should any program want to completely invoke it) in a contract merely by Each individual paragraph and/or numbered citing the Appendix.q.-. this is used for requirements which are excessive for most programs but which may be required for programs with critical readiness/ availability requirements and/or with very complex logistics support systems. H. ) Other words are used to designate the applicability of the particular Task to this phase of the program.MIL-STD-973 (NOTE: During Demonstration/Validation phase. the buying activity can usually handle the relatively simple information system. 117 . appropriate .5. appropriate for the contract for this phase of the program.these are considered the minimum acceptable capabilities of the information system.these usually relate to information available as a result of some “minimum” Tasks in the early phases of the program and of some’’optional” Tasks whose accomplishment provides enhanced management capabilities for many programs. during the Operation phase. this indicates that the related documents or items do not exist during this phase or are not yet controlled by the buying activity. wording similar to the following sample can be used: (e.cf.2. whether the information is obtained from the contractor or from government activity.2 must be tailored. Sample wordinu for contractual taskinq.. paragraph and Tasks (e. Appendix H.

5. This information will provide the capability to determine the expected configuration of each delivered production unit in the inventory.1) Descriptive documentation and identification numbers.. until the completion of the development program and the delivery of operational units and logistics support elements. The following specific tailoring information is provided to supplement the guidance provided in Table III.1. This paragraph is usually left out of contracts unless the Government wants to monitor the contractor’s preparation of the change as well as the government processing of the change. 211 .1. Once into the production phase.g. The program office. but this information can be very expensive to obtain and 118 d.1.5. However. 101). ] — a.2. so the buying activity may be able to track this information until the beginning of production.213) should be not invoked unless the basic Task 201 is invoked. usually has the most complete and timely access to the details of the inhouse processing information. The History Tasks (e. both the contractor and the government have the ability to gather and control this information. the contractor’s existing engineering release system will normally contain this information. certain of the optional Tasks may also be invoked in conjunction with Task 401. c.4) Implementation of approved changes. only a few of the implementation events are applicable. (H.2) Tracking active change processing. or government managing activity.3 S~ecific tailorinu notes.g.1.MIL-STD-973 6.5. 102) should not be invoked without the basic Tasks (e. This paragraph and certain of the Tasks will be invoked on most contracts since the contractor usually has the most complete and timely access to the details of this information. (H. b.3) Approved changes to CI/CSCI configuration. This paragraph may be invoked or deleted.5. (H. The optional Tasks (i. This paragraph and Task 401 will normally be invoked on most contracts since the contractor usually has the most complete and timely access to the details of this information. [NOTE: The number in parentheses at the beginning of each note is the number of the primary paragraph(s) to which it applies. However... (H.2. .e. so it may be easiest to obtain it from that source.

the PCA.1 5. most appropriate if it were desirable to obtain a deliverable copy of the complete history of the audit action items for retention by the Government. on the Contract Data Requirements List (DD Form . excepr where DOD FAR Supplement 27.3.5 5*4.4. This tracking could be accomplished by either Task 602 would be the contractor or the Government.4 DID Number DID Title Contractor’s CM Plan Engineering Release Record Interface Control Management Data Interface Control Drawing Documentation Advance Change Study Notice Engineering Change Proposal Request for Deviation DI-CMAN-80858A DI-CMAN-80463 DI-CMAN-81247 DI-CMAN-81248 DI-CMAN-81246 D1-CMAN-80639 DI-CMAN-80640 119 .1 5.MIL-STD-973 L These requires considerable manpower to monitor. This paragraph Tracking audit action items. The following Data Item 6.5. (H.2.1.6) and Task 601 would normally be invoked on contracts for the FCA and/or which also invoke the requirement f.5.5.3 Data requirements. when . (H. in order to obtain the data.4. Descriptions (DID’s) must be listed. 1423) .5) Configuration of units in the field.1 5.2.3.2 5. it should be used from the start of the delivery of production units to simplify the transition from a contractor to a government information system when production is complete.3. e. they would be most useful in situations where lack of supportability for the system/item can have significant National Security impacts to the extent that such detailed information is necessary to minimize such supportability problems. optional Tasks should be used selectively.3.3.7. J?eference Paraurauh 5.1.2. If so.1 5. 1. . is applied on a contract.2.3.7. This paragraph and Task 501 are normally invoked only for The government support the Production phase contract. this standard . . activity usually has an existing information system which will provide the information required for Tasks 502 and 503.3. as applicable.475-1 exempts the requirement for a DD Form 1423.

The current issue of DOD 501O.6.7 5.6 5.1. and Computer Software (Appendixes G.ion Audit Summary Report Configuration Audit Plan Conference Agenda Conference Minutes The above DID’s are those cleared as of the date of this standard.MIL-STD-973 Reference paracrra~h 5. and I only) 6.2 DID Number DI-CMAN-80641 DI-CMAN-80643A DI-CMAN-80642A DI-CFIAN-81253 DI-CMAN-81245 DI-CMAN-81022A DI-CMAN-80556A DI-ADMIN-81249 DI-ADMIN-81250 DID Title Request for Waiver Specification Change Notice Notice of Revision Configuration Status Accounting Information Installation Completion Notification Configurat.1.6.5.2 5.1. Deviations.5.5 Subiect term (kev word) listinq. Equipments.5 5.12-L.Short Form MIL-STD-481 MIL-S’X’D-482 Configuration Status Accounting Data Elements and Related Features Configuration Configuration Management Management Practices MIL-STD-483 MIL-STD-1456 MIL-STD-1521 Plan Technical Reviews and Audits for Systems.4 Su~ersession data.4.4.4 5.6. that only current.4.1. and Waivers Configuration Control . H.2 5. Acquisition Management Systems and Data Requirements Control List (AMSDL) must be researched to ensure cited on the DD Form 1423.2 5.6.4.Engineering Changes. The following DoD and military standards are superseded by MIL-STD-973: MIL-STD-480 Configuration Control .8 5. cleared DID’s are 6. Advance change study notice Baseline Configuration audit Configuration control Configuration control board Configuration documentation 120 .

MIL-STD-973

Configuration identification Configuration item Configuration management plan Configuration status accounting Computer software configuration item Developmental configuration Deviation/Request for Deviation Effectivity Engineering change. proposal Engineering release Hardware configuration item Interface control Interface control working group Non-developmental item Notice of Revision Specification Change Notice Version Waiver/Request for Waiver Work breakdown structure

121

MIL-STD-973 APPENDIX A

CONTIUiCTOR’S

CONFIGURATION

MANAGEMENT

(CM) PLAN

A.1

GENERAL

A.1.l -“ This Appendix contains the format and content preparation instructions for the Contractor’s CM Plan required by paragraph 5.2.1. This Appendix is a mandatory part of this standard. The information contained herein is intended for compliance.
A.1.2 A~D liability. The provisions of this Appendix whenever the contractor is required to prepare a CM plan. A.2 This A.3 APPLICABLE section DOCUMENTS to this Appendix. apply

is not applicable

DEFINITIONS

A,3.1 Definitions used in this APP endix. For the purpose of this Appendix, the definitions contained in Section 3 shall apply. A.4 GENElU4L REQUIREMENTS

Content and format instructions. A.4.1 The plan shall be prepared on bound 8 1/2 x 11 inch 20 pound copier paper (hard copy) or a form of electronic media as specified in the contract. Each page prior to Section 1 shall be numbered in lower-case reman numerals beginning with Page ii for the Table of Contents. Each page from section 1 through the end of the document, shall be numbered consecutively in Arabic numerals, For hard copy format, the document may be printed on one or both sides of each page (single-sided/double-sided) . For single-sided documents, all pages shall contain the document control number in the top right-hand corner. For double-sided documents, all even numbered pages shall have the page number on the lower left-hand side of the document and all odd-numbered pages shall have the page number on the lower right-hand side of the document. For doublesided documents, the control number shall be placed in the top right-hand corner for each odd-numbered page, and in the top left-hand corner for each even-numbered page. All paragraph and subparagraph headings listed in paragraph A.4.2 below shall be included in the plan. In the event that a paragraph or

122

.-

MIL-STD-973 APPENDIX A subparagraph is tailored out, the following statement shall be added directly following the heading: “This section (or paragraph or subparagraph, as applicable) has been tailored out.” A.4.2 Organization of the following: A.4.2.I A.4.2.2 A.4.2.3 A.4.2.4
A.4.2.5 A.4.2.6
A.4.2.7

of the document.

The plan shall consist

Cover Page Record of Reviews and History page Table of Contents Section 1. Introduction
Section Section 2. 3. Reference documents

Organization

Section 4. milestones Section 5.
Section 6.

Configuration management phasing and Data management
Configuration identification

A.4.2.8
A.4.2.9

A.4.2.1O A.4 .2.11
A.4.2.12

Section 7. Section 8. Section 9.
Section 10.

Interface management Configuration Configuration
Configuration

control status accounting
audits

A.4.2.13

A.4.2.14 A.5

Section 11.

Subcontractor/vendor

control

DETAILED REQUIREMENTS

A.5.1 Content and format. The content and format of the plan shall conform to the following paragraphs. This page shall contain the document control number in the upper right-hand corner. In the center of the page, these words shall appear in the following format:
A.5.1.1 Cover Paqe.

123

MIL-STD-973 APPENDIX A CM PLAN FOR THE [Project Name or CI nomenclature and number] CONTWCT NO. [contract number]

CDRL SEQUENCE NO. [CDRL number] [Date of document - day month year] Prepared for: [Contracting Agency Name, Department Code] Prepared by: [Contractor name and address] [CAGE code] A.5.1.2 Record of Review and History paqe. This page shall include the review and approval dates of all changes to the plan. A.5.1.3 Table of Contents. The Table of contents shall list the title and page number of all titled paragraphs and subparagraphs. The Table of contents shall then list the title and page number of all Figures, Tables, and Appendices, in that order. A.5.1.4 include:
a.

Section 1.

Introduction.

This section shall

The purpose, scope and specific contractual applicability of the configuration management plan and the program phase(s) to which it applies; A brief description of the system or top level CI, and of the component lower level CIS, using approved CI when available, to which the CM Plan nomenclature pertains; Reference to applicable directives or glossaries containing definitions of terminology and acronyms used in the plan; and

b.

c.

124

MIL-STD-973 APPE!JDIX A

d.

A description of the plan’s major features and objectives and a concise summary of the contractor’s approach to CM, including any special conditions (such as large number of organizations, security constraints, interoperability constraints, unique contracting methods, non-developmental items, etc.) upon which the approach is based.

This section Section 2. Reference documents. A.5.1.5 shall list the specifications, standards, manuals and other documents, includinq contractor policy directives, referenced in the Plan by title, ~ocument numb~r, issuing authority, revision, and when applicable, change notice, amendment number, and date of issue.
This section shall Section 3. Organization. A.5.1.6 describe and graphically portray the contractor’s organization with emphasis on the CM activities, and which shall include: a. The relationships and integration of the contractor’s project organization and functional organization; Responsibility and authority for CM of all participating groups and organizations including role in configuration control boards, and the integration of CM functions with other program such as technical reviews; activities

----

b.

their

c. d.

Identification of the contractor’s its responsibilities; and

CM

organization

and and

Interfaces between the contractor’s CM organization the Government, subcontractors, and associate contractors.

Section 4. Configuration management Dhasinq and A.5.1.7 This section shall describe and graphically portray milestones. the sequence of events and milestones for implementation of CM in phase with major program milestones and events, including as a minimum: a. b. Release and submittal of configuration documentation in relation to program events (e.g. , technical reviews) ; Establishment of internal developmental and contractual baselines; 125 configuration

3. b.9 Section 6.8 Section 5.5). This section shall describe the contractor’s procedures for meeting the requirements of 5. Conduct of configuration audits.3) A. Configuration identification. 126 . Allocated and Product baselines. and f. nomenclature.3.7.3. and software identifiers to software and firmware (See 5.3. e.3.4). of configuration control boards. Establishment of internal and Government configuration d. definition of the configuration documentation required for each and graphic illustration of configuration documentation relationships (See 5. drawing and software development libraries and corrective action process (See 5. Engineering release and correlation of manufactured products (See 5. Selection of CIS (HWCIS and CSCIS) (See 5. d. serial numbers and part number to hardware. This section shall describe the methods for meeting the configuration management technical data requirements under the computer-aided acquisition and logistic support (CALS) requirements of the contract.6 and 5. Establishment of the Functional. including: a. Data management.l. and Assignment and application of configuration identifiers including document numbers. Implementation of a status accounting information system and provision of reports/or access to the status accounting information. A.3).MIL-STD-973 APPENDIX c.2).3.5.5. Establishment and management of developmental configuration including document.3.1. e. (See 4.5). c. A Implementation control.

4. processing and maintaining data necessary to provide contractual status accounting information via reports and/or data base access.4.4). Configuration control. including: a. b. d. The contractors methods for collecting.3 and 5. responsibility.4.2. Classification of changes.5. 1.1.5. c.4.3. Processing of Class I Engineering Change Proposals (ECPS) and Value Engineering Change Proposals (VECPS) (See 5.12 Section 9.7) This section Section 8. Identification of current approved configuration documentation and configuration identifiers associated with each CI. 127 .2) .7). f. e.2. establishment of interface agreements and participation in interface control working groups (ICWG). as applicable: (1) system content b.4.MIL-STD-973 APPENDIX A This section Section 7. recording. 9* Processing of Notices of Revision This A. A.1O shall describe the procedures for identification of interface requirements. and the level of authority for change approval/concurrence (See 5.1.2 and 5.4. and authority of configuration control boards. (See 5.5. Processing of Class II ECPS (See 5. Functions.3). Description of reports/information related to. A.4).6). Interf ace management.11 shall describe the contractor’s procedures for meeting the requirements of 5. Processing of Requests for Deviations and Waivers (See 5.4. including: a.4. Processing of Specification (See 5.5 and Appendix H.4. section shall describe the contractor’s procedures for meeting the requirements of 5.2. Conficluration status accounting.2. and Change Notices (NORS) (SCNS) (See 5.

14 section shall ensure subcontractor/vendor compliance with configuration management requirements (See 4. procedures. Status of proposed engineering changes from initiation to implementation.-— MIL-STD-973 APPENDIX A (2) (3) (4) (5) (6) c. including: Plans.1.13 Section 10. and format for reporting resuits of in-process configuration audits.1) . of 5. I.5. status and disposition of discrepancies. Configuration audits. This the methods used by the contractor to A. 128 . Results of configuration audits. This section the A. - Methods of access to information in status accounting information systems and/or frequency of reporting and distribution.5. Status of requests for critical and major deviations and waivers. and schedules for functional and physical configuration audits. shall describe the contractor’s approach to meeting requirements a. Subcontractor/Vendor control.6. Section describe 11. documentation. Traceability of changes from baselined documentation of each CI. and Effectivity and installation status of configuration changes to all CIS at all locations.

procedures the items for the The contractor shall have release of engineering data initial being purchased by the Government and for 129 .3. This Appendix is a mandatory part of the standard. B.2 APPLICABLE DOCUMENTS This section is not applicable to this Appendix. B. b.1. The information contained herein is intended for compliance. and suPPliers” B. For purposes of this Appendix. vendors. Elements of data required Production release functional capabilities and procedures Release of engineering changes Field release functional capabilities and procedures. The contractor shall be responsible to the Government for compliance by subcontractors.3 DEFINITIONS B. B.1 Definitions used in this APP endix. the definitions contained in Section 3 of this standard shall apply.4.1. c.MIL-STD-973 APPENDIX B ENGINEERING RELEASE RECORDS AND CORRELATION OF MANUFACTURED PRODUCTS GENEML B.1 B.l Scope.1 documented describing GENERAL REQUIREMENTS Documented ~rocedures.2 ADP lication. The requirements of this Appendix apply to the contractor’s engineering release system pertaining to: a. The requirements of this Appendix apply to all contracts requiring the preparation of engineering drawings and specifications for CIS and/or requiring the preparation of software documentation/code and specifications for CSCIS to the extent specified in the contract. d.4 B. This Appendix establishes the minimum requirements for achieving the proper relationship between engineering/manufacturing data and manufactured CIS.

B.1. B.1. CI elements: CI number Delivered CI serial numbers Top assembly drawing number number.1 a. Verifying that engineering documentation has been revised and released in accordance with changed contract requirements Assuring that engineering changes have been accomplished and incorporated into deliverable units of the CIS as required by the released engineering documentation c. Engineering release records shall be used to satisfy the requirements for traceability of deviations.2 a.5.5. B.4. The contractor shall prepare and maintain engineering release records in accordance with contractor formats and procedures to fulfill at least the minimum requirements specified herein. The shall B. Only one release record shall be maintained for each drawing number. CI specification Drawinq number identification B. the subsequent Reconciling engineering work authorizations contract requirements to changed b.1. 5.MIL-STD-973 APPENDIX B control of that engineering data. c. and engineering changes.5 DETAILED REQUIREMENTS B. 1. both Class I and Class II.1 Elements of data required for hardware items. d. including the incorporation of approved engineering changes.1 Data elements. The contractor shall ensure that the system is capable of: a.2 Enqineerinq release records. waivers. Drawing elements: 130 . contractor’s engineering release records for hardware items contain the following information. b.1.5.

d. Drawing title CAGE number Number of sheets Date of release All released change letters Date of each change letter release Each effecting change document numbers. Elements of data reauired for software items.3 a. c. To the B. Controlling Component part numbers released. f.2 Production release functional ca~abilities. including drawings and associated lists.1. Part number elements: drawing number B. shall be capable of determining the following released engineering requirements: a. e. The composition of any part at any level in terms of subordinate part numbers All next higher part numbers in which the part is used (or next assembly numbers) b. b.5. The B. the contractor’s release function and documentation. e.MIL-STD-973 APPENDIX B b.2 contractor’s engineering release records shall reference the CSCI Version Description Document (VDD) which contains all of the required data elements.1. c.5. extent that the contractor has detail design responsibility. d. The composition of any CI in terms of component part numbers and subordinate CI numbers The composition of any CSCI in terms of components and units and subordinate CSCI numbers The item part number and serial numbers. 9“ h.5. 1. if serialized~ on which any subordinate provisioned or to be provisioned part is used 131 .

1. or supplier part numbers for all such parts used in the contractor’s deliverable units The contractor specification document.MIL-STD-973 APPENDIX B - f. h. vendor. or source control drawing numbers associated with any subcontractor.5. The change shall be documented and released prior to formal acceptance of the deliverable unit where the engineering change is first installed. B. j. vendor. or supplier part number. B.3. i. and of retaining the record of superseded configuration requirements. specification control drawing numbers.5. numbers or nomenclature of all 9. The release function documentation shall be capable of identifying engineering changes. including week of incorporation The CI numbers and CI serial numbers. 132 . part standard parts used as a component of any nonstandard part k. The CI number and CI serial numbers (effectivity) on which any subordinate provisioned or to be provisioned part is used Identification numbers of class I changes which have been released for any specific serial-numbered unit of a CI Identification numbers of all class II changes which have been partially or completely released for any particular part. which constitute effectivity of each class I engineering change The military specification. or CSCI version numbers. The subcontractor.1 All approved Class I and II engineering changes released for production shall be identified by identification numbers. The contractor’s release function shall verify the approval/concurrence status of each Class I/Class 11 change prior to the release of the related documentation for use in the generation of deliverable units. or milita~-y standard. affecting CIS which have been formally accepted by the Government.3 Release of en~ineerinq chanqes.

Complete verification of the production incorporation of contractually authorized engineering changes shall be accomplished for all CIS in accordance with MIL-I-45208 or MIL-Q-9858.5. Superseded requirements shall be retained in all release records for the documentation until status accounting records indicate that superseded no longer exist or until closeout of all configurations b. action items from the FCA. Engineering changes to CIS which have been formally accepted by the Government.MIL-STD-973 APPENDIX B B. whichever is a requirement of the contract. “ -.4 Release functional capabilities durinq testing. Superseded requirements shall be retained as historical information. 133 . or into complete blocks of units.5. Each Class I engineering change approved by the Government shall be incorporated into all units. however. within one mission.5. shall be released for Government approval and action. design.5 Correlation of enqineerlna chanqes with manufactured product.2 Documentation of the actual released configuration for each CI at the time of its formal acceptance shall be retained in release records for the time specified in the retention of records requirements in the contract. series of the CIS affected. series or type. Prior to establishment of the PBL. B. Superseded requirements may be replaced by superseding requirements in the release records for the units which are being logistically supported by the contractor. model . and which are not being logistically supported by the contractor. B. detail design documents under the control of the contractor during developmental testing and/or initial operational testing shall be kept current with all test activity changes/modifications and releases as follows: a. to allow verification of test data and completion of the FCA.3. whichever is longer.

2 ADI) lication. and product baselines or to record changes from an established configuration baseline. The contractor shall use an ERR to record the release of configuration documentation that establishes the functional. 2617C is authorized.1. when additional space is required. C.5 DETAILED REQUIREMENTS. or an authorized equivalent automated record containing the same information as the paper Local reproduction of DD Forms 2617 and document description. This Appendix is a mandatory part of the standard.2 EnuineerinQ Release Record.4.3 DEFINITIONS C. For the purposes of this Appendix. completion of the DD Form 2617. and DD Form 2617C. Figure 8b.MIL-STD-973 APPENDIX C INSTRUCTIONS FOR THE PREPARATION OF AN ENGINEERING RELEASE RECORD (ERR) UTILIZING DD FORMS 2617 AND 2617C C. C. “Engineering Release Record Continuation Page”.1 GENERAL C. C.1. The information contained herein is intended for compliance. Figure 8a.1 Use of DD Form 2617 and 2617C. allocated.5.4 GENERAL REQUIREMENTS C. C. This Appendix establishes uniform requirements for the preparation of the DD Form 2617.4. C. the definitions contained in Section 3 of this standard shall apply.3. and DD 2617C. The provisions of this Appendix apply whenever DD Forms 2617 and 2617C are utilized to record release of configuration documentation.1 Block 1. C. “Engineering Release Record”.1 Definitions used in this A?m endix. ERR NO. Detailed instruction for C. The contractor shall use DD Form 2617.l ScoDe. Enter the unique ERR identification number or the number assigned by the Government. 134 .2 APPLICABLE DOCUMENTS This section is not applicable to this Appendix.

8 Block 8. appropriate block to identify the configuration baseline established or changed. C.5.MIL-STD-973 APPENDIX C C.7 Block 7.g.5. Enter the C.5.3 Block 3. Enter the CAGE Code of the C. when applicable.. Check appropriate block C.4 agency. each separated by a hyphen (-). C. System or Configuration Item Nomenclature Enter the system or configuration item and Part Number. part number and functional assembly nomenclature of the lowest functional assembly to which the entire ERR applies. Functional Assembly Nomenclature.5. Remarks or Miscellaneous.5 Block 5. minor item. e. The date of the completion of Block 13 will then be entered in Block 2 in six numeric characters.5. Block 4. Date. if desired. e.5.6 Block 6. . CAGE Code.5. Data Released or Revised. month. EXCEPTION: sheet documents will be entered as a single line entry when all sheets are maintained at the same revision level. C. year.2 Block 2.1 Block ha.9 Block 9. DODACC . Multidocument and sheet as a separate line entry. document listed in Block llc conforming to Cataloging Handbook H4/H8.5. 135 . nomenclature and part number.5. This identification numbers of additional ECPS. Tv~e of Release. partial or complete releases. block can also be used to note the item which the documentation identifies. Procurinq Activity Number.5. critical component.1O Block 10. to indicate whether release is establishing a baseline (initial) or a change to the established configuration baseline. Enter C. Enter each C.5. “91-02-06”. configuration item. or any other remarks pertinent to the data being released. Enter the ECP number and the date approved on the lines provided. day. Baseline Established or Chanued. when applicable.11. Entry will not be made in Block 2 until completion of Block 13 (Approved by) is accomplished by an authorized official. C. Enter the DODACC of the procuring Check C. system specification.11 Block 11.g. To be used by Government for entry of internal processing number.

2) Version Description Document C.Troop Installed Development Specification Product Specification Computer Program Test Procedure (DOD-STD-1679A) Computer Program Test Specification Data Base Design Document Firmware Support Manual Interface Design Specification (DOD-STD-1679A) Interface Requirements Specification Life Cycle Software Support Environment User’s Guide Preliminary Description Document (DOD-STD-1679) Program Design Specification Program Package Document Program Performance Specification (DOD-STD-1679) Software Product Specification Software Re~uirements Specification System Specification Software Test Description Software Test Procedure (DOD-STD-2167) Test and Evaluation Master Plan (DOD 5000.2 B ck 1 Enter document type code TYD (commonly used a$. 136 . order by types of documents in ascending numerical and alphanumerical sequence.11.3 Enter documents in a logical Block llc.5.5.11.11.4 Paqe of.ony~ ~. Group drawings by size. Number.5. Enter the particular page Block lld. show~”in the following examples): QQDE Blank SQ IL EL DL PL Ps ED EM ::5 c-5 CPTPR CPTS DBDD FSM IDS IRS LCUG PDD PDS PPD PPS SPS SRS Ss STD STPR TEMP VDD J30CUMENT TITLE (EXAMPLES) Drawings Quality Assurance Provisions Index List (MIL-STD-1OO) List of Inspection Equipment Data List (MIL-STD-1OO) Parts List (MIL-STD-100) Special Packaging Instructions List of Equipment .MIL-STD-973 APPENDIX C C.Depot Installed List of Equipment .Manufacturer Installed List of Equipment . required for single page documents. C. No entry number of the total count of pages in Column he.

11. Chanqe. C. Block hi. printed. 137 .g.MIL-STD-973 APPENDIX C L Block he. Other.9 (1) f Chanqe (CH) . (2) C. To be completed by the Detailed Instructions for Completion of the DD Enter the same number as Block 1.6 Block hf. For original documentation.7 Block Ilq. C.5. C. each separated by a hyphen (-).14 Form 2617C. The total count of pages No entry required for single page Letter. day. 11.5. C.1O C.14.5 comprising the document. Enter type. Enter l~Xt’or each document listed for which the revision level of an established baseline document is being changed. ERR No.5. Submitted by.5. C.11. C.5..11. authorized Government official.8 (1) (2) Block llh.5. year.11. Block hi. Enter “X” for each listed document which is to be deleted from an established configuration baseline. Enter “X” if the document is being initially released.5. Initial Release (IR). Pacies. e. For optional use. New APP lication Release (NAR) . Enter the new revision symbol C. ADD roved by.5. Enter “X” if the document has a new application. or stamped name and signature of responsible drafting or engineering services contractor organization or engineering segment. Enter the document date in six numeric characters. C. documents. enter a hyphen (-). month.1 entered in Block 1 of Page 1 of the ERR. to be issued for the document listed in Column llc.11.12 Block 12. “91-02-06”. Date. Cancellation (CAN) . Release.5.5.13 Block 13.

138 .9.2 Block 2. Follow instructions C.f “91-02-06”.14. Blocks 3a throuuh 31.1 through C. Block 13.11.5.5.MIL-STD-973 APPENDIX C C.5. will then be entered in six numeric characters. year. each separated by a hyphen (-)t e. Entry will not be made in Block 2 until completion of Page 1.11.3 contained in paragraph C. completion of Page 1. Block 13 (Approved by). month.14. Date. is The date of the accomplished by an authorized official.1O. day.5.

DATE (YvMMDD) 3...w-!ng !.ding ?nr IIMC for . APR 92 Figurl Together wfth 00 Form 26 I 7 replac~s DARCOM Wlwh Is obsolete FOrm 17Z4R.q M m. VA 121 8 2~102.. onO$t*tOr mat8wmmt.’aqe ‘0! _ .c I.llO.. O~T.00n. TYPE OF RELEASC (X OW) INITIAL CHANGE 7. ol.910. SUBMlllED BY (S~gndwc) 13 APPROVEO BY (519naure) DD . ca..mamq . matw !09.d n.q kt*nfof 2htsc011w./ Form -.ret cl !!M.aq*! ~aot-of= @rn Ufl... form. IwIOrtw !04 . I!WI nurwn iooec-wtmw of D*Wwe Wa**I .te ~K14 A~(.*l OI?O [O?O~ 0.amgw~grwo. .MIL-STD-973 APPENDIX C ENGINEERINGRELEASERECORD (ERR) uU8ct*wn4. I. DATA RELEASEO OR REVISEO DOCUMENT CAGE CODE L REVISION PAGE of d PAGES e LETTER f DATE (v vMuOOt 9 q TYPE b NuMBER c RELEASE h (R NAR CHANGE C)THER cm CAN J 12.cv06of mfofmat(on .rr au. d .OVERNMENT ISSUING COfJTRA~lNG OFFICER FOR THE CONfRACT/PROCURING ACTIVITY NUMBER LISTED IN ITEM 3 OF THIS FORM ERR NO. I*.t tot rrd.9h**..*..*fw~\ \cw Km O..htb.00) vv**fiI. ?wmaw 01 e.. O. W**q. Engineering 15: Release Record .. .910.9 aal# xwrcn ?t?h*r.bwtOtWO~l<rOf Ww9*m~~~*aB.wuc mom WCIC..on k.!. “wand CWILII..qtO..– ~dqes 9a. 2. m...011. *fbqc $rnd CCmmr”l% Wga. J$!H. Form Approbed I OMO NO 07040188 b. RETUaN COMPLETED .nvmq YF. how P..torm.( . WSPWW . tm. t)o. FORM TO THE ‘L[ASC Do NOT RfTURN YOUR COMPLETtO FORM TO EITHER Of THESE AOORESSf S. .wnao. nq r.q ..j IS Ictf. r.fae. re. 2617.d.*. PROCURING ACTIVITY NUMBER ECO NuMBER 4 b DOE2AAC EFf ECTIVE DATE (VYMMCIO) . 0( )?503 DASELINE ESTASLISHEO OR CHANGED ~UNCTIONAL PUODUC~ FUNCTIONAL n (~ o~t) 6. .J ALLOCATED ASSEMBLY NOMENCLATURE SYSTEM ~CONFIGURATION NOMENCLATURE ITEM b PART NuMBER 0. REMARKS/MISCELLANEOUS 1.

mq rmIm9 O*W wurcm y.C-{IAV I* lIW @ -.. ** I-. of . D.W* OC/0s01 FORM TO flTJ+tR OF 7HE5E ADDRES5ES.e=.3.na Report. w m. *c.1t $ .. PLCASE 00 NOT RETURN YOUR COMPLETED GOVERNMENT ISSUING CONTRACTING OWICIR COMPLETED OD FORM 2617 !.~a’’&’%’kfi~V.M IO..e $*W comments <aqwaonq m.qlOn ..w a 101 IaOu<In lIW buIO*.f M. taw.”10.. t Of Odrw *a8~#. Together wfth DO Form 2617 whch IS ?QPIJCCS DARCOM OtJJOl?t? Form 17?4. RETURN COMPLETED FORM TO THE FOR THE CONTRACT) nOCURl~G ACWIT~ NUMCER LtSTED IN lTtM 3 Of THE 2.MIL-STD-973 APPENDIX C ENGINEERING RELEASE RECORO (ERR)(Contmuatlonsheet) md mamt. bna . OMO 07040188 BUWU mamma bwdan to. (GI q C180.*t-i d m.e!mw. R Paqe _ .t)nl 0. o .wbdauo~tn $wwm. m. q com~.*.*I@w I hO. dam - cottiI06 w.~@ of +Mfovmavofi o awmmd 10 q .~ . 10 Dernn-r.bW$..l?wnq lM (oII?cWO. ..VA JJ)#2~101 . . fRR NO.)f _ Paq+ Figure Engineering Releaae Record Continuation Sheet 140 . . .dq@ *OW*OI. Owrmtm. APR 92 8b. other . . Form Approved NO I Imtturt Iom bwa.rII. (OJMO190)WM. . DATE [t’YMMDO) 1 DATA RELEASED OR REVISED DOCUMENT REvISION PAGE d 0! CAGE CODE a TYPE b NuMBER c PAGES t LETTER f DATE (rrm~oa 9 RELEASE n IR INAR CHANGE OTHER cl.00 2617C.rrno Offm.C. fO*ma 140.d B. raw tor Wormat.om . qf. t..! CAN f DO Form 90 .n ewnw.

4.4 GENEWL REQUIREMENTS D. The information contained herein is intended for compliance.1 Use of the ECP forms. Supplemental page(s) may be used with the ECP forms as necessary.2 A~~lication. only DD Form 1692 (Page 1). This Appendix establishes uniform requirements for the preparation of DD Forms 1692 through 1692/6. When ECP Short Form procedures are specified. DD Forms 1692 through 1692/6 (See Figures 9a . HWCIS.4.10) D.3 DEFINITIONS D. CIS. and CSCIS. Engineering Change Proposal . D. For purposes of this Appendix. the definitions contained in Section 3 of this standard shall apply. (See 5.4.4.3.1.l Sco~e. (See MIL-STD-1806) 141 .3.4. D. Local reproduction of DD Forms D. the ECP package shall include supporting data.1. This Appendix is a mandatory part of the standard.2 SUPD ortinu data.MIL-STD-973 . The provisions of this Appendix apply to all ECP preparing activities and to proposed engineering changes for systems. 1692-1692/6 is authorized. In addition to the information required by this Appendix.3 Local reproduction.1 Jlefinitions used in this l+~~en dix. D.4 Distribution statement.1 GENERAL D. Pages 1-7.9g) shall be used for the submission and processing of all class I engineering changes. D. with applicable enclosures is required. D. APPENDIX D INSTRUCTIONS FOR THE PREPARATION OF AN ECP UTILIZING DD FORMS 1692 THROUGH 1692-7 D.2 APPLICABLE DOCUMENTS This section is not applicable to this Appendix. The appropriate distribution markings shall be affixed to the ECP package in accordance with the requirements”of the contract.

5.5 applicable ECP as defined in 5.4 name and address of the contractor or Government activity. Block 3.5. Enter I or 11 for the D. submitting the ECP.1 or 5. When the contract contains a value engineering clause.2. Originator name and address. D.2.2. which is applicable to the proposed Class I engineering change. (See Figure 9a). Class of ECP.5.2.1 ECP . D.4. Block 5. D. Enter the D. Enter the submittal date of the Enter the Block 4.5.4.1 Value enqineerinq ECP .1. the Government representative will assign the appropriate justification code for other than VECPS. each value engineering ECP shall be identified both by the “V” in Block 6 and by the entry of the following notation at the top of Page 1 of the ECP form: IIVALUE ENGINEERING CHANGE pURSIJANT TO CONTRACT CLAUSE.MIL-STD-973 APPENDIX D Detailed instruction for D. as defined by 5. Procurinu activity number.4.1. Enter the DODAAC of the procuring Block 1. Paqe l“.2.6. if desired.3 activity. Block 6. CODES Bc- — DoPRsv- Interface Compatibility Deficiency Operational or logistics support Production stoppage Cost Reduction Safety Value engineering D.5. Block 2.1 DD Form 1692.1.5. 1. DODAAC. the Government representative shall assign the change classification. “Enuineerincl Chanqe Proposal.1. D.1.2 Government for entry of internal processing number.4.5. Date.1. completion of the DD Forms 1692 through 1692/6.5. Justification code. ” 142 .3.5 DETAILED REQUIREMENTS.6 justification code. To be used by D. When ECP short form procedure is specified by the contract. When short form procedure is specified in the contract.

8.2 Block 8b. Once an ECP number is D. D. the basic ECP shall be identified with the number prescribed above and each related ECP shall be identified by the basic number plus a separate dash number. 1. 1. Enter the CAGE code as shown in Defense Logistic Agency (DLA) Cataloging Handbook H4/H8 for the activity originating the ECP.5. the Government representative will assign the appropriate justification code.5. ECP number. Block 8d. type. or ECP numbers may be assigned in a separate series for each system that the contractor is producing. Model/TYPe.8.I.3. D. Svstem designation.4 assigned to the first submission of a change proposal. enter the CSCI identification number. For CSCIS.8 Block 8. that number shall be retained for all subsequent submissions of that One of the following methods of assigning ECP change proposal. dash number. if known. The number of characters in the ECP number. . Priority. short form procedure is specified by contract. When an ECP is split into a basic ECP and related ECPS.5. The contractor shall recommend D. and the 15 character limitation in paragraph (2) above is not exceeded. for each CAGE Code identified activity. .1.1 designation of the CI for which this proposal is being filled out .2. Urgent or Routine) as defined in 5.1. and revision identification shall not exceed 15.3 level CI designation or nomenclature assigned by the Government shall be entered.4.5.1. “U”. D. Enter either a “P” for (See 5.8.3) 143 b.4. TvRe. The system or topBlock 8c.5. or “F” for formal.5. preliminary. Enter model or type Block 8a. c.8.4.1.5 Block 8e. Other systems may be used provided the ECP number is unique for any CAGE Code identified activity.2.3. CAGE code.8. ECP numbers shall run consecutively commencing with number 1. numbers may be used unless otherwise stated in the contract: a.7 a priority to the Government and enter an “E”. D. or “R” When (Emergency.MIL-STD-973 APPENDIX D Block 7. D.5.ECP desiqnaticn.

the is provided. and the affected contract line item number(s) . to indicate whether there is an effect on other systems or CIS which will require the submittal of related Class I ECPS. their identity by the CAGE code of the design activity. document number. supply details in Blocks 28 and 30.) Place an “X” in the D.MIL-STD-973 APPENDIX D If an ECP is being revised. task number under which the ECP will be funded and implemented shall be provided in this block. (CSCI name) Block Update. box(es) according to the baseline(s) affected. R.1.12 information for all drawings affected by the ECP. Enter a brief title D. D. enter the proper identification of the revision. D.14 Enter the number(s) of all currently active contract(s). are affected.8.5. The CAGE code to be entered is that of the design activity whose number is If more than three drawings assigned to the listed drawing(s).6 Block 8f.e. For example: F-18 Aircraft Air Turbine Start Connector Backshell Replacement.5. Do not include the purpose or description which are to be entered in Block 16. at the originating CAGEcoded activity that are affected by the engineering change. Drawinus affected.1O affected. D. Enter the indicated Block 12. If more contracts are affected than can be fit in the block. Other svstems/configuration items D.la) submitted shall be the date of the revised ECP.5. make reference to the enclosure and paragraph where this information In the case of a Government-prepared change. for subsequent revisions. RI for the (The date first revision.1. .9 Block 9. Enter an “X” in the “yes” or “no” box. Contract number(s) and line item(s) . Block 13.13 to identify the component or system affected by the ECP. D.1. Baseline affected. i. Title of chanue. If Block 11.1.5.1.5. enter the information required in the first line for the top-level drawing affected by the ECP and make direct reference on the second line to the enclosure and paragraph containing the list of all the affected drawings. as applicable.5. shall be entered.11 specifications cited in the contract are affected by the ECP. (See B. Block 14. revision letter. Specifications affected. Block 10.. and the SCN (or NOR) number of the SCN (or NOR) being submitted with the ECP. - 144 - .5.5. AN/AYK-14(v) CP-1502/CP-1503 Reconfiguration to CP-1799. Revision.1.1.

substantiating the 145 .5. etc. --- b. so indicate. For hardware.1. malfunction.5. The nature of the defect. In Production. or authorized name and number of the CI(S) affected by the ECP. it shall be so stated. CSCI name and number if applicable.20 Block 20. D. it will provide the authorization desired. Procurina contracting officer.1.5. Need for chanqe. Additionally. use continuation pages for details but provide an overview in this block . if it is repeated in the contractual document authorizing the change. D. marked if deliveries have not been completed on the contract(s) . Configuration item nomenclature. Enter the procuring contracting officer’s name. The “no’!box shall be marked if the deliveries have been completed.5.16 Block 16. If the proposed change is an interim solution. Enter the Government assigned name and type designation. If not applicable. applicable NSNS shall be entered.1.1. The description of the proposed change shall include the purpose and shall be given in sufficient detail to adequately describe what is to be accomplished.1. enter the name and identifier of each lower level CI and computer software unit affected. All lower level items affected. A description as to which part of the item or system is being changed shall be provided. If additional space is needed. D. Enter an explanation of the need for the change to include specifically identifying the benefit of the change to the Government.5. The number(s) of the part(s) shall also be entered. replacing the existing ECP in its entirety. It shall be phrased in definitive language such that.15 Blo ck 15.MIL-STD-973 APPENDIX D D.1. For CSCI’S.5. D. complete descriptive name of the part(s) shall be given here without resorting to such terms as “Numerous bits and pieces”. An attached list may be used when necessary. Descri~tion of chanue. This block is not always applicable to software. failure.17 The “yes” box shall be B1 ock 17.19 Block 19. code and telephone number applicable to the CI shown in Block 16. D. incident. or provides change pages to the existing ECP. Information should be included as to whether the revision is a resubmittal. an appropriate. Block 18.18 a. Supplemental drawings and sketches shall be provided to the extent necessary to clearly portray the proposed change.

the contractor shall consider. cite that authority herein.1. that fact will be included with sufficient detail to identify the issues.5. in addition to the time factors. D. enter the contractor’s estimated production effectivity point for the production items including serial number. defensive or offensive capabilities. Serial numbers may be used in lieu of version numbers if approved by the Government. etc. the effectivity of the end item CI and vehicle (aircraft. the availability of all support elements affected and the most economical point of introduction consistent with all the salient factors involved. Where applicable. performance. Production effectivity bv serial For hardware. or other item identification (e. the proposed change.) into which the capability represented by the new version of the software is proposed to be If the impact of incorporated. shall also be provided.. Block 21 of the ECP submittal shall include a recommendation to this effect. Correspondence establishing requirements for the change and any testing accomplished prior to the submission shall be identified If the ECP is needed to correct maintenance/ and summarized. Additional pages may be added as required. Block 21. The earliest production incorporation is not necessarily the singular or most important factor in the establishment of a proposed change effectivity point. tank. b. identify the CSCI version number into which the change will be incorporated.g.21 number. a. The effectivity point will be based on concurrent availability of all logistics support elements and materials affected by the change to the item.MIL-STD-973 APPENDIX D Full need for the change shall be described in detail. speed. etc. 146 . For CSCI’S. utilization shall be made of available failure data. shall be described in quantitative terms. If a new capability is to be providedf improvements in range. endurance. the ECP merits the release of a new software version. striking power. block or lot number) as approved by the In determining the effectivity point for Government. Tf the ECP is being submitted as a response to a request for ECP or Government direction. logistics problems. ship.

reference an enclosure in Block 23b on which is specified the dates of availability of tools.23.5. this delivery date will be repeated on the milestone chart together with the schedule for other interrelated actions. jigs.5. If the CSCI 147 . Retrofit. or for related ECPS.4 Block 23d.5. If retrofit is to be accomplished in ships (or in vehicles for which the serial numbers are not shown in Block 23) .23. Shi~/ vehicle class affected. Not applicable when ECP Short Form procedure is specified by contract.1. D. State the location(s) at which retrofit is to be accomplished.2 Block 23b. Recommended item effectivity. Locations or shi~/vehicle numbers affected. Estimated kit deliverv schedule. State the estimated delivery schedule of items incorporating the change.1.3 Block 23c. D. When special tooling for retrofit is required for Government use. so state.1. either in terms of days after contractual approval.1. Not applicable when ECP Short Form procedure is specified by contract.23 Block 23. this block shall apply if the change is part of a hardware or equipment change and implementation of the CSCI change is per a hardware retrofit schedule. enter the identification of such classes.1 Block 23a. D. For a complex ECP.1. D. When the contractor recommends that the engineering change be accomplished in accepted items by retrofit (see Block 43) .5. D.23.5 For CSCI’S.1.5.23.5. or by specific dates contingent upon contractual approval by a specified date. State estimated kit delivery schedule by quantity and date.MIL-STD-973 APPENDIX D D. Such statement regarding items currently in production shall be based upon the estimated approval date of the ECP. enter the ship hull numbers (or vehicle numbers) . or in a referenced enclosure.22 Block 22. the quantities and serial (or lot) numbers of accepted items in which the change will be incorporated by retrofit shall be entered in Block 23a.5. If there will be no effect on the delivery schedule. or the fielded version of the software is to be replaced.23.1. When the delivered CI is installed in one or more ship/vehicle classes. D. and test equipment required in conjunction with the kits to accomplish the change. Effect on production delivery schedule.

[Note: The Contract Administration for use by the Government. Effects on Functional/Allocated Confimration DD Form 1692/1 (See Figure 9b) is to be Identification. approval or disapproval of Class I ECPS by marking Block 27a and completing Block 27d.5. AP~roval/disaR ~roval.25 Block 25. If a separate product function specification is used.5. if there are related ECpS. Enter the total estimated costs/savings impact of the basic and all related ECPS. This indicates the ECP has the official sanction of the submitting activity.MIL-STD-973 APPENDIX D change is part of a larger hardware or equipment change and incorporation of the CSCI change is per a hardware retrofit schedule. For Class I ECPS. Not applicable when ECP Short Form procedures are specified by contract.5.26 Block 26. It will concur or non-concur in the classification of Class II engineering changes by marking Block 27c accordingly and by completing Block 27d. that information will be included here either directly or by reference. Enter the total estimated costs/savings impact of the ECP on the contract for the subject CI. This block is D. D. This Figure normally will be the same as that in column 5. the designated approval activity will mark Block 27b accordingly and will complete Block 27d.2 DD Form 1692/1. 27e and 27f. column 6 the bottom line of Page 4 or. of Page 5. (Savings shall be shown in parentheses. “Enqineerincl Chanqe Proposal.27 Block 27. line e. of DD Form 1692/3 (Page 4).1. When the Government requires approval of Class 11 engineering changes prior to contractor implementation. Submitting activitv authorized An authorized official of the activity entered in siqnature. in column 4. completed only if the proposed change affects the system specification or the item development specification(s) . D. including other costs/savings to the This Figure normally will be the same as that in Government. 1. Block 1 shall sign this block and provide title in Block 26b. line e. the Government contracting officer will mark Block 27g accordingly and will complete Block 27h. ) D. Estimated costs/savinus under contract. It will recommend Office will review all engineering changes. effects on such specification of changes proposed after the PBL has been 148 . Estimated net total costs/savinqs. 1.24 Block 24.5. 1. Paqe 2“.5. D. 27i and 27j.

2.-.1 ECP number. trainincl. For hardware.5.5. including any changes or effects on the In particular. — MIL-STD-973 APPENDIX D established shall be described either on LID Form 1692/2 (Page 3) or on enclosures referenced thereon. For CSCIS. changes in performance allocations and in the functional/physical interfaces defined in the system specification.2. Effects on employment.5.6 Block 32. Identify the other contractors or Government activities which will be affected by this engineering change.2. Identify and explain any anticipated effects of the proposed change on acceptable computer operating time and cycle-time utilization. Other systems affected. or software. Configuration items affected. be an entry detailing any effect on interoperability.2. the system designation also shall be given. -- D. logistics. when Block 7 of DD Form 1692 (Page 1) is checked “yes”.5 Block 31. Enter the D. a.2. Enter the same ECP number as in Block 8d of DD Form 1692 (Page 1). maintenance and operator training names and numbers of all CIS. D. Other contractors/activities affected. or to data base management procedures. and/or personnel and training requirements which have been specified in the approved system and/or CI specifications. 149 (2) . equipment. Effects on ~erformance allocations and Describe in this block the interfaces in svstem specification. deployment.5.3 Block 29. intecrrated louistic support. Identify any required changes to the data base parameters or values.5. the following information shall be entered as applicable to the degree of design development of the CSCI at the time of ECP submission: (1) b. D.5.2 Block 28. and support equipment affected. Insert data D. D. operational effectiveness.2. If the ECP number is assigned on the basis of the system. there shall operability of the system. describe the effects of the proposed change on employment.4 Block 30.

when the proposed engineering change requires a major revision of the development program (e. significant requirements for computer software redesign. new prototypes.2. (See MIL-STD-490) D. Block 34..5. Identify and explain any other relevant impact of the proposed change on utilization of the system. Date by which contractual authority is needed.5.MILI-STD-973 APPENDIX D (3) (4) Provide an estimate of the net effect on computer software storage. as appropriate. changes to the software engineering/test environments. In addition. additional design review activity.5. D. special installation.g.9 Block 35. the contractor shall identify the scheduled sequence of computer software design and test activities which will be required. adaptation. the nature of the new development program shall be described in detail.7 Block 33. For hardware. Developmental requirement s and status. tests to be reaccomplished).1O Block 36.2. D. A b. summary of the various solutions ‘considered shall be included with an analysis showing the reasons for adopting the solution proposed by the ECP. The impact of the software change on the hardware design and input/ output cabling shall also be detailed. and. The effect of the proposed change on performance shall be described in quantitative terms as it relates to the parameters contained in the CI development specifications. D.2.5. and live environment testing.2. ECPS initiated after preliminary design which affect the FBL and/or the ABL shall identify. For CSCIS. 150 . Trade-offs and alternative solutions. Enter the date contractual authority will be required in order to maintain the established schedule. recoding. repetition of testing.8 a. the specific impact of these factors on approved schedules shall be identified. including the status of programs already begun. checkout. Effects on confirzuration item s~ecifications.

when not completely covered on Page 1. Block 37. if any specific logistic interoperability factors are affected. Effects on product configuration documentation. Address nomenclature change when applicable.5. . weight. effects on drawings.3. to document CSCI impacts in these areas. 151 . the contractor shall provide information detailing the possible impact on the operational configuration on an attached page. Form 1692/2 (See Figure 9c) may have been required on DD Form 1692 and 1692/1 (Pages 1 and 2) or does not apply to computer software.5. etc. Effect on Product configuration D. 41. “Enqineerinq Chanqe Proposal.3. Paqe 3“. Such enclosure may consist of a list of enclosed NORS if submittal of an NOR for each drawing affected is a requirement of Indicate any technical data submittal which is not the contract. NORS or other enclosure(s) which cover such proposed text changes in detail. the software engineering and test environments are usually not affected by changes in the product configuration of a CSCI. provided for in the CDRL by means of a referenced enclosure. In Block 42. If the number is assigned by system. The effects on the approved CI product specifications shall be described by reference to the SCNS. a cross-reference to such information will be adequate. shall be described in general terms by means of a referenced enclosure. Block 38. The effects of the engineering change on logistic support of the item shall be indicated by checking the appropriate boxes. 46. include the system designation.3 DD Form 1692/2. APPENDIX D D. Enter the same ECP number as in Block 8d of DD Form 1692 (Page 1). Effect on integrated loqistics sup port D.1 ECP number. For hardware. For CSCIS. The effects on performance. moment.2 documentation or contract. a. These effects shall be explained in detail on an enclosure indexed by appropriate identification adjacent to The information required shall the subject under discussion. the information about the status contractor shall provide There of the software redesign and retesting effort. D. 45. shall be indexed by The proper identification adjacent to the factor affected.3 elements.3. When this information has already been supplied.MIL-STD-973 . shall also be a review of the intent of Blocks 40.5. b. 47 and 49. which are covered in the enclosure(s) .5. Certain information required on DD loqistics and operations.

Spares and repair parts that are changed. Revised or new technical manuals. knowledge and numbers required to support the CI as modified by the change. and for any related ECp not furnished with the basic ECP. obsoleted or additional support equipment (SE). For items of SE and trainers which require change. New operator and maintenance training requirements in terms of training equipment. obsoleted or added. e. New. furnish a brief description of the proposed change(s) in SE and trainers. c. NOTE : Failure to include detailed supply data will delay ECP processing. trainers and training software for operator and maintenance courses. b. d. Revised or new facilities requirements and site activation plan. Extension/revision of the interim support plan. f. modified. including detailed supply data for interim support spares. The following shall be covered as applicable: a. System and/or CI logistics support analysis (LSA) tasks (MIL-STD-1388-1) to be accomplished and LSA data (MIL-STD-1388-2) requiring update wherever it exists in the contract. Effect on maintenance concept and plans for the levels of maintenance and procedures. revised. Qualitative and quantitative personnel requirements data which identify additions or deletions to operator or maintenance manpower in terms of personnel skill levels. j“ . test procedures and software. Effects on schedule and content of the ILS plan. furnish a cross reference to the related ECPS.MIL-STD-973 APPENDIX D indicate the method to be used to determine the integrated logistic support plans and items which will be required for the support of the new configuration as well as retrofitting previously delivered items to the same configuration. 9“ h. This 152 - i.

b. handling. etc. items. required to set up the course at either the contractor or Government facility. See paragraph i above for instructions. m. Effect on o~erational em~lovment. Removal or repositioning of Physical constraints. Any effect on contract maintenance that increases the scope or dollar limitation established in the contract. increase or decrease in overall dimensions. Effects on packaging. The Block 39. and training software) requiring a change to existing code and/or. dimensions. Quantitative values shall be used whenever practicable but are required when reliability and service life Survivability includes nuclear survivability. structural rework. equipment. c. Software (other than operational. maintenance.3. D. GFE or Government Furnished Data (GFD) changed. Other considerations. e. and transportability-resulting from changes in materials. Rework required on other equipment not included previously which will effect the existing operational configuration. inherent environmental or operating conditions. 1.5. etc. fragility.3. .5.MIL-STD-973 APPENDIX D information should include identification of specific courses.4 effects of the engineering change of CI utilization shall be indicated by checking the appropriate factors and providing details by enclosures. (output. modified or obsoleted. 153 d. k. input. Interfaces having an effect on adjacent or related items. n. technical manuals.5 Block 40. size. See paragraph j above for instructions. personnel. storage. resources or addition of new software.). the proposed engineering change on the following shall be identified on an enclosure indexed by appropriate identification adjacent to the factor affected: a. The effects of D. mating connections. are impacted.

When applicable. Where retrofit is not recommended.6 Block 41. D. prototypes.3.—. Additional or modified system test procedures required. When the contractor’s analysis addresses new concepts or new technology.5. any implications thereto.3. including projections of operation and support costs/savings for the item(s) affected over the contractually defined life and projections of the costs/savings to be realized in planned future production and spares buys of the item(s) affected. Develo~mental status. an explanation of this determination shall be provided. 154 - .8 Block 43.7 Block 42.3. Reference shall be made to any enclosure required to state recommended retrofit effectivity (See Block 23a) . The contractor shall provide an analysis of the alternatives. fit checks. installations. including the use of revised operation or maintenance procedures.5. revised part replacement schedules. supporting data (to include LSA if contractually required) should be presented with the proposal to authenticate the trade-off analysis. . the contractor shall make recommendations as to the additional tests. i.5. A summary of the various alternative solutions considered. which will be required to substantiate the proposed engineering change. 9. revised inspection or servicing requirements. identify the advantages and disadvantages inherent in each feasible alternative approach. etc. Recommendations for retrofit. . MIL-STD-973 APPENDIX D f. Alternate solutions. These recommendations shall include the test objective and test vehicle(s) to be used. Any new or additional changes having an effect on existing warranties or guarantees. trials. When applicable. D. shall be included. The contractor shall indicate the development status of the major items of GFE which will be used in conjunction with the change and the availability of the equipment in terms of the estimated production incorporation point. the contractor shall make recommendations for retrofit of the engineering change into accepted items with substantiating data. etc. D. Changes or updates to the parts control program. h. and show the reasons for adopting the alternative solution proposed by the ECP. Effects on life cycle cost projections for the configuration item or program. and a brief description of the action required.

5.5.2. ECP disapproval may be stated in this block or in a referenced enclosure.MIL-STD-973 APPENDIX D D.11 Block 46.14 approved ECPS on item.3.1) allowing additional time for review.3. DD Form 1692/3 (See Figure 9d) is intended as the summary of the estimated net total cost/savings impact of a single ECP.5.1O Block 45. and other incidental handling and processing requirements. . total time period from removal of the equipment from operational service until equipment will be returned to operational status after being retrofitted. Pac7e 4“. Estimate work-hours to install retrofit kits when weapon system is undergoing overhaul.9 Block 44. “Enaineerinq Chanae Pro~osal. etc. If “yes” attach proposed yeuuired? program for contractor participation.1.3.5.3.3 . each cost factor associated with the ECP shall be considered as to whether such cost or portion thereof under the subject 155 . D. Estimate the D.12 Check applicable box. Complete Blocks 44a through 44d to show the amount of work which must be programmed for various activities to install retrofit kits. mailing.3. The contractor shall summarize the cumulative effect upon performance. of this ECP and previously approved ECPS when design Consequences of limitations are being approached or exceeded. Work-hours to conduct system tests Enter the work-hours required to test the system after retrofit. Date contractual authority needed. Where previously approved engineering changes must be incorporated in a specific order in relation to the proposed change. Work-hours Der unit to install retrofit kits.4 DD Form 1692/3.15 contractor shall provide the date by which contractual authority to proceed is needed to maintain the estimated effectiveness specified in the ECP and to provide concurrent ILS and logistics The contractor should consider the support item deliveries. electrical load. D. Estimated net total cost irn~act. Block 50.3. Block 47. or the item following installation of the retrofit kit. Out of service time.3. weight. Block 49.5.4. D.5. This chanqe must be accom~lished. The D.5. such order should be specified. Is contractor field service enqineerinq D. In Blocks 51a through d.13 Block 48. targets for decision (see 5.5. Effect of this ECP and Deviously D.

2 Block 51b. show all redesign and data revision costs when the item is not in production.5.I Block 51a. using entries in the $’unit” and “quantity” columns when appropriate.4. Production costs/savinus. a separate DD Form 1692/3 (Page 4) shall be filled out for the quantities to be delivered to each service. Enter 156 . If an ECP affects items being delivered to more than one service. Costs of modifications required to existing GFE and subsequent testing also shall be shown. include system designation. When Government personnel accomplish. Show design costs of the retrofit kit and data revision costs strictly related to retrofit when the CI is in production.4. Related - D. MIL-STD-973 APPENDIX D contract is recurring or nonrecurring. D.2 ECPS . Enter the projected life cycle costs/savings applicable to the planned production and spares buys of the item that are not yet on contract on the CONFIGURATION ITEM/CSCI line in column 6. The cost analysis applicable to each service shall be appropriately labeled at the top of the form. Show redesign costs for the CI in the block titled “engineering. etc. engineering data revisions” when the item is in production. If the number is assigned by system. as applicable. Firm cost proposals shall be submitted on standard form (SF) 1411.5.2. This estimate of cost impact will be used for planning purposes and for a cost reduction or VE ECP analysis as to the net saving that would result.1 ECP number.5. Enter the estimate of costs/savings applicable to production of the CI resulting from incorporation of the change. redesign. shall be divided between the using services on the basis of the percent of items furnished to each.4. Other costs/savings to the Government resulting from approval of this ECP shall be entered in column 6 to the extent these costs can be determined by the contractor. Enter the estimate of costs applicable to retrofit of the item. Enter the subtotal of production costs (both nonrecurring and recurring) in the fifth column. Unless otherwise prescribed. the installation and/or testing activities.2. Enter the same ECP number as in Block 8d of DD Form 1692 (Page 1). Retrofit costs.5. Estimated CostslSavinas Summarv. D. Enter cost savings in columns 1 and 4. including installation and testing costs.4. together with the appropriate cost breakdown. costs of special tooling. or are involved in.—. D. Savings shall be enclosed with parentheses. Block 51. the estimated costs shall be entered in column 6 on the affected lines. scrap.

2. other than GFE. Block 24. enter the total of such costs in Block 51d. and 6 on this line. retrofit or ILS headings or under Block 51g.4. Enter the subtotal of ILS costs/savings in column 5.2. On the line titled “interim support. training On the line titled equipment and personnel training program.5. associated with ILS elements for which appropriate titles do not appear in Block 51c may be entered in place of a factor not used unless such costs are covered on DD Form 1692/4 (Page 5) or in related ECPS. or if costs of certain coordination changes are not 157 .MIL-STD-973 APPENDIX D If some or the subtotal of retrofit costs in the fifth column. show that deferred portion of the cost applicable to each line of Block 51b in column 6. D. column 5. Other costs/savinas. Enter the D.3 savinqs. if Page 5 is not required. Enter the estimated cost of the various elements of ILS applicable to the item covered by the ECP. If there are Block 51d. Intemated loqistic SUD Port costs/ D. column 6. etc. However. “coordination changes by Government. 4. Subtotal costs/savinqs. The subtotal subtotals of columns 1.” estimated costs shall be entered based upon the period of time between initial installation/operation of the item (aircraft. retrofit or ILS headings.2. and changes to GFE being covered under 51b. This subtotal under the contract then shall be entered on the line so titled in column 6 and on DD Form 1692 (Page 1) .4. Block 51c. all of the retrofit activities and costs will have to be deferred and placed on contract at a future date. “maintenance manpower” shall be entered the estimated costs/ savings for the contracted maintenance support for the remainder Other ILS costs/savings of existing maintenance contracts. the estimated costs thereof shall not be entered in Block 51f. tank. If such coordination changes are covered by related ECPS and summarized on DD ‘Form 1692/4 (Page 5) . 5. Coordination of chanqes with other This term applies to interface changes to items contractors.) as modified by the ECP and Government Such “interim support” costs attainment of support capability. special support equipment.5 Block 51e.4 other costs under the contract which do not fall under the production.5. D. enter the total of such costs in Block 51d.6 Block 51f. in column 5 shall be the sum of columns 1 and 4.4. Enter the operation and support portion of the life cycle cost/savings on the subtotal line in column 6. shall include costs estimates of contractor recommended/provided spares and repair parts.2.4. If there are other costs to the Government which do not fall under the production.5.5.

the contractor shall summarize the costs of related ECPS of the several primes involved in an interface or interrelated ECP on DD Form 1692/4 (Page 5) and shall attach this page to the ECP package. etc.7 Block Slq. System inteqratinq contractor. Block 25.MIL-STD-973 APPENDIX D tabulated on Page 5.4. related ECPS. A few revised requirements for ILS. (2) 158 . the prime contractor submitting the basic ECP shall include the costs of related ECPS being submitted by other affected contractors to the extent such information is available. these additional costs for revision of ILS plans.5. The prime contractor shall summarize the costs/savings of all related ECPS for which the contractor is responsible. Estimated net total costs/savinqs. DD Form 1692/4 (See Figure 9e). etc. Enter in this block an estimate of the cost to the Government of interface changes which must be accomplished in delivered items (aircraft. when available.Estimated costs/savinqs summary. an estimate of such costs shall be entered in Block 51f. Coordination chanqes bv Government.8 Block 51h.2. facilities. D. a.5 DD Form 1692/4. “Enuineerinq Chanqe Pro~osalu Paqe 5’1.) to the extent such costs are not covered in Block 51b or on DD Form 1692/4 (Page 5) . such as ILS plans and maintenance concepts do not appear as headings on DD Form 1692/3 (Page 4). D.4. Responsibility (1) for preparation: — Prime contractor. When a system integrating contractor (or coordinating contractor) has contractual responsibility for ECP coordination. is intended as the summary of the estimated net total cost impact of both the package of related ECPS and other associated new requirements which are needed to support the modified items. on DD Form 1692/4 (Page 5).5.5. Enter the sum of all cost savings on column 6 and on DD Form 1692 (Page 1). and Page 5 may be omitted.2. ships. should be shown on Page 4 under the ILS heading. If there is no system integrating contractor. When only a single ECP is involved. D.

column (5) of DD Form 1692/3 (Page 4) of that ECP. aircraft.5. include system designation. column (3). Retrofit costs. line e. etc. D. of the grouping on the cost summary is to arrive at a total ILS cost. If the practice 159 .) Block 52b. subsystems thereof. Thus costs of ECPS for trainers.MIL-STD-973 APPENDIX D b. If more related ECPS will have to be summarized than there is room available in the blocks on the form.5. the summarization of each cost area shall be accomplished on a separate enclosure and the total for that cost area entered on the subtotal line for that area on the DD Form 1692/4.” and DD Form 1692/4 (Page 5). etc. grouped by the cost areas.5. Enter the production subtotals from columns (5) and (6) of Block 51a of each ECP applicable to weapons.” ‘tILS.5. a separate page(s) shall be provided with the ECP detailing the summary of the individual CSCI costs/savings for each of the related ECPS. The costs of certain related Summarization techniques. The sum of the four subtotals attributed on Page 5. trainers. This form shall not apply in the case where all related ECPS being summarized refer to software changes only.” “retrofit. ECPS are entirely ILS costs. and providing the total costs/savings for all of the related software ECPS . in columns (3) (Note that total costs of ECPS on and (4) respectively. Production costs/savinas. tanks.3 charged by the Government to production funds or maintenance funds or may be split between the two. and a net total cost of all actions for the complete group of related ECPS. Enter the same ECP number as in Block 8d of DD Form 1692 (Page 1).5. and SE are entered in Block 52c.) shall be split into the four subtotals of “production. c. Retrofit costs may be D.2 ECP number in column (2). The type of funds used depends upon the phase in the items life cycle. to an individual Ecp should agree with the subtotal of costs/savings under contract. If the number is assigned by system. training equipment. aircraft. However. Enter the Block 52a. D.1 ECP number.5. Software chanqes only. other training equipment and SE shall be Other listed in total under the “ILS costs” heading. subsystems thereof. ECPS (applicable to weapons. tanks. Cost breakdowns should be arranged in such manner that costs/savings are neither included The purpose more than once on the summary nor omitted.

1 ECP number. D. ) For software-only ECPS.5. The subtotal under contract(s) shall then be entered on the line so titled in column (4). tanks.4. CAGE code.1O through 52.c.4. Enter in Block 52.1.5.2 the ILS subtotals from columns (5) and (6) of Block 51c of each ECP applicable to weapons. enter costs of ECPS for ILS items in Blocks 52. Enter in Blocks 52. See 5. Enter in Block 52d the sum of the “other costs” totals from column (5) and (6) of Block 51d of each ECP applicable to weapons aircraft.8 for information as to when DD Form 1692/5 (See Figure 9f) is required. Other costs/savinqs. 5 and 6. etc. if appropriate. subsystems thereof.18. 160 Enter the CAGE code for the . Enter the subtotals of columns (3) and (4) on this line. ILS costs/savinus.6.4. as appropriate.5.c. etc.5.6. subsystems thereof. D. the DD Form 1692/6 (Page 7). Estimated net total costs/savinqs. when appropriate. Enter costs of revision or preparation of ILS plans and LSA records for the CI or complete system in Block 52.1. If the number is assigned by system. shall be used instead to summarize the detailed software events schedule.5.c. Enter in Block 52. or split between. Enter the sum of the preceding two lines of column 4. If such practice is unknown.7.5.6 Block 52e. Enter the same ECP number as in Block 8d of DD Form 1692 (Page 1).c. retrofit costs shall be entered in.2 Block 53.5. include system designation.c.9 costs of revision of the interim support plan to the extent such costs have not already been covered under Block 51c of DD Form 1692/3 (Page 4) of the applicable ECPS.5. enter in Block 52b the ECP number and the retrofit subtotals from the columns (5) and (6) of Block 51b for each applicable ECP.c. and totalled in column (3).6 DD Form 1692/5 “Enqineerinq Chanqe Proposal [Hardware) Paqe 61~. as appropriate. D. D. Blocks 52b and 52. D. (An equivalent format may be substituted. If the ECP impacts both software and hardware.c. tanks. 4. activity originating the ECP. Enter retrofit costs in Block 52.4 Block 52c. as appropriate.5. aircraft. As stated in D.3.MIL-STD-973 APPENDIX D of the Government in this regard is known to the originator of Page 5. such costs being broken down into nonrecurring and recurring costs.c. both Pages 6 and 7 shall be used.5.5 Block 52d. D.18 the costs of all new requirements for ILS not covered by ECPS.

and documentation incorporating the basic and related ECPS. when appropriate. Enter Enter the information Block 56.7. Confic7uration item nomenclature. or authorized name and number of the CI(S) affected by the ECP. Enter the symbols (see D. D.6.4. Title of chanae. as appropriate for the activity.3 and identification number if applicable.7.1 8d of DD Form 1692 (Page 1) If the number is assigned by system. support equipment.5. D.4 from Block 10. training equipment and documentation incorporating the basic and related ECPS .7. may be substituted. Milestone chart.5.3 the information from Block 16. For hardware-only ECPS. 161 . D.6. D.) . software and hardware. Title of chanqe. shall be used instead to summarize If the ECP impacts both the detailed hardware events schedule. to show the time phasing of the various deliveries of items.5.) the DD Form 1692/5 (Page 6) .5. to show the time phasing of the various deliveries of items.7. Enter the CAGE code for the Enter the CSCI name Block 58.5.4 Block 55. See 5.5 legend on form). as appropriate for the activity. Paqe 7“. as appropriate. include system designation. D. CSCI nomenclature. Enter other symbols and notations to show the initiation or termination of significant actions. All dates are based upon months after contractual approval of the basic ECPS. 18. All dates are based upon months after contractual approval of the basic ECP. Enter other symbols and notations to show the initiation or termination of significant actions. D.5.5. both Page 6 and Page 7 shall be used.6.MIL-STD-973 APPENDIX D Block 54. Milestone chart. Block 57. Enter the information Block 60.2 activity originating the ECP.7 DD Form 1692/6 “Enuineerina Chanqe Proposal (Software) . Block 59. Enter the symbols (See D.7. CAGE Code. Enter the same ECP number as in Block ECP number.5.5 legend on form. from Block 13.8 for information as to when DD (An equivalent format Form 1692/6 (See Figure 9g) is required. D.5. training equipment.

8 ECP form continuation Daqes. The continuation pages are to be numbered consecutively such as: Page 6 of 8.MIL-STD-973 APPENDIX D D. etc. Page 7 of 8. Note: Do not use the designation.5. 162 . enclosure ( ). These pages shall address the block numbers. attachment (yy). Continuation pages should have the same heading as previous ECP pages including the ECP number. and Page 8 of 8.

ECP DESIGNATION J 9.ON 01 CUANGi GOVERNMENT APPROVAL APPROVED ACTIVITY DONOT [na Pdc>f C 0$ Ilca. ESTIMATED b TITLE NET TOTAL COSTS t SAVINGS 27. /CONFIG I -. !@ 9a.. PROCURING CONTRACTING J OFFICER L*ST) c 7ELEBHONE NO 17. d ECP NO ‘RODUCT ITEMS AFFECTEO 1 11 SPECIFICATIONS AFFECTEO CAGE Code Spccflcatlon Document No I 12. I 1 8.0f88 1 PLEASf -—00 NOT RETURN . . NtED FOR CHANGE 21. AWROVAL a r DISAPPROVAL CLASS I CA1.. . BASELINE AFFECTED t) CAGE CODE 1 . PAGE 1 OME NO 0704.P “m$ .ONCin !ryi N‘. PROO12~10N EFFECTIVITY BY SERIAL NUM9ER [22 EFFECT ON PRODUCTION DELIVERY SC14EDULE I 23. CONFIGURATION ITEM NOMENCLATURE 18. . Engineering Change 163 PrOP09al - Page 1 . ‘. AU a LOWER LEVEL ITEMS AFFCCTED b PART NO I f NOMENCLATURE c NSN 19. . . CONTRACT NO. DRAWINGS Rev I SCN I CAGE Code AFFECTED Number I Rev i Noa a b c SYSTEM DEVELOPMENT PRODUCT 13. SUSMl~lNG AUTHORIZED ACTIVITY SIGNATURE I 2S. MODEL t TYPE c SYSTEM DESIGNATION e TYPE 1 r 1 FuNCTIONAL ‘LLOCATED U 10. OTHER SYS. DO Form 1692. IN PRODUCTION NAME CODE ffvrt.MIL-STl)-g7j APPENDIX D ENGINEERING CHANGE PROPOSAL (ECP). DESCRIPTION OF CHANGE 20. AND LINE ITEM 15. DATE S GNED fYYMM~O) - d g 1 q SIGNATURE SIGNATURE h GOVERNMENT ACTIVITY . A.. RETROFIT a RECOMMENCED ITEM EFFECTIVITY b SHIP 1vEHICLE CLASS AFFECTED c ESTIMATED KIT DELIVERY SCHEOULE d LOCATIONS OR SI+IPIVEHICLE NUM9ERS AFFECTED 24. APEE 92 Figure Previous edfrron$ J. TEILE OF CHANGE 14.~$$ f DATE SIGNED (YVMM1301 . . ESTIMATEO COSTS I SAVINGS UNDER CONTRACT X.Wde Innd b 16.

OPERATIONAL EFFE~lVtNESS OR SOFTWARC . 13. lnAOE-OFfSANOALTERNATIVE SOLUTIONS )6. DATE BY WH}CH Form 169211. TRAINING. PAGE 2 I form Aoproved 0M8 NO 0704. DEVELOPMENTAL REQUIREMENTS AND STATUS IS. EFFECTS ON EMPLOYMENT. EFFECTS ON CONFIGURATION ITEM SPECIFICATIONS M. Engineering Change Proposal 164 Page 2 . CONTRACTUAL AUTHORITV IS NEEDED (Y~MMDD) 00 APR 92 PWWIOW qdlrlons qrc ob$ol??e Figure 9b.— MIL-STD-973 APPENDIX D ENGINEERING CHANGE PROPOSAL (ECP). CONFIGURATION lTtMS AFFECTED 31. INTEGRATE LOGISTICS SUPPORT. tFFE~S ON PERFORMANCE ALLOCATIONS ANO INTERFACES IN SYSTEM SPEC)FKATION 32.0188 - m EFFECTS ON FUNCTIONAL/ ALLOCATED CONFIGURATEON DOCUMENTATION 29 OTHER CONTRACTORS/ ACTIVITIE$ AFFfCTED 28 OTHER SYSTEMS AFFECTED 30.

ttOURS TO CONOI ICT SYSTEM TESTS AFTER RETROFIT d OTHER ORGANIZATION C OEPOT 1 M. h t I 1 I I sYSTEM TEST PROCEDURES WARRANTY I GUARANTEE PARTS CONTROL LIFE CYCLE COSTS I 1 m CONTRACT n MAINTENANCE PACKAGING. RECOMMENDATIONS FOR RETROFIT U. TECHNICAL DATA d f I? SERVICE LIFE 38. k I d TRAINING TRAINING EQuIPMENT @ REWORK OF OTHER EQuIPMENT f 9 STORAGE. WORK-HOURS a PER UNIT TO INSTALL RETROFIT KITS b INTERMEDIATE I 1 45. Engineering Change PropoSal . pLANS AND CRITICAL SINGLE POINT FAILURE ITEMS INTEROPERABILITV I LOGISTICS SUPPORT ANA LvSES INTERIM SUPPORT PROGRAMS SpARES AND REPAIR FACILITIES SUPPORT EQUIPMENT OPERATOR TRAINING OPERATOR TRAIN!NG MAINTENANCE MAINTENANCE EQuIPMENT PARTS I 40. EFFECT ON OPERATIONAL EMPLOYMENT q ENCL PAR 37 EFFE13 ON PRODUCT CONFIGURATION 00 CUMENTAT!ON OR CONTRACT ~ b c d e PERFORMANCE WEIGHT BALANCE STABILITY fAwcr#fr) WEIGHT-MOMENT NOM ENCUTURE (Oth@r qqu~pm?nt) SAFETY Survivability RELIABILITY MAINTAINABILITY OPERATING PROCEDURES INTERFERENCE [ b c CDRL. OTHER CONSIDERATIONS INTERFACE OTHER AF~ECTED EQUiPMENT/GFE~GFp PHYSICAL CONSTRAINTS COMPUTER pROGRAMS RESOURCES AND I TECH MANUAL$/PROGRAMMING TAPES q b c I .MIL-STD-973 APPENDIX D 1 EFFECTS ON PRODU~ (x) FACTOR CONFIGURATEON DOCUMENTATION. EFFECT OF THIS ECP ANO PREVIOUSLY ITEM APPROVEO ECPS ON 47. OUT OF SERVICE TIME SO. IS CONTRACTOR FIELO SERVICE ENGINEERING REQUlaEO? 48. OATE CONTRACTUAL ~ PRODUCTION AUTHORITY NEEDCD FOR (Y’fMMDD) DD form 1692/2. THIS CHANGE MUST SE ACCOMPLISHED AFTER THE FOLLOWING 19. ALTERNATE SOLUTIONS S3. LOGISTICS AND OPERATIONS ENCL PAR (x) FACTOR 39.Page 3 165 . WORK.“ O&Ok t~ 9c. HANDLING. EFFECT ON IMEGRATEO LOGISTICS SUPPORT (ILS) ELEMENTS a b C d II + 9 h 9 h I ELEmROMAGNETIC ACTIVATION SCHEDULE ILS PLANS MAINTENANCE PROCEDURES CONCEPT. TRANSPORTABILITY I S1. APR 92 E~~U~e Prc VIOUJ ?dmons 4rQ .

and muntamm~ th+aeqa nnded .MXL-STD-973 APPENDIX D Form Approved ENGINEERING CHANGE PROPOSAL (ECP).13. “t.O.ndua.gm?i. GF? o? G$[ GfP COWL (lO)MOOIrlCA1l~ (1 l)o”A. 0704.on ..cAT.“lwma.w . h.n*l {oIl.Rfo..T . . r PIR$ONNIL PfmtoNwi tN5T&LL4T10N INsTALmTIoN.Oolllw bon \c A. APR 92 Figure PrCVIOUS cdmonl tro obsoh fe 9d.iim” of .fiq DwIIb9h9aav I mf for ?Wrwq l“..mo. Oni W!d**qons I)l! IQ!+?*u).lf..#m ~o. T[STWG AfTER COt4TUC70n GOVWWMtW KETROfIl OF GF[ . RETURN CDMPLE~M TO THE GOVERNMENT ISSUING CONTRA~lNG DffICER FOR THE CONTRA~l PROCURING ACTIVITY NUMBER LISTED IN ITEM 2 OF THE COMPLETED DO }OaM 1691.{IW.trws! on.0188 Wnqd*l.. *slmwt* R@MeuWlW8$WWWt DIrWf OIOtO 101 l.vA )11024302 analO1be O*ueOi M4. ESTIMATCD NET TOTAL COST IMPACT (Use pww!theses fw saw-) COSTS I SAVINGS UNDER CONTRACT FACTOR NonRecurring (a) q RECURRING un)t (b) Quannty (c) Tclta I (acc”mnq) (d) Total (e) Other Cottu’ Sawngs to ttw Gowrnment (f) PRODUCTION COSTS / SAVINGS {1) (2) (3 I (4) (!1 (61 17) W CONF.GUUTION 6ACfORV WSCIA1 SCM* lNGINEi@ING Rfv IWON O.tm and <0m@*t4nQ Wuc.eq-**taMBv PW-Wti RtiufllO- *~0W(07M4!91) ~nbmqwn PLEASE DO NOT RETURN YOUR COMPLETED FORM TO EITHER Of THESE ADMESSCS. .. fNGINffwiG “f\l OATA nEvI$lON 7F\1 ITIM CSCI EOUIPMtNT rOO1lNG IACTORV PROCf DUM$ OF Nfw !Tf M$ S4VIWGS 0uAL16UA180?I -TOTAL @ HOO COSTS b RETROFIT COSTS (1) EwG1uclnlNG OAT* Rrvmm {2) Molow?[ l[$lING f 1 (3) KIT moor ~[5T. OMBNo ic#KhlnQ*. S1.Page 4 .0NAL $Y$l[t. PAGE4 P“W.cm. mllrchon 01 m+ormaoon Of Wfrnu WnhIn910n hoe mmmrmt rcqwamg Ww bwO*.th.m (!2) : SUBTOTAL Of nflWSIT SAVtISG\ 1 INTEGRATED SAVINGS (1] (2) (3 I (4) (9 (6) WaM[\ Nlw / MMM Waaff LOGISTICS SUPPORT COSTSI I PARTS Awo Rf-ta REWORK PAmr$ OATA I w@P1 qROUI$IOMING Y \u@*onl RfThOFIT OPf NATOR FoulFMtM1 K17$ FOO WAhE\ lUINIMG TUINIWi COUnSIS COURS[$ (7) MAIN1f (S1 NV6JON ($ I NANCl of lCCH MANUALS NfW TECHMANUALS (10)lRAIMINC TRAIWM I (1 l)lNTf@lM jlj~l MANPOWfR PRWmM$J of k% oMuMfN?4110N (12) MAIN1[NANC[ (!)) cOMPuTfm (wqsuqTsst4L Com *vma* 1 ! I ~ OTHER COSTS 1SAVINGS SUSTOTAL COSTS/ SAVINGS It) 6WTOTALUNOS@ CONtRA~ COORDINATION OF CHANGES WITH OTHER CONTRACTORS I ! I COORDINATION CHANGES EY GOVERNMENT I DO ESTIMATED NET TOTAL COSTS (SAVINGS Form 1692.molfd *ma . ng . ?~. DC )0$01 KM MII.li (5) ~mt? of Mwo ?no (6) Wfcmc (7) (1) (q) . ng lh* OwdCn teow17m?nt tO q vWq* I h0”!3 W.fO~nWt.ev8*w.fq thi.qttlr!.. @“r<@! g.r!”g k.0R Of O@WO!.Wgqwt. 0.sprn 01 th. \. EngineeringChange 166 Proposal . .P ottw.< _.W (4I nfTnoflT 11?$!o@ 0P[R4!.% c4qm.~ nfTnob.

vthet..P Vva$h... onI o~.dua fOrth.-eu .msljr c INTEGRATED LOGISTICS SUPPORT COSTS t SAVINGS REVISED REQUIREMENTS [II I?!h4 I[lROFIT W not CO”rm$ “-r mm tab wtik. vA 221014301 a. Coof TRNR:T@NG I$Panf MANUALS MAINTtNANCf MANUALS TRNR $PAa[j ~COUIPMENI R[PAW PASTS (/or (f J)) (1s) wwwr fOUIPMINT (fo. fefww O1+If R TWiINING $Lwpow Ua4Wf UNS KS q MAINTFNANC[ !NTf RIM f oultMf*l qeu14mWW EOUIPMEN1 (r#*f raw CWf M. w . S2.vhuff m#sst#. OOr~sl Iow*n O n~nt toocowt m?. . GOVERNMENT ISSUING CONTRACTING 0.! of 09t*.f 10s1 I-.t lh* abw .. TO PROCURING ACTIVITY NUMBCR LISTED IN ITEM 2 OF THE COMPLETED DD FORM 1692.on *U ~Omm**!) IW8. SY$7f M 00 CJMf NT\ SUPPORT qLAN CAG1 NOt4 #f Curbing COSM NEW REQuIREMENTS (10) PROU.— f9) {9) COFACf PT.k vekt? m. -.v* 07#-0188 .NG (ll)OVfn fill (1]) (Iq 00 CUM fN1a710N 0iv1CE5 $ RfPAIR lRNG .0 . ~n. 9AVING$ b RETROFIT COSTS @@lc?ok to qIm#fr fm or Jn Sh!ymm) (1)W-TOTAL 8R7UOFIT osl$ C mk #Kk .$.w0f~RM.n wtwp-tcm) {t) SUOT07AL PUODUCflDN COST9 COIIY Ouo $a.4AlN.MIL-STD-973 APPENDIX D 3 ENGINEERING CHANGE PROPOSAL (ECP). croqMano9*mentb n6B.9 flvln rxh Cc? -VW!.of m~ofmm. ...(..<1.+lellM bl+$. (Wr SUCTOTAL (km of c(f) KS Cosr$ tfUWW# cAGf Coot d OTHER COSTS/ SAVINGS [?OWJ f= PSV 4 mm 4 d or mkwd CC? f) I\ I TOIA1 oTnf a COSTS SAVIUGS 121 NJWOT4L1 W COLUMNS [11 9UBT01AL UNDfR COfAf’RA~ e ESTIMATED NET (4. v!..ON.91D.u WOIN.InQvJwtI ld~m*O.9dstaw.7) qnOVlMOt41NG PA*T$ (18) RfPAt* .DPJca61e to q tmraf! fl...“.“. Engineering Change Proposal .tOWI 04 HC?daumnmWwc$ OI.. WTURN .. qmc.*wmq ww coI1rrmO.qlon. mndc m {n ‘b-) (Ao@KabIc m 41rcr0ff wtmwtrm) (1) 11S sd9T01~ L lAf#xabl* m Sub$ywfm) tO WWJff 3h10 1#..RACT. q LANS. boa <omOMq me Ier w4vung Wwtbuec. O.EW !hl$ bulO*.Page 5 167 .0” 0< $.tI.OW%FA T RETURN YOUR COMPLETED FORM TO EITHER OF THtSE ADDRfSSES. dg*l p8~.me~o. qR.r.alorhr PLEASE D . fOrm*l.km tab fc? 00 (7J .9 [4] total <ost w.me.t*.gn. RELATED ECPS (Usr mrenrhcsc! ~AliE (OOt (a) N 1- NLJM@~R fOf sawmgi) tCP P4uMMR (b) co\T5 5A*ING$ UNOf R CON TRACr$ (<l o.mq --- ard mmwmw mfwm.ntO.. FOa . . DC )0$01 1)15 I??*WW c014ccl .n fro.moIot? tof .6) MANuALS (. r rm.gto. CON.mm*+O. MfR<lJ$7\ SAVINGS TO GOVCRNMCMT (d) a PRODUCTION CO$T5 /S~VlN65 (subrorw of q + 4. dl Form 1692}4.suv9hwav.d. von Dav. ESTIMATED COSTS/ SAVINGS SUMMARY. ffSJ) 00CUMf Wor(r $)) 9Av199G\ c(lS)J fCP NUMDf B NTAIION (CW(IS)) (.v-f*m*tW toa~e. Form Approved I strunmm roIefl(070~O!U) OMBNO w* IthI. ~l!m~l* 0.. .~ ffw!! CHh fCP rowwq ml (6) mm. 0~.Irm th.m~ tank.EOU1* MRV OEVIC[$ (?w (ff)J RfCJR*lNG COS15 UNIT OT v r(JIA.. Ifrm e .. PAGE 5 *tin. Olhr? . TOTAL COSTS/SAVINGS DO APR 92 PrcwIoL4f qdmloni qre otJso/*tc Figure 9e.mo.agr>hovnar.Wdr of {3) OPEM’0* kW?t Tnb+Nf total mwfor VOW<) NAtkCf ‘MINER {Net framer) ?.

Engineering Change Proposal .Page 6 168 .MIL-STD-973 APPENDIX D — — — — — — — — — — — i 5 : u c : — i : — — c TRAINER a CONFIGURATION ITEM b SUPPORT EQUIPMENT Figure 9f.

— — — — -— a CONFIGUMTION ITEM — b SUPPORT EQUIPMENT c TRAINER I Figure 9g.MIL-STD-973 APPENDIX D — — — — — — — — — — — .Page 7 169 . Engineering Change Proposal .

1 GENERAL E.1. E. or an authorized alternative.4.3) E. (See 5. For purposes of this Appendix. Figure 10. The contractor shall request a deviation when. E.l a“ This Appendix establishes uniform requirements for the preparation of the DD Form 1694. Normally.2 APP lication.4 GENEFU4L REQUIREMENTS E.4. the contractor desires authorization to deliver nonconforming items to the Government which do not comply with the applicable technical requirements. E.2 APPLICABLE DOCUME!JTS This section is not applicable to this Appendix. prior to manufacture.4) 170 . to request deviations or waivers.2 Reauest for deviation. E. The contractor shall request a waiver when.1 Definitions used in this A~~endiX.3 DEFINITIONS E. during or after manufacture. .4. it is necessary to depart temporarily from the applicable approved configuration documentation for a specific quantity of deliverable units.4. E.MIL-STD-973 APPENDIX E INSTRUCTIONS FOR THE PREPAIUTION OF REQUEST FOR DEVIATION/WAIVER UTILIZING DD FORM 1694 E. for the unit(s) affected.3. For the unit(s) affected.1. The contractor shall prepare and submit DD Form 1694. (See 5.” This Appendix is a mandatory part of the standard. The provisions of this Appendix apply whenever DD Form 1694 is utilized to request a deviation or a waiver. Local reproduction of DD Form 1694 is authorized.4. the different configuration will normally be permanent.1 Use of DD Form 1694. “Request for Deviation/Waiver. the different configuration will be permanent.3 Reauest for waiver. The information contained herein is intended for compliance. the definitions contained in Section 3 of this standard shall apply.

E. Enter an “X” in the . E.6 Block 6. For CSCIS.1 designation of the CI for which this request is being submitted. major.3 level CI designation or nomenclature assigned by the Government shall be entered. that number shall be waiver number. Svstem designation.2 activity originating the deviation/waiver.2 Block 2.7 Block 7. E. When short form procedure is specified by contract.3 or 5. completion of the DD Form 1694.5. Enter model or type Block 7a.4 Block 3. box.4. part of the deviation number or the letter “W” as part of the Once a number is assigned.7.5.5.5. The system or top Block 7c.5. Detailed instructions for Enter the submittal date.MIL-STD-973 APPENDIX E E.4. Designation for deviation/waiver. or critical in accordance with the definitions in 5.5 appropriate Block 5. Block 4.5.3.3 activity. if known. DODAAC .5. CAGE Code. Enter the CAGE Code for the E. deviations and waivers shall be separately and consecutively numbered commencing with number one. To be used by Government for entry of internal processing number if desired.5.1 Block 1. E. Enter the DODAAC of the procuring Enter the Originator name and address. Model/TY~e. enter the CSCI identification number.7. activity E.5 DETAILED REQUIREMENTS. Date.7. Block 7d. Procurinu activitv number.4. Deviation/ E.3 by entering an “X” in the appropriate box. authorized by the Government.4 waiver identification numbers shall be unique for each CAGE Code Contractors shall include the letter “D” as identified activity. the Government will make this determination. Deviation or waiver. numbers may be assigned from a separate series 171 .7. shall be designated minor. Block 7b. E. E. or Government name and address of the contractor submitting the request. The deviation or waiver E. Deviation/Waiver number. E. Unless otherwise retained for all subsequent submissions.5. As an alternative. Classification.5.5.

11 complete Enter a brief Enter the Block 11.5. descriptive title of the deviation or waiver.1 Block 14a. Check the E. If either a Government or contractor’s CD applies.9 Block 9. E. Other S. When short form procedure is specified by contract. Name of lowest ~art/assemblv affected. enter E. Enter E.5. the Government will make this determination. applicable box for the affected baseline. An appropriate descriptive name of the part(s) shall be given here without resorting to such terms as “Numerous bits and pieces”.5. the defect number(s) which correspond(s) with the characteristic(s) from which an authorized deviation or waiver is desired.12 Block 12. provide summary data in Block 20.5014.5.5. E. E.8 Block 8.vstemiconfiquration items affected. Defect classification. E. Contract number and number and line item. Procurinq contracting officer.1O Block 10. If a CD applies. the Government assigned name and type designation.14. or authorized name and number of the CI to which the deviation or waiver will apply. E.5. applicable to the CI shown in Block 15. 14.13 Block 13. enter the number assigned. the Government will make this determination. E. Defect number.15 Block 15.5.2 Block 14b. CD number.5. if applicable. and type identification shall not exceed 15. Check applicable box. If yes. If a CD Block 14c.5.5. Configuration item nomenclature. 172 . contract Enter the E. line item. When short form procedure is specified by contract.MIL-STD-973 APPENDIX E for each system that the contractor is producing.3 applies check the box which states the proper classification of the defect number(s) entered in Block 14b. The number of characters in the deviation/waiver number. Title of deviationlwaiver. E. code and telephone number procuring contracting officer’s name.14 Block 14. dash number. Configuration baseline affected. Classification of defect (CD).

5.20 Block 20. Enter the part number(s) of the part(s) named in Block 15 or type designation/nomenclature if applicable. Describe any effect on each of these factors.5. If there is no effect on logistics support or the interface. Part number or tvpe designation. Describe the nature of the proposed departure from the technical requirements of the configuration documentation. provide rationale why recurrence was not prevented by previous corrective action and/or accomplished design change. E. Description of deviation/waiver.5. enter the number(s) applicable to the lot(s) for which the deviation or waiver is being requested. Effect on integrated loqistics SUPP ort. Effect on cost/~ rice. If no change in price. The deviation or waiver shall be analyzed to determine whether it affects any of the factors listed in Block 37.19 Block 19. and corrective action to be taken in Block 24.5.5.MIL-STD-973 APPENDIX \ E E.5. E. if yes. describe such effects on an enclosure and reference the enclosure in this block.407) is accepted by the Government. In addition.5. Show whether the same deviation or waiver has been requested and approved previously by placing an “X” in the proper box.22 Block 22. Lot may also be defined by serial numbers of the affected items. enter the words. 173 . and 40 of Dtl Form 1692/2. E. Marked drawings should be included when necessary to provide a better understanding of the deviation or waiver. Enter the estimated reduction or price adjustment. When short form procedure is specified by contract the Go\’ernment will make this determination.18 Block 18. Effect on deliverv schedule. E.” reference the previous correspondence. If the deviation or waiver will have an impact on logistics support or the interface. E. or fee. 39.17 Block 17. If “yes. Effectivity. cost. interface.21 Block 21. The request for deviation or waiver shall include the specific consideration that will be provided to the Government if this “non-conforming” unit(s) (See FAR Part 46.16 Block 16. or software. Recurrinq deviationlwaiver. E. State the effects on the contract delivery schedule that will result from both approval and disapproval of the request for deviation or waiver. so state with rationale. If lot numbers have been assigned. “No effect”. the request number.

Submitting activitv authorized sianature.23 Block 23. is impossible or unreasonable to comply with the configuration documentation within the specified explain why a deviation or waiver design change. is proposed in lieu Also of a E.5. E.5. Describe action being taken to correct non-conformance to prevent a future recurrence.24 Block 24.MIL-STD-973 APPENDIX E Explain why it E.25 Block 25. An authorized official of the activity entered in Block 4 shall sign in this block and enter title. ADDroval/disa~ proval. This block will be completed by the Government activity authorized to make the decision on the request for deviation or waiver. Corrective action taken. permanent delivery schedule.5. E. Need for deviationlwaiver.5.26 Block 26. 174 .

0 w. c ... APPROVAL I DISAPPROVAL b APPROVAL DISAP*ROVID j q RECOMMENO I APPROVAL ACTIVITY I DISAPPROVAL C GOVERNMENT (Fret.MXL-STD-973 APPENDIX E REQUEST FOR DEVIATION/WAIVER (RFD/RFW) ~ FOfm Approved oM8ruo 07040188 PuBU.4 21202~30) PRuOMC:C~NG ACTIVITY qM”CISO. $O. of 5*M comm. DESCRIPTION OF DEVIATION I WAIVER !3. +* 09 . CONFIGURATION ITEM NOMENCLATURE 14.MO_. V h. ...$AOO*OLCD T vPED NAME (FIr$t. b TITLE c SIGNATURE !6.ng ma m*<nf . MKAS/C /mtf#/.rc!10704. A4ddk IIWIW OFFICER LmT) b CODE 13..l . Request for Deviation/Waiver 175 . Zip Code) 5. INTERFACE OR SOFTWARE 12. ~lddic Ir?lt$a/.w *bW.. ---APR 92 pttvlou> F. fo.mn.<l. norr wwo.n Drfr.c.. .*.5 (O1lm Ion 01 . Sttr?.. **9* 1 ho. EFFECT ON OELIVERV SCHEDULE }1 EFFECf ON INTEGRATED LOGISTICS SUPPORT..maw or 4.81.. SLECMITTING A~lVITV I TYPED NAME last) (Fret. <h*q*. PROCURING CONTRACTING a NAME (Fret.l .w . CORRECTIVE A~lON TAKEN !5. 9.t~’qh*.Un .titi 0 qnti <ome. “~O.9 f.se *ahh.o. PART NO. nq !** I me k.eotma!.stime.an *. .0~8@l *t. 7 q DESIGNATION MODE LnYPE FOR DEVIATION b ~GE / WAIVER / WAIVER CODE c SYS DES(G d DEVANAIVER NO 8 BASELINE AFFECTED + ‘}~~A Peootin m ::’:.. +0.otcm. [FFECFIVITY 19.a R*=~t 1> ’S I***.. rO 0wmm+un70+ 1>04 Aflmqtc. 0.on s. . .*( Pre Figure 10. heaao.a.. tOIm~lIOP .v othw ...ngou. *9 mt CCwct. EPHONE NO EFECT CLASSIFICATION 15.ntmmra 10m. * w*. AND LINE ITEM 12. 1694. ?. CONTRACT NO. NEEO FOR DEVIATION/ WAIVER !4. ng w~fwo. .P . p. RATION ITEMS AFFECT[D . ADDRESS (Str@@.9 Irw am . Lasf) 3 DOOAAC b A4kjdle lmtM/. RECURRING DEVIATION I WAIVER 17.mp. CIry. OTHER SV5TEMfCONFlGU.qa. .J. SIGNATURE k Ld DATE SIGNELI ( rYMMDD) --IJD Form . w. (x onrl 6 (x one) MAJOR MlNon CRll<ca. OR TYPE DESIGNATION 18. D. \mn a~t~ $owrm gbtrw. J .na D”Oq@TP*oO*O. *w. m*t.s collw.ng. MIddlc In/t/a/. TITLE OF DEvIATION 11.r$.“dtO1*P 0W8Ce0f Ma.mg1*. ”qtO” 5< >0503 PLfASE DO NOT RETURN YOUR COMPLITED FORM TO EITHER OF THESE AODRESSE5 RETURN COMPLf~ TO THE Government ISSUING CONTRACTING OFFICER FOR THE CONTRACTI PROCURING ACTIVITY NUMSER LISTED IN ITEM 2 OF THIS FORM.*W 01 1. pm.ttt.1$ bo 10.qto. .mn. ..am *oIIh. TYPED NAME La$t) q SIGNATURE f DATE SIGNED (YYMMOD) h GOVERNMENT ACTIVITY C. b. V.eqrrnP. CLASSIFICATION J CD NO OF DEFE~ c TE. -m 0. EFFECT DN COST/ qRICE 20.o. Omof.3 W* SW! DI~wOIX*fO.0. NAME OF LOWEST PART /ASSEMBLY AFFECTED 16.. 4 ORffilNATOR a TYPED NAME (FIti.

6 identifies situations F. standard. F. 176 - . The DD Form 1696 shall provide the F.6. The information contained herein is intended for compliance.1. F.4.1 GENE~L —. DD Form 1696 is the information required by this Appendix. and shall include detailed change information as required by 5. Form 1696 is authorized.4 GENERAL REQUIREMENTS Paragraph 5. Local reproduction of DD under which an SCN is required. Any data which cannot be included in the block spaces allotted on the form shall be included in attachments referenced in the block.2 APPLICABLE DOCUMENTS This section is not applicable to this Appendix. Block 16 (Upper ~“ half). For purposes of this Appendix. have been divided to clarify entries.1. DD Form 1696.l scope.MIL-STD-973 APPENDIX F INSTRUCTIONS FOR PREPARATION OF SPECIFICATION CHANGE NOTICE UTILIZING DD FORM 1696 F. shall provide the information required in this Appendix.4. This Appendix establishes uniform requirements for preparing-the DD Form 1696. the definitions contained in Section 3 of this standard shall apply. required form to be used for processing an SCN unless a contractor format has been authorized by the Government.4. F. The SCN should only state the exact change proposed to the specification.1 AD Dlication. “Specification This Appendix is a mandatory part of the Change Notice”. Figure 11. chanqed F. F.3.4. F.2 Preparation of DD Form 1696.3 DEFINITIONS F.1 Definitions used in this ADD endix. and Block 17 (lower half).4.3 Paqes affected by this SCN and Deviously The columnar sections of DD Form 1696.2 14DP lication.

177 .MIL-STD-973 APPENDIX F . F. F. series (or the nomenclature number) for the system (or major item of equipment. Related ECP number. Enter the complete ECP number (including dash numbers and revisions) that identifies the related engineering change.3 activity. including revision letter.11 Block 11.9 Block 9. F.1O Block 10. Enter the type.5. Block 3.8 Block 8. Enter the identification number. activity preparing the SCN.5.5. F. name and address of the contractor or Government activity which is preparing the SCN. Svstem desiccation.2 Block 2. To be used by Government for entry of internal processing number. If the SCN is being submitted to the Government for final technical approval. Indicate by an “X” in the appropriate block if this is a proposed SCN. Specification number.5.5. The approved block will be marked by the Government upon approval/contractual implementation. Enter the DODAAC of the procuring Enter the F.4 Block 4.5 DETAILED REQUIREMENTS. Enter the CAGE Code of the design activity for the specification identified in Block 7. Enter the CAGE Code of the DLA F. F. Date. Cataloging Handbook H4/H8 contains these codes.6 Block 6.— F. F. Procurinq Activitv No. Originator name and address. CAGE Code. DODAAC . completion of the DD Form 1696. starting with the number “l”. prior to distribution according to the contract. F.5. sequentially for each specification and revision. of the specification being changed. F. F. CAGE Code. if it is not a system) affected. model.7 Block 7.5.1 Block 1.5 Block 5.5. SCN number. Enter the identification SCN numbers are issued number for the SCN being submitted.5.5. if desired. both blocks should be left blank.5. Detailed instructions for Enter the submittal date of the SCN. SCN type.

16 Block 16.5. enter the identification number of each SCN starting with SCN number 1 at the top of the column.13 Block 13. A separate line should be used for each category of page change. Related ECP number. enter the serial numbers of the items for which this SCN is effective. Configuration item nomenclature. Enter a listing of all pages being changed by this SCN and indicate whether the pages are being superseded or added (by entering an “S” or an “A” in the column) or deleted (by printing the word “deleted” after the page numbers so affected).5. (Indicate deletions] . F.12 Block 12. For CSCIS.MIL-STD-973 APPENDIX F F. Contract number. enter the number of the contract modification document used to contractually implement the change. enter the revision or version of the CSCI to which the change applies. this will be different than Block 10. the new version number should be entered here. Block 15. Effectivity. F. if applicable. For all SCNS previously submitted. F. Once the SCN has been approved by the Government. SCN number. If a new version is warranted by the incorporation of this ECP. Paqes. F. 17.5. F.5. Enter the complete contract number(s) affected by this SCN. Enter the nomenclature (name and number) of the CI affected by the change . Summarv of Previously Chanaed F.5. Enter the identification number (including revision designator and dash numbers) of each ECP effected by each previously issued SCN against this specification revision. For hardware. The entries in this section (upper half) shall provide information about the pages affected by the SCN being submitted. For the approved SCN only.17 Block 17. Paqes affected by this SCN.1 Block 17a.2 Block 17b. enter the approval date (from Block 18) in this block. If a unilateral change order is utilized for initial authorization. it’s number shall be entered in this block.5.5. 178 - . b.15 a.14 Block 14. Contractual authorization. There should be no entry in this block on a proposed SCN. Usually this will include the applicable production line items plus items approved for a retrofit or modification program.5. 17. F. Normally.

17. F.5.5. enter the” submitted date for each previously submitted SCN that has been approved opposite the appropriate SCN number in Block 17. For each approved SCN previously submitted.5. or a duly appointed representative. Date submitted. to designate approval of the SCN .18 Block 18. contracting officer. Indicate whether the “S” or an pages are being superseded or added (by entering an “A” in the column) . Government activitv.4 Block 17d. 17. A~Droval date. 17. The Government F. A separate line should be used for each category of page change. enter the submittal date for each previously submitted SCN opposite the appropriate SCN number in Block 17. F. When Block 18 has been signed and the approved box has been marked. and will mark an “X” in the approved box. the status of the SCN changes from a proposed SCN to an approved sCN . For the approved SCN. will affix an approval signature and the date in this block.5. F.MIL-STD-973 APPENDIX F F.les.6 Block 17f. For a proposed SCN.5 Block 17e. TvDe of Chanqe. Pac. enter its approval date on the same line as the SCN number in Block 17. The signature denotes technical concurrence with the contents of the DD Form 1696 and attached change pages.17.3 Block 17c. - 179 . List the pages changed by each previously issued SCN against this specification.5.

CAGE CODE 9. SYSTEM DESIGNATION 11. 4 O~lGINATOR J TYPED NAME (Fms’t.t..o. ~cific~tion ~ntjfiod by tlw numhr (Jti rovisii lett~r) shown by this SCN qrc thosa furnished harawith and carry @U q ppoval dtta of ttw Ram 11.etiw . ons if? oosoww Figure 11.q thn tiworn w. ISYO. — .mawa to q vefqo J !toun sw WWO.t. PAGES AFFECTEO W THIS SCN PAGE(S) a TYPE OF CHANGE” b APPROVAL DATE (YYMMDL7) c 7.—. Cny. W that th.. irsforms rocipicnts PAWS Cltarsgd in tsom relatad of the 7 hss boon EC? list~ m original ISSUC It. SPEC NO. Tha pD~s of ttw ps~ numbers trsd dates Iistad in Items 16 qnd 17. AuTt40aIzATloN 10..IRrwof. S. RWUritOO PWCa (O1OKIISS) Wtwmnqton DC 20S01 1220>4302 . d Morm.g .vshown in ttom 7. DMuIoroI. fw .m tho. b ADDRESS (Street. CONTRACTUAL 14. SUMMARV CN NO a Of PAEVIWSLY NO CHANGED PAGES PAGE(S) c REmTE:ECP DATE SUBMITTED (YYAfMoD) d TYPE OF APPROVAL DATE CHANGE* (YYMMOO) t f “S-mdfcat~s c.tlg.~.. Durdr” to D. zlP Code) 8.wm.MIL-STD-973 APPENDIX F 1.d~.t. cocnbimd with non.ow wmrvnp. A4dd/e Imtfd Las7] -R uu rrxm . .listed wws Of th r. of mfotmww . This rsotu. SCN TYPE PROPOSED APPROVED CAGE CODE 7..qa of IntOImatma n mt.ndcomti*Imq atw rwcwq the ccdknoo. PROCURING ACTIVITY NO.m “ewquanon $w. Y4 Pr?vjouj cuir.qwa. c?n c SIGNATURE d DATE SIGNED (YYh4Moo) (hit.t.n~e.a Government I TYPED NAME su~r~cdos ACTWITY qarller ptge ‘“A“ )nd!cates added Page “D- lnd)c~tes deltt. CONTRACT NO.* miIUWIV w t. WA qnd 10 ttw OUQm of Manag+m@nt q . 13.fw tof rti.-” m.t. RELATED EC? NO. St4t~. DATf (YVMMOO) Form Approved 0M8N0 0704-0188 SPECIFICATION CHANGE NOTICE (SCN) *ubIIcwporrmgnufom W ltm mllurtm wbrch.q10.SCN NO. wnd ‘Omm.i nd v. o. . qnd a~rll ~11 MWu7n DOV. CONFIGURATION ITEM NOMENCMTURf 15 fFFE~lVITV cfswsgod. Last) 6. z 3 DOOAAC PLEASf 00 NOT WIURN VOUR COMPLCTf D FORM TO EITHER Of THESE ADORESSES.mform. 01 4. I Qatlwmqana ma. MIdd/c In/f/#/.on ~rstmn.I WSVFW.v othm abrma of f +s calm. Swtt 120a Atl!. .tst. !2.8. .Sttu*. constitute h currwst q pproved version of this s~cificAtion. wn ...nckeoq w ~m to tCo Uclq !!!..q .. RETURN COMPLETED FORM T~GOVtRNMEN7 tSSUING CONTRAOING OFFKER FOR THE CONTRAffI HOCURING ACTIVITV NUMBEfl LISTED IN ITEM 2 OF THIS FOnM. Specification Change Notice 180 .rcm mtm*t* 2..owlmwnl of O.

Originator name and address.4. Detailed instructions for G.3.5. to propose revisions to drawings. G.2 ADP lication. Procurinci Activity No.MIL-STD-973 APPENDIX G INSTRUCTIONS FOR PREPARATION OF NOTICE OF REVISION UTILIZING DD FORM 1695 G. APPLICABLE DOCUMENTS This section is not applicable to this Appendix. Normally this date will be identical to the ECP submittal date. Local reproduction of DD Form 1695 is authorized.- 181 . G.1. See 5. To be used by Government for entry of interim processing number. completion of the DD Form 1695.2 G. Block 3. Enter the name and address of the contractor or Government activity submitting the proposed NOR. G. .5.5. G. if desired. the definitions contained in Section 3 of this standard shall apply. Date.1 GENERAL G.1 Definitions used in this ADD endix.5 DETAILED REQUIREMENTS..1 Block 1. associated lists. The contractor shall use DD Form 1695. G.7 for NORS applicability.2 Block 2. G.l Scope.4 Block 4. Enter the submittal date of the NOR.4.3 activity. DODAAC . For purposes of this Appendix. Figure 12. The information contained herein is intended for compliance.3 DEFINITIONS G. Enter the DODAAC of the procuring G. “Notice of RevisionIt.4 GENEWL REQUIREMENTS G.1 Use of DD Form 1695.5. This Appendix establishes uniform requirements for preparing DD Form 1695. This Appendix is a mandatory part of the standard.1. or other referenced documents which require revision after ECP approval.

11 Block 11.12 Block 12. the originator shall either assign a number or enter the document number and new revision letter as the NOR number.5. Unless the use of a Government assigned number is prescribed. Enter the title of the document G. Enter the number of the ECP describing the engineering change which necessitates the document revision covered by this NOR. When the requirement in the contract identifies the NOR by ECP number. otherwise. 8C and 16 on ECP Form 1692).1O Block 10. Enter the number of the drawing.5. Description of revision. unless there are known outstanding NORS which may not have been incorporated.6 Block 6.5.8 Block 8. in Block 8. to which the Title of document.1O. ECP number.5. G. CAGE code. Enter the CAGE Code of the NOR number is assigned.1O. Revision letter.5 Block 5.5. Show the revision letter proposed for the revision covered by the NOR. NOR number. G.e.5.13 Block 13. NOR applies.5..9 Block 9. Document number.5. G. enter the name and type designation of the CI to which the ECP applies (see Blocks 8a. Usually the new letter will be the one following the current letter in alphabetical sequence. xxx-l). New. list or other document(s) to be revised.MIL-STD-973 APPENDIX G G. Show the existing revision of the document for which the NOR is prepared. G. Current. G. standard. G. G. G.5.5.1 Block 10a. NOTE : The Government may change the new revision letter proposed by the contractor in order to retain a proper sequence of approved revisions.2 Block 10b. Enter Government assigned system designation (if any) . Enter the originator’s CAGE code of the design activity for the drawing/document identified DLA Cataloging Handbook H4/H8 contains these codes. givinq the exact wording of sentences or 182 - . the originator shall attach a dash number (i.5. Confic4uration item (or system) to which ECP a~~ lies. Describe the revision in detail. G.7 activity whose Block 7. CAGE Code.

2 Blocks 14b. Activity authorized to a~prove chanae.15.5. G. G. Document status. 14e.5.This section for Government use only. -.. If SO. G.5. Activity accom~lishinq revision. G. Title. Activity. G. dimensions.5. The Government approving activity will enter an “X” in the first box if manufacturer may proceed using the existing document as modified a copy of the approved NOR will be furnished by this NOR.15 Block 15. Block 14. If additional space is needed. or that are to replace a marked print when necessary to clearly explain the desired Use a “From . use continuation pages.14.14. If the referenced ECP is approved and the NOR also is approved as written or corrected.. The name of the activity authorized to approve the ECP and the associated NORS for the Government will be entered by such activity. or in a letter of transmittal. and 14f. that are sentences to be added. an authorized representative of the Government approving activity will sign in this block. The name of the activity (custodian) that is directed to make the revision in the master document will be entered by the approving activity.To” format in the description of the revision. in the second box if the contractor is not enter an IfXII by the submitted authorized to incorporate the change proposed The Government NOR until receipt of the revised document. approving activity will enter an “X” in the third box directing the custodian to make the change and distribute copies of the The distribution list may be entered in revised document.5. 183 . change.3 Blocks 14d. G.5.MIL-STD-973 APPENDIX G paragraphs designated State the or paragraphs of the current document.1 Block 15a. siqnature and date.1 Block 14a. including entry of the date of approval. both to the contractor submitting the ECP and to the custodian of The Government approving activity will the master document. on a referenced enclosure. tolerances and other quantitative Attach requirements that are to replace current requirements. 14.14 SECTION 14 . and 14c.

including entry of the date of the accomplishment. Revision com~leted and date.15. 184 .5.MIL-STD-973 APPENDIX G G.2 Blocks 15b. The signed original shall be returned to the Government or held by the activity that maintains the master document. and 15c. An authorized representative of the custodian shall sign in this block to certify that the revision described by the NOR has been accomplished.

.o. . VA 2 PnncllalMG .w..010.MIL-STD-973 APPENDIX G NOTICE OF REVISION (NOR) TMIS 1. .n manufaaurc may mcoroorate th.. . RETURN COMPLETED FORM T~GOVERNMENT ISSUING CONTRACTING OFFICER FOR THE CONTRA~f PROCURING ACTIVITY NUMBER LISTED IN ITEM 2 OF THIS FORM b ADDRESS (Street. .. . O*I*PW Wawllqlon l’l*m”an Pf% Sr. . .. DESCRIBED BELOW -—-— f.cIu-w f~* ~-f Form OMB ADoroved Nci 07(M 0188 .----M m-.o.. La@ f DATE SIGNED (r’YMMDO) q SIGNATURE 1 I 15.d to the OMICr 01 Mmaqeme.6 R?ooti F’IOWI (0~04. I . >22024J02 a.fof-~t.cfltmon Wastinqlon Da*Is ~$-n~ar OC IC5 \ 3 PLEASE DO NOT RfTUaN YOUR COMPlf TED FORM TO EITHER OF THESE ADDRESSES. .. Mold/e /nn/d. ~ TypED NAME (Fnt. . .. TITLE OF DOCUMENT 1 l==+== 1 10. w . T)flS SE~lON a (x W@) FOR GOVERNMENT (1) Ex. ZIP Code) 9. . I 13... Owra!so. OESCRtPTION OF REVISION . REVISION LE~ER a CURRENT b NEW 11 ECP NO. .._ 14.DATE (YYMMDD) LISTEO..lofma!.. Notice of Revi3ion 185 .lm.mon toI .qetmwc. . 0’ HAS BEt N AUTHORIZED .t 4. D.0118\ 12”1~ .I1r 1204 . W mm $01 --. <011.-a S.. It< IoIJIe md ~OUIS WU. I 1~1. St#te..voIu p Wd. .. twm hrlmgto... REvISION ~--=.$ qm-ma !0 MIW - FOm THE DOCUMENT I -. M&le Inkial.song (2) llw$~d documw!t document USE ONLY suppiemwrtcd by ttm NOR may h uwd .t change must M r~cewed docummt before manufaaurer above (3) CU5tOd@n of master b d ACTWITy TITLE AUTHORIZED $hall make TO APpROVE CHANGE FOR GOVERNMENT revmon q nd furmsh rewscd document c TYPED NAME (Fwst. Cny.4 ACTIVITv ACCOMPLISHING REVISION b REvISION COMPLETED (Stgntturc) c DATE SIGNED (Y YMMDO) Figure 12.O.1 b.

This Appendix establishes requirements for CSA of the documentation and identification numbers which describe CIs. However.1. Without specifying the source for the information. H.5 which are not required of the contractor will normally have to be accomplished by the Government. Indeed. such as Task 502) that must be included in most CSA management information systems and the optional requirements (defined in Tasks X1X.1 Scope.2. The CSA requirements established by this Appendix shall apply throughout the life cycle of CIs and systems. and reporting systems will be tailored to address the phase of the life cycle. data base information elements.1. Contracts invoking this Appendix will specifically identify the appropriate applicable tasks and/or paragraphs in the contract statement of work or tasking directive. it is not cost-effective to buy the entire CSA capability from the contractor. Those minimum requirements of paragraph H. for CSA of the processing and implementation of changes to CIs and their associated documentation. and the complexity of the item being procured. many DoD activities have existing information systems that will provide much of the needed information (or they have the software for information systems into which you can enter and manage your information) and will usually provide this information/capability at no cost to your program. specific Government activities 186 . as appropriate. paragraph H.MIL-STD-973 APPENDIX H CONFIGURATION STATUS ACCOUNTING (CSA) REQUIREMENTS AND RECORDS H.2 This Appendix will be tailored by the Government in accordance with Section 6 to specifically identify only those CSA responsibilities to be levied upon the contractor.5 defines both the minimum requirements (defined in Tasks X0X.2 Applicability. such as Task 413) that may be useful for some programs to include in their CSA management information system.1 GENERAL H. Both the minimum and optional requirements to be accomplished by the Government should be identified in the Program Management documentation. and for CSA of the actual configuration of units of CIs. CSA work tasks. H. Tailoring instructions are provided in Section 6. H.1 A considerable amount of data is required in order to accomplish the status accounting function for a program. the scope of the program.2.1.1. other contractual provisions.

and suppliers.3. H. An information/management system shall be established to maintain a record of the most current versions of the documents.3 DEFINITIONS H.2. or their electronic equivalents.5. vendors. However.MIL-STD-973 APPENDIX H will be designated as responsible for their accomplishment. vendors. Specific information system capabilities and data elements selected from the following tasks shall be provided. and suppliers in order to meet the requirements of the Government. Minimum requirements in paragraph H.1 Definitions used in this Appendix. and suppliers and for the application of those necessary requirements to those subcontractors. the contractor shall be responsible for providing all of the information required by the tailored application of this Appendix in the contract.3 The contractor is responsible for the determination of the extent to which the requirements in the contract are applicable to subcontractors. H.5.5 H. This section is not applicable to H.1 SPECIFIC REQUIREMENTS Information system requirements. H. vendors.1. this Appendix. accomplished by neither the contractor nor the Government) should be identified and explained in the Program Management Documentation. These data elements shall be incorporated 187 .1 Descriptive documentation and identification numbers.4 GENERAL REQUIREMENTS. The system shall also identify all proprietary or restricted data and the CIs to which it applies and all licensing agreements and the CIs to which each applies. H.1. including the acquisition of the needed data from the subcontractors. which describe the CIs (and their component parts and assemblies) and to maintain a record of the most current identification numbers used to identify the CIs (and their component parts and assemblies). H.2 APPLICABLE DOCUMENTS This section is not applicable to this Appendix. For purposes of this Appendix. the definitions of terms contained in Section 3 of this standard and the definitions of the data elements contained in Appendix I of this standard apply.5 which are to be waived for the program (that is.

5.1. c. or PBL. d. H. h.2 Task 102: Specification revision/SCN history. For each specification prepared and maintained for this program to describe and control the performance and/or design of the system and its component CIs.MIL-STD-973 APPENDIX H into the system progressively and not later than the date when they first come under Government control as a result of the establishment of the FBL. so that the most current descriptive information is the primary information stored.1.3 Task 103: Drawing revision level.) A record of the same information shall be included for each specification describing an item of GFE used in the system. The information system shall maintain a historical file of the information in Task 101 for each revision of each CI specification from the date of initial release of the basic specification through the current revision and SCN. The specification identification number The specification title The CAGE Code for the design activity The CI nomenclature The current revision letter and date of issue The most current approved SCN number The date of SCN approval The related ECP number The contract number and CDRL sequence number.1.1 Task 101: Specification revision/SCN level. i. H. The record shall show: a. f. ABL.1. g. H. For each drawing (or equivalent electronic record) which is prepared and maintained to describe the parts and which is used to manufacture 188 .1. the system shall identify all currently approved documentation/identification numbers for those configurations. where continuing operational use of more than one configuration of a CI is approved.5. a separate record shall be maintained for each volume. e.1. These data elements shall be updated as changes from the baseline configuration are approved. b. a record shall be established and kept current. However. (For multi-volume specifications.5.

c.4 Task 104: Drawing revision history. H. The information system shall maintain a historical file of the information in Task 103 for each drawing revision from the date of release through the current revision. a record shall be established and kept current. and the identifier of the contractor’s change document 189 . where applicable. f. and the identifier of the contractor’s change document effecting the detailed change to the software and associated documentation. d. e.MIL-STD-973 APPENDIX H and support the system and its component CIs. f.1. b. The record shall reflect: a.1.5 Task 105: Software version level. h. The record shall reflect: a.1.5. a record shall be established and kept current. where applicable.5. The drawing number The CAGE Code for the design activity The drawing title The current revision level The part number(s) of the part(s) changed as a result of that drawing change and the effectivity of the part(s) in terms of CI serial numbers The ECP number effecting the change. H. c. The effective release date The contract number and CDRL sequence number. The software identification number The related CSCI specification number and title The CAGE Code for the design activity The software title The current version and interim version level The ECP number effecting the change. For each item of software purchased/created and maintained for the operation and maintenance of this system and its component CIs. e. g.1. d. b.

g.1. title. the current part number for the software/medium combination The contract number and CDRL sequence number... k. It shall be presented in a hierarchical. and CAGE Code for all hardware parts/assemblies and sub-assemblies (for software. where used. development.5. H.g.MIL-STD-973 APPENDIX H effecting the detailed change to the software and associated documentation. or indentured. The effective release date of the current version/ interim version The number. including those of superseded but still used configurations. next assembly) of the various pieces of the CI can be understood by looking at the arrangement of the record.5. name. a record shall be generated and kept current identifying the CI by name and identifier. and 190 .8 Task 111: Program contracts listing. manner so that the "level of assembly" relationships (e. h. the source code and object code components/units) that comprise the CI.1. The record shall also identify the number. the record shall list all parts/logical units that have been selected by the Government for logistics support and all components of those parts that have been selected as spares.1. For each CI.1.5.g. Contracts to be monitored include those which have been issued by the primary Government activity for the program (e.7 Task 107: CI component indentured listing. i. PROM). The information system shall maintain a historical file of the information in Task 105 for each version and interim version of the software from the date of initial release of the software through the current version. version and date for the current test procedures If the software is resident on a "read only" device (e.6 Task 106: Software version history.g.1. a record shall be established and kept current.1. title. production. version and date for the current operations/programmers/maintenance manuals and version description document The number. As a minimum. j. For each active contract affecting the program. long-lead. H. H..

1 Task 201: Changes being processed status. Specific information system capabilities and data elements selected from the following tasks shall be provided. The system shall contain general information about the change proposal and shall track specific events and dates associated with the processing of the change. Each record shall include: a. separate spares buys. GFE..2. H. nomenclature(s). or part number(s) of the top level assembly(s) being delivered under the contract The number of units to be delivered under the contract. and modifications) and for which all work and/or deliveries have not yet been completed.1. and it shall provide cross-correlation for all related (dash numbered) and companion (associate contractor) formal proposals. the tracking system shall establish and keep current a separate record to identify: a. c. d..5. for the formal proposal.g. ECP number) The CAGE Code of the originator The change title The configuration baseline(s) affected 191 . ECP. e. An information/ management system shall be established capable of tracking all proposed changes from first communication of an idea between the Government and the contractor through either official notice of disapproval or formal issuance of a final negotiated contract modification. b. For each change idea initiated by either the contractor or the Government.1. The type of change involved (e. The system shall contain the required information for the initial study document. d.g. c. The contract number The CAGE Code of the contractor The CI identifiers.g. and for each correction or revision to the proposal(s).2 Tracking active change processing. deviation/waiver) The change identification number (e. b.MIL-STD-973 APPENDIX H spares) or by other Government activities (e..5. H.

d.1. j.2. b. H. based on the need date and the priority of the change. Some of the typical events which this information system shall be capable of tracking include: a. It shall automatically assign suspense dates by which those activities must be completed.2.1. e. g.3 Task 211: Event date entries. the system shall identify and suspense the discrete activities involved in the review of the change by the Government. l. The Government’s change manager will have the capability to change suspense dates (except the need date) and to input completion dates reflecting the status of the processing of the change.2 Task 202: Changes being processed history. f. Change receipt Distributed for coordination/comments Coordination/comments due Technical meeting Corrections due from contractor CCB Directive to contracting 192 . For each change tracked in Task 201. The title and number of the affected specification(s) The related SCN/NOR number The priority The date on which the change was transmitted to the Government The "need date" for a decision on the change The final CCB decision The date on which the official decision notification was provided to the contractor.5.5. H. k. i.MIL-STD-973 APPENDIX H f. g. c. h. The information system shall maintain a historical file of the information in Task 201 for each change document submitted by the contractor to the Government throughout the life of the contract.

MIL-STD-973 APPENDIX H h. i. Design activity’s need date Contract modification issued.

H.5.1.2.4 Task 212: Change processing history. For each change tracked in Task 211, the information system shall maintain a historical record of the dates of all specific Government events throughout the life of the contract. H.5.1.2.5 Task 213: Date search capabilities. For each change tracked in Task 201, when a specific beginning and end date are specified by the user, the system shall have the capability to provide information (as a calendar listing sorted by day) about all scheduled, but not yet completed, events during that time span. Likewise, when an "as of" date is specified by the user, the system shall have the capability to identify all scheduled, but not yet completed, events that should have been accomplished by that date and to sort them by the magnitude of their delinquency. H.5.1.3 Approved changes to CI configuration. An information/management system shall be established to document the initial approved configuration of each CI and to identify the impact of each approved, contractually authorized Class I (or agreed-to Class II) change to the approved configuration. The following task defines the specific information system capabilities and data elements which may be required. H.5.1.3.1 Task 301: Approved change identification and effectivity. For each CI, a historical record documenting all of the changes that have been approved against that CI shall be established and kept current. The record shall reflect: a. b. The change identification number The CAGE Code of the originator (plus for Class I changes the identification number of the Government procuring activity) The title of the change The date of approval of the change The contract modification number, if appropriate The complete unit serial number effectivity (or the month and year of implementation for Class II changes)

c. d. e. f.

193

MIL-STD-973 APPENDIX H g. h. The serial numbers of already-delivered units to be modified as a result of the change The new part numbers and/or drawing revision levels and/or new software component/unit versions (and related affected manuals) resulting from each approved change The contract number and CDRL sequence number.

i.

H.5.1.4 Implementation of approved changes. An information/management system shall be established to track the accomplishment of all tasks required as a result of all approved change proposals. The system shall include key elements of information about each change, including the functional activities responsible for the accomplishment of the tasks. The system may be required to establish and track scheduled and actual dates for the accomplishment of the various tasks involved in the implementation of each approved change. Specific information system capabilities and data elements selected from the following tasks shall be provided. H.5.1.4.1 Task 401: Approved change implementation activities. For each change approved against the system or one of its component CIs, the record established for Task 301 shall include specific suspense dates for the completion of all activities related to each of the major areas of impact of the change. The record shall also identify the specific contact point responsible for each activity, including their phone number. As appropriate to the change involved, these activities include, but are not limited to, the following: a. b. c. d. e. f. g. Status of Redesign and Testing Specification Change/Revision Activity Drawing Revision Activity Software Revision Activity Technical Manual Preparation/Revision Spares Purchase and Distribution Support Equipment Design, Purchase, or Modification

194

MIL-STD-973 APPENDIX H h. i. Retrofit/Modification Kit Development The contract number and CDRL sequence number.

H.5.1.5 Detailed approved change implementation activities. For each change approved against the system or one of its component CIs, each implementation area tracked in the record from Task 401 shall be expanded, as identified in the contract. It shall identify specific discrete activities leading to the completion of the work in that specific implementation area, and it shall include specific suspense dates for the completion of each of those discrete activities. Typical activities which this information system shall be capable of tracking are included in each of the following tracking areas: H.5.1.5.1 Documentation revision activity.

H.5.1.5.1.1 Task 411: Specification change/revision activity. If the change has affected a specification, the record shall track the activities required to distribute the official SCN to holders of the specification in the field. In some cases, the approved change will result in a revision to the specification; the record shall track the similar activities required to distribute the revised specification. Typical discrete events include: a. b. c. d. e. Approval copy prepared (update of originals) Copy submitted to Government Copy approved by Government Approved copy received by contractor SCN and pages distributed to all addressees.

H.5.1.5.1.2 Task 412: Drawing revision activity. If the change has affected a drawing, the record shall track revision, review, and official release of the drawing incorporating the change. Typical discrete events include: a. b. c. Receipt of approved change document Drafting of official drawing changes Review and approval by design function A (e.g., drafting)

195

MIL-STD-973 APPENDIX H d. e. f. g. h. Review and approval by design function B (e.g., design) Review and approval by design function C (e.g., quality) Approval/concurrence by Government representative Release of new document Revised drawings distributed to all addressees.

H.5.1.5.1.3 Task 413: Software revision activity. If the change has affected a software unit, the record shall track the revision, review, and official release of the software incorporating the change. Such tracking shall be provided for software used in the operation of the system, in the maintenance of the system, and/or in trainers and simulators for the system. Typical discrete events include: a. b. c. d. e. f. g. h. i. j. k. Receipt of approved change document Coding, checkout, and testing of the software changes Revision of affected manuals Review and approval by design function A Review and approval by design function B Review and approval by design function C Approval/concurrence by Government representative Release of new software version Update of Software Development Library materials Reproduction on appropriate medium (e.g., floppy disk, cassette, magnetic tape, electronic link) Revised code and manuals distributed to all addressees. Support element update activity.

H.5.1.5.2

H.5.1.5.2.1 Task 414: Technical manual and other related document preparation/revision. If the change requires revision of the information in various manuals written for operation or

196

MIL-STD-973 APPENDIX H maintenance of the CI, the new instructions must be available when deliveries of the new design to the field are started or when modification kits are delivered to the field. The record shall track the events leading to the publication and distribution of the new instructions. Typical discrete events include: a. b. c. d. e. f. Technical writing of the revision Verification of the instructions Revalidation of the technical manual Transmit original to control activity Reproduction of the required copies Distribution of the copies to all addressees.

H.5.1.5.2.2 Task 415: Spares purchase and distribution. If the change requires new spare parts to be stocked, the tracking record shall monitor the events required to provide them to the support organizations. Typical discrete events include: a. b. c. d. e. f. g. h. Old and new part numbers Quantity of new spares required Design Change Notice (DCN) number Design Change Notice issued to logistics activity Purchase/work order issued Parts received from manufacturing activity Parts shipped to support activity Parts received by support activity.

H.5.1.5.2.3 Task 416: Support equipment design, purchase, or modification. If the change requires the development or purchase of new support equipment, the tracking record shall monitor the events required to provide the support equipment to the supporting activities in time to support the new configuration. (When modification of existing support equipment is required to support the new configuration, that modification

197

) Typical discrete events include: a. j. d. Quantity required Purchase/work order issued Issuance of requirements documentation Redesign.4 Task 417: Retrofit/modification kit development. Quantities of kits for delivered units Quantities of kits for spare units Quantities of kits for training sets Purchase/work order issued Parts delivered by manufacturing activity Installation instructions drafted Installation instructions verified 198 . b.5. g. f. g. Typical discrete events include: a. the tracking record shall monitor the events required to develop the kit of parts and the associated instructions. f. b. or new design. i. c. e.2.5. H. e. d. c. h.1. If the change requires that the new configuration approved for the production line be retroactively incorporated (retrofitted) into the units and/or support equipment already accepted by the Government. work completed Prototype constructed Testing completed Final CCB approval Update Engineering Release Records Production started Deliveries to Government.MIL-STD-973 APPENDIX H will be tracked with a record identical to the one used for tracking modification of operational units.

1 Task 501: As-built record. H. and their associated design activity CAGE Codes. and. H.5. or for which licensing agreements apply.1.1.6 Configuration of units in the field.6.2 CSCIs. Validation (proofing) of kit and instructions Delivery of kits to support activity. It shall contain: a. and to track changes to the configuration of each unit and component. As each unit of a CI is manufactured and delivered to the Government. An information/management system shall be established to document the exact delivered configuration of each unit.5. H. as well as certain specifically identified critical components of each unit. 199 .5. associated serial/lot numbers. The system shall be capable of identifying the exact configuration of each unit of the CI and of identifying the total number of units having a specific configuration.1. b. a record shall be established for the Government detailing the exact configuration. The verified detailed composition of the item in terms of subordinate HWCIs and subordinate parts. For HWCIs.1. engineering changes incorporated The variance from as-designed configuration The design activity CAGE Code for the HWCI(s) and the part(s) For part(s) with proprietary or restricted rights. d.1.1 HWCIs.5. shall be provided.6. the as-built data shall correlate to the as-designed engineering data and manufacturing/ quality records.1. H.MIL-STD-973 APPENDIX H h. c. For CSCIs. i.6. a record of the documents which specify the limitations. Certain critical components of each unit shall be tracked by both part number and serial number. the system shall identify all currently approved configurations and the quantities of each configuration in operational use. Specific information system capabilities and data elements selected from the following tasks shall be provided. where applicable. the record shall provide the VDD number and where the CSCI is installed. Where continuing operational use of more than one configuration of a CI is approved.

H. the record of the as-built history shall be updated with information reflecting the retroactive installation (retrofits or modifications) of new design parts in the unit.1.3 Task 503: Retrofit/modification history. The system shall contain general information about the action item and the article that it affects and shall track specific activities and suspenses associated with closing the action item. where applicable.5.2 Task 502: Maintenance history.6. Specific information system capabilities and data elements selected from the following tasks shall be provided. H. c. The record shall reflect the part number and. e. For each action item officially established by the contractor and the Government at each configuration audit for the program.6.1.1. For each unit delivered to the field. the serial number of any part replaced in the unit by maintenance action. b. b. d.MIL-STD-973 APPENDIX H H.1.7.7 Tracking audit action items. For each unit delivered to the field.5. The system shall be capable of providing cross-correlation of all action items to be able to present the current status of all action items relating to a specific audit for a specific configuration item. H.1 Task 601: Audit action item status. An information/ management system shall be established capable of tracking all action items that are established as a part of the functional and physical configuration audits for all of the program’s configuration items (and the system.5. if applicable). the record of the as-built history shall be updated with information reflecting maintenance actions performed on the unit. The record shall reflect: a. The identification number of the CI affected The type of audit The identification number of the action item Short title for the action item The date the action item was established 200 . the tracking system shall establish and keep current a separate record to identify: a.5. The most current part number and name The serial number of the part currently installed in that unit.

201 . Contractual and/or specification requirement affected For each activity identified as required to close out the action item.1. throughout the life of the contract.7. provide: (1) (2) (3) (4) Identification of the activity Identification of the responsible agency The suspense date for completion of the activity The actual closeout date of the activity.MIL-STD-973 APPENDIX H f.5. g. The information system shall maintain a historical file of the information in Task 601. H. organized by configuration item and by audit type.2 Task 602: Audit action item history.

3. Required status accounting information shall be expressed in terms of the standard CSA data elements listed in the detailed requirements of this Appendix.1 Definitions used in this Appendix. ACSN . 202 . or variations shall not be used. The data elements described in this Appendix constitute a minimum set of data elements available for CSA records and reports.4. Additional CSA data elements and related features may be added as required and approved by the Government.1 Standard CSA data elements. alternatives. I.1 GENERAL I.1 Scope.BUDGETARY COST ESTIMATES .ALTERNATIVES TO SUGGESTED CHANGE/STUDY.DATE . such requirements will be specified by the Government.See ESTIMATED NET TOTAL COST SAVINGS.12-M.2 APPLICABLE DOCUMENTS This section is not applicable to this Appendix.3 DEFINITIONS I. including cost considerations and desirability of each alternative.2 Supplemental CSA data elements. For purposes of this Appendix.4. I. the definitions of terms contained in Section 3 of this standard apply. This Appendix is for guidance only.1. Except as may be covered elsewhere in this standard. I.4 GENERAL REQUIREMENTS I. ACSN . I.MIL-STD-973 APPENDIX I CSA DATA ELEMENTS I. This Appendix identifies and defines a standard set of CSA data elements. This Appendix does not prescribe the utilization of data elements or the format of specific CM records. All supplemental data elements shall be defined in accordance with DoD 5000. I. Used to describe each alternative. Substitutes.See DATE PREPARED.5 DETAILED REQUIREMENTS ACSN .

ACTION ITEM DATE. established. ANALYST. ACTION ITEM TITLE. The actual date that production of the designated units with the engineering change is completed.See CHANGE ID. ACSN . The street or post office mailing address for an individual or company.See NAME and ADDRESS. completed. Identify the analyst by name that has been tasked to evaluate and find a solution to the software/firmware problem. ALLOCATED BASELINE (ABL) . ADVANCE CHANGE STUDY NOTICE (ACSN) . ITEM NAME. ACTUAL DATE. 203 . The short title describing the subject of an audit action item. An alphanumeric code used as the unique identifier and primary reference for an audit action item. ADVANCE CHANGE STUDY NOTICE (ACSN) NUMBER .ITEM AFFECTED . The date on which an audit action item was ACTION ITEM ID.See BASELINE IMPACT CODE.DESCRIPTION OF CHANGE/STUDY .MIL-STD-973 APPENDIX I ACSN . CONTRACT NUMBER. An entry in this field indicates that the change affects an end item currently being retrofit.ORIGINATOR . An alphanumeric code used as the unique identifier and primary reference for a residual task resulting from an audit action item. ACTUAL RETROFIT.See CI NOMENCLATURE. and/or enhancement. ACSN .See CHANGE/DOCUMENT TYPE.See DESCRIPTION OF CHANGE. The actual date that a specific activity was ADDRESS. ACTION ITEM RESIDUAL TASK ID. ACTUAL PRODUCTION COMPLETION DATE.

Date of approval/ disapproval of the RFD/RFW by the Government technical authority (e. ARRIVAL DATE . APPROVAL/DISAPPROVAL TYPE . APPROVAL/DISAPPROVAL TECHNICAL. The approved/disapproved designation of the RFD/RFW by the Government technical authority (e. PCO). name and title/ Government activity. APPROVED SCN . and/or enhancement. A code used to designate the type of configuration audit... Date of approval/ disapproval of the ECP/RFD/RFW/SCN by the Government implementation authority (e.See DATE RECEIVED.See DECISION TYPE. 204 . Configuration Manager).MIL-STD-973 APPENDIX I ANALYST ASSIGNED AND COMPLETED DATE. The approved/disapproved designation of the ECP/RFD/RFW/SCN by the Government implementation authority (e. APPLICATION. name and title/ Government activity. APPROVAL.See CHANGE/DOCUMENT TYPE. APPROVAL/DISAPPROVAL TECHNICAL DATE.. ASSOCIATED CHANGE REQUESTS/PROBLEM CHANGE REPORTS. List all associated change requests or problem change reports related to the identified problem/error. A code which indicates the application of the engineering release record (ERR) change data to the configuration file.. ANALYZE-TIME. Identify the time needed to analyze the problem/error/PCR (start and stop time).g.g. Identify the date the analyst was assigned and the date the analyst completed the task.g. name and title/ Government activity. Configuration Manager).g. Identify the configuration control board and the date of the approval for the software/firmware. APPROVAL/DISAPPROVAL FINAL DATE. name and title/ Government activity. PCO). APPROVAL/DISAPPROVAL FINAL. AUDIT TYPE.

Identification of a group of consecutive production units of a CI designated to have an identical configuration. BLOCK NO. This CAGE is the one that becomes part of the document’s unique identifier when combined with the document/drawing identification. DESIGN ACTIVITY . The title of the submitted change. Request for Deviation/ Waiver (RFD/RFW). An alphanumeric code used as the unique identifier and primary reference of the change. CAGE. The CAGE of the controlling design agency of CAGE. Three field containing the type of accompanying Document/Engineering Order. The CAGE of the design agency or contractor responsible for the physical maintenance and modification of the document. CURRENT. CHANGE STATUS. of change/document. CHANGE NOTICE/ENGINEERING ORDER ID.See BASELINE IMPACT CODE. the document. Identify the current status for the software or firmware baseline. BASELINE IMPACT CODE. CHANGE TITLE. CAGE. CAGE (COMMERCIAL AND GOVERNMENT ENTITY). CUSTODIAN. . A code indicating the status of the Engineering Change Proposal (ECP).See CAGE. A five digit code assigned to every government (design) agency or contractor. ORIGINAL. if applicable. A designator used to refer to the type CHANGE ID.MIL-STD-973 APPENDIX I BASELINE AFFECTED . The CAGE of the design agency that was responsible for the original generation of the document. BASELINE STATUS. CHANGE/DOCUMENT TYPE. CAGE. Document/EO Number. and its Revision. The identifier of the baseline affected by a change or RFD/RFW. 205 .

Contract Line Item Number . COMMODITY CODE. (2) Documentation problem. Weapons. Munitions.. The date that the Configuration Manager received the change/release document from the control center with the design agency recommended decision. CLASSIFICATION BY CATEGORY.The number of the section within the contract which specifies how a specific task is to be accomplished. The applicable classification of defect (CD) number of a contractor or Government activity. CM RECEIVED DATE. The date that the Configuration Manager signed and dated the change/release document as approved or rejected. COMPUTER SOFTWARE CONFIGURATION ITEM (CSCI) ID. CSCs may be further decomposed into other CSCs and Computer Software Units (CSUs). CNTRL RECD CM DECISION. Fire Control). A code indicating whether an ECP is classified as a Class I or Class II change. A code used to assign a basic functional area to the document (i. as follows: (1) Software/firmware problem. CM DECISION DATE. The date that the Control Center received the signed approved or rejected change/release document from the Configuration Manager. CLIN. 206 .MIL-STD-973 APPENDIX I CI NOMENCLATURE. CI DESIGNATION FOR RFD/RFW . CLASSIFICATION OF DEFECT (CD) NUMBER. A distinct part of a computer software configuration item (CSCI). and (3) Design problem. CLASS. The classification by category of problems detected during software/firmware operations.e. An alphanumeric code used as the unique identifier and primary reference for a computer software configuration item. COMPUTER SOFTWARE COMPONENT. A configuration item identifier which includes an alphanumeric designation and/or a noun name.See MODEL/END ITEM CODE or CSCI ID.

. The identification of the contract affected CONTRACT OFFICER ID/CODE/TELEPHONE NUMBER. CAGE . and telephone number.g. The contractor’s estimate of the cost of implementation of the change/release action. baselined configuration document) affected by an audit action item or change document. statement of work.See CONTRACT MOD/AGREE ID. CONTRACTOR ADDRESS .See ADDRESS. paragraph number) of a contractual document (e. An alphanumeric code used as the unique identifier for a package of data to be delivered as a part of a specific contract. CONTRACT DATA REQUIREMENTS LIST (CDRL) SEQUENCE NUMBER. Any contractor comments regarding software/firmware will be documented (text format).See NAME. his/her code. affected configuration item.g. The Contract Modification/ Supplemental Agreement Number (if applicable). The date of the contract modification or supplemental agreement number. 207 . CONTRACT MOD/AGREE ID. Three fields identifying the Contracting Officer. CONTRACTOR NAME . and Request for Deviation/Waiver (RFD/RFW). by the action. CONTRACT NUMBER. CONTRACTOR ECP/RFD/RFW NUMBER . CONTRACT MODIFICATION DATE . The specific portion (e.. CONTRACTOR ESTIMATED COSTS.See CHANGE ID. The basic source code element. authorizing the Engineering Change Proposal (ECP).See CAGE. CONTRACTUAL DOCUMENT REQUIREMENT IMPACTED. The nomenclature of an CONFIGURATION ITEM NOMENCLATURE.MIL-STD-973 APPENDIX I COMPUTER SOFTWARE UNIT (CSU). including Specification Change Notices (SCNs) (if applicable). CONTRACTOR COMMENTS. CONTRACT MODIFICATION DATE. CONTRACTOR.

Test (T).TARGET. target costs for interface changes to items other than Government Furnished Equipment (GFE). CURRENT REVISION . COORDINATION OF CHANGES WITH OTHER CONTRACTORS . based on following: Analysis (A).MIL-STD-973 APPENDIX I CONTROL IDENTIFICATION . CORRECTIVE ACTION TAKEN.See RIGHTS. DATE CONTRACTUAL AUTHORITY NEEDED. The actual cost(s) for Government interface changes which must be accomplished in delivered items. and/or documentation. The COORDINATION OF CHANGES WITH OTHER CONTRACTORS . The COORDINATION OF CHARGES BY GOVERNMENT .ACTUAL. Current status associated to the software. The target cost(s) for Government interface changes which must be accomplished in delivered items. DATE ERR TO CONTROL CENTER . and Closed (C). Reengineer (R). CRITICAL.See REVISION.See DATE RECEIVED. A classification of a defect. CSCI AFFECTED.ACTUAL. COORDINATION OF CHARGES BY GOVERNMENT . The date by which contractual approval is required in order to avoid delays to the production delivery schedule and/or change pricing proposed in an engineering change.TARGET. DATA RIGHTS DESIGNATOR . RFD/RFW. CURRENT SOFTWARE OR FIRMWARE STATUS. DATE CCB/ACTION . Implementation (I).See NEXT HIGHER ASSEMBLY. actual costs for interface changes to items other than Government Furnished Equipment (GFE). 208 . Deferred (D).See SCHEDULE DATE or DATE OF DECISION. a classification of a Identify the CSCI that is affected. A brief description of the action being taken to correct non-conformance to prevent a recurrence of the RFD/RFW. firmware.

DAYS AFTER CONTRACT APPROVAL. DATE SUBMITTED. DECISION TYPE. DATE OF REVISION. DATE RECEIVED. The code that indicates the type of decision DEFECT CLASSIFICATION . The date a proposed change was distributed for coordination and completion date for coordination. List the date and time that the software incident/problem occurred. DATE PREPARED. DATE OF DECISION. DESC SOFTWARE AND/OR FIRMWARE INCIDENT OCCURRENCE. The number of days after contractual authorization to complete each scheduled change action required to implement an approved change. approval or information.MIL-STD-973 APPENDIX I DATE COORDINATED. MAJOR. the defect number(s) which correspond with the characteristics from which an authorized deviation or waiver is requested.See CRITICAL. DEFECT NUMBER. The date a decision is made. Describe in detail the software or firmware incident that occurred. The date a required item or document was received at a designated location. made. DESCRIPTION OF CHANGE. DATE/TIME SOFTWARE INCIDENT OCCURRENCE. NOR. or MINOR. 209 . ACSN. DATE TO CONTRACTOR. or waiver.A brief summary of a Deviation or Waiver. A brief summary of a Change. The revision date shown on the revised drawing or document. deviation. The date assigned to a document(s) submitted to an activity for action. The date a change/release document was originally prepared. Date originating contractor is notified of the disapproval decision applicable to the change. Where a CD number applies. or DESCRIPTION OF RFD/RFW .

Identify the operating system software used by the developing activity to create the project/system (including version number). DISK SPACE UTILIZATION. Used to track the utilization of disk space when resource limitations apply. A designator used to categorize a document.See LOWER LEVEL ITEMS AFFECTED. The date the responsible agency signs the recommended decision for the change/release action. DRAWINGS AFFECTED.ALL LOWER LEVEL ITEMS AFFECTED . DISTRIBUTION. DRAWING ID .BASELINE AFFECTED . ECP . Identify the software used by the developing activity to create the project/system (including the version number). A list of drawings affected by an engineering change. List includes drawing number.See DOCUMENT TITLE.MIL-STD-973 APPENDIX I DESIGN AGENCY DECISION DATE. An alphanumeric code used to designate a specific DOD Acquisition Agency. ECP . DEVELOPMENT (HOST) HARDWARE. Codes used to indicate the authorized circulation or dissemination of a document.See DOCUMENT ID. CAGE Code. DEVELOPMENT SOFTWARE. ECP . DODAAC. Identify what hardware was used by the developing activity to create the software for the project/system (including modifications and upgrades). The title of the document. DOCUMENT ID.See DECISION TYPE.CLASS I .See BASELINE IMPACT CODE. revision level. DOCUMENT TITLE. 210 . DRAWING TITLE . DEVELOPMENT OPERATING SYSTEM (HOST) SOFTWARE. DOCUMENT TYPE. An alphanumeric code used as the unique identifier and primary reference of the document. and any applicable Notices of Revision (NORs).

EFFECT ON FUNCTIONAL/ALLOCATED CONFIGURATION IDENTIFICATION . 211 .See CHANGE ID. ECP .See DATE PREPARED.See CONTRACT NUMBER and CLIN. ECP . The effects on the delivery schedule that will result from both approval and disapproval of an engineering change or RFD/RFW.EFFECT ON PRODUCT CONFIGURATION DOCUMENTATION. ECP . or SOFTWARE/FIRMWARE IMPACT.See ILS IMPACT.See DECISION TYPE. INTERFACE IMPACT. CAGE. ECP . ECP .EFFECT ON CONTRACT DELIVERY. CI NOMENCLATURE.See EFFECT ON DELIVERY SCHEDULE.PRODUCTION EFFECTIVITY BY SERIAL NUMBER .ORIGINATOR NAME AND ADDRESS . ECP . CHANGE/DOCUMENT TYPE. A YES (Y) or NO (N) indication as to whether an Engineering Change Proposal (ECP) will affect the delivery date of the item being procured under contract. DRAWINGS AFFECTED.See PRODUCTION EFFECTIVITY. ECP . INTERFACE. ECP . OR SOFTWARE .See ILS IMPACT.EFFECT ON ILS. MODEL/END ITEM CODE. ECP .MIL-STD-973 APPENDIX I ECP .DESIGNATION .NUMBER . INTERFACE IMPACT.EFFECT ON PRODUCTION DELIVERY SCHEDULE . ECP . ECP . CHANGE ID. SPECIFICATIONS AFFECTED. INTERFACE IMPACT.RECOMMENDED ITEM EFFECTIVITY .EFFECT ON DELIVERY SCHEDULE.DATE .EFFECT ON COST/PRICE .See NAME and ADDRESS. ECP .See RETROFIT EFFECTIVITY. ECP . ECP .See CI NOMENCLATURE. ECP REVISION.See ILS IMPACT.CLASS II . SPECIFICATIONS AFFECTED.CONTRACT NO AND LINE ITEM . LOGISTICS.See ESTIMATED COST/SAVINGS UNDER CONTRACT. AND OPERATIONS .

Identify the follow-up disposition taken to implement the solution. ECP . ESTIMATED COST/SAVINGS UNDER CONTRACT. The date of the releasing engineering release record (ERR).See CHANGE TITLE. END ITEM NUMBER. FLIGHT SAFETY. The total estimated costs/savings impact of the Engineering Change Proposal (ECP) on the contract. 212 .See RETROFIT EFFECTIVITY. The total estimated costs/savings impact of the basic and all related change proposals including other costs/savings to the Government. END ITEM CODE. ERR DATE. FOLLOW-UP DISPOSITION. See END ITEM NUMBER. revision or version. N=NO.REVISION or See REVISION.RETROFIT EFFECTIVITY . ESTIMATED NET TOTAL COST/SAVINGS. The designator as shown on the engineering drawing used to identify the location of the part. The estimated delivery dates for retrofit kits required by the approval of an engineering change. The estimated date that the project/system is to be released/delivered to the user. The identification of a part or document that affects/impacts on the safety of flight of an aircraft. ESTIMATED KIT DELIVERY SCHEDULE.MIL-STD-973 APPENDIX I ECP . ERR NUMBER. ECP . FILE IDENTIFICATION. Note if the follow-up correction action was taken (Y=YES. N/A=Not Applicable). This field is also used for sequence numbers which identify alternate or optional parts to the preferred part.TITLE OF CHANGE . ESTIMATED RELEASE/DELIVERY DATE. The identifier for a file including its FIND NUMBER. The designator for any piece of equipment produced by the assembly of component parts. See DOCUMENT ID. The symbol assigned to an engineering change proposal after a revision has been made.

JUSTIFICATION. INSTALLING ACTIVITY. The formal release or delivery date of the project/system to the user. The noun phrase used to describe an item. The identification of a temporary amendment to a document.See BASELINE IMPACT CODE. The impact a proposed change (ECP) will have on interfaces. INTERFACE IMPACT. INTEGRATED LOGISTICS SUPPORT (ILS) IMPACT. The reviewing design agency’s estimate of the cost of implementation of the change/release action into a contract. Trainers and Training). INTEGRATED LOGISTICS SUPPORT (ILS) COSTS (TARGET/ACTUAL). A code identifying the type of change document 213 . IN PRODUCTION.MIL-STD-973 APPENDIX I FORMAL RELEASE/DELIVERY DATE. IMPLEMENTATION SOLUTION. The target or actual ILS costs (or savings) resulting from the change action. KIND DOCUMENT. Publications Supply Operations (spares) Support Equipment (including Test Program Sets.. submitted. INTERIM CHANGE. Identify the solution used to implement the change/enhancement. INTERFACE. The identity of an organization installing an item or a modification to an item.g. A code which indicates the justification or reason for the preparation of the engineering change. FUNCTIONAL BASELINE (FBL) . Identify if problem is an interface problem. HOST SYSTEM .See DEVELOPMENT HARDWARE and DEVELOPMENT SOFTWARE. HOST SOFTWARE . ITEM NAME. An entry in this field indicates that the change affects an end item currently in production.See DEVELOPMENT SOFTWARE. Identify the impact a proposed change (ECP) will have on ILS (e. GOVERNMENT ESTIMATED COSTS. pending a planned revision.

214 . A code identifying the echelon of maintenance to perform the work associated with a retrofit requirement. MEDIA ID. The part number(s) for the parts at the lowest level of assembly affected by the proposed change.See DEVELOPMENT SOFTWARE. Not the theater of operations to which it is temporarily deployed which may be classified. The geographic locations of. The identification of the media on which the software. Used to track memory utilization when resource limitations apply.MIL-STD-973 APPENDIX I LETTER ID. a classification of an RFD/RFW. See DOCUMENT ID. LICENSE RESTRICTIONS DESIGNATOR. etc. a classification of an RFD/RFW. A classification of a defect. heat treat) simultaneously.g. LEVEL OF RETROFIT ACCOMPLISHMENT. LOCATIONS OR SHIP/VEHICLE NUMBER AFFECTED. MAJOR. The organizational Activity Code for (Company. or documentation reside (sometimes called programming or software tape (media). firmware. An identification number for correspondence. Used for part and material traceability as well as for change incorporation. MEMORY UTILIZATION. The identifier for a series of identical items made from the same lot of material or undergoing a process (e. MINOR.. LOT NUMBER. Wing. or the aircraft/ship/hull vehicle number for which the retrofit is to be accomplished. A classification of a defect. LINK IDENTIFIER . MIL SPEC/STD ID. LOWEST AFFECTED PART NUMBER(S).) to which the item is assigned. LOCATION. A code designating any restrictions on use of delivered items or data which were manufactured/procured under license from another design activity. Squadron.

MODIFICATION INSTRUCTION.A code which categorizes the type of change incorporated by a modification kit..g. 215 .. NAME OF LOWEST PART/ASSEMBLY AFFECTED.Navy. The number assigned to each item of supply repetitively used.. and Federal Item Identification Number (FIIN). An identifier of the specific categorization within Type as used in Nomenclature for a weapon system. Airframe Avionics. The instructions for performing a retrofit action. the North Atlantic Treaty Organization (NATO) code. etc. stocked or distributed within the Federal Government.See MODEL. e. NAME. e. Time Compliance Technical Order (TCTO) Air Force. Modification Work Order (MWO) . Also the The nomenclature of NATIONAL STOCK NUMBER (NSN). MODIFICATION KIT TYPE . MODEL. the 14 in the Type-Model/Series F-14D. The name of a specific individual or company.g. Various titles are used for these instructions.MIL-STD-973 APPENDIX I MOD KIT INSTALLATION DATE. Engine. the lowest part/assembly affected. MODIFICATION KIT COMPLETION DATE. MODEL/TYPE . Accessory.See MODIFICATION INSTRUCTION.Army.g. The identifier for the assemblage of necessary material required to perform a desired modification. e. MODIFICATION KIT NUMBER. name of a part or software program. MODIFICATION WORK ORDER . The NSN is a composite of the Federal Supply Classification (FSC) code. Date for installation of a kit to accomplish the retrofit action called for in an ECP and Modification Instruction in a specific serial number or a CI within the specified retrofit effectivity range. Technical Directive (TD) . purchased. The date (target or actual) when all changes associated with the modification kit or engineering change proposal have been accomplished. As a data item usually used to designate the entire Type-Model series.

CONFIGURATION ITEM (OR SYSTEM) TO WHICH ECP APPLIES See CI NOMENCLATURE.See DATE PREPARED. MODEL/TYPE. NOR .See QUANTITY.See DOCUMENT TITLE. NOR . NOR . NEW .DOCUMENT NO .See NAME and ADDRESS. NOR . release. NOMENCLATURE . ORIGINAL DRAWING DATE. A detailed explanation of the need for change. NOR .See CI NOMENCLATURE. NEED FOR RFD/RFW . NEXT HIGHER ASSEMBLY (NHA).See NAME. release. NOR . nature of improvement.REVISION.DATE .See REVISION. The part number of the next higher level item into which a given part is to be assembled. (CURRENT. NUMBER OF UNITS . NEW) . malfunction.ORIGINATOR NAME AND ADDRESS . etc.See DOCUMENT ID.See NEED FOR CHANGE. NOR . NOR . MODEL/END ITEM CODE.NUMBER .See CHANGE ID.DESCRIPTION OF REVISION .MIL-STD-973 APPENDIX I NEED FOR CHANGE. NOTICE OF REVISION (NOR). 216 . The name of the specification or standard that is being replaced.TITLE OF DOCUMENT . The date a document was approved for The date a drawing was approved for ORIGINAL TITLE. failure.See REVISION. NOR . ORIGINAL DOCUMENT DATE. ORIGINATOR NAME .See DESCRIPTION OF CHANGE. The identifier of a Notice of Revision (NOR) document which describes changes to a document requiring revision. defect.REVISION.

PCR TITLE. PART NUMBER. or documentation problem. The PCR title will briefly describe the problem or enhancement detected in software. The identification of a replaced part.MIL-STD-973 APPENDIX I OTHER COSTS/SAVINGS TO GOVERNMENT. When a part is re-identified as a result of an engineering change. PART NUMBER. firmware. A code indicating the pages affected (superseded. OTHER SYSTEMS/CONFIGURATION ITEMS AFFECTED. deleted) by an SCN. 217 .See PART NUMBER. the effectivity of the old part number is limited (from/to) and the replacing part is made effective (from) in accordance with the effectivity of the change. Target or actual miscellaneous costs or savings other than coordination costs/savings applicable to the affected contract and related to the change action. A YES (Y) or NO (N) indication as to whether there is an interface effect with other systems or configuration items. The PCR identifier/number is the method in which a software. OLD. The CI serial numbers for which a given part number applies. The PCR description will detail the problem or enhancement detected in software. PART IDENTIFICATION NUMBER. OLD. PCR IDENTIFIER/NUMBER. added. or documentation. PART NUMBER CHANGED . PCR DESCRIPTION. PERIOD TIME AFFECTED. PAGES AFFECTED BY SCN. firmware. Page numbers and a code used as the unique identifier and primary reference of the part. firmware. or documentation. A YES (Y) or NO (N) indicator as to whether a price adjustment will result from a proposed deviation/waiver. and/or enhancement is traced or identified. PRICE ADJUSTMENT. The identification of a replacement part. PART NUMBER EFFECTIVITY. NEW. The period of time for which a deviation/waiver is being requested.

PROCUREMENT ACTIVITY NUMBER.See PRODUCTION EFFECTIVITY. PRODUCT BASELINE (PBL) . PROCESSING TIME. These reports shall serve as input to the corrective action process.See PRODUCTION EFFECTIVITY. A code used in determining the relative speed at which an ECP is to be reviewed. A specific number of a series assigned by the manufacturer to an individual item for identification. deviation.MIL-STD-973 APPENDIX I PRIORITY. Used to track CPU utilization on time critical applications and when resource limitations apply.See PRODUCTION EFFECTIVITY. PRODUCTION COMPLETION DATE. The scheduled date for the production of the hardware production units affected by the engineering change.See NAME. The PCR shall describe the corrective action needed and the actions taken to resolve the problem. 218 . A PCR describes each problem or enhancement detected in software.See BASELINE IMPACT CODE. The production serial numbers of the hardware unit affected by an engineering change. PRODUCTION SERIAL CUT-IN . PROCURING CONTRACTING OFFICER . or documentation that has been placed under configuration control. The Government-assigned identifier for a proposed engineering change proposal. PRODUCTION SEQUENCE NUMBER (IN-OUT) . PROBLEM CHANGE REPORT (PCR). PRIORITY (SOFTWARE/FIRMWARE). firmware. PRODUCTION COST/SAVINGS. A one-digit (1-5) code used to identify severity of a software problem. PRODUCTION SEQUENCE NUMBER (SHOP SERIAL NUMBER). The savings applicable to production of the configuration item resulting from the incorporation of the change. PRODUCTION EFFECTIVITY. PRODUCTION SERIAL CUT-OUT . or waiver. See CONTRACT OFFICER ID/CODE/TELEPHONE NUMBER.

QUANTITY PER END ITEM. RECURRING DEVIATION/WAIVER.See SYSTEM/MODEL IDENTIFICATION NOMENCLATURE. QUANTITY. RELATED MANUALS . RELEASE DATE. Number of units of an item affected by a change deviation or waiver. PROJECT/SYSTEM NAME . The date a document was approved and released. A YES (Y) mark identifies that deliveries have not been completed on the contract. required. The identification number of a document which releases a drawing/document for production or procurement.See CHANGE/DOCUMENT TYPE. RESPONSIBLE ACTIVITY IDENTIFIER. A YES (Y) or NO (N) indicator as to whether a Deviation or Waiver has been previously requested and approved. QUANTITY DELIVERED. Identify in detail the recommended solution to be used for the implementation of a correction or enhancement. REQUEST FOR DEVIATION . A designator identifying the activity responsible for performing a specific task. A NO (N) mark identifies that deliveries have been completed.See CHANGE/DOCUMENT TYPE. The number of parts. or bulk materials The number of items shipped.See CHANGE/DOCUMENT TYPE.MIL-STD-973 APPENDIX I PRODUCTION Y/N.See MODIFICATION COMPLETION DATE. RELEASE ID. The number of units of an item used in the next higher assembly. assemblies. a CI. RETROFIT COMPLETION DATE .See TECHNICAL MANUAL (TM) AFFECTED ID. QUANTITY ITEM AFFECTED. QUANTITY PER ASSEMBLY. PROPOSED SCN . 219 . The number of units of an item used in RECOMMENDED SOLUTION. REQUEST FOR WAIVER .

RFD/RFW NUMBER .See DATE SUBMITTED. PRODUCTION EFFECTIVITY. 220 . RFD/RFW CLASSIFICATION . RFD/RFW ORIGINATOR NAME AND ADDRESS . approved.TARGET/ACTUAL.See DATE OF DECISION. The date upon which a royalty SCHEDULED COMPLETION DATE .See SUSPENSE DATE. RFD/RFW TITLE . RETROFIT SERIAL CUT-OUT (TO EFFECTIVITY) .See RETROFIT EFFECTIVITY. ROYALTY EXPIRATION DATE.See SYSTEM/MODEL IDENTIFICATION PART NUMBER. REVISION SYMBOL. REVISION.See RETROFIT EFFECTIVITY. A code identifying whether a document contains proprietary information (limited or unlimited). RETROFIT EFFECTIVITY.See NAME and ADDRESS.See CHANGE ID. RFD/RFW ORIGINATOR CAGE . SCN APPROVAL DATE .See CRITICAL. MAJOR or MINOR.See CHANGE TITLE.MIL-STD-973 APPENDIX I RETROFIT COSTS . RFD/RFW DATE SUBMITTED . expires. RFD/RFW SYSTEM DESIGNATION .See CAGE. RFD/RFW EFFECTIVITY . RETROFIT SERIAL CUT-IN (FROM EFFECTIVITY) . The level assigned to a document or a specific sheet to a released document. Estimated retrofit costs (or savings) against the affected contract for retrofit action. OR PERIOD TIME AFFECTED. or accomplished. The serial numbers of the CIS affected by an engineering change for which retrofit is recommended. RIGHTS.See LOT NUMBER. A mark such as a bar to indicate that a line of text has changed as a result of a revision.

The date a shipment was sent. Identify software tools used in development of a version of software for the project.See CONTRACT MOD/AGREE ID.MIL-STD-973 APPENDIX I SCN CONTRACTUAL AUTHORIZATION . SERIAL NUMBER(S) OF UNITS TO BE MODIFIED . SHIP/VEHICLE CLASS AFFECTED. The number (including dash numbers and revision) of the ECP to which the SCN is attached. SCN SYSTEM DESIGNATION . Identifier for a shipment. document.See PRODUCTION EFFECTIVITY or RETROFIT EFFECTIVITY. SCN NUMBER . SECURITY CLASS. SHIPPING DATE. The DOCUMENT ID for all previously submitted SCNs for the same specification. SCN ORIGINATOR CAGE . The identification of a ship/vehicle class. SOFTWARE DEVELOPMENT TOOLS.PREVIOUS. SCN ORIGINATOR NAME AND ADDRESS .See CI NOMENCLATURE MODEL/TYPE. associated with corresponding sets of retrofit cut-in/cut-out numbers.See NAME and ADDRESS. and/or VERSION LEVEL. The code for the security classification of a SERIAL NUMBER. when the delivered configuration item is installed in one or more such classes. SHEET. SCN EFFECTIVITY . RETROFIT EFFECTIVITY.See PRODUCTION EFFECTIVITY.See RETROFIT EFFECTIVITY. A specific number of a series assigned to an individual item for identification.See CAGE. The individual page number of a multiple sheet entry.See DOCUMENT ID. SERIAL NUMBER EFFECTIVITY . SHIPPING NUMBER. 221 . SCN RELATED ECP NUMBER. SCN NUMBERS .

ADA. revision level. SOFTWARE/FIRMWARE LANGUAGE. SPECIFICATIONS AFFECTED. A list of specifications affected by the approval of an engineering change. specification number. software/firmware test specification reference. PCR as a duplicate.. Describe what impact a change will have on the software. Included in list is type of specification.See DATE/CONTRACTUALLY AUTHORIZED.MIL-STD-973 APPENDIX I SOFTWARE/FIRMWARE/DOCUMENTATION IMPACT. DATE OF DECISION. See DOCUMENT ID. SOFTWARE/FIRMWARE TEST SPECIFICATION REFERENCE. phone number. FORTRAN. COBOL. SOFTWARE SUPPORT ACTIVITY (SSA).See SECURITY CLASS. SOFTWARE/FIRMWARE RESIDENCE IDENTIFIER . SPECIFICATION CHANGE NOTICE (SCN) ID. etc. SOFTWARE/FIRMWARE DUPLICATION. Responsible for support of the software/firmware on the proposal after the initial development.See MEDIA ID. Identification of the language in which the program is developed/written. SPECIFICATION CHANGE NOTICE (SCN) APPROVAL DATE .See ITEM NAME.See DOCUMENT TITLE. SPECIFICATION TITLE . A control identification (alpha or number and/or both) for the software/firmware to identify the version and revision of software or firmware). A status indicator closing a SOFTWARE/FIRMWARE INITIATOR/PHONE/DATE. SOFTWARE/FIRMWARE VERSION IDENTIFIER. SOFTWARE/FIRMWARE/DOCUMENTATION SEC CLASS . Identify the initiator. SOFTWARE/FIRMWARE TITLE . or documentation. 222 . Identify the SPECIFICATION ID NUMBER .See DOCUMENT ID. and any associated Specification Change Notices (SCNs). i. firmware.e. CAGE Code. and date of initiation.

MIL-STD-973 APPENDIX I STORAGE MEDIA - See MEDIUM ID. SUBMITTING ACTIVITY AUTHORIZED SIGNATURE/TITLE. The name and title of the individual within the organization submitting the proposed change, authorized to sign the proposed document. SUBROUTINE IDENTIFIER - See COMPUTER SOFTWARE UNIT. SUSPENSE DATE. The date by which a specific activity is scheduled to be completed. SYSTEM DESIGNATION - See SYSTEM/MODEL IDENTIFICATION NOMENCLATURE and MODEL/TYPE, MODEL. SYSTEM/MODEL IDENTIFICATION CAGE. Activity for the System. CAGE Code of the Design See NOMENCLATURE. See PART

SYSTEM/MODEL IDENTIFICATION NOMENCLATURE. SYSTEM/MODEL IDENTIFICATION PART NUMBER. IDENTIFICATION NUMBER.

TARGET PRODUCTION. An entry in this field indicates that the change affects an end item planned for production. TARGET PRODUCTION DATE - See SUSPENSE DATE. TARGET RETROFIT. An entry in this field indicates that the change affects an end item planned for retrofit. TARGET RETROFIT DATE - See SUSPENSE DATE. TDP NUMBER. An alphanumeric code identifying a Technical Data Package (TDP). TECHNICAL DIRECTIVE - See MODIFICATION INSTRUCTION. TECHNICAL MANUAL (TM) AFFECTED ID. The identifier (number) of a Technical Manual (TM) affected by a proposed change. TEST PROCEDURE NUMBER - See DOCUMENT ID. TEST PROCEDURE TITLE - See DOCUMENT TITLE. TIME COMPLIANCE TECHNICAL ORDER - See MODIFICATION INSTRUCTION.

223

MIL-STD-973 APPENDIX I TIME-CORRECT. Identify the time needed to correct the software/firmware problem, error, or enhancement (a start and stop time). TITLE OF CHANGE. TOTAL SHEETS. The title of the submitted change.

The number of sheets/pages in a document.

TRANSMITTAL DATE - See DATE SUBMITTED. TRANSMITTAL DOCUMENT ID. The identifier of a document utilized to identify the transmittal/shipment of an item/group of items. VECP CONTRACT NUMBER. The contract under which a Value Engineering Change Proposal (VECP) was submitted and approved. VECP CONTRACTOR NAME. The supply contractor submitting a Value Engineering Change Proposal (VECP). VECP DECISION DATE - See DATE OF DECISION. VECP NUMBER - See CHANGE ID. VERIFICATION/EVALUATION OF SOFTWARE/FIRMWARE INTEROPERABILITY. Identify any possible interoperability problems and the date of the evaluation. VERSION LEVEL - See SOFTWARE/FIRMWARE VERSION IDENTIFIER.

224

MIL-STD-973 APPENDIX J REPORTING THE ACCOMPLISHMENT OF RETROFIT CHANGES J.1 GENERAL

J.1.1 Scope. This Appendix defines the requirements to be invoked on contracts requiring the reporting of the accomplishment of retrofits and modifications to units of the CI that have been accepted by the buying activity. This Appendix is a mandatory part of the standard. The information contained herein is intended for compliance. J.1.2 Applicability. This Appendix applies to system, computer software, and equipment contractors responsible for implementing approved Class I changes. This Appendix applies in active contracts as a part of the contract modification incorporating an ECP into the contract which requires retrofit activity on units controlled by the contractor. J.2 APPLICABLE DOCUMENTS

This section is not applicable to this Appendix. J.3 DEFINITIONS

J.3.1 Definitions used in this Appendix. For purposes of this Appendix, the definitions of terms contained in section 3 of this standard apply. J.4 GENERAL REQUIREMENTS

J.4.1 Subcontractors. Prime contractors shall be responsible for compliance by subcontractors, vendors, and suppliers to the extent specified in the contract. J.4.2 Recording Class I changes. The contractor shall record the accomplishment of class I changes for units of the system, computer software, equipment, and spares which are under his control. This requirement shall not be used to report the accomplishment of in-production changes prior to delivery or acceptance. The contractor(s) having custody of the CI unit(s) affected shall record the complete information for each unit modified upon accomplishment of the approved change.

225

MIL-STD-973 APPENDIX J J.5 DETAILED REQUIREMENTS

J.5.1 Retrofit records. The contractor shall generate records of retrofit accomplishment as directed in the contract. The record generated for each unit affected by the retrofit shall include the following specific elements of information: a. b. c. Location. The location where the retrofit was accomplished. Identification of change. The ECP number and retrofit instruction number, when applicable. Configuration item affected. The CI identification number, CI part number or software version number, and CI unit serial number, as applicable. Date. unit. The date of installation on this serial numbered

d. e.

Part modified/replaced. The old part number and, if appropriate, the serial number of the part/assembly removed or modified. Part incorporated. The new part number and, if appropriate, the serial number of the part/assembly incorporated or modified.

f.

226

MIL-STD-973 INTERIM NOTICE 1 (DO) APPENDIX K CROSS REFERENCE GUIDANCE ON THE RELATIONSHIP BETWEEN CANCELLED MILITARY STANDARDS AND THIS STANDARD K.1 GENERAL

K.1.1 Scope. This Appendix provides information about the requirements paragraphs that were contained in the cancelled standards (identified in 6.4); it provides the related paragraph in this standard which provides essentially the same requirement or that addresses the requirement area. Information contained in this appendix is for guidance only. K.1.2 Applicability. This Appendix applies to all programs that are planning to apply this standard to an upcoming contract. It is intended to supplement 6.2 and Tables II and III by providing help in identifying requirements from this standard that should be incorporated into the contract. K.2 APPLICABLE DOCUMENTS

This section is not applicable to this Appendix. K.3 CROSS REFERENCE GUIDANCE

K.3.1 Cross reference from MIL-STD-480B (15 July 1988). Table IV provides a direct cross reference between each of the paragraphs contained in MIL-STD-480B and the related paragraphs in MIL-STD-973. Paragraph numbers from MIL-STD-973 followed by an asterisk (*) address the MIL-STD-480B requirement but do not necessarily require the exact same activities. K.3.2 Cross reference from MIL-STD-481B (15 July 1988). Table V provides a direct cross reference between each of the paragraphs contained in MIL-STD-481B and the related paragraphs in MIL-STD-973. Paragraph numbers from MIL-STD-973 followed by an asterisk (*) address the MIL-STD-481B requirement but do not necessarily require the exact same activities. K.3.3 Cross reference from MIL-STD-482A (1 April 1974). Most of the requirements formerly contained in MIL-STD-482A were deleted and replaced by a dictionary of Configuration Status Accounting Data Elements in Appendix I of this standard. That dictionary is intended for guidance purposes only for this issue of MIL-STD-973. Table VI provides a cross reference between each of the paragraphs contained in MIL-STD-482A and the related paragraphs in MIL-STD973.

NEW PAGE

226a

2 * * 5.2 5.2.2d * *4.3.2.4.3 5.1 5.2 5.5 N/A * *4.4.3.3.3 5.3.1 5.3.3.3.4.3.3.3 5.13 6.3.4.8.3.2.4.4.1.4.3.4.2 5.5.7 5.4 5.2.4 5.3.4.3.2.2.6.8 5.1.2.5 5.1.1.4.1 5.2 N/A * *4.3 * *4.2.1.1.4.4.2 5.2.4.4.3.1 5.1 * *4.4.1 5.2.3 5.4.1.4 * *4.4.10 N/A 5.1.2 4.2.1.3.1 * *4.2.1.11 5.1 5.2 * *4.3.2 * * .4c * *4.4.3.6.10 E.3.3.4b * *4.3 5.4.2.3.2.1 5.3.4 5.3 * * 5.4.3.3 5.1.4.2.1 * * 5.3.5 * * 5.2 5.3.1.8 5.4.1.3 5.3.3.4.4 5.4.2.3 5.4.4 5.6.2 5.4.2 * *4.1.3.1.2 5.3.2.4.2.3.4 * *4.3.3.1 5.3.2.1.3.3.4.4.2 * *4.2.3* 5. Cross reference from MIL-STD-480B (15 July 1988).2.5.1.4 * *4.5 5.))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))- TABLE IV.3.2.6.1 5.3.2.4.2.5 5.3.3.1* 5.1 5.6.2.1.5.3 * *4.1 5.3.5 5.2.1.3.6.4.4.8 5.3.3.4.2.4 5.4.4.3.5.2.3.3.3.2.2.1.4.2 * *4.4.1 5.3 * *4.3 5.4.2c * *4.5.5 5.6 5.4.4.4.1 5.1.3.2.2.5.3.4.3.2f * *4.1 5.1 * *4.9 5.3 5.3.2.2.3 N/A 5.2.5.3.2a * *4.4.5 5.6 5.4a * *4.3.4.4.1.1.2.1.2b * *4.4.2* 5.3.3.2 5.3 5.4.6 5.3 5.2.2 5.1 5.1 5.1.3.4 5.14 5.4.2h * *4.6.3.3* 5.1 5. MIL-STD-480B MIL-STD-973 * *MIL-STD-480B MIL-STD-973 REQUIREMENT REQUIREMENT REQUIREMENT * *REQUIREMENT 3 5.1.1 5.6.2.1 * *3 4.3.4.3 5.6* 5.2 5.3.1.1 5.3.2.6 5.4.4.2.2.3.4.3.3.5.2.6.2e * *4.4.1.3.3. NEW PAGE 226b .2.5.5 5.1.4.4.3.3.3.9 E.3.4.4 5.2 5.2.1 N/A * *4.1.4.8.3.3.2 5.3.5 * *4.1 5.3 5.4.1 * *4.12 N/A 5.4 5.4.4.4 * *4.1.2.5.2 5.8.2 5.3 * *4.1 5.5 5.6 N/A 5.2.4.2.2.4.3.2.7 5.1.3.4.3.3.1 5.3.1* *4.1 5.4.3.1 * *4.7* 5.4.3.3 * *4.1.2 5.1.5.3.1.4.3.2 * *4.4.1 5.3.2.3.2.4.4.1 DELETED * *4.3.2.2g * *4.2.5.3 5.4.3.3.6.3.4.4.3.3.4.2.11 G.9 5.1 [EACH TYPE] 5.7 5.2.4.3.2 5.1.7 5.2.2 5.3.2 5.3.1.2 * *4.2 5.3.4.MIL-STD-973 INTERIM NOTICE 1 (DO) APPENDIX K +)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))).1.2.4.4.

4.2 * *5.5 * *5.1.4.4.4.1 None 5.3 5.6.4.4.2 5.5 5.3.4.3.4.4. MIL-STD-481B MIL-STD-973 * *MIL-STD-481B MIL-STD-973 REQUIREMENT REQUIREMENT REQUIREMENT * *REQUIREMENT None 5.1 * *1.1 5.1.4.)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))NEW PAGE 226c TABLE V.4.2.2 N/A 5.4.3.4.6* * *5.6 * *5.1 5.3.8.3 5.1.2.2 5.4.4 APPX E APPX F * * * * APPX F APPX D * * * * APPX G 6.1 5.6.6.4.2.8.3.4.4.4* 5.4.5.4.2 * *3 5.4.4* 5.5 * *2 3* 5.6.1 APPX B APPX E * *5.6.4.3 * *5.1 APPX C APPX E * *5.4.4.6.2.4.3 5.2 5.4.6* * *5.5 5.4.3 * *1.3 5.5.2 N/A APPX D APPX G * *5.4 * *5.5.2 APPX A APPX D * *5.2 N/A * *5.8.4.1 5.4 * *1.8.3 5.2 5.5.4.6* * *5.3 5.2.4 5.4.MIL-STD-973 INTERIM NOTICE 1 (DO) APPENDIX K TABLE IV.4.4.1 5.4 * *5.3 5.2.3 2* 5.8.1 5.4.4.6.4.4.4.1 5. .4.4.6.6* APPX B APPX E * *5.8.3.8.4.2 5.4.4.5 * *5.4.4.2 5.5 5.8.)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))+))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))).2 * * .3.6.3 5.2 5.8.4.1 5.4.4.2 * *5.2 5.4.2.8.3.3.4.4 5.4.6.4.4 5.4.4 5.1* 5.1.4.4. Cross reference from MIL-STD-481B (15 July 1988).2.1.2.1 * *5.4.7* * * N/A APPX C APPX E * *5.4.1 5.2 * *5.3. Cross reference from MIL-STD-480B (15 July 1988) (continued).4.2* * *4.4.4.3 5.5.4* 5.6.1 5.4 5.1 * *5.3* * *4.6.8.4.4.4.3.4.7* * *5.4.2* * *5.2 5.6.4 .3 N/A * *5.3.4 5.4.3 5.6.4.4* APPX A APPX D * *4.1 5.4. MIL-STD-480B MIL-STD-973 * *MIL-STD-480B MIL-STD-973 REQUIREMENT REQUIREMENT REQUIREMENT * *REQUIREMENT 5.5.8. +))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))).2 5.3.

Paragraph numbers from MIL-STD-973 followed by an asterisk (*) address the MIL-STD-483A requirement but do not necessarily require the exact same activities.3 . the requirements from Section 4 of MIL-STD-1521B are now essentially repeated in MIL-STD-973. Most of the requirements formerly contained in MIL-STD-1521B.5.3.6 Cross reference from MIL-STD-1521B (5 June 1985).2. those subparagraphs are also applicable unless a specific lettered subparagraph in MIL-STD-973 is cited. K. Paragraph numbers from MIL-STD-973 followed by an asterisk (*) address the MIL-STD-1521B requirement but do not necessarily require the exact same activities.5 * *5.3 5. K. Appendixes G.2. Cross reference from MIL-STD-482A (1 April 1974).3 APPX III DELETED * *4.5 * *4. were incorporated into MIL-STD-973.2 DELETED * *4.2. H.2 APPX II APPX I [EYE] * *4. TABLE VI.5 Cross reference from MIL-STD-1456A (11 September 1989).5.2 5.1 5.2 DELETED * *5. Where lettered subparagraphs exist in MIL-STD-973 under the numbered paragraphs listed.1 5.2 * *4.3.5 APPX I DELETED * *4 5. Table IX provides a direct cross reference between each of the paragraphs contained in MIL-STD-483A and the related paragraphs in MIL-STD-973.5.4 Cross reference from MIL-STD-483A (5 June 1985). and I. Table VII provides a direct cross reference between each of the paragraphs contained in MIL-STD-483A and the related paragraphs in MIL-STD-973.5. MIL-STD-482A MIL-STD-973 * *MIL-STD-482A MIL-STD-973 REQUIREMENT REQUIREMENT REQUIREMENT * *REQUIREMENT 5. NEW PAGE 226d .))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))K.MIL-STD-973 INTERIM NOTICE 1 (DO) APPENDIX K +)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))).5.1 DELETED * *5.3. Table VIII provides a direct cross reference between each of the paragraphs contained in MIL-STD-1456A and the related paragraphs in MIL-STD-973.

3 Figure 6 DELETED * * 5.9.1 Figure 7 DELETED * *3.2 N/A * *3.2. MIL-STD-483A MIL-STD-973 * *MIL-STD-483A MIL-STD-973 REQUIREMENT REQUIREMENT REQUIREMENT * *REQUIREMENT 4.2 N/A * *3.11 APPX J 80.5 N/A * * 5.4.2 Figure 2 Figure 1 * *3.1.2 80.1 N/A * *3.1 Figure 5 DELETED * * 5.2.7 * *3.3.10 DELETED * *3.5.1.2.3.4 5.4 APPX II 5.4 DELETED APPX V [MIL-STD-490] * *3.3.3 80.6 5.2 5.4.2 N/A * *3.4* * *3. .4.4.4 Figure 4 [MIL-STD-490] * *3.4.3.4 N/A * *3.3.1.4 N/A 80.3 DELETED 80.15 Figure 15 DELETED * * .4.1.6.6.4.MIL-STD-973 INTERIM NOTICE 1 (DO) APPENDIX K +))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))).5 5.1 Figure 1 [MIL-STD-490] * *3.4.1.9.4 70.4.1 5.3.2 5.1 5.5 N/A * *3.8 5.2.7.5 * *3.3.5.14 [MIL-STD-490] Figure 14 DELETED * *3.4 5.1 5.8 5.4.13 DELETED Figure 13 DELETED * *3.1 N/A APPX IV DELETED * *3.4.4.7.7 APPX B APPX VIII * * DELETED 80.2 Figure 12 DELETED * *3.4.4.3.3.3.3.7* * *3.1.4.4.6 80.3 N/A * *3.* *3.2.2 4.6 Figure 11 DELETED * *3.4.10 5.2 N/A Figure 8 DELETED * *3.9.1 5.4.1 N/A * *3.3.6* Figure 10 DELETED * *3.4.3.4.9.1 4.2 [MIL-STD-490] APPX F * *3.2 N/A 80.3 N/A * *3.2 * *3.3.3 APPX III [MIL-STD-490] * *3.4.5.2.5.1 Figure 3 DELETED * * 5.3.3 DELETED Figure 9 Figure 11 * *3.4.9.3 5.3 [MIL-STD-499] APPX I APPX A* * *3.3.5 80.4.1 [DOD-STD-2167] APPX VII 5. Cross reference from MIL-STD-483A (4 June 1985).9 5.4 80.)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))NEW PAGE 226e TABLE VII.3.3.6 * *3.4.4.1 * *3.4.4.9 5.6 [MIL-STD-490] APPX VI [MIL-STD-490] * *3.5 [MIL-STD-490] * *3.1* * *3.1.3.6 * * 5.1 5.3 5.3.4.5.5.5 5.3.7 [MIL-STD-490] * *3.12 APPX H 80.8 80.7.

1 5. A.13 * *5.9 * *5.2.5.2.2 5. Cross reference from MIL-STD-1456A (11 September 1989).1.)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))- TABLE VIII.10 * *5.3 A.5.2 5.2.6 * *3 (Appendix A) 3 5.2.5.2 A.5.5.12 * *5.5.1.11 A.5.5.1.1.2.2.4 5.1.5.1.3 A.6 (incl subs) A.5.2.3 A.5.2 A.7 (incl subs) A.4d 5.12 A.5.6 5.6* APPX XIII N/A * *APPX IX Figure 19 DELETED * * APPX B * *APPX X APPX XIV [IN APPX D*] * * DELETED * *APPX XI DELETED APPX XV APPX J * *Figure 16 DELETED Figure 20 DELETED * *Figure 17 DELETED * *Figure 18 APPX XVI DELETED * * 5.2 A.2.4.4b 5.1.1.5 * *5.3 (incl subs) [MIL-HDBK-61* *5.5.1 A. +))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))).4 A. MIL-STD-483A MIL-STD-973 * *MIL-STD-483A MIL-STD-973 REQUIREMENT REQUIREMENT REQUIREMENT * *REQUIREMENT 5.1(incl subs) A.1.1.MIL-STD-973 INTERIM NOTICE 1 (DO) APPENDIX K TABLE VII.11 * *5.10 (incl subs) A.2.2.5.1.3 5.2 A.1 A.6 * *APPX XII APPX XVII [MIL-HDBK-61] * * .5.2.1 5.4.5 .5.4.5.2.5 * *5.1.8 A.1.9e * *5. MIL-STD-1456A MIL-STD-973 * *MIL-STD-1456A MIL-STD-973 REQUIREMENT REQUIREMENT REQUIREMENT * *REQUIREMENT 5.5. Cross reference from MIL-STD-483A (4 June 1985) (continued).1.2.)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))- +))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))).1.14 * *5.1 5.1.2.5.2 A.3.1.2.4. NEW PAGE 226f .5.5.2.2.6b * *4 (incl subs) 4.5.2.2.5.2.4 A.5.7 5.1.1.9 (incl subs) A.1.

3a 80.5 80.4 5.6.3 5.3.6.1c 5.FCA 5.6.2.2.3 * *4.2 5.2.2.3k * *70.4.3. Cross reference from MIL-STD-1521B (4 June 1985).3f APPX I .6 5.2.4.4.6.3j * *70.4.1.4. NEW PAGE 226g .4.1b 5.4.6.4 5.4.6.3.1 80.3.1 5.3e* * *70.5 5.3.6 5.6.6.3.12 5.5 5.2 80. Table X provides a cross reference between applicable paragraphs contained in DOD-STD-2167A and the related paragraphs in MIL-STD-973 into which these requirements have been integrated.6.2.3* * *4.3 80.6.5 * *4.3.3.5 5.6.1 5.6 5.4.8 5.4.6.9 5.4.1.2.5 .4.3 * *4.6.1.3 5.6.1.3c * * 80.1.3.6.3d * *70.1 5.1.1 5.2* 80.3 5.3.4.6.1 N/A 80.1.2.1.1.4.4.2.2 5.3c 80.6.7 5.3e 80.4.3.6.5 80.1.3i * *70.6.)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))K.3e * * 80.1.3.5 5.4 * *70.3 5.3.4.1 * *4.6.3.1 5.6.3.4.6.6.1 80.4* * *70.2 5.2 * *4.2.2 80.3 5.6.1.2.6.6.6.1 5.1a 5.3a * *4.8 5. MIL-STD-1521B MIL-STD-973 * *MIL-STD-1521B MIL-STD-973 REQUIREMENT REQUIREMENT REQUIREMENT * *REQUIREMENT 5.1 5.2.1.3 5.3.2c * *70.3j* * *70.3.2.3f * * APPX B * *APPX G .6.4 80.6.3.4.1.6.6.2d * *4. The requirements for various configuration management activities contained in DOD-STD-2167A have been integrated into the overall configuration management requirements in MIL-STD-973.3.10 5.3g * *70.4.3 80.1.3h * *70.2 5.3.1 * *4.2a 80.7 5.3l * *70.1.3i * *70.2.6.6.3b * * 5.2 5.3b 80.3.3.6.3.MIL-STD-973 INTERIM NOTICE 1 (DO) APPENDIX K +))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))).4 5. TABLE IX.1.4.6.6.6.2.2.6.6.6.3.1 5.3 5.2.6.4 N/A * *70.6.4 5.FQR DELETED * *70.1 5.4 5.1 80.1.2.3.6.2e * *4.6.6.4.2 5.3a 80.1.6.2.6.2 * *4.4.6.3.6.3.10 5.6.6.PCA * *4.3h * *70.3b 80.3d* 80.3.7 Cross reference from DOD-STD-2167A (29 February 1988).4.1 APPX H .2.3.3d 80.11 5.3 5.6.3.3g * *70.3.1 5.2 N/A * *70.3.9 N/A * *70.3.2 5.3.4.

1.4.3.6.3.5 5.3.1 5.5.3.8.10 4.3 5.3.3.5 4.3.6.5.1 5.5 5.4.3 5.3.3.7.2 5.6 5.2.6.3.3 5.3 * *4.9 5.5 4.6.3.3.3.5.3.1 * *4.1.5 4.5 5.3 5.3.4 * * 4.6 5.3.7.2 * *4.3. NEW PAGE 226h .MIL-STD-973 INTERIM NOTICE 1 (DO) APPENDIX K +))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))).3 * *4.3 * *4.3 * * 5.3.3.4 5.4 * *4.2 5.4 5.7.3 * * 5.3.2 * *4.7 5.6 5.1 * * 4. Cross reference from MIL-STD-2167A (29 February 1988).6.5 4.4 5.)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))- TABLE X.7 5.1.1. MIL-STD-2167A MIL-STD-973 * *MIL-STD-2167A MIL-STD-973 REQUIREMENT REQUIREMENT REQUIREMENT * *REQUIREMENT 5.1 * * 5.3.5 5.3.5.5 .3.6 * * 5.3.5 4.3 * * 4.7.6.5 * * APPX H * * 5.3.4 * * 5.1 * * 4.8 5.4 * * 5.3 5.5 5.4.3.3.3.5 5.2 * * 4.

. . .5.5. .1. .5.5 222-223 2 6 4.2. .5. .5. .2. . . .6.12 D. . . . . .1.1.8. .3. .3.1.11.8 5.1d 4.1 5.6. .MIL-STD-973 INDEX PARAGRAPH CAGE Code . .11.4. . .6.4.3 A.3. .1.2. . .8 177 G.5. .5.1.2.6. .1.1c 191 H.1 30 C.5.5.2.1.13 H.1a 5.5.3.1. Configuration audits .8b 191 H. .5. .2 5.1 5.3. .5.4.2 143 D.1. . .5. . 5. .5.2 161 E.3.1.7 190 H. . .2g 4.1 5.7 182 H.4. .5.3 5. . .2.1. Class I ECP . . .5.1. .6. . . .6. .2.2.5. .1.1.1.4 4. PAGE 5.1. .1c 199 I.3 A.6.5.5.1 135 D. .4. .13 A.3.4. .7 A.4. .5.5.8. .5. . .1 5.4.1.3.7 5. .6.1.3. . 227 . .3 5.4.1c 188 H. .1.2.1. .1.2 5. G.7 ii iii 19 19 126 35 38 38 38 38 39 41 43 18 22 64 64 65 65 123 126 128 200 CALS .6.1.1b 193 H. 144 D.2.1.3b 189 H. .2 5. .2.5.2 171 F. .7.5 210 I. F.1.2 160 D.

4 Configuration item selection . .1 5.3 5. . Configuration status accounting . .2 3.7c A.1 3. . Configuration management planning .18 3. .3 6. .5. .4 5.2. .5 A.5 I. .3. . .1 5.1b 4. 3.5.4.1.2 4. . .1b 5. .MIL-STD-973 PARAGRAPH Configuration baselines .5 4. .26 4. .5 5. .5 3.77 4. . .3. . . .33 3.19 3.5.3.4.2 5.3 5. 228 .6 5. .8 6.11 A. .1 PAGE 8 8 9 25 27 27 33 33 7 8 11 15 18 21 22 24 26 32 33 33 34 59 120 120 123 126 127 4 8 120 204 26 18 4 9 10 18 22 29 63 120 120 Configuration control. . .4.1 5. .22 5.4. . .1 3.19 3. .5 5. .3.3.4.11 Configuration control board .4 5. . . . . . .1 5. .1 4.4.4 6. .5 6.7.24b 3.2.3. .1.3. 3. . . .20 6.4 5. . . . 3.2. . .2.

.33 4. .3. Developmental configuration . .1.2.2. . .5.5c D.1 D. .2i D.4. .1.2. . .1.4a(3) 5.3l(5)(7) 5. 229 . .5.2 I.1 D.3.12 A.5.1. .3.5.5.5.2. .5 D.1.1. . . .2.13 D. .7. . . . .3 D.1.6.1 4.6.5.5 3. .1.4.2 B. .5 Appendix I 3.2. .6b D. . .3j(3)(5) 5.2.5.5.1 3. . . .3. . .3.3.1c 5. . .1e PAGE 121 123 127 186 32 111 112 xii 63 202 4 7 30 31 44 74 88 89 118 131 131 132 143 144 145 145 146 147 148 149 151 156 159 161 171 178 189 199 206 11 18 21 25 CSA data elements . .5. . . .23.23. .5.7. .5 H.3r Appendix I 5.7.4.5.6.1.3l(8)(9) 6.1. .5. .18b D. .5 A.1. .5. .6.16 D.1.6.5.1. 5. .5. .8.2. .2d B. .2.3 6. .5.5 5. CSCI .5. . . .MIL-STD-973 PARAGRAPH Configuration status accounting.5.3 E. .5.5 D.4 5. .8.6. .15b H. . .12 APPENDIX H COTS . .1.3c B. .1. .21b D.1 F.5. 6.6. . .3l 6. . .13 5. . .3. .

5.2.3 5.1 54 6.1 5.MIL-STD-973 PARAGRAPH Developmental configuration.6b 5.4.5. . . .5. . .5. .4.3.5. .4.1g 25 5.5.2 5. .2.4.1.21(a)(b) 146 D.5.3. . .4.3.3e 6. . 3.2. . .4.5 211-221 Engineering change priorities . .4.5 5.3.5.37 5.5. .2f/i 132 D.5. .2.2. . . .2. .3.2. .4.5 121 A.b Document numbers .2.1.3 5.2. . . .5b 4.9.7 A. . . . .23.2.5.3 5.1 5. . . . . .1. .4.3 A. .4. .1. .3j(3) 6.5.6g 22 5.1.2.3. .2.1.1. .9e B. .4. .1.2 5.1 147 D.2. . .4.2.6.1 5. .2 5.2.1. .4. . .2 11 43 8 22 22 28 34 34 34 36 36 36 37 38 39 45 45 48 48 230 .3.3.4.6.1.4. .1f 193 I.1 5. .1.3 5.4. 5.5.1.3. . . .17 173 F.15 178 H.5 A.3.4.1.20 4.2.1 52 5. 5. .3e 189 H.12b(6) 128 B.3.2h PAGE 26 74 109 121 125 126 30 126 131 Effectivity.8 154 E.4. . Engineering changes .2.5.3.5 5. . 4. .3.3.3.5.2. . .4 3.2.1g 5.

3 6.2.9d Appendix B B.6.3.6 57 5.2 B.1.2 141 D.3.2. . . .2.3c 6.5. .4.3e/f 6.3f 49 5. . .1 B. 11 28 87 111 118 119 121 126 129 129 130 130 131 198 212 231 .1 B.3.1. .1.2.2.2.1 132 B.3.3s/u 112 6.2. . . .5 133 D.1.3h I.2 108 6.4.2.4 50 5.4.4.2.2 H.8.1 59 5.5.2. .6.2.1.4.1. .3f 87 6.1 50 5.2.2.27 148 D.5.2.1.3.4.4.4.4.2.5.2.1 51 5.5. .3 50 5. .1.3.3.6. .4.1. B.5.5.3 48 5.4.2 50 5.1.4.3 132 B. .4 60 5.5 204.1 59 5.5.4.4.1 82 5.1 199 Engineering release .1.2 51 5.4.6.5.4.2 130 B.4.3k 6. .5 A. . . .3.8.5 5. .4.2.6 49 5.4c 133 B. 3.1 49-50 5.3.8.5.4.1.3. .MIL-STD-973 PARAGRAPH PAGE Engineering changes.5.3.1 129 B. .1.4 120 A.1. .6.5.5.6.2.5.4.5.40 5.1. 5.4.1 141 D.2.6. .11 155 H.12b(2) 128 B.

1 C. . . . .5.1 5. . . . .MIL-STD-973 PARAGRAPH ERR . . . .1 H.3.3. . . . . .7. .4. .10 E. . .5 Formal ECP . . .11. C.8 C.2 5. .1 I.2b 6. .3.3. .5 PAGE 11 29 134 134 135 137 204-212 8 12 25 32 89 126 136 203-224 41 43 45 5 8 12 22 67 5 13 32-33 111-112 127 10 30 63 82 118 132 135 171 186 187-188 Firmware . .14. .4. .3q A.4 H. . . . .3. 232 . .6.17 3. .1 3.51 4.3. . .6. . . . .5.2.3l A. . . . . . .1. . .5. .6.1 5.5. .4. . .2 3.2 C. . . .4. .3. . .2. . . . .1.2.6. . .16 3.7.1af 3.2 6.26 5. .4 5. .2 I. . .3. . . . .2.3. . . . . .2.3. . .7 5.2 C. ICWG .2.7. . . . . .3.2g C.60 5. .9e Firmware .5. .5. .6. Identification numbers .41 5. . . .44 5.5.1. .2 5.4. . 5.1z 3. . .2.1 Functional configuration audit .5. . .3. . . . 3. .2 5.5.5. .5. 3. .3a B. . .5.10 3. .

.1.6. . .2.2.2 5. .20 146 D. . .1 5.3. .10 C.1 63 6.2 5. . .5. . . .3c 37 5.3 5. .6. .3d 118 D. 3. .2.3 151-152 D.1c 117 6.5. .3. . .6 142 D. .3. .4.3. . .2 36 5.5. .1r 4 3. . .7 190 H.2. .5.2. .3.3f H. .2d 40 5.1.2.2 5. .11.3 5. .4. .1 5. . .5.1.6 149 D. . .3c 5. .1.2.3.4. . .2 30 5.5 211. . . . .1 1 3. . .5.2g 19 5.1ah 5 3. .1. .1.89 16 4.4. . .2. .5.3. .3. .5.5.1. . . .4.4.3j(4) PAGE 5 6 32 71 83 127 136 39 51 6 26 26 26 74 87 196 Justification codes . . . .6. . .3 28 5. . . .1.3.4.3c 49 5.2 197 I. Library .5.1ai 3.5. Library. . .MIL-STD-973 PARAGRAPH Interface requirements .2 3. .2.6.3. . ii 1.1. .2. .21 173 H.5.2. .1. .3.2.5. .4. . .1aa 5.3.2. . .55 13 3. .3.15 155 E.2.7.3z 113 6.3 Logistics .5.2e A. .3.5.2 26 5. . .2. . 213 233 . .3.3. 5. .6.2. . .

MIL-STD-973 PARAGRAPH Lot numbers .2.4. . .5.3 51 6. . .5. . . .1g/h H. . 3. .5.5. .1.3s 5 8 14 22 74 41 45 112 Physical configuration audit .1.1.1 J. . .17 H.1. 5.2. . . .2.1. .1.6 E.1.1.4 H.2. .1. . . .5.73 4.3.1 5. . .1. . .3l/r PAGE 25 30 173 199 10 60 114 178 191 193 194 197 197 198 200 207 215 225 225 5 14 32 111 Modification . .2. . . . . . NDI .7 59 Appendix G 181-185 I. .13 H.3.1aq 3.5.5.1. .3. .2. . . . .4. .1a 3. . 5.3 5. .1. .5. . .5. .1 H. .3. .1. . .4. . .2. .3 I. . .5 216 3. . . . .3 6. .4. .2.6. . . . .5.1am 3. . .1.3w 113 Appendix E 170-175 234 .3 H.7 5. . .6.68 5.8 H.3ac F.5. . Requests for Deviation . .6.4.3.2.6. .6 6.2. .17 3.1.1.1an 5 3. .5 I.6. .5 J. .3.4.4.1e H.2 3. . . . Notice of Revision .3. . . . Preliminary ECP . .5.70 14 5. . .8. . . . .2.7 5.5.2. . . . .7.1g 5.1 6. . . .

. 15 235 .1. . .6 7 3.3. PAGE 5. .2. . .1f/g 193 I. .3 159 F.5 203.3. .4. . . . . .11-3.16 7-8 3.2. . . . .5. . .3.5.4 147 E.5.1. . . . . . Serial numbers .1.23 147 D.MIL-STD-973 PARAGRAPH Requests for Waiver .5.33 11 3. . . . .1. .5.6.3ac 114 D. .1h 195 H5.1.1ax/ay 6 3.5.2. . . .4 6. Serial numbers .5.3x 113 Appendix E 170-175 3.2. . ii-iii 1.1.4.1.2.5. . . .1 5.5 219-223 Appendix J 225-226 5.5. .4.5. .1. . .5.4 198 H.1.1.1. .3. . . .5.5. 3-82. .8 64 6.1. .3m A. .5. .1 3 3. . . .21 146 D.5.5.3c 49 5.15 178 H. . .23 9 3. . . . .1 130 B. .1.1.1. .5.3 189 H.74. .6. .4 54 6. .15 178 H.2. . . . . B. .5.1 1 2. .6 7 3.60 13 3. .2.4. .5 217-220 Software .9 31 82 111 126 Retrofit. . .80 15 5. .3 200 I. .1. . . .46 12 3.2 156 D. . .5.2e/f/i 131 D. 214 I.6.6.17 173 F.1n/p 4 3.23. . .

.4.6 160 D.3f 49 5.4.4. .5 189 236 .1d 41 5.4 44 5.5.2. .1.3.5.2. 25 5.1.3 151 D.3.1.95 17 4.2.21b 146 D.2.2c 48 5.1 5.1. .3.3f 87 5.3e/f 109 6.3 52 5. 89 6.1.1.5.5 147 D.2.6.6.5.89 16 3.2. .2 136 D.2d/e 83 5.2.86 15 3.5.2 129 B.5.3. .1.6.1.3.3.3a 66 5.5.3.5. . .5.18b 145 D.3i 110 A.4 54 5.2.1.3.2.3.7.5.3.3.2. .1.3.1.2 131 C.MIL-STD-973 PARAGRAPH Software.3.3 28 5.4.6.1b(3) 35 5.4.6.21 173 H.2.5.3l 88.2.3 82 5.3. .3.6.5.1. .5.5 5.1 186 H.2. 3.5. 26 5.3 5.7.6.5 153 D. . 189 H. PAGE 3.7 161 E.1 18 5.3.3.1.6 149 D.23.5.3j 73-74 5.4. .1.1. .1.3.6.2 29 5. 5.8b 150 D.4.4.7.5.93. 30 5. .6.1.9b/e 126 B.3.6.2. .3.11.1 31 5. .3.1.5.5.3.2b 32 5.3f.3.5. .5c 159 D.

.5. .2 225 J.3.2.5 5. . . . . .6.2.4. . .1c 226 Software identifiers . . .1.1.1. . . . .1. . .3.5 22 5. .1.5 206-224 J. . .5. .5.3w/x D.1.5. . Work breakdown structure .1.5. . . .3e D.5. .5.5. Technical reviews .2.1. 237 .2. . .7 H. . .1 H.1.1. . .6. . .3.1.5i D.8 H.1.6. .4. . .4. .1b A. .9e 3. . .2. .3 196 I.3n 6.4.97.3e 6.4.5. . .1 D.6 57 A.6.84 15 4.2. .4.3. 190 H. .2 I.222 5.3 6. . .1.11f 127 Appendix F 176-180 I.5. . . .5.3. . 5. . .2.2. .4 3. . .5 207.1.4.5.2 58 120 16 24 120 125 6 17 24 Supersession . . . . .4 A.1.1.92 5. .5.1.1 194 H.4. .1. .3 6.6. . . . .5. Specification Change Notice .6b 3.2.1bg 3.4. . 3.5 J.1az 6 3. J.5.7.3 H.2. 3. . .1b(3) 5.5. .5.MIL-STD-973 PARAGRAPH PAGE H.1.5.98 5. .7 H.2 30 31 126 14 35 87 111 113 152 154 156 157 190 191 194 197 213 225 Spares .66 5. .

AV.17. SH. NM.DO Project: CMAN-0022 Review activities: Army . 14.MIL-STD-973 CONCLUDING MATERIAL Custodians: Army .26. YD Air Force . ET. YD Air Force . CE Navy . MD. SM. MC. TE.CG. OS. GL. MI. 24. PT Navy . IE.10 NS . SC. 13 238 . CR. TM.HD.AR Navy .AM. OS.EC. LM. EA. ER. AT. MR. SH.TCM Preparing activity: OSD . AL.AS Air Force . 10 DLA .DH Other Government Activities: DC User activities: Army . ME. AC.

Sign up to vote on this title
UsefulNot useful